Data Center

 View Only
last person joined: 9 days ago 

Ask questions and share experiences about Data Center Architecture and approaches.
  • 1.  Next hop issue in bgp.evpn.0

    Posted 09-15-2021 23:20
    Anyone can help me to understand where I need to check for Next hop issue?
    bgp.evpn.0: 20 destinations, 20 routes (15 active, 0 holddown, 5 hidden)
    2:192.168.1.44:4::10::00:05:86:71:91:05/304 MAC/IP (1 entry, 0 announced)
             BGP    Preference: 170/-101
                    Route Distinguisher: 192.168.1.44:4
                    Next hop type: Unusable, Next hop index: 0
                    Address: 0xc65e2d0
                    Next-hop reference count: 10
                    State: <Hidden Int Ext Changed>
                    Local AS: 65535 Peer AS: 65535
                    Age: 6
                    Validation State: unverified
                    Task: BGP_65535.192.168.1.11
                    AS path: 64511 I
                    Communities: target:1:1000
                    Import Accepted
                    Route Label: 299776
                    ESI: 00:00:00:00:00:00:00:00:00:00
                    Localpref: 100
                    Router ID: 192.168.1.11
                    Secondary Tables: default-switch.evpn.0
                    Indirect next hops: 1
                            Protocol next hop: 192.168.1.11
                            Indirect next hop: 0x0 - INH Session ID: 0x0
    ​
    root@vQFX-2# run ping 192.168.1.11
    PING 192.168.1.11 (192.168.1.11): 56 data bytes
    64 bytes from 192.168.1.11: icmp_seq=0 ttl=63 time=211.923 ms
    


    thanks a lot in advance !!



  • 2.  RE: Next hop issue in bgp.evpn.0

    Posted 09-16-2021 11:21
    The address within the following red box is next hop ?


    thanks !!



  • 3.  RE: Next hop issue in bgp.evpn.0

    Posted 09-17-2021 12:15
    a. The Address field in the show route command is not the next hop, instead what you should be looking is the Protocol Next-Hop, which in this case is 192.168.1.44.
    b. Remember that if you can have reachability towards the next-hop with a ping, this does not mean that the next-hop can be used for recursion, you need to validate whether the application using the Protocol Next-hop is an MPLS application or not and if it is, check if this exists in the inet.3 table. Does it in this case? Check the show route table inet.3 <PNH>.

    Regards,

    Elvin


  • 4.  RE: Next hop issue in bgp.evpn.0

    Posted 09-17-2021 13:53
    This is my diagram:

    As vQFXs does not need mpls, so no inet.3 table.  00:05:86:71:91:05 is 10.150.10.220
    From bgp.evpn.0 table I have two type 2 entries, one is hidden, one is OK as follows:

    OK 
    --------------------------------------------------------------------------------------------
    root@vQFX-2# run show route hidden table bgp.evpn.0 extensive | find 10.150.10.200
    2:192.168.1.44:5::10::00:05:86:71:91:05::10.150.10.200/304 MAC/IP (2 entries, 0 announced)
            *BGP    Preference: 170/-101
                    Route Distinguisher: 192.168.1.44:5
                    Next hop type: Indirect, Next hop index: 0
                    Address: 0xc65edc0
                    Next-hop reference count: 12
                    Source: 192.168.1.11
                    Protocol next hop: 192.168.1.44
                    Indirect next hop: 0x2 no-forward INH Session ID: 0x0
                    State: <Active Int Ext>
                    Local AS: 65534 Peer AS: 65534
                    Age: 29         Metric2: 5
                    Validation State: unverified
                    Task: BGP_65534.192.168.1.11
                    AS path: 64511 I
                    Communities: target:10:10 encapsulation:vxlan(0x8)
                    Import Accepted
                    Route Label: 10
                    ESI: 00:00:00:00:00:00:00:00:00:00
                    Localpref: 100
                    Router ID: 192.168.1.11
                    Secondary Tables: default-switch.evpn.0
                    Indirect next hops: 1
                            Protocol next hop: 192.168.1.44 Metric: 5
                            Indirect next hop: 0x2 no-forward INH Session ID: 0x0
                            Indirect path forwarding next hops: 1
                                    Next hop type: Router
                                    Next hop: 10.20.12.1 via xe-0/0/4.0
                                    Session Id: 0x0
                                    192.168.1.44/32 Originating RIB: inet.0
                                      Metric: 5     Node path count: 1
                                      Forwarding nexthops: 1
                                            Nexthop: 10.20.12.1 via xe-0/0/4.0
                                            Session Id: 0
    
    ---------------------------------------------------------------------------------------
    hidden one
    
    root@vQFX-2# run show route hidden table bgp.evpn.0 extensive | find 10.150.10.200
    2:192.168.1.44:4::10::00:05:86:71:91:05::10.150.10.200/304 MAC/IP (2 entries, 0 announced)
             BGP    Preference: 170/-101
                    Route Distinguisher: 192.168.1.44:4
                    Next hop type: Unusable, Next hop index: 0
                    Address: 0xc65e2d0
                    Next-hop reference count: 12
                    State: <Hidden Int Ext Changed>
                    Local AS: 65534 Peer AS: 65534
                    Age: 0
                    Validation State: unverified
                    Task: BGP_65534.192.168.1.22
                    AS path: 64511 I
                    Communities: target:1:1000
                    Import Accepted
                    Route Label: 299776
                    ESI: 00:00:00:00:00:00:00:00:00:00
                    Localpref: 100
                    Router ID: 192.168.1.22
                    Secondary Tables: default-switch.evpn.0
                    Indirect next hops: 1
                            Protocol next hop: 192.168.1.44
                            Indirect next hop: 0x0 - INH Session ID: 0x0
    ​

    From 10.150.10.200, I can ping 10.150.10.1
    root@PE1-PE2# run ping 10.150.10.1 routing-instance test-server
    PING 10.150.10.1 (10.150.10.1): 56 data bytes
    64 bytes from 10.150.10.1: icmp_seq=0 ttl=64 time=1860.971 ms
    ​

    My understanding is the OK one is learned from EVPN/vxlan overlay (64534),  the  the hidden one is learned from EVPN/MPLS (64511), right ?

    Can I ignore these hidden routes? 

    I do not want to get panic for those hidden routes,  anyway to resolve this ?

    thanks so so so much !!