Home > Switches > Monitoring and Reporting > MS Event Log Entries and Definitions

MS Event Log Entries and Definitions

If an MS switch is in use on a given network, the event log can be a handy tool to monitor various switching events.

The event log reports the following switch-specific event types:

  • Cable test
  • OSPF
  • Port bounce
  • Port Status Change
  • Port STP Change
  • Power supply inserted/removed
  • SFP Module inserted/removed
  • Sticky MAC whitelist limit reached
  • STP BPDU guard activated
  • STP BPDU sender conflict
  • STP loop guard activated
  • STP root guard activated
  • Temperature Alert

Cable test

Indicates that the cable test live tool was run on the specified port.

Screen Shot 2018-05-07 at 10.48.49 AM.png

OSPF

OSPF event logs include information on OSPF neighborship states, where the possible states are:

  • Init
    • Initial stage of the OSPF neighborship establishment process. The switch received an OSPF hello from its neighbor but the receiving switch's "router ID" was not included in the hello packet.
  • Up
    • Final stage of a successful OSPF neighborship establishment. At this stage, the OSPF neighbors are fully adjacent and successfully share routes.
  • Down
    • Seen when the neighborship is torn down.

Screen Shot 2018-05-07 at 11.05.06 AM.png

Port bounce

This message is logged when the Cycle port live tool is run to bounce a port.

Screen Shot 2018-05-07 at 12.31.28 PM.png

Port Status Change

Port status changes reflect the physical level of the port. The event log entry will display the new speed of the port vs the old speed or state. A down port reflects there is no link established with the client. 

Screen Shot 2018-05-07 at 11.13.44 AM.png

Port STP Change

Port STP changes reflect the STP state of the port. If the MS switch is configured to use STP, an entry will appear in the event log whenever a port’s STP status changes. The event log entry will display the old state and the new state, where the possible states are:

  • Root​​​​​​
    • A “Root” port indicates a “Forwarding” STP state and indicates that the port has the shortest path towards the STP root switch.
  • Designated
    • A “Designated” port indicates a “Forwarding” STP state.
  • Disabled
    • A “Disabled” port means that the port is no longer active. 
  • Alternate and Backup
    • An "Alternate" or “Backup” port indicates a “Blocking” STP state.

Screen Shot 2018-05-07 at 11.32.24 AM.png

Power supply inserted/removed

Power supply insertion/removal messages are logged when a switch detects the presence or loss of a power supply. This event log is specific to models with an external power supply. These messages may also be triggered when the switch reboots and re-discovers the power supplies.

The following events of this type may occur:

  • Power supply inserted
    • The serial number of the power supply unit.
    • The slot the power supply unit was inserted/detected in the switch.
  • Power supply removed
    • The serial number of the power supply unit.
    • The slot the power supply unit was removed from.

Screen Shot 2018-05-07 at 11.29.12 AM.png

SFP Module Inserted/Removed

SFP module entries are the result in the addition or removal of an SFP Module to the MS switch. The "SFP module inserted" event can also be triggered when the switch reboots and re-discovers the SFP modules.

The following events of this type may occur:

  • SFP Module Inserted
    The “SFP Module Inserted” event will include:
    • The Serial number of the SFP module.
    • The port the SFP module was inserted into on the switch.
    • The manufacturer of the SFP module.
    • The connector type of the SFP module.
    • The Speed supported by the SFP module.
    • The part number of the SFP module.
  • SFP Module Removed
    ​The “SFP Module Removed" event log will include:
    • The switch port the module was removed from.

7d85551e-bd92-4ddd-ad3e-1bce00a0c769

 

Sticky MAC whitelist limit reached

Logged when the number of MAC entries learnt on the specified port exceeds the configured "Sticky MAC whitelist size" limit. When this limit is exceeded, all subsequent devices will be denied access to this port.  

Screen Shot 2018-05-07 at 11.40.28 AM.png

 

STP BPDU guard activated

Logged when BPDU guard is enabled on a port and the switch receives an STP BPDU on that port. The port will also start discarding packets received on the port. In addition, the log will also specify the MAC address of the device from which a BPDU was received.

Screen Shot 2018-05-07 at 11.48.19 AM.png

STP BPDU sender conflict

As part of STP and LAN anomaly detection introduced in MS 10 firmware, STP BPDU sender conflict messages are logged when the following conditions are met for a switch port:

  • The port is in RSTP (not legacy STP) mode
  • The port is full duplex
  • Multiple BPDUs are received within a small window that identify different sending ports
  • The port link state has not changed between receiving such BPDUs

Screen Shot 2018-05-07 at 11.50.33 AM.png

STP loop guard activated

Loop guard, introduced in MS 10 firmware, serves as an added layer of protection against L2 forwarding loops. If BPDU's are not received on a loop guard enabled non-designated port, the port is blocked. Useful to avoid erroneous STP port transitions to forwarding due to missed BPDU's.

STP root guard activated

Logged when a port configured for root guard receives a BPDU frame with a bridge priority lower than that of the current root switch. The port will also start discading packets received on the port. In addition, the log will also specify the MAC address of the device from which the superior BPDU was received.

Screen Shot 2018-05-07 at 12.26.33 PM.png
 

Temperature Alert

Logged when critical temperature thresholds are reached. 

Screen Shot 2018-05-07 at 12.35.48 PM.png

 

 

Last modified

Tags

Classifications

This page has no classifications.

Explore the Product

Click to Learn More

Article ID

ID: 1170

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community