Configure Dot 1Q Trunk on HP Switch

Willo · 4th November 2009, 8:56 PM

Hi All,

Whilst I'm not a noob on Networking, I'm also not an expert.

So with that all over with I was wondering if the Network guru's are able to assist.

I have a setup where I have a Cisco 1841 configured with Sub-Interfaces Dot 1 Q trunked to a core 2950 switch.

Off the core switch I have trunks configured to 3 other 2950's which are at the top of each rack.

All working happily with about 5 VLANS all routing between each other nicely.

Along comes a C3000 blade chassis with the poorer cousin a GbE2c HP switch.

Now Mr HP and Mr CISCO don't talk the same language. Mr CISCO says Dot 1 Q trunk or Switchport mode trunk.

But Mr HP says that a trunk is "Etherchannel" or port grouping.

All I want to do is create a Dot1Q trunk between the Cisco switch at the top of the rack and the HP switch in the blade chassis.

I can't figure it out, apparently Mr HP talks about untagged and tagged frames, which the concept I understand but configuration escapes me. Also the switch has a management interfact on a magic vlan id of 4096 which is a connection to the OnBoard Administrator module which if I use my IP addressing scheme reserved for VLAN 1 MGMT VLAN in the rest of the network it sort of screws things around.

Anyone know how to configure a trunk between a HP switch and a Cisco switch???

HELP

Willo

cs-cam · 4th November 2009, 9:32 PM

Etherchannel isn't trunking, it's the same in Cisco and HP worlds. Something like this should work

Code:

interface A1
  # trunk link

vlan 2
  name "VLAN2"
  no untagged A1

vlan 2
  name "VLAN3"
  no untagged A1

Willo · 5th November 2009, 7:47 AM

Quote:

Originally Posted by cs-cam

Etherchannel isn't trunking, it's the same in Cisco and HP worlds. Something like this should work

Code:

interface A1
  # trunk link

vlan 2
  name "VLAN2"
  no untagged A1

vlan 2
  name "VLAN3"
  no untagged A1

Ta,

No it's not but the actual docco from HP explains that the terminology is different??????

Willo · 5th November 2009, 11:21 AM

Here is a document by HP ProCurve Network Engineer:-

"HP ProCurve and Cisco Catalyst Interoperability"

Now the concept for this is quite simple although where I run into trouble is the Management Interface.

As documented the Default/Untagged VLAN on a Cisco Network is VLAN 1. All of my management interfaces on Network Infrastructure, Storage, iLO ports etc are all assigned an address within the same network ID all on VLAN 1.

The docco also states that when deploying the HP it must match the cisco config for tagged/untagged ports as there is no choice as the IOS does the config in the background when you assign a port as a trunk.

That being the case, VLAN 1 is untagged. As per my network schema, the management interface is assigned an address via the Blade OnBoard Admin which is in VLAN 1. Trouble is the HP Switch talks to the network via the OnBoard admin on internally configured VLAN 4096. So to get the internal management interface I don't even need a cable connected to the switch.

when I connect a cable to the switch and set it to VLAN 1 as per docco, the connection to the connection to the management interface starts to flap and pings respond differently eg:-
TimeOut
Response Received
Response Received
TimeOut

So the config is tricking me to no end.

In theory on the HP, the trunk port is Untagged and a member of VLAN 1, but also a member of all the other vlans defined on the HP switch in tagged mode.

The HP switch also has PVID as well as tagged/untagged.

Cheers

Willo

Doc-of-FC · 5th November 2009, 6:49 PM

sorry to sound useless at this time, i will check the old HP switch at work for its previous config if i get a chance tomorrow.

things like the stupid HP naming of shit was one of the reasons i tore out the $15,000 piece of shit HP chassis.

Willo · 7th November 2009, 9:07 PM

BUMP..................

Willo · 10th November 2009, 12:16 PM

BUMP

...........

turiya · 10th November 2009, 1:03 PM

All you need to do is match the vlan config on the two devices.

Cisco uses switchport mode trunk to define a port that is trunking vlans and you can then define the native vlan on that port.

HP just uses untagged or tagged vlans. Your untagged vlan is the same as ciscos native vlan on a trunk. The tagged vlans are the "rest" so to speak.

You would have it configured like this:

Code:

interface A1
  # trunk link

vlan 1
  name "VLAN1"
  untagged A1

vlan 2
  name "VLAN2"
  tagged A1

vlan 3
  name "VLAN3"
  tagged A1

On the Cisco you would have something like this:

Code:

interface fastethernet0/1
  switchport mode trunk
  switchport trunk native vlan 1
!
interface vlan1
  no ip address
!
interface vlan2
  no ip address
!
interface vlan3
  no ip address
!

I'm a little bit rusty on the HP vlanning, but you definately do have to define the untagged vlan for a port(it has to have one untagged vlan) and then any tagged vlans you want on top of that.

I generally don't use the native vlan option with cisco stuff, but it is there if you need it.

The above should work but I have no way of testing it at the moment.

EDIT: Forget about HP's trunk terminology. As that document states, they use the trunking term for link aggregation.

EDIT 2: The above cisco config is correct on 2960 switches, I can't recall if you need to define whether you are wanting to use ISL or dot1Q on 2950 switches.

ltd73 · 10th November 2009, 1:12 PM

Quote:

Originally Posted by Willo

Now Mr HP and Mr CISCO don't talk the same language. Mr CISCO says Dot 1 Q trunk or Switchport mode trunk.

But Mr HP says that a trunk is "Etherchannel" or port grouping.

yep, for whatever reason, HP used the term 'trunk' to not refer to 'VLAN trunking' but instead to refer to Etherchannel.

why HP chose to do this is beyond me. the ability to trunk vlans was invented by cisco and was known as a 'trunk' before HP even had ethernet switches....

in either case, whatever the seting is, you need to enable "802.1Q VLANs over a single link" whatever its called.

Quote:

Originally Posted by Willo

the switch has a management interfact on a magic vlan id of 4096 which is a connection to the OnBoard Administrator module which if I use my IP addressing scheme reserved for VLAN 1 MGMT VLAN in the rest of the network it sort of screws things around.

VLAN # 4096 isn't possible. reason being 802.1Q vlans have a 12-bit vlan number, twelve bits of binary is 111111111111 = 0xfff (hex) = 4095.

the number 4096 cannot be represented with 12 bits.

Quote:

Originally Posted by turiya

On the Cisco you would have something like this:

[...]
interface vlan1
no ip address

"vlan interfaces" are SVIs - the layer3 representation of what a VLAN connects to.

what actually matters in the cisco config for the vlan at layer-2 is the vlan database...

evilasdeath · 10th November 2009, 1:28 PM

Quote:

Originally Posted by turiya

Code:

interface fastethernet0/1
  switchport mode trunk
  switchport trunk native vlan 1
!
interface vlan1
  no ip address
!
interface vlan2
  no ip address
!
interface vlan3
  no ip address
!

The above config is incorrect

Code:

vlan 1
name blah
vlan 2 
name blah2
vlan 3
name blah3

will create the vlans, and depending on your VTP mode will show how they appear in the running config transparent will show the above, server/client will hide them in vlan.dat.

from memory i know that the 2950 will only allow you to add an IP address onto 1 vlan but i'm not sure if it actually allows you to create multiple vlan interfaces without deleting the others.

turiya · 10th November 2009, 1:38 PM

Incorrect in what way?

Yes, I know you need to define the vlans in vlan database(but that was not what the OP was after). I was giving examples of what the config would look like on the two different types of switches. And in this it IS correct. That is exactly how things appear on every one of my multiple 2960 switches I have here in my network.

cs-cam · 10th November 2009, 1:49 PM

Turiya's config is correct in the context of the question, OP isn't missing anything from vlan.dat. Moving along....

VLAN4096 may be a software-only thing in HP Blade switching, I can't comment. I can help with basic trunking and simple configs but like most, I'm a Cisco person with some Procurve switches at an edge site so my knowledge is limited.

Sounds like something you might be better off chasing up on the HP support forums, doesn't look like you're getting a lot of responses here unfortunately.

turiya · 10th November 2009, 1:55 PM

I've trunked between Cisco 2960s and Procurve 2910al's so I'm pretty sure my config examples are what it should look like(assuming your vlans are setup on the cisco in the database correctly).

I'll have a dig around and see if I have direct config examples from the last time I did this.

EDIT: I've only dealt with HP stackable and modular switches and not their blade switches so there may be something different with the way they are configured, but I wouldn't think it too likely.

evilasdeath · 10th November 2009, 1:59 PM

vlan definitions in the database are required, vlan interfaces are not and add nothing if they have no IP address.

And since 2950/2960s only support 1 vlan interface for use with management the other vlan interfaces are useless.

Willo · 10th November 2009, 2:18 PM

The configs look great, thank you.

I think were I will struggle is the VLAN 4096 as the address the blade switch has assigned to this VLAN is VLAN 1 on cisco devices.

So creating a VLAN 1 as untagged on HP and all other VLANS tagged isn't working correctly. With all uplink ports un plugged the Management interface is still connected, it's got a virtual connection through the Onboard Admin.

when I do trunk the two, it get 2 out of 4 pings not getting through.

I might just have to check with HP....

4th November 2009, 8:56 PM	#1
Willo Member Join Date: Oct 2002 Location: Melbourne, Australia Posts: 719	Configure Dot 1Q Trunk on HP Switch Hi All, Whilst I'm not a noob on Networking, I'm also not an expert. So with that all over with I was wondering if the Network guru's are able to assist. I have a setup where I have a Cisco 1841 configured with Sub-Interfaces Dot 1 Q trunked to a core 2950 switch. Off the core switch I have trunks configured to 3 other 2950's which are at the top of each rack. All working happily with about 5 VLANS all routing between each other nicely. Along comes a C3000 blade chassis with the poorer cousin a GbE2c HP switch. Now Mr HP and Mr CISCO don't talk the same language. Mr CISCO says Dot 1 Q trunk or Switchport mode trunk. But Mr HP says that a trunk is "Etherchannel" or port grouping. All I want to do is create a Dot1Q trunk between the Cisco switch at the top of the rack and the HP switch in the blade chassis. I can't figure it out, apparently Mr HP talks about untagged and tagged frames, which the concept I understand but configuration escapes me. Also the switch has a management interfact on a magic vlan id of 4096 which is a connection to the OnBoard Administrator module which if I use my IP addressing scheme reserved for VLAN 1 MGMT VLAN in the rest of the network it sort of screws things around. Anyone know how to configure a trunk between a HP switch and a Cisco switch??? HELP Willo

4th November 2009, 9:32 PM	#2
cs-cam Member Join Date: Oct 2007 Location: Brisbane, QLD Posts: 259	Etherchannel isn't trunking, it's the same in Cisco and HP worlds. Something like this should work Code: interface A1 # trunk link vlan 2 name "VLAN2" no untagged A1 vlan 2 name "VLAN3" no untagged A1

10th November 2009, 1:03 PM	#8
turiya Member Join Date: Sep 2002 Location: Adelaide Posts: 105	All you need to do is match the vlan config on the two devices. Cisco uses switchport mode trunk to define a port that is trunking vlans and you can then define the native vlan on that port. HP just uses untagged or tagged vlans. Your untagged vlan is the same as ciscos native vlan on a trunk. The tagged vlans are the "rest" so to speak. You would have it configured like this: Code: interface A1 # trunk link vlan 1 name "VLAN1" untagged A1 vlan 2 name "VLAN2" tagged A1 vlan 3 name "VLAN3" tagged A1 On the Cisco you would have something like this: Code: interface fastethernet0/1 switchport mode trunk switchport trunk native vlan 1 ! interface vlan1 no ip address ! interface vlan2 no ip address ! interface vlan3 no ip address ! I'm a little bit rusty on the HP vlanning, but you definately do have to define the untagged vlan for a port(it has to have one untagged vlan) and then any tagged vlans you want on top of that. I generally don't use the native vlan option with cisco stuff, but it is there if you need it. The above should work but I have no way of testing it at the moment. EDIT: Forget about HP's trunk terminology. As that document states, they use the trunking term for link aggregation. EDIT 2: The above cisco config is correct on 2960 switches, I can't recall if you need to define whether you are wanting to use ISL or dot1Q on 2950 switches. Last edited by turiya; 10th November 2009 at 1:06 PM.

10th November 2009, 1:55 PM	#13
turiya Member Join Date: Sep 2002 Location: Adelaide Posts: 105	I've trunked between Cisco 2960s and Procurve 2910al's so I'm pretty sure my config examples are what it should look like(assuming your vlans are setup on the cisco in the database correctly). I'll have a dig around and see if I have direct config examples from the last time I did this. EDIT: I've only dealt with HP stackable and modular switches and not their blade switches so there may be something different with the way they are configured, but I wouldn't think it too likely. Last edited by turiya; 10th November 2009 at 2:00 PM.

5th November 2009, 11:21 AM	#4
Willo Member Join Date: Oct 2002 Location: Melbourne, Australia Posts: 719	Here is a document by HP ProCurve Network Engineer:- "HP ProCurve and Cisco Catalyst Interoperability" Now the concept for this is quite simple although where I run into trouble is the Management Interface. As documented the Default/Untagged VLAN on a Cisco Network is VLAN 1. All of my management interfaces on Network Infrastructure, Storage, iLO ports etc are all assigned an address within the same network ID all on VLAN 1. The docco also states that when deploying the HP it must match the cisco config for tagged/untagged ports as there is no choice as the IOS does the config in the background when you assign a port as a trunk. That being the case, VLAN 1 is untagged. As per my network schema, the management interface is assigned an address via the Blade OnBoard Admin which is in VLAN 1. Trouble is the HP Switch talks to the network via the OnBoard admin on internally configured VLAN 4096. So to get the internal management interface I don't even need a cable connected to the switch. when I connect a cable to the switch and set it to VLAN 1 as per docco, the connection to the connection to the management interface starts to flap and pings respond differently eg:- TimeOut Response Received Response Received TimeOut So the config is tricking me to no end. In theory on the HP, the trunk port is Untagged and a member of VLAN 1, but also a member of all the other vlans defined on the HP switch in tagged mode. The HP switch also has PVID as well as tagged/untagged. Cheers Willo

5th November 2009, 6:49 PM	#5
Doc-of-FC Member Join Date: Aug 2001 Location: Canberra Posts: 1,879	sorry to sound useless at this time, i will check the old HP switch at work for its previous config if i get a chance tomorrow. things like the stupid HP naming of shit was one of the reasons i tore out the $15,000 piece of shit HP chassis.

7th November 2009, 9:07 PM	#6
Willo Member Join Date: Oct 2002 Location: Melbourne, Australia Posts: 719	BUMP..................

10th November 2009, 12:16 PM	#7
Willo Member Join Date: Oct 2002 Location: Melbourne, Australia Posts: 719	BUMP ...........

10th November 2009, 1:38 PM	#11
turiya Member Join Date: Sep 2002 Location: Adelaide Posts: 105	Incorrect in what way? Yes, I know you need to define the vlans in vlan database(but that was not what the OP was after). I was giving examples of what the config would look like on the two different types of switches. And in this it IS correct. That is exactly how things appear on every one of my multiple 2960 switches I have here in my network.

10th November 2009, 1:49 PM	#12
cs-cam Member Join Date: Oct 2007 Location: Brisbane, QLD Posts: 259	Turiya's config is correct in the context of the question, OP isn't missing anything from vlan.dat. Moving along.... VLAN4096 may be a software-only thing in HP Blade switching, I can't comment. I can help with basic trunking and simple configs but like most, I'm a Cisco person with some Procurve switches at an edge site so my knowledge is limited. Sounds like something you might be better off chasing up on the HP support forums, doesn't look like you're getting a lot of responses here unfortunately.

10th November 2009, 1:59 PM	#14
evilasdeath Member Join Date: Jul 2004 Posts: 1,527	vlan definitions in the database are required, vlan interfaces are not and add nothing if they have no IP address. And since 2950/2960s only support 1 vlan interface for use with management the other vlan interfaces are useless.

10th November 2009, 2:18 PM	#15
Willo Member Join Date: Oct 2002 Location: Melbourne, Australia Posts: 719	The configs look great, thank you. I think were I will struggle is the VLAN 4096 as the address the blade switch has assigned to this VLAN is VLAN 1 on cisco devices. So creating a VLAN 1 as untagged on HP and all other VLANS tagged isn't working correctly. With all uplink ports un plugged the Management interface is still connected, it's got a virtual connection through the Onboard Admin. when I do trunk the two, it get 2 out of 4 pings not getting through. I might just have to check with HP....