04-28-2009 11:45 AM
Hi guys,
When I try to register one of my two NM-WAE-502-K9 to a WAE612 Central manager,
I get the error that registration failed. This WAE can trace and ping the WAE612 OK.
It has the same OS version as another one that registers with the WAE612.
The WAE 502 did register once but failed to register after I fixed the speed and duplex
on gig 2/0 because the WAE612 Central Manager complained about it.
Ideas please?
Bash
=================================================
ABMWAAAP01(config)#cms enable
Generating new RPC certificate/key pair
Restarting RPC services
Registering WAAS Application Engine...
Sending device registration request to Central Manager with address 192.168.0.2
45
Full thread dump Java HotSpot(TM) Client VM (1.5.0_10-b03 mixed mode):
"Low Memory Detector" daemon prio=1 tid=0x08134a48 nid=0x1eef runnable [0x000000
00..0x00000000]
"CompilerThread0" daemon prio=1 tid=0x08133510 nid=0x1eed waiting on condition [
0x00000000..0xbefff174]
"Signal Dispatcher" daemon prio=1 tid=0x08131458 nid=0x1eec waiting on condition
[0x00000000..0x00000000]
"Finalizer" daemon prio=1 tid=0x081285c8 nid=0x1eeb in Object.wait() [0xbf3ff000
..0xbf3ff68c]
at java.lang.Object.wait(Native Method)
- waiting on <0x2b23bad8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(Unknown Source)
- locked <0x2b23bad8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(Unknown Source)
at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)
"Reference Handler" daemon prio=1 tid=0x08127848 nid=0x1eea in Object.wait() [0x
bf5ff000..0xbf5ff50c]
at java.lang.Object.wait(Native Method)
- waiting on <0x2b23bb58> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Unknown Source)
at java.lang.ref.Reference$ReferenceHandler.run(Unknown Source)
- locked <0x2b23bb58> (a java.lang.ref.Reference$Lock)
"main" prio=1 tid=0x0805eb08 nid=0x1ee6 waiting on condition [0xbfffc000..0xbfff
cf58]
at java.lang.Thread.sleep(Native Method)
at unicorn.Utils.sleepMs(Utils.java:54)
at unicorn.RpcTcpTransport.waitForInput(RpcTcpTransport.java:140)
at unicorn.RpcTcpTransport.invokeSynchronous(RpcTcpTransport.java:227)
at dispatcher.Dispatcher.invokeSynchronous(Dispatcher.java:33)
at unicorn.RpcDispatcherTransport.invokeSynchronous(RpcDispatcherTranspo
rt.java:47)
at distributionAdapterRpc.DistributionAdapterRpc.register(DistributionAd
apterRpc.java:46)
at com.cisco.unicorn.messaging.DistributionAdapterRpcClient.register(Dis
tributionAdapterRpcClient.java:208)
at com.cisco.unicorn.messaging.DistributionAdapter.register(Distribution
Adapter.java:557)
at com.cisco.unicorn.controller.register.rpcRegister(register.java:316)
at com.cisco.unicorn.controller.register.registerCe(register.java:129)
at com.cisco.unicorn.controller.register.main(register.java:469)
"VM Thread" prio=1 tid=0x081215e8 nid=0x1ee9 runnable
"VM Periodic Task Thread" prio=1 tid=0x0814f6d8 nid=0x1ef0 waiting on condition
Failed to contact CDM 192.168.0.245(TIMEOUT). Please check connectivity with CDM
device and status of management service on CDM.
register: Registration failed.
cms: unable to register node
FAILED to enable management services
ABMWAAAP01(config)
=========================================================
ABMWAAAP01#sh vers
Cisco Wide Area Application Services Software (WAAS)
Copyright (c) 1999-2008 by Cisco Systems, Inc.
Cisco Wide Area Application Services Software Release 4.0.19 (build b14 Jun 13 2008)
Version: nme-wae-502-DEVELOPMENT[adbu-relbld-1:/users1/waas_4.0.19-b14]
The system has been up for 2 hours, 56 minutes, 36 seconds.
=========================================================
ABMWAAAP01#sh device-mode current
Current device mode: application-accelerator
04-28-2009 01:17 PM
Try "cms deregister force" to force a deregister and then try cms enable
04-30-2009 02:24 AM
Tried it already and did not work
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