Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

HP LACP config assistance

 
abs4network
Occasional Visitor

HP LACP config assistance

Hi All,

I am new to HP switches and need a configuration assistance in creating LACP channel between 2 switches.

What I want (from Cisco's perspective).

Interface gi1/1

  no switch port

  channel-group 10 mode on

Interface gi1/2

 no switch port

  channel-group 10 mode on

Interface Port-channel10

ip add 1.92.168.1.1 255.255.255.252

Same setup on the other switch with IP of 192.168.1.2/30

I am quiet not getting the correct configuration., so i tried to do the trunk way.

L2 LACP and untagged a vlan over the trk, bound to the trunk group (Lacp).

It works however, i am not able to make the lacp active, it just always is in passive, and thus blocks 1 link.

 

Etherchannel L3 Addresses

SW1 config

trunk C19,E24 trk9 lacp

interface C19
name "Trk9-LACP-Trunk"
untagged vlan 909
trunk trk9 lacp
exit

interface E24
name "Trk9-LACP-Trunk"
untagged vlan 909
trunk trk9 lacp
exit

vlan 909
name "909-trunk"
untagged Trk9
ip address 192.168.90.9 255.255.255.252
exit

LACP

LACP Trunk Port LACP Admin Oper
Port Enabled Group Status Partner Status Key Key
----- ------- ------- ------- ------- ------- ------ ------
C19 Active Trk9 Blocked No Failure 0 970
E24 Active Trk9 Up Yes Success 0 970

Spanning tree: Trk9 | 20000 64 Forwarding | 9cdc71-192100 2 Yes Yes

LACP Peer Information.


System ID: 9cdc71-192100


Local Local Port Oper LACP Tx
Port Trunk System ID Port Priority Key Mode Timer
------ ------ -------------- ----- --------- ------- -------- -----
C19 Trk9 000000-000000 83 0 0 Passive Slow


sh lacp peer E24

LACP Peer Information.


System ID: 9cdc71-192100


Local Local Port Oper LACP Tx
Port Trunk System ID Port Priority Key Mode Timer
------ ------ -------------- ----- --------- ------- -------- -----
E24 Trk9 5820b1-a0cc00 120 0 404 Active Slow

 

I know what is the issue here is, just don't know how to fix it as I am unfamiliar with HP switching configuration syntaxes..

Also, both the switches don't share the vlans, this is just a link that is connectinv the switches via L3 interfaces using static routes pointed to respective subnets via those vlan909 IPs.

Both switches are identical in hardware and software.

Sw model: 5406Rz12

Software revision : KB.16.02.0013

Would appreciate if anyonce can help in here or point me to the correct configuration settings. We want to utilize both links at a time (active) and not blocking.

TIA.

Ab

 

7 REPLIES 7
parnassus
Honored Contributor

Re: HP LACP config assistance

Can you share the outputs of show running-configuration interface X CLI command executed on both SW1 and SW2 for any member interface X of configured Port Trunks here discussed? Can you also share the outputs of show interfaces X CLI command?

abs4networks
Visitor

Re: HP LACP config assistance

Hi Parnassus,

Thanks for responding. My apologies for delayed response as got busy with other works.

Please see the outputs below;

Site-A(is the internet exit)
show running-config interface X
show interface X
==================

# sh run int c19

Running configuration:
interface C19
untagged vlan 909
trunk trk19 lacp
exit

# sh run int D24

Running configuration:
interface D24
untagged vlan 909
trunk trk19 lacp
exit

# sh run vlan 909

Running configuration:

vlan 909
untagged Trk19
ip address 192.168.90.10 255.255.255.252
exit

# sh trunks | i Trk19
C19 | 100/1000T | Trk19 LACP
D24 | 1000LX | Trk19 LACP

# sh lacp | i Trk19
C19 Active Trk19 Blocked No Failure 0 404
D24 Active Trk19 Up Yes Success 0 404

# sh int c19

Status and Counters - Port Counters for port C19

Name :
MAC Address : 5820b1-a0dcad
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 3,656,978,030 Bytes Tx : 1,908,472,480
Unicast Rx : 24,145,706 Unicast Tx : 4,290,435,607
Bcast/Mcast Rx : 97,689,603 Bcast/Mcast Tx : 71,802,234
Errors (Since boot or last clear) :
FCS Rx : 0 Drops Tx : 31
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 0 Deferred Tx : 0
Others (Since boot or last clear) :
Discard Rx : 0 Out Queue Len : 0
Unknown Protos : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 0 Total Tx (bps) : 1,891,128
Unicast Rx (Pkts/sec) : 0 Unicast Tx (Pkts/sec) : 0
B/Mcast Rx (Pkts/sec) : 0 B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 0 % Utilization Tx : 00.18 %


SYD-SW-C01# sh int d24

Status and Counters - Port Counters for port D24

Name :
MAC Address : 5820b1-a0dc88
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 2,382,773,752 Bytes Tx : 2,981,814,175
Unicast Rx : 2,823,611,792 Unicast Tx : 3,894,373,752
Bcast/Mcast Rx : 26,634,828 Bcast/Mcast Tx : 72,300,629
Errors (Since boot or last clear) :
FCS Rx : 2 Drops Tx : 126
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 3 Excessive Colln : 0
Total Rx Errors : 5 Deferred Tx : 0
Others (Since boot or last clear) :
Discard Rx : 0 Out Queue Len : 0
Unknown Protos : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 43,562,720 Total Tx (bps) : 17,930,440
Unicast Rx (Pkts/sec) : 4,079 Unicast Tx (Pkts/sec) : 3,092
B/Mcast Rx (Pkts/sec) : 0 B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 04.35 % Utilization Tx : 01.79 %

# sh vlan 909

Status and Counters - VLAN Information - VLAN 909

VLAN ID : 909
Status : Port-based
Voice : No
Jumbo : No

Port Information Mode Unknown VLAN Status
---------------- -------- ------------ ----------
Trk19 Untagged Learn Up

*******************************************
*******************************************
Site-B (internet exits from Site A)
show running-config interface X
show interface X
==================

#sh run int c19

Running configuration:
interface C19
untagged vlan 909
trunk trk9 lacp
exit

#sh run int e24

Running configuration:
interface E24
untagged vlan 909
trunk trk9 lacp
exit

#sh run vlan 909

Running configuration:

vlan 909
untagged Trk9
ip address 192.168.90.9 255.255.255.252
exit

# sh trunks | i Trk9
C19 | 100/1000T | Trk9 LACP
E24 | 1000LX | Trk9 LACP

# sh lacp | i Trk9
C19 Active Trk9 Blocked No Failure 0 970
E24 Active Trk9 Up Yes Success 0 970


# sh int c19

Status and Counters - Port Counters for port C19

Name :
MAC Address : 9cdc71-1931ad
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 399,142,466 Bytes Tx : 1,013,259,729
Unicast Rx : 324,520 Unicast Tx : 151,626,347
Bcast/Mcast Rx : 1,629 Bcast/Mcast Tx : 1,208,707
Errors (Since boot or last clear) :
FCS Rx : 0 Drops Tx : 0
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 0 Deferred Tx : 0
Others (Since boot or last clear) :
Discard Rx : 0 Out Queue Len : 0
Unknown Protos : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 0 Total Tx (bps) : 0
Unicast Rx (Pkts/sec) : 0 Unicast Tx (Pkts/sec) : 0
B/Mcast Rx (Pkts/sec) : 0 B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 0 % Utilization Tx : 0 %

# sh int e24

Status and Counters - Port Counters for port E24

Name :
MAC Address : 9cdc71-193168
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 2,211,233,104 Bytes Tx : 844,880,459
Unicast Rx : 256,867,408 Unicast Tx : 2,585,839,016
Bcast/Mcast Rx : 39,326,905 Bcast/Mcast Tx : 1,943,220
Errors (Since boot or last clear) :
FCS Rx : 0 Drops Tx : 20,624,260
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 0 Deferred Tx : 0
Others (Since boot or last clear) :
Discard Rx : 7,887 Out Queue Len : 0
Unknown Protos : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 8,229,136 Total Tx (bps) : 25,661,360
Unicast Rx (Pkts/sec) : 2,282 Unicast Tx (Pkts/sec) : 3,303
B/Mcast Rx (Pkts/sec) : 0 B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 00.82 % Utilization Tx : 02.56 %

#sh vlan 909

Status and Counters - VLAN Information - VLAN 909

VLAN ID : 909
Name :
Status : Port-based
Voice : No
Jumbo : No
Private VLAN : none
Associated Primary VID : none
Associated Secondary VIDs : none

Port Information Mode Unknown VLAN Status
---------------- -------- ------------ ----------
Trk9 Untagged Learn Up

 

When we test the links, there is a ping drop for about 10 seconds (Spanning tree) for the other link to become active. I don't want that insteadt use both the ports as active and clubbed together so that when one link goes down, the conenctivity is still UP without any loss of traffic.

PS: Both the sites are supposed to be connected by L3 (logically) as they both share different VLANs. Also, cannot afford to lose access to the site B becuase there is no IT present there hence no console resource available. Has to be done from Site A only without losing the siteB access.

 

Thanks,

Ab

parnassus
Honored Contributor

Re: HP LACP config assistance

Wait...AFAIK...

# sh trunks | i Trk19
C19 | 100/1000T | Trk19 LACP
D24 | 1000LX | Trk19 LACP

...to form a Port Trunk (Trk19 with LACP) you need that both C19 and D24 (and respective interfaces on the peer side) belong to the SAME media type either both 100/1000T (Copper) or both 1000LX (Fiber Optic).

Port Trunk member links need to fulfill these requirements:

  1. Same Media Type
  2. Same Media Speed (generally set with port mode setting "Auto-1000", which is the default value on Gigabit Ethernet Interfaces, if you're working with them)
  3. Full Duplex FD (10Gbps ports operate only at Full-Duplex FD)

So you're not providing the very first requirement (1), on both ends. 

abs4networks
Visitor

Re: HP LACP config assistance

I thought only same speed and duplex were the requirements, coz it works on Cisco so, but will try to see if I can get same media type ports for this.

Will update that and get back to see if the issue remains.

parnassus
Honored Contributor

Re: HP LACP config assistance

Well, for sure I can't speak for Cisco Switches since I'm not a super expert about them, but I'm quite sure HP ProCurve requirements for HP Port Trunking can be essentially summarized with these historical words:

Port Connections and Configuration: All port trunk links must be point-to-point connections between the switch and another switch, router, server, or workstation configured for port trunking. No intervening, non-trunking devices are allowed. It is important to note that ports on both ends of a port trunk group must have the same mode (speed and duplex) and flow control settings.

Link Connections: The switch does not support port trunking through an intermediate, non-trunking device such as a hub, or using more than one media type in a port trunk group. Similarly, all links in the same trunk group must have the same speed, duplex, and flow control.

Then you can configure all permitted bells&whistles on your Port Trunks (LACP versus Non-Protocol, etc.)...but requirements above are essential IMHO.

abs4networks
Visitor

Re: HP LACP config assistance

Thanks for your help.

I checked and unfortunately, we don't have the links available in same medium hence we have to do with what we have, though I was curious if there is anything we can do to reduce the link convergence timeout value as for example:

Original state: Link A (Active), Link B (Blocked)

When link A is down, it takes about approx 10 ping drops (somewhere around 50 seconds) before the Link B comes UP and then once Link A is back online, it again takes 50 seconds to Revert back to Original State.

How can I minimize this STP port state timeout from this long to a quicker one if modifiable.

Known that STP switch ports move through these states in the time-frames as below:

Initialization to Blocking (0 seconds)
Blocking to Listening (20 seconds)
Listening to Learning (15 seconds)
Learning to Forwarding (15 seconds)

Just wanted to know if something can be done to reduce this timeout.

Also, what would be the equivalent study path on HPE in comparision to Cisco CCNA (routing and Switching) (Beginner) and CCNP(Switching)(Avanced). so that I don't make a fool out of my self with such dumb queires because I don't understand how the HPE console/syntax works.

Thanks.

parnassus
Honored Contributor

Re: HP LACP config assistance

You didn't show us any sanitized running configuration of both switches but, generally speaking, RSTP (Rapid STP) should be used (especially if you aren't planning to extensively use features provided by MSTP Multiple STP).

Given that you know to enable and configure RSTP then a point-to-point link (its interface) should be configured with a command like:

spanning-tree x point-to-point-mac true

where x is the interface id used as uplink to the other peer switch.

RSTP should give you better results.