[no] spoke-sdp sdp-id
config>service>vprn
Supported on all 7210 SAS platforms as described in this document
This command binds a service to an existing SDP. The SDP defines the transport tunnel to which this VPRN service is bound.
The SDP has an operational state that 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 is down.
The SDP must already exist in the config>service>sdp context before it can be associated with a VPRN service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id exists, a binding between the specific sdp-id and service is created.
SDPs must be explicitly associated and bound to a service to allow far-end 7210 SAS devices to participate in the service.
The no form of this command removes the SDP binding from the service; the SDP configuration is not affected. When the SDP binding is removed, no packets are forwarded to the far-end router.
Several SDPs can be bound to a VPRN service. Each SDP must be destined for a different 7210 SAS router. If two sdp-id bindings terminate on the same 7210 SAS, an error occurs and the second SDP binding is rejected.
Specifies the SDP identifier. Allowed values are integers for existing SDPs.
Specifies the virtual circuit identifier.
spoke-sdp sdp-id [:vc-id] vc-type {ether | ipipe} [create]
no spoke-sdp sdp-id [:vc-id] vc-type {ether | ipipe} [create]
config>service>vprn>if
Supported on all 7210 SAS platforms as described in this document
This command binds a service to an existing 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 that 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 is down.
The SDP must already be defined in the config>service>sdp context 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 devices can participate in the service.
Class-based forwarding is not supported on a spoke-SDP used for termination on an IES or VPRN services. All packets are forwarded over the default LSP.
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. When removed, no packets are forwarded to the far-end router.
Several SDPs can be bound to a VPRN service. Each SDP must be destined for a different router. If two SDP ID bindings terminate on the same 7210 SAS, an error occurs and the second SDP is binding is rejected.
Specifies the SDP identifier.
Specifies the virtual circuit identifier.
Specifies the encapsulation and pseudowire type for the spoke-SDP.
egress
cconfig>service>vprn>if>spoke-sdp
config>service>vprn>red-if>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command configures an SDP context.
ingress
config>service>vprn>if>spoke-sdp
config>service>vprn>red-if>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command configures the SDP context.
vc-label egress-vc-label
no vc-label [egress-vc-label]
config>service>vprn>if>spoke-sdp>egress
config>service>vprn>red-if>spoke-sdp>egress
Supported on all 7210 SAS platforms as described in this document
This command configures the egress VC label.
Specifies a VC egress value that indicates a specific connection.
vc-label ingress-vc-label
no vc-label [ingress-vc-label]
config>service>vprn>>if>spoke-sdp>ingress
config>service>vprn>red-if>spoke-sdp>ingress
Supported on all 7210 SAS platforms as described in this document
This command configures the ingress VC label.
Specifies a VC ingress value that indicates a specific connection.
filter ip ip-filter-id
no filter
config>service>vprn>if>spoke-sdp>egress
config>service>vprn>if>spoke-sdp>ingress
config>service>vprn>red-if>spoke-sdp>ingress
config>service>vprn>red-if>spoke-sdp>egress
config>service>vprn>nw-if>egress
Supported on all 7210 SAS platforms as described in this document
This command associates an IP filter policy with an ingress or egress SAP or IP interface. An IP filter policy can be associated with spoke SDPs. Filter policies control the forwarding and dropping of packets based on IP or MAC matching criteria.
The filter command is used to associate a filter policy that has a specified ip-filter-id with an ingress or egress SAP. The ip-filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message is returned.
In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is non-IP packets are not applied to IP match criteria, so the default action in the filter policy applies to these packets.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use the scope command within the filter definition to change the scope to local or global. The default scope of a filter is local.
Specifies an IP filter policy. The filter ID must already exist within the created IP filters.