Incorrect sysid Used During MB repalce Causes Aggregate Ownership Issues
Applies to
- ONTAP 9
- Assigned wrong system id when replace MB
- AFF A400
Issue
After a mainboard (controller) replacement, the disk reassign operation was performed using an incorrect system ID.
This resulted in persistent mismatches in disk ownership and home ID, causing the following symptoms:
Nodename(takeover)*> disk reassign -s oldsn(correct SN) -d newsn(incorrect SN)
Warning: Disk reassignment is no longer required
as part of a controller replacement procedure.
For further information, see the latest controller or
NVRAM FRU replacement flyer for your system.
Are you sure you want to reassign disks? {y/n}? y
disk reassign: After a reassignment of partner disks, control must be
returned to partner node "nodename02" with the "storage failover giveback" command.
After partner node "nodename02" becomes operational, you must perform
a takeover and giveback of node "nodename01" from the partner node to
complete the disk reassign process.
Do you want to continue (y/n)? y
Disk ownership will be updated on all disks previously belonging to Filer with sysid xxxxxx.
Do you want to continue (y/n)? y
Unable to complete disk reassign successfully (Error: No disks specified).