Cisco® Smart Call Home is an award-winning, embedded support feature available in a broad range of Cisco products. Smart Call Home enabled devices continuously perform proactive diagnostics on their own components to provide real-time alerts and remediation advice when an issue is detected. Spend less time monitoring your network. Speed issue resolution. Gain automated access to the expertise and knowledge of our industry-leading technical support engineers. Rely on Smart Call Home to help you achieve higher network availability and increased operational efficiency.
Cisco SMARTnet® with Smart Call Home includes embedded diagnostics for the Cisco Unified Computing System, Cisco Nexus® Series Switches, and Cisco Integrated Services Routers (ISR), to name a few. This offers an important benefit to your converged network by identifying and resolving problems more quickly, more accurately, and with fewer resources. Spend less time troubleshooting, experience a speedier resolution to network issues, and gain higher network availability.
For additional resources for Smart Call Home, please see the Technical Support Resources section of this document.
Cisco.com Technical Support Resources for Users of Smart Call Home
The Cisco website offers a full range of online resources to help you use Smart Call Home. Please be sure to visit the award-wiNing support website and support community.
The Smart Call Home product page on Cisco.com is your starting point for learning about and using Smart Call Home. You can see which Cisco products support Smart Call Home and find links to technical content that will help you design, configure, maintain, troubleshoot and optimize your network with Smart Call Home.
The Cisco Support Website is your comprehensive base of technical knowledge and tools to help you design, operate and troubleshoot your Smart Call Home products and technologies. The website offers robust features that enable you to:
Use the Cisco Support Community for Technical Questions on Smart Call Home
Join the Cisco Support Community to learn more about Smart Call Home by interacting with networking peers and experts worldwide. The community offers a variety of resources that help you:
Call or Email the Smart Services Bureau for Technical Questions on Smart Call Home
Smart Call Home customers can contact the Smart Services Bureau for help with registration, device configuration, help navigating the Smart Call Home portal, or any other assistance needed while using Smart Call Home. This resource is included with the service and available globally, 24 hours per day, 5 days per week.
Abbreviations
Product Name
Abbreviation
CAT6500
Catalyst 6500 Series Switches
CAT7600
Catalyst 7600 Series Switches
Nexus 5000
Nexus 5000 Series Switches
Nexus 7000
Nexus 7000 Series Switches
MDS9000
Multiservice Modular Switch
UCS 6100 SAM
Unified Computing System
ASR 1000
Aggregation Services Routers
ISR Series
Integrated Services Routers
ASA
Adaptive Security Appliance
UBR7000
Universal Broadband Router
GSR 12000
Gigabyte Switch Router
CRS-1
Carrier Routing System
CUCM
Cisco Unified Communications Manager
Monitoring Details by Product
The following table provides a quick look at the types of alarms for devices with Smart Call Home. The additional tables that follow provide specific details for each diagnostic, environmental, and syslog alarm, by device. For navigational convenience, those tables are linked to the product names in the first table.
Product
Minimum Version of Smart Call Home
Supported OS
Number of alarms per type
Alarm
Report
Proactive alarms embedded in listed Cisco devices covered by SMARTnet with Smart Call Home.
sam:dme:fltMemoryUnitInoperable - The DIMM id/id on server chassisld/slotld is inoperable.
Y
Y
Diagnostics
sam:dme: fltProcessorUnitInoperable - The CPU on the Server Blade has failed.
Y
Y
Diagnostics
sam:dme: fltComputePhysicalInoperable - A compute server has become inoperable or has lost all communications with UCS Manager.
Y
Y
Diagnostics
sam:dme:fltComputePhysicalIdentityUnestablishable - The Server [ID] cannot establish identity because of an illegal FRU. This fault typically occurs because Cisco UCS Manager has detected an unsupported server or CPU.
Y
Y
Diagnostics
sam:dme:fltComputePhysicalBiosPostTimeout - The Server [ID] BIOS failed power-on-self-test due to bios-post-timeout.
Y
Y
Diagnostics
sam:dme:fltEquipmentIOCardIdentity - The side fabric extender chassisld/id has a malformed FRU and its identity could not be established.
Y
Y
Diagnostics
sam:dme:fltComputeBladeBiosPostTimeout - The Server chassisId/slotId (service profile assignedToDn) BIOS failed power-on self test due to bios-post-timeout .
Y
Y
Diagnostics
sam:dme:fltEquipmentChassisIdentity - The Chassis id has a mismatch between FRU identity reported by the Fabric IntercoNect against the FRU identity reported by the Chassis Management Controller.
Y
Y
Diagnostics
sam:dme:fltEquipmentFanModuleIdentity - The Fan Module id/tray-id has a malformed FRU ID and its identity could not be established.
Y
Y
Diagnostics
sam:dme:fltEquipmentPsuIdentity - The Power supply id on chassis id has a malformed FRU ID and its identity could not be established.
Y
Y
Diagnostics
sam:dme:fltAdaptorUnitAdaptorReachability - Adapter ID on Server ID is unreachable. Cisco UCS cannot access the adapter.
Y
N
Diagnostics
sam:dme:fltComputeBladeAssignedInaccessible - Server ID inaccessible.
Y
Y
Diagnostics
sam:dme:fltComputeBladeUnassignedInaccessible - Server ID is inaccessible.
sam:dme:fltEquipmentChassisThermalThresholdCritical - The Temperature on chassis id is either at a upper-critical or at a lower-critical state.
Y
N
Environment
sam:dme:fltEquipmentChassisThermalThresholdNonRecoverable - The Temperature on chassis id is either at a upper-non-recoverable or at a lower-non-recoverable state.
Y
Y
Environment
sam:dme:fltEquipmentFanInoperable - The Fan id on module id/tray-id is inoperable.
Y
Y
Environment
sam:dme: fltEquipmentPsuInoperable - The system lost one of the four power supplies.
Y
Y
Environment
sam:dme: fltEquipmentIOCardThermal - The side fabric extender chassisId/id reported a thermal-problem on the Fabric Extender I/O module.
Y
N
Environment
sam:dme: fltEquipmentPsuThermalThresholdCritical - This message indicates a potential overheating in the power- supply unit. If the system has four power supplies then the system will operate on reduced capacity.
Y
N
Environment
sam:dme: fltEquipmentPsuThermalThresholdNonRecoverable - The Power supply id in chassis id temperature has reached either an upper-non-recoverable or a lower-non-recoverable state.
Y
Y
Environment
sam:dme: fltEquipmentPsuVoltageThresholdCritical - The power supply is currently operational but might fail if this condition persists.
Y
N
Environment
sam:dme: fltEquipmentPsuVoltageThresholdNonRecoverable - Power supply id has failed. If there is not enough power available, Server Blades may not power up, or will be shut down if previously powered.
Y
Y
Environment
sam:dme: fltMemoryUnitThermalThresholdCritical - The Memory unit id/id on chassis chassisId/slotId temperature has reached either an upper-critical or a lower-critical state.The Cooling algorithm is supposed to speed up to cool the blade.
Y
N
Environment
sam:dme: fltMemoryUnitThermalThresholdNonRecoverable - The Memory unit id/id on chassis chassisId/slotId temperature has reached either an upper-non-recoverable or a lower-non-recoverable state.
Y
Y
Environment
sam:dme:fltProcessorUnitThermalThresholdCritical - The processer may be reaching an overheated condition.
Y
N
Environment
sam:dme: fltProcessorUnitThermalThresholdNonRecoverable - The CPU id on chassis chassisId/slotId temperature has reached either an upper-non-recoverable or a lower-non-recoverable state. The processor will shutdown to protect itself.
TestFabricPort - The Port(s) have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring. The system has shut down the affected ports.
Y
Y
Switch Diagnostics
TestForwardingEngine - The Port(s) have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring. The system has shut down the affected ports.
Y
Y
Switch Diagnostics
TestForwardingEnginePort - The Port(s) have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring. The system has shut down the affected ports.
Y
Y
Switch Diagnostics
TestFrontPort - The Port(s) have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring. The system has shut down the affected ports.
Y
Y
Switch Diagnostics
TestInbandPort - Inband CoNectivity to switch CPU is experiencing failure.
Y
Y
Switch Diagnostics
TestFabricEngine - Fabric ASIC has reported major failure. CoNectivity among all ports depends on Fabric ASIC.
Y
Y
Switch Diagnostics
TestSPROM - The Module (module #) caNot be brought online as the module type is unidentified.
Y
Y
Switch Diagnostics
TestOBFL - The Onboard Fault Logging flash itself has failed.
Y
Y
Switch Diagnostics
TestLED - LED control is done via the same transport mechanism to control other key components on a module. If LED control fails, it is likely that there will be other failures.
Y
N
Switch Environment
Temperature Alarm - The Temperature of device has exceeded major\minor threshold value.
Y
N
Switch Environment
PowerSupplyFailure - The device is currently working with only one power-supply unit.
Y
Y
Switch Environment
TEMPERATURE_ALARM --- Sensor - An access failure to Temperature Sensor is recorded on the device.
Y
Y
Switch Environment
TestFAN -- fan speed <speed> out of range >= expected. <speed> rpm - Status of system and power supply fans.
Y
N
Switch Environment
Multiple fans missing or failed - The device recorded an alarm due to multiple fan failure.
Y
N
Switch Environment
One fan missing or failed - The device recorded an alarm due to a single fan failure / missing.
Y
N
Switch Syslogs
No license installed for feature, is on grace license, will expire in D H - The feature will be disabled on expiry of the grace period.
Y
N
Switch Syslogs
License for feature, will expire in H M - The evaluation license installed for the <package> will expire in <show_license_usage:comments> and will be disabled soon.
Y
N
Switch Syslogs
License has expired for feature - The evaluation license installed for the <feature> has expired and is disabled.
Y
N
Switch Syslogs
License file is missing for feature - The previously installed permanent license file for <feature_name> is missing from the device configuration storage. This feature will be disabled.
sam:dme: fltMemoryUnitThermalThresholdCritical: The temperature, on memory unit id/id on server id, has reached either an upper-critical or a lower-critical state.
Y
N
Environment
sam:dme: fltMemoryUnitThermalThresholdNonRecoverable: The temperature, on memory unit id/id on server id, has reached either an upper-non-recoverable or a lower-non-recoverable state.
Y
Y
Environment
sam:dme:fltProcessorUnitThermalThresholdCritical: The host side of the Server will be shutdown automatically if the temperature of the processor reaches the non-recoverable threshold.
Y
N
Environment
sam:dme: fltProcessorUnitThermalThresholdNonRecoverable: The temperature, on CPU Id on server Id, has reached either an upper-non-recoverable, or a lower-non-recoverable state. The processor will shutdown to protect itself.
Y
Y
Environment
sam:dme:fltComputePhysicalThermalProblem: The server Id has reported thermal-problem operational status. This fault typically occurs when the server thermal sensors have detected a problem.
CPUPegging: CPU usage is monitored based on configured thresholds. Alert is generated if threshold exceeded.
Y
N
Performance
LowAvailableVirtualMemory: Virtual memory is low.
Y
N
Performance
LowSwapPartitionAvailableDiskSpace: Available disk space on swap partition is low.
Y
N
Performance
CallProcessingNodeCPUPegging: Percentage of CPU load on a call processing server exceeds the configured percentage for the configured time.
Y
N
Performance
CodeYellow: The AverageExpectedDelay counter represents the current average expected delay to handle any incoming message. If the value exceeds the value that is specified in Code Yellow Entry Latency service parameter, the Code Yellow alarm is generated.
Y
N
Performance
LowActivePartitionAvailableDiskSpace: The percentage of available disk space on the active partition is lower than the configured value.
Y
N
Performance
MediaListExhausted: The number of MediaListExhausted events exceeds the configured threshold during the configured time interval.
Y
N
Performance
RouteListExhausted: The number of RouteListExhausted events exceeds the configured threshold during the configured time interval.
%CMCC-0-CPLD_INITIALIZATION: The SIP CPLD has failed initialization - A Session Initiation Protocol (SIP) Complex Programmable Logic Device (CPLD) failed to initialize.
Y
N
Syslogs
%CMCC-0-CPLD_IOCTL : A CPLD driver I/O control has failed because [chars] - A complex programmable logic device (CPLD) I/O driver control has failed.
Y
Syslogs
%CMCC-0-SERDES_INITIALIZATION : The SIP Serial Bridge ASIC has failed initialization because [chars] - The Session Initiation Protocol (SIP) serial bridge ASIC failed to initialize.
Y
N
Syslogs
%CMCC-0-SERDES_IOCTL : A Serial Bridge driver I/O control has failed because [chars] - A Serial Bridge driver I/O control has failed.
Y
N
Syslogs
%CMCC-0-HT_INITIALIZATION : The SIP HyperTransport has failed initialization because [chars] - SIP HyperTransport has failed.
Y
N
Syslogs
%CMCC-0-HT_IOCTL : A SIP HyperTransport driver I/O control has failed because [chars] - A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed.
Y
N
Syslogs
%CMCC-0-PLIM_INITIALIZATION : The PLIM has failed initialization because [chars] - The physical layer interface module (PLIM) failed to initialize.
Y
N
Syslogs
%CMCC-0-HTDP_ENABLE : The HTDP initialization has failed because [chars] - The Hypertransort datapath (HTDP) failed to initialize.
Y
N
Syslogs
%CMCC-0-CPLD_INTR_ENABLE : The CPLD initialization has failed because [chars] - The Complex Programmable Logic Devices (CPLD) interrupted enable failed to initialize.
Y
N
Syslogs
%CMCC-0-PLIM_IOCTL : A PLIM driver I/O control has failed because [chars] - A physical layer interface module (PLIM) driver I/O has failed.
Y
N
Syslogs
%CMCC-0-PLIM_HALT : A PLIM driver has critical error [chars], [int], param [int] param [int] - A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed.
Y
N
Syslogs
%CMCC-0-CHASSIS_TYPE : The chassis type [chars] is invalid - The system has detected an invalid chassis type.
Y
N
Syslogs
%CMCC-0-CHASFS_OBJECT_CREATE : Failed to create chassis filesystem object [chars] because [chars] - The system failed to create a chassis filesystem object.
Y
N
Syslogs
%CMCC-0-CHASFS_PROPERTY_CREATE : Failed to create chassis filesystem object [chars] property [chars] because [chars].
Y
N
Syslogs
%CMCC-0-CHASFS_PROPERTY_GET : Failed to read chassis filesystem object [chars] property [chars] because [chars] - The system failed to create a chassis filesystem object.
Y
N
Syslogs
%CMCC-0-CHASFS_PROPERTY_SET : Failed to write chassis filesystem object [chars] property [chars] because [chars] - The system failed to read a chassis file system object property.
Y
N
Syslogs
%CMCC-0-CHASFS_OBJECT_WATCH : Failed to watch chassis filesystem object [chars] because [chars] - Failed to watch a chassis filesystem object.
Y
N
Syslogs
%CMCC-0-CHASFS_OBJECT_NOT_PRESENT : Expected chassis filesystem object [chars][chars] not present - The system was unable to find an expected chassis filesystem object.
Y
N
Syslogs
%CMCC-0-CHASFS_PROPERTY_NOT_PRESENT : Expected chassis filesystem object [chars] property [chars] not present - The system caNot locate a chassis filesystem object property.
Y
N
Syslogs
%CMCC-0-CHASFS_LOCATION_TRANSLATE : Failed to translate a location to a chasfs object name because [chars] - The system failed to translate a data sensor location to the chassis filesystem (CHASFS) module.
Y
N
Syslogs
%CMCC-0-PEER_INVALID - An invalid state occurred in a peer table entry.
Y
N
Syslogs
%CMCC-0-UIPEER_CREATE : Failed to create user interface peer.
Y
N
Syslogs
%CMCC-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars].
Y
N
Syslogs
%CMCC-0-IPC_INITIALIZATION : IPC initialization failed because [chars].
Y
N
Syslogs
%CMCC-0-IPC_CONECT_MASTER : IPC coNection to the active RP failed because [chars].
Y
N
Syslogs
%CMCC-0-IPC_CONECTION_INVALID : An IPC coNection has invalid state.
Y
N
Syslogs
%CMFP-0-SPI4_MUX_HALT : SPI4 MUX driver has detected a critical error [chars].
Y
N
Syslogs
%CMRP-0-CPLD_INITIALIZATION : The RP CPLD has failed initialization because [chars].
Y
N
Syslogs
%CMRP-0-CPLD_IOCTL : A CPLD driver I/O control has failed because [chars].
Y
N
Syslogs
%CMRP-0-I2C_INITIALIZATION : The RP I2C has failed initialization because [chars].
Y
N
Syslogs
%CMRP-0-BITS_INITIALIZATION : The RP BITS E1/T1 interface has failed initialization because [chars].
Y
N
Syslogs
%CMRP-0-WANPLL_INITIALIZATION : The RP WAN PLL has failed initialization because [chars].
Y
N
Syslogs
%CMRP-0-DDR_INITIALIZATION : The RP DDR has failed initialization because [chars].
Y
N
Syslogs
%CMRP-0-SERDES_INITIALIZATION : The RP Serial Bridge ASIC has failed initialization because [chars].
Y
N
Syslogs
%CMRP-0-SERDES_IOCTL : A Serial Bridge driver I/O control has failed because [chars].
Y
N
Syslogs
%CMRP-0-SERDES_INTERRUPT_DISPATCH : Serial Bridge interrupt dispatch error: [chars].
Y
N
Syslogs
%CMRP-0-HT_INITIALIZATION : The RP HyperTransport has failed initialization because [chars].
Y
N
Syslogs
%CMRP-0-HT_IOCTL : A RP HyperTransport driver I/O control has failed because [chars].
Y
N
Syslogs
%CMRP-0-EHSA_INITIALIZATION : EHSA initialization has failed because [chars].
Y
N
Syslogs
%CMRP-0-EHSA_STATE_GET : Failed to get EHSA state because [chars].
Y
N
Syslogs
Diagnostics
Alarm Type
Alarm message information
Notify
Create Service Request
Diagnostics
esi_underrun_cnt (RE =0) - This ASIC number and Register number combination indicates the elasticity FIFO was read when empty, caused by clock drift. The underrun errors indicate the number of times that the transmitter has been ruNing faster than the router can handle.
Y
N
Diagnostics
esi_overrun_cnt (RE =1) - This ASIC number and Register number combination indicates the elasticity FIFO was written when already full, caused by clock drift. The overrun errors indicate the number of times that the receiver hardware was incapable of handing received data to a hardware buffer because the input rate exceeded the receiver's capability to handle the data.
Y
N
Diagnostics
esi_reframe_cnt (RE =2) - This ASIC number and Register number combination indicates that the link layer has gone from link in sync to link out of sync.
Y
N
Diagnostics
esi_disparity_cnt (RE =3) - This ASIC number and Register number combination indicates an unknown packet separator was received.
Y
N
Diagnostics
spi_rx_discard_bytes (RE =4) - This ASIC number and Register number combination indicate the count of SPI rx bytes discarded.
Y
N
Diagnostics
spi_rx_discard_pkts (RE =5) - This ASIC number and Register number combination indicate the count of SPI rx packets discarded.
Y
N
Diagnostics
spi_rx_los_cnt (RE =6) - A Count of SPI rx loss of sync errors.
Y
N
Diagnostics
spi_tx_cal_parity_err_cnt (RE =7) - A count of SPI tx cal parity errors.
Y
N
Diagnostics
in_undersize (RE =0) - This ASIC number and Register number combination points to the total frames received with a length of less than 64 octets but with a valid FCS.
Y
N
Diagnostics
in_oversize (RE =1) - This ASIC number and Register number combination points to the total frames received with a length of more than MaxSize octets but with a valid FCS.
Y
N
Diagnostics
in_fragments (RE =2) - This ASIC number and Register number combination points to the total frames received with a length of less than 64 octets but with an invalid FCS.
Y
N
Diagnostics
in_jabber (RE =3) - This ASIC number and Register number combination points to the total frames received with a length of more than MaxSize octets but with an invalid FCS.
Y
N
Diagnostics
in_rx_err (RE =4) - This ASIC number and Register number combination points to the total frames received with an RxErr signal from the PHY.
Y
N
Diagnostics
in_fcs_err (RE =5) - This ASIC number and Register number combination points to the total frames received with an CRC error not counted in InFragments, InJabber or InRxErr.
Y
N
Diagnostics
Collisions (RE =6) - This ASIC number and Register number combination points to the number of collision events seen by the MAC not including those counted in Single, Multiple, Excessive or Late.
Y
N
Diagnostics
Late (RE =7) - This ASIC number and Register number combination points to the number of times a collision is detected later than 512 bits-times into the transmission of a frame.
Y
N
Diagnostics
in_bad_octets (RE =8) - This ASIC number and Register number combination points to the sum of the lengths of all the bad Ethernet frames that were received.
Y
N
Diagnostics
out_fcs_err (RE =9) - This ASIC number and Register number combination points to the number of frames transmitted with an invalid FCS.
Y
N
Alarm Type
Alarm message information
Notify
Create Service Request
Environment
Temperature Alarm - sensorcrossedthresholdmajor - Operating temperature has risen above the Critical threshold value.
Y
N
Environment
Temperature Alarm - sensorfailedmajor - A Temperature Sensor failure is recorded on the device.
Y
N
Environment
Temperature Alarm - sensorrecoveryminor - The device has recovered from an earlier temperature alarm at <Inlet on slot R0 Sensor >.
Y
N
Environment
Power Supply Failure - External power supply has failed or one PEM has failed/been removed.
Y
N
Environment
Power Supply Failure - Recovery - The device has recovered from an earlier alarm on one of the power entry modules.
Y
N
Environment
Fan failure - The router's cooling fans fan # failed.
Y
N
Environment
Fan failure - Recovery - The device has recovered from an earlier alarm on one of the fans.
Card Locked: Triggered whenever a card is physically locked by sliding the card latch into the locked position.
Y
N
Diagnostics
Card Unlockied (for HAT): Triggered whenever a card is physically unlocked by sliding the card latch into the unlocked position.
Y
N
Diagnostics
Card Removal Cancelled (Relocked): A card is locked, unlocked, and again locked, without being pulled.
Y
N
Diagnostics
Card Ready for Removal: Indicates that a card can now safely be removed from the chassis.
Y
N
Diagnostics
Card Pulled When Not Ready: A card is physically removed from the chassis and was not ready for removal.
Y
N
Diagnostics
Card Pulled When Ready: A card is physically removed from the chassis and it was ready for removal.
Y
N
Diagnostics
Card Failed (for HAT): A card failed.
Y
Y
Diagnostics
Card Not Usable: A card is not usable due to failure, unknown type, etc.
Y
Y
Diagnostics
Card Initialized:The NPUMGR on an application card (SPC/PAC/TAC) finished initializing hardware.
Y
N
Diagnostics
Card Initialization Failed: The NPUMGR on an application card (SPC/PAC/TAC) does not finish initializing hardware within the timout period.
Y
Y
Diagnostics
Card Became Active: The card is active.
Y
N
Diagnostics
Card missing Required Daughter Card: The card is missing required daughter card.
Y
Y
Diagnostics
Card Type Invalid For Redundancy Mode: The card installed is not valid for redundancy mode.
Y
Y
Diagnostics
Card Type Invalid For Framing Mode: The card installed is not valid for framing mode that is being configured on the card.
Y
Y
Diagnostics
Card Has Entered Low Power Mode: The card has entered a low power mode.
Y
Y
Diagnostics
Card Has Left Low Power Mode: The card has recovered from an earlier error condition of low power mode.
Y
N
Diagnostics
Unsupported Card Insert: The newly inserted card is not supported on the chassis.
Y
N
Diagnostics
Unsupported Card Locked: An unsupported card is physically locked by sliding the card latch into the locked position.
Y
N
Diagnostics
Unsupported Card Unlocked: An unsupported card is phycially unlocked by sliding the card latch into the unlocked position.
Y
N
Diagnostics
Unsupported Card Ready for Removal: The unsupported card can now safely be removed from the chassis.
Y
N
Diagnostics
Unsupported Card Pulled: An unsupported card is physically removed from the chassis.
Y
N
Diagnostics
Unsupported Card Shutdown Issued: An unsupported card's administrative state is set to disabled because of a 'shutdown' command.
Y
N
Diagnostics
Warning: Card Unlocked [for CSP-Card Slot Port]: Triggered whenever a card is physically unlocked by sliding the card latch into the unlocked position.
Y
N
Diagnostics
Card Failed [for CSP]: A card has failed.
Y
Y
Diagnostics
IDEEPROM Failed: When a CSP subsystem detects an IDEEPROM failure; when it fails to read it, CSP notifies HATSYSTEM (High Availability Task - this is a software task that manages the operational state of the system).
Y
Y
Diagnostics
CPU Failed: The CPU has failed.
Y
Y
Diagnostics
Memory failed: Too many memory ECC unrecoverable errors occur. The device will automatically try to reboot the card, and if this fails, a card failure alert will be triggered.
Y
N
Diagnostics
RCC Switch Fabric Failed: The RCC VC3002 switch fabric has failed.
Y
Y
Diagnostics
FPGA Failed on a Card: A FPGA failure is detected.
Y
Y
Diagnostics
GE Switch Failed: A Gigabit Ethernet switch on the Switch Processor Card (SPC)/System Management Card (SMC) SPC or Packet Services Cards (PSC/PAC) has failed.
Y
Y
Diagnostics
Vitesse Switch Fabric Failed: The Vitesse Switch Fabric has failed on SPC or PAC.
Y
Y
Diagnostics
NPU Subsystem Failed: Network Processing Unit manager (NPUMGR) detects NPUT component failure, which leads to the NPU subsystem failure, and wants to take card recovery action. The device will automatically try to reboot the card, and if this fails, a card failure alert will be triggered.
Y
N
Diagnostics
LC Failed: NPUMGR reports that a line card failed.
Y
Y
Diagnostics
Card Failed Recovery Attempt Failed: A card failure recovery attempton High Availability Task (HAT) request by CSP fails.
Y
Y
Diagnostics
Card Error Detected: A recoverable error has occurred on a card.
Y
Y
Diagnostics
Crash: A crash has occurred in the device.
Y
Y
Environment
Alarm Type
Alarm message information
Notify
Create Service Request
Environment
Temperature Recovery of a Card Completed: Temperature of a card drops to normal after an overtemp event.
Y
N
Environment
Temperature Failed: HATCPU detects a card failed because of over temperature.
Y
N
Environment
Card Temperature Under 20C Degrees: A card is experiencing an under temperature condition. The safe operating range for the chassis and its subcomponents is 0 - 55ºC. The device is powered off at 0ºC, allowed to reach equilibrium, then is powered back up.
Y
N
Environment
Card Temperature over 71C Degrees: Temperature of a card is experiencing a high temperature condition.
Y
N
Environment
Multiple Cards Over 71C Degree Temperature Failure: Multiple over temperature conditions have occurred in the chassis.
Y
N
Environment
Fan Failed: A fan failure is identified on the device.
Y
N
Environment
Fan Tray Inserted
Y
N
Environment
Fan Tray Removed
Y
N
Environment
Mismatched Power Control States: Standby HATSYSTEM power control map does not match with that on primary HATSYSTEM and overwrites its value with that of primary HATSYSTEM state.
Y
N
Environment
Power Control Failure: Any of the four power sources fluctuate beyond specified limits.
Y
N
Environment
Power Applied from Power Filter: Power is applied from a DC power filter in the chassis.
Y
N
Environment
Power Remoted from Power Filter: Power is removed from a DC power filter in the chassis.
Y
N
Environment
Card Sensor Access Failure: The sensor on a card is inaccessible. The card will be shut down by the system.
Trace-back - Assertion - The device crashed due to an assertion error.Y
Y
Diagnostics
Trace-back - Assertion w/ block corruption - The device crashed due to block corruption.Y
Y
Diagnostics
Trace-back - Checkheaps - The device crashed because of memory corruption.Y
Y
Diagnostics
Trace-back - Page Fault - The device crashed when accessing an invalid memory address Y
Y
Diagnostics
Trace-back - Watchdog Timeout - The device crashed because a process was stuck, usually because of deadlock.
Y
Y
Diagnostics
Mini-Dump - ASA Crash Recovery Dump - The device recovered from an internal error.N
N
Diagnostics
Failover - Set by the config command: A CLI command was issued causing a failover switch from active or standby.
Y
N
Diagnostics
Failover - Failover state check: The failover state changed because the failover states of both units were not in a stable state.
N
N
Diagnostics
Failover - Failover interface become OK: The failover state changed because the failed/down interfaces are now back on-line.
N
N
Diagnostics
Failover - HELLO not heard from mate: The failover state changed because the device lost its coNections with the peer unit.
Y
N
Diagnostics
Failover - Other unit has different software version: The ASA failover pair do not have matched software images.
Y
N
Diagnostics
Failover - Other unit operating mode is different: The ASA failover pair do not have matched operating mode (one is in single mode and the other is in multiple mode).
Y
N
Diagnostics
Failover - Other unit license is different: The ASA failover pair do not have matched licenses.
Y
N
Diagnostics
Failover - Other unit chassis configuration is different: The ASA failover pair are not the same model.
Y
N
Diagnostics
Failover - Other unit card configuration is different: The ASA failover pair do not have the same software module card or interface card.
Y
N
Diagnostics
Failover - Other unit wants me Active: The "no failover active" command was issued on the peer device in order to switch the peer to standby and make this ASA become active.
Y
N
Diagnostics
Failover - Other unit wants me Standby: The "failover active" command was issued on the peer unit to switch the peer to active and make this ASA become standby.
Y
N
Diagnostics
Failover - Other unit reports that I am failed: The failover peer device did not receive the failover message because this ASA device is too busy to answer failover traffic.
Y
Y
Diagnostics
Failover - Other unit reports that it is failed: The failover peer unit experienced a hardware failure.
Y
Y
Diagnostics
Failover - Configuration mismatch: The ruNing configurations on the two ASA failover peer units are not synced.
N
N
Diagnostics
Failover - Detected an Active mate: A peer unit was detected.
N
N
Diagnostics
Failover - No Active unit found: Failover peer was not found.
N
N
Diagnostics
Failover - Recovered from communication failure: The failover pair re-established communication.
N
N
Diagnostics
Failover - Incomplete configuration synchronization: Configuration sync is not completed and configuration on the standby unit is not synchronized.
Y
N
Diagnostics
Failover - Configuration synchronization failed: Configuration synchronization failed and configuration is not able to get synced from the active unit.
Y
N
Diagnostics
Failover - Interface check: The interface check failed on this device; the interfaces were either down or failed.
Y
N
Diagnostics
Failover - ACK not received for failover message: An acknowledgement for a failover message sent by this device was not received from peer unit.
Y
N
Diagnostics
Failover - Other unit got stuck in learn state after sync: The peer unit of the failover group is stuck in config sync.
Y
N
Diagnostics
Failover - No failover cable: The failover serial cable does not exist.
Y
N
Diagnostics
Failover - HA state progression failed: The failover state transition failed.
Y
N
Diagnostics
Failover - Detect service card failure: The service card has failed on this device.
Y
N
Diagnostics
Failover - Service card in other unit has failed: The service card has failed on the peer unit of the failover group.
N
N
Diagnostics
Failover - My service card is as good as peer: The service card becomes operational, or the peer unit's service card failed.
N
N
Diagnostics
Failover - LAN Interface become un-configured: Failover LAN interface is not configured.
N
N
Diagnostics
Failover - Peer unit just reloaded: The peer unit just reloaded.
N
N
Diagnostics
Failover - Switch from Serial Cable to LAN-Based fover Switched from serial cable to LAN-based failover.
N
N
Diagnostics
Failover - Auto-Update request: The auto-update module requested the failover state change.
N
N
Diagnostics
[Primary] Failover switched from Bulk Sync to Standby Ready. Reason: No Error
N
N
Diagnostics
[Primary] Failover switched from Not Detected to Disabled. Reason: No Error
N
N
Diagnostics
[Secondary] Failover group 1 switched from Bulk Sync to Standby Ready. Reason: No Error
N
N
Environment
Alarm Type
Alarm Message Information
Notify
Create Service Request
Environment
Memory Module 1 Temperature OK: 170 C
Y
N
Environment
Memory Module 5 Voltage OK: 187 Volts
Y
N
Environment
Power Supply 2 Cooling Fan OK: 0 RPM
Y
N
Environment
Power Supply 2 Voltage OK: 139 Volts
Y
N
Environment
Mainboard 6 Voltage OK: 130 Volts
Y
N
Environment
Power Supply 2 Cooling Fan Failure Detected
Y
Y
Environment
Power Supply 2 Voltage Critical
Y
N
Environment
Mainboard 6 Voltage Critical
Y
N
Environment
Memory Module 5 Voltage Critical
Y
N
Environment
Health - Cooling Fan x Fail: Cooling fan x has failed.
Y
Y
Environment
Health - Cooling Fan x OK: Cooling fan x has been restored to normal operation.
N
N
Environment
Health - Cooling Fan Redundancy Lost: This message is accompanied by a cooling fan failure. Cooling Fan unit redundancy has been lost.
Y
Y
Environment
Health - Cooling Fan Redundancy OK: Cooling Fan redundancy has been restored.
N
N
Environment
Health - Power Supply Redundancy Lost :This message is accompanied by a power supply failure. Power supply unit redundancy has been lost.
Y
N
Environment
Health - Power Supply Redundancy OK: Power supply unit redundancy has been restored.
N
N
Environment
Health - CPU x Temperature Critical: CPU x has reached a critical temperature.
Y
Y
Environment
Health - CPU x Temperature Warm: CPU x is near the critical value, but is still within a functioning range.
Y
Y
Environment
Health - CPU x Temperature OK: CPU x has returned to normal operating temperature.
N
N
Environment
Health - Chassis x Temperature Critical: Chassis x temperature has reached a critical level.
Y
Y
Environment
Health - Chassis x Temperature Warm: Chassis x temperature is near critical value, but is still within operating range.
Y
Y
Environment
Health - Chassis x Temperature OK: Chassis x has returned to normal operating temperature.
N
N
Environment
Health - Power Supply x Temperature Critical: Power supply x has reached a critical level.
Y
Y
Environment
Health - Power Supply x Temperature Warm: Power supply x is near critical value but still within a functional range.
Y
Y
Environment
Health - Power Supply x Temperature OK: Power supply x has returned to a normal operating temperature.
N
N
Environment
Health - Power Supply x Failure Detected: Power supply x has been lost or the power supply has failed.
Y
Y
Environment
Health - Power Supply x OK: Power supply x has been restored to normal operation.
N
N
Environment
Resource - Memory Usage High: Memory usage is higher than configured threshold (default 90%).
Y
Y
Environment
Resource - Memory Usage OK: Memory usage is back to normal (default 85% or lower).
N
N
Environment
Resource - CPU Usage High: CPU usage is higher than configured threshold (default 90%).
Y
Y
Environment
Resource - CPU Usage OK: CPU usage is back to normal (default 85% or lower).
N
N
Syslogs
Alarm Type
Alarm Message Information
Notify
Create Service Request
Syslogs
ASA-5-711005: Traceback: This syslog message is logged on the device because of an internal software error.
TestPortAsicStackPortLoopback - The device failed the TestPortAsicStackPortLoopback test; this is a non-disruptive test.
Y
N
Diagnostic
TestPortAsicLoopback - The device failed the TEstPortAsicLoopback test; this is a disruptive on-demand test. The switch will reload after test completion.
Y
Y
Diagnostic
TestPortAsicCam - The device failed the TestPortAsicCam test; this is a disruptive on-demand test. This test will cause the switch under test to reload.
Y
Y
Diagnostic
TestPortAsicRingLoopback - The device failed the TestPortAsicRingLoopback test; this is a disruptive on-demand test. The test will cause the switch under test to reload.
Y
N
Diagnostic
TestMicRingLoopback - The device failed the TestMicRingLoopback test; this is a disruptive on-demand test. This test will cause the switch under test to reload. If the switch under test is in a stack and a test causes the switch to lose stack connectivity, the switch will reload when it rejoins the stack.
Y
N
Diagnostic
TestPOrtAsicMem - The device failed the TestPortAsicMem test; this is a disruptive on-demand test. The test will cause the switch under test to reload. If the switch under test is in a stack and a test causes the switch to lose stack connectivity, the switch will reload when it rejoins the stack.
Y
N
Diagnostic
TestInlinePwrCtlr - The device failed the TestInlinePwrCtlr test; this is a disruptive on-demand test. The test will cause the switch under test to reload. If the switch under test is in a stack and a test causes the switch to lose stack connectivity, the switch will reload when it rejoins the stack.
Y
Y
Environment
Alarm Type
Alarm message information
Notify
Create Service Request
Environment
TempHigh - The operating temperature has risen above the <yellow/red> threshold value.
Y
N
Environment
CriticalTemp - The operating temperature has risen above the <yeloow/red> threshold value.
Y
N
Environment
PowerSupplyBad - The device recorded a power supply alarm.
Y
N
Environment
PowerSupplyFanBad - The device recorded an alarm on fan in the power supply.
Y
N
Environment
InlinePowerSupplyBad - The device recorded an alert condition on the power supply.
Y
N
Environment
RedundantPowerSupplyFailure - The device recorded a power supply alarm.
Y
N
Environment
FanTrayBad - The device recorded an alert condition on the fans.
Supervisor-bootup - Runs only on Supervisor modules as part of POST and performs CPU, traffic, system, system memory, and feature tests.
Y
Y
Diagnostics
Packet-memory-bootup - Boot time memory test performing diagnostics on SRAM and runs for all Supervisor modules to check if the packet-memory is initialized properly.
Y
Y
Diagnostics
Packet-memory-ongoing - This test performs diagnostics on SRAM and runs all the time on all Supervisor modules to ensure that packet-memory has valid data and that the data has not been corrupted.
Y
Y
Diagnostics
Linecard-online-diag - Verifies that all ports on a linecard are working correctly.
Y
Y
Diagnostics
Online-diag-tdr - Uses the Time Domain Reflectometer (TDR) feature to determine if the network cabling is at fault.
Y
N
Diagnostics
Stub-rx errors - Tests the data path from the supervisor to the line cards.
Y
Y
Diagnostics
Supervisor-rx-errors: Tests the data path from the supervisort to the line cards.
Y
Y
Environment
Alarm Type
Alarm message information
Notify
Create Service Request
Environment
Redundancy Power Supply Failure - The second power supply installed on the switch, the backup, is detected and determined to be incompatible with the primary power supply.
Y
N
Environment
No Sufficient Power failure.
Y
N
Environment
Fan Assembly failure.
Y
N
Environment
System Alarms exceed critical or warning threshold.
Y
N
Environment
Bad Power Supply failure.
Y
N
Environment
Module major alarm on Module x All Module Temp Sensors failed.
Y
N
Environment
Module warning alarm on Module x Some Module Temp Sensors failed.
Y
N
Environment
Power warning alarm on Power Supply x Inline Power failed.
Y
N
Environment
Power warning alarm on Power Supply x Power Supply decreased.
Y
N
Environment
Power warning alarm on Power Supply x Power Supply Fan failed.
Y
N
Environment
System major alarm on Fan Tray bad.
Y
N
Environment
System warning alarm on Fan Tray Fan Assembly failure: partial.
Y
N
Environment
System warning alarm on Fan Tray Partial failure.
Y
N
Environment
Module major alarm on Module x All Module Temp Sensors failed.
TestSPRPInbandPing - This test fails when the Switch Processor (SP) is not properly communicating with the Route Processor (RP) on the Supervisor module.
Y
Y
Diagnostics
TestScratchRegister - Monitors the health of the application-specific integrated circuits (ASICs) by writing values into registers then reading them back.
Y
Y
Diagnostics
TestMacNotification - Verifies the data and control path between the DFC modules.
Y
Y
Diagnostics
TestNonDisruptiveLoopback - Verifies the data path between the supervisor and the network ports of a line card.
Y
Y
Diagnostics
TestUnusedPortLoopback - A health monitoring test and runs every 60 seconds on admin-down ports.
Y
Y
Diagnostics
TestAsicSync - Periodically tests the status of bus and port synchronization ASICs.
Y
Y
Diagnostics
TestLoopback - Verifies the data path between the supervisor and the network ports of a line card.
Y
Y
Diagnostics
TestEarlMemOnBoot-up: An exhaustive test that tests all the bits and locations of EARL memories, supported by Generic Memory Testing Logic (GMTL); runs as a boot-up test.
Y
Y
Diagnostics
TestMgmtPortsLoopback: Tests layer 3 connectivity from the supervisor's in-band port to the Firewall/NAM service module to verify the health of the longest data path in the module.
Y
Y
Diagnostics
TestDataportLoopback: Tests layer 3 connectivity from the supervisor inbound port to one of the data ports on the service module.
Y
N
Diagnostics
TestDCPLoopback: Checks the data plane data path.
Y
N
Diagnostics
TestCCPLoopback: Checks the control plane data path.
Y
N
Diagnostics
TestNPLoopback: Verifies the data path between supervisor engine and four different NPs on ACE30.
Y
Y
Diagnostics
TestActiveToStandbyLoopback - Verifies the data path between the active supervisor and the network ports of the standby supervisor.
Y
N
Diagnostics
TestTransceiverIntegrity - Performed on the transceiver during transceiver Online Insertion and Removal (OIR) or card bootup to make sure the transceiver is supported.
Y
N
Diagnostics
TestNetflowInlineRewrite - Verifies netflow operation, ACL permit/deny, inline rewrite capabilities of the ASIC.
Y
Y
Diagnostics
TestNewIndexLearn - Makes sure that existing MAC address table entries can be updated.
N
N
Diagnostics
TestDontConditionalLearn - Verifies that the new source MAC addresses are not populated in the MAC address table when they should not be learned.
N
N
Diagnostics
TestBadBpdu - Verifies that the Trap feature of the Layer 2 forwarding engine is working properly.
N
N
Diagnostics
TestBadBpduTrap - Verifies the Trap feature of the Layer 2 forwarding engine.
N
N
Diagnostics
TestMatchCapture - Verifies the ability to match on specific Layer 2 protocols in the Layer 2 forwarding engine.
N
N
Diagnostics
TestStaticEntry - Verifies the ability to populate static entries in the Layer 2 MAC address table.
Y
Y
Diagnostics
TestDontLearn - Verifies the Don't Learn feature of the Layer 2 forwarding engine.
N
N
Diagnostics
TestNewLearn - Verifies the Layer 2 source MAC address learning functionality of the Layer 2 forwarding engine.
Y
Y
Diagnostics
TestIndexLearn - Verifies the Index Learn feature of the Layer 2 forwarding engine.
Y
Y
Diagnostics
TestConditionalLearn - Verifies the ability to learn a Layer 2 source MAC address under specific conditions.
N
N
Diagnostics
TestTrap - Verifies the Trap feature of the Layer 2 forwarding engine.
N
N
Diagnostics
TestBpduTrap - this test is a combination of TestBpdu and TestTrap. TestTrap verifies the ability to trap or redirect packets to the CPU. TestBpdu verifies the ability to redirect BPDU packets to the CPU.
Y
Y
Diagnostics
TestProtocolMatchChannel - Verifies the ability to match on specific Layer 2 protocols in the Layer 2 forwarding engine.
Y
Y
Diagnostics
TestCapture - Verifies the Capture (cap1) feature of the Layer 2 forwarding engine.
N
N
Diagnostics
TestFibDevices - Verifies whether the Forwarding Information Base (FIB) ternary content addressable memory (TCAM) and adjacency devices are functional.
Y
Y
Diagnostics
TestPortSecurity - Verifies the ability to redirect packets to the switch processor, if a secure MAC address is transmitting the packets from a different port.
Y
Y
Diagnostics
TestAclRedirect - Verifies the ACL redirect feature of the layer 3 forwarding engine (Supervisor Engine 2T).
Diagnostics
TestRBAcl - Verifies the role based ACL feature of the layer 3 forwarding engine (Supervisor Engine 2T).
Y
Y
Diagnostics
TestDQUP - Verifies the policer update packets can be generated when diagnostic packets hit QoS entry (Supervisor Engine 2T).
Y
Y
Diagnostics
TestInbandEdit - Verifies the inband edit packets of the layer 3 forwarding engine (Supervisor Engine 2T).
Y
Y
Diagnostics
TestIPv4FibShortcut - Verifies the IPV4 Forwarding Information Base (FIB) forwarding of the Layer 3 forwarding engine.
N
N
Diagnostics
TestNATFibShortcut - Verifies the ability to rewrite a packet based on network address translation (NAT) adjacency information (rewrite destination IP address).
N
N
Diagnostics
TestAclPermit - Verifies the access control list (ACL) permit functionality.
Y
Y
Diagnostics
TestNetflowShortcut - Verifies the Netflow forwarding of the Layer 3 forwarding engine.
N
N
Diagnostics
TestQos - Verifies whether the Quality of Service (QoS) input/output ternary content addressable memory (TCAM) is functional.
N
N
Diagnostics
TestIPv6FibShortcut - Verifies the IPV6 Forwarding Information Base (FIB) forwarding of the Layer 3 forwarding engine.
N
N
Diagnostics
TestMPLSFibShortcut - Verifies that the MPLS forwarding of the Layer 3 forwarding engine is working properly.
N
N
Diagnostics
TestL3Capture2 - Verifies the Layer 3 Capture (Capture 2) feature of the Layer 3 forwarding engine.
N
N
Diagnostics
TestL3TcamMonitoring - Enabled by default as a health monitoring test, verifies L3 packet switching (Supervisor Engine 2T).
Y
Y
Diagnostics
TestL2CTSLoopback - provides encapsulation for Layer 2 Ethernet packets sent from the supervisor engine inband port to each port inside the Ganita ASIC. The test sends back the Layer 2 Ethernet packet to the supervisor engine inband port after decapsulation with its original content.
Y
Y
Diagnostics
TestL3CTSLoopback - provides encapsulation for Layer 3 IPv4 packets sent from the supervisor engine inband port to each port inside the Ganita ASIC and sends back the Layer 3 IPv4 packet to the supervisor engine inband port after decapsulation with its original content.
Y
Y
Diagnostics
TestAclDeny - Verifies the access control list (ACL) deny feature of the Layer 2 and Layer 3 forwarding engine.
N
N
Diagnostics
TestL3VlanMet - Verifies the multicast functionality of the replication engine.
Y
Y
Diagnostics
TestIngressSpan - Ensures that the port application-specific integrated circuit (ASIC) is able to tag packets for ingress Switched Port Analyzer (SPAN).
N
N
Diagnostics
TestEgressSpan - Verifies the proper operation of the egress Switched Port Analyzer (SPAN) replication functionality of the rewrite engine for both SPAN queues.
N
N
Diagnostics
TestFabricVlanLoopback - a non-disruptive test supported for supervisors and line cards that have fabric switching ASIC. Tests the data path between the in-band port of the card under test and the local fabric port responsible for switching the traffic from and to the in-band port.
Y
Y
Diagnostics
TestFabricInternalSnake - Internal snake test.
Y
Y
Diagnostics
TestFabricSnakeBackward - External snake test.
Y
Y
Diagnostics
TestSynchedFabChaNel - Sends a Serial Control Protocol (SCP) control message to the line card and fabric to query the synch status.
Y
Y
Diagnostics
TestFabricCh0Health - Constantly monitors the health of the ingress and egress data paths for fabric channel #0 on 10G line cards.
Y
Y
Diagnostics
TestFabricCh1Health - Constantly monitors the health of the ingress and egress data paths for fabric channel #1 on 10G line cards.
Y
Y
Diagnostics
TestFibTcamSSRAM - Exhaustive memory test that checks the Forwarding Information Base (FIB) ternary content addressable memory (TCAM) and Layer 3 adjacency static random access memory (SSRAM).
Y
Y
Diagnostics
TestFibTcam - Exhaustive memory test that checks the Forwarding Information Base (FIB) ternary content addressable memory (TCAM) (Supervisor Engine 2T).
Y
Y
Diagnostics
TestAsicMemory - Exhaustive memory test that checks all memories on a module (supervisor or line card) using the MarchC test algorithm.
Y
Y
Diagnostics
TestAclQosTcam - Tests all the bits and locations of both access control lists (ACLs) and Quality of Service (QoS) Ternary Content Addressable Memory (TCAMs) on PFC3BXL, PFC3B, and Supervisor Engine 2T.
Y
Y
Diagnostics
TestNetflowTcam - Tests all the bits and locations of Netflow ternary content addressable memory (TCAM).
Y
Y
Diagnostics
TestQoSTcam - Exhaustive memory tests for Quality of Service (QoS) ternary content addressable memory (TCAM) devices.
Y
Y
Diagnostics
TestIPSecClearPkt - Verifies that encryption is not performed on sent packets.
N
N
Diagnostics
TestHapiEchoPkt - Sends a Hapi Echo packet to the crypto engine using the control path to get a packet echoed back from the crypto engine.
N
N
Diagnostics
TestIPSecEncryptDecryptPkt - Verifies that the encryption and decryption processes are working correctly.
Y
N
Diagnostics
TestTrafficStress - Stress test the system by using all the line cards on the chassis and ensuring that no packets get dropped.
N
N
Diagnostics
TestEobcStressPing - Stress-test a particular line card's Ethernet out-of-band chaNel (EOBC) link with the supervisor.
Y
Y
Diagnostics
ScheduleSwitchover - Allows the customer to trigger switch over at a desired date/time.
N
N
Diagnostics
TestFirmwareDiagStatus - Displays the result of power-on diag tests run by firmware during line card bring-up.
Y
Y
Diagnostics
TestOBFL - Verifies the on-board failure logging capabilities.
N
N
Diagnostics
TestCFRW - Performs a read write test on inserted compact flash (CF) card.
Y
N
Diagnostics
TestL3HealthMonitoring - Health monitoring test that runs periodically to check ASIC (Earl) error conditions.
Y
Y
Diagnostics
TestVslLocalLoopback - Verifies the hardware functionality of each port on a Vsl card before the Vsl link interface is up.
Y
Y
Diagnostics
TestVslStatus - Reports the status change detected by VSLP protocol.
Y
Y
Diagnostics
TestPortTxMonitoring - This test will error disable the failed port upon failure.
Y
N
Diagnostics
TestFabricFlowControlStatus - Detects chaNel rate reduction below the threshold, current fabric-chaNel utilization above the threshold, peak fabric-chaNel utilization and SP CPU utilization above the threshold.
Y
N
Diagnostics
TestSpuriousIsrDetection - Runs when an interrupt is detected on a fabric ASIC.
Y
N
Diagnostics
TestVDB - Check that ready bit is asserted and diag-fail bit is not.
Y
Y
Diagnostics
BusCoNectivityTest - A disruptive test and runs automatically during bootup and Health monitoring test.
Y
N
Diagnostics
TestIntPortLoopback - A nondisruptive health monitoring test.
Y
Y
Diagnostics
TestVslBridgeLink - Provides the diagnostic coverage not covered by the TestVslLocalLoopback test.
Y
Y
Diagnostics
TestVSActiveToStandbyLoopback - Only GOLD test which tests the full datapath across the virtual switch links.
Y
Y
Diagnostics
TestIPSecBaseComponents - covers as much component parts in IPSec base module (Cheronia) card as possible in run-time environment for hardware functionality and integrity check.
Y
Y
Diagnostics
TestIPSecSPAComponents - checks the components in the IPSec Shared Port Adapter (SPA) sub-module (Zamboni) in a run-time environment for hardware functionality and integrity check.
Y
Y
Diagnostics
TestL3Capture - erifies that the Layer 3 capture (capture 1) feature of the Layer 3 forwarding engine is working properly.
Y
N
Environment
Alarm Type
Alarm message information
Notify
Create Service Request
Environment
System minor alarm on fan-tray x fan-fail
Y
Y
Environment
System major alarm on backplane clock count
Y
Y
Environment
System minor alarm on clock x OK
Y
Y
Environment
System major alarm on VTT x outlet temperature
Y
N
Environment
System minor alarm on VTT x outlet temperature
Y
N
Environment
System minor alarm on VTT x OK
Y
Y
Environment
Module major alarm on module x fan-upgrade required
Y
N
Environment
System minor alarm on power-supply x fan-fail
Y
N
Environment
System minor alarm on power-supply x power-output-fail
Y
N
Environment
Module major alarm on module x inlet temperature
Y
N
Environment
Module major alarm on module x outlet temperature
Y
N
Environment
Module major alarm on RP x inlet temperature
Y
N
Environment
Module major alarm on RP x outlet temperature
Y
N
Environment
Module major alarm on EARL x inlet temperature
Y
N
Environment
Module major alarm on EARL x outlet temperature
Y
N
Environment
Module major alarm on module x device-1 temperature
Y
N
Environment
Module major alarm on module x device-2 temperature
Y
N
Environment
System minor alarm on power-supply x incompatible with fan
Y
N
Environment
Module major alarm on module x insufficient cooling
Y
N
Environment
System minor alarm on backplane clock count
Y
Y
Environment
System minor alarm on backplane VTT count
Y
Y
Environment
System major alarm on backplane VTT count
Y
N
Environment
System minor alarm on backplane Fantray count
Y
N
Environment
Module minor alarm on module x inlet temperature
Y
N
Environment
Module minor alarm on module x outlet temperature
Y
N
Environment
Module minor alarm on module x device-1 temperature
Y
N
Environment
Module minor alarm on module x device-2 temperature
Y
N
Environment
Module minor alarm on RP x inlet temperature
Y
N
Environment
Module minor alarm on RP x outlet temperature
Y
N
Environment
Module minor alarm on EARL x inlet temperature
Y
N
Environment
Module minor alarm on EARL x outlet temperature
Y
N
Environment
Module minor alarm on module x asic-1 temperature
Y
N
Environment
Module minor alarm on module x asic-2 temperature
Y
N
Environment
Module minor alarm on module x asic-3 temperature
Y
N
Environment
Module minor alarm on module x asic-4 temperature
Y
N
Environment
Module minor alarm on module x asic-5 temperature
Y
N
Environment
Module minor alarm on module x asic-6 temperature
Y
N
Environment
Module minor alarm on module x aux-1 temperature
Y
N
Environment
Module major alarm on module x asic-1 temperature
Y
N
Environment
Module major alarm on module x asic-2 temperature
Y
N
Environment
Module major alarm on module x asic-3 temperature
Y
N
Environment
Module major alarm on module x asic-4 temperature
Y
N
Environment
Module major alarm on module x asic-5 temperature
Y
N
Environment
Module major alarm on module x asic-6 temperature
Y
N
Environment
Module major alarm on module x aux-1 temperature
Y
N
Environment
System minor alarm on power-supply x power-output-mode
Temperature/Voltage alarm - Operating temperature has risen above the <Warning/Critical> threshold value.
Y
N
Environment
Fan number x failure (This failure is C7201 specific.) - One of router's cooling fans failed.
Y
N
Environment
Power supply state changes from x to y - One of the power supply test points underwent a state change.
Y
N
Environment
Power minor/major alarm on Power Supply x inserted/removed - change in power supply status due to the removal or insertion of a power supply module in the system.
Y
N
Environment
Recovery - Device has recovered form a previously raised environmental alarm.
Y
N
Environment
Temperature minor alarm on I/O controller
Y
N
Environment
Major Temperature alarm I/O Cont
Y
Y
Environment
Recovered: Module major alarm on Temp Sensor I/O Cont
Y
N
Environment
Minor Temperature alarm NPE
Y
N
Environment
Major Temperature alarm NPE
Y
Y
Environment
Recovered: Module major alarm on Temp Sensor NPE
Y
N
Environment
Minor Temperature alarm CPU Die
Y
N
Environment
Major Temperature alarm CPU Die
Y
Y
Environment
Recovered : Module major alarm on Temp Sensor CPU Die
System minor alarm on x/y/CPU0 host__InletTemp temp x(C),th:y(C): indicates that the temperature has exceeded the minor threshold limit on <LOCATION>.
Y
N
Environment
System major alarm on x/y/CPU0 host__InletTemp temp x(C),th:y(C): indicates that the temperature has exceeded the major threshold limit on <LOCATION>.
Y
N
Environment
System critical alarm on x/y/CPU0 host__InletTemp temp x(C),th:y(C): indicates that the temperature has exceeded critical threshold limit on <LOCATION>.
Y
N
Environment
System minor alarm on 0/2/CPU0 host__MB_12V volt 13000mV,th:12840mV: indicates that a minor voltage alarm has occurred on <LOCATION>.
Y
N
Environment
System minor alarm on 0/2/1 spa-volt 130 ,th:120: indicates that a minor voltage alarm has occurred on <LOCATION>.
Y
N
Environment
System major alarm on 0/2/CPU0 host__MB_12V volt 13000mV,th:12840Mv: indicates that a major voltage alarm has occurred on the card <LOCATION>.
Y
N
Environment
System major alarm on 0/2/1 spa-volt 130: indicates that a major voltage alarm has occurred on the card <LOCATION> ,th:120
Y
N
Environment
System critical alarm on 0/2/CPU0 host__MB_12V volt 13000mV,th:12840Mv: indicates that a critical voltage alarm has occurred on the card <LOCATION>.
Y
Y
Environment
System critical alarm on 0/2/1 spa-volt 130 ,th:120: indicates that a critical voltage alarm has occurred on the card <LOCATION>.
Y
Y
Environment
Power minor alarm on 0/24/CPU0 pwrs-shl-fail 1 ,th:-2: indicates a minor alarm due to power-shelf failure.
Y
N
Environment
Power major alarm on 0/24/CPU0 pwrs-shl-fail 1 ,th:-2: indicates a major alarm due to power-shelf failure.
Y
N
Environment
Power critical alarm on 0/24/CPU0 pwrs-shl-fail 1 ,th:-2: indicates a critical alarm due to power-shelf failure.
Y
Y
Environment
Power minor alarm on 0/24/CPU0 pwrs-shl-fault 1 ,th:-2: indicates a minor alarm due to faulty power-shelf.
Y
N
Environment
Power major alarm on 0/24/CPU0 pwrs-shl-fault 1 ,th:-2: indicates a major alarm due to faulty power-shelf.
Y
N
Environment
Power critical alarm on 0/24/CPU0 pwrs-shl-fault 1 ,th:-2: indicates a critical alarm due to faulty power-shelf.
Y
Y
Environment
System minor alarm on 0/5/1 spa-temp 56 ,th:55: indicates a minor alarm that the SPA temperature on <LOCATION>has risen above the minor threshold limit.
Y
Y
Environment
System major alarm on 0/5/1 spa-temp 56 ,th:55: indicates that the SPA temperature on <LOCATION>has risen above the majorthreshold limit.
Y
Y
Environment
System critical alarm on 0/5/1 spa-temp 56 ,th:55: indicates that the SPA temperature on <LOCATION>has risen above the criticalthreshold limit.
Y
Y
Environment
System minor alarm on 0/2/CPU0 host__MB_12A curr 130A,th:128A: indicates that a minor alarm has occurred on <LOCATION> due to abnormal current condition.
Y
Y
Environment
System major alarm on 0/2/CPU0 host__MB_12A curr 130A,th:128A: indicates that a major alarm has occurred on <LOCATION> due to abnormal current condition.
Y
N
Environment
System critical alarm on 0/2/CPU0 host__MB_12A curr 130A,th:128A: indicates that a critical alarm has occurred on <LOCATION> due to abnormal current condition.
Y
Y
Environment
Power minor alarm on 0/24/CPU0 pwrs-nonop 1 ,th:-2: indicates a minor power alarm on <LOCATION>.
Y
N
Environment
Power major alarm on 0/24/CPU0 pwrs-nonop 1 ,th:-2: indicates a major power alarm on <LOCATION>.
Y
N
Environment
Power critical alarm on 0/24/CPU0 pwrs-nonop 1 ,th:-2: indicates a critical power alarm on <LOCATION>.
Y
Y
Environment
Power minor alarm on Fan slot 29 fans 1 ,th:1: indicates that the router's cooling fan on slot <SLOT>has malfunctioned.
Y
N
Environment
Power major alarm on Fan slot 29 fans 1 ,th:1: indicates that the router's cooling fan on slot <SLOT>has malfunctioned.
Y
Y
Environment
Power critical alarm on Fan slot 29 fans 1 ,th:1: indicates that the router's cooling fan on slot <SLOT>has malfunctioned.
RMON_ALERT - The monitored object value is above or below the configured threshhold value.
Y
N
Diagnostics
SUP_FAILURE - The standby supervisor failed to boot up.
Y
Y
Diagnostics
SUP_FAILURE sup failure caused switchover
Y
Y
Diagnostics
LINECARD_FAILURE - All ports on this module will be unusable until the failure is cleared.
Y
Y
Diagnostics
PORT_FAILURE - A hardware failure has occurred on the Interface.
Y
N
Diagnostics
SW_CRASH - A service has terminated its execution abnormally and a syslog message is recorded.
Y
Y
Diagnostics
SW_SYSTEM_INCONSISTENT - An Upgrade process is aborted without user requesting an abort and/or due to an error.
Y
N
Diagnostics
BOOTFLASH_FAILURE - Bootflash on the active supervisor module failed and a switchover is forced.
Y
Y
Diagnostics
EOBC_FAILURE - An EOBC failure occured on the active supervisor and a switchover is forced.
Y
Y
Diagnostics
INBAND_FAILURE - Inband coNectivity failed on the module <module_no>.
Y
Y
Diagnostics
POWER_UP_DIAGNOSTICS_FAILURE - This alarm is generated when the linecard fails to bootup after it is powered up successfully.
Y
Y
Diagnostics
NAME_SERVER_DATABASE_FULL - Generated when the name server database has maximum allowed device entries in the fabric and a new a host or target tries to register itself to name server.
Y
Y
Diagnostics
NVRAM_FAILURE - Non-Volatile memory corrupted or failed on supervisor module.
Y
Y
Diagnostics
FREEDISK_FAILURE - Indicate that the " /tmp" diectory can be full or near full.
ManagementPortLoopback - Places the external Ethernet management port into loopback, sends a diagnostic packet to it, and verifies it is received.
Y
Y
Diagnostics
EOBCPortLoopback - Checks the internal Ethernet Out-of-Band ChaNel (EOBC) coNectivity.
Y
Y
Diagnostics
USB - Checks for the initialization of the USB controller on the supervisor card.
Y
Y
Diagnostics
CryptoDevice - Checks for the initialization of the Cavium Security chip on the Supervisor card.
Y
Y
Diagnostics
ASICRegisterCheck - Monitors the health of the application-specific integrated circuits (ASICs).
Y
Y
Diagnostics
SpineControlBus - Checks the standby control bus coNectivity from the spine card to the active Supervisor card.
Y
Y
Diagnostics
NVRAM - Periodically verifies the checksum of a small block of NVRAM.
Y
N
Diagnostics
RealTimeClock - Compares the RTC time with system clock, and verifies they are in sync.
Y
N
Diagnostics
PrimaryBootROM - Checks the integrity of the image programmed on the primary bootrom.
Y
N
Diagnostics
SecondaryBootROM - Verifies the image programmed on the secondary bootrom.
Y
N
Diagnostics
CompactFlash - Performs a read write test on the internal compact flash that stores bootup images.
Y
N
Diagnostics
ExternalCompactFlash - Performs a read write test External compact flash in slot 0.
Y
N
Diagnostics
PwrMgmtBus - Verifies the power management card and the power management Bus.
Y
N
Diagnostics
SystemMgmtBus - Checks the functionality of system management bus that coNects the supervisor to fan-tray, power supplies and system identification PROMs.
Y
N
Diagnostics
PortLoopback - Health monitoring test and at linecard bootup.
Y
N
Diagnostics
RewriteEngineLoopback - Verifies whether the forwarding device and rewrite engine on the linecards are functional.
Y
N
Diagnostics
LogFlash(ExternalCompactFlash) - LogFlash test performs a read/write test on the external LogFlash on the supervisor module slot1.
Y
N
Diagnostics
CMP_FAILURE - The device has a CMP failure with message <message from message description>.
Y
Y
Diagnostics
SUP_FAILURE - Standby supervisor failed and needs to be rebooted.
Y
Y
Diagnostics
LINECARD_FAILURE - Line card is not recognized by the device or the device is unable to bring up the line card.
Y
Y
Diagnostics
PORT_FAILURE - A Hardware failure has occurred on the interface <port string> and the port is down.
Y
N
Diagnostics
SW_CRASH - A service has terminated its execution abnormally and a syslog message is recorded.
ManagementPortLoopback - Places the external Ethernet management port into loopback, sends a diagnostic packet to it, and verifies it is received.
Y
Y
Diagnostics
EOBCPortLoopback - Checks the internal Ethernet Out-of-Band ChaNel (EOBC) coNectivity.
Y
Y
Diagnostics
USB - Checks for the initialization of the USB controller on the supervisor card.
Y
Y
Diagnostics
CryptoDevice - Checks for the initialization of the Cavium Security chip on the Supervisor card.
Y
Y
Diagnostics
ASICRegisterCheck - Monitors the health of the application-specific integrated circuits (ASICs).
Y
Y
Diagnostics
SpineControlBus - Checks the standby control bus coNectivity from the spine card to the active Supervisor card.
Y
Y
Diagnostics
NVRAM - Periodically verifies the checksum of a small block of NVRAM.
Y
N
Diagnostics
RealTimeClock - Compares the RTC time with system clock, and verifies they are in sync.
Y
N
Diagnostics
PrimaryBootROM - Checks the integrity of the image programmed on the primary bootrom.
Y
N
Diagnostics
SecondaryBootROM - Verifies the image programmed on the secondary bootrom.
Y
N
Diagnostics
CompactFlash - Performs a read write test on the internal compact flash that stores bootup images.
Y
N
Diagnostics
ExternalCompactFlash - Performs a read write test External compact flash in slot 0.
Y
N
Diagnostics
PwrMgmtBus - Verifies the power management card and the power management Bus.
Y
N
Diagnostics
SystemMgmtBus - Checks the functionality of system management bus that coNects the supervisor to fan-tray, power supplies and system identification PROMs.
Y
N
Diagnostics
PortLoopback - Health monitoring test and at linecard bootup.
Y
N
Diagnostics
RewriteEngineLoopback - Verifies whether the forwarding device and rewrite engine on the linecards are functional.
Y
N
Diagnostics
LogFlash(ExternalCompactFlash) - LogFlash test performs a read/write test on the external LogFlash on the supervisor module slot1.
Y
N
Diagnostics
CMP_FAILURE - The device has a CMP failure with message <message from message description>.
Y
Y
Diagnostics
SUP_FAILURE - Standby supervisor failed and needs to be rebooted.
Y
Y
Diagnostics
LINECARD_FAILURE - Line card is not recognized by the device or the device is unable to bring up the line card.
Y
Y
Diagnostics
PORT_FAILURE - A Hardware failure has occurred on the interface <port string> and the port is down.
Y
N
Diagnostics
SW_CRASH - A service has terminated its execution abnormally and a syslog message is recorded.
Y
N
Diagnostics
SW_SYSTEM_INCONSISTENT
Y
N
Environment
Alarm Type
Alarm Message Information
Notify
Create Service Request
Environment
TEMPERATURE_ALARM - This is a temperature faultalarm message for module x.
Y
N
Environment
TEMPERATURE_ALARM - This is a Minor temperature alarm message for module x.
Y
N
Environment
TEMPERATURE_ALARM - This is a Major temperature alarm message for module x.
Y
N
Environment
FAN_FAILURE - Fan Tray FAN_TRAY_NUM is reporting an alarm.
Y
Y
Environment
POWER_SUPPLY_FAILURE - There is insufficient power to operate all FRUs in the system.
Y
Y
Environment
POWER_SUPPLY_SHUTDOWN - Power Supply POWER_MOD has reported a power supply shutdown alarm.
Y
N
Environment
POWER_SUPPLY_FAILURE - Fan failure in power supply.
Y
Y
Environment
POWER_SUPPLY_ALERT- Detected an unsupported power supply.
Forwarding ASIC port failure - The Port(s) on the forwarding engine ASICs have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring.
Y
Y
Fex Diagnostics
Forwarding ASIC failure - The forwarding engine ASICs have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring.
Y
Y
Fex Diagnostics
OBFL Flash failure - This test verifies the integrity of the On Board Failure Logging flash (OBFL).
Y
N
Fex Diagnostics
GPIO Access failure - Tests the general purpose I/O (GPIO) components.
Temperature Alarm - Temp has exceeded threshold value.
Y
N
Fex Environment
PowerSupplyFailure - The device is currently working with only one Power Supply unit.
Y
N
Fex Environment
PowerSupplyOIR - Indicates a change in power supply status.
Y
N
Fex Environment
TEMPERATURE_ALARM --- Sensor - An access failure to Temperature Sensor is recorded on the device.
Y
N
Fex Environment
Fan failure.
Y
N
Fex Environment
Fan tray missing.
Y
N
Fex Environment
Module shutdown due to FAN failure.
Y
N
Fex Environment
Module shutdown due to over-temperature condition.
Y
N
N5K Diagnostics
Alarm Type
Alarm message information
Notify
Create Service Request
N5K Diagnostics
TestFabricPort - The Port(s) have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring.
Y
Y (if ports fail > 25%)
N5K Diagnostics
TestForwardingEngine - The Port(s) have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring.
Y
Y (if ports fail > 25%)
N5K Diagnostics
TestForwardingEnginePort - The Port(s) have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring.
Y
Y (if ports fail > 25%)
N5K Diagnostics
TestFrontPort - The Port(s) have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring.
Y
Y (if ports fail > 25%)
N5K Diagnostics
TestInbandPort - Since switch CPU can no longer run the appropriate control plane protocols, switch can no longer function.
Y
Y
N5K Diagnostics
TestFabricEngine - Fabric ASIC has reported major failure.
Y
Y
N5K Diagnostics
TestSPROM - Software determines module type based on information stored in Module SPROM.
Y
Y
N5K Diagnostics
TestOBFL - This failure can occur on module 1 only. OBFL is Onboard Fault Logging.
Y
Y
N5K Diagnostics
TestLED - LED control is done via the same transport mechanism to control other key components on a module.
Y
N
N5K Environment
Alarm Type
Alarm message information
Notify
Create Service Request
N5K Environment
TestFAN -- fan speed <speed> out of range >= expected. <speed> rpm.
Y
N
N5K Environment
TestPowerSuppy
N
N
N5K Environment
TestTemperatureSensor
N
N
N5K Environment
TEMPERATURE_ALARM --- Sensor.
Y
Y
N5K Environment
PowerSupplyFailure
Y
Y
N5K Environment
Multiple fans missing or failed.
Y
N
N5K Environment
One fan missing or failed.
Y
N
N5K Syslogs
Alarm Type
Alarm message information
Notify
Create Service Request
N5K Syslog
No license installed for feature, is on grace license, will expire in D H.
Y
N
N5K Syslog
License for feature, will expire in H M.
Y
N
N5K Syslog
License has expired for feature.
Y
N
N5K Syslog
License file is missing for feature.
Y
N
Syslog
%KERN-2-SYSTEM_MSG
Y
N
Syslog
%SYSMGR-2-VOLATILE_DB_FULL
Y
N
FEX Diagnostics
Alarm Type
Alarm message information
Notify
Create Service Request
Fex Diagnostics
Forwarding ASIC port failure - The Port(s) on the forwarding engine ASICs have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring.
Y
Y
Fex Diagnostics
Forwarding ASIC failure - The forwarding engine ASICs have failed this diagnostic test either during Power-On-Self-Test or during the Run Time monitoring.
Y
Y
Fex Diagnostics
OBFL Flash failure - This test verifies the integrity of the On Board Failure Logging flash (OBFL).
Y
N
Fex Diagnostics
GPIO Access failure - Tests the general purpose I/O (GPIO) components.
Y
N
FEX Environment
Alarm Type
Alarm message information
Notify
Create Service Request
Fex Environment
Temperature Alarm - Temp has exceeded threshold value.
Y
N
Fex Environment
PowerSupplyFailure - The device is currently working with only one Power Supply unit.
Y
N
Fex Environment
PowerSupplyOIR - Indicates a change in power supply status.
Y
N
Fex Environment
TEMPERATURE_ALARM --- Sensor - An access failure to Temperature Sensor is recorded on the device.
Y
N
Fex Environment
Fan failure.
Y
N
Fex Environment
Fan tray missing.
Y
N
Fex Environment
Module shutdown due to FAN failure.
Y
N
Fex Environment
Module shutdown due to over-temperature condition.
No license installed for feature, is on grace license, will expire in D H- The evaluation license installed for the <feature> is ruNing under grace period.
Y
N
Syslogs
License for feature, will expire in H M - The evaluation license installed for the <package> will expire in <show_license_usage:comments> and will be disabled soon.
Y
N
Syslogs
License has expired for feature.
Y
N
Syslogs
License file is missing for feature.
Y
N
Diagnostics
Alarm Type
Alarm message information
Notify
Create Service Request
Diagnostics
TestFrontPort & TestForwardingPort - The Port(s) have failed this diagnostic test during the Run Time monitoring.
Y
Y if ports failed >25%
Diagnostics
FREEDISK_FAILURE - Indicates that the " /tmp" directory can be full or near full.
Y
N
Diagnostics
NVRAM_FAILURE - Non-Volatile memory corrupted or failed on switch module <x>.
Y
N
Diagnostics
MGMT_PORT_FAILURE - Management Ethernet Port communications failed for the active supervisor module.
Y
N
Diagnostics
BOOTFLASH_FAILURE - On the switch module, the boot flash stores various vital information required for the operation of the switch.
Y
N
Syslogs
Alarm Type
Alarm message information
Notify
Create Service Request
Syslogs
No license installed for feature, is on grace license, will expire in D H- The evaluation license installed for the <feature> is ruNing under grace period.
Y
N
Syslogs
License for feature, will expire in H M - The evaluation license installed for the <package> will expire in <show_license_usage:comments> and will be disabled soon.
Y
N
Syslogs
License has expired for feature.
Y
N
Syslogs
License file is missing for feature.
Y
N
Environment
Alarm Type
Alarm message information
Notify
Create Service Request
Environment
Temperature Alarm.
Y
N
Environment
Outstanding Alarms support: The device has recorded a <component> status of '<failure_status_from show environment>'.
Y
N
Environment
Recovery Alarms support: This message indicates that the device has recovered from a previous environmental alarm condition.
