首页 > 其他分享 >Solaris IPMP两种配置方法

Solaris IPMP两种配置方法

时间：2024-07-24 12:51:35浏览次数：14  
标签：Solaris 配置 192.168 mtu IPMP netmask MULTICAST IPv4 inet

更换华为防火墙后，发现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
  1. 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

标签：Solaris,配置,192.168,mtu,IPMP,netmask,MULTICAST,IPv4,inet
From： https://www.cnblogs.com/kyo-1115/p/18320632

相关文章

  • solaris10 for sparc 编译安装expect 实现sftp 脚本交互
    0、先设置root的环境变量：exportPATH=/usr/sfw/bin:/usr/ccs/bin:$PATH1、安装tcl下载tcl8.6.13-src.tar.gz文件下载网站：gunziptcl8.6.13-src.tar.gztar-xvftcl8.6.13-src.tarcdtcl8.6.13/unixmkdirsolariscdsolaris/../configure--prefix=/data/expect_local--e......
  • Solaris11升级openssh和openssl
    源码编译升级openssl版本官网下载openssl-1.1.1d.targunzipopenssl-1.1.1d.tar.gztaropenssl-1.1.1d.tarcdopenssl-1.1.1d./config--prefix=/usr/local/sslsharedmakemakeinstall替换老版本:备份mv/usr/bin/openssl/usr/bin/openssl.oldmv/usr/i......
  • solaris vbs巡检脚本
    ```vbscript#$language="VBScript"#$interface="1.0"crt.Screen.Synchronous=True'Thisautomaticallygeneratedscriptmayneedtobe'editedinordertoworkcorrectly.'chr(13)回车符SubMain'---thesystem......
  • 微信小程序 - 最新详细实现集成腾讯地图配置流程及使用教程，基于腾讯位置服务做地图标
    前言网上的教程代码太乱了，并且很少有真实请求的示例，本文提供优质配置教程及示例源码。在微信小程序开发中，详解实现接入腾讯地图教程，后台配置完整流程及使用教程，附带腾讯地图显示渲染和地图标记点，获取本机当前定位省市区或精确的经纬度，IP属地定位获取城市名称/市区名，将经......
  • 配置文件mybatis-plus: global-config: db-config: table-prefix: true
    具体来说，table-underline的含义是：当table-underline设置为true时：假设你有一个实体类名为UserInfo，那么MyBatis-Plus会默认去数据库中寻找名为user_info的表（即，驼峰命名法自动转换为下划线命名法）。同理，如果你的数据库表名是user_info，但你的实体类名是UserInfo，那么M......
  • 【运维自动化-配置平台】如何跨业务转移主机
    在如何创建业务拓扑中，了解到业务是蓝鲸体系重要的资源管理纬度，主机在业务之前需要流转怎么做呢？比如要把A业务一台主机划给B业务使用权限中心跨业务转移主机一般场景是由源主机所在业务的负责人发起，需要申请目标业务的相关权限。（如果是管理员操作则无需申请权限）填写关联资源实......
  • Linux如何配置触控板?
    Linux配置触控板通常涉及编辑或创建配置文件，并调整相应的设置以符合个人使用习惯。以下是一个详细的步骤指南，主要基于使用Xorg图形服务器和libinput驱动的情况，因为libinput是许多现代Linux发行版中推荐的触控板驱动。确认你的Linux系统是否已安装libinput驱动。libinput是许多......
  • springboot属性统一配置，分层级
    app.user.name=JohnDoeapp.user.age=30app.user.address.city=NewYorkapp.user.address.country=USAimportorg.springframework.boot.context.properties.ConfigurationProperties;importorg.springframework.context.annotation.Configuration;@Configuration......
  • Django 5.0：配置本地开发和生产环境？
    这个问题已经以各种形式被问过几次。然而，关于这个主题的大多数答案都有十年或更久的历史了。我的《TwoScoops》书是针对Django3.x的。我认为更新与Django5.0相关的答案和今天可用的托管选项可能会很有用。这是我回顾过的许多旧讨论之一：Django：如何管理开......
  • Spring Boot 自动配置原理
    Author:ACatSmilingSince:2024-07-23核心场景启动器SpringBoot的每个场景启动器都引入了一个spring-boot-starter，这是SpringBoot的核心场景启动器。<dependency><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter</artifactId>&l......

赞助商

阅读排行

网站主页关于我们联系我们网站地图

本网站内容转载自其他媒体，侵权联系[admin##ips99.com]。

Copyright © 2020-2023 IPS99 版权所有 IPS99