26.12.2014 Views

Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

2–Advanced <strong>Fabric</strong> <strong>Manager</strong> Capabilities<br />

Performance <strong>Manager</strong><br />

• Congestion – Associated with the port which is unable to process the<br />

incoming data rate. This port is causing backpressure and fabric congestion.<br />

The value is computed as a weighted sum, the weight of each counter is<br />

configurable. Some of the values such as Inefficiency percent are computed<br />

based on ratios of congestion to the link utilization.<br />

• SmaCongestion – Associated with the port which is unable to process the<br />

inbound VL15 traffic. This port is discarding VL15 SMA packets.<br />

• Security – Associated with the port which is attempting to be cracked and<br />

therefore packets are being sent to this port which violate security<br />

• Routing – Associated with the port which is receiving packets it cannot<br />

route. This is only applicable to switch ports on <strong>QLogic</strong> Switches (many 3rd<br />

party switches incorrectly tabulate this counter so it is ignored for<br />

non-<strong>QLogic</strong> switches).<br />

• Adaptive Routing – Associated with the port which is doing the adapting.<br />

This is only applicable to switch ports on <strong>QLogic</strong> 12000 series switches with<br />

6.0 or newer firmware versions. See “Adaptive Routing” on page 2-7 for<br />

more information.<br />

Congestion Statistics<br />

NOTE:<br />

The PortRcvRemotePhysicalErrors counter is not included in any of<br />

these conditions. This counter indicates packets which were marked<br />

bad due to discovery of a packet error during switch cut through. When<br />

such errors occur the counters included in Integrity will allow the issue<br />

to be pinpointed. In contrast this counter will occur for every hop along<br />

the route and is not very useful for the root causing the Integrity issue.<br />

Congestion is a weighted sum of five items:<br />

• XmitDiscard – Count of packets sent which were discarded due to<br />

congestion, link going down or invalid MTU/routing. Note that packets are<br />

only discarded in the event of extreme congestion.<br />

• XmitCongestionPct10 – Percentage of time that the outgoing port was<br />

congested and the outbound queue was deep. This value is only available<br />

for <strong>QLogic</strong> switches and requires PmaSwVendorEnable to be enabled. This<br />

is expressed as an integer *10. So for example 100% is reported as 1,000<br />

• XmitInefficiencyPct10 – Percentage of time that the outgoing port was<br />

congested when it was transmitting. Computed as<br />

XmitCongestionPct/(XmitCongestionPct+Utilization%) This value is only<br />

available for <strong>QLogic</strong> switches. This is expressed as an integer *10. So for<br />

example 100% is reported as 1,000<br />

IB0054608-01 B 2-31

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!