evc and oam software for servalww1.microchip.com/downloads/en/appnotes/vppd-03585_ent-an1077.pdf ·...

Application Note ENT-AN1077

EVC and OAM Software for Serval

Table of Contents

This document gives an overview of the software used to support EVC and OAM solutions for Serval. Itincludes examples of EVC configurations with associated CLI commands, and describes functionality inCEServices release 3.40 used with Serval-1 revision B.

Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2EP-Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6EVP-Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12E-Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13EP-Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23L2CP Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

July 2015 1

© 2015 Microsemi Corporation

EVC and OAM Software for Serval EVC and OAM Software for Serval

Software OverviewThe following illustration shows the Microsemi application software, API software, and the Serval device.It does not include Command Line Interface (CLI) and Web management modules and interfaces. TheAPI functions and the application control modules are described in the following sections.

Microsemi API FunctionsThe following sections list the relevant Microsemi API groups and the most important functions related toEVC and OAM control.

VLAN APIsThe VLAN APIs are used to set up basic classification parameters per port and set up the VLANmembership table used in the Serval L2 forwarding block.

Figure 1 • EVC and OAM Software Overview

Microsemi Application

Serval

MSCC API

VLAN EPS

Basic Classification

IS1 TCAM

IS2 TCAM

L2 Forward

Queue System

ES0 TCAM

ERPS EVC MCEACL

OAM

OAM

VLAN ACL

MEP

EVC

EPS ERPS

Table 1 • VLAN API

Function Description

vtss_vlan_port_conf_set() Set VLAN port configuration

vtss_vlan_port_members_set() Set VLAN port members

22

Software OverviewSoftware Overview

EPS APIsThe End Point Protection Service (EPS) APIs are used to control port protection in the L2 forwardingblock.

ACL APIsThe Access Control List (ACL) APIs are used to set up the access control list in the IS2 TCAM. ACL rulescan be used for filtering, policing, and CPU frame copy.

OAM APIsThe Operations, Administration, and Maintenance (OAM) APIs are used to control the Microsemi OAMprocessor and endpoints in Serval.

ERPS APIsThe ERPS APIs are used to control ring protection in the L2 forwarding block.

Table 2 • EPS API


vtss_eps_port_conf_set() Set EPS port configuration

vtss_eps_port_selector_set() Set EPS port selector

Table 3 • ACL API


vtss_ace_add() Add ACL rule

vtss_ace_del() Delete ACL rule

Table 4 • OAM API


vtss_oam_vop_conf_set() Set VOP configuration

vtss_oam_voe_alloc() Allocate a VOE

vtss_oam_voe_free() Free a VOE

vtss_oam_voe_conf_set() Set VOE configuration

vtss_oam_voe_event_enable() Enable/disable VOE event generation

vtss_oam_voe_event_poll() Poll VOE event

vtss_oam_event_poll() Poll VOP event

vtss_oam_ccm_status_get() Get CCM status for VOE

vtss_oam_pdu_seen_status_get() Get PDU-seen status from VOE

vtss_oam_proc_status_get() Get PDU processing status from VOE

vtss_oam_voe_counter_get() Get VOE counters

Table 5 • ERPS API


vtss_erps_vlan_membet_set() Set ERPS member state for a VLAN

vtss_erps_port_state_set() Set ERPS state for ERPS instance and port

33


EVC APIsThe EVC APIs are used to set up Ethernet virtual connections, primarily in the IS1 and ES0 TCAMs. Thisrequires setup of both EVC and ECE rules.

MCE APIsThe MCE APIs are used to set up MEP control entries in the IS1 and ES0 TCAMs.

Packet APIsThe packet API can be used to control L2CP forwarding per port.

Microsemi Control ModulesThe following sections describe the application software control modules and the most importantinterfaces related to EVC and OAM control.

VLAN ModuleThe VLAN module is responsible for controlling the VLAN port configuration and VLAN membershipsusing the following interfaces:

• Consumed Interfaces

– Microsemi VLAN APIs

• Provided Interfaces

– Management APIs for configuration and status

– Control APIs for dynamic configuration from other modules.

Table 6 • EVC API


vtss_evc_port_conf_set() Set EVC port configuration

vtss_evc_policer_conf_set() Set EVC policer configuration

vtss_evc_add() Add EVC entry

vtss_evc_del() Delete EVC entry

vtss_ece_add() Add ECE entry

vtss_ece_del() Delete ECE entry

vtss_evc_oam_port_conf_set() Set VOE index for EVC and port

vtss_evc_counters_get() Get counters for EVC and port

vtss_ece_counters_get Get counters for ECE and port

Table 7 • MCE API


vtss_mce_add() Add MCE

vtss_mce_del() Delete MCE

vtss_mce_port_info_get() Get ISDX for MCE and port

Table 8 • Packet API


vtss_packet_rx_port_conf_set() Set packet Rx port configuration

44

Software OverviewSoftware Overview

ACL ModuleThe ACL module is responsible for controlling the ACL port configuration, policer configuration, and ACLrules using the following interfaces:


– Microsemi ACL APIs



– Control APIs for dynamic configuration from other modules.

EPS ModuleThe EPS module controls port protection using the following interfaces:


– Microsemi EPS APIs

– MEP module APIs for APS PDU reception and transmission



ERPS ModuleThe ERPS module controls ring protection using the following interfaces:


– Microsemi ERPS APIs

– VLAN module APIs for enabling VLAN ingress filtering

– MEP module APIs for APS PDU reception and transmission



MEP ModuleThe MEP module controls the OAM processing using the following interfaces:


– Microsemi OAM APIs

– Microsemi MCE APIs

– ACL module APIs for CPU copy of frames

– VLAN module APIs for ERPS management VLAN membership control.

– EVC module APIs for EVC/ECE change events and configuration access.



– Control APIs for APS PDU reception and transmission

EVC ModuleThe EVC module controls and EVC port configuration, policer configuration, EVC/ECE rules and L2CPforwarding using the following APIs:


– Microsemi EVC APIs

– Microsemi Packet APIs

– VLAN module APIs for EVC VLAN membership control.



– Control APIs for EVC/ECE change events

55


EP-Line

Unprotected EP-LineThe following illustration shows a provider network offering an unprotected Ethernet private line betweentwo UNIs. The following sections describe how to configure the edge bridges using Microsemi CLIcommands. It is assumed that the bridges are in default configuration before applying these commands.

Control Protocols Disable some control protocols that are enabled by default.

# Disable STP and LLDP on UNI/NNI ports interface GigabitEthernet 1/1,3 no lldp receive no lldp transmit no spanning-tree

VLAN ConfigurationSet up the basic VLAN configuration for the UNI and NNI ports.

# Exclude UNI/NNI ports from default VLAN # Set PVID to an unused VLAN to discard non-classified frames # UNI is C-port, NNI is S-port interface GigabitEthernet 1/1 switchport hybrid native vlan 4095 switchport hybrid allowed vlan none switchport hybrid port-type c-port switchport mode hybridinterface GigabitEthernet 1/3 switchport hybrid native vlan 4095 switchport hybrid allowed vlan none switchport hybrid port-type s-port switchport mode hybrid

QoS Configuration Enable one-to-one ingress and egress mapping between CoS and PCP on the UNI and NNI ports.

# On UNI and NNI, enable ingress one-to-one mapping from PCP to CoS interface GigabitEthernet 1/1,3 qos trust tag qos map tag-cos pcp 0 dei 0 cos 0 dpl 0 qos map tag-cos pcp 0 dei 1 cos 0 dpl 1 qos map tag-cos pcp 1 dei 0 cos 1 dpl 0 qos map tag-cos pcp 1 dei 1 cos 1 dpl 1 # On UNI and NNI, enable egress one-to-one mapping from CoS to PCP

Figure 2 • Unprotected EP-Line

Provider Network

Edge Bridge

Edge Bridge

1 13Core

Bridge3

UNI UNICore

Bridge

NNI NNI

66

EP-LineEP-Line

qos tag-remark mapped qos map cos-tag cos 0 dpl 0 pcp 0 dei 0 qos map cos-tag cos 0 dpl 1 pcp 0 dei 1 qos map cos-tag cos 1 dpl 0 pcp 1 dei 0 qos map cos-tag cos 1 dpl 1 pcp 1 dei 1

L2CP Configuration Tunnel all L2 control protocols except LLDP over the EVC. LLDP uses DMAC 01-80-C2-00-00-0Ecorresponding to L2CP ID 14.

# On UNI/NNI port, forward all L2CP except LLDP interface GigabitEthernet 1/1,3 evc l2cp forward 0-13,15

EVC ConfigurationTo conserve resources, set up the UNI and NNI ports to use quarter rules in IS1. The EVC is set up withEVC ID 10 and S-VID 1000. The EVC control module will dynamically register VLAN membership for UNIand NNI ports.

# Use quarter rules for UNI and NNI interface GigabitEthernet 1/1,3 evc key double-tag # Add EVC 10 using S-VID 1000 and NNI port, disable learning. evc 10 vid 1000 ivid 1000 interface GigabitEthernet 1/3

ECE Configuration Use ECE rules to divide the UNI traffic into two service classes:

• Frames received on the UNI port with PCP 4-7 values are mapped to class 4 and sent with PCP 4in the outer tag on the NNI port.

• Other frames received on the UNI port are mapped to class 0 and sent with PCP 0 in the outer tagon the NNI port.

The following sections describe two ways to do this. The first method requires fewer resources in Serval.

• Simple NNI: All EVCs on the NNI port are using the same QoS mapping and statistics.

• Advanced NNI: Each EVC on the NNI port has separate QoS mapping and statistics.

Simple NNISet up the ECE rules mapping to the EVC.

# On UNI port, map tagged frames with PCP 4-7 to class 4, use VID egress lookup evc ece 1 interface GigabitEthernet 1/1 outer-tag match type tagged pcp 4-7 add pcp-mode mapped dei-mode dp tx-lookup vid evc 10 cos 4 # On UNI port, map other frames to class 0, with Rx rule only. evc ece 2 outer-tag add pcp-mode mapped dei-mode dp rule-type rx evc 10 cos 0

Advanced NNI Set up the ECE rules including the QoS mappings.

# On UNI port, map tagged frames with PCP 4-7 to class 4, use (VID, PCP) lookup evc ece 1 interface GigabitEthernet 1/1 outer-tag match type tagged pcp 4-7 tx-lookup pcp-vid evc 10 cos 4 # On UNI port, map other frames to class 0, use (VID, PCP) lookupevc ece 2 interface GigabitEthernet 1/1 tx-lookup pcp-vid evc 10 cos 0

OAM Configuration The following illustration shows the following OAM MEPs in the left Edge Bridge:

• UNI MEP for port level management at the UNI port.

• NNI MEP for port level management at the NNI port.

• EVC Up MEP for EVC level management seen from the UNI side.

77


• EVC Down MEP for EVC level management seen from the NNI side.

The following sections show examples of MEP configurations.

The following commands can be used to create a VOE-based port MEP on the UNI port and enable CCMon this. MEG level 0, MEP ID 1 and peer MEP ID 2 are used. The peer switch must be set upaccordingly.

# Create UNI port MEP with MEG level 0 and MEP ID 1mep 1 down domain port flow 1 level 0 interface GigabitEthernet 1/1mep 1 meg-id ICC000MEG0000 itu mep 1 voe# Enable UNI peer with MEP ID 2mep 1 peer-mep-id 2# Enable CCM on UNI MEP with 1 second intervalmep 1 cc 0

NNI MEPCreate a VOE-based port MEP on the NNI port and enable CCM on it.

# Create NNI port MEP with MEG level 0 and MEP ID 3mep 3 down domain port flow 3 level 0 interface GigabitEthernet 1/3mep 3 meg-id ICC000MEG0000 itu mep 3 voe# Enable NNI peer with MEP ID 2mep 3 peer-mep-id 2# Enable CCM on UNI MEP with 1 second intervalmep 3 cc 0

EVC Down MEPCreate a VOE-based EVC down MEP on the NNI port and enable CCM on it. MEG level 1, MEP ID 1 andpeer MEP ID 2 are used. The peer switch must be set up accordingly. The MEP control module willallocate VOEs and set up MCE rules as needed.

# Create EVC Down MEP on NNI port with MEG level 1 and MEP ID 1mep 10 down domain evc flow 10 level 1 interface GigabitEthernet 1/3mep 10 meg-id ICC000MEG0000 itu mep 10 voe# Enable EVC peer with MEP ID 2mep 10 peer-mep-id 2# Enable CCM on EVC MEP with 1 second intervalmep 10 cc 4

EVC Up MEPCreate a VOE-based EVC up MEP on the UNI port and enable CCM on it. MEG level 2, MEP ID 1 andpeer MEP ID 2 are used. The peer switch must be set up accordingly. The MEP control module willallocate VOEs and set up MCE rules as needed.

# Create EVC Up MEP on UNI port with MEG level 2 and MEP ID 1mep 20 up domain evc flow 10 level 2 interface GigabitEthernet 1/1mep 20 voe# Enable EVC peer with MEP ID 2mep 20 peer-mep-id 2# Enable CCM on EVC MEP with 1 second intervalmep 20 cc 0

Figure 3 • Unprotected EP-Line

1

UNI NNI

3

EVC Up MEP

EPL

UNI MEP

EVC Down MEP

NNI MEP

88

EP-LineEP-Line

Port Protected EP-LineThe following illustration shows an EP-Line with 1:1 port protection on the NNI side. The followingsections describe how the edge bridges can be configured. This setup requires more resourcescompared to the unprotected EP-Line, because rules must be added for both NNI ports.

Control Protocols, VLAN, QoS, and L2CP ConfigurationThe following commands are used for control protocols, VLAN, and QoS configuration.

# Disable STP and LLDP on UNI/NNI portsinterface GigabitEthernet 1/1,3,4 no lldp receive no lldp transmit no spanning-tree# Exclude UNI/NNI ports from default VLAN# Set PVID to an unused VLAN to discard non-classified frames# UNI is C-port, NNI is S-portinterface GigabitEthernet 1/1 switchport hybrid native vlan 4095 switchport hybrid allowed vlan none switchport hybrid port-type c-port switchport mode hybridinterface GigabitEthernet 1/3,4 switchport hybrid native vlan 4095 switchport hybrid allowed vlan none switchport hybrid port-type s-port switchport mode hybrid# On UNI and NNI, enable ingress one-to-one mapping from PCP to CoSinterface GigabitEthernet 1/1,3,4qos trust tag qos map tag-cos pcp 0 dei 0 cos 0 dpl 0 qos map tag-cos pcp 0 dei 1 cos 0 dpl 1 qos map tag-cos pcp 1 dei 0 cos 1 dpl 0 qos map tag-cos pcp 1 dei 1 cos 1 dpl 1# On UNI and NNI, enable egress one-to-one mapping from CoS to PCPqos tag-remark mapped qos map cos-tag cos 0 dpl 0 pcp 0 dei 0 qos map cos-tag cos 0 dpl 1 pcp 0 dei 1 qos map cos-tag cos 1 dpl 0 pcp 1 dei 0 qos map cos-tag cos 1 dpl 1 pcp 1 dei 1# On UNI/NNI port, forward all L2CP except LLDPinterface GigabitEthernet 1/1,3,4 evc l2cp forward 0-13,15

Figure 4 • Port Protected EP-Line

Provider Network

Edge Bridge

Edge Bridge

1 1

3Core

Bridge

3UNI UNI

4 4

Core Bridge

NNI NNI

99


EVC ConfigurationBoth NNI ports are included in the EVC.

# Add EVC 10 using S-VID 1000 and NNI port, disable learning.evc 10 vid 1000 ivid 1000 interface GigabitEthernet 1/3,4

ECE ConfigurationThe ECE configuration for the Advanced NNI setup is used.

# On UNI port, map tagged frames with PCP 4-7 to class 4, use (VID, PCP) lookupevc ece 1 interface GigabitEthernet 1/1 outer-tag match type c-tagged pcp 4-7 add pcp-mode fixed pcp 4 tx-lookup pcp-vid evc 10 cos 4# On UNI port, map other frames to class 0, use (VID, PCP) lookupevc ece 2 interface GigabitEthernet 1/1 outer-tag add pcp-mode fixed pcp 0 tx-lookup pcp-vid evc 10 cos 0

OAM ConfigurationPort MEPs are created on the NNI ports to control protection switching and L-APS is enabled on theprotecting MEP.

# Create NNI port 3 MEP with MEG level 0 and MEP ID 3mep 3 down domain port flow 3 level 0 interface GigabitEthernet 1/3mep 3 meg-id ICC000MEG0000 itu mep 3 voe# Enable NNI peer with MEP ID 2mep 3 peer-mep-id 2# Enable CCM on UNI MEP with 1 second intervalmep 3 cc 0# Create NNI port 4 MEP with MEG level 0 and MEP ID 4mep 4 down domain port flow 4 level 0 interface GigabitEthernet 1/4mep 4 meg-id ICC000MEG0000 itu mep 4 voe# Enable NNI peer with MEP ID 2mep 4 peer-mep-id 2# Enable CCM on NNI MEP with 1 second intervalmep 4 cc 0# Enable L-APS transmissionsmep 4 aps 7 laps

EPS ConfigurationAn EPS instance is created based on the NNI MEPs with the APS protocol enabled.

# Create EPS instance using NNI portseps 1 domain port architecture 1for1 work-flow GigabitEthernet 1/3 protect-flow GigabitEthernet 1/4# Configure MEP and enable APS on EPS instanceeps 1 mep-work 3 mep-protect 4 mep-aps 4

1010

EP-LineEP-Line

Ring Protected EP-LineThe following illustration shows an EP-Line with ring protection on the NNI side. The resourceconsumption is similar to the port protection scenario, because rules must be added for each NNI port.

Control Protocols, VLAN, QoS, and L2CP ConfigurationThe basic setup is identical to that for the "EVP-Line".

EVC ConfigurationBoth NNI ports are included in the EVC. ERPS requires that learning is enabled.

# Use quarter rules for UNI and NNIinterface GigabitEthernet 1/1,3,4evc key double-tag# Add EVC 10 using S-VID 1000 and NNI port, enable learningevc 10 vid 1000 ivid 1000 interface GigabitEthernet 1/3,4 learning

ECE ConfigurationThe ECE configuration for the Advanced NNI setup is used.

# On UNI port, map tagged frames with PCP 4-7 to class 4, use (VID, PCP) lookupevc ece 1 interface GigabitEthernet 1/1 outer-tag match type tagged pcp 4-7 tx-lookup pcp-vid evc 10 cos 4# On UNI port, map other frames to class 0, use (VID, PCP) lookupevc ece 2 interface GigabitEthernet 1/1 tx-lookup pcp-vid evc 10 cos 0

OAM ConfigurationPort MEPs are created on the NNI ports to control protection switching using VLAN 50 and enabling R-APS on both MEPs.

# Create NNI port 3 MEP with MEG level 0, MEP ID 3 and vid 50mep 3 down domain port flow 3 level 0 interface GigabitEthernet 1/3mep 3 meg-id ICC000MEG0000 itu mep 3 voemep 3 vid 50# Enable NNI peer with MEP ID 2mep 3 peer-mep-id 2# Enable CCM on UNI MEP with 1 second intervalmep 3 cc 0# Enable R-APSmep 3 aps 7 multi raps octet 0# Create NNI port 4 MEP with MEG level 0, MEP ID 4 and vid 50mep 4 down domain port flow 4 level 0 interface GigabitEthernet 1/4mep 4 meg-id ICC000MEG0000 itu mep 4 voe

Figure 5 • Ring Protected EP-Line

Provider Network

Edge Bridge

Edge Bridge

1 1

3

Core Bridge

3UNI UNI

4 4

Core Bridge

NNI NNI

Core Bridge

Core Bridge

1111


mep 4 vid 50# Enable NNI peer with MEP ID 2mep 4 peer-mep-id 2# Enable CCM on UNI MEP with 1 second intervalmep 4 cc 0# Enable R-APSmep 4 aps 7 multi raps octet 0

ERPS ConfigurationAn ERPS instance is created based on the NNI MEPs. The EVC S-VID is enabled for this ring. Theswitch is setup as RPL owner on port 3. The peer switch must be RPL neighbor on this port.

# Create ERPS instanceerps 1 major port0 interface GigabitEthernet 1/3 port1 interface GigabitEthernet 1/4# Map VLAN 1000 to the ringerps 1 vlan add 1000# Map NNI MEPs to ringerps 1 mep port0 sf 3 aps 3 port1 sf 4 aps 4# Set as RPL owner on port 3erps 1 rpl owner port0

EVP-Line

Unprotected EVP-LineThe following illustration shows an unprotected EVP-Line forwarding frames with C-VID 17 between theUNI ports.

Control Protocols, VLAN, and QoS ConfigurationThe setups are identical to those for the "EP-Line".

L2CP ConfigurationAll L2 control protocols except LLDP must be tunneled over the EVC. LLDP uses DMAC 01-80-C2-00-00-0E corresponding to L2CP ID 14. ACL policy 42 is used to identify an L2CP profile because multipleEVP-Lines may be set up on the UNI port with different L2CP forwarding properties, and, as a result, theconfiguration cannot be based on the port alone. An ACL rule matching this policy and the UNI port is setup to discard LLDP frames.

# On UNI/NNI port, forward all L2CP.interface GigabitEthernet 1/1,3 evc l2cp forward 0-13,15# Discard LLDP frames using ACL rule matching policy 42

Figure 6 • Unprotected EVP-Line

Provider Network

Edge Bridge

Edge Bridge

1 13Core

Bridge3

UNI UNI

Core Bridge

NNI NNIC-VID 17 C-VID 17

1212

E-TreeE-Tree

access-list ace 1 policy 0x2a policy-bitmask 0x3F tag-priority 0 frametype etype dmac 01-80-c2-00-00-0e action deny

EVC ConfigurationThe EVC setup is identical to that for the "EP-Line".

ECE ConfigurationThe ECEs are added using the advanced NNI method. Two service classes are used based the PCP.Only tagged frames with C-VID 17 are mapped to the EVC. The ECEs are mapped to ACL policy 42 forL2CP frame handling.

# On UNI port, map tagged frames with PCP 4-7 to class 4, use (VID, PCP) lookup evc ece 1 interface GigabitEthernet 1/1 outer-tag match type c-tagged vid 17 pcp 4-7 add pcp-mode fixed pcp 4 tx-lookup pcp-vid evc 10 cos 4 policy 42# On UNI port, map other frames to class 0, use (VID, PCP) lookup evc ece 2 interface GigabitEthernet 1/1 outer tag match type c-tagged vid 17 add pcp-mode fixed pcp 0 tx-lookup pcp-vid evc 10 cos 0 policy 42

OAM ConfigurationOAM MEP setup is identical to that for the "EP-Line".

E-TreeEthernet services have been increasingly deployed by carriers over the last few years through E-Line(point-to-point) services and E-LAN (multipoint-to-multipoint) services. In a variety of scenarios, anenterprise needs to distribute data from one or multiple sources (or roots) to a large number ofdestinations (or leaves). These scenarios might include multimedia companies distributing video streamsto affiliated stations, financial institutions distributing market data to their clients, and organizationsutilizing live video remote training or presentations.

The main requirements of such designs are:

• Almost uni-directionality of the data stream (for instance, from the root to the leaves)

• A relatively limited amount of data from the leaves back to the root

• Lack of communication between the leaves

In order to address this type of request, an E-Tree (rooted point-to-multipoint service) set of services wasdefined as a CE service. It is a new type of Ethernet service over infrastructure. E-Trees classify rootUNIs and leaf UNIs. Data can be exchanged root-to-root or root-to-leaf, but not leaf-to-leaf. Services overE-Tree are compatible with the wide range of Ethernet products offered by carriers today. They also have

1313


the proven potential to support new possibilities and applications such as video distribution, mobilebackhaul, and clock synchronization.

Advantages of E-Tree• The advantages of E-tree include:

• Improved video broadcasting

• Network infrastructure sharing

• Bandwidth optimization

• Reduced network infrastructure cost

Platform SupportE-tree is supported on Jaguar-1™ (VSC7460), LynX™ (VSC7462), and Serval-1™ (VSC7418).

E-Tree Use ModelMEF defines an E-Tree as a Rooted-Multipoint EVC based on two UNI types:

• Leaf UNI

• Root UNI

Figure 7 • E-Tree Diagram

Carrier Ethernet N etw ork

Leaf

Leaf

Root

Root

Leaf

Leaf

Leaf

Leaf

UNI

UNI

UNI UNI UNI

UNI

UNIUNI

1414

E-TreeE-Tree

Frames from leaf UNIs may only be delivered to root UNIs. Frames from root UNIs may be delivered toleaf and root UNIs. The following illustration shows an E-Tree implemented using two VLANs with sharedVLAN learning as recommended by IEEE802.1Q-2011, Annex F.1.3.

The leaf VLAN receives frames from leaf ports and sends frames to root ports only. The root VLANreceives frames from root ports and sends frames to leaf and root ports.

Configuring E-TreeThis section describes how to configure an E-Tree that enables additional connectivity choices forenterprises

Figure 8 • E-Tree Use Model

Leaf UNI

Root UNI

Leaf UNI

Root UNI

Leaf VLAN

Root VLAN

1515


Configuring E-Tree using the CLIThe following example shows how to configure E-Tree from the CLI. This service has two UNIs (one leafUNI and one root UNI) and one NNI port. In this example, both the leaf and the root are on the sameswitch.

1. Set up an E-tree service (no-bundling) on a leaf UNI (Port 2) for CEVLAN ID 73

2. Set up an E-tree service (no-bundling) on a root UNI (Port 3) for CEVLAN ID 73

3. On NNI egress, add one tag: outer VID=103 (root), VID = 104 (Leaf)

4. On NNI ingress, pop one tag

5. Match on a NNI (port 4) for Root VID=103 or Leaf VID = 104 and inner VID=73

Configuration:1. Map VLAN 104 and 103 to FID 10

svl fid 10 vlan 104,1032. Create an EVC as described above.

evc 6 vid 103 ivid 103 interface GigabitEthernet 1/1 leaf vid 104 ivid 104 interfaceGigabitEthernet 1/2 learning policer noneWhere,

evc-id = 6NNI vid = 103NNI ivid = 103NNI port-id = 1/1 leaf vid = 104 leaf ivid = 104Leaf port-id = 1/2

3. Create an ECE for UNI#1 (Leaf UNI).

evc ece 1 interface GigabitEthernet 1/2 outer-tag match type tagged vid 73 evc 6 policer noneWhere,

ece-id = 1 port-id = 1/2 vid = 73

Figure 9 • Example of E-Tree

VID73

VID73 VID73

VID73 VID104

VID103

Leaf UNI

Root UNI

Preserve

NNI

RemoveAdd

Preserve

NNI

1616

E-TreeE-Tree

evc-id = 64. Create an ECE for UNI#2 (Root UNI).

evc ece 2 interface GigabitEthernet 1/3 outer-tag match type tagged vid 73 evc 6 policer noneWhere,

ece-id = 2 port-id = 1/3 vid = 73evc-id = 6

Configuring E-Tree using the Web interfaceIn order to configure E-Tree using the Web interface, EVC and ECE must also be configured.

Configuring EVCUse the following steps to configure EVC from the web interface.

1. Navigate to the Web interface, click Configuration > Ethernet Services > EVCs.

The EVC Control List Configuration page opens.

2. To add a new EVC, click Add New EVC button on the EVC Control List Configuration page.

The EVC Configuration page opens.

3. To assign Leaf UNIs for E-Tree, select an appropriate NNI port from under the NNI Ports sectionin the EVC Configuration page.

4. To set the EVC parameters, provide the appropriate details under the EVC Parameters section inthe EVC Configuration page as shown below.

5. To set the leaf parameters, provide the appropriate details under the Leaf Parameters section inthe EVC Configuration page, as shown below.

Figure 10 • EVC Control List

Figure 11 • NNI Port Selection

Figure 12 • EVC Parameter Setting

Figure 13 • Leaf Parameter Setting

1717


6. To assign the leaf ports, select the appropriate ports from under the Leaf Ports section in theEVC Configuration page.

Configuring ECEUse the following steps to configure ECEs for the Leaf and Root UNIS from the web interface.

1. Navigate to the Web interface, click Configuration > Ethernet Services > ECEs.

Figure 14 • Leaf Ports Setting

7. Click Save.

Table 9 • Control Field Details

Field Description

EVC ID The EVC ID identifies the EVC. The range is from 1 through 1024.

VID The VLAN ID in the PB network. It may be inserted in a C-tag, S-tag, orS-custom tag depending on the NNI port VLAN configuration. Therange is from 0 through 4095.

IVID The Internal/classified VLAN ID in the PB network. The range is from 1through 4095.

Learning The learning mode for the EVC controls whether the source MACaddresses are learned for the frames matching the EVC. Learning maybe disabled if EVC includes only two UNI/NNI ports.

The possible values are:

Enabled: Learning is enabled (MAC addresses are learned).

Disabled: Learning is disabled (MAC addresses are not learned).

Policer ID Value The ingress bandwidth profile mode for the EVC. The possible valuesare:

Specific: The range is from 1 through 1022 .

Discard: All received frames are discarded for the EVC.

None: No bandwidth profile for the EVC.

Policer ID Filter

NNI Ports The list of Network-to-Network Interfaces for the EVC.

MPLS PW IDs Attach EVC to the MPLS Pseudo-Wires.

MPLS PW Split-Horizon IDs Attach EVC to the MPLS split-horizon Pseudo-Wires. Split-horizon isjust an attribute indicating that the traffic received on another non-split-horizon PW cannot be forwarded to this split-horizon PW.

Leaf VID The leaf VLAN ID used in the outer tag for the EVC.

Leaf IVID The leaf internal classified VLAN ID for the EVC.

Leaf Ports The list of leaf ports for the EVC.

1818

E-TreeE-Tree

The ECE Control List Configuration page opens.

2. To add new ECE, click Add New ECE button in the ECE Control List Configuration page.

The ECE Configuration page opens.

3. To assign Leaf/Root UNIs for E-Tree, select an appropriate UNI port from under the UNI Portssection in the ECE Configuration page.

Note: Only UNIs selected as Leaf are treated as Leaf UNIs, and the other UNIs in the configuration areautomatically treated as Root UNIs.

4. To set the Ingress matching, provide the appropriate details under the Ingress Matching sectionin the ECE Configuration page, as shown below.

Figure 15 • ECE Control List Configuration

Figure 16 • ECE UNI Port Setting

Figure 17 • E-Tree ECE Ingress Matching

1919


5. To set the appropriate actions, provide the appropriate details under the Actions section in theECE Configuration page, as shown below.

6. To set the MAC parameters, provide the appropriate details under the MAC Parameters section,in the ECE Configuration page, as shown below.

7. To set the MAC parameters, provide the appropriate details under the MAC Parameters section,in the ECE Configuration page, as shown below.

8. Click Save..

Figure 18 • E-Tree ECE Action Setting

Figure 19 • ECE MAC Parameter Setting

Figure 20 • ECE Egress and Ingress Setting

Table 10 • Control Field Details

Field Description

UNI Ports

UNI Ports The list of User Network Interfaces for the ECE.

Ingress Matching

Lookup The lookup type for matching the ECE.

The allowed values are: Basic: First lookup for basic classification.

Advanced: Second lookup for advanced classification.

2020

E-TreeE-Tree

Tag Type The tag type for matching the ECE.

The possible values are: Any: The ECE matches with both tagged and untaggedframes. Untagged: The ECE matches with the untagged frames only. C-Tagged:The ECE matches with the custom tagged frames only. S-Tagged: The ECEmatches with the service tagged frames only. Tagged: The ECE matches withthe tagged frames only.

Inner Tag Type The inner tag type for matching the ECE.

The possible values are: Any: The ECE matches with both tagged and untaggedframes. Untagged: The ECE matches with the untagged frames only. Tagged:The ECE matches with the tagged frames only.

Frame Type The frame type for the ECE.

The possible values are: Any: The ECE matches with any frame type. IPv4: TheECE matches with the IPv4 frames only. IPv6: The ECE matches with the IPv6frames only. Ethernet Type: The ECE matches with the Ethernet type framesonly. LLC: The ECE matches with the LLC frames only. SNAP: The ECEmatches with the SNAP frames only. L2CP: The ECE matches with the L2CPframes only.

Actions

Directions The EVCs and ECEs are used to setup flows in one or both directions asdetermined by the ECE Direction parameter. If the ECE is bidirectional, then theingress rules of the NNI ports is setup to match the traffic being forwarded to NNIports. The possible values are:

Both: Bidirectional.

UNI-to-NNI: Unidirectional from UNI to NNI.

NNI-to-UNI: Unidirectional from NNI to UNI.

Rule Type The TX lookup for the ECE.

The possible values are: VID lookup : The TX lookup is based on VID. VID-PCP: The TX lookup is based on VID and PCP. ISDX : The TX lookup is basedon ISDX.

TXL Lookup Attach EVC to the MPLS Pseudo-Wires.

L2CP Mode The L2CP mode for the ECE.

The possible values are: Forward: Forward with unchanged DMAC. Tunnel:Forward EType/LLC/SNAP frame and replace DMAC. Discard: Drop frame.Peer: Process frame by local protocol entity.

L2CP DMAC The L2CP destination MAC for the ECE.

The possible values are: Custom: The L2CP destination MAC address is basedon IEEE L2CP MAC addresses (01-00-0C-CD-CD-0X or 01-00-0C-CD-CD-2X).

Cisco: The L2CP destination MAC address is based on Cisco L2CP MACaddress (01-00-0C-CD-CD-D0).

EVC ID Filter The EVC ID for the ECE. The ECE is only active when mapping to an existingEVC.

The possible values are: Any: No EVC ID filter is specified. (EVC ID filter statusis "don't-care".) Specific: If you want to filter a specific EVC ID with this ECE,choose this value. A field for entering a specific value appears.

EVC ID Value When "Specific" is selected for the VLAN ID filter, you can enter a specific value.The allowed value is from 1 through 1024 .

Table 10 • Control Field Details (continued)

Field Description

2121


Policer ID Filter The policer ID filter for matching the ECE.

The possible values are: Specific: If you want to filter a specific policer ID valuewith this ECE, then choose this value. A field for entering a specific valueappears. Discard: All received frames are discarded for the ECE. None : Allreceived frames are forwarded for the ECE. None: The bandwidth profile for thespecified EVC ID is used.

Policer ID Value When "Specific" is selected for the policer ID filter, you can enter a specific value.The value is from 1 through 1022.

Tag Pop Count The ingress tag pop count for the ECE. The allowed range is from 0 through 2.

Policy ID The ACL Policy ID for the ECE for matching ACL rules. The allowed range isfrom 0 through 63.

Class The traffic class for the ECE. The allowed range is from 0 through 7 or disabled.

Drop Precedence The drop precedence for the ECE. The allowed range is 0 , 1 or disabled.

MAC Parameters

SMAC Filter The source MAC address for matching the ECE.

The possible values are: Any: No SMAC filter is specified. (SMAC filter status is"don't-care".) Specific: If you want to filter a specific SMAC value with this ECE,then choose this value. A field for entering a specific value appears.

DMAC Filter When "Specific" is selected for the SMAC filter, you can enter a specific value.

The legal format is "xx-xx-xx-xx-xx-xx" or "xx.xx.xx.xx.xx.xx" or"xxxxxxxxxxxx" (x is a hexadecimal digit).

Egress Outer Tag/Egress Inner Tag

Egress Mode The outer tag for nni-to-uni direction for the ECE.

The possible values are: Enable: Enable outer tag for nni-to-uni direction for theECE. Disable: Disable outer tag for nni-to-uni direction for the ECE.

Ingress Type The inner type for the ECE determines whether an inner tag is inserted in framesforwarded to NNI ports. The possible values are: None: An inner tag is notinserted. C-tag: An inner C-tag is inserted. S-tag: An inner S-tag is inserted. S-custom-tag: An inner tag is inserted and the tag type is determined by the VLANport configuration of the NNI.

VLAN ID The EVC outer/inner tag VID for UNI ports. The allowed value is from 1 through4095.

PCP Mode The outer/inner tag PCP value for the ECE. The allowed range is from 0 through7.

PCP The outer/inner tag PCP value for the ECE. The allowed range is from 0 through7.

DEI Mode The outer/inner tag DEI mode for the ECE.

The possible values are: Classified: The outer tag DEI mode is classified. Fixed :The outer tag DEI mode is fixed. Drop Precedence: The outer tag DEI mode isdrop precedence.

DEI The outer/inner tag DEI value for the ECE. The allowed value is 0 or 1.

Table 10 • Control Field Details (continued)

Field Description

2222

EP-TreeEP-Tree

EP-Tree

Unprotected EP-TreeThe following illustration shows a Provider Network offering an unprotected Ethernet Private Treebetween two Leaf UNIs and two root UNIs. Two VLANs are used to form the E-Tree.

• The root VLAN is used for frames received on root UNIs.

• The leaf VLAN is used for frames received on leaf UNIs.

Control Protocols, VLAN, and QoS Configuration The following commands are executed to disable control protocols and setup VLAN and QoS for the UNIand NNI ports. Shared VLAN learning is enabled for VLAN 10 and 20, which will be used as root and leafVLAN.

# SVL: Map VLAN 10 and 20 to FID 10svl fid 10 vlan 10,20 # Disable STP and LLDP on UNI/NNI portsinterface GigabitEthernet 1/1-3 no lldp receive no lldp transmit no spanning-tree # Exclude UNI/NNI ports from all VLANs# Set PVID to an unused VLAN to discard non-classified frames# UNIs are C-port, NNI is S-portinterface GigabitEthernet 1/1-2 switchport hybrid native vlan 4095 switchport hybrid allowed vlan none switchport hybrid port-type c-port switchport mode hybridinterface GigabitEthernet 1/3 switchport hybrid native vlan 4095 switchport hybrid allowed vlan none switchport hybrid port-type s-port switchport mode hybrid # Enable ingress one-to-one mapping from PCP to CoSinterface GigabitEthernet 1/1-3 qos trust tag qos map tag-cos pcp 0 dei 0 cos 0 dpl 0 qos map tag-cos pcp 0 dei 1 cos 0 dpl 1 qos map tag-cos pcp 1 dei 0 cos 1 dpl 0 qos map tag-cos pcp 1 dei 1 cos 1 dpl 1 # Enable egress one-to-one mapping from CoS to PCP

Figure 21 • Unprotected EP-Tree

Provider Network

Edge Bridge

Edge Bridge

1 1

3Core

Bridge3

Leaf UNI

Core Bridge

NNI NNI

2Root UNI

2

Leaf UNI

Root UNI

2323


qos tag-remark mapped qos map cos-tag cos 0 dpl 0 pcp 0 dei 0 qos map cos-tag cos 0 dpl 1 pcp 0 dei 1 qos map cos-tag cos 1 dpl 0 pcp 1 dei 0 qos map cos-tag cos 1 dpl 1 pcp 1 dei 1

EVC Configuration The EVC is set up with the leaf and root VLANs and leaf UNI list.

# Add EVC 10 using Root VID 10 and Leaf VID 20evc 10 vid 10 ivid 10 interface GigabitEthernet 1/3 leaf vid 20 ivid 20 interface GigabitEthernet 1/1 learning

ECE Configuration The ECE configuration for the advanced NNI setup is used.

# Map tagged frames with PCP 4-7 to class 4, use (VID, PCP) lookupevc ece 1 interface GigabitEthernet 1/1-2 outer-tag match type c-tagged pcp 4-7 add pcp-mode fixed pcp 4 tx-lookup pcp-vid evc 10 cos 4 # Map other frames to class 0, use (VID, PCP) lookupevc ece 2 interface GigabitEthernet 1/1-2 outer-tag add pcp-mode fixed pcp 0 tx-lookup pcp-vid evc 10 cos 0

L2CP ProcessingThe previous sections describe how L2CP frames can be discarded using EVC port configuration (EP-Line) or ACL rules (EVP-Line). This section describes more advanced L2CP processing, again usingLLDP as the example. The EVC configurations described in the previous sections can be reused, if theL2CP configuration parts are replaced by the L2CP configuration shown in the following sections.

PeeringPeering is done by default for LLDP, as a result, the following commands are only needed if the LLDP orL2CP configuration for the UNI has been changed.

# Enable and Peer LLDPinterface GigabitEthernet 1/1 lldp receive lldp transmit evc update l2cp peer 14

DiscardingDiscarding LLDP at a UNI is done using the L2CP mode for the port.

# Discard L2CPinterface GigabitEthernet 1/1 evc update l2cp discard 14

ForwardingForwarding LLDP over an EVC requires that the UNI and NNI are set up to forward the protocol. LLDPframes will then be treated like other frames forwarded over the EVC.

# Forward LLDPinterface GigabitEthernet 1/1,3 evc update l2cp forward 14

TunnelingL2CP tunneling means that the DMAC of the L2CP frame is replaced by a tunnel DMAC when forwardingfrom UNI to NNI port. When forwarding from NNI to UNI port, the tunnel DMAC is replaced with the

2424

L2CP ProcessingL2CP Processing

original L2CP DMAC. This can be used to avoid core bridges inside the provider network processing theframes as L2CP frames.

L2CP tunneling requires that the advanced ingress lookup is used for classification on UNI ports. It alsorequires that the EVC is set up with a specific ACL policy. The ECE configuration for the Advanced NNIsetup is used in the following example, using ACL policy 42. For more information, see "Advanced NNI"on page 7.

# Map tagged frames with PCP 4-7 to class 4, use (VID, PCP) lookupevc ece 1 interface GigabitEthernet 1/1 outer-tag match type c-tagged pcp 4-7 add pcp-mode fixed pcp 4 tx-lookup pcp-vid evc 10 cos 4 policy42# Map other frames to class 0, use (VID, PCP) lookupevc ece 2 interface GigabitEthernet 1/1 outer-tag add pcp-mode fixed pcp 0 tx-lookup pcp-vid evc 10 cos 0 policy 42# Tunnel LLDP framesevc ece 3 lookup advanced interface GigabitEthernet 1/1 frame-type l2cp lldp outer-tag add pcp-mode fixed pcp 4 tx-lookup pcp-vid evc 10 cos 4 policy 42 l2cp mode tunnel# Forward LLDP frames and use half key advanced ingress lookupinterface GigabitEthernet 1/1evc update key-advanced normal l2cp forward 14

2525

VPPD-03585. 1.1. July 2015

Power Matters.TM

Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductorand system solutions for communications, defense & security, aerospace and industrialmarkets. Products include high-performance and radiation-hardened analog mixed-signalintegrated circuits, FPGAs, SoCs and ASICs; power management products; timing andsynchronization devices and precise time solutions, setting the world's standard for time; voiceprocessing devices; RF solutions; discrete components; security technologies and scalableanti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well ascustom design capabilities and services. Microsemi is headquartered in Aliso Viejo, Calif., andhas approximately 3,600 employees globally. Learn more at www.microsemi.com.

Microsemi Corporate HeadquartersOne Enterprise, Aliso Viejo,CA 92656 USA

Within the USA: +1 (800) 713-4113 Outside the USA: +1 (949) 380-6100Sales: +1 (949) 380-6136Fax: +1 (949) 215-4996E-mail: [email protected]

© 2015 Microsemi Corporation. All rightsreserved. Microsemi and the Microsemilogo are trademarks of MicrosemiCorporation. All other trademarks andservice marks are the property of theirrespective owners.

Microsemi makes no warranty, representation, or guarantee regarding the information contained herein orthe suitability of its products and services for any particular purpose, nor does Microsemi assume anyliability whatsoever arising out of the application or use of any product or circuit. The products soldhereunder and any other products sold by Microsemi have been subject to limited testing and should notbe used in conjunction with mission-critical equipment or applications. Any performance specifications arebelieved to be reliable but are not verified, and Buyer must conduct and complete all performance andother testing of the products, alone and together with, or installed in, any end-products. Buyer shall not relyon any data and performance specifications or parameters provided by Microsemi. It is the Buyer'sresponsibility to independently determine suitability of any products and to test and verify the same. Theinformation provided by Microsemi hereunder is provided “as is, where is” and with all faults, and the entirerisk associated with such information is entirely with the Buyer. Microsemi does not grant, explicitly orimplicitly, to any party any patent rights, licenses, or any other IP rights, whether with regard to suchinformation itself or anything described by such information. Information provided in this document isproprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in thisdocument or to any products and services at any time without notice.

mailto:[email protected]

www.microsemi.com

evc and oam software for servalww1.microchip.com/downloads/en/appnotes/vppd-03585_ent-an1077.pdf ·...

Documents