I wonder whether VirtualEthernet0/0/1 has been deleted and created again while sub-interface BonEthernet0.1514 was created in between. Looking at the sw_if_index for these interfaces:
· VirtualEthernet0/0/0 => 5 · BonEthernet0.1514 => 6 · VirtualEthernet0/0/1 => 7 I wonder whether VirtualEthernet0/0/1 had sw_if_index 6, was deleted, with sw_if_index 6 reused by BonEthernet0.1514, then created again and now got sw_if_index 7. Now, “show int rx” still had the old sw_if_index of 6 for vhost-user-input queue assignments hence displaying stale information. Regards, John From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Steven Luong (sluong) Sent: Thursday, June 29, 2017 10:26 AM To: Yichen Wang (yicwang) <yicw...@cisco.com>; Denis Lotarev via vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] VPP interface parsing error? Yichen, We need more information for the problem as described. Does the problem just show up when you configure VPP? If that is the case, please unicast me the config and procedure to recreate the problem. If it is difficult to reproduce, please run the debug image with gdb and I can work with you when you got it to happen. Steven From: <vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>> on behalf of "Yichen Wang (yicwang)" <yicw...@cisco.com<mailto:yicw...@cisco.com>> Date: Wednesday, June 28, 2017 at 6:05 PM To: Denis Lotarev via vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: [vpp-dev] VPP interface parsing error? Hi, VPP folks, I am on latest VPP 17.07-rc1, and saw an interface parsing error. vpp# show int Name Idx State Counter Count BondEthernet0 3 up rx packets 1955066091 rx bytes 125124243370 tx packets 1508472227 tx bytes 96542222800 drops 317 rx-miss 1328405166 BondEthernet0.1527 4 up rx packets 1422663050 rx bytes 91050435200 tx packets 532269842 tx bytes 34065269888 drops 1 BondEthernet0.1514 6 up rx packets 532402727 rx bytes 34073774528 tx packets 976202368 tx bytes 62476951552 drops 2 TenGigabitEthernet81/0/1 2 bond-slave rx-miss 1109342837 TenGigabitEthernete/0/1 1 bond-slave rx-miss 219062329 VirtualEthernet0/0/0 5 up rx packets 532269844 rx bytes 31936190640 tx packets 1422663049 tx bytes 85359782940 drops 430668918 VirtualEthernet0/0/1 7 up rx packets 976202370 rx bytes 58572142200 tx packets 532402725 tx bytes 31944163500 drops 27063 local0 0 down vpp# show interface rx-pl Thread 1 (vpp_wk_0): node dpdk-input: TenGigabitEthernete/0/1 queue 0 (polling) TenGigabitEthernet81/0/1 queue 0 (polling) BondEthernet0 queue 0 (polling) Thread 2 (vpp_wk_1): node dpdk-input: TenGigabitEthernete/0/1 queue 1 (polling) TenGigabitEthernet81/0/1 queue 1 (polling) BondEthernet0 queue 1 (polling) Thread 3 (vpp_wk_2): node vhost-user-input: BondEthernet0.1527 queue 0 (polling) Thread 4 (vpp_wk_3): node vhost-user-input: VirtualEthernet0/0/0 queue 0 (polling) It is clearly wrong for the CLI above. BondEthernet0.1527 cannot be in vhost-user-input node. Also “show vhost” also confirms that Thread 3 should have VirtualEthernet0/0/0 and Thread 4 should have VirtualEthernet0/0/1. So I believe this is just the names shown here are wrong, but this will be really confusing… ☺ Thanks very much! Regards, Yichen
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
