| Asset ID: |
1-79-2077216.1 |
| Update Date: | 2018-05-09 |
| Keywords: | |
Solution Type
Predictive Self-Healing Sure
Solution
2077216.1
:
Fujitsu M10-1/M10-4/M10-4S Servers: Integration of an Flash Accelerator F160 NVMe Card (Aura 3 NVMe) at a glance
| Related Items |
- Fujitsu M10-4
- Fujitsu M10-1
- Fujitsu M10-4S
|
| Related Categories |
- PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Fujitsu M10
|
Applies to:
Fujitsu M10-1
Fujitsu M10-4
Fujitsu M10-4S
Information in this document applies to any platform.
Purpose
The PCI Express "Flash Accelerator F160 NVMe Card" (F160 card) codename "Aura 3 NVMe" is a 1.6TB Solid State Drive (SSD)
card. NVMe stands for Non-Volatile Memory express. This document outlines the requirements for operating an F160 card
specifically on M10-Series. There are requirements for the F160 card's Firmware Version and the Solaris Operating System.
This document also shows some command outputs that inform whether the F160 Card is well integrated.
Details
Documentation
The F160 card's information in the Oracle System Handbook is https://support.oracle.com/handbook_private/Devices/SCSI/SCSI_Flash_Accel_F160.html.
The associated Documentation Library is http://www.oracle.com/goto/oracleflashf160/docs.
Required Firmware Version and Solaris Operating System
The Firmware and Solaris OS requirements are mentioned in the Documentation Library's Product Notes of the F160 card
The patch numbers 21683464, 21683470, and 21683474 cover the Drive Firmware Version 8DV1RA13.
# unzip -t p21683474_1300_Generic.zip
Archive: p21683474_1300_Generic.zip
testing: 8DV1RA13_8B1B012E_signed.bin OK
testing: README.txt OK
testing: license.txt OK
No errors detected in compressed data of p21683474_1300_Generic.zip.
"Solaris 11 SRU 14" (Support Repository Update) as mentioned above means SRU 11.2.14.5.0 which is the first SRU 11.2.14.*
with Solaris 11.2. See also the Oracle Solaris 11.2 SRU Index, Doc# 1672221.1.
An M10-4S PPAR where the requirements do not meet
In case the Solaris OS and Firmware requirements do not meet you might see similar information as shown in the
following example on an M10-4S PPAR with Solaris 11.2.2.8.0 where finally no F160 card is visible in 'format'...
# pkg info -l entire fwupdate |egrep "Name:|Summary:|Version:|FMRI:"
Name: entire
Summary: entire incorporation including Support Repository Update (Oracle Solaris 11.2.2.8.0).
Version: 0.5.11 (Oracle Solaris 11.2.2.8.0)
FMRI: pkg://solaris/entire@0.5.11,5.11-0.175.2.2.0.8.0:20140926T190209Z
Name: system/management/fwupdate
Summary: Oracle Hardware Management Pack - fwupdate
Version: 2.2.8
FMRI: pkg://solaris/system/management/fwupdate@2.2.8,5.11-0.175.2.2.0.4.0:20140829T201741Z
# vi messages
45 Oct 6 22:12:03 <M10-4S Host-1> pcie: [ID 661617 kern.notice] NOTICE: pciehpc (pcieb50): card is inserted in the slot BB#1-PCI#1
46 Oct 6 22:12:11 <M10-4S Host-1> nvme: [ID 199988 kern.warning] WARNING: Fail to attach: 8192 page size is not supported by the controller.
47 Oct 6 22:12:11 <M10-4S Host-1> genunix: [ID 646827 kern.warning] WARNING: (pcieb50): failed to attach driver for a device (nvme-1) under the Connection BB#1-PCI#1
48 Oct 6 22:12:44 <M10-4S Host-1> pcie: [ID 661617 kern.notice] NOTICE: pciehpc (pcieb10): card is inserted in the slot BB#0-PCI#1
49 Oct 6 22:12:50 <M10-4S Host-1> nvme: [ID 199988 kern.warning] WARNING: Fail to attach: 8192 page size is not supported by the controller.
50 Oct 6 22:12:50 <M10-4S Host-1> genunix: [ID 646827 kern.warning] WARNING: (pcieb10): failed to attach driver for a device (nvme-1) under the Connection BB#0-PCI#1
138 Oct 6 23:11:23 <M10-4S Host-1> genunix: [ID 540533 kern.notice] SunOS Release 5.11 Version 11.2 64-bit
955 Oct 6 23:13:44 <M10-4S Host-1> nvme: [ID 199988 kern.warning] WARNING: Fail to attach: 8192 page size is not supported by the controller.
# egrep -i "^ Id|nvme|blkdev" sysconfig/modinfo.out
Id Loadaddr Size Info Rev Module Name
198 7bb82000 c128 152 1 nvme (NVMExpress HBA driver)
199 7bb0c000 3340 12 1 blkdev (Generic Block Device)
# echo | format ==> Not any /<...>/nvme@0/disk@1
# grep nvme /etc/path_to_inst ==> ids as device-id, etc. indicate an incomplete integration of the F160 card(s)
"/pci@8100/pci@4/pci@0/pci@8/pciex108e,370b@0" 1 "nvme"
"/pci@8100/pci@4/pci@0/pci@8/pciex8086,953@0" 2 "nvme"
"/pci@8d00/pci@4/pci@0/pci@8/pciex108e,370b@0" 0 "nvme"
"/pci@8d00/pci@4/pci@0/pci@8/pciex8086,953@0" 3 "nvme"
# fwupdate list controller
ERROR: platform not supported
Other commands as 'prtconf -vp', 'cfgadm -alv', etc. will simply confirm that the F160 cards are not fully integrated.
The Oracle Hardware Management Pack (OHMP) that also includes the /usr/sbin/fwupdate is bundled with Solaris 11.2.
An M10-4S PPAR where the requirements do meet
In case the Solaris OS and Firmware requirements do meet the F160 card(s) will be fully integrated. The following is
on an M10-4S PPAR with SRU 11.2.15.4.0
# pkg info -l entire fwupdate |egrep "Name:|Summary:|Version:|FMRI:"
Name: entire
Summary: entire incorporation including Support Repository Update (Oracle Solaris 11.2.15.4.0).
Version: 0.5.11 (Oracle Solaris 11.2.15.4.0)
FMRI: pkg://solaris/entire@0.5.11,5.11-0.175.2.15.0.4.0:20150923T161056Z
Name: system/management/fwupdate
Summary: Oracle Hardware Management Pack - fwupdate
Version: 2.3.3.0
FMRI: pkg://solaris/system/management/fwupdate@2.3.3.0,5.11-0.175.2.14.0.2.0:20150813T225439Z
# vi messages
857 Nov 3 20:20:57 <M10-4S Host-2> genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11 Version 11.2 64-bit
1336 Nov 3 20:23:35 <M10-4S Host-2> blkdev: [ID 348765 kern.info] Block device: disk@1, blkdev0
1337 Nov 3 20:23:35 <M10-4S Host-2> genunix: [ID 936769 kern.info] blkdev0 is /pci@8200/pci@4/pci@0/pci@8/nvme@0/disk@1
1338 Nov 3 20:23:35 <M10-4S Host-2> genunix: [ID 408114 kern.info] /pci@8200/pci@4/pci@0/pci@8/nvme@0/disk@1 (blkdev0) online
1339 Nov 3 20:23:35 <M10-4S Host-2> pcieb: [ID 586369 kern.info] PCIE-device: nvme@0, nvme0
1340 Nov 3 20:23:35 <M10-4S Host-2> genunix: [ID 936769 kern.info] nvme0 is /pci@8200/pci@4/pci@0/pci@8/nvme@0
1363 Nov 3 20:23:36 <M10-4S Host-2> blkdev: [ID 348765 kern.info] Block device: disk@1, blkdev1
1364 Nov 3 20:23:36 <M10-4S Host-2> genunix: [ID 936769 kern.info] blkdev1 is /pci@8200/pci@4/pci@0/pci@9/nvme@0/disk@1
1365 Nov 3 20:23:36 <M10-4S Host-2> genunix: [ID 408114 kern.info] /pci@8200/pci@4/pci@0/pci@9/nvme@0/disk@1 (blkdev1) online
1366 Nov 3 20:23:36 <M10-4S Host-2> pcieb: [ID 586369 kern.info] PCIE-device: nvme@0, nvme1
1367 Nov 3 20:23:36 <M10-4S Host-2> genunix: [ID 936769 kern.info] nvme1 is /pci@8200/pci@4/pci@0/pci@9/nvme@0
# echo | format ==>
8. c2t1d0 <INTEL-SSDPEDME016T4S-8DV1 cyl 63589 alt 2 hd 256 sec 192>
/pci@8200/pci@4/pci@0/pci@8/nvme@0/disk@1
/dev/chassis/SYS/BB#0-PCI#4/NVME/disk
9. c8t1d0 <INTEL-SSDPEDME016T4S-8DV1 cyl 63589 alt 2 hd 256 sec 192>
/pci@8200/pci@4/pci@0/pci@9/nvme@0/disk@1
/dev/chassis/SYS/BB#0-PCI#5/NVME/disk
# grep nvme /etc/path_to_inst
"/pci@8200/pci@4/pci@0/pci@8/nvme@0" 0 "nvme"
"/pci@8200/pci@4/pci@0/pci@8/nvme@0/disk@1" 0 "blkdev"
"/pci@8200/pci@4/pci@0/pci@9/nvme@0" 1 "nvme"
"/pci@8200/pci@4/pci@0/pci@9/nvme@0/disk@1" 1 "blkdev"
The OHMP Utility 'fwupdate' is also covered in the explorer data.
sysconfig/fwupdate_list_all.out ==>
ID Type Manufacturer Model Product Name FW Version BIOS Version EFI Version FCODE Version <...>
----------------------------------------------------------------------------------------------------------------------------
c0 NVMe Intel 0x0953 INTEL SSDPEDME016T4S 8DV1RA13 - - -
c1 NVMe Intel 0x0953 INTEL SSDPEDME016T4S 8DV1RA13 - - -
How to update the F160 card firmware ?
For updating the F160 card firmware you can refer to the F160 card's User Guide to come finally to the 'fwupdate' syntax...
# fwupdate update <target> -n <device, e.g. c0> -f <firmware filename>
For an F160 card the <target> is nvme-controller-firmware
References
<NOTE:1672221.1> - Oracle Solaris 11.2 Support Repository Updates (SRU) Index
<NOTE:2047847.1> - Fujitsu M10: Firmware for the Various Hardware Components used on Fujitsu M10
Attachments
This solution has no attachment
