dataPortCopperForcedConfiguration

CAMBIUM-PTP800-MIB · .1.3.6.1.4.1.17713.8.6.29

Object

scalar Enumeration

This forces the configuration of the copper data 
Ethernet interface rather than using auto negotiation. 
THE CONFIGURATION SHOULD ONLY BE FORCED IF YOU ARE HAVING 
PROBLEMS WITH AUTO NEGOTIATION - AND YOU MUST ENSURE THAT 
YOU CONFIGURE BOTH THIS UNIT AND THE Ethernet PORT TO 
WHICH IT IS CONNECTED IDENTICALLY! WARNING: Duplex 
mismatch may result if both ends of the Ethernet link do 
not have the same settings. Do not use auto negotiation 
together with a fixed setting at the Ethernet link 
partner (other end of the link)

Context

MIB: CAMBIUM-PTP800-MIB
OID: .1.3.6.1.4.1.17713.8.6.29
Type: scalar
Access: readonly
Status: current
Parent: ethernet
Groups: 1

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'CAMBIUM-PTP800-MIB' -M '/opt/observium/mibs/cambium:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CAMBIUM-PTP800-MIB::dataPortCopperForcedConfiguration.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'CAMBIUM-PTP800-MIB' -M '/opt/observium/mibs/cambium:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CAMBIUM-PTP800-MIB::dataPortCopperForcedConfiguration'

Syntax

Enumeration

Values & Constraints

Enumerated Values

`1`	force100MbpsFullDuplex