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.
Original Message:
Sent: 03-30-2023 10:44
From: aaron.gould
Subject: GNS3 QFX OSPF Adjacency not forming
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
Original Message:
Sent: 03-30-2023 10:35
From: Jason-net
Subject: GNS3 QFX OSPF Adjacency not forming
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.
Original Message:
Sent: 03-29-2023 06:32
From: aaron.gould
Subject: GNS3 QFX OSPF Adjacency not forming
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
Original Message:
Sent: 03-28-2023 14:25
From: Jason-net
Subject: GNS3 QFX OSPF Adjacency not forming
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;
}
}