Filter
Top Products
Configuring Logical Ports 5-17
Frame Relay Status and Configuration
You must conÞgure a different DLCI for every logical port on a physical port
because logical ports and DLCIs have a one-to-one relationship. Also, make sure
that each interface (IP, IPX or LLC2) or frame relay bridge port has a different
DLCI. Do not assign a DLCI number that is conÞgured as a frame relay backup
DLCI.
Priority
This Þeld allows you to set a priority for trafÞc within the node. The higher the
number, the higher the priority relative to other intra-nodal trafÞc. These
priorities have no effect on trafÞc exiting a node. When conÞguring priorities, be
careful to consider the types of trafÞc being routed on other connections in the
node.
Bandwidth Allocation Group
Use this Þeld to assign the logical port to one of 16 Bandwidth Allocation Groups
(BAG). BAGs regulate bandwidth usage by outgoing trafÞc on the physical link
and can ensure that response time-sensitive trafÞc gets access to the available
frame relay bandwidth. Up to 16 groups can be deÞned and conÞgured through
console management (refer to your FRX or SmartSwitch 1800 hardware
documentation for more information).
Max Packet Size
Use this Þeld to specify the maximum data packet size that will be allowed to pass
through this logical port. The packet size included in a call setup packet will be
used, as long as it is smaller than the maximum speciÞed here. Valid values are
128, 256, 512, 1024, 2048 and 4096.
If X.25 will be run over this port, do not conÞgure a size greater than 2048. If 4096
is speciÞed, additional X.25 and frame headers can make the frame too large. The
value of 2048 will not cause a problem, since larger frames will simply be split,
then reassembled at the destination.
Default Packet Size
The value entered in this Þeld will be assigned to an incoming call setup packet if
the packet does not include a packet size. Valid values are 16, 32, 64, 128, 256, 512,
1024, 2048 and 4096.
If X.25 will be run over this port, do not conÞgure a size greater than 2048. If 4096
is speciÞed, additional X.25 and frame headers can make the frame too large. The
value of 2048 will not cause a problem, since larger frames will simply be split,
then reassembled at the destination.
NOTE
Bandwidth allocation groups cannot currently be conÞgured via SPMA; for more
information on conÞguring these groups, see your FRX or SmartSwitch 1800 hardware
documentation.