netapp - the nvmem led on the faceplate will start ...for netapp authorized service engineers -2 a...

I. Appliance / PCM Visual Checks VIII. Set date and time on the RTCII. Node Pre-Checks IX. Update Firmware on the Replacement PCMIII. Node State Check and Shutdown Procedure X. Run Diagnostics (22-30 min)IV. Capture the Current System Configuration XI. Set Fibre Channel (FC) "target" PortsV. Remove the cables and extract the PCM XII. Disk Reassignment on the Replacement PCMVI. Move Battery, SFPs - Exchange the CF Cards XIII. Boot the Operating SystemVII. XIV. New controller registration, Submit logs , Part Return

I.Step

1 Visually verify if you are working on correct model and READ the STOP box below.The FAS2020 Appliance has 1 or 2 Processor Controller Module(s) (PCM) integrated into a 12 Bay Shelf

Fig 1 Fig 2 Rear View (clustered system shown)

Fig 3

2 Continue with Section I on next page.

FAS2020 Appliance: Appliance / PCM Visual Checks Action Description

of 16

This procedure will take 60-90 minutes SECTION OUTLINE of a FAS2020 Appliance Processor Controller Module (PCM) Replacement

Partially Reinsert the Replacement PCM and Reconnect the cables

Processor Controller Module (PCM) Replacement for the FAS2020For NetApp Authorized Service Engineers-2

PS-2 ACSwitch

FAS Model NumberOne Thumbscrew and cam handle to extract each PCM.

Each PCM (Processor Controller Module) Card, (A or B) has it's own System Serial Number. Verify the system serial number!

A

B

ConsolePort

BMCPort

PS-1 ACSwitch

Fibre Channel Ports: 0a, 0b Ethernet Ports: e0a, e0b

2u

The NVMEM LED on the faceplate will start flashing when power is removed from the controller if the system is "waiting for giveback", or the system was not shutdown properly (uncommitted data). Follow the steps in Section V carefully.

STOP !!

ACLED " ! " LED is ON when hardware

failures are detected and if the controller fails over.

Status LED!

The Status LED will be "ON" if the PCM is faulted or if controller failiover is disabled

If the NVMEM (TOP) LED is flashing when PCM is removed, read STOP!! below

A "HA" Configuration has 2 PCM cards, (A & B) as shown. A non Active-Active system has only one card in the bottom slot, the top slot is a filler plate. The PCM is HOT pluggable.

Activity LEDsIf the LED actively

flashes, that controller is online.

1 Orange Thumbscrew to extract each PCM

I.Step

Fig 4

II.Step

1 Review Section I and confirm the pictures in Fig 1 Section I. match your appliance2

34 Remove the replacement PCM from the anti-static bag and examine the housing and connector for damage.5 Go to Section III, "Node State Check and Shutdown Procedure" on next page.

Action Description

of 16

Adhere to anti-static precautions. (A paper ESD strap is included inside the RMA box if you don't have your own)

FAS2020 Appliance: Node Pre-Checks Action Description

Verify the "Order Reference 8xxxxxxxxx number on the RMA packing slip is the same as the Part Request (PREQ) number listed in your dispatch notes.

FAS2020 Appliance: Appliance / PCM Visual Checks (Cont.)


A typical FAS2020 PCM

Notes: 1. This procedure will take 60-90 minutes.

2. This Action Plan needs to be followed in step order.

3. Note the Caution on the NVRAM LED in Section V.

4. FC port configuration, disk list and the system date are captured prior to removing the original PCM.

5. Compact Flash (CF) Card and PCI Card need to be moved from the Original PCM to the Replacement PCM.

6. System variables; date-time, disk reassignment and FC port configuration must be set before rebooting the system.

III.Step

1To review the Job Aid on how to connect to console (IOIOI) port and serial emulator options, click >> Console Attach Aid

NOTE

NOTE Chassis Check: To see if two controllers are installed reference "HA" figures here > HA Configs2

two controller assemblies installed in the same physical chassis. See detailed messages here >3

NOTE "cf Status" will display the state of controller failover. "cf" command example is here >> cf status cmd

4 HA (Dual) Controller Configurationa)

5 If the console response is "LOADER>", go to Section IV.6 If the console response is "Waiting for giveback" hit ^C (Ctrl-c) to abort the giveback.7 If this is displayed, "Do you wish to halt this node rather than wait [y/n]?" Enter "y" for yes.8 After the system runs through a prom initialization, the system should drop to the "LOADER>" console prompt.

9 Go to Section IV, "Capture the Current System Configuration" on next page.

WARNING for HA Controller ConfigurationsIf the failure has caused a controller failover you may have been dispatched on the surviving controller's serial number, not the failed one. Check console responses before proceeding. See "Appliance Check",

STOP!

If both controllers are UP and Online and controller failover is enabled: A "cf takeover" will have to be executed from the partner node or issue a "halt" if failover is disabled. Work with NGS if you have questions.

of 16

FAS2020 Appliance: Node State Check and Shutdown Procedure Action Description

If a SINGLE controller configuration: The console response is "login" or "password" or the <system prompt>, the end-user will have issue a 'halt' on the system for proper shutdown. Work with NGS if you have questions.

Always capture the node’s console output to a text file, “NetApp-dispatch-num.txt”, even if using the end-user's

Visual Chassis Checks FRONT: Look for an Amber Status ( ! ) LED, then observe which Activity LED is flashing, and if one is OFF. The activity LED that is not flashing is ready for servicing, or the controller is not installed.REAR: Look for the controller that has the Status ( ! )LED ON. Both could be on, verify which Activity LED is not flashing - Continue with console response checks in step 2.

Check the state of the node by viewing the console port responses from (each) controller if is HA. HA requiresAppliance Check

" ! " (Status) LED is ON for :1) PCM failure 2) PCM was taken over by

its partner 3) Controller failiver feature

is disabled.


Controller Activity LEDsIf LED actively flashes

GREEN, that controller is online -"A" is online. "A" is the top controller, "B" is the bottom controller.

Front OPS LEDS Controller Fault ( ! ) LED on Rear

"B" Controller Fault LED is "ON""A" Top is OFF

Fig 6

Fig 5

Waiting for giveback...(Press Ctrl-C to abort wait)Waiting for giveback...(Press Ctrl-C to abort wait)This node was previously declared dead.Pausing to check cluster partner status ... partner is operational and in takeover mode.........Do you wish to halt this node rather than wait [y/n]? y

Halting...........CPU Type: Mobile Intel(R) Celeron(R) CPU 2.20GHzLOADER>

Step 6: Hit '^C' (Ctrl-c)

Step 7: Enter 'y'

The "LOADER" prompt is displayed

".…" = Deletedlines to save space

AC Power

A

B

IVStep NOTE

1

2 a)

b) From the LOADER> prompt enter "autoboot" to initiate a prom bootstrap. c)

d) Enter '5' for "Maintenance mode boot".e) If asked "Continue with boot?" Answer: y

3 a) If this is the "Original" PCM - Continue with Section IV on next page.b) If this is the "Replacement" PCM -Return to Section XI and continue with step-4.

Action Description

of 16

FAS2020 Appliance: Capture the Current System Configuration

When this message appears: "Press CTRL-C for special boot menu" , press CTRL-C (^C) to load the "Special boot options menu". After about 30-40 seconds, the "Maintenance menu" will appear.

Reference the example of console output below and follow these steps. The ….. (dots) represent deleted text to highlight the specific output messages to key on.

The date and time is stored in the system PROM in Greenwich Mean Time, (GMT) also known as Universal Time Clock, (UTC). At the LOADER> prompt, enter: "show date". Record on paper the system's GMT time and the local time to determine the number of hours (and minutes) the local time is ahead or behind GMT.

Confirm the "console" output is being saved to a text file. It will be needed later in this action plan.

NOTE If the original PCM fails to boot to the Maintenance menu, continue with the PCM removal in the next SectionIf the replacement PCM fails to boot to the Maintenance menu, engage NGS for assistance.


LOADER> show dateCurrent date & time is: 10/17/2008 12:21:38

LOADER> autoboot....Starting program at 0x00202018

Press CTRL-C for special boot menu........Special boot options menu will be available..

(1) Normal boot.(2) Boot without /etc/rc.(3) Change password.(4) Initialize owned disks (28 disks are owned by this filer).(4a) Same as option 4, but create a flexible root volume.(5) Maintenance mode boot.

Selection (1-5)? 5

You have selected the maintenance boot option:the system has booted in maintenance mode allowing thefollowing operations to be performed:

? disk fcadmin fcstat ........ fctest disktest outb disk_mung

Type "help <command>" for more details.

In a cluster, you MUST ensure that the partner is (and remains) down,or that takeover is manually disabled on the partner node,because clustering software is not started or fully enabledin Maintenance mode.

FAILURE TO DO SO CAN RESULT IN YOUR FILESYSTEMS BEING DESTROYEDContinue with boot? y

> *>

Step 2c): Wait for this message, then hit ^C (CTRL-C) Then in a few seconds this message will be displayed.

Step 2d): Enter "5"

Step 2b): Enter "autoboot"

This is the maintenance mode console prompt

Step 2e): If this node has a partner node this message will be displayed. Answer: '"y " to the "Continue with boot?" question.

Step 1): Enter "show date"

IVStep

4 From the > *> prompt enter "fcadmin config" to log the configuration of the integrated FC host adapters. a)

5 Enter "disk show -v" from the > *> prompt to view which FC Adapter ports are driving disks- See Text Box 5

NOTE

6 Take note of all the Adapter numbers displayed - Text Box 6. In this example: Only adapter ' 0c' is displayed.7 At the > *> prompt enter "halt" (after prom initialization the console will display the "LOADER>" prompt)

8 Go to Section V, "Remove the cables and extract the PCM" on next page.

The "disk show -v" sample console output is below. It lists the OWNER for each disk, which is the node's hostname. Later in this procedure we will reassign the disks to the new PCM.

of 16

FAS2020 Appliance: Capture the Current System Configuration (cont.) Action Description

Take note of the Adapter ports listed configured as "target" ports. After the PCM is replaced if any internal FC Adapter ports were configured as a "target", the "fcadmin config" command will be used to re-configure them.

*> fcadmin config

Local Adapter Type State Status---------------------------------------------------0a target CONFIGURED offline0b target CONFIGURED offline

*>

*> disk show -v

Local System ID: 135023148

DISK OWNER POOL SERIAL NUMBER ------------ --------------- ----- -------------

0c.00.1 fas2020cl1 (135023136) Pool0 5QE4RA7Z

0c.00.4 fas2020cl2 (135023148) Pool0 5QE4RAFA

0c.00.0 fas2020cl2 (135023148) Pool0 5QE4Q5CH

0c.00.6 fas2020cl2 (135023148) Pool0 5QE4RAB1

0c.00.5 fas2020cl1 (135023136) Pool0 5QE4RADS

0c.00.3 fas2020cl1 (135023136) Pool0 5QE4R8Y4

0c.00.7 fas2020cl1 (135023136) Pool0 5QE4RADG

0c.00.8 fas2020cl2 (135023148) Pool0 5QE4Q5CJ

0c.00.9 fas2020cl2 (135023148) Pool0 5QE4RA69

0c.00.2 fas2020cl2 (135023148) Pool0 5QE4RAAG

0c.00.10 fas2020cl2 (135023148) Pool0 5QE4RAHG

0c.00.11 fas2020cl1 (135023136) Pool0 5QE4Q5JL ....*> halt

Step4: Enter "fcadmin config"

Step 4a): "fcadmin config"displays all integrated FC Adapters. In this example, both Adapters are configured as "target" ports. Note adapter numbers listed as "target".

Step 5: "disk show -v" prints the System ID of the Local System (135023148). It also prints the node's hostname for each disk under the OWNER heading. This node's hostname is "fas2020cl2". It owns disks: 0c.00.4, 0c.00.0, 0c.00.6, 0c.00.8 etc.

Step 7: Enter "halt" to exit to the "LOADER>" prompt

Step 6: Under the DISK heading, all FC Adapters connected to disk shelves are listed. In this example adapter ' 0c' is the only one listed, but often there are more. After the PCM is replaced, confirm the same adapters are listed meaning there is an active FC path to the disks.


The partner owns disks: 0c.00.1, 0c.00.5, 0c.00.3, etc.

V.Step

NOTE

1 On the PCM to be serviced, label each cable connector with its port number and then unplug them and move them aside.NOTE If 2 PCMs installed: Do not leave the PCM removed for much more than 2 minutes so the other PCM does not over heat.

2 Loosen the orange thumbscrew, ref Fig 3, and pull down on the cam lever to unlatch the PCM and extract it HOT.

Before proceeding, the state of the NVRAM LED should be resolved if it's flashing by reading the caution above.Reference Section I. Figure 3 for the location of the NVMEM LED on the PCM.

VI.Step

1

2 Remove the top cover on the old PCM to expose the NVMEM battery. Disconnect the cable and remove the battery.

STOP

3 Insert orignal battery into the replacement PCM. If one exists in it, move it to old PCM. Connect battery cable - Fig 7.

4 Turn the PCM upside down to reveal the Compact Flash (CF) cover.5 Slide the CF cover up and carefully slide the CF card from it's connector and mark it with an "O" for original -Fig 8.

NetApp Label is on the Top Side

6

VII.Step

1 Partially insert the replacement PCM into the slot so that the cables can be attached- DO NOT engage the backplane yet.2

3 Re-attach laptop to the console port and capture the display output even if the end-user is doing it.4 Go to Section VIII, "Update Firmware on the Replacement PCM" on the next page.

FAS2020 Appliance: Partially Reinsert the Replacement PCM and Reconnect the cables Action Description

Cables: Fully insert each cable that was removed to its proper port until it clicks in. Test by pulling on them. Especially the FC ports!

Exchange the CF cards between the PCMs. The one marked "O" should now be in the replacement PCM.

Some replacement PCMs have the NVMEM battery pre-installed. If one is installed, remove it and place it in the defective PCM, as it is most often too discharged to complete the part replacement process.

FAS2020 Appliance: Move the battery, SFPs - Exchange the CF Cards Action Description

of 16

FAS2020 Appliance: Remove the cables and extract the PCM Action DescriptionIf TWO PCMs are installed, DO NOT shut off the power supplies to replace the PCM. Only shut off both power supplies if just one PCM is installed.

3

Remove each SFP/GBICs one at a time, installed in the Ethernet and FC ports from the original Controller Module and fully insert each one into the same port location in the replacement Module. (Do not mix them up!)


Slide the CF card to disengage it from the connector

HA (Dual) PCM Configuration: If the green NVMEM (TOP) LED starts flashing, Ref Fig 3, when the PCM is extracted from the chassis, confirm that a clean takeover occurred from the end-user or NGS as the flashing LED may indicate uncommitted data in the NVRAM memory before continuing!

Single PCM Configuration: If the NVMEM (TOP) LED is flashing, the system was not 'halted' properly. Check with end-user. If not halted properly, re-insert PCM and try to boot by entering 'bye' at the LOADER>

STOPand

READthis

CAUTION

Fig 8

Battery and cable connector. Presstab to release connector. Batteryis held into the module by Velcro tape.

Connector is next to Heat Sinkwhich may be Hot, let it cool

FAS2020PCM

Fig 7

Slide the CF cover as indicated to expose the CF Card.

VIII.Step NOTE

1 Fully Insert the controller into the slot and raise the cam lever and secure it with Orange thumbscrew. Ref Section I, Fig 2.2

3 If you miss the window to abort the autoboot: "Press CTRL-C for Special boot menu" and follow steps 3a-3d.a. Press ^C (CTRL-C) to access the "Special boot menu".b. When the Special Menu Selection is displayed, enter "5" - see below.c. If the question comes up "Continue with boot?" Answer "y"d. At the "> *>" prompt enter "halt" to drop to the "LOADER>" prompt after about 20 seconds - see below.

6 Continue with Section VIII on next page.

IMMEDIATELY after the console message "Starting AUTOBOOT press Ctrl-C to abort…" is displayed, press Ctrl-C (^C) key to abort the autoboot. See Console output below. If you miss the window go to step 3 otherwise step 6.

of 16

FAS2020 Appliance: Set date and time on the RTC Action DescriptionConfirm laptop is attached (or end-user's PC) as it is required to stop the boot sequence.


Fig 12 Fig 11

AMI BIOS8 Modular BIOSCopyright (C) 1985-2006, American Megatrends, Inc. All Rights Reserved Portions Copyright (C) 2006 Network Appliance, Inc. All Rights Reserved BIOS Version 3.0.........CPU Type: Mobile Intel(R) Celeron(R) CPU 2.20GHz

Starting AUTOBOOT press Ctrl-C to abort...

Autoboot of PRIMARY image aborted by user.

LOADER>

....Starting program at 0x00200000Press CTRL-C for special boot menu

Special boot options menu will be available.NetApp Release 7.2.4L1P3D2: Tue Jun 3 18:51:55 PDT 2008........(1) Normal boot.(2) Boot without /etc/rc.(3) Change password.(4) Initialize owned disks (6 disks are owned by this filer).(4a) Same as option 4, but create a flexible root volume.(5) Maintenance mode boot.Selection (1-5)? 5

You have selected the maintenance boot option:the following operations can be performed:

.... ....

.... .... disktest diskcopy xortest outb

Type "help <command>" for more details....> *> halt

Step 2: Press "CTRL-C"

This message should be displayed.

Step 3a: Press "CTRL-C"

".…" = Deletedlines to save space

Step 3b: Enter "5" for Maintenance mode boot

Step 3d: Enter "halt". Will drop to LOADER> prompt after about 20 seconds

VIII.Step

7

8

NOTE Detailed instructions for another method of obtaining the time in GMT and setting the date and time is here> RTC Check9 To set the time issue: set time hh:mm:ss Set the time in GMT using 24 hour format - Do not set the time to local time.

NOTE If this maintenance period spans across the midnight hour in GMT time, the DATE will also need to be set.10 To change the date, issue: set date mm/dd/yyyy (mm = 2-digit month, dd = 2-digit Day, yyyy = 4-digit Year)11 If the date or time was changed, issue: show date again to verify the GMT date and time are correct.

IX.Step

1 At the LOADER> prompt enter the next 4 commands after each one completes:a) update_flash to copy the firmware on the Compact Flash card to the motherboard's flash PROM.

NOTE The flash will not update if the replacement PCM's version is newer - if so, skip this stepb)c) "set-defaults" to reset the PROM variables to defaults.d) ^G (Ctrl-G) to enter the BMC-shell . The prompt changes to: "bmc shell ->".

2 Continue with Section IX on next page.

At the LOADER> prompt enter: "show date" to display the date and time in GMT on the new PCM

"update_bmc" to update the firmware on the Baseboard Management Controller (BMC) from the Compact Flash card.

of 16

FAS2020 Appliance: Update Firmware on the Replacement PCM Action Description

FAS2020 Appliance: Set date and time on the RTC (cont.) Action Description

The original motherboard's GMT time and local time should have been recorded in Section IV. If you don't have it, you can obtain the GMT time from the partner node, or another NetApp appliance or any Unix Server using: "date -u". (The "-u" option displays the time in GMT/UTC) The new motherboard's Real Time Clock (RTC) must be set within 2 minutes of the time displayed (which is GMT time) for users to be able to re-connect to this appliance.


LOADER> update_flashNew BIOS Version: 3.0New Loader Version: 1.3Saving Primary Image to Backup flash deviceProgramming .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+ done. 1048576 bytes writtenUpdating Primary Boot FlashProgramming .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+ done. 1048576 bytes writtenLOADER>

LOADER> update_bmcBMC firmware version: 1.2Programming: this may take up to 120 seconds to complete...

BMC Release 1.2Press ^G to enter BMC command shellpre-init time [bmc.reset.power:notice]: Hard reset by external power-cycle.

Important: In order for the BMC firmware changes to fully take effect, it is necessary to reboot using the "bye" command before starting OnTap

LOADER> set-defaults*** Variable(s) modified but NOT saved until the OS is booted ***LOADER>

LOADER> ^G (CTRL-G)=== OEMCLP v1.0.0 BMC v1.2 ===bmc shell ->

Step 1a): At the LOADER> prompt, enter update_flash to update the flash PROM

Step 1c): At the LOADER> prompt, enter set-defaults to reset PROM variables.

Step 1b): At the LOADER> prompt, enter update_bmc to update the flash memory on the baseboard management controller on the replacement PCM

Step 1d): At the LOADER> prompt, enter ^G (CTRL-G) to enter the BMC-shell.

LOADER> show dateCurrent date & time is: 10/14/2010 16:36:50LOADER>

Time is displayed in in 24hr mode

Daylight SavingsTime will vary the offset from GMT

IX.Step

3 At the bmc shell -> prompt: a) Enter: 'priv set advanced' to change to "bmc shell * ->". (Has Asterisk)b) Enter: 'battery show' to display the NVmem battery status.c) Confirm "status" indicates "ready" or "charging".d) Enter: 'battery verify' to make sure all battery parameters are correct.e) Enter: 'exit' to return to "LOADER>" prompt.

4 Go to Section X, "Run Diagnostics (run time 22-25 minutes)" on next page.

of 16

FAS2020 Appliance: Update Firmware on the Replacement PCM (Cont. ) Action Description

bmc shell -> priv set advancedWarning: These advanced commands are potentially dangerous; use

them only when directed to do so by Network Appliancepersonnel.

bmc shell*->

bmc shell*-> battery showchemistry :LIONdevice-name :bq20z80expected-load-mw:81id :27100010manufacturer :AVTmanufacture-date:4/9/2007rev_cell :2rev_firmware :200rev_hardware :c0serial :03dcstatus :readytest-capacity :disabledbmc shell*->

bmc shell*-> battery verifyTest passedbmc shell*->

bmc shell*-> exitPress ^G to enter BMC command shellLOADER>


Step 3b): At the bmc shell*-> prompt, enter battery show to display the battery status.

Step 3a): At the bmc shell -> prompt, enter priv set advanced to change to "bmc shell * ->"

Step 3d): At the bmc shell*-> prompt, enter battery verify to make sure all battery parameters are correct.

Step 3e): At the bmc shell*-> prompt, enter exit to return to "LOADER>" prompt.

Step 3c): "status" must indicate "ready" or "charging."

X.Step

STOP

1 Test the Replacement PCM with diagnostics by entering "boot_diags" at the "LOADER>" prompt.2

3 Enter "yes" to the question "OK to run FCAL test in Normal Mode (yes/no) ?"4 If question: "OK to run NVMEM diagnostic (yes/no)? " is displayed, enter "yes"

5 Continue with Section X on next page.

of 16

FAS2020 Appliance: Run Diagnostics (run time 22-25 minutes) Action Description

In the Diagnostic Menu enter "all". ("all" Diag selection provides basic confidence tests of the MB, memory, battery and other internal controllers.)

Review the fcadmin config output from Section IV Step 4. If either FC adapter port, '0a' or '0b' were configured as a "target" port, disconnect the FC cable to that port for the diag tests as the FC test will indicate a false failure.


LOADER> boot_diagsLoading:....0x200000/8638944 0xa3d1e0/3506016 0xd95140/8 Entry at 0x00200000Starting program at 0x00200000

Copyright (c) 1992-2008 Network Appliance, Inc.

Diagnostic Monitorversion: 5.3built: Thu Apr 10 23:00:25 PDT 2008

--------------------------------------all Run all system diagnosticsmb FAS2020 motherboard diagnosticmem Main memory diagnosticcf-card CompactFlash controller diagnosticstress System wide stress diagnostic

Commands:Config (print a list of configured PCI devices)Default (restore all options to default settings)Exit (exit diagnostics)Help (print this commands list)Options (print current option settings)Version (print the diagnostic version)Run <diag ... diag> (run selected diagnostics)

Options:Count <number> (loop selected diagnostic(s) (number) of passes)Loop <yes|no> (loop selected diagnostic(s))Status <yes|no> (print status messages)Stop <yes|no> (stop-on-error / keep running)Xtnd <yes|no> (extended tests / regular tests)Mchk <auto|off|on|halt> (machine check control)Seed <number> (random seed (0:use machine generated number))

Enter Diag, Command or Option: all

NOTE: Disks are not tested in Normal Mode.

To enable Extended Mode, type "xtnd yes" before running the test.

OK to run FCAL test in Normal Mode (yes/no)? yesWARNING! Do not run the NVMEM diagnostic immediately after a

system crash or if there is a possibility that logdata is stored. Run only on new boards, or after anormal system shutdown, or if there is no chance ofpreserving customer data.

OK to run NVMEM diagnostic (yes/no)? yes

STEP 1: Enter "boot_diags"

STEP 2: Enter "all"

STEP 3: Enter: "yes"

STEP 4: Enter: "yes"

X.Step STOP Verify your diagnostic output matches the "DIAGNOSTIC RESULTS CONFIRMATION CHECKS" text box below

6

To view a sample of the complete test output click here > FAS2020 Full Diag Output7 Confirm "BMC" Comprehensive Test show as PASSED. This includes the battery subsystem tests.8 Confirm all the memory was discovered: For a FAS2020 it almost ~ 1GB.9 Test suite completes with "Completed pass 1 date - time" Verify with your output.

10 Enter: exit This exits the diags and system drops to "LOADER>" prompt after 10-20 seconds.

11 Go to Section XI, "Set Fibre Channel (FC) "target" Ports" on next page.

Each test suite ends with a "Comprehensive" test result. Confirm the result shows PASSED or SKIPPED. If any list FAILED, scroll back through your test output to see which test FAILED and call NGS to report the test failure.

of 16

FAS2020 Appliance: Run Diagnostics (cont.) Action Description


FAS2020 Motherboard Diagnostic------------------------------

Performing comprehensive motherboard diagnostic............................................................Environmental check, subsystem: BMC ......... PASSED****** Comprehensive BMC Test ................... PASSED

****** Comprehensive mb test .................... PASSED

Testing : 928 MB (start=4000000, end=38000000)Main Memory Diagnostic----------------------

Performing comprehensive main memory test........****** Comprehensive Memory test ................ PASSED................

--- Completed pass 1. Current date = Wednesday Oct 22 09:45:17 2008

Enter Diag, Command or Option: exit........LOADER>

Step 7: FAS2020 should total almost 1GB.

DIAGNOTIC RESULTS CONFIRMATION CHECKSa) All Comprehensive Tests state: PASSED or SKIPPED ,

no test should indicate FAILED. If so STOP - call NGS!b) BMC Environment Test PASSED -** IMPORTANT

This tests the battery. If the test fails contact NGS and advise you need a replacement battery

c) Verify reported memory size, see belowd) Final output shows “Completed Pass 1 Date - Time”

Step 10: Enter: exit to exit the Diags. The prom will initialize displaying many messages. After about 10-20 seconds, the it will drop to the LOADER> prompt.

Step 8: Test SuiteComplete message

XI.Step

12

NOTE

3 a)

b)

c) Enter '5' for "Maintenance mode boot".d) If asked "Continue with boot?" Answer: "y" to exit to the maintenance mode >*> prompt.

Some newer PCM firmware raises the low threshold voltage for the NVMEM battery or you need to replace the battery.Review the diags output and see if the BMC Environment test failed - Call NGS and advise of issue, noting next line.Under no circumstances bypass the system halt for a low NVRAM battery. The disk reassign or giveback will fail!

4

NOTE

5

6

7 Go to Section XII, "Disk Reassignment on the Replacement PCM" on next page.

If the adapter that needs to be changed to a target, is listed as " online", it must be off-lined first before it can be changed. Issue: fcadmin offline <HA>

If the old motherboard's configuration was not captured in Section IV and the node is HA, execute these commands on the partner node: filer> partner fcadmin config. (This reports the target node's configuration)If not HA, engage NGS to determine the FC Adapter configuration by examining Autosupports at NetApp.

From the LOADER> prompt enter "autoboot" to initiate a prom bootstrap.(Reference the example of an "abbreviated" console screen shot in section IV step 2)

Enter "fcadmin config" again to confirm the FC Adapter(s) that are to be configured as a "target" ports, display "PENDING (target)". Our example shows 0a, 0b.

p p g g g g ( p ) Issue one command for each. Using the sample output from Section IV, this example configures Adapter ports 0a and 0b as targets:

of 16

FAS2020 Appliance: Set Fibre Channel (FC) "target" Ports

At the *> prompt, enter: fcadmin config to view the configuration of the FC Adapters on the Replacement PCM. Since we performed a set-defaults, all should display as "initiators".

Action DescriptionThe console prompt should be the LOADER> prompt if Diags were exited properly.

When this message appears: "Press CTRL-C for special boot menu" , press CTRL-C (^C) to load the "Special boot options menu". After about 30-40 seconds, the "Maintenance menu" will appear.

If either FC cable was disconnected in Section X for the diag tests, reconnect the cables to the correct FC adapter.

STOP

If the autoboot halts with a message: "NVMEM battery voltage is too low or doesn't have adequate charge", STOP!


*> fcadmin config

LocalAdapter Type State Status---------------------------------------------------0a initiator CONFIGURED. offline0b initiator CONFIGURED. offline

*> fcadmin config -t target 0a Tue Jun 26 19:31:30 GMT [fci.config.state:info]: Fibre channel initiator adapter 0a is in the PENDING (target) state.A reboot is required for the new adapter configuration to take effect.

*> fcadmin config -t target 0bTue Jun 26 19:33:01 GMT [fci.config.state:info]: Fibre channel initiator adapter 0b is in the PENDING (target) state.A reboot is required for the new adapter configuration to take effect.

*> fcadmin config

Local Adapter Type State Status---------------------------------------------------0a initiator PENDING (target) offline0b initiator PENDING (target) offline

Step 4: Enter: fcadmin config

Step 5: Enter: fcadmin config -t target <HA>for each port to be configured as a target

Step 6: Enter: fcadmin config to confirm each "target" port is shownas PENDING

XII.Step

12 Open up your console log file to retrieve the original System ID.

3

NOTE

A.A1 Login as "root" to the Partner node. End-user may be required to provide password.

NOTE

A2 Enter: ' priv set advanced ' at the prompt for the following command to work. Prompt will include " * ".A3

A4 A message similar to the one here will be displayed. Enter ' y ' to confirm.

A5 Continue with step 4 on next page.

B.B1

B2 A message similar to the one here will be displayed. Enter ' y ' to confirm.

B3 Continue with step 4 on next page.

At the console prompt enter: ' disk reassign -s <old_system_ID> -d <new_system_ID> '. Cut-n-paste the old and new System IDs from the console Log.

At the maintenance mode " * > " prompt enter: ' disk reassign -s <old_system_ID> -d <new_system_ID> '. Cut-n-paste the old and new System IDs from the console Log.

Single Controller configuration or the partner did NOT takeover. Execute the "B" steps from Maintenance mode on the replacement Controller.

Execute the "A" steps on the partner node. Engage-user to assist and for the password.

The partner console prompt must have the word "(takeover)" in it. If not, verify with end-user or NGS that the takeover did NOT occur. If it did not, use Method B

The disk reassignment process takes several seconds and a message is printed for each disk that is reassigned.

Follow procedure-A if the node was successfully taken over by its partner.Follow procedure-B if this node is a single controller configuration or the partner did NOT takeover.

of 16

FAS2020 Appliance: Disk Reassignment on the Replacement PCM Action DescriptionAt the *> prompt, enter "disk show -v" to display the new system ID and disk assignments. Example below.


*> disk show -v


DISK OWNER POOL SERIAL NUMBER------------ ------------- ----- -------------0c.00.1 fas2020cl1 (135023136) Pool0 5QE4RA7Z 0c.00.4 fas2020cl2 (135023148) Pool0 5QE4RAFA 0c.00.0 fas2020cl2 (135023148) Pool0 5QE4Q5CH 0c.00.6 fas2020cl2 (135023148) Pool0 5QE4RAB1 0c.00.5 fas2020cl1 (135023136) Pool0 5QE4RADS 0c.00.3 fas2020cl1 (135023136) Pool0 5QE4R8Y4 0c.00.7 fas2020cl1 (135023136) Pool0 5QE4RADG 0c.00.8 fas2020cl2 (135023148) Pool0 5QE4Q5CJ 0c.00.9 fas2020cl2 (135023148) Pool0 5QE4RA69 0c.00.2 fas2020cl2 (135023148) Pool0 5QE4RAAG 0c.00.10 fas2020cl2 (135023148) Pool0 5QE4RAHG 0c.00.11 fas2020cl1 (135023136) Pool0 5QE4Q5JL........*>

In this example, the Local System IDfor the new PCM for node "fas2020cl2" is 137053922.

The old System ID (135023148) on disks owned by "fas2020cl2" need to be reassigned to the new Local System ID.

Document Example: *> disk reassign -s 135023148 -d 137053922Disk ownership will be updated on all disks previously belonging to Filer with sysid 135023148.Would you like to continue (y/n)? y

Document Example: partner-systemname(takeover)*> disk reassign -s 135023148 -d 137053922Disk ownership will be updated on all disks previously belonging to Filer with sysid 135023148.Would you like to continue (y/n)? y

Enter ' y '

A console message will be displayed for each disk changing ownership (System ID)

Enter ' y '

A console message will be displayed for each disk changing ownership (System ID)

XII.Step

4

5 At the maintenance mode prompt: " * >" , enter ' halt ' to exit to " LOADER> ".6 Go to Section XIII, "Boot the Operating System" on next page.

STOP!

of 16

FAS2020 Appliance: Disk Reassignment on the Replacement PCM (cont.) Action DescriptionFrom the console port on controller you replaced (in maintenance mode): Enter ' disk show -v ' to display the disks reassigned to the new System ID.

Verify the system-id for this node's disks listed under "OWNER" and the "Local System ID" are the same. If not, confirm the correct system-ids were entered on the disk reassign. If problems, call NGS for assistance.

*> disk show -v


DISK OWNER POOL SERIAL NUMBER------------ --------------- ----- -------------0c.00.1 fas2020cl1 (135023136) Pool0 5QE4RA7Z

0c.00.4 (137053922) Pool0 5QE4RAFA

0c.00.0 (137053922) Pool0 5QE4Q5CH

0c.00.6 (137053922) Pool0 5QE4RAB1

0c.00.5 fas2020cl1 (135023136) Pool0 5QE4RADS

0c.00.3 fas2020cl1 (135023136) Pool0 5QE4R8Y4

0c.00.7 fas2020cl1 (135023136) Pool0 5QE4RADG

0c.00.8 (137053922) Pool0 5QE4Q5CJ

0c.00.9 (137053922) Pool0 5QE4RA69

0c.00.2 (137053922) Pool0 5QE4RAAG

0c.00.10 (137053922) Pool0 5QE4RAHG

0c.00.11 fas2020cl1 (135023136) Pool0 5QE4Q5JL ........

*> halt


The new Local System ID for the PCM is 137053922. The owner name "fas2020cl2" may or may not be shown. But those disks should reflect the new Local System ID.

Step 5: Enter "halt" to exit to the "LOADER>" prompt

XIII.Step

1 At the "LOADER>" prompt, enter "autoboot" to boot Data Ontap.

STOP

2 (i)

(ii)

NOTE:

A. Example: Complete boot ( node operating in stand-alone mode)

B. Example: Partial boot (node is part of a cluster and was taken over by its partner)

3 Go to Section XIV, "New controller registration, Submit logs and Part Return" on the next page.

of 16

FAS2020 Appliance: Boot the Operating System Action Description

While the system is booting, visually confirm the "link" (typically green) LEDs are lit on all FCAL HA cable connections on the controller that have a cable in them to verify the cable (and GBIC) are properly seated. FC Adapters configured as targets and Ethernet link LEDs will turn ON when the system is almost UP.

If the node autoboots to a login prompt (hit <enter> for response) - see "A. Example" below - the node is operating in stand-alone mode; (Stand-Alone: Single node in chassis, or no partner takeover occurred), then skip to Step 3.If the node displays "Press Ctrl-C for Maintenance menu to release disks" and "Waiting for giveback" after the <enter> key is hit - see "B. Example" below - this node was taken over by its partner node. Login into the PARTNER node if it's password is known (or engage the system admin), issue a 'cf giveback' - READ text box Note B.1.

A successful giveback will display "giveback completed" and remove the word "takeover" from the prompt.

AMI BIOS8 Modular BIOSCopyright (C) 1985-2006, American Megatrends, Inc. All Rights Reserved BIOS Version 3.0................Boot Loader version 1.3 ..........CPU Type: Mobile Intel(R) Celeron(R) CPU 2.20GHz

Starting AUTOBOOT press Ctrl-C to abort...

Press CTRL-C for special boot menu................Thu Jul 31 12:42:04 PDT [mgr.boot.disk_done:info]: NetApp Release 7.2.4L1P3D2 boot complete.Data ONTAP (fas2020cl2)login:


These are sometypical Boot strap

console messages.If the node is operating in stand-alone

mode, you should eventually get a "login" prompt when

you hit <enter>.

.... Many typical system startup messages removed for clarity

LOADER> LOADER> autoboot

AMI BIOS8 Modular BIOSCopyright (C) 1985-2006, American Megatrends, Inc. All Rights Reserved BIOS Version 3.0................Boot Loader version 1.3 ..........Starting AUTOBOOT press Ctrl-C to abort...

Press CTRL-C for special boot menu........

Press Ctrl-C for Maintenance menu to release disks.

Waiting for giveback

".…" = Deleted lines to save space

NOTE B.1:If you see this message, this node is part of a HA configuration and the partner node took over for it.

If the "cf giveback" fails due to partner "not ready", wait 5 minutes for the NVMEMs to synchronize. If the giveback fails due to "open CIFS sessions", failed disks or for any other reason, contact NGS.

STEP 2(ii): Will get this response after hitting <enter>

XIV.Step

1

2 Email the console log with the NetApp Reference Number in the Subject Line to [email protected] Follow the return shipping instructions on the box to ship the part(s) back to NetApp’s RMA processing center. If the

shipping label is missing see process to obtain a shipping label here >>Missing Shipping Label?56

Verify with customer that the system is OK and call NGS to be released from the dispatch.Call NGS Partner IVR and close out dispatch per Rules of Engagement.

If the target system is UP, request end-user to send NetApp an Autosupport so the configuration setup can be verified and the new system serial number registered by NGS. Use the following command: filer> options autosupport.doit <enter NetApp FSO/case # here> without the < > brackets(The FSO number is 7 digits and begins with 5xxxxxx. Case numbers are ten digits and begin with 2xxxxxxxxx)

of 16

FAS2020 Appliance: New controller registration, Submit logs and Part Return Action Description

Place the defective Controller Module in antistatic bag and seal the box.


mailto:[email protected]�

netapp - the nvmem led on the faceplate will start ...for netapp authorized service engineers -2 a...

Documents