search

open-switch / opx-nas-l3

https://openswitch.net
1 stars 9 forks source link

No l3 traffic forwarding on S6010 after reload #30

Closed waliulislam closed 5 years ago

waliulislam commented 5 years ago

L3 unicast trafic get dropped at ingress port. Broadcast and multicast is fine. ARP get resolved and OSPF neighborship is ok. But data traffic or ICMP does not reach to peer device.This is an intermittent issue.

Ping is not working:

root@AG1:~# vtysh -c "show ip ospf nei"

Neighbor ID     Pri State           Dead Time Address         Interface            RXmtL RqstL DBsmL
100.0.3.1         1 Full/DROther      39.147s 100.3.0.1       br3101:100.3.0.0         0     0     0
100.0.3.1         1 Full/DROther      39.147s 100.3.1.1       br3102:100.3.1.0         0     0     0
100.0.3.1         1 Full/DROther      39.147s 100.3.2.1       br3103:100.3.2.0         0     0     0
100.0.3.1         1 Full/DROther      39.147s 100.3.3.1       br3104:100.3.3.0         0     0     0
............
............

root@AG1:~# ifconfig -a br3101
br3101: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 100.3.0.0  netmask 255.255.255.254  broadcast 255.255.255.255
        inet6 fe80::f68e:38ff:fe1c:c56  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::f68e:38ff:fe1c:be2  prefixlen 64  scopeid 0x20<link>
        ether f4:8e:38:1c:0c:56  txqueuelen 1000  (Ethernet)
        RX packets 2252  bytes 265292 (259.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2474  bytes 313068 (305.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@AG1:~# ping 100.3.0.1
PING 100.3.0.1 (100.3.0.1) 56(84) bytes of data.
^C
--- 100.3.0.1 ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 13293ms

root@AG1:~# ip neigh show | grep 100.3.0.1
100.3.0.1 dev br3101 lladdr d8:9e:f3:be:e2:c9 REACHABLE
root@AG1:~#

Receving data traffic from peer destination is host belongs to 120.30.0.0/16 network.

root@AG1:~# ip route show 120.30.0.0/16
120.30.0.0/16 proto 188 metric 20
        nexthop via 100.3.0.1  dev br3101 weight 1
        nexthop via 100.3.1.1  dev br3102 weight 1
        nexthop via 100.3.2.1  dev br3103 weight 1
        nexthop via 100.3.3.1  dev br3104 weight 1
        nexthop via 100.3.4.1  dev br3105 weight 1
        nexthop via 100.3.5.1  dev br3106 weight 1
        nexthop via 100.3.6.1  dev br3107 weight 1
        nexthop via 100.3.7.1  dev br3108 weight 1
        nexthop via 100.3.8.1  dev br3109 weight 1
        nexthop via 100.3.9.1  dev br3110 weight 1
        nexthop via 100.3.10.1  dev br3111 weight 1
        nexthop via 100.3.11.1  dev br3112 weight 1
        nexthop via 100.3.12.1  dev br3113 weight 1
        nexthop via 100.3.13.1  dev br3114 weight 1
        nexthop via 100.3.14.1  dev br3115 weight 1
        nexthop via 100.3.15.1  dev br3116 weight 1

root@AG1:~# ip route show 120.30.0.0/16
120.30.0.0/16 proto 188 metric 20
        nexthop via 100.3.0.1  dev br3101 weight 1
        nexthop via 100.3.1.1  dev br3102 weight 1
        nexthop via 100.3.2.1  dev br3103 weight 1
        nexthop via 100.3.3.1  dev br3104 weight 1
        nexthop via 100.3.4.1  dev br3105 weight 1
        nexthop via 100.3.5.1  dev br3106 weight 1
        nexthop via 100.3.6.1  dev br3107 weight 1
        nexthop via 100.3.7.1  dev br3108 weight 1
        nexthop via 100.3.8.1  dev br3109 weight 1
        nexthop via 100.3.9.1  dev br3110 weight 1
        nexthop via 100.3.10.1  dev br3111 weight 1
        nexthop via 100.3.11.1  dev br3112 weight 1
        nexthop via 100.3.12.1  dev br3113 weight 1
        nexthop via 100.3.13.1  dev br3114 weight 1
        nexthop via 100.3.14.1  dev br3115 weight 1
        nexthop via 100.3.15.1  dev br3116 weight 1
root@AG1:~#
jeff-yin commented 5 years ago

@waliulislam please see if the issue still occurs on OPX 3.1.0 beta release

jeff-yin commented 5 years ago

@waliulislam I'll close the issue for now (you can always reopen it later if you see it again).