06-23-2022 02:37 AM
Good morning everyone.
I needed your help to understand if it is possible to configure a HWIC interface... so that it has access to a vlan configured on the same router, but on a sub-interface of an L3 interface. I also attach a packet tracer file with the scenario.
I want PC (192.168.99.56) to be able to communicate with others on the same VLAN and, of course, with the router interface 192.168.99.254, which is on the same equipment. I tried to configure via SVI and create the VLANs interfaces but for that I need to have at least one device connected so that the VLAN interface is UP but that doesn't happen.
Thank you.
06-23-2022 01:15 PM - edited 06-23-2022 01:23 PM
Hi,
on router0
interface FastEthernet0/1/0
switchport access vlan 99
switchport mode access
no shut
!
interface FastEthernet0/1/3
switchport access vlan 99
switchport mode access
no shut
!
PC-PT
C:\>ping 192.168.99.23
Pinging 192.168.99.23 with 32 bytes of data:
Reply from 192.168.99.23: bytes=32 time=1ms TTL=128
Reply from 192.168.99.23: bytes=32 time=1ms TTL=128
Reply from 192.168.99.23: bytes=32 time<1ms TTL=128
06-24-2022 02:19 AM - edited 06-24-2022 02:26 AM
Good Morning and thank you.
Yes, that way it works but I didn't want a second connection between the router and the switch, that brings a L2 loop.
It's possible withou second connection?
06-24-2022 03:30 AM - edited 06-24-2022 03:33 AM
Thanks for your feedback, can you expand a little and explain how did you come to the conclusion that there is L2 loop?
Switch# show span vlan 99
VLAN0099
Spanning tree enabled protocol ieee
Root ID Priority 32867
Address 0001.6408.B226
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32867 (priority 32768 sys-id-ext 99)
Address 0001.6408.B226
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 20
Interface Role Sts Cost Prio.Nbr Type
---------------- ---- --- --------- -------- ----------------------
Fa0/1 Desg FWD 19 128.1 P2p
Fa0/24 Desg FWD 19 128.24 P2p
06-24-2022 06:30 AM
Hi.
Sorry, because i add a second link between router and switch and keep the router f0/0.99 connected to switch
From the picture I can see that you assigned the IP to VLAN99 and stopped using the L3 interface, why?
I have to test but I think I really have to use the L3 interface in trunk because, in the real scenario, this vlan is also used in a VM, whose interface is trunked.
06-24-2022 06:45 AM
@rjcm wrote:From the picture I can see that you assigned the IP to VLAN99 and stopped using the L3 interface, why?
why not?
in the real scenario, this vlan is also used in a VM,.
In your topology PC-PT supposed to simulate a VM?
06-24-2022 07:26 AM
Yes, PC-PT (192.168.99.23) will be a VM.
06-24-2022 07:54 AM - edited 06-24-2022 08:01 AM
Excellent,
In terms of topology this should look something like this:
https://tamlx.wordpress.com/2015/07/20/vmware-bai-11-cau-hinh-vlan-vsphere-5-5/
And in packet tracker should look something like this:
Of course there are a number of ways to implement this solution, for example you can move the layer 3 (.254/24 - default gateway of the vm) to the layer 3 switch (3560-24ps) for example.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide