User Guide

MIB Navigator
3-26 Local Management User’s Guide
b. DLCMI Protocol Error: This is a service affecting condition that
can/will occur due to any error that has happened between/
before the link goes down due to excessive polling errors. If 3
out of 4 errors have not occurred yet, but the circuit was
prevented from going active by any one of the FR errors listed
in Section, then this will be the condition listed for the inactive
reason.
c. Startup/Initialization: This basically means there have been no
errors, we are polling correctly with the switch, but for some
reason the switch reports to us inactive for that DLCI. Possible
reasons for this are:
- The FR DTE bridge/router <-> FR DCE switch on the far
side of the WAN cloud is not connected, or has polling error
problems. Refer to the remote mibnav/LM screen for CSX
products, the Telecommunications/Remote Access Service
provider, or other means (remote device console support/
protocol analyzer) at the far end to troubleshoot the remote
device.
- It may take up to 60 seconds (by default) [t391 (10 by
default) seconds x n391 (6 by default) cycles for a circuit to
go active, even in a well behaved properly communicating
network. This is due to STATUS polling convergence of
both FR DCE switches, with both FR DTE bridge/routers.
imux:
Syntax: imux <options>
Description: The imux command lets you balance your LAN traffic between two T1
WAN ports and is used with Point to Point Protocol (PPP). When you
select Inverse Multiplexing via QuickSET, bridging, IP routing, and IPX
routing functions are all disabled. The WAN device at the other end of
the WAN link(s) must be a Cabletron Systems device, capable of
receiving the balanced WAN traffic. The imux command with no options
displays the status information.