Rebuilding a Sig. Server 2

[dogg1]

If I wanted to rebuild a Current signaling server all I would need to do is boot the servers with the Linux OS for cots server CD and follow the install procedures correct? Or is there more to it than that?

 

[janaya]

Just don't reformat the admin partition. that will be your backup. why the rebuild?

 

[dogg1]

I'm not worried about the backup, I only have one test phone on the Sig. Servers. When the sig servers were built not all the patches were put in for some reason and we started to get Heap memory errors under a few of the headings in element manager. I'm thinking this has caused some issues so I would like to rebuild them while we only have 1 set on them.

 

[janaya]

Ok.

then put in the LINUX flash card, or OS DVD and roll with the installation.

Make sure you load the three individual patches (in the correct order). Then just reconfigure in UCM and commit/deploy the applications.

I would start the OS load about 15 minutes before going to lunch. Once you verify your settings start the rebuild and go to lunch. It will be done when you get back. this helps techs that aren't real patient (like me). so we don't end up staring at the screen.

Hope this helps.

 

[BkMesser]

I had to do this due to a bad drive. It is for a release 6.
I wrote this doc so I would remember how to do it if I needed to again.

Feel free to update or share.



Rebuild Information Sheet for IBM x3350 Signaling Servers
The reference book for most of this is: NN43001-315,
1. Plug serial port from Procom PC into serial port on back of signaling server. Connect at 9600/N/8/1. You need a null modem db-9 to db-9 cable to do this.
2. Power up server.
3. You should come up with a screen that asks you if you want to use com1 press Y for yes.
4. After you select com1 you should see a message about the OS is not found on the hard drive.
5. Put CS1000 Linux Operating System on COTS Server DVD in the DVD drive.
6. The system should start running and you should end up at a Base Configuration Data Selection Screen.
7. Fill in Network information.
8. Fill in Time zone information.
9. Set primary and secondary DNS server IP addresses.
10. Correct Time if needed.
11. Change root and Nortel passwords.
12. The system will start the installation. I estimate about an hour. It formats a bunch of areas and then installs Linux.
13. The system will run a hardening utility and reboot.
14. The DVD will eject. Take it out of the drive.
15. Connect to the sig server with a crossover cable. Change your computer’s IP address to be in the range that can communicate with the ELAN IP address of the signaling server.
16. Using WINSCP copy patches to the signaling server. You will have to use the “nortel” as the username and your passwor from step 11. Put the two *.ntl patches in the var/opt/nortel/patch folder. Put the service pack in the var/opt/nortel/patch/sp folder.
17. Load the Linux patch first using the “pload” and “pins” commands. The system will reboot.
18. Load the Patch Web patch second using the “pload” and “pins” commands. All of the Nortel applications will stop and re-start, but the system will not reboot.
19. Put CS1000 Linux Applications DVD in your computer’s drive. Browse via IE to the ELAN IP address and load software from the applications CD. Then deploy the applications that were on the old server.
20. Load the Service Update using the “spload” and “spins” commands. All of the Nortel applications will stop and re-start, but the system will not reboot.
21. Take old server down.
22. Remove the hyper links from UCM.
23. Install new server. Power it up.
24. Browse to the ip address of the new signaling server. Do the security configuration. You will have to put the username and password and ELAN IP address of the UCM.
25. The system will tell you the security server will reboot. The UCM server does not reboot at this time. Wait 5-10 minutes. Browse to the ELAN IP address of the new signaling server. If you get logged into it and the security configuration button is greyed out then proceed.
26. Login to UCM and browse to the new signaling server via the new EM hyper link. Go to IP Network/Nodes: Servers, Media Cards. Click on the node ID and hit Save. Then hit transfer now. Then synch all of the elements that require it.
27. Restart applications on server that was replaced.
28. Login to the switch and do a stat serv in LD 117. You will get TBD in the STATE field of the elements that were not changed. Wait a few minutes and that should change to Link Up.
29. Go back to the UCM server. Click on Secure FTP Token and the click the regenerate now button. Any elements that the UCM cannot communicate with will be in red at the top of the list.
• These are the Linux commands to gather this information from the signaling server you are replacing. (networkconfig --show) and (dnsconfig --show).

 

[KCFLHRC]

There is a tree view in UCM also that the existing server will have to be removed from. Dont forget the 2 base batches, then deploy, then service pack. Do the 2 base patches from the cli and the service pack from the web interface.

 

[dogg1]

KCFLHRC,

Even though I'm compleely rebuilding both sig servers I still need to remove them from the tree view?

 

[KCFLHRC]

If you are rebuilding all your sig servers then you wont have a UCM so it wont be necessary to remove anything unless you have a 3rd server. You will be wiping out everything if I understand correctly what you are doing.

 

[dogg1]

Yes, we only have one test phone on the sig servers.

 

[KCFLHRC]

Are your call servers vxworks? I'm assuming they are. If you are wiping out everything just start in. No reason to remove anything because you will be formatting the drives anyway. Good luck

 

[dogg1]

I have everything done including my users. When I try and access the EM i get an error talking about my login isn't correct. Is there somewhere special that I need to change?

 

[KCFLHRC]

You need to register your call server into UCM. Ld 117 REG UCM SYS

 

[dogg1]

Thanks KCFLHRC! That did it. I'm having issues with the VGMC Cards but that can wait til tomorrow as there are no phones on the Sig. Servers. For some reason I can't remove the VGMC's so I may have to remove the node and rebuild the node for them to take.


Thanks again for all the input.

 

[dogg1]

I have another issue. I still can't sync my 2 vgtmc cards up. I have tried rebuilding the node, reseating the cards but still wont sync. They are in the UCM security in LD 117 and they stat IDL on both cards but for what ever reason they wont sync. I noticed that they aren't on the elements page when you first log into the leader Sig. server. I also noticed that under deployment View->cs1000 Systems->Node X it show the old VGMC's. Does that need to be removed?

 

[KCFLHRC]

I would remove the old VGMC's. If they arent registering into UCM you will need to go into the command line on the MGC card and issue the command joinsecdomain, all one word and no spaces. Then it will prompt you to put in the Primary Security Server's IP address and the login and password for it.

 

[dogg1]

Actually in the PBX they show registered. The problem I think is with the SIG Servers and VGMC's not syncing together. In EM the Sig. Servers sync but not the VGMC's. I done four major sites and this seems to be my problem shild

 

[KCFLHRC]

Go into LD 117 and do a stat ucm sys refresh. Make sure they show registered in the Call Server. I would still register them as I stated earlier.

 

[dogg1]

KCFLHRC,

I did the stat ucm sys refresh and both VGMC's show registered.

 

[dogg1]

KCFLHRC,

Thanks for all your help. The joinsecdomain command in the VGMC worked.

Thanks for all your help!

 

[KCFLHRC]

Good deal, glad it worked.