1SMP_REP_PHY_ERR_LOG(8) SMP_UTILS SMP_REP_PHY_ERR_LOG(8)
2
3
4
6 smp_rep_phy_err_log - invoke REPORT PHY ERROR LOG SMP function
7
9 smp_rep_phy_err_log [--help] [--hex] [--interface=PARAMS] [--phy=ID]
10 [--raw] [--sa=SAS_ADDR] [--verbose] [--version] [--zero] SMP_DEVICE[,N]
11
13 Sends a SAS Serial Management Protocol (SMP) REPORT PHY ERROR LOG func‐
14 tion request to an SMP target. The SMP target is identified by the
15 SMP_DEVICE and the SAS_ADDR. Depending on the interface, the SAS_ADDR
16 may be deduced from the SMP_DEVICE. The mpt interface uses SMP_DEVICE
17 to identify a HBA (an SMP initiator) and needs the additional ,N to
18 differentiate between HBAs if there are multiple present.
19
21 Mandatory arguments to long options are mandatory for short options as
22 well.
23
24 -h, --help
25 output the usage message then exit.
26
27 -H, --hex
28 output the response (less the CRC field) in hexadecimal.
29
30 -I, --interface=PARAMS
31 interface specific parameters. In this case "interface" refers
32 to the path through the operating system to the SMP initiator.
33 See the smp_utils man page for more information.
34
35 -p, --phy=ID
36 phy identifier. ID is a value between 0 and 254. Default is 0.
37
38 -r, --raw
39 send the response (less the CRC field) to stdout in binary. All
40 error messages are sent to stderr.
41
42 -s, --sa=SAS_ADDR
43 specifies the SAS address of the SMP target device. Typically
44 this is an expander. This option may not be needed if the
45 SMP_DEVICE has the target's SAS address within it. The SAS_ADDR
46 is in decimal but most SAS addresses are shown in hexadecimal.
47 To give a number in hexadecimal either prefix it with '0x' or
48 put a trailing 'h' on it.
49
50 -v, --verbose
51 increase the verbosity of the output. Can be used multiple times
52
53 -V, --version
54 print the version string and then exit.
55
56 -z, --zero
57 zero the Allocated Response Length field in the request. This
58 option also zeros the Request Length field in the request. This
59 is required for strict SAS-1.1 compliance. However this option
60 should not be given in SAS-2 and later; if it is given an
61 abridged response may result.
62
64 Similar information is maintained for SAS SSP target phys (e.g. on a
65 SAS disk). It can be obtained from the Protocol Specific Port log page
66 with the sg_logs utility.
67
68 Similar information may be obtained for SAS initiator phys (e.g. on a
69 SAS HBA). As an example in Linux 2.6.28 error information can be found
70 in this directory /sys/class/sas_phy/phy-4:0 (for the phy 0 in SCSI/SAS
71 host 4).
72
73 Similar information may be obtained for SATA device phys (e.g. on a
74 SATA disk). If there is a SAT layer between OS and the SATA device then
75 the sg_sat_phy_event utility can fetch the information.
76
78 The SMP REPORT PHY ERROR LOG function was introduced in SAS-1 . The
79 "Expander change count" field was added in SAS-2 .
80
82 Written by Douglas Gilbert.
83
85 Report bugs to <dgilbert at interlog dot com>.
86
88 Copyright © 2006-2011 Douglas Gilbert
89 This software is distributed under a FreeBSD license. There is NO war‐
90 ranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR‐
91 POSE.
92
94 smp_utils, smp_phy_control(smp_utils), sg_logs(sg3_utils),
95 sg_sat_phy_event(sg3_utils)
96
97
98
99smp_utils-0.96 May 2011 SMP_REP_PHY_ERR_LOG(8)