Aruba & ProVision-based
1753872 Members
7410 Online
108809 Solutions
New Discussion юеВ

Re: Procurve 2910al linking

 
itguy01
Occasional Visitor

Procurve 2910al linking

Hi

 

Am still a bit confused with the staging of both switches

 

Config:

There are 2 VLAN's per switchTwo switches in total.  (sw1 & sw2)

Default VLAN

Data VLAN

Software revision: W1470

 

Servers are connected to the both switches in the data VLANTwo ports have been configured for trunks (2x1GB) between both switches.The trk2 resides in the data vlan.

 

For testing purposes I plugged a server into sw2 data vlan but can not ping an ip in the data vlan in sw1This should work or not?

 

Referance I looked at but is not clear to me.

 

http://h30499.www3.hp.com/t5/Switches-Hubs-Modems-Legacy-ITRC/stacking-2-HP-Procurve-2910al-switches/td-p/4792177#.UA193qBdDyI

 

Thank you in advanced

4 REPLIES 4
Fredrik L├╢nnman
Honored Contributor

Re: Procurve 2910al linking

That should work. Could you paste some config?

---
CCIE Service Provider
MASE Network Infrastructure [2011]
H3CSE
CCNP R&S

Usaia Tawakevou
Valued Contributor

Re: Procurve 2910al linking

Should work if you tagged both trunk ports on the two switches data VLAN

itguy01
Occasional Visitor

Re: Procurve 2910al linking

Thank you for your responce.

Ports 17-20 are the candidates to link both 2910al switches

Switch1 is current the primary switch and switch2 will be added to the config. Traffic must flow in an active/active state

From switch2 ports 9-12 will be moved to switch2

 

On switch1 it is TRK3 and switch2 its TRK2.  Tried the Trunk or LACP mode but still can not ping from switch2 to switch

paulgear
Esteemed Contributor

Re: Procurve 2910al linking

Be aware that the word "trunk" has a different meaning on ProCurve than most other switches. Here, trunk means link aggregation. What you need is not only to set up the trunk, but also configure the right VLANs on the trunk (which is the Cisco meaning of trunk).

Are you really sure you want two separate 2 Gbps trunks? In most cases it would be better for them to share a single trunk, in a configuration like this:

switch 1:

vlan 1
name default
untagged ...,trk1
ip address 1.2.1.1 255.255.255.0
vlan 2
name data
tagged ...,trk1
ip address 1.2.2.1 255.255.255.0
trunk 17-20 trk1 lacp

switch 2:

vlan 1
name default
untagged ...,trk1
ip address 1.2.1.2 255.255.255.0
vlan 2
name data
tagged ...,trk1
ip address 1.2.2.2 255.255.255.0
trunk 17-20 trk1 lacp
Regards,
Paul