Aruba & ProVision-based

Unable to get interfaces to bond with BAG and use LCP - Also what is best method steps?

 
jerryroy1
Occasional Contributor

Unable to get interfaces to bond with BAG and use LCP - Also what is best method steps?

I am trying to bond two interfaces into a BAG and then use LCP to connect to a XenServer. Can anyone explain these error messages and the order of operation (1st, 2nd, 3rd etc...). I have tried multiple ways and keep getting this same output.

bagg24.pngbagg24-2.pngbagg24-3.png

5 REPLIES 5
jerryroy1
Occasional Contributor

Re: Unable to get interfaces to bond with BAG and use LCP - Also what is best method steps?

From the CLI, what could be wrong?

[HP5500-DMZ-1-GigabitEthernet2/0/18]display link-aggregation verbose Bridge-Aggregation 24
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired

Aggregation Interface: Bridge-Aggregation24
Aggregation Mode: Dynamic
Loadsharing Type: Shar
System ID: 0x8000, d07e-286f-58f8
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
GE1/0/24 S 32768 21 {ACDEFG}
GE2/0/18 U 32768 21 {ACG}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
GE1/0/24 0 32768 0 0x8000, 0000-0000-0000 {DEF}
GE2/0/18 0 32768 0 0x8000, 0000-0000-0000 {DEF}
[HP5500-DMZ-1-GigabitEthernet2/0/18]

akg7
HPE Pro

Re: Unable to get interfaces to bond with BAG and use LCP - Also what is best method steps?

Hello,

Can you please share below details:
1. Current software version in switches?
2. Are these switches in IRF?
3. Please share both interfaces configuration and other end configuration?
4. Are you doing bonding or binding at other end?

Thanks!
I am an HPE Employee

Accept or Kudo

jerryroy1
Occasional Contributor

Re: Unable to get interfaces to bond with BAG and use LCP - Also what is best method steps?

1) <HP5500-DMZ-1>display version
HP Comware Platform Software
Comware Software, Version 5.20.99, Release 5101P05
Copyright (c) 2010-2012 Hewlett-Packard Development Company, L.P.
HP A5500-24G-4SFP HI Switch with 2 interface Slots uptime is 424 weeks, 6 days, 3 hours, 52 minutes

HP A5500-24G-4SFP HI Switch with 2 interface Slots with 2 Processors
1024M bytes SDRAM
4096K bytes Nor Flash Memory

512M bytes Nand Flash Memory
Hardware Version is REV.B
CPLD Version is 002
Bootrom Version is 116
[SubSlot 0] 24GE+4SFP+2SFP PLUS Hardware Version is REV.B
[SubSlot 2] 2 CX4 Hardware Version is REV.A

<HP5500-DMZ-1>

2) Yes 3 switches in IRF Ring
3) Interfaces:

interface Bridge-Aggregation24
port access vlan 35
link-aggregation mode dynamic

interface GigabitEthernet1/0/24
port link-mode bridge
port access vlan 35
port link-aggregation group 24

interface GigabitEthernet2/0/18
port link-mode bridge
port access vlan 35
port link-aggregation group 24

bagg24-4.pngbagg24-5.png

These two images are from our XenServer. We have other LACP bonded links with two or 4 interfaces and all are working correctly.

akg7
HPE Pro

Re: Unable to get interfaces to bond with BAG and use LCP - Also what is best method steps?

Hello,

It seems issue is on server side LACP configuration.

Is there any port speed configured at server side?

Can you select Active-Active mode instead of LACP load balancing?

Thanks!

I am an HPE Employee

Accept or Kudo

parnassus
Honored Contributor

Re: Unable to get interfaces to bond with BAG and use LCP - Also what is best method steps?

Hi! follow this (for the Comware switch part of setting up the LAG Link Aggregation Group):

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03503743

The order of execution is explained very clearly. I suggest you to (re)start from scratch with 1/0/24 and 2/0/18 physical interfaces in their default states (thus remove them from LAG 24, delete LAG 24, default 1/0/24 and 2/0/18 and start again...with Xen Server cables disconnected).

The Xen server side looks pretty much correct (LACP -> two Gigabit Ethernet interfaces were bonded together), the hosts should be set to be VLAN unaware (default I believe)....because, as last LAG configuration step switch side, you should set the VLAN membership (VLAN 35 as untagged -> native) at LAG logical interface level only (without touching LAG's member interfaces) and this setting will propagate down to LAG's physical member interfaces.

Note:

HP A5500-24G-4SFP HI Switch with 2 interface Slots uptime is 424 weeks, 6 days, 3 hours, 52 minutes

424 Weeks of uptime means more than 8 Years of uptime!


I'm not an HPE Employee
Kudos and Accepted Solution banner