Specifications

Table Of Contents
2-560
Cisco SCE 2000 and SCE 1000 CLI Command Reference
OL-26797-03
Chapter 2 CLI Command Reference
virtual-links index direction
The virtual links solution consists of three separate stages in three different components of the Cisco
Service Control solution:
Create and apply a virtual links policy with the template Global Controllers.
The policy is managed and applied via the GUI or API.
Create the virtual links and optionally set any specific bandwidth configuration in the Global
Controllers.
Virtual links are created and managed in the SCE via a set of CLI commands.
Set the virtual link names in the CM.
The virtual link names are set using a command line utility (CLU) in the CM. These names are used
in the the Virtual Links Reports.
Direction
Virtual links are directional. In the CLI commands, a virtual link is always identified by both the index
number assigned to the virtual link and the direction (upstream or downstream).
Always use the direction keyword and specify upstream or downstream.
Global Controller (GC) Templates
The virtual links policy created in the SCA BB console specifies Global Controllers that will be used as
bandwidth templates for the virtual links. When a new virtual link is created using this command, it
receives a set of the directional template VL Global Controllers with their PIR values as configured in
the SCA BB console.
In some cases, you may want to modify the PIR values of a particular template GC for use with a
particular virtual link:
Use the set-PIR keyword with the desired PIR value to change the PIR value of a specified GC
associated with a specified virtual link.
Use the reset-PIR keyword with no PIR values to reset the PIR values of a specified GC to the
original values, as configured via the console.
Global Controllers -Relative Index
To specify the GC, use the gc keyword and then indicate the relative GC index. This is the number of the
relevant GC as found in the GC configuration for the specified direction. Note that GC numbering starts
at 0 for the default BWC in each direction, so the third user-configured GC, for example, is number ‘3’.
In the GC configuration pictured below, the relative index for the P2P GC for upstream is ‘2’ and for
downstream is ‘3’.
Note Each GC also has an absolute index. Referring to the configuration below, you see that there are six
configured GCs altogether, each of which is identified internally by a unique index. This absolute index
does not concern us when identifying a particular GC in these commands.