OID reference
1.3.6.1.4.1.8708.2.27.2.2.1.1.19
Band-width in VC-3 or VC-4. The parameter is interpreted as VC-3 or VC-4 depending on the traffic combination: - VC-3 is used in framedGbEx10 - VC-4 is used in framedGbEx10Vc4
Identification
{1 3 6 1 4 1 8708 2 27 2 2 1 1 19}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.
Published row index: clientIfIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.8708.2.27.2.2.1.1.19
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
clientIfBandWidth OBJECT-TYPE
SYNTAX Integer32 (0..48)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Band-width in VC-3 or VC-4.
The parameter is interpreted as VC-3 or VC-4
depending on the traffic combination:
- VC-3 is used in framedGbEx10
- VC-4 is used in framedGbEx10Vc4
"
DEFVAL { 0 }
::= { clientIfEntry 19 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Band-width in VC-3 or VC-4. The parameter is interpreted as VC-3 or VC-4 depending on the traffic combination: - VC-3 is used in framedGbEx10 - VC-4 is used in framedGbEx10Vc4
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: clientIfBandWidth
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"clientIfBandWidth",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"48",
")",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"Band-width in VC-3 or VC-4. The parameter is interpreted as VC-3 or VC-4 depending on the traffic combination: - VC-3 is used in framedGbEx10 - VC-4 is used in framedGbEx10Vc4 \"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"clientIfEntry",
"19",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
48
]
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Band-width in VC-3 or VC-4. The parameter is interpreted as VC-3 or VC-4 depending on the traffic combination: - VC-3 is used in framedGbEx10 - VC-4 is used in framedGbEx10Vc4"
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}Vendor MIB copy from the Observium Community archive.
Module: LUM-CLIENT-MIB
See published definition above
{'LUM-TC': ['FaultStatus', 'MgmtNameString', 'SubrackNumber', 'SlotNumber', 'PortNumber', 'BoardOrInterfaceOperStatus', 'BoardOrInterfaceAdminStatus', 'CommandString', 'LambdaFrequency', 'SignalFormat', 'TrxMedia', 'ObjectProperty', 'BerLevelMTOSI', 'OpticalLayerMappingType', 'LaneFrequency', 'TrxRxState', 'TrxTxState', 'PhysicalLayerMappingType', 'SignalDirection', 'SignalStatusWithNA', 'EnableDisable', 'OnOff', 'InterfaceType'], 'LUM-REG': ['lumModules', 'lumClientMIB'], 'SNMPv2-TC': ['DisplayString', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Integer32', 'NOTIFICATION-TYPE', 'Gauge32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP']}Related source files and packages:
Registration