I have a juniper ex4300 configured with a bunch of vlans on an AE interface. connected to this I have a cisco 3750 switch.

the link AE to PC is setup with LACP. On the production cisco the link never comes up. neither the pc nor the gigE interface.

The juniper shows athe AE as down but the ge-0/2/0 interface as up. I've checked the config several times and both sides match

native vlan, the vlans themselfs. the are both set to active active. nothing I can think of gets the link to come up......

here's the funny thing. I took a spare cisco 3750 switch with the same version ios and the config from the production cisco and put it on the spare 3750, AND IT WORKS JUST AS IT SHOULD with the Juniper. 

anyone have any ideas why the production switch doesn't come up?, yes I changed the optics, had the fiber tested, even moved to a different sfp slot on the production cisco 3750. still won't come up.....

any help appreciated

There are several links for that, you can find them here:

https://www.juniper.net/documentation/en_US/release-independent/junos/topics/topic-map/ex2300-virtual-chassis.html

https://www.juniper.net/documentation/en_US/junos/topics/concept/virtual-chassis-ex4200-overview.html#jd0e30

https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/virtual-chassis-ex4300-member-adding-cli.html

https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/virtual-chassis-ex4300-configuring.html

As EX2300 supports SFP/SFP+ transceiver, you need LC/PC cables.

Hey Big,

I hope you are doing great, seems to be an issue with LACP, are you seeing the LACP PDU's going back and forth? are they collecting and distributing? at least one of them is in active mode? 

>show lacp statistic interface aex

>show lacp interface aex

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/

Regards,

Lil Dexx
JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

no you don't see lacp rx packets when the juniper is connected to the production cisco. the lacp tx counter increments as it should.

when connected to the spare cisco 3750, which works, both counters increment

I have the Deco x60s connected through an ex4200. I discovered that if you enable igmp snooping it filters out the IEEE 1905 packets. So check to see if you have that in your config and disable it. Afterwards you have to reboot the APs as it doesn't seem to switchover to Ethernet Backhaul automatically. Hope this helps.

Joe

Hey Big,

Assuming that this information is from the CISCO perspective what the Juniper device is showing as rx and tx?

Can you share the LACP configuration from both sides ( Cisco and Juniper)

Have you tried doing some packet captures?

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/

Regards,

Lil Dexx
JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

keep in mode the literally exact cisco config works in a different 3750

!--------------------------- cisco side ----------------------------------------
!
spanning-tree mode rapid-pvst
spanning-tree loopguard default
spanning-tree extend system-id
!
!
!vlan internal allocation policy ascending
!
vlan 171
name guest
!
vlan 269
name vendl4
!
vlan 270
name 130.199.218.0/24
!
vlan 271
name 130.199.219.0/24
!
vlan 272
name 130.199.220.0/24
!
vlan 273
name 130.199.221.0/24
!
vlan 274
name 130.199.222.0/24
!
vlan 275
name 130.199.223.0/24
!
vlan 399
name 10.251.118.0/24
!
vlan 441
name 10.251.124.0/29
!
vlan 442
name 10.251.124.16/28
!
vlan 641
name 10.251.120.0/24
!
vlan 642
name 10.251.121.0/24
!
vlan 643
name 10.251.122.0/24
!
vlan 644
name 10.251.123.0/24
!
vlan 2404
name 10.251.252.0/24
!
vlan 2406
name 10.251.250.0/24
!
vlan 2408
name 10.251.248.0/24
!
vlan 2410
name 10.251.246.0/24
!
vlan 2412
name 10.251.244.0/24
!
vlan 2414
name 10.251.242.0/24
!
vlan 2420
name 10.251.236.0/24
!
vlan 3404
name 10.251.4.0/24
!
vlan 3406
name 10.251.6.0/24
!
vlan 3408
name 10.251.8.0/24
!
vlan 3410
name 10.251.10.0/24
!
vlan 3412
name 10.251.12.0/24
!
vlan 3414
name 10.251.14.0/24

!
interface Port-channel42
description
switchport trunk encapsulation dot1q
switchport trunk native vlan 641
switchport trunk allowed vlan 171,270-275,399,441,442,641-644,2404,2406,2408
switchport trunk allowed vlan add 2410,2412,2414,2420,3404,3406,3408,3410,3412
switchport trunk allowed vlan add 3414
switchport mode trunk
switchport nonegotiate
spanning-tree link-type point-to-point
!
interface GigabitEthernet1/0/2
description
switchport trunk encapsulation dot1q
switchport trunk native vlan 641
switchport trunk allowed vlan 171,270-275,399,441,442,641-644,2404,2406,2408
switchport trunk allowed vlan add 2410,2412,2414,2420,3404,3406,3408,3410,3412
switchport trunk allowed vlan add 3414
switchport mode trunk
switchport nonegotiate
udld port disable
no cdp enable
spanning-tree link-type point-to-point
channel-group 42 mode active
!

------------------------------- juniper side ------------------------------------------

set interfaces ge-0/2/0 description
set interfaces ge-0/2/0 ether-options 802.3ad ae0
set interfaces ae0 description
set interfaces ae0 native-vlan-id 641
set interfaces ae0 aggregated-ether-options minimum-links 1
set interfaces ae0 aggregated-ether-options lacp active
set interfaces ae0 unit 0 family ethernet-switching interface-mode trunk
set interfaces ae0 unit 0 family ethernet-switching vlan members 171
set interfaces ae0 unit 0 family ethernet-switching vlan members 270-275
set interfaces ae0 unit 0 family ethernet-switching vlan members 399
set interfaces ae0 unit 0 family ethernet-switching vlan members 441-442
set interfaces ae0 unit 0 family ethernet-switching vlan members 641-644
set interfaces ae0 unit 0 family ethernet-switching vlan members 2404
set interfaces ae0 unit 0 family ethernet-switching vlan members 2406
set interfaces ae0 unit 0 family ethernet-switching vlan members 2408
set interfaces ae0 unit 0 family ethernet-switching vlan members 2410
set interfaces ae0 unit 0 family ethernet-switching vlan members 2412
set interfaces ae0 unit 0 family ethernet-switching vlan members 2414
set interfaces ae0 unit 0 family ethernet-switching vlan members 2420
set interfaces ae0 unit 0 family ethernet-switching vlan members 3404
set interfaces ae0 unit 0 family ethernet-switching vlan members 3406
set interfaces ae0 unit 0 family ethernet-switching vlan members 3408
set interfaces ae0 unit 0 family ethernet-switching vlan members 3410
set interfaces ae0 unit 0 family ethernet-switching vlan members 3412
set interfaces ae0 unit 0 family ethernet-switching vlan members 3414
set interfaces ae0 unit 0 family ethernet-switching recovery-timeout 60

set protocols vstp interface ae0 mode point-to-point

et protocols vstp vlan 1
set protocols vstp vlan 171
set protocols vstp vlan 2404
set protocols vstp vlan 2406
set protocols vstp vlan 2408
set protocols vstp vlan 2410
set protocols vstp vlan 2412
set protocols vstp vlan 2414
set protocols vstp vlan 2420
set protocols vstp vlan 270
set protocols vstp vlan 271
set protocols vstp vlan 272
set protocols vstp vlan 273
set protocols vstp vlan 274
set protocols vstp vlan 275
set protocols vstp vlan 3404
set protocols vstp vlan 3406
set protocols vstp vlan 3408
set protocols vstp vlan 3410
set protocols vstp vlan 3412
set protocols vstp vlan 3414
set protocols vstp vlan 399
set protocols vstp vlan 441
set protocols vstp vlan 442
set protocols vstp vlan 641
set protocols vstp vlan 642
set protocols vstp vlan 643
set protocols vstp vlan 644

Hello All,

I've run into an issue trying to commit configuration changes to a VC of EX3400 switches.  There's nothing exotic here.  I've tried rebooting, changing code versions, restarting the mgd process... all to no avail.  Hopefully, someone here can shed some light.

Here's the output:

branto@faes-mdf-edge-swi-01# show | compare
[edit interfaces interface-range faes-standard-access-ports]
- member ge-0/0/46;
[edit interfaces]
+ ge-0/0/46 {
+ unit 0 {
+ family ethernet-switching {
+ interface-mode trunk;
+ vlan {
+ members all;
+ }
+ }
+ }
+ }
[edit protocols]
+ layer2-control {
+ bpdu-block {
+ interface ge-0/0/46 {
+ disable;
+ }
+ }
+ }
[edit protocols rstp]
+ interface ge-0/0/46;

{master:0}[edit]
branto@faes-mdf-edge-swi-01#

{master:0}[edit]
branto@faes-mdf-edge-swi-01#

{master:0}[edit]
branto@faes-mdf-edge-swi-01# commit

{master:0}[edit]
branto@faes-mdf-edge-swi-01# commit check

{master:0}[edit]
branto@faes-mdf-edge-swi-01# run show comm
^
syntax error, expecting <command>.
branto@faes-mdf-edge-swi-01# run show system commit ?
Possible completions:
<[Enter]> Execute this command
revision Show latest commit revision number for shared database
server Show commit server detail
synchronize-server Show commit synchronize server information
| Pipe through a command
{master:0}[edit]
branto@faes-mdf-edge-swi-01# run show system commit revision
Revision: fpc0-1600011733-25

{master:0}[edit]
branto@faes-mdf-edge-swi-01# run show system commit
0 2020-09-13 15:42:27 UTC by root via other
1 2020-09-13 15:38:44 UTC by root via other
2 2020-09-11 12:10:07 UTC by root via other
3 2020-09-11 11:57:15 UTC by branto via cli
4 2020-09-11 11:56:56 UTC by branto via cli
5 2020-09-11 03:34:21 UTC by branto via cli
6 2020-09-11 03:29:02 UTC by root via other
7 2020-09-11 03:28:55 UTC by root via other
Synchronization with remote Routing Engine
8 2020-09-11 03:27:58 UTC by root via button
9 2020-09-11 03:21:40 UTC by root via other

{master:0}[edit]
branto@faes-mdf-edge-swi-01#

Hi,

I dont see any error in the snippet while committing the configuration.

Is it that the commit is successful but you do not see corresponding change in the configuration ?

Hello,

i have 2x qfx 3500 in VC mode, one of them members fan trays are showing as failed, 

i have swaped it with a healthy fan trays but still its remain as failed,

can any one help me?

thanks,

Hey blackmetal, 

Could you please share the alarm ? Also the related log messages? 

show chassis alarms

show log messages | match fan

Since you replaced this with a working one - I think it should be issue with Fan Tray slot.

Howver, I would suggest you to try reseating this FAN TRAY, if this doesn't fix, I think it should be a slot issue and replacement is the only option.

Cooling System and Airflow for a QFX3500 Device

https://www.juniper.net/documentation/en_US/release-independent/junos/topics/reference/specifications/cooling-system-qfx3500.html

Installing a Fan Tray in a QFX3500 Device

https://www.juniper.net/documentation/en_US/release-independent/junos/topics/task/installation/fan-tray-qfx3500-installing.html

Hope this helps.

Please mark "Accept as solution" if this answers your query.  Kudos are appreciated too! 

Regards, 

Sharat Ainapur

Hello branto, 

Greetings,

Could you please share the output of show | compare in [edit] mode to understand the config change being made? 

Also, commit check doesn't list whether check was successful or not, so do share the commit check output as well.

Regards,

Sharat

noc@IDc-CoreSWT> show chassis alarms
1 alarms currently active
Alarm time Class Description
2020-09-14 10:00:00 UTC Major FPC 1 Fan 0 not spinning

{master:0}
noc@IDc-CoreSWT> show log messages | match fan
Sep 14 05:34:30 IDc-CoreSWT alarmd[1736]: Alarm set: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 not spinning
Sep 14 05:34:30 IDc-CoreSWT craftd[1737]: Receive FX craftd set alarm message: color: 1 class: 100 object: 76 slot: 3 silent: 0 short_reason=FPC 1 Fan 0 Fail long_reason=FPC 1 Fan 0 not spinning id=1275265030 reason=6
Sep 14 05:34:30 IDc-CoreSWT craftd[1737]: Major alarm set, FPC 1 Fan 0 not spinning
Sep 14 06:48:39 IDc-CoreSWT alarmd[1736]: Alarm set: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 Fan/Blower Absent
Sep 14 06:48:39 IDc-CoreSWT alarmd[1736]: Alarm cleared: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 not spinning
Sep 14 06:48:39 IDc-CoreSWT craftd[1737]: Receive FX craftd set alarm message: color: 1 class: 100 object: 76 slot: 3 silent: 0 short_reason=FPC 1 Fan 0 Fan/Blo long_reason=FPC 1 Fan 0 Fan/Blower Absent id=1275265026 reason=2
Sep 14 06:48:39 IDc-CoreSWT craftd[1737]: Major alarm set, FPC 1 Fan 0 Fan/Blower Absent
Sep 14 06:48:39 IDc-CoreSWT craftd[1737]: Major alarm cleared, FPC 1 Fan 0 not spinning
Sep 14 06:48:44 IDc-CoreSWT alarmd[1736]: Alarm cleared: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 Fan/Blower Absent
Sep 14 06:48:44 IDc-CoreSWT chassisd[1553]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Ok (jnxFruContentsIndex 4, jnxFruL1Index 2, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName Fan Tray 0 @ 1/0/*, jnxFruType 13, jnxFruSlot 1)
Sep 14 06:48:44 IDc-CoreSWT craftd[1737]: Major alarm cleared, FPC 1 Fan 0 Fan/Blower Absent
Sep 14 06:48:44 IDc-CoreSWT alarmd[1736]: Alarm set: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 not spinning
Sep 14 06:48:44 IDc-CoreSWT craftd[1737]: Receive FX craftd set alarm message: color: 1 class: 100 object: 76 slot: 3 silent: 0 short_reason=FPC 1 Fan 0 Fail long_reason=FPC 1 Fan 0 not spinning id=1275265030 reason=6
Sep 14 06:48:44 IDc-CoreSWT craftd[1737]: Major alarm set, FPC 1 Fan 0 not spinning
Sep 14 09:59:55 IDc-CoreSWT alarmd[1736]: Alarm set: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 Fan/Blower Absent
Sep 14 09:59:55 IDc-CoreSWT craftd[1737]: Receive FX craftd set alarm message: color: 1 class: 100 object: 76 slot: 3 silent: 0 short_reason=FPC 1 Fan 0 Fan/Blo long_reason=FPC 1 Fan 0 Fan/Blower Absent id=1275265026 reason=2
Sep 14 09:59:55 IDc-CoreSWT craftd[1737]: Major alarm set, FPC 1 Fan 0 Fan/Blower Absent
Sep 14 09:59:55 IDc-CoreSWT alarmd[1736]: Alarm cleared: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 not spinning
Sep 14 09:59:55 IDc-CoreSWT craftd[1737]: Major alarm cleared, FPC 1 Fan 0 not spinning
Sep 14 10:00:00 IDc-CoreSWT alarmd[1736]: Alarm cleared: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 Fan/Blower Absent
Sep 14 10:00:00 IDc-CoreSWT craftd[1737]: Major alarm cleared, FPC 1 Fan 0 Fan/Blower Absent
Sep 14 10:00:00 IDc-CoreSWT chassisd[1553]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Ok (jnxFruContentsIndex 4, jnxFruL1Index 2, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName Fan Tray 0 @ 1/0/*, jnxFruType 13, jnxFruSlot 1)
Sep 14 10:00:00 IDc-CoreSWT alarmd[1736]: Alarm set: FAN SFXPC color=RED, class=CHASSIS, reason=FPC 1 Fan 0 not spinning
Sep 14 10:00:00 IDc-CoreSWT craftd[1737]: Receive FX craftd set alarm message: color: 1 class: 100 object: 76 slot: 3 silent: 0 short_reason=FPC 1 Fan 0 Fail long_reason=FPC 1 Fan 0 not spinning id=1275265030 reason=6
Sep 14 10:00:00 IDc-CoreSWT craftd[1737]: Major alarm set, FPC 1 Fan 0 not spinning

i think its not realted to fan tray slot because it was working since last week up to today and suddenly this happe

Hey blackmetal,

As per the documentation, it says the Fan is missing. When a fan tray is removed, the CLI message Fan/Blower is Absent is logged in the system log, and the system raises a minor alarm.

Link: QFX3500 Chassis Alarm Messages 

Try changing it with another FAN TRAY of same type in similar slot i.e. Fan Tray 0 or 1 from the other device and check the behaviour. 

Regards,

Sharat Ainapur

I'm not the OP but show|compare is literally the output he provided: 

branto@faes-mdf-edge-swi-01# show | compare

...

The issue appears to be that commit and commit check are returning no output or other feedback.

---

 wrote:

Hello branto, 

 

Greetings,

 

Could you please share the output of show | compare in [edit] mode to understand the config change being made? 

Also, commit check doesn't list whether check was successful or not, so do share the commit check output as well.

 

Regards,

Sharat

---

.

Hello smicker, 

Yes you are right, I did miss out on this clearly. Thank you sir for pointing this out 🙂 

I was just curious because commit check did not clearly indicate anything. 

As you rightly pointed out that is the issue here - configuration commit.

Regards,

Sharat

i just replcaed the faulty devices and everythng working correctly,

here is the poutput

show chassis environment
Class Item Status Measurement
Power FPC 0 Power Supply 0 OK
FPC 0 Power Supply 1 OK
FPC 1 Power Supply 0 OK
FPC 1 Power Supply 1 OK
Temp FPC 0 Sensor TopLeft I OK 15 degrees C / 59 degrees F
FPC 0 Sensor TopRight I OK 14 degrees C / 57 degrees F
FPC 0 Sensor TopLeft E OK 23 degrees C / 73 degrees F
FPC 0 Sensor TopRight E OK 23 degrees C / 73 degrees F
FPC 0 Sensor TopMiddle I OK 22 degrees C / 71 degrees F
FPC 0 Sensor TopMiddle E OK 21 degrees C / 69 degrees F
FPC 0 Sensor Bottom I OK 25 degrees C / 77 degrees F
FPC 0 Sensor Bottom E OK 20 degrees C / 68 degrees F
FPC 0 Sensor Die Temp OK 35 degrees C / 95 degrees F
FPC 0 Sensor Mgmnt Brd I OK 13 degrees C / 55 degrees F
FPC 0 Sensor Switch I OK 21 degrees C / 69 degrees F
FPC 1 Sensor TopLeft I OK 14 degrees C / 57 degrees F
FPC 1 Sensor TopRight I OK 14 degrees C / 57 degrees F
FPC 1 Sensor TopLeft E OK 23 degrees C / 73 degrees F
FPC 1 Sensor TopRight E OK 21 degrees C / 69 degrees F
FPC 1 Sensor TopMiddle I OK 20 degrees C / 68 degrees F
FPC 1 Sensor TopMiddle E OK 20 degrees C / 68 degrees F
FPC 1 Sensor Bottom I OK 26 degrees C / 78 degrees F
FPC 1 Sensor Bottom E OK 19 degrees C / 66 degrees F
FPC 1 Sensor Die Temp OK 32 degrees C / 89 degrees F
FPC 1 Sensor Mgmnt Brd I OK 13 degrees C / 55 degrees F
FPC 1 Sensor Switch I OK 20 degrees C / 68 degrees F
Fans FPC 0 Fan Tray 0 OK Spinning at normal speed
FPC 0 Fan Tray 1 OK Spinning at normal speed
FPC 0 Fan Tray 2 OK Spinning at normal speed
FPC 1 Fan Tray 0 OK Spinning at normal speed
FPC 1 Fan Tray 1 OK Spinning at normal speed
FPC 1 Fan Tray 2 OK Spinning at normal speed

but when i execute 

2 alarms currently active
Alarm time Class Description
2020-09-14 11:32:36 UTC Major FPC 1 Fan 0 Fan/Blower Absent
2020-09-14 11:12:28 UTC Major FPC 1 Fan 1 not spinning

it shows alarms it seems the alarm is not removed,

can you help me how can i clear this alarm?

Hi blackmetal, 

If this is not in production right now, I would suggest you to reboot the member 1 in this VC setup. Use the command:

request system reboot member <member-id>

Hope this helps.

Please mark "Accept as solution" if this answers your query.  Kudos are appreciated too! 

Regards, 

Sharat Ainapur

actually it is in productional mode,

is there nay other way to remove this log ?

Hello. 

Base on the output where the commit check does not shows any information will be good to know the version you are running. 

This could be a bug or not however it is a simple test on lab so probably will need to be replicated using the same data you are using as well as version. 

I would recommend you to open a case so JTAC can test that out or check on Data base if this has seeing before.