We can get to the VM but cannot get to the Hypervisor via Vsphere Client

Version 1
    This document was generated from CDN thread

    Created by: Jiasi Li on 23-03-2011 05:10:01 PM
    Hi, we ran into an issue recently on our 3945 router.  For some reason we can get access to our VM via Telnet and ping, but we cannot get access to the Hypervisor via VSpher nor can we ping it from the router or anywhere else.  Below is our config and some diagnoistics.  Any help will be appreciated.   Thanks.
     
    !<<<<<<<<<<<<<<<<<< CONFIG <<<<<<<<<<<<<<<<<<<<
    !
    interface GigabitEthernet0/2
     ip address 8.8.8.1 255.255.255.0 secondary
     ip address 10.250.64.85 255.255.248.0
     ip traffic-export apply g01_wan
     duplex full
     speed 100
     ipv6 address FD3A:9290:84F:31F7::1/64
     ipv6 enable
     
    !
    interface SM2/0
     ip unnumbered GigabitEthernet0/2
     service-module ip address 10.250.64.93 255.255.248.0
     !Application: SRE-V Running on SMV
     service-module ip default-gateway 10.250.64.85
     service-module mgf ip address 10.250.80.205 255.255.255.248
     service-module mgf ip default-gateway 10.250.80.201
     ipv6 enable
     
    !
    interface Vlan1
     ip address 10.250.80.201 255.255.255.248
     
    ip route 0.0.0.0 0.0.0.0 8.8.8.2
    ip route 1.1.1.1 255.255.255.255 GigabitEthernet0/1
    ip route 1.1.1.2 255.255.255.255 GigabitEthernet0/1
    ip route 2.2.2.1 255.255.255.255 GigabitEthernet0/2
    ip route 2.2.2.2 255.255.255.255 GigabitEthernet0/2
    ip route 10.10.10.0 255.255.255.0 GigabitEthernet0/1
    ip route 10.31.23.0 255.255.255.0 9.9.9.2
    ip route 10.31.27.0 255.255.255.0 8.8.8.2
    ip route 10.50.12.0 255.255.255.0 8.8.8.2
    ip route 10.50.14.2 255.255.255.255 8.8.8.2
    ip route 10.50.116.0 255.255.255.0 9.9.9.2
    ip route 10.50.118.2 255.255.255.255 9.9.9.2
    ip route 10.250.64.0 255.255.248.0 8.8.8.2
    !<<<<<<<<  Related to SRE Module <<<<<<<<
    ip route 10.250.64.83 255.255.255.255 SM1/0
    ip route 10.250.64.93 255.255.255.255 SM2/0
    ip route 10.250.80.202 255.255.255.255 Vlan1
    ip route 10.250.80.205 255.255.255.255 Vlan1
    !>>>>>>>>>>
    ip route 10.250.74.25 255.255.255.255 Serial0/1/0:0
    ip route 10.250.80.0 255.255.255.0 8.8.8.2
    ip route 10.250.80.2 255.255.255.255 8.8.8.2
    ip route 10.250.80.3 255.255.255.255 9.9.9.2
    ip route 10.250.80.193 255.255.255.255 Vlan40
    ip route 10.250.80.226 255.255.255.255 Vlan40
    ip route 10.250.80.234 255.255.255.255 Vlan55
    ip route 20.20.20.0 255.255.255.0 Serial0/1/0:0
    ip route 99.99.99.7 255.255.255.255 Vlan99
    ip route 100.100.3.0 255.255.255.0 8.8.8.2
    ip route 129.196.200.0 255.255.255.0 8.8.8.2
    !>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
     
    3900_router#show ip route
    Gateway of last resort is 8.8.8.2 to network 0.0.0.0
    S*    0.0.0.0/0 [1/0] via 8.8.8.2
          1.0.0.0/32 is subnetted, 2 subnets
    S        1.1.1.1 is directly connected, GigabitEthernet0/1
    S        1.1.1.2 is directly connected, GigabitEthernet0/1
          2.0.0.0/32 is subnetted, 2 subnets
    S        2.2.2.1 is directly connected, GigabitEthernet0/2
    S        2.2.2.2 is directly connected, GigabitEthernet0/2
          8.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
    C        8.8.8.0/24 is directly connected, GigabitEthernet0/2
    L        8.8.8.1/32 is directly connected, GigabitEthernet0/2
          9.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
    C        9.9.9.0/24 is directly connected, GigabitEthernet0/1
    L        9.9.9.1/32 is directly connected, GigabitEthernet0/1
          10.0.0.0/8 is variably subnetted, 24 subnets, 4 masks
    S        10.10.10.0/24 is directly connected, GigabitEthernet0/1
    S        10.31.23.0/24 [1/0] via 9.9.9.2
    S        10.31.27.0/24 [1/0] via 8.8.8.2
    S        10.50.12.0/24 [1/0] via 8.8.8.2
    S        10.50.14.2/32 [1/0] via 8.8.8.2
    S        10.50.116.0/24 [1/0] via 9.9.9.2
    S        10.50.118.2/32 [1/0] via 9.9.9.2
    C        10.250.64.0/21 is directly connected, GigabitEthernet0/2
    C        10.250.64.64/32 is directly connected, Serial0/1/0:0
    S        10.250.64.83/32 is directly connected, SM1/0
    L        10.250.64.85/32 is directly connected, GigabitEthernet0/2
    S        10.250.64.93/32 is directly connected, SM2/0
    S        10.250.74.25/32 is directly connected, Serial0/1/0:0
    S        10.250.80.0/24 [1/0] via 8.8.8.2
    S        10.250.80.2/32 [1/0] via 8.8.8.2
    S        10.250.80.3/32 [1/0] via 9.9.9.2
    S        10.250.80.193/32 is directly connected, Vlan40
    C        10.250.80.200/29 is directly connected, Vlan1
    L        10.250.80.201/32 is directly connected, Vlan1
    S        10.250.80.202/32 is directly connected, Vlan1
    S        10.250.80.205/32 is directly connected, Vlan1
    C        10.250.80.224/29 is directly connected, GigabitEthernet0/2.40
    L        10.250.80.225/32 is directly connected, GigabitEthernet0/2.40
    S        10.250.80.226/32 is directly connected, Vlan40
          20.0.0.0/8 is variably subnetted, 3 subnets, 3 masks
    S        20.20.20.0/24 is directly connected, Serial0/1/0:0
    C        20.20.20.0/30 is directly connected, Serial0/1/0:0
    L        20.20.20.1/32 is directly connected, Serial0/1/0:0
          100.0.0.0/24 is subnetted, 1 subnets
    S        100.100.3.0 [1/0] via 8.8.8.2
          129.196.0.0/24 is subnetted, 1 subnets
    S        129.196.200.0 [1/0] via 8.8.8.2
    3900_router#
     
    3900_router#service-module sm2/0 session
    Trying 10.250.64.85, 2131 ... Open
    se-10-250-64-93#
    se-10-250-64-93# show hyp ip
    Hostname:               localhost
    Domain Name:            danahertm.com
    IP Config:              10.250.80.205(Subnet Mask: 255.255.255.248)
                            169.254.1.1(Subnet Mask: 255.255.255.0)
    Default Gateway:        10.250.80.201
    Preferred DNS Server:   10.250.64.16
    Alternative DNS Server: None
    se-10-250-64-93# show hyp nics
    Name    PCI            I/E Driver      Link Speed     Duplex MAC Address
    vmnic1  0000:01:00.00  E   e1000e      Down 0Mbps     Half   c8:4c:75:23:b1:31
    vmnic2  0000:02:00.00  I   bnx2        Up   1000Mbps  Full   88:43:e1:bc:92:61
    vmnic3  0000:02:00.01  I   bnx2        Up   1000Mbps  Full   88:43:e1:bc:92:60
    3 total nics (I - Internal nic, E - External nic)
    se-10-250-64-93# show ip route
    Main Routing Table:
               DEST            GATE            MASK IFACE
        169.254.1.0         0.0.0.0   255.255.255.0 eth2
        10.250.64.0         0.0.0.0   255.255.248.0 eth0
            0.0.0.0    10.250.64.85         0.0.0.0 eth0
    se-10-250-64-93#
     
    3900_router#ping 10.250.64.93
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.250.64.93, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
    3900_router#ping 10.250.80.205
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.250.80.205, timeout is 2 seconds:
    .....
    Success rate is 0 percent (0/5)
    3900_router#ping 10.250.80.206
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.250.80.206, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

    Subject: RE: We can get to the VM but cannot get to the Hypervisor via Vsphere Clien
    Replied by: Jiasi Li on 05-04-2011 03:45:02 PM
    this issue was due to VLAN set on the VM Network on the ESXi host.  The issue here is that once someone set it this way; there is no way to unset or change it through the service-module sessions CLI.  Will there be support for this and other ESXi-type commands in the future?

    Subject: RE: New Message from Jiasi Li in Service Ready Engine Virtualization - Tech
    Replied by: Anurag Gurtu on 05-04-2011 03:49:27 PM
    Most of the VMware related configuration is done using vSphere client. As of now we are not planning to add a CLI for this feature however in future you should be able to use VMware CLI and make necessary changes.



    Thanks



    Anurag Gurtu, CISSP



    From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    Sent: Tuesday, April 05, 2011 12:45 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from Jiasi Li in Service Ready Engine Virtualization - Technical Questions: RE: We can get to the VM but cannot get to the Hypervisor via Vsphere Clien



    Jiasi Li has created a new message in the forum "Technical Questions":

    --------------------------------------------------------------
    this issue was due to VLAN set on the VM Network on the ESXi host. The issue here is that once someone set it this way; there is no way to unset or change it through the service-module sessions CLI. Will there be support for this and other ESXi-type commands in the future?
    --
    To respond to this post, please click the following link:

    <http://developer.cisco.com/web/srev/forums/-/message_boards/view_message/3514098>

    or simply reply to this email.