Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-HH3C-PBR-MIB | 38.62 KB |
HH3C-PBR-MIB
About this MIB
Use this MIB to obtain and configure PBR information.
MIB file name
hh3c-pbr.mib
Notifications
hh3cPBRNexthopFailedTrap
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.113.1.2.2.0.1 |
The next hop in a PBR policy becomes unreachable. |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the next hop in a PBR policy becomes unreachable.
System impact
A PBR policy cannot use an invalid next hop to forward packets.
Status control
ON
CLI: Use the snmp-agent trap enable policy-based-route command.
OFF
CLI: Use the undo snmp-agent trap enable policy-based-route command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.113.1.2.1.1 (hh3cPBRNexthopAddrType) |
Next hop address type. |
N/A |
INTEGER |
ipv4(1), , ipv6(2), |
|
1.3.6.1.4.1.25506.2.113.1.2.1.2 (hh3cPBRNexthopAddr) |
Next hop address. |
N/A |
OCTET STRING |
OCTET STRING (0..255) |
Recommended action
Check the network status, locate the reason that the next hop route becomes unreachable, and resolve the route reachability issue.
1.Identify whether the output interface of the next hop is up. Execute the display interface interface-type interface-number brief command to view the physical layer state of the interface. If the physical layer state or data link layer state of the interface is not up, resolve the interface or link failure. If the output interface is up, proceed to step 2.
2.Identify whether the route is correctly issued. Execute the display ip routing-table [ vpn-instance vpn-instance-name ] ip-address [ mask-length | mask ] [ longer-match ] verbose or display ipv6 routing-table [ vpn-instance vpn-instance-name ] ipv6-address [ prefix-length ] [ longer-match ] [ verbose ] command to view route information about the specified destination address. If the routing table does not contain the route with the specified next hop and output interface, check the route configuration. If the route configuration is correct, proceed to step 3.
3.Identify whether the IP addresses at both ends are on the same network segment. Execute the display ip interface interface-type interface-number brief or display ipv6 interface interface-type interface-number brief command on both the local and next hop devices to view the IP addresses of the interfaces on both ends.
If the IP addresses of the interfaces on both ends are not on the same network segment, execute the ip address or ipv6 address command in interface view to edit the IP addresses on both ends to make sure they are on the same network segment.
If the IP addresses of the interfaces on both ends are not on the same network segment, proceed to step 4.
4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
