WAAS Problem,

nickolaskoiser · ‎08-23-2008

Am doing a WAAS demo for a client,

I have a central manager and a core WAE,the core WAE is working okay,it has registered with the central manager and its intercepting traffic.

I have a problem with the branch edge WAE which was initially working ok,then the branch went offline-after the link to the branch was restored it came up as offline in the central manager.

Both the central manager and the edge WAE can ping each okay,

I did cms deregister force on the edge wae,

I then specified the central manager address and while doing cms enable,this is what came:

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)#

I have reloaded both the CM and the edge but it still shows as offline on the CM.

How do i resolve this?

Please help.

Giuseppe Larosa · ‎08-23-2008

Hello Nickolas,

it looks like that some other device is using the same Certificate to authenticate with the central manager

device NSSF-W

AAS-EDGE(CeConfig_865); Mac 00:14:5e:84:36:39

or is this actually your WAAS device ?

check if the MAC address is that of yours WAAS device or not.

Hope to help

Giuseppe

nickolaskoiser · ‎08-23-2008

Hallo,

I have just confirmed that the mac-address indeed belongs to the edge device.

Giuseppe Larosa · ‎08-23-2008

Hello Nickolas,

I think you need to find a way to delete this disturbing entry on the manager itself.

The problem you have is an authentication problem the manager thinks you are trying to pretend to be the edge device but actually it is !

Hope to help

Giuseppe

ropethic · ‎08-25-2008

1. delete the node from central manager

2. cms deregister force on edge wae

3. remove IP address from wae primary interface

4. reload

5. reconfigure IP on wae primary