Wired Intelligent Edge

Hello Community,

 

I have a problem connecting a HPE 5945 48SFP28 8QSFP28 Switch (7.10.R6555) with an HP (aruba) 5406 zl Switch (K.15.18.0019).

In the comware Switch I have an JD118B LX Transceiver, in the aruba switch there is an J4859C Transceiver.

 

I configured the port the following way:

 

interface Bridge-Aggregation137
port link-type trunk
port trunk permit vlan 1 500
link-aggregation mode dynamic
stp root-protection

interface Twenty-FiveGigE1/0/37
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 500
speed 1000
port link-aggregation group 137

interface Twenty-FiveGigE2/0/37
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 500
speed 1000
port link-aggregation group 137

After connecting the switches the Comware-Switch, it says the link is "up", but when I look to the interface statistics I can see, that there are only outgoing packets, no incomming packets. The aruba switch says the link is "down".

 

Before I implemented the 5945 there was a HP 5920 in use. The same transceiver was working in the 5920, the config was the same, except the "speed" settings:

 

interface Bridge-Aggregation11
 port link-type trunk
 port trunk permit vlan 1 500
 link-aggregation mode dynamic
 stp root-protection

interface Ten-GigabitEthernet1/0/6
 port link-mode bridge
 port link-type trunk
 port trunk permit vlan 1 500
 qos trust dscp
 port link-aggregation group 11

interface Ten-GigabitEthernet2/0/6
 port link-mode bridge
 port link-type trunk
 port trunk permit vlan 1 500
 qos trust dscp
 port link-aggregation group 11

The Config in the aruba switch does not changed.

I tried the following:

in the aruba switch:

speed-duplex 1000-full

in the comware switch: 

duplex full

but no changes.

Any ideas?

 

Regards.

Are you using a J4859C (LX Long Reach) on HP 5400zl side? Shouldn't be a J4858C (SR Short Reach)?

 

The J4859C works at a very different Central Wavelength (1310 nm) with respect to J4858C (850 nm)...and that is also valid for to the counterpart JD118B (850 nm)! it's cristal clear that pairing links served by a J4859C with those ones served by a JD118B will no work.

 

Try the J4858C...and report back.

 

sorry, it was a typo... the transceiver is an JD119B LX Transceiver.

Twenty-FiveGigE1/0/37 transceiver information:
 Transceiver Type : 1000_BASE_LX_SFP
 Connector Type : LC
 Wavelength(nm) : 1310
 Transfer Distance(km) : 10(SMF)
 Digital Diagnostic Monitoring : YES
 Vendor Name : HPE
 Ordering Name : JD119B

The same transceiver is working in a 5920AF switch

Can you post sanitized outputs of show lacp, show trunks and show tech transceivers commands executed against the HP 5406zl?

of course

5406# show tech transceivers

transceivers

Transceiver Technical Information:
 Port # | Type      | Prod #     | Serial #         | Part #
 -------+-----------+------------+------------------+----------
 A24    | 1000LX    |     J4859B | P961PV6          |
 B24    | 1000LX    |     J4859B | P962APD          |

5406r# show lacp

                                    LACP

           LACP      Trunk     Port                LACP      Admin   Oper
   Port    Enabled   Group     Status    Partner   Status    Key     Key
   -----   -------   -------   -------   -------   -------   ------  ------
   A24     Active    Trk1      Down      No        Success   0       290
   B24     Active    Trk1      Down      No        Success   0       290

5406# show trunks

 Load Balancing Method:  L3-based (default)

  Port | Name                             Type       | Group  Type
  ---- + -------------------------------- ---------- + ------ --------
  A24  | Uplink                           1000LX     | Trk1   LACP
  B24  | Uplink                           1000LX     | Trk1   LACP

What's about Trk1 member interfaces?

 

Could you also post the output of those commands (HP 5406 zl):

 

• show interfaces brief ethernet A24
• show interfaces brief ethernet B24
• show interfaces transceiver ethernet A24 detail
• show interfaces transceiver ethernet B24 detail
• show running-config interface ethernet trk1
• show running-config interface ethernet A24
• show running-config interface ethernet B24

Down means that the physical port is enabled, but a LACP link is not established: this can indicate, as example, a physical port that is not connected to the network or a speed mismatch between a pair of linked ports.

Hello parnassus,

 

thanks for your reply,

actualy I am not on site so I can't give you these information. But do you think that there is something wrong with the 5406?

Because when I plug out the GBICs from the new 5945 and plug it into the old 5920 and connect it to the 5406, than everything is fine and up. The trunk/link-agg is working and traffic is passing in both ways. I don't have to change anything in the 5406.

It seems that either the configuration on the 5945 is wrong or the transceivers are not compatible together... :-/

 

Hi! sorry I don't follow you...do you mean that the very same SFP Transceivers pair (JD119B) which IS NOT WORKING on the HPE 5945 once pulled out from 5945 and inserted on the HPE 5920 immediately starts WORKING without any other change considering that, in both cases, the LAG peer - the HP 5406 zl - is not touched at all (neither physically nor logically)?

 

Physical links running fromthe HP 5406 zl are the very same on both tests? I mean...Fiber Optic patch cords to HPE 5945 and to HPE 5920 too?

 

If so there is for sure an issue with configuration (or software version) on HPE 5945 side...have you done a like-for-like configurations comparison between 5945 and 5920?

yes, the GBICs are exactly the same. In the 5920 the link is working, in the 5945 not. I also used the the cabling.

I wrote the configuration of both switches in my first post. I cant see anything that could be the reason why this is not working, because there are no special settings... just a tagged VLAN

 

 

Hi We have similar issues connecting fiber links with SFP's HPE ( JD118B ) against Avaya and Cisco Switches with their proprietary SFP. I can put a link working like this : HPE 5945 takes an Avaya SFP and Avaya gets an HPE SFP. as soon as we do this workaround traffic on both ways. We are pointing out to firmware problem...7.1 R6555 like the one on this post Regards Bruno

Have you tried to use JD119B on back SFP Ports instead of using front SFP28 ports?

No, not yet. It will take some time to test it because I am not on site.

Hi guys,

I had the same issue. Turn out that I had to specify the speed and duplex on both ends.

As per the installation guide these ports does not support autonegociation.

Test it and give us feedback.

Regards

Hi

Never seen this before

but a fact is a fact!

HPE5945 installation guide, page 70

 

NOTE:

 

• To connect an SFP28 port on the HPE 5945 48SFP28 8QSFP28 switch to a peer interface that does not support speed and duplex autonegotiation, you must execute the speed and duplex full commands on both interfaces. Configure the same speed and duplex mode for the two interfaces and the speed must be the same as that of the transceiver module or cable installed in the interface.

 

• An SFP28 port on the LSWM124TG2H does not support rate and duplex autonegotiation. You must use the speed and duplex commands to ensure that the interfaces at both ends of a link operate at the same speed and duplex mode. An interface can go up only when the speed configured for the interface is the same as the speed of the transceiver module or cable installed in the interface.

 

Regards

As I wrote in my first post, I tried the following:

in the aruba switch:

speed-duplex 1000-full

in the comware switch: 

duplex full

but no changes. speed 1000 is already set.

Hi

Today we tested another link.
HPE 5945 side auto neg, Cisco side no negotiation. Guess what.

Link is up!

Hi Something or similar is not working using a Avaya 5520 Switch on the end or a Cisco 2960. We connect the links to that switches from an HPE 5945, link is up , but traffic not working.. Seems HPE SFP gbics problems. Currently testing several combinations shows that if you use Avaya Gbic on HPE 5945 side and HPE Gbic on Avaya side it works.. Wowww!!!!