Troubleshooting Tunnel Problems - Avaya 8800 Troubleshooting Manual

Troubleshooting the Unified Access solution
3. Dump tunnel information to get general information and the current status of all the
4. Check the WLAN Packet Processing Statistics for this switch:
5. Check how memory is allocated and check memory for consistency:

Troubleshooting tunnel problems

Use the following steps to troubleshoot why a tunnel is bouncing or lost connection.
Procedure
1. If a tunnel fails and never comes back up, check the Layer 3 connectivity.
2. If a tunnel is bouncing, check to make sure keepalive packets are being received:
3. Determine the source port for the incoming keepalive packet and then mirror that
4. Check to make sure keepalive packets are being forwarded:
5. Determine the egress port of the tunnel and then mirror that port to verify that the
434 Troubleshooting
(ACLI) dump wireless ma vlan-advertised <mac>
dump wireless ma vlan-map [<name>]
dump wireless ma vlan-server [<name>]
access tunnels (AT) and mobility tunnels (MT) associated with this switch or for a
specific endpoint:
dump wireless tunnel [<ipaddr>] [summary]
dump wireless stats
dump wireless memory malloc-summary {interface | mvlan |
tunnel | wdp | vmm | osapi | mvmp | all}
dump wireless memory mem-check
(CLI) show wireless tunnel-statistics keepalive
(ACLI) show wireless switch tunnel-statistics keepalive
port to verify that the keepalive is received every second. Identify the keepalive
packet in the trace by looking for a UDP packet with an IP header length of 36:
(CLI) config rsp-trace ingress-pkt-trace port <value> state
enable interval <value>
(ACLI) rsp-trace ingress-pkt-trace <slot/port> enable
<interval 1–300>
(CLI) show wireless tunnel-statistics keepalive
(ACLI) show wireless switch tunnel-statistics keepalive
keepalive is sent out. Identify the keepalive packet in the trace by looking for a UDP
packet with an IP header length of 36:
Comments? infodev@avaya.com
July 2013