Solved: Edge WAE permanently showing offline:

nickolaskoiser · ‎08-07-2008

I was doing demo for WAAS for a client in town and I went into some problem;

I am doing an off-path deployment, I was unable to secure the inline cards for this demo-I am using the gig interface of WAE 512.

I configured WCCP(service groups 61 and 62) on the routers at both ends.

I connected the WAEs on the unused Ethernet interface of the routers at the both ends configured 'ip wccp exclude in 'on the same interfaces to avoid routing loops.

The network connectivity is okay and i can ping from the central manager and from any part of the network.

I have also done 'cms enable' and specified the centralmanager IP.

The problem is the edge WAE permanently shows offline on the central manager,unlike the core wae which has been online all along.

What could be causing this branch WAE to be in this offline state.

Is this a bug?

Anyone who has experience with an off-path deployment before.

Please help the client is on my case.

Thank You

ropethic · ‎08-24-2008

Please try the following steps below

Question

What can be done if the following error is observed ?WAAS(config)#cms enable

Registering WAAS Application Engine...

Sending device registration request to Central Manager with address 10.1.1.1

Registration record for this device already exists or other nodes share the following information with this node: Mac 00:14:5e:95:57

:09 already used by device HQ-WAAS(CeConfig_188); Ip address HQ-WAAS#192.168.10.1 already used by device HQ-WAAS(CeConfig_188);

register: Registration failed.

cms: unable to register node

Answer

There are a couple of possibilities. If the WAE has been registered prior to this attempt with a different IP address, the CM recognizes the MAC address and flags this as an error condition. It is also possible that there is some stale information in the management database (on the CM and/or the WAE).

Please try the following steps to clear this state:

1. Delete the device from the CM GUI (If you still see it).

2. Do a "cms deregister force" on the WAE.

3. Set the CM ip address on the WAE again (if required).

4. "cms enable" on the WAE.

5. The device will need to be re-activated on the CM.

You should see the device on the CM in an active state momentarily.

View solution in original post

smalkeric · ‎08-13-2008

You can try to restore factory-defaults preserve basic settings on both the edge and core and reregistered the WCCP on the WAAS devices. The following URL may help you:

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4011/release/notes/ws4011rn.html

cfolkerts · ‎08-13-2008

Can you ping the edge WAE? and can the Edge WAE ping the central manager?

nickolaskoiser · ‎08-13-2008

Yeah both the CM and the edge WAE can ping each other well,at cms service is enabled-yet its stuck at 'offline' on the CM.

WAAS-EDGE#show cms info

Device registration information :

Device Id = 194

Device registered as = WAAS Application Engine

Current WAAS Central Manager = 172.16.63.200

Registered with WAAS Central Manager = 172.16.63.200

CMS services information :

Service cms_ce is running

WAAS-EDGE#

WAAS-EDGE#ping 172.16.63.200

PING 172.16.63.200 (172.16.63.200) from 192.168.1.10 : 56(84) bytes of data.

64 bytes from 172.16.63.200: icmp_seq=0 ttl=59 time=206.676 msec

64 bytes from 172.16.63.200: icmp_seq=1 ttl=59 time=149.744 msec

64 bytes from 172.16.63.200: icmp_seq=2 ttl=59 time=114.081 msec

64 bytes from 172.16.63.200: icmp_seq=3 ttl=59 time=142.352 msec

64 bytes from 172.16.63.200: icmp_seq=4 ttl=59 time=53.938 msec

--- 172.16.63.200 ping statistics ---

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

round-trip min/avg/max/mdev = 53.938/133.358/206.676/49.808 ms

WAAS-EDGE#

I really dont know what's causing this,

Help,

ropethic · ‎08-15-2008

try this command on the edge WAE-

"cms deregister force"

This will remove the WAE registration to the CM.

then do a cms enable.

Also make sure the CM is same or lower version of the edge WAE.

Let me know if this helps

nickolaskoiser · ‎08-15-2008

Hi,

Very many thanks for your response,

After putting in the 'cms deregister force',i ran into this problem,i have reloaded it a number of time,began the config all over again but this is what comes,though they can ping each other and management services are running on the CM:

NSSF-WAAS-EDGE(config)#cms enable

Registering WAAS Application Engine...

Sending device registration request to Central Manager with address 172.16.63.2

00

Failed to contact CDM 172.16.63.200(Unmarshaled: 9001). Please check connectivity with CDM de

vice and status of management service on CDM.

register: Registration failed.

cms: unable to register node

FAILED to enable management services

WAAS-EDGE(config)#

WAAS-EDGE(config)#â™¥

WAAS-EDGE#ping 172.16.63.200

PING 172.16.63.200 (172.16.63.200) from 192.168.1.10 : 56(84) bytes of data.

64 bytes from 172.16.63.200: icmp_seq=0 ttl=59 time=33.016 msec

64 bytes from 172.16.63.200: icmp_seq=1 ttl=59 time=33.027 msec

64 bytes from 172.16.63.200: icmp_seq=2 ttl=59 time=33.101 msec

64 bytes from 172.16.63.200: icmp_seq=3 ttl=59 time=33.036 msec

64 bytes from 172.16.63.200: icmp_seq=4 ttl=59 time=33.103 msec

--- 172.16.63.200 ping statistics ---

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

round-trip min/avg/max/mdev = 33.016/33.056/33.103/0.202 ms

WAAS-EDGE#

ropethic · ‎08-16-2008

What version of WAAS is running on edge and CM?

nickolaskoiser · ‎08-16-2008

This is the central manager:

WAAS-CM#show ver

Cisco Wide Area Application Services Software (WAAS)

Cisco Wide Area Application Services Software Release 4.0.13 (build b23 Sep 8 2

007)

Version: oe512-4.0.13.23

Compiled 18:41:02 Sep 8 2007 by cnbuild

System was restarted on Fri Aug 15 15:38:27 2008.

The system has been up for 22 hours, 53 minutes, 30 seconds.

WAAS-CM#

This is the output from the Edge WAE:

WAAS-EDGE#show ver

Cisco Wide Area Application Services Software (WAAS)

Cisco Wide Area Application Services Software Release 4.0.13 (build b23 Sep 8 2

007)

Version: oe512-4.0.13.23

Compiled 18:41:02 Sep 8 2007 by cnbuild

System was restarted on Sat Aug 16 11:50:24 2008.

The system has been up for 2 hours, 43 minutes, 49 seconds.

Both of them are running software release 4.0.13.23.

ropethic · ‎08-16-2008

is there a firewall between the remote and central device. If so, need to open tcp 445 for registration

ropethic · ‎08-16-2008

couple of things we can do:

First: debug cms

this will allow us to see the actual registration process

or

Second: tethereal -R "tcp.port==445"

if nothing appears just capture without -r

during the above do a cms enable and forward me the trace

nickolaskoiser · ‎08-16-2008

please find the output attached,

ropethic · ‎08-17-2008

The trace reveals no reply from CM on port 445. Check to make sure there is no firewall blocking tcp port 445 or an access list.

I only see traffic out, none coming in

nickolaskoiser · ‎08-22-2008

Hallo,

Very many thanks for your response,it helped a great deal,

However the curreent problem at hand is:

NSSF-WAAS-EDGE(config)#cms enable

Registering WAAS Application Engine...

Sending device registration request to Central Manager with address 172.16.63.2

00

Registration record for this device already exists or other nodes share the foll

owing information with this node: Certificate hash already used by device NSSF-W

AAS-EDGE(CeConfig_865); Mac 00:14:5e:84:36:39 already used by device NSSF-WAAS-E

DGE(CeConfig_865); Ip address NSSF-WAAS-EDGE.nssfkenya.co.ke#192.168.1.10 alread

y used by device NSSF-WAAS-EDGE(CeConfig_865);

register: Registration failed.

cms: unable to register node

FAILED to enable management services

NSSF-WAAS-EDGE(config)#

Thus it still comes in the CM as offline,

Tried reloading both of devices,putting in fresh configs but no results,

How do go about resolving this?

Thank You,

ropethic · ‎08-24-2008

I will have an answer tonight, need to research

Hang in there

ropethic · ‎08-24-2008

Please try the following steps below

Question

What can be done if the following error is observed ?WAAS(config)#cms enable

Registering WAAS Application Engine...

Sending device registration request to Central Manager with address 10.1.1.1

Registration record for this device already exists or other nodes share the following information with this node: Mac 00:14:5e:95:57

:09 already used by device HQ-WAAS(CeConfig_188); Ip address HQ-WAAS#192.168.10.1 already used by device HQ-WAAS(CeConfig_188);

register: Registration failed.

cms: unable to register node

Answer

There are a couple of possibilities. If the WAE has been registered prior to this attempt with a different IP address, the CM recognizes the MAC address and flags this as an error condition. It is also possible that there is some stale information in the management database (on the CM and/or the WAE).

Please try the following steps to clear this state:

1. Delete the device from the CM GUI (If you still see it).

2. Do a "cms deregister force" on the WAE.

3. Set the CM ip address on the WAE again (if required).

4. "cms enable" on the WAE.

5. The device will need to be re-activated on the CM.

You should see the device on the CM in an active state momentarily.