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.
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;