Configuring ATM 1483 Dynamic Subinterfaces

E-series routers support configuration of dynamic ATM 1483 subinterfaces over static ATM AAL5 interfaces over ATM. The dynamic ATM 1483 subinterface can perform autodetection and dynamic creation of the following upper-layer encapsulation types:

• Bridged Ethernet
• IP
• PPP
• PPPoE

Figure 50 shows the dynamic upper-interface columns supported by dynamic ATM 1483 subinterfaces, and indicates which layers in the columns are static and dynamic.

Figure 50: Dynamic Interface Columns over Dynamic ATM 1483 Subinterfaces

About Configuring Dynamic ATM 1483 Subinterfaces

This section introduces important concepts that you need to understand before you configure dynamic ATM 1483 subinterfaces.

Overview and Benefits

When you use dynamic interfaces over static ATM 1483 subinterfaces, you must configure the ATM interface and each ATM 1483 subinterface, including the ATM PVC and the attributes of the subinterface. Subinterface attributes include profile assignments, autoconfiguration settings, and subscriber configurations.

By contrast, when you use dynamic ATM 1483 subinterfaces over static ATM AAL5 interfaces, you use a process called bulk configuration to configure a range of ATM PVCs that support dynamic interfaces. On receipt of an incoming packet on the virtual circuit, the router dynamically creates the ATM 1483 subinterface. As part of the configuration process, you create an ATM 1483 base profile, which can optionally include nested profile assignments, to define the attributes required to configure the dynamic ATM 1483 subinterface and the dynamic upper-layer encapsulation types built over it.

Bulk configuration provides an efficient and timesaving way to specify a range of ATM PVCs for dynamic ATM 1483 subinterfaces. Because bulk configuration requires significantly less configuration of the router, it results in reduced output when you issue the show configuration command to display the current router configuration.

Dynamic ATM 1483 subinterfaces function identically to static ATM 1483 subinterfaces, except for the manner in which they are created and configured. The creation of dynamic upper-layer encapsulation types is essentially the same regardless of whether they are configured over static ATM 1483 subinterfaces or dynamic ATM 1483 subinterfaces.

ATM 1483 Base Profiles

To configure a dynamic ATM 1483 subinterface over a static ATM AAL5 interface, you must create a base profile. The base profile includes one or more of the following attributes for the ATM 1483 subinterface, listed alphabetically:

• advisory-rx-speed—Sets an advisory receive speed for ATM 1483 subinterfaces that are created with this base profile. For information, see atm atm1483 advisory-rx-speed.
• atm pvc—Applies encapsulation, traffic-shaping, and OAM parameters to the range of ATM PVCs configured on the ATM AAL5 interface for use by the dynamic ATM 1483 subinterface. For information, see atm pvc.
• auto-configure—Specifies the types of upper-interface encapsulations that are accepted or detected by the dynamic ATM 1483 subinterface. For information, see atm atm1483 auto-configure.
• atm class-vc—Specifies the VC class assigned to the bulk-configured VC ranges created on the dynamic ATM 1483 subinterfaces associated with this base profile. For information, see atm class-vc.
• description—Assigns a description to ATM 1483 subinterfaces that are created with this base profile. For information, see atm atm1483 description. You can then set up the router to send this description to AAA by using the atm atm1483 export-subinterface-description command, as described in Sending Interface Descriptions to AAA in Configuring ATM .
• profile—Adds a nested profile assignment, which references another profile that dynamically configures an upper-interface encapsulation type over the ATM 1483 subinterface. For information, see atm atm1483 profile.
• subscriber—Configures a local subscriber for a dynamic upper-interface encapsulation type. For information, see atm atm1483 subscriber.

You can override the base profile assignment for a single ATM PVC that exists within a bulk-configured VC subrange with a profile that includes debugging attributes. This feature is useful for troubleshooting problems with the ATM 1483 dynamic subinterface columns created on the specified PVC. For more information, see Overriding Base Profile Assignments.

Nested Profile Assignments

The configuration for each dynamic upper-interface encapsulation type might differ, depending on the column type built by the router. To manage these differences, you can include one or more nested profile assignments within the ATM 1483 base profile. A nested profile assignment references another profile that configures attributes for a dynamic upper-interface encapsulation type. You can create different profiles for each upper-interface encapsulation type, or you can create a single profile that includes attributes for multiple encapsulation types.

For example, the following commands create a base profile named atm1483BaseProfile with two nested profile assignments. The first nested profile assignment references an IP profile named atm1483ProfileIp, and the second nested profile assignment references a PPP profile named atm1483ProfilePpp.

In this example, atm1483ProfileIp and atm1483ProfilePpp have different IP configurations depending on the dynamic interface column constructed. For an IP over ATM (IPoA) dynamic interface column, the router uses the IP attributes in atm1483ProfileIp. For an IP over PPP over ATM dynamic interface column, the router uses the IP attributes in atm1483ProfilePpp.

The concepts that apply to profiles created for upper-interface encapsulation types configured over static ATM 1483 subinterfaces also apply to profiles created for upper-interface encapsulation configured over dynamic ATM 1483 subinterfaces. For information about creating profiles for upper-interface encapsulation types, see Configuring Dynamic Interfaces.

Additional Profile Characteristics for Upper Interfaces

In addition to ATM 1483 attributes and nested profile assignments, the base profile for a dynamic ATM 1483 subinterface can also include individual characteristics for several upper-interface encapsulation types, provided that no nested profile assignment for the specified encapsulation type is in the base profile. If, on the other hand, a nested profile assignment for this encapsulation type exists in the base profile, the router obtains all characteristics for that encapsulation type from the nested profile and not from the base profile.

For lists of the characteristics for each supported upper-interface encapsulation type, see Profile Characteristics in Configuring Dynamic Interfaces.

Bulk Configuration of VC Ranges

When you create a static ATM 1483 subinterface, you must configure a permanent virtual circuit (PVC), also known as a virtual circuit (VC). The ATM protocol requires one or more VCs over which data traffic is transmitted to higher layers in the protocol stack.

Similarly, dynamic creation of ATM 1483 subinterfaces requires you to configure a range of ATM PVCs on the ATM AAL5 interface and assign a name to this range. Each VC range consists of one or more nonoverlapping VC subranges. A VC subrange is a group of VCs that resides within the virtual path identifier (VPI) and virtual circuit identifier (VCI) ranges you specify.

The process of configuring a VC range for a dynamic ATM 1483 subinterface is referred to as bulk configuration. You create a bulk configuration by issuing the atm bulk-config command. For example, the following commands create an ATM 1483 bulk configuration named myBulkConfig on the specified ATM AAL5 interface.

In this example, the atm bulk-config command configures a VC range made up of two VC subranges. The first subrange, with VPIs 0–3 and VCIs 101–1100, configures 1000 VCs on each of four VPIs, for a total of 4000 VCs. The second subrange, with VPIs 4–7 and VCIs 201–700, configures 500 VCs on each of four VPIs, for a total of 2000 VCs. The entire myBulkConfig VC range configures a combined total of 6000 VCs.

Note: For information about the maximum number of ATM 1483 bulk configurations supported per router, see JUNOSe Release Notes, Appendix A, System Maximums.

After you issue the atm bulk-config command, the router provisions all circuits in the specified VC range at the same time. This provisioning can take several seconds, depending on the number of VCs being created. The router does not dynamically create the ATM 1483 subinterface for the circuit until it receives incoming data traffic on the circuit.

After you create a named VC range, you cannot remove the underlying ATM AAL5 interface until you issue the no atm bulk-config command to remove the VC range from that interface.

Note: For information about the maximum number of VCs (sum of the VPI/VCI addresses within all VC subranges) that you can configure with the atm bulk-config command per line module and per chassis, see JUNOSe Release Notes, Appendix A, System Maximums. Do not use any reserved VCI values when configuring VCs with the atm bulk-config command. For information about reserved VCIs, see Configuring F4 OAM in Configuring ATM .

Bulk Configuration and VC Classes

You can assign a previously configured VC class to a bulk-configured VC range. A VC class is a set of attributes for virtual circuits that can include the service category, encapsulation method, F5 OAM options, and Inverse ARP. Using VC classes to configure VC attributes provides the following benefits:

• VC classes enable you to classify and group VCs based on the OAM and traffic requirements of their associated subscribers.
• When subscriber requirements change, a VC class is easier and less time-consuming to modify than individual PVC attributes.

To assign a VC class to a bulk-configured VC range, you use the atm class-vc command from Profile Configuration mode to associate the VC class to a base profile. Issuing this command applies the set of attributes in the specified VC class to all bulk-configured VC ranges that are dynamically created from this base profile.

For details about configuring and using VC classes, including information about how precedence levels affect how the router determines attributes values for dynamically created circuits, see Configuring ATM VC Classes in Configuring ATM . For information about how to use the atm vc-class command to assign a VC class to a base profile, see atm class-vc.

Note: Using the atm class-vc command inside a nested profile that is referenced in a base profile has no effect on the bulk-configured VC ranges associated with the base profile. The router accepts only those VC class assignments that are configured in a base profile and ignores any VC class assignments made in a nested profile.

Bulk Configuration and CAC

You cannot create a bulk-configured VC range on an ATM interface on which you have configured connection admission control (CAC). Conversely, you cannot configure CAC on an ATM interface on which you have created a bulk-configured VC range.

If you are upgrading to the current JUNOSe software release from a lower-numbered release, configurations that use CAC and bulk configuration on the same ATM interface continue to work. However, we recommend that you disable CAC on these ATM interfaces to ensure continued compatibility with future JUNOSe releases.

For information about how to use the atm cac command to configure CAC, see Setting Optional Parameters in Configuring ATM .

Dynamic Interface Creation

After you configure the ATM 1483 base profile and create the range of VCs on the ATM AAL5 interface, you associate these two components by assigning the base profile to the VC range with the profile atm1483 bulk-config-name command.

As a final step, you must issue the auto-configure atm1483 command. This command configures the ATM AAL5 interface to support autodetection of the ATM 1483 dynamic encapsulation type.

When the router receives an incoming data packet on a circuit, it dynamically creates the ATM 1483 subinterface, using the attributes specified in the base profile. After examining the contents of the data packet, the router dynamically creates the required interface columns above the ATM 1483 subinterface, using the configuration attributes contained in the nested profiles, if specified, or in the base profile itself.

Overriding Base Profile Assignments

You can use the profile atm1483 bulk-config-name pvc command to assign an overriding profile to a single ATM PVC that exists within a bulk-configured VC subrange. The VC subrange that encompasses the PVC must have been previously configured with the atm bulk-config command for use by a dynamic ATM 1483 subinterface. After you assign the overriding profile, the router uses the information in this profile instead of the information in the previously assigned base profile to create any subsequent ATM 1483 dynamic subinterface columns on the specified PVC.

Overriding the base profile assignment for an ATM PVC with a profile that includes debugging attributes enables you to troubleshoot problems with ATM 1483 dynamic subinterface columns created on the specified PVC. The overriding profile, like the original 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.

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.

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.
• If a VC subrange includes a statically defined ATM interface, overriding profile assignments configured for the same VPI/VCI address as a statically defined ATM interface become inactive until the static ATM 1483 subinterface is removed. The overriding profile becomes active again when you remove the static ATM 1483 subinterface. You can display the current operational status (active or inactive) of overriding profile assignments by using the show atm bulk-config command.
• Operations that add, remove, modify, merge, disable, or enable VC subranges within a bulk-configured VC range do not affect any static ATM interfaces defined within the VC subrange.
• You cannot create a static ATM circuit if the VPI/VCI address conflicts with an existing ATM 1483 dynamic subinterface column. Such a configuration would disrupt subscribers already connected to the router via the dynamic subinterface.
• You cannot create a static ATM interface with a VPI/VCI address that falls within a range of circuits reserved for use by the MPLS downstream-on-demand label distribution method.
• You cannot configure CAC on a static ATM interface within an existing bulk-configured VC subrange. Conversely, you cannot create a bulk-configured VC subrange that includes a static ATM interface on which CAC is configured. (For information about how to use the atm cac command to configure CAC, see Setting Optional Parameters in Configuring ATM .)

For configuration information and examples, see Configuring Static ATM Interfaces Within VC Subranges.

Terminating Stale PPPoA Subscribers and Restarting LCP Negotiations

In configurations of dynamic IP over dynamic PPP over a dynamic (bulk-configured) ATM 1483 subinterface, the router sends an LCP terminate request packet to a PPPoA CPE device in response to receipt of an IPv4-over-PPP data packet or an IPv6-over-PPP data packet when the dynamic ATM 1483 subinterface transitions to a dormant state due to an ungraceful subscriber logout. This action terminates stale PPPoA subscribers and causes the CPE to restart LCP negotiations. This behavior is always in effect on the router and does not require CLI or SNMP configuration.

The implementation of this feature for dynamic ATM 1483 subinterfaces is almost identical to the implementation for static ATM 1483 subinterfaces, with the following difference:

• For static ATM 1483 subinterfaces, the restart of LCP negotiations by the CPE causes the router to re-create the dynamic PPP and IP upper-layer interfaces above the static ATM 1483 subinterface.
• For dynamic ATM 1483 subinterfaces, the receipt of a PPP data packet from the CPE causes the router to re-create only the dynamic ATM 1483 subinterface to send the LCP terminate request packet, but not the dynamic PPP and IP upper-layer interfaces above the dynamic ATM 1483 subinterface. The router re-creates the dynamic PPP and IP upper-layer interfaces when the CPE restarts LCP negotiations.

For details about the operation and benefits of this feature, see Terminating Stale PPPoA Subscribers and Restarting LCP Negotiations in Configuring Dynamic Interfaces, which describes the router behavior for static ATM 1483 subinterfaces.

Authenticating Subscribers on Dynamic Bridged Ethernet over Dynamic ATM Interfaces

You can use either of the following methods to configure and manage RADIUS authentication for IP subscribers on dynamic bridged Ethernet over dynamic ATM 1483 subinterfaces:

• The atm atm1483 subscriber command
• The subscriber management application

The atm atm1483 subscriber command does not support running stateful SRP switchover (high availability) on the router. Therefore, the configuration method you choose depends on whether stateful SRP switchover is or is not running on your router.

When you use the atm atm1483 subscriber command, as described in atm atm1483 subscriber, to configure IP subscribers on dynamic bridged Ethernet over dynamic ATM 1483 subinterface columns to support RADIUS authentication, the atm atm1483 subscriber command provides the subscriber’s authentication parameters. The dynamic ATM 1483 subinterface acts as the authenticating layer that establishes a session with RADIUS and passes the subscriber’s locally configured username and password information to the RADIUS server.

However, if your router is running stateful SRP switchover (high availability), the use of the atm atm1483 subscriber command in this configuration might suspend stateful SRP switchover on the router or prevent stateful SRP switchover from becoming active. To bypass this limitation, you can use the subscriber management application to configure IP subscribers on dynamic bridged Ethernet interfaces.

You can use the JUNOSe subscriber management application to configure and manage IP subscribers associated with a dynamic bridged Ethernet interface column. The subscriber management application uses an IP service profile to manage and authenticate IP subscribers with RADIUS. An IP service profile contains user and password information, and is used in a route map for subscriber management and to authenticate subscribers with RADIUS.

In this configuration, the IP service profile provides the subscriber’s authentication parameters, and the subscriber management application acts as the authenticating layer to obtain information from RADIUS for configuration of dynamic IP subscribers. To assign the IP service profile to the interface profile from which the dynamic bridged Ethernet interface is created, you use the bridge1483 service-profile command in Profile Configuration mode.

If stateful SRP switchover is disabled or not running on your router, you can continue to use the atm atm1483 subscriber command to configure IP subscribers on dynamic bridged Ethernet interfaces to support RADIUS authentication.

Alternatively, you can use the subscriber management application to create and configure dynamic IP interfaces regardless of whether stateful SRP switchover is running on the router. In addition, using subscriber management enables you to take advantage of several useful features such as the IP inactivity timer.

In the event that an interface profile for a dynamic bridged Ethernet interface includes the atm atm1483 subscriber command to configure a local subscriber as well as the bridge1483 service-profile command to reference an IP service profile, the values specified with the atm atm1483 subscriber command take precedence. The router ignores the values in the IP service profile in this case.

For details about using the subscriber management application to configure RADIUS authentication for IP subscribers on dynamic bridged Ethernet interfaces, see Authenticating Subscribers on Dynamic Bridged Ethernet over Static ATM Interfaces and Configuring Subscriber Management for IP Subscribers on Dynamic Bridged Ethernet Interfaces in Configuring Dynamic Interfaces. The information in these sections, which explains how to use subscriber management to achieve the same functionality as the subscriber command without adversely affecting stateful SRP switchover, applies equally to the atm atm1483 subscriber command.

For more information about using the subscriber management application, see JUNOSe Broadband Access Configuration Guide.

Configuring a Dynamic ATM 1483 Subinterface

To configure a dynamic ATM 1483 subinterface:

1. (Optional) Configure profiles containing characteristics for the dynamic upper-interface encapsulation types to be created over the dynamic ATM 1483 subinterface.

   These profiles are referenced in the base profile for the dynamic ATM subinterface as nested profile assignments. For detailed instructions on creating profiles, see Configuring a Dynamic Interface from a Profile in Configuring Dynamic Interfaces.

2. Create the base profile for the dynamic ATM 1483 subinterface by assigning the profile a name.

   host1(config)#profile atm1483BaseProfile

   This command accesses Profile Configuration mode, which enables you to configure attributes in the base profile.

3. Define attributes for the ATM 1483 subinterface in the base profile.
   1. Apply traffic-shaping parameters to the VC range on the ATM AAL5 interface.
   2. Configure the ATM 1483 subinterface for autodetection of the PPP upper-interface encapsulation type.
   3. Configure the ATM 1483 subinterface for autodetection of the IP upper-interface encapsulation type using a nondefault lockout time range of 3600–7200 seconds (1–2 hours).
   4. Configure a subscriber for the IP upper-interface encapsulation type.
   5. Configure a description for ATM 1483 subinterfaces that are created with this base profile.
   6. Set an advisory speed for ATM subinterfaces that are created with this base profile.
   7. Assign a VC class to the bulk-configured VC ranges created on the dynamic ATM 1483 subinterfaces associated with this base profile. You must issue the exit command from Profile Configuration mode for the VC class association to take effect.

      host1(config-profile)#atm pvc aal5autoconfig cbr 10000

      host1(config-profile)#atm atm1483 auto-configure ppp

      host1(config-profile)#atm atm1483 auto-configure ip lockout-time 3600 7200

      host1(config-profile)#atm atm1483 subscriber ip user-prefix joesmith
      domain myisp password-prefix abc123

      host1(config-profile)#atm atm1483 description VC_atm1

      host1(config-profile)#atm atm1483 advisory-rx-speed 2000

      host1(config-profile)#atm class-vc premium-subscriber-class

      host1(config-profile)#exit

4. (Optional) In the base profile, create nested profile assignments for the upper-interface encapsulation types, and include additional profile characteristics for other encapsulation types as needed.

   For example, the following commands configure nested profile assignments for the PPP and IP upper-interface encapsulation types, and define additional attributes for the PPPoE upper-interface encapsulation type.

   host1(config-profile)#atm atm1483 profile ppp myPppProfile

   host1(config-profile)#atm atm1483 profile ip myIpProfile

   host1(config-profile)#pppoe duplicate-protection

   host1(config-profile)#pppoe sessions 3000

5. Exit Profile Configuration mode.
6. Configure the ATM and ATM AAL5 interface.

   host1(config)#interface atm 5/0

7. Configure a range of VCs on the static ATM AAL5 interface, and assign a name to this range. This operation can take several minutes to complete, depending on the number of VCs being configured.

   Note: For information about the maximum number of ATM 1483 bulk configurations supported per chassis, see JUNOSe Release Notes, Appendix A, System Maximums.

   For example, the following command creates a VC range named myBulkConfig made up of two VC subranges that configure a total of 5,000 virtual circuits.

   host1(config-if)#atm bulk-config myBulkConfig vc-range 0 2 101 1100
   vc-range 3 6 201 700

   Note: For information about the maximum number of VCs (sum of the VPI/VCI addresses within all VC subranges) that you can configure with the atm bulk-config command per line module and per chassis, see JUNOSe Release Notes, Appendix A, System Maximums. Do not use any reserved VCI values when configuring VCs with the atm bulk-config command. For information about reserved VCIs, see Configuring F4 OAM in Configuring ATM .

8. Assign the base profile configured for the ATM 1483 subinterface to the VC range configured on the ATM AAL5 interface.

   host1(config-if)#profile atm1483 bulk-config-name myBulkConfig atm1483BaseProfile

9. Configure the ATM AAL5 interface to support autodetection of the ATM 1483 dynamic encapsulation type.

   host1(config-if)#auto-configure atm1483

atm atm1483 advisory-rx-speed

• Use to set an advisory receive speed for ATM 1483 subinterfaces that are created with the profile that you are configuring. This setting has no effect on data forwarding. You can use it to indicate the speed of the client interface. When traffic is tunneled with L2TP, the advisory receive speed is sent from the LAC to the LNS. See LAC Configuration Prerequisites for additional information about the advisory receive speed.
• The range is 0–2147483647 kbps.
• Example

  host1(config-profile)#atm atm1483 advisory-rx-speed 2000

• Use the no version to restore the default behavior—the RX speed is not sent to the LNS.
• See atm atm1483 advisory-rx-speed.

atm atm1483 auto-configure

• Use to specify the types of dynamic upper-interface encapsulations that are accepted or detected by a dynamic ATM 1483 subinterface.
• Include this command in the base profile for a dynamic ATM 1483 subinterface.
• For the bridged Ethernet, IP, PPP, and PPPoE encapsulation types, you can optionally specify the lockout time range for the encapsulation type. For more information, see Encapsulation Type Lockout .
• Examples

  host1(config-profile)#atm atm1483 auto-configure ip lockout-time 3600 7200

  host1(config-profile)#atm atm1483 auto-configure pppoe

• Use the no version to terminate detection of the specified encapsulation type
• See atm atm1483 auto-configure.

atm atm1483 description

• Use to assign a text description for ATM 1483 subinterfaces that are created with the profile that you are configuring.
• The description can be up to 255 characters.
• Example

  host1(config-profile)#atm atm1483 description VC_atm1

• Use the no version to remove the text description.
• See atm atm1483 description.

atm atm1483 profile

• Use to add a nested profile assignment to a base profile for a dynamic ATM 1483 subinterface.
• A nested profile assignment references another profile that configures attributes for a dynamic upper-interface type over the ATM 1483 subinterface.
• Example

  host1(config-profile)#atm atm1483 profile pppoe atm1483ProfilePppoe

• Use the no version to remove the profile assignment for the upper-interface encapsulation type.
• See atm atm1483 profile.

atm atm1483 subscriber

• Use to configure a local subscriber for a dynamic upper-interface encapsulation type configured over a dynamic ATM 1483 subinterface. A subscriber supports authentication and configuration from the RADIUS server.
• Optionally, you can include this command in the base profile for a dynamic ATM 1483 subinterface.
• When you configure a subscriber, you must specify the following:
  • upperInterfaceType—Type of dynamic interface, bridgedEthernet or ip
  • userNameUsage—How the dynamic interface uses the username for authentication purposes
    • user—Use the name as specified.
    • user-prefix—Use the name as a prefix to the interface physical location. The router automatically postpends the physical location of the user to the username string. The username format is userName.slot.port.vpi.vci. The resulting username string is then used to authenticate the subscriber with the RADIUS server.
  • userName—RADIUS username
  • domainName—Domain name
• You can optionally supply password information:
  • passwordUsage—How the dynamic interface uses the password for authentication purposes
    • password—Use the password as specified.
    • password-prefix—Use the password as a prefix to the interface physical location. The router automatically postpends the physical location of the user to the password string. The password format is password.slot.port.vpi.vci. The resulting password string is then used to authenticate the subscriber with the RADIUS server.
  • password—RADIUS password
• If your router is running stateful SRP switchover (high availability), the use of the atm atm1483 subscriber command to configure RADIUS authentication for subscribers on dynamic bridged Ethernet interfaces might suspend stateful SRP switchover on the router or prevent stateful SRP switchover from becoming active. For more information about using the subscriber management application to bypass this limitation, see Authenticating Subscribers on Dynamic Bridged Ethernet over Dynamic ATM Interfaces.
• Example 1

  host1(config-profile)#atm atm1483 subscriber ip user-prefix boston01
  domain myisp password-prefix abc123

• Example 2

  host1(config-subif)#atm atm1483 subscriber bridgedEthernet user westford003
  domain acmecorp.east password xyz123

• Use the no version to remove the subscriber.
• See atm atm1483 subscriber.

atm bulk-config

• Use to create a bulk-configured VC range on a static ATM AAL5 interface for use by a dynamic ATM 1483 subinterface.

  Note: For information about the maximum number of ATM 1483 bulk configurations supported per chassis, see JUNOSe Release Notes, Appendix A, System Maximums.

• Each VC range consists of one or more nonoverlapping VC subranges. A VC subrange is a group of VCs that resides within the VPI and VCI ranges you specify.
• You can configure multiple VC ranges on an ATM AAL5 interface.

  Note: For information about the maximum number of VCs (sum of the VPI/VCI addresses within all VC subranges) that you can configure with the atm bulk-config command per line module and per chassis, see JUNOSe Release Notes, Appendix A, System Maximums. Do not use any reserved VCI values when configuring VCs with the atm bulk-config command. For information about reserved VCIs, see Configuring F4 OAM in Configuring ATM .

• When you create a bulk-configured VC range, you must specify the following:
  • A name of up to 80 alphanumeric characters; this is also referred to as the bulk configuration name
  • The starting and ending VPI values (inclusive) for each VC subrange
  • The starting and ending VCI values (inclusive) for each VC subrange
• You can create a placeholder VC range by issuing the atm bulk-config command without specifying any subranges. You can assign a profile to this placeholder and add subranges to it later.
• You can add and remove individual VC subranges.
• You cannot remove a VC subrange if any dynamic ATM 1483 subinterfaces currently exist for any circuit within the subrange. Use the atm bulk-config shutdown command to remove dynamic ATM 1483 interfaces created within a subrange.
• Removal of a subrange automatically results in the removal of all overriding profile assignments on that subrange.
• You can create a bulk-configured VC subrange that includes the VPI and VCI addresses belonging to an existing ATM PVC on a static ATM interface.
• You cannot create a bulk-configured VC range on an ATM interface on which you have configured CAC. Conversely, you cannot configure CAC on an ATM interface on which you have created a bulk-configured VC range. For information about configuring CAC, see Setting Optional Parameters in Configuring ATM .
• Example 1—Configures a VC range named myBulkConfig with a single VC subrange containing VPIs 0–2 and VCIs 101–1100; this command configures a total of 3000 VCs

  host1(config-if)#atm bulk-config myBulkConfig vc-range 0 2 101 1100

• Example 2—Configures a VC range named myMultiBulkConfig with two VC subranges containing VPIs 0–1 and VCIs 101–600 (first subrange) and VPIs 3–5 and VCIs 201–3200 (second subrange); this command configures a total of 10,000 VCs

  host1(config-if)#atm bulk-config myMultiBulkConfig vc-range 0 1 101 600 vc-range 3 5 201 3200

• Use the no version to remove the specified VC range from the ATM AAL5 interface, to remove the specified subranges from the specified VC range, or to remove all subranges from the specified VC range. The no version also removes any overriding profile assignments for ATM PVCs within the deleted VC range or VC subrange.
• See atm bulk-config.

atm class-vc

• Use to assign a previously configured VC class to a base profile for a dynamic ATM 1483 subinterface.
• Issuing this command applies the set of attributes in the specified VC class to all bulk-configured VC ranges that are dynamically created from this base profile.
• You must issue the exit command from Profile Configuration mode for the VC class association to take effect.
• Changes to a VC class specified in a base profile apply only to those PVCs that are dynamically created after the change is made. These changes do not apply to dynamic PVCs that were created prior to the VC class modification.
• Example

  host1(config-profile)#atm class-vc gold-subscriber-class

  host1(config-profile)#exit

• Use the no version to remove the VC class association with the base profile.
• See atm class-vc.

atm pvc

• Use to apply encapsulation, traffic-shaping, and OAM parameters to the range of ATM PVCs configured on an ATM AAL5 interface for use by a dynamic ATM 1483 subinterface.
• Include this command in the base profile for a dynamic ATM 1483 subinterface.
• You must specify one of the following encapsulation types:
  • aal5autoconfig—Enables autodetection of the 1483 encapsulation (LLC/SNAP or VC multiplexed)
  • aal5snap—Specifies a logical link control (LLC) encapsulated circuit; the LLC/Subnetwork Access Protocol (LLC/SNAP) header precedes the protocol datagram
  • aal5mux ip—Specifies a VC-based multiplexed circuit used for IP only
• You can optionally set the peak, average, and burst sizes. To use VBR-RT or VBR-NRT as the service type, you must specify each of these options.
• The default service type is UBR. To set a different service type, specify one of the following keywords:
  • rt—Selects VBR-RT as the service type; you can select rt only if you set the peak, average, and burst parameters
  • cbr—Selects CBR as the service type; you must set the CBR rate in Kbps
• You can optionally include the oam keyword and a number of seconds in the range 1–600 to enable generation of OAM F5 loopback cells on this circuit. This option enables VC integrity features that affect the operational state of the ATM PVC.
• Example

  host1(config-profile)#atm pvc aal5autoconfig cbr 10000 oam 120

• Use the no version to restore the default service type, UBR, on the VC range.
• See atm pvc.

auto-configure atm1483

• Use to configure the static ATM AAL5 interface to support autodetection of an ATM 1483 dynamic interface type.
• You must issue this command to enable creation of a dynamic ATM 1483 subinterface.
• Example

  host1(config-if)#auto-configure atm1483

• Use the no version to terminate autodetection of the ATM 1483 encapsulation type.
• See auto-configure atm1483.

interface atm

• Use to select an ATM interface or ATM 1483 subinterface.
• To specify an ATM interface for ERX-7xx models, ERX-14xx models, and ERX-310 routers, use the slot/port.[subinterface ] format.
  • slot—Number of the chassis slot
  • port—Port number on the I/O module
  • subinterface—Number of the subinterface in the range 1–2147483647
• To specify an ATM interface for E120 and E320 routers, use the slot/adapter/port[.subinterface ] format.
  • slot—Number of the chassis slot
  • adapter—Identifier for the IOA within the E320 chassis, either 0 or 1, where:
    • 0 indicates that the IOA is installed in the right IOA bay (E120 router) or the upper IOA bay (E320 router).
    • 1 indicates that the IOA is installed in the left IOA bay (E120 router) or the lower IOA bay (E320 router).
  • port—Port number on the IOA
  • subinterface—Number of the subinterface in the range 1–2147483647
• For more information, see Creating a Basic Configuration in Configuring ATM .
• Examples

  host1(config)#interface atm 5/0.1

  host1(config)#interface atm 5/0/0.1

• Use the no version to remove the interface or subinterface.
• See interface atm.

profile

• Use to create a base profile to configure attributes for a dynamic ATM 1483 subinterface.
• Specify a profile name of up to 80 alphanumeric characters.
• Example

  host1(config)#profile atm1483BaseProfile

• Use the no version to delete the specified profile if it is not being used by any existing VC subranges.

  Note: If VC ranges are configured for the dynamic ATM 1483 subinterface associated with the base profile you want to delete, you must use the no atm bulk-config command to remove the VC ranges before you can use the no profile command to remove the associated base profile.

• See profile.

profile atm1483 bulk-config-name

• Use to assign the base profile configured for a dynamic ATM 1483 subinterface to the VC range configured on a static ATM AAL5 interface.
• You must specify both of the following:
  • Name assigned to the VC range on an ATM AAL5 interface, as specified in the atm bulk-config command
  • Name assigned to the base profile for a dynamic ATM 1483 subinterface
• Example

  host1(config-if)#profile atm1483 bulk-config-name myBulkConfig atm1483BaseProfile

• Use the no version to remove the profile assignment.
• See profile atm1483 bulk-config-name

Configuring Overriding Profile Assignments

Configuring overriding profile assignments includes the following tasks:

• Assigning an overriding profile to an ATM PVC within a bulk-configured VC subrange
• Removing an overriding profile assignment from an ATM PVC
• Removing overriding profile assignments from a VC range or VC subrange

The following sections describe how to perform these tasks.

Assigning an Overriding Profile to an ATM PVC

You can assign an overriding profile to a single ATM PVC within a bulk-configured VC subrange. Typically, the overriding profile includes debugging attributes to help you identify and troubleshoot problems with the ATM 1483 dynamic subinterface column created on the specified PVC.

To assign an overriding profile to an ATM PVC within a bulk-configured VC subrange:

1. Configure both of the following:
   • Base profile for the bulk-configured VC range on the static ATM AAL5 interface. The VC range consists of one or more VC subranges.
   • Overriding profile for an ATM PVC within a bulk-configured VC subrange

   For information about configuring profiles, see Configuring a Dynamic Interface from a Profile in Configuring Dynamic Interfaces.

2. Create a bulk-configured range of VCs on a static ATM AAL5 interface. The following commands create a bulk-configured VC range named myBulkConfig that consists of two VC subranges. The first subrange encompasses VPIs 0–4 and VCIs 21–1000. The second subrange encompasses VPIs 5–7 and VCIs 21–2000.

   host1(config)#interface atm 4/0

   host1(config-if)#atm bulk-config myBulkConfig vc-range 0 4 21 1000
   vc-range 5 7 21 2000

3. Assign the previously configured base profile (atm1483BaseProfile) to the bulk-configured VC range.

   host1(config-if)#profile atm1483 bulk-config-name myBulkConfig atm1483BaseProfile

4. Assign the previously configured overriding profile to a single ATM PVC within the bulk-configured VC subrange. The following command assigns the overriding profile myDebugProfile to the PVC with VPI 0 and VCI 101. This PVC exists within the first VC subrange (VPIs 0–4 and VCIs 21–1000) configured in Step 2.

   host1(config-if)#profile atm1483 bulk-config-name myBulkConfig pvc 0 101 myDebugProfile

   The router now uses the information in the overriding profile instead of the information in the base profile to create subsequent ATM 1483 dynamic subinterface columns over this PVC.

5. (Optional) You can assign the same overriding profile to a different ATM PVC within the same VC subrange or within a different VC subrange. For example, the following command assigns the overriding profile myDebugProfile to the PVC with VPI 6 and VCI 901. This PVC exists within the second VC subrange (VPIs 5–7 and VCIs 21–2000) configured in Step 2.

   host1(config-if)#profile atm1483 bulk-config-name myBulkConfig pvc 6 901 myDebugProfile

   Note: You can reverse the order of Step 3 and Step 4 with identical results. That is, you can assign the overriding profile to the ATM PVC and then assign the base profile to the entire VC range. In either case, you must first create the bulk-configured VC range with the atm bulk-config command.

6. Configure the ATM AAL5 interface to enable all bulk configurations and to support autodetection of the ATM 1483 dynamic encapsulation type.

   host1(config-if)#auto-configure atm1483

7. (Optional) Use the show atm bulk-config command to verify the overriding profile configuration.

   For more information about using this command, see show atm bulk-config.

Removing an Overriding Profile Assignment from an ATM PVC

After you troubleshoot the ATM 1483 dynamic subinterface column created on the specified PVC, make sure that you remove the overriding profile assignment to restore the original base profile assignment. This action ensures that subsequent ATM 1483 dynamic subinterface columns are created using the same attributes defined in the base profile.

To remove an overriding profile assignment from an ATM PVC within a bulk-configured VC range:

1. Remove the overriding profile assignment from the specified ATM PVC.

   host1(config-if)#no profile atm1483 bulk-config-name myBulkConfig pvc 0 101

2. Select the dynamic ATM 1483 subinterface on which the ATM 1483 dynamic subinterface column resides.

   host1(config)#interface atm 4/0.101

3. Use the shutdown command to disable the dynamic ATM 1483 subinterface. The shutdown command deletes the ATM 1483 dynamic subinterface column and removes the dynamic ATM 1483 subinterface.

   host1(config-subif)#shutdown

4. Send traffic over the specified PVC (VPI 0 and VCI 101) on the ATM AAL5 interface. This action re-creates the ATM 1483 dynamic subinterface column with the original base profile association.

   The router now uses the information in the base profile instead of the information in the overriding profile to create subsequent ATM 1483 dynamic subinterface columns for the specified PVC.

5. (Optional) Use the show atm bulk-config command to verify the removal of the overriding profile assignment.

   For more information about using this command, see show atm bulk-config.

Removing Overriding Profile Assignments from a VC Range or VC Subrange

When you issue the no atm bulk-config command to remove an entire VC range (and all VC subranges within that VC range), the router also removes any overriding profile assignments configured for PVCs within those VC subranges. For example, the following command removes the bulk-configured VC range named myBulkConfig and any overriding profile assignments for PVCs within the VC subranges belonging to myBulkConfig.

When you issue the no atm bulk-config command to remove a particular VC subrange in a bulk-configured VC range, the router also removes any overriding profile assignments for PVCs within that VC subrange. However, overriding profile assignments for PVCs within other VC subranges in the VC range remain intact. For example, the following command removes one VC subrange (VPIs 0–4 and VCIs 21–1000) and only those overriding profile assignments associated with this subrange.

atm bulk-config

• Use to create a bulk-configured VC range on a static ATM AAL5 interface for use by a dynamic ATM 1483 subinterface.
• For detailed information about how to use this command, see atm bulk-config.
• Example

  host1(config)#atm bulk-config test1 vc-range 0 1 101 600
  vc-range 3 5 201 3200

• Use the no version to remove the specified VC range from the ATM AAL5 interface, to remove the specified subranges from the specified VC range, or to remove all subranges from the specified VC range. The no version also removes any overriding profile assignments for ATM PVCs within the deleted VC range or VC subrange.
• See atm bulk-config.

auto-configure atm1483

• Use to configure the static ATM AAL5 interface to enable all bulk configurations and support autodetection of the ATM 1483 dynamic encapsulation type.
• You must issue this command to enable creation of a dynamic ATM 1483 subinterface.
• Example

  host1(config-if)#auto-configure atm1483

• Use the no version to terminate autodetection of the ATM 1483 encapsulation type.
• See auto-configure atm1483.

profile atm1483 bulk-config-name

• Use to assign the base profile configured for a dynamic ATM 1483 subinterface to the VC range configured on a static ATM AAL5 interface.
• You must include both of the following:
  • Name assigned to the VC range on an ATM AAL5 interface, as specified in the atm bulk-config command
  • Name assigned to the base profile for a dynamic ATM 1483 subinterface
• Example

  host1(config-if)#profile atm1483 bulk-config-name test1 test1BaseProfile

• Use the no version to remove the base profile assignment.
• See profile atm1483 bulk-config-name.

profile atm1483 bulk-config-name pvc

• Use to assign an overriding profile to a single ATM PVC that exists within a bulk-configured VC subrange.
• An overriding profile typically includes debugging attributes that help you troubleshoot problems with the ATM 1483 dynamic subinterface column created on the specified PVC.
• The VPI and VCI values of the PVC you specify must exist between the starting VPI/VCI values and ending VPI/VCI values of a VC subrange previously configured with the atm bulk-config command.
• Example 1—In this example, a previously configured VC range named test1 includes a VC subrange with VPIs 3–5 and VCIs 201–3200. The following command assigns an overriding profile (test1DebugProfile) to the ATM PVC with VPI 4 and VCI 301 that is within this subrange.

  host1(config-if)#profile atm1483 bulk-config-name test1 pvc 4 301 test1DebugProfile

• Example 2—Removes the overriding profile assignment from the ATM PVC with VPI 4 and VCI 301, and restores the original base profile assignment

  host1(config-if)#no profile atm1483 bulk-config-name test1 pvc 4 301

• Use the no version to remove the overriding profile assignment for the PVC and restore the original base profile assignment.
• See profile atm1483 bulk-config-name pvc.

shutdown

• Use to disable an interface.
• When you disable a dynamic ATM 1483 interface, the shutdown command deletes the ATM 1483 dynamic subinterface column and removes the dynamic ATM 1483 subinterface.
• Example

  host1(config-subif)#shutdown

• Because the shutdown command removes the dynamic ATM 1483 subinterface from the router, issuing a subsequent no version of this command has no effect; that is, it does not restart the disabled subinterface.
• See shutdown.

Changing VC Subranges

Changing VC subranges within a bulk-configured VC range includes the following tasks:

• Adding new VC subranges to an existing VC range
• Removing VC subranges from an existing VC range
• Modifying a VC subrange by shortening or expanding the subrange values
• Merging multiple VC subranges belonging to an existing VC range
• Changing the administrative state of VC subranges

The following sections describe how to perform these tasks.

Adding VC Subranges

You can add a new VC subrange to an existing VC range only when the new subrange does not overlap with any existing subrange. Any overlap causes the addition to fail.

You can add multiple subranges to an existing VC range simultaneously. However, the entire operation fails if even one of the new subranges overlaps with an existing subrange.

The following example specifies the original VC subranges.

To add subranges to this bulk-configured VC range, you can choose either of the following methods. Each method adds a new subrange (4, 4, 401, 450) to the existing VC range, test.

• Specify one new subrange at a time.

  host1(config-if)#atm bulk-config test vc-range 4 4 401 450

• Specify the new subrange and all the existing subranges. If you use this method, all the existing subranges and their order must match exactly, or the operation fails.

  host1(config-if)#atm bulk-config test vc-range 1 1 101 150 vc-range 2 2 201 250 vc-range 5 5 501 550 vc-range 3 3 301 350 vc-range 4 4 401 450

  The following operation fails because the order of subranges does not match the existing order.

  host1(config-if)#atm bulk-config test vc-range 2 2 201 250 vc-range 1 1 101 150 vc-range 5 5 501 550 vc-range 3 3 301 350 vc-range 4 4 401 450
  vc-range 6 6 601 650

You can create a placeholder VC range by specifying a VC range name without specifying any subrange parameters. This VC range has no circuit reservation, but you can assign a profile to it, and add subranges later as desired. The following commands illustrate this approach.

Removing VC Subranges

You can remove VC subranges from an existing VC range if no dynamic ATM 1483 subinterfaces currently exists for any circuit within those subranges. The removal operation fails if any such dynamic ATM 1483 subinterface exists. You must first remove the dynamic ATM 1483 subinterfaces before you can remove the subranges. Removal of a subrange automatically results in the removal of all overriding profile assignments on that subrange.

You can remove only a single specific VC subrange at a time. The following example specifies the original VC subranges.

The following command removes one subrange (1, 1, 101, 150) and leaves the remaining subranges, and the named VC range, test, intact.

To remove more than one VC subrange, you must issue multiple removal commands, one for each subrange. You cannot remove only part of a subrange. A removal command cannot encompass more than one subrange, even if the subranges are adjacent. However, if you do not specify any subranges, you can remove all subranges in the VC, and the named VC range, at the same time.

Modifying VC Subranges

You can shorten or expand a subrange by modifying the subrange values of a VC range. You can expand a subrange if none of the circuits added overlap with any other subrange. You can shorten a subrange if none of the circuits dropped have existing dynamic ATM 1483 subinterfaces.

You can modify only a single specific subrange at a time. The following example specifies the original VC subranges.

The following command modifies the second subrange from (2, 2, 201, 250) to
(2, 3, 210, 230).

The router retains any overriding profiles assigned to a subrange after you modify the subrange if the override assignment still falls within the modified subrange. If the assignment falls outside of the newly modified subrange, the router drops the overriding profile assignment.

You cannot modify a subrange at the same time you are adding or removing a subrange. If the new modified values for a subrange partially overlap with another subrange, the operation fails and the router displays an error message.

Merging VC Subranges

You can merge multiple subranges of any particular VC range to form a single unified subrange, conserving subrange resources. Merging takes place only when you modify a subrange so that it completely includes at least one other subrange of the same VC range. The merged subranges do not need to be adjacent to each other.

If the encompassing subrange has any circuits that are outside the subranges to be merged, those circuits are added. The encompassing subrange must cover a subrange completely to incorporate it in the merged subrange. The merge operation fails if the encompassing subrange completely overlaps some subranges but only partially overlaps with another subrange. The encompassing subrange does not have to encompass all subranges of the VC range.

Each subrange that is merged with another frees up a subrange. E-series routers currently support a maximum of 300 bulk-configured VC ranges per chassis. Therefore, if a VC range consists of 5 subranges, 295 subranges are still available for subsequent configuration. If you merge 2 of those subranges, resulting in a new total of 4 subranges in the VC range, then 296 subranges are available for configuration.

The router retains any overriding profile assignments on the subranges made before the merger, and applies them to the new merged subrange. You can separate merged subranges either by removing the merged subrange and then adding new separate subranges or by modifying the merged subrange to remove some portion of the subrange and then adding a new subrange.

The following example specifies the original VC subranges.

The following command merges two subranges, (1, 1, 101, 150) and
(2, 2, 201, 250), and effectively replaces them with the new subrange (1, 2, 101, 250).

To separate the merged subranges, you can modify the unified subrange and add subranges as needed, provided that no dynamic ATM 1483 subinterfaces currently exist for any circuit within those subranges.

If you merge subranges by using SNMP, the new merged subrange takes the lowest instance value of the incorporated subranges. For example, if a VC range has three subranges with instance values of 2, 4, and 5 and the subranges with instance values of 2 and 5 are merged, the new merged subrange has an instance value of 2.

Changing the Administrative State of VC Subranges

VC subranges have an administrative state that enables you to remove dynamic ATM 1483 subinterfaces on various subranges that belong to a single VC range. This functionality is important because subrange removal requires that no dynamic ATM 1483 subinterfaces exist for any circuit on that subrange. The removal operation fails if any such interfaces exist.

By default, the administrative state of a VC subrange is up. When you change the administrative state to down by using the atm bulk-config shutdown command, the router deletes all dynamic ATM 1483 subinterfaces on the affected subranges. You can use the show atm subinterface command or the show atm vc command to monitor the progress of the removal of all dynamic ATM 1483 subinterfaces for the specified subrange.

No additional dynamic ATM 1483 subinterfaces can be created for the subrange until you restore the administrative state to up by using the no atm bulk-config shutdown command.

The following example specifies the original VC subranges.

You cannot specify a partial subrange; the specified subrange must exactly match a subrange that has already been configured. The following command changes the administrative state of the second subrange (2, 2, 201, 250) to down. The router removes all dynamic interface columns built on any of the circuits in this subrange. No additional dynamic ATM 1483 subinterfaces can be created until you change the administrative state to up.

The following command changes the administrative state of this same VC subrange to up.

You can change the administrative state of all subranges in a VC range at the same time by issuing the command without specifying any subranges. The following command shuts down all four subranges belonging to the named VC range, test, regardless of their current state.

The time required for the router to complete an administrative state change depends on the number of VC subranges configured.

atm bulk-config

• Use to create a bulk-configured VC range on a static ATM AAL5 interface for use by a dynamic ATM 1483 subinterface.
• For detailed information about how to use this command, see atm bulk-config.
• Example

  host1(config)#atm bulk-config test1 vc-range 0 1 101 600
  vc-range 3 5 201 3200

• Use the no version to remove the specified VC range from the ATM AAL5 interface, to remove the specified subranges from the specified VC range, or to remove all subranges from the specified VC range. The no version also removes any overriding profile assignments for ATM PVCs within the deleted VC range or VC subrange.
• See atm bulk-config.

atm bulk-config modify

• Use to expand or shorten the range of the specified VC subrange. You can modify only a single specific subrange at a time.
• You can expand a subrange if none of the added circuits overlap with any other subrange. You can shorten a subrange if none of the dropped circuits have existing dynamic ATM 1483 subinterfaces.
• Modifying a subrange so that it completely includes at least one other subrange from within the same VC range effectively merges the subranges. Each subrange that is merged with another frees up a subrange for subsequent configuration. The subranges that are merged do not need to be adjacent to each other.
• The router retains any overriding profiles assigned to a subrange if the assignment falls within the modified subrange. If the assignment falls outside of the newly modified subrange, the router drops the overriding profile assignment. If two subranges are merged, the router retains overriding profiles that were assigned to the separate subranges and applies the overriding profiles to the newly merged subrange.
• Example

  host1(config-if)#atm bulk-config test modify vc-range 2 3 210 230

• There is no no version.
• See atm bulk-config modify.

atm bulk-config shutdown

• Use to administratively disable (shut down) a specified VC subrange or all subranges in a VC range. The administrative state of a VC subrange is enabled by default.
• Disabling the VC subrange deletes all dynamic ATM 1483 subinterfaces on the affected subranges. You can use the show atm subinterface command or the show atm vc command to monitor the progress of the removal of all dynamic ATM 1483 subinterfaces for the specified subrange.
• No dynamic ATM 1483 subinterfaces can subsequently be created for the subrange until you restore the administrative state to enabled by using the no atm bulk-config shutdown command.
• Example

  host1(config-if)#atm bulk-config test shutdown vc-range 2 2 201 250

• Use the no version to enable the specified VC subrange or all subranges in a VC range.
• See atm bulk-config shutdown.

Configuring Static ATM Interfaces Within VC Subranges

You can do either of the following on an E-series router:

• Create a static ATM interface within an existing bulk-configured VC subrange
• Create a bulk-configured VC subrange that includes an existing static ATM interface

The following sections describe how to perform these tasks.

Creating 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.

To create a static ATM interface within a VC subrange:

1. Create a bulk-configured VC range that includes one or more VC subranges.

   host1(config)#interface atm 0/0

   host1(config-if)#atm bulk-config test vc-range 1 3 32 1031

2. Specify a static ATM 1483 subinterface.

   host1(config-if)#interface atm 0/0.2100

3. Configure an ATM PVC with VPI and VCI values that fall within the bulk-configured VC subrange. In this example, the VPI value (2) is within the VPI range 1–3, and the VCI value (100) is within the VCI range 32–1031.

   host1(config-subif)#atm pvc 2100 2 100 aal0

4. Configure the static ATM interface. For example, the mpls-relay command creates a ATM layer 2 services over MPLS tunnel on the circuit.

   host1(config-subif)#mpls-relay 192.168.0.1 2100

Creating VC Subranges That Include Static ATM Interfaces

You can configure a bulk-configured VC subrange that includes the VPI and VCI addresses belonging to an existing ATM PVC on a static ATM interface. This example is essentially the reverse of the procedure in Creating Static ATM Interfaces Within VC Subranges.

To create a VC subrange that includes a static ATM interface:

1. Specify a static ATM 1483 subinterface.

   host1(config-if)#interface atm 3/1.201

2. Configure an ATM PVC on the static ATM 1483 subinterface. In this example, the VPI value is 1 and the VCI value is 101.

   host1(config-subif)#atm pvc 201 1 101 aal0

3. Configure the static ATM interface. For example, the mpls-relay command creates an ATM layer 2 services over MPLS tunnel on the circuit.

   host1(config-subif)#mpls-relay 5.1.1.1 201

4. Create a bulk-configured VC range that includes the VPI and VCI values of the previously configured ATM PVC. In this example, the VPI range (0–2) includes VPI 1, and the VCI range (100–250) includes VCI 101.

   host1(config)#interface atm 3/1

   host1(config-if)#atm bulk-config test2 vc-range 0 2 100 250

atm bulk-config

• Use to create a bulk-configured VC range on a static ATM AAL5 interface for use by a dynamic ATM 1483 subinterface.
• For detailed information about how to use this command, see atm bulk-config.
• Example

  host1(config)#atm bulk-config test1 vc-range 0 1 101 600
  vc-range 3 5 201 3200

• Use the no version to remove the specified VC range from the ATM AAL5 interface, to remove the specified subranges from the specified VC range, or to remove all subranges from the specified VC range. The no version also removes any overriding profile assignments for ATM PVCs within the deleted VC range or VC subrange.
• See atm bulk-config.

atm pvc

• Use to configure a PVC on an ATM interface.
• Specify the VCD, the VPI, the VCI, and the encapsulation type. For more information about these parameters, see Creating a Basic Configuration in Configuring ATM .
• You can create a PVC within an existing bulk-configured VC subrange, or a bulk-configured VC subrange that includes the VPI and VCI values of an existing PVC.
• Use the aal0 encapsulation keyword to cause the router to receive raw ATM cells on this circuit and to forward the cells without performing AAL5 packet reassembly.
• Example

  host1(config-subif)#atm pvc 10 100 22 aal0

• Use the no version to remove the specified PVC.
• See atm pvc.

interface atm

• Use to select an ATM interface or ATM 1483 subinterface.
• For information about specifying the ATM interface or subinterface, see interface atm.
• Examples

  host1(config)#interface atm 5/0.1

  host1(config)#interface atm 4/0/2

• Use the no version to remove the interface or subinterface.
• See interface atm.

mpls-relay

• Use to route layer 2 traffic to the specified router.
• For detailed information about using the mpls-relay command, see chapter Configuring Layer 2 Services over MPLS in JUNOSe BGP and MPLS Configuration Guide.
• Example

  host1(config-if)#mpls-relay 10.10.100.2 45

• Use the no version to negate this command.
• See mpls-relay.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.