This article explains the Chassis Manager error message "SMIC_CMERROR_VOLT_HIGH" that is seen on MX Series routers, which is indicative of high voltage for a Modular Interface Card (MIC) module.

The following syslog messages are reported:

May 17 02:11:45.885  JTAC_LAB_RE0  fpc4 Error: /fpc/4/pfe/0/cm/0/SMIC(4_1)/0/SMIC_CMERROR_VOLT_HIGH (0x1b0001), scope: board, category: functional, severity: major, module: SMIC(4/1), type: Device Voltage Level High
May 17 02:11:45.889  JTAC_LAB_RE0  fpc4 Performing action cmalarm for error /fpc/4/pfe/0/cm/0/SMIC(4_1)/0/SMIC_CMERROR_VOLT_HIGH (0x1b0001) in module: SMIC(4/1) with scope: board category: functional level: major
May 17 02:11:45.894  JTAC_LAB_RE0  fpc4 Performing action get-state for error /fpc/4/pfe/0/cm/0/SMIC(4_1)/0/SMIC_CMERROR_VOLT_HIGH (0x1b0001) in module: SMIC(4/1) with scope: board category: functional level: major
May 17 02:12:10.228  JTAC_LAB_RE0  fpc4 Performing action disable-pfe for error /fpc/4/pfe/0/cm/0/SMIC(4_1)/0/SMIC_CMERROR_VOLT_HIGH (0x1b0001) in module: SMIC(4/1) with scope: board category: functional level: major
May 17 02:12:10.259  JTAC_LAB_RE0  fpc4 Cmerror Op Sub Set: SMIC(4/1): MIC8-PMBUS-1V0-MAX20731_A voltage: (4.218) exceeded threshold (1.120)
May 17 02:12:45.884  JTAC_LAB_RE0  fpc4 Performing action clear-cmalarm for error /fpc/4/pfe/0/cm/0/SMIC(4_1)/0/SMIC_CMERROR_VOLT_HIGH (0x1b0001) in module: SMIC(4/1) with scope: board category: functional level: major
May 17 02:12:45.886  JTAC_LAB_RE0  fpc4 Cmerror Op Sub Clear: SMIC(4/1): MIC8-PMBUS-1V0-MAX20731_A voltage: (1.032) within threshold (1.120)

The SMIC_CMERROR_VOLT_HIGH error message has been introduced as part of the MIC error handling mechanism, which checks if the voltage supplied to the MIC module is within the operating range. If the supplied voltage is higher than the operating voltage, it is reported as a CM error as shown above.

This occurrence can be ignored if it is a one-off message or isolated in nature. If the issue persists, proceed with the following steps:

If this is a first occurrence and it clears on its own, then monitor it for a few days and collect the following outputs:

var/logs

Check the alarm timeline to locate the following error:

May  7 19:27:00  <FPC 4> ASIC Error detected errorno 0x001b0001Disable PFE action performed
May  7 19:27:00  <FPC 4> Sending action response to fpc 0x1 0x40 PFE 0x1 module id 71

Then run the following commands:

request pfe execute target fpc1 command "show cmerror module 71 error 0x1b0001"

request pfe execute command "show smic 0 faults" target fpc1

request pfe execute command "show smic 1 faults" target fpc1

If the issue persists, the system attempts to correct the error by disabling the affected Packet Forwarding Engine (PFE) and thus taking the MIC offline. If this is the case, check the status and subsequently bring the PFE online by using the following CLI command:

show chassis pic fpc-slot <fpc-slot-number> pic-slot <pic-slot-number>

If you find the MIC offline, try bringing it online and monitor the messages file to determine if it is recurring:​

request chassis pic fpc-slot <fpc-slot-number> pic-slot <pic-slot-number> online

If the MIC stays offline even after attempts have been made to clear the issue and bring it online, then restart the FPC that has the affected MIC so as to re-initialize the affected MIC driver as part of recovery.

request chassis fpc slot <fpc-slot-number> restart

If the errors persist, contact Support for further assistance.

2021-06-30: Updated Solution section with more data collection commands