3.10. Configuring Global Service Entities with CLI

This section provides information to create subscriber (customer) accounts and to configure service destination points (SDPs) using the command line interface.

Topics in this section include:

  1. Service Model Entities
  2. Basic Configuration
  3. Common Configuration Tasks
  4. ETH-CFM (802.1ag and Y.1731) Tasks
  5. Service Management Tasks

3.11. Service Model Entities

The Nokia service model uses (logical) service entities to construct a service. Each entity within the model has properties that describe it and influence its behavior. The service model has four main entities to configure a service. The entities are:

  1. Customers
    1. Configuring Customer Accounts
  2. Service Destination Points (SDPs)
    1. Configuring SDPs
  3. Service Types
    1. ATM VLL (Apipe) Services
    2. Circuit Emulation VLL (Cpipe) Services
    3. Ethernet VLL (Epipe) Services
    4. Frame Relay VLL (Fpipe) Services
    5. HDLC VLL (Hpipe) Services
    6. IP Interworking VLL (Ipipe) Services
    7. VPLS
    8. Internet Enhanced Service
    9. VPRN Services
  4. Service Access Points (SAPs)
    1. Configuring Apipe SAP Parameters
    2. Configuring Cpipe SAP Parameters
    3. Configuring Epipe SAP Parameters
    4. Configuring Fpipe SAP Parameters
    5. Configuring Hpipe SAP Parameters
    6. Configuring Ipipe SAP Parameters
    7. Configuring a VPLS SAP
    8. Configuring IES SAP Parameters
    9. Configuring VPRN Interface SAP Parameters

3.12. Basic Configuration

Before configuring a subscriber service, the QoS, logs, and MPLS LSPs (if applicable) must be configured. Refer to the following guides for more information:

  1. 7705 SAR Quality of Service Guide
  2. 7705 SAR Router Configuration Guide
  3. 7705 SAR System Management Guide
  4. 7705 SAR MPLS Guide

A basic service configuration must have the following items configured:

  1. a customer ID
  2. a service type
  3. a service ID (a service-id number is mandatory and a service-name is optional)
  4. a SAP identifying a port and encapsulation value
  5. an interface (where required) identifying an IP address, IP subnet, and broadcast address
  6. an associated SDP (for distributed services)

The following example shows an Epipe service configuration displaying the SDP and Epipe service entities. SDP ID 2 was created with the far-end node 10.10.10.104. Epipe ID 6000 was created for customer ID 6, which uses the SDP ID 2.

A:ALU-B>config>service# info detail
#------------------------------------------
...
        sdp 2 mpls create
            description "MPLS-10.10.10.104"
            far-end 10.10.10.104
            ldp
            signaling tldp
            no vlan-vc-etype
            no path-mtu
            keep-alive
                shutdown
                hello-time 10
                hold-down-time 10
                max-drop-count 3
                timeout 5
                no message-length
            exit
            no shutdown
        exit
...
...
        epipe 6000 customer 6 vpn 6000 create
           service-mtu 1514
           service-name “Epipe_6000” 
           sap 1/1/2:0 create
               ingress
                   filter ip 1
                   qos 1
               exit
               egress
                    qos 1
               exit
           no shutdown
           exit
           spoke-sdp 2:6111 create
               ingress
                   no vc-label
           exit
               egress
                   no vc-label
           exit
               no shutdown
           exit
           no shutdown
       exit
...
#------------------------------------------
A:ALU-B>config>service#

3.13. Common Configuration Tasks

This section provides a brief overview of the following common configuration tasks that must be performed to configure a customer account and an SDP:

  1. Configuring Customer Accounts
  2. Configuring SDPs
  3. Configuring Service Names

3.13.1. Configuring Customer Accounts

Use the customer command to configure customer information. Every customer account must have a customer ID. Optional parameters include:

  1. description
  2. contact name
  3. telephone number

If special characters are included in the customer description string, such as spaces, #, or ?, the entire string must be enclosed in double quotes.

Use the following CLI syntax to create and input customer information.

CLI Syntax:
config>service# customer customer-id create
contact contact-information
description description-string
phone phone-number
Example:
config>service# customer 5 create
config>service>cust# contact "Technical Support"
config>service>cust$ description "Nokia Customer"
config>service>cust# phone "650 555-5100"
config>service>cust# exit

The following example displays the customer account configuration output.

A:ALU-12>config>service# info
-------------------------------------------
    customer 5 create
        contact "Technical Support"
        description "Nokia Customer"
        phone "650 555-5100"
    exit

3.13.2. Configuring SDPs

Every service destination point (SDP) must have the following items configured:

  1. a locally unique SDP identification (ID) number
  2. the system IP address of the far-end router
  3. an SDP encapsulation type—MPLS, GRE, or IP

3.13.2.1. SDP Configuration Considerations

Consider the following SDP characteristics when creating and configuring an SDP.

  1. SDPs can be configured as MPLS, GRE, or IP.
  2. If an SDP configuration does not include the IP address of the associated far-end router, then VLL, VPLS, and VPRN services to the far-end router cannot be provided.
  3. A distributed service must be bound to an SDP.
    By default, SDPs are not associated with services. Once an SDP is created, services can be associated with that SDP.
  4. An SDP can have more than one service bound to it. That is, an SDP is not specific or exclusive to any one service or any type of service.
  5. When configuring an SDP:
    1. The far-end SDP IP address must be the system IP address of a 7705 SAR or an SR-series router.
    2. For MPLS SDPs, LSPs must be configured before the LSP-to-SDP associations can be assigned. The LSP-to-SDP associations must be created explicitly.
    3. Automatic ingress and egress labeling (targeted LDP) is enabled by default. Ingress and egress VC labels are signaled over a targeted LDP connection between two 7705 SAR routers.
Note:

If signaling is disabled for an SDP, then ingress and egress vc-labels for the services using that SDP must be configured manually.

To configure a basic SDP, perform the following steps:

  1. Specify an originating node.
  2. Create an SDP ID.
  3. Specify an encapsulation type.
  4. Specify a far-end node.

3.13.2.2. Configuring an SDP

When configuring an SDP, consider the following points.

  1. If you do not specify an encapsulation type, the default is MPLS.
  2. When configuring a distributed service, you must identify an SDP ID and the far-end IP address. Use the show>service>sdp command to display a list of qualifying SDPs.
  3. When specifying MPLS SDP parameters, you can either specify an LSP or enable an LDP. There cannot be two methods of transport in a single SDP. If an LSP is specified, then RSVP is used for dynamic signaling within the LSP.
  4. LSPs are configured in the config>router>mpls context. See the 7705 SAR MPLS Guide for configuration and command information.

Use the following CLI syntax to create an SDP.

CLI Syntax:
config>service>sdp sdp-id [gre | mpls | ip] create
adv-mtu-override
description description-string
far-end ip-addr
keep-alive
hello-time seconds
hold-down-time seconds
max-drop-count count
message-length octets
timeout timeout
no shutdown
ldp                     (for MPLS SDPs only)
lsp lsp-name [lsp-name] (for MPLS SDPs only)
path-mtu octets
signaling {off|tldp}
no shutdown
Example:
config>service# sdp 2 gre create
config>service>sdp# description “GRE-10.10.10.104”
config>service>sdp# far-end “10.10.10.104”
config>service>sdp# no shutdown
config>service>sdp# exit
config>service# sdp 4 mpls create
config>service>sdp# description “MPLS-10.10.10.104”
config>service>sdp# far-end “10.10.10.104”
config>service>sdp# ldp
config>service>sdp# no shutdown
config>service>sdp# exit
config>service# sdp 8 mpls create
config>service>sdp# description "MPLS-10.10.10.104"
config>service>sdp# far-end “10.10.10.104”
config>service>sdp# lsp "to-104"
config>service>sdp# no shutdown
config>service>sdp# exit
config>service# sdp 104 mpls create
config>service>sdp# description "MPLS-10.10.10.94"
config>service>sdp# far-end “10.10.10.94”
config>service>sdp# ldp
config>service>sdp# no shutdown
config>service>sdp# exit

The following example displays the SDP configuration output.

A:ALU-12>config>service# info
-------------------------------------------
...
        sdp 2  create
            description "GRE-10.10.10.104"
            far-end 10.10.10.104
            keep-alive
                shutdown
            exit
            no shutdown
        sdp 4  create
            description "MPLS-10.10.10.104"
            far-end 10.10.10.104
            ldp
            keep-alive
                shutdown
            exit
            no shutdown
        exit
        sdp 8 mpls create
            description "MPLS-10.10.10.104"
            far-end 10.10.10.104
            lsp "to-104"
            keep-alive
                shutdown
            exit
            no shutdown
        exit
        sdp 104 mpls create
            description "MPLS-10.10.10.94"
            far-end 10.10.10.94
            ldp
            keep-alive
                shutdown
            exit
            no shutdown
        exit
...
-----------------------------------------
A:ALU-12>config>service#

3.13.2.3. Enabling IP Fragmentation for GRE SDPs

Use the following CLI syntax to enable fragmentation of IP packets for GRE SDPs.

CLI Syntax:
config>service>sdp sdp-id gre [create]
allow-fragmentation
Example:
config>service# sdp 2 gre create
config>service>sdp# allow-fragmentation
Note:

Fragmented IP packets require a reassembly profile in order to ensure that packets that cannot be reassembled are disposed of in a timely manner. See the 7705 SAR Router Configuration Guide for configuration and command information.

3.13.3. Configuring Service Names

After a service has been created, it can be assigned a service name.

Use the following CLI syntax to assign a service name to a service. The syntax example is for an Epipe.

CLI Syntax:
config>service>epipe# service-name service-name
Example:
config>service# epipe 1 customer 1 create
config>service>epipe# service-name “Epipe_1”

The following example displays the service name configuration output.

A:ALU-12>config>service>epipe# info
-------------------------------------------
...
            shutdown
            service-name "Epipe_1"
            sdp 2  create
                description "GRE-10.10.10.104"
                far-end 10.10.10.104
                keep-alive
                    shutdown
                exit
                no shutdown
            exit
...
-----------------------------------------
A:ALU-12>config>service#

3.14. ETH-CFM (802.1ag and Y.1731) Tasks

This section provides a brief overview of the following ETH-CFM tasks:

  1. Configuring ETH-CFM Parameters (802.1ag and Y.1731)
  2. Applying ETH-CFM Parameters

3.14.1. Configuring ETH-CFM Parameters (802.1ag and Y.1731)

Configuration commands for both the 802.1ag and the Y.1731 functions are entered in an eth-cfm context (either global or Epipe service). For information on Ethernet OAM commands for 802.1ag and Y.1731 OAM, refer to the “Ethernet OAM Capabilities” section in the 7705 SAR OAM and Diagnostics Guide.

An 802.1ag MEP and a Y.1731 MEP are similar in function. Configure a MEP to be a Y.1731 MEP by choosing the format none keywords in the global domain command, and the format icc-based keywords in the global association command. Configure a MEP to be a Y.1731 MEP that can interoperate with a 802.1ag MEP by choosing the format none keywords in the global domain command, and the format string keywords in the global association command.

802.1ag Configuration

The first set of commands occurs at the global level. The second set occurs at the Epipe service level.

*A:ALU-1>config>eth-cfm# info
----------------------------------------------
    domain 1 name "kanata_MD" level 5
        association 1 format string name "kanata_MA"
            bridge-identifier 2
            exit
            ccm-interval 60
            remote-mepid 125
        exit
    exit
----------------------------------------------
*A:ALU-1>config>service>epipe# info
----------------------------------------------
    shutdown
    sap 1/5/1 create
        eth-cfm
            mep 1 domain 1 association 1 direction down
                shutdown
            exit
        exit
    exit
    spoke-sdp 1:11 create
        eth-cfm
            mep 2 domain 1 association 1 direction down
                shutdown
            exit
        exit
        exit
----------------------------------------------
Note:

RDI information is carried in the CCM OAMPDU. To be able to transmit and also receive RDI information, a MEP must have CCM enabled. See Applying ETH-CFM Parameters.

Y.1731 Configuration

The following example displays a Y.1731 configuration. The first set of commands occurs at the global level. The second set occurs at the Epipe service level.

*A:ALU-1>config>eth-cfm# info
----------------------------------------------
    domain 1 format none level 1
        association 1 format icc-based name "1234567890123"
            bridge-identifier 100
            exit
            ccm-interval 1
        exit
    exit
----------------------------------------------
*A:ALU-1>config>service>epipe# info
----------------------------------------------
    shutdown
    sap 2/2/1:40 create
        eth-cfm
            mep 1 domain 1 association 1 direction up
                ais-enable
                    priority 2
                    interval 60
                exit
                eth-test-enable
                    test-pattern all-ones crc-enable
                exit
                no shutdown
            exit
        exit
    exit
    no shutdown
...
----------------------------------------------
Note:

To be able to transmit and also receive AIS PDUs, a Y.1731 MEP must have ais-enable set. To be able to transmit and also receive ETH-Test PDUs, a Y.1731 MEP must have eth-test-enable set.

3.14.2. Applying ETH-CFM Parameters

Apply ETH-CFM parameters to the following entities, as shown in the CLI syntax examples below:

  1. Epipe SAP
  2. Epipe spoke SDP
  3. OAM tests (loopback, linktrace, Ethernet test, delay measurement, loss measurement, synthetic loss measurement)

The MAC address for a MEP on an Epipe cannot be changed. For a MEP on a SAP, the MAC address is the port MAC address. For a MEP on a spoke SDP, the MAC address is the system MAC address.

The 7705 SAR supports the following MEPs:

  1. 802.1ag
    1. SAP Up MEP
    2. SAP Down MEP
    3. spoke SDP Down MEP
  2. Y.1731
    1. SAP Up MEP
    2. SAP Down MEP
CLI Syntax:
config>service>epipe>sap
eth-cfm
hold-mep-up-on-failure
mep mep-id domain md-index association ma-index [direction {up | down}]
ccm-enable
ais-enable
ccm-ltm-priority priority
dual-ended-loss-test-enable
eth-test-enable
low-priority-defect {allDef|macRemErrXcon| remErrXcon|errXcon|xcon|noXcon}
one-way-delay-threshold seconds
[no] shutdown
config>service>epipe>spoke-sdp
eth-cfm
mep mep-id domain md-index association ma-index [direction {up | down}]
ccm-enable
ccm-ltm-priority priority
low-priority-defect {allDef|macRemErrXcon| remErrXcon|errXcon|xcon|noXcon}
[no] shutdown
oam
eth-cfm linktrace mac-address mep mep-id domain md-index association ma-index [ttl ttl-value]
eth-cfm loopback mac-address mep mep-id domain md-index association ma-index [send-count send-count] [size data-size] [priority priority]
eth-cfm eth-test mac-address mep mep-id domain md-index association ma-index [priority priority] [data-length data-length]
eth-cfm one-way-delay-test mac-address mep mep-id domain md-index association ma-index [priority priority]
eth-cfm two-way-delay-test mac-address mep mep-id domain md-index association ma-index [priority priority]
eth-cfm single-ended-loss-test mac-address mep mep-id domain md-index association ma-index [priority priority] [interval {100ms|1s}] [send-count send-count]
eth-cfm two-way-slm-test mac-address mep mep-id domain md-index association ma-index [priority priority] [send-count send-count] [size data-size] [timeout timeout] [interval interval]

3.15. Service Management Tasks

This section provides a brief overview of the following service management tasks:

  1. Modifying Customer Accounts
  2. Deleting Customers
  3. Modifying SDPs
  4. Deleting SDPs
  5. Deleting LSP Associations

3.15.1. Modifying Customer Accounts

Use the show>service>customer command to display a list of customer IDs.

To modify a customer account:

  1. Access the specific account by specifying the customer ID.
  2. Enter the parameter to modify (description, contact, phone) and then enter the new information.
CLI Syntax:
config>service# customer customer-id create
[no] contact contact-information
[no] description description-string
[no] phone phone-number
Example:
config>service# customer 27 create
config>service>customer$ description “Western Division”
config>service>customer# contact “John Dough”
config>service>customer# no phone “(650) 237-5102”

3.15.2. Deleting Customers

The no form of the customer command typically removes a customer ID and all associated information; however, all service references to the customer must be shut down and deleted before a customer account can be deleted.

CLI Syntax:
config>service# no customer customer-id
Example:
config>service# epipe 5 customer 27 shutdown
config>service# epipe 9 customer 27 shutdown
config>service# no epipe 5
config>service# no epipe 9
config>service# no customer 27

3.15.3. Modifying SDPs

Use the show>service>sdp command to display a list of SDP IDs.

To modify an SDP:

  1. Access the specific SDP by specifying the SDP ID.
  2. Enter the parameter to modify, such as description, far-end, or lsp, and then enter the new information.
Note:

Once the SDP is created, you cannot modify the SDP encapsulation type.

CLI Syntax:
config>service# sdp sdp-id
Example:
config>service# sdp 79
config>service>sdp# description “Path-to-107”
config>service>sdp# shutdown
config>service>sdp# far-end “10.10.10.107”
config>service>sdp# path-mtu 1503
config>service>sdp# no shutdown

3.15.4. Deleting SDPs

The no form of the sdp command typically removes an SDP ID and all associated information; however, before an SDP can be deleted, the SDP must be shut down and removed (unbound) from all customer services where it is applied.

CLI Syntax:
config>service# no sdp 79
Example:
config>service# epipe 5 spoke-sdp 79:5
config>service>epipe>spoke-sdp# shutdown
config>service>epipe>spoke-sdp# exit
config>service>epipe 5 no spoke-sdp 79:5
config>service>epipe# exit
config>service# no sdp 79

3.15.5. Deleting LSP Associations

The no form of the lsp command removes an LSP ID and all associated information; however, before an LSP can be deleted, it must be removed from all SDP associations.

CLI Syntax:
config>service# sdp sdp-id
[no] lsp lsp-name
Example:
config>service# sdp 79
config>service>sdp# no lsp 123
config>service>sdp# exit all