NETGEAR ProSafe GSM7224P User Manual page 678

Prosafe managed switch command line interface (cli) 9.0.2
Hide thumbs Also See for ProSafe GSM7224P:
Table of Contents

Advertisement

Table 32. 802.1Q Log Messages
Component
Message
802.1Q
dot1qIssueCmd: Unable to send message
%d to dot1qMsgQueue for vlan %d - %d
msgs in queue
802.1Q
dot1qVlanCreateProcess: Attempt to
create a vlan with an invalid vlan id %d ;
VLAN %d not in range,
802.1Q
dot1qMapIntfIsConfigurable: Error
accessing DOT1Q config data for
interface %d in
dot1qMapIntfIsConfigurable.
802.1Q
dot1qVlanDeleteProcess: Deleting the
default VLAN
802.1Q
dot1qVlanMemberSetModify,
dot1qVlanTaggedMemberSetModify:
Dynamic entry %d can only be modified
after it is converted to static
Table 33. 802.1S Log Messages
Component
Message
802.1S
dot1sIssueCmd: Dot1s Msg Queue is
full!!!!Event: %u, on interface: %u, for
instance: %u
802.1S
dot1sStateMachineRxBpdu(): Rcvd BPDU
Discarded
802.1S
dot1sBpduTransmit(): could not get a buffer Out of system buffers
Table 34. Port Mac Locking Log Message
Component
Message
Port Mac
pmlMapIntfIsConfigurable: Error accessing
Locking
PML config data for interface %d in
pmlMapIntfIsConfigurable.
ProSafe Managed Switch
Cause
dot1qMsgQueue is full.
This accommodates for reserved vlan ids.
i.e. 4094 - x
A default configuration does not exist for
this interface. Typically a case when a new
interface is created and has no
pre-configuration.
Typically encountered during clear Vlan
and clear config
If this vlan is a learnt via GVRP then we
cannot modify it's member set via
management.
Cause
The message Queue is full.
The current conditions, like port is not
enabled or we are currently not finished
processing another BPDU on the same
interface, does not allow us to process this
BPDU
Cause
A default configuration does not exist for
this interface. Typically a case when a new
interface is created and has no
pre-configuration.
Log Messages
678

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents