This section provides a brief overview of the tasks performed to configure SDPs, and provides the CLI commands.
Consider the following SDP characteristics:
SDPs can be created as MPLS.
Each distributed service must have an SDP defined for every remote router to provide VLL, VPLS, IES and VPRN services.
A distributed service must be bound to an SDP. By default, no SDP is associated with a service. When an SDP is created, services can be associated to that SDP.
An SDP is not specific or exclusive to any one service or any type of service. An SDP can have more than one service bound to it.
The SDP IP address must be a 7210 SAS-series system IP address.
To configure an MPLS SDP, LSPs must be configured first, then the LSP-to-SDP association must be explicitly created.
In the SDP configuration, automatic ingress and egress labeling (targeted LDP) is enabled by default. Ingress and egress VC labels are signaled over a TLDP connection between two 7210 SAS-series routers.
If signaling is disabled for an SDP, services using that SDP must configure ingress and egress VC labels manually.
To configure a basic SDP, perform the following steps:
Specify an originating node.
Create an SDP ID.
Specify an encapsulation type.
Specify a far-end node.