Send the output of show vlans extensive. Cut and paste into text file, and attach the file.
Re: Adding a EX2300-C POE+ switch to a Pair of EX3300 Switches in a Virtual Chassis Configuration
Re: Adding a EX2300-C POE+ switch to a Pair of EX3300 Switches in a Virtual Chassis Configuration
rccpgm wrote:Send the output of show vlans extensive. Cut and paste into text file, and attach the file.
Here is the file...
Re: Adding a EX2300-C POE+ switch to a Pair of EX3300 Switches in a Virtual Chassis Configuration
Based on the file I attached, I see no reference to Vlan 0.. It seems to be working, but I am still confused why Vlan 0 is tied to ae1 and ae2. Once again, I am wondering if the ports used in the aggregration link is still tied to vlan 0.
Re: Adding a EX2300-C POE+ switch to a Pair of EX3300 Switches in a Virtual Chassis Configuration
I am going to assume your AE's 1 and 2 are tagged trunks and are set with vlan member all. This is why they are also associated with VLAN 0 - I believe.
There will be no harm in having VLAN 0 (which has no other members) being a part of these AE's. I see that VLAN 1 is associated with AE0.0. If you change AE 1 and 2 to have member VLANs of 1-4094 (or something similar) then the VLAN 0 reference should go away.
This is my best guess. Using VLAN 0 was stupid idea to start with, which is corrected in later SW. You could always use later code and factory default the switch, and then re-add saved config, and VLAN 0 nonsense should go away as well.
Up to you which path you take. If it was me, I'd probably set the AE 1 and 2 members to 1-4094 (or similar).
Good luck.
Re: Alternatives for ring topology - EX3400/EX4600
The answer is to use ERPS (G.8032). This is supported on many EX switches, and I "THINK" it should also be there on EX3400, but I am not 100% sure, and documentation is not clear. This support is there on EX4600 and EX4300, as well legacy EX switches, that is why I 'think' it should be there on EX3400. For info see this link:
Since VC itself is actually a ring topology (ISIS under the cover, L2 on top) you could make such a configuration easily with a mixed-chassis of EX4600 and EX4300. Unfortunately, you have EX3400 which can NOT VC with EX4600.
I'd really suggest you discuss your needs (which I assume are some what based on Fiber plant lay-out) with your Juniper Partner or Sales team to come-up with the best approach. Of course xSTP will work for this, but there might be better alternatives depending upon your exact needs.
Good luck.
Re: Alternatives for ring topology - EX3400/EX4600
Thanks for your reply.
Well, that was one thought that I had first, to make larger VCs since each can consist of 10 devices we chould group the 7 chassis down to 3 chassis. But we still would have to connect the 3 chassis together and "uplink" them to the ex4600 that is the distribution point in this case.
Regarding ERPS, well looking at the feature navigatet most EX models seems to support it, even the smaller compact versions, but for some reason the EX3400 isen't listed and the command is not available in the cli either. Feels a bit strange since we have some old EX3300, and they seems to support ERPS.
I have raised the question with our Juniper partner, but I still would like to educate my self and hear thought and ideas from the user community.
Best regards,
Johan Christensson
Re: Alternatives for ring topology - EX3400/EX4600
Hi Johan,
you are right in your finding regards EX3400. It does not support ERPS which brings you down to classic xSTP.
An option for lowering the impact for a break in the ring could be doing two links on each hop and bundle them together in an aggregated ethernet (ae) interface which keeps the logical link up in case of optics failure or repatch error in a patchpanel. Not pretty but better than nothing.
Alternatively you could look into some (passive) DWDM multiplexers with OADM's beside each EX3400 VC making it possible for you to connect all EX3400 VC's directly to the EX4600 VC via ae's. This would require single mode cabling all over and some extra cost for optics, multiplexers and OADM's...
Re: Adding a EX2300-C POE+ switch to a Pair of EX3300 Switches in a Virtual Chassis Configuration
rccpgm wrote:I am going to assume your AE's 1 and 2 are tagged trunks and are set with vlan member all. This is why they are also associated with VLAN 0 - I believe.
There will be no harm in having VLAN 0 (which has no other members) being a part of these AE's. I see that VLAN 1 is associated with AE0.0. If you change AE 1 and 2 to have member VLANs of 1-4094 (or something similar) then the VLAN 0 reference should go away.
This is my best guess. Using VLAN 0 was stupid idea to start with, which is corrected in later SW. You could always use later code and factory default the switch, and then re-add saved config, and VLAN 0 nonsense should go away as well.
Up to you which path you take. If it was me, I'd probably set the AE 1 and 2 members to 1-4094 (or similar).
Good luck.
The ae1 and ae2 LACP has only VLAN 30 and VLAN 2000. VLAN 0 is not assigned (see attachment). So I am still confused on what is going on.
QSFP28 DAC cables causing packet loss and framing issues
So the systems I am using are MX960 MPC7e.
When I use the 1meter 100G DAC I have zero errors + zero packet loss.
When I use the 3meter 100G DAC cables I have packet loss & framing errors. I tried 3 DAC cables on 2 different sets of routers…all MX960 MPC7e.
These are 3rd party DAC cables, all from the same place, but what I do not understand is why the 1M cables work and the 3M are giving me errors. The only difference between the cables that I have noticed is that the 3M are 28AWG and the 1M are 30AWG.
Any ideas as to what the issue is? I would think it was just a bad cable, but all 3 of them seems a little strange.
Remove interface from range
I need to change an interface from a trunk to an access port. Here's the current config:
interface-range wireless-ap-ports {
member-range ge-4/0/36 to ge-4/0/47;
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ Wireless CSMSBYOD ];
}
native-vlan-id 5;
}
}
}
Interface ge-4/0/36 is a trunk port and a member of a few VLANs. I need to remove it and make it an access port in a single VLAN. The vendor that installed/configured my EX switches are no longer in business and I do not have the required knowledge of the JunOS to be able to make these type of changes.
Re: Remove interface from range
Hi,
Basicly you need following lines;
delete interface-range wireless-ap-ports member-range
set interface-range wireless-ap-ports member-range ge-4/0/37 to ge-4/0/47
set interfaces ge-4/0/36.0 family ethernet-switching port-mode access vlan members VLAN-NAME
By the way,
If you using 12.3xx version, lets say one of the ports are configured within range and it's configured single, the single configuration will override the range config. For example if you have following 3 lines;
set interface-range wireless-ap-ports member-range ge-4/0/36 to ge-4/0/47
set interface-range wireless-ap-ports unit 0 port-mode trunk vlan members [ Wireless CSMSBYOD ]
set interfaces ge-4/0/36.0 family ethernet-switching port-mode access vlan members VLAN-NAME
ge-4/0/36 interface will be a access port. But this is a dangerous configuration, because one day you decide to upgrade your device to 15.xx version -while those 3 lines are in configuration- ethernet switching of device wil stop, it's like a bug or something.
My opinion is never use range configuration.
I hope it is clean.
MCLAG Question
Hi there,
I have two QFX10K, connected between them with
2x40 for ICCP connectivity - ae0 Layer3
2x100 for ICL connectivity - ae1 as trunk
The MC-AE's interfaces connected to 2 QFX5K
the iccp is up, the mc-ae interfaces are up
I might be missing something, but on some manuals i saw that the ICCP link and the loopback0 of the machine should be familiar by routing, i saw it was done by ospf as both bounded to are 0.0.0.0
lo0 uses as the iccp endpoints of the machine, and I guess as ae0 serves as the ICCP links, some kind of routing is needed.
on my example, the lo0 is internet routable, the sh route indicates the peer iccp is routed through the switch layer 3 feeds (isis). in this case:
how would i know ae0 does anything?
how would i know that internet goes off (both links) - iccp can still communicate via ae0?
should i use static to route iccp peers across the ae0 with higher metric?
should i run routing protocol between ae0's?
i'm sure i'm missing something here. will appriciate your help.
Uplink from EX3300 VC to EX2300-C not passing traffic for Default Vlan (1)
I need your help. Attached are configuration files for the EX3300 and EX2300 switches.
I have setup a 20GB uplink from the EX3300 VC to the EX2300 switch using a link aggregation interface. The LACP on EX3300 is ae3 and on the EX2300 is ae0. Both interfaces are up and running and seems to be working.
On the EX3300 I have configured Vlan 30 (Guest_Network) and Vlan 1 (default) which is carried over the trunk ae3 interface to the EX2300 switch. Vlan 1 is setup as the native vlan. Vlan 1 and Vlan 30 are setup as RVIs on the EX3300. Vlan 1 subnet is 192.168.1.0/24 and Vlan 30 subnet is 192.168.30.0/24.
On the EX2300, I have configured Vlan 30 (Guest_Network). Vlan 1 (default) is aready setup by factory default; however it is not showing up in the configuration file attached. I have not setup RVIs for Vlan 1 or Vlan 30. Vlan30 and Vlan 1 is carried over the trunk ae0 interface to the EX3300 VC switch. On the EX2300 all the ports have Vlan 1 (default) assigned and the first 4 ports also have VLAN 30.
I have attached my laptop to port 9 on the EX2300 which is assigned Vlan 1 (default) and configured my Iaptop with the following network information:
IP = 192.168.1.160
SubNet = 255.255.255.0
Gateway = 192.168.1.2 (This is the IP address of the RVI for Vlan 1 on the EX3300 VC)
For some reason, I cannot ping any IP address on the 192.168.1.0/24 subnet. Also I am unable to connect to the Internet.
What am I doing wrong? Please help..
Re: Uplink from EX3300 VC to EX2300-C not passing traffic for Default Vlan (1)
Could it be related to my static route information on the EX2300.
On the EX3300, the static route must point to my pfSense router which is 10.1.1.6.
Re: Uplink from EX3300 VC to EX2300-C not passing traffic for Default Vlan (1)
I did some more troubleshooting.. Trying to convince myself that this is a routing issue, but not sure.
I have setup out-of-band management for the management port on the EX2300. It is assigned an IP of 192.168.99.30 and is connected to one of Vlan 99 management ports on the EX3300. That is working fine.
I connected to the console port on the EX2300 via a serial connection. As long as I have management cable connected on the EX2300, I can ping all the RVIs on the EX3300. When I disconnect the management cable and ping the RVIs on the EX3300, I get a message "No route to host" message.
So do I have a routing issue or an issue with the link aggregation interfaces?
FYI.. The static route on the EX2300 is 0.0.0.0/0 -> Next Hop 192.168.99.1
Re: Uplink from EX3300 VC to EX2300-C not passing traffic for Default Vlan (1)
The link aggregation interface on both switches (EX2300 & EX3300) will be carrying tagged traffic on VLAN 30 and untagged traffic from the native Vlan (which is VLAN (1) default). That is my understanding.
Re: Uplink from EX3300 VC to EX2300-C not passing traffic for Default Vlan (1)
Re: Uplink from EX3300 VC to EX2300-C not passing traffic for Default Vlan (1)
EX-2300 15.1X53-D56 DHCP snooping untrust on trunk
Hi Guys
I seems to have a big problem with configuring trunks as untrusted interfaces.
I can not find the way to override a default configuration of DHCP trust on trunk ports.
Can you please help.
show vlans VL-998 forwarding-options dhcp-security
group UNTRUST {
overrides {
##
## Warning: statement ignored: unsupported platform (ex2300-24p)
##
untrusted;
}
}