I'm wanting to use two ports from each of SP-A and SP-B on my new VNXe for connectivity to 10GB modules on new 3850 switches (with 2 10GB ports per switch, stack of 2). I've got everything cabled up and all is working well. The only issue I have is that the Health Status is indicating that it want cables plugged into Ports 3 & 4 of each SP. I'm not wanting to use those. How do I get the system to drop the error condition (see below picture)?
When I log in, using my partner ID, I get an "Access denied" message. It says "Page you are trying to access is not allowed. Sorry for inconvenience." Can you provide a publicly facing article on this?
- If there is no configuration on an eth port, and network cable is disconnected, the port shows as blank/unconnected.
- If there is an IP configuration on an Ethernet port, with no cable connected, VNXe treats it as a possible data link down. The port is then marked as ‘red’ implying that it lost connection to the network.
Note: Physical link disconnection, and shutting down a port from switch are treated differently. If we bring down the port from the switch, the ‘red’ icon doesn’t appear.
I'm having a similar issue, and haven't found a work-around yet. We ordered the I/O module with no SFP slots with the intention of using direct-connect/twin-ax cables to connect to our switching, but only have two cables connected per SP. Due to the ports being empty, it's putting our Storage Pools into a "Warning" state, which is preventing us from being able to perform any software upgrades on the system. It seems that the only way to clear this particular warning would be to put in two compatible SFP+ modules in each SP, but spending many hundreds of dollars on modules that we're likely never going to use just to clear an error doesn't seem like a great fix.
Has anyone else found a way around the "SFP module in this port has been removed" error?
Is there an IP address configured for the unused ports? If so, you need to remove the IP address from the unused ports and that should get rid of the error.
Hi Glen, thanks for the reply,
I confirmed that there isn't an IP address configured on the ports that are displaying the error:
Current software version: 18.104.22.16895470 (trying to update, but can't while these errors persist, apparently)