SDP binding configuration
Overview
SDP bindings are associations of SDPs to services. The SDPs are required only on distributed services. A distributed service spans more than one NE. SDPs are used to direct traffic from one NE to another through a service tunnel.
The XML API allows you to create and manage SDP bindings by using the classes specified in the following table.
Table 19-6: Service SDP binding objects
Service type |
Package and class |
---|---|
Apipe |
svt.SpokeSdpBinding |
Epipe | |
Fpipe | |
Ipipe | |
Cpipe | |
Hpipe | |
VPRN | |
IES | |
VPLS, MVPLS, PBB |
svt.MeshSdpBinding, svt.SpokeSdpBinding |
The following example shows the minimum XML parameter tags required to develop an XML request to create a basic service SDP bindings.
The genericObject.configureChildInstance method is used in the XML request to create a SDP binding. The XML response returns the <objectFullName> parameter to identify the new service SDP binding.
Service SDP binding creation parameters
-
childConfigInfo - creates and configures the following SDP binding parameters:
-
Service object - see Table 19-6, Service SDP binding objects
-
<tunnelSelectionTerminationSiteId> - assigns the termination site ID of the SDP binding
-
Figure 19-8: SDP binding creation request example
<generic.GenericObject.configureChildInstance xmlns="xmlapi_1.0"> |
<deployer>immediate</deployer> |
<synchronousDeploy>true</synchronousDeploy> |
<distinguishedName>svc-mgr:service-620: 198.51.100.198</distinguishedName> |
<childConfigInfo> |
<svt.SpokeSdpBinding> |
<actionMask> |
<bit>create</bit> |
</actionMask> |
<tunnelSelectionTerminationSiteId>198.51.100.82</tunnelSelectionTerminationSiteId> |
.. |
</svt.SpokeSdpBinding> |
</childConfigInfo> |
</generic.GenericObject.configureChildInstance> |
See the XML API Reference and Schema Reference for more information about classes, properties, and methods to create the required SDP bindings.