cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3454
Views
20
Helpful
21
Replies

Routing for VLANs

htshurup21
Level 1
Level 1

Hello everybody.

In my HomeLab I have 2960G-48 switch  with VLANs 10,32,64,90 for vMotion,100 - for esxi hosts.

Switch connection comes from 1921 router from gig0/0 to gig0/44 on switch.

Default network is 192.168.0.0 255.255.255.0

On router gig0/0 has IP 192.168.0.1 255.255.255.0

IPs on VLANs:

10 -192.168.10.0

32- 192.168.32.0

64- 192.168.64.0

90- 192.168.90.0

100- 10.100.100.0

IPs have been assigned to sub interfaces on router with numbers of the VLANs (ie   gig0/0.10 , gig0/0.32....etc)

When Im setting up on router    ip route 192.168.10.0 255.255.255.0 192.168.0.0   Im still not able to get to the hosts on that subnet.

Trunk has been setup on switch on port gig0/44 as it connects with gig0/0 on router.

Native for trunk is 80 and is being setup on port gig 0/44 on switch.

interface GigabitEthernet0/1
switchport access vlan 100
switchport mode access

Same settings are on other interfaces on switch.

From switch I can ping gig0.0.10 or  sub interface gig 0/0.10 on router, but cannot ping any other sub interface.

Could you please tell me what am I doing wrong?

Sorry for my broken english.

Regards,

Vitalii

21 Replies 21

Julio E. Moisa
VIP Alumni
VIP Alumni

Hi

You dont need static routing if you are implementing intervlan routing in this case router in a stick scenario. 

Could you please provide the configuration of the router and switch?

Thank you in advance. 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

You should have the following config:

Router --- trunk ----Switch

10 -192.168.10.0

32- 192.168.32.0

64- 192.168.64.0

90- 192.168.90.0

100- 10.100.100.0

ROUTER

int g0/0
no shutdown

int g0/0.10
encapsulation dot1q 10
ip add 192.168.10.1 255.255.255.0

int g0/0.32
encapsulation dot1q 32
ip add 192.168.32.1 255.255.255.0

> Similar for the rest of the sub interfaces <

inter g0/0.80 
encapsulation dot1q 80 native

SWITCH

create vlans

vlans, 10,32,64,80....

interface g0/44
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk native vlan 80
no shut

Hope it is useful

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Thanks for heads up.

Did add this string to a router and lost remote connection to my homeLAB.

inter g0/0.80 
encapsulation dot1q 80 native

Now the VPN to a server in the 192.168.0.0 network doesnt work. =( 

Still able to operate remotely with router.

Hi,

Please see my last post, I see the main problem is the configuration under the g0/0 interface.

Your topology is:

Router  --- Sub-interfaces --- trunk ---- Switch

is that correct?

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Also some subnets are not the same like in your first comment. 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Those are the main subnets that I want to understand how to mess with.

Hi

In this kind of scenario (router in a stick) the IP addresses are configured under the sub interfaces only, these frames are sent as tagged between the switch and router except the frame related to the native vlan, so you could configure the network of you home under other sub-interfaces like you did with the other subnets. 

The following link could be useful:

https://learningnetwork.cisco.com/thread/30977




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

This link could be useful:

http://www.firewall.cx/cisco-technical-knowledgebase/cisco-routers/336-cisco-router-8021q-router-stick.html




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Most likely Im ending up at this point with wiping of the router and switch and starting over as I cannot understand what is not working =)

Hi

Remember get a backup before to reset the devices. Once you have the factory settings, you could follow these steps:

- Configure Vlans on the switch
- Configure Trunk interface to be used with the router
- Create the subinterfaces on the router
- Test connectivity between vlans. 
- Create the default route pointing to your ISP on the router
- Create the NAT settings (ACL, nat under interfaces, PAT)
- Test connectivity.

If you need any assistance we can be in touch through this discuss.

Have a good day.

:-)




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Thanks for assistance. Appreciate it. Have a good day as well.

Speaking about backups. I wasn't even able to do it before setting up sub interfaces and setting up other stuff like VPN and port forwarding.

Did create a VM with TFTP but never managed in the last couple weeks to have a backup of router or switch as Router wasn't able to ping anything above 192.168.10.

All IPs before 192.168.0.10 were busy....

Thats why I decide to create sub interfaces and setup VLANs so I could separate esxi hosts for more play with them.

Regards,

Vitalii

No worries my friend, it is easy if you are using putty terminal software, please see the attachment, once you have selected the location to save the config, you can execute a show run and all this information showed in your screen will be saved on the text file. To go to change settings (pic1) clic on the top and right clic. 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Good morning. 

Before resetting to default my router and switch I tried to make it work and nothing helped except returning the IP address on gig 0/0. Only after this it went through. Of course  subnets are still not pingable and nothing is working as the main question stated in first message. Before wiping it will play more.

Here are the current configs, could you please check and maybe now the issue will be more visible..

Regards,

Vitalii

Hi my friend,

Sure, please let me see the files and keep you posted.

Regards. 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<