AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Layer 3 'Core' switch: All the SVIs (Switch Virtual Interfaces) for all the VLANs are configured on here. Once that's done, the switches instantly know the reverse route. The network knows where my workstation is and can route traffic there right away. To speed things up, for example, I'll sometimes ping my workstation from a new VM instead of the other way around. Sometimes, I'll have to use ping -t for 10 or 15 seconds when accessing a device the first time in a complex network. One or two pings is typical for a switch that might be 1 or 2 hops away. ![]() When the target device answers, it has re-discovered the route. Faced with this, the switch floods an ARP broadcast out each port and listens for a return. If no traffic passes through the switch destined for a specific MAC, the switch will forget how to get there. These addresses are cached for a fixed time (or until the table fills up), then they expire. ![]() ![]() The core switch has a table of MAC addresses that tells it how to forward traffic. Is this normal if it hasn't been pinged in a while?Yes, this is normal. ![]() If I keep repeating the test, the subsequent ones are fine. Sometimes when I ping from core to one of the access switches, it misses the first 2 pings, but the others are quick. Yes, I am setting the default gateway for the mgmt vlan SVI on the core switch.
0 Comments
Read More
Leave a Reply. |