connecting procurve and cisco switches with vlans

[Jon Scales]

Looking for some assistance. I have a number of procurve 2650's and in someone's wisdom they added a cisco catalyst switch into the network for servers!!!
We run a data and voice vlan and I need this traffic to pass through to the catalyst.
Can anyone help with the configuration?
Thanks

[Kell van Daal]

Hi Jon,

can you be a little more specific?
It will allow for better answers ;)

A small hint to start with:

Configuring VLAN's on ProCurve switches differ from configuring VLAN's on Cisco switches.
For example:
Configuring port membership for VLAN's on ProCurve is done within the VLAN configuration context. For Cisco this is done within the port configuration context.
A VLAN that has a port configured as untagged on ProCurve is the same as a VLAN configured as native on a port on Cisco.

For ProCurve, download the manual here:
ftp://ftp.hp.com/pub/networking/software/59908853-1004-Adv-Trff-Mgmt.pdf

For Cisco, view the manual here:
http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a0080160a90.html

(random catalyst btw, since you didn't specify the type)

[Jon Scales]

I am happy configuring the hp equipment and have done many in the procurve range from 2524 up to 9308's.

The catalyst is a 2950.
The issue I am having is configuring the "trunk" ports on the hp switch to carry both my voice and data traffic to the Cisco.

[Kell van Daal]

Assuming VLAN 10 is Data and VLAN 20 is voice. Also assuming the first port on each switch is the trunk port, the nessecary configuration on both switches would look like:

ProCurve 2650:
conf t
vlan 10
untagged 1
vlan 20
tagged 1


Cisco 2950:
conf t
vlan 10
exit
vlan 20
exit
interface fastethernet 0/1
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk native vlan 10
switchport nonegotiate
switchport trunk allowed vlan remove 1


This setup would pass traffic for VLAN 10 untagged and traffic for VLAN 20 tagged between the switches.
Could be that the 2950 does not support ISL trunking. In that case setting the encapsulation won't be nessecary.

Hope this helps.

[Jon Scales]

Kell,

Thanks for that information. Most helpful.

Jon

[stefano colombo_1]

Hi ,
I'm the same problem.
We have done the configuration you suggested except for the data vlan . We have set both the VLAN tagged on the trunk port .
But it didn't work

[stefano colombo_1]

Hi ,
I've untagged the native vlan on the HP switch and now it works
Thanks