Cisco UCS C-Series Server Integration with Cisco UCS Manager 2.0(2) and 2.0(3)
Cisco UCS C-Series Integration with Cisco UCS Manager
Downloads: This chapterpdf (PDF - 2.06MB) The complete bookPDF (PDF - 2.98MB) | The complete bookePub (ePub - 646.0KB) | Feedback

Cisco UCS C-Series Integration with Cisco UCS Manager

Cisco UCS C-Series Integration with Cisco UCS Manager

This chapter includes the following sections:

Overview

This guide contains information and procedures for installing Cisco UCS Rack Mount Servers releases 1.4.3c, 1.4.4a and 1.4.5d for integration with Cisco UCS Manager release 2.0.2(2).

Cisco UCS C-Series Rack-Mount Servers are managed by the built-in standalone software, Cisco Integrated Management Controller (CIMC) . When a C-Series Rack-Mount Server is integrated with Cisco UCS Manager, the CIMC does not manage the server anymore. Instead it is managed with the Cisco UCS Manager software. You will manage the server using the Cisco UCS Manager GUI or Cisco UCS Manager CLI.

Important:

If your server is not factory new, make sure to reset the server to factory default settings before integrating the server with Cisco UCS Manager.

You can integrate Cisco UCS C-Series Rack-Mount Servers with Cisco UCS Manager in either one of the following setup:

  • Cluster setup: Using two fabric extenders (FEXes) to connect the C-Series Rack-Mount Server with two fabric interconnects.
  • Non-cluster setup: Connecting the C-Series Rack-Mount Server with one FEX and one FI.

Integrating Release 1.4.3c or 1.4.4a or 1.4.5d Servers with Cisco UCS Manager 2.0(2) and 2.0(3)

The prerequisites for integration with Cisco UCS Manager are built into the C-Series Rack-Mount Server releases 1.4.3c, 1.4.4a and 1.4.5d. You can connect them to the Cisco UCS Manager 2.0.2 domain immediately. If your server is at a release that does not support integration with Cisco UCS Manager 2.0.2 or 2.0.3 , you must upgrade your server to the required release level for integration. For more information on required server CIMC version, see Required Items for Integration with Cisco UCS Manager 2.0(2) and 2.0(3). For more information on upgrading the CIMC release for integration, see Upgrading and Connection Procedures.

See the following URLs for additional information about the equipment in this configuration.

For information about the Cisco UCS 6100 Series or 6200 Series fabric interconnects (FIs) in the configuration, see the documentation at the following links:

For information about the Cisco Nexus 2232PP fabric extenders (FEXes) in the configuration, see the documentation at the following link:

Cisco Nexus 2000 Series Fabric Extender documentation

Required Items for Integration with Cisco UCS Manager 2.0(2) and 2.0(3)

The following are the required items for C-Series server CIMC versions 1.4.3c, 1.4.4a, 1.4.5d to be integration with Cisco UCS Manager versions 2.0.2 and 2.0(2):

Note


The hardware configuration will contain redundant network fabrics and paths for both management traffic and data traffic.


  • A Cisco UCS system running Cisco UCS Manager software release 2.0(2) or 2.0(3).
  • Any of the Cisco UCS C-Series servers and corresponding Cisco UCS Manager release version:

    Server

    CIMC Version

    Minimum UCS Manager Version

    Cisco UCS C22 M3 Server

    1.4.5d

    2.0(3)

    Cisco UCS C24 M3 Server

    1.4.5d

    2.0(3)

    Cisco UCS C200 M2 Server

    1.4.3c

    2.0(2)

    Cisco UCS C210 M2 Server

    1.4.3c

    2.0(2)

    Cisco UCS C220 M3 Server

    1.4.4a

    2.0(2)

    Cisco UCS C240 M3 Server

    1.4.4a

    2.0(2)

    Cisco UCS C250 M2 Server

    1.4.3c

    2.0(2)

    Cisco UCS C260 M2 Server

    1.4.3c

    2.0(2)

    Cisco UCS C460 M2 Server

    1.4.3c

    2.0(2)


    Note


    • When the Cisco UCS C-Series server is discovered, check if the firmware package is at the required level for the Cisco UCS Manager version. If not, you must update or downgrade to the required firmware level.
    • If you install Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), and want to use this card for UCS integration, the minimum card-firmware level requirement is 2.0(2g). See the section on Special Considerations for the Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), in Install and Upgrade Guides.

  • Two Cisco UCS 6100 Series or 6200 Series FIs. The switch ports that carry server traffic must be enabled as server ports.
  • Two Cisco Nexus 2232PP FEXes.

    Note


    • Cisco UCS Manager releases 2.0.2 and after support only Cisco Nexus 2232PP FEXes. If you have Cisco Nexus 2248 FEX, you must migrate to Cisco Nexus 2232PP FEX.
    • You must plug a power cord into each of the two power supplies in the FEX. If a power is connected and there are issues in the hardware, you might see “Major” faults reported during power-on self test (POST). For example, you might see this error: Power supply 1 in fex 6 power: error. You can clear these errors by connecting the missing power cord to the FEX power supply.

  • Two RJ-45 Ethernet cables.
  • Six 10-Gb SFP cables.

    Note


    • Two cables for linking the data traffic path between server and FEX.
    • Four cables for uplinks from FEX to fabric interconnects. Each of these four cables used for uplink from FEX to FIs can either use supported 10-gb twinaxial cable or one of the following SFP type cables:
      • SFP - 10GE-SR
      • FET - 10GE

    Important:

    Do not mix SFP types on an uplink. If you mix the SFP types on an uplink, you will see Discovery Failed errors.

  • Two 1000BASE-T SFP transceivers (GLC-T)

FEX Connection Mode and Discovery

You can connect the FEX to the FI in two ways. Cisco UCS Manager FI discovers the FEX based on the connection mode. The FEX connection modes are:

  • Hard-Pinning mode: The server facing FEX ports are pinned to the connected uplink ports when the FEX is discovered. Cisco UCS Manager pins the server-facing ports to the uplink ports based on the number of acknowledged uplink ports. After the pinning, if you add a new uplink or delete an existing uplink, you must manually acknowledge the FEX to apply the changes.
  • Port-Channel mode: Port-Channel mode does not have pinning. A single port channel works as the uplink to all server-facing ports. And all uplink ports are members of this single port channel. If one of the uplink ports go down, the traffic is automatically distributed to another available uplink port.

Note


These connection modes apply only to the 6200 series FIs.


In port-channel mode, when you cable between FEX and the FI, the available virtual interface (VIF) namespace varies, depending on where the uplinks are connected to the FI ports:
  • When port-channel uplinks from the FEX are connected only within a set of eight ports managed by a single chip, Cisco UCS Manager maximizes the number of VIFs used in service profiles deployed on the servers.
  • If uplink connections are distributed across ports managed by separate chips, the VIF count is decreased. For example (see Figure), if you connect seven members of the port channel to ports 1–7, but the eighth member to port 9, this port channel can only support VIFs as though it had one member.

The Cisco UCS 6200 Series FI has six sets of eight contiguous ports. Each set of ports is managed by a single chip. For more information on FEX discovery policies and port-channel allocation, see the Cisco UCS Manager Configuration Guide, Release 2.0 or later.

Figure 1. Six Sets of Ports in Fabric Interconnect and Expansion Module

Maximum Configurable vNICs/vHBAs Based on Number of FEX Uplinks

The following table describes maximum configurable vNICs/vHBAs based on number of FEX uplinks:

Table 1 Cisco UCS 6100 Fabric Interconnect

Acknowledged link between FEX and FI

Maximum configurable vNICs/vHBA per VIC adapter

1

Not supported

2

4

4

10

8

22

Table 2 Cisco UCS 6200 Fabric Interconnect

Acknowledged link between FEX and FI

Maximum configurable vNICs/vHBA per VIC adapter

1

13

2

28

4

58

8

118


Note


For a non-VIC adapter the maximum number of vNICs are 2 and the maximum number of vHBAs are 2.


Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup

Before connecting the server with the Cisco UCS domain, make sure you have the recommended card-firmware level for the integration. The card-firmware level for Cisco UCS P81E Virtual Interface Card must be a minimum 2.0(2g) for the integration. If you do not have this card-firmware level, update the server firmware in stand alone mode before the integration. If you connect a card with earlier firmware version to Cisco UCS Manager 2.0(2x), during the discovery process, you will get discovery and association/disassociation failures. If you encounter these problems, see the upgrade procedure and upgrade the card firmware level.

To view illustrations on the connectivity for each C-Series Rack-Mount Server, see Physical Connectivity Illustrations for Cluster Setup.

Important:

Make sure the server CIMC is set to factory default settings to integrate with Cisco UCS Manager.

Procedure
    Step 1   Install the server in the rack. See the Install and Upgrade Guide for the server that you are using. The install guides are available at the following url: Install and Upgrade Guides.
    Step 2   To connect the management traffic paths, do the following:
    1. Insert one GLC-T transceiver into a port of the FEX that is connected to Fabric A. You can use any port on the FEX.
    2. Insert one GLC-T transceiver into a port of the FEX that is connected to Fabric B. You can use any port on the FEX.
    3. Connect an RJ-45 Ethernet cable between a 1-Gb port on the rear panel of the server and the transceiver that you inserted into the FEX in Fabric A.
    4. Connect an RJ-45 Ethernet cable between a 1-Gb port on the rear panel of the server and the transceiver that you inserted into the FEX in Fabric B.
    Step 3   To connect the data traffic paths, do the following:
    1. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on a FEX in Fabric A. You can use any port on the FEX.
    2. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on a FEX in Fabric B. You can use any port on the FEX.
    Step 4   Connect the paths from the FEXes to the FIs. These paths carry both data and management traffic.
    1. Connect two 10-Gb SFP cables between FEX A and two ports on FI A. You can use any ports on FI A, but the ports must be enabled for server traffic.
    2. Connect two 10-Gb SFP cables between FEX B and two ports on FI B. You can use any ports on FI B, but the ports must be enabled for server traffic.
      Note   
      • On the FEX, you can use only the right block of eight ports for uplinks.
      • The maximum number of uplinks is eight. Based on the Cisco UCS Manager FI discovery policy the port cabling requirement between the FEX and FI vary.
      • Do not mix SFP types on an uplink. If you do, you will see Discovery Failed errors.
    Step 5   Attach a power cord to each power supply in your server, and then attach the power cord to a grounded AC power outlet.
    Step 6   Reboot the server.
    Step 7   To view and configure settings for the server from within the Cisco UCS Manager software, see the information and instructions in the Cisco UCS Manager Configuration Guide for Release 2.0.

    Physical Connectivity Illustrations for Cluster Setup

    The following images shows the physical connectivity for each C-Series Rack-Mount Server with Cisco UCS Domain, Cisco UCS Manager, release 2.0(2) or 2.0(3).

    The following image show the cabling configuration for Cisco UCS Manager integration with the C22 M3 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 2. Cisco UCS C22 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C22 M3 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot 1

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    The following image show the cabling configuration for Cisco UCS Manager integration with the C24 M3 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 3. Cisco UCS C24 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C24 M3 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot 1

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    The following image show the cabling configuration for Cisco UCS Manager integration with the C200 M2 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 4. Cisco UCS C200 M2 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C200 M2 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot 6

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    The following image show the cabling configuration for Cisco UCS Manager integration with the C210 M2 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 5. Cisco UCS C210 M2 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C210 M2 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot 1

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    The following image show the cabling configuration for Cisco UCS Manager integration with the C220 M3 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 6. Cisco UCS C220 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C220 M3 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot 1

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    The following image show the cabling configuration for Cisco UCS Manager integration with the C240 M3 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 7. Cisco UCS C240 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C240 M3 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot 1

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    The following image show the cabling configuration for Cisco UCS Manager integration with the C250 M2 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 8. Cisco UCS C250 M2 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C250 M2 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot D

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    The following image show the cabling configuration for Cisco UCS Manager integration with the C260 M2 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 9. Cisco UCS C260 M2 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C260 M2 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot 1

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    The following image show the cabling configuration for Cisco UCS Manager integration with the C460 M2 server. The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.

    Figure 10. Cisco UCS C460 M2 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    6

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    GLC-T transceiver in FEX port (Fabric A)

    7

    Cisco UCS C460 M2 server

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    8

    1-Gb Ethernet LOM ports

    4

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    9

    10-Gb Adapter card in PCIe slot 1

    5

    GLC-T transceiver in FEX port (Fabric B)

    -

    -

    Managing the Rack-Mount Server in Cisco UCS Manager after Integration

    You can manage and monitor all rack-mount servers that have been integrated with a Cisco UCS domain through Cisco UCS Manager. After the integration, you will perform all rack-mount server management tasks only through the service profiles from Cisco UCS Manager GUI or Cisco UCS Manager CLI. The C-Series Rack-Mount Server CIMC is not accessible when you start managing the server with Cisco UCS Manager.

    Cisco UCS Manager provides information, errors, and faults for each rack-mount server that it has discovered.

    For more information on managing C-Series Rack-Mount Servers from Cisco UCS Manager, see the chapter on Managing Rack-Mount Servers in your release specific Cisco UCS Manager GUI Configuration Guide.

    Reverting a Server From Cisco UCS Domain Mode to Standalone Mode

    When you manage a Cisco UCS C-Series server with Cisco UCS Manager software, a UCS Manager service profile is associated with the server. If you want to revert a C-Series server to standalone mode (so that it can be managed by CIMC software), you must do the following actions in UCS Manager:

    Procedure
      Step 1   Disassociate the UCS Manager service profile from the server.
      Step 2   Decommission the server.
      Caution   

      If you do not disassociate the service profile from the server, MAC and WWN numbers assigned by UCS Manager might be kept by the server. This can cause numbering duplication and conflicts with other servers that are managed by UCS Manager. Also, if you revert a server to standalone mode without disassociating its service profile, any LSI RAID controller will not show as a bootable device in the standalone server, preventing local booting.