Multiple Spanning Tree Protocol Events

https://www.arubanetworks.com/techdocs/AOS-CX/10.07/HTML/5200-8214/Content/fir-int.htm

https://www.arubanetworks.com/techdocs/AOS-CX/10.07/PDF/5200-8214.pdf

Multiple Spanning Tree Protocol Events

Base Rule

Spanning Tree Info Msg

Information

Event ID

<vmid>

Number

Event ID 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019

Severity

<severity>

Text/String

For All: Information
For 2003, 2004, 2005, 2007: Warning

Message

<subject>

Text/String

Event ID 2001:
This command enables the MSTP (Multiple Spanning-tree Protocol) feature in the device.

<subject>

Text/String

Event ID 2002:
This command disables the MSTP (Multiple Spanning-tree Protocol) feature in the device.

<subject>
<object>
<objectname>

Text/String/Number

Event ID 2003:
This log event informs the user that the MSTP config parameter is bad

<subject>
<object>
<objectname>

Text/String/Number

Event ID 2004:
This log event informs the user that the Switch received a BPDU with a bad config

<subject>
<object>

Text/String

Event ID 2005:
This log event informs the user that the MSTP reconfig parameter is bad

<subject>
<protname>
<smac>
<dmac>

Text/String

Event ID 2006:
This log event informs the user that the MSTP root has changed

<subject>
<dport>

Text/String/Number

Event ID 2007:
This log event informs the user that BPDU was received on protected port

<subject>
<protname>
<objecttype>
<dport>
<dmac>

Text/String/Number

Event ID 2008:
This log event informs the user that the Rx queue is starved in the paticular port

<subject>
<protname>
<dport>

Text/String/Number

Event ID 2009:
This log event informs the user that the port is in inconsistent state

<subject>
<protname>
<dport>

Text/String/Number

Event ID 2010:
This log event informs the user that the MSTP is out of inconsistent state

<subject>
<protname>
<dport>
<smac>

Text/String/Number

Event ID 2011:
This log event informs the user that the MSTP topology change is received

<subject>
<protname>
<dport>
<status>

Text/String/Number

Event ID 2012:
This log event informs the user that the MSTP topology change is generated

<subject>
<dport>

Text/String/Number

Event ID 2013:
This log event informs the user that a BPDU was received on admin edge port

<subject>
<dport>

Text/String/Number

Event ID 2014:
This log event informs the user that the CIST port is blocked

<subject>
<dport>

Text/String/Number

Event ID 2015:
This log event informs the user that the CIST port is unblocked

<subject>
<dport>

Text/String/Number

Event ID 2016:
This log event informs the user that the MSTI port is blocked

<subject>
<dport>

Text/String/Number

Event ID 2017:
This log event informs the user that the MSTI port is unblocked

<subject>
<protname>
<dport>

Text/String/Number

Event ID 2018:
This log event informs the user that the root port is changed

<subject>
<action>

Text/String

Event ID 2019:
This log event informs the user that the spanning tree mode is changed.