R0106-HP MSR Router Series Layer 3 - IP Routing Configuration Guide(V7)

157
Ste
p
Command Remarks
2. Enter IS-IS IPv4
unicast address
family view or IS-IS
IPv4 unicast topology
view.
• Enter IS-IS IPv4 unicast address family view:
a. isis [ process-id ] [ vpn-instance
vpn-instance-name ]
b. cost-style { wide | wide-compatible }
c. address-family ipv4 [ unicast ]
• Enter IS-IS IPv4 unicast topology view:
d. isis [ process-id ] [ vpn-instance
vpn-instance-name ]
e. cost-style { wide | wide-compatible }
f. address-family ipv4 [ unicast ]
g. topology topo-name tid tid
Use either method.
3. Enable IS-IS ISPF.
ispf enable By default, IS-IS is disabled.
Enabling prefix suppression
Perform this task to disable an interface from advertising its prefix in LSPs. This enhances network security
by preventing IP routing to the interval nodes and speeds up network convergence.
To enable prefix suppression:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter interface view.
interface interface-type interface-number N/A
3. Enable prefix
suppression on the
interface.
isis prefix-suppression
By default, prefix suppression is
disabled on the interface.
This command is also
applicable to the secondary IP
address of the interface.
Configuring IS-IS network management
This task includes the following configurations:
• Bind an IS-IS process to MIB so that you can use network management software to manage the
specified IS-IS process.
• Enable IS-IS notifications to report important events.
Notifications are delivered to the SNMP module, which outputs the notifications according to the
configured output rules. For more information about SNMP notifications, see Network Management and
Monitoring Configuration Guide.
TRILL uses the IS-IS MIB to provide the TRILL object management function for NMS. Because the MIB
objects defined in the IS-IS MIB are single-instance management objects, NMS cannot manage IS-IS and
TRILL at the same time. According to the management for multiple OSPF instances defined in RFC 4750,
you can set a context name for the SNMP object for managing TRILL. In this way, the SNMP requests for
managing IS-IS and the SNMP requests for managing TRILL from NMS can be distinguished. Because
the context name is a concept specific to SNMPv3, the community names are mapped to context names
for distinguishing different protocols in SNMPv1/v2c.