HPE Aruba Networking & ProVision-based
1837086 Members
2321 Online
110112 Solutions
New Discussion

Re: LACP Link aggregation between HP 2910al and SPARC T4-1 Server

 
rrahul
New Member

LACP Link aggregation between HP 2910al and SPARC T4-1 Server

Hi All,

 

I'm currently facing a strange issue. We have 2 x 2910al switches, one at the PROD and the other at the DR site. Both connected via a fibre uplink. On each switch we have an LACP Trunk of 4x1G links connecting to SPARC T4-1 server. The problem is when a file is copied between both the SPARC servers using SCP then it fails. Error received is "Disconnecting: Corrupted MAC at the input". 

 

Strangely the FTP transfer also fails. I tried connecting a machine directly on one switch and then tried transfering a file to directly connected switch using Secure Copy, it also fails. The LACP config is as below:

 

# sh lacp

LACP

PORT LACP TRUNK PORT LACP LACP
NUMB ENABLED GROUP STATUS PARTNER STATUS
---- ------- ------- ------- ------- -------
5 Active Trk2 Up Yes Success
7 Active Trk2 Up Yes Success
8 Active Trk1 Up Yes Success
9 Active Trk2 Up Yes Success
10 Active Trk1 Up Yes Success
12 Active Trk1 Up Yes Success
13 Active Trk2 Up Yes Success
14 Active Trk1 Up Yes Success

 

trunk 8,10,12,14 Trk1 LACP
trunk 5,7,9,13 Trk2 LACP

 

spanning-tree Trk1 priority 4

 

Any suggessions would be greatly appreciated.

 

Thanks

Rahul

 

 

P.S. This thread has been moved fromSwitches, Hubs, Modems (Legacy ITRC forum) to ProCurve / ProVision-Based. - Hp Forum moderator

2 REPLIES 2
Vince-Whirlwind
Honored Contributor

Re: LACP Link aggregation between HP 2910al and SPARC T4-1 Server

What are the physical and trunk interface configs?

 

I wonder if you are sending frames to the servers in .1q format (ie, with VLAN tags on), and the servers don't understand .1q?

Priyansha
Valued Contributor

Re: LACP Link aggregation between HP 2910al and SPARC T4-1 Server

hi,

 

This is a known issue with scp while transferring large files over the LAN.

 

There could be 3 reasons :

 

1 : Bad Nic card (Need to replace it or upgrade the driver)

2: Faulty RAM on the machine

3:A firewall rule on the remote box which rejected traffic to IP 224.0.0.1, which is part of the Local Network Control Block. That's evidently a channel required by the two host systems in connection with rx and tx delay requests.

Thank you,
Was the post useful? Click on the white KUDOS! Star.
For HP Guided Troubleshooting; https://support.hpe.com/connect/s/?language=en_US