Routing

Expand all | Collapse all

SRX routing issue

Jump to Best Answer
  • 1.  SRX routing issue

     
    Posted 02-13-2018 06:00

    Hi all,

     

    Another question.... thought I would keep everyone busy 🙂

     

    During excellent help from Rahul this morning I was able to access our radius server remotely, but since then, I have tried to reconnect and something strange has happened, as follows:

     

    RADIUS (em1) --> (ge-0/0/2)THW-SRX --> (ae2)Core 1(ae1) -->(ae1) LNS 1

     

    When I logon to THW-SRX to see the routing table I see the following (to the default route from every VR)... The default is injected into iBGP for the failover the core systems.... so, when I try and ping the RADIUS I get a TTL expired in transit..... obviously I wanted to know where the loop was and it is bouncing between the core and the LNS.

     

    Why on Earth would a device connected directly to the SRX be going through the default.....? Heer is the config I have for that (remembering it was fine earlier and no one has touched anything (that I know of):

     

    set interfaces ge-0/0/2 unit 0 family inet address 195.80.0.37/30
    set interfaces ge-0/0/2 unit 0 family iso

    set routing-options static route 195.80.0.38/32 next-hop 195.80.0.37

    set routing-instances NineGroup-VR instance-type virtual-router
    set routing-instances NineGroup-VR interface lt-0/0/0.1
    set routing-instances NineGroup-VR interface ge-0/0/2.0
    set routing-instances NineGroup-VR interface ge-0/0/6.0
    set routing-instances NineGroup-VR interface ge-0/0/8.0
    set routing-instances NineGroup-VR interface lo0.20
    set routing-instances NineGroup-VR protocols isis export export_statics
    set routing-instances NineGroup-VR protocols isis level 1 authentication-key "$9$RplElM7Nb2oGVwGiqfn60BIEreM8X-bs"
    set routing-instances NineGroup-VR protocols isis level 1 authentication-type md5
    set routing-instances NineGroup-VR protocols isis level 2 authentication-key "$9$lc7eLNsYoGjq4aqfQnpuhSre8XNdb2oJ"
    set routing-instances NineGroup-VR protocols isis level 2 authentication-type md5
    set routing-instances NineGroup-VR protocols isis interface lt-0/0/0.1
    set routing-instances NineGroup-VR protocols isis interface ge-0/0/2.0
    set routing-instances NineGroup-VR protocols isis interface ge-0/0/6.0
    set routing-instances NineGroup-VR protocols isis interface ge-0/0/8.0
    set routing-instances NineGroup-VR protocols isis interface lo0.20

     

    All the other interfaces in this instance are working fine..... This is weird

     

    Thanks

     

     



  • 2.  RE: SRX routing issue

     
    Posted 02-13-2018 06:15

    Apologies. Forgot to add the routing table:

     

    Clive@THW-SRX-01# run show route 195.80.0.38

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

    0.0.0.0/0 *[IS-IS/160] 21:21:14, metric 10
    > to 195.80.0.17 via ae2.0

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

    0.0.0.0/0 *[IS-IS/160] 21:21:14, metric 20
    > to 20.20.20.2 via lt-0/0/0.1

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

    0.0.0.0/0 *[IS-IS/160] 21:21:14, metric 20
    > to 30.30.30.2 via lt-0/0/0.3

     

    Clive@THW-SRX-01# run show route 192.168.50.209

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

    192.168.50.0/24 *[Direct/0] 02:06:48
    > via ge-0/0/8.0

     

    Clive@THW-SRX-01# run show route 195.80.0.9

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

    195.80.0.8/30 *[Direct/0] 02:11:38
    > via ge-0/0/6.0

     

    As you can see, the other interfaces are routing fine  🙂



  • 3.  RE: SRX routing issue
    Best Answer

     
    Posted 02-13-2018 06:21

    Hi Clive,

     

    Did you seen whether interface is up or not? Why you need static route for /30?

     

    set interfaces ge-0/0/2 unit 0 family inet address 195.80.0.37/30
    set interfaces ge-0/0/2 unit 0 family iso

    set routing-options static route 195.80.0.38/32 next-hop 195.80.0.37

     

    Regards,

    Rahul



  • 4.  RE: SRX routing issue

     
    Posted 02-13-2018 06:25

    Oh, good shout Rahul, the one thing I did not check as nobody has touched anything as far as I knew.... It shows as "Down"..... don't know why.... I will go to the Cabinet and check.....

     

    Clive@THW-SRX-01# run show interfaces terse ge-0/0/2
    Interface               Admin Link Proto    Local                 Remote
    ge-0/0/2                up    down
    ge-0/0/2.0              up    down inet     195.80.0.37/30

     

    Thanks

     



  • 5.  RE: SRX routing issue

     
    Posted 02-13-2018 06:30

    Unfortunately, due to the current infrastructure, we only have available here, on site, a few cat6 cables and on two of them the RJ45 clip has come off and so it is just balancing in the switch. It had come slightly out, so someone must have accidentally touched it. I have pushed it back in and everything now comes up okay....

     

    My apologies for asking such a stupid question without checking the interface first. How to make yourself look silly in one quick, easy step 🙂