[rear-users] is there a problem with bonding network?

Schlomo Schapiro schlomo at schapiro.org
Tue Jul 3 10:38:08 CEST 2012


Hi,

what happens if you run
the /etc/scripts/system-setup.d/60-network-devices.sh script manually?

Try adding debug to the ReaR *kernel* command line, it should set the
rescue system into debug mode and give you everything in verbose.

Regards,
Schlomo

PS: I am happy to see others also use meaningful network device names...

On 3 July 2012 00:11, Philipp Westphal <westphal at b1-systems.de> wrote:

>
>
> Hi,
>
> I installed ReaR (Relax and Recover 1.12.0, from distribution package
> (SLES 11SP1)) recently onto a machine, running some Database
> stuff and should be fast and easily to recover.
> Everything works fine so far, but lately we tried to test the recovery
> media and found that the network is not configured.
> Since the Backup now lurks on NFS this is not what i hoped expect.
>
>
> ---8<---
> # ip a s
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
> qlen 1000
>     link/ether 2c:76:8a:af:81:30 brd ff:ff:ff:ff:ff:ff
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
> qlen 1000
>     link/ether e4:11:5b:b5:cb:da brd ff:ff:ff:ff:ff:ff
> 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
> qlen 1000
>     link/ether 3c:d9:2b:0b:0f:c8 brd ff:ff:ff:ff:ff:ff
> 5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 100
>     link/ether 00:26:55:ea:f7:c2 brd ff:ff:ff:ff:ff:ff
> 6: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
>     link/ether 78:e3:b5:06:66:0c brd ff:ff:ff:ff:ff:ff
> 7: eth8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
>     link/ether 78:e3:b5:06:66:0d brd ff:ff:ff:ff:ff:ff
> 8: eth9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
>     link/ether 78:e3:b5:06:66:0e brd ff:ff:ff:ff:ff:ff
> 9: eth10: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
>     link/ether 78:e3:b5:06:66:0f brd ff:ff:ff:ff:ff:ff
> 10: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
>     link/ether 00:26:55:ea:f7:c3 brd ff:ff:ff:ff:ff:ff
> 11: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 100
>     link/ether 00:26:55:ea:ef:78 brd ff:ff:ff:ff:ff:ff
> 12: eth6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
>     link/ether 00:26:55:ea:ef:79 brd ff:ff:ff:ff:ff:ff
> 13: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 14: bond1: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 15: bond2: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 16: bond3: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN
>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
>
> --->8---
>
> /etc/scripts/system-setup.d/60-network-devices.sh:
> ---8<---
> if [ ! -z "$DHCLIENT_BIN" -o ! -z "$DHCLIENT6_BIN" ]; then
>         return
> fi
> ip addr add 192.168.0.1/24 dev bondblan
> ip link set dev bondblan up
> ip addr add 192.168.10.1/24 dev bonddrbd
> ip link set dev bonddrbd up
> ip addr add 10.177.245.5/24 dev bondglan
> ip link set dev bondglan up
> ip addr add 140.4.200.55/16 dev bondhlan
> ip link set dev bondhlan up
> ip link set dev eth0 up
> ip link set dev eth1 up
> ip link set dev eth2 up
> ip link set dev eth3 up
> ip link set dev eth4 up
> ip link set dev eth5 up
> ip link set dev eth6 up
> ip link set dev eth9 up
> modprobe bonding max_bonds=4 miimon=100 mode=1 use_carrier=0
> ip link set dev bondblan up
> ifenslave bondblan eth9 eth1
> sleep 5
> ip addr add 192.168.0.1/24 dev bondblan
> ip link set dev bonddrbd up
> ifenslave bonddrbd eth0 eth2
> sleep 5
> ip addr add 192.168.10.1/24 dev bonddrbd
> ip link set dev bondglan up
> ifenslave bondglan eth3 eth5
> sleep 5
> ip addr add 10.177.245.5/24 dev bondglan
> ip link set dev bondhlan up
> ifenslave bondhlan eth4 eth6
> sleep 5
> ip addr add 140.4.200.55/16 dev bondhla
> --->8---
> seems to be ok.
> But I still have no network to start recovery. Is this known and maybe
> someone got this to work properly?
> Has anyone any idea what went wrong?
>
>
> Regards Philipp
>
> --
> Philipp Westphal
> Linux/Unix Consultant
> Tel.: +49-(0)160-90512791
> Mail: westphal at b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> _______________________________________________
> rear-users mailing list
> rear-users at lists.relax-and-recover.org
> http://pikachu.3ti.be/mailman/listinfo/rear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pikachu.3ti.be/pipermail/rear-users/attachments/20120703/43af2986/attachment.html 


More information about the rear-users mailing list