unplumbing the active physical int with IPMP

unplumbing the active physical int with IPMP

Post by linux_b » Sat, 06 May 2006 16:28:42



In a multipathing group
I have the scenario ACTIVE-STANDBY where bge1 is active and bge2 is
standy.
I we pull the network cable out of the bge1 than the failover takes
place and bge2 will become active.
But if I unplumb the physical interface bge1 than the failover do not
take place and bge1 dissapperas with all the data ips and test ip.
Is this the right behaviour? I think in this case too the failover
should take place. if yes, what configuration changes we need to make.

NOrmal Output of ifconfig -a is
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index
2
inet 192.168.9.192 netmask ffffff00 broadcast 192.168.9.255
groupname gr_401_9
ether 0:3:ba:47:fc:17
bge0:1:
flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER>
mtu 1500 index 2
inet 192.168.9.57 netmask ffffff00 broadcast 192.168.9.255
bge0:50: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 2
inet 192.168.9.211 netmask ffffff00 broadcast 192.168.9.255
bge1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index
3
inet 192.168.8.168 netmask ffffff00 broadcast 192.168.8.255
groupname gr_401_8
ether 0:3:ba:47:fc:18
bge1:1:
flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER>
mtu 1500 index 3
inet 192.168.8.131 netmask ffffff00 broadcast 192.168.8.255
bge1:50: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 3
inet 192.168.8.186 netmask ffffff00 broadcast 192.168.8.255
bge1:51: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 3
inet 192.168.8.185 netmask ffffff00 broadcast 192.168.8.255
bge2:
flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STA
NDBY,INACTIVE> mtu 1500 index 4
inet 192.168.8.133 netmask ffffff00 broadcast 192.168.8.255
groupname gr_401_8
ether 0:3:ba:47:fc:19
bge3:
flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STA
NDBY,INACTIVE> mtu 1500 index 5
inet 192.168.9.96 netmask ffffff00 broadcast 192.168.9.255
groupname gr_401_9
ether 0:3:ba:47:fc:1a

 
 
 

unplumbing the active physical int with IPMP

Post by Rowle » Sat, 06 May 2006 18:03:06


http://opensolaris.org/os/community/networking/ipmp-highlevel-design.pdf

"Like any other interface, the unplumb keyword will cause an IPMP group
interface to be destroyed. However, destruction will only be possible
if there are no physical interfaces currently part of the relevant IPMP
group" For instance:

# ifconfig ipmp1 ipmp group b
# ifconfig ce0 group b
# ifconfig ipmp1 unplumb
ifconfig: ipmp1: cannot unplumb: interface busy
# ifconfig ce0 group ""
# ifconfig ipmp1 unplumb
As with a traditional physical interface, any IP addresses associated
with the IPMP interface will be removed from the system as part of the
unplumb operation.

hth.

 
 
 

unplumbing the active physical int with IPMP

Post by linux_b » Sat, 06 May 2006 18:33:38


Thanks for replying.. but my concern is to unplumb the physical
interface in an ipmp group.
bge1 and bge2 are in IPMP group gr_401_8 with bge1 active and bge2 at
standby.
if i give
#ifconfig bge1 unplumb
then it will unplumb the bge1 but failover do not take place on bge2.
 
 
 

unplumbing the active physical int with IPMP

Post by Darren Dunha » Sun, 07 May 2006 02:44:58



> Thanks for replying.. but my concern is to unplumb the physical
> interface in an ipmp group.
> bge1 and bge2 are in IPMP group gr_401_8 with bge1 active and bge2 at
> standby.
> if i give
> #ifconfig bge1 unplumb
> then it will unplumb the bge1 but failover do not take place on bge2.

Can I ask what you're trying to accomplish here?  Why do you need to
retain the IPMP configuration when you're trying to unplumb underneath
it?

Why are you unplumbing the interface?

--

Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

 
 
 

unplumbing the active physical int with IPMP

Post by linux_b » Sun, 07 May 2006 11:38:16


Thanks for replying.
I want to know that if we bring down interface in IPMP group
administratively, by turning down the active interface using "ifconfig
bge1 down" or unplumb it using "ifconfig bge1 unplumb", then should it
get migrated to standby?
 
 
 

unplumbing the active physical int with IPMP

Post by Darren Dunha » Sun, 07 May 2006 13:03:07



> Thanks for replying.
> I want to know that if we bring down interface in IPMP group
> administratively, by turning down the active interface using "ifconfig
> bge1 down" or unplumb it using "ifconfig bge1 unplumb", then should it
> get migrated to standby?

I don't see anything in the documentation that suggests that it should.
IPMP is trying to correct for hardware failures, not administrative
changes.

--

Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

 
 
 

1. extern void (*signal(int, void (*)(int)))(int);

Subject says it all.  Can anyone explain this
prototype, piece by piece, to me?

        extern void (*signal(int, void (*)(int)))(int);

I can and do use the signal() function frequently,
but I have no idea why the compiler likes me to cast
pointers to functions as so strangely.  A successful
cal looks like:

        signal(SIGCHLD, (void(*)(int))reaper);

Although it only warns me if I don't cast it,
I'd still like to understand what all that mess
in the prototpe means.

Thanks.

-----------------+----------------------------------------
  John Siracusa  | If you only have a hammer, you tend to

2. miro pnp media online

3. int connect(int sockfd, struct sockaddr *serv_addr, int addrlen )???

4. Please recommend a PCI video card that can do 1280*1024@85Hz

5. Is there a function like muldiv(int,int,int)?

6. Invisible GPIB-ENET packets? Sniffers don't sniff!

7. Converting from unsigned int to int in C++ / More info

8. How to disaable printer....???

9. urgent: int (int argc, char argv[]) problem

10. I loose int tell(int fd) C function with new glibc !!!

11. urgent: int (int argc, char argv[]) problem

12. Problem with the "int modify_ldt(int, void *, unsigned long)" function.

13. How to use int mount() and int umount() ???