What is the likely cause of an intermittent SAN Boot fails?

Question

Options

• AMisconfigured SAN boot target in the boot policy of the service profile
• BLUN ID Mismatch
• CFCoE used instead of FC
• DWrong boot order in the service profile

• A
  83% (34)
• B
  2% (1)
• C
  10% (4)
• D
  5% (2)

Explanation

A misconfigured SAN boot target in the service profile's boot policy is the most likely cause of intermittent failures because if the target WWN or boot LUN path is wrong or inconsistent, the host may sometimes connect (e.g., via a secondary path or cached entry) and sometimes fail, producing the erratic behavior that defines "intermittent." Option B (LUN ID mismatch) would typically cause a consistent failure, not an intermittent one - the wrong LUN is simply always wrong. Option C (FCoE vs. FC) is a protocol/fabric configuration issue that would cause a persistent, reproducible failure rather than a sporadic one. Option D (wrong boot order) would result in the system consistently booting from the wrong device or failing entirely, not intermittently.

Memory tip: Think "intermittent = target misconfiguration." A wrong target in the boot policy means connectivity to the SAN fabric works fine some of the time (paths, HBAs, fabric are all good), but the boot destination is unreliable - that maps directly to a misconfigured boot target in the service profile policy.

No community discussion yet for this question.