HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

intervlan routing, share WAN route for all VLANs

 
Convergo
Advisor

intervlan routing, share WAN route for all VLANs

Hi,

we have configured a 5900 IRF stack with several VLANS. Per VLAN we have configured a VLAN interface that will be used as gateway for the specific VLAN.

Workstations in VLAN 10 (10.0.10.0/24) use VLAN interface 10.0.10.1 as the default gateway
Servers in VLAN 20 (10.0.20.0/24) use VLAN interface 10.0.20.1 as the default gateway

For internet purposes we have placed the internet gateway in VLAN 1000 (192.168.100.0/24) where the VLAN interface 192.168.100.1) will be the default gateway.

Within the irf stack we add a static route 0.0.0.0 0.0.0.0 192.168.100.254 (that is the next hop to internet)

On the IRF stack we can ping to the internet (8.8.8.8).

When configuring a workstation in VLAN 10 we are able to ping servers in VLAN20 and we are able to ping the gateway in VLAN 1000. However it is impossible to connect to the internet (8.8.8.8)

When configuring a workstation in VLAN1000 we are able to ping servers in VLAN20 and we are able to ping the gateway in VLAN 1000. In this configuration it is possible to connect to the internet (8.8.8.8)

I assumed that being a layer 3 switch it would be possble to route to the internetgateway for all available VLANs configured with a VLAN interface address. However it seems to be that we need to configure an additional interface on the internet gateway, however this would not be preferrable I think.

Has anyone managed to configure layer 3 routing as described ?

thanks !

 

1 REPLY
Vince-Whirlwind
Honored Contributor

Re: intervlan routing, share WAN route for all VLANs

Looks like you have it all configured properly.

The device with the 192.168.100.254 IP address has no routes for the 10.0.10.0 and 10.0.20.0 subnets, so it's not returning any packets to hosts in those subnets.