Overview

NE support

The VLAN Connection Profile policy is supported on 7450 ESS, 7750 SR and 7950 XRS NEs. The TPS Connection Profile policy is a variant that is supported on the 1830 TPS.

Description

The Ethernet policy VLAN Connection Profile and TPS Connection Profile enable you to configure SAPs to be part of multiple VLANs in a single command. You can specify all the VLANs that the SAPs needs to be part of by providing a range of VLAN IDs or separate, individual, VLAN IDs. When this policy is used under a SAP, the NFM-P distributes the connection profile to the NE first and then references the connection profile.

After creating a policy, you can use it in Epipe (terminating sites only) and VPLS (regular sites only) services. The VLAN Connection Profile policies are not supported in the following services: Etree, M-VPLS, B-VPLS, R-VPLS, I-VPLS and PBB-Epipe.

The NFM-P performs the validation of VLAN ID ranges to ensure that different connections profiles do not overlap.

SAP encapsulation

Only access and hybrid ports with the encapsulation type of Dot1 Q and Q-in-Q support VLAN Connection Profile and TPS Connection Profile policies. You need to be aware of the SAP encapsulation requirements and dependencies for the policy when using the policy in an Epipe or VPLS service.

The VLAN Connection Profile policy supports the following new SAP types:

• Dot1 Q encapsulation port

  • sap 1/1/1:cp-1

    A connection profile policy is required for the creation of this SAP type.

• Q-in-Q encapsulation port

  • sap 1/1/2:cp-2.*

    A connection profile policy is required for the creation of this SAP type, the VLAN Connection Profile tag needs to be Outer, and the inner encapsulation value needs to be set to 0, 4095, or * (asterisk).

  • sap 1/1/3:1234.cp-3

    A connection profile policy is required for the creation of this SAP type, the VLAN Connection Profile tag needs to be Inner, and the outer encapsulation value needs to be set to a value from 1 through 4094.

The assignment of SAPs with overlapping encapsulation types causes operation failure.

Constraints

This section describes the constraints that must be considered when configuring SAPs for VLAN connection profiles.

Services

VLAN connection profiles are not supported in the following types of services:

• Etree

• M-VPLS

• B-VPLS

• R-VPLS

• I-VPLS

• PBB-Epipe

Features

The following features are not supported in combination with VLAN connection profile services:

• Proxy ARP and Proxy ND

• Capture SAPs

• Ethernet tunnel SAPs

• Ethernet ring SAPs

  The VLAN connection profile SAPs can be used as Ethernet ring data SAPs, but do not support control G.8032 traffic.

• VLAN translation

• Xstp

  The VLAN connection profile SAPs can be managed by an M-VPLS, but services with CP SAPs do not support Xstp.

• L2PT

• BPDU translation

• Subscriber management features

• IGMP/MLD/PIM (v4 or v6)

• VLAN VC Tag under an SDP-binding sharing service with a VLAN connection profile SAP