IPMP in Solaris
#1
Scooby Regular
Thread Starter
Join Date: Mar 2001
Location: Berkshire
Posts: 5,528
Likes: 0
Received 0 Likes
on
0 Posts
Anyone got any good web links or info on configuring IPMP in Solaris 8/9 ?
Have used google but was wondering if there is any more out there.
Dave
Have used google but was wondering if there is any more out there.
Dave
#2
Scooby Regular
Join Date: Oct 2000
Location: Surrey, UK
Posts: 8,384
Likes: 0
Received 0 Likes
on
0 Posts
Does this one help?
FAQ ID Synopsis Date
3212 What are IP Network Multipathing failover and failback? 17 Nov 2000
Description Top
What are IP Network Multipathing failover and failback?
How can we configure and how can we confirm if it is working or not?
NOTE: IP Network Multipathing has been available since Solaris 8 10/00.Solution Summary Top
- What is IP Networking Multipathing Failure Detection (failover)?
Ability to detect when a network adaptor has failed and automatically
switching (failover) the network access to an alternate network.
- What is IP Networking Multipathing Repair Detection (failback)?
Ability to detect when a network adaptor that failed preciously has
been repaired and automatically switching back (failback) the network
access to an alternate network adaptor.
- How can we configure?
There are two ways. One is command line configuration and the other
is using hostname file.
(a) command line
ifconfig <interface1> group <group-name>
ifconfig <interface2> group <group-name>
ifconfig <interface1> addif <test-ip-addr-1> -failover deprecated up
ifconfig <interface2> addif <test-ip-addr-2> -failover deprecated up
(b) hostname file
[/etc/hostname.<interface1>]
<ip-address1> group <group-name> up \
addif <ip-address1-1> -failover deprecated up
[/etc/hostname.<interface2>]
<ip-address2> group <group-name> up \
addif <ip-address2-1> -failover deprecated up
- How can we confirm it it is working or not?
(1) decide IP address and the interface name
Suppose the following IP address assignment.
le0 129.158.70.34, le0:1 129.158.70.82
le1 129.158.70.81, le1:1 129.158.70.83
Suppose the group name is "multipath-test".
(2) configure IP multipathing
# ifconfig le0 group multipath-test
# ifconfig le1 group multipath-test
# ifconfig le0 addif 129.158.70.82 -failover deprecated up
# ifconfig le1 addif 129.158.70.83 -failover deprecated up
(3) confirm the configuration validity
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv 4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
le0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IP v4> mtu 1500 index 2
inet 129.158.70.34 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 2
inet 129.158.70.82 netmask ffff0000 broadcast 129.158.255.255
le1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IP v4> mtu 1500 index 3
inet 129.158.70.81 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
inet 129.158.70.83 netmask ffff0000 broadcast 129.158.255.255
(4) create a session
Create telnet session to another host.
(5) see the physical interface utilization
We can confirm only le0 is used from the netstat output.
# netstat -ran | grep UHA
129.158.118.65 -- UHA 3 446 le0
:
:
(6) disable le0
When the network adaptor le0 is out of order, the output of ifconfig
changes as follows. "FAILED" is shown in le0. And le1:2 is replacing
it. It can be enabled by pulling out the network cable.
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv 4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
le0: flags=19000842<BROADCAST,RUNNING,MULTICAST,IPv4 ,NOFAILOVER,FAILED>
mtu 0 index 2
inet 0.0.0.0 netmask 0
groupname multipath-test
ether 8:0:20:1c:0:4f
le0:1: flags=19040843<UP,BROADCAST,RUNNING,MULTICAST,D EPRECATED,IPv4,
NOFAILOVER,FAILED> mtu 1500 index 2
inet 129.158.70.82 netmask ffff0000 broadcast 129.158.255.255
le1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
inet 129.158.70.81 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
inet 129.158.70.83 netmask ffff0000 broadcast 129.158.255.255
le1:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IP v4> mtu 1500 index 3
inet 129.158.70.34 netmask ffffff00 broadcast 129.158.70.255
The connection with another host can be maintained by switching to
le1 interface. Actually the communication with another host works.
# netstat -ran | grep UHA
129.158.118.65 -- UHA 2 26 le1
:
:
This is the failover.
(7) repair le0
When the le0 adaptor is repaired, le0 interface works again as follows.
It can be enabled by connecting the network cable again.
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv 4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
le0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IP v4> mtu 1500 index 2
inet 129.158.70.34 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 2
inet 129.158.70.82 netmask ffff0000 broadcast 129.158.255.255
le1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
inet 129.158.70.81 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
This is the failback.Date Approved 11/17/00
FAQ ID Synopsis Date
3212 What are IP Network Multipathing failover and failback? 17 Nov 2000
Description Top
What are IP Network Multipathing failover and failback?
How can we configure and how can we confirm if it is working or not?
NOTE: IP Network Multipathing has been available since Solaris 8 10/00.Solution Summary Top
- What is IP Networking Multipathing Failure Detection (failover)?
Ability to detect when a network adaptor has failed and automatically
switching (failover) the network access to an alternate network.
- What is IP Networking Multipathing Repair Detection (failback)?
Ability to detect when a network adaptor that failed preciously has
been repaired and automatically switching back (failback) the network
access to an alternate network adaptor.
- How can we configure?
There are two ways. One is command line configuration and the other
is using hostname file.
(a) command line
ifconfig <interface1> group <group-name>
ifconfig <interface2> group <group-name>
ifconfig <interface1> addif <test-ip-addr-1> -failover deprecated up
ifconfig <interface2> addif <test-ip-addr-2> -failover deprecated up
(b) hostname file
[/etc/hostname.<interface1>]
<ip-address1> group <group-name> up \
addif <ip-address1-1> -failover deprecated up
[/etc/hostname.<interface2>]
<ip-address2> group <group-name> up \
addif <ip-address2-1> -failover deprecated up
- How can we confirm it it is working or not?
(1) decide IP address and the interface name
Suppose the following IP address assignment.
le0 129.158.70.34, le0:1 129.158.70.82
le1 129.158.70.81, le1:1 129.158.70.83
Suppose the group name is "multipath-test".
(2) configure IP multipathing
# ifconfig le0 group multipath-test
# ifconfig le1 group multipath-test
# ifconfig le0 addif 129.158.70.82 -failover deprecated up
# ifconfig le1 addif 129.158.70.83 -failover deprecated up
(3) confirm the configuration validity
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv 4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
le0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IP v4> mtu 1500 index 2
inet 129.158.70.34 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 2
inet 129.158.70.82 netmask ffff0000 broadcast 129.158.255.255
le1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IP v4> mtu 1500 index 3
inet 129.158.70.81 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
inet 129.158.70.83 netmask ffff0000 broadcast 129.158.255.255
(4) create a session
Create telnet session to another host.
(5) see the physical interface utilization
We can confirm only le0 is used from the netstat output.
# netstat -ran | grep UHA
129.158.118.65 -- UHA 3 446 le0
:
:
(6) disable le0
When the network adaptor le0 is out of order, the output of ifconfig
changes as follows. "FAILED" is shown in le0. And le1:2 is replacing
it. It can be enabled by pulling out the network cable.
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv 4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
le0: flags=19000842<BROADCAST,RUNNING,MULTICAST,IPv4 ,NOFAILOVER,FAILED>
mtu 0 index 2
inet 0.0.0.0 netmask 0
groupname multipath-test
ether 8:0:20:1c:0:4f
le0:1: flags=19040843<UP,BROADCAST,RUNNING,MULTICAST,D EPRECATED,IPv4,
NOFAILOVER,FAILED> mtu 1500 index 2
inet 129.158.70.82 netmask ffff0000 broadcast 129.158.255.255
le1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
inet 129.158.70.81 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
inet 129.158.70.83 netmask ffff0000 broadcast 129.158.255.255
le1:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IP v4> mtu 1500 index 3
inet 129.158.70.34 netmask ffffff00 broadcast 129.158.70.255
The connection with another host can be maintained by switching to
le1 interface. Actually the communication with another host works.
# netstat -ran | grep UHA
129.158.118.65 -- UHA 2 26 le1
:
:
This is the failover.
(7) repair le0
When the le0 adaptor is repaired, le0 interface works again as follows.
It can be enabled by connecting the network cable again.
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv 4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
le0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IP v4> mtu 1500 index 2
inet 129.158.70.34 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 2
inet 129.158.70.82 netmask ffff0000 broadcast 129.158.255.255
le1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
inet 129.158.70.81 netmask ffffff00 broadcast 129.158.70.255
groupname multipath-test
ether 8:0:20:1c:0:4f
le1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DE PRECATED,IPv4,
NOFAILOVER> mtu 1500 index 3
This is the failback.Date Approved 11/17/00
#4
Scooby Regular
Thread Starter
Join Date: Mar 2001
Location: Berkshire
Posts: 5,528
Likes: 0
Received 0 Likes
on
0 Posts
Thanks Alex, currently helping to set up a bucket load of Primepowers in Germany and that has really helped.
Must find my Sunsolve password.......
Must find my Sunsolve password.......
#6
Primepowers.
Germany.
When are you gonna come over to the light from the dark side
I'm in dusseldorf at the moment upgrading 6800's... at 7:45 pm.
By myself.
In a server room.
with only a laptop to surf with
Germany.
When are you gonna come over to the light from the dark side
I'm in dusseldorf at the moment upgrading 6800's... at 7:45 pm.
By myself.
In a server room.
with only a laptop to surf with
#7
Scooby Regular
Thread Starter
Join Date: Mar 2001
Location: Berkshire
Posts: 5,528
Likes: 0
Received 0 Likes
on
0 Posts
Lol dave - i am with a big UK tv company that has kicked out the other type of Solaris systems and bought Primepower
Server room, laptop, Scoobynet. What more do I need !!!
Dave
Server room, laptop, Scoobynet. What more do I need !!!
Dave
Trending Topics
#8
Scooby Regular
Join Date: Oct 2000
Location: Surrey, UK
Posts: 8,384
Likes: 0
Received 0 Likes
on
0 Posts
Which one do you want??
http://sunsolve.sun.co.uk/
FAQs: 1..3 (of 3 ):
1. When will any changes to /etc/default/mpathd be effective?
FAQs: 3222 100%
6 Dec 2000
2. What are IP Network Multipathing failover and failback?
FAQs: 3212 50%
17 Nov 2000
3. Differences between Trunking and Interface group
FAQs: 3428 50%
11 Apr 2001
Return to Top
Info Docs: 1..7 (of 7 ):
1. IPMP: Configuring ipmp to use multiple testpartners in a 'defaultrouter' environment
Info Docs: 43720 100%
24 Jan 2003
2. How to set up IPMP without a defaultrouter.
Info Docs: 41422 40%
3 Feb 2003
3. IPMP: Using IPMP to failover virtual interfaces
Info Docs: 46165 26%
27 Jan 2003
4. Sun[TM] ONE Grid Engine: Installing in machines with IPMP turned on
Info Docs: 48530 20%
7 Nov 2002
5. IPMP: How to change the Failure detection Time in IP Multipathing
Info Docs: 28165 6%
28 Jan 2003
6. Ethernet: What methods are there to to determine link status of ethernet interfaces?
Info Docs: 47729 6%
29 Jan 2003
7. Patch Club Report: Week Ending 1/17/2003
Info Docs: 50165 6%
4 Feb 2003
Return to Top
Symptoms and Resolutions: 1..2 (of 2 ):
1. IPMP: in.mpathd cannot meet the requested failure detection time
Symptoms and Resolutions: 41553 100%
28 Jan 2003
2. Packet Loss Issue
Symptoms and Resolutions: 44583 66%
17 Jul 2002
Let me know mate.
[Edited by DrEvil - 2/11/2003 11:31:24 AM]
http://sunsolve.sun.co.uk/
FAQs: 1..3 (of 3 ):
1. When will any changes to /etc/default/mpathd be effective?
FAQs: 3222 100%
6 Dec 2000
2. What are IP Network Multipathing failover and failback?
FAQs: 3212 50%
17 Nov 2000
3. Differences between Trunking and Interface group
FAQs: 3428 50%
11 Apr 2001
Return to Top
Info Docs: 1..7 (of 7 ):
1. IPMP: Configuring ipmp to use multiple testpartners in a 'defaultrouter' environment
Info Docs: 43720 100%
24 Jan 2003
2. How to set up IPMP without a defaultrouter.
Info Docs: 41422 40%
3 Feb 2003
3. IPMP: Using IPMP to failover virtual interfaces
Info Docs: 46165 26%
27 Jan 2003
4. Sun[TM] ONE Grid Engine: Installing in machines with IPMP turned on
Info Docs: 48530 20%
7 Nov 2002
5. IPMP: How to change the Failure detection Time in IP Multipathing
Info Docs: 28165 6%
28 Jan 2003
6. Ethernet: What methods are there to to determine link status of ethernet interfaces?
Info Docs: 47729 6%
29 Jan 2003
7. Patch Club Report: Week Ending 1/17/2003
Info Docs: 50165 6%
4 Feb 2003
Return to Top
Symptoms and Resolutions: 1..2 (of 2 ):
1. IPMP: in.mpathd cannot meet the requested failure detection time
Symptoms and Resolutions: 41553 100%
28 Jan 2003
2. Packet Loss Issue
Symptoms and Resolutions: 44583 66%
17 Jul 2002
Let me know mate.
[Edited by DrEvil - 2/11/2003 11:31:24 AM]
Thread
Thread Starter
Forum
Replies
Last Post
DrEvil
Computer & Technology Related
9
13 January 2004 10:36 AM