Multi-service sites create a virtual scheduler hierarchy and making it available to queues and, at egress only, policers on multiple Service Access Points (SAPs). The ingress and egress scheduler-policy commands on the SAP are mutually exclusive with the SAP multi-service-site command. The multi-service customer site association must be removed from the SAP before local scheduler polices may be applied.
After a multi-service site is created, it must be assigned to a chassis slot or port.
Use the following CLI syntax to configure customer multi-service sites.
config>service# customer customer-id
— multi-service-site customer-site-name
— assignment {port port-id | card slot}
— description description-string
— egress
— agg-rate-limit agg-rate
— scheduler-policy scheduler-policy-name
— ingress
— scheduler-policy scheduler-policy-name
The following displays a customer’s multi-service-site configuration.
A:ALA-12>config>service# info
-------------------------------------------
..
customer 5 create
multi-service-site "EastCoast" create
assignment card 4
ingress
scheduler-policy "alpha1"
exit
exit
multi-service-site "WestCoast" create
assignment card 3
egress
scheduler-policy "SLA1"
exit
exit
description "Nokia Customer"
contact "Technical Support"
phone "650 555-5100"
exit
...
-------------------------------------------
A:ALA-12>config>service#
The following shows an example of a customer’s 7450 ESS multi-service-site configuration.
A:ALA-12>config>service# info
-------------------------------------------
..
customer 5 create
multi-service-site "EastCoast" create
assignment card 4
ingress
scheduler-policy "alpha1"
exit
exit
multi-service-site "WestCoast" create
assignment card 3
egress
scheduler-policy "SLA1"
exit
exit
description "Nokia Customer"
contact "Technical Support"
phone "650 555-5100"
exit
...
-------------------------------------------
A:ALA-12>config>service#