One thing to be aware of if you are adding NetApp storage to the V-Series controller – you need to check the environment settings for fc-non-array-adapter. The value for this setting is the port name that connects to locally attached (eg NetApp disk) storage. If you don’t do this you risk panicking BOTH filers (if it isn’t set and you connect the loop into both controllers). Without this properly set the panic message you may receive is:
PANIC: sanown: received add for already known disk in process sanown_notify……
In order to check this setting you need to do a cf takeover and press ctrl-c on the other node to bring it to the loader prompt. From there run printenv and look for the value of fc-non-array-adapter. For this customer the value was 1a,2a,1b,2b because there was 2 multi path loops of NetApp FC disk. 1c and 2c were used for non-NetApp storage that was presented to the V-Series so those ports didn’t need to be listed. To add a loop of SATA I had to add 1d and 2d in there as well.
fc-non-array-adapter "1a,2a,1b,2b,1d,2d"
followed by
boot_ontap
I assume the reason this setting may seem “backwards” is because prior to 7.3 you weren’t able to connect NetApp shelves to a V-Series controller so by default it assumes the initiator ports are connecting to other vendors. It’d be nice if in the future you can hot add a NetApp shelf without needing to do a cluster failover to check/change the environment variable.
Popularity: 9% [?]
My Popular Posts
