ONTAP Discussions

NetApp Controller FAS 3140 is geting panic.

VIKAS_MAURYA
4,073 Views

Hello All,

NetApp FAS 3140 is getting panic and generating the following logs while running the diagnostic.

RLM Asi> system console
Type Ctrl-D to exit.

Invalid command: "ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ"
Available commands: version, update_flash, netboot, boot_diags, boot_backup, boot_primary, boot_ontap, flash, bye, set, lsmod, autoboot, go, boot, load, ndp, ping, arp, ifconfig, show, savenv, saveenv, unsetenv, set-defaults, setenv, printenv, help

*** command status = -1
LOADER-A>
LOADER-A>
LOADER-A> ?
Invalid command: "?"
Available commands: version, update_flash, netboot, boot_diags, boot_backup, boot_primary, boot_ontap, flash, bye, set, lsmod, autoboot, go, boot, load, ndp, ping, arp, ifconfig, show, savenv, saveenv, unsetenv, set-defaults, setenv, printenv, help

*** command status = -1
LOADER-A> version

Variable Name        Value
-------------------- --------------------------------------------------
BIOS_VERSION         4.4.0
LOADER_VERSION       1.8
LOADER-A> sldiag
Invalid command: "sldiag"
Available commands: version, update_flash, netboot, boot_diags, boot_backup, boot_primary, boot_ontap, flash, bye, set, lsmod, autoboot, go, boot, load, ndp, ping, arp, ifconfig, show, savenv, saveenv, unsetenv, set-defaults, setenv, printenv, help

*** command status = -1
LOADER-A> boot_diags
Loading x86_64/diag/diag.krn:...0x200000/13263960 0xea6458/9332576 0x178cbb8/8 Entry at 0x00202018
Starting program at 0x00202018
hcr fields values
in_param = 0x0
input_modifier = 0x80000000
out_param = 0x100
token = 0x1234
opcode = 0x1
opcode modifier = 0x0
e = 0
go = 0
status = 0x7
NVRAM DDR memory error - you may have a bad NVRAM DIMM
THH_hob_create: CMD_error in THH_cmd_SYS_EN (7)
Please try powercycling the system. If the problem persists, please replace the motherboard.
========= go bit analysys =================
up to 2500 clocks: 0 counts
up to 5000 clocks: 0 counts
up to 10000 clocks: 0 counts
up to 20000 clocks: 0 counts
up to 50000 clocks: 0 counts
up to 100000 clocks: 0 counts
up to 4294967295 clocks: 0 counts
total counts=0


Copyright (c) 1992-2011 NetApp.
init mca for BSP


WARNING : Memory interleaving disabled


Diagnostic Monitor
version: 5.7.1
   built: Wed Sep  5 00:44:24 PDT 2012
--------------------------------------
all     Run all system diagnostics
mb      FAS3140 motherboard diagnostic
mem     Main memory diagnostic
agent   agent & rlm diagnostic
cf-card CompactFlash controller diagnostic
sas     SAS controller diagnostic
fCache  Flash Cache diagnostic
stress  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)
Cpu     <0|1> (default cpu)
Seed    <number> (random seed (0:use machine generated number))

Enter Diag, Command or Option: all
|
NOTE: Disks are not tested in Normal Mode.

Please help on this.

2 REPLIES 2

aborzenkov
4,073 Views

You are in diagnostic monitor now. You can find documentation here: https://library.netapp.com/ecmdocs/ECMP1112531/html/index.htm.

Marcin
3,614 Views

Hello

 

NVRAM mem DIMM is defect.

 

You should replace this with new one and run diag to check system status after repalce.

 

Regards

Marcin

Public