R2511-HP MSR Router Series Layer 3 - IP Routing Configuration Guide(V5)

124
CLV Code Name PDU T
yp
e
132 IP Interface Address IIH, LSP
Supported IS-IS features
Multiple instances and processes
IS-IS supports multiple instances and processes. Multiple processes allow an IS-IS process to work in
concert with a group of interfaces. A router can run multiple IS-IS processes, and each process
corresponds to a unique group of interfaces.
For routers supporting VPN, each IS-IS process is associated with a VPN instance, which means the VPN
instance is also associated with interfaces of the process.
Active/standby failover
IS-IS supports the following backup modes:
• Nonstop routing (NSR)—Backs up all IS-IS data. After an active/standby MPU switchover, IS-IS can
work immediately.
• Graceful restart (GR)—Backs up only the configuration of IS-IS. After an active/standby MPU
switchover, IS-IS performs graceful restart to synchronize the LSDB with neighbors.
The MSR series routers do not support IS-IS NSR.
IS-IS Graceful Restart
GR ensures the continuity of packet forwarding when a routing protocol restarts or an active/standby
switchover occurs:
• GR restarter—Graceful restarting router. It must be GR capable.
• GR helper—A neighbor of the GR restarter. It helps the GR restarter to complete the GR process.
After an IS-IS GR restarter restarts, it must complete the following tasks to synchronize the LSDB with its
neighbors:
• Obtain IS-IS neighbor information without changing adjacencies.
• Obtain the LSDB.
To complete these tasks, the GR restarter sends an OSPF GR signal to GR helpers so that the GR helpers
keep their adjacencies with the GR restarter, and restores the neighbor table after receiving responses
from neighbors. The GR restarter then synchronizes the LSDB with all GR-capable neighbors, calculates
routes, updates its routing table and forwarding table, and removes stale routes. The IS-IS routing
convergence is then complete.
IS-IS TE
IS-IS traffic engineering (TE) creates and maintains the Label Switched Path (LSP).
When creating the Constraint-based Routed LSP (CR LSP), MPLS must get the traffic attributes of all links
in the local area. MPLS obtains the traffic engineering information of links from IS-IS. For more
information about configuring IS-IS TE, see MPLS Configuration Guide.
Management tag
Management tag simplifies routing information management by carrying the management information
of the IP address prefixes (to control route redistribution from other routing protocols) and BGP community
and extended community attributes.