Skip to main content

Juniper IS-IS summary


  1. #####################################################################################################
  2. ## ISIS
  3. #####################################################################################################
  4. # Be sure to set family iso on the interface to be placed into ISIS
  5. set interfaces <interface> family iso
  6. # By default Junos places interfaces as L1/L2
  7. # Default route leaking:
  8.         L1 to L2 - all internal routes
  9.         L2 to L1 - 0/0 route
  10. # L1/L2 will send the attached-bit down to L1 and it will act as a NSSA-like area.  When the L1 interface
  11. # receives the attached-bit it will inject a 0/0 route into the RIB point to the L1/L2 interface.
  12. # To disable the attached bit use:
  13. set protocols isis ignore-attached-bit
  14. # Be careful with the "interface all" command, as it may have some unexpected consequences such as trying
  15. # to establish a neighbor on your fxp0 management interface.  Use explicit interface names.  If you must
  16. # use the "interface all" command, remember that if you also define another explicit interface such as
  17. # "interface ge-0/0/0.0 <options>" that it _doesn't_ inherit the "interface all" options.
  18. # ALWAYS include the interface lo0.0
  19. # L2 backbone must be contiguous.
  20. # Human-readable hostnames via TLV 137.  Good to quickly verify that the router has the proper adjcancies .
  21. show isis hostname
  22. # Set LSP authentication (per area knob)
  23. set protocols isis level <level> authentication-type (simple|md5)
  24. set protocols isis level <level> authentication-key <key>
  25. # Set hello authentication (per interface knob)
  26. set protocols isis interface <interface> hello-authentication-type (simple|md5)
  27. set protocols isis interface <interface> hello-authentication-key <key>
  28. # Set lsp-interval
  29. set interfaces ge-0/0/0.0 lsp-interval <milliseconds>
  30. # L2 to L1 route summarization
  31. ## set aggregate route in routing-options
  32. set routing-options aggregate route 10/8
  33. ## set policy-options - what prefix to match
  34. set policy-options policy-statement isis-export term 1 from protocol aggregate route-filter 10/8 exact
  35. ## set policy-options - what level to go _to_
  36. set policy-options policy-statement isis-export term 1 to level 1
  37. ## set action
  38. set policy-options policy-statement isis-export term 1 then accept
  39. # L1 to L2 route summarization
  40. ## set aggregate route in routing-options
  41. set routing-optiong aggregate route 10/8
  42. ## set policy-options
  43. ### match exact route
  44. set policy-options policy-statement isis-export term 1 from protocol aggregate router-filter 10/8 exact
  45. ## set policy-options - what level to go _to_
  46. set policy-options policy-statement isis-export term 1 to level 2
  47. ## set action
  48. set policy-options policy-statement isis-export term 1 then accept
  49. ### suppress more specific routes (to prevent advertisements of both aggregate and more specific routes)
  50. set policy-options policy-statement isis-export term 2 from protocol isis
  51. set policy-options policy-statement isis-export term 2 from level 1
  52. set policy-options policy-statement isis-export term 2 to level 2
  53. ## set action
  54. set policy-options policy-statement isis-export term 2 then reject
  55. # Verify that a route is internal or external
  56. show route protocol isis <prefix> exact
  57. show isis database <sysid> detail
  58. # When using wide-metrics-only it makes the route internal.  When there is a situtation where the L1 routers
  59. # are wide-metrics-only and are exporting external routes into the L1 area, they will appear as internal
  60. # routes.  Also if there are any L1/L2 routers in the area that exported prefix will be automatically
  61. # redistributed from L1 into L2 because it's showing as an internal route.  If narrow-metrics were used, the
  62. # L1/L2 routers would have to have an export policy to redistributed the prefix from L1 to L2.
  63. # Set DIS priority
  64. set protocols isis interface <interface> level <level> priority <level>
  65. ## Remember that the highest MAC address is the tie-breaker if the priorities are equal
  66. ## view current DIS
  67. show isis interface

Popular posts from this blog

IOS on Unix (IOU)

source http://evilrouters.net/2011/01/18/cisco-iou-faq/ What is IOU? From the Cisco Engineering Education web site (a long time ago): IOS on Unix (IOU) is a fully working version of IOS that runs as a user mode UNIX (Solaris) process. IOU is built as a native Solaris image and run just like any other program. IOU supports all platform independent protocols and features. What operating systems does IOU run on? It is my understanding that, initially, IOU was Solaris (SPARC) only. Nowadays, however, there are also builds for OS X and Linux. Similar to dynamips, IOU allows you to build out a network topology on a computer, without the need for physical routers. This is useful for validating designs, proof-of-concept testing, and certification self-study. Is my system compatible with IOU? You will need to be running the operating system that your IOU image were built for, obviously. Other than that, there are no special requirements to run IOU. It is not very CPU- or memory-intensive, unlik...

Impressed with Poly brand for conference headphones

I previously used my Sony XM4 headphones for calls and initially found them versatile for multiple purposes. However, as my meetings extended to several hours, I noticed they became less comfortable. To address this, I upgraded to wireless headphones from Poly, which offer significantly improved comfort. While I don’t plan to use them for music listening, my initial impression is very positive.

Flapping LDP/RSVP on Olive

I had a strange problem where the LDP and RSVP was flapping on JunOS/Olive and I think I managed to fix it by changing the driver from e1000 to i82559er and lo0.0 with 127.0.0.1.  I don't want to spend more time investigating it but if someone have similar problem at least this comment could be a good start. root@jr2>  *** MPLS *** May 21 14:27:21.472443 Session 4.4.4.4 hold timer expired in Operational state May 21 14:27:21.473451 Connection 4.4.4.4 state Open -> Closed May 21 14:27:21.473838 Session 4.4.4.4 GR state Operational -> Nonexistent May 21 14:27:21.473923 Session 4.4.4.4 state Operational -> Closing May 21 14:27:21.474054 LDP session 4.4.4.4 is down, reason: hold time expired May 21 14:27:21.474364 RPD_LDP_SESSIONDOWN: LDP session 4.4.4.4 is down, reason: hold time expired May 21 14:27:21.475567 Session 4.4.4.4 state Closing -> Nonexistent May 21 14:27:21.476180 CHANGE   317024 /52          nhid ...