Hi,
today we added an update to the version in the subject on an EX4200 switch. At the time of rebooting all the VoIP phones were not registered and in the system we noticed errors such as
"eswd [1398]: ESWD_DAI_FAILED: 2 ARP_REPLY received, interface ge-0/0 / 18.0 [index 146], vlan .... ".
With the 12.3R12-S12 they never happened to us. How can it be solved? We have already tried to disable and reabilitate the DAI but without a positive outcome.
Thanks in advance
Hi guys
I have a VC with QFX5110. when master sw. shut down, back-up sw take master role is spend more than 2 minutes.
İs it a normal or there is some problem do you think?
thanks for all reply
Hello,
I have virtual chassis with 2 EX2300 switches. Today, I saw red led on one of the switches, but I couldn't find the reason of that.
How can I find the issue?
{master:0}
root> show chassis led
LED status for: FPC 0
-----------------------------------
LEDs status:
Alarm LED : Red
System LED: Green
Master LED: Green
Interface LED(SPD/DPX/ADM/POE)
-------------------------------------
ge-0/0/0 Green
ge-0/0/1 Green
ge-0/0/2 Green
ge-0/0/3 Off
ge-0/0/4 Off
ge-0/0/5 Off
ge-0/0/6 Off
ge-0/0/7 Off
ge-0/0/8 Off
ge-0/0/9 Off
ge-0/0/10 Off
ge-0/0/11 Off
ge-0/0/12 Off
ge-0/0/13 Off
ge-0/0/14 Off
ge-0/0/15 Off
ge-0/0/16 Off
ge-0/0/17 Off
ge-0/0/18 Off
ge-0/0/19 Off
ge-0/0/20 Off
ge-0/0/21 Off
ge-0/0/22 Off
ge-0/0/23 Off
LED status for: FPC 1
-----------------------------------
LEDs status:
Alarm LED : Yellow
Beacon LED: Beacon ON
System LED: Green
Master LED: Green Blinking
Phone Home LED: Green
Interface LED(SPD/DPX/ADM/POE)
-------------------------------------
ge-1/0/0 Green
ge-1/0/1 Green
ge-1/0/2 Green
ge-1/0/3 Off
ge-1/0/4 Off
ge-1/0/5 Off
ge-1/0/6 Off
ge-1/0/7 Off
ge-1/0/8 Off
ge-1/0/9 Off
ge-1/0/10 Green
ge-1/0/11 Off
ge-1/0/12 Off
ge-1/0/13 Off
ge-1/0/14 Off
ge-1/0/15 Off
ge-1/0/16 Off
ge-1/0/17 Off
ge-1/0/18 Off
ge-1/0/19 Off
ge-1/0/20 Off
ge-1/0/21 Off
ge-1/0/22 Off
ge-1/0/23 Off
root> show chassis alarms
2 alarms currently active
Alarm time Class Description
1970-01-01 01:11:35 UTC Major Host 1 me0 : Ethernet Link Down
2000-01-02 01:02:23 UTC Major Host 0 me0 : Ethernet Link Down
root> show system alarms
2 alarms currently active
Alarm time Class Description
1970-01-01 01:11:35 UTC Major Host 1 me0 : Ethernet Link Down
2000-01-02 01:02:23 UTC Major Host 0 me0 : Ethernet Link Down
root> show chassis fpc pic-status
Slot 0 Online EX2300-24T
PIC 0 Online 24x10/100/1000 Base-T
PIC 1 Online 4x10G SFP/SFP+
Slot 1 Online EX2300-24T
PIC 0 Online 24x10/100/1000 Base-T
PIC 1 Online 4x10G SFP/SFP+
root> show chassis environment
Class Item Status Measurement
Power FPC 0 Power Supply 0 OK
FPC 1 Power Supply 0 OK
Temp FPC 0 CPU Sensor OK 37 degrees C / 98 degrees F
FPC 0 PSU Sensor OK 29 degrees C / 84 degrees F
FPC 1 CPU Sensor OK 37 degrees C / 98 degrees F
FPC 1 PSU Sensor OK 28 degrees C / 82 degrees F
Fans FPC 0 Fan Tray 0 OK Spinning at normal speed
FPC 1 Fan Tray 0 OK Spinning at normal speed
root> show virtual-chassis status
Virtual Chassis ID: a374.14cf.38cb
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID Interface
0 (FPC 0) Prsnt JZ0219300138 ex2300-24t 255 Master* N VC 1 vcp-255/1/0
1 (FPC 1) Prsnt JZ0219300194 ex2300-24t 255 Backup N VC 0 vcp-255/1/0
root> show chassis environment routing-engine
Routing Engine 0 status:
State Online Master
Temperature 37 degrees C / 98 degrees F
Routing Engine 1 status:
State Online Standby
Temperature 37 degrees C / 98 degrees F
root> show chassis power-budget-statistics
fpc 0:
-------------------------------------------------------------------------
PSU 0 (JPSU-65W-AC-AFO ) : 65 W Online
Power redundancy configuration : N+0
Total power supplied by all online PSUs : 65 W
Base power reserved : 55 W
fpc 1:
-------------------------------------------------------------------------
PSU 0 (JPSU-65W-AC-AFO ) : 65 W Online
Power redundancy configuration : N+0
Total power supplied by all online PSUs : 65 W
Base power reserved : 55 W
root> show chassis temperature-thresholds
Fan speed Yellow alarm Red alarm Fire Shutdown
(degrees C) (degrees C) (degrees C) (degrees C)
Item Normal High Normal Bad fan Normal Bad fan Normal
FPC 0 CPU Sensor 45 52 63 63 71 71 76
FPC 0 PSU Sensor 37 42 57 57 65 65 71
FPC 1 CPU Sensor 45 61 63 63 71 71 76
FPC 1 PSU Sensor 37 55 57 57 65 65 71
hello All
can you help with Juniper switch EX4550 , i have an issue where it blocks traffic from routers connected to it, phyisically interfaces are up, but i can not ping the connected IP, this don't happen for all connected router, it disconnect some routers.
and this is solved by rebooting the switch
from logs i am seeing this errors
Dec 18 16:13:30 chassism[1203]: validate_configuration (626) config validation failed pic 0xf04c port 13 xcvr_type 0 AN 0 speed 2 duplex 0
Dec 18 16:13:30 chassism[1203]: validate_configuration (626) config validation failed pic 0xf04c port 13 xcvr_type 0 AN 0 speed 2 duplex 0
Dec 18 16:13:56 mib2d[1320]: SNMP_TRAP_LINK_DOWN: ifIndex 527, ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/x
Dec 18 16:13:57 mib2d[1320]: SNMP_TRAP_LINK_DOWN: ifIndex 526, ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/y
Dec 18 16:13:59 chassism[1203]: validate_configuration (626) config validation failed pic 0xf04c port 13 xcvr_type 0 AN 0 speed 2 duplex 0
Dec 18 16:14:02 chassism[1203]: validate_configuration (626) config validation failed pic 0xf04c port 14 xcvr_type 0 AN 0 speed 2 duplex 0
Dec 18 16:14:09 sfid[1204]: SFID: DMA Tx Watchdog has been discardfor dev 1, queue 0
Dec 18 16:14:12 sfid[1204]: SFID: DMA Tx Watchdog has been discardfor dev 1, queue 0
Dec 18 16:14:14 sfid[1204]: SFID: DMA Tx Watchdog has been discardfor dev 1, queue 7
Dec 18 16:14:19 sfid[1204]: SFID: DMA Tx Watchdog has been discardfor dev 1, queue 7
Dec 18 16:14:27 mib2d[1320]: SNMP_TRAP_LINK_DOWN: ifIndex 527, ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/x
Dec 18 16:14:27 mib2d[1320]: SNMP_TRAP_LINK_DOWN: ifIndex 526, ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/y
Dec 18 16:14:29 chassism[1203]: validate_configuration (626) config validation failed pic 0xf04c port 14 xcvr_type 0 AN 0 speed 2 duplex
i am running this version
Model: ex4550-32t
Junos: 15.1R7.8
JUNOS EX Software Suite [15.1R7.8]
JUNOS FIPS mode utilities [15.1R7.8]
JUNOS Crypto Software Suite [15.1R7.8]
JUNOS Online Documentation [15.1R7.8]
JUNOS EX 4500 Software Suite [15.1R7.8]
JUNOS Web Management Platform Package [15.1R7.8]
can you check and advise why this issue is happening to the switch.
Hi All,
When looking at the NX-OS switch' features, some of them are below...... I like to ask which Juniper switch platform or series has the same or similar features?
High availability:
- VDC (Virtual Device Context, it can be created many virtual NX-OS for Fault Isolation).
Security:
-Virtual Port Channel -vPC
-Encryption 802.1ae Macsee
-Control Plane Policing -CoPP
Embedded Services:
-SPAN
-ERSPAN
-NetFlow
Hi all,
I've a bit of a strange one - dhcp has been working without issue for some time but today we came in and it's not!
The config hasn't changed however "show dhcp statistics" is showing packets dropped with majority of them being "Switchover recovery". Unfortuanately syslog has been off for a while so I don't have any useful information there. Virtual chasis doesn't look to have changed recently either.
traceoptions doesn't seem to provide much information either...
I have restarted the process but no change. I tried to remove the configuration under access>address-assignment and system>services>dhcp-local-server but it's saying there's bindings so I can't remove it... But I've already removed the bindings but no change...
Anyone got any thoughts as to what may be causing it? I may have to reboot it but really don't want to as it's a pretty important switch in a pretty inaccable place if there's any issues!
Hello,
I wonder if someone can help. We are experiencing issues with our optical ports between QFX5100 and EX4300 since we rebooted our EX4300 switch.
On our EX4300 the switch port is showing as down when I look at the status and the physical port light is also off
show interfaces et-0/1/3 terse Interface Admin Link Proto Local Remote et-0/1/3 up down et-0/1/3.100 up down aenet --> ae0.100 et-0/1/3.32767 up down aenet --> ae0.32767
But when I use “show interfaces diagnostics optics” it is both sending and receiving laser from the port
show interfaces diagnostics optics
Physical interface: et-0/1/3
Module temperature : 34 degrees C / 93 degrees F
Module voltage : 3.1840 V
Module temperature high alarm : Off
Module temperature low alarm : Off
Module temperature high warning : Off
Module temperature low warning : Off
Module voltage high alarm : Off
Module voltage low alarm : Off
Module voltage high warning : Off
Module voltage low warning : Off
Module temperature high alarm threshold : 85 degrees C / 185 degrees F
Module temperature low alarm threshold : -10 degrees C / 14 degrees F
Module temperature high warning threshold : 70 degrees C / 158 degrees F
Module temperature low warning threshold : 0 degrees C / 32 degrees F
Module voltage high alarm threshold : 3.5990 V
Module voltage low alarm threshold : 2.9000 V
Module voltage high warning threshold : 3.5000 V
Module voltage low warning threshold : 3.0990 V
Laser bias current high alarm threshold : 15.000 mA
Laser bias current low alarm threshold : 0.000 mA
Laser bias current high warning threshold : 12.000 mA
Laser bias current low warning threshold : 2.000 mA
Laser output power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser output power low alarm threshold : 0.0871 mW / -10.60 dBm
Laser output power high warning threshold : 1.7378 mW / 2.40 dBm
Laser output power low warning threshold : 0.1738 mW / -7.60 dBm
Laser rx power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser rx power low alarm threshold : 0.0158 mW / -18.01 dBm
Laser rx power high warning threshold : 1.5849 mW / 2.00 dBm
Laser rx power low warning threshold : 0.0316 mW / -15.00 dBm
Lane 0
Laser bias current : 5.159 mA
Laser output power : 0.903 mW / -0.44 dBm
Laser receiver power : 0.463 mW / -3.35 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Tx laser disabled alarm : Off
Lane 1
Laser bias current : 5.113 mA
Laser output power : 0.895 mW / -0.48 dBm
Laser receiver power : 0.856 mW / -0.67 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Tx laser disabled alarm : Off
Lane 2
Laser bias current : 5.093 mA
Laser output power : 0.891 mW / -0.50 dBm
Laser receiver power : 0.994 mW / -0.02 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Tx laser disabled alarm : Off
Lane 3
Laser bias current : 5.193 mA
Laser output power : 0.909 mW / -0.41 dBm
Laser receiver power : 1.035 mW / 0.15 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Tx laser disabled alarm : OffOn the QFX5100 the light on the port is on but the “et” interface is down but instead it is showing that port as multiple xe interfaces and showing them as up
xe-1/0/53:0 up up xe-1/0/53:1 up up xe-1/0/53:2 up up xe-1/0/53:3 up up
Also “show interfaces diagnostics optics” shows that there are four xe interfaces rather than an et interface
Physical interface: xe-1/0/53:0
Module temperature : 36 degrees C / 97 degrees F
Module voltage : 3.2400 V
Module temperature high alarm : Off
Module temperature low alarm : Off
Module temperature high warning : Off
Module temperature low warning : Off
Module voltage high alarm : Off
Module voltage low alarm : Off
Module voltage high warning : Off
Module voltage low warning : Off
Module temperature high alarm threshold : 85 degrees C / 185 degrees F
Module temperature low alarm threshold : -10 degrees C / 14 degrees F
Module temperature high warning threshold : 70 degrees C / 158 degrees F
Module temperature low warning threshold : 0 degrees C / 32 degrees F
Module voltage high alarm threshold : 3.5990 V
Module voltage low alarm threshold : 2.9000 V
Module voltage high warning threshold : 3.5000 V
Module voltage low warning threshold : 3.0990 V
Laser bias current high alarm threshold : 15.000 mA
Laser bias current low alarm threshold : 0.000 mA
Laser bias current high warning threshold : 12.000 mA
Laser bias current low warning threshold : 2.000 mA
Laser output power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser output power low alarm threshold : 0.0871 mW / -10.60 dBm
Laser output power high warning threshold : 1.7378 mW / 2.40 dBm
Laser output power low warning threshold : 0.1738 mW / -7.60 dBm
Laser rx power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser rx power low alarm threshold : 0.0158 mW / -18.01 dBm
Laser rx power high warning threshold : 1.5849 mW / 2.00 dBm
Laser rx power low warning threshold : 0.0316 mW / -15.00 dBm
Lane 0
Laser bias current : 5.288 mA
Laser output power : 0.925 mW / -0.34 dBm
Laser receiver power : 0.913 mW / -0.40 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 1
Laser bias current : 5.328 mA
Laser output power : 0.932 mW / -0.30 dBm
Laser receiver power : 0.814 mW / -0.89 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 2
Laser bias current : 5.460 mA
Laser output power : 0.955 mW / -0.20 dBm
Laser receiver power : 0.972 mW / -0.12 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 3
Laser bias current : 5.394 mA
Laser output power : 0.944 mW / -0.25 dBm
Laser receiver power : 0.954 mW / -0.21 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Physical interface: xe-1/0/53:1
Module temperature : 36 degrees C / 97 degrees F
Module voltage : 3.2400 V
Module temperature high alarm : Off
Module temperature low alarm : Off
Module temperature high warning : Off
Module temperature low warning : Off
Module voltage high alarm : Off
Module voltage low alarm : Off
Module voltage high warning : Off
Module voltage low warning : Off
Module temperature high alarm threshold : 85 degrees C / 185 degrees F
Module temperature low alarm threshold : -10 degrees C / 14 degrees F
Module temperature high warning threshold : 70 degrees C / 158 degrees F
Module temperature low warning threshold : 0 degrees C / 32 degrees F
Module voltage high alarm threshold : 3.5990 V
Module voltage low alarm threshold : 2.9000 V
Module voltage high warning threshold : 3.5000 V
Module voltage low warning threshold : 3.0990 V
Laser bias current high alarm threshold : 15.000 mA
Laser bias current low alarm threshold : 0.000 mA
Laser bias current high warning threshold : 12.000 mA
Laser bias current low warning threshold : 2.000 mA
Laser output power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser output power low alarm threshold : 0.0871 mW / -10.60 dBm
Laser output power high warning threshold : 1.7378 mW / 2.40 dBm
Laser output power low warning threshold : 0.1738 mW / -7.60 dBm
Laser rx power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser rx power low alarm threshold : 0.0158 mW / -18.01 dBm
Laser rx power high warning threshold : 1.5849 mW / 2.00 dBm
Laser rx power low warning threshold : 0.0316 mW / -15.00 dBm
Lane 0
Laser bias current : 5.288 mA
Laser output power : 0.925 mW / -0.34 dBm
Laser receiver power : 0.913 mW / -0.40 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 1
Laser bias current : 5.328 mA
Laser output power : 0.932 mW / -0.30 dBm
Laser receiver power : 0.814 mW / -0.89 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 2
Laser bias current : 5.460 mA
Laser output power : 0.955 mW / -0.20 dBm
Laser receiver power : 0.972 mW / -0.12 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 3
Laser bias current : 5.394 mA
Laser output power : 0.944 mW / -0.25 dBm
Laser receiver power : 0.954 mW / -0.21 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Physical interface: xe-1/0/53:2
Module temperature : 36 degrees C / 97 degrees F
Module voltage : 3.2400 V
Module temperature high alarm : Off
Module temperature low alarm : Off
Module temperature high warning : Off
Module temperature low warning : Off
Module voltage high alarm : Off
Module voltage low alarm : Off
Module voltage high warning : Off
Module voltage low warning : Off
Module temperature high alarm threshold : 85 degrees C / 185 degrees F
Module temperature low alarm threshold : -10 degrees C / 14 degrees F
Module temperature high warning threshold : 70 degrees C / 158 degrees F
Module temperature low warning threshold : 0 degrees C / 32 degrees F
Module voltage high alarm threshold : 3.5990 V
Module voltage low alarm threshold : 2.9000 V
Module voltage high warning threshold : 3.5000 V
Module voltage low warning threshold : 3.0990 V
Laser bias current high alarm threshold : 15.000 mA
Laser bias current low alarm threshold : 0.000 mA
Laser bias current high warning threshold : 12.000 mA
Laser bias current low warning threshold : 2.000 mA
Laser output power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser output power low alarm threshold : 0.0871 mW / -10.60 dBm
Laser output power high warning threshold : 1.7378 mW / 2.40 dBm
Laser output power low warning threshold : 0.1738 mW / -7.60 dBm
Laser rx power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser rx power low alarm threshold : 0.0158 mW / -18.01 dBm
Laser rx power high warning threshold : 1.5849 mW / 2.00 dBm
Laser rx power low warning threshold : 0.0316 mW / -15.00 dBm
Lane 0
Laser bias current : 5.288 mA
Laser output power : 0.925 mW / -0.34 dBm
Laser receiver power : 0.913 mW / -0.40 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 1
Laser bias current : 5.328 mA
Laser output power : 0.932 mW / -0.30 dBm
Laser receiver power : 0.814 mW / -0.89 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 2
Laser bias current : 5.460 mA
Laser output power : 0.955 mW / -0.20 dBm
Laser receiver power : 0.972 mW / -0.12 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 3
Laser bias current : 5.394 mA
Laser output power : 0.944 mW / -0.25 dBm
Laser receiver power : 0.954 mW / -0.21 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Physical interface: xe-1/0/53:3
Module temperature : 36 degrees C / 97 degrees F
Module voltage : 3.2400 V
Module temperature high alarm : Off
Module temperature low alarm : Off
Module temperature high warning : Off
Module temperature low warning : Off
Module voltage high alarm : Off
Module voltage low alarm : Off
Module voltage high warning : Off
Module voltage low warning : Off
Module temperature high alarm threshold : 85 degrees C / 185 degrees F
Module temperature low alarm threshold : -10 degrees C / 14 degrees F
Module temperature high warning threshold : 70 degrees C / 158 degrees F
Module temperature low warning threshold : 0 degrees C / 32 degrees F
Module voltage high alarm threshold : 3.5990 V
Module voltage low alarm threshold : 2.9000 V
Module voltage high warning threshold : 3.5000 V
Module voltage low warning threshold : 3.0990 V
Laser bias current high alarm threshold : 15.000 mA
Laser bias current low alarm threshold : 0.000 mA
Laser bias current high warning threshold : 12.000 mA
Laser bias current low warning threshold : 2.000 mA
Laser output power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser output power low alarm threshold : 0.0871 mW / -10.60 dBm
Laser output power high warning threshold : 1.7378 mW / 2.40 dBm
Laser output power low warning threshold : 0.1738 mW / -7.60 dBm
Laser rx power high alarm threshold : 2.5119 mW / 4.00 dBm
Laser rx power low alarm threshold : 0.0158 mW / -18.01 dBm
Laser rx power high warning threshold : 1.5849 mW / 2.00 dBm
Laser rx power low warning threshold : 0.0316 mW / -15.00 dBm
Lane 0
Laser bias current : 5.288 mA
Laser output power : 0.925 mW / -0.34 dBm
Laser receiver power : 0.913 mW / -0.40 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 1
Laser bias current : 5.328 mA
Laser output power : 0.932 mW / -0.30 dBm
Laser receiver power : 0.814 mW / -0.89 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 2
Laser bias current : 5.460 mA
Laser output power : 0.955 mW / -0.20 dBm
Laser receiver power : 0.972 mW / -0.12 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Lane 3
Laser bias current : 5.394 mA
Laser output power : 0.944 mW / -0.25 dBm
Laser receiver power : 0.954 mW / -0.21 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser receiver power high alarm : Off
Laser receiver power low alarm : Off
Laser receiver power high warning : Off
Laser receiver power low warning : Off
Tx loss of signal functionality alarm : Off
Rx loss of signal alarm : Off
Just wanted to check if GRE tunnel interfaces are supported on EX4300 series switches.
Also if they are supported - if I have a route in a routing-instance that points to this tunnel, and a FilterBasedForwarding rule that drives this routing instance - can I route incoming packets onto this tunnel interface ??
Will do some more googling - but wanted to try here first.
Hello,
I have firewall filter rule for all of my ports inside my ex4200 for prevent ip spoofing and this is my access list :
filter port1 {
term layer2 {
from {
ether-type arp;
}
then accept;
}
term port1 {
from {
source-address {
185.x.x.x/28;
}
}
then accept;
}
}
when i want to add ipv6 prefix to this rule i see following error
set filter port1 term port1 from source-address 2ayy:xxxx:x::100/120
^
invalid ip address or hostname: 2ayy:xxxx:x::100/120 at '2ayy:xxxx:x::100/120'
any idea how can i add ipv6 prefix to my firewall filter rule to prevent ipv6 spoofing?
Thank you.
Hello,
I have EX4200 switchs and they are access switch so i want to apply shaping on my users inbound traffic,
i have tried following commands
interfaces {
ge-0/0/15 {
scheduler-map sched-map-be-60m;
}
ge-0/0/23 {
scheduler-map sched-map-be-60m;
shaping-rate 60m;
}
}
scheduler-maps {
sched-map-be-60m {
forwarding-class best-effort scheduler sched-queue-shap-60m;
}
}
schedulers {
sched-queue-shap-60m {
shaping-rate 60m;
}
}
but they are not working, any idea how solve it?
thanks
Hi,
New to Juniper and setting up a bunch of EX4300`s.
We are running on
Junos :14.1X53-D49.1
JWeb: 19.4A1.
When looking for newer version to install I notice the recommended is
Junos: Junos 18.1R3-S8/18.4R2-S2
and JWeb:19.4A1
However, when I go into my support/software portal there is a latest 14.1 version published December 2019.
Furthermore, when I sign into JWEB on my switch, its telling me
Latest JUNOS Web Management Application package [14.1X53-A3] is available for download.
Can someone please clear this up for me. What is the difference between 14.X and 19.X when both seem current?
It seems I have 14.X of Junos installed but 19.X of JWeb installed. Should both be 14.x or 19.x?
Hi all,
Currently i'm try simulate prevent ARP poisoning / spoofing based on below url by add command dhcp-security stanza. When i add the dhcp-security arp-inspection then the windows PC cannot get the ip address from DHCP server. When i delete the config then the Win7 can get the dhcp. Is it normal behaviour or need to add another config to make sure the Windows PC can get the ip address even the dhcp-security stanza configure in bridge-domain. Appreciate any feedback
New to Junos here, so please be kind! 
I have an EX4600 that I'm configuring to link some downstream routers to (mikrotik). My requirement is that all incoming traffic from the downstream routers pass from the switch, to an external QoS Server (layer 2) and back into the switch. I've separated out the incoming traffic on vlan 120 to keep the traffic segragated.
If I add an l3-interface to vlan120, I can then ping 10.0.0.11, but also lets the traffic directly access 10.0.0.11 without going through the QoS server. I suspect it's an ARP port-learning issue or something. My knowledge of layer 2 switching is being taxed. :/
Here is my setup:
version 18.1R3.3;
groups {
global;
}
interfaces {
xe-0/0/8 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members queue120;
}
}
}
}
xe-0/0/9 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members queue120;
}
}
}
}
xe-0/0/12 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members queue110;
}
}
}
}
xe-0/0/13 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members queue120;
}
}
}
}
irb {
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex4600;
}
}
}
unit 110 {
family inet {
address 10.0.0.11/24;
}
}
}
lo0 {
unit 0 {
family inet;
}
}
}
forwarding-options {
storm-control-profiles default {
all;
}
}
routing-options {
router-id 10.0.0.11;
}
protocols {
rstp {
interface xe-0/0/12 {
disable;
}
interface xe-0/0/13 {
disable;
}
interface all;
}
}
vlans {
default {
vlan-id 1;
l3-interface irb.0;
}
queue110 {
description "EX -> Q -> Towers";
vlan-id 110;
l3-interface irb.110;
}
queue120 {
description "Towers -> Q -> EX";
vlan-id 120;
}
}I disabled RSTP on interfaces 12 and 13 as though those are technically a loop, I figured having them access ports for different vlans would supress any storms, etc.
Any ideas as to why I can't access layer 3 traffic through the loop? Could it be that R1 / R2 learn of the mac of 10.0.0.11 which isn't on the interface they're connected through?
EDIT: for simplicity, I've tried putting in a simple switch in place of the QoS server, and even a literal loop. No change.
My test switch is an EX4300 running 17.3R3-S4.2. I have not put a license on it yet. For all intents and purposes, this is an out-of-the-box switch with the bare minimum configuration.
My team and I are currently migrating from a non-Juniper switch platform to the EX4300s. We use a layer 3 access design with dual L3 uplinks. Overall process for migration is to put in a layer 2 interregion between the two switches to share the production VLANs, establish an OSPF adjacency for a layer 3 interregion, then migrate one of the layer 3 uplinks to the EX4300. For the production VLANs, we would use an FHRP between them, but we don't have a compatible protocol (old switch does not support VRRP). So migration has been by disabling the VLAN interface on the old switch, then turning up the irb interface on the EX4300. This causes a brief outage during the commit, but it's outside business hours. At this point, all devices are still connected to their VLANs on the old switch.
Many devices come back automatically, albeit with a short delay. However, the VoIP telephones take upwards of 20 minutes -- which looks suspiciously like an ARP issue, not getting the new gateway MAC address.
On my test switch, when I bring up the irb interface, I get a GARP request, which is for duplicate address detection. However, I cannot get Junos to send a GARP reply. The old switch sends a GARP reply to cause connected devices to update their ARP tables and it works beautifully.
I've learned the gratuitous-arp-reply option is for the EX to update its own ARP table when it hears a GARP reply.
I've learned the no-gratuitous-arp-request option is so the EX does not reply to GARP requests it hears.
But I can't find anything to make the EX send a GARP reply, like the old switch does, to update the ARP tables on the telephones.
Any thoughts on this? Is there a configuration option I'm missing or is it a Junos design thing and I'm Sorta Outta Luck? Should the telephones be taken the GARP request and handling it the same as a GARP reply (updating their ARP tables)? Also, is the fact that I don't have a license on this test switch a factor? The production EX switches are properly licensed. I've done a capture off of my test switch, but not off the production EX.
Hi,
I unpacked today a brandnew EX3300-24P but it did not start. I connect a serial cable and got this output.
U-Boot 1.1.6 (Jun 4 2012 - 01:56:18)
Board: EX3300-24P 5.15
EPLD: Version 04.130327 (0x10)
DRAM: Initializing (1GB)
Flash: 8 MB
Firmware Version: --- 01.00.00 ---
USB: scanning bus for devices...
Root Hub 0: 2 USB Device(s) found
Root Hub 1: 1 USB Device(s) found
scanning bus for storage devices... data abort
pc : [<00237a4c>] lr : [<00211810>]
sp : 801fdbb4 ip : 0029a802 fp : 00000001
r10: 00000000 r9 : 0029a800 r8 : 001fffb4
r7 : 0028c550 r6 : 0029a740 r5 : 00001a52 r4 : 0029a740
r3 : 200000d3 r2 : 200000d3 r1 : 0029a77f r0 : 0029a740
Flags: nzCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
Switch boots around 3 times and stops. Any idea how to fix ? Thank you for your help.
Regards, Daniel
Hello,
I'm working with a few EX3400-48P that are exhibiting some odd behavior around PoE. Every few hours, one of the poe devices (there doesn't look to be any pattern to which device, it seems evenly distributed) will reboot indicating a momentary loss of PoE. At the same time, the following message appears in the syslog:
fpc0 PoE: Failed to read voltage measurements
My searching hasn't found what that message means so I'm at a bit of a loss to where to look for a resolution. This is happening on multiple switches in the facility. I have already updated the PoE controller. Every port/switch is well below the PoE budget.
root@switch1> show chassis firmware detail
FPC 0
PoE firmware 2.1.1.19.3
Boot Firmware
U-Boot U-Boot 2016.01-rc1 (Sep 01 2016 - 16:00:13 -0700) 1.3.0
Boot Firmware
loader FreeBSD/armv6 U-Boot loader 1.2
FPC 1
Boot Firmware
U-Boot U-Boot 2016.01-rc1 (Sep 01 2016 - 16:00:13 -0700) 1.3.0
Boot Firmware
loader FreeBSD/armv6 U-Boot loader 1.2root@switch1> show version fpc0: -------------------------------------------------------------------------- Hostname: switch1 Model: ex3400-48p Junos: 18.2R3.4 JUNOS OS Kernel 32-bit [20190605.30b921f_builder_stable_11] JUNOS OS libs [20190605.30b921f_builder_stable_11] JUNOS OS runtime [20190605.30b921f_builder_stable_11] JUNOS OS time zone information [20190605.30b921f_builder_stable_11] JUNOS py extensions [20190620.215446_builder_junos_182_r3] JUNOS py base [20190620.215446_builder_junos_182_r3] JUNOS OS crypto [20190605.30b921f_builder_stable_11] JUNOS network stack and utilities [20190620.215446_builder_junos_182_r3] JUNOS libs [20190620.215446_builder_junos_182_r3] JUNOS runtime [20190620.215446_builder_junos_182_r3] JUNOS Web Management Platform Package [20190620.215446_builder_junos_182_r3] JUNOS ex libs [20190620.215446_builder_junos_182_r3] JUNOS ex runtime [20190620.215446_builder_junos_182_r3] JUNOS ex platform support [20190620.215446_builder_junos_182_r3] JUNOS dcp network modules [20190620.215446_builder_junos_182_r3] JUNOS modules [20190620.215446_builder_junos_182_r3] JUNOS ex modules [20190620.215446_builder_junos_182_r3] JUNOS ex Data Plane Crypto Support [20190620.215446_builder_junos_182_r3] JUNOS daemons [20190620.215446_builder_junos_182_r3] JUNOS SDN Software Suite [20190620.215446_builder_junos_182_r3] JUNOS Extension Toolkit [20190620.215446_builder_junos_182_r3] JUNOS Phone-home [20190620.215446_builder_junos_182_r3] JUNOS Packet Forwarding Engine Support (EX34XX) [20190620.215446_builder_junos_182_r3] JUNOS jdocs ex [20190620.215446_builder_junos_182_r3] JUNOS jail runtime [20190605.30b921f_builder_stable_11] JUNOS FIPS mode utilities [20190620.215446_builder_junos_182_r3] fpc1: -------------------------------------------------------------------------- Hostname: switch1 Model: ex3400-48t Junos: 18.2R3.4 JUNOS OS Kernel 32-bit [20190605.30b921f_builder_stable_11] JUNOS OS libs [20190605.30b921f_builder_stable_11] JUNOS OS runtime [20190605.30b921f_builder_stable_11] JUNOS OS time zone information [20190605.30b921f_builder_stable_11] JUNOS py extensions [20190620.215446_builder_junos_182_r3] JUNOS py base [20190620.215446_builder_junos_182_r3] JUNOS OS crypto [20190605.30b921f_builder_stable_11] JUNOS network stack and utilities [20190620.215446_builder_junos_182_r3] JUNOS libs [20190620.215446_builder_junos_182_r3] JUNOS runtime [20190620.215446_builder_junos_182_r3] JUNOS Web Management Platform Package [20190620.215446_builder_junos_182_r3] JUNOS ex libs [20190620.215446_builder_junos_182_r3] JUNOS ex runtime [20190620.215446_builder_junos_182_r3] JUNOS ex platform support [20190620.215446_builder_junos_182_r3] JUNOS dcp network modules [20190620.215446_builder_junos_182_r3] JUNOS modules [20190620.215446_builder_junos_182_r3] JUNOS ex modules [20190620.215446_builder_junos_182_r3] JUNOS ex Data Plane Crypto Support [20190620.215446_builder_junos_182_r3] JUNOS daemons [20190620.215446_builder_junos_182_r3] JUNOS SDN Software Suite [20190620.215446_builder_junos_182_r3] JUNOS Extension Toolkit [20190620.215446_builder_junos_182_r3] JUNOS Phone-home [20190620.215446_builder_junos_182_r3] JUNOS Packet Forwarding Engine Support (EX34XX) [20190620.215446_builder_junos_182_r3] JUNOS jdocs ex [20190620.215446_builder_junos_182_r3] JUNOS jail runtime [20190605.30b921f_builder_stable_11] JUNOS FIPS mode utilities [20190620.215446_builder_junos_182_r3]
root@switch1> show poe controller Controller Maximum Power Guard Management Status Lldp index power consumption band Priority 0 740W 67.00W 0W Class AT_MODE Disabled
Any insight into this would be greatly appreciated.
Hi everyone,
Happy New Decade.
I'm attempting bandwidth management on an EX3400 and was wondering if the below scenario is the best way of achieving it. Or if there is a better way. Welcome any comment.
Thank you.
Scenario: a single EX3400 (VC) uplinks to two Cisco Viptela (active, passive). The uplinks are trunks with two separate VLANs, each in a separate virtual-router Blue and Red. IRB.100 = Blue, IRB.200 = Red. No control of Viptela.
Goal: hard split bandwidth 10Mbps on Blue and 20Mbps on Red up the trunk.
Further improvement: Allow either VLANs to make use of the full 30Mbps when the link is not busy.
ex3400vc> show configuration interface
ge-0/0/1 {
unit 0 {
bandwidth 30m;
family ethernet-switching {
interface-mode trunk;
vlan {
members [ vlan-blue vlan-red ];
}
}
}
}
ge-1/0/1 {
unit 0 {
bandwidth 30m;
family ethernet-switching {
interface-mode trunk;
vlan {
members [ vlan-blue vlan-red ];
}
}
}
}
irb {
unit 100 {
bandwidth 10m;
family inet {
filter {
input filter-blue;
output filter-blue;
}
address 192.168.100.1/24;
}
}
unit 200 {
bandwidth 20m;
family inet {
filter {
input filter-red;
output filter-red;
}
address 192.168.200.1/24;
}
}
}
ex3400vc> show configuration firewall
family inet {
filter filter-blue {
term allow {
then {
policer policer-10m;
accept;
}
}
}
filter filter-red {
term allow {
then {
policer policer-20m;
accept;
}
}
}
}
policer policer-10m {
filter-specific;
if-exceeding {
bandwidth-limit 10m;
}
then discard;
}
policer policer-20m {
filter-specific;
if-exceeding {
bandwidth-limit 20m;
}
then discard;
}
ex3400vc> show configuration routing-instances
vr-blue {
instance-type virtual-router;
interface irb.100;
routing-options {
static {
route 0.0.0.0/0 next-hop x.x.x.x;
}
instance-import red-routes;
}
}
vr-red {
instance-type virtual-router;
interface irb.200;
routing-options {
static {
route 0.0.0.0/0 next-hop y.y.y.y;
}
instance-import blue-routes;
}
}