06-03-2017 11:54 PM - edited 03-08-2019 10:50 AM
Hi,
I have a question regarding my layer 3 switch. Currently, the network works fine except that the layer 3 switch (which is Curly) cannot ping outside the management VLAN, and other devices cannot ping it. Moe can ping all devices fine.
So, my question is, how do I get Curly to ping the PC's and other router interfaces. I have not had much experience with the 3560 switch. Any help would be greatly appreciated
Thanks
Solved! Go to Solution.
06-04-2017 02:01 PM
Curly>sh ip arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 83.174.64.190 0 0001.6499.8402 ARPA Vlan452
Internet 83.174.64.205 - 00E0.F774.E59E ARPA Vlan452
This is what I got. Don't seem to be getting the 83.174.64.206 which is what I should be getting.
06-04-2017 02:11 PM
There is definitely something not working properly.
It may be a software bug, difficult to say but you should only see arp entries for devices in multiple vlans when the switch is acting a L3 switch.
Have you tracked down those mac addresses ie. what devices are they ?
Jon
06-04-2017 02:19 PM
0001.6499.8402 is the router,
00E0.F774.E59E would probably be one of the switches (most likely the L3), I can't find that info on packet tracer.
06-04-2017 02:29 PM
All I can say is that we have seen bugs with the software you are using before and the switches don't always behave as real world switches would.
That is not a satisfactory answer but the behaviour is not what you would expect to see unless I am missing something really obvious.
It is, as far as I can tell, definitely not due to your lack of understanding and I don't think you have configured anything incorrectly.
You may want to post this question using the link Dan provided above as they will have a lot more people using the same software and they may spot something I have missed or recognise a bug I am not aware of.
Sorry I couldn't be of more help but if you do find an answer would be interested to hear it :)
Jon
06-04-2017 02:32 PM
No worries Jon. Thanks for the help anyway. I am going to test it on real devices today so hopefully I will be able to confirm whether it is just a software bug.
Thank you once again for the time and help you gave me. Will definitely let you if a solution is found.
06-04-2017 05:31 PM
Hi Jon.
I am left to believe it is a software bug. Did the task on real hardware and it worked perfectly. Thank you for all the help.
Caitlyn
06-04-2017 05:57 PM
No problem, thanks for letting me know.
Jon
06-04-2017 12:46 PM
Sorry you did say you couldn't ping any other router interface IPs.
When you try what does the arp table on the L3 switch look like ?
Also can you post a "sh spanning-tree vlan 452" from the switch.
Jon
06-04-2017 12:56 PM
Just checked that output again and with the "sh int trunk" it is saying that on both trunks there are no vlans in STP forwarding state which is obviously not how it should be.
But then this would mean nothing was being forwarded and yet you can ping within the network.
Not sure what is going on at the moment.
Jon
06-04-2017 12:07 PM
Ok, sorry, I'm very new to this forum.
No problem, but you may be interested to know the communities of CSC are related to support of real hardware. As you mentioned Packet Tracer I assume the we are speaking about Packet Tracer simulated network. Packet Tracer is in Cisco Learning courses tool thus it's better to ask in appropriate community of Cisco Learning Network next time.
Cheers
Dan
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