奇怪的路由问题[关闭]


1

由于我的错误,我刚刚更新了路线表。

我正在努力使网络在客户站点的14个虚拟服务器的集群上正常工作。其中11个适用于路由,3个不能正常运行其管理网络(172.28.56.0)。所有都运行Windows Web Server 2008R2。

默认网关在生产网络(172.28.58.0)上设置,而不在管理网络上(使用持久静态路由处理)。

在工作服务器上,路由打印给我以下(MAC编辑)

===========================================================================
Interface List
 11...XX XX XX XX XX XX ......Intel(R) PRO/1000 MT Network Connection
 13...XX XX XX XX XX XX00 0c 29 85 b2 98 ......Intel(R) PRO/1000 MT Network Connection #2
  1...........................Software Loopback Interface 1
 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table

===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
           0.0.0.0         0.0.0.0      172.28.58.1    172.28.58.11     266
        10.18.1.22 255.255.255.255      172.28.58.1    172.28.58.11      11
         10.32.0.0     255.255.0.0      172.28.56.1   172.28.56.201      11
         127.0.0.0       255.0.0.0          On-link       127.0.0.1     306
         127.0.0.1 255.255.255.255          On-link       127.0.0.1     306
   127.255.255.255 255.255.255.255          On-link       127.0.0.1     306
      172.28.34.0    255.255.255.0      172.28.56.1   172.28.56.201      11
      172.28.42.0    255.255.255.0      172.28.56.1   172.28.56.201      11
      172.28.56.0    255.255.255.0          On-link   172.28.56.201     266
      172.28.56.0    255.255.255.0      172.28.56.1   172.28.56.201      11
    172.28.56.201  255.255.255.255          On-link   172.28.56.201     266
    172.28.56.255  255.255.255.255          On-link   172.28.56.201     266
      172.28.58.0  255.255.255.224          On-link    172.28.58.11     266
      172.28.58.0  255.255.255.224      172.28.58.1    172.28.58.11      11
      172.28.58.1  255.255.255.255      172.28.58.1    172.28.58.11      11
     172.28.58.11  255.255.255.255          On-link    172.28.58.11     266
     172.28.58.31  255.255.255.255          On-link    172.28.58.11     266
      172.28.60.0    255.255.255.0      172.28.56.1   172.28.56.201      11
      172.28.63.0    255.255.255.0      172.28.56.1   172.28.56.201      11
      192.168.0.0      255.255.0.0      172.28.56.1   172.28.56.201      11
        224.0.0.0        240.0.0.0          On-link       127.0.0.1     306
        224.0.0.0        240.0.0.0          On-link   172.28.56.201     266
        224.0.0.0        240.0.0.0          On-link    172.28.58.11     266
  255.255.255.255  255.255.255.255          On-link       127.0.0.1     306
  255.255.255.255  255.255.255.255          On-link   172.28.56.201     266
  255.255.255.255  255.255.255.255          On-link    172.28.58.11     266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      172.28.56.0    255.255.255.0      172.28.56.1       1
      172.28.63.0    255.255.255.0      172.28.56.1       1
      192.168.0.0      255.255.0.0      172.28.56.1       1
      172.28.60.0    255.255.255.0      172.28.56.1       1
        10.32.0.0      255.255.0.0      172.28.56.1       1
      172.28.34.0    255.255.255.0      172.28.56.1       1
      172.28.42.0    255.255.255.0      172.28.56.1       1
          0.0.0.0          0.0.0.0      172.28.58.1  Default
===========================================================================

IPv6 Route Table

===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  1    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

在其中一个非工作服务器上,路由打印给我以下(MAC编辑)

===========================================================================
Interface List
 11...XX XX XX XX XX XX ......Intel(R) PRO/1000 MT Network Connection
 13...XX XX XX XX XX XX ......Intel(R) PRO/1000 MT Network Connection #2
  1...........................Software Loopback Interface 1
 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table

===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
           0.0.0.0         0.0.0.0      172.28.58.1    172.28.58.21     266
         10.32.0.0     255.255.0.0      172.28.56.1   172.28.56.211      11
         127.0.0.0       255.0.0.0          On-link       127.0.0.1     306
         127.0.0.1 255.255.255.255          On-link       127.0.0.1     306
   127.255.255.255 255.255.255.255          On-link       127.0.0.1     306
       172.28.34.0   255.255.255.0      172.28.56.1   172.28.56.211      11
       172.28.42.0   255.255.255.0      172.28.56.1   172.28.56.211      11
       172.28.56.0   255.255.255.0      172.28.56.1   172.28.56.211      11
     172.28.56.211 255.255.255.255          On-link   172.28.56.211     266
       172.28.58.0   255.255.255.0      172.28.58.1    172.28.58.21      11
       172.28.58.0 255.255.255.224          On-link    172.28.58.21     266
      172.28.58.21 255.255.255.255          On-link    172.28.58.21     266
      172.28.58.31 255.255.255.255          On-link    172.28.58.21     266
       172.28.60.0   255.255.255.0      172.28.56.1   172.28.56.211      11
       172.28.63.0   255.255.255.0      172.28.56.1   172.28.56.211      11
       192.168.0.0     255.255.0.0      172.28.56.1   172.28.56.211      11
         224.0.0.0       240.0.0.0          On-link       127.0.0.1     306
         224.0.0.0       240.0.0.0          On-link   172.28.56.211     266
         224.0.0.0       240.0.0.0          On-link    172.28.58.21     266
   255.255.255.255 255.255.255.255          On-link       127.0.0.1      06
   255.255.255.255 255.255.255.255          On-link   172.28.56.211     266
   255.255.255.255 255.255.255.255          On-link    172.28.58.21     266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      172.28.56.0    255.255.255.0      172.28.56.1       1
      172.28.60.0    255.255.255.0      172.28.56.1       1
      172.28.63.0    255.255.255.0      172.28.56.1       1
      172.28.34.0    255.255.255.0      172.28.56.1       1
      172.28.42.0    255.255.255.0      172.28.56.1       1
      192.168.0.0      255.255.0.0      172.28.56.1       1
        10.32.0.0      255.255.0.0      172.28.56.1       1
          0.0.0.0          0.0.0.0      172.28.58.1  Default
      172.28.58.0    255.255.255.0      172.28.58.1       1
===========================================================================

IPv6 Route Table

===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  1    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

我完全失去了为什么非工作服务器没有172.28.56.0的On-link路由。有没有人对我应该考虑什么有任何建议来解决这个问题?此外,如果需要,我可以通过vSphere Client对控制台进行“物理”访问。


欢迎来到超级用户!虽然这里没有明确的偏离主题,但很有可能在服务器故障(我们的专业服务器管理员的姐妹站点)上获得更好的结果。没有必要在那里交叉发布您的问题 - 如果主持人或其他几个用户同意,问题将会为您迁移。
Darth Android

由于没有其他人似乎投票移动它而我需要这个ASAP的帮助,我发布了Server Fault。
smccloud

请不要CROSSPOST。

Randolph,我不会但很遗憾,直到我说我只做了Darth Android提供了任何帮助。
smccloud

@smccloud为了将来的参考,理想的解决方案是简单地标记你自己的帖子以供主持人注意(假设你可以,我不确定是否有代表要求),或者只是等待。这对于超级用户来说并不是一个糟糕的问题- 社区之间存在很多重叠 - 但从长远来看,它更适合服务器故障。尽管如此,我希望你能解决问题!
Darth Android
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.