Bonding broken
145 views
Skip to first unread message
Александр Зыков
Nov 12, 2018, 9:19:31 AM11/12/18
to esos-users
Start setting up ...
Interface bond0 retired after restarting the network
cat /var/log/messages
Nov 12 14:16:02 localhost kernel: [ 7044.835710] bonding: bond0 is being created...
Nov 12 14:16:21 localhost kernel: [ 7064.196784] 8021q: adding VLAN 0 to HW filter on device bond0
Nov 12 14:16:21 localhost kernel: [ 7064.197299] bonding: bond0 is being deleted...
Nov 12 14:16:21 localhost kernel: [ 7064.197368] bond0 (unregistering): Released all slaves
Nov 12 14:16:22 localhost kernel: [ 7064.623280] 8021q: adding VLAN 0 to HW filter on device eno1
Nov 12 14:16:22 localhost kernel: [ 7064.665762] 8021q: adding VLAN 0 to HW filter on device eno2
Nov 12 14:16:27 localhost kernel: [ 7069.425284] igb 0000:02:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[root@nas-02 ~]# date
Mon Nov 12 14:17:02 -00 2018
[root@nas-02 ~]#
Nov 12 14:16:21 localhost kernel: [ 7064.196784] 8021q: adding VLAN 0 to HW filter on device bond0
Nov 12 14:16:21 localhost kernel: [ 7064.197299] bonding: bond0 is being deleted...
Nov 12 14:16:21 localhost kernel: [ 7064.197368] bond0 (unregistering): Released all slaves
Nov 12 14:16:22 localhost kernel: [ 7064.623280] 8021q: adding VLAN 0 to HW filter on device eno1
Nov 12 14:16:22 localhost kernel: [ 7064.665762] 8021q: adding VLAN 0 to HW filter on device eno2
Nov 12 14:16:27 localhost kernel: [ 7069.425284] igb 0000:02:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[root@nas-02 ~]# date
Mon Nov 12 14:17:02 -00 2018
[root@nas-02 ~]#
Marc Smith
Nov 12, 2018, 10:07:30 AM11/12/18
to esos-...@googlegroups.com
Please provide your /etc/network.conf file and the output of running
"/etc/rc.d/rc.network stop && /etc/rc.d/rc.network start" from the
shell.
--Marc
On Mon, Nov 12, 2018 at 9:19 AM Александр Зыков <shur...@yandex.ru> wrote:
>
> Start setting up ...
> You received this message because you are subscribed to the Google Groups "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
"/etc/rc.d/rc.network stop && /etc/rc.d/rc.network start" from the
shell.
--Marc
On Mon, Nov 12, 2018 at 9:19 AM Александр Зыков <shur...@yandex.ru> wrote:
>
> Start setting up ...
>
>
>
> Interface bond0 retired after restarting the network
>
> cat /var/log/messages
>
> Nov 12 14:16:02 localhost kernel: [ 7044.835710] bonding: bond0 is being created...
> Nov 12 14:16:21 localhost kernel: [ 7064.196784] 8021q: adding VLAN 0 to HW filter on device bond0
> Nov 12 14:16:21 localhost kernel: [ 7064.197299] bonding: bond0 is being deleted...
> Nov 12 14:16:21 localhost kernel: [ 7064.197368] bond0 (unregistering): Released all slaves
> Nov 12 14:16:22 localhost kernel: [ 7064.623280] 8021q: adding VLAN 0 to HW filter on device eno1
> Nov 12 14:16:22 localhost kernel: [ 7064.665762] 8021q: adding VLAN 0 to HW filter on device eno2
> Nov 12 14:16:27 localhost kernel: [ 7069.425284] igb 0000:02:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
> [root@nas-02 ~]# date
> Mon Nov 12 14:17:02 -00 2018
> [root@nas-02 ~]#
>
>
> --
>
>
> Interface bond0 retired after restarting the network
>
> cat /var/log/messages
>
> Nov 12 14:16:02 localhost kernel: [ 7044.835710] bonding: bond0 is being created...
> Nov 12 14:16:21 localhost kernel: [ 7064.196784] 8021q: adding VLAN 0 to HW filter on device bond0
> Nov 12 14:16:21 localhost kernel: [ 7064.197299] bonding: bond0 is being deleted...
> Nov 12 14:16:21 localhost kernel: [ 7064.197368] bond0 (unregistering): Released all slaves
> Nov 12 14:16:22 localhost kernel: [ 7064.623280] 8021q: adding VLAN 0 to HW filter on device eno1
> Nov 12 14:16:22 localhost kernel: [ 7064.665762] 8021q: adding VLAN 0 to HW filter on device eno2
> Nov 12 14:16:27 localhost kernel: [ 7069.425284] igb 0000:02:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
> [root@nas-02 ~]# date
> Mon Nov 12 14:17:02 -00 2018
> [root@nas-02 ~]#
>
>
> You received this message because you are subscribed to the Google Groups "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Message has been deleted
Александр Зыков
Nov 13, 2018, 6:43:11 AM11/13/18
to esos-users
[root@nas-02 ~]# cat /sys/class/net/bonding_masters
[root@nas-02 ~]# ls /sys/class/net/
bonding_masters eno1 eno2 enp3s0f0 enp3s0f1 lo sit0
[root@nas-02 ~]# echo +bond0 > /sys/class/net/bonding_masters
[root@nas-02 ~]# cat /sys/class/net/bonding_masters
bond0
[root@nas-02 ~]# ls /sys/class/net/
bond0 bonding_masters eno1 eno2 enp3s0f0 enp3s0f1 lo sit0
[root@nas-02 ~]# /etc/rc.d/rc.network stop && /etc/rc.d/rc.network start
Deleting the current default route (GW: 10.3.3.254)...
Bringing down interface bond0...
Deleting bonding interface bond0...
Bringing down interface eno1...
Bringing down interface eno2...
Bringing down interface enp3s0f0...
Bringing down interface enp3s0f1...
Bringing up interface eno1...
Bringing up interface eno2...
Bringing up interface enp3s0f0...
Bringing up interface enp3s0f1...
Setting MTU for interface eno1...
Running /sbin/udhcpc for interface eno1...
udhcpc: started, v1.26.2
Setting IP address 0.0.0.0 on eno1
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending select for 10.3.3.129
udhcpc: lease of 10.3.3.129 obtained, lease time 86400
Setting IP address 10.3.3.129 on eno1
Deleting routers
route: SIOCDELRT: No such process
Adding router 10.3.3.254
Recreating /etc/resolv.conf
Setting system host name: nas-02.asutp-cps.local
Updating hosts file...
[root@nas-02 ~]# ifconfig -a
eno1 Link encap:Ethernet HWaddr 5C:B9:01:7B:BA:5B
inet addr:10.3.3.129 Bcast:10.3.3.255 Mask:255.255.255.0
inet6 addr: fe80::5eb9:1ff:fe7b:ba5b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5968 errors:0 dropped:0 overruns:0 frame:0
TX packets:5689 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:440070 (429.7 KiB) TX bytes:4102030 (3.9 MiB)
Memory:94300000-943fffff
eno2 Link encap:Ethernet HWaddr 5C:B9:01:7B:BA:5C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Memory:94200000-942fffff
enp3s0f0 Link encap:Ethernet HWaddr 28:80:23:A3:E2:B4
inet6 addr: fe80::2a80:23ff:fea3:e2b4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7623 (7.4 KiB) TX bytes:680 (680.0 B)
Interrupt:16
enp3s0f1 Link encap:Ethernet HWaddr 28:80:23:A3:E2:B5
inet6 addr: fe80::2a80:23ff:fea3:e2b5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7495 (7.3 KiB) TX bytes:680 (680.0 B)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:121 errors:0 dropped:0 overruns:0 frame:0
TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:5438 (5.3 KiB) TX bytes:5438 (5.3 KiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
[root@nas-02 ~]#
понедельник, 12 ноября 2018 г., 18:07:30 UTC+3 пользователь Marc Smith написал:
[root@nas-02 ~]# ls /sys/class/net/
bonding_masters eno1 eno2 enp3s0f0 enp3s0f1 lo sit0
[root@nas-02 ~]# echo +bond0 > /sys/class/net/bonding_masters
[root@nas-02 ~]# cat /sys/class/net/bonding_masters
bond0
[root@nas-02 ~]# ls /sys/class/net/
bond0 bonding_masters eno1 eno2 enp3s0f0 enp3s0f1 lo sit0
[root@nas-02 ~]# /etc/rc.d/rc.network stop && /etc/rc.d/rc.network start
Deleting the current default route (GW: 10.3.3.254)...
Bringing down interface bond0...
Deleting bonding interface bond0...
Bringing down interface eno1...
Bringing down interface eno2...
Bringing down interface enp3s0f0...
Bringing down interface enp3s0f1...
Bringing up interface eno1...
Bringing up interface eno2...
Bringing up interface enp3s0f0...
Bringing up interface enp3s0f1...
Setting MTU for interface eno1...
Running /sbin/udhcpc for interface eno1...
udhcpc: started, v1.26.2
Setting IP address 0.0.0.0 on eno1
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending select for 10.3.3.129
udhcpc: lease of 10.3.3.129 obtained, lease time 86400
Setting IP address 10.3.3.129 on eno1
Deleting routers
route: SIOCDELRT: No such process
Adding router 10.3.3.254
Recreating /etc/resolv.conf
Setting system host name: nas-02.asutp-cps.local
Updating hosts file...
[root@nas-02 ~]# ifconfig -a
eno1 Link encap:Ethernet HWaddr 5C:B9:01:7B:BA:5B
inet addr:10.3.3.129 Bcast:10.3.3.255 Mask:255.255.255.0
inet6 addr: fe80::5eb9:1ff:fe7b:ba5b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5968 errors:0 dropped:0 overruns:0 frame:0
TX packets:5689 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:440070 (429.7 KiB) TX bytes:4102030 (3.9 MiB)
Memory:94300000-943fffff
eno2 Link encap:Ethernet HWaddr 5C:B9:01:7B:BA:5C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Memory:94200000-942fffff
enp3s0f0 Link encap:Ethernet HWaddr 28:80:23:A3:E2:B4
inet6 addr: fe80::2a80:23ff:fea3:e2b4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7623 (7.4 KiB) TX bytes:680 (680.0 B)
Interrupt:16
enp3s0f1 Link encap:Ethernet HWaddr 28:80:23:A3:E2:B5
inet6 addr: fe80::2a80:23ff:fea3:e2b5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7495 (7.3 KiB) TX bytes:680 (680.0 B)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:121 errors:0 dropped:0 overruns:0 frame:0
TX packets:121 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:5438 (5.3 KiB) TX bytes:5438 (5.3 KiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
[root@nas-02 ~]#
понедельник, 12 ноября 2018 г., 18:07:30 UTC+3 пользователь Marc Smith написал:
Message has been deleted
Marc Smith
Nov 13, 2018, 9:58:07 AM11/13/18
to esos-...@googlegroups.com
It appears you haven't configured the bonding interface in the TUI
network setup screen yet (nothing bonding related in
/etc/network.conf). So when the network restarts, nothing will be
created/configured for the bonding setup. See this page for detail on
configuring bonding interfaces:
https://github.com/parodyne/esos/wiki/22_Advanced_System_Setup#nic-bonding
--Marc
On Tue, Nov 13, 2018 at 6:47 AM Александр Зыков <shur...@yandex.ru> wrote:
>
> [root@nas-02 ~]# cat /etc/modprobe.conf
> options bonding max_bonds=0 #what value should be ?????????
> options ocs_fc_scst initiator=1
> options zfs zfs_prefetch_disable=1
> options celerity16fc target_mode=1
network setup screen yet (nothing bonding related in
/etc/network.conf). So when the network restarts, nothing will be
created/configured for the bonding setup. See this page for detail on
configuring bonding interfaces:
https://github.com/parodyne/esos/wiki/22_Advanced_System_Setup#nic-bonding
--Marc
On Tue, Nov 13, 2018 at 6:47 AM Александр Зыков <shur...@yandex.ru> wrote:
>
> [root@nas-02 ~]# cat /etc/modprobe.conf
> options bonding max_bonds=0 #what value should be ?????????
> options ocs_fc_scst initiator=1
> options zfs zfs_prefetch_disable=1
> options celerity16fc target_mode=1
> [root@nas-02 ~]#
>
>
> понедельник, 12 ноября 2018 г., 18:07:30 UTC+3 пользователь Marc Smith написал:
>>
>
>
> понедельник, 12 ноября 2018 г., 18:07:30 UTC+3 пользователь Marc Smith написал:
>>
Александр Зыков
Nov 13, 2018, 10:00:10 AM11/13/18
to esos-users
If in the TUI
system -> Network settings -> bond0 check the IP Settings: Disable
checkbox, then the interface bond0 is deleted when the network is
restarted.
How to configure VLAN 3 bond0.3 ???
вторник, 13 ноября 2018 г., 14:43:11 UTC+3 пользователь Александр Зыков написал:
How to configure VLAN 3 bond0.3 ???
вторник, 13 ноября 2018 г., 14:43:11 UTC+3 пользователь Александр Зыков написал:
Александр Зыков
Nov 13, 2018, 10:05:17 AM11/13/18
to esos-users
If in the TUI
system -> Network settings -> bond0 check the IP Settings: Disable
checkbox, then the interface bond0 is deleted when the network is
restarted.
How to configure VLAN 3 bond0.3 ???
How to configure VLAN 3 bond0.3 ???
вторник, 13 ноября 2018 г., 17:58:07 UTC+3 пользователь Marc Smith написал:
Marc Smith
Nov 13, 2018, 10:06:05 AM11/13/18
to esos-...@googlegroups.com
You have to set an IP address (static or DHCP) for the bonding
interface, leaving it disabled will cause that interface configuration
to not be saved.
If you need something more exotic outside of what the TUI / rc.network
script can handle, then see this page:
https://github.com/parodyne/esos/wiki/22_Advanced_System_Setup#extra-configuration
And put your shell commands into the pre-SCST file for the network
config (everything) and don't rely on rc.network to do anything
network config.
--Marc
interface, leaving it disabled will cause that interface configuration
to not be saved.
If you need something more exotic outside of what the TUI / rc.network
script can handle, then see this page:
https://github.com/parodyne/esos/wiki/22_Advanced_System_Setup#extra-configuration
And put your shell commands into the pre-SCST file for the network
config (everything) and don't rely on rc.network to do anything
network config.
--Marc
Reply all
Reply to author
Forward
0 new messages