原创作品,出自 “深蓝的blog” 博客,欢迎转载,转载时请务必注明以下出处,否则追究版权法律责任。 深蓝的blog:http://blog.csdn.net/huangyanlong/article/details/40735481 环境:Cent0S 6.4 64bit、grid 64bit 自检出现“TCP connectivity of subnet”
原创作品,出自 “深蓝的blog” 博客,欢迎转载,转载时请务必注明以下出处,否则追究版权法律责任。
无线网络修复工具是一款联想出品的小工具,旨在诊断并修复计算机的无线网络问题。它全面检查硬件故障、驱动程序错误、无线开关设置、连接设置和路由器配置。 该工具支持 Windows XP、Win7 和 Win10 系统。请注意,在运行该工具之前,应拔出电脑的网线,以确保准确诊断和修复。 使用此工具,用户可以轻松找出并解决 WiFi 问题,无需手动排查故障。它提供了一键式解决方案,即使对于非技术用户也易于使用。
0
深蓝的blog:http://blog.csdn.net/huangyanlong/article/details/40735481
环境:Cent0S 6.4 64bit、grid 64bit
自检出现“TCP connectivity of subnet”问题。
【问题】
手工进行grid自检,报出如下错误:
[grid@xzxt1 grid]$ ./runcluvfy.sh stage -pre crsinst -n xzxt1,xzxt2 -fixup -verbose
...... ...... Check: Node connectivity of subnet "192.168.56.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- xzxt2[192.168.56.31] xzxt1[192.168.56.30] yes Result: Node connectivity passed for subnet "192.168.56.0" with node(s) xzxt2,xzxt1 Check: TCP connectivity of subnet "192.168.56.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- xzxt1:192.168.56.30 xzxt2:192.168.56.31 failed ERROR: PRVF-7617 : Node connectivity between "xzxt1 : 192.168.56.30" and "xzxt2 : 192.168.56.31" failed Result: TCP connectivity check failed for subnet "192.168.56.0" Check: Node connectivity of subnet "10.10.10.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- xzxt2[10.10.10.91] xzxt1[10.10.10.90] yes Result: Node connectivity passed for subnet "10.10.10.0" with node(s) xzxt2,xzxt1 Check: TCP connectivity of subnet "10.10.10.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- xzxt1:10.10.10.90 xzxt2:10.10.10.91 failed ERROR: PRVF-7617 : Node connectivity between "xzxt1 : 10.10.10.90" and "xzxt2 : 10.10.10.91" failed Result: TCP connectivity check failed for subnet "10.10.10.0" Interfaces found on subnet "192.168.56.0" that are likely candidates for VIP are: xzxt2 eth0:192.168.56.31 xzxt1 eth0:192.168.56.30 WARNING: Could not find a suitable set of interfaces for the private interconnect Checking subnet mask consistency... Subnet mask consistency check passed for subnet "192.168.56.0". Subnet mask consistency check passed for subnet "10.10.10.0". Subnet mask consistency check passed. Result: Node connectivity check failed Checking multicast communication... Checking subnet "192.168.56.0" for multicast communication with multicast group "230.0.1.0"... PRVG-11134 : Interface "192.168.56.31" on node "xzxt2" is not able to communicate with interface "192.168.56.31" on node "xzxt2" PRVG-11134 : Interface "192.168.56.31" on node "xzxt2" is not able to communicate with interface "192.168.56.30" on node "xzxt1" PRVG-11134 : Interface "192.168.56.30" on node "xzxt1" is not able to communicate with interface "192.168.56.31" on node "xzxt2" PRVG-11134 : Interface "192.168.56.30" on node "xzxt1" is not able to communicate with interface "192.168.56.30" on node "xzxt1" Checking subnet "192.168.56.0" for multicast communication with multicast group "224.0.0.251"... PRVG-11134 : Interface "192.168.56.31" on node "xzxt2" is not able to communicate with interface "192.168.56.31" on node "xzxt2" PRVG-11134 : Interface "192.168.56.31" on node "xzxt2" is not able to communicate with interface "192.168.56.30" on node "xzxt1" PRVG-11134 : Interface "192.168.56.30" on node "xzxt1" is not able to communicate with interface "192.168.56.31" on node "xzxt2" PRVG-11134 : Interface "192.168.56.30" on node "xzxt1" is not able to communicate with interface "192.168.56.30" on node "xzxt1" Checking subnet "10.10.10.0" for multicast communication with multicast group "230.0.1.0"... PRVG-11134 : Interface "10.10.10.91" on node "xzxt2" is not able to communicate with interface "10.10.10.91" on node "xzxt2" PRVG-11134 : Interface "10.10.10.91" on node "xzxt2" is not able to communicate with interface "10.10.10.90" on node "xzxt1" PRVG-11134 : Interface "10.10.10.90" on node "xzxt1" is not able to communicate with interface "10.10.10.91" on node "xzxt2" PRVG-11134 : Interface "10.10.10.90" on node "xzxt1" is not able to communicate with interface "10.10.10.90" on node "xzxt1" Checking subnet "10.10.10.0" for multicast communication with multicast group "224.0.0.251"... PRVG-11134 : Interface "10.10.10.91" on node "xzxt2" is not able to communicate with interface "10.10.10.91" on node "xzxt2" PRVG-11134 : Interface "10.10.10.91" on node "xzxt2" is not able to communicate with interface "10.10.10.90" on node "xzxt1" PRVG-11134 : Interface "10.10.10.90" on node "xzxt1" is not able to communicate with interface "10.10.10.91" on node "xzxt2" PRVG-11134 : Interface "10.10.10.90" on node "xzxt1" is not able to communicate with interface "10.10.10.90" on node "xzxt1" ...... ......
【解决】
[root@xzxt1 network-scripts]# vi ifcfg-eth0
--去掉GATEWAY=192.168.56.1
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
IPADDR=192.168.56.30
NETMASK=255.255.255.0
[root@xzxt1 network-scripts]# vi ifcfg-eth1
--去掉GATEWAY=10.10.10.1
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=static
IPADDR=10.10.10.90
NETMASK=255.255.255.0
重启服务器后,再次自检此问题不再出现。
原创作品,出自 “深蓝的blog” 博客,欢迎转载,转载时请务必注明以下出处,否则追究版权法律责任。
深蓝的blog:http://blog.csdn.net/huangyanlong/article/details/40735481
每个人都需要一台速度更快、更稳定的 PC。随着时间的推移,垃圾文件、旧注册表数据和不必要的后台进程会占用资源并降低性能。幸运的是,许多工具可以让 Windows 保持平稳运行。
C++高性能并发应用_C++如何开发性能关键应用
Java AI集成Deep Java Library_Java怎么集成AI模型部署
Golang后端API开发_Golang如何高效开发后端和API
Python异步并发改进_Python异步编程有哪些新改进
C++系统编程内存管理_C++系统编程怎么与Rust竞争内存安全
Java GraalVM原生镜像构建_Java怎么用GraalVM构建高效原生镜像
Python FastAPI异步API开发_Python怎么用FastAPI构建异步API
C++现代C++20/23/26特性_现代C++有哪些新标准特性如modules和coroutines
Copyright 2014-2025 https://www.php.cn/ All Rights Reserved | php.cn | 湘ICP备2023035733号