Alcatel-Lucent 7750 SR Manual page 1317

Os services guide

Hide thumbs Also See for 7750 SR:

Table of Contents

7750 SR-1 in which the slot is set to 1. When scheduler policies are defined for ingress and egress, the

scheduler names contained in each policy are created according to the parameters defined in the

policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy

and making it available to queues on multiple Service Access Points (SAPs).

The scheduler policy association with the customer site normally prevents the scheduler policy from

being deleted until after the scheduler policy is removed from the customer site. The multi-service-

site object will generate a log message indicating that the association was deleted due to scheduler

policy removal.

When the multi-service customer site is created, an ingress and egress scheduler policy association

does not exist. This does not prevent the site from being assigned to a chassis slot or prevent service

SAP assignment. After the site has been created, the ingress and egress scheduler policy associations

can be assigned or removed at any time.

None — Each customer site must be explicitly created.

customer-site-name: — Each customer site must have a unique name within the context of the

7750 SR OS Services Guide

customer. If customer-site-name already exists for the customer ID, the CLI context changes to

that site name for the purpose of editing the site scheduler policies or assignment. Any

modifications made to an existing site will affect all SAPs associated with the site. Changing a

scheduler policy association may cause new schedulers to be created and existing queues on the

SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing

queues relying on that scheduler to be orphaned.

If the customer-site-name does not exist, it is assumed that an attempt is being made to create a

site of that name in the customer ID context. The success of the command execution depends on

the following:

The maximum number of customer sites defined for the chassis slot has not been met.

The customer-site-name is valid.

The create keyword is included in the command line syntax (if the system requires it).

When the maximum number of customer sites has been exceeded a configuration error occurs;

the command will not execute and the CLI context will not change.

If the customer-site-name is invalid, a syntax error occurs; the command will not execute and the

CLI context will not change.

Valid names consist of any string up to 32 characters long composed of printable, 7-

bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the

entire string must be enclosed within double quotes.

Virtual Private Routed Network Services