We have a virtual stack set up in the following manner (simplified for brevity):
Router/Firewall => Dell Switches => VMWare Cluster => Dell Switches (SAN traffic) => SAN.
In working with VMWare support, they couldn't stress enough that we have all our SAN traffic separated from everything else. So all the management, vMotion, and VM traffic stays on that first set of switches. The only traffic on the SAN switches is the ports assigned to the iSCSI adapter and to the SAN controllers. The SAN traffic is on 192.168.10.0/24 and everything else is on 192.168.11.0/24.
I've now realized that I can't log in to manage the SAN switches unless I physically plug into it, or if I create a VM on the same vSwitch that the iSCSI adapters are on, which in both cases mixes "normal" traffic with the iSCSI traffic. So they suggest setting up a separate VLAN on the SAN switch for management. And that's where I have the problem.
I picked a port on the SAN switch, created a new VLAN 10, and tagged the port for that vlan. This automatically marked it as Forbidden for the default vlan, so it's now separated from the iSCSI traffic. I also configured vlan 10 to have an IP address in the 192.168.11.0/24 network (the same as everything else on switch 1). I then place an uplink from that port up to switch 1, create the same vlan, set the port to "General" mode (is this a Dell thing?), have it untagged for the default vlan 1, and tagged for vlan 10, with the PVID set to 10.
I then plug my my laptop in to another port in switch 1, make it tagged for VLAN 10... but nothing. I can't ping nor pull up the admin portal for the SAN switch.
What part of the vlan tagging am I not understanding? On the SAN switch, it's set to Access and Tagged with vlan 10, so that should be the only traffic allowed on it. Then on the uplink on switch 1, I assigned it to General mode, untagged default, tagged vlan 10, and pvid 10. So this should allow access from any port from vlan 1 or 10, if it comes in untagged, it tags it as 10, and it should be able to forward the data when I request the IP of the vlan on the SAN switch. But obviously it's not, so where am I going wrong?