| | #1 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | CS2000 Geo Redundant Can anyone please advise me as what is supported on a carrier grade GEO Redudant CVM solution. 1. Does the GEO Redudant CVM support 2 or 4 ERS8600's 2. Does the GEO Redudant CVM support Hybrid configurations, where by the Legacy Message Switch is still incoporated into the New SAM21/Compact Call Agent infrastructure. Any high level diagrams or powerpoints describing how this solution is put together, would be much appreciated. CarrierGrade | ||||||||
| | |
| | #2 (permalink) | ||||||||
| Junior Member
Location: Chlt-NC Rep Power: 6 ![]() | Not sure what you mean by CVM. I have worked on a geo CS2100, and in the last 4 months have worked thru the process of converting a SL100 SuperNode and an SL100 SNSE to CS2100 systems (non-geo). 1.) I believe geo systems are now configured with 4 ERS8600's. There were issues with the ability of IP phones, and gateways losing connectivity to the core under some types of failure conditions. I think by going to a 4-8600 configuration it prevents outage conditions. 2.) In a geo split, only the core that is located where the MS resides connects to the MS. The geo site with the MS is equipped with two SAM21 shelfs. One shelf only contains an MC card. The MC (Message Controller) has two ports on it. One port goes to MS0 the other to MS1. The "primary" SAM with the Call Agent also has an MC connected in the same manner. Per the geo planning guide, if you lose your core at the host/tdm site the core at the remote/geo site won't do much for you. Personally, I think geo split is best when you are either all IP, or you have MG9K's in front of your LGC's/LTC's, and you are using IP trunk gateways. This way, the whole backbone is IP and the components can talk to either core. No more ENET or MS. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | Carrier Grade CVM Geo Solution Thanks for responding, The CS2100 is an enterprise solution, based on the CS2000 aka CVM geo-redundant (greenfield/hybrid) solution. The research I've collected identifies the CS2000 geo-redundant solution with 2 8600 HA, with a hitless upgrade. From what I gathered, in the carrier space, the Geo-redundant hybrid (compact call agent) solution that have MC blades use only 2 8600's HA, and still keeps the 5 9's reliabilty. This CVM Geo redundant engineered solution is outlined in the Nortel Carrier SEB's (Sales eng. bulletins). The Enterprise CS2100 has it's own SEB's outlining their approach to 5'9's reliablity. The 4 router geo solution is not supported in the Carrier space but is supported in the Enterprise space. I don't understand why Enterprise geo solution uses a different approach (4 8600 Single cpu vs 2 HA 8600's), as the Enterprise CS2100 geo compact hybrid is based on the Carrier CS2000 geo compact hybrid. Seems to me the more components (8600's) you have, the more difficult it is to engineer a cookie cutter solution. ![]() | ||||||||
| | |
| | #4 (permalink) | ||||||||
| Junior Member
Rep Power: 4 ![]() | We have a GEO setup and use 4 8600's. They used to install them with 2 but it limits redundancy. The sales docs do say 5 9's, but after working on them and also talking to other customers that doesnt seem to be the case. Each upgrade we (Nortel) have done we have had a outage. | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| UK BUYER WTB YOUR REDUNDANT PBX TELEPHONE SYSTEMS | tdsystems | Wanted to Buy | 0 | 02-24-2005 08:41 AM |
| Redundant cpu problem | justzikle | Meridian Systems | 6 | 12-06-2004 01:56 PM |
| REDUNDANT ELANS? | jstyles | Meridian Systems | 3 | 11-30-2004 11:39 AM |
| Opt 11C redundant? | da_phone_dude | Meridian Systems | 4 | 11-16-2004 06:24 AM |
| Mitel SX2000Light Redundant Hard Disk | 2004pbx | Mitel | 1 | 02-24-2004 01:40 PM |