The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
When you connect the C-Series servers in Cisco UCS system, make sure to review the following information:
The C-Series UCSM integration requires six 10-Gb SFP cables for the following purposes:
Linking the data traffic paths between server and 2232PP FEX - 2 cables
Uplinks from the 2232PP FEXes to the FIs - 4 cables
Each of the four uplinks from the FEXes to the FIs can use either a Cisco 10-Gb twinax cable, or one of the following SFP types:
Caution | Do not mix SFP types on an uplink. If you mix SFP types on an uplink, you will get Discovery failed errors. |
If your server CIMC release version does not meet the requirement for integration with Cisco UCS Manager, make sure to upgrade the server firmware before connecting the server with Cisco UCS domain. For more information on upgrading the C-Series server firmware, see the host upgrade utility quick start guide for your release http://www.cisco.com/en/US/products/ps10493/products_user_guide_list.html
After upgrading the server to the compatible server release version, you must establish the physical connection for the server to make it a part of Cisco UCS domain.To connect the server to your Cisco UCS FEXes and FIs, see Connecting the C-Series Server with Cisco UCS Domain in Cluster Setup.
Using the power button or Cisco UCS Manager, if you set the desired power status to Down for an integrated C-Series server's associated service profile, when you try to rest the server to the desired power state, the server becomes out of sync with the actual power state. This may cause the server to shut down unexpectedly at a later time.
Use the Boot Server action in Cisco UCS Manager to safely reboot a server from a power-down state.
The following table shows how the physical server power states can differ from the Cisco UCS Manager service profile power states when the power button on the server is used.
Initial Service Profile Power State |
Server Initial Power State |
Action From Physical Power Button |
Actual Server Power State After the Action |
Power State Under UCSM Equipment Tab |
Desired Power State Under Service Profile |
---|---|---|---|---|---|
Down |
Off |
Push button to turn on |
On |
On |
Down |
Up |
On |
Push button to turn off |
Off |
Off |
Up |
Make sure to consider the following when using the adapter cards in Cisco UCS C-Series server integration with Cisco UCS Manager:
Cisco UCS Manager supports only four UCS managed adapter cards in the integrated Cisco UCS C-series servers, even if the server has more than four PCI slots. If you have more than four adapter cards in the server, after integration, the rack server discovery fails in Cisco UCS Manager.
When you add, remove, or replace an adapter card in a UCS-managed server, you must first decommission the server in Cisco UCS Manager. After the operation, you must then recommission the server.
If an integrated server contains two Cisco UCS P81E Virtual Interface Cards, the vNICs/vHBAs on Adapter 1 might have a higher PCI order in Cisco UCS Manager than the vNICs/vHBAs on Adapter 2.
Acknowledged Links between 2232PP FEX and FI |
Maximum vNIC+vHBA for VIC adapter with 6100 FI |
Maximum vNIC+vHBA for VIC adapter with 6200 FI |
---|---|---|
1 |
1 |
13 |
2 |
4 |
28 |
4 |
10 |
58 |
8 |
22 |
118 |
Note | The available vNIC can be failover or non-failover vNIC. |
In C200 or C210 servers, BIOS version 1.4(3c) and later, you have an option to enable or disable SR-IOV/ARI (single-root I/O virtualization/alternative routing-ID interpretation) bus reservation. Whenever you change the SR-IOV/ARI bus reservation settings on a UCS-managed server, you must re-acknowledge the server.
Whenever you decommission or recommission a Cisco UCS 2232PP FEX, all the servers that are connected to that FEX must be re-acknowledged in UCS Manager.