Solaris IPMP两种配置方法

最新推荐文章于 2020-06-02 17:00:00 发布
最新推荐文章于 2020-06-02 17:00:00 发布
阅读量373 收藏
点赞数
原文链接：http://www.cnblogs.com/airport/p/7241100.html
版权
Solaris IPMP两种配置方法

更换华为防火墙后，发现Solaris基于ip探测方式配置的IPMP 呈现failed状态。经过分析，更改为基于link的IPMP配置方式后，解决了这次问题。

1、Multiple interface Link based IPMP configuration
a. Active – Active configuration
Command line :


# ifconfig e1000g0 plumb 192.168.1.2 netmask + broadcast + group IPMPgroup up
#
# ifconfig e1000g1 plumb group IPMPgroup up
For persistent configuration across reboots edit the files :
/etc/hostname.e1000g0

192.168.1.2 netmask + broadcast + group IPMPgroup up

/etc/hostname.e1000g1

group IPMPgroup up
Before Failure :
# ifconfig -a

lo0: flags=2001000849[UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL] mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 14

inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255

groupname IPMPgroup

ether 0:c:29:f6:ef:67

e1000g1: flags=1000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 15

inet 0.0.0.0 netmask ff000000

groupname IPMPgroup

ether 0:c:29:f6:ef:71
After Failure
# ifconfig -a

lo0: flags=2001000849[UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL] mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=19000802[BROADCAST,MULTICAST,IPv4,NOFAILOVER,FAILED] mtu 0 index 14

inet 0.0.0.0 netmask 0

groupname IPMPgroup

ether 0:c:29:f6:ef:67

e1000g1: flags=1000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 15

inet 0.0.0.0 netmask ff000000

groupname IPMPgroup

ether 0:c:29:f6:ef:71

e1000g1:1: flags=1000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 15

inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255


b. Active standby Configuration
Command line :

# ifconfig e1000g0 plumb 192.168.1.2 netmask + broadcast + group IPMPgroup up
#
# ifconfig e1000g1 plumb group IPMPgroup standby up
For persistent configuration across reboots edit the files :
/etc/hostname.e1000g0

192.168.1.2 netmask + broadcast + group IPMPgroup up

/etc/hostname.e1000g1

group IPMPgroup standby up
Before failure
# ifconfig -a

lo0: flags=2001000849[UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL] mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 20

inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255

groupname IPMPgroup

ether 0:c:29:f6:ef:67

e1000g0:1: flags=1000842[BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 20

inet 0.0.0.0 netmask 0

e1000g1: flags=69000842[BROADCAST,RUNNING,MULTICAST,IPv4,NOFAILOVER,STANDBY,INACTIVE] mtu 0 index 21

inet 0.0.0.0 netmask 0

groupname IPMPgroup

ether 0:c:29:f6:ef:71
After failure
# ifconfig -a

lo0: flags=2001000849[UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL] mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=19000802[BROADCAST,MULTICAST,IPv4,NOFAILOVER,FAILED] mtu 0 index 20

inet 0.0.0.0 netmask 0

groupname IPMPgroup

ether 0:c:29:f6:ef:67

e1000g1: flags=21000842[BROADCAST,RUNNING,MULTICAST,IPv4,STANDBY] mtu 1500 index 21

inet 0.0.0.0 netmask 0

groupname IPMPgroup

ether 0:c:29:f6:ef:71

e1000g1:1: flags=21000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4,STANDBY] mtu 1500 index 21

inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
2、Most commonly used Probe-Based IPMP configurations
a. Active – Active configuration
Groupname:             ipmp0
Active interface(s):   e1000g0 
                        e1000g1
Standby interface(s):  -
Data IP addresse(s):   192.168.1.2
Test IP addresse(s):   192.168.1.3
                        192.168.1.4
Command line :

# ifconfig e1000g0 plumb 192.168.1.2 netmask + broadcast + group ipmp0 up addif 192.168.1.3 netmask + broadcast + deprecated -failover up
#
# ifconfig e1000g1 plumb 192.168.1.4 netmask + broadcast + deprecated -failover group ipmp0 up


To ensure persistent configuration across reboots edit the files :
/etc/hostname.e1000g0:
192.168.1.2 netmask + broadcast + group ipmp0 up \
addif 192.168.1.3 netmask + broadcast + deprecated -failover up

/
/etc/hostname.e1000g1:

192.168.1.4 netmask + broadcast + deprecated -failover group ipmp0 up
Before failure :
# ifconfig -a

lo0: flags=2001000849[UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL] mtu 8232 index 1
 
        inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 9
 
        inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
 
        groupname ipmp0
 
        ether 0:c:29:f6:ef:67

e1000g0:1: flags=9040843[UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER] mtu 1500 index 9
 
        inet 192.168.1.3 netmask ffffff00 broadcast 192.168.1.255

e1000g1: flags=9040843[UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER] mtu 1500 index 10
 
        inet 192.168.1.4 netmask ffffff00 broadcast 192.168.1.255
 
        groupname ipmp0
 
        ether 0:c:29:f6:ef:71


After failure :
# ifconfig -a

lo0: flags=2001000849[UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL] mtu 8232 index 1
 
        inet 127.0.0.1 netmask ff000000

e1000g0: flags=19000802[BROADCAST,MULTICAST,IPv4,NOFAILOVER,FAILED] mtu 0 index 9
 
        inet 0.0.0.0 netmask 0
 
        groupname ipmp0
 
        ether 0:c:29:f6:ef:67

e1000g0:1: flags=19040803[UP,BROADCAST,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,FAILED] mtu 1500 index 9
 
        inet 192.168.1.3 netmask ffffff00 broadcast 192.168.1.255

e1000g1: flags=9040843[UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER] mtu 1500 index 10
 
        inet 192.168.1.4 netmask ffffff00 broadcast 192.168.1.255
 
        groupname ipmp0
 
        ether 0:c:29:f6:ef:71

e1000g1:1: flags=1000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 10
 
        inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255


2. Active – Standby
The only difference in case of a active-standby configuration is – the interface configured as standby is not used to send any out bound traffic. Thus disabling the load balancing feature of an active-active configuration.
Groupname:             ipmp0
Active interface(s):   e1000g0             
Standby interface(s):  e1000g1
Data IP addresse(s):   192.168.1.2
Test IP addresse(s):   192.168.1.3
                        192.168.1.4
Command line :

# ifconfig e1000g0 plumb 192.168.1.2 netmask + broadcast + group ipmp0 up addif 192.168.1.3 netmask + broadcast + deprecated -failover up
#
# ifconfig e1000g1 plumb 192.168.1.4 netmask + broadcast + deprecated -failover group ipmp0 standby up
To ensure persistent configuration across reboots edit the files :
/etc/hostname.e1000g0:

192.168.1.2 netmask + broadcast + group ipmp0 up \

addif 192.168.1.3 netmask + broadcast + deprecated -failover up

/
/etc/hostname.e1000g1:
192.168.1.4 netmask + broadcast + deprecated -failover group ipmp0 standby up
Before failure :
# ifconfig -a

lo0: flags=2001000849[UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL] mtu 8232 index 1
 
        inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4] mtu 1500 index 11
 
        inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
 
        groupname ipmp0
 
        ether 0:c:29:f6:ef:67

e1000g0:1: flags=9040843[UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER] mtu 1500 index 11
 
        inet 192.168.1.3 netmask ffffff00 broadcast 192.168.1.255

e1000g1: flags=69040843[UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY,INACTIVE] mtu 1500 index 12
 
        inet 192.168.1.4 netmask ffffff00 broadcast 192.168.1.255
 
        groupname ipmp0
 
        ether 0:c:29:f6:ef:71
After failure :
# ifconfig -a

lo0: flags=2001000849[UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL] mtu 8232 index 1
 
        inet 127.0.0.1 netmask ff000000

e1000g0: flags=19000802[BROADCAST,MULTICAST,IPv4,NOFAILOVER,FAILED] mtu 0 index 11
 
        inet 0.0.0.0 netmask 0
 
        groupname ipmp0
 
        ether 0:c:29:f6:ef:67

e1000g0:1: flags=19040803[UP,BROADCAST,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,FAILED] mtu 1500 index 11
 
        inet 192.168.1.3 netmask ffffff00 broadcast 192.168.1.255

e1000g1: flags=29040843[UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY] mtu 1500 index 12
 
        inet 192.168.1.4 netmask ffffff00 broadcast 192.168.1.255
 
        groupname ipmp0
 
        ether 0:c:29:f6:ef:71

e1000g1:1: flags=21000843[UP,BROADCAST,RUNNING,MULTICAST,IPv4,STANDBY] mtu 1500 index 12
 
        inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255

 

posted on 2017-07-26 17:56  #东来# 阅读( ...) 评论( ...) 编辑 收藏

转载于:https://www.cnblogs.com/airport/p/7241100.html

dingmeng3224
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Solaris10下配置IPMP实例
12-02
利用solaris操作系统的IPMP技术，实现双网口互为主备，当主网口故障时，可以将业务通信自动漂移到备用网口上，从而实现主机的网络双连接
Solaris IPMP 配置
weixin_33708432的博客
09-03 134
IPMP（IPNetwork Multipathing）是Solaris产品中的一个主要特性，其目的在于：一、增加网络的吞吐量，可方便快捷的将几个网络接口绑定在一起使用，从而起到增加带宽的作用。二、实现网络接口的有效性，通过IPMP，可以做到网络接口的冗余使用，即使宕掉一块网卡，其他的网卡均能有效运行，并且坏掉的网卡上的业务IP不会丢失，将平滑转移到其他网卡上。 配置方法： 1、配...
Solaris IPMP配置
weixin_34258838的博客
01-17 159
先解释一下什么是IPMPIP网络多路径(IP networkmultipathing, IPMP)为在同一IP链路上具有多个接口的系统提供物理接口故障检测和透明网络访问故障转移功能。IPMP还为具有多个接口的系统提供了包负荷分配。通过IPMP，可以将一个或多个物理接口配置到IP多路径组（IPMP组）中。配置IPMP后，系统将自动监视IPMP组中的接口是否出现故障。由于IPMP...
Solaris 10 Configure IPMP
congjian0578的博客
01-17 260
1.Link Based IPMP Request: Configure IP address “192.168.2.50” on e1000g1 & e1000g2 using Link ...
Solaris IPMP系统管理指南
01-28
Solaris IPMP系统管理指南 介绍IPMP的实现原理、配置方法、及问题解决
solaris中IPMP的配置
06-25
在solaris中为了提高网卡的冗余技术，IPMP
solaris ipmp shell
04-05
solaris ipmp shell solaris ipmp shellsolaris ipmp shell solaris ipmp shellsolaris ipmp shell solaris ipmp shellsolaris ipmp shell solaris ipmp shellsolaris ipmp shell solaris ipmp shellsolaris ipmp ...
Solaris 网卡聚合及IPMP配置
10-30
Solaris 网卡聚合及IPMP配置，需要配置网卡聚合的指导文档
SOLARIS IPMP配置实例
weixin_33910434的博客
09-03 171
IPMP配置 类型一：IPMP组内所有网卡均启用 IP规划如下： e1000g0：数据IP：192.168.77.1 测试IP：192.168.77.11 e1000g1：数据IP：192.168.77.2 测试IP：192.168.77.22 # ifconfig e1000g0 group test_ipmp # ifconfig e1000g1 group test_ipmp ...
在Solaris下使用IPMP（IP Multipathing）
plusboy的专栏
07-03 2998
在Solaris下使用IPMP（IP Multipathing）为什么要使用IPMP1、为了增加网络的吞吐量，实现多网卡的负载均衡。2、为了实现网卡冗余，提高系统可靠性与可用性。比如有某块网卡因为某些不可预测的原因，从网络上断开了，这时候客户就再也访问不了与该网卡相关联的IP地址了。但是如果使用了IPMP，我们就可以把几块网卡配置成一个组，一旦组里面的某块网卡与网络的连接断开了，那么IPMP就会检
Solaris系统配置IPMP （基于IP寻址与链路）
weixin_34087503的博客
12-04 301
一、 IPMP介绍IP 网络多路径 (IP network multipathing, IPMP) 为在同一 IP 链路上具有多个接口的系统提供物理接口故障检测和透明网络访问故障转移功能。IPMP 还为具有多个接口的系统提供了包负荷分配。通过IPMP，可以将一个或多个物理接口配置到IP多路径组（IPMP）中，配置IPMP后，IPMP的故障转移功能可以保持连接并防止断开任何现有...
solaris 10 ipmp
weixin_34123613的博客
09-14 181
Solaris 10 IPMP配置（案例一） 前提： 1）.所有IP在一个网段（VLAN）内，同网段内有其他设备（router或者主机）。 2）.两块网卡能提供同样的工作模式 3）.Solaris 8以上的版本 4）.网卡的测试IP地址不能做别的用 5）.每块网卡有一个独立唯一的MAC地址。 工作原理： 系统通过测试地址发ICMP的echo reque...
Solaris 10 IPMP 配置过程
weixin_33862993的博客
09-10 451
使用IPMP实现网卡负载(网卡负载就是需要两张网卡共用一个IP地址实现网卡灾备功能)。修/etc/hosts、/etc /hostname.bge0、/etc/hostname.bge1、 /etc/defaultrouter、/etc/netmasks 五个文件，具体配置如下：使用Solaris 10 的IPMP实现网卡负载均衡功能，网卡负载均衡即使用两个或两个以上的网...
独家 | 如何为计算机视觉和深度学习安置英伟达？
数据派THU
06-02 822
作者：Sangeet Aggarwal翻译：王晓颖校对：张若楠本文约10000字，建议阅读10+分钟本文教你如何使用 Tensor Flow，Keras，Tensor RT，以及Open...
Solaris 11 创建IPMP
li1121567428的博客
11-05 782
创建IPMP 1）显示数据链路信息以识别聚合的数据链路 root@cass102:~# dladm show-phys LINK MEDIA STATE SPEED DUPLEX DEVICE net0 Ethernet up 1000 full ...
配置IPMP
cl2689163935的博客
03-06 261
做这个可以把2快网卡绑成一个网口!This article demostrates how to set up IPMP on a Solaris 8 host and configure a virtual IP. Envir...
solaris下修改 IPMP 配置
weixin_33694172的博客
09-03 158
使用 IPMP 配置文件 /etc/default/mpathd 为 IPMP 组配置以下系统范围的参数。 FAILURE_DETECTION_TIME TRACK_INTERFACES_ONLY_WITH_GROUPS FAILBACK 如何配置 /etc/default/mpathd 文件 在具有 IPMP 组配置的系统上，承担主管理员角色或成为超级用户。 主管理员角色拥有主管理员...
IPMP报名考试官网
最新发布
03-07
IPMP（Information Processing and Management Professional）是一种信息处理与管理专业资格认证，由中国信息产业协会主办。如果您想了解IPMP考试的相关信息，建议您访问中国信息产业协会的官方网站或者通过其他可靠...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值