FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN Service
Issue: 13 3HH-11985-AAAA-TQZZA 261
5.16.2.18 mesh-sdp
Table 142 mesh-dsp command
Parameters seconds — The aging time for local MACs expressed in seconds.
Values: 60 — 86400
Item Description
(2 of 2)
Item Description
Syntax mesh-dsp sdp-id[:vc-id] [vc-type {ether|vlan}] [create]
no mesh-dsp sdp-id[:vc-id]
Context configure>service>vpls
Description This command binds a VPLS service to an existing Service Distribution Point (SDP). Mesh
SDPs bound to a service are logically treated like a single bridge “port” for flooded traffic where
flooded traffic received on any mesh SDP on the service is replicated to other “ports” (spoke
SDPs and SAPs) and not transmitted on any mesh SDPs.
Note that this command creates a binding between a service and an SDP. The SDP has an
operational state which determines the operational state of the SDP within the service. For
example, if the SDP is administratively or operationally down, the SDP for the service will be
down.
The SDP must already be defined in the config>service>sdp context in order to associate the
SDP with a valid service. If the sdp sdp-id is not already configured, an error message is
generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service,
no far end ISAM devices can participate in the service.
The no form of this command removes the SDP binding from the service. The SDP
configuration is not affected; only the binding of the SDP to a service. Once removed, no
packets are forwarded to the far-end router.
Default No sdp-id is bound to a service.
Special cases VPLS — Several SDPs can be bound to a VPLS. Each SDP must be destined to a different
ISAM router. If two sdp-id bindings terminate on the same ISAM, an error occurs and the
second SDP is binding is rejected.
(1 of 2)
To Next Page
Loading...
