Routing

Expand all | Collapse all

ISIS Routing

Jump to Best Answer
  • 1.  ISIS Routing

     
    Posted 12-18-2017 03:44

    I am sure I may have missed something very simple....

     

    During testing I had all routing working fine with no problems and now I am changing the systems to get them ready for live install.... I have changed single interfaces to aggregated groups and am having to re-assign the ISIS configuration... So, a very easy setup to start with...

     

    MX240-1 --> MX240-2  -----  Agrregated Interface labeled as ae0....

     

    Configuration on MX240-1:

    set interface ae0 unit 0 family iso

    set interface ae0 unit 0 family inet address xxx.xxx.xxx.xxx

    set interface ae0 unit 0 family inet6 address xxxxxxxxxxxxxx

     

    set interface lo0 unit 0 family inet address xxx.xxx.xxx.xxx

    set interface lo0 unit 0 family inet6 address xxxxxxxxxxxxxxxx

    set interface lo0 unit 0 family iso address 49.0001.xxxx.xxxx.xxxx.00

     

    set protocols isis interface lo0.0 passive

    set protocols isis interface ae0.0

     

    Configuration in MX240-2

    Same as above but with different IP's and NET address...

     

    As I mentioned, this worked before the change.... the interfaces are up and all I get from traceoptions on ISIS with a flag of "all" is below: 

     

    Dec 18 11:30:05.220092 task_process_events_internal: recv ready for IS-IS I/O./var/run/ppmd_control
    Dec 18 11:30:05.220134 task_process_events_internal: recv ready for IS-IS I/O./var/run/ppmd_control
    Dec 18 11:30:05.220155 task_timer_uset: timer IS-IS I/O./var/run/ppmd_control_PPM Hold <Touched> set to offset 2:00 at 11:32:05.220134
    Dec 18 11:30:05.220164 ISIS L2 periodic xmit to 01:80:c2:00:00:15 interface ae0.0
    Dec 18 11:30:06.848078 task_process_events_internal: recv ready for IS-IS I/O./var/run/ppmd_control
    Dec 18 11:30:06.848113 task_process_events_internal: recv ready for IS-IS I/O./var/run/ppmd_control
    Dec 18 11:30:06.848132 task_timer_uset: timer IS-IS I/O./var/run/ppmd_control_PPM Hold <Touched> set to offset 2:00 at 11:32:06.848113
    Dec 18 11:30:06.848140 ISIS L1 periodic xmit to 01:80:c2:00:00:14 interface ae0.0
    Dec 18 11:30:14.062097 task_process_events_internal: recv ready for IS-IS I/O./var/run/ppmd_control
    Dec 18 11:30:14.062138 task_process_events_internal: recv ready for IS-IS I/O./var/run/ppmd_control
    Dec 18 11:30:14.062158 task_timer_uset: timer IS-IS I/O./var/run/ppmd_control_PPM Hold <Touched> set to offset 2:00 at 11:32:14.062138

     

    Also, when I complete a "run show route" command, all I see is the NET address..... What am I missing please?

     

    iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    49.0001.1950.0080.0002/72
                       *[Direct/0] 00:24:15
                        > via lo0.0

     

    Surely I should be seeing the other MX address ranges?

     



  • 2.  RE: ISIS Routing
    Best Answer

    Posted 12-18-2017 04:08

    You are seeing iso.0 table.

     

    Check the inet.0 table and see if you see the ISIS routes



  • 3.  RE: ISIS Routing

     
    Posted 12-18-2017 05:08

    Hi,

     

    Thanks for the answer..... I have already looked and nothing.... Here's the whole output of show route on MX240-02

     

    inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    185.89.120.7/32    *[Local/0] 01:08:42
                          Reject
    195.80.0.2/32      *[Direct/0] 01:08:42
                        > via lo0.0
    195.80.0.14/32     *[Local/0] 01:08:37
                          Reject
    195.80.0.17/32     *[Local/0] 01:08:37
                          Reject
    195.80.0.20/30     *[Direct/0] 01:05:16
                        > via ae0.0
    195.80.0.21/32     *[Local/0] 01:08:37
                          Local via ae0.0

    iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    49.0001.1950.0080.0002/72
                       *[Direct/0] 01:08:42
                        > via lo0.0

    inet6.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    2a05:d840:9:ffff:ffff:ffff:0:1/128
                       *[Direct/0] 01:08:42
                        > via lo0.0
    2a05:d840:26:ffff:ffff:ffff:0:2/128
                       *[Local/0] 01:08:37
                          Reject
    2a05:d840:2b:ffff:ffff:ffff:0:1/128
                       *[Local/0] 01:08:37
                          Reject
    2a05:d840:3a:ffff:ffff:ffff::/127
                       *[Direct/0] 01:05:05
                        > via ae0.0
    2a05:d840:3a:ffff:ffff:ffff:0:1/128
                       *[Local/0] 01:08:37
                          Local via ae0.0
    fe80::2a0:a50f:fca6:55d6/128
                       *[Direct/0] 01:08:42
                        > via lo0.0
    fe80::7ee2:caff:febf:efcc/128
                       *[Local/0] 01:08:37
                          Local via ae0.0
    fe80::7ee2:caff:febf:efcd/128
                       *[Local/0] 01:08:37
                          Reject
    fe80::7ee2:caff:febf:efce/128
                       *[Local/0] 01:08:37
                          Reject

     

    Don't worry about the "Reject" it's because those interfaces are not yet connected..... The interfaces connected are ae0 to ae0....

     

    Here is the output of the interface terse for the interfaces included:

     

    lo0                     up    up
    lo0.0                   up    up   inet     195.80.0.2          --> 0/0
                                       iso      49.0001.1950.0080.0002
                                       inet6    2a05:d840:9:ffff:ffff:ffff:0:1
                                                fe80::2a0:a50f:fca6:55d6

    xe-1/2/0                up    up
    xe-1/2/0.0              up    up   aenet    --> ae0.0
    xe-1/2/1                up    up
    xe-1/2/1.0              up    up   aenet    --> ae0.0

    ae0                     up    up
    ae0.0                   up    up   inet     195.80.0.21/30
                                       iso
                                       inet6    2a05:d840:3a:ffff:ffff:ffff:0:1/127
                                                fe80::7ee2:caff:febf:efcc/64
                                       multiservice

     

    The same shows on the other side:

     

    This all worked before I changed the interfaces.... if you want the whole config of both sides please ask...

     

    Thanks

     

     

     

     

     

     



  • 4.  RE: ISIS Routing

     
    Posted 12-18-2017 05:50

    Ignore this please. Idiot on keyboard.... sometimes you can't see the wood for the trees... I could have sworn I put the "iso" command on the ae interface on MX240-1 but I had not.... Sorry for wasitng everyones time....