Glad to see that alert!
It's possible that you don't have both WWNS in the same initiator group, so the nimble things the 2 WWNS are different hosts, OR just when the server boots, it is only logging into the SAN with one card, until the OS loads and initializes MPIO, then brings the redundant paths. In that case, I would expect the alert is auto-cleared after that happens.
Nimble/Alletra 6K support is great, they answer the phone quick. Give the a call to get to the root issue, and make sure zoning best practice is followed. If it is an expected alarm from booting from SAN (that short period where the boot process is not using MPIO), see what they recommend for mitigating the false/expected alarm. Please share what you learn! If you are in the USA the number is 877-364-6253
_________________ Richard Siemers The views and opinions expressed are my own and do not necessarily reflect those of my employer.
|