Hello all,
We've got a QFX5100-48S with on a single port 'family ethernet-switching' and 'family inet' configuration.
This has worked for a long time, and by committing this configuration back then, the device didn't stop us.
Later on, we committed another 'family inet' unit on this port and the 'family ethernet-switching' part just stopped working.
The existing 'family inet' part kept on working.
Is this something only SRX, EX and MX devices stop you from committing?
Beeelze
Hi Logtech,
This has a diagram for the VC:
This includes the VC configuration steps:
Please let me know if this helps.
Regards,
-r.
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated 
.
Thank you so much -r
Hi there,
We can configure one family on unit 0. If you meant, multiple subinterfaces/units with different families then you can use the "flexible-ethernet-services" feature for this config on same physical interface:
https://www.juniper.net/documentation/en_US/junos/topics/topic-map/switches-interface-flexible.html
https://www.juniper.net/documentation/en_US/junos/topics/topic-map/switches-interface-flexible.html
The feature is not supported on Juniper EX4xxx/EX3xxx/EX2xxx series products. However you may always use L2-switched subinterfaces/units with a vlan configured with a vlan-id. Then configure an irb interface assigned to that vlan and if L3 services are needed, add an IP to this IRB based on the new ELS-style config for switching products supported from 12.3R2 onwards).
https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/getting-started-els.html
Hope this helps.
Regards,
-r.
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated .
Hope this helps.
Regards,
-r.
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated .
Hi -r,
Thanks for your response.
Only 1 family on unit 0, got it! But that's not what we have here.
Our QFX accepts the following configuration, 'family ethernet-switching' and 'family inet' on the same interface.
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members [ couple of VLANs ];
}
}
}
unit 10 {
vlan-id 10;
family inet {
address x.x.x.x/30;
}
}After configuring unit 10, but then for 2 different VLANs, the 'family ethernet-switching' portion doesn't work anymore.
So what I'm asking is, can the 'family ethernet-switching' and 'family inet' familes coexist on the same interface?
Beelze
Hi Beeelzebub,
What's the Junos version on your QFX5100? From the reference links:
"On QFX5100 switches, you can combine encapsulations on the same physical interface for vlan-bridge and family ethernet switching. Starting with Junos OS Release 16.1R6, you can also combine encapsulations on the same physical interface for family inet and family ethernet-switching."
Hope this helps.
Regards,
-r.
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated .
Hi -r,
beelze@qfx5100-nkh-01> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx5100-nkh-01
Model: qfx5100-48s-6q
Junos: 14.1X53-D45.3
Were you able to find out the cause of the "Port high non-unicast traffic"? I'm seeing similar events on most of my switches but haven't been able to find anything with Wireshark.
Hi hmorton,
While hoping starlog could respond on the old post...
Perhaps you could toggle mirroring different ports and analyze packets (wireshark) with each. In Wireshark, "Statistics>End Points" will help find the top talkers (IP/MAC). If traffic to any one MAC doesn't stand out, try to check a few different MACs and compare the MAC table "show ethernet-switching table" on the switch if they are all known.
Hope this helps.
Regards,
-r.
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated .
Hi
I found a problem on my switch on last week. I have 5 unit of EX4300 within mix virtual chassis. version is 14.1X53-D30.3 All IRB route is not shown in routing table. I have to reboot it after that It will show again.
I try to get a log message it. Output as attached. There was a interesting in one log message.
"PYH-FL17-EX4300-Core chassisd[1184]: CHASSISD_IPC_FLUSH_ERROR: ch_flush_fru_pipe: flush operation failed for LCD 4"
PYH-FL17-EX4300-Core chassisd[1184]: CHASSISD_FRU_IPC_WRITE_ERROR: fru_send_msg: FRU LCD 4, errno 40, Message too long"
Have you ever seen these log messeage??
Thanks!
Hi Halo,
Please check this for the explanation: https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1038830
Based on this, Junos version JUNOS 14.1X53-D30.3 is affected and this issue is resolved in following releases and upwards:
14.1X53-D37 14.1X53-D39 14.1X53-D40 15.1R4.
It might be based to upgrade to the recommended version:
https://kb.juniper.net/InfoCenter/index?page=content&id=KB21476&actp=METADATA
Hope this helps.
Regards,
-r.
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated .
Hi
Thank you for your response.
I've followed your link. I will try to upgrade to recommended version but Is it a root cause which make my switch has no installed IRB route???
Hi Halo,
The PR is for the chassisd error log.
The IRB route issue should be different. If you've seen reboot resolves it, does the route disappear on its own again or is there a pattern (specific trigger/time period etc.) ? It could be due to duplicate IPs. For that you may check this when the IRB is showing up fine:
show irb extensive ----> Look for "Duplicate" flag
show log messages | match DAD ------> Look for "DAD" messages
Other than that, there's little reason for IRB route to vanish. Please check if there's any other trigger or error messages seen related to RPD - "show log messages | match "irb|rpd".
After checking the above, if none of thes points to the problem, it wouldn't hurt upgrading to resolve the chassisd issue and then monitor for the IRB issue.
Hope this helps. Please let me know.
Regards,
-r.
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated .
Let me check on my device
Thank you for yor prompt response!
Hi mriyaz,
Is it written somewhere that combining "family ethernet-switching" and "family inet" on the same interface is not supported?
I just need to be sure that my QFX5100 switches aren't broken, or that this type of switch has this as a "bug".
Thanks for checking this out!
Beelze
Experts,
We are going to expand our infrastructure by adding using 60-90 IP cameras, by adding them to current IDFs and MDF. Creating another vlan for such network is not an issue. The traffic inside will be expanding since these cameras send all the time traffic to the main DVR. Having in network currently 1000 end devices and using EX 3300 & EX 4300 switches should not be a problem correct? Any specific QoS on juniper for cameras or just separate VLAN? Any other thoughts?
Thank you
The feature that allows mixing of family inet and ethernet services is setting the interface to flexible vlan tagging. This is not supported on all platforms so you will need to see if you can use it.
When you do you won't have all the members on unit 0 but you will need to call out each vlan tag on a separate subinterface. And also each vlan tag with the family inet ports.
here is a short example:
root@steve> show configuration interfaces fe-0/0/2
flexible-vlan-tagging;
unit 1 {
vlan-id 20;
family inet {
address 192.168.10.11/31;
}
}
unit 2 {
vlan-id 30;
family ethernet-switching;
}
unit 3 {
vlan-id 40;
family ethernet-switching;
}I also think you can do this on devices that have flexible ethernet services as an option, but don't have a box handy to confirm that with. Try that if flexible vlan tagging is not an option on the qfx5100.
I found a similar issue in my customer's EX4300MP.
may I know what the exact hardware and junos version are you using, if possible would you share me the output "show chassis hardware" and "show version"
thank you very much.