All MIBs › ADN-MIB › adnPmdNodeKindOfPmd
adnPmdNodeKindOfPmd
Module: ADN-MIB
OID (symbolic): ADN-MIB::adnPmdNodeKindOfPmd
OID (numeric): 1.3.6.1.4.1.637.3.1.5.18.1.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: This defines the type of post mortem dump (PMD) to execute. This variable applies at the node level.
min : post mortem dump will be minimum (only the failure ~~~ context is provided) at the board and processor . levels, unless the values of adnPmdBoardKindOfPmd . and adnPmdProcessorKindOfPmd are short, long or . full. . In this case, the more complete PMD is chosen.
short : post mortem dump will be short at the board and ~~~~~ processor levels, unless the values of . adnPmdBoardKindOfPmd and adnPmdProcessorKindOfPmd . are long or full. . In this case, the more complete PMD is chosen. . Short means only the memory areas belonging to the . faulty application and explicitly declared for the . post mortem dump are extracted from the target . memory.
long : post mortem dump will be long at the board and ~~~~ processor levels, unless the values of . adnPmdBoardKindOfPmd and adnPmdProcessorKindOfPmd . is full. . In this case, the full PMD is chosen. . Long means all the memory areas explicitly declared . by the applications for the post mortem dump are . extracted from the target memory.
full : post mortem dump will be full (entire memory) ~~~~ at the board and processor levels, no matter what . the values are for adnPmdBoardKindOfPmd and . adnPmdProcessorKindOfPmd, no matter what the memory . areas declared by the applications are.
free : the post mortem dump will be processed at the board ~~~~ and processor levels according to the values of the . adnPmdBoardKindOfPmd and adnPmdProcessorKindOfPmd . objects.
What is adnPmdNodeKindOfPmd?
This read-write OID defines the scope of post mortem dump collection at the node level, with options like minimum, short, long, or full to control how much diagnostic data is captured. Network engineers adjust this setting based on available storage space and diagnostic needs, increasing detail when working on complex failures. For example, setting this to 'minimum' captures only the failure context to conserve storage, while 'full' captures everything.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.637.3.1.5.18.1.1.2 snmpwalk -v2c -c public <target> ADN-MIB::adnPmdNodeKindOfPmd
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.637.3.1.5.18.1.1.2.1 snmpget -v2c -c public <target> ADN-MIB::adnPmdNodeKindOfPmd.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.637.3.1.5.18.1.1.2.1 i <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> adnPmdNodeKindOfPmd.1
Start monitoring Ascom Timeplex ADN multiplexers (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ADN-MIB::adnPmdNodeKindOfPmd OID value, configure state conditions and alerts, and monitor any Ascom Timeplex ADN multiplexers (legacy) from a single console.
OID Breakdown
Upper-level ancestors (6 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 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.637 | alcatel | ADN-MIB |
| 1.3.6.1.4.1.637.3 | adn | ADN-MIB |
| 1.3.6.1.4.1.637.3.1 | adnMIB | ADN-MIB |
| 1.3.6.1.4.1.637.3.1.5 | adnProprietary | ADN-MIB |
| 1.3.6.1.4.1.637.3.1.5.18 | adnPmdMIB | ADN-MIB |
| 1.3.6.1.4.1.637.3.1.5.18.1 | adnPmdNodeTable | ADN-MIB |
| 1.3.6.1.4.1.637.3.1.5.18.1.1 | adnPmdNodeEntry | ADN-MIB |
| 1.3.6.1.4.1.637.3.1.5.18.1.1.2 | adnPmdNodeKindOfPmd | ADN-MIB |