Skip to main content
Skip table of contents

Virtual Switching Framework (VSF) Events

Vendor Documentation

Classification

Rule Name

Rule Type

Common Event

Classification

Virtual Switching Framework (VSF) Events

Base Rule

General Information Log Message

Information

Mapping with LogRhythm Schema

Device Key in Log Message

LogRhythm Schema

Data Type

Schema Description

Event ID

<vmid>

Number

Event ID 9901, 9902, 9903, 9905, 9906, 9907, 9908, 9910, 9911, 9912, 9913, 9914, 9915, 9916, 9917, 9919, 9920, 9921, 9922, 9923, 9924, 9925, 9926, 9927, 9928, 9929, 9930, 9931, 9932, 9933, 9934, 9935, 9936, 9937, 9938, 9939, 9940, 9941, 9942, 9943, 9944, 9945, 9946, 9947, 9948, 9949

Severity

<severity>

Text/String

For All: Information
For 9906, 9907, 9911, 9913, 9917-9922, 9925, 9926, 9933, 9934, 9935, 9938-9944, 9947, 9948: Warning

Message

<subject>
<object>

Text/String

Event ID 9901:
log event for member boot complete

<subject>
<object>

Text/String

Event ID 9902:
log event for standby boot complete

<subject>
<object>

Text/String

Event ID 9903:
log event for Master boot complete

<subject>
<object>

Text/String

Event ID 9905:
Event log indicates that member is reseting

<subject>
<object>

Text/String

Event ID 9906:
Event log for Failed processing Hello packet because of member number conflict

<subject>

Text/String

Event ID 9907:
Event log for indicates that we got a packet with a diff proto ver

<subject>
<objecttype>
<object>

Text/String

Event ID 9908:
Event log indicates the current topology

<subject>
<object>

Text/String

Event ID 9910:
Event log indicates the member has been removed due to user request

<subject>
<objecttype>
<dmac>

Text/String

Event ID 9911:
Event log indicates that we would exceed the MAX switches if we add this new switch

<subject>
<object>

Text/String

Event ID 9912:
log event for stack state active

<subject>
<reason>
<object>

Text/String

Event ID 9913:
Event log for lost member

<subject>
<status>
<dmac>

Text/String

Event ID 9914:
Event log for status of a reboot request

<subject>
<reason>
<object>

Text/String

Event ID 9915:
log event for the switch won as master

<subject>
<reason>
<object>

Text/String

Event ID 9916:
log event for the switch won as standby

<subject>
<dmac>
<object>

Text/String

Event ID 9917:
log event for the member was not allowed to join due to a mismatched product-id

<subject>
<dmac>
<objecttype>
<smac>
<sport>

Text/String/Number

Event ID 9919:
log event for switch running on a different platform and trying to join the stack

<subject>
<object>

Text/String

Event ID 9920:
log event for heart beat lost

<subject>
<object>

Text/String

Event ID 9921:
log event when os_version_mismatch happened on standby and member

<subject>
<object>

Text/String

Event ID 9922:
log event when member attempt to connect to a different stack

<subject>

Text/String

Event ID 9923:
log event when vsf link is up

<subject>

Text/String

Event ID 9924:
log event when vsf link is down

<subject>
<dmac>
<smac>

Text/String

Event ID 9925:
log event when different MAC address on the same link

<subject>

Text/String

Event ID 9926:
log event when there is a 2 member loop in topology

<subject>
<object>

Text/String

Event ID 9927:
log event for active fragment

<subject>
<object>

Text/String

Event ID 9928:
log event for Inactive fragment

<subject>

Text/String

Event ID 9929:
log event for active stack detection timeout

<subject>
<object>

Text/String

Event ID 9930:
log event for standby configuration

<subject>

Text/String

Event ID 9931:
log event for standby unconfiguration

<subject>
<dmac>
<object>

Text/String

Event ID 9932:
log event when Mater SKU device joins the stack

<subject>
<dport>

Text/String/Number

Event ID 9933:
log event for peer time out as it did not receive any packet

<subject>
<dport>

Text/String/Number

Event ID 9934:
Peer timeout on interface <port_id>

<subject>
<dport>

Text/String/Number

Event ID 9935:
log event when peer switch is in different VSF handshake version

<subject>
<dport>

Text/String/Number

Event ID 9936:
log event when interface added to a particular link

<subject>
<dport>

Text/String/Number

Event ID 9937:
log event when interface removed from a particular link

<subject>
<dmac>
<dport>

Text/String/Number

Event ID 9938:
log event when the switch is not able to autojoin as it is connected with a non default VSF interface

<subject>
<dmac>
<dport>
<object>

Text/String/Number

Event ID 9939:
log event when there is an inconsistency detected between masters provisioned VSF link configuration and the interface on which switch is attempting to autojoin

<subject>
<dmac>

Text/String

Event ID 9940:
log event when peer switch is not autojoin eligible

<subject>
<dmac>

Text/String

Event ID 9941:
log event when there is more than one interface physically connected to same switch VSF link for autojoin

<subject>
<dmac>

Text/String

Event ID 9942:
log even when switch is not allowed to autojoin because of insufficient resources

<subject>
<dmac>
<dport>

Text/String/Number

Event ID 9943:
log event when two different switches are attempting to autojoin by connecting to the same VSF link on the peer

<subject>

Text/String

Event ID 9944:
log event when VSF force autojoin fails as VSF configurations exists

<subject>

Text/String

Event ID 9945:
log event when VSF force autojoin is enabled

<subject>

Text/String

Event ID 9946:
log event when VSF force autojoin is disabled

<subject>
<dmac>
<smac>

Text/String

Event ID 9947:
log event when member connected to an unsupported interface

<subject>

Text/String

Event ID 9948:
log event when interface is in inconsistent link configuration error

<subject>

Text/String

Event ID 9949:
log event when existing secondary changes to new specified secondary member

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.