HA5.0配置成功之后,一根心跳线显示异常
<server>
*ah1 .............: Caution
lanhb1 : Caution LAN Heartbeat
lanhb2 : Normal LAN Heartbeat
lankhb2 : Normal Kernel Mode LAN Heartbeat
lankhb1 : Caution Kernel Mode LAN Heartbeat
ah2 .............: Caution
lanhb1 : Caution LAN Heartbeat
lanhb2 : Normal LAN Heartbeat
lankhb2 : Normal Kernel Mode LAN Heartbeat
lankhb1 : Caution Kernel Mode LAN Heartbeat
<group>
|
从现象看,应该就是心跳线有问题,用户说是可以HA现在用着是正常的,应用也都正常,而且两台机器之间,通过这两跟心跳都是可以ping通的。奇怪了。
登录上去看了看日志lanhb.log.cur
[E] 03/16 11:33:19.969 [03859:b7c88bb0] lanhb.c:2513 hbcheck **TIMEOUT(cur:0x1
9999d1b,last:0x199979ee,diff:9005,hbto:90,tck:100/sec)
[E] 03/16 11:33:19.969 [03859:b7c88bb0] lanhb.c:2524 hbcheck rsc(lanhb1)/node(
ah1(0)) -> OFFLINE
[E] 03/16 11:33:19.969 [03859:b7c88bb0] lanhb.c:2419 setrscstat rsc(lanhb1) statu
s change to CAUTION
|
而且两边都是类似的提示,超时。看来应该是物理链路的问题了。
ifconfig没有什么问题,但是mii-tool却出现问题了
[root@ah1 log]# mii-tool
eth0: negotiated 100baseTx-FD flow-control, link ok
SIOCGMIIPHY on 'eth1' failed: Bad address
|
这提示可真是出乎我的意料,从来没有见过这个提示,错误的地址。这个有待查一查,不过通过直连心跳ping了一下,发现丢包率很高
[root@ah1 log]# ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=0.319 ms
64 bytes from 192.168.0.2: icmp_seq=4 ttl=64 time=0.321 ms
64 bytes from 192.168.0.2: icmp_seq=5 ttl=64 time=0.305 ms
64 bytes from 192.168.0.2: icmp_seq=6 ttl=64 time=0.301 ms
--- 192.168.0.2 ping statistics ---
7 packets transmitted, 4 received, 42% packet loss, time 6001ms
rtt min/avg/max/mdev = 0.301/0.311/0.321/0.019 ms, pipe 2
|
不用问了,肯定是线不好。换线再说吧。
阅读(2214) | 评论(0) | 转发(1) |