Rel 6 Installation Summary
CPPM Co Res Call server
(most of this is applicable to non CoRes systems except the deployment of CS in step 18)
- Create the installation compact flash card, optionally add the .NAI file for software deployment to the flash card ( 2 Gb required)
- Prepare the CPPM card for CoRes operation Card requires 2Gb Ram - 40Gb Hard Drive - Switch 5 set to 2
- Reset the CMOS on the card to Factory Defaults
- Using a VXWORKS installation compact Flash install BIOS upgrade to card
- Boot from CF
- Go to Tools Menu
- Select BIOS upgrade option and install lmdu74aa_0018
- Insert the Linux Installer CF and boot the system pressing F when prompted. Be patient.
- Hit return at the BOOT: prompt on the console to send output to the COM port. Be patient. The install programme will then guide you through adding the IP addresses, Hostname, Domain, time zone etc. CHECK THE TIME IS CORRECT ON THE SYSTEM.
- You will also be prompted for the passwords for the accounts “root” and “nortel” which need to be complex ( suggestion CS1000+r6) the install will proceed be patient.
- When the system completes installation and reboots login at the prompt to check both accounts.
- Browse in internet Explorer to the TLAN address of the system e.g. HTTP://10.5.10.12 , or the FQDN if you have a DNS. This should bring up a login page for the UCM, ignore any certificate errors at this point and continue. Login using the “nortel” account where you will be offered the options of Security Configuration or Local Administration. If you need to add other Hosts (for name resolution if you don’t have a DNS) or check/set the time select Local administration. If you use the Local Administration option you will need to log out and log back in again before continuing.
- Select Security Configuration, check the FQDN is correct and click next. Select which Security server type you require (One Primary, one Backup, multiple Members. Primary for a standalone system).You are then prompted for the “admin” account password (suggestion Nortel_123), this is the built-in Network Administrator account. Click Next
- You are now prompted to add the Certificate information for the system. Complete the form and submit. When completed click the Restart button and wait 10 minutes trying to login again.
- If you are not using a DNS entry for the system edit the “Hosts” file on your PC ( windows/system32/drivers/etc ) to contain an entry to link the FQDN to TLAN address e.g. 10.5.10.32 sys3.gktrain.com.
- Next click on the CERTIFICATES menu option under SECURITY. In the CERTIFICATE ENDPOINTS tab use the radio button to select the endpoint and then click on WEB SSL in the Endpoints Detail area. This will offer you a dialogue with several certificate options. Choose ASSIGN AN EXISTING CERTIFICATE and assign the certificate offered. This is the one created when you did the Security Configuration.
- Now click on the PRIVATE CERTIFICATE AUTHORITY tab and use the DOWNLOAD button to save the certificate to your PC. Leaving your web browser locate the downloaded certificate and double click it to install it on your PC. Make sure you save the certificate into Phil Pattington @mlex @ssociates Issue 4 the TRUSTED ROOT CERTIFICATION AUTHORITIES store. This will stop any further certificate errors being flagged up.
- Return to the UCM browser window and now select SOFTWARE DEPLOYMENT under CS 1000 SERVICES, this will show the Deployment Targets window. However we need to add a software load before we can deploy the server so select the SOFTWARE LOADS menu option.
- Select the Location for the “.NAI” file and use the BROWSE button to select the file from your Client PC or the Compact Flash on the Deployment server and use the ADD LOAD button to add it to the server. Be patient. When the load has been added return to the DEPLOYMENT TARGETS screen.
- Select the target system and click the DEPLOY button, select the items you wish to deploy on the target. (EM+SS+CS+NRSM+SM)
- If you are deploying a Call Server you will be prompted to select a Keycode on your PC to use. Once selected click the VALIDATE button to check it. Next select the Languages and select which database to use, again from your local PC.
- When the deployment completes the system is ready to login to.
- Access the Patch manager on the UCM or Base manager and apply any PEP’s, Service Updates or Service Pack to the systems.
- Once the Service packs are applied and activated you can configure the system as normal.
You may need extra PTY’s. To access the Call server on a CoRes system use csconsole on the Linux command line(
ad to return to Linux).
- When you have created the Media Gateways you need to add them into the Security Domain, otherwise they will not register correctly to the Call Server. To do this, use the REG UCM SYSTEM/DEVICE in LD 117.
- If REG UCM fails then you may need to login directly to each Media Gateway using
oam (Remember to use the “admin2” login as the MGC is still outside the UCM domain. From the command line issue the command “joinSecDomain” and follow the prompts to register the MGC to the UCM.
- Once you have run REG UCM SYSTEM and all the devices have been added to the Security Domain you will only be able to login using the admin account or another UCM based account. admin1 & admin2 will no longer work unless the call server is removed from the Security Domain.
- In Element Manager you will need to “Save & Transfer” the IP Node (you may also need to create it depending on the upgrade).This is now known as SYNCHRONIZE. When you open the Node it will have a STATUS in the far right column probably SYNCHRONIZED (Even though it isn’t at this point). Click on this link.
- This will open the SYNCRONIZE page. Select the Node (Check box) and click the START SYNC button.
- When the Node is SYNCRONIZED, as this is the first time the Sig Server has received the configuration you will need to RESTART APPLICATIONS. Select the Node and click the RESTART APPLICATIONS button.
- Remember to EDD the Call Server. Where the database has been converted (Small system to Large) you will need to do an EDD CLR on the first backup.
© Phil Pattington @mlex @ssociates