FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN ServiceIssue: 13 3HH-11985-AAAA-TQZZA 2055.8.5 Configuring VPLS SAP ParametersAfter an SAP is created for a service, you can modify SAP parameters including IPand MAC filter policies, static MAC, and SAP specific RSTP/MSTP parameters.5.8.5.1 Configuring egress and ingress filter policies on anSAPYou can associate an IP or MAC filter policy with an ingress or egress ServiceAccess Point (SAP) or IP interface. Filter policies control forwarding and dropping ofpackets based on IP or MAC matching criteria. Only one type may be applied to anSAP at a time.The filter ID must be defined prior to associating the policy with an ingress or egressSAP. In general, filters applied to SAPs (ingress or egress) apply to all packets onthe SAP. One exception is non-IP packets are not applied to IP match criteria, so thedefault action in the filter policy applies to these packets.5.8.5.2 Configuring a static MAC on an SAPLocal static MAC entries create a permanent MAC address to SAP association in theforwarding database for the VPLS instance, so that the MAC address will not belearned on the edge device.The following CLI command syntax can be used to create or delete a static MACassociation 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 ParametersWhen a m-VPLS has STP enabled, each SAP within the m-VPLS has STP enabledby default.SAP STP Administrative StateThe administrative state of STP within an SAP controls how BPDUs are transmittedand handled when received. The allowable states are:• SAP Admin UpThe default administrative state is up for STP on an SAP. BPDUs are handled inthe normal STP manner on an SAP that is administratively up.
