Global Service Configuration Commands
Page 82 7750 SR OS Services Guide
phone
Syntax [no] phone string
Context config>service>customer customer-id
Description This command adds telephone number information for a customer ID.
Default No telephone number information is associated with a customer.
The no form of this command removes the phone number value from the customer ID.
Parameters string — The customer phone number entered as an ASCII string string up to 80 characters. If the
string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within
double quotes. Any printable, seven bit ASCII characters may be used within the string.
multi-service-site
Syntax multi-service-site customer-site-name
no multi-service-site customer-site-name
Context config>service>customer
Description This command creates a new customer site or edits an existing customer site with the customer-site-
name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler
hierarchy. When a site is created, it must be assigned to a chassis slot or port with the exception of the
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.
Default None — Each customer site must be explicitly created.
Parameters customer-site-name — Each customer site must have a unique name within the context of the
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.
To Next Page
Loading...
