- Preface
- Overview of Cisco Unified Computing System
- Overview of Cisco UCS Manager
- Overview of Cisco UCS Manager CLI
- Configuring the Fabric Interconnects
- Configuring Ports and Port Channels
- Configuring Communication Services
- Configuring Authentication
- Configuring Organizations
- Configuring Role-Based Access Control
- Configuring DNS Servers
- Configuring System-Related Policies
- Managing Licenses
- Managing Virtual Interfaces
- Registering Cisco UCS Domains with Cisco UCS Central
- VLANs
- Configuring LAN Pin Groups
- Configuring MAC Pools
- Configuring Quality of Service
- Configuring Network-Related Policies
- Configuring Upstream Disjoint Layer-2 Networks
- Configuring Named VSANs
- Configuring SAN Pin Groups
- Configuring WWN Pools
- Configuring Storage-Related Policies
- Configuring Fibre Channel Zoning
- Configuring Server-Related Pools
- Setting the Management IP Address
- Configuring Server-Related Policies
- Configuring Server Boot
- Deferring Deployment of Service Profile Updates
- Service Profiles
- Configuring Storage Profiles
- Managing Power in Cisco UCS
- Managing Time Zones
- Managing the Chassis
- Managing Blade Servers
- Managing Rack-Mount Servers
- CIMC Session Management
- Managing the I/O Modules
- Backing Up and Restoring the Configuration
- Recovering a Lost Password
Managing the I/O Modules
This chapter includes the following sections:
- I/O Module Management in Cisco UCS Manager GUI
- Acknowledging an IO Module
- Resetting the I/O Module
- Resetting an I/O Module from a Peer I/O Module
I/O Module Management in Cisco UCS Manager GUI
You can manage and monitor all I/O modules in a Cisco UCS domain through Cisco UCS Manager GUI.
Acknowledging an IO Module
Cisco UCS Manager Release 2.2(4) introduces the ability to acknowledge a specific IO module in a chassis.
![]() Note | This operation rebuilds the network connectivity between the IO module and the Fabrics to which it is connected. |
| Command or Action | Purpose |
|---|
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
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.
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

Feedback