Changing Vc Subranges; Static Atm Interfaces Within Vc Subranges - Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual

JunosE 11.2.x Link Layer Configuration Guide
630
base profile, can include ATM 1483 attributes, nested profile assignments, and individual
characteristics for dynamic upper-interface encapsulation types.
For configuration instructions and examples, see "Configuring Overriding Profile
Assignments" on page 641.
NOTE: See JunosE Release Notes, Appendix A, System Maximums for information about
the maximum number of overriding profile assignments currently supported per router.

Changing VC Subranges

You can add, remove, modify, merge, disable, and enable VC subranges within an existing
bulk-configured VC range. Previously, changes to VC subranges were possible only if you
removed the VC range and then configured it again with different subrange values. The
ability to make changes to VC subranges without first having to remove the entire VC
range avoids potentially disrupting all subscribers on existing dynamic ATM 1483
subinterfaces associated with the deleted VC range.
For configuration instructions and examples, see "Changing VC Subranges" on page 646.

Static ATM Interfaces Within VC Subranges

You can configure a static ATM interface with an ATM PVC whose VPI and VCI addresses
fall within an existing bulk-configured VC subrange. Conversely, you can also create a
bulk-configured VC subrange that includes the VPI and VCI addresses belonging to an
existing ATM PVC on a static ATM interface. Previously, configurations that caused
VPI/VCI address conflicts between a static ATM interface and a bulk-configured VC
subrange were prohibited on the router.
In certain ATM network configurations, you might need to transparently forward traffic
from selected circuits with unrelated addresses to another location in the network. The
ability to create a static ATM interface on a circuit within a bulk-configured VPI/VCI
address range is particularly useful when you use ATM layer 2 services over MPLS with
Martini encapsulation to forward the traffic from the selected circuits. You must create
the interface stack for ATM layer 2 statically and define the configuration parameters
individually on a per-interface basis.
The following rules apply when you configure either a static ATM interface within an
existing bulk-configured VC subrange, or a subrange that includes an existing static ATM
interface:
All of the following ATM configurations are supported on the static ATM interface:
ATM layer 2 services over MPLS including local cross-connects, point-to-point
connections, and nonbroadcast multiaccess (NBMA) connections.
Static ATM interfaces and circuits defined within a bulk-configured VC subrange are
stored in NVS and preserved after a reboot.
The base profile associated with the VC subrange does not apply to any statically
defined ATM interfaces that fall within the subrange.
Copyright © 2010, Juniper Networks, Inc.