HH3C-CUSP-MIB: View SNMP OID List / Download MIB

VENDOR: H3C


 Home MIB: HH3C-CUSP-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, INET-ADDRESS-MIB, HH3C-OID-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 hh3cCusp 1.3.6.1.4.1.25506.2.190
This MIB contains information about the control-/user-plane separation trap
         hh3cCuspMibTrap 1.3.6.1.4.1.25506.2.190.1
             hh3cCuspMibTrapOid 1.3.6.1.4.1.25506.2.190.1.1
                 hh3cCuspServerDisconnectReason 1.3.6.1.4.1.25506.2.190.1.1.1 integer32 no-access
Reason why this instance is disconnected from a controller 0: Connection became abnormal. 1: An SSL connection became abnormal. 2: BFD timed out. 3: Version negotiation failed. 4: Protocol disabled. 5: Connection became abnormal when messages were being sent. 6: Connection recovery failed. 7: Received invalid packets or incorrectly processed received packets. 8: Connection became abnormal when messages were being received. 9: VPN instance deleted. 10: A TCP connection became abnormal. 11: Heartbeat packets sending failed. 12: Heartbeat packets timed out. 13: Configuration changes. 14: Not enough memory.
                 hh3cCuspClientDisconnectReason 1.3.6.1.4.1.25506.2.190.1.1.2 integer32 no-access
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.
                 hh3cCuspVpnInstanceName 1.3.6.1.4.1.25506.2.190.1.1.3 octet string no-access
VPN name for a CUSP connection.
                 hh3cCuspLocalIPaddressType 1.3.6.1.4.1.25506.2.190.1.1.4 inetaddresstype no-access
IP addresses type of the CUSP connection local IP address.
                 hh3cCuspLocalIPaddress 1.3.6.1.4.1.25506.2.190.1.1.5 inetaddress no-access
CUSP connection local IP address. The type of this address is determined by the value of hh3cCuspLocalIPaddressType.
                 hh3cCuspRemoteIPaddressType 1.3.6.1.4.1.25506.2.190.1.1.6 inetaddresstype no-access
IP addresses type of the CUSP connection remote IP address.
                 hh3cCuspRemoteIPaddress 1.3.6.1.4.1.25506.2.190.1.1.7 inetaddress no-access
CUSP connection remote IP address. The type of this address is determined by the value of hh3cCuspRemoteIPaddressType.
             hh3cCuspTraps 1.3.6.1.4.1.25506.2.190.1.2
                 hh3cCuspTrapsPrefix 1.3.6.1.4.1.25506.2.190.1.2.0
                     hh3cCuspServerDisconnect 1.3.6.1.4.1.25506.2.190.1.2.0.1
This trap is generated when the controller is disconnected from the agent. The disconnection reason is hh3cCuspServerDisconnectReason.
                     hh3cCuspServerConnect 1.3.6.1.4.1.25506.2.190.1.2.0.2
This trap is generated when the controller is connected to the agent.
                     hh3cCuspClientDisconnect 1.3.6.1.4.1.25506.2.190.1.2.0.3
This trap is generated when the agent is disconnected from the controller. The disconnection reason is hh3cCuspClientDisconnectReason.
                     hh3cCuspClientConnect 1.3.6.1.4.1.25506.2.190.1.2.0.4
This trap is generated when the agent is connected to the controller.