Chapter 76: VLL service management

Overview

Purpose

The NFM-P supports the provisioning of VLL services on edge devices. A VLL service is an L2 point-to-point service that connects access interfaces. A VLL service is completely transparent to customer or subscriber data and to control protocols. Because of this, the device performs no MAC learning in a VLL service.

The NFM-P supports multiple variations of VLL services. See VLL service management overview in this section for more information.

A VLL service that connects access interfaces on one device is called a local VLL service. As there is no need for signaling between devices, a local VLL service uses no SDPs.

A VLL service that connects access interfaces on two devices is called a distributed VLL service. Subscriber or customer data enters a distributed VLL service through access interfaces on different edge devices. The VLL service encapsulates the data and transports it across a service provider IP/MPLS network through GRE, MPLS, or MPLS-TP service tunnels.

Packets that arrive at an edge device are associated with a VLL service based on the access interface on which they arrive. An access interface is uniquely identified using these parameters.

A VLL service uses T-LDP signaling, and uses MPLS or GRE as the service tunnel transport.

A new or existing VLL can be configured as the spoke of an HVPLS. See HVPLS in VPLS management overview and Chapter 85, Composite service management for more information.

The NFM-P supports end-to-end VLL configuration using tabbed configuration forms with an embedded navigation tree.

Common to all device services, such as VLL, are policies that are assigned to the service. Policies are defined at a global level and can then be applied to components of the service, such as interfaces or circuits, when the service is configured or modified. The following policies are common to all device services:

See Chapter 49, Policies overview for more information about policies.

OAM diagnostics can be performed on a per-service basis. See Chapter 90, OAM diagnostic tests for more information.

The General tab of the VLL service management form displays information about the operational state of the service and its sites through the Operational State and State Cause indicators.

The Operational State indicator identifies the states of the sites that are part of the service, as follows:

When the Operational State is Down, a check mark appears beside the appropriate State Cause indicator to identify the type of fault to the NFM-P operator.

For Epipe services, you can configure SAPs so that if their operational state goes down, the service operational state remains up, to allow performance monitoring and ETH CFM on the service. See To create a VLL L2 access interface on a terminating site and the NE documentation for more information.

You can run the OAM Validation test suite for the service by clicking Validate. Alternatively, you can also perform a One Time Validation. If a check mark appears beside the OAM Validation Failed state cause indicator, the test has failed. In addition, the Tested Entity Result tab on the Tests tab displays detailed information about the OAM test result. See Chapter 89, Service Test Manager for more information about how to configure OAM validation test suites.

The NFM-P also monitors the status of a peer SAP after a VLL has been created and put into service. Status information includes faults detected on the service tunnel, and access and network SAP transmissions and receptions. The States tab of the Spoke SDP Binding form displays indicators of failure in the VLL in the State Cause panel.

When you use the NFM-P to create or discover a service, the NFM-P assigns a default Service Tier value to the service. The Service Tier parameter value is relevant only in the context of composite service topology views. See Chapter 85, Composite service management for more information about the hierarchical organization of composite services.

Contents

Overview

VLL service management overview

VLL service management overview

Sample VLL service configuration

VLL service management procedures

Workflow to create a VLL service

To create a VLL service

To view the VLL service operational status

To move a VLL service

To modify a VLL service

To view VLL service contents

To modify a VLL service using the topology view

To delete a VLL service

To configure service tunnel required bandwidth for the service

To create an endpoint for a redundant VLL service

To associate a MEP or MIP with a VLL Epipe SDP binding

To configure an MPLS-TP static pseudowire on a VLL spoke SDP binding

To clear BFD sessions and statistics on a VLL SDP binding

To view the BFD session status on a VLL SDP binding

To switch to the redundant port for one or more VLL SAPs

To create a SAP aggregation group on a 7705 SAR Apipe

To configure EVPN on an Epipe site

To create an HSDPA resiliency configuration

To activate and manually operate an HSDPA resiliency configuration

To run an OAM validation test for a VLL service

To create a BGP VPWS

To view ECMP/LAG hashing of Epipe services

To view the local PW status information for a VLL service

To view the peer PW status information for a VLL service

VLL site management procedures

To configure a VLL site

To configure a GNE site on a VLL service

To configure service tunnel required bandwidth for the site

To link an Epipe service to a backbone VPLS site

To associate a Facility MEP with a VLL Epipe site

To configure segment routing with IPv6 on a VLL Epipe site

To configure a spoke SDP binding on a VLL site

To configure a spoke SDP binding with an L2TPv3 tunnel on a VLL Epipe site

To create a spoke SDP FEC binding on a VLL Epipe site

To configure an Epipe site for BGP multi-homing

To enable the automatic selection of an RD on a VLL Epipe site

To view the last cleared BFD statistics and sessions on a VLL site

VLL access interface management procedures

To create a VLL L2 access interface on a terminating site

To configure LAG per-link hashing on a VLL Epipe or Ipipe L2 access interface

To assign ingress and egress QoS policies to a VLL L2 access interface

To assign ingress and egress QoS policies to a VLL L2 access interface on a 7210 SAS site

To configure scheduling on a VLL L2 access interface

To assign ingress and egress ACL filters to the VLL L2 access interface

To assign an accounting policy to a VLL L2 access interface

To configure Ethernet loopback for a VLL Epipe L2 access interface on a 7705 SAR

To assign a time of day suite to the VLL L2 access interface

To assign a DoS or DDoS protection policy to a VLL L2 access interface or SDP binding

To create MIPs and MEPs on an Epipe or Apipe L2 access interface

To configure microwave compression on an MW link SAP on a VLL L2 access interface

To configure an Ethernet tunnel on a VLL L2 access interface

To assign an ANCP policy to a VLL L2 access interface

To specify the CEM functionality for an Epipe or Cpipe L2 access interface with CEM encapsulation

To switch to the redundant port for a VLL SAP from an L2 access interface properties form

To configure FPE association on a VLL Epipe site