Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

802.1q trunk between ProCurve 2650 and ProCurve 1700-24

SOLVED
Go to solution
Eduardo Abela
Occasional Visitor

802.1q trunk between ProCurve 2650 and ProCurve 1700-24

Hello all,

On one site we have a central ProCurve 2650 set up with 5 VLANs, connected to two other ProCurve managed switches via trunks, and also uplinked to an unmanaged ProCurve switch to extend the VLAN with id 2. Now we need to add another VLAN on every switch, so we need to replace the unmanaged switch with a managed one and set up a new 802.1q trunk between both switches. We bought a 1700-24 to do this, but this one is a web-only managed switch and the trunk terminology is different from the 2650 one. I have tried many settings on both switches (trunked/no trunk port on 2650, tagged/all on 1700) to no avail - I only get traffic on VLAN 1 to go between the switches, but can not get any other VLAN packets to pass. What should be the correct configuration on both switches to set up a 802.1q trunk and get VLANs 2 and 6 to work properly?

Also, we need to access a server on VLAN 6 (192.168.6.0/24) from both VLAN 1 (192.168.1.0/24) and VLAN 2 (192.168.2.0/24). Is this possible with ip routing on the 2650 and no external router?

Thanks in advance,

Eduardo
3 REPLIES
OLARU Dan
Trusted Contributor

Re: 802.1q trunk between ProCurve 2650 and ProCurve 1700-24

Install the latest firmwares in all your devices. Maybe someone heared you and implemented and posted some upgrade that you are not aware yet.
OLARU Dan
Trusted Contributor

Re: 802.1q trunk between ProCurve 2650 and ProCurve 1700-24

Install the latest firmwares in all your devices. Maybe someone heared you and implemented and posted some upgrade that you are not aware of yet.
Dmitry G. Spitsyn
Trusted Contributor
Solution

Re: 802.1q trunk between ProCurve 2650 and ProCurve 1700-24

Hi, Eduardo !

The term trunk means a port trunk (aggregation of ports) on the most of ProCurve switches. The command trunk is used to create a static port trunk.
By default all the ports are untagged members of default VLAN (VLAN 1).
If you create a static port trunk (logical port)by default it will also become an untagged member of default VLAN.

To create VLAN trunk (802.1q trunk) you should use the following.

1. At your ProCurve 2650 side. Say:

vlan 2
tagged 50 #if you need port 50 also to be a tagged member of VLAN 2.
vlan 3
tagged 50 #if you need port 50 also to be a tagged member of VLAN 3.
etc.

OR/AND

vlan 2
tagged Trk1 #if you need the static trunk Trk1 also to be a tagged member of VLAN 2.
vlan 3
tagged Trk1 #if you need the static trunk Trk1 also to be a tagged member of VLAN 3.
etc.

2. At your ProCurve 1700-24 side.
You can configure VLAN behavior for specific interfaces (port/trunk), including the default VLAN identifier (PVID) and accepted frame types.
Port/Trunk â The port number or the ID of a trunk.
VLAN Aware Enabled â VLAN aware ports are able to use VLAN tagged frames to determine the destination of the frame. Click to
enable or disable VLAN awareness mode for this port. (Default: Enabled)
Packet Type â Users can set the interface to accept all frame types, or only tagged frames.
If the Packet Type is set to â All,â the port can accept incoming tagged and untagged packets. Untagged packets will be associated with the VLAN identified by the PVID. Tagged packets will be dropped unless the port is a member of the VLAN identified by the VLAN tag in the packet.
PVID â From a drop down menu, choose the VLAN ID that will be assigned to untagged frames received on this port. You cannot choose â Noneâ for the VLAN ID unless the packet type is set to â Tagged Only.â
Choosing â Noneâ will not assign any VLAN ID to untagged frames received on this port. It is not possible to remove a port from VLAN
1 unless its PVID has been changed to something other than 1. The PVID has no effect on ports that have Packet Type set to Tagged. (Default: 1)

Good luck,
Dmitry