Table Of Contents
Installation for Cisco UCS Integration
Integration With Cisco UCS Manager 2.0(2xx) and Later
Integrating a Release 1.4(3c) or Later Server With Cisco UCS Manager 2.0(2xx)
Hard-Pinning Mode and Port-Channel Mode Discovery Policies
Required Items
Procedure
Upgrading a Server Earlier Than Release 1.4(3c) for Cisco UCS Manager 2.0(2) Integration
Required Items
Upgrade and Connection Procedures
Integration With Cisco UCS Manager Earlier Than 2.0(2xx)
Installing a Release 1.2(2xx) Server With Cisco UCS Manager 1.4 or 2.0(1)
Required Items
Procedure
Upgrading a Server Earlier Than Release 1.2(2) For Cisco UCS Manager 1.4 or 2.0(1) Integration
Required Items
Upgrade and Connection Procedures
Migrating an Earlier Configuration to Release 2.0(2xx) or Later
Supported Network Adapter Cards for UCSM Mode
Supported Adapter Cards
Supported Card Combinations
Supported 2232 FEX-to-FI Uplink Cable SFP Types
Reverting a Server From UCSM Mode to Standalone Mode
Special Considerations For Integrated Servers
Updating Cisco UCS P81E VIC Firmware and uboot Image in Integrated Servers
Integrated Server Power States vs. Service Profile Power States
Adapter Card Considerations
FEX Considerations
Installation for Cisco UCS Integration
This appendix contains information and procedures for installing a Cisco UCS C250 server for integration with the Cisco Unified Computing System (UCS).
In this integration, the server is not managed by its standalone Cisco Integrated Management Controller (CIMC) GUI or CLI commands because it is instead managed through the Cisco UCS Manager software.
This appendix contains the following topics:
•
Integration With Cisco UCS Manager 2.0(2xx) and Later
•Integration With Cisco UCS Manager Earlier Than 2.0(2xx)
•Migrating an Earlier Configuration to Release 2.0(2xx) or Later
•Supported Network Adapter Cards for UCSM Mode
•Supported 2232 FEX-to-FI Uplink Cable SFP Types
•Reverting a Server From UCSM Mode to Standalone Mode
•Special Considerations For Integrated Servers
Important Note Regarding Cisco UCS Manager Compatibility and These Instructions
The Cisco UCS C250 M2 server was qualified for integration with an older version of Cisco UCS Manager software. The older version requires different firmware, hardware, and cabling than the most current integration scheme. Instructions for both integration schemes are included in this appendix:
•If your Cisco UCS Manager software is at release 2.0(2xx) or later—your server must use CIMC release 1.4(3c) or later firmware for the Cisco UCS integration. See the instructions in Integration With Cisco UCS Manager 2.0(2xx) and Later.
•If your Cisco UCS Manager software is release 1.4(nx)—your server must use CIMC release 1.2(2xx) firmware for the Cisco UCS integration. See the instructions in Integration With Cisco UCS Manager Earlier Than 2.0(2xx).
•If you want to migrate an earlier configuration to Cisco UCS Manager software release 2.0(2xx) or later—See the instructions in Migrating an Earlier Configuration to Release 2.0(2xx) or Later.
Integration With Cisco UCS Manager 2.0(2xx) and Later
This section contains two procedures:
•Integrating a Release 1.4(3c) or Later Server With Cisco UCS Manager 2.0(2xx)
•Upgrading a Server Earlier Than Release 1.4(3c) for Cisco UCS Manager 2.0(2) Integration
Integrating a Release 1.4(3c) or Later Server With Cisco UCS Manager 2.0(2xx)
Servers that are at CIMC release 1.4(3c) or later already have the prerequisite firmware and settings so that they are ready to be connected to the Cisco UCS environment immediately. If your server is at a CIMC release earlier than 1.4(3c), you must upgrade it as described in Upgrading a Server Earlier Than Release 1.4(3c) for Cisco UCS Manager 2.0(2) Integration.
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:
–Cisco UCS 6100 Series Fabric Interconnect documentation
–Cisco UCS 6200 Series Fabric Interconnect documentation
•For information about the Cisco Nexus 2232 fabric extenders (FEXes) in the configuration, see the documentation at the following link:
Cisco Nexus 2000 Series Fabric Extender documentation
Hard-Pinning Mode and Port-Channel Mode Discovery Policies
In the configuration described in this procedure, the FEXes can be connected to the FIs in two ways. You have the option to choose either of two modes as your FEX discovery policy in Cisco UCS Manager.
1. Hard-pinning mode—In this mode, the server-facing ports of the FEX are pinned to the connected uplink ports as soon as the FEX is discovered. The Cisco UCS Manager software pins the server-facing ports to the uplink ports based on the number of uplink ports that are acknowledged. If a new uplink is connected later or if an existing uplink is deleted, you must manually acknowledge the FEX again to make the changes take effect.
2. Port-channel mode—In this mode, all uplink ports are members of a single port-channel that acts as the uplink to all server-facing ports. There is no pinning. If a port-channel member goes down, traffic is automatically distributed to another member.
The Cisco UCS 6200 Series FI has six sets of eight contiguous ports, with each set of ports managed by a single chip (see Figure D-1).
When you cable between the FEX and the FI in port-channel mode, 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 D-1), 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.
Figure D-1 Six Sets of Ports in the Fabric Interconnect (Including Expansion Module)
For more information on FEX discovery policies and port-channel allocation, see the Cisco UCS Manager Configuration Guide, Release 2.0 or later.
Required Items
The hardware configuration described in this procedure provides redundant network fabrics and paths for both management and data traffic. The following items are required to create this configuration.
•A Cisco UCS system running Cisco UCS Manager software release 2.0(2xx) or later.
•A Cisco UCS C250 M2 server at CIMC release 1.4(3c) or later, with a 10-Gb adapter card installed.
Note If you install a Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), see Special Considerations for the Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01). To use this card for integration with Cisco UCS Manager 2.0(2xx) and later, the minimum card-firmware and uboot image version is 2.0(2g).
•Two Cisco UCS 6100 Series or 6200 Series FIs.
Note The switch ports that carry server traffic must be enabled as server ports.
•Two Cisco Nexus 2232 FEXes.
Note You must plug a power cord into each of the two power supplies in each FEX. If a power supply is not connected to power, you might see "Major" faults reported during power-on self test (POST). For example, 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 (two for linking the data traffic paths between server and FEX; four for the uplinks from the FEXes to the fabric interconnects)
Note Each of the four uplinks from the FEXes to the FIs can use a 10-Gb twinaxial cable, or they can use one of the following SFP types.
-SFP-10GE-SR
-FET-10GE
Do not mix SFP types on an uplink. Discovery failed errors are returned if SFP types are mixed on an uplink.
•Two 1000BASE-T SFP transceivers (GLC-T)
Procedure
Use the following procedure to connect the Cisco UCS C250 M2 server to the Cisco UCS environment.
Step 1 Install the server into your rack. See Installing the Server Into a Rack.
Note The card-firmware and uboot image version for a Cisco UCS P81E Virtual Interface Card must be minimum 2.0(2g) for this integration. It is recommended that you update the card firmware and uboot image in standalone mode before you integrate the server into UCSM mode (see Upgrading a Server Earlier Than Release 1.2(2) For Cisco UCS Manager 1.4 or 2.0(1) Integration). If you connect this card to a Cisco UCS Manager 2.0(2xx) system with earlier card firmware and uboot image, the UCS Manager software might return discovery and association/disassociation failures. If you encounter this problem, see Updating Cisco UCS P81E VIC Firmware and uboot Image in Integrated Servers for an upgrade procedure.
Step 2 Connect the management traffic paths from the server to the FEXes (see Figure D-2):
a. Insert one GLC-T transceiver into a port of the FEX in Fabric A. You can use any port on the FEX.
b. Insert one GLC-T transceiver into a port of the FEX in Fabric B. You can use any port on the FEX.
c. Connect an RJ-45 Ethernet cable between 1-Gb port Eth1 or Eth 3 on the rear panel of the server and the transceiver that you inserted into the FEX in Fabric A.
d. Connect an RJ-45 Ethernet cable between 1-Gb port Eth1 or Eth 3 on the rear panel of the server and the transceiver that you inserted into the FEX in Fabric B.
Step 3 Connect the data traffic paths from the server to the FEXes (see Figure D-2):
a. 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.
b. 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.
Note The maximum number of uplinks is eight. The port cabling requirements between the FEX and the FI vary, depending on whether your UCS Manager FI discovery policy is set to hard-pinning mode or port-channel mode. See Hard-Pinning Mode and Port-Channel Mode Discovery Policies.
Note Each of the four uplinks from the FEXes to the FIs can use a 10-Gb twinaxial cable, or they can use one of the following SFP types.
-SFP-10GE-SR
-FET-10GE
Do not mix SFP types on an uplink. Discovery failed errors are returned if SFP types are mixed on an uplink.
Note Only the right-most block of eight ports on the FEX can be used for uplinks (see Figure D-2).
a. 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.
b. 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.
Step 5 Attach a power cord to each power supply in your server, and then attach each power cord to a grounded AC power outlet.
Note During bootup, the server beeps once for each USB device that is attached to the server. Even if there are no external USB devices attached, there is a short beep for each virtual USB device such as a virtual floppy drive, CD/DVD drive, keyboard, or mouse. A beep is also emitted if a USB device is hot-plugged or hot-unplugged during BIOS power-on self test (POST), or while you are accessing the BIOS Setup utility or the EFI shell.
Step 6 Use the supplied KVM cable to connect a keyboard and VGA monitor to the console connector on the front panel (see Figure 1-1).
Note Alternatively, you can use the VGA and USB ports on the rear panel. However, you cannot use the front panel VGA and the rear panel VGA at the same time. If you are connected to one VGA connector and you then connect a video device to the other connector, the first VGA connector is disabled.
Step 7 Reboot the server.
Step 8 To view and configure settings for the server from within the Cisco UCS Manager software, see the information instructions in the Cisco UCS Manager Configuration Guide, Release 2.0 or later.
Figure D-2 Cabling Configuration for Cisco UCS Manager 2.0(2xx) Integration
1
|
Cisco UCS 6100 Series or 6200 Series FI (Fabric A)
|
6
|
Cisco Nexus 2232 FEX
(Fabric B)
|
2
|
GLC-T transceiver in FEX port
(Fabric A)
|
7
|
Cisco UCS C250 M2 server
|
3
|
Cisco Nexus 2232 FEX
(Fabric A)
|
8
|
1-Gb Ethernet LOM ports Eth1 and Eth3
|
4
|
Cisco UCS 6100 Series or 6200 Series FI (Fabric B)
|
9
|
10-Gb adapter card in PCIe slot D
|
5
|
GLC-T transceiver in FEX port
(Fabric B)
|
|
|
Note The paths shown in blue carry management traffic. The paths shown in gold carry data traffic. The paths shown in green carry both data and management traffic.
Note The maximum number of physical uplinks between a FEX and an FI is eight. See Hard-Pinning Mode and Port-Channel Mode Discovery Policies for important information about FI port groups.
Note Only the right-most block of eight ports on the FEX can be used for uplinks (see Figure D-2).
Upgrading a Server Earlier Than Release 1.4(3c) for Cisco UCS Manager 2.0(2) Integration
This section describes the process for upgrading a server that was shipped prior to the 1.4(3c) release so that it can be used in the Cisco UCS environment.
Note The server must be a Generation M2 (or later) server.
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:
–Cisco UCS 6100 Series Fabric Interconnect documentation
–Cisco UCS 6200 Series Fabric Interconnect documentation
•For information about the Cisco Nexus 2232 fabric extenders (FEXes) in the configuration, see the documentation at the following link:
Cisco Nexus 2000 Series Fabric Extender documentation
Required Items
The hardware configuration described in this procedure provides redundant network fabrics and paths for both management traffic and data traffic. The following items are required to create this configuration.
•A Cisco UCS system running Cisco UCS Manager software release 2.0(2xx) or later.
•A Cisco UCS C250 M2 server, with a 10-Gb adapter card installed.
Note If you install a Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), see Special Considerations for the Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01). To use this card for integration with Cisco UCS Manager 2.0(2xx) and later, the minimum card-firmware and uboot image version is 2.0(2g).
•A physical VGA monitor and a USB keyboard. You can use a KVM dongle on the front-panel KVM connector or connect directly to the server ports.
•The Cisco UCS C-Series 1.4(3c) or later standalone software release container for your server. The software release is distributed on Cisco.com as an ISO file that contains the Cisco UCS Host Upgrade Utility and required firmware.
•(Optional for local upgrades) A writable DVD with at least 23 MB of space.
•Two Cisco UCS 6100 Series or 6200 Series FIs.
•Two Cisco Nexus 2232 FEXes.
Note You must plug a power cord into each of the two power supplies in the FEX. If a power supply is not connected to power, you might see "Major" faults reported during power-on self test (POST). For example, 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 (two for linking the data traffic paths between server and FEX; four for the uplinks from the FEXes to the fabric interconnects)
Note Each of the four uplinks from the FEXes to the FIs can use a 10-Gb twinaxial cable, or they can use one of the following SFP types.
-SFP-10GE-SR
-FET-10GE
Do not mix SFP types on an uplink. Discovery failed errors are returned if SFP types are mixed on an uplink.
•Two 1000BASE-T SFP transceivers (GLC-T)
Upgrade and Connection Procedures
Use the procedures in this section in the following order to upgrade your server and connect it to the Cisco UCS environment:
Note These procedures assume that you have already installed the server in your rack and connected it to power. See Installing the Server Into a Rack and Initial Server Setup.
•1. Upgrading the Firmware and Rebooting in UCSM Mode
•2. Physically Connecting the Server to the Cisco UCS Environment
1. Upgrading the Firmware and Rebooting in UCSM Mode
Step 1 Find the Host Upgrade Utility ISO file download for your server online and download it to a temporary location on your workstation:
a. See the following URL: http://www.cisco.com/cisco/software/navigator.html
b. Click Unified Computing and Servers in the middle column.
c. Click Cisco UCS C-Series Rack-Mount Standalone Server Software in the right-hand column.
d. Click your model of server in the right-hand column.
e. Click Unified Computing System (UCS) Server Firmware.
f. Click the release number that you are downloading.
Note CIMC release 1.4(3c) or later is the required level for integration with Cisco UCS Manager 2.0(2xx).
g. Click Download Now to download the ISO file.
h. Verify the information on the next page, then click Proceed With Download.
i. Continue through the subsequent screens to accept the license agreement and then browse to a location where you save the ISO file.
Step 2 Prepare the ISO file on either local media for local upgrade, or as a virtual device for remote upgrade:
•For local upgrade—Perform these steps before you go to Step 3:
a. Burn the ISO image onto a writable DVD.
b. Connect a VGA monitor and USB keyboard to the Cisco C-Series server.
c. Insert the DVD into the DVD drive of the Cisco C-Series server.
•For remote upgrade—Perform these steps before you go to Step 3:
a. Use a browser to connect to the CIMC Manager software on the server that you are upgrading.
Enter the CIMC IP address for that server in the address field of the browser, then enter your user name and password.
b. Launch a KVM Console window (click the KVM keyboard icon).
c. When the Virtual KVM Console window launches, select Tools > Launch Virtual Media.
d. In the Virtual Media Session window, click Add Image and then use the dialog to navigate to the utility ISO file and select it. Navigate to the location where you downloaded the ISO. The ISO image is displayed in the Client View pane.
e. In the Virtual Media Session window, check the check box in the Mapped column for the ISO file that you added, and then wait for mapping to complete. Observe the progress in the Details pane.
Now the ISO file is mapped as a remote device.
Step 3 Boot the server and press F6 when prompted to open the Boot Menu screen.
Step 4 On the Boot Menu screen, select the device where you prepared the ISO in Step 2:
•If you are upgrading locally, select the physical CD/DVD device and then press Enter (for example, SATA5:TSSTcorp CDDVDW TS-L633C).
•If you are upgrading remotely, select Cisco Virtual CD/DVD and then press Enter.
The server is rebooted from the device that you chose.
Step 5 A screen appears with the server BIOS and CIMC firmware versions. Answer the prompt, "Have you read the Cisco EULA" (end user license agreement)?
•Press y to accept the EULA and continue the update.
•Press n to read the EULA. The EULA is displayed and you are prompted to press y to continue the update, or n to cancel. If you press n, the server will reboot without updating.
•Press q to exit without updating. This selection reboots the server.
The Host Upgrade Menu screen is displayed.
Step 6 Upgrade all the firmware by entering the number for the All the above menu item at the Enter Choice prompt.
The utility selects the correct firmware components for your server and then upgrades them. Watch your console screen until you see confirmation that the upgrades were successful, then go to Step 7.
Step 7 After the upgrades are successful, reboot the server with UCSM mode settings from the Host Upgrade Menu by entering the number for the Reboot (Configures CIMC to UCSM mode—default factory settings) menu item at the Enter Choice prompt.
Note The new CIMC firmware is activated automatically during this reboot.
The utility reboots the server with UCSM mode settings. This mode allows integration with the Cisco UCS environment.
Note These UCSM mode settings enable DHCP, Active-Active NIC redundancy, and Shared LOM NIC mode, which enables CIMC control through the 1Gb LOM ports, rather than the management port. Any static IP addresses and the management port are disabled, so you lose connection with the CIMC. To connect the server to your Cisco UCS FEXes and FIs, continue with 2. Physically Connecting the Server to the Cisco UCS Environment.
2. Physically Connecting the Server to the Cisco UCS Environment
Use the following procedure to connect the Cisco UCS C250 M2 server to the Cisco UCS environment.
Step 1 Connect the management traffic paths from the server to the FEXes (see Figure D-3):
a. Insert one GLC-T transceiver into a port of the FEX in Fabric A. You can use any port on the FEX.
b. Insert one GLC-T transceiver into a port of the FEX in Fabric B. You can use any port on the FEX.
c. Connect an RJ-45 Ethernet cable between 1-Gb port Eth1 or Eth 3 on the rear panel of the server and the transceiver that you inserted into the FEX in Fabric A.
d. Connect an RJ-45 Ethernet cable between 1-Gb port Eth1 or Eth 3 on the rear panel of the server and the transceiver that you inserted into the FEX in Fabric B.
Step 2 Connect the data traffic paths from the server to the FEXes (see Figure D-3):
a. 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.
b. 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 3 Connect the paths from the FEXes to the FIs. These paths carry both data and management traffic.
Note The maximum number of uplinks is eight. The port cabling requirements between the FEX and the FI vary, depending on whether your UCS Manager FI discovery policy is set to hard-pinning mode or port-channel mode. See Hard-Pinning Mode and Port-Channel Mode Discovery Policies.
Note Each of the four uplinks from the FEXes to the FIs can use a 10-Gb twinaxial cable, or they can use one of the following SFP types.
-SFP-10GE-SR
-FET-10GE
Do not mix SFP types on an uplink. Discovery failed errors are returned if SFP types are mixed on an uplink.
Note Only the right-most block of eight ports on the FEX can be used for uplinks (see Figure D-3).
a. 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.
b. 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.
Step 4 Reboot the server.
Step 5 To view and configure settings for the server from within the Cisco UCS Manager software, see the information instructions in the Cisco UCS Manager Configuration Guide, Release 2.0 or later.
Figure D-3 Cabling Configuration for Cisco UCS Manager 2.0(2xx) Integration
1
|
Cisco UCS 6100 Series or 6200 Series FI (Fabric A)
|
6
|
Cisco Nexus 2232 FEX
(Fabric B)
|
2
|
GLC-T transceiver in FEX port
(Fabric A)
|
7
|
Cisco UCS C250 M2 server
|
3
|
Cisco Nexus 2232 FEX
(Fabric A)
|
8
|
1-Gb Ethernet LOM ports Eth1 and Eth3
|
4
|
Cisco UCS 6100 Series or 6200 Series FI (Fabric B)
|
9
|
10-Gb adapter card in PCIe slot D
|
5
|
GLC-T transceiver in FEX port
(Fabric B)
|
|
|
Note The paths shown in blue carry management traffic. The paths shown in gold carry data traffic. The paths shown in green carry both data and management traffic.
Note The maximum number of physical uplinks between a FEX and an FI is eight. See Hard-Pinning Mode and Port-Channel Mode Discovery Policies for important information about FI port groups.
Note Only the right-most block of eight ports on the FEX can be used for uplinks (see Figure D-3).
Integration With Cisco UCS Manager Earlier Than 2.0(2xx)
This section contains two procedures:
•Installing a Release 1.2(2xx) Server With Cisco UCS Manager 1.4 or 2.0(1)
•Upgrading a Server Earlier Than Release 1.2(2) For Cisco UCS Manager 1.4 or 2.0(1) Integration
Installing a Release 1.2(2xx) Server With Cisco UCS Manager 1.4 or 2.0(1)
Servers that are Release 1.2(2xx) already have the prerequisite firmware and settings so that they are ready to be connected to the Cisco UCS Manager 1.4 or 2.0(1) environment immediately.
Note Release 1.3(xx) does not support UCS integration. Do not upgrade your server later than 1.2(2xx) if you want to use the server in UCSM mode with UCS Manager 1.4 or 2.0(1).
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:
–Cisco UCS 6100 Series Fabric Interconnect documentation
–Cisco UCS 6200 Series Fabric Interconnect documentation
•For information about the Cisco Nexus 2248 fabric extenders (FEXes) in the configuration, see the documentation at the following link:
Cisco Nexus 2000 Series Fabric Extender documentation
Required Items
The hardware configuration described in this procedure provides redundant network fabrics and paths for both management traffic and data traffic. The following items are required to create this configuration.
•A Cisco UCS system running Cisco UCS Manager software release 1.4(1x) or 2.0(1x).
•A Cisco UCS C-Series server with a 10-Gb adapter card installed.
Note If you install a Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), see Special Considerations for the Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01). To use this card for UCS integration, the minimum card-firmware level is 1.4(1i).
•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 2248 FEXes.
Note You must plug a power cord into each of the two power supplies in the FEX. If a power supply is not connected to power, you might see "Major" faults reported during power-on self test (POST). For example, 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.
•Four 10-Gb SFP cables.
Procedure
Use the following procedure to connect the Cisco UCS C250 M2 server to the Cisco UCS environment.
Step 1 Install the server into your rack. See Installing the Server Into a Rack.
Step 2 Connect the management traffic paths (see Figure D-4):
a. Connect an RJ-45 Ethernet cable between 1-Gb port Eth1 or Eth2 on the rear panel of the server and a port on a FEX in Fabric A. You can use any port on the FEX.
b. Connect an RJ-45 Ethernet cable between 1-Gb port Eth3 or Eth4 on the rear panel of the server and a port on a FEX in Fabric B. You can use any port on the FEX.
Note You must use one port from each pair [Eth1+ Eth2] and [Eth3 + Eth4] to ensure redundancy.
c. Connect a 10-Gb SFP cable between FEX A and a port on FI A. You can use any port on FI A, but the port must be enabled for server traffic.
d. Connect a 10-Gb SFP cable between FEX B and a port on FI B. You can use any port on FI B, but the port must be enabled for server traffic.
Step 3 Connect the data traffic paths (see Figure D-4):
a. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on FI A. You can use any port on FI A, but the port must be enabled for server traffic.
b. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on FI B. You can use any port on FI B, but the port must be enabled for server traffic.
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.
Wait for approximately two minutes to let the server boot in standby power during the first bootup.
You can verify power status by looking at the Power Status LED on the front panel (see Figure 1-1):
•Off—The server is not receiving power. Check the power cord connections and the power source of the facility.
•Amber—The server is in standby power mode. Power is supplied only to the service processor and some motherboard functions.
•Solid green—The server is in main power mode. Power is supplied to all server components.
Note During bootup, the server beeps once for each USB device that is attached to the server. Even if there are no external USB devices attached, there is a short beep for each virtual USB device such as a virtual floppy drive, CD/DVD drive, keyboard, or mouse. A beep is also emitted if a USB device is hot-plugged or hot-unplugged during BIOS power-on self test (POST), or while you are accessing the BIOS Setup utility or the EFI shell.
Step 5 Use the supplied KVM cable to connect a keyboard and VGA monitor to the console connector on the front panel (see Figure 1-1).
Note Alternatively, you can use the VGA and USB ports on the rear panel. However, you cannot use the front panel VGA and the rear panel VGA at the same time. If you are connected to one VGA connector and you then connect a video device to the other connector, the first VGA connector is disabled.
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 instructions in the Cisco UCS Manager Configuration Guide for Release 1.4(1) or the Cisco UCS Manager Configuration Guide for Release 2.0(1).
Figure D-4 Cabling Configuration For Cisco UCS Manager 1.4(nx) Integration
1
|
Cisco UCS 6100 Series or 6200 Series FI (Fabric A)
|
5
|
Cisco UCS C250 M2 (or later) server
|
2
|
Cisco Nexus 2248 FEX
(Fabric A)
|
6
|
1-Gb Ethernet LOM ports Eth1 and Eth3
|
3
|
Cisco UCS 6100 Series or 6200 Series FI (Fabric B)
|
7
|
10-Gb adapter card in PCIe slot D
|
4
|
Cisco Nexus 2248 FEX
(Fabric B)
|
|
|
Note The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.
Upgrading a Server Earlier Than Release 1.2(2) For Cisco UCS Manager 1.4 or 2.0(1) Integration
This section describes the process for upgrading a server that was shipped prior to the 1.2(2) release so that it can be integrated with UCS Manager 1.4(1x) or 2.0(1x).
Note The server must be a Generation M2 (or later) server.
Note Release 1.3(x) does not support UCS integration. Do not upgrade your server later than 1.2(2xx) if you want to use the server in UCSM mode with UCS Manager 1.4 or 2.0(1).
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:
–Cisco UCS 6100 Series Fabric Interconnect documentation
–Cisco UCS 6200 Series Fabric Interconnect documentation
•For information about the Cisco Nexus 2248 fabric extenders (FEXes) in the configuration, see the documentation at the following link:
Cisco Nexus 2000 Series Fabric Extender documentation
Required Items
The hardware configuration described in this procedure provides redundant network fabrics and paths for both management traffic and data traffic. The following items are required to create this configuration.
•A Cisco UCS system running Cisco UCS Manager software release 1.4(1x) or 2.0(1x).
•A Cisco UCS C-Series M2 server with a Cisco 10-Gb adapter card installed.
Note This server CIMC and BIOS firmware must be at version 1.2(1a) or later before you can use the Cisco Host Upgrade Utility as described in this upgrade procedure.
Note If you install a Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01), see Special Considerations for the Cisco UCS P81E Virtual Interface Card (N2XX-ACPCI01). To use this card for UCS integration, the minimum card-firmware level is 1.4(1i).
•A physical VGA monitor and a USB keyboard. You can use a KVM dongle on the front-panel KVM connector or connect directly to the server ports.
•The Cisco UCS C-Series 1.2(2xx) standalone software release container for your server. The software release is distributed on Cisco.com as an ISO file that contains the Host Upgrade Utility and required firmware.
•(Optional for local upgrades) A writable DVD with at least 23 MB of space.
•Two Cisco UCS 6100 Series or 6200 Series FIs.
•Two Cisco Nexus 2248 FEXes.
Note You must plug a power cord into each of the two power supplies in the FEX. If a power supply is not connected to power, you might see "Major" faults reported during power-on self test (POST). For example, 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.
•Four 10-Gb SFP cables.
Upgrade and Connection Procedures
Use the procedures in this section in the following order to upgrade your server and connect it to the Cisco UCS environment:
Note These procedures assume that you have already installed the server in your rack and connected it to power. See Installing the Server Into a Rack and Initial Server Setup.
•1. Upgrading the Firmware and Rebooting in UCSM Mode
•2. Physically Attach the Server to the Cisco UCS Environment
1. Upgrading the Firmware and Rebooting in UCSM Mode
Step 1 Find the Host Upgrade Utility ISO file download for your server online and download it to a temporary location on your workstation:
a. See the following URL: http://www.cisco.com/cisco/software/navigator.html
b. Click Unified Computing and Servers in the middle column.
c. Click Cisco UCS C-Series Rack-Mount Standalone Server Software in the right-hand column.
d. Click your model of server in the right-hand column.
e. Click Unified Computing System (UCS) Server Firmware.
f. Click the release number that you are downloading.
Note Release 1.2(2xx) is the required level for Cisco UCS manager 1.4(1x) or 2.0(1x) integration.
g. Click Download Now to download the ISO file.
h. Verify the information on the next page, then click Proceed With Download.
i. Continue through the subsequent screens to accept the license agreement and then browse to a location where you will save the ISO file.
Step 2 Prepare the ISO on either local media for local upgrade, or as a virtual device for remote upgrade:
•For local upgrade—Perform these steps before you go to Step 3:
a. Burn the ISO image onto a writable DVD.
b. Connect a VGA monitor and USB keyboard to the Cisco C-Series server.
c. Insert the DVD into the DVD drive of the Cisco C-Series server.
•For remote upgrade—Perform these steps before you go to Step 3:
a. Use a browser to connect to the CIMC Manager software on the server that you are upgrading.
Enter the CIMC IP address for that server in the address field of the browser, then enter your user name and password.
b. Launch a KVM Console window (click the KVM keyboard icon).
c. When the Virtual KVM Console window launches, select Tools > Launch Virtual Media.
d. In the Virtual Media Session window, click Add Image and then use the dialog to navigate to the utility ISO file and select it. Navigate to the location where you downloaded the ISO. The ISO image is displayed in the Client View pane.
e. In the Virtual Media Session window, check the check box in the Mapped column for the ISO file that you added, and then wait for mapping to complete. Observe the progress in the Details pane.
Now the ISO file is mapped as a remote device.
Step 3 Boot the server and press F6 when prompted to open the Boot Menu screen.
Step 4 On the Boot Menu screen, select the device where you prepared the ISO in Step 2:
•If you are upgrading locally, select the physical CD/DVD device and then press Enter (for example, SATA5:TSSTcorp CDDVDW TS-L633C).
•If you are upgrading remotely, select Cisco Virtual CD/DVD and then press Enter.
The server is rebooted from the device that you chose.
Step 5 A screen appears with the server BIOS and CIMC firmware versions. Answer the prompt, "Have you read the Cisco EULA" (end user license agreement)?
•Press y to accept the EULA and continue the update.
•Press n to read the EULA. The EULA is displayed and you are prompted to press y to continue the update, or n to cancel. If you press n, the server will reboot without updating.
•Press q to exit without updating. This selection reboots the server.
The Host Upgrade Menu screen is displayed.
Step 6 Upgrade all the firmware by entering the number for the All the above menu item at the Enter Choice prompt:
The utility selects the correct firmware components for your server and then upgrades the firmware. Watch your console screen until you see confirmation that the upgrades were successful, then go to Step 7.
Step 7 After the upgrades are successful, reboot the server with UCSM mode settings from the Host Upgrade Menu by entering the number for the Reboot (Configures CIMC to UCSM mode—default factory settings) menu item at the Enter Choice prompt.
Note The new CIMC firmware is activated automatically during this reboot.
The utility reboots the server with UCSM mode settings. This mode allows integration with the Cisco UCS environment.
Note These UCSM mode settings enable DHCP, Active-Active NIC redundancy, and Shared LOM NIC mode, which enables CIMC control through the 1Gb LOM ports, rather than the management port. Any static IP addresses and the management port are disabled, so you lose connection with the CIMC. To connect the server to your Cisco UCS FIs, continue with 2. Physically Attach the Server to the Cisco UCS Environment.
2. Physically Attach the Server to the Cisco UCS Environment
Use the following procedure to connect the Cisco UCS C250 server to the Cisco UCS environment.
Step 1 Connect the management traffic paths (see Figure D-5):
a. Connect an RJ-45 Ethernet cable between 1-Gb port Eth1 or Eth2 on the rear panel of the server and a port on a FEX in Fabric A.
b. Connect an RJ-45 Ethernet cable between 1-Gb port Eth3 or Eth4 on the rear panel of the server and a port on a FEX in Fabric B.
Note You must use one port from each pair [Eth1+ Eth2] and [Eth3 + Eth4] to ensure redundancy.
c. Connect a 10-Gb SFP cable between FEX A and a port on FI A. The port that you use on FI A must be enabled for server traffic.
d. Connect a 10-Gb SFP cable between FEX B and a port on FI B. The port that you use on FI B must be enabled for server traffic.
Step 2 Connect the data traffic paths (see Figure D-5):
a. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on FI A. The port that you use on FI A must be enabled for server traffic.
b. Connect a 10-Gb SFP cable between the 10-Gb adapter card in the server and a port on FI B. The port that you use on FI B must be enabled for server traffic.
Step 3 Reboot the server.
Step 4 To view and configure settings for the server from within the Cisco UCS Manager software, see the information instructions in the Cisco UCS Manager Configuration Guide for Release 1.4(1) or the Cisco UCS Manager Configuration Guide for Release 2.0(1).
Figure D-5 Cabling Configuration For Cisco UCS Manager 1.4(nx) Integration
1
|
Cisco UCS 6100 Series or 6200 Series FI (Fabric A)
|
5
|
Cisco UCS C250 M2 server
|
2
|
Cisco Nexus 2248 FEX
(Fabric A)
|
6
|
1-Gb Ethernet LOM ports Eth1 and Eth3
|
3
|
Cisco UCS 6100 Series or 6200 Series FI (Fabric B)
|
7
|
10-Gb adapter card in PCIe slot D
|
4
|
Cisco Nexus 2248 FEX
(Fabric B)
|
|
|
Note The paths shown in blue carry management traffic. The paths shown in gold carry data traffic.
Migrating an Earlier Configuration to Release 2.0(2xx) or Later
Note This procedure causes server downtime.
This start of this procedure assumes this existing configuration:
•A Cisco UCS system running Cisco UCS Manager software release 1.4(1x) or 2.0(1x).
•A Cisco UCS C-Series server that is running CIMC firmware release 1.2(2xx).
•The server has been discovered by UCS Manager and it has an associated service profile.
•The configuration uses two Cisco Nexus 2248 FEXes.
•The management path from the server connects to the FEX but the data path connects directly to the FI (as shown in Figure D-4).
Use the following procedure to migrate an earlier configuration to Cisco UCS Manager 2.0(2xx) or later.
Step 1 Use UCS Manager to decommission all of the rack servers in the UCS system.
Step 2 Use UCS Manager to Unconfigure all FI server ports that are connected to the Nexus 2248 FEX.
For information about using Cisco UCS Manager, see the Cisco UCS Manager Configuration Guide, Release 2.0 or later.
Step 3 Verify the unconfigure by issuing an NX-OS show fex command. Wait until the command return does not list the FEX.
Step 4 Disconnect the cable that is between the FEX and the FI.
Step 5 In UCS Manager, issue a remove fex <fex_ID> command to remove the FEX from the database.
Step 6 Use UCS Manager to Unconfigure all FI server ports that are connected to the server's adapter card.
Step 7 Disconnect the cable that is between the FI and the server's adapter card.
Step 8 Disconnect the cable that is between the FEX and the server's LOM connector.
Step 9 Upgrade your UCS Manager software to release 2.0(2xx) or later and the FI firmware to the corresponding level.
See the upgrade guides at the following link: Cisco UCS Manager install and upgrade guides.
Step 10 Physically replace the Nexus 2248 FEX with a Nexus 2232 FEX in your rack.
Step 11 While your C-series server is still unattached to the UCS system, connect it directly to your network so that you can upgrade the firmware by using the standalone CIMC utility.
a. Connect an Ethernet line from your LAN to one of the 1-Gb LOM ports on the server (not the dedicated management port, which is disabled in UCSM mode).
b. Follow the instructions in 1. Upgrading the Firmware and Rebooting in UCSM Mode, then return to the next step in this procedure.
Step 12 Cable the configuration as shown in Figure D-2.
In this new configuration, the data and management paths both connect from the server to the FEX. The paths between the FEX and the FI carry both data and management traffic.
Step 13 Verify the FEX by issuing an NX-OS show fex command. Wait until the command return lists the new Nexus 2232 FEX. The FEX will automatically upgrade to the corresponding FI firmware version.
Step 14 Repeat the above steps on the second fabric in your configuration.
Step 15 After both fabrics are cabled, use UCS Manager to Re-commission the servers that you decommissioned in the first step.
After a server is discovered, it re-associates with any prior service profiles that were assigned to it.
Supported Network Adapter Cards for UCSM Mode
Network Adapter cards can be Cisco Virtual Interface Cards (VICs), Converged Network Adapters (CNAs), or Ethernet adapters.
Supported Adapter Cards
Table D-1 shows the adapter cards that are officially supported for use in C-Series servers in UCSM mode. Not all adapters in the table are supported in all servers, so find your server model and then read down its column to see which adapters have been qualified for use in UCSM mode.
Table D-1 Supported Network Adapter Cards by Server
Adapter/Server Model
|
C200 M2
|
C210 M2
|
C220 M3
|
C240 M3
|
C250 M2
|
C260 M2
|
C460 M2
|
Cisco UCS P81E VIC
(N2XX-ACPCI01)
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Emulex OCe10102-F CNA
(N2XX-AEPCI01)
|
Y
|
Y
|
|
|
Y
|
Y
|
Y
|
QLogic QLE8152 CNA
(N2XX-AQPCI01)
|
Y
|
Y
|
|
|
Y
|
Y
|
Y
|
Broadcom BCM57711 10Gb
(N2XX-ABPCI02)
|
Y
|
Y
|
|
|
Y
|
Y
|
Y
|
Intel X520 10Gb
(N2XX-AIPCI01)
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Supported Card Combinations
When the server is used in UCSM mode, only certain combinations of adapters have been qualified for official support:
•Only Cisco Virtual Interface Cards (VICs) installed in the server. No mixing with CNAs or Ethernet cards.
•Only one type of CNA (Q or E) installed in the server. No mixing with VICs or Ethernet adapters.
•Only one type of Ethernet adapter (B or I) installed in the server. No mixing with VICs or CNAs.
Supported 2232 FEX-to-FI Uplink Cable SFP Types
The UCSM 2.0 integration described in this appendix uses a total of six 10-Gb SFP cables—two for linking the data traffic paths between server and 2232 FEX; four for the uplinks from the 2232 FEXes to the FIs.
Each of the four uplinks from the FEXes to the FIs can use a 10-Gb twinaxial cable, or they can use one of the following SFP types.
•SFP-10GE-SR
•FET-10GE
Note Do not mix SFP types on an uplink. Discovery failed errors are returned if SFP types are mixed on an uplink.
Reverting a Server From UCSM 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:
1. Disassociate the UCS Manager service profile from the server.
2. Decommission the server.
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.
Special Considerations For Integrated Servers
This section contains considerations and caveats for Cisco UCS C-Series servers that are integrated with a Cisco UCS system.
•Updating Cisco UCS P81E VIC Firmware and uboot Image in Integrated Servers
•Integrated Server Power States vs. Service Profile Power States
•Adapter Card Considerations
•FEX Considerations
Updating Cisco UCS P81E VIC Firmware and uboot Image in Integrated Servers
If you are integrating your server with any UCS Manager version, and your Cisco UCS P81E VIC firmware and uboot version is earlier than 2.0(2g), the UCS Manager software will return discovery and associate/disassociate failures.
•It is recommended that you upgrade your P81E VIC firmware and uboot image to the required minimum 2.0(2g) level in standalone mode before you integrate it with a UCS Manager 2.0(2xx) or later system.
•If your server is already integrated, there is no ability to update the P81E VIC uboot image in the UCS Manager software. Use the following procedure to remove the server from the integration so that you can use the Cisco Host Upgrade Utility (HUU) to upgrade the card and server firmware to the required levels.
Note The following procedure requires about one half-hour of downtime for the server.
Step 1 Decommission the server from UCS Manager.
Step 2 Disconnect the cables from the 1-Gb LOM ports on the server.
Step 3 Connect an Ethernet line from your LAN to one of the 1-Gb LOM ports (not to the dedicated management port, which is disabled in UCSM mode).
Step 4 Find the Host Upgrade Utility ISO file download for your server online and download it to a temporary location on your workstation:
a. See the following URL: http://www.cisco.com/cisco/software/navigator.html
b. Click Unified Computing and Servers in the middle column.
c. Click Cisco UCS C-Series Rack-Mount Standalone Server Software in the right-hand column.
d. Click your model of server in the right-hand column.
e. Click Unified Computing System (UCS) Server Firmware.
f. Click the release number that you are downloading.
Note CIMC release 1.4(3c) or later is the required level for integration with Cisco UCS Manager 2.0(2xx).
g. Click Download Now to download the ISO file.
h. Verify the information on the next page, then click Proceed With Download.
i. Continue through the subsequent screens to accept the license agreement and then browse to a location where you save the ISO file.
Step 5 Prepare the ISO file on either local media for local upgrade, or as a virtual device for remote upgrade:
•For local upgrade—Perform these steps before you go to Step 3:
a. Burn the ISO image onto a writable DVD.
b. Connect a VGA monitor and USB keyboard to the Cisco C-Series server.
c. Insert the DVD into the DVD drive of the Cisco C-Series server.
•For remote upgrade—Perform these steps before you go to Step 3:
a. Use a browser to connect to the CIMC Manager software on the server that you are upgrading.
Enter the CIMC IP address for that server in the address field of the browser, then enter your user name and password.
b. Launch a KVM Console window (click the KVM keyboard icon).
c. When the Virtual KVM Console window launches, select Tools > Launch Virtual Media.
d. In the Virtual Media Session window, click Add Image and then use the dialog to navigate to the utility ISO file and select it. Navigate to the location where you downloaded the ISO. The ISO image is displayed in the Client View pane.
e. In the Virtual Media Session window, check the check box in the Mapped column for the ISO file that you added, and then wait for mapping to complete. Observe the progress in the Details pane.
Now the ISO file is mapped as a remote device.
Step 6 Boot the server and press F6 when prompted to open the Boot Menu screen.
Step 7 On the Boot Menu screen, select the device where you prepared the ISO in Step 2:
•If you are upgrading locally, select the physical CD/DVD device and then press Enter (for example, SATA5:TSSTcorp CDDVDW TS-L633C).
•If you are upgrading remotely, select Cisco Virtual CD/DVD and then press Enter.
The server is rebooted from the device that you chose.
Step 8 A screen appears with the server BIOS and CIMC firmware versions. Answer the prompt, "Have you read the Cisco EULA" (end user license agreement)?
•Press y to accept the EULA and continue the update.
•Press n to read the EULA. The EULA is displayed and you are prompted to press y to continue the update, or n to cancel. If you press n, the server will reboot without updating.
•Press q to exit without updating. This selection reboots the server.
The Host Upgrade Menu screen is displayed.
Step 9 Select the option to Update UCS P81E VIC. This will update the card firmware and uboot image to the required level.
Step 10 Select the option to Update CIMC Firmware. This will update the CIMC firmware.
Step 11 Verify the firmware levels on the next screen.
Step 12 Select the option to Reboot the machine.
Step 13 When you see the F8 prompt during rebooting, press F8 to open the CIMC Configuration Utility.
Step 14 In the CIMC Configuration Utility, select the option CIMC Factory Default, then press F10 to save your changes.
Step 15 Return the cables from the FEXes to the 1-Gb LOM ports on the server.
Step 16 Recommission the server in UCS Manager.
Integrated Server Power States vs. Service Profile Power States
If the desired power state for a service profile associated with an integrated C-Series server is set to Down, using the power button or Cisco UCS Manager to reset the server causes the desired power state of the server to become out of sync with the actual power state and the server may unexpected shut down at a later time.
To safely reboot a server from a power-down state, use the Boot Server action in Cisco UCS Manager.
The following table shows how the physical server power states can differ from the UCSM 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 Power State of Server After Action Was Taken
|
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
|
Adapter Card Considerations
Decommission/Recommission When Adding, Removing, or Replacing an Adapter Card
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.
vNIC/vHBA Priority When Two Cisco UCS P81E VIC Adapter Cards Are Installed
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.
FEX Considerations
Re-acknowledge Attached Servers After a 2232 FEX Is Decommissioned/Recommissioned
Whenever you decommission or recommission a Cisco UCS 2232 FEX, all the servers that are connected to that FEX must be re-acknowledged in UCS Manager.
