nme-wea-502 configure

Unanswered Question
Jun 28th, 2010

HI Zack,

Under is the configuration about NME-WEA-502

APP#cms deregister  force
Management service is not enabled/registered.

Based on the input, the following configuratio
       central-manager address 172.16.1.250
       ip name-server 172.16.1.253
       ip domain-name  c.c
       primary-interface GigabitEthernet 1/0
       hostname APP
       clock timezone UTC 0 0
       cms enable
       wccp version 2
       wccp router-list 8 13.13.13.11
       wccp tcp-promiscuous router-list 8

APP#ping 172.16.1.250

PING 172.16.1.250 (172.16.1.250) 56(84) bytes of data.

64 bytes from 172.16.1.250: icmp_seq=1 ttl=61 time=0.943 ms

64 bytes from 172.16.1.250: icmp_seq=2 ttl=61 time=0.620 ms

64 bytes from 172.16.1.250: icmp_seq=3 ttl=61 time=0.669 ms

64 bytes from 172.16.1.250: icmp_seq=4 ttl=61 time=0.759 ms

64 bytes from 172.16.1.250: icmp_seq=5 ttl=61 time=0.811 ms

--- 172.16.1.250 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 0.620/0.760/0.943/0.115 ms
APP#conf t
APP(config)#cms enable
Registering WAAS Application Engine...
Sending  device registration request to Central Manager with address 172.16.1.250
Failed to contact CDM 172.16.1.250(TIMEOUT). Please check connectivity with CDM
device and status of management service on CDM.
register: Registration failed(512).
cms: unable to register node i

FAILED to enable management services

I had  registed to the CM before ,when NME-WEA-502 offline ,and I try to  regist to the

CM again, show this error,could you mind to tell me how to fix it ?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Zach Seils Mon, 06/28/2010 - 06:04

Let's check a couple of things:

  1. If you look at the list of devices in the CM, do you see the NME-WAE there?  If so, delete the record of that device on the CM.
  2. What is the output of sh cms info on the CM?

Thanks,

Zach

Actions

This Discussion