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] SMP_DEVICE[,N]
11
13 Sends a SAS Management Protocol (SMP) REPORT PHY ERROR LOG request
14 function to a 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. With one interface there is one
17 SMP_DEVICE per machine so the SMP_DEVICE,N syntax is needed to differ‐
18 entiate 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 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 127. Default is 0.
37
38 -r, --raw
39 send the response to stdout in binary. All error messages are
40 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
57 Similar information is maintained for SAS SSP target phys (e.g. on a
58 SAS disk). It can be obtained from the Protocol Specific Port log page
59 with the sg_logs utility.
60
61 Similar information may be obtained for SAS initiator phys (e.g. on a
62 SAS HBA). As an example in Linux 2.6.28 error information can be found
63 in this directory /sys/class/sas_phy/phy-4:0 (for the phy 0 in SCSI/SAS
64 host 4).
65
66 Similar information may be obtained for SATA device phys (e.g. on a
67 SATA disk). If there is a SAT layer between OS and the SATA device then
68 the sg_sat_phy_event utility can fetch the information.
69
71 The SMP REPORT PHY ERROR LOG function was introduced in SAS-1 . The
72 "Expander change count" field was added in SAS-2 .
73
75 Written by Douglas Gilbert.
76
78 Report bugs to <dgilbert at interlog dot com>.
79
81 Copyright © 2006-2008 Douglas Gilbert
82 This software is distributed under a FreeBSD license. There is NO war‐
83 ranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR‐
84 POSE.
85
87 smp_utils, smp_phy_control(smp_utils), sg_logs(sg3_utils),
88 sg_sat_phy_event(sg3_utils)
89
90
91
92smp_utils-0.94 December 2008 SMP_REP_PHY_ERR_LOG(8)