How to change IP addresses in IOG20 and APG40 Network: GSM Node: AXE BSC Node: AXE MSC IOG20

APG40 Fix: Solution for IOG20 Follow the OPI "Internet Port, Change" 54/154 31-ANZ 216 20 Uen Solution for APG40 Change the Passive node IP address. 1. Log into the passive APG40 node using pcANYWHERE. The passive node can be confirmed by typing the command prcstate at the command prompt. C:\> prcstate passive 2. Open up the Network properties. Start -> Settings -> Control Panel -> Network 3. Click on the Protocols tab. 4. Click on Properties. 5. From the Adapter: pull down menu select the public LAN card indicated as Slot 9. 6. Change the IP Address, Subnet Mask and Default Gateway to the new valu es. 7. Click on OK to close the properties dialog box. 8. Click on OK to close the Network settings. 9. You will be asked to reboot the machine for the new setting to take ef fect. Click Yes to confirm. 10. If the new IP address is physically on a new subnet then change the e thernet cable on the passive node. 11. After the node finishes rebooting (approx 5 minutes) test the new IP address. This can be done by ping ing the default gateway from the APG40 or trying to ping the passive node s new IP address from an external machine. Tests should be made from the APG40 passive node to make sure all external hosts like the bil ling centre or an O&M can be contacted. Ping, telnet or ftp can be used. 12. Do not continue until the new IP address is working properly. 13. Open the Cluster Administrator. Start -> Programs -> Administrative Tools -> Cluster Administrator 14. In the left frame, expand the Groups folder and click on the RGAPM_0 group. 15. In the right frame right click on resource ACS_PRC_ClusterControl_0 a nd select Take Offline . 16. In the left frame click on the RGAPM_1 group. In the right frame righ t click on resource ACS_PRC_ClusterControl_1 and select Take Offline . Change the Cluster IP address. 1. Log into the active APG40 node using pcANYWHERE. The active node can b e confirmed by typing the command prcstate at the command prompt. C:\> prcstate active 2. Open the Cluster Administrator. Start -> Programs -> Administrative Tools -> Cluster Administrator 3. In the left frame, expand the Groups folder and click on the Cluster G

roup. 4. In the right frame right click on the Cluster IP Address resource and select Properties. 5. Click on the parameters tab. 6. Change the IP address to the new Cluster IP address and press the Tab key. Note: the Subnet mask: and Network to use: should change automatically to the co rrect values if the passive node has rebooted and joined the cluster. 7. Click on OK to confirm that the new settings will become active the ne xt time the resource is brought online. Change the Active Node IP address. 1. On the active node, open up the Network properties. Start -> Settings -> Control Panel -> Network 2. Click on the Protocols tab. 3. Click on Properties. 4. From the Adapter: pull down menu select the public lan card indicated as Slot 9. 5. Change the IP Address, Subnet Mask and Default Gateway to the new valu es. 6. Click on OK to close the properties dialog box. 7. Click on OK to close the Network settings. NOTE: After the Active node is rebooted a failover of the cluster will occur. 8. You will be asked to reboot the machine for the new setting to take ef fect. Click Yes to confirm. 9. If the new IP address is physically on a new subnet then change the et hernet cable on the active node. //////////////////////////////////////////////////////// How to change IP address in Windows Server 2003 Network: GSM APG40 Software: Window Server 2003 Public IP address of APG40 needs to be changed Solution: Condition: 1. A new IP address is available. Procedure: Please follow the OPI in R12 ALEX: AP, IP Address Change, Initiate It is strongly recommend to perform this OPI on site or with RDC connection. Sin ce i experienced problem to telnet to one of the node at the end of the OPI I had tested the OPI in the test plnat, most of the steps were working fine exce pt the following ones: 1. Step 15& 23: The command line of netsh will not work in one line until you go into the sub-level of the netsh command 1.1 go to netsh manu:

Command: netsh 1.2 then next level: interface: Command: interface 1.3 go to IP level: Command: ip 1.4 perform the change under IP level: Command: set address Public static <new ip address> <new mask> <new gw> gwmetric 1.5 Confirm if the address has been changed succesfully, and also check the not e below in this primus before continue next steps: Command: show address !note: how to exit or go back to uper level in netsh: use ".." to go back to uper level use "exit" to exit from netsh 2. Step 41, the previous cluster group may fail after you start up another clust er group. You may need to login to the node which the clsuter group fails to man ually start up the cluster service. At this point, you may have telnet problem, so you need to login to the node loc ally or with RDC to start up the cluster service:

Command: net start clussvc It was found that network connection name was changed by the system after chan ging the IP address of "public". So it is important to check the network connect ion setting after changed the IP address. incorrect network connetion name for " public" will lead to ACS_NSF_Server_X process failed to start and lead to Ap cy clic reboot. A follow up CSR will be opend for emgergency CSR 626732 which addre ssed this issue during the IP change in windows 2003 Below is how to change the network connection name if it is not correct. 1. Start --> Control panel -->network connections --> Right click on the network connection and select "rename".

2. enter the correct name for the network connections, below are the names to fi ll in if anyone of them were not correct, the name should be exactly the same as below (Orders maybe different) Heartbeat 1 Heartbeat 2 IPN100-1 IPN100-2 Local Maintenance Public 3. Then restart the failing NSF process again. cluster res ACS_NSF_Server_X /on /wait