4.9. Configuring a VLL Service with CLI

This section provides the information required to configure Virtual Leased Line (VLL) services using the command line interface.

Topics in this section include:

4.10. Common Configuration Tasks

The following list provides a brief overview of the tasks that must be performed to configure a VLL service.

  1. Associate the service with a customer ID.
  2. Define SAP parameters.
    1. Optional—select egress and ingress QoS policies (configured in the config>qos context)
    2. Optional—select ingress IP filter policies (for Epipes and Ipipes only)
  3. Define spoke SDP parameters.
    1. Optional—select egress and ingress vc label parameters
    2. Optional—explicitly assign spoke SDP endpoints for pseudowire (PW) redundancy applications
  4. Enable the service.

4.11. Configuring VLL Components

This section provides configuration examples for components of VLL services. Each component includes some or all of the following: introductory information, CLI syntax, a specific CLI example, and an example of the CLI display output. Included are the following VLL components:

4.11.1. Creating an Apipe Service

This section describes how to create an Apipe service. Additional topics in this section include:

Use the following CLI syntax to create an Apipe service.

CLI Syntax:
config>service# apipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {atm-vcc | atm-vpc | atm-cell}] [vc-switching]
description description-string
service-mtu octets
no shutdown

PE router 1 (A:ALU-41):

Example:
A:ALU-41>config>service# apipe 5 customer 1 create
A:ALU-41config>service>apipe# description “apipe test”
A:ALU-41config>service>apipe# service-mtu 1400
A:ALU-41config>service>apipe# no shutdown

PE router 2 (A:ALU-42):

Example:
A:ALU-42>config>service# apipe 5 customer 1 create
A:ALU-42>config>service>apipe# description “apipe test”
A:ALU-42>config>service>apipe# service-mtu 1400
A:ALU-42>config>service>apipe# no shutdown

The following example shows the Apipe service creation output.

PE Router 1 (ALU-41):

A:ALU-41>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            description "apipe test"
            service-mtu 1400
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#

PE Router 2 (ALU-42):

A:ALU-42>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            description "apipe test"
            service-mtu 1400
            no shutdown
        exit
-------------------------------------
A:ALU-42>config>service# 

4.11.1.1. Configuring Apipe SAP Parameters

Use the following CLI syntax to configure Apipe SAP parameters. For ingress and egress configuration information, see Configuring Ingress and Egress SAP Parameters.

CLI Syntax:
config>service# apipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {atm-vcc | atm-vpc | atm-cell}] [vc-switching]
sap sap-id [create]
accounting-policy acct-policy-id
atm
egress
traffic-desc traffic-desc-profile-id
ingress
traffic-desc traffic-desc-profile-id
oam
alarm-cells
collect-stats
description description-string
egress
qos policy-id
ingress
qos policy-id
no shutdown
Example:
A:ALU-41>config>service# apipe 5
A:ALU-41>config>service>apipe# sap 1/1/1.1:0/32 create
A:ALU-41>config>service>apipe>sap# ingress
A:ALU-41>config>service>apipe>sap>ingress# qos 102
A:ALU-41>config>service>apipe>sap>ingress# exit
A:ALU-41>config>service>apipe>sap# egress
A:ALU-41>config>service>apipe>sap>egress# qos 103
A:ALU-41>config>service>apipe>sap>egress# exit
A:ALU-41>config>service>apipe>sap# no shutdown
A:ALU-41>config>service>apipe>sap# exit

The following example shows Apipe SAP configuration output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            description "apipe test"
            service-mtu 1400
            sap 1/1/1.1:0/32 create
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            no shutdown
        exit
-------------------------------------

To configure a basic local Apipe service (SAP-to-SAP), enter the sap sap-id command twice with different port IDs in the same service configuration.

The following example shows an ATM SAP-to-SAP configuration:

A:ALU-4>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            description "ATM sap2sap"
            service-mtu 1514
            sap 1/1/1.1:0/32
            sap 1/2/1.1:0/100
            no shutdown
        exit
-------------------------------------

The following example shows an Apipe SAP configuration for a virtual trunk service:

A:ALU-4>config>service# info
-------------------------------------
...
        apipe 5 customer 1 vc-type atm-cell create
            description "port VT apipe"
            service-mtu 1500
            sap 1/1/10 create
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
           exit
            no shutdown
        exit
-------------------------------------

4.11.1.2. Configuring Apipe SDP Bindings

Use the following CLI syntax to create a spoke SDP binding with an Apipe service (for distributed service). For SDP configuration information, see Configuring SDPs.

CLI Syntax:
config>service# apipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {atm-vcc | atm-vpc | atm-cell}] [vc-switching]
spoke-sdp sdp-id:vc-id [create]
cell-concatenation
clp-change
max-cells cell-count
max-delay delay-time
egress
vc-label egress-vc-label
ingress
vc-label ingress-vc-label
no shutdown
Example:
A:ALU-41>config>service# apipe 5
A:ALU-41>config>service>apipe# spoke-sdp 1:5 create
A:ALU-41>config>service>apipe>spoke-sdp# no shutdown
A:ALU-41>config>service>apipe>spoke-sdp# exit

The following example shows the Apipe spoke SDP configuration output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            description "apipe test"
            service-mtu 1400
            sap 1/1/1.1:0/32 create
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            spoke-sdp 1:5 create
            exit
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#

4.11.1.3. Configuring Apipe SAP Aggregation Groups

Use the following CLI syntax to configure the parameters for an Apipe SAP aggregation group. The vc-type parameter must be set to atm-vcc. For ingress and egress configuration information, see Configuring Ingress and Egress SAP Parameters.

CLI Syntax:
config>service# apipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {atm-vcc | atm-vpc | atm-cell}] [vc-switching]
sap-aggregation-group group-id [create]
accounting-policy acct-policy-id
collect-stats
description description-string
egress
qos policy-id
ingress
qos policy-id
no shutdown
no shutdown
Example:
A-ALU-1>config>service# apipe 3 customer 1 vc-type atm-vcc create
A-ALU-1>config>service>apipe# sap-aggregation-group GroupName1 create
A-ALU-1>config>service>apipe>sap-aggregation-group# ingress
A-ALU-1>config>service>apipe>sap-aggregation-group>ingress# qos 102
A-ALU-1>config>service>apipe>sap-aggregation-group>ingress# exit
A-ALU-1>config>service>apipe>sap-aggregation-group# egress
A-ALU-1>config>service>apipe>sap-aggregation-group# egress qos 103
A-ALU-1>config>service>apipe>sap-aggregation-group>egress# exit
A-ALU-1>config>service>apipe>sap-aggregation-group# no shutdown
A-ALU-1>config>service>apipe>sap-aggregation-group# exit
A-ALU-1>config>service>apipe#

The following example shows an Apipe SAP aggregation group configuration output.

A-ALU-1>config>service# info 
------------------------------------- 
... 
        apipe 3 customer 1 vc-type atm-vcc create 
            description "SAP aggregation group 1" 
            sap-aggregation-group GroupName1 create 
               ingress 
                   qos 102 
               exit 
               egress 
                   qos 103 
               exit 
            exit 
            no shutdown 
        exit 
... 
------------------------------------- 

4.11.1.4. Configuring Apipe SAPs as Aggregation Group Members

Use the following CLI syntax to configure an Apipe SAP as a member of a SAP aggregation group. To add a SAP as a member of a SAP aggregation group, enter the sap-aggregation-group group-id command after the sap sap-id command. A SAP aggregation group can have up to 16 SAP members.

ATM attributes for aggregation group members can also be configured, including:

  1. vcid-translation
  2. traffic descriptor profiles for egress
    Note:

    You cannot apply ATM QoS traffic descriptor profiles on ingress to a SAP in a SAP aggregation group; the profile is set to the default (1). Attempting to change the ingress traffic descriptor will cause an error message to be displayed.

  3. OAM alarm notifications

For ingress and egress configuration information, see Configuring Apipe SAP Parameters.

CLI Syntax:
config>service# apipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {atm-vcc | atm-vpc | atm-cell}] [vc-switching]
sap sap-id sap-aggregation-group group-id
atm
vcid-translation vpi/vci
egress
traffic-desc traffic-desc-profile-id
ingress
traffic-desc traffic-desc-profile-id
oam
alarm-cells
description description-string
no shutdown
no shutdown
Example:
A-ALU-1>config>service# apipe 3 customer 1 create
A-ALU-1>config>service>apipe# sap 1/2/2.1:10/10 sap-aggregation-group GroupName1
A-ALU-1>config>service>apipe>sap# exit
A-ALU-1>config>service>apipe# sap 1/2/2.1:20/20 sap-aggregation-group GroupName1
A-ALU-1>config>service>apipe>sap# exit
A-ALU-1>config>service>apipe# sap 1/2/2.1:30/30 sap-aggregation-group GroupName1
A-ALU-1>config>service>apipe>sap# exit
A-ALU-1>config>service>apipe#

The following example shows the output for an Apipe service with a SAP aggregation group containing three SAPs as aggregation group members.

A:ALU-41>config>service# info 
------------------------------------- 
... 
        apipe 3 customer 1 create
           sap-aggregation-group "GroupName1" create
           exit
           sap 1/2/2.1:10/10 sap-aggregation-group "GroupName1" create
           exit
           sap 1/2/2.1:20/20 sap-aggregation-group "GroupName1" create
           exit
           sap 1/2/2.1:30/30 sap-aggregation-group "GroupName1" create
           exit
        exit
... 
------------------------------------- 

4.11.2. Creating a Cpipe Service

This section describes how to create a Cpipe service. Additional topics in this section include:

Use the following CLI syntax to create a Cpipe service.

CLI Syntax:
config>service# cpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {satop-e1 | satop-t1 | satop-e3 | satop-t3 | cesopsn | cesopsn-cas}] [vc-switching]
description description-string
service-mtu octets
no shutdown
Example:
config>service# cpipe 234 customer 123 create vc-type cesopsn
config>service>cpipe# description “cpipe test”
config>service>cpipe# service-mtu 1400
config>service>cpipe# no shutdown
config>service>cpipe#

The following example shows the Cpipe service creation output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
     cpipe 234 customer 123 create
            description "cpipe test"
            service-mtu 1400
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#

4.11.2.1. Configuring Cpipe SAP Parameters

Use the following CLI syntax to configure Cpipe SAP parameters. For ingress and egress configuration information, see Configuring Ingress and Egress SAP Parameters.

CLI Syntax:
config>service# cpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {satop-e1 | satop-t1 | satop-e3 | satop-t3 | cesopsn | cesopsn-cas}] [vc-switching]
sap sap-id [create]
cem
[no] packet
asym-delay-control [samples {ksamples}] [min-repeat minutes][threshold-repeat uSecs]
jitter-buffer value | payload-size size
payload-size size
[no] report-alarm [stray] [malformed] [pktloss]
   [overrun] [underrun] [rpktloss]
   [rfault] [rrdi]
[no] rtp-header
[no] collect-stats
description description-string
no description
egress
qos policy-id
no qos
ingress
qos policy-id
no qos
[no] shutdown
Example:
A:ALU-41>config>service# cpipe 5 cesopsn
A:ALU-41>config>service>cpipe# sap 1/1/1.1 create
A:ALU-41>config>service>cpipe>sap# ingress
A:ALU-41>config>service>cpipe>sap>ingress# qos 102
A:ALU-41>config>service>cpipe>sap>ingress# exit
A:ALU-41>config>service>cpipe>sap# egress
A:ALU-41>config>service>cpipe>sap>egress# qos 103
A:ALU-41>config>service>cpipe>sap>egress# exit
A:ALU-41>config>service>cpipe>sap# no shutdown
A:ALU-41>config>service>cpipe>sap# exit
A:ALU-41>config>service>cpipe#

The following example shows the Cpipe SAP configuration output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
        cpipe 5 customer 1 create
            description "cpipe test"
            service-mtu 1400
            sap 1/1/1.1 create
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            no shutdown
        exit
...
-------------------------------------

To configure a basic local Cpipe service (SAP-to-SAP), enter the sap sap-id command twice with different port IDs in the same service configuration.

The following example shows a TDM SAP-to-SAP configuration:

A:ALU-41>config>service# info
-------------------------------------
...
        cpipe 5 customer 1 create
            description "TDM sap2sap"
            service-mtu 1400
            sap 1/1/1.1
            sap 1/2/1.1
            no shutdown
        exit
...
-------------------------------------

Use the following CLI syntax to configure a Cpipe SAP used by a Surveillance, Control, and Data Acquisition Support (SCADA) bridge. In this instance, the sap-id variable is in the format slot/mda/bridge-id.branch-id, where bridge-id represents an existing bridge number with a value of 1 to 16 and branch-id represents an existing branch number with a value of 1 to 32. Refer to the 7705 SAR Interface Configuration Guide, “Configuration Command Reference”, for information on how to configure bridges and branches for a SCADA application.

CLI Syntax:
config>service# cpipe service-id [customer customer-id] [create] vc-type cesopsn
sap sap-id [create]
description description-string
no description
[no] shutdown
Example:
A:ALU-41>config>service# cpipe 8 customer 1 create vc-type cesopsn
A:ALU-41>config>service>cpipe# sap 1/5/16.10 create
A:ALU-41>config>service>cpipe>sap# description “sap branch 10”
A:ALU-41>config>service>cpipe>sap# no shutdown
A:ALU-41>config>service>cpipe>sap# exit
A:ALU-41>config>service>cpipe#

The following example shows a SCADA bridge Cpipe SAP configuration:

A:ALU-41>config>service# info
-------------------------------------
...
        cpipe 8 customer 1 vc-type cesopsn
            sap 1/5/16.10
            description "sap branch 10"
            no shutdown
        exit

4.11.2.2. Configuring Cpipe SDP Bindings

Use the following CLI syntax to create a spoke SDP binding with a Cpipe service. For SDP configuration information, see Configuring SDPs.

CLI Syntax:
config>service# cpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {satop-e1 | satop-t1 | satop-e3 | satop-t3 | cesopsn | cesopsn-cas}] [vc-switching]
spoke-sdp sdp-id:vc-id [create]
egress
vc-label egress-vc-label
ingress
vc-label ingress-vc-label
[no] shutdown
Example:
A:ALU-41>config>service# cpipe 5
A:ALU-41>config>service>cpipe# spoke-sdp 1:5 create
A:ALU-41>config>service>cpipe>spoke-sdp# no shutdown
A:ALU-41>config>service>cpipe>spoke-sdp# exit

The following example shows the Cpipe spoke SDP configuration output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
        cpipe 5 customer 1 create
            description "cpipe test"
            service-mtu 1400
            sap 1/1/1.1 create
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            spoke-sdp 1:5 create
            exit
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#

4.11.3. Creating an Epipe Service

This section describes how to create an Epipe service. Additional topics in this section include:

Use the following CLI syntax to create an Epipe service.

CLI Syntax:
config>service# epipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-switching]
description description-string
no shutdown
Example:
config>service# epipe 500 customer 5 create
config>service>epipe$ description “Local epipe service”
config>service>epipe# no shutdown

The following example shows the Epipe service creation output.

ALU-1>config>service# info
-------------------------------------------
        epipe 500 customer 5 vpn 500 create
            description "Local epipe service"
            no shutdown
        exit
-------------------------------------------

4.11.3.1. Configuring Epipe SAP Parameters

The 7705 SAR supports distributed Epipe service and local (SAP-to-SAP) Epipe service. A distributed Epipe consists of two SAPs on different nodes. A local Epipe consists of both SAPs on the same 7705 SAR. To configure a distributed Epipe service, you must configure service entities on the originating and far-end nodes.

Use the following CLI syntax to create distributed Epipe SAPs. For ingress and egress configuration information, see Configuring Ingress and Egress SAP Parameters. For information on configuring ETH-CFM parameters on an Epipe SAP, see ETH-CFM (802.1ag and Y.1731) Tasks.

CLI Syntax:
config>service# epipe service-id [customer customer-id] [create] [vc-switching]
sap sap-id [create]
accounting-policy policy-id
collect-stats
description description-string
no shutdown
egress
qos policy-id
eth-cfm
ingress
filter [ip ip-filter-id]
qos policy-id
Example:
ALU-1>epipe 5500 customer 5 create
config>service>epipe$ description "Distributed epipe service to east coast"
config>service>epipe# sap 1/1/3:21 create
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# filter ip 1
config>service>epipe>sap>ingress# qos 555
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# egress
config>service>epipe>sap>egress# qos 627
config>service>epipe>sap>egress# exit
config>service>epipe>sap# no shutdown
config>service>epipe>sap# exit
config>service>epipe#
ALU-2>config>service# epipe 5500 customer 5 create
config>service>epipe$ description "Distributed epipe service to west coast"
config>service>epipe# sap 1/1/4:550 create
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# qos 654
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# egress
config>service>epipe>sap>egress# qos 432
config>service>epipe>sap>egress# exit
config>service>epipe>sap# no shutdown
config>service>epipe#

The following example shows the SAP configuration output for ALU-1 and ALU-2.

ALU-1>config>service# info
----------------------------------------------
...
        epipe 5500 customer 5 vpn 5500 create
            description "Distributed epipe service to east coast"
            sap 1/1/3:21 create
                ingress
                    filter ip 1
                    qos 555
                exit
                egress
                    qos 627
                exit
            exit
        exit
...
----------------------------------------------
ALU-1>config>service#
 
ALU-2>config>service# info
----------------------------------------------
...
        epipe 5500 customer 5 vpn 5500 create
            description "Distributed epipe service to west coast"
            sap 1/1/4:550 create
                ingress
                    qos 654
               exit
               egress
                    qos 432
               exit
            exit
        exit
...
----------------------------------------------
ALU-2>config>service#

To configure a basic local Epipe service (SAP-to-SAP), enter the sap sap-id command twice with different port IDs in the same service configuration.

The following example shows an Ethernet SAP-to-SAP configuration:

A:ALU-4>config>service# info
-------------------------------------
...
        epipe 2 customer 1 create
            description "Ethernet sap2sap"
               sap 1/1/1:1000
               sap 1/2/1:50
            no shutdown
        exit
...
-------------------------------------

4.11.3.2. Configuring Epipe with ATM SAP

Use the following CLI syntax to configure an Epipe with ATM SAP. An OC3 clear channel ATM path is configured and then the Epipe SAP is configured.

CLI Syntax:
configure port port-id
description description
sonet-sdh
path
atm
cell-format uni
mtu mtu
no shutdown
no shutdown

The following example shows an OC3 clear channel ATM path configuration and output.

Example:
*A:Sar8 Dut-B# configure port 1/2/3
config>port# description “1/OC03/KAN”
config>port# sonet-sdh
config>port>sonet-sdh# path
config>port>sonet-sdh>path# atm
config>port>sonet-sdh>path>atm# cell-format uni
config>port>sonet-sdh>path>atm# exit
config>port>sonet-sdh>path# mtu 2090
config>port>sonet-sdh>path# no shutdown
config>port>sonet-sdh>path# exit
config>port>sonet-sdh# exit
*A:Sar8 Dut-B>config>port# info
----------------------------------------------
        description "1/OC03/KAN"
        sonet-sdh
            path
                atm
                    cell-format uni
                mtu 2090
                exit
                no shutdown
            exit
        exit
        no shutdown
CLI Syntax:
config>service# epipe service-id [customer customer-id] create
description description-string
sap sap-id create
description description-string
egress
qos policy-id
no shutdown
ingress
qos policy-id
service-mtu octets
service-name service-name
spoke-sdp sdp-id:vc-id create
no shutdown
no shutdown

The following example shows an Epipe SAP configuration and output.

Example:
*A:Sar8 Dut-B# configure service epipe 202165 customer 1 create
config>service>epipe$ description "00/ARDU/902/863/2949"
config>service>epipe$ sap 1/2/3:0/49 create
config>service>epipe>sap$ description "00/ARDU/902/863/2949"
config>service>epipe>sap$ egress
config>service>epipe>sap>egress$ qos 1421
config>service>epipe>sap>egress$ exit
config>service>epipe>sap$ no shutdown
config>service>epipe>sap$ ingress
config>service>epipe>sap>ingress$ qos 1421
config>service>epipe>sap>ingress$ exit
config>service>epipe>sap$ exit
config>service>epipe$ service-mtu 1622
config>service>epipe$ service-name "EPIPE 202165"
config>service>epipe$ spoke-sdp 3080:202165 create
config>service>epipe>spoke-sdp$ no shutdown
config>service>epipe>spoke-sdp$ exit
config>service>epipe$ no shutdown
config>service>epipe$ exit
*A:Sar8 Dut-B>config>service>epipe$ info
----------------------------------------------
description "00/ARDU/902/863/2949"
            service-mtu 1622
            service-name "EPIPE 202165"
            sap 1/2/3:0/49 create
                description "00/ARDU/902/863/2949"
                egress
                    qos 1421
                exit
                ingress
                    qos 1421
                exit     
                no shutdown
            exit
            spoke-sdp 3080:202165 create
                description "00/ARDU/902/863/2949"
                no shutdown
            exit
            no shutdown
        exit

4.11.3.3. Configuring Epipe SAP MEF 8 Parameters

MEF 8 allows TDM services to be encapsulated across Epipes. To configure MEF 8, define one TDM SAP and one Ethernet SAP on the Epipe; see Configuring Epipe SAP Parameters for information on configuring an Ethernet SAP. The TDM SAP for the Epipe must include a local and remote ECID and a far-end destination MAC address. The TDM port’s MAC address is used as the source MAC address for the circuit.

TDM can also be encapsulated into Ethernet, which is then encapsulated in MPLS (or GRE) by configuring an Epipe with a TDM SAP and a spoke SDP. See Configuring SDPs for information on configuring a spoke SDP. The TDM SAP configured in the Epipe must include a local and remote ECID and a far-end destination MAC address. The TDM port’s MAC address is used as the source MAC address for the circuit.

Use the following CLI syntax to configure MEF 8 parameters:

CLI Syntax:
config>service# epipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-switching]
description description-string
sap sap-id [create]
accounting-policy policy-id
cem
packet
jitter-buffer value | payload-size size
payload-size size
local-ecid value
no local-ecid
remote-ecid value
no remote-ecid
remote-mac ieee-mac-addr
no remote-mac
report-alarm [stray] [malformed] [pktloss] [overrun] [underrun] [rpktloss] [rfault] [rrdi]
description description-string

The following example shows a TDM SAP-to-Ethernet SAP MEF 8 configuration and output.

Example:
ALU-1>epipe 1
config>service>epipe# description “Test Epipe for service ID 1”
config>service>epipe# sap 1/2/4:1 create
config>service>epipe>sap# description “test SAP for service ID 1”
config>service>epipe>sap# exit
config>service>epipe# sap 1/1/1.1 create
config>service>epipe>sap# description “test SAP2 for service ID 1”
config>service>epipe>sap# cem
config>service>epipe>sap>cem# report alarm rpktloss rfault rrdi
config>service>epipe>sap>cem# local-ecid 1
config>service>epipe>sap>cem# remote-ecid 1
config>service>epipe>sap>cem# remote-mac 10:00:50:00:00:02
config>service>epipe>sap>cem# exit
config>service>epipe>sap# exit
config>service>epipe# no shutdown
*A:7705:Dut-A>config>service>epipe# info 
----------------------------------------------
            description "Default epipe description for service id 1"
            sap 1/2/4:1 create
                description "Test SAP for service ID 1"
            exit
            sap 1/1/1.1 create
                description "Test SAP2 for service ID 1"
                cem
                    report-alarm rpktloss rfault rrdi 
                    local-ecid 1
                    remote-ecid 1
                    remote-mac 10:00:50:00:00:02
                exit
            exit
            no shutdown
----------------------------------------------
*A:7705:Dut-A>config>service>epipe# back 

The following example shows a TDM SAP-to-spoke SDP MEF 8 configuration and output. See Configuring SDPs for more information about SDPs.

Example:
config>service>epipe 2
config>service>epipe# description “Test Epipe for service ID 2”
config>service>epipe# sap 1/1/1.2 create
config>service>epipe>sap# description “test SAP for service ID 2”
config>service>epipe>sap# exit
config>service>epipe# exit
config>service# sdp 2 mpls create
config>service>sdp# description “MPLS-10.10.10.104”
config>service>sdp# far-end “10.10.10.104”
config>service>sdp# no shutdown
config>service>sdp# exit
config service# epipe 2 sap
config>service>epipe>sap# cem
config>service>epipe>sap>cem# report alarm rpktloss rfault rrdi
config>service>epipe>sap>cem# local-ecid 2
config>service>epipe>sap>cem# remote-ecid 2
config>service>epipe>sap>cem# remote-mac 10:00:50:00:00:02
config>service>epipe>sap>cem# exit
config>service>epipe>sap# exit
config>service>epipe# no shutdown
*A:7705:Dut-A>config>service# epipe 2 
*A:7705:Dut-A>config>service>epipe# info 
----------------------------------------------
            description "Default epipe description for service id 2"
            sap 1/1/1.2 create
                description "Default sap description for service id 2"
                cem
                    report-alarm rpktloss rfault rrdi 
                    local-ecid 2
                    remote-ecid 2
                    remote-mac 10:00:50:00:00:02
                exit
            exit
            spoke-sdp 2:2 create
            exit
            no shutdown
----------------------------------------------
*A:7705:Dut-A>config>service>epipe#

4.11.3.4. Configuring Epipe SAP Microwave Link Parameters for Interworking with TDM2Ethernet

In a Microwave Awareness environment, a mixed microwave link scenario may exist where an access link site has an MPR-e radio connected to a 7705 SAR-8 or 7705 SAR-18 as a standalone network element as well as an MPR-e radio connected to a 9500 MSS as an indoor unit, as shown in Figure 77.

When TDM2Ethernet transport is required, the 9500 MSS packetizes the TDM2Ethernet stream using a MEF 8 frame format; the 7705 SAR-8 or 7705 SAR-18 acts as the MEF 8 endpoint. From a packet flow perspective, the TDM2Ethernet MEF 8 stream is a VLAN flow that can be handled by a VLAN SAP into an Epipe service going into the 7705 SAR-8 or 7705 SAR-18. To optimize the microwave bandwidth for the TDM2Ethernet MEF 8 transport, the packet header is compressed at the ingress MPR-e radio (connected to the 9500 MSS) and restored at the egress MPR-e radio (connected to the 7705 SAR-8 or 7705 SAR-18). In order for the egress MPR-e radio to perform this function, the parameters listed below are configured for an Epipe SAP on a 7705 SAR-8 or 7705 SAR-18; see Epipe Service Configuration Commands for more information:

  1. TDM2Ethernet compression on the Epipe
  2. Real-time Transport Protocol (RTP) header, if required (see RTP Header for a description of how an RTP header is applied)
  3. source 9500 MSS MAC address and destination 7705 SAR-8 or 7705 SAR-18 MAC address
Figure 77:  Mixed Microwave Link Scenario 

Apply Epipe SAP microwave link parameters for interworking with TDM2Ethernet as shown in the CLI syntax example below:

CLI Syntax:
config>service>epipe epipe-id customer customer-id create
sap sap-id create
mw
compression source-mac destination-mac [rtp]

4.11.3.5. Configuring ATM Encapsulation Under Epipe Service (7705 SAR-M only)

The 7705 SAR-M can provide the transport of Ethernet traffic over an ATM network through the configuration of a SAP-to-SAP Ethernet PW. For example, as shown in Figure 78, the 7705 SAR-M provides radio access of Ethernet traffic into an existing ATM network.

The SAP facing the eNodeB is configured as a null- or dot1q-encapsulated Ethernet SAP. The SAP facing the ATM network is ATM/IMA-encapsulated.

ATM/IMA is configured on E1 ports of the 7705 SAR-M. The uplink port must be in access mode in order to host the ATM/IMA SAP. The 7705 SAR-M supports IMA groups with 1 to 16 member links as well as ATM encapsulation on a single E1 port.

The following exceptions on ATM encapsulation under an Epipe service apply:

  1. ATM SAPs are allowed on E1 and E1 IMA ports only
  2. ETH-CFM OAM on an Ethernet SAP is not supported
  3. ACL filtering is not supported
  4. QinQ encapsulated Ethernet SAP interworking to an ATM SAP is not supported
  5. ATM policing on an ATM SAP is not supported
Note:

In addition to supporting ATM-encapsulated SAPs under an Epipe service, the 7705 SAR-M also supports:

  1. the termination of ATM-encapsulated SAPs to IES for node management purposes. If the only transport uplink for a site is ATM, it is necessary to offer in-band management over the existing ATM network.
  2. VC-mux routed PDU encapsulated SAPs for node management. The SAP must be attached to an IES service. No IP forwarding is supported on this management SAP.

For the application described in this section, an ATM-encapsulated SAP to IES is used for managing the 7705 SAR-M at the cell site. See IES for In-band Management for details.

Figure 78:  Ethernet-to-ATM Interworking on the 7705 SAR-M 

The following examples show the Epipe SAP-to-SAP configurations for Ethernet-to-ATM interworking. The first example shows the ATM SAP configuration (ATM VPI/VCI is 30/80), and the second example shows the IMA configuration (IMA bundle). In both examples, SAP 1/1/2:2 is the Ethernet SAP facing the eNodeB.

Example:
epipe 105 customer 1 create
    sap 1/1/2:2 create
    exit
    sap 1/2/3.1:30/80 create
    exit
    no shutdown
exit
Example:
epipe 105 customer 1 create
    sap 1/1/2:2 create
    exit
    sap bundle-ima-1/2.1:20/200 create
        atm
        exit
    exit
    no shutdown
exit

When ATM encapsulation under an Epipe service is used, the AAL-5 encapsulation type for the ATM SAP is “aal5mux-bridged-eth-nof*”, as shown in the following show>service>id service-id>sap sap-id detail screen.

-------------------------------------------------------------------------------
ATM SAP Configuration Information
-------------------------------------------------------------------------------
Ingress TD Profile : 1                        Egress TD Profile : 1
Ingress TD Ovr     : N/A                      Egress TD Ovr     : N/A
Alarm Cell Handling: Enabled
OAM Termination    : Disabled                 Periodic Loopback : Disabled
AAL-5 Encap        : aal5mux-bridged-eth-nof*
-------------------------------------------------------------------------------

4.11.3.6. Configuring Epipe Spoke SDP Bindings

Figure 79 shows an example of a distributed Epipe service configuration between two routers, identifying the service and customer IDs and the unidirectional SDPs required to communicate to the far-end routers. The spoke-sdp sdp-id:vc-id must match on both sides.

Figure 79:  SDPs—Unidirectional Tunnels 

An SDP must exist before it can be used with a spoke SDP. For SDP configuration information, see Configuring SDPs.

For information on configuring ETH-CFM parameters on a spoke SDP, see ETH-CFM (802.1ag and Y.1731) Tasks.

Use the following CLI syntax to create a spoke SDP binding with an Epipe service.

CLI Syntax:
config>service# epipe service-id [customer customer-id] [create] [vc-switching]
spoke-sdp sdp-id:vc-id [vc-type {ether|vlan}] [create] vlan-vc-tag 0..4094
egress
vc-label egress-vc-label
eth-cfm
ingress
vc-label ingress-vc-label
no shutdown
Example:
ALU-1>config>service# epipe 5500
config>service>epipe# spoke-sdp 2:123
config>service>epipe>spoke-sdp# egress
config>service>epipe>spoke-sdp>egress# vc-label 5500
config>service>epipe>spoke-sdp>egress# exit
config>service>epipe>spoke-sdp# ingress
config>service>epipe>spoke-sdp>ingress# vc-label 6600
config>service>epipe>spoke-sdp>ingress# exit
config>service>epipe>spoke-sdp# no shutdown
ALU-2>config>service# epipe 5500
config>service>epipe# spoke-sdp 2:123
config>service>epipe>spoke-sdp# egress
config>service>epipe>spoke-sdp>egress# vc-label 6600
config>service>epipe>spoke-sdp>egress# exit
config>service>epipe>spoke-sdp# ingress
config>service>epipe>spoke-sdp>ingress# vc-label 5500
config>service>epipe>spoke-sdp>ingress# exit
config>service>epipe>spoke-sdp# no shutdown

The following example shows the configuration output for binding an Epipe service between ALU-1 and ALU-2. This example assumes the SAPs have already been configured (see Configuring Epipe SAP Parameters).

ALU-1>config>service# info
----------------------------------------------
...
        epipe 5500 customer 5 vpn 5500 create
            description "Distributed epipe service to east coast"
            sap 1/1/3:21 create
                ingress
                    filter ip 1
                    qos 555
                exit
                egress
                    qos 627
                exit
            exit
            spoke-sdp 2:123 create
                ingress
                    vc-label 6600
                exit
                egress
                    vc-label 5500
                exit
            exit
            no shutdown
        exit
...
----------------------------------------------
ALU-1>config>service#
 
ALU-2>config>service# info
----------------------------------------------
...
exit
        epipe 5500 customer 5 vpn 5500 create
            description "Distributed epipe service to west coast"
            sap 1/1/4:550 create
                ingress
                    qos 654
                exit
                egress
                    qos 432
                exit
            exit
            spoke-sdp 2:123 create
                ingress
                    vc-label 5500
                exit
                egress
                    vc-label 6600
                exit
            exit
            no shutdown
        exit
...
----------------------------------------------

4.11.3.7. Configuring a Security Zone Within an Epipe

To configure firewall security functionality, you must:

  1. configure a firewall security profile and policy in the config>security context
    1. in the config>security>profile context, specify the timeouts for the TCP/UDP/ICMP protocols and configure logging and application assurance parameters. This step is optional. If you do not configure the profile, a default profile is assigned.
    2. in the config>security>policy context, configure a security policy and specify the match criteria and the action to be applied to a packet if a match is found
  2. configure a firewall bypass policy in the config>security context and assign it to the Epipe, as shown in the following CLI syntax. This step is optional. If you do not configure a bypass policy, the protocol packets are firewalled based on the firewall security policies.
  3. configure a security zone and apply the policy ID to the zone, as shown in the following CLI syntax
CLI Syntax:
config>service
epipe service-id [customer customer-id] [create]
fw-bypass-policy {bypass-id | name}
zone zone-id [create]
abort
begin
commit
description description-string
inbound
outbound
policy {policy-id | policy-name}
sap sap-id
shutdown
spoke-sdp sdp-id:vc-id

The following example displays the security zone configuration output.

*A:Sar8 Dut-A>config>service>epipe# info
----------------------------------------------
            stp
                shutdown
            exit
            fw-bypass-policy 1
            sap 1/2/2 create
                no shutdown
            zone 1 create
                name "Epipe zone"
                description "Sample zone"
                sap “1/2/3”
                policy "4"
                inbound
                    limit
                    exit
                exit
                outbound
                    limit
                    exit
                exit
                commit
            exit
            no shutdown
----------------------------------------------

4.11.4. Creating an Fpipe Service

This section describes how to create an Fpipe service. Additional topics in this section include:

Use the following CLI syntax to create an Fpipe service.

CLI Syntax:
config>service# fpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {fr-dlci}] [vc-switching]
description description-string
service-mtu octets
no shutdown

PE router 1 (A:ALU-41):

Example:
A:ALU-41>config>service# fpipe 1 customer 1 create
A:ALU-41>config>service>fpipe# description “fpipe test”
A:ALU-41>config>service>fpipe# service-mtu 1400
A:ALU-41>config>service>fpipe# no shutdown
A:ALU-41>config>service>fpipe#

PE router 2 (A:ALU-42):

Example:
A:ALU-42>config>service# fpipe 1 customer 1 create
A:ALU-42>config>service>fpipe# description “fpipe test”
A:ALU-42>config>service>fpipe# service-mtu 1400
A:ALU-42>config>service>fpipe# no shutdown
A:ALU-42>config>service>fpipe#

The following example shows the Fpipe service creation output.

PE Router 1 (ALU-41):

A:ALU-41>config>service# info 
------------------------------------- 
... 
        fpipe 1 customer 1 create
            description "fpipe test" 
            service-mtu 1400 
            no shutdown 
        exit 
... 
-------------------------------------
A:ALU-41>config>service#

PE Router 2 (ALU-42):

A:ALU-42>config>service# info 
------------------------------------- 
... 
        fpipe 1 customer 1 create
            description "fpipe test"
            service-mtu 1400 
            no shutdown 
        exit 
------------------------------------- 
A:ALU-42>config>service#

4.11.4.1. Configuring Fpipe SAP Parameters

Use the following CLI syntax to configure Fpipe SAP parameters.

For ingress and egress configuration information, see Configuring Ingress and Egress SAP Parameters.

CLI Syntax:
config>service# fpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {fr-dlci}] [vc-switching]
sap sap-id [create]
accounting-policy acct-policy-id
collect-stats
description description-string
egress
qos policy-id
ingress
qos policy-id [shared-queuing]
no shutdown
Example:
A:ALU-41>config>service# fpipe 1
A:ALU-41>config>service>fpipe# sap 1/2/1:16 create
A:ALU-41>config>service>fpipe>sap# ingress
A:ALU-41>config>service>fpipe>sap>ingress# qos 101
A:ALU-41>config>service>fpipe>sap>ingress# exit
A:ALU-41>config>service>fpipe>sap# egress
A:ALU-41>config>service>fpipe>sap>egress# qos 1020
A:ALU-41>config>service>fpipe>sap>egress# exit
A:ALU-41>config>service>fpipe>sap# no shutdown
A:ALU-41>config>service>fpipe>sap# exit
A:ALU-41>config>service>fpipe#

The following example shows the Fpipe SAP configuration output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
        fpipe 1 customer 1 create
            description "fpipe test"
            service-mtu 1400 
            sap 1/2/1:16 create
               ingress
                   qos 101
               exit 
               egress
                   qos 1020 
               exit 
            exit 
            no shutdown 
        exit
... 
------------------------------------- 

To configure a basic local Fpipe service (SAP-to-SAP), enter the sap sap-id command twice with different port IDs in the same service configuration.

The following example shows an FR SAP-to-SAP configuration:

A:ALU-41>config>service# info
-------------------------------------
...
        fpipe 1 customer 1 create
            description "FR sap2sap"
            service-mtu 1400
            sap 1/2/1:16
            sap 1/3/1:20
            no shutdown
        exit
...
-------------------------------------

4.11.4.2. Configuring Fpipe SDP Bindings

Use the following CLI syntax to create a spoke SDP binding with an Fpipe service (for distributed service). For SDP configuration information, see Configuring SDPs.

CLI Syntax:
config>service# fpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {fr-dlci}] [vc-switching]
spoke-sdp sdp-id:vc-id [create]
egress
vc-label egress-vc-label
ingress
vc-label ingress-vc-label
no shutdown
Example:
A:ALU-41>config>service# fpipe 1
A:ALU-41>config>service>fpipe# spoke-sdp 1:1 create
A:ALU-41>config>service>fpipe>spoke-sdp# no shutdown
A:ALU-41>config>service>fpipe>spoke-sdp# exit

The following example shows the Fpipe spoke SDP configuration output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
        fpipe 1 customer 1 create
            description "fpipe test"
            service-mtu 1400
            sap 1/2/1:16 create
               ingress
                   qos 101
               exit
               egress
                   qos 1020
               exit
            exit
            spoke-sdp 1:1 create
            exit
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#

4.11.5. Creating an Hpipe Service

This section describes how to create an Hpipe service. Additional topics in this section include:

Use the following CLI syntax to create an Hpipe service.

CLI Syntax:
config>service# hpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {hdlc}] [vc-switching]
description description-string
service-mtu octets
no shutdown

PE router 1 (ALU-41):

Example:
A:ALU-41>config>service# hpipe 4 customer 1 create
A:ALU-41>config>service>hpipe# description “hpipe test”
A:ALU-41>config>service>hpipe# service-mtu 1400
A:ALU-41>config>service>hpipe# no shutdown
A:ALU-41>config>service>hpipe#

PE router 2 (ALU-42):

Example:
A:ALU-42>config>service# hpipe 4 customer 1 create
A:ALU-42>config>service>hpipe# description “hpipe test”
A:ALU-42>config>service>hpipe# service-mtu 1400
A:ALU-42>config>service>hpipe# no shutdown
A:ALU-42>config>service>hpipe#

The following example shows the Hpipe service creation output.

PE Router 1 (ALU-41):

A:ALU-41>config>service# info
-------------------------------------
...
        hpipe 4 customer 1 create
            description "hpipe test"
            service-mtu 1400
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#

PE Router 2 (ALU-42):

A:ALU-42>config>service# info
-------------------------------------
...
        hpipe 4 customer 1 create
            description "hpipe test"
            service-mtu 1400
            no shutdown
        exit

4.11.5.1. Configuring Hpipe SAP Parameters

Use the following CLI syntax to configure Hpipe SAP parameters. For ingress and egress configuration information, see Configuring Ingress and Egress SAP Parameters.

CLI Syntax:
config>service# hpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {hdlc}] [vc-switching]
sap sap-id [create]
accounting-policy acct-policy-id
collect-stats
description description-string
egress
qos policy-id
ingress
qos policy-id [shared queuing]
no shutdown
Example:
A:ALU-41>config>service# hpipe 4
A:ALU-41>config>service>hpipe# sap 1/4/1.20 create
A:ALU-41>config>service>hpipe>sap# ingress
A:ALU-41>config>service>hpipe>sap>ingress# qos 102
A:ALU-41>config>service>hpipe>sap>ingress# exit
A:ALU-41>config>service>hpipe>sap# egress
A:ALU-41>config>service>hpipe>sap>egress# qos 103
A:ALU-41>config>service>hpipe>sap>egress# exit
A:ALU-41>config>service>hpipe>sap# no shutdown
A:ALU-41>config>service>hpipe>sap# exit
A:ALU-41>config>service>hpipe#

The following example shows the Hpipe SAP configuration output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
        hpipe 4 customer 1 create
            description "hpipe test"
            service-mtu 1400
            sap 1/4/1.20 create
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            no shutdown
        exit
...
-------------------------------------

To configure a basic local Hpipe service (SAP-to-SAP), enter the sap sap-id command twice with different port IDs in the same service configuration.

The following example shows an HDLC SAP-to-SAP configuration:

A:ALU-41>config>service# info
-------------------------------------
...
        hpipe 4 customer 1 create
            description "HDLC sap2sap"
            service-mtu 1514
            sap 1/4/1.20
            sap 1/5/1.10
            no shutdown
        exit
...
-------------------------------------

4.11.5.2. Configuring Hpipe SDP Bindings

Use the following CLI syntax to create a spoke SDP binding with an Hpipe service (for distributed service). For SDP configuration information, see Configuring SDPs.

CLI Syntax:
config>service# hpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {hdlc}] [vc-switching]
spoke-sdp sdp-id:vc-id [create]
egress
vc-label egress-vc-label
ingress
vc-label ingress-vc-label
no shutdown
Example:
A:ALU-41>config>service# hpipe 4
A:ALU-41>config>service>hpipe# spoke-sdp 1:4 create
A:ALU-41>config>service>hpipe>spoke-sdp# no shutdown
A:ALU-41>config>service>hpipe>spoke-sdp# exit

The following example shows the Hpipe spoke SDP configuration output for PE Router 1 (ALU-41).

A:ALU-41>config>service# info
-------------------------------------
...
        hpipe 4 customer 1 create
            description "hpipe test"
            service-mtu 1400
            sap 1/4/1.20 create
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            spoke-sdp 1:4 create
            exit
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#

4.11.6. Creating an Ipipe Service

This section describes how to create an Ipipe service. Additional topics in this section include:

Use the following CLI syntax to create an Ipipe service.

CLI Syntax:
config>service# ipipe service-id [customer customer-id] [vpn vpn-id] [vc-switching]
description description-string
no shutdown

The following example shows an Ipipe configuration:

A:ALU-1>config>service# info
-------------------------------------------
...
        ipipe 202 customer 1 create
            description "eth_ipipe"
            no shutdown
        exit
-------------------------------------------
A:ALU-1>config>service# 

4.11.6.1. Configuring Ipipe SAP Parameters

The following example shows an Ipipe SAP configuration:

A:ALU-48>config>service# info
----------------------------------------------
...
        ipipe 202 customer 1 create
            sap 1/1/2:444 create
                description "eth_ipipe"
                ce-address 172.16.0.0
            exit
             spoke-sdp 16:516 create
                ce-address 172.16.0.1
            exit
            no shutdown
        exit
...
----------------------------------------------

The following shows a PPP to Ethernet local Ipipe example:

Example:
 config>service# ipipe 206 customer 1 create
  config>service>ipipe$ sap 1/1/2:447 create
  config>service>ipipe>sap$ description "eth_ppp_ipipe"
  config>service>ipipe>sap$ ce-address 172.16.0.0
  config>service>ipipe>sap$ no shutdown
  config>service>ipipe>sap$ exit
  config>service>ipipe# spoke-sdp 15:516 create
  config>service>ipipe>sap>spoke-sdp$ ce-address  172.16.0.1
  config>service>ipipe>sap-spoke-sdp$ exit
  config>service>ipipe>$ exit
  config>service>ipipe# no shutdown
  config>service>ipipe# exit
  config>service#

The following shows the output:

A:ALU-48>config>service# info
----------------------------------------------
ipipe 206 customer 1 create
            sap 1/1/2:447 create
                description "eth_ppp_ipipe"
                ce-address 172.16.0.0
            exit
            spoke-sdp 15:516 create
                ce-address 172.16.0.1
             exit
            exit
            no shutdown
        exit
exit
----------------------------------------------

The configuration of a Cisco HDLC SAP on an Ipipe is similar to the above example, except that the sap-id has the form slot/mda/port.channel-group (1/2/2.1).

4.11.6.2. Configuring Ipipe SDP Bindings

The following shows an Ipipe SDP configuration example:

A:ALU-48>config>service# info
----------------------------------------------
...
        sdp 16 mpls create
            far-end 10.4.4.4
            ldp
            path-mtu 1600
            keep-alive
                shutdown
            exit
            no shutdown
        exit
...
        ipipe 207 customer 1 create
            shutdown
            sap 1/1/2:449 create
                description "Remote_Ipipe"
                ce-address 172.16.0.10
            exit
            spoke-sdp 16:516 create
                ce-address 172.16.0.11
            exit

4.11.7. Configuring PW Switching

The vc-switching parameter defines a VLL service as a PW switching point, also called an S-PE. This is the point where a VLL service switches from one PW type to another. The vc-switching parameter must be specified when the VLL service is created.

Once a VLL service is configured as an S-PE, you cannot add a SAP to the configuration. The following example shows the error message generated by the CLI if you attempt to create a SAP on a VLL PW switching service.

Example:
*A:ALU>config>service>epipe 2 customer 1 create
vc-switching
*A:ALU>config>service>epipe$ sap 1/5/1 create
MINOR: SVCMGR #1311 SAP is not allowed under PW switching service
*A:ALU>config>service>epipe$

Use the following CLI syntax to configure pseudowire switching VLL services.

CLI Syntax:
config>service# apipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {atm-vcc|atm-vpc|atm-cell}] [vc-switching]
description description-string
spoke-sdp sdp-id:vc-id
no shutdown
config>service# cpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {satop-e1 | satop-t1 | satop-e3 | satop-t3 | cesopsn | cesopsn-cas}] [vc-switching]
description description-string
service-mtu octets
no shutdown
config>service# epipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-switching]
description description-string
spoke-sdp sdp-id:vc-id
no shutdown
config>service# fpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {fr-dlci}] [vc-switching]
description description-string
spoke-sdp sdp-id:vc-id
no shutdown
config>service# hpipe service-id [customer customer-id] [create] [vpn vpn-id] [vc-type {hdlc}] [vc-switching]
description description-string
spoke-sdp sdp-id:vc-id
no shutdown
config>service# ipipe service-id [customer customer-id] [vpn vpn-id] [vc-switching]
description description-string
spoke-sdp sdp-id:vc-id
no shutdown

The following shows an example of the command usage to configure a VLL service as a PW switching service:

Example:
ALU-1>config>service# apipe 5 customer 1 vpn 1 vc-switching create
config>service>apipe$ description “Default apipe description for service id 100”
config>service>apipe# spoke-sdp 3:1 create
config>service>apipe>spoke-sdp# exit
config>service>apipe# spoke-sdp 6:200 create
config>service>apipe>spoke-sdp# exit
config>service>apipe# no shutdown

The following example shows configurations for each service:

*A:ALA-48>config>service# info
----------------------------------------------
apipe 100 customer 1 vpn 1 vc-switching create
description "Default apipe description for service id 100"
spoke-sdp 3:1 create
exit
spoke-sdp 6:200 create
exit
no shutdown
exit
...
cpipe 107 customer 1 vpn 107 vc-switching vc-type satop-e1 create
description "Default cpipe description for service id 107"
spoke-sdp 3:7 create
exit
spoke-sdp 6:207 create
exit
no shutdown
exit
...
epipe 108 customer 1 vpn 108 vc-switching create
description "Default epipe description for service id 108"
spoke-sdp 3:8 create
exit
spoke-sdp 6:208 create
exit
no shutdown
exit
...
fpipe 109 customer 1 vpn 75 vc-switching create
description "Default fpipe description for service id 109"
spoke-sdp 3:9 create
exit
spoke-sdp 6:209 create
exit
no shutdown
exit
...
hpipe 110 customer 1 vpn 76 vc-switching create
description "Default hpipe description for service id 110"
spoke-sdp 3:10 create
exit
spoke-sdp 6:210 create
exit
no shutdown
exit
...
ipipe 111 customer 1 vpn 77 vc-switching create
description "Default ipipe description for service id 111"
spoke-sdp 3:11 create
exit
spoke-sdp 6:211 create
exit
no shutdown
exit
...
----------------------------------------------

4.11.8. Configuring Ingress and Egress SAP Parameters

By default, QoS policy ID 1 is applied to ingress and egress service SAPs. Existing QoS policies can be associated with service SAPs on ingress and egress ports.

Ingress and egress QoS SAP parameters can be applied to distributed and local Epipe, Fpipe, Hpipe, and Ipipe service SAPs, and to local Apipe and Cpipe service SAPs.

Ingress and egress QoS parameters can also be applied to SAP aggregation groups for ATM VCC VLL services. QoS parameters cannot be applied to SAPs that are members of the aggregation group.

By default, there are no IP filters associated with interfaces or services. IP filter policies can be applied to ingress Epipe and Ipipe service SAPs.

Example:
ALU-1>config>service# epipe 5500
config>service>epipe# sap 1/1/3:21
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# filter ip 1
config>service>epipe>sap>ingress# qos 555
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# egress
config>service>epipe>sap>egress# qos 627
config>service>epipe>sap>egress# exit
config>service>epipe>sap#

The following example shows the Epipe SAP ingress and egress configuration output.

ALU-1>config>service#
----------------------------------------------
        epipe 5500 customer 5 vpn 5500 create
            description "Distributed epipe service to east coast"
            sap 1/1/3:21 create
                ingress
                    filter ip 1
                    qos 555
                exit
                egress
                    qos 627
                exit
            exit
            spoke-sdp 2:123 create
                ingress
                    vc-label 6600
                exit
                egress
                    vc-label 5500
                exit
            exit
            no shutdown
        exit
----------------------------------------------

4.11.9. Using the Control Word

The control word is mandatory for Cpipe SAToP and CESoPSN configurations, Epipe MEF 8 configurations, and Fpipe one-to-one mapping configurations.

The control word is optional for Apipe, Epipe (non-MEF 8), Hpipe, and Ipipe services, but must be enabled for Hpipe pseudowire services when transporting packets that are less than 64 bytes. If the control word is enabled for Epipe or Ipipe services, it will be set to all zeros and ignored on egress.

When the control word is enabled, the Admin Control Word is set to Preferred. Both sides of the VLL must be configured with a matching control word, either both enabled or both disabled, for the pipe to be up.

The control word state will be set to True or False depending on what is configured, either enabled (True) or disabled (False).

Example:
config>service# cpipe 2100 customer 1
config>service>cpipe$ description ”Default cpipe description for service id 2100”
config>service>cpipe$ sap 1/2/7.1:4 create
config>service>cpipe>sap$ description “Default sap description for service id 2100”
config>service>cpipe>sap$ exit
config>service>cpipe# spoke-sdp 1:2001 create
config>service>cpipe>spoke-sdp$ control-word
config>service>cpipe>spoke-sdp$ exit
config>service>cpipe# no shutdown

The following example shows the control word configuration output for a Cpipe service.

*A:ALU-Dut-B>config>service>cpipe# info 
----------------------------------------------
            description "Default cpipe description for service id 2100"
            sap 1/2/7.1:4 create
                description "Default sap description for service id 2100"
            exit
            spoke-sdp 1:2001 create
                control-word
            exit
            no shutdown
----------------------------------------------
*A:ALU-Dut-B>config>service>cpipe# 

The control word cannot be disabled on Cpipe, Epipe MEF 8, or Fpipe services. To disable the control word option on Apipe, Epipe (non-MEF 8), Hpipe, or Ipipe services, use the no control-word command.

Example:
config>service>apipe# spoke-sdp 1:2001 no control-word
config>service>apipe>spoke-sdp$ exit

4.11.10. Configuring PW Redundancy

This section describes configuring PW redundancy. Additional topics in this section include:

For PW redundancy, create an explicit endpoint and then assign a primary spoke SDP and up to three secondary spoke SDPs, or up to four secondary spoke SDPs with no primary spoke SDP, to that endpoint.

CLI Syntax:
config>service# cpipe service-id [customer customer-id] [create]
endpoint endpoint-name [create]
spoke-sdp sdp-id:vc-id endpoint endpoint-name [create]
precedence precedence-value
no shutdown
Example:
config>service# cpipe 2100
config>service>cpipe$ endpoint “Endpoint_Y” create
config>service>cpipe$ spoke-sdp 1:100 endpoint
    “Endpoint_Y” create
config>service>cpipe>spoke-sdp$ precedence primary
config>service>cpipe$ spoke-sdp 2:200 endpoint
    “Endpoint_Y” create
config>service>cpipe>spoke-sdp$ precedence 1
no shutdown

The following example shows the PW redundancy configuration output for a Cpipe service.

*A:7705:Dut-C>config>service>cpipe# info
----------------------------------------------
            endpoint "Endpoint_Y" create
            exit
            spoke-sdp 1:100 endpoint "Endpoint_Y" create
                precedence primary
            exit
            spoke-sdp 2:200 endpoint "Endpoint_Y" create
                precedence 1
            exit
----------------------------------------------------
*A:7705:Dut-C>config>service>cpipe# 

4.11.10.1. Configuring PW Redundancy—Standby Signaling

For standby signaling, create an endpoint as shown in the preceding section, but specify an SDP as the standby signaling master and the far-end endpoints as standby signaling slaves.

In the following example, precedence primary indicates that the spoke SDP is the active SDP and precedence 1 indicates that the spoke SDP is the standby SDP.

To create a standby signaling master:

CLI Syntax:
config>service# cpipe service-id [customer customer-id] [create]
endpoint endpoint-name [create]
standby-signaling-master
exit
spoke-sdp sdp-id:vc-id endpoint endpoint-name [create]
precedence precedence-value
no shutdown
Example:
config>service cpipe 555
config>service>cpipe# endpoint “stdbyMaster” create
config>service>cpipe>endpoint# standby-signaling-master
config>service>cpipe>endpoint# exit
config>service>cpipe# spoke-sdp 5:555 endpoint
    “stdbyMaster” create
config>service>cpipe>spoke-sdp$ precedence primary
exit
config>service>cpipe# spoke-sdp 131:555 endpoint
    “stdbyMaster” create
config>service>cpipe>spoke-sdp$ precedence 1
exit

To create the far-end endpoints as standby signaling slaves:

CLI Syntax:
config>service# cpipe service-id [customer customer-id] [create]
endpoint endpoint-name [create]
standby-signaling-slave
exit
spoke-sdp sdp-id:vc-id endpoint endpoint-name [create]
precedence precedence-value
no shutdown
Example:
config>service cpipe 555
config>service>cpipe# endpoint “FarendA” create
config>service>cpipe>endpoint# standby-signaling-slave
config>service>cpipe>endpoint# exit
config>service>cpipe# spoke-sdp 130:555 endpoint
    “FarendA” create
config>service>cpipe>spoke-sdp$ precedence primary
exit
Example:
config>service cpipe 555
config>service>cpipe# endpoint “FarendB” create
config>service>cpipe>endpoint# standby-signaling-slave
config>service>cpipe>endpoint# exit
config>service>cpipe# spoke-sdp 130:555 endpoint
    “FarendB” create
config>service>cpipe>spoke-sdp$ precedence primary
exit

4.11.10.2. Configuring PW Redundancy—ICB

Inter-Chassis Backup (ICB) spoke SDPs are supported for use with Cpipe services in an MC-APS configuration or MC-LCR configuration and with Epipe services in an MC-LAG configuration. ICB improves switch times, provides additional protection in case of network failures, and reduces packet loss when an active endpoint is switched from a failed MC-APS, MC-LCR, or MC-LAG node to a protection node.

To configure ICB, create explicit endpoints on the access and network side on the working node and then assign a primary spoke SDP on the reverse side of the protection node.

CLI Syntax:
config>service# cpipe service-id [customer customer-id] [create]
description description-string
endpoint endpoint-name [create]
service-mtu octets
standby-signaling-master
exit
sap sap-id [create]
spoke-sdp sdp-id:vc-id endpoint endpoint-name [icb] [create]
precedence precedence-value
no shutdown

The example below shows how to configure ICB on the working node in an MC-APS scenario:

Example:
config>service cpipe 555
config>service>cpipe# description “Cpipe for service id 1”
config>service>cpipe# service-mtu 1000
config>service>cpipe# endpoint “X” create
config>service>cpipe>endpoint# exit
config>service>cpipe# endpoint “Y” create
config>service>cpipe>endpoint# exit
config>service>cpipe# sap aps-1.1.1.1.1 endpoint “X” create
config>service>cpipe>sap# description “SAP for service id 1”
config>service>cpipe>sap# exit
config>service>cpipe# spoke-sdp 2003:1 endpoint
    “Y” create
config>service>cpipe>spoke-sdp# exit
config>service>cpipe# spoke-sdp 2004:1001 endpoint    “X” icb create
config>service>cpipe>spoke-sdp# exit
config>service>cpipe# spoke-sdp 2004:1001 endpoint    “Y” icb create
config>service>cpipe>spoke-sdp# exit
config>service>cpipe# no shutdown
exit

The example below shows how to configure ICB on the protection node in an MC-APS scenario:

Example:
config>service cpipe 1 vc-type cesopsn create
config>service>cpipe# service-mtu 1000
config>service>cpipe# endpoint “X” create
config>service>cpipe>endpoint# exit
config>service>cpipe# endpoint “Y” create
config>service>cpipe>endpoint# exit
config>service>cpipe# sap aps-1.1.1.1.1 endpoint “X” create
config>service>cpipe>sap# description “SAP description for service id 1”
config>service>cpipe>sap# exit
config>service>cpipe# spoke-sdp 4003:1 endpoint
    “Y” create
config>service>cpipe>spoke-sdp# exit
config>service>cpipe# spoke-sdp 4002:1001 endpoint    “Y” icb create
config>service>cpipe>spoke-sdp# exit
config>service>cpipe# spoke-sdp 4002:2001 endpoint    “X” icb create
config>service>cpipe>spoke-sdp# exit
config>service>cpipe# no shutdown
exit

The CLI output below shows an example of ICB configured on the working node in an MC-LCR scenario:

 cpipe 1 customer 1 vc-type cesopsn create
            description "Default Cpipe description for service id 1"
            service-mtu 1000
            endpoint "X" create
            exit
            endpoint "Y" create
            exit
            sap lcr-1/1.1 endpoint "X" create
                description "Default sap description for service id 1"
                no shutdown
            exit
            spoke-sdp 6003:1 endpoint "Y" create
                no shutdown
            exit
            spoke-sdp 6001:1001 endpoint "X" icb create
                no shutdown
            exit
            spoke-sdp 6001:2001 endpoint "Y" icb create
               no shutdown
            exit
            no shutdown
        exit

The CLI output below shows an example of ICB configured on the protection node in an MC-LCR scenario:

 cpipe 1 customer 1 vc-type cesopsn create
            description "Default Cpipe description for service id 1"
            service-mtu 1000
            endpoint "X" create
            exit
            endpoint "Y" create
            exit
            sap lcr-1/1.1 endpoint "X" create
                description "Default sap description for service id 1"
                no shutdown
            exit
            spoke-sdp 1003:1 endpoint "Y" create
                no shutdown
            exit
            spoke-sdp 1006:1001 endpoint "Y" icb create
                no shutdown
            exit
            spoke-sdp 1006:2001 endpoint "X" icb create
                no shutdown
            exit
            no shutdown
        exit

4.12. Service Management Tasks

The service management tasks are similar for Apipe, Cpipe, Epipe, and Ipipe services. This section discusses the following service management tasks:

4.12.1. Modifying Service Parameters

Use the show service service-using command to display a list of configured VLL services.

To modify a VLL service:

  1. Access the specific account by specifying the service ID.
  2. Enter the service parameter to modify and then enter the new information.

PE router 1 (A:ALU-41):

Example:
A:ALU-41>config>service# apipe 5
A:ALU-41>config>service>apipe# sap 1/1/1.1:0/32 create
A:ALU-41>config>service>apipe>sap# accounting-policy 2
A:ALU-41>config>service>apipe>sap# exit
A:ALU-41>config>service>apipe# spoke-sdp 1:4
A:ALU-41>config>service>apipe>spoke-sdp# egress
A:ALU-41>config>service>apipe>spoke-sdp>egress# vc-label 2048
A:ALU-41>config>service>apipe>spoke-sdp>egress# exit
A:ALU-41>config>service>apipe>spoke-sdp# ingress
A:ALU-41>config>service>apipe>spoke-sdp>ingress# vc-label 18431
A:ALU-41>config>service>apipe>spoke-sdp>ingress# exit
A:ALU-41>config>service>apipe>spoke-sdp# exit
A:ALU-41>config>service>apipe#

PE router 2 (A:ALU-42):

Example:
A:ALU-42>config>service# apipe 5
A:ALU-42>config>service>apipe# sap 2/2/2.1:0/32 create
A:ALU-42>config>service>apipe>sap# accounting-policy 2
A:ALU-42>config>service>apipe>sap# exit
A:ALU-42>config>service>apipe# spoke-sdp 1:4
A:ALU-42>config>service>apipe>spoke-sdp# egress
A:ALU-42>config>service>apipe>spoke-sdp>egress# vc-label 18431
A:ALU-42>config>service>apipe>spoke-sdp>egress# exit
A:ALU-41>config>service>apipe>spoke-sdp# ingress
A:ALU-41>config>service>apipe>spoke-sdp>ingress# vc-label 2043
A:ALU-41>config>service>apipe>spoke-sdp>ingress# exit
A:ALU-42>config>service>apipe>spoke-sdp# exit
A:ALU-42>config>service>apipe#

The following example shows the configuration output when adding an accounting-policy to an existing SAP and modifying the spoke SDP parameters on an existing Apipe service for PE Router 1 (ALU-41) and PE Router 2 (ALU-42).

Use a similar syntax to modify Cpipe, Epipe, and Ipipe services.

A:ALU-41>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            description "apipe test"
            service-mtu 1400
            sap 1/1/1.1:0/32 create
               accounting-policy 2
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            spoke-sdp 1:4 create
               egress
                   vc-label 2048
               ingress
                   vc-label 18431
          exit
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#
 
 
 
 
A:ALU-42>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            description "apipe test"
            service-mtu 1400
            sap 2/2/2.1:0/32 create
               accounting-policy 2
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            spoke-sdp 1:4 create
               egress
                   vc-label 18431
               ingress
                   vc-label 2048
          exit
            no shutdown
        exit
...
-------------------------------------
A:ALU-42>config>service# 

4.12.2. Disabling a Service

A service can be shut down without deleting the service parameters.

Use the shutdown command to shut down a VLL service. The following CLI syntax shows the command to shut down an Apipe service. Use a similar syntax to shut down Cpipe, Epipe, Fpipe, Hpipe, and Ipipe services.

CLI Syntax:
config>service#
apipe service-id
shutdown

PE router 1 (A:ALU-41):

Example:
A:ALU-41>config>service# apipe 5
A:ALU-41>config>service>apipe# shutdown
A:ALU-41>config>service>apipe# exit

PE router 2 (A:ALU-42):

Example:
A:ALU-42>config>service# apipe 5
A:ALU-42>config>service>apipe# shutdown
A:ALU-42>config>service>apipe# exit

The following example shows the configuration output for deleting an Apipe service on PE Router 1 (ALU-41) and PE Router 2 (ALU-42).

A:ALU-41>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            shutdown
            description "apipe test"
            service-mtu 1400
            sap 1/1/1.1:0/32 create
               accounting-policy 2
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            spoke-sdp 1:4 create
               egress
                   vc-label 16
            exit
            no shutdown
        exit
...
-------------------------------------
A:ALU-41>config>service#
 
A:ALU-42>config>service# info
-------------------------------------
...
        apipe 5 customer 1 create
            shutdown
            description "apipe test"
            service-mtu 1400
            sap 2/2/2.1:0/32 create
               accounting-policy 2
               ingress
                   qos 102
               exit
               egress
                   qos 103
               exit
            exit
            spoke-sdp 1:4 create
               egress
                   vc-label 16
            exit
        exit
...
-------------------------------------
A:ALU-42>config>service# 

4.12.3. Re-enabling a Service

Use the no shutdown command to re-enable a previously disabled VLL service. The following CLI syntax shows the command to re-enable an Apipe service. Use a similar syntax to re-enable Cpipe, Epipe, Fpipe, Hpipe, and Ipipe services.

CLI Syntax:
config>service#
apipe service-id
no shutdown

PE router 1 (A:ALU-41):

Example:
A:ALU-41>config>service# apipe 5
A:ALU-41>config>service>apipe# no shutdown
A:ALU-41>config>service>apipe# exit

PE router 2 (A:ALU-42):

Example:
A:ALU-42>config>service# apipe 5
A:ALU-42>config>service>apipe# no shutdown
A:ALU-42>config>service>apipe# exit

4.12.4. Deleting a Service

Use the shutdown command to delete a VLL service. The SAP, and any associated protocols and spoke SDPs, must be deleted from the VLL service before the VLL service can be deleted.

Perform the following steps to delete a service:

  1. Shut down the SAP and SDP.
  2. Delete the SAP and SDP.
  3. Shut down the service.

Use the following syntax to delete Apipe services. Use a similar syntax to delete Cpipe, Epipe, Fpipe, Hpipe, and Ipipe services.

CLI Syntax:
config>service#
apipe service-id
sap sap-id
shutdown
exit
no sap sap-id
spoke-sdp [sdp-id:vc-id]
shutdown
exit
no spoke-sdp [sdp-id:vc-id]
shutdown
exit
no apipe service-id
Example:
A:ALU-41>config>service# apipe 5
A:ALU-41>config>service>apipe# sap 1/1/1.1:0/32
A:ALU-41>config>service>apipe>sap# shutdown
A:ALU-41>config>service>apipe>sap# exit
A:ALU-41>config>service>apipe# no sap 1/1/1.1:0/32
A:ALU-41>config>service>apipe# spoke-sdp 1:4
A:ALU-41>config>service>apipe>spoke-sdp# shutdown
A:ALU-41>config>service>apipe>spoke-sdp# exit
A:ALU-41>config>service>apipe# no spoke-sdp 1:4
A:ALU-41>config>service>apipe# shutdown
A:ALU-41>config>service>apipe# exit
A:ALU-41>config>service# no apipe 5