Ingress Network Classification; Ingress Sap Classification; Filter Policies; Mac Resources - Nokia 7302 Manual

FD 100/320Gbps NT and FX NT IHub Services Guide
4.3.3.2
A service ingress network QoS policy defines the match criteria used to determine
the Flow Class of each packet, entering via an SDP binding (i.e. PW). The operator
can configure ingress network QoS policy for the service. By default each Epipe
service is associated the default ingress network QoS policy: policy ID 1.
4.3.3.3
A service ingress access QoS policy defines the match criteria used to determine the
Flow Class for each packet, entering via a SAP. The operator can configure ingress
access QoS policy for the service. By default each Epipe service is associated the
default ingress access QoS policy: policy ID 1. The classification can be based on
the EXP bits of the VC label or based on the inner p-bits of the encapsulated L2
frames.
4.3.4
An Epipe service can have a single filter policy associated on both ingress and
egress. Both MAC and IP filter policies can be used on Epipe services.
4.3.5
Epipe services are point-to-point layer 2 VPNs capable of carrying any Ethernet
payloads. Although an Epipe is a layer 2 service, the ISAM Epipe implementation
does not perform any MAC learning on the service, so Epipe services do not
consume any MAC hardware resources.

4.4 Configuring a VLL Service with CLI

This section provides information to configure Virtual Leased Line (VLL) services
using the command line interface.
Topics in this section include:
•
•
•
•
Issue: 13

Ingress Network Classification

Ingress SAP Classification

Filter Policies

MAC Resources

Common Configuration Tasks
Creating an Epipe Service
Using Spoke SDP Control Words
Service Management Tasks
3HH-11985-AAAA-TQZZA
Virtual Leased Line Services
111