Re: open-iscsi: iSCSI boot fails when network bonding enabled
On Mon, Jul 10, 2017 at 05:57:57AM -0700, George Kennedy wrote: > Also, 'iscsid' is runnig prior to the bond interface setup. If you run it as 'iscsid -d ' do you see any extra output when the network interface goes down? Thanks. > > On Friday, July 7, 2017 at 2:33:29 PM UTC-4, George Kennedy wrote: > > > > Running RHEL 6.7 with a Xen guest that's an iSCSI target and a second Xen > > guest that > > installs to the iSCSI target, the subsequent iSCSI boot from the iSCSI > > target fails > > if network bonding is configured in the second Xen guest. > > > > iSCSI boot works ok if network bonding is not setup in the second Xen > > guest. > > > > It appears that when the network bonding setup is attempted, the slave > > network > > interface cannot be brought down to be made the bonding slave because the > > iSCSI > > rootfs is accessed through what would be the slave network interface. > > > > Has anyone else encountered this issue? > > > > Here's console output showing the error: > > > > Bringing up loopback interface: [ OK ] > > Bringing up interface bond0: > > [ 46.467963] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) > > [ 46.484767] bonding: bond0 is being created... > > [ 46.490626] bonding: bond0 already exists > > [ 46.560601] bond0: Setting MII monitoring interval to 250 > > [ 46.569844] bond0: Setting use_carrier to 1 > > [ 46.574589] bond0: Setting up delay to 500 > > [ 46.579601] bond0: Setting down delay to 500 > > [ 46.584645] bond0: Setting primary_reselect to failure (2) > > [ 46.728908] bond0: Setting MII monitoring interval to 250 > > [ 46.737620] bond0: Note: Updating updelay (to 500) since it is a > > multiple of the miimon value > > [ 46.749168] bond0: Note: Updating downdelay (to 500) since it is a > > multiple of the miimon value > > [ 46.759837] bond0: Setting use_carrier to 1 > > [ 46.764687] bond0: Setting up delay to 500 > > [ 46.769476] bond0: Setting down delay to 500 > > [ 46.774468] bond0: Setting primary_reselect to failure (2) > > [ 47.090932] bond0: Adding slave eth0 > > [ 47.131796] bond0: Enslaving eth0 as a backup interface with a down link > > [ 47.142334] bond0: Setting eth0 as primary slave > > [ 49.115135] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow > > Control: RX > > [ 49.289431] bond0: link status up for interface eth0, enabling it in 0 > > ms > > [ 49.300463] bond0: link status definitely up for interface eth0, 1000 > > Mbps full duplex > > [ 49.310302] bond0: making interface eth0 the new active one > > [ 49.331748] bond0: first active interface up! > > [ 56.684137] connection1:0: ping timeout of 5 secs expired, recv > > timeout 5, last rx 4294713972, last ping 4294718976, now 4294723984 > > [ 56.685064] connection1:0: detected conn error (1022) > > [ 176.702085] session1: session recovery timed out after 120 secs > > [ 176.709606] sd 2:0:0:1: rejecting I/O to offline device > > [ 176.710573] sd 2:0:0:1: [sda] killing request > > [ 176.710573] sd 2:0:0:1: rejecting I/O to offline device > > [ 176.710573] sd 2:0:0:1: rejecting I/O to offline device > > ... > > > > Here's the original ifcfg file (there's only one): > > > > ifcfg-eth0: > > --- > > HWADDR="00:21:F6:00:08:FC" > > DEVICE=eth0 > > TYPE=Ethernet > > ONBOOT=yes > > NM_CONTROLLED=yes > > BOOTPROTO=dhcp > > > > > > Here are the ifcfg files used for bonding (again only one network > > interface): > > > > ifcfg-eth0: > > --- > > DEVICE="eth0" > > BOOTPROTO="none" > > HWADDR="00:21:F6:00:08:FC" > > MASTER="bond0" > > SLAVE="yes" > > NM_CONTROLLED="no" > > ONBOOT="yes" > > > > ifcfg-bond0 > > --- > > DEVICE=bond0 > > BONDING_OPTS="mode=1 miimon=250 use_carrier=1 updelay=500 downdelay=500 > > primary_reselect=2 primary=eth0" > > BOOTPROTO="dhcp" > > ONBOOT=yes > > > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: open-iscsi: iSCSI boot fails when network bonding enabled
Also, 'iscsid' is runnig prior to the bond interface setup. On Friday, July 7, 2017 at 2:33:29 PM UTC-4, George Kennedy wrote: > > Running RHEL 6.7 with a Xen guest that's an iSCSI target and a second Xen > guest that > installs to the iSCSI target, the subsequent iSCSI boot from the iSCSI > target fails > if network bonding is configured in the second Xen guest. > > iSCSI boot works ok if network bonding is not setup in the second Xen > guest. > > It appears that when the network bonding setup is attempted, the slave > network > interface cannot be brought down to be made the bonding slave because the > iSCSI > rootfs is accessed through what would be the slave network interface. > > Has anyone else encountered this issue? > > Here's console output showing the error: > > Bringing up loopback interface: [ OK ] > Bringing up interface bond0: > [ 46.467963] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) > [ 46.484767] bonding: bond0 is being created... > [ 46.490626] bonding: bond0 already exists > [ 46.560601] bond0: Setting MII monitoring interval to 250 > [ 46.569844] bond0: Setting use_carrier to 1 > [ 46.574589] bond0: Setting up delay to 500 > [ 46.579601] bond0: Setting down delay to 500 > [ 46.584645] bond0: Setting primary_reselect to failure (2) > [ 46.728908] bond0: Setting MII monitoring interval to 250 > [ 46.737620] bond0: Note: Updating updelay (to 500) since it is a > multiple of the miimon value > [ 46.749168] bond0: Note: Updating downdelay (to 500) since it is a > multiple of the miimon value > [ 46.759837] bond0: Setting use_carrier to 1 > [ 46.764687] bond0: Setting up delay to 500 > [ 46.769476] bond0: Setting down delay to 500 > [ 46.774468] bond0: Setting primary_reselect to failure (2) > [ 47.090932] bond0: Adding slave eth0 > [ 47.131796] bond0: Enslaving eth0 as a backup interface with a down link > [ 47.142334] bond0: Setting eth0 as primary slave > [ 49.115135] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow > Control: RX > [ 49.289431] bond0: link status up for interface eth0, enabling it in 0 > ms > [ 49.300463] bond0: link status definitely up for interface eth0, 1000 > Mbps full duplex > [ 49.310302] bond0: making interface eth0 the new active one > [ 49.331748] bond0: first active interface up! > [ 56.684137] connection1:0: ping timeout of 5 secs expired, recv > timeout 5, last rx 4294713972, last ping 4294718976, now 4294723984 > [ 56.685064] connection1:0: detected conn error (1022) > [ 176.702085] session1: session recovery timed out after 120 secs > [ 176.709606] sd 2:0:0:1: rejecting I/O to offline device > [ 176.710573] sd 2:0:0:1: [sda] killing request > [ 176.710573] sd 2:0:0:1: rejecting I/O to offline device > [ 176.710573] sd 2:0:0:1: rejecting I/O to offline device > ... > > Here's the original ifcfg file (there's only one): > > ifcfg-eth0: > --- > HWADDR="00:21:F6:00:08:FC" > DEVICE=eth0 > TYPE=Ethernet > ONBOOT=yes > NM_CONTROLLED=yes > BOOTPROTO=dhcp > > > Here are the ifcfg files used for bonding (again only one network > interface): > > ifcfg-eth0: > --- > DEVICE="eth0" > BOOTPROTO="none" > HWADDR="00:21:F6:00:08:FC" > MASTER="bond0" > SLAVE="yes" > NM_CONTROLLED="no" > ONBOOT="yes" > > ifcfg-bond0 > --- > DEVICE=bond0 > BONDING_OPTS="mode=1 miimon=250 use_carrier=1 updelay=500 downdelay=500 > primary_reselect=2 primary=eth0" > BOOTPROTO="dhcp" > ONBOOT=yes > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
open-iscsi: iSCSI boot fails when network bonding enabled
Running RHEL 6.7 with a Xen guest that's an iSCSI target and a second Xen guest that installs to the iSCSI target, the subsequent iSCSI boot from the iSCSI target fails if network bonding is configured in the second Xen guest. iSCSI boot works ok if network bonding is not setup in the second Xen guest. It appears that when the network bonding setup is attempted, the slave network interface cannot be brought down to be made the bonding slave because the iSCSI rootfs is accessed through what would be the slave network interface. Has anyone else encountered this issue? Here's console output showing the error: Bringing up loopback interface: [ OK ] Bringing up interface bond0: [ 46.467963] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) [ 46.484767] bonding: bond0 is being created... [ 46.490626] bonding: bond0 already exists [ 46.560601] bond0: Setting MII monitoring interval to 250 [ 46.569844] bond0: Setting use_carrier to 1 [ 46.574589] bond0: Setting up delay to 500 [ 46.579601] bond0: Setting down delay to 500 [ 46.584645] bond0: Setting primary_reselect to failure (2) [ 46.728908] bond0: Setting MII monitoring interval to 250 [ 46.737620] bond0: Note: Updating updelay (to 500) since it is a multiple of the miimon value [ 46.749168] bond0: Note: Updating downdelay (to 500) since it is a multiple of the miimon value [ 46.759837] bond0: Setting use_carrier to 1 [ 46.764687] bond0: Setting up delay to 500 [ 46.769476] bond0: Setting down delay to 500 [ 46.774468] bond0: Setting primary_reselect to failure (2) [ 47.090932] bond0: Adding slave eth0 [ 47.131796] bond0: Enslaving eth0 as a backup interface with a down link [ 47.142334] bond0: Setting eth0 as primary slave [ 49.115135] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 49.289431] bond0: link status up for interface eth0, enabling it in 0 ms [ 49.300463] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex [ 49.310302] bond0: making interface eth0 the new active one [ 49.331748] bond0: first active interface up! [ 56.684137] connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4294713972, last ping 4294718976, now 4294723984 [ 56.685064] connection1:0: detected conn error (1022) [ 176.702085] session1: session recovery timed out after 120 secs [ 176.709606] sd 2:0:0:1: rejecting I/O to offline device [ 176.710573] sd 2:0:0:1: [sda] killing request [ 176.710573] sd 2:0:0:1: rejecting I/O to offline device [ 176.710573] sd 2:0:0:1: rejecting I/O to offline device ... Here's the original ifcfg file (there's only one): ifcfg-eth0: --- HWADDR="00:21:F6:00:08:FC" DEVICE=eth0 TYPE=Ethernet ONBOOT=yes NM_CONTROLLED=yes BOOTPROTO=dhcp Here are the ifcfg files used for bonding (again only one network interface): ifcfg-eth0: --- DEVICE="eth0" BOOTPROTO="none" HWADDR="00:21:F6:00:08:FC" MASTER="bond0" SLAVE="yes" NM_CONTROLLED="no" ONBOOT="yes" ifcfg-bond0 --- DEVICE=bond0 BONDING_OPTS="mode=1 miimon=250 use_carrier=1 updelay=500 downdelay=500 primary_reselect=2 primary=eth0" BOOTPROTO="dhcp" ONBOOT=yes -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
