All MIBs › PDN-MPE-BRIDGE-MIB › mpePdnDot1dTpFdbStatus
mpePdnDot1dTpFdbStatus
Module: PDN-MPE-BRIDGE-MIB
OID (symbolic): PDN-MPE-BRIDGE-MIB::mpePdnDot1dTpFdbStatus
OID (numeric): 1.3.6.1.4.1.1795.2.24.12.21.1.2.1.1.4
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The status of this entry. The meanings of the values are:
other(1) : none of the following. This would include the case where some other MIB object (not the corresponding instance of mpePdnDot1dTpFdbPort, nor an entry in the mpePdnDot1dStaticTable) in being used to determine if and how frames addressed to the value of the corresponding instance of mpePdnDot1dTpFdbAddress are being forwarded.
invalid(2) : this entry is not longer valid (e.g., it was learned but has since
aged-out), but has not yet been flushed from the table.
learned(3) : the value of the corresponding instance of mpePdnDot1dTpFdbPort was learned, and is being used.
self(4) : the value of the corresponding instance of mpePdnDot1dTpFdbAddress represents one of the bridge's addresses. The corresponding instance of mpePdnDot1dTpFdbPort indicates which of the bridge's ports has this address.
mgmt(5) : the value of the corresponding instance of mpePdnDot1dTpFdbAddress is
also the value of an existing instance of mpePdnDot1dStaticAddress.
What is mpePdnDot1dTpFdbStatus?
This read-only enumerated value reports the status of a forwarding database entry: other(1) when some mechanism outside this entry or the static table determines forwarding, invalid(2) when the entry is no longer valid (such as aged out) but not yet flushed, learned(3) when the port value was dynamically learned and is in use, self(4) when the address is one of the bridge's own addresses, or mgmt(5) when the address also exists as a configured static address. Admins use this to distinguish dynamically learned MAC entries from statically configured or bridge-owned ones during troubleshooting. For example, an entry showing self(4) identifies that MAC address as belonging to the bridge itself rather than to an attached host.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.12.21.1.2.1.1.4 snmpwalk -v2c -c public <target> PDN-MPE-BRIDGE-MIB::mpePdnDot1dTpFdbStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.1795.2.24.12.21.1.2.1.1.4.1 snmpget -v2c -c public <target> PDN-MPE-BRIDGE-MIB::mpePdnDot1dTpFdbStatus.1
Start monitoring Paradyne MPE Ethernet expansion module, DSL access multiplexer (802.1D bridging/VLAN forwarding) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PDN-MPE-BRIDGE-MIB::mpePdnDot1dTpFdbStatus OID value, configure state conditions and alerts, and monitor any Paradyne MPE Ethernet expansion module, DSL access multiplexer (802.1D bridging/VLAN forwarding) from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.1795 | pdyn | PDN-HEADER-MIB |
| 1.3.6.1.4.1.1795.2 | pdn_mgmt | PDN-HEADER-MIB |
| 1.3.6.1.4.1.1795.2.24 | paradyne | PDN-HEADER-MIB |
| 1.3.6.1.4.1.1795.2.24.12 | pdn_mpe | PDN-HEADER-MIB |
| 1.3.6.1.4.1.1795.2.24.12.21 | mpe_bridge | PDN-HEADER-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.1795.2.24.12.21.1 | mpePdnBridgeGenericMIBObjects | PDN-MPE-BRIDGE-MIB |
| 1.3.6.1.4.1.1795.2.24.12.21.1.2 | mpePdnDot1dTpFdb | PDN-MPE-BRIDGE-MIB |
| 1.3.6.1.4.1.1795.2.24.12.21.1.2.1 | mpePdnDot1dTpFdbTable | PDN-MPE-BRIDGE-MIB |
| 1.3.6.1.4.1.1795.2.24.12.21.1.2.1.1 | mpePdnDot1dTpFdbEntry | PDN-MPE-BRIDGE-MIB |
| 1.3.6.1.4.1.1795.2.24.12.21.1.2.1.1.4 | mpePdnDot1dTpFdbStatus | PDN-MPE-BRIDGE-MIB |