LACP is not needed for Aggregated Ethernet to work. LACP is a control protocol which will be covered in a future video. As for the minimum-links statement, once your available "UP" interfaces go below the number of minimum links you have configured under the ae interface, the ae interface will go down. This is only used if you have a backup path via other interfaces, otherwise this statement does not really apply to your environment.
Hello there, I really enjoy your videos and I am trying to put my own skills into practice with Eve-ng. When I tried out the configuration from this video on the QFX images I kept getting messages saying "device not found" - with show int xe-0/0/0 terse. I can configure these interfaces, but they do not show up in the show commands. The 10Gbit xe- Interfaces are displayed on the "show configuration" command, but not with the "show interfaces terse". With the "terse" command, the output displays the "em0 -14" interfaces. Do you recognize this? I've probably done something wrong somewhere when importing the images. Many thanks for any help
Appreciate the kind words! I had this issue a few times. Do you have both QFX images? The RE and control plane? Those have to be linked as well as in the video. Make sure that when you add them the versions are identical on both devices. Sometimes a reboot of both fixes this issue even if everything is correct. Seems like a bug with either the QFX images or EVE-NG.
@@lameaveragetechies1040 Thanks for getting back to me - much appreciated. I think you could be right about there being an issue with the images. I am going to wipe the Lab clean, and re-import them, including the older versions. I'll post my results👍
@@lameaveragetechies1040 Hello again, regarding the problem I was having with my QFX images on Eve-ng , where the "xe-0/0/0" interfaces were not showing, just the "em" interfaces - I have fixed the problem. The problem was that the PFE and RE file names were not the same, but they have to be the same. The PFE file was named "hda.qcow" and the RE file was named "hda.qcow2" . As soon as I named both files "hda.qcow2" and re-imported the nodes, I did a "show interfaces terse", this time the xe-0/0/0 - xe-0/0/11 interfaces appeared.
@@burnsybob70 The issue is due to a common problem in EVE-NG and vQFX images where you have to remove a few files from the shell on the QFX and then reboot the node.
Juniper is very obscure with this info but from testing it looks like it uses per-packet load balancing, which is actually per session load balancing. So I believe all of the above is used to determine the session.
Hello good morning, I'm new to the Juniper world, I'm having difficulty attaching the vlan to the interface, could you help with this issue commit [edit interfaces xe-0/0/1 unit 0 family] 'ethernet-switching' Family ethernet-switching and rest of the families are mutually exclusive error: commit failed: (statements constraint check failed)
Hey, you need to delete the full interface config first. It has some basic config by default. From edit mode you can just do “delete interfaces” and it will delete all config on all interfaces, then you can configure it from scratch with VLAN tagging etc 👍 Or if you dont want to delete all interface config, just do “delete interfaces xe-0/0/1” You will then just need to re-apply your config on this interface and it should go through. I usually just delete everything before I setup a new device.
@@lameaveragetechies1040 Good morning , I applied the commands below, it displays the following message .... root@vqfx-re# delete interfaces xe-0/0/1 warning: statement not found {master:0}[edit] root@vqfx-re# commit error: In routing-instance default-switch vlan vlan20 configured under interface xe-0/0/0.0 does not exist error: configuration checkout failed
I think the best is to just delete all the config on the switch as there seems to be conflicting config somewhere. At root level just type “delete”. Then set the root password otherwise it wont commit. Probably the safer bet at this point.
@@williamdasilvasantossantos7579 That implies that you are have pointed to a vlan under interface xe-0/0/0 that doesn't exist, meaning you haven't created the vlan under vlans yet. Like LAT said, it's easier to just delete all the interfaces by typing delete interfaces from the top of the config mode.
Hi, it depends. Do you have 2 SRX in a cluster? Or single SRX? If it is SRX in cluster then you need to use RETH interfaces. But if it is a single SRX then the config is the same yes. If you use LACP on thr Cisco, you need to use LACP on Juniper as well, there is a video on LACP also on the channel 👍
@@lameaveragetechies1040 and one thing sir, do you have tutorials how about srx load balancing 2 isp,but if i want the trafic like a zoom, teams through isp 1 and others trafic isp 2. thanks a lot
It is not so easy on SRX unfortunately. On Fortigate the separation of traffic is much easier, so I usually recommend people to use Fortigate in enterprise deployments
I got a new monitor that is higher resolution so I didnt notice that it was smaller than usual after the recording. Our config font will be increased in our next videos
LACP is not needed for Aggregated Ethernet to work. LACP is a control protocol which will be covered in a future video. As for the minimum-links statement, once your available "UP" interfaces go below the number of minimum links you have configured under the ae interface, the ae interface will go down. This is only used if you have a backup path via other interfaces, otherwise this statement does not really apply to your environment.
Hi sir, excellent tutorial! Thank you very much!👍
Great explanation man!
Glad you liked it!
Excellent tutorial, Thank you.
Hello there, I really enjoy your videos and I am trying to put my own skills into practice with Eve-ng. When I tried out the configuration from this video on the QFX images I kept getting messages saying "device not found" - with show int xe-0/0/0 terse. I can configure these interfaces, but they do not show up in the show commands.
The 10Gbit xe- Interfaces are displayed on the "show configuration" command, but not with the "show interfaces terse". With the "terse" command, the output displays the "em0 -14" interfaces. Do you recognize this? I've probably done something wrong somewhere when importing the images. Many thanks for any help
Appreciate the kind words! I had this issue a few times. Do you have both QFX images? The RE and control plane? Those have to be linked as well as in the video. Make sure that when you add them the versions are identical on both devices. Sometimes a reboot of both fixes this issue even if everything is correct. Seems like a bug with either the QFX images or EVE-NG.
@@lameaveragetechies1040 Thanks for getting back to me - much appreciated. I think you could be right about there being an issue with the images.
I am going to wipe the Lab clean, and re-import them, including the older versions.
I'll post my results👍
@@lameaveragetechies1040 Hello again, regarding the problem I was having with my QFX images on Eve-ng , where the "xe-0/0/0" interfaces were not showing, just the "em" interfaces - I have fixed the problem. The problem was that the PFE and RE file names were not the same, but they have to be the same.
The PFE file was named "hda.qcow" and the RE file was named "hda.qcow2" . As soon as I named both files "hda.qcow2" and re-imported the nodes, I did a "show interfaces terse", this time the xe-0/0/0 - xe-0/0/11 interfaces appeared.
@@burnsybob70 The issue is due to a common problem in EVE-NG and vQFX images where you have to remove a few files from the shell on the QFX and then reboot the node.
Do u know what hashing method it uses to load balance the traffic across the links? Does it use Source/Destination IP and TCP port?
Juniper is very obscure with this info but from testing it looks like it uses per-packet load balancing, which is actually per session load balancing. So I believe all of the above is used to determine the session.
you are gem buddy!!
Hello good morning, I'm new to the Juniper world, I'm having difficulty attaching the vlan to the interface, could you help with this issue
commit
[edit interfaces xe-0/0/1 unit 0 family]
'ethernet-switching'
Family ethernet-switching and rest of the families are mutually exclusive
error: commit failed: (statements constraint check failed)
Hey, you need to delete the full interface config first. It has some basic config by default. From edit mode you can just do “delete interfaces” and it will delete all config on all interfaces, then you can configure it from scratch with VLAN tagging etc 👍
Or if you dont want to delete all interface config, just do “delete interfaces xe-0/0/1” You will then just need to re-apply your config on this interface and it should go through.
I usually just delete everything before I setup a new device.
@@lameaveragetechies1040 Good morning ,
I applied the commands below, it displays the following message ....
root@vqfx-re# delete interfaces xe-0/0/1
warning: statement not found
{master:0}[edit]
root@vqfx-re# commit
error: In routing-instance default-switch vlan vlan20 configured under interface xe-0/0/0.0 does not exist
error: configuration checkout failed
I think the best is to just delete all the config on the switch as there seems to be conflicting config somewhere. At root level just type “delete”. Then set the root password otherwise it wont commit. Probably the safer bet at this point.
@@williamdasilvasantossantos7579 That implies that you are have pointed to a vlan under interface xe-0/0/0 that doesn't exist, meaning you haven't created the vlan under vlans yet. Like LAT said, it's easier to just delete all the interfaces by typing delete interfaces from the top of the config mode.
hello sir, how about juniper srx LAG to Cisco Layer 3 3560 , is the same config like this ? thanks
Hi, it depends. Do you have 2 SRX in a cluster? Or single SRX? If it is SRX in cluster then you need to use RETH interfaces. But if it is a single SRX then the config is the same yes. If you use LACP on thr Cisco, you need to use LACP on Juniper as well, there is a video on LACP also on the channel 👍
@@lameaveragetechies1040 and one thing sir, do you have tutorials how about srx load balancing 2 isp,but if i want the trafic like a zoom, teams through isp 1 and others trafic isp 2. thanks a lot
It is not so easy on SRX unfortunately. On Fortigate the separation of traffic is much easier, so I usually recommend people to use Fortigate in enterprise deployments
what simulation tool you're using..
We are using EVE-NG
use larger font size for config..
I got a new monitor that is higher resolution so I didnt notice that it was smaller than usual after the recording. Our config font will be increased in our next videos