ATM Configuration Seul
ATM Configuration Seul
Software
              This chapter describes how to configure ATM on the Cisco XR 12000 Series Router using
              Cisco IOS XR software. ATM is a cell-switching and multiplexing technology that is widely used in
              Wide Area Networks (WANs). ATM protocol standards enable point-to-point, point-to-multipoint, and
              broadcast services connections using various slow- and high-speed network media. Connectivity
              between two ATM permanent virtual circuits (PVCs) is established using ATM signaling mechanisms.
              Various ATM signaling standards are defined by the following ATM forum standards:
               •   UNI Version 3.0, Version 3.1, and Version 4.0
               •   ITU
               •   IETF
Contents
               •   Prerequisites for Implementing ATM, page 2
               •   Information About ATM, page 2
Note A single ATM interface can simultaneously support point-to-point and L2VPN subinterfaces.
                         In Cisco IOS XR software, ATM interface configuration is hierarchical and comprises the following
                         elements:
                          1.   The ATM main interface, which is the physical interface. ATM main interfaces can be configured
                               with point-to-point subinterfaces, VP-tunnels, ILMI interfaces, or as Layer 2 port mode attachment
                               circuits (ACs) or Layer 2 subinterface ACs.
                          2.   ATM subinterfaces, which are configured under the ATM main interface. An ATM subinterface does
                               not actively carry traffic until you configure a PVC or PVP under the ATM subinterface.
                          3.   PVCs, which are configured under an ATM subinterface. A single PVC is allowed per subinterface.
                               PVCs are supported under point-to-point and Layer 2 subinterfaces.
                          4.   Permanent virtual paths (PVPs), which are configured under a Layer 2 ATM subinterface. A single
                               PVP is allowed per subinterface.
VC-Class Mapping
                         A virtual circuit (VC) class enables the configuration of VC parameters that are then mapped to a main
                         interface, subinterface, or PVC. Without vc-classes, you must perform considerable manual
                         configuration on each ATM main interface, subinterface, and PVC and on the router. This configuration
                         can be time consuming and error prone. After you have created vc-class, you can apply that vc-class to
                         as many ATM interfaces, subinterfaces, or PVCs as you want.
                         Vc-classes include the following types of configuration data:
                           •   ATM encapsulation for the VC
                           •   OAM management
                           •   traffic shaping
                         The order of configuration precedence is hierarchical, as demonstrated in the following list, where
                         configuration on the PVC takes the highest precedence, and configuration on a vc-class that is attached
                         to the ATM main interface takes the lowest precedence:
                          1.   Configuration on the PVC
                          2.   Configuration on a vc-class that is attached to the PVC
                          3.   Configuration on the subinterface
                          4.   Configuration on a vc-class that is attached to the subinterface
                          5.   Configuration on the ATM main interface
                          6.   Configuration on a vc-class that is attached to the ATM main interface
                         For example, if the a PVC has unspecified bit rate (UBR) traffic shaping configured, but it is attached to
                         a class map that is configure with CBR traffic shaping, the PVC maintains the UBR traffic shaping.
               Note      Vc-classes are not applicable to Layer 2 port mode ACs and Layer 2 PVPs. For Layer 2 VPN
                         configurations, Vc-classes are applicable to the PVC only.
VP-Tunnels
                          ATM interfaces support vp-tunnels. Vp-tunnels are typically used to shape PVCs into a bundle and
                          manage F4 Operation, Administration, and Maintenance (OAM). A Vp-tunnel is configured under the
                          main ATM interface, and then subinterfaces and PVCs can be added to the vp-tunnel. Vp-tunnels and the
                          PVCs that are configured under them share the same VPI. When a vp-tunnel goes down, all PVCs
                          configured under that vp-tunnel go down, too.
                          By default, two F4 OAM connections are automatically opened for each vp-tunnel. Use the f4oam
                          disable command in ATM vp-tunnel configuration mode to disable the F4 OAM packets for a vp-tunnel.
             Note         The oam ais-rdi and oam retry commands take affect only after OAM management is enabled on a PVC
                          with the oam-pvc manage command.
             Note         You must use the same VPI and VCI values on both ends of the PVC that connects the end device and
                          the router.
               Note      The ILMI configuration commands are available only after an ILMI PVC is created under the ATM main
                         interface. The ILMI configuration takes affect on the ATM main interface.
               Note      For detailed information about configuring an L2VPN network, see the “Implementing MPLS Layer 2
                         VPNs” module of Cisco IOS XR Multiprotocol Label Switching Configuration Guide.
Prerequisites
                         You must have one of the following line cards installed in a Cisco XR 12000 Series Router that is
                         running Cisco IOS XR software:
                          •    4-port OC12
                          •    4-port OC3
Restrictions
                         The configuration on both ends of the ATM connection must match for the interface to be active.
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance
                          3.   no shutdown
                          4.   end
                               or
                               commit
                          5.   exit
                          6.   exit
                          7.   Repeat Step 1 through Step 6 to bring up the interface at the other end of the connection.
                          8.   show interfaces atm instance brief
DETAILED STEPSs
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance                                       Enters ATM interface configuration mode.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1
Step 3    no shutdown                                                  Removes the shutdown configuration.
                                                                       Note      Removal of the shutdown configuration eliminates
          Example:                                                               the forced administrative down on the interface,
          RP/0/0/CPU0:router (config-if)# no shutdown                            enabling it to move to an up or down state.
Step 4    end                                                          Saves configuration changes.
          or
                                                                        •     When you issue the end command, the system prompts
          commit                                                              you to commit changes:
                                                                              Uncommitted changes found, commit them before
          Example:                                                            exiting(yes/no/cancel)?
          RP/0/0/CPU0:router (config-if)# end                                 [cancel]:
          or
                                                                               – Entering yes saves configuration changes to the
          RP/0/0/CPU0:router(config-if)# commit                                   running configuration file, exits the configuration
                                                                                  session, and returns the router to EXEC mode.
                                                                               – Entering no exits the configuration session and
                                                                                  returns the router to EXEC mode without
                                                                                  committing the configuration changes.
                                                                               – Entering cancel leaves the router in the current
                                                                                  configuration session without exiting or
                                                                                  committing the configuration changes.
                                                                        •     Use the commit command to save the configuration
                                                                              changes to the running configuration file and remain
                                                                              within the configuration session.
         Example:
         RP/0/0/CPU0:router (config)# exit
Step 7   Repeat Step 1 through Step 6 to bring up the interface Brings up the connection.
         at the other end of the connection.
                                                                Note   The configuration on both ends of the ATM
                                                                       connection must match.
Step 8   show interfaces atm instance brief                                 (Optional) Verifies that the interface is active and properly
                                                                            configured.
         Example:                                                           If you have brought up an ATM interface properly, the
         RP/0/0/CPU0:router# show interfaces atm 0/6/0/1                    “Intf State” field for that interface in the show interfaces
         brief                                                              atm command output shows “up.”
What to do Next
                          •   To modify the default configuration of the ATM interface you just brought up, see the “Configuring
                              Optional ATM Interface Parameters” section on page 8.
                          •   To configure a point-to-point subinterface on the ATM interface you just brought up, see the “How
                              to Create and Configure a Point-to-Point ATM Subinterface with a PVC” section on page 11.
                          •   To create a Vp-tunnel on the ATM interface you just brought up, see the “How to Create and
                              Configure a VP-Tunnel” section on page 16.
                          •   To use the interface as a Layer 2 post mode AC, see the “How to Configure a Layer 2 Attachment
                              Circuit” section on page 22.
                          •   To attach a Vc-class to the ATM interface you just brought up, see the “How to Create and Configure
                              a Vc-Class” section on page 33.
                          •   To enable ILMI on the ATM interface you just brought up, see the “How to Configure ILMI on ATM
                              Interfaces” section on page 41.
Prerequisites
                         Before you modify the default ATM interface configuration, we recommend that you bring up the ATM
                         interface and remove the shutdown configuration, as described in the “Bringing Up an ATM Interface”
                         section on page 6.
Restrictions
                         The configuration on both ends of the ATM connection must match for the interface to be active.
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance
                          3.   atm maxvpi-bits 12
                          4.   atm oam flush
                          5.   atm mcpt-timers timer-1 timer-2 timer-3
                          6.   end
                               or
                               commit
                          7.   exit
                          8.   exit
                          9.   show atm interface atm [instance]
                         10. show interfaces atm instance brief
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance                                     Enters ATM interface configuration mode.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1
Step 3    atm maxvpi-bits 12                                         (Optional) Enables support for the 12-bit VPI NNI cell
                                                                     format.
          Example:
          RP/0/0/CPU0:router (config-if)# atm maxvpi-bits
          12
Step 4    atm oam flush                                              (Optional) Drops all current and future OAM cells received
                                                                     on an ATM interface.
          Example:
          RP/0/0/CPU0:router (config-if)# atm oam flush
Step 5    atm mcpt-timers timer-1 timer-2 timer-3                    (Optional) Specifies the maximum cell packing timeout
                                                                     values for each of the three per-interface MCPT timers, in
                                                                     microseconds.
          Example:
          RP/0/0/CPU0:router (config-if)# atm mcpt-timers            Note     The default value for each timer is 50 microseconds.
          50 100 200
                                                                     Note     The atm mcpt-timers command is applicable to
                                                                              Layer 2 ATM ACs only.
          Example:
          RP/0/0/CPU0:router (config)# exit
Step 9    show atm interface atm [instance]                                  (Optional) Displays ATM-specific data for the specified
                                                                             ATM interface.
          Example:
          RP/0/0/CPU0:router# show atm interface atm
          0/6/0/1
Step 10   show interfaces atm instance                                       (Optional) Displays general information for the specified
                                                                             ATM interface.
          Example:
          RP/0/0/CPU0:router# show interfaces atm 0/6/0/1
What to do Next
                           •   To configure a point-to-point subinterface on the ATM interface you just brought up, see the “How
                               to Create and Configure a Point-to-Point ATM Subinterface with a PVC” section on page 11.
                           •   To create a Vp-tunnel on the ATM interface you just brought up, see the “How to Create and
                               Configure a VP-Tunnel” section on page 16.
                           •   To use the interface as a Layer 2 ATM AC, see the “How to Configure a Layer 2 Attachment Circuit”
                               section on page 22.
                           •   To attach a Vc-class to the ATM interface you just brought up, see the “How to Create and Configure
                               a Vc-Class” section on page 33.
                           •   To enable ILMI on the ATM interface you just brought up, see the “How to Configure ILMI on ATM
                               Interfaces” section on page 41.
Prerequisites
                         Before you can create an ATM subinterface on an ATM interface, you must bring up an ATM interface,
                         as described in the “Bringing Up an ATM Interface” section on page 6.
Restrictions
                         Only one PVC can be configured for each point-to-point ATM subinterface.
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance.subinterface point-to-point
                          3.   ipv4 address ipv4_address/prefix
                          4.   pvc vpi/vci
                          5.   end
                               or
                               commit
                          6.   Repeat Step 1 through Step 5 to bring up the ATM subinterface and any associated PVC at the other
                               end of the connection.
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface                                 Enters ATM subinterface configuration mode.
          point-to-point
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1.10
Step 3    ipv4 address ipv4_address/prefix                                    Assigns an IP address and subnet mask to the subinterface.
          Example:
          RP/0/0/CPU0:router (config-subif)#ipv4 address
          10.46.8.6/24
Step 4    pvc vpi/vci                                                         (Optional) Creates an ATM permanent virtual circuit (PVC)
                                                                              and enters ATM PVC configuration submode.
          Example:                                                            Note      Only one PVC is allowed per subinterface.
          RP/0/0/CPU0:router (config-subif)# pvc 5/10
Step 5    end                                                                 Saves configuration changes.
          or
                                                                               •     When you issue the end command, the system prompts
          commit                                                                     you to commit changes:
                                                                                     Uncommitted changes found, commit them before
          Example:                                                                   exiting(yes/no/cancel)?
          RP/0/0/CPU0:router (config-subif)# end                                     [cancel]:
          or
                                                                                      – Entering yes saves configuration changes to the
          RP/0/0/CPU0:router(config-subif)# commit                                       running configuration file, exits the configuration
                                                                                         session, and returns the router to EXEC mode.
                                                                                      – Entering no exits the configuration session and
                                                                                         returns the router to EXEC mode without
                                                                                         committing the configuration changes.
                                                                                      – Entering cancel leaves the router in the current
                                                                                         configuration session without exiting or
                                                                                         committing the configuration changes.
                                                                               •     Use the commit command to save the configuration
                                                                                     changes to the running configuration file and remain
                                                                                     within the configuration session.
Step 6    Repeat Step 1 through Step 5 to bring up the ATM                    Brings up the ATM connection.
          subinterface and any associated PVC at the other end
                                                                              Note      The configuration on both ends of the subinterface
          of the connection.
                                                                                        connection must match.
What to do Next
                           •   To configure optional PVC parameters, see the “Configuring Optional Point-to-Point ATM PVC
                               Parameters” section on page 13.
                           •   To attach Layer 3 service policies, such as Multiprotocol Label Switching (MPLS) or quality of
                               service (QoS), to the PVC under the PVC submode, refer to the appropriate Cisco IOS XR software
                               configuration guide.
                           •   To configure a vc-class and apply it to an ATM subinterface or PVC, see the “Creating and
                               Configuring a VC-Class” section on page 34.
Prerequisites
                         Before you can modify the default PVC configuration, you must create the PVC on an ATM subinterface,
                         as described in the “Creating a Point-to-Point ATM Subinterface with a PVC” section on page 11.
Restrictions
                         The configuration on both ends of the PVC must match for the connection to be active.
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance.subinterface point-to-point
                          3.   pvc vpi/vci
                          4.   encapsulation {aal5mux ipv4 | aal5nlpid | aal5snap}
                          5.   oam-pvc manage [frequency] [disable] [keep-vc-up [seg-aisrdi-failure]]
                          6.   oam ais-rdi [down-count [up-count]]
                          7.   oam retry
                          8.   shape [cbr peak_output_rate | ubr peak_output_rate | vbr-nrt peak_output_rate
                               sustained_output_rate burst_size| vbr-rt peak_output_rate sustained_output_rate burst_size]
                          9.   service-policy [input | output] policy_name
                         10. end
                               or
                               commit
                         11. Repeat Step 1 through Step 10 to configure the PVC at the other end of the connection.
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface                                 Enters ATM subinterface configuration mode.
          point-to-point
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1.10 point-to-point
Step 3    pvc vpi/vci                                                         Enters subinterface configuration mode for the PVC.
          Example:
          RP/0/0/CPU0:router (config-subif)# pvc 5/10
Step 4    encapsulation {aal5mux ipv4 | aal5nlpid |                           Configures the ATM adaptation layer (AAL) and
          aal5snap}                                                           encapsulation type for a PVC.
                                                                              Note      The default encapsulation type for a vc-class is
          Example:                                                                      AAL5/SNAP
          RP/0/0/CPU0:router (config-atm-vc)#
          encapsulation aal5snap
Step 5    oam-pvc manage [frequency] [disable]                                Enable ATM OAM F5 loopback cell generation and
          [keep-vc-up [seg-aisrdi-failure]                                    configures continuity check (CC) management for the ATM
                                                                              permanent virtual circuit (PVC).
          Example:                                                             •     Include the disable keyword to disable OAM
          RP/0/0/CPU0:router (config-atm-vc)# oam-pvc                                management on the specified PVC.
          manage 200 keep-vc-up
                                                                               •     Include the keep-vc-up keyword specify that PVC
                                                                                     remains in the UP state when CC cells detect
                                                                                     connectivity failure.
                                                                               •     Include the seg-aisrdi-failure keyword to specify that,
                                                                                     if segment AIS/RDI cells are received, the VC will not
                                                                                     be brought down because of end CC failure or loopback
                                                                                     failure.
Step 6    oam ais-rdi [down-count [up-count]]                                 Configures the PVC so that it is brought down after a
                                                                              specified number of OAM alarm indication signal/remote
                                                                              defect indication (AIS/RDI) cells are received on the
          Example:
          RP/0/0/CPU0:router (config-atm-vc)# oam ais-rdi
                                                                              associated PVC.
          25 5
Step 7    oam retry [up-count [down-count                                     Configures parameters related to OAM management for the
          [retry-frequency]]]                                                 PVC.
                                                                              If no OAM AIS/RDI cells are received within the specified
          Example:                                                            interval, the PVC is brought up.
          RP/0/0/CPU0:router (config-atm-vc)# oam retry 5
          10 5
What to do Next
                           •   To attach Layer 3 service policies, such as MPLS or QoS, to the PVC under the PVC submode, refer
                               to the appropriate Cisco IOS XR software configuration guide.
                           •   To configure a vc-class and apply it to an ATM subinterface or PVC, see the “Creating and
                               Configuring a VC-Class” section on page 34.
Note VP-tunnels are specific to point-to-point ATM interfaces and cannot be configured on ATM ACs.
Prerequisites
                         Before you can create a vp-tunnel on an ATM main interface, you must bring up an ATM interface, as
                         described in the “Bringing Up an ATM Interface” section on page 6.
Restrictions
                          •    A vp-tunnel is not truly active until a PVC is created with the same VPI value as the vp-tunnel, as
                               described in the “Creating and Configuring Subinterfaces with PVCs on a VP-tunnel” section on
                               page 19.
                          •    When a vp-tunnel goes down, all VCs that are configured under that vp-tunnel go down.
                          •    The following cards do not support Vp-tunnels with a VPI of 0:
                                – 4-Port OC-3c/STM-1c ATM ISE Line Card, multimode
                                – 4-Port OC-3c/STM-1c ATM ISE Line Card, single-mode
                                – 4-port OC-12/STM-4 ATM multimode ISE line card with SC connector
                                – Series 4-port OC-12/STM-4 ATM single-mode, intermediate-reach ISE line card with SC
                                   Connector
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance
                          3.   vp-tunnel vpi
                          4.   f4oam disable
                          5.   shape [cbr peak_output_rate | vbr-nrt peak_output_rate sustained_output_rate burst_size | vbr-rt
                               peak_output_rate sustained_output_rate burst_size]
                          6.   end
                               or
                               commit
                          7.   exit
                          8.   exit
                          9.   Repeat Step 1 through Step 8 to bring up the vp-tunnel at the other end of the connection.
                         10. show atm vp-tunnel interface atm [instance]
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance                                       Enters ATM interface configuration mode.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1
Step 3    vp-tunnel vpi                                                Configures a vp-tunnel on an ATM interface.
          Example:
          RP/0/0/CPU0:router (config)# vp-tunnel 10
Step 4    f4oam disable                                                (Optional) Disables the passing of OAM packets.
          Example:
          RP/0/0/CPU0:router(config-atm-vp-tunnel)# f4oam
          disable
          Example:
          RP/0/0/CPU0:router (config)# exit
What to do Next
                         To attach Layer 3 service policies, such as MPLS or QoS, to the vp-tunnel or its PVCs, refer to the
                         appropriate Cisco IOS XR software configuration guide.
Note A vp-tunnel is not truly active until a PVC is created with the same VPI value as the vp-tunnel.
Prerequisites
                         Before you can create a subinterface with a PVC on an ATM vp-tunnel, you must create a vp-tunnel on
                         the ATM main interface, as described in the “Creating and Configuring a VP-Tunnel on an ATM
                         Interface” section on page 16.
Restrictions
                           •   A PVC and its host vp-tunnel must share the same VPI for the connection to be active.
                           •   The following cards do not support Vp-tunnels with a VPI of 0:
                                – 4-Port OC-3c/STM-1c ATM ISE Line Card, multimode
                                – 4-Port OC-3c/STM-1c ATM ISE Line Card, single-mode
                                – 4-port OC-12/STM-4 ATM multimode ISE line card with SC connector
                                – Series 4-port OC-12/STM-4 ATM single-mode, intermediate-reach ISE line card with SC
                                    Connector
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance.subinterface point-to-point
                          3.   ipv4 address ipv4_address/prefix
                          4.   pvc vpi/vci
                          5.   end
                               or
                               commit
                          6.   Repeat Step 1 through Step 5 to bring up the ATM subinterface and PVC at the other end of the
                               connection.
                          7.   ping atm interface atm instance.subinterface vpi/vci
                          8.   show atm vp-tunnel [interface atm instance]
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface                               Creates a new subinterface and enters ATM subinterface
          point-to-point                                                    configuration mode for that subinterface.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1.10 point-to-point
Step 3    ipv4 address ipv4_address/prefix                                  Assigns an IP address and subnet mask to the subinterface.
          Example:
          RP/0/0/CPU0:router (config-subif)#ipv4 address
          10.46.8.6/24
Step 4    pvc vpi/vci                                                       Creates an ATM permanent virtual circuit (PVC) on the
                                                                            subinterface and attaches it to the vp-tunnel you created in
                                                                            the “Creating and Configuring a VP-Tunnel on an ATM
          Example:
          RP/0/0/CPU0:router (config-subif)# pvc 5/10
                                                                            Interface” section on page 16.
                                                                            Replace vpi with the VPI of the vp-tunnel on which you are
                                                                            creating the PVC.
                                                                            Note    The PVC VPI and vp-tunnel VCI must match or the
                                                                                    connection will not be active.
What to do Next
                           •   To create and configure ATM subinterfaces and PVCs on a vp-tunnel, see the “Creating and
                               Configuring Subinterfaces with PVCs on a VP-tunnel” section on page 19
                           •   To configure a vc-class and apply it to an ATM interface, see the “Creating and Configuring a
                               VC-Class” section on page 34.
               Note       After you configure an interface for Layer 2 switching, no routing commands such as ipv4 address are
                          permissible. If any routing commands are configured on the interface, then the l2transport command is
                          rejected.
Prerequisites
                          Before you can create a Layer 2 port mode AC, you must bring up an ATM main interface, as described
                          in the “Bringing Up an ATM Interface” section on page 6.
Restrictions
                          ILMI configuration is not supported on Layer 2 port mode ACs.
Restrictions
                          Before you can configure an Layer 2 port mode AC, you must ensure that no configuration, such as
                          subinterfaces, already exists on that port. If any preconfiguration does exist, you must remove it.
SUMMARY STEPS
                           1.   configure
                           2.   interface atm instance
                           3.   l2transport
                           4.   end
                                or
                                commit
                           5.   Repeat Step 1 through Step 4 to bring up the ATM AC at the other end of the connection.
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance                                      Enters interface configuration mode for an ATM interface.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1
Step 3    l2transport                                                 Enters ATM Layer 2 transport configuration mode, and
                                                                      enables Layer 2 port mode on this ATM interface.
          Example:
          RP/0/0/CPU0:router (config-if)# l2transport
Step 4    end                                                         Saves configuration changes.
          or
                                                                       •     When you issue the end command, the system prompts
          commit                                                             you to commit changes:
                                                                             Uncommitted changes found, commit them before
          Example:                                                           exiting(yes/no/cancel)?
          RP/0/0/CPU0:router (config-if-l2)# end                             [cancel]:
          or
                                                                              – Entering yes saves configuration changes to the
          RP/0/0/CPU0:router(config-if-l2)# commit                               running configuration file, exits the configuration
                                                                                 session, and returns the router to EXEC mode.
                                                                              – Entering no exits the configuration session and
                                                                                 returns the router to EXEC mode without
                                                                                 committing the configuration changes.
                                                                              – Entering cancel leaves the router in the current
                                                                                 configuration session without exiting or
                                                                                 committing the configuration changes.
                                                                       •     Use the commit command to save the configuration
                                                                             changes to the running configuration file and remain
                                                                             within the configuration session.
Step 5    Repeat Step 1 through Step 4 to bring up the Layer 2        Brings up the Layer 2 port mode AC.
          port mode AC at the other end of the connection.
                                                                      Note      The configuration on both ends of the connection
                                                                                must match.
What to do Next
                           •   To configure a point-to-point pseudowire XConnect on the Layer 2 port mode AC you just created,
                               see the “Implementing MPLS Layer 2 VPNs” module of Cisco IOS XR Multiprotocol Label
                               Switching Configuration Guide.
                           •   To configure optional Layer 2 VPN parameters for the ATM AC, see the “Configuring Optional
                               Parameters on a Layer 2 Port Mode AC” section on page 24.
Prerequisites
                          Before you can configure Layer 2 VPN parameters on a Layer 2 port mode AC, you must create a Layer
                          2 port mode AC, as described in the “Creating a Layer 2 Port Mode AC” section on page 22.
SUMMARY STEPS
                           1.   configure
                           2.   interface atm instance
                           3.   atm mcpt-timers timer-1 timer-2 timer-3
                           4.   l2transport
                           5.   cell-packing cells timer
                           6.   end
                                or
                                commit
                           7.   Repeat Step 1 through Step 6 to configure the Layer 2 port mode AC at the other end of the
                                connection.
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance                                            Enters interface configuration mode for an ATM interface.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1
Step 3    atm mcpt-timers timer-1 timer-2 timer-3                           Specifies the maximum cell packing timeout values for each
                                                                            of the three per-interface MCPT timers, in microseconds.
          Example:                                                          Note    The default value for each timer is 50 microseconds.
          RP/0/0/CPU0:router (config-if)# atm mcpt-timers
          50 100 200
Step 4    l2transport                                                       Enters ATM Layer 2 transport configuration mode.
          Example:
          RP/0/0/CPU0:router (config-if)# l2transport
Prerequisites
                         Before you can create a subinterface on an ATM interface, you must bring up an ATM interface, as
                         described in the “Bringing Up an ATM Interface” section on page 6.
Restrictions
                         Only one PVC can be configured for each ATM subinterface.
SUMMARY STEPS
                           1.   configure
                           2.   interface atm instance.subinterface l2transport
                           3.   pvc vpi/vci
                           4.   end
                                or
                                commit
                           5.   Repeat Step 1 through Step 4 to bring up the ATM subinterface and any associated PVC at the other
                                end of the AC.
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface l2transport                   Creates a subinterface and enters ATM subinterface
                                                                            configuration mode for that subinterface.
          Example:
          RP/0/0/CPU0:router(config)# interface atm
          0/6/0/1.10 l2transport
Step 3    pvc vpi/vci                                                       Creates an ATM permanent virtual circuit (PVC) and enters
                                                                            ATM Layer 2 transport PVC configuration mode.
          Example:                                                          Note    Only one PVC is allowed per subinterface.
          RP/0/0/CPU0:router(config-if)# pvc 5/20
What to do Next
                           •   To configure optional PVC parameters, see the “Configuring Optional ATM Layer 2 PVC
                               Parameters” section on page 27.
                           •   To configure a vc-class and apply it to the PVC, see the“Attaching a Vc-Class to a PVC on an ATM
                               Subinterface” section on page 39.
                           •   To configure a point-to-point pseudowire XConnect on the AC you just created, see the
                               “Implementing MPLS Layer 2 VPNs” module of Cisco IOS XR Multiprotocol Label Switching
                               Configuration Guide.
Prerequisites
                         Before you can modify the default PVC configuration, you must create the PVC on a Layer 2 ATM
                         subinterface, as described in the “Creating an ATM Layer 2 Subinterface with a PVC” section on
                         page 25.
Restrictions
                          The configuration on both ends of the PVC must match for the connection to be active.
SUMMARY STEPS
                           1.   configure
                           2.   interface atm instance.subinterface l2transport
                           3.   pvc vpi/vci
                           4.   encapsulation {aal0 | aal5}
                           5.   cell-packing cells timer
                           6.   shape [cbr peak_output_rate | ubr peak_output_rate | vbr-nrt peak_output_rate
                                sustained_output_rate burst_size| vbr-rt peak_output_rate sustained_output_rate burst_size]
                           7.   end
                                or
                                commit
                           8.   Repeat Step 1 through Step 7 to configure the PVC at the other end of the AC.
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface l2transport                   Enters ATM subinterface configuration mode for a Layer 2
                                                                            ATM subinterface.
          Example:
          RP/0/0/CPU0:router(config-if)# interface atm
          0/6/0/1.10 l2transport
Step 3    pvc vpi/vci                                                       Enters ATM Layer 2 transport PVC configuration mode for
                                                                            the specified PVC.
          Example:
          RP/0/0/CPU0:router(config-atm-l2transport-pvc)#
          pvc 5/20
Step 4    encapsulation {aal0 | aal5}                                       Configures the ATM adaptation layer (AAL) and
                                                                            encapsulation type for a PVC.
          Example:                                                          Note    The default encapsulation type for a PVC is AAL5.
          RP/0/0/CPU0:router(config-atm-l2transport-pvc)#
          encapsulation aal5
What to do Next
                           •   To configure a pseudo-wire XConnect on the AC you just created, see the “Implementing MPLS
                               Layer 2 VPNs” module of Cisco IOS XR Multiprotocol Label Switching Configuration Guide.
                           •    To configure a vc-class and apply it to the PVC, see the“Attaching a Vc-Class to a PVC on an ATM
                                Subinterface” section on page 39.
Prerequisites
                          Before you can create a subinterface with a PVP on an ATM interface, you must bring up an ATM
                          interface, as described in the “Bringing Up an ATM Interface” section on page 6.
Restrictions
                           •    Only one PVP can be configured for each L2VPN ATM AC.
                           •    F4 OAM emulation is not supported on Layer 2 PVPs.
SUMMARY STEPS
                           1.   configure
                           2.   interface atm instance.subinterface l2transport
                           3.   pvp vpi
                           4.   end
                                or
                                commit
                           5.   Repeat Step 1 through Step 4 to bring up the ATM subinterface and any associated PVP at the other
                                end of the AC.
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface l2transport                   Creates an ATM subinterface and enters ATM layer2
                                                                            transport configuration mode for that subinterface.
          Example:
          RP/0/0/CPU0:router(config)# interface atm
          0/6/0/1.10 l2transport
Step 3    pvp vpi                                                           (Optional) Creates an ATM PVP and enters ATM PVP
                                                                            configuration submode.
          Example:                                                          Note    Only one PVP is allowed per subinterface.
          RP/0/0/CPU0:router(config-if)# pvp 100
What to do Next
                           •   To configure optional PVP parameters, see the “Configuring Optional ATM Layer 2 PVP
                               Parameters” section on page 31.
                           •   To configure a point-to-point pseudowire XConnect on the AC you just created, see the
                               “Implementing MPLS Layer 2 VPNs” module of Cisco IOS XR Multiprotocol Label Switching
                               Configuration Guide.
Prerequisites
                         Before you can modify the default PVP configuration, you must create the PVP on an ATM subinterface,
                         as described in the “Creating an ATM Layer 2 Subinterface with a PVP” section on page 30.
Restrictions
                           •   The following cards do not support Vp-tunnels with a VPI of 0:
                                – 4-Port OC-3c/STM-1c ATM ISE Line Card, multimode
SUMMARY STEPS
                           1.   configure
                           2.   interface atm instance.subinterface l2transport
                           3.   pvp vpi
                           4.   cell-packing cells timer
                           5.   shape [cbr peak_output_rate | ubr peak_output_rate | vbr-nrt peak_output_rate
                                sustained_output_rate burst_size| vbr-rt peak_output_rate sustained_output_rate burst_size]
                           6.   end
                                or
                                commit
                           7.   Repeat Step 1 through Step 6 to configure the PVP at the other end of the connection.
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface l2transport                   Enters ATM subinterface configuration mode.
          Example:
          RP/0/0/CPU0:router(config)# interface atm
          0/6/0/1.10 l2transport
Step 3    pvp vpi                                                           Enters subinterface configuration mode for the PVP.
          Example:
          RP/0/0/CPU0:router(config-if)# pvp 10
Step 4    cell-packing cells timer                                          Sets the maximum number of cells allowed per packet, and
                                                                            specifies a maximum cell packing timeout (MCPT) timer to
                                                                            use for cell packing.
          Example:
          RP/0/0/CPU0:router(config-atm-l2transport-pvp)#                    •      Replace cells with the maximum number of cells to use
          cell-packing 5 2                                                          per packet. Range is from 2 through 86.
                                                                             •      Replace timer with the number that indicates the
                                                                                    appropriate MCPT timer to use for cell packing. Can be
                                                                                    1, 2, or 3. You can configure up to three different MCPT
                                                                                    values for a single main interface.
What to do Next
                           •   To configure a point-to-point pseudowire XConnect on the AC you just created, see the
                               “Implementing MPLS Layer 2 VPNs” module of Cisco IOS XR Multiprotocol Label Switching
                               Configuration Guide.
Restrictions
                         For Layer 2 VPN AC configurations, Vc-classes can be applied to PVCs only. Vc-classes are not
                         supported on Layer 2 port mode interfaces or PVPs.
SUMMARY STEPS
                          1.   configure
                          2.   vc-class atm name
                          3.   encapsulation {aal5mux ipv4 | aal5nlpid | aal5snap}
                          4.   oam ais-rdi [down-count [up-count]]
                          5.   oam retry [up-count [down-count [retry-frequency]]]
                          6.   oam-pvc manage seconds
                          7.   shape [cbr peak_output_rate | ubr peak_output_rate | vbr-nrt peak_output_rate
                               sustained_output_rate burst_size| vbr-rt peak_output_rate sustained_output_rate burst_size]
                          8.   end
                               or
                               commit
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    vc-class atm name                                                 Creates a vc-class for an ATM interface and enters vc-class
                                                                            configuration mode.
          Example:
          RP/0/0/CPU0:router (config)# vc-class atm
          class1
What to do Next
                         Attach the vc-class to an ATM main interface, subinterface, or PVC.
                          •   To attach a vc-class to an ATM main interface, see the “Attaching a Vc-Class to a Point-to-Point
                              ATM Main Interface” section on page -36.
                          •   To attach a vc-class to an ATM subinterface, see the “Attaching a Vc-Class to a Point-to-Point ATM
                              Subinterface” section on page -38.
                          •   To attach a vc-class to an ATM PVC, see the “Attaching a Vc-Class to a PVC on an ATM
                              Subinterface” section on page -39.
Restrictions
                         Vc-classes are not applicable to Layer 2 port mode ACs. For Layer 2 VPN configurations, Vc-classes
                         are applicable to the PVC only.
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance point-to-point
                          3.   class-int vc-class-name
                          4.   end
                               or
                               commit
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance point-to-point                        Enters ATM interface configuration mode.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1 point-to-point
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance.subinterface point-to-point
                          3.   class-int vc-class-name
                          4.   end
                               or
                               commit
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface                       Enters ATM subinterface configuration mode.
          point-to-point
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1.10 point-to-point
Step 3    class-int vc-class-name                                   Assigns the vc-class to an ATM subinterface. Replace the
                                                                    vc-class-name argument with the name of the vc-class you
                                                                    configured in the “Creating and Configuring a VC-Class”
          Example:
          RP/0/0/CPU0:router (config-subif)# class-int
                                                                    section on page -34.
          classA
Step 4    end                                                       Saves configuration changes.
          or
                                                                     •   When you issue the end command, the system prompts
          commit                                                         you to commit changes:
                                                                         Uncommitted changes found, commit them before
          Example:                                                       exiting(yes/no/cancel)?
          RP/0/0/CPU0:router (config-subif)# end                         [cancel]:
          or
                                                                          – Entering yes saves configuration changes to the
          RP/0/0/CPU0:router(config-subif)# commit                            running configuration file, exits the configuration
                                                                              session, and returns the router to EXEC mode.
                                                                          – Entering no exits the configuration session and
                                                                              returns the router to EXEC mode without
                                                                              committing the configuration changes.
                                                                          – Entering cancel leaves the router in the current
                                                                              configuration session without exiting or
                                                                              committing the configuration changes.
                                                                     •   Use the commit command to save the configuration
                                                                         changes to the running configuration file and remain
                                                                         within the configuration session.
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance[.subinterface] [point-to-point | l2transport]
                          3.   pvc vpi/vci
                          4.   class vc vc-class-name
                          5.   end
                               or
                               commit
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance.subinterface                               Enters subinterface configuration mode and creates the
          [point-to-point | l2transport]                                    ATM subinterface if it does not already exist.
                                                                            Use the point-to-point keyword if you are attaching the
          Example:                                                          vc-class to a point-to-point subinterface. Use the
          RP/0/0/CPU0:router (config)# interface atm                        l2transport keyword if you are attaching the vc-class to a
          0/6/0/1.10
                                                                            Layer 2 transport subinterface.
                                                                            Note    For more information on creating and configuring
                                                                                    ATM subinterfaces, see the “Creating a
                                                                                    Point-to-Point ATM Subinterface with a PVC”
                                                                                    section on page 11.
Step 3    pvc vpi/vci                                                       Enters ATM PVC configuration mode and creates the PVC
                                                                            if it does not already exist.
          Example:                                                          Note    For more information on creating and configuring
          RP/0/0/CPU0:router (config-if)# pvc 5/50                                  PVCs on ATM subinterfaces, see the “Creating a
                                                                                    Point-to-Point ATM Subinterface with a PVC”
                                                                                    section on page 11.
                Note     For ILMI, a PVC is configured directly on the ATM main interface. Subinterface configuration is not
                         necessary for ATM interfaces that are used for ILMI.
Prerequisites
                         Bring up the ATM interface and remove the shutdown configuration, as described in the “Bringing Up
                         an ATM Interface” section on page 6.
Restrictions
                          •    The configuration on both ends of the ATM ILMI connection must match for the interface to be
                               active.
                          •    ILMI configuration is not supported on Layer 2 port mode ACs.
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance
                          3.   atm address-registration
                          4.   atm ilmi-keepalive [act-poll-freq frequency] [retries count] [inact-poll-freq frequency]
                          5.   pvc vpi/vci ilmi
                          6.   end
                               or
                               commit
                          7.   exit
                          8.   exit
                          9.   show atm ilmi-status [atm instance]
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance                                            Enters ATM interface configuration mode.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1
Step 3    atm address-registration                                          (Optional) Enables the router to engage in address
                                                                            registration and callback functions with the Interim Local
                                                                            Management Interface (ILMI).
          Example:
          RP/0/0/CPU0:router (config-if)# atm
          address-registration
Step 4    atm ilmi-keepalive [act-poll-freq frequency]                      (Optional) Enables ILMI keepalives on an ATM interface.
          [retries count] [inact-poll-freq frequency]
          Example:
          RP/0/0/CPU0:router (config-if)# atm
          ilmi-keepalive
          Example:
          RP/0/0/CPU0:router (config)# exit
Step 9    show atm ilmi-status [atm instance]                       (Optional) Verifies the ILMI configuration for the specified
                                                                    interface.
          Example:
          RP/0/0/CPU0:router (config)# show atm
          ilmi-status atm 0/6/0/1
SUMMARY STEPS
                          1.   configure
                          2.   interface atm instance
DETAILED STEPS
          Example:
          RP/0/0/CPU0:router# configure
Step 2    interface atm instance                                            Enters ATM interface configuration mode.
          Example:
          RP/0/0/CPU0:router (config)# interface atm
          0/6/0/1
Step 3    atm ilmi-config disable                                           (Optional) Disables ILMI on the ATM interface.
                                                                            To re-enable ILMI on an ATM interface, use the no atm
          Example:                                                          ilmi-config disable form of this command.
          RP/0/0/CPU0:router (config-if)# atm ilmi-config
          disable
Step 4    end                                                               Saves configuration changes.
          or
                                                                             •      When you issue the end command, the system prompts
          commit                                                                    you to commit changes:
                                                                                    Uncommitted changes found, commit them before
          Example:                                                                  exiting(yes/no/cancel)?
          RP/0/0/CPU0:router (config-if)# end                                       [cancel]:
          or
                                                                                     – Entering yes saves configuration changes to the
          RP/0/0/CPU0:router(config-if)# commit                                         running configuration file, exits the configuration
                                                                                        session, and returns the router to EXEC mode.
                                                                                     – Entering no exits the configuration session and
                                                                                        returns the router to EXEC mode without
                                                                                        committing the configuration changes.
                                                                                     – Entering cancel leaves the router in the current
                                                                                        configuration session without exiting or
                                                                                        committing the configuration changes.
                                                                             •      Use the commit command to save the configuration
                                                                                    changes to the running configuration file and remain
                                                                                    within the configuration session.
          Example:
          RP/0/0/CPU0:router (config)# exit
Step 7    show atm ilmi-status [atm instance]                               (Optional) Verifies the ILMI configuration for the specified
                                                                            interface.
          Example:
          RP/0/0/CPU0:router (config)# show atm
          ilmi-status atm 0/6/0/1
                       Interface                                          :   ATM0/2/0/2
                       AAL Enabled                                        :   AAL5
                       Max-VP                                             :   254
                       Max-VC                                             :   2048
                       Configured VP-Tunnels                              :   0
                       Configured PVCs                                    :   4
                       VP-Tunnels in Down State                           :   0
                       PVCs in Down State                                 :   4
                         The following example shows how to create and configure an ATM subinterface and PVC on one
                         endpoint of a a vp-tunnel, and then verify connectivity through that vp-tunnel:
                         RP/0/0/CPU0:router # configure
                         RP/0/0/CPU0:router(config)# interface atm 0/6/0/0.16 point-to-point
                         RP/0/0/CPU0:router(config-subif)# pvc 10/100
                         RP/0/0/CPU0:router (config-atm-vc)# commit
                         RP/0/0/CPU0:router (config-subif)# exit
                         RP/0/0/CPU0:router (config)# exit
                         RP/0/0/CPU0:router # ping atm interface atm 0/6/0/0.16 10/100
                        The following example shows how to create and configure an AC on a Layer 2 subinterface with a PVC:
                        RP/0/0/CPU0:router# configure
                        RP/0/0/CPU0:router(config)# interface atm 0/1/0/0.230 l2transport
                        RP/0/0/CPU0:router(config-if)# pvc 15/230
                        RP/0/0/CPU0:router(config-atm-l2transport-pvc)# encapsulation aal0
                        RP/0/0/CPU0:router(config-atm-l2transport-pvc)# cell-packing 5 2
                        RP/0/0/CPU0:router(config-atm-l2transport-pvc)# shape cbr 622000
                        RP/0/0/CPU0:router(config-atm-l2transport-pvc)# commit
                        RP/0/0/CPU0:router(config-atm-l2transport-pvc)#
                        RP/0/0/CPU0:router(config-if)# exit
                        RP/0/0/CPU0:router(config)# exit
                        RP/0/0/CPU0:router# show atm pvc
                        The following example shows how to create and configure an AC on an ATM subinterface with a PVP:
                        RP/0/0/CPU0:router# configure
                        RP/0/0/CPU0:router(config)# interface atm 0/6/0/1.10 l2transport
                        RP/0/0/CPU0:router(config-if)# pvp 100
                        RP/0/0/CPU0:router(config-atm-l2transport-pvp)# cell-packing 5 2
                        RP/0/0/CPU0:router(config-atm-l2transport-pvp)# shape ubr 155000
                        RP/0/0/CPU0:router(config-atm-l2transport-pvp)# commit
                        The following example shows how to attach a vc-class to an ATM main interface:
                        RP/0/0/CPU0:router # configure
                        RP/0/0/CPU0:router(config)# interface ATM0/2/0/0.1 point-to-point
                        RP/0/0/CPU0:router (config-if)# class-int atm-class-1
                        RP/0/0/CPU0:router (config-if)# commit
                        The following example shows how to display information about a specific ATM vc-class:
                        RP/0/0/CPU0:router # show atm vc-class atm-class-1
                        ATM vc-class atm-class-1
                           encapsulation              -   aal5snap
                           shape                      -   cbr 100000
                           oam ais-rdi                -   not configured
                           oam retry                  -   not configured
                           oam-pvc                    -   manage 300
                        The following example shows how to display configuration information for the parameters on a virtual
                        circuit (VC) class that is associated with a particular PVC:
                        RP/0/0/CPU0:router # show atm class-link 10/100
Additional References
                            The following sections provide references related to implementing ATM for Cisco IOS XR software.
Related Documents
Related Topic                                                     Document Title
ATM commands: complete command syntax,                            Cisco IOS XR Interface and Hardware Command Reference
command modes, command history, defaults, usage
guidelines, and examples
Standards
Standards                                                         Title
No new or modified standards are supported by this       —
feature, and support for existing standards has not been
modified by this feature.
MIBs
RFCs
RFCs                                                   Title
RFC 1483                                               Multiprotocol Encapsulation over ATM Adaptation Layer 5
RFC 1577                                               Classical IP and ARP over ATM.
RFC 2225                                               Classical IP and ARP over ATM
RFC 2255                                               The LDAP URL Format
RFC 2684                                               Multiprotocol Encapsulation over ATM Adaptation Layer 5.
RFC 4385                                               Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use
                                                       over an MPLS PSN
RFC 4717                                               Encapsulation Methods for Transport of Asynchronous Transfer
                                                       Mode (ATM) over MPLS Networks
RFC 4816                                               Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous
                                                       Transfer Mode (ATM) Transparent Cell Transport Service
Technical Assistance
Description                                            Link
The Cisco Technical Support website contains           http://www.cisco.com/techsupport
thousands of pages of searchable technical content,
including links to products, technologies, solutions,
technical tips, and tools. Registered Cisco.com users
can log in from this page to access even more content.