Blogs

There are limitations in SRE-V regarding tracking real time hardware events such as the failure of a hard drive. The Service Ready Engine Virtualization platform (SRE-V) has VMware ESXI 5.0 built into the platform which provides virtualization, and SRE-V installs onto the Service Ready Engine (SRE) service module . ESXI utilizes a technology called CIM as well as SNMP with some limitations to track hardware events. SRE-V uses a software RAID developed by Promise and the release implemented d ...Read More

 

SRE-V 2.0.1 leverage VMware vSphere Hypervisor 5.0 to provide full virtualization for virtual machines (VM). Customers utilizing previous releases of Cisco SRE-V must upgrade their licenses in order to use the Cisco SRE-V 2.0 software.

As of January 4, 2012, all new orders for Cisco SRE-V licenses will ship with VMware vSphere Hypervisor 5.0 license activation codes or VMware vSphere Hypervisor 5.0 license keys if the licenses are ordered with the Cisco SRE hardware.
...Read More

 

The recently released Service Ready Engine Virtualization 1.1.1 release adds Raid 0 and Raid 1 support on SM-900 service modules. When installing the SRE-V platform onto the SM-900 service module you may now select from the options of Non-Raid, Raid 0 or Raid 1.
...Read More

 

Upgrading your IOS image on the Integrated Service Router is a relatively straight forward procedure, but with several steps. After the desired IOS image has been downloaded, there are a few pre-upgrade steps that should be taken before upgrading the IOS image on the router. These steps along with the entire upgrade process have been provided below.

The official IOS upgrade documentation is also available here: ...Read More

 

The release of the new Cisco Borderless Network product Service Ready Engine Virtualization (SRE-V), provides the next generation of virtualization functionality for partners desiring to run server applications on the router. Utilizing VMware ESXi as its built-in engine, SRE-V features support of Windows 2003 and 2008 servers on which virtual machines can be created, monitored and maintained via VMware's vSphere client. With this new feature, packaging and porting applications as previous ...Read More

 

Showing 5 results.

Forums

« Back to SRE-V Technical Questions

My VMs (CentOS6.2) residing on two different SRE are unable to talk to each

Combination View Flat View Tree View
toggle
I have two ISR G2 (Cisco3900) routers.
there network domain being 10.104.231.64-79 255.255.255.240
 
my default router is 10.104.231.65
My two ISR G2 have IP assigned as
---10.104.231.71 (ISR G2 )
-------- 10.104.231.74 (SRE module having EXSI 4.1) (its SM 3/0)
--------------10.104.231.75 (VM runing centos 6.2)
---10.104.231.72 (ISR G2 )
-------- 10.104.231.76 (SRE module having EXSI 4.1) (its SM 4/0)
--------------10.104.231.77 (VM runing centos 6.2)
 
(a) The problem is i am unable to ping 10.104.231.75 from outside network.
same thing goes with  10.104.231.77 (unable to ping from outside)
(b) i am able to ping both the ISRs (ip 71 and 72 from outside network)
(c) i am able to ping both the SRE (ip 74 and 76 from outside network)
(d) i am able to ping both the VMs (ip address 75 and 77) from both the ISRs respectively (ip 71 and 72)
(e) i am able to ping SRE (both) and ISR(both) from any of the VMs (ip 75 and 77)
(f) Traceroute (tracert 10.104.231.75) shows i am able to reach upto isr with ip 71 but after that packets get lost.
 
PS:
(1) i have attached the route table of both the ISRs.
(2) i have attached the tracert for vm with ip 75.
(3) i have attached the setup (VM hypervisor) snapshop.
 
Question:-
why i am unable to ping the VM as stated in (a). can somebdy plz point me to what i am missing??
Also is it because i am using the same vmk0 interface??
Attachments:

Hi Himanshu,

If you haven't resolved this issue, it looks to me like your configuration is correct for SM 3/0, but I don't see any ip routes or the configuration for your SM4/0 interface. You'll need to add IP routes for the SM4/0 interface as well.

Thanks,

Brett

Hi Himanshu,

you have to create one more vm network from vswitch0 and add your vm to that network and vm route to sm 4/0.

Regards
Kshitij

Collateral


No files available