All MIBs › HH3C-CUSP-MIB
Organization: New H3C Technologies Co., Ltd.
Last Updated: 2020-09-11
Category: Technology: SDN/OpenFlow, Vendor: H3C/HH3C
Description: Manages H3C Cloud Unified SDN Platform (CUSP) southbound controller interfaces and OpenFlow channel statistics.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is HH3C-CUSP-MIB?
HH3C-CUSP-MIB is an H3C proprietary MIB supporting the Cloud Unified SDN Platform's control/user-plane separation (CUSP) architecture, covering the southbound channel between an SDN controller and forwarding elements. Its content is centered on connection-state notifications for the control-plane/user-plane split, including disconnect reason codes and the local/remote IP addressing of the control channel. In terms of monitoring, this MIB is almost entirely fault/trap oriented: it reports why a CUSP server or client disconnected (hh3cCuspServerDisconnectReason / hh3cCuspClientDisconnectReason), which is critical software-status information for detecting SDN control-plane instability affecting the forwarding devices under a controller's management. It presumes an underlying VPN-instance and IP-addressing model consistent with standard IETF INET-ADDRESS-MIB conventions for typed IP addresses. It is deployed in H3C SDN/CUSP-based network architectures where control-plane and user-plane processing are separated across controller and forwarding nodes. Engineers can download the HH3C-CUSP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in HH3C-CUSP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- H3C SDN-capable switches/routers participating in a Cloud Unified SDN Platform (CUSP) fabric
Monitoring Examples
An operator monitoring an SDN fabric would subscribe to hh3cCuspTraps under hh3cCuspTrapsPrefix and inspect hh3cCuspMibTrap/hh3cCuspMibTrapOid payloads carrying hh3cCuspServerDisconnectReason or hh3cCuspClientDisconnectReason whenever a control-plane session drops. Correlating hh3cCuspLocalIPaddress/hh3cCuspRemoteIPaddress with hh3cCuspVpnInstanceName would identify exactly which controller-to-node channel failed and in which VPN context. Because this MIB centers on connection-state traps rather than a rich set of polled counters, ongoing health is primarily inferred from the absence or presence of disconnect notifications rather than continuous scalar polling.
What Can Be Monitored
- control/user-plane disconnect reason
- local and remote control-channel IP addresses
- VPN instance associated with the channel
- disconnect trap events
Imported Objects
From HH3C-OID-MIB
| hh3cCommon | OBJECT-IDENTITY |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE |
OIDs
RFC description
Vendor-private H3C MIB for CUSP (possibly Custom User Service Protocol or similar); defines management objects for H3C device services and features.
Start monitoring H3C SDN-capable switch/router (control/user-plane separation, CUSP) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.