Richard Siemers wrote:
"Controlled release" = Does that mean that you volunteered for it?
At least was your storage online and servicing hosts during the trouble shooting process, as in no hard outages?
Was the problem with all network ports, and your 7200 was just set to auto... or is the problem specific to the adapters used on the V400/V800?
Controlled release just means it is officially released code, but not for wide spread deployment. And while my hosts were still being serviced with IO, my replication was down for 14 hours and I have dozens of systems that have 15 min SLAs.
Problem should impact any 3.1.3 array that has management or RCIP ports set to a fixed speed. If your management port is set to a fixed speed then the array becomes unmanageable via IP and needs a serial connection. Andy node with RCIP port not set to auto will not initialize network ports and since the MGMT and RCIP ports use the same driver it will impact both on a given node. A secondary problem is due to the driver bug the netc process will continually restart as it hits the driver issue and one of our nodes eventually paniced and rebooted due to the process recycling so often.
