FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN Service
Issue: 13 3HH-11985-AAAA-TQZZA 205
5.8.5 Configuring VPLS SAP Parameters
After an SAP is created for a service, you can modify SAP parameters including IP
and MAC filter policies, static MAC, and SAP specific RSTP/MSTP parameters.
5.8.5.1 Configuring egress and ingress filter policies on an
SAP
You can associate an IP or MAC filter policy with an ingress or egress Service
Access Point (SAP) or IP interface. Filter policies control forwarding and dropping of
packets based on IP or MAC matching criteria. Only one type may be applied to an
SAP at a time.
The filter ID must be defined prior to associating the policy with an ingress or egress
SAP. 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.
5.8.5.2 Configuring a static MAC on an SAP
Local static MAC entries create a permanent MAC address to SAP association in the
forwarding database for the VPLS instance, so that the MAC address will not be
learned on the edge device.
The following CLI command syntax can be used to create or delete a static MAC
association with an SAP:
configure service vpls <service-id> sap [{<port-id> | <lag-id>}:<vlan-id>]
[no] static-mac <static-mac>
5.8.5.3 Configuring SAP-Specific STP Parameters
When a m-VPLS has STP enabled, each SAP within the m-VPLS has STP enabled
by default.
SAP STP Administrative State
The administrative state of STP within an SAP controls how BPDUs are transmitted
and handled when received. The allowable states are:
• SAP Admin Up
The default administrative state is up for STP on an SAP. BPDUs are handled in
the normal STP manner on an SAP that is administratively up.
To Next Page
Loading...
