Services Overview
50
FD 100/320Gbps NT and FX NT IHub Services Guide
3HH-11985-AAAA-TQZZA Issue: 13
An SDP has the following characteristics:
• An SDP is locally unique to a participating ISAM. The same SDP ID can appear
on other service routers/ISAMs.
• An SDP uses the system IP address to identify the far-end PE.
• An SDP is not specific to any one service or any type of service. Once an SDP is
created, services are bound to the SDP. An SDP can also have more than one
service type associated with it.
• All services mapped to an SDP use the same transport encapsulation type
defined for the SDP (i.e MPLS).
• An SDP is a management entity. Even though the SDP configuration and the
services carried within are independent, they are related objects. Operations on
the SDP affect all the services associated with the SDP. For example, the
operational and administrative state of an SDP controls the state of services
bound to the SDP.
An SDP from the local device to a far-end PE requires a return path SDP from the
far-end PE back to the local ISAM. Each device must have an SDP defined for every
remote PE to which it wants to provide service. SDPs must be created first, before a
distributed service can be configured.
Figure 3 SDP
3.4.3.1 SDP Bindings
To configure a distributed service from ALA-A to ALA-B, the SDP ID must be
specified in the service creation process in order to “bind” the service to the tunnel
(the SDP). Otherwise, service traffic is not directed to a far-end point and the far-end
PE (ISAM or service router) cannot participate in the service (there is no service). To
configure a distributed service from ALA-B to ALA-A, the SDP ID must be specified.
Spoke and Mesh SDPs
When an SDP is bound to a service, it is bound as either a spoke SDP or a mesh
SDP. The type of SDP indicates how flooded traffic is transmitted.
Customer
27
IP/MPLS Network
SAP
3/1/6
dot1q
SAP
2/2/3
dot1q
Service
Cust-27
SDP
ALA-A
Customer
27
To Next Page
Loading...
