HH3C-CUSP-MIB :: hh3cCuspClientDisconnectReason

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › HH3C-CUSP-MIB › hh3cCuspClientDisconnectReason

hh3cCuspClientDisconnectReason

Module: HH3C-CUSP-MIB

OID (symbolic): HH3C-CUSP-MIB::hh3cCuspClientDisconnectReason

OID (numeric): 1.3.6.1.4.1.25506.2.190.1.1.2

Node type: OBJECT-TYPE

Type: Integer32

Access: accessible-for-notify

Description: Reason why this instance is disconnected from a controller 0: Connection became abnormal. 1: Configuration changes. 2: Heartbeat packets timed out. 3: Version negotiation failed. 4: Receiving Hello packets timed out. 5: A TCP connection became abnormal. 6: VPN instance deleted. 7: VRF service disabled. 8: Resource request failed. 9: BFD timed out. 10: Not enough memory.

What is hh3cCuspClientDisconnectReason?

This notification-only value, an integer from 0 to 10, reports the specific reason a CUSP client instance was disconnected from a controller, such as Hello packet timeout, VRF service disabled, or resource request failure. Admins read this trap variable to diagnose client-side CUSP disconnects, which use a distinct reason-code set from the server-side reasons. For example, this object reporting value 7, "VRF service disabled", tells an admin the disconnect was caused by the VRF instance being administratively disabled rather than a network fault.

OID Breakdown

Upper-level ancestors (8 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.25506hh3cHH3C-OID-MIB
1.3.6.1.4.1.25506.2hh3cCommonHH3C-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.25506.2.190hh3cCuspHH3C-CUSP-MIB
1.3.6.1.4.1.25506.2.190.1hh3cCuspMibTrapHH3C-CUSP-MIB
1.3.6.1.4.1.25506.2.190.1.1hh3cCuspMibTrapOidHH3C-CUSP-MIB
1.3.6.1.4.1.25506.2.190.1.1.2hh3cCuspClientDisconnectReasonHH3C-CUSP-MIB