HP 2530 - Cisco 2960 VLAN problem

[Gavinm]

Hi all, this has been asked numerous times before (by other people) but I'm still having problems!
I have a HP 2530 connected from port 24 to port 19 on a CISCO 2960 Gigabit Copper
Using Default VLAN 1 and VLAN 40
VLAN 40 should get an IP 172.20.x.x
VLAN 1 IP 172.24.x.x

Problem
VLAN 40 traffic not trunking (CISCO trunk not aggregation) from HP 2530 to CISCO 2960
When a computer is connected to port 20 on the CISCO it gets a VLAN 40 IP address (correct result)
When a computer is connected to port 5 on the HP it should get a VLAN 40 address but gets a VLAN 1 (incorrect result)

Set Up
HP 2530
Port 5 - VLAN 40 tagged
Port 5 - VLAN 1 (default native) untagged
Port 24 - VLAN 40 tagged
Port 24 - VLAN 1 (default native) untagged
STP disabled

CISCO 2960
Port 19 (Uplink Trunk)
switchport mode trunk
switchport nonegotiate

Port 20
interface GigabitEthernet0/20
switchport access vlan 40
switchport mode access
spanning-tree portfast trunk (not needed but left)
STP disabled

How can I get a computer connected to port 5 on the HP 2530 to pick up a VLAN 40 IP address when passing through the CISCO?

Thanks

[vladi0782]

Configurar
HP 2530
Port 5 - VLAN 40 untagged

[parnassus · Accepted solution]

Also, port 24 (HP Switch) and port 19 (Cisco Switch) should match their VLANs tagging: this means that, HP side, port 24 should (as is) be untagged member of VLAN 1 and tagged member of VLAN 40...and, Cisco side, port 19 must be native on VLAN 1 and permit VLAN 40.

In terms of configurations:

Aruba/HP 2530 (ArubaOS-Switch or HP ProVision):

vlan 1
untagged 24
vlan 40
tagged 24

Cisco IOS:

interface GigabitEthernet 19 <-- eventually correct the interface name
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 1
switchport trunk allowed vlan 1,40 <-- corrected
switchport mode trunk
switchport nonegotiate

 See here.

[Gavinm]

Thanks  vladi0782 but I don't think that can be right.
Surely the port must be tagged VLAN 40 (not untagged) for it to be on the VLAN.

[Gavinm]

Thanks  parnassus for the information and link.
I'll try this out later and see if it works.

One question - on page 4 of the linked pdf has the line  
switchport trunk allowed vlan 1-3 
but in your information you have
switchport trunk allowed vlan 40

Do you think I should use:
switchport trunk allowed vlan 1,40
or should the native VLAN go through automatically?

Thanks

[parnassus]

Typo, corrected.

With regards to access port (the port where you're going to connect your client)...if the client isn't able to recognize (or is not setup to recognize) tagged frames...then the switch port should be set as untagged member of VLAN you need to be part of (VLAN 40 in your case)...that's the HP/HPE/Aruba jargon...that's to say that @vladi0782 is correct about that.

See the example (Access) on the presentation at page 5, on Cisco you have:

interface GigabitEthernet 0/20
switchport
switchport access vlan 40
switchport mode access

which translates into HP configuration jargon for interface 5:

vlan 40
untagged 5

as @vladi0782 wrote you above.

[Gavinm]

Hi   vladi0782  
Ignore my previous comment, you were correct about the untagging.

As parnassus has pointed out, your solution was correct when configure with parnassus's help.

Thanks for this, it has solved a real problem!

[Gavinm]

Thanks, it works!

Between you and  @vladi0782 the VLAN is now working
Thanks also for the useful link - it will be added to my massive file of useful information.

[parnassus]

Glad we helped and you were able to solve your issue...so we deserve Kudos!