Switching

Greetings!  I have a couple of EX3400T running Junos 19.1R1.6 in a virtual chassis.  An extended freatures license is installed on both.  I have a 10Gb sfp+ installed connected to a MX480 router.  The link between the two is up, passing traffic and is running clean with no errors.  Problem is the link lights on the EX3400 do not light up.  Link light on MX480 is up.  Tried this with serveral different optics and even tried it with a 1Gb sfp.  Same results:  Link comes up, runs perfectly but no link light.

PIC 2 REV 20 650-059888 NV0218210047 4x10G SFP/SFP+

      Xcvr 0 REV 01 740-030128 G1811063863 SFP+-10G-ER

Did something change in 19.1R1.6 so that link lights do not show by default?

I have an ongoing JTAC case running on the exact same thing, just on EX2300 running 18.1R3-S3 (and -S4). Tried three different switches, both EX2300-24T and EX2300-24P. Same switches had working LEDs while running 15.1X53-D58 and -D59.

JTAC has confirmed that they can reproduce the behaviour in their lab and I'm now awaiting if there is a workaround or which release it will be fixed.

I would suspect that the same bug has hit your EX3400 running 19.1. Think you should create a JTAC case and refer to case number #2019-0423-0222. I have not received any PR number.

and just to confirm. From the CLI the LED should be active... but nothing when looking at the switch 🙂

root@ex2300-24p> show chassis led | match xe
xe-0/1/0 Green

Due to other reasons I have also upgraded an EX3400-24T to 19.1R1.6 and can confirm that SFP+ LEDs does not work in this release.

I have added this info to the ongoing JTAC case and awaits if they will accept to combine the same issue on the two platforms in the same case.

If others have this issue it's currently tracked at JTAC under PR1428703.

We have the same issue on our three EX3400-24T since upgrading from 15.1X53 to 18.1R3-S4 (and now -S5). On the one hardware I looked at, it only affects our DAC cables, the SFP+-10G-LRM used for Virtual Chassis are lighted correctly.

When I try to open the mentioned PR1428703, I get

It appears you are searching for a PR which is not available. It could be that the PR number is not valid, or that it refers to a PR which has no externally available content.

Is that expected at this stage?

Thanks,

Jonas

I don't think the PR is public in it's current state. That's why you receive this error.

I mentioned the PR for others to refer to instead of JTAC starting all over with new cases.

Anyway; I know that 18.1R3-S4 is the JTAC recommended but 18.2 or 18.3 should be working just as well and have working LED's - if you don't want to wait for a fixed JTAC recommended version.

I'm really quite amazed that this is still an issue on 18.1R3-S7 and 18.1R3-S6 is still the jtac recommended version.

I just did a large deployment and as I always do, when to the jtac recommended version as it is supposed to be the best choice.  Found this issue then tried S7 and still not fixed.

I experienced the issue on ex2300-c-12t and ex2300-24t.

Anyone running the v19 releases on ex2300's any issues?

Anyone aware if juniper is going to update the jtac recommendation or fix this issue in the recommended release line?

Couple of things.  For the EX3400 LED situation, I believe this was covered under PR1329903.  This should be fixed in 18.1R2 and above.  This is the situation where when a cable is removed LED stays on.

I would suggest at this time, the best option for EX3400 and/or EX2300 is to go to 18.2R3-S1.  You will likely need to follow KB 31201 - https://kb.juniper.net/InfoCenter/index?page=content&id=KB31201&actp=METADATA

Now once you are on this code, you should be able to upgrade, without needing the extra steps - SW will take care of clean and file space automatically via PR1417441 change.

As for other PR mentioned in this thread, PR1428703, that is fixed (right now) only in 19.1R2 and 19.2R2, and I believe PR1417441 is also resolved there, BUT neither of these is out yet.

I do not have any personal experience with 19.x on these platforms.

Just FYI JTAC recommended is generic recommendation for majority of customers, and does not target any specific PR or feature functionality.

I will look to see if PR1428703 can be expedited to be in 18.2R3-S2, which will likely become next JTAC recommended.

I have observed a similar behavior on 18.1R3-S4 and S6, on both EX-2300C and EX3400 switches.  In addition, I upgraded a VC of EX3400's from 18.1R3.3 to 18.1R3-S6 and saw that while none of the SFP ports were populated, the link lights would blink randomly across many of them.  I also had populated QSFP ports that would not light at all.  Downgrading to 15.1X53-D590 solved all of these issues for me.

Puzzling that a visible fault can persist through so many iterations of software.

I can confirm that the SFP LEDs do not light up on an EX-2300C under 19.2R1 or 19.2R1-S1.

Using show chassis led is a workaround 😀

root@ala01-spi-main> show chassis led |match ge-0/1 
ge-0/1/0        Green Blinking       
ge-0/1/1        Green Blinking       

---

@dwojoAVI wrote:

 

I experienced the issue on ex2300-c-12t and ex2300-24t.

 

Anyone running the v19 releases on ex2300's any issues?

---

 Bonjour, 

   I experienced the issue on my EX2300-C. I opened and closed a Service Request in may. 19.1 is affected by the issue: I connected 2 switches opticals, one running 18.3 and the other running 19.1R6. Traffic flows. Link and ST leds up on the 18.3, off on the 19.1 .

 Since switches were not deployed, we decided to rollback to 15.1X53 to fix a problem of communication lost that affected us on versions 18 and 19. 15 seems not affected, so we are sticking to the latest release of May 2019. you may want to check EX2300-48T Stop working after random time after upgrade to 19.1R1.6  discussion

as an aside, the DX indicator does not seems to work: selecting DX, and setting a port to Half duplex does not change the led display as per the manual. Another service request opened and closed on the subject. 

Michel

We just deployed a number of EX2300-C's  and upgraded to 19.2R1.8 and are seeing this consistently across all of them, so presumably this issue isn't fixed in this release either.

Please check this link --> https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1428703

I just read that someone tested this situation with 18.2R3-S1, and the LED situation is resolved with this code.  I'd hope some other might try this and report back.  Getting to 18.2R3-S1 is also a good place as future upgrades from this code should function much better.

Hope to hear other good news, . . .