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.  GNS3 QFX OSPF Adjacency not forming

    Posted 03-28-2023 14:26

    I am using GNS3.  I have 2 QFX devices configured for OSPF.  I see their hello packets to each other on wireshark but the 2 QFX devices don't see each other it seems.  They both show 0 received hello packets.  Can you take a look at my configs and tell me if you see what I am missing?

    Site A config

    system {
        host-name Site-A;
        syslog {
            user * {
                any emergency;
            }
            file messages {
                any notice;
                authorization info;
            }
            file interactive-commands {
                interactive-commands any;
            }
        }
        extensions {
            providers {
                juniper {
                    license-type juniper deployment-scope commercial;
                }
                chef {
                    license-type juniper deployment-scope commercial;
                }
            }
        }
    }
    interfaces {
        xe-0/0/0 {
            description "host 1";
            unit 0 {
                family ethernet-switching {
                    vlan {
                        members VLAN10;
                    }
                }
            }
        }
        xe-0/0/1 {
            description "uplink to site B";
            mtu 9192;
            unit 0 {
                family inet {
                    address 10.10.10.1/30;
                }
            }
        }
        em1 {
            unit 0 {
                family inet {
                    address 169.254.0.2/24;
                }
            }
        }
        irb {
            unit 10 {
                family inet {
                    address 192.168.1.1/24;
                }
            }
        }
    }
    forwarding-options {
        storm-control-profiles default {
            all;
        }
    }
    protocols {
        ospf {
            area 0.0.0.0 {
                interface xe-0/0/1.0;
            }
        }
        igmp-snooping {
            vlan default;
        }
    }
    vlans {
        VLAN10 {
            vlan-id 10;
            l3-interface irb.10;
        }
        default {
            vlan-id 1;
        }
    }

    Site B config

    system {
        host-name SITE-B;
        login {
            user vagrant {
                uid 2000;
                class super-user;
                authentication {
                }
            }
        }
        services {
            ssh {
                root-login allow;
            }
            netconf {
                ssh;
            }
            rest {
                http {
                    port 8080;
                }
                enable-explorer;
            }
        }
        syslog {
            user * {
                any emergency;
            }
            file messages {
                any notice;
                authorization info;
            }
            file interactive-commands {
                interactive-commands any;
            }
        }
        extensions {
            providers {
                juniper {
                    license-type juniper deployment-scope commercial;
                }
                chef {
                    license-type juniper deployment-scope commercial;
                }
            }
        }
    }
    interfaces {
        xe-0/0/0 {
            description "Host 1";
            unit 0 {
                family ethernet-switching {
                    vlan {
                        members VLAN20;
                    }
                }
            }
        }
        xe-0/0/1 {
            description "Uplink to Site A";
            mtu 9192;
            unit 0 {
                family inet {
                    address 10.10.10.2/30;
                }
            }
        }
        em0 {
            unit 0 {
                family inet {
                    dhcp;
                }
            }
        }
        em1 {
            unit 0 {
                family inet {
                    address 169.254.0.2/24;
                }
            }
        }
        irb {
            unit 20 {
                family inet {
                    address 192.168.2.1/24;
                }
            }
        }
        lo0 {
            unit 0;
        }
    }
    forwarding-options {
        storm-control-profiles default {
            all;
        }
    }
    routing-options {
        router-id 192.168.1.1;
    }
    protocols {
        ospf {
            area 0.0.0.0 {
                interface xe-0/0/1.0;
            }
        }
        igmp-snooping {
            vlan default;
        }
    }
    vlans {
        VLAN20 {
            vlan-id 20;
            l3-interface irb.20;
        }
        default {
            vlan-id 1;
        }
    }



  • 2.  RE: GNS3 QFX OSPF Adjacency not forming

    Posted 03-29-2023 06:33

    Hi, can 10.10.10.1 ping  10.10.10.2?   If not, check these things...

    • Make sure you are connecting the vQFX PFE (vFP) and RE (vCP)  using the em1 interfaces on both pfe and re
    • Check "show chassis fpc" and you should see slot 0 Online/Testing

    I'm using vQFX in EVE-NG.  I'm assuming the setup is similar in GNS3, but I haven't used GNS3 in years.

    This video I did may help.  https://youtu.be/jZY5JhEoY9s



    ------------------------------
    - Aaron
    ------------------------------



  • 3.  RE: GNS3 QFX OSPF Adjacency not forming

    Posted 03-30-2023 08:38

    Hi Aaron.  It is nice to meet as I have utilized your videos from youtube in the past.  Thank you for those! 

    I cannot ping 10.10.10.1 from 10.10.10.2 or vice versa. 

    I am connecting the PFE and the RE using em1 and they seem to be communicating fine over that connection. 

    The show chassis fpc does show online/testing.

    Does my config look okay as far as forming an OSPF adjacency?  Like I said, when I capture packets using wireshark on the connection between the two different routing engines I can see the hello packets from each of 2 routing engines. I gave them unique router ids, I confirmed the hello interval is the same between the two. 




  • 4.  RE: GNS3 QFX OSPF Adjacency not forming

    Posted 03-30-2023 10:06

    I also just followed your video and again they still both don't respond to each other.  I can see both devices trying to ping each other using Wireshark on the same line but they dont respond to each other.  Its weird and I am assuming its not the configs that are the issue.    




  • 5.  RE: GNS3 QFX OSPF Adjacency not forming

    Posted 03-30-2023 10:36

    Another interesting thing is that I downloaded the vqfx 20.2r1 images from juniper. When I boot them up and "run system software" it reports that it's running 19.4R1.10.  




  • 6.  RE: GNS3 QFX OSPF Adjacency not forming

    Posted 03-30-2023 10:44

    yeah, I'm starting to wonder if it's something not config related, but more an issue of the vQFX system functionality on GNS3... I'm using EVE-NG and I fired-up (2) vQFX's and imported your config's and pings and ospf are working fine.  check your arp cache and interface state.   my quess is you aren't learning an arp entry.  if not, you can't make a basic connection between the 2. 

    also, does GNS3 use a RE and a separate PFE for a single vQFX node?  if so, are you making the connections between (2) different QFX's using the RE on both?  That's how I did it in EVE-NG.  like this...

    site 1 (RE) xe-0/0/1 ------- xe-0/0/1 (RE) site 2

    {master:0}
    root@Site-A> ping 10.10.10.2
    PING 10.10.10.2 (10.10.10.2): 56 data bytes
    64 bytes from 10.10.10.2: icmp_seq=0 ttl=64 time=113.649 ms
    64 bytes from 10.10.10.2: icmp_seq=1 ttl=64 time=114.210 ms
    64 bytes from 10.10.10.2: icmp_seq=2 ttl=64 time=109.099 ms
    ^C
    --- 10.10.10.2 ping statistics ---
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 109.099/112.319/114.210/2.289 ms

    {master:0}
    root@Site-A>

    {master:0}
    root@Site-A> show arp interface xe-0/0/1.0 no-resolve
    MAC Address       Address         Interface         Flags
    02:05:86:71:3f:07 10.10.10.2      xe-0/0/1.0               none

    {master:0}
    root@Site-A> show interfaces terse xe-0/0/1
    Interface               Admin Link Proto    Local                 Remote
    xe-0/0/1                up    up
    xe-0/0/1.0              up    up   inet     10.10.10.1/30

    {master:0}
    root@Site-A>

    {master:0}
    root@Site-A> show ospf neighbor
    Address          Interface              State     ID               Pri  Dead
    10.10.10.2       xe-0/0/1.0             Full      192.168.1.1      128    39



    ------------------------------
    - Aaron
    ------------------------------



  • 7.  RE: GNS3 QFX OSPF Adjacency not forming

    Posted 03-31-2023 07:06

    GNS3 does use separate RE and PFE files.   I am using the RE's to connect the two.  I have seen posts from many years ago with someone on this forum having the same issues with GNS3 and the qfx. His solution was using a different qfx version.  It appears at this time I can only download 3 versions from Juniper's website.  20, 19 and 15.  I was using version 20 in this setup. I am going to try the other 2 versions now and see what happens. 




  • 8.  RE: GNS3 QFX OSPF Adjacency not forming

    Posted 03-31-2023 12:48

    It seems my issue was that I made the connection between the two routing engines while they were running. It appears that I needed to have them powered off when I connected the xe-0/0/0 on site a to xe-0/0/0 on site b.  

    In GNS3 you can make the connections while they are powered on but it seems this probably caused my issues. 




  • 9.  RE: GNS3 QFX OSPF Adjacency not forming

    Posted 03-31-2023 14:07

    ah, so i take it your ospf is working now.  yeah, sounds like what is typical of the virtual environments.  making hot/live connections in eve-ng community edition is not allowed either.  pro license is required for that.  glad you found it.



    ------------------------------
    - Aaron
    ------------------------------