CS1000 Survivability questions

[srcvh1]

Hello All,

I am about to get involved in an implementation of a survivable network and I have some basic questions I'm sure you experts can answer before I have dive deeper into the NTPs.

Here is the scenario:
I am migrating an existing Option 81C to a CS1000E w/1010 cabinets. The new layout of this has the cores in seperate locations across the street from one another.

They are adding 2 new SMGs at different locations

They are adding 3 new SRG50s at different locations

They are upgrading 2 Option 11s to SCPMG at different locations

Right now they are totally TDM. All of the sites are now standalone systems.

Here are my questions:
- Is this considered a High Scalability solution?
- Does this scenario implement Geo Redundancy?
- Do each one of the remotes require a seperate zone?
- What is the connection for each of the sites? Is it strictly the WAN, SIP trunking, or either.
- What IP considerations do I need to make at each location (all the SMGs are CPMG cards)
- I know that each SMG will get assigned it's own SUPL. What does the SRG get?

Sorry if some of these questions seem basic. I just need some starting points before I start figuring out what NTPs to study.

Thank you all

 

[phones1]

Its a bit more of a design question but I'll add my view:

Geo redundancy = SMG you may see it refered to as G'Nway to be smg's they will have Ip requirement (look in NTP NN43001-507 System Redundancy Fundamentals)
High Scalability = a HA switch (redundant cores) again look at the above NTP.
Zones= It allows you to manage your bandwidth resources far beeter if each site has its own zone
SRG= didnt think this was supported at 7.5 as the BCM is end of life (look into it)

as for a more detailed info read the above NTP



Remember if it doesn't work hit it harder

Scott UK

 

[KCFLHRC]

High Scalibility and High Availibility are completely different animals. High Availability is Redundant Call Servers that share the same database. High Scalibility is groups of HA Systems that share some of the database. Geo redundancy basically replicates the database to another Standby Call Server. All of these systems require IP connectivity. Part of your configuration looks like Campus redundancy where you have your cores in separate buildings, this requires Gigabit ethernet for the Call Servers to talk to each other. Each site will require it's separate zone because you will most likely have to implement Zone based dialing for 911 purposes and local dialing. The NTP's for High Scalibility and System Redundancy Fundamentals will explain it all, they are very good. Looks like you have your work load for the next few weeks. You have lots going on here.

 

[srcvh1]

KCFLHRC, Great info! So it sounds like my scenario is HA, correct? Also if the SMGs are survivable, don't they have to be GR? I'm thinking that the GR schedule needs to be set up at the main to update the SMGs?

 

[KCFLHRC]

Yes, I think you have an HA with Campus Redundancy where your cores are located separately. Yes, if the SMG's are survivable they would be GR. You set up a schedule to replicate the database. The one I have I replicate it daily around 8:00 pm way before the midnight routine runs. After it replicates the GR sites do a sysload to accept the new database. The main site doesn't sysload though. The main and GR site will have different software packages. You also have to tell the MGC cards they have an alternate call server to register to. It's all explained in the NTP. Good luck, sounds like a fun project.