We are replacing a Cisco 4500x with an Aruba 6300 SFP+ switch. When we make the swap, one closet does not come back up, 14 others do. We have tried both Cisco and Aruba access switches on the access end and neither work with the 6300, but both do work when connected to the 4500x.
Customer does not know anything about their fiber, but I can tell it is extremely old MM. Even stranger, the colors do not match for this particular run. One side is orange blue, the other is green brown, so there must be a junction box somewhere. Both sides use 1g SX(MM) SFPs, and each one is properly branded for the corresponding switch. All transceivers and fiber zips have been tested and proved to work on other connections. Both configurations are just straight trunk ports, nothing fancy. We do not even get a link light when using the aruba core. We also put a fluke tester on it and it shows the fiber to be bad, like doesn't even show a link. The distance between the buildings is well within the max range (at least if its a relatively straight shot).Basically I think (99% sure) the fiber is bad in some way. But what I am trying to be able to explain to the customer is why it works with their existing cisco core, but not when we put in the aruba 6300. All I can think of is that there is a sensitivity threshold for allowing the link to form, and the Cisco device allows for connections to form with a weaker connection than the 6300 does, but I cannot find any data to back that up. I am also going to try using a Cisco transceiver on the aruba core with the unsupported module command in place to test this theory. Has anyone run into anything similar or have any thoughts?
Both SFPs are 1g-SFP-SX, for reference.
Here's a link to the transceiver guide: It lists maximum distance and a support matrixhttps://support.hpe.com/hpesc/public/docDisplay?docId=a00028947en_us
show interface transceiver threshold-violations
show interface transceiver detailshow interface x/x/x dom detailMay give you additional insight into why those issues are happening. The dom command specifically should give some more information. It should list current level, and "warning" and "alarm" levels.
As a side note, We use Fluke for our fiber testing, and we've had very good experiences. When it tells us there is a problem, there is a problem.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.