[Contents] [Prev] [Next] [Index] [Report an Error]

# atm pvc

#### Syntax

To create a PVC on an ATM interface when using the aal5snap, aal5autoconfig, or aal5mux ip encapsulation type:

atm pvc vcd vpi vci encapsulation [ cbr cbr | peak [ average burst [ rt ] ] ]
[ oam [ seconds | cc [ segment | end-to-end ] { source | sink | both } ] ]
[ inArp [ minutes ] ]

no atm pvc vcd

To create a PVC on an ATM interface when using the aal5all, aal0, or ilmi encapsulation type:

atm pvc vcd vpi vci encapsulation [ cbr cbr | peak [ average burst [ rt ] ] ]

no atm pvc vcd

To use a profile to apply encapsulation and traffic-shaping parameters to a bulk range of PVCs configured for a dynamic ATM 1483 subinterface:

atm pvc encapsulation [ cbr cbr | peak [ average burst [ rt ] ] ] [oam seconds ]

no atm pvc

#### Release Information

Command introduced before JUNOSe Release 7.1.0.

#### Description

From Interface Configuration or Subinterface Configuration mode, creates a PVC on an ATM interface. The no version removes the specified PVC.

From Profile Configuration mode, applies encapsulation, traffic-shaping, and OAM parameters to the range of PVCs configured on a static ATM AAL5 interface for use by a dynamic ATM 1483 subinterface. The no version restores the default service type, UBR, on the VC range.

| Note: The optional peak, average, and burst parameters configure traffic-shaping parameters for the circuit. The allowable traffic-shaping features and range specifications depend on the line module capabilities.

#### Options

- vcd—Virtual circuit descriptor that is an identifier for the VC in other commands; in the range 1–2147483647
- vpi—Virtual path identifier of this PVC. The allowable numeric range depends on the line module capabilities and current configuration. The VPI and VCI cannot both be set to 0; if one is 0, the other cannot be 0.
- vci—Virtual circuit identifier of this PVC. The allowable numeric range depends on the line module capabilities and current configuration. The VPI and VCI cannot both be set to 0; if one is 0, the other cannot be 0.
- encapsulation—Available options differ for ATM interfaces and dynamic ATM 1483 subinterfaces, as follows:
  - For PVCs created on ATM interfaces:
    - aal5all—Causes the router to pass through all ATM AAL5 traffic without interpreting it; supported for ATM layer 2 services over MPLS
    - aal0—Causes the router to receive raw ATM cells on this circuit and forward the cells without performing AAL5 packet reassembly; supported for ATM layer 2 services over MPLS
    - aal5snap—LLC encapsulated circuit; LLC/SNAP header precedes the protocol datagram
    - aal5mux ip—VC-based multiplexed circuit used for IP only
    - aal5autoconfig—Enables autodetection of the 1483 encapsulation (LLC/SNAP or VC multiplexed)
    - ilmi—Integrated local management interface encapsulation
  - For PVCs created on dynamic ATM 1483 subinterfaces:
    - aal5snap—LLC encapsulated circuit; LLC/SNAP header precedes the protocol datagram
    - aal5mux ip—VC-based multiplexed circuit used for IP only
    - aal5autoconfig—Enables autodetection of the 1483 encapsulation (LLC/SNAP or VC multiplexed)
- cbr—Constant bit rate in Kbps
- peak—PCR in Kbps
- average—Average rate in Kbps; also referred to as SCR
- burst—Length in cells of the burst; also referred to as MBS
- rt—Selects VBR-RT as the service type; the default type is VBR-NRT. You can select rt only if you set the peak, average, and burst parameters.
- oam—Enables generation of OAM F5 loopback cells on this circuit. This option enables VC integrity features that affect the operational state of the ATM PVC. You can use the oam keyword only if you specify the aal5snap, aal5autoconfig, or aal5mux ip encapsulation type.
- seconds—Time interval in the range 1–600 seconds between transmissions of OAM F5 end-to-end loopback cells for VC connectivity verification.
- inArp—Enables Inverse ARP. You can use the inArp keyword only if you specify the aal5snap encapsulation type.
- minutes—Inverse ARP refresh rate in minutes; 15 minutes is the default
- cc—Enables CC cells on the PVC; you can enable CC cells only on data circuits, not on control circuits, such as ILMI or signaling circuits
- segment—Opens an OAM CC segment cell flow
- end-to-end—Opens an OAM CC end-to-end cell flow
- sink—Enables this VC as a sink point (cell receiver)
- source—Enables this VC as the source point (cell generator)
- both—Enables this VC as both a sink point and a source point

#### Mode

Interface Configuration, Profile Configuration, Subinterface Configuration

#### Related Topics

- Configuring an MPLS Pseudowire with VCC Cell Relay Encapsulation, Configuring Local ATM Cross-Connects with AAL5 Encapsulation, and Configuring MPLS LSPs for L2VPNs in the JUNOSe BGP and MPLS Configuration Guide

[Contents] [Prev] [Next] [Index] [Report an Error]