No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-Why Some Routes Have Flag but Some do not in Displaying ISIS Routes

Publication Date:  2012-07-27 Views:  36 Downloads:  0
Issue Description
Q: In displaying the ISIS routes, why do some routes have flag, but some do not have? 
See the following: 
<RTB>dis isis rout
                  ISIS Level - 1 Forwarding Table :
          Type - D -Direct, C -Connected, I -ISIS, S -Static, O -OSPF
                 B -BGP, R -RIP
     Flags: R-Added to RM, L-Advertised in LSPs, U-Up/Down Bit Set
  Destination/Mask  In.Met     Ex.Met NextHop         Interface       Flags
----------------------------------------------------------------------------
D 55.0.0.0/8         10         NULL  Direct          Pos5/0/0        R/L/-
D 68.0.0.0/8         10         NULL  Direct          Ethernet2/0/8   R/L/-
I 90.0.0.0/8         20         NULL  55.0.0.1        Pos5/0/0        R/L/-
                                      68.0.0.2        Ethernet2/0/8
S 3.3.3.3/32         21         NULL Direct           LoopBack
O 2.2.2.2/32         55         NULL  68.0.0.2        Ethernet2/0/8
B 22.0.0.0/8         0            63  68.0.0.2        Ethernet2/0/8
Alarm Information
Null
Handling Process
A: Only the route after ISIS route calculation could generate flag, and it is a part of route calculation, including the direct route of interface enabling ISIS, and the route received through ISIS. 
For the meaning of Flags, reference to the interpretation in what is displayed. 
Root Cause
Null
Suggestions
Null

END