Routing

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  Why is the generate route hidden ?

    Posted 03-25-2021 01:35
    I have the following configuration as I did before, but this time the generated route is hidden. I could not find the root cause. Anyway to debug the policy ?
    root@R2# run show bgp summary 
    Groups: 2 Peers: 2 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0               
                           4          0          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    21.100.0.1              653        554        550       0       0     4:07:08 0/3/3/0              0/0/0/0
    172.30.30.4             212          6          6       0       0        1:27 0/1/1/0              0/0/0/0​

    BGP is up.

    root@R2# run show route aspath-regex 212    
    
    inet.0: 24 destinations, 25 routes (20 active, 0 holddown, 4 hidden)
    + = Active Route, - = Last Active, * = Both
    
    172.30.30.4/32      [BGP/170] 00:01:35, localpref 100, from 172.30.30.4
                          AS path: 212 I, validation-state: unverified
                          to 6.7.7.1 via ge-0/0/2.102
                        > to 6.6.6.1 via ge-0/0/3.101

    At least one route is learned.

    root@R2# show policy-options | display set | match T1up 
    set policy-options policy-statement T1up term 1 from protocol bgp
    set policy-options policy-statement T1up term 1 from neighbor 172.30.30.4
    set policy-options policy-statement T1up term 1 then accept
    set policy-options policy-statement T1up term 2 then reject
    
    root@R2# show routing-options generate | display set 
    set routing-options generate route 0.0.0.0/0 policy T1up

    Created a generated route based on the policy

    root@R2# run show route hidden extensive exact 0.0.0.0/0 
    
    inet.0: 24 destinations, 25 routes (20 active, 0 holddown, 4 hidden)
    0.0.0.0/0 (1 entry, 0 announced)
             Aggregate
                    Next hop type: Reject
                    Address: 0x9292a44
                    Next-hop reference count: 1
                    State: <Hidden Int Ext>
                    Local AS:   653 
                    Age: 31:20 
                    Validation State: unverified 
                    Task: Aggregate
                    AS path: I
                                    Flags: Generate Depth: 0        Inactive

    The generated route is hidden.

    Anyone can help me to take a look what I missed here ?

    thanks !!



  • 2.  RE: Why is the generate route hidden ?
    Best Answer

    Posted 03-25-2021 07:33
    I think the generate route is hidden because your T1up policy is waiting for valid routes from the neighbor 172.30.30.4 (not just the neighbor IP itself) . The neighbor is up, but no route is active. You can see the route count in the "show bgp summary" that you posted:

    0/1/1/0​


    The neighbor sends one route, but the route is not active. Can you check why?

    Edit:

    I now see your "show route aspath-regex 212" output. Can you check with "show route 172.30.30.4" what is the best protocol? If there's an OSPF route to that IP, or a Direct route, then that's why the T1up does not activate the generate route. It was confusing me for a second because the neighbor IP and route IP are the same.



  • 3.  RE: Why is the generate route hidden ?

    Posted 03-25-2021 09:26
    thanks a lot for your good points !!  

    The bgp route is inactive as I have static route  too.
    root@R2> show route 172.30.30.4 
    
    inet.0: 24 destinations, 25 routes (20 active, 0 holddown, 4 hidden)
    + = Active Route, - = Last Active, * = Both
    
    172.30.30.4/32     *[Static/5] 07:48:10
                          to 6.7.7.1 via ge-0/0/2.102
                        > to 6.6.6.1 via ge-0/0/3.101
                        [BGP/170] 07:48:00, localpref 100, from 172.30.30.4
                          AS path: 212 I, validation-state: unverified
                          to 6.7.7.1 via ge-0/0/2.102
                        > to 6.6.6.1 via ge-0/0/3.101​