How to setup L3 routing between VLANs on a 1920S switch

[Koine]

Good afternoon.
Trying to have L3 routing between 2 VLANs on a HPE OfficeConnect Switch, 1920S 48G 4SFP, JL382A
Software Version PD.01.05, Operating System Linux 3.6.5

IP 192.168.228.93/25 assigned to the switch, managed via web browser.
The first VLAN (VLAN_1) is the default VLAN. NO static IP was set . In effect, i tried to assign a static IP as 192.168.228.93/25 to VLAN_1, but an error arise (IP/Subnet conflict ??) ...

The second VLAN (VLAN_243) is a separate VLAN. Static IP 10.220.243.190/27 assigned. 6 ports assigned (UNTAGGED) to this VLAN 
In Routing IP Interface Summary I can see some routes ...
Routing Mode is also enabled in Global Routing IP Configuration 

BUT ...

All VLANS do work as they were TWO separate switches: 
All the PC on VLAN_243 can see each other, they can ping their gateway (10.220.243.190), but they don't reach nor the 192.168.228.93 IP (switch IP on the VLAN_1), nor the rest of the network (the Internet gateway is on the VLAN_1 ...)
All the PC on VLAN_1 can see each other, they can ping their gateway (192.168.228.95) and also the 192.168.228.93 IP (the switch IP on the VLAN_1), but they don't reach nor the 10.220.243.190 IP (switch IP on the VLAN_243), nor the rest of the 10.220.243.190/27 network

The L3 routing between the 2 VLANs is not working, perhaps is not defined (my fault, I don't know how to perform that ... and didn't understand it from the user manual)
Certainly SOMETHING is missing ... but what??

Thank you for your help

Antonio

[Ihaqueit]

As per your query.

The L3 routing between the 2 VLANs is not working?

Is this two vlan you assigned on how many switches?

The L3 routing between two vlans or between two switches VLAN?

If you have only one switch why you want to create vlans, normally assigned the ports to user and unusable port block.

If this switch for Server and end user, Everything you handle thru group policy and join every end user pc to domain.

[akg7]

Hello @Koine ,

If you got conflict error for 192.168.228.93/25 then the same subnet might be configured on same network

Regarding the intervaln routing issue:

1. For testing, can you try to give default gateway of VLAN 1 to PC connected on VLAN243 and vice versa?

2. If above step doesn't work then can you confirm what is the default gateway configured in the device?

Check it from Routing --> Configuration-->Gobal

If default gateway is configured then give same default gateway to PC's.

Also share the two interface connecting to PC and VLAN 1 & VLAN 243 interface configuration from

Routing-->Configuration-->VLAN/Interface Configuration and select vlan then interface?

Thanks!

[Koine]

Hi I Haq

Only ONE switch is involved.
The first VLAN is the default one, and the switch has the 192.168.228.93/23 IP, though NOT on the Routing IP Interface Configuration of the default VLAN_1 ... BUT in the Setup Network - Get Connected - Network Details 
We setup another ONE separate VLAN (VLAN_243 let's say 6 UNTAGGED ports) for the 10.220.243.190/27 subnet.

We would want : 1) PCs on both VLANs could communicate between themselves, each having the Switch IP as their gateway on their specific subnet AND 2) all traffic flowing from the 10.220.243.190/27 subnet and directed to "other" subnets (0.0.0.0 mask 0.0.0.0 ... that is other company sites AND Internet) could go to the overall (site) Gateway, that's 192.168.228.95 and is configured in the Setup Network - Get Connected - Network Details)

We want 2 separate VLANS to have another (different) site subnet (the 10.220.243.190/27 network), and a Next Hop (the 192.168.228.93 IP) on the "public" side (the 192.168.228.93/23 LAN) to declare on the Gateway (192.168.228.95) for the internal routing for the 10.220.243.190/27 network.
We usually did it (and it works in other sites!) using AUX interfaces on the site firewall, or using a Router , or even using one 4000-5000 series HP switch (where we did it with just TWO lines from the console command-line TELNET management interface ... create the VLAN, assign the VLAN an IP address and a mask, run the IP ROUTE command, set the overall gateway ... voilà) ..
This time we would achieve using only the 1920 switch, no command line (telnet access) available, only web interface ... this is getting ourselves lost ...

A

[Koine]

Hi akg7
I can't setup the default Gateway in the Routing --> Configuration-->Gobal. If I try, I get an error (Unable to set the 'Global Default gateway' value in the device due to a subnet conflict with the network port). The 192.168.228.95 gateway is defined in the Setup Network - Get Connected - Network Details

I'll try to summarize: Only ONE switch is involved.
The first VLAN is the default one, and the switch has the 192.168.228.93/23 IP, though NOT on the Routing IP Interface Configuration of the default VLAN_1 ... BUT in the Setup Network - Get Connected - Network Details 
We setup another ONE separate VLAN (VLAN_243 let's say 6 UNTAGGED ports) for the 10.220.243.190/27 subnet.

We would want : 1) PCs on both VLANs could communicate between themselves, each having the Switch IP as their gateway on their specific subnet AND 2) all traffic flowing from the 10.220.243.190/27 subnet and directed to "other" subnets (0.0.0.0 mask 0.0.0.0 ... that is other company sites AND Internet) could go to the overall (site) Gateway, that's 192.168.228.95 and is configured in the Setup Network - Get Connected - Network Details)

We want 2 separate VLANS to have another (different) site subnet (the 10.220.243.190/27 network), and a Next Hop (the 192.168.228.93 IP) on the "public" side (the 192.168.228.93/23 LAN) to declare on the Gateway (192.168.228.95) for the internal routing for the 10.220.243.190/27 network.
We usually did it (and it works in other sites!) using AUX interfaces on the site firewall, or using a Router , or even using one 4000-5000 series HP switch (where we did it with just TWO lines from the console command-line TELNET management interface ... create the VLAN, assign the VLAN an IP address and a mask, run the IP ROUTE command [ip route 0.0.0.0 0.0.0.0 <overall gateway>], set the overall gateway [ip default-gateway <overall gateway>] ... that's it) ..

This time we would achieve using only the 1920 switch, no command line (telnet access) available, only web interface ... this is getting ourselves lost ...

[Koine]

... still unable to upload images ... sorry ...

[Ihaqueit]

You may need to use a separate ethernet port for each interface, or you may be able to use one ethernet port that will let you pass both VLAN's on the same cable. The latter is usually called 'router on a stick'. 

You'll then need to set up a route in the Layer3 switch from interface 1 to interface 2, and from interface 2 to interface 1.

Can you send the configuration file in textformat?

[Koine]

Hi

Sorry ... i keep trying to post a reply, but after pressing the POST button, I can't see the post in the web portal ... ??
WIll try to separate the answer text from the configuration file lines ...

You may need to use a separate ethernet port for each interface,

We currently assigned 6 ports to the VLAN_243 ... all other ports are on the default VLAN ... all of them UNTAGGED. Can'y understand the meaning of "use a separate ethernet port for each interface"

or you may be able to use one ethernet port that will let you pass both VLAN's on the same cable. The latter is usually called 'router on a stick'. 

We could assign a single port to BOTH VLANS, in TAGGED mode. Is this enough to have the L3 routing working between the VLANs, and the data traffic flow between them, even if no Network Cable is connected to this "bridge" port?

You'll then need to set up a route in the Layer3 switch from interface 1 to interface 2, and from interface 2 to interface 1.

Logically clear, but can't undestand how to do it from the web interface.

Can you send the configuration file in textformat?

Sure, it follows in the next post. Actual configuration regards VLAN_243 including ports 2,4,6,8,10,12 , all UNTAGGED, and the other ports on the default VLAN

Thanks

Antonio

[Ihaqueit]

(303) How to configure VLAN on HPE switch | NETVN - YouTube

[Ihaqueit]

Its based on JL262A switch.

[Ivan_B]

@Ihaqueit 1920s doesn't have CLI. Your example is for 2930F switch which runs totally different OS. Irrelevant and misleading

[Ihaqueit]

Thanks for confirmation Ivan,

Then please provide the solution regarding L3 routing.

[Ivan_B]

Dear @Ihaqueit ,

Thank you for your kind suggestion and invitation, however my colleague @akg7 is doing great job on this post, I don't have anything to add at this point. 

[akg7]

Hello @Koine ,

Apologies for delayed response.

Can you please share a network topolgy diagram, hand drawn is also fine?

Want to see uplink and down line connectivity.

Thanks!

[Koine]

00 - Network Diagram.01 - Routing-Configuration-Global02 - Setup Network - Get Connected03 - Error Setting Global Default Gateway04 -VLAN Configuration05a - Routing - Configuration - VLAN_105b - Routing - Configuration - VLAN_24305c - Routing - Configuration - Interface_2 [in VLAN_243]05d - Routing - Configuration - Interface_9 [in VLAN_1]06 - Routing - Configuration - Status - IP Interface Summary

[Koine]

Hello akg7

Today I found ourselves ENABLED to upload images ... I will try to explain, referring to the pictures just posted (they show the current Switch configuration, as required.)

The first image is a simple network diagram. The LEFT part is the original site network (192.168.228.0/23), with the 1920S switch (192.168.228.93, IP used for management purpose) and the overall gateway (192.168.228.95). Other 1920 switches are not depicted (not relevant here).
In the RIGHT part there is the "new" site network (10.220.243.160/27): we build a VLAN_243 with (currently) 6 UNTAGGED ports on the same 1920S , this VLAN has a 10.220.243.190 IP, also used as PC Gateway for the 10.220.243.160/27 PCs

As explained, both VLANS do work as they were TWO separate switches:  all the PC on VLAN_243 can see each other, they can ping their gateway (10.220.243.190), but they don't reach nor the 192.168.228.93 IP (switch IP on the VLAN_1), nor the rest of the network (the Internet gateway 192.168.228.95)
All the PC on VLAN_1 can see each other, they can ping their gateway (192.168.228.95) and also the 192.168.228.93 IP (the switch management IP on the VLAN_1), but they don't reach nor the 10.220.243.190 IP (switch IP on the VLAN_243), nor the rest of the 10.220.243.190/27 network

Thank you for your help

[akg7]

Hello @Koine ,

So there are two 1920s switches?How both devices connected? IP address between them?

Thanks!

[Koine]

Hi akg7
Sorry, perhaps I'm not so good in drawing
Only ONE switch involved. In the diagram I depicted the "separate" (logical) 2 VLANs, created after the VLAN_243 definition
One switch, 6 UNTAGGED ports (currently 2,4,6,8,10,12) for the VLAN_243, all other ports UNTAGGED in the default (original) VLAN (VLAN_1)
With the dotted lines I wanted to JOIN the 2 logical parts ...

Hope it's more clear now

A

[akg7]

Hello @Koine ,

Thank You for the information.

And is there L3 switch connected as uplink to this switch?

Thanks!

[akg7]

Hello @Koine ,

Enabling global routing is enough for same switch intervlan routing.

Are these switches are acting as  layer 2 or layer 3?

Thanks!

[Koine]

Hi

No other L3 switch connected as uplink to this switch.

We would perform L3 routing between the two VLANs of this same switch, as we do with "bigger" 4000-5000 series HP Switches in other sites (separate VLAN, IP routing enabled etc)

A

[Koine]

Hi

Enabling global routing is enough for same switch intervlan routing.

Same switch InterVLAN routing is what we wanted, but some missing configuration, or wrong parameter, prevents it from working as needed

Are these switches are acting as  layer 2 or layer 3?

Before the modification (with the default VLAN_1 only), all the site switches (they are FOUR identical 48 ports 1920S switches) were acting only as L2 switch, all of them for the 192.168.228.0/23 subnet. Each one of them had a different 192.168.228.9n  IP  (n=1,2,3,4) and the same 192.168.228.95 Overall Gateway configured, just for management purposes.

With just ONE 1920S (192.168.228.93) we would like to add the VLAN_243 for the 10.220.243.160/27 subnet, and the L3 routing capabilities only on this single switch, if possible

[akg7]

Hello @Koine ,

Regarding the issue:

The first VLAN (VLAN_1) is the default VLAN. NO static IP was set . In effect, i tried to assign a static IP as 192.168.228.93/25 to VLAN_1, but an error arise (IP/Subnet conflict ??) .--No need to assign IP address into VLAN 1 because this IP address is already assigned to switch and by default management is part of VLAN 1.

I have tested in LAB and enabling global routing is enough for Layer 3 intervlan communication.

Routing-->Configuration-->Global  -->I believe you have already enabled.

Have you tried to ping from one of the host in VLAN 243 to host in VLAN 1 instead of gateways?

Similar for host in VLAN 1 ti host in VLAN 243.

Thanks!

[Koine]

Regarding the issue:
The first VLAN (VLAN_1) is the default VLAN. NO static IP was set . In effect, i tried to assign a static IP as 192.168.228.93/25 to VLAN_1, but an error arise (IP/Subnet conflict ??) .
--No need to assign IP address into VLAN 1 because this IP address is already assigned to switch and by default management is part of VLAN 1.

OK ... explanation clear. As from the beginning, our VLAN_1 has IP Address Configuration Method to "None", while VLAN_243 has IP Address Configuration Method to "Manual" and IP Address and Mask set as shown in the images

I have tested in LAB and enabling global routing is enough for Layer 3 intervlan communication.
Routing-->Configuration-->Global  -->I believe you have already enabled.

YES: Routing-->Configuration-->Global -> Routing Mode is ENABLED
But We can't set any value in Routing-->Configuration-->Global -> Global Default Gateway (perhaps it's not needed ... the device will use the value in Setup Network -> Get Connected -> Gateway Address ... is it correct?)
Also, both VLANS have Routing Mode "Enabled" in VLAN -> Configuration -> VLAN/INterface Configuration -> Routing IP Interface Configuration

 Have you tried to ping from one of the host in VLAN 243 to host in VLAN 1 instead of gateways?

Yes, no result / no answer. The VLAN_243 PCs have the switch IP (10.220.243.190) as their Gateway. Two PCs on the same VLAN_243 can ping each other, and they can ping their gateway

Similar for host in VLAN 1 ti host in VLAN 243.

Similar: no result / no answer. The Default VLAN PCs have the same gateway as the switch gateway (192.168.228.95). Two PCs on the same default VLAN can ping each other, and they can ping their gateway

I'll be away for a week.
Some of our staff is preparing another 1920S in our lab, to test a configuration from scratch in a "non-production" environment ...
They will also watch the video wich you sent us the link of, perhaps that will help ...
If you could provide us a configuration file (from your LAB switch, that is working if I understand well ... ) just to load it in our device, even if with different subnets, ... it would be great ... Could you??
Otherwise, we will come back to the issue in early September

Thank you

Antonio