10-24-2011 10:06 PM
Had to replace the WAE-612 chassis because of water damage.
used original memory, Flash and Disks, booted ok.
did a "cms rderegister force" and deleted the device from the CM
got the following when did the
"cms enable" command
DEVWAD01(config)#cms enable
Registering WAAS Application Engine...
null certificate
register: Registration failed(512).
2011 Oct 25 16:01:39 DEVWAD01 perl: %WAAS-CMS-0-700001: Registration failed(512).
cms: unable to register node
2011 Oct 25 16:01:39 DEVWAD01 perl: %WAAS-CMS-0-700001: unable to register node
FAILED to enable management services
DEVWAD01(config)#
the secure store is not initialised.but syas can't do that until registered with CM
the WAAS is working as it has active connections
I have not had this problem before, is there something different wit rel 4.3.3 compared to earleir releases?
10-24-2011 11:43 PM
Hi,
What do you see in the output of the following show commands:
show disk details
show alarms
show crypto certificates
show disk tech-support detail
Do you see any alarm realted to disks? Just to make sure the disks are fine.
Regards
Kiran.
10-25-2011 02:35 PM
Kiran,
the Disks are ok no errors, and as I said the WAAS is working just not able to register with the CM
this is what I get from
Sh Alarms
Critical Alarms:
----------------
Alarm ID Module/Submodule Instance
--------------- -------------------- ---------------
1 svcdisabled nodemgr rpc_httpd
Major Alarms:
-------------
None
Minor Alarms:
-------------
None
I don't think that has any relevence just saying not connected to CM ( I think)
But when I show crypto certificate see this
Management Service Certificate
------------------------------
Invalid File
is this the problem?
is this related to the null certificate when trying to register?
10-25-2011 06:48 PM
Fixed the problem by doing the CLI command " restore factory-default preserve basic-config " command
obviously something somwhere within the WAE not liked by the CM when trying to register
04-24-2012 09:57 AM
hi there,
I faced this problem before and the workaround for it is to remove the WAAS database and create it again and issue the command cms enable.
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