Wired Intelligent Edge

Hi,

I have to create a trunk group between a hp 5308xl and hp 2510G procurve switch. The ports on 5308xl that need to be in a trunk group are on a specific vlan. Hence, I cannot use dynamic lacp because I do not have GVRP enabled.

I've read that there are three trunk options:

Dynamic lacp

Static lacp and

Static trunk

ftp://ftp.hp.com/pub/networking/software/Mgmt-Oct2005-59906023-Chap12.pdf

How do I create a three port trunk group between those two switches and keep them in a specific vlan?

Is static lacp and static trunk the same?

Any help is much appreciated!

Thanks!

I don't know why you need GVRP?

I had a Procurve "Core" switch with some H3C access switches and the trunks were:

LACP v. Dynamic according to my saved configs

Elsewhere, I have an H3C Core with some Procurve Access switches. For them, the trunks are:

static v. trunk

Vince_Whilwind,

Thanks for the response.

HP documentation says:

"Dynamic LACP trunks operate only in the default VLAN (unless GVRP isenabled and Forbid is used to prevent the trunked ports from joining the default VLAN). Thus, if an LACP dynamic trunk forms using ports that are not in thedefault VLAN, the trunk will automatically move to the default VLAN unless GVRP operation is configured to prevent this from occurring. In some cases, this can create a traffic loop in your network."

h30499.www3.hp.com/t5/forums/replypage/board-id/switching-e-series-forum/message-id/4807

I have GVRP disabled on my switches.

So you are saying I can use static lacp on one and static trunk on the other switch to get the trunk established?

This is what I'm hoping to get out of this:

I have a heavy traffic link on the core switch (5308xl) that is connected to the 2510g, which is also a part of the vlan 100 and I would like to get three ports on each switch into a trunk group.

What would be my best shot at this?

And also, does the link on core switch go down before I make it a trunk group? If so, please let me know as I can only do it during non-business hours.

I've played with cisco gear mostly and haven't had much exposure to hp switches.. so any help in this regard would be great!

Thanks!

You will want to practice on a test switch to get it right, but enabling a bridge-aggregate/trunk on a production system will cause no outage provided you follow the correct order of configuration.

I have to pass VLAN1, so what I am about to propose will differ on that score from what you are looking for. I looked into passing it as a tagged VLAN at least, but things were starting to look unnecessarily complicated, so I left it as the Untagged/PVID trunk VLAN.

Mine also differs in that it is a Commware7 config v. a Procurve 5406, but I'm sure the principle's the same.

Here's my recent config:

On the core

interface Bridge-Aggregation104
port link-type trunk
port trunk permit vlan 1 104 204 249

interface Ten-GigabitEthernet1/3/0/4
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 104 204 249
port link-aggregation group 104

interface Ten-GigabitEthernet2/3/0/4
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 104 204 249
port link-aggregation group 104
 

Then, on the Access switch:

interface Trk1
   tagged vlan 104,204,249
   untagged vlan 1

interface A21
   untagged vlan 1
   trunk trk1 trunk

interface B21
   untagged vlan 1
   trunk trk1 trunk

Vince_Whirlwind,

I wish I could practice it on a test switch but unfortunately I don't have the resources to do so.
And HP does not have simulators like Cisco Packet Tracer or GNS3 to test on..

Could you please clarify why would we need to use Bridge-Aggregation?

I have an hp 5308xl procurve and a hp 2510g procurve switch.

Thanks,

Sorry, I was thinking H3C with the 5308 - if it's Procurve/Procurve then it's easy.

Just make sure you create and configure the trunk interfaces before assigning interfaces to them. If you do it the other way around, they lose their config and you lose the connection.

In one of the replies I notice the conclusion to use LACP on one end and static trunk on the other end; that won't work.

Whatever protocol you choose, make sure both ends of the trunk are using the same protocol to establish the trunk.

The difference between LACP and a static trunk is that with a static trunk you define two or more interfaces that are to be bundled. They will, whatever is on the other side of those links. When using LACP, you are telling the switch to creeate a bundled link, but only of the other side of those links agree to bundle them (ie: the switch at the other side is also configured for LACP,  and the cables are connected to the right interfaces and switches).

So with a static trunk, the switch doens't check anything, it blindly does what you configure.

With LACP there is some checking by the switch. And that is where the default VLAN comes in... the LACP-related communications is done over the default VLAN, so that default VLAN is (by definition) going to be one of the VLANs on the trunk-interface.

So in your scenario, the static trunk sounds the best choice; and then add that Trk-interface to the VLAN you want.

John,

I really appreciate your response to this!

I will try what you suggested this week and let you know!

Thanks a bunch!!

John,

I was unable to work on this last week.

However, I have to get this fixed tomorrow.

I have two hp procurve switches - and right now there is only one link connected to each other which has heavy traffic between them. Hence, I would like to create a trunk of three ports for bandwidth distribution.

Please let me know if this configuration commands are correct and if it will work:

conf t

Core#

trunk C-16, B-16, D-16 trk1 trunk

vlan 10

untagged trk1

ip address xxxx xxxx

switch2#

trunk 42-44 trk1 trunk

vlan 10

untagged trk1

We already have a vlan 10 configured with an ip address.. so does that make any difference?

Or would I just assign the same ip address to the Core switch?

Please let me know!!

Thanks a bunch!

Suggest you use LACP instead of trunk. In your scenario there will be no real difference, but LACP is the current standard, and there is no reason not to use it

trunk C16, B16, D16 trk1 lacp

and

trunk 42-44 trk1 lacp

Richard,

I will try this for sure and let you know how it goes!

Thanks!