Binding An Is-Is Process With Mibs; Configuring Bfd For Is-Is; Configuring Is-Is Mtr - HPE FlexNetwork HSR6800 Configuration Manual

Step
Enable SNMP trap.
3.

Binding an IS-IS process with MIBs

This task allows you to bind MIB with an IS-IS process to send and collect information. For more
information about MIB, see Network Management and Monitoring Configuration Guide.
To bind an IS-IS process with MIBs:
Step
Enter system view.
1.
Enter IS-IS view.
2.
Bind the IS-IS process with
3.
MIBs.

Configuring BFD for IS-IS

To enable BFD on an IS-IS interface:
Step
Enter system view.
1.
Enter interface view.
2.
Enable IS-IS on the
3.
interface.
Enable BFD on the IS-IS
4.
interface.

Configuring IS-IS MTR

Typically, different service packets with the same destination are forwarded over the same link. To
forward them over different links, you can use policy-based routing (PBR) to change their next hop or
use traffic engineering (TE). MTR provides another method to achieve the same purpose. Compared
with PBR, MTR is based on topology rather than next hop. Compared with TE, MTR is easier to
deploy. MTR splits the base topology of a specific address family (for example, IPv4) into multiple
topologies, and forwards traffic on a per-topology basis. (For information about configuring IPv6
IS-IS MTR, see "Configuring IPv6 IS-IS.")
Command
is-snmp-traps enable
Command
system-view
isis [ process-id ] [ vpn-instance
vpn-instance-name ]
isis mib-binding process-id
Command
system-view
interface interface-type
interface-number
isis enable [ process-id ]
isis bfd enable
152
Remarks
Enabled by default.
Remarks
N/A
N/A
By default, MIBs are bound with
IS-IS process 1.
Remarks
N/A
N/A
Disabled by default.
Not enabled by default.