Hello friends
In the diagram below, I am in the process of deploying the switch with the IP of 192.168.100.14.
As you can see, the difference between this switch and the others is that it daisy chains off of 192.168.100.15 and is not part of the hub\spoke setup off 192.168.100.13
192.168.100.0 / 24 network is the management VLAN
10.11.144.0 / 24 is the DATA vlan
10.11.143.0 / 24 is the VOIP vlan
Problem
From this setup, if I am sitting at the laptop computer I am able to ping every device in this setup except the new switch of 192.169.100.14. However, if I am “telnetted” into any switch / device in the management network I am able to ping the new switch (192.168.100.14)
even weirder yet, If I connect directly into the new switch, the laptop functions the exact same way, meaning, I am able to ping any other device EXCEPT for the new switch that I am directly plugged into.
I am sure it is a routing issue and I have tried static routes, default routes, but I cannot figure out why I cannot access this new switch...
Going back to the picture
From the laptop computer, if I perform a tracert to 192.168.100.15 the path is as follows
Hop 1 – default client gateway of 10.11.144.254
Hop 2 – 10.11.143.230
Hop 3 – path completed 192.168.100.15
If I perform a tracert to the new switch connected off of the switch I just reached the path is as follows
Hop 1 – default client gateway of 10.11.144.254
Hop 2 – 10.11.143.230
Then the path dies
The line between 192.168.100.15 and 192.168.100.14 are both configured as simple trunk
switchport trunk encapsulation dot1
switchport mode trunk
Any thought / ideas / solutions on why I am unable to reach 192.168.100.14
Accepted Solutions
