02-04-2017 03:03 AM - edited 03-08-2019 09:11 AM
it's amazing how the bare basics get forgotten
Switch--FA 0/22------------------FA 0--Server
Server
ip address 172.16.0.4 /17
default gateway 172.16.0.1
Switch
vlan 172
vlan 172 address 172.16.0.1 /17
int fa 0/22 switchport access vlan 172
The server can only ping 172.16.0.1 if port Fa 0/22 on Switch is in Vlan 172
Does this sound right?
Packet Tracer
Solved! Go to Solution.
02-04-2017 03:13 AM
If I am understanding you correctly, yes, that sounds right. If you create a VLAN 172 interface that is the same network/default gateway as the server, then the server needs to be put in that VLAN.
I know it is Packet Tracer, but by default all switch ports are in VLAN 1, so if you keep the server in the default VLAN and gave the logical VLAN 1 interface the same 172.16.0.1 IP, then you wouldn't have to put the server port into VLAN 172.
Hope that helps
02-04-2017 03:13 AM
If I am understanding you correctly, yes, that sounds right. If you create a VLAN 172 interface that is the same network/default gateway as the server, then the server needs to be put in that VLAN.
I know it is Packet Tracer, but by default all switch ports are in VLAN 1, so if you keep the server in the default VLAN and gave the logical VLAN 1 interface the same 172.16.0.1 IP, then you wouldn't have to put the server port into VLAN 172.
Hope that helps
02-04-2017 04:01 AM
yes agree so without ip routing enabled or a device doing the routing , you can only reach whats in your current broadcast domain in a switch acting as layer 2
you need a l3 enabled device to be able to ping between vlans , the server should be able to reach anything else in vlan 172 though , once as you seen you need to have the access ports in that vlan 2
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