smp_rep_phy_event(8)

1SMP_REP_PHY_EVENT(8)               SMP_UTILS              SMP_REP_PHY_EVENT(8)
2
3
4

NAME

6       smp_rep_phy_event - invoke REPORT PHY EVENT SMP function
7

SYNOPSIS

9       smp_rep_phy_event  [--desc]  [--enumerate]  [--help]  [--hex] [--inter‐
10       face=PARAMS] [--long] [--phy=ID]  [--raw]  [--sa=SAS_ADDR]  [--verbose]
11       [--version] [--zero] SMP_DEVICE[,N]
12

DESCRIPTION

14       Sends  a SAS Serial Management Protocol (SMP) REPORT PHY EVENT function
15       request to  an  SMP  target.  The  SMP  target  is  identified  by  the
16       SMP_DEVICE  and  the SAS_ADDR. Depending on the interface, the SAS_ADDR
17       may be deduced from the SMP_DEVICE. The mpt interface  uses  SMP_DEVICE
18       to  identify  a  HBA  (an SMP initiator) and needs the additional ,N to
19       differentiate between HBAs if there are multiple present.
20
21       Reports zero or more phy event descriptors. Each descriptor contains  a
22       phy  event source, a phy event (i.e. a count) and a peak value detector
23       theshold.  At least one phy event should be maintained for each phy.
24

OPTIONS

26       Mandatory arguments to long options are mandatory for short options  as
27       well.
28
29       -d, --desc
30              precede  each  phy  event  descriptor with a line announcing its
31              descriptor index number. Index numbers start at 1.
32
33       -e, --enumerate
34              enumerate all of the known Phy Event Source names, one per  line
35              preceded by its value in hex. Ignores SMP_DEVICE if it is given;
36              most other options are also ignored. Exits after displaying  the
37              names.
38
39       -h, --help
40              output the usage message then exit.
41
42       -H, --hex
43              output the response (less the CRC field) in hexadecimal.
44
45       -I, --interface=PARAMS
46              interface  specific  parameters. In this case "interface" refers
47              to the path through the operating system to the  SMP  initiator.
48              See the smp_utils man page for more information.
49
50       -l, --long
51              prefix  each phy event source string with its numeric identifier
52              in hex.  For example: "[0x1]: Invalid word count: 23"
53
54       -p, --phy=ID
55              phy identifier. ID is a value between 0 and 254. Default is 0.
56
57       -r, --raw
58              send the response (less the CRC field) to stdout in binary.  All
59              error messages are sent to stderr.
60
61       -s, --sa=SAS_ADDR
62              specifies  the  SAS  address of the SMP target device. Typically
63              this is an expander. This  option  may  not  be  needed  if  the
64              SMP_DEVICE  has the target's SAS address within it. The SAS_ADDR
65              is in decimal but most SAS addresses are shown  in  hexadecimal.
66              To  give  a  number in hexadecimal either prefix it with '0x' or
67              put a trailing 'h' on it.
68
69       -v, --verbose
70              increase the verbosity of the output. Can be used multiple times
71
72       -V, --version
73              print the version string and then exit.
74

NOTES

76       Similar information is maintained for SAS SSP target phys  (e.g.  on  a
77       SAS  disk). It can be obtained from the Protocol Specific Port log page
78       with the sg_logs utility.
79
80       Similar information may be obtained for SAS initiator phys (e.g.  on  a
81       SAS  HBA). As an example in Linux 2.6.28 error information can be found
82       in this directory /sys/class/sas_phy/phy-4:0 (for the phy 0 in SCSI/SAS
83       host 4).
84
85       Similar  information  may  be  obtained for SATA device phys (e.g. on a
86       SATA disk). If there is a SAT layer between OS and the SATA device then
87       the sg_sat_phy_event utility can fetch the information.
88

CONFORMING TO

90       The SMP REPORT PHY EVENT function was introduced in SAS-2 .
91

AUTHORS

93       Written by Douglas Gilbert.
94

REPORTING BUGS

96       Report bugs to <dgilbert at interlog dot com>.
97

COPYRIGHT

99       Copyright © 2011 Douglas Gilbert
100       This  software is distributed under a FreeBSD license. There is NO war‐
101       ranty; not even for MERCHANTABILITY or FITNESS FOR  A  PARTICULAR  PUR‐
102       POSE.
103