HPN-ICF-DVPN-MIB :: hpnicfDvpnMapState

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HPN-ICF-DVPN-MIB › hpnicfDvpnMapState

hpnicfDvpnMapState

Module: HPN-ICF-DVPN-MIB

OID (symbolic): HPN-ICF-DVPN-MIB::hpnicfDvpnMapState

OID (numeric): 1.3.6.1.4.1.11.2.14.11.15.2.57.1.2.5.1.17

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: mapClientInit: The client initiates the map. mapClientBegin: The client begins the process of registering to the server. mapClientAlgreq: The client requests to negotiate the algorithm. mapClientKexReq: The client requests to negotiate the key. mapClientAuthenReq: The client sends authentication information to the server. mapClientConfigReq: The client requests to get some configuration information from the server. Do not support now. mapClientReq: The client requests to register to the server. mapClientSuccess: The client registers to the server successfully. mapServerBegin: The server begins the process of receive a new register. mapServerAlgorithm:The sever begins to negotiate Algorithm. mapServerKexInit: The server replys to the algorithm negotiation packet from the client successfully and begin to negotiate key. mapServerAuthenInit: The server replys to the key negotiation packet from the client successfully and begin to authenticate client, in the case of the authentication-client method is not none. mapServerConfigInit: The server send some configuration information to client. Do not support now. mapServerInit: The server replys to the authentication packet from the client successfully and begin to receive client information. mapServerFinished: The server receives client information successfully.

What is hpnicfDvpnMapState?

Reports which step of the DVPN registration handshake this map entry is currently in, ranging from the client initiating the map (mapClientInit) through algorithm, key, and authentication negotiation to a fully registered client (mapClientSuccess), or on the server side from receiving a new registration (mapServerBegin) through to finishing processing it (mapServerFinished). Use it to see exactly where a stuck or failed registration attempt is hanging.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.15.2.57.1.2.5.1.17
snmpwalk -v2c -c public <target> HPN-ICF-DVPN-MIB::hpnicfDvpnMapState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.15.2.57.1.2.5.1.17.1
snmpget -v2c -c public <target> HPN-ICF-DVPN-MIB::hpnicfDvpnMapState.1

Start monitoring HP/H3C Comware router (Dynamic VPN tunnels) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HPN-ICF-DVPN-MIB::hpnicfDvpnMapState OID value, configure state conditions and alerts, and monitor any HP/H3C Comware router (Dynamic VPN tunnels) from a single console.

OID Breakdown

Upper-level ancestors (12 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.11hpCLJ8500-MIB
1.3.6.1.4.1.11.2nmCLJ8500-MIB
1.3.6.1.4.1.11.2.14icfCONFIG-MIB
1.3.6.1.4.1.11.2.14.11hpicfObjectsCONFIG-MIB
1.3.6.1.4.1.11.2.14.11.15hpnicfHPN-ICF-OID-MIB
1.3.6.1.4.1.11.2.14.11.15.2hpnicfCommonHPN-ICF-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.11.2.14.11.15.2.57hpnicfDvpnHPN-ICF-DVPN-MIB
1.3.6.1.4.1.11.2.14.11.15.2.57.1hpnicfDvpnMibObjectsHPN-ICF-DVPN-MIB
1.3.6.1.4.1.11.2.14.11.15.2.57.1.2hpnicfDvpnMibTableTroopHPN-ICF-DVPN-MIB
1.3.6.1.4.1.11.2.14.11.15.2.57.1.2.5hpnicfDvpnMapTableHPN-ICF-DVPN-MIB
1.3.6.1.4.1.11.2.14.11.15.2.57.1.2.5.1hpnicfDvpnMapEntryHPN-ICF-DVPN-MIB
1.3.6.1.4.1.11.2.14.11.15.2.57.1.2.5.1.17hpnicfDvpnMapStateHPN-ICF-DVPN-MIB