Getting Started Guide for Cisco UCS E-Series Servers, Release 1.0
Configuration Differences Between Cisco SRE-V and E-Series Server
Downloads: This chapterpdf (PDF - 392.0KB) The complete bookPDF (PDF - 3.66MB) | Feedback

Configuration Differences Between Cisco SRE-V and E-Series Server

Configuration Differences Between Cisco SRE-V and E-Series Server

The Cisco Services Ready Engine Virtualization (Cisco SRE-V) and the E-Series Server have two major configuration differences:

  • Differences in router configuration.
  • Differences in VMware vSphere Hypervisor™ configuration.

This chapter includes the following sections:

Router Configuration Differences

The examples in the following table provide the key differences between the Cisco SRE-V and the E-Series Server configuration.

Table 1  Differences in Router Configuration Between the Cisco SRE-V and the E-Series Server

Cisco SRE-V Configuration

Cisco E-Series Server Configuration

GigabitEthernet0/0
10.0.0.1 255.0.0.0

sm 1/0
ip unnumbered GigabitEthernet0/0
service-module ip address 10.0.0.2 255.0.0.0
service-module ip default-gateway 10.0.0.1


interface SM1/1
 switchport mode trunk

ip route 10.0.0.2 255.255.255.255 sm1/0
GigabitEthernet0/0
10.0.0.1 255.0.0.0

ucse 1/0
ip unnumbered GigabitEthernet0/0
imc ip address 10.0.0.2 255.0.0.0 default-gateway 10.0.0.1
imc access-port shared-lom console


interface ucse1/1
 switchport mode trunk

ip route 10.0.0.2 255.255.255.255 ucse1/0

Note the following differences:

  • In the E-Series Server, the sm slot/port command is replaced by the ucse slot/port command.
  • In the E-Series Server, the service-module keyword is replaced by the imc keyword.
  • In the E-Series Server, the default gateway command resides in the same command as the imc ip address command.
  • Since the E-Series Server has different external interfaces, you must specify the access port using the imc access-port command.
  • In the E-Series Server, you can either use the dedicated interface or one of the shared local area network on motherboard (shared LOM) interfaces to configure CIMC access. See Configuring CIMC Access. In the above example, the imc access-port shared-lom console command uses the console interface for CIMC access, where:
    • imc access-port—is the physical Ethernet connection to the E-Series Server.
    • shared-lom—is shared LOM.
    • console—is the router interface.

The command to session into the server has also changed:

  • Cisco SRE-V uses the service-module sm slot/0 session command to session into the server.
  • E-Series Server uses the ucse slot session {imc | host} command to session into the server.

VMware vSphere Hypervisor Configuration Differences

In Cisco SRE-V, the IP address of the VMware vSphere Hypervisor™ host is the same as the IP address of the service module. For example, in Cisco SRE-V, the service-module ip address 10.0.0.2 (see next table) is also assigned to the VMware vSphere Hypervisor™ host.

Table 2  Differences in Router Configuration Between the Cisco SRE-V and the E-Series Server

Cisco SRE-V Configuration

Cisco E-Series Server Configuration

GigabitEthernet0/0
10.0.0.1 255.0.0.0

sm 1/0
ip unnumbered GigabitEthernet0/0
service-module ip address 10.0.0.2 255.0.0.0
service-module ip default-gateway 10.0.0.1


interface SM1/1
 switchport mode trunk

ip route 10.0.0.2 255.255.255.255 sm1/0
GigabitEthernet0/0
10.0.0.1 255.0.0.0

ucse 1/0
ip unnumbered GigabitEthernet0/0
imc ip address 10.0.0.2 255.0.0.0 default-gateway 10.0.0.1
imc access-port shared-lom console


interface ucse1/1
 switchport mode trunk

ip route 10.0.0.2 255.255.255.255 ucse1/0

However, with the E-Series Server, the imc ip address, which is also 10.0.0.2 (see the example above), is reserved for CIMC access. You enter this IP address (10.0.0.2) on your web browser to access the CIMC GUI.

In the E-Series Server, either the VMware vSphere Hypervisor™ assigns an IP address to the host using DHCP, or you can choose to assign a static IP address to the VMware vSphere Hypervisor™ host. See Assigning a Static IP Address to the VMware vSphere Hypervisor.