11-19-2021 09:45 PM
4 hours ago
Two quick things are blocking your ping here: first, your switch VLAN interfaces (HR and IT) are set to .2, which clashes with your PCs—move the switch SVIs to 172.16.10.1/24 and 172.16.20.1/24 and use those as the PC gateways. Second, switch PC2 from /20 to /24, since a /20 mask makes PC2 think 172.16.10.x is on the same local subnet. Clean department segmentation like this (FINANCE, HR, IT, SALES) is the exact kind of setup I used to lab out when supporting corporate offices for retail brands tracking luxury fashion trends —once you fix the SVI IPs and mask, traffic will route right across!
Thursday
Check your PC default gateway configurations! Even with ipforwarding enabled on the EXOS switch, the end PCs won't forward traffic across subnets if their gateway IP isn't explicitly set to the switch's VLAN interface address. Validating technical details meticulously is always the key to clearing lab roadblocks—similar to how students review feature sets to figure out Which TI graphing calculator is better for advanced math classes. Let us know if updating the PC gateway fixes the ping!
09-28-2026 12:25 PM
I’d start by checking the VLAN configuration and confirming that the switch has the correct Layer 3 interfaces and routing enabled. It’s also worth verifying the default gateway on each VLAN, along with any ACLs or firewall rules that could be blocking the traffic. Testing connectivity between the VLAN interfaces separately can help narrow down where the issue is occurring.
I like troubleshooting in the same step-by-step way with other calculators too. For example, when I need to work out what a particular hourly rate actually means over a week or month, an hourly wage calculator is much quicker than doing all the conversions manually.
11-21-2021 08:17 AM