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:
The Alcatel-Lucent 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:
Before configuring a subscriber service, the QoS, logs, and MPLS LSPs (if applicable) must be configured. Refer to the following guides for more information:
A basic service configuration must have the following items configured:
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.
This section provides a brief overview of the following common configuration tasks that must be performed to configure a customer account and an SDP:
Use the customer command to configure customer information. Every customer account must have a customer ID. Optional parameters include:
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.
Every service destination point (SDP) must have the following items configured:
Consider the following SDP characteristics when creating and configuring an SDP.
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:
When configuring an SDP, consider the following points.
Use the following CLI syntax to create an SDP.
The following example displays the SDP sample configuration output.
This section provides a brief overview of the following ETH-CFM tasks:
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 OS 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.
The first set of commands occurs at the global level. The second set occurs at the Epipe 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. |
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.
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. |
Apply ETH-CFM parameters to the following entities, as shown in the CLI syntax examples below:
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:
This section provides a brief overview of the following service management tasks:
Use the show>service>customer command to display a list of customer IDs.
To modify a customer account:
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.
Use the show>service>sdp command to display a list of SDP IDs.
To modify an SDP:
Note:
Once the SDP is created, you cannot modify the SDP encapsulation type. |
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.
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.