11-18-2008 06:53 AM
Dear all
I have received lately, 3 waas devices
1 for central manager and 2 Application accelerator,
So i was connecting them, and found a strange behaviour in the Central manager,
when i finished the CLI configuration, i tried to login to the GUI interface of the central manager, and I couldn't get to the usual Central manager interface, i got a weird one
the existting Version was 4.0.17
I upgraded the 3 devices into WAAS-4.1.1a.10 and still have the same error
I need urgently to fix this issue ASAP
I attached the Configuration of the central manager, and the gui interface that i am getting
Solved! Go to Solution.
11-18-2008 07:23 AM
Hi,
Have you reloaded the CM after you assigned it the role of Central Manager? It is still in Application Accelerator Mode with all the policies at the bottom. Try reloading it and then see if CMS comes up. In "sh cms info" it's role should say Central Manager and CMS processes should be started.
Thanks,
Dan
11-18-2008 07:06 AM
And note that i am unable to register any appliance with the central manager, although there is PING connectivity between them.
Core-WAE(config)#cms enable
Registering WAAS Application Engine...
Sending device registration request to Central Manager with address 10.4.1.222
Failed to contact CDM 10.4.1.222(Unmarshaled: 9001). Please check connectivity with CDM device and status of management service on CDM.
register: Registration failed(512).
cms: unable to register node
FAILED to enable management services
Core-WAE(config)#
11-18-2008 07:23 AM
Hi,
Have you reloaded the CM after you assigned it the role of Central Manager? It is still in Application Accelerator Mode with all the policies at the bottom. Try reloading it and then see if CMS comes up. In "sh cms info" it's role should say Central Manager and CMS processes should be started.
Thanks,
Dan
11-18-2008 10:46 PM
here are the results
CentralManager#show cms info
Device registration information :
Device Id = 165
Device registered as = WAAS Central Manager
Current WAAS Central Manager role = Primary
CMS services information :
Service cms_httpd is running
Service cms_cdm is running
CentralManager#show license
License Name Status Activation Date Activated By
-------------- ----------- --------------- --------------
Enterprise active 11/18/2008 admin
CentralManager#
the GUI interface worked properly after the reload.
although, after I upgraded the version, I did restore factory-default and enter the configurations from start
anyway the problem is solved, thank you all.
HOPE THE DEMO WORKS FINE :)
11-18-2008 07:36 AM
Try CMS deregister force on CM and WAEs.
This will clear all CMS info / database.
Then cms enable
Chances are it is also configured as an acclerator
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide