论坛徽章:: 0

电梯直达

1楼 [收藏(0)] [报告]

发表于 2010-03-22 12:20 |只看该作者 |倒序浏览

本帖最后由 wangyl1977 于 2010-03-22 14:54 编辑 \n\n1) 默认情况下, IPMP的daemon \" /usr/lib/inet/in.mpathd -a \" 是不启动的,配好IPMP后重起机器后才启动? 系统是通过check哪个文件来判断是否启动这个process呢? /etc/hostname.* ??? \r\n2) IPMP分为 link-based和 probe_based ? 如何分辨是link-based还是 probe_based?\r\n 是不是在/etc/hostname.*里加了addif BackupTest deprecated 就算是probe-based? \r\n3) 在probe-based模式下, 感觉应该只需要check testip就能判断nic的状态,但 Solaris 10 IPMP配置 http://www.ixdba.net/hbcms/article/ae/270.html \r\n 里的工作原理上说, \" 2个条件都成功，则认为连接成功（并的关系）\" 难道任何状况下都需要判断2个条件? 那分成2种type还有什么意义?\r\n4) 里面说关闭路由时机就需要touch /etc/norouter, 是不是说配为link-based就需要执行这一步,配为probe_based就一定不能做这一步?\r\n4) 上篇文章(http://www.ixdba.net/hbcms/article/ae/270.html)的Solaris 10 IPMP配置（案例二） IPMP的balance模式,是否还需要在交换机上做配置.\r\n我配了类似的,执行if_mpadm -d报错了.\r\n\r\n[root@hostA etc]#>more /etc/hosts\r\n# Internet host table\r\n#\r\n::1 localhost \r\n127.0.0.1 localhost \r\n150.198.91.62 hostA loghost\r\n150.198.90.70 lxsfrac07\r\n150.198.90.73 lxsfrac08\r\n150.198.91.47 china1\r\n10.200.59.188 mpnim\r\n150.198.91.249 testsg-vip\r\n150.198.90.66 v20z66 \r\n150.198.90.67 v20z67 \r\n150.198.90.69 v20z69 \r\n150.198.90.55 vjss240\r\n192.168.0.1 s102 \r\n192.168.0.2 s103 \r\n192.168.0.3 test2\r\n192.168.0.4 test3\r\n\r\n[root@hostA etc]#>more /etc/hostname.e1000g1\r\ns102 netmask + broadcast + group mpgrp up addif test2 deprecated netmask + broadcast + -failover up\r\n\r\n[root@hostA etc]#>more /etc/hostname.e1000g2\r\ns103 netmask + broadcast + group mpgrp up addif test3 deprecated netmask + broadcast + -failover up\r\n\r\n[root@hostA etc]#>ifconfig -a\r\nlo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1\r\n inet 127.0.0.1 netmask ff000000 \r\ne1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2\r\n inet 150.198.91.62 netmask fffff800 broadcast 150.198.95.255\r\n ether 0:13:72:52:59:2c \r\ne1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3\r\n inet 192.168.0.1 netmask ffffff00 broadcast 192.168.0.255\r\n groupname mpgrp\r\n ether 0:13:72:52:59:2d \r\ne1000g1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 3\r\n inet 192.168.0.3 netmask ffffff00 broadcast 192.168.0.255\r\ne1000g2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4\r\n inet 192.168.0.2 netmask ffffff00 broadcast 192.168.0.255\r\n groupname mpgrp\r\n ether 0:4:23:ca:e9:f0 \r\ne1000g2:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 4\r\n inet 192.168.0.4 netmask ffffff00 broadcast 192.168.0.255\r\n\r\n[root@hostA etc]#>if_mpadm -d e1000g2\r\nOffline failed as there is no other functional interface available in the multipathing group for failing over the network access.\r\n[root@hostA etc]#>if_mpadm -d e1000g1\r\nOffline failed as there is no other functional interface available in the multipathing group for failing over the network access.