Diagnostics on ESR needed to define if the network operation is correct.
Check for the core availability from access point management networks
Command:
ping <server ip address> source ip <bridge ip address>
Example:
ESR100# ping 192.168.1.1 source ip 192.168.2.2 PING 192.168.1.1 (192.168.1.1) from 192.168.200.4 : 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.128 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.116 ms ^C--- 192.168.1.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.116/0.122/0.128/0.006 ms ESR1000#
192.168.1.1 – EMS server addresswhere:
192.168.2.2 – the address of the ESR bridge that is the access point management network’s gateway
Check for tunnels
Management tunnel check command:
show tunnel status | include "<tunnel terminating ip address>"
Example:
ESR1000# show tunnel status | include "10.203.5.11" softgre 10 Up Up 1462 10.203.5.11 10.203.37.235 61 days, 2 hours, 16 softgre 23 Up Up 1462 10.203.5.11 10.203.36.59 6 days, 2 hours, 46 softgre 27 Up Up 1462 10.203.5.11 10.203.40.114 34 days, 2 hours, 38 softgre 28 Up Up 1462 10.203.5.11 10.203.37.124 34 days, 17 hours, 56 softgre 29 Up Up 1462 10.203.5.11 10.203.40.80 34 days, 2 hours, 38
where 10.203.5.11 – the address of the interface where management tunnels terminate
Interface traffic check
Command:
show interfaces utilization
Example:
ESR1000# show interfaces utilization
Interface Period, s Sent, Recv, Frames Sent Frames Recv
Kbit/s Kbit/s
------------- ----------- ----------- ----------- ----------- -----------
gi1/0/1 5 80 49466 37 5960
gi1/0/2 5 76873 27311 11301 5413
gi1/0/3 5 0 0 0 0
...
gi1/0/24 5 0 0 0 0
te1/0/1 5 0 0 0 0
te1/0/2 5 0 0 0 0
po1 5 76954 76778 11339 11373
bridge 2 5 172 115 99 101
bridge 3 5 90 136 53 57
bridge 4 5 49182 24367 5995 5301
bridge 5 5 24920 48515 5261 5976
bridge 6 5 51703 26331 6136 5430
bridge 7 5 0 0 0 0
bridge 8 5 273 12 29 13
bridge 9 5 14 274 12 31
bridge 10 5 0 0 0 2
Null values in 'Sent' or 'Recv' columns demonstrate the lack of activity on the relevant bridge. If the bridge is intended for users, failures are possible.
Check for the DHCP availability from user network
Command:
ping <server ip address> source ip <bridge ip address>
Example:
ESR1000# ping 192.168.1.2 source ip 100.65.64.4 PING 192.168.1.2 (192.168.1.2) from 100.65.64.4 : 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.176 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.152 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.312 ms ^C --- 192.168.114.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.152/0.213/0.312/0.071 ms ESR1000#
192.168.1.2 – DHCP server’s addresswhere:
100.65.64.4 - the address of the ESR bridge that is the user network’s gateway
Check for external resources availability from a user network bridge
Command:
ping <server ip address> source ip <bridge ip address>
Example:
ESR1000# ping 8.8.8.8 source ip 100.65.64.4 PING 8.8.8.8 (8.8.8.8) from 100.65.24.1 : 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=16.1 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=15.8 ms ^C --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 15.892/15.998/16.105/0.165 ms ESR1000#
8.8.8.8 – any external resource that should be available for a userwhere:
100.65.64.4 - the address of the ESR bridge that is the user network’s gateway