1.Link Based IPMP

Request:

Configure IP address “192.168.2.50” on e1000g1 & e1000g2 using Link based IPMP.

Step:1

Find out the installed NIC’s on the systems and its status.Verify the ifconfig output as well.
Make sure the NIC status are up and not in use.
Arena-Node1#dladm show-dev
e1000g0         link: up        speed: 1000  Mbps       duplex: full
e1000g1         link: up        speed: 1000  Mbps       duplex: full
e1000g2         link: up        speed: 1000  Mbps       duplex: full
Arena-Node1#ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843 mtu 1500 index 2
inet 192.168.2.5 netmask ffffff00 broadcast 192.168.2.255
ether 0:c:29:ec:b3:af
Arena-Node1#

Step:2
Add the IP address in /etc/hosts and specify the netmask value in /etc/netmasks like below one.
Arena-Node1#cat /etc/hosts |grep 192.168.2.50
192.168.2.50    arenagroupIP
Arena-Node1#cat /etc/netmasks |grep 192.168.2
192.168.2.0     255.255.255.0
Arena-Node1#eeprom "local-mac-address?=true"

Step:3
Plumb the interfaces which you are going to use for new IP address. check the status in “ifconfig” output.
Arena-Node1#ifconfig e1000g1 plumb
Arena-Node1#ifconfig e1000g2 plumb
Arena-Node1#ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843 mtu 1500 index 2
inet 192.168.2.5 netmask ffffff00 broadcast 192.168.2.255
ether 0:c:29:ec:b3:af
e1000g1: flags=1000842 mtu 1500 index 3
inet 0.0.0.0 netmask 0
ether 0:c:29:ec:b3:b9
e1000g2: flags=1000842 mtu 1500 index 4
inet 0.0.0.0 netmask 0
ether 0:c:29:ec:b3:c3

Step:4
Configure IP on Primary interface and add the interfaces to IPMP group with your own group name.
Arena-Node1#ifconfig e1000g1 192.168.2.50 netmask 255.255.255.0 broadcast + up
Arena-Node1#ifconfig e1000g1
e1000g1: flags=1000843 mtu 1500 index 3
inet 192.168.2.50 netmask ffffff00 broadcast 192.168.2.255
ether 0:c:29:ec:b3:b9
Arena-Node1#ifconfig e1000g1 group arenagroup-1
Arena-Node1#ifconfig e1000g2 group arenagroup-1
Arena-Node1#ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843 mtu 1500 index 2
inet 192.168.2.5 netmask ffffff00 broadcast 192.168.2.255
ether 0:c:29:ec:b3:af
e1000g1: flags=1000843 mtu 1500 index 3
inet 192.168.2.50 netmask ffffff00 broadcast 192.168.2.255
groupname arenagroup-1
ether 0:c:29:ec:b3:b9
e1000g2: flags=1000842 mtu 1500 index 4
inet 0.0.0.0 netmask 0
groupname arenagroup-1
ether 0:c:29:ec:b3:c3

----------------------------

Step:5
Now we have to ensure IPMP is working fine.This can be done in two ways.

i.Test:1 Remove the primary LAN cable and check it.Here i have removed the LAN cable from e1000g1 and let see what happens.
Arena-Node1#ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843 mtu 1500 index 2
inet 192.168.2.5 netmask ffffff00 broadcast 192.168.2.255
ether 0:c:29:ec:b3:af
e1000g1: flags=19000802 mtu 0 index 3
inet 0.0.0.0 netmask 0
groupname arenagroup-1
ether 0:c:29:ec:b3:b9
e1000g2: flags=1000842 mtu 1500 index 4
inet 0.0.0.0 netmask 0
groupname arenagroup-1
ether 0:c:29:ec:b3:c3
e1000g2:1: flags=1000843 mtu 1500 index 4
inet 192.168.2.50 netmask ffffff00 broadcast 192.168.2.255

Again i have connected back  the LAN cable to e1000g1.
Arena-Node1#dladm show-dev
e1000g0         link: up        speed: 1000  Mbps       duplex: full
e1000g1         link: up        speed: 1000  Mbps       duplex: full
e1000g2         link: up        speed: 1000  Mbps       duplex: full
Arena-Node1#ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843 mtu 1500 index 2
inet 192.168.2.5 netmask ffffff00 broadcast 192.168.2.255
ether 0:c:29:ec:b3:af
e1000g1: flags=1000843 mtu 1500 index 3
inet 192.168.2.50 netmask ffffff00 broadcast 192.168.2.255
groupname arenagroup-1
ether 0:c:29:ec:b3:b9
e1000g2: flags=1000842 mtu 1500 index 4
inet 0.0.0.0 netmask 0
groupname arenagroup-1
ether 0:c:29:ec:b3:c3

Here the configured IP is going back to original interface where it was running before. Here I had specified “FALLBACK=yes” . That’s why IP is moving back to original interface.The same way you can also specify failure detection time to mpathd  using parameter “FAILURE_DETECTION_TIME” in ms.
Arena-Node1#cat /etc/default/mpathd |grep -v "#"
FAILURE_DETECTION_TIME=10000
FAILBACK=yes
TRACK_INTERFACES_ONLY_WITH_GROUPS=yes
Arena-Node1#

ii.Test:2 Normally most of the Unix admins will be sitting in remote site. So you will be not able to perform the above test.In this case ,you can use “if_mpadm” command to disable the interface in OS level.
Fist i am going to disable e1000g1 and let see what happens.
Arena-Node1#if_mpadm -d e1000g1
Arena-Node1#ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843 mtu 1500 index 2
inet 192.168.2.5 netmask ffffff00 broadcast 192.168.2.255
ether 0:c:29:ec:b3:af
e1000g1: flags=89000842 mtu 0 index 3
inet 0.0.0.0 netmask 0
groupname arenagroup-1
ether 0:c:29:ec:b3:b9
e1000g2: flags=1000842 mtu 1500 index 4
inet 0.0.0.0 netmask 0
groupname arenagroup-1
ether 0:c:29:ec:b3:c3
e1000g2:1: flags=1000843 mtu 1500 index 4
inet 192.168.2.50 netmask ffffff00 broadcast 192.168.2.255

Now i am going to enable it back.
Arena-Node1#if_mpadm -r e1000g1
Arena-Node1#ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843 mtu 1500 index 2
inet 192.168.2.5 netmask ffffff00 broadcast 192.168.2.255
ether 0:c:29:ec:b3:af
e1000g1: flags=1000843 mtu 1500 index 3
inet 192.168.2.50 netmask ffffff00 broadcast 192.168.2.255
groupname arenagroup-1
ether 0:c:29:ec:b3:b9
e1000g2: flags=1000842 mtu 1500 index 4
inet 0.0.0.0 netmask 0
groupname arenagroup-1
ether 0:c:29:ec:b3:c3

The same way you can manually failover the IP to one interface to another interface.

In the both tests,we can clearly see IP is moving from e1000g1 to e1000g2 automatically without any issues.So we have successfully configured Link based IPMP on Solaris.
These failover logs will be logged in /var/adm/messages like below.
Jun 26 20:57:24 node1 in.mpathd[3800]: [ID 215189 daemon.error] The link has gone down on e1000g1
Jun 26 20:57:24 node1 in.mpathd[3800]: [ID 594170 daemon.error] NIC failure detected on e1000g1 of group arenagroup-1
Jun 26 20:57:24 node1 in.mpathd[3800]: [ID 832587 daemon.error] Successfully failed over from NIC e1000g1 to NIC e1000g2
Jun 26 20:57:57 node1 in.mpathd[3800]: [ID 820239 daemon.error] The link has come up on e1000g1
Jun 26 20:57:57 node1 in.mpathd[3800]: [ID 299542 daemon.error] NIC repair detected on e1000g1 of group arenagroup-1
Jun 26 20:57:57 node1 in.mpathd[3800]: [ID 620804 daemon.error] Successfully failed back to NIC e1000g1
Jun 26 21:03:59 node1 in.mpathd[3800]: [ID 832587 daemon.error] Successfully failed over from NIC e1000g1 to NIC e1000g2
Jun 26 21:04:07 node1 in.mpathd[3800]: [ID 620804 daemon.error] Successfully failed back to NIC e1000g1

To make the above work persistent across the reboot create the configuration files for both the network interfaces.
Arena-Node1#cat /etc/hostname.e1000g1
arenagroupIP netmask + broadcast + group arenagroup up
Arena-Node1#cat /etc/hostname.e1000g2
group arenagroup up

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/31401608/viewspace-2150235/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/31401608/viewspace-2150235/

Solaris 10 Configure IPMP相关推荐

  1. solaris 10 ipmp

    Solaris 10 IPMP配置(案例一) 前提: 1).所有IP在一个网段(VLAN)内,同网段内有其他设备(router或者主机). 2).两块网卡能提供同样的工作模式 3).Solaris 8 ...

  2. solaris php,在Solaris 10 64位上配置PHP

    我们目前在Solaris 10服务器上运行 PHP 5.2.13.我需要启用一些额外的功能,所以我去运行配置脚本,但我遇到了一些错误. 我做了'export CFLAGS =" – m64& ...

  3. 日记 [2007年09月22日]solaris 10 挑战

    Linux还没玩转呢,就想来挑战solaris 10了,哈哈,9.3号下载了iso,一共5个文件,然后在虚拟机里面安装,老规矩,虚拟机里面安装过很多次操作系统了.呀,怎么半天都不动,是不是我下的ISO ...

  4. Solaris 10 学习笔记

    {转}Solaris 10 学习笔记 Solaris 10 安装并运行Solarids 10的硬件环境 1．           SPARC平台 2．           X86平台 3．       ...

  5. sun服务器删除多余文件,Sun服务器（基于Solaris 10）日常应用基本处理的一些实例...

    原稿增加了存储和磁带机的相关内容,但给朋友误删了,在郁闷中--  哎-- 本文档知识来源于网络.个人经验等 大家也可以添加进来 在不断更新中 1.31更新 SUN FIRE 系列........... ...

  6. Solaris 10 系统维护

    作者:田逸([email]sery@163.com[/email]) 相信很多人和我有类似的想法:要是solaris 10安装配置完以后把它扔到某个位置再也不用管它,那该有多好.当然,这只是我们的一厢 ...

  7. ArcSDE 9.1 for Oracle10g on Solaris 10

    作者:Flyingis Unix系统安装方法都基本相同,但是这次走常规路线出现问题,先看看环境. 操作系统:Solaris 10(64bit)     数据库:Oracle 10.2.0.3 RAC ...

  8. Solaris 10网络服务

    作者:田逸(sery@163.com) <开放系统世界> 2006年10期 多年前,sun 微系统公司提出"网络就是计算机"这一著名的口号,从而使得网络的概念逐渐为世人 ...

  9. Solaris 10 x86 上折腾Mono

    这是一个异常折腾的过程,写下来记录下. 从http://www.mono-project.com/的Download里下载了Solaris 10的gz压缩的pkg包. 为了安装pkg包,一开始不知道咋 ...

最新文章

  1. Oracle 11g 错误：ORA-28002： the password will expire within 7 days 解决方法
  2. @EnableDiscoveryClient和@EnableEurekaClient的区别
  3. jQuery防止多次提交
  4. 阿里云存储OSS中设置上传文件content type
  5. NodeJs实现下载Excel文件
  6. MySQL笔记创建表结构_MySQL表结构笔记9
  7. 比较完善的是vmware Fusion和Parallels
  8. 查看Android设备的分辨率
  9. 蓝桥杯题目练习 水题 [蓝桥杯2019初赛]矩形切割
  10. 数学建模三大模型以及十大算法
  11. 【密码学】费马小定理素性检测（C++代码实现）
  12. 第四章第八节数据资产盘点-系统数据梳理
  13. 2023年首家！上海万得征信获企业征信备案公示
  14. 阿里云不同账号实现内网ping通
  15. 腾讯一面：内存满了，会发生什么？
  16. raid读写速度对比_RAID5和RAID1的读写速度对比大概是多少
  17. linux freemodbus tcp,FreeModbus LINUXTCP Compile ERROR
  18. 持续更新:免费的IT学习资源分享
  19. 上海国际快递物流展浅谈快递自动化分拣设备市场“起风了”！
  20. web扫描器之AppScan

热门文章

  1. EasyDarwin开源流媒体服务器内存管理优化
  2. 当下正值网络大电影投资热潮，你该如何参与？VDAX给你支招
  3. Silverlight书籍推荐阅读排行榜【续】
  4. RS485的EMC防雷保护方案
  5. Spring In Action读书笔记
  6. 博士申请 | 香港中文大学（深圳）张瑞茂老师组招收计算机视觉博士/硕士/RA
  7. 那些让人极度舒适的软件，盘点一下数据人必备的黑科技
  8. LED智能照明与健康-光莆电子-张潇
  9. 计算机网络(湖南科技大学)
  10. centos 7.6 ——NFS共享存储服务