System Platform 6.0.3.0.3 Address changes

[platinum8]

Staged System Platform (HP DL360 G7 server) prior to receiving IP addressing from the end user.
When we got the final address list from the customer, used the CDom web interface to change addresses. After the change, cannot access the CM SMI web interface from the platform Services port. All other virtual servers are accesable/pingable from the Services port.
IP Forwarding is enabled at the Domain 0 level.
Our only option to fix this is to reload both System Platform and the CM Solution Template.

Anyone seen this symptom?

 

[IPOthermia]

I had to install a Single Server MAS/MSS. Templates living on an System Platform essentially. When we got the system on site, and got the final addressing we found it better to start over. There may of course be other options.

 

[Mitch672]

Actually, it can be done. These are the steps:

1. log into "System Platform", using the existing IP address
2. click on "Server Management", then "Network Configuration" (wait a while now)
3. you now have access to the fields that need to change:

General Network Settings: Default Gateway

under "Domain Network Interface":
Domain-0 (avpublic eth1.1)
Console Domain (avpublic eth0)

under "Template Network Configuration", "Global Template Network Configuration":

CM IPv4 Address
Utility Server IPv4 Address

type in your new IP's to these fields, you only get 1 shot at getting this correct. Then click on "save"

now you need to change your network scheme to the new one, and give it a few minutes.

You will also need to go into the G430 and change the PMI, the best way to do that is through the front "Service" LAN port @ 192.11.13.6, once you change the IP scheme, remember to change the "MGC list" as well (clear mgc list, set mgc list)

now once you get back into CM, you also need to update the node-names, especialy the one being used for the CMM Signalling group (usually sig 99), once thats done, CMM should ocme back online as well.

takes about an hour, and is much faster than reloading.
of course make a full backup and backup your "46xxettings.txt" file from the utility server, in case it does not go well for you, and you have to reload from scratch.

Also, don't forget to go in to the "46xxsettings.txt" file located on your utility server and update any IP address's in the file as well. You will also likely have to update whatever you are using for the DHCP Server as well (possibly could be your utility server or something external as well)

Mitch


Mitch

AVAYA Certified Expert