Message:<label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the internal temperature of the switch has changed.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. To prevent recurring messages, disable the changed alarm for this threshold. If you receive a temperature-related message, check for an accompanying fan-related message and check fan performance. If all fans are functioning normally, check the climate control in your lab.
Message: <Label>, is below low boundary (High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the internal temperature of the switch has fallen below the low boundary.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Typically, low temperatures means that the fans and airflow of a switch are functioning normally.
Verify that the location temperature is within the operational range of the switch. Refer to the Hardware Reference Manual for the environmental temperature range of your switch.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the internal temperature of the switch has risen above the high boundary to a value that may damage the switch.
Recommended Action: This message generally appears when a fan fails. If so, a fan-failure message accompanies this message. Replace the fan.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the internal temperature of the switch has changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. If you receive a temperature-related message, check for an accompanying fan-related message and check fan performance. If all fans are functioning normally, check the climate control in your lab.
Message: <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the speed of the fan has changed. Fan problems typically contribute to temperature problems.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Consistently abnormal fan speeds generally indicate that the fan is malfunctioning.
Message: <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the speed of the fan has changed. Fan problems typically contribute to temperature problems.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Consistently abnormal fan speeds generally indicate that the fan is malfunctioning.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the speed of the fan has risen above the high boundary. Fan problems typically contribute to temperature problems.
Recommended Action: Consistently abnormal fan speeds generally indicate that the fan is failing. Replace the fan.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the speed of the fan has changed from a value outside of the acceptable range to a value within the acceptable range. Fan problems typically contribute to temperature problems.
Recommended Action: No action is required. Consistently abnormal fan speeds generally indicate that the fan is failing. If this message occurs repeatedly, replace the fan.
Message: <Label>, value has changed (High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the state of the power supply has changed from faulty to functional or from functional to faulty.
Recommended Action: If the power supply is functioning correctly, no action is required.
If the power supply is functioning below the acceptable boundary, verify that it is seated correctly in the chassis. Execute the show environment power command to view the status of the power supply. If the power supply continues to be a problem, replace the faulty power supply.
Message: <Label>, is below low boundary (High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the power supply is faulty. The power supply is not producing enough power.
Recommended Action: Verify that the power supply is installed correctly and that it is correctly seated in the chassis. If the problem persists, replace the faulty power supply.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the power supply counter changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the temperature of the small form-factor pluggable (SFP) transceiver has fallen below the low boundary.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the temperature of the small form-factor pluggable (SFP) transceiver has risen above the high boundary.
Recommended Action: Frequent fluctuations in temperature may indicate a deteriorating SFP transceiver. Replace the SFP transceiver.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the temperature of the small form-factor pluggable (SFP) transceiver has changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: No action is required.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the receive power value of the small form-factor pluggable (SFP) transceiver has fallen below the low boundary. The receive performance area measures the amount of incoming laser to help you determine if the SFP transceiver is in good working condition or not. If the counter often exceeds the threshold, the SFP transceiver is deteriorating.
Recommended Action: Verify that the optical components are clean and functioning properly. Replace deteriorating cables or SFP transceivers. Check for damage from heat or age.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the receive power value of the small form-factor pluggable (SFP) transceiver has risen above the high boundary. The receive performance area measures the amount of incoming laser to help you determine if the SFP transceiver is in good working condition or not. If the counter often exceeds the threshold, the SFP transceiver is deteriorating.
Recommended Action: Replace the SFP transceiver before it deteriorates.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the receive power value of the small form-factor pluggable (SFP) transceiver has changed from a value outside of the acceptable range to a value within the acceptable range. The receive performance area measures the amount of incoming laser to help you determine if the SFP transceiver is in good working condition or not. If the counter often exceeds the threshold, the SFP transceiver is deteriorating.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the transmit power value of the small form-factor pluggable (SFP) transceiver has fallen below the low boundary. The transmit performance area measures the amount of outgoing laser to help you determine if the SFP transceiver is in good working condition or not. If the counter often exceeds the threshold, the SFP transceiver is deteriorating.
Recommended Action: Verify that the optical components are clean and functioning properly. Replace deteriorating cables or SFP transceivers. Check for damage from heat or age.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the transmit power value of the small form-factor pluggable (SFP) transceiver has risen above the high boundary. The transmit performance area measures the amount of outgoing laser to help you determine if the SFP transceiver is in good working condition or not. If the counter often exceeds the threshold, the SFP transceiver is deteriorating.
Recommended Action: Replace the SFP transceiver.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the transmit power value of the small form-factor pluggable (SFP) transceiver has changed from a value outside of the acceptable range to a value within the acceptable range. The transmit performance area measures the amount of outgoing laser to help you determine if the SFP transceiver is in good working condition or not. If the counter often exceeds the threshold, the SFP transceiver is deteriorating.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the value of the small form-factor pluggable (SFP) transceiver voltage has fallen below the low boundary.
Recommended Action: Verify that the optical components are clean and functioning properly. Replace deteriorating cables or SFP transceivers. Check for damage from heat or age.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the value of the small form-factor pluggable (SFP) transceiver voltage has risen above the high boundary.
Recommended Action:The supplied current of the SFP transceiver is outside of the normal range, indicating possible hardware failure. If the current rises above the high boundary, replace the SFP transceiver.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the value of the small form-factor pluggable (SFP) transceiver voltage has changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the value of the small form-factor pluggable (SFP) transceiver has fallen below the low boundary.
Recommended Action: Configure the low threshold to 1 so that the threshold triggers an alarm when the value falls to 0 (Out_of_Range). If continuous or repeated alarms occur, replace the SFP transceiver before it deteriorates.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the value of the small form-factor pluggable (SFP) transceiver voltage has risen above the high boundary. High voltages indicate possible hardware failures.
Recommended Action: Frequent voltage fluctuations are an indication that the SFP transceiver is deteriorating. Replace the SFP transceiver.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the value of the small form-factor pluggable (SFP) transceiver voltage has changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has fallen below the low boundary.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of invalid CRCs means the switch is functioning normally.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has risen above the high boundary.
Recommended Action: This error generally indicates an deteriorating fabric hardware. Check small form-factor pluggable (SFP) transceivers, cables, and connections for faulty hardware. Verify that all optical hardware is clean.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Frequent fluctuations in CRC errors generally indicate an aging fabric. Check the small form-factor pluggable (SFP) transceivers, cables, and connections for faulty hardware. Verify that all optical hardware is clean.
Message: <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences crossed lower threshold boundary to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Frequent fluctuations in CRC errors generally indicate an aging fabric. Check small form-factor pluggable (SFP) transceivers, cables, and connections for faulty hardware. Verify that all optical hardware is clean.
Message: <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has dropped below upper threshold boundary to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Frequent fluctuations in CRC errors generally indicate an aging fabric. Check small form-factor pluggable (SFP) transceivers, cables, and connections for faulty hardware. Verify that all optical hardware is clean.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of Abnormal Frame termination frames that the port experiences has fallen below the low boundary.
Recommended Action: No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of abnormal frame termination errors means the system is operating normally.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the number of abnormal frame termination frames that the port experiences has risen above the high boundary. Flapping interfaces during the traffic flow can generate this error.
Recommended Action: Check all loose connections in the fabric.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of abnormal frame termination frames that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check all loose connections in the fabric.
Message: <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of abnormal frame termination frames that the port experiences crossed lower threshold boundary to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check all loose connections in the fabric.
Message: <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of abnormal frame termination frames that the port experiences has dropped below upper threshold boundary to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check all loose connections in the fabric.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of frames with symbol error that the port experiences has fallen below the low boundary.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of symbol errors means the system is operating normally.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause:Indicates that the number of frames with symbol error that the port experiences has risen above the high boundary. Flapping interfaces or loose connections can cause this error.
A high number of symbol errors indicate a deteriorated device, cable, or hardware.
Recommended Action: Check your small form-factor pluggables (SFPs), cables, and connections for faulty hardware. Verify that all optical hardware is clean.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of frames with symbol error that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check all cables and form factors in the system.
Message: <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of frames with symbol error that the port experiences crossed lower threshold boundary to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check all cables and form factors in the system.
Message: <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of frames with symbol error that the port experiences has dropped below upper threshold boundary to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check all cables and form factors in the system.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of inter frame gap violation errors that the port experiences has fallen below the low boundary.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of inter frame gap errors means the system is operating normally.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the number of inter frame gap violation errors that the port experiences has risen above the high boundary. Flapping interfaces during the traffic flow can generate this error. Congestion or transmitting multiple frames without an inter frame gap.
Recommended Action: Check loose connections and congestion in the fabric.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of inter frame gap violation errors that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check loose connections and congestion in the fabric.
Message: <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of inter frame gap violation errors that the port experiences crossed lower threshold boundary to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check loose connections and congestion in the fabric.
Message: <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause:Indicates that the number of inter frame gap violation errors that the port experiences has dropped below upper threshold boundary to a value within the acceptable range.
Recommended Action: Respond to this message as is appropriate to the particular policy of the end-user installation. Check loose connections and congestion in the fabric.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of Telnet violations has fallen below the low boundary. Telnet violations indicate that a Telnet connection request has been received from an unauthorized IP address. The TELNET_POLICY contains a list of IP addresses that are authorized to establish Telnet connections to switches in the fabric.
Recommended Action: No action is required.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the number of Telnet violations has risen above the high boundary. Telnet violations indicate that a Telnet connection request has been received from an unauthorized IP address. The TELNET_POLICY contains a list of IP addresses that are authorized to establish Telnet connections to switches in the fabric.
Recommended Action: Execute the show logging raslog command to determine the IP address that sent the request. Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of Telnet violations has changed from a value outside of the acceptable range to a value within the acceptable range. Telnet violations indicate that a Telnet connection request has been received from an unauthorized IP address. The TELNET_POLICY contains a list of IP addresses that are authorized to establish Telnet connections to switches in the fabric.
Recommended Action: No action is required.
Message: <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of login violations has fallen below the low boundary. Login violations indicate that a login failure has been detected.
Recommended Action: No action is required.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the number of login violations has risen above the high boundary. Login violations indicate that a login failure has been detected.
Recommended Action: Execute the show logging raslog command to determine the IP address of the log in attempt. Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the number of login violations has changed from a value outside of the acceptable range to a value within the acceptable range. Login violations indicate that a login failure has been detected.
Recommended Action: No action is required.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the CPU or memory usage is between the boundary limits.
Recommended Action: No action is required.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the CPU or memory usage is above the configured threshold. If this message pertains to memory usage, then the usage is above middle memory threshold.
Recommended Action: No action is required.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the memory usage is above low threshold.
Recommended Action: No action is required.
Message: <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: CRITICAL
Probable Cause: Indicates that the memory usage is above the configured high threshold for memory usage.
Recommended Action: No action is required.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the memory usage is between the configured high and medium thresholds for memory usage.
Recommended Action: No action is required.
Message: <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the memory usage is between the configured low and medium thresholds for memory usage.
Recommended Action: No action is required.
Message: Current disk utilization is <Value> <Unit>. Deleting <File>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates high compact flash (CF) disk utilization.
Recommended Action: No action is required.
Message: Disk usage is greater than 60 percent and max number of Core file limit [5] has been exceeded. Deleting the oldest core file: <File>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the maximum number of core file limit has been exceeded.
Recommended Action: No action is required.
Message: Switch status changed from <Previous state> to <Current state>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because of a policy violation.
Recommended Action: Execute the show system monitor command to determine the policy violation.
Message: Switch status changed from <Bad state> to HEALTHY.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the switch status has changed to a healthy state. This state change occurred because a policy is no longer violated.
Recommended Action: No action is required.
Message: Switch status change contributing factor Power supply: <Number Bad> bad, <Number Missing> absent.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of faulty or missing power supplies is greater than or equal to the policy set by the system-monitor command.
Recommended Action: Replace the faulty or missing power supplies.
Message: Switch status change contributing factor Power supply: <Number Bad> bad.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of faulty power supplies is greater than or equal to the policy set by the system-monitor command.
Recommended Action: Replace the faulty power supplies.
Message: Switch status change contributing factor Power supply: <Number Missing> absent.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of missing power supplies is greater than or equal to the policy set by the system-monitor command.
Recommended Action: Replace the missing power supplies.
Message: Switch status change contributing factor: Power supplies are not redundant.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the power supplies are not in the correct slots for redundancy.
Recommended Action: Rearrange the power supplies so that one is in an odd slot and another in an even slot to make them redundant.
Message: Switch status change contributing factor <string>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of faulty temperature sensors is greater than or equal to the policy set by the system-monitor command. A temperature sensor is faulty when the sensor value is not in the acceptable range.
Recommended Action: Replace the field-replaceable unit (FRU) with the faulty temperature sensor.
Message: Switch status change contributing factor Fan: <Number Bad> bad.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of faulty fans is greater than or equal to the policy set by the system-monitor command. A fan is faulty when sensor value is not in the acceptable range.
Recommended Action: Replace the faulty or deteriorating fans.
Message: Switch status change contributing factor Cid-Card: <Number Bad> bad.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of faulty Chassis ID (CID) cards is greater than or equal to the policy set by the system-monitor command.
Recommended Action: Replace the faulty CID card.
Message: Switch status change contributing factor non-redundant MM : M<CP Number> <MM Status>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of faulty management modules is greater than or equal to the policy set by the system-monitor command. The management modules are non-redundant.
Recommended Action: Execute the show firmware command to verify if both the management modules have compatible firmware levels. Execute the firmware download command to install the same level of firmware to both management modules. Replace any faulty management modules.
If you reset the micro-switch (the latch on the management module) on the active management module before the heartbeat was up on a power cycle, and the management modules came up non-redundant, reload the management modules again to clear the problem.
Message: Switch status change contributing factor LC: <Number Bad> LC failures (<LC Numbers>).
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of line card (LC) failures is greater than or equal to the policy set by the system-monitor command.
Recommended Action: Replace the faulty LC.
Message: Switch status change contributing factor SFM: <Number Bad> SFM failures (<Switch State>).
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the number of switch fabric module (SFM) failures is greater than or equal to the policy set by the system-monitor command.
Recommended Action: Replace the faulty SFM.
Message: Switch status change contributing factor Flash: usage out of range.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the flash usage is out of range. The policy was set using the system-monitor command.
Recommended Action: Execute the clear support command to clear the kernel flash.
Message: Switch status change contributing factor Switch offline.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the switch is not in a healthy state. This occurred because the switch is offline.
Recommended Action: Execute the chassis enable command to bring the switch online.
Message: <FRU label> state has changed to <FRU state>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the state of the specified field-replaceable unit (FRU) has changed to "absent".
Recommended Action: Verify if the event was planned. If the event was planned, no action is required. If the event was not planned, check with your system administrator on the hardware state change.
Message: <FRU label> state has changed to <FRU state>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the state of the specified field-replaceable unit (FRU) has changed to "inserted". This means that an FRU is inserted but not powered on.
Recommended Action: Verify if the event was planned. If the event was planned, no action is required. If the event was not planned, check with your system administrator on the hardware state change.
Message: <FRU label> state has changed to <FRU state>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the state of the specified field-replaceable unit (FRU) has changed to "on".
Recommended Action: Verify if the event was planned. If the event was planned, no action is required. If the event was not planned, check with your system administrator on the hardware state change.
Message: <FRU label> state has changed to <FRU state>.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the state of the specified field-replaceable unit (FRU) has changed to "off".
Recommended Action: Verify if the event was planned. If the event was planned, no action is required. If the event was not planned, check with your system administrator on the hardware state change.
Message: <FRU label> state has changed to <FRU state>.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that the state of the specified field-replaceable unit (FRU) has changed to "faulty".
Recommended Action:Replace the FRU.
Message: Mail overflow - Alerts being discarded.
Message Type: LOG
Severity: WARNING
Probable Cause: Indicates that a mail alert overflow condition has occurred.
Recommended Action: Resolve or disable the mail alert using the system-monitor-mail fru command.
Message: Mail overflow cleared - <Mails discarded> alerts discarded.
Message Type: LOG
Severity: INFO
Probable Cause: Indicates that the mail overflow condition has cleared
Recommended Action: No action is required.
Message: <Area string> threshold exceeded: Port <Port number> disabled.
Message Type: LOG
Severity: INFO
Protocol errors indicates cyclic redundancy check (CRC) sum disparity. Occasionally, these errors occur due to software glitches. Persistent errors occur due to hardware problems.
Recommended Action: Check for concurrent loss of synchronization errors. Check the SFP transceiver and the cable and enable the port using the no shutdown command.
Message: CPU 10G <CPU 10G port name> port link down detected.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates CPU 10G link is down
Recommended Action: No action is required.
Message: CPU 10G <CPU 10G port name> port link recovery is started.
Message Type: LOG
Severity: ERROR
Probable Cause: Indicates CPU 10G link recovery is triggered.
Recommended Action: No action is required.