Procurve untagged/tagged on Cisco side

[Hubsi-Smith]

Hello,

I have a problem with in future mixed environment with Procurve and Cisco devices.

Environment looks like: Router <-> SW1 (192.168.100.1) <-> SW2 (192.168.100.2)<-> Server20 (end device with networkcard and several VLANs)

I will explain the current situation. We have two Procurve devices and some identical VLANs.

VLAN 1: default VLAN(IP Address 192.168.100.0/24)

VLAN 100: Server-MGMT (no IP)

VLAN 200: CAD-Server (no IP)

VLAN 300: CAD-Clients (no IP)

Uplink Port looks like VLAN 1 is untagged and VLAN100 to 300 are tagged.

Server20 is connect to SW2 on Port 12.

VLANs on Port12 are configured to:

VLAN 1: no

VLAN 100: untagged

VLAN 200: tagged

VLAN 300: tagged

This configuration works very well with Procurve switches.

But on Cisco side a switchport could only be an access port either a trunk port.Well, I am not sure how I could this configure with a Cisco SG500 switch? 

[RFS]

With Cisco, if you want to have multiple tagged VLANs go through the port you set it up as a trunking port. In general, access port is assigned to only one VLAN.

[Georg Pauwen · Accepted solution]

Hello,

on the SG500 switches, the corresponding syntax would look like below:

switchport trunk allowed vlan add all
switchport trunk native vlan 100
spanning-tree link-type point-to-point

[Hubsi-Smith]

Hello,

thank you for your response.

I am not very common with Cisco devices, but what is the difference between "switchport trunk allowed vlan add all" and "switchport mode trunk" ?

Does "switchport trunk native vlan 100" means the default vlan moved from VLAN 1 to VLAN 100? Could there any mismatch occure?

How does the Uplinkport looks on Cisco side? Could I still reach any IP address configured in VLAN-1?

[Jon Marshall · Accepted solution]

The "switchport mode trunk" command tells the port it is going to be a trunk. 

The "switchport trunk allowed vlan ..." command allows you to specify what vlans are allowed on the trunk (by default all vlans are allowed). 

The "switchport trunk native vlan <x>" command tell the switch which vlan is going to be untagged on the trunk, it is nothing to do with the default vlan so just make sure the untagged vlan is the same on both ends of the trunk and you should not get any mismatches. 

Jon

[Hubsi-Smith]

Hello,

if I understood right, I also have to set the "switchport trunk native vlan 100" on the Uplink port.

Maybe it looks like this on the Cisco Uplink port:

int gi24

switchport mode trunk
switchport trunk allowed vlan add 1, 100, 200, 300
switchport trunk native vlan 100

On the Procurve configuration side I set on the Uplink port

VLAN 1, 200 and 300 as tagged port and

VLAN 100 as untagged port.

I hope that I am right...

[Jon Marshall]

Correct. 

Jon

[Hubsi-Smith]

Hello,

thank you so far... one last question.

If my HP switch has IP: 192.168.100.1 (VLAN-1) and the Cisco Switch has IP: 192.168.100.2 (VLAN-1).

Could I still ping from HP to the Cisco switch in VLAN-1 ?

[Jon Marshall]

Yes as you are allowing vlan 1 on the trunk.

Jon