1NVME-WDC-VS-FW-A(1)               NVMe Manual              NVME-WDC-VS-FW-A(1)
2
3
4

NAME

6       nvme-wdc-vs-fw-activate-history - Execute NVMe WDC
7       vs-fw-activate-history Vendor Unique Command, return result
8

SYNOPSIS

10       nvme wdc vs-fw-activate-history <device> [--output-format=<normal|json> -o <normal|json>]
11

DESCRIPTION

13       For the NVMe device given, read a Vendor Unique WDC log page that
14       returns the firmware actiation history.
15
16       The <device> parameter is mandatory and must be the NVMe character
17       device (ex: /dev/nvme0).
18
19       This will only work on WDC devices supporting this feature. Results for
20       any other device are undefined.
21
22       On success it returns 0, error code otherwise.
23

OPTIONS

25       -o <format>, --output-format=<format>
26           Set the reporting format to normal, or json. Only one output format
27           can be used at a time. Default is normal.
28

FIRMWARE ACTIVATE HISTORY LOG PAGE DATA OUTPUT EXPLANATION

30       ┌───────────────────┬────────────────────────────┐
31       │Field              │ Description                │
32       ├───────────────────┼────────────────────────────┤
33       │                   │                            │
34       │Entry Number       │ The number of fw activate  │
35       │                   │ entry. The most recent 20  │
36       │                   │ entries will be displayed. │
37       ├───────────────────┼────────────────────────────┤
38       │                   │                            │
39       │Power on Hour      │ The time since the power   │
40       │                   │ on in                      │
41       │                   │ hours:minutes:seconds.     │
42       ├───────────────────┼────────────────────────────┤
43       │                   │                            │
44       │Power Cycle Count  │ The power cycle count that │
45       │                   │ the firmware activation    │
46       │                   │ occurred.                  │
47       ├───────────────────┼────────────────────────────┤
48       │                   │                            │
49       │Current Firmware   │ The firmware level         │
50       │                   │ currently running on the   │
51       │                   │ SSD before the activation  │
52       │                   │ took place.                │
53       ├───────────────────┼────────────────────────────┤
54       │                   │                            │
55       │New Firmware       │ The new firmware level     │
56       │                   │ running on the SSD after   │
57       │                   │ the activation took place. │
58       ├───────────────────┼────────────────────────────┤
59       │                   │                            │
60       │Slot Number        │ The slot tht the firmware  │
61       │                   │ is being activated from.   │
62       ├───────────────────┼────────────────────────────┤
63       │                   │                            │
64       │Commit Action Type │ The commit action type     │
65       │                   │ associated with the        │
66       │                   │ firmware activation event  │
67       ├───────────────────┼────────────────────────────┤
68       │                   │                            │
69       │Result             │ The result of the firmware │
70       │                   │ activation event. The      │
71       │                   │ ouput shall be in the      │
72       │                   │ format: Pass or Failed +   │
73       │                   │ error code                 │
74       └───────────────────┴────────────────────────────┘
75

EXAMPLES

77       ·   Has the program issue WDC vs-fw-activate-history Vendor Unique
78           Command :
79
80               # nvme wdc vs-fw-activate-history /dev/nvme0
81

NVME

83       Part of the nvme-user suite.
84
85
86
87NVMe                              04/24/2020               NVME-WDC-VS-FW-A(1)