Option: Reserving LSP Bandwidth for a Layer 2 Circuit
You can specify the amount of bandwidth in bytes per second that must be available on an LSP for a specific Layer 2 circuit. By using a bandwidth constraint for a Layer 2 circuit, the router performs a type of call admission control. If an LSP exists that contains the required bandwidth, the Layer 2 circuit is established. If the bandwidth is not available on an LSP, the Layer 2 circuit is not established.
To configure bandwidth requirements for a Layer 2
circuit, include the bandwidth statement at the [edit
protocols mpls label-switched-path lsp-name] hierarchy level and the [edit protocols l2circuit neighbor ip-address interface interface-name] hierarchy level.
[edit]
protocols {
mpls {
label-switched-path lsp-name {
bandwidth traffic-class bytes-per-second;
}
}
l2circuit {
neighbor ip-address {
interface interface-name {
bandwidth bytes-per-second;
}
}
}
}
You can also assign minimum bandwidth requirements
for class-of-service (CoS) queues within a Layer 2 circuit and
its corresponding LSP. Class type (CT) queues 0, 1, 2, and 3 in a
Layer 2 circuit or LSP correspond to the standard four CoS queues
available on M Series, MX Series, and T Series routers.
To enable mapping of class type queues to the standard CoS queues,
include the bandwidth-model statement at the [edit
protocols mpls diffserv-te] hierarchy level. To assign specific
bandwidth requirements to each class type queue, include the ct0, ct1, ct2, and ct3 statements
at the [edit protocols mpls label-switched-path lsp-name bandwidth] hierarchy level and the [edit protocols l2circuit
neighbor ip-address interface interface-name bandwidth] hierarchy level.
[edit]
protocols {
mpls {
diffserv-te {
bandwidth-model extended-mam;
}
label-switched-path lsp-name {
bandwidth {
ct0 100m;
ct1 100m;
ct2 50m;
ct3 5m;
}
}
}
l2circuit {
neighbor ip-address {
interface interface-name {
bandwidth {
ct0 100m;
ct1 100m;
ct2 50m;
ct3 5m;
}
}
}
}
}
