2 VLANs over 1 optical fibre

[vinz3nt]

Hello,

I'm quite new to this. Please don't judge me on that! I hope to learn from this.

I have 2 buildings, each one has 3 switches (hp 2520-24 PoE), so 6 switches in total.

I have 2 VLANs, VLAN1 for data and VLAN50 for VoIP. VLAN 1 is in the 10.23.x.x range and VLAN50 is in the 10.50.160.x range.

the first 2 switches in each building are dedicated to Data (VLAN1) and the 3rd switch in both buildings are dedicated to VoIP (VLAN50).

Now, the second building is just recently built. No I need to get both VLANs over one optical fibre. In both buildings I put the transceiver in the first switch, in port 27. The other switches are linked together via the 1000Base-T uplink ports with UTP cables.

I heart there are 2 ways to do this, via VLAN tagging or via trunk ports. I tried to do it myself but didn't succeed :-( and no-one can tell me exactly how to do this.

Hopefully someone can help me on this. Any help greatly appreciated!

P.S. This thread has been moved from Switches, Hubs, Modems (Legacy ITRC forum) to ProCurve / ProVision-Based. - Hp Forum Moderator

[Richard Brodie_1]

Unfortunately, the terminology differs between vendors. Trunk is often used for multiple VLANs on a link in the Cisco world but Procurve uses it to mean something else. So only one choice really.

Could you paste the existing VLAN sections (from show run)  on the main switch and the VoIP one please? Redact anything private if you like. The factory default looks like:

vlan 1
   name "DEFAULT_VLAN"
   untagged 1-24
   ip address .....
   exit

[Vince_Whirlwind]

OK, so if you think about your physical links (copper, fibre, whatever) as being pipes, then think about the VLANs as being coloured bits of string that run along inside those pipes.

First objective: You need to get two VLANs to run between the two switches where the fibre is patching in.

Step 1. Create VLAN1 on the switch. Creat VLAN50 on the switch.

Step 2. On the interface that has the transceiver, you need to add the two VLANs:

"vlan 1 tagged 27"

"vlan 50 tagged 27"

Step 3. Repeat for the switch on the other side of the link.

You now have a pipe running between your "Switch 1" in each building, and that pipe has a blue bit of string running through it (VLAN1) and a green bit of string running through it (VLAN50).

Objective 2: You need to get VLAN50 out to "Switch 3".

Step 1. Pick a port on Switch 1 and a port on Switch 3 and patch them together. (Let's pretend you've picked port 24 on both)

Step 2. Extend VLAN 50 out of the port on Switch 1:

vlan 50 tagged 24

Step 3. Create VLAN 50 on Switch 3.

Step 4. Extend VLAN 50 into Switch 3:

vlan 50 tagged 24

Step 5. Make VLAN 50 available for all the voice devices on Switch 3:

vlan 50 untagged 1-23

[vinz3nt]

Hi,

Thanks for the replies!

The second answer is very clear, I made a sketch of this and it made it even more clear.

Tomorrow I wil post a running config of the current situation, it's really interesting en very exciting to learn it this way. I know all the principles but unfortunately I don't get to have enough real-world practice.

Thanks a lot for your knowledge so far!

[vinz3nt]

I'm sorry. Due to a very heavy workload, a colleague of mine with a lot more experience finished my project as I was deployed elsewhere.

He told me over the phone how he did it but I didn't exaclty understand what he meant so I pulled the running config from the 2 switches which are connected via the fiber i.e. switch 10.23.1.101 which is in the main building, port 27 has the transceiver with the fiber and port 28 is used to link via copper to the other 2 switches in the main building, i.e. 10.23.1.102 and 102

I also copied the VLAN port assignment, the 2 mentioned ports are configured as trk1 and trk2 , ports. Trunk ports.

Here it is:

; J9138A Configuration Editor; Created on release #S.15.09.0007
; Ver #03:01.14.05:13
hostname "ProCurve Switch 2520-24-PoE"
console flow-control none
console inactivity-timer 1
trunk 27 trk1 trunk
trunk 28 trk2 trunk
power-over-ethernet pre-std-detect
qos dscp-map 000000 priority 0
qos dscp-map 001000 priority 1
qos dscp-map 010000 priority 2
qos dscp-map 011000 priority 3
qos dscp-map 100000 priority 4
qos dscp-map 101000 priority 5
qos dscp-map 110000 priority 6
qos dscp-map 111000 priority 7
snmp-server community "public" unrestricted
snmp-server contact "Van Breda B.V." location "Switch 1 MER"
vlan 1
name "DEFAULT_VLAN"
untagged 1-26
tagged Trk1-Trk2
ip address 10.23.1.101 255.255.248.0
exit
vlan 50
name "VLAN 50"
tagged Trk1-Trk2
no ip address
exit
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
password manager
password operator

===========================- TELNET - MANAGER MODE -============================
Switch Configuration - VLAN - VLAN Port Assignment

Port DEFAULT_VLAN   VLAN 50 | Port   DEFAULT_VLAN        VLAN 50
---- + ------------ ---------------| ---- + ------------ ------------
3  | Untagged       No      | 17   | Untagged            No
4  | Untagged       No      | 18   | Untagged            No
5  | Untagged       No      | 19   | Untagged            No
6  | Untagged       No      | 20   | Untagged            No
7  | Untagged       No      | 21   | Untagged            No
8  | Untagged       No      | 22   | Untagged            No
9  | Untagged       No      | 23   | Untagged            No
10 | Untagged       No      | 24   | Untagged            No
11 | Untagged       No      | 25   | Untagged            No
12 | Untagged       No      | 26   | Untagged            No
13 | Untagged       No      | Trk1 | Tagged              Tagged
14 | Untagged       No      | Trk2 | Tagged              Tagged

That was the main building, the MER. Below here the SER.

Again, 3 switches, 10.23.1.104, 105 and 106. The fiber is connected to 10.23.1.106 because this switch was already dedicated for IP DECT basestations and was already in use, the other 2 switches were not in use at that time. Just in case you were wondering why the fiber was not connected to 10.23.1.104, being the first switch in the SER.

Here the config:

; J9138A Configuration Editor; Created on release #S.15.09.0007
; Ver #03:01.14.05:13
hostname "Switch 106"
console baud-rate 9600
console flow-control none
trunk 27 trk1 trunk
power-over-ethernet pre-std-detect
interface 25
speed-duplex 100-full
exit
interface 26
speed-duplex 100-full
exit
snmp-server community "public" unrestricted
vlan 1
name "DEFAULT_VLAN"
no untagged 1-22
untagged 23-26,28
tagged Trk1
ip address 10.23.1.106 255.255.248.0
exit
vlan 50
name "VLAN 50"
untagged 1-22
tagged Trk1
no ip address
exit
spanning-tree Trk1 priority 4
no dhcp config-file-update
password manager
password operator

===========================- TELNET - MANAGER MODE -============================
Switch Configuration - VLAN - VLAN Port Assignment

Port DEFAULT_VLAN VLAN 50 | Port   DEFAULT_VLAN VLAN 50
---- + ------------ ------------ | ---- + ------------ ------------
3  | No           Untagged | 17  | No           Untagged
4  | No           Untagged | 18  | No           Untagged
5  | No           Untagged | 19  | No           Untagged
6  | No           Untagged | 20  | No           Untagged
7  | No           Untagged | 21  | No           Untagged
8  | No           Untagged | 22  | No           Untagged
9  | No           Untagged | 23  | Untagged     No
10 | No           Untagged | 24  | Untagged     No
11 | No           Untagged | 25  | Untagged     No
12 | No           Untagged | 26  | Untagged     No
13 | No           Untagged | 28  | Untagged     No
14 | No           Untagged | Trk1 | Tagged      Tagged

Vince, as far as I can tell it's almost exactly as you explained. The ports in the MER and the SER with the fiber are configured so that VLAN1 and VLAN50 are tagged over this port.  The same is done for the ports that interconnect the switches via copper, so both VLANs go over these ports.

What is the function of the trk setting?? Is it really needed? I also don't understand why he configured trk1 and trk2 ports. Being a less is more kinda guy I would all set them as trk1 as it's one LAN anyway. Or isn't that possible.

Well, hopefully you can shed some light on this?

I now have one switch at home so I can test this myself!

Thanks!

[vinz3nt]

This is what I found on trunk ports:

Trunking in HP terms is bundling 2 or more ports together to create a larger bandwidth port. In Cisco terms it is referred to as Etherchannel. The connecting switch must also be configured for trunking.

So, in fact  what my collegue did was actually not necessary at all. He now created a trunk with only 1 port!

Basically, the VLAN tagging on both ends already did the job.