Routing

Expand all | Collapse all

Cannot PING between PE to PE (MX2020)

Jump to Best Answer
  • 1.  Cannot PING between PE to PE (MX2020)

    Posted 10-31-2018 02:43

    Hi,

     

    I have been seeing a very strange issue is that we have 2 MX2020 devices. One of the devices having a family inet interface and routing-instance can ping between PEs easily without any issue.

     

    Configuring the same thing on another MX2020, it doesn't (with the same IP and deactivating interfaces on the first one).

     

    The only difference is that the routing-instance on the first MX2020 is without any instance-type!

     

    One the 2nd one, I cannot deploy without setting an instance-type as it will not accept VRF-IMPORT.

     

    What could be the reason here?

     

    Below is the configuration:

     

    FIRST MX2020 (WORKING)

    set routing-instances RI-XXXX description V452:XXX
    set routing-instances RI-XXXX interface irb.5597
    set routing-instances RI-XXXX interface irb.10441
    set routing-instances RI-XXXX vrf-import PL-VRF-V452_XXXX-IMPORT
    set routing-instances RI-XXXX vrf-export PL-VRF-V452_XXXX-EXPORT
    set routing-instances RI-XXXX routing-options maximum-prefixes 1400
    set routing-instances RI-XXXX routing-options maximum-prefixes threshold 80
    deactivate routing-instances RI-XXXX routing-options maximum-prefixes

    SECOND MX2020 (HAVING THE ISSUE)

    [edit routing-instances RI-V452_XXXX]
      'vrf-import'
        RT Instance: vrf-import cannot be configured for non-forwarding instance: RI-V452_XXXX
    error: configuration check-out failed
    


  • 2.  RE: Cannot PING between PE to PE (MX2020)
    Best Answer

     
    Posted 10-31-2018 03:55

    Hi, 

     

    Any chances you might be inheriting some group settings on the first PE. 

     show configuration routing-instances RI-XXXX | display inheritance

    AFAIK, the instance-type needs to be specified for route-target imports/exports.

    Cheers, 

    Ashvin



  • 3.  RE: Cannot PING between PE to PE (MX2020)

    Posted 10-31-2018 04:25

    @AshvinO wrote:

    Hi, 

     

    Any chances you might be inheriting some group settings on the first PE. 

     show configuration routing-instances RI-XXXX | display inheritance

    AFAIK, the instance-type needs to be specified for route-target imports/exports.

    Cheers, 

    Ashvin


    Hello,

     

    Thanx for your reply.

     

    Below is the following output from the first PE when I execute the command provided by you:

    ##
    ## 'vrf-table-label' was inherited from group 'GR-L3VPN'
    ##
    vrf-table-label;
    ##
    ## 'routing-options' was inherited from group 'GR-L3VPN'
    ##
    routing-options {
        ##
        ## 'static' was inherited from group 'GR-L3VPN'
        ##
        static {
            ##
            ## '0.0.0.0/0' was inherited from group 'GR-L3VPN'
            ##
            route 0.0.0.0/0 {
                ##
                ## 'preference' was inherited from group 'GR-L3VPN'
                ##
                preference;
            }
        }
        ##
        ## 'multipath' was inherited from group 'GR-L3VPN'
        ##
        multipath {
            ##
            ## 'vpn-unequal-cost' was inherited from group 'GR-L3VPN'
            ##
            vpn-unequal-cost;
        }
    }
    


  • 4.  RE: Cannot PING between PE to PE (MX2020)

     
    Posted 10-31-2018 08:22

    Hi, 

    Can see some settings being inherited, however cannot see the instance-type defined.

    You can check using:

    show route instance RI-XXXX
    show configuration groups 'GR-L3VPN'

    To go back to the original question, the instance-type needs to be defined for route-targets.

     

    Cheers, 
    Ashvin



  • 5.  RE: Cannot PING between PE to PE (MX2020)

    Posted 11-03-2018 22:22

    Hi,

     

    Thank You for your reply.

     

    I tried checking the "show configuration groups GR-L3VPN" but shows nothing inside.

     

    Anyways, I applied the two missing groups to the routing-instance and I can indeed deploy the routing-instance without an instance-type defined. Probably inheriting from the vrf-table-label or something.

     

    The issue is solved, hence I would mark your post as the solution.

     

    Thank You.