Installing the CPU module

Put on the antistatic wrist strap and grounding leash.

Connect all cables to the CPU module before inserting the module into its CPU module bay. For more information, see the gFiler Gateway Hardware Installation Guide.

From the back of your gateway, slide the module into the CPU module bay and push the cam mechanism levers into place.

Set the terminate switch on the CPU module to the proper position.

If power was removed, reconnect the power to your gateway and turn on the power switch on both power supplies. See the gFiler Gateway Hardware Installation Guide.

If you installed a new CPU module with a new CompactFlash card, the card might not contain any data, in which case you need to boot your gateway from a remote image. See Netboot process for the GF270c.

Press Ctrl-c to stop rebooting.

Run diagnostics on the new CPU module by entering the following command:

boot_diags

At the diagnostics prompt, run all tests by entering the following command:

all

Exit diagnostics by entering the following command:

exit

See the Diagnostics Guide at http://now.netapp.com for more information.

Boot Data ONTAP by entering the following command:

boot_ontap

Press Ctrl-c to enter the Maintenance menu.

Select option 5 to enter Maintenance mode.

Fix disk ownership.

To see all disks and the old CPU module name, enter the following command:

disk show -v

Reassign disk ownership by entering the following command:

disk reassign -o systemname

Shut down the gateway by entering the following command at the console:

halt

Boot Data ONTAP by entering the following command:

boot_ontap

Put on the antistatic wrist strap and grounding leash.

Connect all cables to the CPU module before inserting it into the module bay. For more information, see the gFiler Gateway Hardware Installation Guide.

Set the terminate switch on the CPU module to the proper position.

From the back of your gateway, slide the module into the module bay and push the cam mechanism levers into place.

If you installed a new CPU module with a new CompactFlash card, the card might not contain any data, in which case you need to boot your gateway from a remote image. See Netboot process for the GF270c.

Capture the output from the console. Be sure to write down the system ID number, as shown in boldface in the following example. The output should look something like this:

Loading: 0xffffffff80001000/8500653 Entry at 0xffffffff80001000
Closing network.
Starting program at 0xffffffff80001000
Press CTRL-C for special boot menu
.
.
WARNING: there do not appear to be any disks attached to the system.

Check that disks have been assigned ownership to this

system (ID 84166052) using the 'disk show' and 'disk 
assign' commands from maintenance mode.

No root volume found.
Rebooting...

Press Ctrl-c to stop rebooting.

Reassign disk ownership for the new CPU module from the partner node with the new SYSID, by entering the following commands at the takeover prompt:

priv set advanced

Enter the following command using the recorded System ID from Step 6, for example:

disk reassign -d 84166083

The console screen should display something resembling the following:

node x(takeover)> priv set advanced
node x(takeover)*> disk reassign -d 84166083

Disk ownership will be updated on all disks previously belonging to Filer with serial number 123456.
Would you like to continue (y/n)?

Select y.

Verify disk ownership. Make sure that all disks that were supposed to be reassigned, were reassigned.

To see all disks, enter the following command:

disk show -v

The new CPU module should see the disk on the next reboot, accompanied by the following message:

Waiting for cluster giveback

From the partner node, enter the following command:

cf giveback

Note
If the giveback doesn't succeed, see the System Administration Storage Management Guide for additional information.