Thanks Rene, will try the things you mention. The SFP is 100% official Juniper I have checked the part number and its a finisar made Juniper module, unless there is a newer model?
Original Message:
Sent: 04-15-2026 19:31
From: Rene1
Subject: EX4400-48F port issues
As you can see on the logs the EX4400 uses a newer Broadcom Seahawks chipset, this chipset is known to be picky
about I2C timing and SFP handshake protocols than the older 4200 series, so this could be a I2C Bus bug, this could mean the
switch cannot read the EEPROM, which means it can not verify the optic type, power levels, or capabilities. even if layer 1 is Up, so it fails to initialise at driver level, which means moving to a different port may move it to a different I2C bus or PIC.
Suggestions:
1) try recommended stable firmware version for it, earlier versions may have had issues with seahawks chipset
2) Disable Auto negotiation
set interfaces ge-0/0/14 speed 1g
set interfaces ge-0/0/14 link-mode full-duplex
set interfaces ge-0/0/14 gigether-options no-auto-negotiation
3) check for "Non-Juniper" even if they are juniper, I know crazy right, older models from 4200 may not pass the more strict 4400 validation process
if you see anything not supported try
set chassis fpc 0 pic 0 allow-unsupported-transceiver
If all above fails, looks like an RMA job for you
Original Message:
Sent: 04-15-2026 10:42
From: STEVEN LOWERY
Subject: EX4400-48F port issues
Hi,
Currently replacing an estate of EX4200 switches for EX4400-48F and having some weird port issues. Some ports just wont work. Its very random where I see layer 2 in the ethernet switching table on the old EX4200 but if I move it to the new EX4400 with the same config, sfp etc.... i dont see anything in the table. The sfp does show up in chassis hardware and the physical link comes up but it just doesn't work.
Have tried different firmware versions on the switch, new Juniper sfp, cables etc..... its just really weird and have no clue: The logs show errors but Junipers known issues say these messages are just informal but i'n not so sure:
Apr 15 12:23:43 Honstname fpc0 BCM Error: API bcm_plp_seahawks_module_read(phy_info, addr, (offset + i), TVP_DRV_I2C_RW_OP_LENGTH, data) at tvp_bcm_seahawks_eeprom_read:766 -> -8
Apr 15 12:23:43 Honstname fpc0 [TVP-PIC-BCM] tvp_bcm_seahawks_eeprom_read - Failed to read optic EEPROM for 0/14
Apr 15 12:23:43 Honstname fpc0 [TVP-PIC-BCM] tvp_optics_diag_eeprom_read - Failed to read eeprom for link 0/14
Apr 15 12:23:43 Honstname fpc0 FAILED(100) read of SFP eeprom for port: 14
Apr 15 12:23:56 Honstname fpc0 BCM Error: API bcm_plp_seahawks_module_read(phy_info, addr, (offset + i), TVP_DRV_I2C_RW_OP_LENGTH, data) at tvp_bcm_seahawks_eeprom_read:766 -> -9
Apr 15 12:23:56 Honstname fpc0 [TVP-PIC-BCM] tvp_bcm_seahawks_eeprom_read - Failed to read optic EEPROM for 0/14
Apr 15 12:23:56 Honstname fpc0 [TVP-PIC-BCM] tvp_optics_eeprom_read: Failed to read eeprom for link 0/14
Apr 15 12:23:56 Honstname fpc0 FAILED(100) read of SFP eeprom for port: 14
Apr 15 12:23:56 Honstname fpc0 sfp-0/0/14(14), SFP 6: in sfp_read_range, failed to read SFP EEPROM address 0
Coincidently i've had a couple of times where i move config to another port and repatch it starts working.
Anyone else have any problems like this? Was going to try the latest firmware although its not the latest stable version???
Any help appreciated
------------------------------
STEVEN LOWERY
------------------------------