CT-ELS100-MIB :: kxaddrFlags

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCT-ELS100-MIBkxaddrFlags

kxaddrFlags

Module: CT-ELS100-MIB

OID (symbolic): CT-ELS100-MIB::kxaddrFlags

OID (numeric): 1.3.6.1.4.1.97.8.5.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Flags to describe the use and control of this address entry. Each bit has a different meaning. The NMS must always set either entry-static, entry-none, or entry-mesh; however, for GetRequests, the NMS will see either no bits set (if the entry does not exist), or exactly one of the following bits set: entry-dynamic-local = 30, entry-dynamic-remote = 29, entry-static = 28, entry-other = 27, entry-none = 26, entry-mesh = 25, entry-statistics = 24, Bit 31 is reserved.

Any combination of the restriction bits (bits 23-21) may be set for any type of entry, except entry-other or entry-mesh: entry-no-source = 23, entry-no-multi = 22, Bit 21 is reserved, Bits 20-18 are reserved.

Exactly one of the special entry bits (bits 17-10) must be set for entry-other entries, and none of the bits may be set for other than entry-other entries: entry-all-lmas = 17, entry-any-lma = 16, entry-lma = 15, entry-port = 14, entry-bpdu = 13, entry-reserved = 12, Bits 11-10 are reserved for future expansion. Bits 9-0 are reserved.

What is kxaddrFlags?

This read-write bitmask INTEGER describes the type and control state of a specific address table entry, where on a read exactly one bit among entry-dynamic-local, entry-dynamic-remote, entry-static, entry-other, entry-none, entry-mesh, or entry-statistics will be set, or none if the entry doesn't exist, while on a write the NMS must set specifically entry-static, entry-none, or entry-mesh. An admin distinguishes, for any given address table row, whether it was learned dynamically locally or remotely, configured statically, or serves some other special purpose, by reading this flags field rather than assuming from context. For example, to confirm a MAC address the admin manually added is actually stored as a permanent binding rather than a dynamically learned one, they would read kxaddrFlags for that entry and check that the entry-static bit is set.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.97.8.5.5
snmpwalk -v2c -c public <target> CT-ELS100-MIB::kxaddrFlags

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.97.8.5.5.1
snmpget -v2c -c public <target> CT-ELS100-MIB::kxaddrFlags.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.97.8.5.5.1 i <value>

Start monitoring Cabletron ELS100 series Ethernet switch (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CT-ELS100-MIB::kxaddrFlags OID value, configure state conditions and alerts, and monitor any Cabletron ELS100 series Ethernet switch (legacy) from a single console.

OID Breakdown

Upper-level ancestors (7 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.97sigmaCT-ELS10-27-MIB
Numeric OIDNameModule
1.3.6.1.4.1.97.8els_100CT-ELS100-MIB
1.3.6.1.4.1.97.8.5kxaddrCT-ELS100-MIB
1.3.6.1.4.1.97.8.5.5kxaddrFlagsCT-ELS100-MIB