The fault was isolated to Layer 2, specifically in the VLAN and trunking configuration. After upgrading a Cisco Meraki core switch from MS 17. 5, we experienced a production outage. However, when checking the connected device on Port 24, it displays the configured IP but shows. We have a pair of Dell N3224P-ON switches and today's morning my colleague gave me a task and instructions to remove some unused VLANs. When I saved the configuration, everything stopped working and now we don't know what to do. We already rebooted both. Having already solved your first trouble ticket for the day, which basically was an “Internet is down” issue (including common switch issues, VLAN-related issues, and spanning-tree issues), you're now ready to tackle your second trouble ticket. This time, we're looking into a “No connectivity”. New core switch VLANs not routing Hello all- I've inherited an HP Procurve infrastructure after years in a Cisco environment. It was my understanding that after creating the VLAN and assigning it an IP address. Pinging between VLANs or capturing traffic between VLANs shows packet loss, even though the physical NICs (vmnics) are reported as being up (from the physical switch and the ESXi hosts).