Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 03-HH3C-CUPM-UP-MIB | 76.81 KB |
Contents
hh3cCupmUpVbVxlanID (1.3.6.1.4.1.25506.2.195.1.1)
hh3cCupmUpVbSrcAddrType (1.3.6.1.4.1.25506.2.195.1.2)
hh3cCupmUpVbSrcAddr (1.3.6.1.4.1.25506.2.195.1.3)
hh3cCupmUpVbDestAddrType (1.3.6.1.4.1.25506.2.195.1.4)
hh3cCupmUpVbDestAddr (1.3.6.1.4.1.25506.2.195.1.5)
hh3cCupmUpVbVpnName (1.3.6.1.4.1.25506.2.195.1.6)
HH3C-CUPM-UP-MIB
About this MIB
Use this MIB to implement trap notifications associated with the UP-side channels.
MIB file name
hh3c-cupm-up.mib
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cCupmUp(195)
Scalar objects
hh3cCupmUpVbVxlanID (1.3.6.1.4.1.25506.2.195.1.1)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cCupmUpVbVxlanID (1.3.6.1.4.1.25506.2.195.1.1) |
accessible-for-notify |
Integer32 |
Standard MIB values. |
VXLAN ID |
As per the MIB. |
hh3cCupmUpVbSrcAddrType (1.3.6.1.4.1.25506.2.195.1.2)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cCupmUpVbSrcAddrType (1.3.6.1.4.1.25506.2.195.1.2) |
accessible-for-notify |
InetAddressType |
Standard MIB values. |
Address type |
As per the MIB. |
hh3cCupmUpVbSrcAddr (1.3.6.1.4.1.25506.2.195.1.3)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cCupmUpVbSrcAddr (1.3.6.1.4.1.25506.2.195.1.3) |
accessible-for-notify |
InetAddress |
Standard MIB values. |
Source IP address |
As per the MIB. |
hh3cCupmUpVbDestAddrType (1.3.6.1.4.1.25506.2.195.1.4)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cCupmUpVbDestAddrType (1.3.6.1.4.1.25506.2.195.1.4) |
accessible-for-notify |
InetAddressType |
Standard MIB values. |
Address type |
As per the MIB. |
hh3cCupmUpVbDestAddr (1.3.6.1.4.1.25506.2.195.1.5)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cCupmUpVbDestAddr (1.3.6.1.4.1.25506.2.195.1.5) |
accessible-for-notify |
InetAddress |
Standard MIB values. |
Destination IP address. |
As per the MIB. |
hh3cCupmUpVbVpnName (1.3.6.1.4.1.25506.2.195.1.6)
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cCupmUpVbVpnName (1.3.6.1.4.1.25506.2.195.1.6) |
accessible-for-notify |
OCTET STRING |
Standard MIB values. |
VPN name |
As per the MIB. |
Notifications
hh3cCupmUpProtoTnlUp
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.195.0.1 |
The UP is successfully connected to the VXLAN tunnel. |
Recovery |
Major |
N/A (N/A) |
ON |
Notification triggers
The notification is generated when the UP-side device detects VXLAN tunnel connection.
Possible causes for the notification include the following:
The CP starts up or recovers.
The UP starts up or recovers.
The CP-UP network recovers.
System impact
Identify whether the VXLAN tunnel is as expected.
After the VXLAN tunnel is established, the CP communicates with the UP, and then provides UP-based BRAS user services.
The issue might trigger UP switchover.
The issue might trigger master/backup switchover for the CPDR group.
Status control
ON
CLI: Use the snmp-agent trap enable protocol-tunnel command.
OFF
CLI: Use the undo snmp-agent trap enable protocol-tunnel command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.195.1.1 (hh3cCupmUpVbVxlanID) |
VXLAN ID. |
N/A |
Integer32 |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.2 (hh3cCupmUpVbSrcAddrType) |
Source address type. |
N/A |
InetAddressType |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.3 (hh3cCupmUpVbSrcAddr) |
Source IP address. |
N/A |
InetAddress |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.4 (hh3cCupmUpVbDestAddrType) |
Destination address type. |
N/A |
InetAddressType |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.5 (hh3cCupmUpVbDestAddr) |
Destination IP address. |
N/A |
InetAddress |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.6 (hh3cCupmUpVbVpnName) |
VPN name. |
N/A |
OCTET STRING |
Standard MIB values. |
Recommended action
No action is required.
hh3cCupmUpProtoTnlDown
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.195.0.2 |
The UP is disconnected from the VXLAN tunnel. |
Error |
Major |
1.3.6.1.4.1.25506.2.195.0.1 (hh3cCupmUpProtoTnlUp) |
ON |
Notification triggers
The notification is generated when the UP-side device detects disconnection of the VXLAN tunnel.
Possible causes for the notification include the following:
The CP is faulty or disconnected.
The CP-UP network is faulty.
System impact
Identify whether the VXLAN tunnel is as expected.
After the VXLAN tunnel is disconnected, the CP disconnects from the UP, and then cannot provide UP-based BRAS user services.
The issue might trigger UP switchover.
The issue might trigger master/backup switchover for the CPDR group.
Status control
ON
CLI: Use the snmp-agent trap enable protocol-tunnel command.
OFF
CLI: Use the undo snmp-agent trap enable protocol-tunnel command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.195.1.1 (hh3cCupmUpVbVxlanID) |
VXLAN ID. |
N/A |
Integer32 |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.2 (hh3cCupmUpVbSrcAddrType) |
Source address type. |
N/A |
InetAddressType |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.3 (hh3cCupmUpVbSrcAddr) |
Source IP address. |
N/A |
InetAddress |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.4 (hh3cCupmUpVbDestAddrType) |
Destination address type. |
N/A |
InetAddressType |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.5 (hh3cCupmUpVbDestAddr) |
Destination IP address. |
N/A |
InetAddress |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.195.1.6 (hh3cCupmUpVbVpnName) |
VPN name. |
N/A |
OCTET STRING |
Standard MIB values. |
Recommended action
To resolve this issue:
1.Make sure the VXLAN tunnel configuration is correct.
2.Execute the display this command on the interface interconnecting the CP and UP to identify whether the interface is shut down.
- If the interface is shut down, execute the undo shutdown command in interface view to bring it up.
- If the interface is not shut down, proceed to step 3.
3.Identify whether the CP-side and UP-side network interfaces are faulty.
- If the interface-attached physical link is not operating correctly, connect the physical link again and then identify whether the alarm has been cleared.
- If the physical link is operating correctly, proceed to step 4.
4.If the issue persists, collect CP-side and UP-side alarm information and configuration data, and then contact H3C Support for help.
