lcsLossMeasurementPriority
LCOS-SX-MIB ·
.1.3.6.1.4.1.2356.14.2.26.15.4
Object
The priority to be inserted as PCP bits in TAG (if any). In case of enable of Continuity Check and Loss Measurement both implemented on SW based CCM, 'Priority' has to be the same. range:0-7
Context
- MIB
- LCOS-SX-MIB
- OID
.1.3.6.1.4.1.2356.14.2.26.15.4- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- lcsPerformanceMonitor
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'LCOS-SX-MIB' -M '/opt/observium/mibs/lancom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LCOS-SX-MIB::lcsLossMeasurementPriority.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'LCOS-SX-MIB' -M '/opt/observium/mibs/lancom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'LCOS-SX-MIB::lcsLossMeasurementPriority'
Syntax
- Source
- SNMPv2-SMIInteger32
- Base type
Integer32
Values & Constraints
Type Constraints
range: -2147483648..2147483647