In the last how to, we performed the firmware upgrade and initial configuration on the HP v1910 24G.
It’s now time to start placing some VLAN’s onto our switch. A good starting point is why do we use VLAN’s?
Well a VLAN enables us to:
- Logically segment a switch into smaller switches, much same way that ESXi allows you to run multiple virtual machines on the same physical hardware.
- Create logical boundaries so that traffic from one VLAN to another VLAN is permitted or not permitted e.g. User VLAN accessing Server VLAN.
- Reduce the broadcast domains, in the same way that a switch creates a separate collision domain for each device plugged into it. A VLAN reduces the ARP broadcasts sent out.
Before we move any further, we need to understand what purpose the VLAN’s will serve in our environment and what they will be assigned too. For me, it’s quite straight forward, the HP v1910 will be used as my main home lab switch and as such I need a VLAN for the following purposes:
- HP Fail Over Manager
With this in mind, I would highly recommend creating a network table containing your VLAN Names, VLAN ID, Subnet and Switch IP Address. You may ask why do you bother? Well I deal with large number of clients infrastructure and I often find that I get confused as what subnet’s are doing what!
You will notice that I have assigned an IP address to the switch on every VLAN. The reason for this is the HP v1910 can also do layer 3 static routing so in my home environment the switch is the default gateway as well.
Layer 3 Static Routes
OK, lets login to the HP v1910 24G using the IP address and username/password we assigned previously.
Why use layer 3 static routes? Well I want to be able to route between VLAN’s. This is critical for my HP Failover Manager (FOM VLAN) which needs to be in a logical third site to communicate with the HP Virtual Storage Appliance (iSCSI VLAN). For each device on each VLAN they will use the switch as there default gateway. This means that the network traffic will only leave the switch if it has a destination subnet for which it is not responsible e.g. the internet.
To do this, click on Network from the left hand panel then IPv4 Routing
Click Create in the Destination IP Address enter 0.0.0.0 Mask enter 0.0.0.0 Next Hop enter 192.168.37.254 Select Preference and enter 10
So what are we actually doing? Well we are saying to the switch for ‘any destination IP address’ and ‘any subnet’ send all that traffic to this router/firewall whose IP address is 192.168.37.254 (next hop).
Hopefully it should look something like this.
Cool, let’s test it. Change a computer to use the HP v1910 24G switch as it’s default gateway.
We should now be able to ping the switch, the switches next hop and also something out on the internet.
Boom, it’s all working, let’s move on!
Hopefully, you have already decided on your VLAN configuration and IP address’s for the switch. So let’s crack on and start configuring.
Select Network from the left hand menu then VLAN and then Create
My first VLAN ID is 10, so we enter this and click Create to the left hand side. Next Modify the VLAN description from VLAN 0010 to iSCSI and then click Apply.
Rinse and repeat until you have entered all of your VLAN’s into the switch. Here’s one I made earlier.
TOP TIP, don’t forget to click Save in the top right hand corner on a regular basis.
Great, we have created the VLAN’s now we need to assign them to some switch ports. We need to understand what happens when we change the port characteristics. The options we have are:
- Untagged – what ever device we plug into this switch port will automatically be placed into this VLAN. Commonly used for devices which are not VLAN aware (most desktops/laptops).
- Tagged – if a device is VLAN aware and it has been assigned to a VLAN, when it is plugged into the switch port it won’t go into the Untagged VLAN, it will go into the Tagged VLAN (think IP phones)
As this switch is for my vSphere 5 environment and vSphere is VLAN aware. We are going to set every port to be Tagged into every VLAN. What will this achieve? Well every device which is not VLAN away will go straight into the Management VLAN. Then on the port group’s within the vSwitches I can assign VLAN’s.
To do this, click Network from the left hand menu, then VLAN and finally Modify Port
By default every port will be ‘untagged’ in VLAN 1 so we don’t need to make any modifications to this. Click Select All then Tagged and last of all Enter the VLAN ID’s in this case 10,20,30,40 and click Apply.
You will receive a pop up letting you know that Access Ports will change to Hybrid Ports, we are cool with this, so Click OK.
To verify the VLAN’s have been set correctly, go to Port Detail and choose Select All, it should show the following.
Assign An IP Address To Each VLAN
I mentioned earlier on in the post that we wanted to assign an IP address to each VLAN so that the HP v1910 24G becomes the default gateway for all devices. To do this select Network from the left hand menu, then VLAN interface and Create.
Now this is when I need to refer back to my network table! We input the VLAN ID e.g. 10 and then enter the IP Address e.g. 10.37.10.221 and Mask e.g. 255.255.255.0
I always deselect ‘Configure IPv6 Link Local Address’ then click Apply.
Rinse and repeat for the rest of your VLAN’s. To make sure everything is ‘tickety boo’ click on Summary and you should be greeted with a page similar to this.
Time to test. So from your computer you should now be able to ping each VLAN IP address on the switch.
Success, that’s our HP v1910 24G configured with VLAN’s.
128 thoughts on “How To Configure Layer 3 Static Routes & VLAN’s On HP v1910 24G”
I create vla 10,20 and 30 0n the layer 3 switch
and assigned ip addresses and ports
i have signed port 11 as hybrid to access all vlans using CLI
To test my configuration:
i can ping all the vlan using command line in the switch ( hyperterminal)
but I can’t access my pc’s when using web interface.
i need to do routing but don’t know how? please help me
Click on the IPv4 Routing. Then enter the network, subnet mask and switch IP addresses. Example 10.37.10.0 (network), 255.255.255.0 (mask), 10.37.10.221 (gateway). Any traffic bound for the 10.37.10.0 network wil be forwarded/transmitted through the 10.37.10.221 interface/IP address. Need to setup the other networks such as 10.37.20.0, 255.255.255.0, 10.37.20.221 so they can talk back and forth. Also setup the default gateway to be the switch Ip address x.x.x.221
I have created my VLAN’s and am able to ping each one. I want to have my Vsphere lab separate and would like to be able to have VLAN 10 get access to the internet. How do I create a static route for VLAN 10 to access the internet? The switch IP is 192 168.1.70, VLAN 10 is 172.16.10.70 (ESXI host and vCenter server) My home router gateway is 192.168.1.1 My switch is the HPE 1920s 24G POE+ current on firmware.
I created VLAN’s 1, 2 and 10. I need traffic to 3 devices with VLAN 1 IP addresses to route through my firewall for redirection to a branch office. This redirection works fine for any address not on VLAN1. On the switch, I removed the IP address for VLAN 1 and setup the 0.0.0.0 default to route through the VLAN 2 interface. I also defined these 3 IP addresses with static routes through the VLAN 2 interface. From the switch diagnostic tools, the ping and trace route traffic the way I want. However, if I plug into a port untagged on VLAN 1 and set my ip address to be in the VLAN 1 subnet, I can ping any vlan 1 IP that are inside my network, but the 3 I need to route through my firewall come back as unreachable. What can I do to force the traffic to route through my firewall as a gateway?
me podra ayuar como repartir la banda ancha