Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

LACP port not working

tonyvarghese06
Occasional Visitor

LACP port not working

Ha friends,

 

I'm a Cisco certified professional.My recent employer using procure 4204, 2510 series  swish.  Now I'm facing lacp loop issue.  I create 4 lacp port (b1,b3,b5,b7) lacp ports in our 4204 swish. It's dynamic lacp. the loop create when I connect 4 port  together. Our network diagram  look like this.

 

 

 

procurve2510     procurve 2510

 

                        

                  procurve 4204

this is 4204 config

J8770A Configuration Editor; Created on release #L.10.23

hostname "ProCurve Switch 4204vl"
module 1 type J8768A
module 2 type J9033A
interface B1
   lacp Active
exit
interface B3
   lacp Active
exit
interface B5
   lacp Active
exit
interface B7
   lacp Active
exit
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged A1-A24,B1-B24
   ip address 192.168.100.3 255.255.0.0
   exit

 

both 2510 have same configuration

 

; J9280A Configuration Editor; Created on release #Y.11.12

hostname "ProCurve Switch 2510G-48"  
trunk 47-48 Trk1 LACP
interface 7-8 LACP active   
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-2
   ip address 192.168.100.1 255.255.255.0
   no untagged 3-46,Trk1
   exit
vlan 20
   name "LAN"
   untagged 6-10
   tagged 1,45-46,Trk1
   exit
vlan 30
   name "VOICE"
   untagged 11-12
   tagged 1,45-46,Trk1
   exit
vlan 40
   name "DB"
   untagged 13-15
   tagged 1,45-46,Trk1
   exit
vlan 50
   name "SAN"
   untagged 16-19
   no ip address
   tagged 1,45-46,Trk1
   exit
vlan 60
   name "SERVERS"
   untagged 20-32
   tagged 1,45-46,Trk1
   exit
vlan 9
   name "BSNL"
   untagged 3
   no ip address
   tagged 4-5
   exit
vlan 70
   name "DMZ"
   untagged 33-44
   tagged 1,45-46,Trk1
   exit 

 

 

please help me to rectify this problem.

1 REPLY
Peter_Debruyne
Honored Contributor

Re: LACP port not working

Hi,

 

why do you manually assign the trunk members on 1 side and let it dynamic on the other side ?

In general this dynamic method is not recommended, so I would recommend you create the trunks on the 4200 as well:

trunk x1,x2 trk1 lacp

trunk x3,x4 trk2 lacp

 

This will also allow you to assign the proper vlan tags on these trk1 and trk2 interfaces (in the posted config the access switches are sending tagged traffic, but that would not be accepted by the 4200).

 

Use show trunk and show lacp (if supported) to verify the status

use show vlan port trk1 (detail) to verify if the vlans match on both sides.

 

Hope this helps,Peter