Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

solaris 10 ipmp problem

797449Oct 14 2008 — edited Aug 26 2009
Hi,

I am facing a problem with ipmp on solaris 10 machine,
below are the interface configuration files and the ifconfig output after link failure on e1000g0 interface.
The ip on e1000g0 doesn't failover to e1000g1 ("as should be"). I am able to ping the faild interface ip and the test ip from within the server itself by login to the server by the ip on e1000g1 interface. ("not pinging from other machines on the subnet). Kindly help me in resolving the problem

#more /etc/hostname.e1000g0
t2000 netmask + broadcast + group prim_grp up \
addif t2000test netmask + broadcast + -failover deprecated up

# more /etc/hostname.e1000g1
t2000-g1 netmask + broadcast + group prim_grp up \
addif t2000test-g1 netmask + broadcast + -failover deprecated up

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=11000803<UP,BROADCAST,MULTICAST,IPv4,FAILED> mtu 1500 index 2
inet 10.0.1.32 netmask ffffff00 broadcast 10.0.1.255
groupname prim_grp
ether 0:14:4f:af:b3:2e
e1000g0:1: flags=19040803<UP,BROADCAST,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,FAILED> mtu 1500 index 2
inet 192.168.3.1 netmask ffffff00 broadcast 192.168.3.255
e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.0.1.33 netmask ffffff00 broadcast 10.0.1.255
groupname prim_grp
ether 0:14:4f:af:b3:2f
e1000g1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 3
inet 192.168.3.2 netmask ffffff00 broadcast 192.168.3.255
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 23 2009
Added on Oct 14 2008
6 comments
969 views