Brandon Garnett
asked on
Configuring trunk group from HP V1910 to HP 2910al, unable to make it work
We have an HP ProCurve V1910 24-port switch and an HP ProCurve 2910al 48-port switch. Currently we have three VLANs: 23, 33, and 43. 23 is server traffic, 33 is PC traffic , and 43 is VoIP traffic.
I configured the 2910al’s ports 23 and 24 as Trunk Group 2 with Trunk Type LACP. I tagged Trk2 with VLANs 23, 33, and 43. (Other trunk groups on this 2910al are configured this way that connect to another 2910al.)
I am trying to configure ports 23,24 on the V1910 to trunk to ports 23,24 on the 2910al. On the V1910 I created a dynamic link aggregation group BAGG1 that includes ports 23,24. Is that what I should do?
I have also set BAGG1 as tagged for VLANs 23, 33, and 43.
The problem I have is the browser GUI for the V1910 is very basic and restrictive compared to the 2910al. Some settings are missing and others I just may not be understanding. I’m a Cisco guy. I can work real magic on Cisco equipment, but HP’s switches baffle me. Sadly, the V1910 does not have a CLI worth anything, it has just a few commands available unlike the 2910al.
Has anyone got experience with setting up a trunk group between an HP V1910 and an HP 2910al? I am obviously not getting it right because I am unable to pass traffic between the two switches when I physically connect the trunking cables. Any help would be greatly appreciated.
-RS
I configured the 2910al’s ports 23 and 24 as Trunk Group 2 with Trunk Type LACP. I tagged Trk2 with VLANs 23, 33, and 43. (Other trunk groups on this 2910al are configured this way that connect to another 2910al.)
I am trying to configure ports 23,24 on the V1910 to trunk to ports 23,24 on the 2910al. On the V1910 I created a dynamic link aggregation group BAGG1 that includes ports 23,24. Is that what I should do?
I have also set BAGG1 as tagged for VLANs 23, 33, and 43.
The problem I have is the browser GUI for the V1910 is very basic and restrictive compared to the 2910al. Some settings are missing and others I just may not be understanding. I’m a Cisco guy. I can work real magic on Cisco equipment, but HP’s switches baffle me. Sadly, the V1910 does not have a CLI worth anything, it has just a few commands available unlike the 2910al.
Has anyone got experience with setting up a trunk group between an HP V1910 and an HP 2910al? I am obviously not getting it right because I am unable to pass traffic between the two switches when I physically connect the trunking cables. Any help would be greatly appreciated.
-RS
ASKER
Thank you for the reply.
BAGG1 was not a mistype, that's exactly what I configured on the switch. I have been looking over the manual while trying to configure this switch and according to page 206 of that PDF, it says to go to Network then Link Aggregation and create a new Aggregation Interface, which is exactly what I did. That creates the BAGG1 interface. It can be static or dynamic, both of which I don't understand.
So if BAGG is not what I want, what could possibly be the solution? I really have looked this manual over and I see no other option to try. BAGG seems to be it.
BAGG1 was not a mistype, that's exactly what I configured on the switch. I have been looking over the manual while trying to configure this switch and according to page 206 of that PDF, it says to go to Network then Link Aggregation and create a new Aggregation Interface, which is exactly what I did. That creates the BAGG1 interface. It can be static or dynamic, both of which I don't understand.
So if BAGG is not what I want, what could possibly be the solution? I really have looked this manual over and I see no other option to try. BAGG seems to be it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Following the below manual should give you the details to configure the lag on the 1910.
I am a Cisco guy as well and had to go through the pains of learning the hp cli and still cringe when I come across a model that has a nearly non existent cli.
The alternate is to evaluate if you really need the bandwidth of a lag or if you can live with configuring MST, doing a little vlan load balancing, and accepting the short outage when a link fails.
For all those out there reading, remember that the speed of any single session going across a lag can only go as fast as a single link within the lag. The only way to increase the throughput of a session across a lag is to increase the speed of the links, or lower the latency end to end. If there are enough simultaneous sessions going across a lag that equal more bandwidth than a single link, then a lag is definitely required.
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03586669/c03586669.pdf