Configuring global service entities with CLI

Use the following CLI syntax to create and input customer information:

config>service# customer customer-id [create]
    — contact contact-information
    — description description-string
    — multi-service-site customer-site-name [create]
        — assignment {port port-id | card slot}
        — description description-string
        — egress
        — egress
            — agg-rate
                — burst-limit size [bytes | kilobytes]
                — limit-unused-bandwidth
                — queue-frame-based-accounting
                — rate kilobits-per-second
            — policer-control-policy name
                — scheduler-override
                — scheduler scheduler-name [create]
                    — parent {[weight weight] [cir-weight cir-weight]}
                    — rate pir-rate [cir cir-rate]
                — scheduler-policy scheduler-policy-name
        — ingress
            — scheduler-override
                — scheduler scheduler-name [create]
                    — parent {[weight weight] [cir-weight cir-weight]}
                    — rate pir-rate [cir cir-rate]
            — scheduler-policy scheduler-policy-name
    — phone phone-number

The following displays a basic customer account configuration.

A:ALA-12>config>service# info
-------------------------------------------
...
       customer 5 create
           description "Nokia Customer"
           contact "Technical Support"
           phone "650 555-5100"
       exit
...
-------------------------------------------
A:A:ALA-12>config>service#

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#

Use the following CLI syntax to create an SDP and select an encapsulation type. If gre or mpls is not specified, the default encapsulation type is gre.

When specifying MPLS SDP parameters, specify an LSP or enable LDP. There cannot be two methods of transport in a single SDP except if the mixed-lsp command is specified. If an LSP name is specified, then RSVP is used for dynamic signaling within the LSP.

LSPs are configured in the config>router>mpls context. See the 7450 ESS, 7750 SR, 7950 XRS, and VSR MPLS Guide MPLS Configuration Guide for configuration and command information.

Use the following CLI syntax to create a GRE SDP or an MPLS SDP:

config>service>sdp sdp-id [gre | mpls] create
    — adv-mtu-override
    — description description-string
    — far-end ip-address
    — keep-alive 
        — hello-time seconds
        — hold-down-time seconds
        — max-drop-count count
        — message-length octets
        — timeout timeout
        — no shutdown 
                — ldp 		(only for MPLS SDPs)
                — lsp lsp-name [lsp-name]		(only for MPLS SDPs)
    — path-mtu octets
    — signaling {off | tldp}
    — no shutdown 

The following displays an example of a GRE SDP, an LSP-signaled MPLS SDP, and an LDP-signaled MPLS SDP configuration.

A:ALA-12>config>service# info
-------------------------------------------
...
        sdp 2  create
            description "GRE-10.10.10.104"
            far-end 10.10.10.104
            keep-alive
                shutdown
            exit
            no shutdown
        exit
        sdp 8 mpls create
            description "MPLS-10.10.10.104"
            far-end 10.10.10.104
            lsp "to-104"
            keep-alive
                shutdown
            exit
            no shutdown
        exit
        sdp 104 mpls create
            description "MPLS-10.10.10.94"
            far-end 10.10.10.94
            ldp
            keep-alive
                shutdown
            exit
            no shutdown
        exit
...
-----------------------------------------
A:ALA-12>config>service#