Configuring Vpls Saps - Nokia 7302 Manual

Intelligent services access manager/fttn/fx, fd 100/320gbps nt and fx nt ihub services
Hide thumbs Also See for 7302:
Table of Contents

Advertisement

Virtual Private LAN Service
5.8.4
A default QoS policy is applied to each ingress and egress SAP. Additional QoS
policies can be configured in the configure>qos context.VPLS services use SAPs
to associate the service with a dot1q Ethernet encapsulation access physical port or
LAG. The virtual port is automatically associated with a v-VPLS when the service is
created and requires no input from the operator.
An m-VPLS uses Ethernet dot1q encapsulated SAPs to enable xSTP protocol on
ports and LAGs.
A v-VPLS/VPLS uses Ethernet dot1q encapsulated SAPs exclusively, to handle
VLAN ID tagged traffic received on the regular (network), hybrid, or residential (user)
access port defined by the SAP associated with the v-VPLS/VPLS.
Note that the v-VPLS/VPLS behavior distinguishes between residential (user-side)
and regular (network-side) ports, to secure control over MAC learning capabilities,
and enable the ability to control user-to-user communication between residential
ports.
Ingress and egress IP and MAC filter policies can also be configured for SAPs.
SAP level STP parameters are also specified for RSTP or MSTP on the m-VPLS.
5.8.4.1
The following conditions apply when creating SAPs for VPLS services:
202

Configuring VPLS SAPs

Configuration Guidelines
SAPs can only be configured on dot1q Ethernet encapsulation access or hybrid
ports
All SAPs must refer to the associated m-VPLS or v-VPLS VLAN ID. For m-VPLS
SAPs, the VLAN ID notation is "no-tag".
An SAP on a v-VPLS can be created with a null VLAN ID, to receive and send
untagged frames.
If a null SAP is not created on a port, untagged
Note 1 —
packets will be dropped.
You cannot configure an SAP with a null VLAN ID on
Note 2 —
an LT port (which is never needed in practice). The null VLAN
ID would be overruled by the internal VLAN ID used to
interconnect the LT to NT. Untagged L2CP traffic is handled by
the m-VPLS.
A description can be added or modified after the SAP is created.
There are no default filter policies. Filter policies must be explicitly applied to an
SAP after the SAP is created.
An SAP that is created on an m-VPLS, a v-VPLS or a VPLS that is administratively
up will attempt to enter the operationally up state.
3HH-11985-AAAA-TQZZA
FD 100/320Gbps NT and FX NT IHub Services Guide
Issue: 13

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

73307360

Table of Contents