All MIBs › CISCO-WIRELESS-P2MP-PHY-MIB › p2mpLastPhyFailureType
p2mpLastPhyFailureType
Module: CISCO-WIRELESS-P2MP-PHY-MIB
OID (symbolic): CISCO-WIRELESS-P2MP-PHY-MIB::p2mpLastPhyFailureType
OID (numeric): 1.3.6.1.4.1.9.9.170.1.1.1.1.1.8
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: This object indicates the last physical link failure that resulted in a p2mpRadioPhyFailNotification trap.
none(1) - no failure
p2mpHwConfigUnsupported(2) - The radio subsystem has detected that the configuration requested is not supported by the hardware. The p2mpLastPhyFailureReason variable will indicate which configuration parameter is not supported.
p2mpHwConfigMismatch(3) - The radio subsystem has detected that the combination of the configuration parameters requested is inconsistent and cannot be supported. The p2mpLastPhyFailReason variable will indicate the configuration parameter that causes the mismatch.
p2mpHwInitFailure(4) - The radio subsystem has failed to initialize the hardware. This implies that there is a critical error condition in the associated hardware. The p2mpLastPhyFailReason specifies the reason why the init failed.
p2mpHostIfCommLinkError(5) - The host could not communicate with the IF module.
p2mpAutoCableCompFailure(6) - Failed to achieve automatic cable compensation due to loss of Tx signal.
What is p2mpLastPhyFailureType?
A read-only INTEGER enumeration recording the type of the most recent physical-link failure that caused a p2mpRadioPhyFailNotification trap, such as an unsupported or mismatched hardware configuration, or a hardware initialization failure. This gives an admin an immediate categorized diagnosis of what specifically went wrong at the physical layer, without having to separately investigate from scratch after receiving the failure trap. For example, an admin who received a p2mpRadioPhyFailNotification could read p2mpLastPhyFailureType and see p2mpHwConfigMismatch, immediately narrowing the investigation to a hardware and configuration mismatch rather than a purely software or environmental issue.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.170.1.1.1.1.1.8 snmpwalk -v2c -c public <target> CISCO-WIRELESS-P2MP-PHY-MIB::p2mpLastPhyFailureType
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.170.1.1.1.1.1.8.1 snmpget -v2c -c public <target> CISCO-WIRELESS-P2MP-PHY-MIB::p2mpLastPhyFailureType.1
Start monitoring Cisco wireless P2MP radio (head-end and subscriber-unit, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WIRELESS-P2MP-PHY-MIB::p2mpLastPhyFailureType OID value, configure state conditions and alerts, and monitor any Cisco wireless P2MP radio (head-end and subscriber-unit, legacy) from a single console.
OID Breakdown
Upper-level ancestors (8 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.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.170 | ciscoWirelessPhyMIB | CISCO-WIRELESS-P2MP-PHY-MIB |
| 1.3.6.1.4.1.9.9.170.1 | p2mpRadioObjects | CISCO-WIRELESS-P2MP-PHY-MIB |
| 1.3.6.1.4.1.9.9.170.1.1 | p2mpRadioBaseObjects | CISCO-WIRELESS-P2MP-PHY-MIB |
| 1.3.6.1.4.1.9.9.170.1.1.1 | p2mpPhyConfigGroup | CISCO-WIRELESS-P2MP-PHY-MIB |
| 1.3.6.1.4.1.9.9.170.1.1.1.1 | p2mpRadioPhyTable | CISCO-WIRELESS-P2MP-PHY-MIB |
| 1.3.6.1.4.1.9.9.170.1.1.1.1.1 | p2mpRadioPhyEntry | CISCO-WIRELESS-P2MP-PHY-MIB |
| 1.3.6.1.4.1.9.9.170.1.1.1.1.1.8 | p2mpLastPhyFailureType | CISCO-WIRELESS-P2MP-PHY-MIB |