Configure Administrative Groups
Administrative groups, also known as link coloring or resource class, are manually assigned attributes that describe the "color" of links, such that links with the same color conceptually belong to the same class. You can use administrative groups to implement a variety of policy-based LSP setups.
Administrative groups are meaningful only when constrained-path LSP computation
is enabled.
Administrative groups require three levels of configuration. First, configure a table of group names:
admin-groups {
group-name group-value;
}
You can configure this statement at the following hierarchy levels:
You can assign up to 32 names and values (in the range 0 through 31), which define a series of names and their corresponding values. The administrative names and values must be identical across all routers within a single domain.
To configure administrative groups, follow these steps:
- Define multiple levels of service quality:
protocols {
mpls {
admin-groups {
best-effort 1;
copper 2;
silver 3;
gold 4;
violet 5;
}
}
}
You can configure these statement at the following hierarchy levels:
- Define the administrative groups to which an interface belongs. You can assign multiple groups to an interface.
protocols {
mpls {
interface interface name {
admin-group [group-namegroup-name...];
}
}
}
You can configure these statement at the following hierarchy levels:
If you do not include the admin-group statement, an interface does not belong to any group.
IGPs use the group information to build link-state packets, which are then flooded throughout the network, providing information to all nodes in the network. At any router, the IGP topology, as well as administrative groups of all the links, is available.
Changing the interface's administrative group affects only new LSPs. Existing LSPs on the interface are not preempted or recomputed to keep the network stable. If LSPs need to be removed because of a group change, issue the clear rsvp session command.
- Configure an administrative group constraint for each LSP or for each primary or secondary LSP path:
protocols {
mpls {
label-switched-path lsp-path-name {
to address;
...
admin-group {
exclude [group-namegroup-name... ];
include [group-namegroup-name... ];
}
primary path-name {
admin-group {
exclude [group-namegroup-name... ];
include [group-namegroup-name... ];
}
}
secondary path-name {
admin-group {
exclude [group-namegroup-name... ];
include [group-namegroup-name... ];
}
}
}
}
}
For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement.
If you omit the include or exclude statements, the path computation proceeds unchanged. The path computation is based on the constrained-path LSP computation. If you configure an exclude list, all chosen links must not have a color in the exclude list. If you configure an include list, all chosen links must have at least one color in the include list. Links that have no color are automatically disqualified by any include or exclude list.
 |
NOTE: Changing the LSP's administrative group causes an immediate recomputation of the route; therefore, the LSP might be rerouted. |