Aaedward at 02:04, 7 December 2012

2012-12-07T02:04:52Z

← Older revision		Revision as of 02:04, 7 December 2012
Line 36:		Line 36:
	== Cisco WAAS Auto Deploy Troubleshooting ==		== Cisco WAAS Auto Deploy Troubleshooting ==

-	Cisco WAAS Auto Deploy ~~simplifies~~ network deployment of WAN optimization in branches, and greatly reduces dependency physical configuration.	+	Cisco WAAS Auto Deploy and Auto Registration Enhancements simplify network deployment of WAN optimization in branches, and greatly reduces dependency physical configuration.

-	'''NOTE:''' The ~~AppNav~~ feature was introduced in WAAS version 5.1.1. This section is not applicable to earlier WAAS versions.	+	'''NOTE:''' The Auto Deploy feature was introduced in WAAS version 5.1.1. This section is not applicable to earlier WAAS versions.

	=== Verifying DNS Configuration ===		=== Verifying DNS Configuration ===

Aaedward: initial content for WAAS Auto Deploy troubleshooting in WAAS 5.1.1

2012-12-07T02:03:53Z

initial content for WAAS Auto Deploy troubleshooting in WAAS 5.1.1

New page

{{Template:Required Metadata}} This article describes how to troubleshoot the Cisco WAAS Auto Deploy feature.

{| align="right" border="1" cellspacing="0"
|-
| align="center" | '''Guide Contents'''
|-
| [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later|Main Article]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Understanding the WAAS Architecture and Traffic Flow|Understanding the WAAS Architecture and Traffic Flow]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Preliminary WAAS Troubleshooting|Preliminary WAAS Troubleshooting]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting Optimization|Troubleshooting Optimization]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting Application Acceleration|Troubleshooting Application Acceleration]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting the CIFS AO|Troubleshooting the CIFS AO]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting the HTTP AO|Troubleshooting the HTTP AO]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting the EPM AO|Troubleshooting the EPM AO]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting the MAPI AO|Troubleshooting the MAPI AO]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting the NFS AO|Troubleshooting the NFS AO]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting the SSL AO|Troubleshooting the SSL AO]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting the Video AO|Troubleshooting the Video AO]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting the Generic AO|Troubleshooting the Generic AO]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting Overload Conditions|Troubleshooting Overload Conditions]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting WCCP|Troubleshooting WCCP]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting AppNav|Troubleshooting AppNav]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting Disk and Hardware Problems|Troubleshooting Disk and Hardware Problems]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting Serial Inline Clusters|Troubleshooting Serial Inline Clusters]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting vWAAS|Troubleshooting vWAAS]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting WAAS Express|Troubleshooting WAAS Express]] [[Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting NAM Integration|Troubleshooting NAM Integration]] 
|}

__TOC__

 

 

 

 

 

 

 

 

 

 

 

 

== Cisco WAAS Auto Deploy Troubleshooting ==

Cisco WAAS Auto Deploy simplifies network deployment of WAN optimization in branches, and greatly reduces dependency physical configuration.

'''NOTE:''' The AppNav feature was introduced in WAAS version 5.1.1. This section is not applicable to earlier WAAS versions.

=== Verifying DNS Configuration ===

Verify the following DNS queries can be made from a PC in the WAAS Network range:

*DNS "SRV" query for _waascms._tcp.customerdomain.com
**If fails, "SRV" query for _waascms._tcp.customerdomain.com

The above SRV query should return the "A" (Host) record of the WAAS Central Manager. Verify that this record can also be resolved.
<pre>aaedward-mbp:~ aaedward$ nslookup
> set type=SRV
> _waascms._tcp.adbu.local
Server: 2.8.3.2
Address: 2.8.3.2#53

_waascms._tcp.adbu.local service = 0 100 8443 pod3-cm.adbu.local.
> set type=A
> pod3-cm.adbu.local
Server: 2.8.3.2
Address: 2.8.3.2#53

Name: pod3-cm.adbu.local
Address: 2.8.30.100
></pre>
=== Debugging Auto Deploy ===

If Cisco WAAS Auto Deploy succeeds, the following messages should be seen in the syslog.txt file:
<pre>2012 Nov 15 08:26:01 NO-HOSTNAME dhclient: %WAAS-DHCP-5-191000: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
2012 Nov 15 08:26:01 NO-HOSTNAME dhclient: %WAAS-DHCP-5-191000: DHCPOFFER from 7.1.247.49
2012 Nov 15 08:26:06 NO-HOSTNAME dhclient: %WAAS-DHCP-5-191000: DHCPREQUEST on eth0 to 255.255.255.255 port 67
2012 Nov 15 08:26:06 NO-HOSTNAME dhclient: %WAAS-DHCP-5-191000: DHCPACK from 7.1.247.49
2012 Nov 15 08:26:06 NO-HOSTNAME %WAAS-DHCP-5-191000: Script called with reason: BOUND
2012 Nov 15 08:26:06 NO-HOSTNAME %WAAS-DHCP-5-191000: Configuring hostname: FIT1-OFF2-574
2012 Nov 15 08:26:06 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring new IP andress: 7.1.247.50 255.255.255.240
2012 Nov 15 08:26:06 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring default gateway: 7.1.247.49
2012 Nov 15 08:26:06 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring domain name myfit.local
2012 Nov 15 08:26:06 FIT1-OFF2-574 cfg_bin_ip_domainname: %WAAS-CLI-5-170053: Recreated etc_hosts (1, 0)
2012 Nov 15 08:26:06 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring nameserver:7.1.240.10
2012 Nov 15 08:26:07 FIT1-OFF2-574 kernel: %WAAS-SYS-4-900000: process `dig' is using obsolete setsockopt SO_BSDCOMPAT
2012 Nov 15 08:26:11 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Enabling CMS with CDM: fit1-cm1.myfit.local.
2012 Nov 15 08:26:11 FIT1-OFF2-574 cfg_bin_autoreg_runcms: %WAAS-AUTOREG-5-111020: Primary interface configuration successful
2012 Nov 15 08:26:11 FIT1-OFF2-574 cfg_bin_autoreg_runcms: %WAAS-AUTOREG-5-111024: Central Manager hostname configuration successful</pre>
If Cisco WAAS Auto Deploy fails, debugging can be done via the console connection.

To enable debugging, issue the following commands:
<pre>NO-HOSTNAME#debug dhcp
NO-HOSTNAME#config t
NO-HOSTNAME(config)#logging console enable
NO-HOSTNAME(config)#logging console priority debug</pre>
Once debugging is enabled, toggle Auto Deploy off, then back on.
<pre>NO-HOSTNAME#config t
NO-HOSTNAME(config)#no auto-register enable
NO-HOSTNAME(config)#auto-register enable</pre>
After toggling Auto Deploy, debug messages should be printed to syslog.txt:
<pre>2012 Oct 8 07:04:25 FIT1-OFF2-574 config: %WAAS-PARSER-6-350232: CLI_LOG log_cli_command: auto-register enable
FIT1-OFF2-574(config)#2012 Oct 8 07:04:25 FIT1-OFF2-574 dhclient: %WAAS-DHCP-3-191000: teql0: unknown hardware address type 65535
2012 Oct 8 07:04:25 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Script called with reason: PREINIT
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-3-191000: teql0: unknown hardware address type 65535
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 000: 01 01 06 00 ae 97 26 53 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 010: 00 00 00 00 00 00 00 00 00 00 00 00 00 21 5a 0c
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 020: 7d 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 0a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 0b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 0c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 0d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 0e0: 00 00 00 00 00 00 00 00 00 00 00 00 63 82 53 63
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 0f0: 35 01 03 36 04 07 01 f7 31 32 04 07 01 f7 32 37
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 100: 06 01 03 0f 06 0c 2b 3c 08 43 49 53 43 4f 43 44
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 110: 4e 3d 08 43 49 53 43 4f 43 44 4e ff 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-7-191000: 120: 00 00 00 00 00 00 00 00 00 00 00 00
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-5-191000: DHCPREQUEST on eth0 to 255.255.255.255 port 67
2012 Oct 8 07:04:26 FIT1-OFF2-574 dhclient: %WAAS-DHCP-5-191000: DHCPACK from 7.1.247.49
2012 Oct 8 07:04:26 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Script called with reason: REBOOT
2012 Oct 8 07:04:26 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring hostname: FIT1-OFF2-574
2012 Oct 8 07:04:26 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring new IP address: 7.1.247.50 255.255.255.240
2012 Oct 8 07:04:26 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring default gateway: 7.1.247.49
2012 Oct 8 07:04:26 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring domain name: myfit.local
2012 Oct 8 07:04:26 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Configuring nameserver: 7.1.240.10
2012 Oct 8 07:04:27 FIT1-OFF2-574 Nodemgr: %WAAS-NODEMGR-5-330084: [Nodemgr_Admin] requests restart service nscd
2012 Oct 8 07:04:27 FIT1-OFF2-574 Nodemgr: %WAAS-NODEMGR-5-330032: Stopping service: 'nscd'.
2012 Oct 8 07:04:27 FIT1-OFF2-574 Nodemgr: %WAAS-NODEMGR-5-330036: Stop service 'nscd' using: '/ruby/bin/nscd_stop' with pid: 9595
2012 Oct 8 07:04:27 FIT1-OFF2-574 %WAAS-DHCP-5-191000: Enabling CMS with CDM: cm1.myfit.local.
2012 Oct 8 07:04:27 FIT1-OFF2-574 cfg_bin_autoreg_runcms: %WAAS-AUTOREG-5-111020: Primary interface configuration successful
2012 Oct 8 07:04:27 FIT1-OFF2-574 cfg_bin_autoreg_runcms: %WAAS-AUTOREG-5-111022: Device is already registered with Central Manager, skipping auto-registration.</pre>

Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later -- Troubleshooting Auto Deploy - Revision history

Aaedward at 02:04, 7 December 2012

Aaedward: initial content for WAAS Auto Deploy troubleshooting in WAAS 5.1.1