Qlogic Fast Fabric User Manual

Contents

Qlogic Fast Fabric User Manual Manual pdf 82 page image

5 – Detailed Descriptions of Command LineToolsFabric Analysis Tools5-28 D000006-000 Rev AQFor operations against chassis use of the -S option is recommended. This avoidsthe need to keep the password in configuration files.When performing showallports against externally-managed switches itrequires an IB-enabled management node with Fast Fabric installed. Typicallythis will be the Fast Fabric node from which showallports is being run.However, if desired an alternate node may be specified by the -M option orMGMT_HOST environment variable.5.4.3iba_report(All): iba_report provides powerful fabric analysis and reporting capabilities.It must be run on a host connected to the IB fabric with Fast Fabric installed.iba_report obtains all its data in an IBTA-compliant manner. Therefore, it willinteroperate with both SilverStorm and 3rd party IB components, provided thosecomponents are IBTA compliant and implement the IBTA optional featuresrequired by iba_report.iba_report requires that the subnet manager implement all the IBTA SAqueries defined in the standard (such as SM Info records, Link Records, TraceRoutes, Port Records, Node Records, etc). As such, it is recommended that theQuickSilver Fabric Manager version 4.0 or later be used. iba_report requiresall end nodes to implement the PMA PortCounters (IBTA mandatory counters).Also any end nodes which report support of a IBTA device management agentmust implement the IOU Info, IOC Profile and Service Entry queries as outlinedin the IBTA 1.1 standard.iba_report takes advantage of these interfaces to obtain extensiveinformation about the fabric from the subnet manager and the end nodes. Usingthis information, iba_report is able to cross reference it and produce analysisgreatly beyond what any single subnet manager request could provide. As such,it exceeds the capabilities previously available in tools such as saquery andfabric_info.iba_report internally cross references all this information so its output can bein user-friendly form. Reports will include both GUIDs, LIDs and names forcomponents. Obviously, these reports will be easiest to read if the end user hastaken the time to provide unique names for all the components in the fabric (nodenames and IOC names). All SilverStorm components support this capability.For hosts, the node names automatically are assigned based on the networkhost name of the server. For switches and line cards the names can be assignedvia the element managers for each component.Each run of iba_report obtains up to date information from the fabric. At thestart of the run iba_report will take a few seconds to obtain all the fabric data,then it will output it to stdout. The reports are sorted by GUIDs and otherpermanent information such that they can be rerun in the future and produce