WAAS cms error

Unanswered Question
May 11th, 2009

I'm doing a proof-of-concept for a client and the issue is that the edge wae is not registering with the central manager.


The edge wae can ping the central manager's ip address and even complete a traceroute to the CM at three hops.


The error is as follows:

--------------------------------

EDGE(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 172.16.2.28

Failed to contact CDM 172.16.2.28(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.

----------------------------

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
hadbou Fri, 05/15/2009 - 04:09

De-register cms on the central manager, de-register the core WAE, and re-enabling cms on the central manager, core and edge WAEs. I hope This will resolve your issue.

Koiser_Nicholas Sat, 05/16/2009 - 01:37

Hello,

This did not help-we went through the whole procedure above.

We restored all equipment to factory/ default settings and began the configurations afresh.We then upgraded all the WAE to software release 4.0.19.

we are getting this error message:

WAAS-EDGE(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 172.16.2.28

Full thread dump Java HotSpot(TM) Client VM (1.5.0_10-b03 mixed mode):

"Low Memory Detector" daemon prio=1 tid=0x08134a50 nid=0x17dc runnable [0x000000

00..0x00000000]

"CompilerThread0" daemon prio=1 tid=0x081335b8 nid=0x17d4 waiting on condition [

0x00000000..0xbeffef74]

"Signal Dispatcher" daemon prio=1 tid=0x081325a8 nid=0x17d3 waiting on condition [0x00000000..0x00000000]

"Finalizer" daemon prio=1 tid=0x081285d0 nid=0x17d0 in Object.wait() [0xbf3ff000

..0xbf3ff88c]

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=0x08127850 nid=0x17cf in Object.wait() [0x

bf5ff000..0xbf5ff70c]

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=0x17ca 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=0x081215f0 nid=0x17ce runnable


"VM Periodic Task Thread" prio=1 tid=0x0814f780 nid=0x17dd waiting on condition


Failed to contact CDM 172.16.2.28(TIMEOUT). Please check connectivity with CDM d

evice and status of management service on CDM.

register: Registration failed.

cms: unable to register node


FAILED to enable management services

WAAS-EDGE#ping 172.16.2.28

PING 172.16.2.28 (172.16.2.28) from 192.168.105.17 : 56(84) bytes of data.

64 bytes from 172.16.2.28: icmp_seq=0 ttl=61 time=10.513 msec

64 bytes from 172.16.2.28: icmp_seq=1 ttl=61 time=11.862 msec

64 bytes from 172.16.2.28: icmp_seq=2 ttl=61 time=24.472 msec

64 bytes from 172.16.2.28: icmp_seq=3 ttl=61 time=10.850 msec

64 bytes from 172.16.2.28: icmp_seq=4 ttl=61 time=78.139 msec


--- 172.16.2.28 ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max/mdev = 10.513/27.167/78.139/26.012 ms


What could be the problem?

Martin Gorny Thu, 03/25/2010 - 06:44

Hi,

in my case a normal reboot of the WAE solved the problem.


Cheers,

Martin.

praveen14031978 Tue, 08/25/2015 - 04:38

Hi Team,

Kindly advise how to deregister from central manager for a single remote WAAS. I am also facing same problem. I can see option to deregister from remote WAAS.

 

Rgds

Praveen

Actions

This Discussion