EasyManuals Logo

Foundry Networks FESX User Manual

Foundry Networks FESX
820 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #744 background imageLoading...
Page #744 background image
Foundry Configuration Guide for the FESX, FSX, and FWSX
A - 18 © Foundry Networks, Inc. December 2005
Informational user <username> added | deleted | modified
from console | telnet | ssh | web | snmp
A user created, modified, or deleted a local
user account via the Web, SNMP, console,
SSH, or Telnet session.
Informational vlan <vlan id> added | deleted | modified
from console | telnet | ssh | web | snmp
session
A user created, modified, or deleted a VLAN
via the Web, SNMP, console, SSH, or Telnet
session.
Informational Warm start The system software (flash code) has been
reloaded.
Informational vlan <vlan-id> Bridge is RootBridge <mac-
address> (MgmtPriChg)
802.1W changed the current bridge to be the
root bridge of the given topology due to
administrative change in bridge priority.
Informational vlan <vlan-id> Bridge is RootBridge <mac-
address> (MsgAgeExpiry)
The message age expired on the Root port
so 802.1W changed the current bridge to be
the root bridge of the topology.
Informational vlan <vlan-id> interface <portnum> Bridge
TC Event (DOT1wTransition)
802.1W recognized a topology change event
in the bridge. The topology change event is
the forwarding action that started on a non-
edge Designated port or Root port.
Informational vlan <vlan-id> interface <portnum> STP
state -> <state> (DOT1wTransition)
802.1W changed the state of a port to a new
state: forwarding, learning, blocking. If the
port changes to blocking, the bridge port is in
discarding state.
Informational vlan <vlan-id> New RootBridge <mac-
address> RootPort <portnum> (BpduRcvd)
802.1W selected a new root bridge as a
result of the BPDUs received on a bridge
port.
Informational vlan <vlan-id> New RootPort <portnum>
(RootSelection)
802.1W changed the port’s role to Root port,
using the root selection computation.
Notification ACL exceed max DMA L4 cam resource,
using flow based ACL instead
The port does not have enough Layer 4 CAM
entries for the ACL.
To correct this condition, allocate more Layer
4 CAM entries. To allocate more Layer 4
CAM entries, enter the following command at
the CLI configuration level for the interface:
ip access-group max-l4-cam <num>
Notification ACL insufficient L4 cam resource, using flow
based ACL instead
The port does not have a large enough CAM
partition for the ACLs.
Notification ACL insufficient L4 session resource, using
flow based ACL instead
The device does not have enough Layer 4
session entries.
To correct this condition, allocate more
memory for sessions. To allocate more
memory, enter the following command at the
global CONFIG level of the CLI interface:
system-max session-limit <num>
Table A.3: Foundry Syslog Messages (Continued)
Message Level Message Explanation

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Foundry Networks FESX and is the answer not in the manual?

Foundry Networks FESX Specifications

General IconGeneral
BrandFoundry Networks
ModelFESX
CategorySwitch
LanguageEnglish

Related product manuals