Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Procedures for installing the CPU module

Choosing the proper installation procedure  Top

There are three separate cases to consider when installing a CPU module. Choose one of the following three procedures, based on your system criteria:

Installing the module in a nonclustered system  Top

To install the CPU module in a nonclustered system, complete the following steps.

Step

Action

1

Put on the antistatic wrist strap and grounding leash.

2

Connect all cables to the CPU module before inserting the module into its CPU module bay. For more information, see Connecting your appliance to a network.

3

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

4

For FAS270 only

Set the terminate switch on the CPU module to the proper position. See Step 7 of the section Connecting a nonclustered FAS250 or FAS270.

5

Reconnect the power to your appliance and turn on the power switch on both power supplies. See Connecting your system to a power source.

6

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 appliance from a remote image. See Netboot process for the FAS200 series.

7

At the console screen, bring your system to the CFE (common firmware environment) prompt, or halt the system if it tries to autoboot Data ONTAP, by entering the following command:

halt
8

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

boot_diags
9

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

all

Note
The RTC (real-time clock) uses the same battery as NVMEM. If the battery is disconnected and drained, the RTC loses its time, which can cause some tests to fail on startup. One solution is to ignore the message and set the clock in Data ONTAP later, or set the clock from within diagnostics and repeat the diagnostics tests.

10

Exit diagnostics by entering the following command:

exit

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

11

Boot Data ONTAP by entering the following command:

boot_ontap
12

Press ctrl-c to enter the maintenance menu.

13

Select option 5 to enter maintenance mode.

14

Fix disk ownership.

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

disk show -v
15

Reassign disk ownership by entering the following command:

disk reassign -o systemname

16

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

halt
17

Boot Data ONTAP by entering the following command:

boot_ontap

Installing the module in a clustered system with cf disabled  Top

To install the CPU module in a clustered system where the partner node has not performed a takeover, complete the following steps.

Step

Action

1

Put on the antistatic wrist strap and grounding leash.

2

Connect all cables to the CPU module before inserting the module into its CPU module bay. For more information, see Connecting your appliance to a network.

3

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

4

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

5

If power was removed, reconnect the power to your appliance and turn on the power switch on both power supplies. See Connecting your system to a power source.

6

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 appliance from a remote image. See Netboot process for the FAS200 series.

7

Press ctrl-c to stop rebooting.

8

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

boot_diags
9

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

all
10

Exit diagnostics by entering the following command:

exit

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

11

Boot Data ONTAP by entering the following command:

boot_ontap
12

Press ctrl-c to enter the maintenance menu.

13

Select option 5 to enter maintenance mode.

14

Fix disk ownership.

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

disk show -v

15

Reassign disk ownership by entering the following command:

disk reassign -o systemname

16

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

halt
17

Boot Data ONTAP by entering the following command:

boot_ontap

Hot swapping a module in a clustered system while in takeover mode  Top

To install the CPU module in a clustered system where the partner node has performed a takeover, complete the following steps.

Step

Action

1

Put on the antistatic wrist strap and grounding leash.

2

Connect all cables to the CPU module before inserting it into the module bay. For more information, see Connecting your appliance to a network.

3

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

4

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

5

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 appliance from a remote image. See Netboot process for the FAS200 series.

6

Capture the output from the console. Be sure to write down the system ID number, as shown in bold 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
...

7

Press ctrl-c to stop rebooting.

8

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

priv set advanced

9

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

disk reassign -d 84166052

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)?

10

Select y.

11

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

12

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.

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments