Aruba & ProVision-based

Multiple VLANs on HP 2530-24-PoEP Switch (J9779A)

Occasional Contributor

Multiple VLANs on HP 2530-24-PoEP Switch (J9779A)


I have a longstanding discussion with some collegues I want to end  once and for all.

We mainly use the HP 2530-24-PoEP Switch (J9779A) switches. Connected are a mix of devices;

- Wifi accesspoints (Aruba or Ubiquiti)
- Domotic care system for elderly people
- VoiP clienst (the domotic system als wel as the PBX and wireless phones use this)
- Private GSM picocells (NanoBTS)
- FreePBX (Asterisk) with only SIP clients (Yealink or Aastra phones and Grandstream SIP client on Android phones)
- IP camera's for video surveillance
- Access control (Suprema IP card readers)

Needless to say the network is divided in several VLANs. Every items listed abover here has a unique VLAN ID.
This works very well and until recently all different VLANs had their own switches connected to a router.

Just recently we started to use multiple VLANs on 1 switch as sometimes 1 switch only had a few ports in use. Multiple VLANs could save us a few switches on the whole installation.

Now, as we're all CCNA trained of course we started to use trunks as this is common in Cisco switched. But, we are using HP switches now.

It's my opinion that trunking in hp switched is used to do some sort of load balancing. I thinks its only needed to tag ports 25 and 26 to transport all the VLANs over multiple switches (we usually daisy-chain multiple switches to 1 router port, or we use 2 router ports to the first and last switch with spanning tree for rendundancy).

Am I right or not? For me it's working fine but some collegues persist in using trunks (trk1, trk2...etc.) and we are aiming to deliver a unified solution to all our custumers, we all have a week service duty every 8 weeks so I think it's important all clients are running a similar network.

Richard Litchfield
Respected Contributor

Re: Multiple VLANs on HP 2530-24-PoEP Switch (J9779A)

Search for and download the free document "HPE Networking and Cisco CLI Reference Guide Version 3.2".  If you have a Cisco background, it will help you transition into the world of HPE/ProCurve/E-Series/ArubaOS-Switch networking.

In ProCurve speak, a trunk is a link-aggregation group, typically using LACP.

trunk 1/B24,2/B24 trk24 lacp
interface 1/B24
   name "Link to 3800-02"
interface 2/B24
   name "Link to 3800-02"
interface Trk24
   mvrp enable
vlan 930
   name "Show-Servers"
   tagged  1/A1-1/A13,2/A1-2/A13
   untagged Trk24
   ip address
   ip igmp