•
All valid configurations specified for MLPPP interfaces with inet address families are
also valid for MLPPP interfaces with MPLS address families. For example, EXP classifier
as a global classifier is supported for ingress classification and EXP rewrite rule is
supported for egress logical interfaces.
•
PPP encapsulation is supported on ACX1000, ACX2000, ACX2100, and ACX4000
routers.
•
A maximum of 1000 logical interfaces can be supported on an ACX router .
•
A maximum of 280 PPP or MLPPP logical interfaces can support drop-profiles on a
system. On each MIC, a maximum of 140 PPP or MLPPP interfaces are supported.
Limitations for CoS on MLPPP Interfaces
The following restrictions apply for configuring CoS on MLPPP interfaces on ACX Series
routers:
•
Percentage-based configuration for scheduling and shaping parameters is not
supported; only absolute rate configuration is supported. As a result, dynamic, swift
redjustment of shaping and scheduling settings does not happen with the addition or
deletion of T1/E1 links.
•
Buffer size is calculated in terms of a single T1 or E1 link speed. Therefore, a temporal
value, in microseconds, is used to compute the buffer size for a higher value of the
buffer size. For the temporal setting, the queuing algorithm starts dropping packets
when it queues more than a computed number of bytes. This maximum is computed
by multiplying the transmission rate of the queue by the configured temporal value.
The default queue size and percentage-based queue size are not based on the current
bandwidth.
•
If you configure a scheduler map without a fragmentation map, any scheduler-map
configuration including the default settings are applied the same behavior as the exact
transmission rate functionality. Priorities of traffic are not honored and no excess rates
are provisioned. The forwarding class with no rate configuration receives the minimum
fixed rate allocated to it, which is 32 Kbps.
•
Support for oversubscription and priority is not available, which might cause inefficient
bandwidth utilization. For example, consider a default scheduler map, with the
best-effort queue configured with a rate that is equal to 16*T1*(.95) transmit-rate
exact.
•
The network-control queue is configured with a rate that is equal to 16*T1*(0.05)
transmit rate exact. In such a scenario, the following behavior is observed for MLPPP
bundle with a single T1 link:
Traffic that arrives as only best-effort type of traffic is provided with complete
bandwidth capacity if no traffic is distributed to any other queue. Traffic that arrives
on the only network-control queue is limited to a bandwidth of 1.2288 Mbps, even if
no traffic is present on any other queue. When traffic arrives on both the best-effort
and network-control queues, an equal division of traffic is done on both the queues
because both the queues are within their minimum guarantee rate. Queues other than
Best-Effort and Network-Control receive 32 Kbps of exact transmit bandwidth.
Copyright © 2017, Juniper Networks, Inc.880
ACX Series Universal Access Router Configuration Guide
To Next Page
Loading...
Need help?
General
