6

Introduction

The steps described in this manual have been applied in order to enable the connection between multiple VLANs which reside on the same switch.

Two VLANs have been configured.

VLAN 1:

ip address 10.1.2.1 255.255.255.0

VLAN 2:

ip address 10.1.3.1 255.255.255.0

Ports:

interface GigabitEthernet0/1
 switchport access vlan 1
!
interface GigabitEthernet0/2
 switchport access vlan 1
!
interface GigabitEthernet0/3
 switchport access vlan 2
!

Network Adapter System 1:

10.30.50.71/24

Network Adapter System 2:

10.30.50.72/24

Both systems are able to access each other if the ethernet cables are connected to ports which reside to VLAN 1.

If one of the ethernet cables has been moved to a port which belongs to VLAN 2, the systems are not able to access each other any more.

Will interVLAN solve this issue? What kind of commands are available to facilitate troubleshooting this issue?

Question

How to connect Multiple VLANs which reside on the same L3 Switch?

6
  • What port are you using as your L3 port? Can we get a dump of the configs for the switch? Specifically the port configs and confirmation that the "ip routing" command has been entered? – HAL Jun 16 '14 at 14:22
  • 2
    Did you configure default gateways on your systems? They should match the address of the Vlan interface(s) – Ron Trunk Jun 16 '14 at 14:27
  • @HAL the ports running-config snippet has been added to the question – 030 Jun 16 '14 at 14:37
  • @HAL sh run confirms that ip routing command has been entered – 030 Jun 16 '14 at 14:51
  • @Ron while ip route 0.0.0.0 0.0.0.0 200.1.1.2 has been executed, sh ip route indicates that Gateway of last resort is not set – 030 Jun 16 '14 at 14:59
4

The default gateway on your systems is incorrect. The systems on VLAN 1 must have their default gateway set to 10.1.2.1, the address of the VLAN 1 interface.

Likewise, the systems on VLAN 2 should have their default gateway set to 10.1.3.1, the interface for VLAN 2

There is nothing you need to change on the switch.

4
  • The default gateways were changed as described in the answer. However, a system connected to VLAN1 was not able to ping a system connected to VLAN2, while systems connected to VLAN1 are able to access each other. This is applicable to systems connected to VLAN2 as well. The solution of specifying default gateway is not working at the moment probably due to incorrect static IPs. IP system1: 10.30.50.71, IP system2: 10.30.50.72. – 030 Jun 16 '14 at 16:12
  • 1
    Yes, your system IP addresses MUST be in the same subnet as your VLAN. – Ron Trunk Jun 16 '14 at 16:26
  • I will test this tomorrow and let you know the outcome – 030 Jun 16 '14 at 16:50
  • The IP addresses have been changed and reside in the same subnet as the VLAN. The systems can access each other now. Thank you. – 030 Jun 17 '14 at 8:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.