
Configuring DLSw Services
C-2 114063 Rev. A
For information on viewing events and messages using Site Manager or a
compatible third-party network management software, see Managing Routers and
BNX Platforms. For a complete description of all warning, fault, trace, and
informational messages, refer to Event Messages for Routers and BNX Platforms.
For information on viewing events using the Technician Interface, see Using
Technician Interface Software.
Enabling Extended Logging
Subsystems such as LLC and SDLC allow you to enable extended logging
through the Management Information Base (MIB). Extended logging provides
additional messages and information that can help you identify and troubleshoot a
DLSw network problem. However, using extended logging causes the router to
use more log space and memory, and affects CPU performance.
You enable extended logging using the Bay Networks Technician Interface.
Table C-1 lists each subsystem, the Technician Interface command that enables
extended logging for that subsystem, and type(s) of messages or events that could
appear in the log.
With extended logging enabled, log messages describing the frame flows and state
transitions appear during the critical phases of each connection being established.
*. Enabled by default.
†. DLS, LLC, and SDLC extended logging set by Technician Interface only.
Table C-1. Extended Logging Commands for Subsystems
Subsystem How to Enable Items Logged
DLS s wfDls.14.0 0xffffffff;commit*
s wfDls.15.0 0x3;commit†
DLSw protocol and data
link control events
leading to connection
state changes
LLC s wfLlcInterfaceEntry.2.cct 0cfff1;commit LLC inbound and
outbound packets
SDLC s wfSdlcPortAdminEntry.36.cct 0x1;commit SDLC messages
Comentários a estes Manuais