Managing the I/O Modules

This chapter includes the following sections:

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.


Procedure
     Command or ActionPurpose
    Step 1 UCS-A# scope chassis chassis-num  

    Enters chassis mode for the specified chassis.

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

    Acknowledges the specified IOM in the chassis.

     
    Step 3UCS-A /chassis* # commit-buffer  

    Commits the transaction to the system configuration.

     

    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

    Procedure
       Command or ActionPurpose
      Step 1UCS-A# scope chassis chassis-num  

      Enters chassis mode for the specified chassis.

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

      Enters chassis IOM mode for the specified IOM.

       
      Step 3UCS-A /chassis/iom # reset  

      Resets the IOM.

       
      Step 4UCS-A /chassis/iom # commit-buffer  

      Commits the transaction to the system configuration.

       

      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.

      Procedure
         Command or ActionPurpose
        Step 1 UCS-A# scope chassis chassis-num  

        Enters chassis mode for the specified chassis.

         
        Step 2UCS-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 3UCS-A /chassis/iom # reset-peer  

        Resets the peer IOM of the specified IOM.

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

        Commits the transaction to the system configuration.

         

        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