I am running vpp v20.01-release on Ubuntu 18.04 on an Azure VM. I had been forwarding traffic with VPP for about 5 days and today I noticed that my 2 main interfaces FailsafeEthernet2 and FailsafeEthernet4) had gone down and I could not find a reason. I looked at the journalctl logs (which only go back about 6 hours and the interfaces went down about 18 hours ago), dmesg logs, and ran a few commands in vppctl to no avail.
I was able to restore the interfaces just by setting their state back to 'up'. vpp# show int Name Idx State MTU (L3/IP4/IP6/MPLS) Counter Count FailsafeEthernet2 1 up 9000/0/0/0 rx packets 972 rx bytes 72060 tx packets 1435428 tx bytes 94738701 drops 972 ip4 956 ip6 15 FailsafeEthernet4 2 up 9000/0/0/0 rx packets 1435458 rx bytes 94741057 drops 31 ip4 1435430 ip6 28 I did, however, notice that I have more Linux network interfaces than I expected: ifconfig dtap2: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500 inet6 fe80::20d:3aff:feff:1b82 prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:ff:1b:82 txqueuelen 1000 (Ethernet) RX packets 2012647 bytes 2878934474 (2.8 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24822 bytes 1839632 (1.8 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 dtap3: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500 inet6 fe80::20d:3aff:fe84:aa4f prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:84:aa:4f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1692203 bytes 2362194140 (2.3 GB) TX errors 0 dropped 1096 overruns 0 carrier 0 collisions 0 dtap4: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500 inet6 fe80::20d:3aff:feff:1b82 prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:ff:1b:82 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1527 bytes 113126 (113.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 dtap5: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500 inet6 fe80::20d:3aff:fe84:aa4f prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:84:aa:4f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7164 bytes 6532230 (6.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 dtap8: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500 inet6 fe80::20d:3aff:feff:1b82 prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:ff:1b:82 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1101 bytes 81606 (81.6 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 dtap9: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500 inet6 fe80::20d:3aff:fe84:aa4f prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:84:aa:4f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 67 bytes 4834 (4.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.9.4 netmask 255.255.255.0 broadcast 10.0.9.255 inet6 fe80::20d:3aff:feff:1a42 prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:ff:1a:42 txqueuelen 1000 (Ethernet) RX packets 9860630 bytes 8395557697 (8.3 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7300672 bytes 1643536351 (1.6 GB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500 inet 10.0.8.4 netmask 255.255.255.0 broadcast 10.0.8.255 inet6 fe80::20d:3aff:feff:1b82 prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:ff:1b:82 txqueuelen 1000 (Ethernet) RX packets 45588 bytes 3379906 (3.3 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2012803 bytes 2878946062 (2.8 GB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth2: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500 inet 10.0.10.4 netmask 255.255.255.0 broadcast 10.0.10.255 inet6 fe80::20d:3aff:fe84:aa4f prefixlen 64 scopeid 0x20<link> ether 00:0d:3a:84:aa:4f txqueuelen 1000 (Ethernet) RX packets 1651556 bytes 2368775116 (2.3 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 155 bytes 11518 (11.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 439044 bytes 59701416 (59.7 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 439044 bytes 59701416 (59.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 rename11: flags=6723<UP,BROADCAST,RUNNING,ALLMULTI,SLAVE,MULTICAST> mtu 1500 ether 00:0d:3a:ff:1b:82 txqueuelen 1000 (Ethernet) RX packets 2 bytes 180 (180.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 114841 bytes 163438128 (163.4 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 rename12: flags=6723<UP,BROADCAST,RUNNING,ALLMULTI,SLAVE,MULTICAST> mtu 1500 ether 00:0d:3a:84:aa:4f txqueuelen 1000 (Ethernet) RX packets 53463 bytes 76829988 (76.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 120 bytes 8400 (8.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I am surprised there are so many dtap interfaces. I was expecting only 2 of them. Any suggestions for why my interfaces went down or what I can do to troubleshoot or prevent this? Thanks!
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15864): https://lists.fd.io/g/vpp-dev/message/15864 Mute This Topic: https://lists.fd.io/mt/72540981/21656 Mute #azure: https://lists.fd.io/mk?hashtag=azure&subid=1480452 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
