Hi all, I have an project to set up the Gateway G650 and I will have a few PRI (local # and 800) soon coming in, please give the a list of steps I need to prepare (like Add DS1, Signal Group and Trunk Group ...)and how to test it or you can point me to where I can get instruction how to build this from the scratch. On this G650 box I already have IPSI, MEDPRO, DS1 and some Digital cards, I mean this box is ready to go. Appreciate for your help.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SETTING UP G650
- Thread starter Shawnltd
- Start date
Any other G650s on that system? I'd imagine so if they're still adding them. Follow that lead.
Get an old CM implementation doc, basically you just ssh or telnet to the IPSI on the services port, give it an IP/mask/gateway, program that cabinet and IPSI IP in CM, if you're lucky, your cabinet is up.
Then you gotta add node-names for all the IP cards and add ip-interfaces for them. The rest is pretty well the same as a G450.
You'll probably need to learn about data modules too. Why are you even adding a G650? Presumably it's <5.0 and can't take a G450? Or leftover spare parts?
Get an old CM implementation doc, basically you just ssh or telnet to the IPSI on the services port, give it an IP/mask/gateway, program that cabinet and IPSI IP in CM, if you're lucky, your cabinet is up.
Then you gotta add node-names for all the IP cards and add ip-interfaces for them. The rest is pretty well the same as a G450.
You'll probably need to learn about data modules too. Why are you even adding a G650? Presumably it's <5.0 and can't take a G450? Or leftover spare parts?
- Thread starter
- #3
Kyle, actually We have total of 4 working G650. just disconnected 2 and relocate them to a new V-lan at new location. That left the other 2 that are currently in operation still. Then starting to port local and 800 number to 2 cabinets in the new place, the IPSI in the 2 moving G650 were already given an IP/mask, does this sound like add node-name is done at this step?
Presuming they were single PN G650s (one IPSI each).
If the G650s you're installing already had their own port network and medpros and other IP cards, then they're already "built" in CM. Once the IPSI is up, it downloads the config for the cabinet - so the medpro in slot A14 might have nodename medpro_4a14 and an IP in there. If you disable the ip-interface 4a14 to be able to change node-names ip and pop a new IP address in there for the medpro, that's all that's involved in making it work on the subnet at the new location.
From there it'll autodetect the cards in it, or you can manually do that with "change cabinet" to say a DS1 will be in slot 4a10,11,12 if you want to start programming them before they're in there.
Otherwise, if you told me you wanted to move an already working PN from one place to another and you IP'd the IPSI properly, then you don't gotta do a thing beyond follow the cabling to bring it up as the same port network. Fix the CLAN, MedPro and VAL IPs and have fun.
Renaming things, changing the name of location 4 from old_office to new_office, ARS, stuff like that, sure, that's work, but not inherently different than any other gateway type. Troubleshooting can be a pain though.
in /var/log/ecs are logs that'll have IPSI sanity errors. If you're missing QOS on the IPSI, that's when the cabinet gets all jumbly because the control messages are being lost. Its old stuff and might not autoneg nicely or lock down nicely either. So depending on what kind of switching is there, watch out for speed/duplex mismatches. Those'll drive ya crazy. Otherwise, the worst part sounds like the heavy lifting and cabling.
If the G650s you're installing already had their own port network and medpros and other IP cards, then they're already "built" in CM. Once the IPSI is up, it downloads the config for the cabinet - so the medpro in slot A14 might have nodename medpro_4a14 and an IP in there. If you disable the ip-interface 4a14 to be able to change node-names ip and pop a new IP address in there for the medpro, that's all that's involved in making it work on the subnet at the new location.
From there it'll autodetect the cards in it, or you can manually do that with "change cabinet" to say a DS1 will be in slot 4a10,11,12 if you want to start programming them before they're in there.
Otherwise, if you told me you wanted to move an already working PN from one place to another and you IP'd the IPSI properly, then you don't gotta do a thing beyond follow the cabling to bring it up as the same port network. Fix the CLAN, MedPro and VAL IPs and have fun.
Renaming things, changing the name of location 4 from old_office to new_office, ARS, stuff like that, sure, that's work, but not inherently different than any other gateway type. Troubleshooting can be a pain though.
in /var/log/ecs are logs that'll have IPSI sanity errors. If you're missing QOS on the IPSI, that's when the cabinet gets all jumbly because the control messages are being lost. Its old stuff and might not autoneg nicely or lock down nicely either. So depending on what kind of switching is there, watch out for speed/duplex mismatches. Those'll drive ya crazy. Otherwise, the worst part sounds like the heavy lifting and cabling.
- Thread starter
- #5
- Status
Similar threads
- Locked
- Question