Each fabric
interconnect is connected to IOMs in the UCS chassis, which provides
connectivity to each blade server. Internal connectivity from blade servers to
IOMs is transparently provided by
Cisco UCS Manager using 10BASE-KR Ethernet standard for
backplane implementations, and no additional configuration is required. You
must configure the connectivity between the fabric interconnect server ports
and IOMs. Each IOM, when connected with the fabric interconnect server port,
behaves as a line card to fabric interconnect, hence IOMs should never be
cross-connected to the fabric interconnect. Each IOM is connected directly to a
single fabric interconnect.
The Fabric Extender
(also referred to as the IOM, or FEX) logically extends the fabric
interconnects to the blade server. The best analogy is to think of it as a
remote line card that’s embedded in the blade server chassis, allowing
connectivity to the external world. IOM settings are pushed via Cisco UCS
Manager and are not managed directly. The primary functions of this module are
to facilitate blade server I/O connectivity (internal and external), multiplex
all I/O traffic up to the fabric interconnects, and help monitor and manage the
Cisco UCS infrastructure.
Configure Fabric
interconnect ports that should be connected to downlink IOM cards as server
ports. Make sure there is physical connectivity between the fabric interconnect
and IOMs. You must also configure the IOM ports and the global chassis
discovery policy.
Note |
For UCS 2200 I/O
modules, you can also select the Port Channel option and all I/O
module-connected server ports will be automatically added to a port channel.
|