Cisco UCS C-Series Server Integration with Cisco UCS Manager 2.1
Configuring Single-Wire Management
Downloads: This chapterpdf (PDF - 1.83MB) The complete bookPDF (PDF - 3.63MB) | The complete bookePub (ePub - 1.04MB) | Feedback

Configuring SingleConnect

Configuring SingleConnect

This chapter includes the following sections:

SingleConnect

Cisco UCS Manager 2.1 supports an option to integrate the C-Series Rack-Mount Server with Cisco UCS Manager using the NC-SI. This option enables Cisco UCS Manager to manage the C-Series Rack-Mount Servers using a single cable for both management traffic and data traffic. When you use the SingleConnect mode, one host facing port on the FEX is sufficient to manage one rack-mount server, instead of the two ports you will use in the Shared-LOM mode. So you can connect more number of rack-mount servers with Cisco UCS Manager for integrated server management. Make sure you have correct server firmware for integration with Cisco UCS Manager. If not, upgrade your server firmware before integrating the server with Cisco UCS Manager. See Upgrading the C-Series Server Firmware.


Note


C-Series Rack-Mount Servers C200, C210, and C250 do not support SingleConnect.


Important Guidelines for SingleConnect

SingleConnect has the following guidelines and limitations:

  • To enable SingleConnect for the Cisco UCS Manager integration you must have the Cisco UCS VIC1225 installed in the specific slot assigned for SingleConnect in the rack server. If the VIC is not in the specific slot, SingleConnect does not work.
    Important:

    VIC 1225 refers specifically to UCSC-PCIE-CSC-02.

  • The Cisco UCS VIC1225 also supports dual-wire management. If you have the Cisco UCS 1225 VIC installed, you can select either SingleConnect or dual-wire management as your connection option.

Management Connection Policy and Connection Mode

When establishing the physical connection for the C-Series Rack-Mount Server in the Cisco UCS Domain, you must specify the connection mode and management policy in Cisco UCS Manager GUI or Cisco UCS Manager CLI. The management policy is global to all connected C-Series Rack-Mount Servers. The connection mode determines the rack server discovery in Cisco UCS Manager.

You can specify either one of the following connection policies for the rack servers:

  • Auto-acknowledged: This is the recommended and default connection mode for the C-Series Rack-Mount Server. If the connection mode is auto-acknowledged, immediately after establishing the physical connection, Cisco UCS Manager discovers the rack server and starts managing the server based on the specified management policy.
  • User-acknowledged: If the connection mode is user-acknowledged, after establishing the physical connection, you must manually acknowledge the connection and specify the connection mode in the Cisco UCS Manager GUI or Cisco UCS Manager CLI to begin the discovery. Cisco UCS Manager does not begin the C-Series Rack-Mount Server discovery until you specify the connection mode.

Note


When rack servers are discovered and are managed by Cisco UCS Manager, if you want to change the existing connection mode for one C-Series Rack-Mount Server , you have to decommission the server, re-commission it and specify the new connection mode. Only then Cisco UCS Manager can discover the server in the new connection mode.


Requirements for SingleConnect Integration with Cisco UCS Manager

Requirements for Cluster Setup

You must have the following items to create a single-wire integration for C-Series Rack-Mount Server with Cisco UCS Manager in cluster setup:

  • A Cisco UCS system that is running Cisco UCS Manager release 2.1 and above.
  • Any of the Cisco UCS C-Series servers and corresponding CIMC release versions listed in the following table:
    Table 1 Minimum Required Version of CIMC and BIOS for Single-Wire Integration

    Server

    CIMC

    BIOS

    Cisco UCS C22 M3 Server

    1.4(6)

    1.4.7a

    Cisco UCS C24 M3 Server

    1.4(6)

    1.4.7a

    Cisco UCS C220 M3 Server

    1.4(6)

    1.4.7a

    Cisco UCS C240 M3 Server

    1.4(6)

    1.4.7a

    Cisco UCS C260 M2 Server

    1.4(6)

    1.4.7

    Cisco UCS C420 M3 Server

    1.4(7)

    1.4.8

    Cisco UCS C460 M2 Server

    1.4(6)

    1.4.7

    Important:

    The server must have Cisco UCS VIC1225 installed. The Firmware and Boot Loader versions for Cisco UCS VIC1225 are:

    • Recommended — 2.1(0.457a)
    • Minimum required — 2.1(0.367e)

    VIC 1225 refers specifically to UCSC-PCIE-CSC-02.

    The Cisco UCS VIC1225 must be installed in the correct slot in each server as mentioned in the following table:

    Table 2 Cisco UCS VIC1225 Slot for Single-wire Integration

    Server

    PCIe Slot

    Cisco UCS C22 M3 Server

    1

    Cisco UCS C24 M3 Server

    1

    Cisco UCS C220 M3 Server

    1

    Cisco UCS C240 M3 Server

    2

    Cisco UCS C260 M2 Server

    7

    Cisco UCS C420 M3 Server

    4

    Cisco UCS C460 M2 Server

    1

  • Two Cisco UCS 6100 Series or 6200 Series FIs. The switch ports where Fabric Extenders (FEX) will be connected must be marked as server ports.
  • Two Cisco Nexus 2232PP FEXes.

    Note


    You must plug a power cord into each of the two power supplies in the FEX. If the power is connected and there are issues in the hardware, you might see “Major” faults reported during the power-on self test (POST). For example, you might see this error: Power supply 1 in fex 6 power: error. You can clear errors by connecting any missing power cord to the FEX power supply.


  • Four 10-Gb Small Form-Factor Pluggable (SFP) cables.

    Note


    • At least one cable to connect each FEX with corresponding FI.
    • At least two cables to link the data traffic path between server and FEX.
    • If you are using 6100 Series FI, you require two cables to connect each FEX to corresponding FI.
    • At least four cables for uplinks from the FEX to FIs. You can either use 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.

Requirement for Non-cluster Setup

If you are integrating the server in a non-cluster setup, along with the Cisco UCS Manager and C-series rack mount server, you will need the following components :

  • One Cisco UCS 6100 Series or 6200 Series FIs. The switch ports where Fabric Extenders (FEX) will be connected must be marked as server ports.
  • One Cisco Nexus 2232PP FEXes.
  • Three 10-Gb SFP cables.

    Note


    • If you are using 6200 Series FI, the minimum requirement for SFP cable is 2.
    • At least one cable for linking the data traffic path between server and FEX.
    • At least two cables for uplinks from the FEX to FIs. Each of these two cables used for uplink from the FEX to FIs can either use 10-gb twinaxial cable or one of the following Small Form-Factor Pluggable (SFP) type cables:
      • SFP - 10GE-SR
      • FET - 10GE

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

Before you connect the server, make sure the Cisco UCS VIC1225 is installed in the correct slot for integration with Cisco UCS Manager. If the card is not installed in the correct slot, you cannot enable the single-wire management for the server.

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   Connect the path that carries both data traffic and management traffic to the FEXes:
    1. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on the FEX that is connected to 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 the FEX that is connected to Fabric B. You can use any port on the FEX.
    Step 3   Connect the paths from the FEXes to the FIs.
    1. Connect at least 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 at least 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
      • Do not mix SFP types on an uplink. If you do, you will get Discovery Failed errors.
    Step 4   Attach a power cord to each power supply in your server, and then attach the power cord to a grounded AC power outlet.
    Step 5   Reboot the server.

    Physical Connectivity Illustrations for SingleConnect Cluster Setup

    The following images shows SingleConnect physical connectivity for each C-Series Rack-Mount Server with Cisco UCS Domain, Cisco UCS Manager, release 2.1.

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

    Figure 1. Cisco UCS C22 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    4

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    Cisco Nexus 2232PP FEX (Fabric A)

    5

    Cisco UCS C22 M3 server

    3

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    6

    Cisco UCS VIC1225 in PCIe slot 1

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

    Figure 2. Cisco UCS C24 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    4

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    Cisco Nexus 2232PP FEX (Fabric A)

    5

    Cisco UCS C24 M3 server

    3

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    6

    Cisco UCS VIC1225 in PCIe slot 1

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

    Figure 3. Cisco UCS C220 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    5

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    Cisco Nexus 2232PP FEX (Fabric A)

    6

    Cisco UCS C220 M3 server

    3

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    7

    Cisco UCS VIC1225 in PCIe slot 1

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

    Figure 4. Cisco UCS C240 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    4

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    Cisco Nexus 2232PP FEX (Fabric A)

    5

    Cisco UCS C240 M3 server

    3

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    6

    Cisco UCS VIC1225 in PCIe slot 2

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

    Figure 5. Cisco UCS C420 M3 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    4

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    Cisco Nexus 2232PP FEX (Fabric A)

    5

    Cisco UCS C420 M3 server

    3

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    6

    Cisco UCS VIC1225 in PCIe slot 4

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

    Figure 6. Cisco UCS C260 M2 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    4

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    Cisco Nexus 2232PP FEX (Fabric A)

    5

    Cisco UCS C260 M2 server

    3

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    6

    Cisco UCS VIC1225 in PCIe slot 7

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

    Figure 7. Cisco UCS C460 M2 Server



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    4

    Cisco Nexus 2232PP FEX (Fabric B)

    2

    Cisco Nexus 2232PP FEX (Fabric A)

    5

    Cisco UCS C460 M2 server

    3

    Cisco UCS 6100 Series or 6200 FI (Fabric B)

    6

    Cisco UCS VIC1225 in PCIe slot 1

    Connecting the C-Series Server with UCS Domain in Non-cluster Setup

    You will follow the same steps explained in Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup. Instead of connecting two FIs and two FEXes, you will connect only one FI and one FEX.

    Figure 8. Single-wire Non-Cluster Setup Example

    The following illustration is an example of non-cluster setup in single-wire management.



    1

    Cisco UCS 6100 Series or 6200 FI (Fabric A)

    4

    Cisco UCS C-Series server

    2

    Single Connect connection

    5

    Cisco UCS VIC1225 in PCIe slot 1

    3

    Cisco Nexus 2232PP FEX (Fabric A)

    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 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.