ISIS Case study

densmadensma Member Posts: 40 ■■□□□□□□□□
in Juniper
I like to know if LSP cannot be set globally.

under ISIS case study change "Configure the network to keep LSPs that are up to 3600 seconds old"
when i configured LSP Interval globally, the change is not applied.
but when i configured on interface specific then it works.
any idea?



root@R5# run show isis interface detail
IS-IS interface database:
fxp0.0
Index: 64, State: 0x6, Circuit id: 0x2, Circuit type: 2
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 1 64 5 3.000 9 R5.02 (us)
fxp1.0
Index: 65, State: 0x6, Circuit id: 0x3, Circuit type: 2
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 1 64 5 3.000 9 R5.03 (us)
fxp2.0
Index: 66, State: 0x6, Circuit id: 0x4, Circuit type: 1
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1 1 0 5 3.000 9 R5.04 (us)
fxp3.0
Index: 67, State: 0x6, Circuit id: 0x1, Circuit type: 1
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1 1 0 5 9.000 27 R6.02 (not us)
lo0.0
Index: 68, State: 0x6, Circuit id: 0x1, Circuit type: 0
LSP interval: 100 ms, CSNP interval: disabled
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 0 64 0 Passive

[edit protocols isis]
root@R5# set lsp-lifetime 3600

[edit protocols isis]
root@R5# commit
commit complete

[edit protocols isis]
root@R5# run show isis interface detail
IS-IS interface database:
fxp0.0
Index: 64, State: 0x6, Circuit id: 0x2, Circuit type: 2
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 1 64 5 3.000 9 R5.02 (us)
fxp1.0
Index: 65, State: 0x6, Circuit id: 0x3, Circuit type: 2
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 1 64 5 3.000 9 R5.03 (us)
fxp2.0
Index: 66, State: 0x6, Circuit id: 0x4, Circuit type: 1
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1 1 0 5 3.000 9 R5.04 (us)
fxp3.0
Index: 67, State: 0x6, Circuit id: 0x1, Circuit type: 1
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1 1 0 5 9.000 27 R6.02 (not us)
lo0.0
Index: 68, State: 0x6, Circuit id: 0x1, Circuit type: 0
LSP interval: 100 ms, CSNP interval: disabled
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 0 64 0 Passive

[edit protocols isis]
root@R5# set interface fxp0.0 lsp-interval 3600

[edit protocols isis]
root@R5# commit
commit complete

[edit protocols isis]
root@R5# run show isis interface detail
IS-IS interface database:
fxp0.0
Index: 64, State: 0x26, Circuit id: 0x2, Circuit type: 2
LSP interval: 3600 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 1 64 5 3.000 9 R5.02 (us)
fxp1.0
Index: 65, State: 0x6, Circuit id: 0x3, Circuit type: 2
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 1 64 5 3.000 9 R5.03 (us)
fxp2.0
Index: 66, State: 0x6, Circuit id: 0x4, Circuit type: 1
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1 1 0 5 3.000 9 R5.04 (us)
fxp3.0
Index: 67, State: 0x6, Circuit id: 0x1, Circuit type: 1
LSP interval: 100 ms, CSNP interval: 10 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1 1 0 5 9.000 27 R6.02 (not us)
lo0.0
Index: 68, State: 0x6, Circuit id: 0x1, Circuit type: 0
LSP interval: 100 ms, CSNP interval: disabled
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
2 0 64 0 Passive

[edit protocols isis]
root@R5#
· Share on FacebookShare on Twitter

Comments

  • hoogen82hoogen82 Member Posts: 272
    You are looking at two different commands...

    LSP Lifetime is for the ISIS database...I set this command on my R3 router and all R3 routers reported the change in lifetime...


    r3.00-00 Sequence: 0x122, Checksum: 0x8d8c, Lifetime: 3588 secs
    IS neighbor: r3.02 Metric: 10
    IS neighbor: r3.04 Metric: 10
    IP prefix: 10.0.4.0/30 Metric: 10 Internal Up
    IP prefix: 10.0.4.12/30 Metric: 10 Internal Up

    r3.02-00 Sequence: 0x11c, Checksum: 0x67c7, Lifetime: 3588 secs
    IS neighbor: r1.00 Metric: 0
    IS neighbor: r3.00 Metric: 0

    r3.04-00 Sequence: 0x11c, Checksum: 0x5907, Lifetime: 3588 secs
    IS neighbor: r2.00 Metric: 0
    IS neighbor: r3.00 Metric: 0

    r4.00-00 Sequence: 0x125, Checksum: 0xae5, Lifetime: 492 secs
    IS neighbor: r4.02 Metric: 10
    IS neighbor: r4.04 Metric: 10
    IP prefix: 10.0.4.8/30 Metric: 10 Internal Up
    IP prefix: 10.0.4.16/30 Metric: 10 Internal Up

    r4.02-00 Sequence: 0x11e, Checksum: 0x6396, Lifetime: 716 secs
    IS neighbor: r1.00 Metric: 0
    IS neighbor: r4.00 Metric: 0

    r4.04-00 Sequence: 0x11f, Checksum: 0x53d6, Lifetime: 716 secs
    IS neighbor: r2.00 Metric: 0
    IS neighbor: r4.00 Metric: 0

    IS-IS level 2 link-state database:

    r3.00-00 Sequence: 0x16c, Checksum: 0x8171, Lifetime: 3595 secs
    IS neighbor: r3.03 Metric: 10
    IS neighbor: r4.00 Metric: 10
    IS neighbor: r5.00 Metric: 10
    IP prefix: 10.0.2.0/30 Metric: 10 Internal Up
    IP prefix: 10.0.2.4/30 Metric: 10 Internal Up
    IP prefix: 10.0.2.12/30 Metric: 10 Internal Up
    IP prefix: 10.0.3.3/32 Metric: 0 Internal Up
    IP prefix: 10.0.4.0/30 Metric: 10 Internal Up
    IP prefix: 10.0.4.4/30 Metric: 20 Internal Up
    IP prefix: 10.0.4.8/30 Metric: 20 Internal Up
    IP prefix: 10.0.4.12/30 Metric: 10 Internal Up
    IP prefix: 10.0.4.16/30 Metric: 20 Internal Up
    IP prefix: 10.0.5.0/24 Metric: 20 Internal Up
    IP prefix: 10.0.6.1/32 Metric: 10 Internal Up
    IP prefix: 10.0.6.2/32 Metric: 10 Internal Up

    r3.03-00 Sequence: 0x13e, Checksum: 0x1cef, Lifetime: 3588 secs
    IS neighbor: r3.00 Metric: 0
    IS neighbor: r6.00 Metric: 0


    LSP-interval though refer lsp-interval - JUNOS 9.4 Routing Protocols Configuration Guide

    Interesting to note though that the range is 0-1000 and you were able to give 3600...

    Cheers,
    Hoogen
    IS-IS Sleeps.
    BGP peers are quiet.
    Something must be wrong.
    · Share on FacebookShare on Twitter
  • AldurAldur Member Posts: 1,460
    hoogen82 wrote: »
    LSP-interval though refer lsp-interval - JUNOS 9.4 Routing Protocols Configuration Guide

    Interesting to note though that the range is 0-1000 and you were able to give 3600...

    In 9.1 it doesn't specify a range and I configured 36000000

    {master}[edit protocols isis]
    x@E# set interface ge-5/0/9.0 lsp-interval ?
    Possible completions:
    <lsp-interval> Interval between LSP transmissions (milliseconds)

    {master}[edit protocols isis]
    x@E# set interface ge-5/0/9.0 lsp-interval 36000000

    {master}[edit protocols isis]
    x@E# show interface ge-5/0/9.0
    lsp-interval 36000000;
    level 2 {
    metric 1000;
    }

    {master}[edit protocols isis]
    x@E# commit check
    re0:
    configuration check succeeds
    re1:
    configuration check succeeds

    {master}[edit protocols isis]
    x@E#
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
    · Share on FacebookShare on Twitter
  • hoogen82hoogen82 Member Posts: 272
    Oh yeah.. I was running 8.3 code... Must have changed..
    IS-IS Sleeps.
    BGP peers are quiet.
    Something must be wrong.
    · Share on FacebookShare on Twitter
  • AldurAldur Member Posts: 1,460
    maybe just for 9.1...

    lsp-interval - JUNOS 9.4 Routing Protocols Configuration Guide says the following
    [B]Options[/B]

   [I]milliseconds[/I]—Number of milliseconds between the 
   sending of LSPs. Specifying a value of 0 blocks all LSP transmission. 
  [B]Range: [/B]0 through 1000 milliseconds 
  [B]Default: [/B]100 milliseconds
    The the configurable max is supposed to be 1000 in 9.4... oh well I suppose it really don't matter though :)
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
    · Share on FacebookShare on Twitter
  • densmadensma Member Posts: 40 ■■□□□□□□□□
    oh i see now.
    yup those are 2 commands
    thanks!
    · Share on FacebookShare on Twitter
Sign In or Register to comment.