
Configuring Bridging
13-15
Port Priority
will become the first octet of the
Port ID
field in Spanning Tree Protocol messages. The
lower the number, the higher the priority that the interface will be given among other
interfaces in the spanning tree.
Path Cost
is the "cost" of transmitting a frame through the port onto the LAN. This cost, deter-
mined by the speed of the LAN/port (the higher the speed, the lower the cost), will be
added together with all other path costs on a specific link between source and desti-
nation devices. The total will then be compared to other total path costs to determine
the least "expensive" end-to-end path.
Priority
prioritizes this interface for intra-nodal traffic; the higher the number, the higher the
priority. (This priority has no effect on traffic exiting a node.)
A priority is also configured in Node Defaults, as well as for each logical port, SNA
PU, LLC2 host, IP interface, IPX interface, SVC subscriber, and PVC connection. The
device processor in the node uses these priorities to help determine the order in which
it will process protocols.
This priority has no connection to
Bridge Priority
or
Port Priority
.
When configuring priorities, be careful to consider the types of
traffic being routed on other connections in the node.
LAN Card
identifies the LAN card, as defined in PROTOCOL.INI (
[A], [C], [B]
from the Main
Menu). (The single LAN card in an FRM is always card
0
, and the LAN interface in
an FRX4000 is seen as
0
.)
LAN ID
identifies the ring number used by a frame relay-compliant source-route bridge at the
other end of this PVC. The value is normally assigned by a system administrator.
LAN IDs can also be configured in LLC2/Bridge Node Defaults
(described in Chapter 8). Each LAN ID must be unique within
the network on which this node will operate.
RLP/Port
identifies the LP and physical port containing the interface.
Make sure the physical frame relay port is not reserved for
backup DLCIs (as determined by the
For Backup Use Only
parameter in the port record—see Chapter 6).
Summary of Contents for MMAC-Plus 9F116-01
Page 2: ......
Page 15: ...Section I Introduction ...
Page 16: ......
Page 37: ...Section II Configuration ...
Page 38: ......
Page 46: ......
Page 76: ...4 18 FRX FRM 3 3 User Guide Rev 04 ...
Page 174: ......
Page 196: ......
Page 271: ...Section III Operation ...
Page 272: ......
Page 340: ...17 46 FRX FRM 3 3 User Guide Rev 04 ...
Page 370: ......
Page 371: ...Section IV Appendices ...
Page 372: ......
Page 383: ...Appendix D Cause and Diagnostic Codes ...
Page 394: ......
Page 398: ......
Page 402: ...G 4 FRX FRM 3 3 User Guide Rev 04 ...