FAST-ETHERNET-MIB :: ctFastEthernetReceivedTechnologyAbility

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › FAST-ETHERNET-MIB › ctFastEthernetReceivedTechnologyAbility

ctFastEthernetReceivedTechnologyAbility

Module: FAST-ETHERNET-MIB

OID (symbolic): FAST-ETHERNET-MIB::ctFastEthernetReceivedTechnologyAbility

OID (numeric): 1.3.6.1.4.1.52.4.1.2.9.1.1.1.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Indicates the advertised ability of the remote hardware, or link partner. The value of this object is the logical OR of all supported technologies. Where each technology is given the values below:

other(1) Undefined Auto-Negotiation(2) Auto-Negotiation/Parallel Detection Not-Detected(4) Link Partner does not support Auto-Negotiation 10BASE-T(8) 10BASE-T 10BASE-TFD(16) Full duplex 10BASE-T 100BASE-TX(32) 100BASE-TX as defined in clause 25 100BASE-TXFD(64) Full Duplex 100BASE-TX 100BASE-T4(128) 100BASE-T4 as defined in clause 23 100Base-FX(256) 100Base-FX 100Base-FXFD(512) Full Duplex 100Base-FX

For example a port which supports 100Base-TX(32), 100Base-TXFD(64), would have a value of 98(32 + 64 + Auto-Negotiation(2)).

A read should always include Auto-Negotiation(2), unless the link partner does not support auto-negotiation, at which time the value will be Not-Detected(4) or auto-negotiation is disabled(or not supported) for this port at which time the value will be other(1).

What is ctFastEthernetReceivedTechnologyAbility?

This read-only bitmask reports the technology abilities advertised by the remote link partner during auto-negotiation, using the same bit codes, with Not-Detected(4) meaning the partner doesn't support auto-negotiation and other(1) meaning auto-negotiation is disabled locally. Admins use it to diagnose speed/duplex mismatches by comparing what the local port advertised against what the far end actually offered. For example, ctFastEthernetReceivedTechnologyAbility reading 4 (Not-Detected) explains why a link settled into half-duplex — the far-end device doesn't support auto-negotiation at all.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.52.4.1.2.9.1.1.1.7
snmpwalk -v2c -c public <target> FAST-ETHERNET-MIB::ctFastEthernetReceivedTechnologyAbility

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.52.4.1.2.9.1.1.1.7.1
snmpget -v2c -c public <target> FAST-ETHERNET-MIB::ctFastEthernetReceivedTechnologyAbility.1

Start monitoring Cabletron Systems/Enterasys managed Ethernet switch (100BASE-T Fast Ethernet negotiation) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the FAST-ETHERNET-MIB::ctFastEthernetReceivedTechnologyAbility OID value, configure state conditions and alerts, and monitor any Cabletron Systems/Enterasys managed Ethernet switch (100BASE-T Fast Ethernet negotiation) from a single console.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.52cabletronCabletron-MIB
1.3.6.1.4.1.52.4mibsCT-PRIORITY-QUEUING
1.3.6.1.4.1.52.4.1ctronCTRON-ISDN-CONFIGURATION-MIB
1.3.6.1.4.1.52.4.1.2ctDataLinkCTRON-ISDN-CONFIGURATION-MIB
1.3.6.1.4.1.52.4.1.2.9ctFastEthernetCTRON-MIB-NAMES
Numeric OIDNameModule
1.3.6.1.4.1.52.4.1.2.9.1ctFastEthernetCtlFAST-ETHERNET-MIB
1.3.6.1.4.1.52.4.1.2.9.1.1ctFastEthernetCtlTableFAST-ETHERNET-MIB
1.3.6.1.4.1.52.4.1.2.9.1.1.1ctFastEthernetCtlEntryFAST-ETHERNET-MIB
1.3.6.1.4.1.52.4.1.2.9.1.1.1.7ctFastEthernetReceivedTechnologyAbilityFAST-ETHERNET-MIB