OpenSolaris

Printable Version Enter a New Search
Bug ID 6359536
Synopsis enabling STANDBY on an interface with no test address acts oddly
State 10-Fix Delivered (Fix available in build)
Category:Subcategory network:ipmp
Keywords BOP | clearview
Responsible Engineer Peter Memishian
Reported Against
Duplicate Of
Introduced In solaris_10
Commit to Fix snv_107
Fixed In snv_107
Release Fixed solaris_nevada(snv_107)
Related Bugs 6740826 , 6783149 , 6818569 , 4840370
Submit Date 6-December-2005
Last Update Date 15-January-2010
Description 
When using hostname.qfe(x)
qfe0:
192.168.1.100 netmask 255.255.255.0 broadcast + group test up
qfe1:
standby group test up

Then reboot...it will create.
qfe0
qfe0:1
qfe1
This can be reproduced in Solaris10.
   1.modify files
 filename: hostname.qfe0
     add: 192.168.1.100 netmask 255.255.255.0 broadcast + group test up
 filename: hostname.qfe1
     add : standby group test up
   2.reboot
   3.After reboot,run ifconfig -a
-----------------------------------------------------------------------
  qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 192.168.1.100 netmask ffffff00 broadcast 192.168.1.255
        groupname test
        ether 8:0:20:b8:27:38
qfe0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
qfe1: flags=69000842<BROADCAST,RUNNING,MULTICAST,IPv4,NOFAILOVER,STANDBY,INACTIVE> mtu 0 index 4
        inet 0.0.0.0 netmask 0
        groupname test
        ether 8:0:20:b8:27:39
-----------------------------------------------------------------------
  qfe0:1 is up.

The issue also was found when used ge and hme NIC
-----------------------------------------------------------------------
ge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.1.105 netmask ffffff00 broadcast 192.168.1.255
        groupname test
        ether 8:0:20:b2:23:78
ge0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
hme0: flags=69000842<BROADCAST,RUNNING,MULTICAST,IPv4,NOFAILOVER,
                                   STANDBY,INACTIVE> mtu 0 index 3
        inet 0.0.0.0 netmask 0
        groupname test
        ether 8:0:20:c4:99:68
 -----------------------------------------------------------------------
Although the issue happen,it will NOT influence system.
Because all code relation to this issue will be gone after 
the IPMP Rearchitecture is complete.It might be best for
us just to leave it.
Work Around 
no
unplumb logical interface or FAILBACK=no
Kill in.mpathd and allow SMF to restart it.
Except for Sun Cluster, SMF does not manage in.mpathd yet.
Comments 
This was introduced as part of 4840370; setting "Introduced in Release"
and "Introduced in Build" accordingly.