M4250-12G2XF-PoE+ Problem lost link on a trunk link

[glvideo]

Hello,

I have a problem using a M4250-12G2XF-PoE+ along with a M4250-26G4XF-PoE+.

Issue : works well for some times (30 mins or 2 hours) then connection is lost on the trunk link

Both switches are equiped with a Ubiquity 10G Copper SFP+ module.

M4250-12G2XF-PoE+

- SFP+ module on port 12

- port 12 on Trunk mode (also tried on General mode with all ports Untagged but port 12 Tagged)

- Auto Trunk disabled

- All other ports on VLAN1 General Mode

- Ports set to NDI 4 profile

M4250-26G4XF-PoE+

- SFP+ module on port 30

- port 30 on Trunk mode (also tried on General mode with all ports Untagged but port 30 Tagged)

- Auto Trunk disabled

- All other ports on VLAN1 General Mode

- Ports set to NDI 4 profile

Trunk link is a CAT6a cable of about 20m

Firmware on both switches : 13.0.2.34 / 1.0.0.7

Everything works well for 30min to several hours until the trunk connection is lost.

I have noticed the M4250-12G2XF-PoE+ Admin Mode in port configuration on port 12 is switched to D-Enabled.

Switching it back to Enabled brings the connexion back... until the next disconnection

Any insight on this ? 

Thanks a lot

[LaurentMa]

Hi, the fs.com 10G Copper transceiver isn't supported, you should really use AXM765-20000S 10GBASE-T NETGEAR certified module in this case. Please export the tech-support file out of this switch using the AV User Interface, please go the botoom of left menu, "Support". And please the flle at ProAVDesign@netgear.com with a link to that thread. We will assess the errors (FCS, checksum, etc.) and if this is the module that is faulty, we will tell you!

Regards, 

[glvideo]

Hi,

Thanks for the quick answer.

SFP not certified yet showed as "Supported" on the switch.

But yes, prone to incompatibility i guess.

File sent via email.

Thanks a lot

[schumaku]

Allow some notes here:

Is there no indication in the logs (on the IT view) why the link was disabled?

Most makers and vendors sold and still offer 10GbE copper modules wiy limited reach only (like max 30 m, sometimes 35 m), due to high power requirements of the earlier chipsets). The reason @LaurentMa pointed to the -200000 version because it's providing longer reach.

[glvideo]

Hi,

thanks for the insight.

the module is effectively getting pretty hot, don't know if it is expected.

Can't say more from the IT point of view.

Thanks

[schumaku]

So no potential related items in the device log?

From wally brain these cli commands show some basic insightof the SFP modules:

# show fiber-ports optics all
# show fiber-ports optics-info all

#show fiber-ports optics-eeprom 1/0/1 (this is unit/slot/port
or
#show fiber-ports optics-eeprom all

[glvideo]

Sorry misunderstood your first question.

NETGEAR support team certified there is a "local fault" error on port 12 (SFP) of the M4250-12G2XF.

Though it only appears on this switch, never on the M4250-26G4XF on the other side.

[schumaku]

Temperatures up to mit 75°C are not uncommon for 10GbE SFP+ copper modules, both generations (30m or 80m) take a lot of power, the longer the link is.

If there is a choice - so in each case except when having to link a 10GbE copper-only system - it's always better to go for DAC, active DAC, active fiber DAC, or fiber modules and a fiber pair not connection. All these need just som 0.xW, up to 1 for Multimode at 300 meters, or up to 1.5W for single mode fiber pairs regardles if it's a short, a 10 km, or even a 30 km (or much longer up to 150..180km) at a high module cost.

10Gb copper Ethernet does draw up to about 3W (or the allowed maximum), and does create a lot of heat regardless of the link length. Combined with fan-less or low-noise AV switches, it's not a difficult guess this is not an ideal solution - because the module cages are not specially covered by airflow.

[glvideo]

Well then if it happens the actual module faulty is caused by overheat then the problem would be the same when using a certified NETGEAR module right ?

I have about 20m cable run between the two switches. Using copper is much more convenient as the infrastructure is already set. i could eventually run a fiber cable if really needed but will get some work and mess up a bit the installation.