VLL Service Configuration Commands
Page 380 7750 SR OS Services Guide
• The VC type value for an Ethernet VLAN is 0x0004.
• The VC type value for a VPLS service is defined as 0x000B.
Values ethernet
ether — Defines the VC type as Ethernet. The ethernet and vlan keywords are mutually exclusive.
When the VC type is not defined then the default is Ethernet for spoke SDP bindings. Defining
Ethernet is the same as executing no vc-type and restores the default VC type for the spoke SDP
binding.
vlan — Defines the VC type as VLAN. The ethernet and vlan keywords are mutually exclusive.
When the VC type is not defined then the default is Ethernet for spoke SDP bindings.
The VLAN VC-type requires at least one dot1Q tag within each encapsulated Ethernet packet
transmitted to the far end.
no endpoint — Removes the association of a spoke SDP with an explicit endpoint name.
endpoint endpoint-name — Specifies the name of the service endpoint.
icb — Configures the spoke SDP as an inter-chassis backup SDP binding.
spoke-sdp
Syntax spoke-sdp sdp-id[:vc-id] [no-endpoint]
spoke-sdp sdp-id[:vc-id] endpoint endpoint-name [icb]
no spoke-sdp sdp-id[:vc-id]
Context config>service>apipe
config>service>cpipe
config>service>fpipe
config>service>ipipe
Description This command binds a service to an existing Service Distribution Point (SDP). A spoke SDP is
treated like the equivalent of a traditional bridge “port” where flooded traffic received on the spoke
SDP is replicated on all other “ports” (other spoke and mesh SDPs or SAPs) and not transmitted on
the port it was received.
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 an SDP
with a 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 SR/ESS 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.
To Next Page
Loading...
