cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
832
Views
5
Helpful
8
Replies

Cannot Ping SVI from hosts in vlans

John Papas
Level 1
Level 1

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.

 

 

 

1 Accepted Solution

Accepted Solutions

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

View solution in original post

8 Replies 8

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
Please rate this and mark as solution/answer, if this resolved your issue
Good luck
KB

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.

John,

Please provide the packet tracer file; What version of packet tracer is it?)

Here it is.  The packet tracer version is 8.1.1.0022

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

Thanks for the reply.

I will try this out and i will let you know.

 

 

fracjackmac
Level 1
Level 1

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]

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: