09-23-2022 05:13 PM - edited 09-23-2022 05:16 PM
Hello community,
I have created a lab in packet tracer for practice and i face an issue.
I have attached a picture that shows the lab i have created.
I have created a SVI called vlan 23 on SW3. The vlan 23 is up/up, but it is unreachable.
I have uploaded a text file with the configurations i have done on SW3.
The rest of the hosts in VLANS can communicate each other, everything is fine.
I dont know what i am missing. Any help is appreciated.
Thanks in advance.
Solved! Go to Solution.
09-24-2022 07:29 PM
John,
Thanks for providing the Packet Tracer Lab file; it definitely helped in troubleshooting. I would have gotten back to you sooner, but as I was looking through the lab...the universe decided I need a break and the power went out.
Anyway, here's a solution to the SVI issue:
Change VLAN 23's IP address to an address on its own subnet.
Example: 192.168.23.1/24
Configure R2 Subinterface G0/1.23 for VLAN 23
S3 SVI (VLAN 23) is now reachable from devices on the 192.168.1.X/26 subnets.
If you want the S3 SVI (VLAN 23) to be reachable from devices on the 10.0.0.X/26 subnets, you need to configure a static route in R1.
Example: 192.168.23.0 255.255.255.0 g0/1
09-23-2022 07:59 PM
is below commands adding successfully in configuration? it have same IP address. also check the subnets of your PCs
interface Vlan1
ip address 192.168.1.3 255.255.255.192
shutdown
!
interface Vlan23
ip address 192.168.1.3 255.255.255.192
09-24-2022 01:06 AM
Hello Kasun,
Thanks for the answer,
I have disabled vlan 1. It is down/down. I have also changed the ip address of vlan 23 to a different one.
It is still not working.
09-24-2022 01:50 AM
John,
Please provide the packet tracer file; What version of packet tracer is it?)
09-24-2022 02:03 AM - edited 09-24-2022 02:05 AM
09-24-2022 07:29 PM
John,
Thanks for providing the Packet Tracer Lab file; it definitely helped in troubleshooting. I would have gotten back to you sooner, but as I was looking through the lab...the universe decided I need a break and the power went out.
Anyway, here's a solution to the SVI issue:
Change VLAN 23's IP address to an address on its own subnet.
Example: 192.168.23.1/24
Configure R2 Subinterface G0/1.23 for VLAN 23
S3 SVI (VLAN 23) is now reachable from devices on the 192.168.1.X/26 subnets.
If you want the S3 SVI (VLAN 23) to be reachable from devices on the 10.0.0.X/26 subnets, you need to configure a static route in R1.
Example: 192.168.23.0 255.255.255.0 g0/1
09-25-2022 02:34 AM
Thanks for the reply.
I will try this out and i will let you know.
09-24-2022 05:20 PM
Hello @John Papas,
When you run the command "show interface vlan 23", which of the following do you see?
1) Vlan23 is up, line protocol is up
or
2) Vlan23 is up, line protocol is down
If you see number 1, then there is a bug in the Packet Tracer software.
If you see number 2, then the software and switch are acting as expected.
You MUST assign a switch port to Vlan 23 AND have an active connection on the port BEFORE the line protocol for the SVI comes up, producing an interface in the Up/Up state.
Once you achieve the Up/Up state, you'll be able to ping the SVI IP address.
fjm / vrs
@[@ittybittypacket]
09-25-2022 02:40 AM
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