PTOPO-MIB :: ptopoConnMultiMacSASeen

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PTOPO-MIB › ptopoConnMultiMacSASeen

ptopoConnMultiMacSASeen

Module: PTOPO-MIB

OID (symbolic): PTOPO-MIB::ptopoConnMultiMacSASeen

OID (numeric): 1.3.6.1.2.1.79.1.1.1.1.12

Node type: OBJECT-TYPE

Type: PtopoAddrSeenState

Access: read-only

Description: This object indicates if multiple unicast source MAC addresses have been detected by the agent from the remote connection endpoint, since the creation of this entry.

If this entry has an associated ptopoConnRemoteChassisType and/or ptopoConnRemotePortType value other than 'portIdMacAddr(3)', then the value 'notUsed(1)' is returned.

Otherwise, one of the following conditions must be true:

If the agent has not yet detected any unicast source MAC addresses from the remote port, then the value 'unknown(2)' is returned.

If the agent has detected exactly one unicast source MAC address from the remote port, then the value 'oneAddr(3)' is returned.

If the agent has detected more than one unicast source MAC address from the remote port, then the value 'multiAddr(4)' is returned.

What is ptopoConnMultiMacSASeen?

This read-only PtopoAddrSeenState indicates, per its source description, whether multiple unicast source MAC addresses have been seen on the remote end of this connection since the entry was created, returning notUsed(1) if the row's identifier types aren't MAC-based, unknown(2) if no MAC has been seen yet, oneAddr(3) for exactly one seen, or multiAddr(4) for more than one seen. Admins use a multiAddr(4) result to detect that what was assumed to be a direct point-to-point link is actually behind a hub or unmanaged switch relaying multiple devices' traffic. For example, seeing multiAddr(4) on a port expected to connect directly to a single IP phone would suggest an unauthorized hub or switch has been inserted in between.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.79.1.1.1.1.12
snmpwalk -v2c -c public <target> PTOPO-MIB::ptopoConnMultiMacSASeen

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.79.1.1.1.1.12.1
snmpget -v2c -c public <target> PTOPO-MIB::ptopoConnMultiMacSASeen.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> ptopoConnMultiMacSASeen.1

Start monitoring vendor-neutral, standards-based MIB (physical topology discovery) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PTOPO-MIB::ptopoConnMultiMacSASeen OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB (physical topology discovery) from a single console.

OID Breakdown

Upper-level ancestors (6 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.79ptopoMIBPTOPO-MIB
1.3.6.1.2.1.79.1ptopoMIBObjectsPTOPO-MIB
1.3.6.1.2.1.79.1.1ptopoDataPTOPO-MIB
1.3.6.1.2.1.79.1.1.1ptopoConnTablePTOPO-MIB
1.3.6.1.2.1.79.1.1.1.1ptopoConnEntryPTOPO-MIB
1.3.6.1.2.1.79.1.1.1.1.12ptopoConnMultiMacSASeenPTOPO-MIB