Status in source: current.
Names: fsQoSEgressExpDot1pMapProfileTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsQoSEgressExpDot1pMapProfileTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"FsQoSEgressExpDot1pMapProfileEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"This object specifies the table containing Egress MPLS Profile Table. Currently table will store the internal Priority to Experimental and DOT1P value. When this profile is mapped to an interface, it will be applied to all the tunnels created on top of that interface. Default mapping is given below. Internal Priority | Exp | DOT1P 0 | 0 | 0 1 | 1 | 1 2 | 2 | 2 3 | 3 | 3 4 | 4 | 4 5 | 5 | 5 6 | 6 | 6 7 | 7 | 7 This profile is meant only for egress. This creates a profile which maps internal priority to both EXP and DOT1P for the specific label. This profile if mapped on an interface, will be effective for all tunnels. This profile will not apply for egress DOT1P mapping of the interface; if DOT1P profile alone need to be mapped to the interface, then egress DOT1P profile needs to be attached separately. Currently this Profile table is supported for BCM and its not supported for Marvell. Similarly , if any other Chipset supports profile concept, we can use new table else the user has to use Old Priority mapping table.\"",
"::=",
"{",
"fsQoSSystem",
"12",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"FsQoSEgressExpDot1pMapProfileEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object specifies the table containing Egress MPLS Profile Table. Currently table will store the internal Priority to Experimental and DOT1P value. When this profile is mapped to an interface, it will be applied to all the tunnels created on top of that interface. Default mapping is given below. Internal Priority | Exp | DOT1P 0 | 0 | 0 1 | 1 | 1 2 | 2 | 2 3 | 3 | 3 4 | 4 | 4 5 | 5 | 5 6 | 6 | 6 7 | 7 | 7 This profile is meant only for egress. This creates a profile which maps internal priority to both EXP and DOT1P for the specific label. This profile if mapped on an interface, will be effective for all tunnels. This profile will not apply for egress DOT1P mapping of the interface; if DOT1P profile alone need to be mapped to the interface, then egress DOT1P profile needs to be attached separately. Currently this Profile table is supported for BCM and its not supported for Marvell. Similarly , if any other Chipset supports profile concept, we can use new table else the user has to use Old Priority mapping table."
],
null,
null,
null,
null
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: ARICENT-DIFFSERV-MIB
See published definition above
Module imports
{'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'DisplayString', 'TruthValue'], 'SNMPv2-SMI': ['Unsigned32', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Integer32', 'Counter64']}
· Download ARICENT-DIFFSERV-MIB
Related source files and packages: