Trunk between h3c and procurve

[Takkari]

We are trying to setup a 4 port trunk between hp 5308xl and hp 5120ei series switch to accommodate load balancing and increase throughput. After doing some research we have decided to go with static lacp as the trunking protocol.
There is a link that's connected to our application servers and it is in a specific vlan, vlan 5.
Any suggestions on how to get this up and running effectively?
Thanks!

 

[Ertaz]

Is vlan 5 tagged on the existing connection to the other switch? Can you post the config for that vlan and the config for the existing switch link?

 

[Takkari]

Ertaz,

This is what we are hoping to get done eventually:

We currently have one link (connection) between 5308xl and a 251048g switch.
Core is 5308xl and 2510 is the switch connecting our servers.

The hp 5120ei switch is a brand new addition.
We would like to create a four port trunk between 5308xl and 5120ei and then from 5120ei to 251048g switch another four port trunk.
We are going to terminate the link between 5308xl and 2510-48g as soon as we figure out the above.
I hope that makes sense..

And vlan 5 is not tagged on the existing connection to 2510-48g switch.

Core Switch1# sh vlan 5

Status and Counters - VLAN Information - Ports - VLAN 5

802.1Q VLAN ID : 5
Name : CITRIX
Status : Port-based
Voice : No

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




Please let me know if you need more info..

 

[Ertaz]

So all the devices on the 2510-48g are in vlan 5?

 

[Takkari]

This is the running-configuration on the 2510 switch:
All the devices are on the default vlan...

ProCurve-2510G-48# sh running-config

Running configuration:

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

hostname "ProCurve-2510G-48"
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 1-48
ip address dhcp-bootp
exit

 

[Ertaz]

OK, so it appears that your vlans are inconsistent between the two switches. You have VLAN 5 on the core connected to vlan one on your edge switch. With a new trunk config we can fix that error. Be back with more info in a few.

 

[imagoon]

LACP is a port-channel protocol and has nothing to do with trunking. That may help you find info on the internet about it.

Normally the switches need something like this:

interface port-channel 1
switchport mode trunk
switchport trunk allowed vlan add 5

interface range ethernet 1/g1,2/g1
channel-group 1 mode auto

Basically you build the port channel, then assign the ports. From there the channel groups need to be consistent, IE same vlans, native vlans etc.

 

[Ertaz]

Here is a quick drawing of what you're proposing:


http://www.vci.net/~eoverby/drawing/hptrunk.xps



Forgive the appearance.

 

[Takkari]

Okay, so after reading some on hp 5308xl and hp 5120ei guide.. I have come to a conclusion that in my scenario I could use Static LACP or Static Trunk.
The difference between lacp and static trunk is that with static trunk you can define two or more interfaces that need to be bundled on both switches.
When using lacp, you tell the switch to create a bundled link, but only of the other side of those links agree to bundle them(the switch at the other side has to be configured for LACP and the cables are connected to the right interfaces).
So with a static trunk, the switch doesn'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.

Ertaz,

The traffic going from the core into the edge switch is untagged.. So do I still have to make any changes to the config???
And by the way, the drawing is dead on!! What tool did you use to create that? Do you mind sharing? I think it's a great tool!

 

[Takkari]

This is what I did on both the switches to configure trunking:
Core Switch1# sh trunks

Load Balancing

Port | Name Type | Group Type
---- + -------------------------------- --------- + ----- -----
B15 | 100/1000T | Trk1 Trunk
B16 | 100/1000T | Trk1 Trunk
D15 | 100/1000T | Trk1 Trunk
D16 | 100/1000T | Trk1 Trunk


Core Switch1#show running-config

trunk B15-B16,D15-D16 Trk1 Trunk
spanning-tree Trk1 priority 4


Question: Why does my configuration show spanning-tree Trk1 priority 4!!??
Spanning-tree is disabled on all my switches... I know, it would be great to enable STP but I need to do some reading before I can enable that on my production network..
Any thoughts on what that command specifies?


Now the configuration on the HP 5120ei switch:

[HP 5120]display current-configuration
interface GigabitEthernet1/0/45
port link-type trunk
port trunk permit vlan 1
shutdown
#
interface GigabitEthernet1/0/46
port link-type trunk
port trunk permit vlan 1
shutdown
#
interface GigabitEthernet1/0/47
port link-type trunk
port trunk permit vlan 1
shutdown
#
interface GigabitEthernet1/0/48
port link-type trunk
port trunk permit vlan 1
shutdown


Both the switches are configured with static trunk.
The ports are disabled for now as I cannot test it until after hours.
I would really love to see it fly without any issues with the above configuration..

 

[Ertaz]

Okay, so after reading some on hp 5308xl and hp 5120ei guide.. I have come to a conclusion that in my scenario I could use Static LACP or Static Trunk.
The difference between lacp and static trunk is that with static trunk you can define two or more interfaces that need to be bundled on both switches.
When using lacp, you tell the switch to create a bundled link, but only of the other side of those links agree to bundle them(the switch at the other side has to be configured for LACP and the cables are connected to the right interfaces).
So with a static trunk, the switch doesn'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.

Ertaz,

The traffic going from the core into the edge switch is untagged.. So do I still have to make any changes to the config???
And by the way, the drawing is dead on!! What tool did you use to create that? Do you mind sharing? I think it's a great tool!

Hey, I've got a copy of Visio here. Works pretty well for most things.

So basically you have the default vlan(assuming 1) the same for both sides of the LACP for each set of switches and ports?

Does vlan 5 exist on all the switches?

Is vlan 5 set to be qtagged over the LACP on both sides?

The ports that your Servers are attached to the 2501 edge switch appear to be in vlan 1 on your current configuration.

They will need to be moved to vlan 5 once you perform this change.

 

[Ertaz]

Also
QUESTIONS:What VLANS do you want for the host ports on the 5120ei and 2510 switches?

Do you want to be able to dynamically assign vlans to ports at a later time?


Is there a reason that you want to have the 5120ei between the 2510 and the core?

Do you have a snmp tool configured for monitoring utilization and errors? (CACTI is free if you don’t)

 

[Takkari]

Ertaz,
I do not want any VLANs on the host ports on 5120ei switch..
Would my configuration above not work in my scenario..?

 

[Ertaz]

Ertaz,
I do not want any VLANs on the host ports on 5120ei switch..
Would my configuration above not work in my scenario..?

If you want the server vlan, (5) to be on the 2510 switch as it effectively is today, you have to make sure:

1) VLAN 5 exists on the core switch, 5308, the intermediate switch, 5120ei, and the 2510
2) VLAN 1 is the untagged vlan on the trunk of all three switches.
2) VLAN 5 is QTAG'd via the trunking you've setup on all three switches.
3) VLAN 5 is assigned untagged to the access ports that you require, like the serevers that are crrently connected on the 2510.


From your current config it looks like the 2510's VLAN config is all vlan 1, and is bridged to vlan 5 on connection to the 5308. While this works, it needs to be corrected in order to trunk everything properly.

The remaining access ports on the 5120ei can be left in vlan 1, it only needs to pass vlan 5 on the trunk ports.

 

[Takkari]

Ertaz,

Thank you for all the information you have shared! I was able to get this going.
However, I have a new question:

I am now trying to setup an aggregation between two switches.
A Cisco 3550 and a hp procurve 5308xl.
We currently have one 100 mbit link between two sites.
We leased another 100 mbit link so we can aggregate both and have 200mbit bandwidth for fail-over and more throughput.

How can I get this going effectively? Please help. Thanks!

 

[Ertaz]

Ertaz,

Thank you for all the information you have shared! I was able to get this going.
However, I have a new question:

I am now trying to setup an aggregation between two switches.
A Cisco 3550 and a hp procurve 5308xl.
We currently have one 100 mbit link between two sites.
We leased another 100 mbit link so we can aggregate both and have 200mbit bandwidth for fail-over and more throughput.

How can I get this going effectively? Please help. Thanks!

Glad you got it working.


Here is a link with the basics:

http://integratingi****************...regation-between-cisco-and-procurve-switches/



Here is the Cisco L2 Etherchannel setup for the 3550:

http://www.cisco.com/c/en/us/td/doc...ea1/configuration/guide/3550scg/swethchl.html


Look these over, then post what ports you plan on using on each side and what you think the config will look like. We'll hash it out after that. You seem to have the link agg mastered on the HP side, and the Cisco side is just a touch easier, imo.