FAS3210 to 2x DS4324 cable setup

aaronswtelogis — Wed, 04 Jun 2025 22:09:43 GMT

Hello

I need help with cabling. Will the Universal Cable setup be appropriate here? On pg 48 of this guide, I am seeing what I think is the likely setup: https://library.netapp.com/ecm/ecm_get_file/ECMM1280392

I've inherited a storage unit, a FAS3210 with dual-controller and 2x DS4324s. This is version 8.0.2P4 7-Mode.

Seeing a few of (bad) things fron console connection, but the biggest concern is the controllers not seeing disks. I am certain this is a cabling issue.

I've read a few blogs that suggest factory reset, however the remote admin (and I agree with him) says that the setup was working before, it would be better not to do this --basically re-cable, everything should work fine.

Any help on this would be appreciated.

thanks

Re: FAS3210 to 2x DS4324 cable setup

aaronswtelogis — Wed, 03 Feb 2016 23:59:01 GMT

using the cabling setup from cabling guide https://library.netapp.com/ecm/ecm_get_file/ECMM1280392 working from pg 41 '32xx or FAS8020 single-chassis multipath HA'.

However I am not seeing anything in maintenance mode. No shelves -- there are two. No drives.

I am happy to relay diagnostics on this.

I've already re-seated controller and DIMMs to handle a panic error.

I've tried a couple of different cable setups. The one described in the link seems most likely, however I am not confident this is the correct setup. Any help on this would be appreciated.

thanks

Re: FAS3210 to 2x DS4324 cable setup

aborzenkov — Thu, 04 Feb 2016 04:12:15 GMT

Copy paste exact commands you use to check for drives and their output.

Re: FAS3210 to 2x DS4324 cable setup

aaronswtelogis — Thu, 04 Feb 2016 17:55:17 GMT

thanks for the reply

I reseated the RAM for either controller -- the CPU/Panic error is back.

I also the see PS2 error -- this just happened yesterday as well. Reseated PS, the error is still present.

Let me know what other diagnostics I can provide. In and out of DC, will check email as often as I can.

Phoenix TrustedCore(tm) Server
Copyright 1985-2006 Phoenix Technologies Ltd.
All Rights Reserved
BIOS version: 5.1.1
Portions Copyright (c) 2007-2011 NetApp, Inc. All Rights Reserved

CPU = 1 Processors Detected, Cores per Processor = 2
Intel(R) Xeon(R) CPU E5220 @ 2.33GHz
Testing RAM
512MB RAM tested
5120MB RAM installed
6144 KB L2 Cache
System BIOS shadowed
USB 2.0: MICRON eUSB DISK
BIOS is scanning PCI Option ROMs, this will take few seconds...
+++++++++++++++++++

CPU Type: Intel(R) Xeon(R) CPU E5220 @ 2.33GHz

Starting AUTOBOOT press Ctrl-C to abort...
Loading X86_64/freebsd/image1/kernel:0x100000/3401320 0x53f000/3229520 0x853750/1227824 Entry at 0x80148a80
Loading X86_64/freebsd/image1/platform.ko:0x980000/569180 0xab4480/535320 0xa0af60/17256 0xb36f98/29808 0xa0f2c8/1360 0xb3e408/4080 0xa0f818/54268 0xa1cc18/71003 0xa2e178/1504 0xb3f3f8/4512 0xa2e758/256 0xb40598/768 0xa2e858/968 0xb40898/2904 0xa2ec20/112 0xb413f0/336 0xa2eca0/137088 0xb41540/142200 0xa50420/425 0xa75c60/8377 0xab4392/237 0xa77d20/126120 0xa969c8/121290
NetApp Data ONTAP 8.0.2P4 7-Mode

PANIC: The 0 is not a supported platform

version: NetApp Release 8.0.2P4: Tue Nov 15 16:16:47 PST 2011
cpuid = 0
Uptime: 1s

The operating system has halted.
Please press any key to reboot.

System halting...
cpu_reset called on cpu#0

Phoenix TrustedCore(tm) Server
Copyright 1985-2006 Phoenix Technologies Ltd.
All Rights Reserved
BIOS version: 5.1.1
Portions Copyright (c) 2007-2011 NetApp, Inc. All Rights Reserved

* *

^CBoot Menu will be available.

Please choose one of the following:

(1) Normal Boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
Selection (1-8)? 5
Chelsio T3 RDMA Driver - version 0.1
Ipspace "iwarp-ipspace" created
Sat Mar 31 00:02:00 GMT [callhome.chassis.ps.off:error]: Call home for CHASSIS POWER SUPPLY OFF: PS 2
Sat Mar 31 00:02:00 GMT [monitor.chassisPowerSupply.off:notice]: Chassis power supply 2 off
Sat Mar 31 00:02:07 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0c.
Sat Mar 31 00:02:07 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0d.
Sat Mar 31 00:02:07 GMT [netif.linkDown:info]: Ethernet Wrench Port: Link down, check cable.
Sat Mar 31 00:02:16 GMT [diskown.isEnabled:info]: software ownership has been enabled for this system
arp_rtrequest: bad gateway 127.0.20.1 (!AF_LINK)
add host 127.0.10.1: gateway 127.0.Sat Mar 31 00:02:16 GMT [monitor.chassisPower.degraded:notice]: Chassis power is degraded:
Sat Mar 31 00:02:16 GMT [callhome.chassis.power:error]: Call home for CHASSIS POWER DEGRADED:
20.1
5

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

? disk
key_manager fcadmin
fcstat sasadmin
sasstat acpadmin
halt help
ifconfig raid_config
storage sesdiag
sysconfig vmservices
version vol
aggr sldiag
dumpblock environment
systemshell vol_db
led_on led_off
sata acorn
scsi nv8
disk_list ha-config
fctest disktest
diskcopy vsa
xortest faltest
disk_mung

Type "help <command>" for more details.

In a High Availablity configuration, you MUST ensure that the
partner node is (and remains) down, or that takeover is manually
disabled on the partner node, because High Availability
software is not started or fully enabled in Maintenance mode.

FAILURE TO DO SO CAN RESULT IN YOUR FILESYSTEMS BEING DESTROYED

NOTE: It is okay to use 'show/status' sub-commands such as
'disk show or aggr status' in Maintenance mode while the partner is up
Continue with boot? y
y

Sat Mar 31 00:02:21 GMT [mgr.boot.reason_ok:notice]: System rebooted.
Sat Mar 31 00:02:21 GMT [callhome.reboot.unknown:info]: Call home for REBOOT
Ipspace "acp-ipspace" created
Sat Mar 31 00:02:24 GMT [netif.linkUp:info]: Ethernet e0P: Link up.
Sat Mar 31 00:02:28 GMT [netif.linkDown:info]: Ethernet e0b: Link down, check cable.
Sat Mar 31 00:02:28 GMT [netif.linkDown:info]: Ethernet e0a: Link down, check cable.
Sat Mar 31 00:02:30 GMT [netif.linkDown:info]: Ethernet e0M: Link down, check cable.
Sat Mar 31 00:02:32 GMT [netif.linkDown:info]: Ethernet e1a: Link down, check cable.
Sat Mar 31 00:02:32 GMT [netif.linkDown:info]: Ethernet e1b: Link down, check cable.
filter sync'd

Sat Mar 31 00:02:34 UTC 2007
Sat Mar 31 00:02:34 GMT [sas.link.error:error]: Could not recover link on SAS adapter 0a after 30 seconds. Offlining the adapter.
Sat Mar 31 00:02:34 GMT [sas.link.error:error]: Could not recover link on SAS adapter 0b after 30 seconds. Offlining the adapter.
Sat Mar 31 00:02:34 GMT [console_login_mgr:info]: root logged in from console
*> Sat Mar 31 00:02:34 GMT [rlmauth_login_mgr:info]: root logged in from SP

sysconfig -v
Sat Mar 31 00:02:59 GMT [shelf.config.unknown:info]: System storage configuration is unknown
NetApp Release 8.0.2P4 7-Mode: Tue Nov 15 16:16:47 PST 2011
System ID: 1574125760 (); partner ID: 1574172085 ()
System Serial Number: 700000731045 ()
System Rev: F3
System Storage Configuration: Unknown
System ACP Connectivity: NA
slot 0: System Board 2.3 GHz (System Board XVI F3)
Model Name: FAS3210
Part Number: 111-00585
Revision: F3
Serial Number: 5003839361
BIOS version: 5.1.1
Loader version: 3.2
Processors: 2
Processor type: Intel(R) Xeon(R) CPU E5220 @ 2.33GHz
Memory Size: 5120 MB
Memory Attributes: Bank Interleaving
Hoisting
Rank Interleaving
Normal ECC
NVMEM Size: 640 MB of Main Memory Used
CMOS RAM Status: OK
Service Processor Status: Unknown
IPMI: unknown
PKT: unknown
slot 0: Internal BGE 10/100 Ethernet Controller
e0M MAC Address: 00:a0:98:17:36:fc (auto-unknown-down)
e0P MAC Address: 00:a0:98:17:36:fd (auto-100tx-fd-up)
Device Type: BCM5721
slot 0: Dual 10G Ethernet Controller T320E-SFP/KR
Device Type: CT-FE-3
Version Number: T3-SRAM1.1.0-BR1016-02-01-FW7.7.192-DR04
Serial Number: jb04050693
c0a MAC Address: 00:a0:98:17:36:fa (auto-unknown-enabling)
c0b MAC Address: 00:a0:98:17:36:fb (auto-unknown-enabling)
slot 0: Dual 10/100/1000 Ethernet Controller G20
e0a MAC Address: 00:a0:98:17:36:f8 (auto-unknown-down)
e0b MAC Address: 00:a0:98:17:36:f9 (auto-unknown-down)
Device Type: Rev 6
slot 0: SAS Host Adapter 0a (PMC-Sierra PM8001 rev. C, SAS, <OFFLINE (hard)>)
Firmware rev: 01.11.00.00
Base WWN: 5:00a098:00014a6:10
Phy State: [0] Enabled, Rate unknown
[1] Enabled, Rate unknown
[2] Enabled, Rate unknown
[3] Enabled, Rate unknown
QSFP Vendor: Molex Inc.
QSFP Part Number: 112-00178+A0
QSFP Type: Passive Copper 5m ID:00
QSFP Serial Number: 115120221
slot 0: SAS Host Adapter 0b (PMC-Sierra PM8001 rev. C, SAS, <OFFLINE (hard)>)
Firmware rev: 01.11.00.00
Base WWN: 5:00a098:00014a6:14
Phy State: [4] Enabled, Rate unknown
[5] Enabled, Rate unknown
[6] Enabled, Rate unknown
[7] Enabled, Rate unknown
QSFP Vendor: Molex Inc.
QSFP Part Number: 112-00177+A0
QSFP Type: Passive Copper 2m ID:00
QSFP Serial Number: 111620428
slot 0: Intel ICH USB EHCI Adapter u0a (0xdff01400)
boot0 Micron Technology Real SSD eUSB 2GB, rev 2.00/11.10, addr 2 1936MB 512B/sect (4DF0022700110402)
slot 0: FC Host Adapter 0c (QLogic 2432 rev. 2, L-port, <OFFLINE (hard)>)
Firmware rev: 5.4.0
Host Loop Id: 0
FC Node Name: 5:00a:098000:14a608
FC Port Name: 5:00a:098000:14a608
Sat Mar 31 00:03:03 GMT [callhome.chassis.ps.off:error]: Call home for CHASSIS POWER SUPPLY OFF: PS 2
Sat Mar 31 00:03:03 GMT [monitor.chassisPowerSupply.off:notice]: Chassis power supply 2 off
SFP Vendor: FINISAR CORP.
SFP Part Number: FTLF8524P2BNV
SFP Serial Number: PK84E58
SFP Capabilities: 1, 2 or 4 Gbit
Link Data Rate: N/A
slot 0: FC Host Adapter 0d (QLogic 2432 rev. 2, L-port, <OFFLINE (hard)>)
Firmware rev: 5.4.0
Host Loop Id: 0
FC Node Name: 5:00a:098100:14a608
FC Port Name: 5:00a:098100:14a608
SFP Vendor: FINISAR CORP.
SFP Part Number: FTLF8524P2BNV
SFP Serial Number: PK84FCL
SFP Capabilities: 1, 2 or 4 Gbit
Link Data Rate: N/A
slot 1: Dual 10G Ethernet Controller T320E-SFP+
Device Type: CT-31-3
Version Number: T3-SRAM1.1.0-BR1114-30-A0-FW7.7.192-DR04
Serial Number: PT19110261
e1a MAC Address: 00:07:43:07:95:81 (auto-unknown-down)
e1b MAC Address: 00:07:43:07:95:82 (auto-unknown-down)
*> storage show disk -p
PRIMARY PORT SECONDARY PORT SHELF BAY
------- ---- --------- ---- ---------
*> Sat Mar 31 00:03:15 GMT [netif.linkUp:info]: Ethernet c0b: Link up.
Sat Mar 31 00:03:17 GMT [netif.linkDown:info]: Ethernet c0b: Link down, check cable.

*> storage show expander
No expanders found.
*> storage show
Slot: 0a
Description: SAS Host Adapter 0a (PMC-Sierra PM8001 rev. C)
Firmware Rev: 01.11.00.00
Base WWN: 5:00a098:00014a6:10
State: Disabled
In Use: No
Redundant: Yes
Phy State: [0] Enabled, rate unknown (0)
[1] Enabled, rate unknown (0)
[2] Enabled, rate unknown (0)
[3] Enabled, rate unknown (0)

Slot: 0b
Description: SAS Host Adapter 0b (PMC-Sierra PM8001 rev. C)
Firmware Rev: 01.11.00.00
Base WWN: 5:00a098:00014a6:14
State: Disabled
In Use: No
Redundant: Yes
Phy State: [0] Enabled, rate unknown (0)
[1] Enabled, rate unknown (0)
[2] Enabled, rate unknown (0)
[3] Enabled, rate unknown (0)

Slot: 0c
Description: Fibre Channel Host Adapter 0c (QLogic 2432 rev. 2)
Firmware Rev: 5.4.0
FC Node Name: 5:00a:098000:14a608
FC Port Name: 5:00a:098000:14a608
FC Packet Size: 2048
Link Data Rate: N/A
SRAM Parity: Yes
External GBIC: No
State: Disabled
In Use: No
Redundant: Yes

Slot: 0d
Description: Fibre Channel Host Adapter 0d (QLogic 2432 rev. 2)
Firmware Rev: 5.4.0
FC Node Name: 5:00a:098100:14a608
FC Port Name: 5:00a:098100:14a608
FC Packet Size: 2048
Link Data Rate: N/A
SRAM Parity: Yes
External GBIC: No
State: Disabled
In Use: No
Redundant: Yes

No hubs found.

No expanders found.

DISK SHELF BAY SERIAL VENDOR MODEL REV
--------------------- --------- ---------------- -------- ---------- ----

SHARED STORAGE HOSTNAME SYSTEM ID
------------------------- ----------
*> Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Over Curr is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Over Volt is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Over Temp is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fault is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 DC OK is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 On is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fan2 Fault is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fan2 Speed is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fan1 Fault is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Fan1 Speed is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Current is Unreadable
Sat Mar 31 00:04:11 GMT [monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 Temperature is Unreadable

*> sasadmin expander 0a
Cannot Complete operation on channel 0a; Status Not Available.
sasadmin expander: failed.
*> sasadmin expander 0b
Cannot Complete operation on channel 0b; Status Not Available.
sasadmin expander: failed.
*> environment shelf_logSat Mar 31 00:04:59 GMT [netif.linkUp:info]: Ethernet c0b: Link up.

SES shelf information is not available
*> Sat Mar 31 00:05:00 GMT [netif.linkDown:info]: Ethernet c0b: Link down, check cable.

*> environment shelf_log
SES shelf information is not available
*>

*> storage show fault
Storage subsystem fault information is not available
*> storage trace info all
Adapter Interface Type Module ID Module Instance Trace State Buffer Size
----------------------------------------------------------------------------------------------
0c FC_L_PORT 7 0 ACTIVE 500
0d FC_L_PORT 7 1 ACTIVE 500

TRACE ID NAME TRACE ID TRACE ID ON? Trace Level Trace Cat
---------------------------------------------------------------------------------------------------
TRACE_ID_FCAL_SOFT_ADDR 0 1 0 2000h
TRACE_ID_FCAL_TASK_MGMT 1 1 0 1h
TRACE_ID_FCAL_LOGIN_INITIATE 2 1 0 1h
TRACE_ID_FCAL_LOGIN_DONE 3 1 0 1h
TRACE_ID_FCAL_LOGIN_FAILURE 4 1 0 2000h
TRACE_ID_FCAL_IO_QUIESCE 5 1 0 8000h
TRACE_ID_FCAL_INVALIDATE_DEBOUNCE 6 1 0 1h
TRACE_ID_FCAL_DEV_EXISTS 7 1 0 1h
TRACE_ID_FCAL_DEV_CAME_BACK 8 1 0 1h
TRACE_ID_FCAL_DEV_INVALIDATE_DONE 9 1 0 1h
TRACE_ID_FCAL_IO_TIMEOUT 10 1 0 1h
TRACE_ID_FCAL_MAP 11 1 0 1h
TRACE_ID_FCAL_ADAPTER_ERROR 12 1 0 2000h
TRACE_ID_FCAL_ADAPTER_WARNING 13 1 0 8000h
TRACE_ID_FCAL_ASYNC_EVENT 14 1 0 1h

SES Class Driver Trace State Buffer Size
----------------------------------------------
ACTIVE 500

TRACE ID NAME TRACE ID TRACE ID ON? Trace Level Trace Cat
---------------------------------------------------------------------------------------------------
TRACE_ID_SES_DRV_SFW_SIGNAL_TRACE 0 1 0 1h
TRACE_ID_SES_DRV_SFW_STATE_TRANSITION 1 1 0 1h
TRACE_ID_SES_DRV_SFW_START_UPDATE 2 1 0 1h
TRACE_ID_SES_DRV_SCAN_DONE

Re: FAS3210 to 2x DS4324 cable setup

aborzenkov — Fri, 05 Feb 2016 06:34:53 GMT

It sounds like you have SP problem. Can you get into SP from serial console (Ctrl-G)?

Re: FAS3210 to 2x DS4324 cable setup

aaronswtelogis — Fri, 05 Feb 2016 12:18:33 GMT

Hello

Yes. That's how I was able to get the diagnostics. The array is caught in a loop.

Re: FAS3210 to 2x DS4324 cable setup

aaronswtelogis — Fri, 05 Feb 2016 16:47:33 GMT

got it too boot -- universal cable guide worked. on to addressing power supply 2 and recurring panic

topic Re: FAS3210 to 2x DS4324 cable setup in ONTAP Hardware

FAS3210 to 2x DS4324 cable setup

Re: FAS3210 to 2x DS4324 cable setup

Re: FAS3210 to 2x DS4324 cable setup

Re: FAS3210 to 2x DS4324 cable setup

Re: FAS3210 to 2x DS4324 cable setup

Re: FAS3210 to 2x DS4324 cable setup

Re: FAS3210 to 2x DS4324 cable setup