Any one knows any other sollution to this issue?
I'm having the same problem here with EX2300C-12p and adding a L3 interface for every vlan, evein if it's not required is a bit silly, to say the least.
Any one knows any other sollution to this issue?
I'm having the same problem here with EX2300C-12p and adding a L3 interface for every vlan, evein if it's not required is a bit silly, to say the least.
Hi all, hope you are well !!!
I have an issue with ex3400 ( Junos 15.1X53-D58.3 ) where I want to setup specific MTU on an interface ge-3/0/10 which is a L2 Access port with a specific Vlan assigned to it.
I go edit interface ge-3/0/10 >> Set mtu 1500.
Then, set disable >> commit
then, delete disable >> commit
This is to make sure interface goes down and then up to be 100% sure that change will apply.
When I do this, the VLAN where my interfece belongs to has MTU 1500 instead of 1514.
How is it possible 1 physical port 's settings to affect the entire Vlan users and loose connectivity ?
Is there any other step that must be done before this setting is applied to the interface ?
Thanks in advance.
Same problem here. The running version is :
Model: ex4550-32f
Junos: 15.1R6.7
We have one 40G AE(4x10G), and the throughtput is around ~5G and output packets is dropping, and the subinterfaces are dropping averagely:
> show interfaces queue ae12
..
Transmitted:
Packets : 1509457580
Bytes : 2051157733767
Tail-dropped packets : 75213
> show interfaces queue xe-0/0/12
...
Transmitted:
Packets : 374696489
Bytes : 509184591187
Tail-dropped packets : 20902
> show interfaces queue xe-0/0/13
..
Packets : 376184274
Bytes : 511061534855
Tail-dropped packets : 18569
> show interfaces queue xe-0/0/14
...
Transmitted:
Packets : 382162947
Bytes : 519414409928
Tail-dropped packets : 16943
> show interfaces queue xe-0/0/15
...
Transmitted:
Packets : 384081876
Bytes : 521986740266
Tail-dropped packets : 19344
Does anyone upgrade the junos and fix the problem?
Hello this is my sh chasis lcd output please help me how can I resolve this error.
Juniper-EX4200-1> show chassis lcd
Front panel contents for slot: 0
---------------------------------
LCD screen:
00:RE NF-Juniper
LEDPD ALARM 03
LEDs status:
Alarms LED: Red
System LED: Green
Master LED: Green
Interface LED(ADM/SPD/DPX/POE)
-------------------------------------
ge-0/0/0 On:3 blinks per sec
ge-0/0/1 On:3 blinks per sec
ge-0/0/2 On:2 blinks per sec
ge-0/0/3 Off
ge-0/0/4 On:3 blinks per sec
ge-0/0/5 Off
ge-0/0/6 On:3 blinks per sec
ge-0/0/7 Off
ge-0/0/8 On:3 blinks per sec
ge-0/0/9 Off
ge-0/0/10 On:3 blinks per sec
ge-0/0/11 On:3 blinks per sec
ge-0/0/12 On:3 blinks per sec
ge-0/0/13 Off
ge-0/0/14 On:3 blinks per sec
ge-0/0/15 Off
ge-0/0/16 On:3 blinks per sec
ge-0/0/17 Off
ge-0/0/18 Off
ge-0/0/19 Off
ge-0/0/20 On:3 blinks per sec
ge-0/0/21 Off
ge-0/0/22 Off
ge-0/0/23 Off
ge-0/0/24 Off
ge-0/0/25 Off
ge-0/0/26 On:3 blinks per sec
ge-0/0/27 Off
ge-0/0/28 On:3 blinks per sec
ge-0/0/29 Off
ge-0/0/30 Off
ge-0/0/31 Off
ge-0/0/32 Off
ge-0/0/33 Off
ge-0/0/34 Off
ge-0/0/35 Off
ge-0/0/36 Off
ge-0/0/37 Off
ge-0/0/38 Off
ge-0/0/39 Off
ge-0/0/40 Off
ge-0/0/41 Off
ge-0/0/42 Off
ge-0/0/43 Off
ge-0/0/44 Off
ge-0/0/45 On:2 blinks per sec
ge-0/0/46 Off
ge-0/0/47 On:3 blinks per sec
It's like an ARP Proxy but for only one IP...
I'll post a response just to make it correct on this thread.
The
switchport nonegotiate
does not equal
ether-options { no-auto-negotiation; }
The equivalent cisco on this platform might be, speed nonegotiate, or specifying a speed with can disable autoneg.
You shouldn't be turning this off unless you have a specific requirement.
switchport nonnegoitate has to do with the ability to automatically detect and switch between an access or trunk port. (or to remove the ability in this case)
Remove the below and all should be fine.
speed 1g; ether-options { no-auto-negotiation; }
The poor Cisco is still trying to complete autonegotiation and correctly holding the port down.
Why interface-specific doesn't work for vlans?
set firewall policer 50Mbps filter-specific
set firewall policer 50Mbps if-exceeding bandwidth-limit 50m
set firewall policer 50Mbps if-exceeding burst-size-limit 10m
set firewall policer 50Mbps then discard
set firewall family ethernet-switching filter 50mbps-in interface-specific
set firewall family ethernet-switching filter 50mbps-in term 1 then policer 50Mbps
set firewall family ethernet-switching filter 50mbps-out interface-specific
set firewall family ethernet-switching filter 50mbps-out term 1 then policer 50Mbps
set vlans V10 vlan-id 10
set vlans V10 l3-interface irb.10
set vlans V10 forwarding-options filter input 50mbps-in
set vlans V10 forwarding-options filter output 50mbps-out
set vlans V20 vlan-id 20
set vlans V20 l3-interface irb.20
set vlans V20 forwarding-options filter input 50mbps-in
set vlans V20 forwarding-options filter output 50mbps-out
Commit error:
'filter'
Interface specific filter 50mbps-in cannot be as an FTF
I can to create a filter without interface-specific:
set firewall family ethernet-switching filter 50mbps-in term 1 then policer 50Mbps
set vlans V10 forwarding-options filter input 50mbps-in
I can use the same filter for vlan 10/20:
set vlans V10 forwarding-options filter input 50mbps-in
set vlans V20 forwarding-options filter input 50mbps-in
set vlans V10 forwarding-options filter input 50mbps-out
set vlans V20 forwarding-options filter input 50mbps-out
But in this case I think that the bandwith limits will be shared between the vlans.
So the vlans need independent bandwidth limits.
The configuration bellow will work if I use different names for the filters? Will be the bandwith limits all independent?
set firewall family ethernet-switching filter 50mbpsV10-in term 1 then policer 50Mbps
set firewall family ethernet-switching filter 50mbpsV10-out term 1 then policer 50Mbps
set firewall family ethernet-switching filter 50mbpsV20-in term 1 then policer 50Mbps
set firewall family ethernet-switching filter 50mbpsV20-out term 1 then policer 50Mbps
set vlans V10 forwarding-options filter input 50mbpsV10-in
set vlans V10 forwarding-options filter output 50mbpsV10-out
set vlans V20 forwarding-options filter input 50mbpsV20-in
set vlans V20 forwarding-options filter output 50mbpsV20-out
Well this is not new setup, the problem is prtg is working fine for a week maybe two and then all of our Juniper switches timeouts according to PRTG. While PRTG says switch down - ping down - I can ping the switch from other clients with no issue. I have to try ping it directly from PRTG and see if the host is the issue. But definitely, these alerts are not true, making PRTG being worthless.
Of course when open cases with both each other blame with no actual output. Its not only about 4300, its about other 2200 3300 too.
I was planning to use Nagios to monitor Juniper and just abandon PRTG (Windows2012 installation) troubleshooting.
I wonder fs you guys have any instructions on how to use Nagios to monitor Juniper switch. My plan is just monitored just one and see if these alerts are true. Does not have to be Nagios but another tool so I can try for a moment. Any thoughts?
Hello...you cannot add this sensor type to the Hosted Probe of a PRTG hosted by Paessler instance. If you want to use this sensor type, please add it to a remote probe device.
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the setting fields that are required for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change (nearly) all settings in the sensor's Settings tab later.
Hi Dave, I dont get it - so I cannot add it as SMTP traffic sensor on PRTG?
Try incognito, that usually does the trick for me.
Hi Guys,
I am trying to find out whether the QSFP ports on the back of the EX4300-24P switches support breakout cables?
I can see from older posts that back in 2014-2016 that it was not supported then - as listed on the old datasheets - as there was a clause that said they were not supported. This does not appear to be in the manuals or setup info anymore.
I have no idea of hardware of firmware on the pair of EX4300's that I have, as they are still in the box waiting to be commissioned.
Any help here would be appreciated.
Under at least 17.3 there is no channel-speed option on the EX4300, so I'd guess still no.
test@test# set chassis fpc 0 pic 1 ? Possible completions: + apply-groups Groups from which to inherit configuration data + apply-groups-except Don't inherit configuration data from these groups mlfr-uni-nni-bundles-inline Number of inline multilink frame relay UNI NNI bundles no-multi-rate Disable multi-rate mode> q-pic-large-buffer Run in large delay buffer mode
ALARM 03 means you have 3 alarms. You will need to use show chassis alarms from the CLI to list them.
As a matter of interest is that port still setup as a VCP port (which is the QSFP port default)?
Hello All,
I have some EX4200's on our network that are all in a switch stack (anywhere from 2 to 4 switches in each stack). They are on an extremely old code (10.4R9.2) and I have been going through and upgrading them to 15.1R7.9. Now obviously this will need two upgrades to get there and the path I took was 10.4R9.2 > 12.3R12.4 > 15.1R7.9.
I almost never run into problems with the latter half of this upgrade, but no matter what methods I use I always run into issues upgrading from 10.x to 12.x. I have tried multiple scenarios and I still cannot find a foolproof way to do these so I could comfortably do them remotely. I have seen issues like an FPC member coming up on a corrupt image and denying the install, an FPC member breaking away from the VC as "Not Present" in which that FPC was stuck in the bootup sequence, and even an issue where an FPC member crashed and went into db> mode.
I have tried every single way Juniper has recommended (at least from what I could find) on how to upgrade a switch stack of EX4200 switches in a VC.
Tried the normal way:
request system software add validate /var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz
request system reboot all-members
request system snapshot slice alternate
request system software add validate /var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz
request system reboot all-members
request system snapshot slice alternate
Tried the tedious way (with the jloader):
file copy fpc0:/var/tmp/jloader-ex-3242-12.1R3-signed.tgz fpc1:/var/tmp/
file copy fpc0:/var/tmp/jloader-ex-3242-12.1R3-signed.tgz fpc2:/var/tmp/
request system software add /var/tmp/jloader-ex-3242-12.1R3-signed.tgz member 2
request system software add /var/tmp/jloader-ex-3242-12.1R3-signed.tgz member 1
request system software add /var/tmp/jloader-ex-3242-12.1R3-signed.tgz member 0
file copy fpc0:/var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz fpc1:/var/tmp/
file copy fpc0:/var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz fpc2:/var/tmp/
request system software add validate /var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz member 2
request system software add validate /var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz member 1
request system software add validate /var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz member 0
request system reboot all-members
request system snapshot slice alternate
file copy fpc0:/var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz fpc1:/var/tmp/
file copy fpc0:/var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz fpc2:/var/tmp/
request system software add validate /var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz member 2
request system software add validate /var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz member 1
request system software add validate /var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz member 0
request system reboot all-members
request system snapshot slice alternate
Tried it without the jloader:
file copy fpc0:/var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz fpc1:/var/tmp/
file copy fpc0:/var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz fpc2:/var/tmp/
request system software add validate /var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz member 2
request system software add validate /var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz member 1
request system software add validate /var/tmp/jinstall-ex-4200-12.3R12.4-domestic-signed.tgz member 0
request system reboot all-members
request system snapshot slice alternate
file copy fpc0:/var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz fpc1:/var/tmp/
file copy fpc0:/var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz fpc2:/var/tmp/
request system software add validate /var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz member 2
request system software add validate /var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz member 1
request system software add validate /var/tmp/jinstall-ex-4200-15.1R7.9-domestic-signed.tgz member 0
request system reboot all-members
request system snapshot slice alternate
And even now in the lab consoled in I tried it the normal way again but this time added the jloader, rebooted, then added the jinstall for 12., rebooted and FPC 0 did not take the upgrade. Received the below error during bootup sequence.
gzip: stdin: invalid compressed data--format violated
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
*** The installer exited with status 2 ***
*** The installation is unsuccessful!!! ***
A shell has been started. type exit<cr> to reboot:
Any suggestions would be greatly appreciated.
Hi,
I beilive the upgrade path would be 10.4 -> 11.4 -> 12.X-> 15.x
But i dont see 11.X version in our support site since its end of support.
Would you be able to try a USB install ? Ofcourse this will erase all your existing configuration.
You may need to take a backup in that case.
-Ajo Thomas
It was my understanding that you can push an upgrade between two version releases at a time. Is there some sort of exception regarding the 10.x versions that I am unaware of?
That's another thing. The "tedious" way I posted earlier, I have tested that multiple times in a lab setting on a two switch stack, however when I went to implement this on a three switch stack remotely FPC 2 broke and went into db> mode.
EDIT: To be a little more precise you can upgrade between 2 service releases and 3 extended releases IIRC.
Last time I got information on this subject, I was told it is a hardware-limitation in the switching ASIC used in the EX4300 - so the QSFP ports will never able to be channelized into 4x10G.
I believe I know the issue that I was seeing in the lab. I never had the date set and it was pulling an install package that was signed at a later date than what the switch is on.
That answers the lab... Not the other issues, however.