免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
12下一页
最近访问板块 发新帖
查看: 7049 | 回复: 13
打印 上一主题 下一主题

[HACMP集群] HACMP5.3网络拓扑配置总是有问题,好心人帮帮忙! [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2006-07-19 11:50 |只看该作者 |倒序浏览
ERROR: could not find an unused address for heartbeat via alias on network net_enter_boot.
Either reduce the number of adapters on this network
or expand the netmask so more addresses can be allocated per subnet.
Verification to be performed on the following:
        Cluster Topology
        Cluster Resources

Verification will interactively correct verification errors.



Verifying Cluster Topology...

WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb1, network: net_enter_boot. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb2, network: net_enter_boot. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb1, network: net_ether_priv. Multiple communication interfaces are
recommended for networks that will use IP aliasing.

WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb2, network: net_ether_priv. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb1, network: net_ether_stby. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb2, network: net_ether_stby. Multiple communication interfaces are
recommended for networks that will use IP aliasing.

Verifying XD Solutions...

ERROR: could not find an unused address for heartbeat via alias
on network net_enter_boot.
Either reduce the number of adapters on this network
or expand the netmask so more addresses can be allocated per subnet.

Verification has completed normally.


下面是/etc/hosts文件内容:

10.76.1.130     sndb1
10.76.1.130     sndb1_boot
10.76.200.130   sndb1_stby
10.76.1.132     sndb1_vip
10.10.10.10     sndb1_priv

10.76.1.131     sndb2
10.76.1.131     sndb2_boot
10.76.200.131   sndb2_stby
10.76.1.133     sndb2_vip
10.10.10.11     sndb2_priv

论坛徽章:
0
2 [报告]
发表于 2006-07-19 11:54 |只看该作者

我在HACMP配置网络拓扑时候,配置了三个网络

分别是:
net_enter_boot             255.255.255.0           这个网络中包括:sndb_boot
net_enter_stby              255.255.255.0          这个网络中包括:sndb_stby
net_enter_priv               255.255.255.0          这个网络中包括:sndb_priv

但是浮动虚拟IP地址:sndb1_vip : 10.76.1.132     sndb2_vip:  10.76.1.133  根本就加不进去,说这个地址不存在,因为群集还没有启动呀,所以就是不存在呀,可怎么办呢?????

论坛徽章:
0
3 [报告]
发表于 2006-07-19 12:33 |只看该作者

在线等待高手

这个问题已经折腾了2天了

论坛徽章:
0
4 [报告]
发表于 2006-07-19 15:01 |只看该作者

ooo

Verification to be performed on the following:
        Cluster Topology
        Cluster Resources

Verification will interactively correct verification errors.


Retrieving data from available cluster nodes.  This could take a few minutes......


Verifying Cluster Topology...

WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb1, network: net_enter_boot. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb2, network: net_enter_boot. Multiple communication interfaces are

WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb2, network: net_enter_boot. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb1, network: net_enter_priv. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb2, network: net_enter_priv. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb1, network: net_enter_stby. Multiple communication interfaces are

WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb1, network: net_enter_stby. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


WARNING: There may be an insufficient number of communication interfaces defined
on node: sndb2, network: net_enter_stby. Multiple communication interfaces are
recommended for networks that will use IP aliasing.


ERROR: Service adapter sndb2_vip on network net_enter_boot is on the same
subnet as at least one of the communication interfaces on this network.
Service labels must be on a different subnet when the network is configured
to use IP aliasing for IP address takeover.

ERROR: Service adapter sndb1_vip on network net_enter_boot is on the same
subnet as at least one of the communication interfaces on this network.
Service labels must be on a different subnet when the network is configured
to use IP aliasing for IP address takeover.

ERROR: Service adapter sndb2_vip on network net_enter_boot is on the same
subnet as at least one of the communication interfaces on this network.
Service labels must be on a different subnet when the network is configured
to use IP aliasing for IP address takeover.

ERROR: Service adapter sndb1_vip on network net_enter_boot is on the same
subnet as at least one of the communication interfaces on this network.
Service labels must be on a different subnet when the network is configured
to use IP aliasing for IP address takeover.


Verifying Cluster Resources...

WARNING: The service IP label: sndb2_vip on node: sndb1 is not configured
to be part of a resource group. It will not be acquired and
used as a service address by any node.

WARNING: The service IP label: sndb1_vip on node: sndb1 is not configured
to be part of a resource group. It will not be acquired and
to be part of a resource group. It will not be acquired and
used as a service address by any node.

WARNING: Only one node: sndb1  was defined for resource group: sndb1_resource.

WARNING: Only one node: sndb2 was defined for resource group: sndb2_resource.


Verifying XD Solutions...


Verification exiting with error count: 4

cldare: Failures detected during verification.  Please correct
the errors and retry this command.

Verification has completed normally.

论坛徽章:
0
5 [报告]
发表于 2006-07-19 16:27 |只看该作者
讨论一下
10.76.1.130     sndb1
10.76.1.130     sndb1_boot
你这种写法和10.76.1.130     sndb1_boot  sndb1写法是一个意思吗?如果是的话,为什么要写在boot地址后面呢?

论坛徽章:
0
6 [报告]
发表于 2006-07-20 17:24 |只看该作者
在上文里:
10.76.1.130     sndb1               这个应该是服务地址
10.76.1.130     sndb1_boot      这个是启动地址
在5.3里,一旦HACMP启动之后,boot IP是继续运行的,用netstat -in就能看到,而且还可以ping/telnet。如果IP象上面所设置,那serv IP还有什么意义呢?正常来说,serv IP是一个公网地址,可以漂到另外一台机器上去,但现在和BOOT一样的地址,应该是不行的。
不知道我的理解对不对?

论坛徽章:
1
操作系统版块每日发帖之星
日期:2015-11-09 06:20:00
7 [报告]
发表于 2006-07-21 10:28 |只看该作者
10.76.1.130     sndb1
10.76.1.130     sndb1_boot
服务IP和启动IP是同一IP吗,HACMP5.3没搞过.

论坛徽章:
0
8 [报告]
发表于 2006-07-21 10:35 |只看该作者
这样的配置方法boot,standby,浮动IP好像要在不同的网段
把bootIP修改为10.76.2.130  这个网段试试

论坛徽章:
0
9 [报告]
发表于 2006-07-21 11:50 |只看该作者
使用ip别名就行啦。

论坛徽章:
0
10 [报告]
发表于 2006-07-23 10:57 |只看该作者

问题已经解决

问题已经解决,不过很麻烦,急需知道解果的可以给我发mail     johnson.chao@163.com
说明你有什么问题,想问的是哪个我提交的问题!OK
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP