MplsDsTeIfUnresBwEntry |
|
SEQUENCE |
|
|
|
|
mplsDsTeIfUnresBwTEClass0 |
MplsBitRate |
|
|
mplsDsTeIfUnresBwTEClass1 |
MplsBitRate |
|
|
mplsDsTeIfUnresBwTEClass2 |
MplsBitRate |
|
|
mplsDsTeIfUnresBwTEClass3 |
MplsBitRate |
|
|
mplsDsTeIfUnresBwTEClass4 |
MplsBitRate |
|
|
mplsDsTeIfUnresBwTEClass5 |
MplsBitRate |
|
|
mplsDsTeIfUnresBwTEClass6 |
MplsBitRate |
|
|
mplsDsTeIfUnresBwTEClass7 |
MplsBitRate |
|
MplsDsTeTunEntry |
|
SEQUENCE |
|
|
|
|
mplsDsTeTunTunnelClassType |
Unsigned32 |
0..7 |
mplsDsTeIfBCEntry |
1.3.6.1.2.1.10.9999.8.1.3.1 |
A row is created in this table automatically by an LSR for every
interface capable of supporting MPLS DS-TE if this MIB is
implemented. This relationship exists because each MPLS-enabled
interface must participate in DS-TE. Therefore, this table
AUGMENTS corresponding entries in the mplsInterfaceConfTable.
Each entry in this table corresponds specified the bandwidth
constraint associated with the corresponding MPLS interface, in
Kbps. [However, if the mplsInterfaceConfTable has a conceptual
row with index 0, all of the bandwidth constraints corresponding
to that row will be no significance and will can not be modified]
By default, all the bandwidth constraint other than BC0 is set
to 0 Kbps. The BC0 by default is set to the maximum link
bandwidth.
Bandwidth constraints defined in this table are significant only if
the corresponding Class-Type is defined in the
mplsDsTeClassTable. Furthermore, the relationship of the
Class-Types with the bandwidth constraints defined in this table is
determined by the Bandwidth Constraint Model indicated in
mplsDsTeBandwidthConstraintModel.
For example, if the Russian Dolls Bandwidth Constraint Model
[DSTE-RUSSIAN] is used then the LSR must ensure that BCi is
configured smaller or equal to BCj, where i is greater than j, for
all significant BCs.
On the other hand Maximum Allocation Model [DSTE-MAM] does not have
any such restrictions. MIB implementor need to refer to the
document describing the BC Models for specific details.
Bandwidth Constraints defined in this table are significant only
if their corresponding CTs appear in the mplsDsTeClassTable. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MplsDsTeIfBCEntry |
|
|
mplsDsTeIfLOMEntry |
1.3.6.1.2.1.10.9999.8.1.4.1 |
A row is created in this table automatically by an LSR for every
interface capable of supporting MPLS and is enable to do
so, since it AUGMENTs the mplsInterfaceConfTable.
According to the [DSTE-REQ] draft, an administrator can deploy
upto 8 Class-Types. It also allows the tweaking of the overbooking
ratio for each of these Class-Types on a per interface basis.
Each entry in this table allows the administrator to configure a
overbooking factor on a per-link per-class-type basis. [However,
if the mplsInterfaceConfTable has a conceptual row with index 0,
all of the LOMs corresponding to that row will be no
significance and will can not be modified]
The overbooking ration defined in this entry, will be significant
for different Class-Types, only when the corresponding Class-Type
is supported in the LSR (see the mplsDsTeClassTable).
Additionally, agent might have to enforce other requirements as
per the Bandwidth Constraint Model.
The units of the bandwidth constraints are in terms of percentage
(%) of the actual bandwidth requested by the connection.
A LOM with value 100 indicates no overbooking in use
<100 indicates underbooking in use
>100 indicates overbooking in use.
By default, all the overbooking multipliers defined in this table
will be initialized to 100 (i.e. no overbooking). |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MplsDsTeIfLOMEntry |
|
|
mplsDsTeClassEntry |
1.3.6.1.2.1.10.9999.8.1.5.1 |
An entry in this table represents a mapping between the TE-Class
and pair.
The [DSTE-PROTO] indicates that a DS TE domain can support 8
TE-Classes defined, by the pair. An
administrator must defined the TE-Class he wants to support in
the domain by creating appropriate entries in this table. All
the LSRs in the domain, must have the same set of entries.
Besides defining the TE-Classes, the entries in this table also
indicate the active Class-Types within the LSR and the connection
priorities it can support. More specifically:-
The LSR is considered to support a particular Class-Type only if
it appears in the definition of the 8 possible TE-Classes.
A (setup/holding) priority associated with a LSP, on a LSR is
consider to be valid only if it appears as a pair with the
class-type of the connection.
An empty mplsDsTeClassTable effectively disables DSTE and TE on
the LSR and no (DSTE/TE) LSPs can be established on the LSR.
There are no other restrictions on how any of the 8 Class-Types can
be paired up with any of the 8 preemption priorities to form a TE-
class[DSTE-PROTO]. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MplsDsTeClassEntry |
|
|
mplsDsTeIfUnresBwEntry |
1.3.6.1.2.1.10.9999.8.1.6.1 |
A row is created in this table automatically by an LSR for every
interface capable of supporting MPLS and is enable to do
so, since it AUGMENTs the mplsInterfaceConfTable.
Each entry in this table presents the unreserved / available
bandwidth for different TE-Classes on this interface. [However,
if the mplsInterfaceConfTable has a conceptual row with index 0,
all of the LOMs corresponding to that row will be no
significance and will can not be modified]
When the TE-Class is not supported on the LSR, the corresponding
unreserved bandwidth will be set to zero. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MplsDsTeIfUnresBwEntry |
|
|
mplsDsTeTunEntry |
1.3.6.1.2.1.10.9999.8.1.7.1 |
An entry in this table is created by an LSR for every traffic
engineering tunnel instance capable of supporting MPLS
DiffServ-Aware Traffic Engineering. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MplsDsTeTunEntry |
|
|
mplsDsTeLspEntry |
1.3.6.1.2.1.10.9999.8.1.8.1 |
An entry in this table is created by an LSR for every LSP capable of
supporting MPLS DiffServ-Aware Traffic Engineering. Specifically, an
entry in this table must correspond to an entry in the mplsXCTable
from the MPLS-LSR-MIB [MPLS-LSR-MIB]. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MplsDsTeLspEntry |
|
|