07-08-2023
03:38 AM
- last edited on
07-12-2023
11:23 PM
by
Translator
Hello users,
I have some problems regarding PC / Laptop & Server pinging problem after VLAN configuration & inter-VLAN routing.The detailed problems are
- The laptops can reach the switches, routers and the server but they can't reach the laptops from other building (same VLAN laptops)
- The server can reach the switches and routers but it can't reach any laptop
Did I miss any configuration? I did included my related files right here with the
.pkt file
and its questions and my addressing table in .pdf (it can be wrong since it is my own answer).
Thanks in advance!
Solved! Go to Solution.
07-09-2023
12:48 AM
- last edited on
07-12-2023
11:41 PM
by
Translator
Hello @syazwanmarzuki,
there is a misunderstood.
Your server has got
IP 192.18.10.1/24
and its Gateway is itself....... I don't understand the role of R-DSEC Router regarding its configuration.
You don't have anymore L3 equipement on your topology...then no more SVI acted as Gateway for each VLAN.
Then for what you expected is OK ; only PC on the same department can ping each other since they are in the same VLAN no need og Gateway!
But Server in VLAN 10 is only pingable frome other VLAN 10 ressources.....
Also adjust config on S-DSEC Switch if you want VLAN 10 ping Server MAIN-01:
07-09-2023 05:42 AM - edited 07-09-2023 05:43 AM
Adujst neflow configuration on R-SDEC:
You will have sample on netflow configurator on SERVER-MAIN-01:
Follow this for netflow config.:https://www.packettracernetwork.com/tutorials/packet-tracer-netflow.html
07-08-2023
06:55 AM
- last edited on
07-12-2023
11:26 PM
by
Translator
Hello @syazwanmarzuki,
First, configure IP add ont the sub Int ; for example on Router R-BLOK-0:
Ping between laptops from engineerig to Administration should be OK (left side)
Other things, you can not have same IP ADD
(i.e. 192.168.10.0/24 - vlan 10)
on different routing segment. It should not work, you'll need to stretch vlan 10 (L2VPN).
You can have same vlan ID because it is a local ID, but on your context you should do subnetting -- subnetting the IP ADD for Engineering subnet and administration subnet. For example:
R-BLOK-0: vlan 10 - Engineering 192.168.10.0/25 and administration 192.168.20.0/25
R-BLOC-N: vlan 10- Engineering 192.168.10.128/25 and administration 192.168.20.128/25 (keep same for vlan 30 and 40).
On R-BLOK-0 side no need to have sub int for vlan 30-40! Same idea on R-BLOK-N side.
Proposition:
-No need multiple links between L2 switches
-Subnetting (Engineering/administration)
-R-BLOK-0 advertise (redistribute) 192.168.10.0/25 and 192.168.20.0/25
-R-BLOK-N advertise (redistribute) 192.168.10.128/25 - 192.168.20.128/25 - 192.168.30.0/24 and 192.168.40.0/24
07-08-2023
08:08 AM
- last edited on
07-12-2023
11:28 PM
by
Translator
Hello M02@rt37 ,
I'd done configure as you asked on both Router R-BLOK-O and Router R-BLOK-N. I'd keep sub int for VLAN 30-40 for R-BLOK-0 for future implementation of the other two departments. Take note that I want to ping device in same department only (example: Left-side PC Engineering can ping right-side PC Engineering and vice versa).
Result:
- The laptops can ping/reach the switches, routers and the server but they can't reach the laptops from other building (same VLAN laptops)
- All Engineering and Administration devices can ping the server but the other two departments can't ping the server
- The server (source) can ping/reaches the switches and routers but it can't reach any laptop (destination)
Hello @Martin L ,
these are my remaining objectives while other objectives were completed.
Remaining Objective:
- LAPTOP-O-01 and LAPTOP-O-02 can ping LAPTOP-N-05 and LAPTOP-N-06 only (all under VLAN 10)
- LAPTOP-O-03 and LAPTOP-O-04 can ping LAPTOP-N-07 and LAPTOP-N-08 only (all under VLAN 20)
- LAPTOP-N-01 and LAPTOP-N-02 (VLAN 30 Account), LAPTOP-N-03 and LAPTOP-N-04 (VLAN 40 Sales & Marketing) can ping the server SERVER-MAIN-01
- The server SERVER-MAIN-01 can ping all laptops (end devices)
I did attached the updated file with these inter-VLAN configurations here.
Thanks in advance, again
07-08-2023
08:17 AM
- last edited on
07-12-2023
11:30 PM
by
Translator
Delete SVI on you L2 Switches. For example, you have on the left side, engineering vlan,
IP add 192.168.10.1/24 on the Sw
and on the R-BLOK-O too!!!! Let's this IP on your L3 equipement, such as R-BLOK-R ; it serves as Gateway also for your vlan!
Why you wan SVI on your L2 switch? The only one should be an SVI for management purpose!
I delete on SW-BLOK-O-1 SVI and ip default gateway
LAPTOP can ping its Gateway hosted on R-BLOC-O
I delete also SVI on S-BLOC-O-2 and now vlan 10 ping vlan 20 on left side !
07-08-2023
08:29 AM
- last edited on
07-12-2023
11:33 PM
by
Translator
you say "ake note that I want to ping device in same department only (example: Left-side PC Engineering can ping right-side PC Engineering and vice versa)."
it's impossible, in your topology like this, that Left-side PC Engineering can ping right-side PC Engineering and vice versa. As @Martin L explain to you. In other word, how you want R-BLOK-O router route packet from left-side
192.168.10.0/24 to its WAN Interface
towards Right-side engineering
subnet 192.168.10.0/24
? It's directly connected! You should NAT or do subnetting !
07-08-2023 06:08 PM
What is objective of this lab? purpose or goals? is it just VSLM subnetting? did u study NAT/PAT ?
if u must follow pdf subnet table and there is no mistake/typo in pdf, then u must do PAT on edge routers. because you have same network and subnet on opposite sides, aka 2 companies. it just like real world example where u and I have 192.168.10.1 on home PC, yours and mine ISP does translation PAT for us so that e can communicate over the Internet.
Regards, ML
**Please Rate All Helpful Responses **
07-08-2023
07:03 AM
- last edited on
07-12-2023
11:35 PM
by
Translator
That is normal ! By default, PCs in vlan 10 will not reach PCs in the same vlan 10 across L3 Broadcast domain. This is true even if they are on the same subnet. L3 B-cast domain is separating L2 and L3 domains. PCs on the same subnet will need some kind of NAT translation in your case on the edges. OR change IP subnet for vlan 10 and 20 on one side; then fix routing.
Routing with RIP is obsolete but if u want use RIP version 2 and
no auto-summary
commands.
there might be other issues ....
Regards, ML
**Please Rate All Helpful Responses **
07-09-2023
12:19 AM
- last edited on
07-12-2023
11:38 PM
by
Translator
Hello M02@rt37 and @Martin L ,
First of all, thanks for spending time on configuring and troubleshooting my
.pkt file
However, there are a lot of misunderstanding and misconception. I beg for apologise from both of you.
My goal and objective is to create fastest topology and fastest internet connection since the question did told me:
The minimum bandwidth for internet access is 100 Mbps and is expected to increase significantly in few years ahead.
Discuss the most appropriate physical layer medium for the network connectivity of the following cases:
1) Within the Blok-O and Blok-N
2) All the way from Blok-O and Blok-N to the main server room in SDEC.
You may assume that the switches can support any transmission medium.
I didn't insert in the first place (the first .zip file), I'm sorry again.
So I tried to implement mesh topologies in both LAN and MAN connection. So I tried to connect mesh topology with mesh topology. As M02@rt37 and @Martin L said earlier, I suppose that this topology is impossible. Therefore, I change the topology from connecting mesh topology with another mesh topology to connect star topology (MAN) with another star topology (LAN).
It works! Here's the design I made:As you can see, I wrote the labelling on both topology.
Achieved wanted objectives:
- LAPTOP-O-01 and LAPTOP-O-02 able to ping LAPTOP-N-05 and LAPTOP-N-06 only (all under VLAN 10)
- LAPTOP-O-03 and LAPTOP-O-04 able to ping LAPTOP-N-07 and LAPTOP-N-08 only (all under VLAN 20)
However,
- The server SERVER-MAIN-01 cannot ping all laptops (end devices) and all laptops cannot ping the server
How to fix this? Because after fixing this server ping problem, I want to make the server for network monitoring. I want to implement Net flow for network monitoring.
@Martin L , I didn't study about VSLM subnetting and NAT/PAT. I just follow what the YouTube says, I'm sorry. And I already adjust all end devices to use the 192.168.10.0/24 IP address block. I leave the updated
.pkt file
and the whole question below.
Thanks in advance and sorry for miscommunication.
07-09-2023
12:48 AM
- last edited on
07-12-2023
11:41 PM
by
Translator
Hello @syazwanmarzuki,
there is a misunderstood.
Your server has got
IP 192.18.10.1/24
and its Gateway is itself....... I don't understand the role of R-DSEC Router regarding its configuration.
You don't have anymore L3 equipement on your topology...then no more SVI acted as Gateway for each VLAN.
Then for what you expected is OK ; only PC on the same department can ping each other since they are in the same VLAN no need og Gateway!
But Server in VLAN 10 is only pingable frome other VLAN 10 ressources.....
Also adjust config on S-DSEC Switch if you want VLAN 10 ping Server MAIN-01:
07-09-2023
05:12 AM
- last edited on
07-12-2023
11:44 PM
by
Translator
Hello M02@rt37 ,
Thanks a lot! It works now, for practical purposes, laptops under VLAN 10 can ping the server.
I also adjust the switch where as the router are connected to VLAN 10 too. Actually, the router is used for NetFlow configuration.
I have done the router R-SDEC settings
ip flow destination 192.168.10.1 . Also, ip flow ingress and egress for Gig 3/0 R-SDEC
I can ping 192.168.10.1 (the server) and 192.168.10.2 (the router R-SDEC) from LAPTOP-0-01 under VLAN 10.
But there is no any output when I use the server's NetFlow app. If the server's NetFlow app got output, my whole assignment is complete.
How to fix this? Latest
.pkt
file below.
Thanks a lot in advance.
07-09-2023 05:42 AM - edited 07-09-2023 05:43 AM
Adujst neflow configuration on R-SDEC:
You will have sample on netflow configurator on SERVER-MAIN-01:
Follow this for netflow config.:https://www.packettracernetwork.com/tutorials/packet-tracer-netflow.html
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