I would like to re-address management port of WAE. What is the correct method for doing it? Because the WAE is registered in the central manager WAE. When I re-address management port of WAE, the central manager has problem with the new address. Thank you.
Solved! Go to Solution.
I would probably restore it to factory defaults and then go through the normal configuration process:
# restore factory-default
This clears the unit and then it will reboot.
When it comes back up, you configure the interfaces:
(config)# interface GigabitEthernet 1/0
(config-if)# ip address X.X.X.X X.X.X.X
Duplex is automatically at 1000 full. If something else is required, add the following (as appropriate):
(config-if)# bandwidth 100
(config)# ip default-gateway x.x.x.x
(config)# ip name-server x.x.x.x
(config)# ip domain-name myDomain.com
(config)# host myHost
(config)# clock timezone US/Eastern -5 0
(config)# ntp server x.x.x.x
(config)# show clock (verify Timezone settings)
***You still need this next line even if you are using inline cards
(config)# primary-interface gigabitEthernet 1/0
(config)# central-manager address x.x.x.x
(config)# cms enable
If cms registration isn't successful, try burning the config to flash and doing a reload. Then reattempt and it should work. The WAE must be connected to the network and able to communicate with the Central Manager for the âcmsâ command to work. It fails because it can't generate the certificate. Timeout is 15 seconds and states it was âunable to register.â
Once the cms enable is successfully completed, a reload is a good idea.
Hope this helps.
I just changed the IP address of management port, but CM told me, that this device exists with old address:-( I use WAAS 4.0.17.
I just went into the lab, used the CLI to change the IP address of the primary interface on an application accelerator and after the next CMS update, the CM showed the new IP address of the box in the GUI and it was OK. What exactly are you trying to do?
I tried it a different way as well, I did a deregister force, deleted it from the CM and readded it. You have to reconfigure the box with the device groups, but it works as well. That would be the brute force method if for some reason CMS isn't updating the CM.