Alcatel-Lucent OmniSwitch 10K - Advanced Troubleshooting

OmniSwitch OS6860/OS6900/OS10K Troubleshooting Guide Part No.032996-00 Rev.A
AOS Release 7.X and 8.X January 2015
Alcatel-Lucent Page 61 of 148
<snap> swlogd: ipni udprelay debug1(6) port-chk: match
<snap> swlogd: ipni udprelay debug3(8) ipni_is_udp_pkt_dhcp: udp-dport 53
<snap> swlogd: ipni udprelay debug2(7) pkt (len 98) sent to UDP-CMM
<snap> swlogd: udpRelay main debug1(6) [UDP Relay Debug]: IP ni Receive(slot 1).... len = 130
<snap> swlogd: udpRelay main debug1(6) [UDP Relay Debug]: Processing pket from NI ....
<snap> swlogd: udpRelay main debug1(6) UdpPort = 4529
<snap> swlogd: udpRelay main debug1(6) Gport = 47
<snap> swlogd: udpRelay main debug1(6) VLAN = 100
<snap> swlogd: udpRelay main debug1(6) VRF = 0
<snap> swlogd: udpRelay main debug1(6) Pkt len = 98
<snap> swlogd: udpRelay main debug1(6) UDP Relay CMM: udpRelay_pktForwarding ...
<snap> swlogd: udpRelay main debug1(6) [dhcpSnoopingCheckLpsViolation:10637] Gport: 47
<snap> swlogd: udpRelay main debug3(8) dhcpSnoopingGetPortEntry: ifIndex 1048
<snap> swlogd: udpRelay main debug3(8) dhcpSnoopingGetPortEntry: ret 0xaa498
<snap> swlogd: udpRelay main debug1(6) udpRelay_pktForwarding: gport: 47, vid: 100, pkt len 102
vrf = 0, ifIndex = 1048
<snap> swlogd: udpRelay main debug1(6) ...packet get transfered to genericHandleRequest: Msg
type=0 VRF=0
<snap> swlogd: udpRelay main debug1(6)genericHandleRequest:from vlan = 100,sport = 4529, dport=53
<snap> swlogd: udpRelay main debug1(6) Generic REQ: req recd on i/f addr = 0xc0a864fe
<snap> swlogd: ipni udprelay debug2(7) pkt (len 72) sent to UDP-CMM
<snap> swlogd: udpRelay main debug1(6) [UDP Relay Debug]: IP ni Receive (slot 1).... len = 104
<snap> swlogd: udpRelay main debug1(6) UdpPort = 4530
<snap> swlogd: udpRelay main debug1(6) Pkt len = 72
<snap> swlogd: udpRelay main debug1(6) udpRelay_pktForwarding: gport: 47, vid: 100, pkt len 76
vrf = 0, ifIndex = 1048
<snap> swlogd: udpRelay main debug1(6)genericHandleRequest:from vlan = 100, sport = 4530,dport=53
<snap> shasta swlogd: ipni udprelay debug2(7) port-chk: udp-dport 137
9.4. Advanced troubleshooting
DHCP Relay operation can be monitored using "debug ip packet".
An example of a DHCP Renew (the client is connected to port 1/1/48, the server is connected to port 1/1/1):
-> debug ip packet protocol udp start timeout 60
-> 1 1 R 1/1/48 0007e9:1ff566->ffffff:ffffff IP 0.0.0.0->255.255.255.255 UDP 68,67
1 1 S UDP 0007e9:1ff566->ffffff:ffffff IP 0.0.0.0->255.255.255.255 UDP 68,67
1 C S 1/1/1 e8e732:ab17bd->00e0b1:f47b19 IP 192.168.10.253->192.168.10.254 UDP 67,67
1 1 R CMM1 e8e732:ab17bd->00e0b1:f47b19 IP 192.168.10.253->192.168.10.254 UDP 67,67
1 1 S 1/1/1 e8e732:ab17bd->00e0b1:f47b19 IP 192.168.10.253->192.168.10.254 UDP 67,67
1 1 S FLD e8e732:ab17bd->ffffff:ffffff ARP Request 192.168.100.254->192.168.100.100
1 1 R 1/1/1 00e0b1:f47b19->e8e732:ab17bd IP 192.168.10.254->192.168.100.254 UDP 67,67
1 1 S UDP 00e0b1:f47b19->e8e732:ab17bd IP 192.168.10.254->192.168.100.254 UDP 67,67
1 1 R UDP e8e732:ab17bd->0007e9:1ff566 IP 192.168.100.254->255.255.255.255 UDP 67,68
1 1 S 1/1/48 e8e732:ab17bd->0007e9:1ff566 IP 192.168.100.254->255.255.255.255 UDP 67,68
1 1 R 1/1/48 0007e9:1ff566->ffffff:ffffff IP 0.0.0.0->255.255.255.255 UDP 68,67
1 1 S UDP 0007e9:1ff566->ffffff:ffffff IP 0.0.0.0->255.255.255.255 UDP 68,67
1 C S 1/1/1 e8e732:ab17bd->00e0b1:f47b19 IP 192.168.10.253->192.168.10.254 UDP 67,67
1 1 R CMM1 e8e732:ab17bd->00e0b1:f47b19 IP 192.168.10.253->192.168.10.254 UDP 67,67
1 1 S 1/1/1 e8e732:ab17bd->00e0b1:f47b19 IP 192.168.10.253->192.168.10.254 UDP 67,67
1 1 R 1/1/1 00e0b1:f47b19->e8e732:ab17bd IP 192.168.10.254->192.168.100.254 UDP 67,67
1 1 S UDP 00e0b1:f47b19->e8e732:ab17bd IP 192.168.10.254->192.168.100.254 UDP 67,67
1 1 R UDP e8e732:ab17bd->0007e9:1ff566 IP 192.168.100.254->255.255.255.255 UDP 67,68
1 1 S 1/1/48 e8e732:ab17bd->0007e9:1ff566 IP 192.168.100.254->255.255.255.255 UDP 67,68
1 1 R 1/1/48 0007e9:1ff566->ffffff:ffffff ARP Request 192.168.100.100->192.168.100.100
1 1 R 1/1/48 0007e9:1ff566->ffffff:ffffff ARP Request 192.168.100.100->192.168.100.100
1 1 R 1/1/48 0007e9:1ff566->ffffff:ffffff ARP Request 192.168.100.100->192.168.100.100
An example of DHCP Release (the client is connected to port 1/1/48, the server is connected to port 1/1/1):
-> debug ip packet protocol udp start timeout 60
-> 1 1 R 1/1/48 0007e9:1ff566->e8e732:ab17bd IP 192.168.100.100->192.168.10.254 UDP 68,67
1 1 S UDP 0007e9:1ff566->e8e732:ab17bd IP 192.168.100.100->192.168.10.254 UDP 68,67
1 C S FLD e8e732:ab17bd->ffffff:ffffff ARP Request 192.168.10.253->192.168.10.254
1 1 R CMM e8e732:ab17bd->ffffff:ffffff ARP Request 192.168.10.253->192.168.10.254
1 1 S FLD e8e732:ab17bd->ffffff:ffffff ARP Request 192.168.10.253->192.168.10.254
1 1 R 1/1/1 00e0b1:f47b19->e8e732:ab17bd ARP Reply 192.168.10.254->192.168.10.253