Automatic SDP (service tunnel) binding for services

Overview

You configure automatic service tunnel (SDP) binding for services when you configure a service using configuration forms.

The NFM-P defines its own internal rules on how automatic mesh SDP bindings are performed.

1. The NFM-P tries to find the least-used SDP (service tunnel) with the lowest load factor (the lower the number of bindings, the lower the load factor) from the source to destination NE when the service tunnel meets the following conditions:

   • the service tunnel operational state is up

   • the operational MTU is greater than or equal to the MTU value of the service site

   • T-LDP is set for SDP bindings of VPLS, IES, or VLL services

   • the selected transport method, either GRE, LDP, or RSVP

2. When no service tunnel operational state is up, NFM-P tries to find the least-used service tunnel with the lowest load factor in an operationally down state.

3. For mirror services, binding are created from the source sites to the destination sites.

4. When a service tunnel cannot be found for a service site, a change in the site leads to another search. For example, if the service MTU is 1500 and the highest path MTU in all SDPs from that site is 1472, no SDP binding can be successful. If the service MTU is lowered to 1472 or less, a successful SDP binding results.

5. When a service tunnel is not found, and the transport method selected is GRE, NFM-P attempts to create a GRE service tunnel with a path MTU equal to the service site service MTU with T-LDP signaling turned on.

See MTU size and port configuration in Working with port and channel objects for more information on MTU size considerations.