Nokia 7302 - VPLS SAP Configuration Example

FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN Service
Issue: 13 3HH-11985-AAAA-TQZZA 203
5.8.4.2 VPLS SAP configuration example
To configure a local VPLS service, enter the sap sap-id command twice with different
port IDs in the same service configuration.
configure service vpls <service-id> sap {<port-id> | <lag-id>}:<vlan-id>
create
The following CLI command syntax to create or modify an SAP:
configure service vpls <service-id> sap {<port-id> | <lag-id>}:<vlan-id>
create
The port or LAG is specified in the following format:
• Network (regular) ports: <slot>:<type of port>:<faceplate sequential number>.
• LT (residential or user) ports: lt:<rack>/<shelf>/<sequential number of the line
board>
The VLAN ID must match the VLAN ID of the associated service as follows:
• For an m-VPLS SAP, “no-tag” is used for the externally untagged L2CP frames
processed by the m-VPLS
• For a v-VPLS SAP, the VLAN ID must be explicitly specified.
• For a VPLS there are no restrictions, that is, SAPs of a VPLS can have a different
VLAN ID. The only restriction is that a VLAN ID of a V-VPLS cannot be used.
The following example displays SAPs configured for an m-VPLS:
*A:ALA-1>configure>service# info
----------------------------------------------
...
vpls 1 customer 1 create
description “Local m-VPLS”
stp
shutdown
exit
sap nt-a:sfp:2 create
description “SAP for RSTP service”
exit
sap nt-a:sfp:5 create
description “SAP for RSTP service”
exit
no shutdown
exit
----------------------------------------------
*A:ALA-1>configure>service#
The following example displays configuration of distributed VPLS SAPs:
To configure a distributed VPLS service, you must configure service entities on
originating and far-end nodes. You must use the same service ID on all ends (for
example, create a VPLS service ID 9000 on ALA-1, ALA-2, and ALA-3). A distributed
VPLS consists of an SAP on each participating node and an SDP bound to each
participating node.