|
Description
|
When IPMP fails over to another interface, it brings down the IPv6 link local address. When IPMP fails back, it doesn't bring the IPv6 link local address up.
Test case:
----------
[root@v4u-60l-blr03]:/space/katla#ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 129.158.233.106 netmask ffffff00 broadcast 129.158.233.255
ether 8:0:20:cf:32:80
qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.158.20.10 netmask ffffff00 broadcast 192.158.20.255
groupname test1
ether 8:0:20:8e:e1:8c
qfe0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 3
inet 192.158.20.11 netmask ffffff00 broadcast 192.158.20.255
qfe1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 192.158.20.20 netmask ffffff00 broadcast 192.158.20.255
groupname test1
ether 8:0:20:8e:e1:8d
qfe1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4
inet 192.158.20.21 netmask ffffff00 broadcast 192.158.20.255
qfe0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 3
inet6 fe80::a00:20ff:fe8e:e18c/10
groupname test1
ether 8:0:20:8e:e1:8c
qfe0:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 3
inet6 20a1:5a0:826:804::1/64
qfe1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 4
inet6 fe80::a00:20ff:fe8e:e18d/10
groupname test1
ether 8:0:20:8e:e1:8d
qfe1:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 4
inet6 20a1:5a0:826:804::2/64
[root@v4u-60l-blr03]:/space/katla#if_mpadm -d qfe0
Mar 28 11:26:04 v4u-60l-blr03 in.mpathd[632]: Successfully failed over from NIC qfe0 to NIC qfe1
[root@v4u-60l-blr03]:/space/katla#ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 129.158.233.106 netmask ffffff00 broadcast 129.158.233.255
ether 8:0:20:cf:32:80
qfe0: flags=89000842<BROADCAST,RUNNING,MULTICAST,IPv4,NOFAILOVER,OFFLINE> mtu 0 index 3
inet 0.0.0.0 netmask 0
groupname test1
ether 8:0:20:8e:e1:8c
qfe0:1: flags=89040842<BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,OFFLINE> mtu 1500 index 3
inet 192.158.20.11 netmask ffffff00 broadcast 192.158.20.255
qfe1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 192.158.20.20 netmask ffffff00 broadcast 192.158.20.255
groupname test1
ether 8:0:20:8e:e1:8d
qfe1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4
inet 192.158.20.21 netmask ffffff00 broadcast 192.158.20.255
qfe1:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 192.158.20.10 netmask ffffff00 broadcast 192.158.20.255
qfe0: flags=82000840<RUNNING,MULTICAST,IPv6,OFFLINE> mtu 1500 index 3
inet6 fe80::a00:20ff:fe8e:e18c/10
groupname test1
ether 8:0:20:8e:e1:8c
qfe1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 4
inet6 fe80::a00:20ff:fe8e:e18d/10
groupname test1
ether 8:0:20:8e:e1:8d
qfe1:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 4
inet6 20a1:5a0:826:804::2/64
qfe1:2: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 4
inet6 20a1:5a0:826:804::1/64
[root@v4u-60l-blr03]:/space/katla#if_mpadm -r qfe0
Mar 28 11:26:19 v4u-60l-blr03 in.mpathd[632]: Successfully failed back to NIC qfe0
[root@v4u-60l-blr03]:/space/katla#ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 129.158.233.106 netmask ffffff00 broadcast 129.158.233.255
ether 8:0:20:cf:32:80
qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.158.20.10 netmask ffffff00 broadcast 192.158.20.255
groupname test1
ether 8:0:20:8e:e1:8c
qfe0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 3
inet 192.158.20.11 netmask ffffff00 broadcast 192.158.20.255
qfe1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 192.158.20.20 netmask ffffff00 broadcast 192.158.20.255
groupname test1
ether 8:0:20:8e:e1:8d
qfe1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4
inet 192.158.20.21 netmask ffffff00 broadcast 192.158.20.255
qfe0: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 3 <<< NOT UP <<<
inet6 fe80::a00:20ff:fe8e:e18c/10
groupname test1
ether 8:0:20:8e:e1:8c
qfe0:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 3
inet6 20a1:5a0:826:804::1/64
qfe1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 4
inet6 fe80::a00:20ff:fe8e:e18d/10
groupname test1
ether 8:0:20:8e:e1:8d
qfe1:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 4
inet6 20a1:5a0:826:804::2/64
xxxxx@xxxxx.com 2005-03-28 06:17:08 GMT
If IFF_NOFAILOVER is set to the link local address, this issue will not happen.
And also, it will not happen in normal link failover/failback.
This happen only with the if_mpadm.
if_mpadm offlines (sets IFF_OFFLINE flags) and clears the IFF_UP flags to all the interfaces.
So, actual synopsis should be "if_mpadm -r <interface> doesn't bring up IPv6 link local address, if IFF_NOFAILOVER is not set to the link local interface".
Updated synopsis to address Ramesh's observation above.
|