OPERATIONAL DEFECT DATABASE
...
...
The hw-module subslot shutdown unpowered command does not power down the ESM like expected: c4351(config)#hw-module subslot 1/0 shutdown unpowered c4351(config)# *Feb 18 06:15:03.699: %SPA_OIR-6-SHUTDOWN: subslot 1/0 is administratively shutdown; Use 'no hw-module shutdown' to enable *Feb 18 06:15:03.702: %SPA_OIR-6-OFFLINECARD: SPA (SM-X-ES3-24-P) offline in subslot 1/0 The module shows as being down but it can still be accessed: c4351#hw-module session 1/0 Establishing session connect to subslot 1/0 To exit, type ^a^q picocom v1.4 port is : /dev/ttyDASH0 flowcontrol : none baudrate is : 9600 parity is : none databits are : 8 escape is : C-a noinit is : no noreset is : no nolock is : yes send_cmd is : ascii_xfr -s -v -l10 receive_cmd is : rz -vv Terminal ready Switch# *Feb 18 06:15:03.699: %SPA_OIR-6-SHUTDOWN: subslot 1/0 is administratively shutdown; Use 'no hw-module shutdown' to enable *Feb 18 06:15:03.702: %SPA_OIR-6-OFFLINECARD: SPA (SM-X-ES3-24-P) offline in subslot 1/0 Switch# Switch#
This is seen on a 4400/4300 with a Cisco SM-X Layer 2/3 ESM such as a SM-X-ES3-24-P. The only other modules affected are the UCSE modules.
Use the IOS exec CLI "hw subslot stop" command. The non-config 'hw subslot stop' stop command performs the same operation as the config 'hw-module subslot shut unpowered' command - the module is powered off and be inaccessible to any traffic. The only difference between the two is that the config CLI is meant to be persistent across router reloads. Thus, the 'hw-module subslot stop' command will stop the module and perform the same actions as the config command and can be used as a workaround for this defect. When the config 'hw subslot shut unpowered' command is executed the module is non-operational even though the power is not turned off.
The hw-module subslot / shutdown unpowered command will keep the module powered down if the command is already configured when the device is first powered up. If the router reloads, the module will remain up since the module doesn't lose power if the router itself reloads.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
