Wired Intelligent Edge

 View Only
last person joined: 20 hours ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution

Fiber to Ethernet converter that works with 1930 switches?

This thread has been viewed 10 times
  • 1.  Fiber to Ethernet converter that works with 1930 switches?

    Posted May 31, 2022 07:06 PM
    Anyone have a fiber converter that they can recommend that will work with the 1930 switches on the fiber side?

    I have a couple of TP-Link MC200CM converters that worked great with our older 2810 and 2530 switches, but the new 1930s will not even bring up a link.
    I also tried a couple of MC200L with HP fiber transceivers with the same result.

    Testing with the TPLink MC200L:
    1. I can take a HP J4858C, put it into the TPLink MC200L fiber converter and plug a patch cable from there to the J4858D in the 1930 and it does not bring up a link to the 1930 (nothing in the error logs, it acts like it wasn't plugged in).
    2. I can put a J4858C in a Netgear ProSafe GS510TPP (or a HP 2810, or a HP/Aruba 2530) and plug a patch cable from there to the J4858D in the 1930 and it brings the link from the 1930 to the Netgear, the 2810 or the 2530 up instantly.
    3. I can put a J4858C in the TPLink MC200L fiber converter, put a J4858C or J4858D it into a Netgear ProSafe GS510TPP, connect them with a patch cable and it brings the link from the TPLink to the Netgear up instantly.
    4. I can put a J4858C in the TPLink MC200L fiber converter, connect it with a patch cable to a J4858C or J4858D in the HP 2810 and it brings the link from the TPLink to the 2810 up instantly.
    5. I can put a J4858C in the TPLink MC200L fiber converter, connect it with a patch cable to a J4858C in the HP/Aruba 2530 and it brings the link from the TPLink to the 2530 up instantly.

    Testing with the TPLink MC200CM:
    1. I can take a TPLink MC200CM fiber converter, connect it with a patch cable to the J4858D in the 1930 and it does not bring up a link to the 1930 (nothing in the error logs, it acts like it wasn't plugged in).
    2. I can take a TPLink MC200CM fiber converter, connect it with a patch cable to a J4858C or J4858D in a Netgear ProSafe GS510TPP and it brings the link from the fiber converter to the Netgear up instantly.
    3. I can take a TPLink MC200CM fiber converter, connect it with a patch cable to a J4858C in a HP 2810 and it brings the link from the fiber converter to the 2530 up instantly.
    4. I can take a TPLink MC200CM fiber converter, connect it with a patch cable to a J4858C in a HP/Aruba 2530 and it brings the link from the fiber converter to the 2530 up instantly.

    I have tried these tests with:
    2 different LC to LC fiber optic cables
    3 different SC to LC fiber optic cables (for the MC200CM)
    3 different J4858C transceivers
    1 J4858D transceiver
    1 Linksys MGBSX1 transceiver
    4 CableMatters 104066 transceivers
    3 TPLink MC200CM fiber converters
    2 TPLink MC200L fiber converters
    2 Aruba 1930 8 port JL681A switches
    1 Aruba 1930 24+4 port JL682A switch
    1 Netgear ProSafe GS510TPP

    All are fiber transceivers and the MC200CM converters are 850NM 1000BASE-SX transceivers and I have had the exact same results with all of them.

    No matter which transceiver is in which device or which fiber converter I use, the 1930s will not bring up a link to the TPLink fiber converter.

    So, the SFPs are good, the fiber converters are good, the cables are good, but the 1930 will not connect to a TPLink MC200L or MC200MC fiber converter.

    It looks like this has been a problem since at least 2021 in firmware version 1.0.5.0(139) per the thread here: https://community.arubanetworks.com/community-home/digestviewer/viewthread?GroupId=25&MID=260735 from hpe091 (originally posted on the old forum before it was migrated).

    I opened a ticket almost 2 weeks ago now, but I keep getting "escalated" or having my issue "raised to the internal team" or "raised to engineering" (that was Thursday's update) and but haven't gotten anything beyond that back from support.
    ------------------------------
    Aaron Z
    ------------------------------