TMU-MIB :: fibTmuPortsAllowedAddrLoaded

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TMU-MIB › fibTmuPortsAllowedAddrLoaded

fibTmuPortsAllowedAddrLoaded

Module: TMU-MIB

OID (symbolic): TMU-MIB::fibTmuPortsAllowedAddrLoaded

OID (numeric): 1.3.6.1.4.1.22.60.5.29.1.26

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This is the status of fibTmuPortsAllowedAddr. When reading, the possible values are as follows: addr-not-loaded indicates the value in fibTmuPortsAllowedAddr is meaningless. No security address has been loaded for this port. loaded-not-active indicates the value in fibTmuPortsAllowedAddr is stored in non volatile memory but security action for this port is not active. This happens when address is loaded while security action for the Tmu system is disabled (fibTmuSecurityModeRun has bit0 reset). loaded-and-active indicates the value in fibTmuPortsAllowedAddr is loaded in non volatile memory and security is active on this port. This means that if a station is directly connected to this port then it must have the specified physical address or this port will automatically close. As for writing, this object can be written only if its value is either 'loaded-not-active' or 'loaded-and-active' and the only value allowed is addr-not-loaded. In that case, 'fibTmuPortsAllowedAddr' is erased from the non-volatile memory and 'fibTmuNumStationLeft' is incremented. If port has been closed because of security (fibTmuPortsPortStatus had bit9 set) then it will open (provided it has not been closed because of some other reason).

What is fibTmuPortsAllowedAddrLoaded?

This reports the status of fibTmuPortsAllowedAddr: addr-not-loaded (no security address configured for this port, so the address value is meaningless), loaded-not-active (an address is stored but security enforcement isn't currently active for the system), or a further loaded-and-active state per the source text. Admins check it to confirm whether a configured port-security address is actually being enforced right now versus just stored for later. For example, loaded-not-active would explain why an unauthorized device was still able to join a port that has an allowed address configured.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.22.60.5.29.1.26
snmpwalk -v2c -c public <target> TMU-MIB::fibTmuPortsAllowedAddrLoaded

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.22.60.5.29.1.26.1
snmpget -v2c -c public <target> TMU-MIB::fibTmuPortsAllowedAddrLoaded.1

Set instance 1 (SNMPv2c):

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

Start monitoring Legacy networking equipment, enterprise OID 22 fibronics (firmware inventory/fault-handling status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TMU-MIB::fibTmuPortsAllowedAddrLoaded OID value, configure state conditions and alerts, and monitor any Legacy networking equipment, enterprise OID 22 fibronics (firmware inventory/fault-handling status) 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.22spartacusCMU-MIB
Numeric OIDNameModule
1.3.6.1.4.1.22.60tmuTMU-MIB
1.3.6.1.4.1.22.60.5tmuPortsTMU-MIB
1.3.6.1.4.1.22.60.5.29fibTmuPortsTauTableTMU-MIB
1.3.6.1.4.1.22.60.5.29.1fibTmuPortsTauEntryTMU-MIB
1.3.6.1.4.1.22.60.5.29.1.26fibTmuPortsAllowedAddrLoadedTMU-MIB