That works. Thanks John. On Thu, Mar 30, 2017 at 5:52 PM, John Lo (loj) <[email protected]> wrote:
> Please take the latest 1704 version with v17.04-rc1…. and see if it works > better. -John > > > > *From:* John Pearson [mailto:[email protected]] > *Sent:* Thursday, March 30, 2017 8:32 PM > *To:* John Lo (loj) <[email protected]> > *Cc:* [email protected] > *Subject:* Re: [vpp-dev] vdev bonding -- carrier down > > > > Hi John, > > > > show ver verbose: Version: v17.04-rc0~302-g4a3f69c > > > > Thanks > > > > On Thu, Mar 30, 2017 at 5:28 PM, John Lo (loj) <[email protected]> wrote: > > Which version of VPP are you using? Is it latest from either 1704 or > master? > > After VPP moved to DPDK 17.02, there were some breakages with bonded > interface PMD that was fixes via these patches: > > https://gerrit.fd.io/r/#/c/5786/ > > https://gerrit.fd.io/r/#/c/5788/ > > > > Regards, > > John > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *John Pearson > *Sent:* Thursday, March 30, 2017 8:19 PM > *To:* [email protected] > *Subject:* [vpp-dev] vdev bonding -- carrier down > > > > Hi all, > > > > I'm trying to setup bonding in mode 1 (http://dpdk.org/doc/guides/ > prog_guide/link_bonding_poll_mode_drv_lib.html) with this config: > > dpdk { > > dev 0000:08:00.0 > > dev 0000:09:00.0 > > vdev eth_bond0,mode=1,slave=0000:08:00.0,primary=0000:09:00.0 > > } > > > > Nothing comes up with *show error:* > > vpp# show error > > Count Node Reason > > > > *show hardware output:* > > Name Idx Link Hardware > > GigabitEthernet8/0/0 1 down GigabitEthernet8/0/0 > > Ethernet address 00:03:a2:0a:27:fb > > Intel e1000 > > carrier down > > rx queues 1, rx desc 1024, tx queues 1, tx desc 1024 > > > > GigabitEthernet9/0/0 2 down GigabitEthernet9/0/0 > > Ethernet address 00:06:a3:0a:27:fc > > Intel e1000 > > carrier down > > rx queues 1, rx desc 1024, tx queues 1, tx desc 1024 > > > > UnknownEthernet2 3 down UnknownEthernet2 > > Ethernet address 00:00:00:00:00:00 > > ### UNKNOWN ### > > carrier down > > rx queues 1, rx desc 1024, tx queues 1, tx desc 1024 > > cpu socket 0 > > > > local0 0 down local0 > > local > > > > *show pci output:* > > Address Sock VID:PID Link Speed Driver Product Name > Vital Product Data > > 0000:00:14.0 8086:1f41 unknown igb > > > 0000:00:14.1 8086:1f41 unknown igb > > > 0000:00:14.2 8086:1f41 unknown igb > > > 0000:00:14.3 8086:1f41 unknown igb > > > 0000:08:00.0 8086:1539 2.5 GT/s x1 uio_pci_generic > > > 0000:09:00.0 8086:1539 2.5 GT/s x1 uio_pci_generic > > > > *show int output:* > > Name Idx State Counter > Count > > GigabitEthernet8/0/0 1 down > > GigabitEthernet9/0/0 2 down > > UnknownEthernet2 3 down > > local0 > > > > > > */var/log/syslog output: * > > Mar 30 16:51:43 vppbox vpp[1599]: EAL: Detected 4 lcore(s) > > Mar 30 16:51:43 vppbox vpp[1599]: EAL: Probing VFIO support... > > Mar 30 16:51:43 vppbox vnet[1599]: EAL: Probing VFIO support... > > Mar 30 16:51:44 vppbox vpp[1599]: EAL: PCI device 0000:08:00.0 on NUMA > socket -1 > > Mar 30 16:51:44 vppbox vpp[1599]: EAL: probe driver: 8086:1539 > net_e1000_igb > > Mar 30 16:51:44 vppbox vnet[1599]: EAL: PCI device 0000:08:00.0 on NUMA > socket -1 > > Mar 30 16:51:44 vppbox vnet[1599]: EAL: probe driver: 8086:1539 > net_e1000_igb > > Mar 30 16:51:44 vppbox vpp[1599]: EAL: PCI device 0000:09:00.0 on NUMA > socket -1 > > Mar 30 16:51:44 vppbox vpp[1599]: EAL: probe driver: 8086:1539 > net_e1000_igb > > Mar 30 16:51:44 vppbox vnet[1599]: EAL: PCI device 0000:09:00.0 on NUMA > socket -1 > > Mar 30 16:51:44 vppbox vnet[1599]: EAL: probe driver: 8086:1539 > net_e1000_igb > > Mar 30 16:51:44 vppbox vpp[1599]: EAL: Initializing pmd_bond for eth_bond0 > > Mar 30 16:51:44 vppbox vnet[1599]: EAL: Initializing pmd_bond for eth_bond0 > > Mar 30 16:51:44 vppbox vpp[1599]: EAL: Create bonded device eth_bond0 on > port 2 in mode 1 on socket 0. > > Mar 30 16:51:44 vppbox vnet[1599]: EAL: Create bonded device eth_bond0 on > port 2 in mode 1 on socket 0. > > Mar 30 16:51:44 vppbox vpp[1599]: /usr/bin/vpp[1599]: dpdk_lib_init:309: > DPDK drivers found 3 ports... > > Mar 30 16:51:44 vppbox /usr/bin/vpp[1599]: dpdk_lib_init:309: DPDK drivers > found 3 ports... > > Mar 30 16:51:44 vppbox vpp[1599]: /usr/bin/vpp[1599]: > dpdk_ipsec_process:241: DPDK Cryptodev support is disabled, default to > OpenSSL IPsec > > Mar 30 16:51:44 vppbox /usr/bin/vpp[1599]: dpdk_ipsec_process:241: DPDK > Cryptodev support is disabled, default to OpenSSL IPsec > > Mar 30 16:51:46 vppbox vpp[1599]: /usr/bin/vpp[1599]: unknown input ` > > Mar 30 16:51:46 vppbox /usr/bin/vpp[1599]: unknown input ` > > > > I just have an empty config right now, *output of /tmp/vpp.log:* > > 2017/ 3/30 16:32:44:952: ***** Start: PID 1135 ***** > > 2017/ 3/30 16:32:46:968: ***** Startup Config ***** > > 2017/ 3/30 16:32:46:968: ***** End Startup Config ***** > > 2017/ 3/30 16:51:44:780: ***** Start: PID 1599 ***** > > 2017/ 3/30 16:51:46:786: ***** Startup Config ***** > > 2017/ 3/30 16:51:46:787: ***** End Startup Config ***** > > > > > > I came across this similar issue(https://jira.fd.io/browse/VPP-614) which > was closed after turning iommu on, I did that to no avail: > > GRUB_CMDLINE_LINUX_DEFAULT="iommu=pt intel_iommu=on" > > >
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
