HBA Port Stats Test
By periodically checking the target port status and measuring the I/O processing capability of the ports, you can identify overloaded ports, and thus proactively detect potential/existing load-balancing irregularities and/or processing bottlenecks on the host bus adapter. The HBA Port Stats test facilitates this port check.
For every port configured on the Host Bus Adapter, this test reports the port state, the I/O processing ability of the ports, and the errors encountered by each port. In the process, the test not only points administrators to overloaded ports, but also puts a finger on ports that are slow in processing I/O requests and the ports that are erroneous.
Target of the test : A Microsoft File server
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for each HBA: port combination connecting to the file server that is being monitored
Parameters | Description |
---|---|
Test period |
This indicates how often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
Refers to the port used by the File server. |
Measurement | Description | Measurement Unit | Interpretation | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
HBA port state |
Indicates the current state of this port. |
|
The numeric values that correspond to the states are as follows:
Note: By default, the test reports the States listed in the table above to indicate the current state of the port. In the graph of this measure however, the state is indicated using the corresponding numeric equivalents only. |
||||||||||||||||||||||||
HBA port type |
Indicates the current type of this port. |
|
The values that this measure can take and their corresponding numeric values are as follows:
Note: By default, this measure reports one of the Measure Values listed in the table above. In the graph of this measure however, the port type is indicated by the corresponding numeric equivalents only. |
||||||||||||||||||||||||
HBA port operational speed |
Indicates the current operational speed of this port. |
Gbps |
|
||||||||||||||||||||||||
Received frames |
Indicates the rate at which frames were received by this port during the last measurement period. |
Frames/sec |
Compare the value of these measures across the ports to identify the slowest port in terms of receiving / transferring frames. |
||||||||||||||||||||||||
Transfer frames |
Indicates the rate at which frames were transferred from this port during the last measurement period. |
Frames/sec |
|||||||||||||||||||||||||
Received words |
Indicates the rate at which words were received by this port during the last measurement period. |
Words/sec |
Compare the value of these measures across the ports to identify the slowest port in terms of receiving / transferring words. |
||||||||||||||||||||||||
Transfer words |
Indicates the rate at which words were transferred from this port during the last measurement period. |
Words/sec |
|||||||||||||||||||||||||
Error frames |
Indicates the rate at which frames were received / transferred with errors from this port during the last measurement period. |
Frames/sec |
Compare the value of this measure across the ports to identify the port that is more error prone. |
||||||||||||||||||||||||
Dumped frames |
Indicates the number of frames dumped by this port per second due to lack of buffer credit during the last measurement period. |
Frames/sec |
Buffer credits, also called buffer-to-buffer credits (BBC) are used as a flow control method by Fiber Channel technology and represent the number of frames a port can store. Each time a port transmits a frame that port's BB Credit is decremented by one; for each R_RDY received, that port's BB Credit is incremented by one. Transmission of an R_RDY indicates that the port has processed a frame, freed a receive buffer, and is ready for one more. If the BB Credit is zero, the corresponding node cannot transmit until an R_RDY is received back. A high value for this measure therefore indicates that an R_RDY was not received by the FC port for a long time. This is a cause for concern, as until the R_RDY is received, the FC port will not resume communication. The solution for this problem is to allocate optimal buffer credits to the FC port. The optimal number of buffer credits is determined by the distance (frame delivery time), the processing time at the receiving port, the link signaling rate, and the size of the frames being transmitted. As the link speed increases, the frame delivery time is reduced and the number of buffer credits must be increased to obtain full link utilization, even in a short-distance environment. Smaller frame sizes need more buffer credits. |
||||||||||||||||||||||||
Loop initialization primitive events |
Indicates the number of Loop initialization primitive events on this port during the last measurement period. |
Number |
|
||||||||||||||||||||||||
Non-operational state primitive events |
Indicates the number of Non-operational state (NOS) primitive events on this port during the last measurement period. |
Number |
|
||||||||||||||||||||||||
Link failure count |
Indicates the number of link failures experienced per second by this target during the last measurement period. |
Number |
Ideally, the value of this measure should be zero. A non-zero value indicates that Fiber Channel connectivity with this target was “broken” that many times. This is likely an indicator for a faulty connector or cable. These are also caused when the device connected to this target is restarted, replaced or being serviced when the Fiber Channel cable connected to this target is temporarily disconnected. |
||||||||||||||||||||||||
Loss of synchronization count |
Indicates the number of times this port failed to synchronize during the last measurement period. |
Number |
Ideally, the value of this measure should be zero. A non-zero value for this measure indicates that port went into the “loss of synchronization” state, where it encountered continuous Disparity errors. This is likely an indicator for a faulty connector or cable. These are also caused when the device connected to the port is restarted, replaced or being serviced when the Fiber Channel cable connected to the port is temporarily disconnected. If the port is in the “loss of synchronization” state for longer than a specific period, the port will get into the link failure state which could degrade the performance of the Fiber Channel link. |
||||||||||||||||||||||||
Loss of signal count |
Indicates number of signals lost on this port during the last measurement period. |
Number |
Ideally, the value of this measure should be zero. A non-zero value for this measure indicates that the port detected a loss of the electrical or optical signal used to transfer data on the port. This is likely an indicator for a faulty connector or cable. These are also caused when the device connected to the port is restarted, replaced or being serviced when the Fiber Channel cable connected to the port is temporarily disconnected. If the port is in the “loss of signal” state for longer than a specific period, the port will get into the link failure state which could degrade the performance of the Fiber Channel link. |
||||||||||||||||||||||||
Primitive sequence protocol errors |
Indicates the number of Primitive sequence protocol errors that occurred on this port during the last measurement period. |
Number |
Ideally, the value of this measure should be zero. |
||||||||||||||||||||||||
Invalid word transmissions |
Indicates the number of invalid word transmissions detected on this port per second during the last measurement period. |
Words/sec |
A low value is desired for this measure. |
||||||||||||||||||||||||
Cyclic redundency checksum errors |
Indicates the number of invalid Cyclic Redundancy Checksums that occurred on this port during the last measurement period. |
Number |
Ideally, the value of this measure should be zero. A high value for this measure indicates poor health of the target port. These are usually recoverable errors and will not degrade system performance unless their occurrence is sustained when the data cannot be relayed after retransmissions. |