Tim,   You may want a case opened to really dig into this, but if you pull a UCSM show tech from the domain you should be able to check the below logging for more information.     svc_sam_controller.log <--- This will have cluster state logging (so you can see the switchover start and likely some messaging following this with the reason for failing back) svc_sam_dme.log <--- This is the overarching management process, and may also contain some helpful information Note for both the above you may need to look into the archived logs (so not just the initial svc_sam_controller.log file).   Let us know if you see anything strange there. -- Niko ... View more

Hello ZenON,   Would you be able to attach a screenshot of your Scrub policy as well?   -- Niko ... View more

Hello,   I can't speak to the changes not being saved, although I would suspect that this means there is some disconnect between the host and storage (changes aren't being written and thus not persisting through reboot).   Regarding the iscsi vNIC as vmnic0, this could certainly be possible, and is based on how ESXi enumerates the devices. See the below VMware KB. https://kb.vmware.com/s/article/2091560   Hope this helps!   -- Niko ... View more

Hello,   I believe those are to represent the LUN mask (in this case it appears to be 0, so we are looking for the LUN masked as 0). If you still have the server in a failed to boot state, can you run the below and provide the output?   connect adapter [chassis #]/[blade #]/1 connect attach-fls lunlist   *Edit (Saw this output on another thread in this discussion).   adapter 1/1/1 (fls):2# lunlist 13 vnic : 13 lifid: 3 - FLOGI State : flogi est (fc_id 0x270302) - PLOGI Sessions - WWNN 50:06:01:69:3e:e0:3e:9e WWPN 50:06:01:69:3e:e0:3e:9e fc_id 0x270600 - LUN's configured (SCSI Type, Version, Vendor, Serial No.) LUN ID : 0x0000000000000000 (0x0, 0x4, DGC , FCN00131500079 ) - REPORT LUNs Query Response LUN ID : 0x0000000000000000 - WWNN 50:06:01:60:3e:e0:3e:9e WWPN 50:06:01:60:3e:e0:3e:9e fc_id 0x270500 - LUN's configured (SCSI Type, Version, Vendor, Serial No.) LUN ID : 0x0000000000000000 (0x0, 0x4, DGC , FCN00131500079 ) - REPORT LUNs Query Response LUN ID : 0x0000000000000000 - Nameserver Query Response - WWPN : 50:06:01:60:3e:e0:3e:9e - WWPN : 50:06:01:69:3e:e0:3e:9e   This output looks good from what I can see, the section highlighted above tells me that from the server's perspective it can see the LUN. What OS are you trying to install? Does the OS include the appropriate drivers for the adapter?   -- Niko ... View more

Hello,   Looking at your steps below, is there a reason you are not simply adding the new vNICs to the original profile? That way you won't have to unassociate/re-associate, and the MACs/WWPNs for the original virtual interfaces all remain the same.   Assuming we can't do the above...   Do I have to copy the identifiers from the old profile to the new one? Likely not, although you will want to be careful when adjusting any FC WWPN, as you will likely lose connectivity to storage until your SAN is reconfigured.   -- Niko ... View more