I/O Module Management

I/O Module Management in Cisco UCS Manager CLI

You can manage and monitor all I/O modules in a Cisco UCS domain through Cisco UCS Manager CLI.

Cisco UCS Manager Release 4.0(4c) introduces the Cisco 2408 IO module. This IO Module has 32 25-Gigabit backplane ports and 4 100-Gigabit uplink ports, and is supported only on the Cisco UCS 6454 Fabric Interconnect.

Cisco UCS Manager Release 4.0(4a) introduces the Cisco UCS-IOM-2304V2 I/O module which is based on Cisco UCS-IOM-2304 I/O module.

Cisco UCS Manager Release 3.1(1) introduces the Cisco UCS-IOM-2304 I/O module with 40 GbE connectivity to the Cisco UCS 6300 Series Fabric Interconnect. The Cisco UCS Manager Getting Started Guide provides more information about this functionality.

Acknowledging an IO Module

Cisco UCS Manager Release 2.2(4) introduces the ability to acknowledge a specific IO module in a chassis.


Note

  • After adding or removing physical links between Fabric Interconnect and IO Module, an acknowledgement of the IO Module is required to properly configure the connection.

  • The ability to re-acknowledge each IO Module individually allows to rebuild the network connectivity between a single IO Module and its parent Fabric Interconnect without disrupting production traffic in the other fabric interconnect.

SUMMARY STEPS

  1. UCS-A# scope chassis chassis-num
  2. UCS-A /chassis # acknowledge iom {1 | 2}
  3. UCS-A /chassis* # commit-buffer

DETAILED STEPS

  Command or Action Purpose
Step 1

UCS-A# scope chassis chassis-num

Enters chassis mode for the specified chassis.

Step 2

UCS-A /chassis # acknowledge iom {1 | 2}

Acknowledges the specified IOM in the chassis.

Step 3

UCS-A /chassis* # commit-buffer

Commits the transaction to the system configuration.

Example

The following example acknowledges IO Module 1 and commits the transaction: 

UCS-A# scope chassis 1
UCS-A /chassis # acknowledge iom 1
UCS-A /chassis* # commit-buffer
UCS-A /chassis #

Resetting the I/O Module

SUMMARY STEPS

  1. UCS-A# scope chassis chassis-num
  2. UCS-A /chassis # scope iom {a b}
  3. UCS-A /chassis/iom # reset
  4. UCS-A /chassis/iom # commit-buffer

DETAILED STEPS

  Command or Action Purpose
Step 1

UCS-A# scope chassis chassis-num

Enters chassis mode for the specified chassis.
Step 2

UCS-A /chassis # scope iom {a b}

Enters chassis IOM mode for the specified IOM.

Step 3

UCS-A /chassis/iom # reset

Resets the IOM.
Step 4

UCS-A /chassis/iom # commit-buffer

Commits the transaction to the system configuration.

Example

The following example resets the IOM on fabric A and commits the transaction:

UCS-A# scope chassis 1
UCS-A /chassis # scope iom a
UCS-A /chassis/iom # reset
UCS-A /chassis/iom* # commit-buffer
UCS-A /chassis/iom #

Resetting an I/O Module from a Peer I/O Module

Sometimes, I/O module upgrades can result in failures or I/O modules can become unreachable from Cisco UCS Manager due to memory leaks. You can now reboot an I/O module that is unreachable through its peer I/O module.

Resetting the I/O module restores the I/O module to factory default settings, deletes all cache files and temporary files, but retains the size-limited OBFL file.

SUMMARY STEPS

  1. UCS-A# scope chassis chassis-num
  2. UCS-A /chassis # scope iom {a b}
  3. UCS-A /chassis/iom # reset-peer
  4. UCS-A /chassis/iom* # commit-buffer

DETAILED STEPS

  Command or Action Purpose
Step 1

UCS-A# scope chassis chassis-num

Enters chassis mode for the specified chassis.

Step 2

UCS-A /chassis # scope iom {a b}

Enters chassis IOM mode for the specified IOM.

Specify the peer IOM of the IOM that you want to reset.

Step 3

UCS-A /chassis/iom # reset-peer

Resets the peer IOM of the specified IOM.

Step 4

UCS-A /chassis/iom* # commit-buffer

Commits the transaction to the system configuration.

Example

This example shows how to reset IOM b from IOM a: 

UCS-A# scope chassis 1
UCS-A /chassis # scope iom a
UCS-A /chassis/iom # reset-peer
UCS-A /chassis/iom* # commit-buffer