Service Ccag Sap Provisioning - Alcatel-Lucent 7750 SR Manual

Os services guide

Hide thumbs Also See for 7750 SR:

Table of Contents

Services Commands

Service CCAG SAP Provisioning

Services are provisioned onto a CCAG using a special CCAG SAP definition. CCAG SAPs must

reference a ccag-id, a CCA path (a or b), a pairing type (sap-sap or sap-net) and a unique cc-id. The

ccag-id identifies the group of CCAs that will be used for forwarding packets associated with the

SAP. The path identifies the bandwidth control grouping used to manage CCA egress bandwidth. The

pairing type helps the system identify which buffering resources will be used to manage egress

queuing of packets. Finally, the cc-id is used to explicitly cross connect the SAP to another SAP or

network IP interface configured with the same cc-id.

sap ccag-ccag-id.{a | b}[.sap-net | .sap-sap]:cc-id [create]

no sap ccag-ccag-id.{a | b}[.sap-net | .sap-sap]:cc-id

config>service>epipe

This command creates a cross connect SAP on the ccag-id referenced in the Epipe service. A CCAG

SAP is identified by four items; the ccag-id, the CCAG path, the pairing type and the cc-id. An Epipe

CCAG SAP supports all the available QoS, filtering and accounting features as an Epipe Dot1Q SAP.

The no form of the command removes a SAP from a service context. Once removed, all information

and resources concerning the SAP is deleted from the system including the CCAG cc-id in use on the

ccag — The ccag portion of the SAP identifier is required and specifies that the epipe SAP is of the

-ccag-id — The ccag-id portion of the SAP identifier is required and specifies which ccag-id on

.a | .b — The .a and .b portion of the CCAG SAP identifier is required and is used to define the CCA

7750 SR OS Services Guide

Epipe SAP on page 1485

VPLS SAP on page 1487

IES SAP on page 1489

VPRN SAP on page 1490

which the SAP must be created. The specified ccag-id must exist on the system or the SAP

creation will fail. The leading dash must be included as a separator between ccag and the ccag-id.

-1 (dash 1) to -8 (dash 8)

bandwidth path with will be associated with the SAP. The path association must be specified and

.a and .b are mutually exclusive. The .a designation identifies the SAP as being on the Alpha path

and the .b designation identifies the SAP as being on the Beta path. The paired SAP or network

Versatile Service Module