3.11. 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:
3.12. 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:
- Customers
- Service Destination Points (SDPs)
- Service Types
- Service Access Points (SAPs)
3.13. 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:
- 7705 SAR Quality of Service Guide
- 7705 SAR Router Configuration Guide
- 7705 SAR System Management Guide
- 7705 SAR MPLS Guide
A basic service configuration must have the following items configured:
- a customer ID
- a service type
- a service ID (a service-id number is mandatory and a service-name is optional)
- a SAP identifying a port and encapsulation value
- an interface (where required) identifying an IP address, IP subnet, and broadcast address
- 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.
3.14. 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:
3.14.1. Configuring Customer Accounts
Use the customer command to configure customer information. Every customer account must have a customer ID. Optional parameters include:
- description
- contact name
- 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.
The following example displays the customer account configuration output.
3.14.2. Configuring SDPs
When configuring an SDP, consider the following points.
- SDPs can be configured for MPLS, GRE, or IP encapsulation.
- If you do not specify an encapsulation type, the default is MPLS.
- 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.
- By default, SDPs are not associated with services. After an SDP is created, services can be associated with that SDP.
- A distributed service must be bound to an SDP.
- 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.
- If an SDP configuration does not include the IP address of the associated far-end router, VLL and VPLS services to the far-end router cannot be provided.
- Up to eight RSVP-TE or SR-TE LSPs can be configured under a single MPLS-encapsulated SDP. However, a mix of RSVP-TE and SR-TE LSPs is not supported. RSVP-TE LSPs are configured using the config>service>sdp>lsp command and SR-TE LSPs are configured using the config>service>sdp> sr-te-lsp command.
- For MPLS-encapsulated SDPs, LSPs must be configured before the LSP-to-SDP associations can be assigned. The LSP-to-SDP associations must be created explicitly.
- LSPs are configured in the config>router>mpls context. Refer to the 7705 SAR MPLS Guide for configuration and command information.
- The destination address of the LSPs must match the far-end IP address of the SDP.
- The far-end SDP IP address can be the system IP address of a 7705 SAR or an SR-series router, or loopback or network interface of the far-end router
- When configuring MPLS SDP parameters, you can either specify up to eight RSVP-TE LSPs using the config>service>sdp>lsp command or enable LDP using the config>service>sdp>ldp command. There cannot be two methods of transport in a single SDP unless the mixed-lsp-mode option is selected (the lsp and ldp commands are mutually exclusive).If mixed-lsp-mode is enabled and an LSP is specified, RSVP-TE is used for dynamic signaling in the LSP.
- 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, ingress and egress vc-labels for the services using that SDP must be configured manually.
For a basic SDP configuration, perform the following steps:
- Create an SDP ID.
- Specify an encapsulation type.
- Specify a far-end node.
The following examples show the CLI syntax for a basic MPLS SDP configuration. The first two show the syntax for configuring the SDP without mixed-lsp-mode enabled; one shows an RSVP-TE LSP configuration and the other shows an LDP configuration. The third example shows the syntax for configuring the SDP with mixed-lsp-mode enabled, with both an RSVP-TE LSP and LDP configured.
The following example displays a basic SDP LSP configuration output.
The following example displays a basic SDP LDP configuration output.
The following example displays a basic SDP mixed-lsp-mode configuration output.
The following examples show the CLI syntax for a basic GRE SDP configuration.
The following example displays a basic GRE SDP configuration output.
3.14.2.1. Enabling IP Fragmentation for GRE SDPs
Use the following CLI syntax to enable fragmentation of IP packets for GRE SDPs.
| 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.14.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.
The following example displays the service name configuration output.
3.15. ETH-CFM (802.1ag and Y.1731) Tasks
This section provides a brief overview of the following ETH-CFM tasks:
3.15.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 (global or Epipe or VPLS 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 or VPLS service level.
| 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 or VPLS service level.
| 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.15.2. Applying ETH-CFM Parameters
Apply ETH-CFM parameters to the following entities, as shown in the CLI syntax examples below:
- Epipe SAP
- Epipe spoke SDP
- VPLS SAP
- VPLS spoke or mesh SDP
- OAM tests (loopback, linktrace, Ethernet test, delay measurement, loss measurement, synthetic loss measurement)
The MAC address for a MEP on an Epipe SAP or on an Epipe or VPLS SDP cannot be changed. For a MEP on an Epipe SAP, the MAC address is the port MAC address. For a MEP on an Epipe or VPLS SDP, the MAC address is the system MAC address. The MAC address for a MEP on a VPLS SAP can be changed; the default is the port MAC address.
The 7705 SAR supports the following MEPs for both 802.1ag and Y.1731:
- SAP Up and Down MEPs
- spoke SDP Up and Down MEPs
- mesh SDP Up and Down MEPs (VPLS only)
The following two syntax examples are for an Epipe service. Configuration for VPLS is the same except that the hold-mep-up-on-failure and dual-ended-loss-test-enable parameters are not supported on VPLS SAPs.
The third syntax shows the OAM tests that can be applied to MEPs.
3.16. Service Management Tasks
This section provides a brief overview of the following service management tasks:
3.16.1. Modifying Customer Accounts
Use the show>service>customer command to display a list of customer IDs.
To modify a customer account:
- Access the specific account by specifying the customer ID.
- Enter the parameter to modify (description, contact, phone) and then enter the new information.
3.16.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.
3.16.3. Modifying SDPs
Use the show>service>sdp command to display a list of SDP IDs.
To modify an SDP:
- Access the specific SDP by specifying the SDP ID.
- 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. |
3.16.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.
3.16.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.