WAAS - NAT between CM and WAE

Unanswered Question
Jun 17th, 2008
User Badges:

Seem to have a problem with nat/firewall between CM and WAE. Configuration commands issues via CM GUI do not make it to the WAE (checked via CLI).


I configured the NATed IP address ofor the WAE in device activation screen NAT section. I am running WAAS 4.0.19.b14.


Any ideas please?

Thanks

DG

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Zach Seils Wed, 06/18/2008 - 07:49
User Badges:
  • Cisco Employee,

DG,


Is the WAE status Online in the CM?


Zach



d.gabo Wed, 06/18/2008 - 15:15
User Badges:

Zach,


The WAE s had registered successfully wit the CM and its status is on line. It looks lie CM does not recognise the NAT entry for the to communicate with it using its real address, which i assume is derived from the registration.


Configuration snapshots are in the file attached. The device behind FW/NAT is 172.21.227.205





Attachment: 
Zach Seils Thu, 06/19/2008 - 07:55
User Badges:
  • Cisco Employee,

Looks like the CM tries to push the change using the WAEs real IP address, which fails. However, in my lab, the configuration change is picked up by the WAE on the 5 minute refresh cycle (when the WAE contacts the CM).


Are you not seeing the configuration change update after 5-10 minutes?


Zach



d.gabo Thu, 06/19/2008 - 14:28
User Badges:

Zach,


I may have been too impatient, expecting an instant push of config changes from CM to WAE. The CM already has the NATed address of WAE and I would have thought should not rely on refresh cycle to pick it up. I did not realise that WAE pulls configs from CM.


I'll give it a try.

Thanks


Zach Seils Fri, 06/20/2008 - 21:13
User Badges:
  • Cisco Employee,

DG,


Can you uncheck the 'Use WAE's primary IP Address' box and retest?


Thanks,

Zach



Actions

This Discussion