- Integrated Systems
- About Us
- Integrated Systems
- About Us
03-06-2020 02:50 AM
HPE 1820 VLAN help
Good day, I ask you to help me figure out the organization of vlan in the office network. What do we have:
The Cisco RV320 Router on which to create the subnets:
- MGMT 10.100.5.0/24 VLAN 5 - DHCP OFF - ports Untagged / Inter VLAN Routing - enable
- LAN 10.100.10.0/24 VLAN 10 - DHCP ON (10.100.10.20 - 254) - Tagged / Inter VLAN Routing port - enable
- VoIP 10.100.20.0/24 VLAN 20 - DHCP ON (10.100.20.10 - 254) - Tagged / Inter VLAN Routing port - enable
- WiFi 10.100.30.0/24 VLAN 30 - DHCP ON (10.100.30.10 - 254) - Tagged / Inter VLAN Routing port - disable
With one cable, I connected port number 1 on the router to port number 48 on the switch
HPE 1820 48G Switch:
Edited the trunk (TRK1) as follows:
Trunk Name: Cisco
Admin mode: enabled
STP Mode: Disabled
Static Mode: Enabled
Load Balance: Source / Destination MAC. VLAN Ethertype incoming port
In members add the port that is connected to the router, the status has changed to Up
In VMware ESX Server (the server is connected to the switch on port 47 and 46):
Created a group of ports with VLAN20
Assigned a group to a virtual machine with a telephony server
I start the server and can not get the IP address from DHCP
I can't figure out how to configure vlan, could you help me? I know English very poorly and use a translator, sorry
03-06-2020 04:43 PM - edited 03-06-2020 04:54 PM
Re: HPE 1820 VLAN help
Hi! So your Cisco RV320 is acting as the IPv4 Router for the VLANs you're planning to create. That's the first assumption. It's OK...but then, remember, that Cisco RV320 needs to manage not only the routing between them (it should perform that automatically once each VLAN will have a SVI assigned to it...but also it needs to manage the access policies to permit/deny traffic between all of them). If this is expected...you're OK with your design.
So...let's see...the first error I see is you defined a Trunk on the HP Switch, that's an error....Trunk in HP Jargon means aggregating more (member) interfaces to form a resilient logical interface...called...Trunk. Cisco designates as a Trunk a port operation mode that permit that port to carry more VLANs concurrently (what HP calls tagging).
Forget about Trunk in HP if you aren't going to aggregate two or more ports together (Static or LACP...).
So, first, destroy the Trunk you created with just the port 48 alone. Then, once you defined the VLANs on the HP 1820 (without IP)...just tag the uplink port to the Cisco RV320 with VLANs 5, 10, 20 and 30...since on the Cisco RV320 the port 1 will have, I presume, 4 logical sub interfaces, one for each VLAN id you have planned to use TAGGED (to be carried along the downlink to the HP Switch).
That's a way. Each Cisco RV320's SVI will become the default gateways of hosts connected to the right ports on the HP 1820 Switch. Here I suppose you will untag some ports on some/all the defined VLANs remembering that a port can be untagged member of just one VLAN and, concurrently, can be tagged member of various VLANS...eventually a port can be orphaned of untagged VLAN membership (HP calls this state as "no untagged") but that very same port needs to be tagged to at least one VLAN.
On the Cisco RV320 (which I haven't direct experience with) you should have the SVIs set on the Interface 1 as Sub-Interfaces, as example this way:
- Sub-Interface 1.5 - Tagged VLAN 5 SVI IP Address: 10.100.5.254 (Net 10.100.5.0/24)
- Sub-Interface 1.10 - Tagged VLAN 10 SVI IP Address: 10.100.10.254 (Net 10.100.10.0/24) -> limit the DHCP Pool range between .10 and .253
- Sub-Interface 1.20 - Tagged VLAN 20 SVI IP Address: 10.100.20.254 (Net 10.100.20.0/24) -> limit the DHCP Pool range between .10 and .253
- Sub-Interface 1.30 - Tagged VLAN 30 SVI IP Address: 10.100.30.254 (Net 10.100.30.0/24) -> limit the DHCP Pool range between .10 and .253
VLAN id 1 will remain untagged and unused on Port 1 expecting no traffic untagged on the downlink/uplink.
Here you should pay attention not to lose Web GUI access to your HP 1820 from the standpoint of the VLAN you will set to manage it.
I'm not an HPE Employee