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

Beijing - China

I am not sure how to describe Beijing China, maybe everyone who goes their simply use the world 'Amazing' because it will be nearly impossible to describe it. I had a personal driver and tour guide which significantly simplify my trip around.  Of course, it was a business trip and I didn't have as much time as I needed to see everything from Beijing but I will try to share couple of pictures and some of my impressions. I will start with the food.  I remember when I was younger there was so many Chines restaurants in the neighbourhood and I could eat Chines food everyday, and at every time - my parents were joking that I will became a Chines if I continue to eat only Chines, but it was so good and I didn't care ;-)  In Beijing I tried so many different things and I am amazed by the quality of the food, and most amazingly I didn't have any problems with my stomach - which was a good sign ;-) . I uploaded few photos from my album, which are from different places I

So, You Want To Be a CCIE?, Part 2

Prepare yourself for "game day" of the CCIE exams in this second part of a two-part primer on Cisco's highest-level cert by the columnist of TCP Q&A. by Scott Morris July 2005 — Editor's note: To read part one of this two-part series, go here . There’s never any point in time when you will truly know everything. Similarly, there’s never any point in time when the exam will be as bad as you may think it is until you try it! So you can spend years and years “studying” for the CCIE written exam and never think you know enough to take it. But you won’t know until you try. And you may also surprise yourself along the way: You probably know more than you give yourself credit for. (Either that or you’re really lucky!) --------------------------------------------------------- http://tcpmag.com/features/article.asp?EditorialsID=91 ---------------------------------------------------------