RE: Vm can not ping default gateway

RE: New Message from Kshitij Purwar in Service Ready Engine Virtualization

2012-03-15T21:16:52Z

Hi Anurag, I made the change you suggested, and I still cannot ping from the VM to the DG. Windows FW is turned off as well.

RE: New Message from Kshitij Purwar in Service Ready Engine Virtualization

2012-03-15T20:59:58Z

If you like you can create a new port group under vSwitch0 and have your VM point to that and not use vSwitch at all. Thanks Anurag Gurtu, CISSP

RE: Vm can not ping default gateway

2012-03-15T20:47:11Z

cjones@apshealthcare.com

RE: Vm can not ping default gateway

2012-03-15T20:47:11Z

cjones@apshealthcare.com

RE: New Message from Charlie Jones in Service Ready Engine Virtualization -

2012-03-15T20:45:58Z

Can we do a WebEx session tomorrow to debug this? Please send me your email address if you want to do the WebEx so I can send you the meeting invite. From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 15, 2012 12:29 PM To: cdicuser@developer.cisco.com Subject: New Message from Charlie Jones in Service Ready Engine Virtualization - SRE-V Technical Questions: RE: Vm can not ping default gateway Charlie Jones has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- I couldn't get the screen captures to cut over. Looking through the screenshots, the only difference between the two switches is in the port group properties. On the switch that the VM is on, the vlan 100. On the mgmt network (Vswitch0), the vlan shown is 0. -- To respond to this post, please click the following link: or simply reply to this email.

RE: Vm can not ping default gateway

2012-03-15T20:28:43Z

I couldn't get the screen captures to cut over. Looking through the screenshots, the only difference between the two switches is in the port group properties. On the switch that the VM is on, the vlan 100. On the mgmt network (Vswitch0), the vlan shown is 0.

RE: New Message from Charlie Jones in Service Ready Engine Virtualization -

2012-03-15T20:12:58Z

Hi Charlie, It might help if you can give screen shots of the newtroking configuration and the vmnetwork port group edit properties screen shot. Also one more thing to check is if your vm is running windows you check the firewall properties. If the above two steps don’t help we can have a debugging session this via a webex. Thanks, Radhika From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 15, 2012 12:08 PM To: cdicuser@developer.cisco.com Subject: New Message from Charlie Jones in Service Ready Engine Virtualization - SRE-V Technical Questions: RE: Vm can not ping default gateway Charlie Jones has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- Unfortunately, I still cannot ping the gateway from the VM. Is there anything from the Vsphere client I could attach to assist? -- To respond to this post, please click the following link: or simply reply to this email.

RE: Vm can not ping default gateway

2012-03-15T20:07:49Z

Unfortunately, I still cannot ping the gateway from the VM. Is there anything from the Vsphere client I could attach to assist?

RE: New Message from Kshitij Purwar in Service Ready Engine Virtualization

2012-03-15T19:52:58Z

Interface gi0/0 ip Thanks, Radhika From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 15, 2012 11:51 AM To: cdicuser@developer.cisco.com Subject: New Message from Kshitij Purwar in Service Ready Engine Virtualization - SRE-V Technical Questions: RE: Vm can not ping default gateway Kshitij Purwar has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- Hi Radhika, Thanks for all your reply. one more question in my case what would be the default gateway for vm inter gi0/0 ip or esx ip Regards kshitij -- To respond to this post, please click the following link: or simply reply to this email.

RE: Vm can not ping default gateway

2012-03-15T19:51:05Z

Hi Radhika, Thanks for all your reply. one more question in my case what would be the default gateway for vm inter gi0/0 ip or esx ip Regards kshitij

RE: New Message from Charlie Jones in Service Ready Engine Virtualization -

2012-03-15T19:44:58Z

Ok one thing I fort got mention is that by default the vmnetwork port group is configured to get traffic from vlan 1 can you edit the properties of the port group from vsphere client to port 100. You can do this by following steps: 1) Login to vSphere client 2) Select the ESXI host 3) Select the Configuration tab -> then select networking. 4) In the networking screen select the Vm netwok port group in vswitch 1-> edit properties. 5) You should be able to change the vlan id here. Thanks, Radhika From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 15, 2012 11:32 AM To: cdicuser@developer.cisco.com Subject: New Message from Charlie Jones in Service Ready Engine Virtualization - SRE-V Technical Questions: RE: Vm can not ping default gateway Charlie Jones has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- Sorry, I didn't do a show run to see that the configuration change stayed part of the configuration. Below is the current configuration, and when I try to ping the DG, I get destination host unreachable. The server config is the following: IP - 10.191.100.20/24, DG is 10.191.100.1 interface GigabitEthernet0/0 no ip address ip nbar protocol-discovery ip flow ingress duplex full speed 100 no snmp trap link-status interface GigabitEthernet0/0.100 encapsulation dot1Q 100 ip address 10.191.100.1 255.255.255.0 ip helper-address 10.172.1.242 ip flow ingress interface SM1/0 ip unnumbered GigabitEthernet0/0.100 service-module ip address 10.191.100.5 255.255.255.0 !Application: VMware ESXi 5.0.0 build-474610 running on SRE service-module ip default-gateway 10.191.100.1 ! interface SM1/1 description Internal switch interface connected to Service Module switchport mode trunk no ip address ! interface Vlan1 no ip address ! interface Vlan100 ip unnumbered GigabitEthernet0/0 ! ! ip route 0.0.0.0 0.0.0.0 10.191.100.2 ip route 10.191.100.5 255.255.255.255 SM1/0 ip route 10.191.100.20 255.255.255.255 Vlan100 -- To respond to this post, please click the following link: or simply reply to this email.

RE: Vm can not ping default gateway

2012-03-15T19:32:05Z

Sorry, I didn't do a show run to see that the configuration change stayed part of the configuration. Below is the current configuration, and when I try to ping the DG, I get destination host unreachable. The server config is the following: IP - 10.191.100.20/24, DG is 10.191.100.1 interface GigabitEthernet0/0 no ip address ip nbar protocol-discovery ip flow ingress duplex full speed 100 no snmp trap link-status interface GigabitEthernet0/0.100 encapsulation dot1Q 100 ip address 10.191.100.1 255.255.255.0 ip helper-address 10.172.1.242 ip flow ingress interface SM1/0 ip unnumbered GigabitEthernet0/0.100 service-module ip address 10.191.100.5 255.255.255.0 !Application: VMware ESXi 5.0.0 build-474610 running on SRE service-module ip default-gateway 10.191.100.1 ! interface SM1/1 description Internal switch interface connected to Service Module switchport mode trunk no ip address ! interface Vlan1 no ip address ! interface Vlan100 ip unnumbered GigabitEthernet0/0 ! ! ip route 0.0.0.0 0.0.0.0 10.191.100.2 ip route 10.191.100.5 255.255.255.255 SM1/0 ip route 10.191.100.20 255.255.255.255 Vlan100

RE: New Message from Charlie Jones in Service Ready Engine Virtualization -

2012-03-15T19:17:58Z

Yes the warning is expected for ip unnumbered as some the benefits of vlan creation are lost by doing the ip unnumbered configuration. From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 15, 2012 11:13 AM To: cdicuser@developer.cisco.com Subject: New Message from Charlie Jones in Service Ready Engine Virtualization - SRE-V Technical Questions: RE: Vm can not ping default gateway Charlie Jones has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- What I am trying to accomplish is to have the server IP be in the same subnet as our users subnet (10.191.100.x/24). What you said makes sense to me, however when I tried to set interface VLAN 100 to ip unnumbered GI0/0.100, I receive the following error message. Warning: dynamic routing protocols will not work on SVI interfaces with IP unnumbered configured. -- To respond to this post, please click the following link: or simply reply to this email.

RE: New Message from Kshitij Purwar in Service Ready Engine Virtualization

2012-03-15T19:16:58Z

Hi Kshitij, You can use the example below to configure vlan in the same subnet interface vlan 100 ip unnumbered GigabitEthernet0/0 ip route 10.19.100.12 255.255.255.255 vlan100 à where 10.191.100.12 is the ip address of your VM if you want to create a new port group under vsiwtch 0 and move the Vm there please see http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-networking-guide.pdf page 15 Add a Virtual Machine Port Group Thanks, Radhika From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 15, 2012 11:08 AM To: cdicuser@developer.cisco.com Subject: New Message from Kshitij Purwar in Service Ready Engine Virtualization - SRE-V Technical Questions: RE: Vm can not ping default gateway Kshitij Purwar has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- Hi, I canot configure vlan with same subnet,because gi0/0 has been configured the same subnet IP and we dont have any other subnet for configure. can you please tell me what would be the deafult gateway and default route for vM. Please also let me know how to configure port group and how to move VM to this port group. Regards kshitij -- To respond to this post, please click the following link: or simply reply to this email.

RE: Vm can not ping default gateway

2012-03-15T19:13:03Z

What I am trying to accomplish is to have the server IP be in the same subnet as our users subnet (10.191.100.x/24). What you said makes sense to me, however when I tried to set interface VLAN 100 to ip unnumbered GI0/0.100, I receive the following error message. Warning: dynamic routing protocols will not work on SVI interfaces with IP unnumbered configured.

RE: Vm can not ping default gateway

2012-03-15T19:07:40Z

Hi, I canot configure vlan with same subnet,because gi0/0 has been configured the same subnet IP and we dont have any other subnet for configure. can you please tell me what would be the deafult gateway and default route for vM. Please also let me know how to configure port group and how to move VM to this port group. Regards kshitij

RE: New Message from Charlie Jones in Service Ready Engine Virtualization -

2012-03-15T19:02:58Z

Charlie, If I understand what you are saying correctly you can not create a vlan 100 and give it same subnet as your DG but you can increate vlan 100 and have ip unnumbered to the interface the DG is on. Then add a ip route for the ip address you assign to the VM and point it to vlan100 Example interface vlan 100 ip unnumbered GigabitEthernet0/0.100 ip route 10.191.100.11 255.255.255.255 vlan100 à where 10.191.100.11 is the ip address of your VM Hope this helps. Thanks, Radhika From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 15, 2012 10:55 AM To: cdicuser@developer.cisco.com Subject: New Message from Charlie Jones in Service Ready Engine Virtualization - SRE-V Technical Questions: RE: Vm can not ping default gateway Charlie Jones has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- So with the configuration I have, do I just need to create a vlan 100 (which is the same as my DG, and the same subnet that my VM will be in.)? If that is the case, do I just need to give it any IP address in that same subnet (10.191.100.x/24)? -- To respond to this post, please click the following link: or simply reply to this email.

RE: Vm can not ping default gateway

2012-03-15T18:54:45Z

So with the configuration I have, do I just need to create a vlan 100 (which is the same as my DG, and the same subnet that my VM will be in.)? If that is the case, do I just need to give it any IP address in that same subnet (10.191.100.x/24)?

RE: New Message from Charlie Jones in Service Ready Engine Virtualization -

2012-03-15T18:49:58Z

Hi Charlie, Vswitch 0 is connected to inter sm 1/0 and vswitch 1 is connected to interface sm 1/1 ( need to configure vlan ). If the VM is in vsiwtch 1 (default vmport group) you need to configure the vlan 1. Please take a look at that the document http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/sre_v/2.0/user/guide/vsphere.html#wp1081138 section Networking Prerequisites for Creating Virtual Machines This section has an example of configuring networking for the VM when the VM is in vswitch 1. Thanks, Radhika From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Thursday, March 15, 2012 10:42 AM To: cdicuser@developer.cisco.com Subject: New Message from Charlie Jones in Service Ready Engine Virtualization - SRE-V Technical Questions: RE: Vm can not ping default gateway Charlie Jones has created a new message in the forum "SRE-V Technical Questions": -------------------------------------------------------------- I have the same issue. Below is my configuration, at least the pertinent info for the SRE. You mention that vlan1 needs to be configured. Can that be any IP in the same subnet as my gi0/0.100 interface? On the same note as Kshitij, when I go into V-sphere, I have two switches Vswitch0 and Vswitch1. Vswitch0 is the mgmt, and vswitch1 is where my VM is. Just looking at the configuration, do these switches need to show up as connected? Or does my VM need to be on Vswitch0? interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 no ip address ip nbar protocol-discovery ip flow ingress duplex full speed 100 no snmp trap link-status ! interface GigabitEthernet0/0.100 encapsulation dot1Q 100 ip address 10.191.100.1 255.255.255.0 ip helper-address 10.172.1.242 ip flow ingress interface SM1/0 ip unnumbered GigabitEthernet0/0.100 service-module ip address 10.191.100.5 255.255.255.0 !Application: VMware ESXi 5.0.0 build-474610 running on SRE service-module ip default-gateway 10.191.100.1 ! interface SM1/1 description Internal switch interface connected to Service Module switchport mode trunk no ip address ip route 0.0.0.0 0.0.0.0 10.191.100.2 ip route 10.191.100.5 255.255.255.255 SM1/0 ip route 10.191.100.10 255.255.255.255 SM1/0 -- To respond to this post, please click the following link: or simply reply to this email.

RE: Vm can not ping default gateway

2012-03-15T18:42:29Z

I have the same issue. Below is my configuration, at least the pertinent info for the SRE. You mention that vlan1 needs to be configured. Can that be any IP in the same subnet as my gi0/0.100 interface? On the same note as Kshitij, when I go into V-sphere, I have two switches Vswitch0 and Vswitch1. Vswitch0 is the mgmt, and vswitch1 is where my VM is. Just looking at the configuration, do these switches need to show up as connected? Or does my VM need to be on Vswitch0? interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 no ip address ip nbar protocol-discovery ip flow ingress duplex full speed 100 no snmp trap link-status ! interface GigabitEthernet0/0.100 encapsulation dot1Q 100 ip address 10.191.100.1 255.255.255.0 ip helper-address 10.172.1.242 ip flow ingress interface SM1/0 ip unnumbered GigabitEthernet0/0.100 service-module ip address 10.191.100.5 255.255.255.0 !Application: VMware ESXi 5.0.0 build-474610 running on SRE service-module ip default-gateway 10.191.100.1 ! interface SM1/1 description Internal switch interface connected to Service Module switchport mode trunk no ip address ip route 0.0.0.0 0.0.0.0 10.191.100.2 ip route 10.191.100.5 255.255.255.255 SM1/0 ip route 10.191.100.10 255.255.255.255 SM1/0