A bank restores a logical configuration backup onto a replacement fabric interconnect pair. Service profiles, pools, and policies return, but every vHBA logs in with a new WWPN and the SAN zones miss the blades. What was left off when that backup was taken?
Select an answer to reveal the explanation.
Short Explanation
You moved the office and the nameplates came out of a new drawer. A logical backup can carry the real WWPNs, MACs, and UUIDs when preserve identities is selected. Without it, the restore builds the profiles and then hands out new pool identities, and the zones still name the old ones.
Full Explanation
A logical configuration backup is the XML of service profiles, pools, policies, VLANs, and VSANs. Preserve identities tells that backup to keep the addresses already drawn from the pools, including vHBA WWPNs. The bank's restore brought the profiles back and assigned new WWPNs, which is what happens when that selection was off. The chassis power policy decides how PSUs redundantly feed the chassis. It does not mint WWPNs. An Intersight advisory is a published notice. It is not a backup of server identities. A full-state file is a binary system snapshot and can rebuild a fabric interconnect, but it is not the only backup that can hold a WWPN. A logical backup with preserve identities is the readable file that would have kept these port names. Caveat: the zones on the SAN are outside UCS. Restoring the old WWPNs makes the existing zones right again. It does not rewrite the array. Operational check: before the next restore, confirm the backup type is logical and that preserve identities was selected, then compare one vHBA WWPN with the zone member.