SAN/HBA Data Collection Script/Steps If Explorer is not Available
(Doc ID 1302031.1)
Last updated on OCTOBER 27, 2020
Applies to:Services Tools Bundle - STB - Version 5.3 and later
Information in this document applies to any platform.
This document is primarily for customers that cannot install explorer on their server at the moment or running explorer normally take a long time to complete. It is designed to provide minimum outputs for SAN/HBA troubleshooting to begin.
If issue is explorer does not run for some reason then, it would be interesting to know why explorer doesn't currently run. Also has explorer been run before successfully, when and (if recent enough) provide a copy of it in the /opt/SUNWexplo/output directory.
If you've just installed explorer (now bundled within the Service Tools Bundle (STB)) then you'll need to configure it before you can use it. Use "/opt/SUNWexplo/bin/explorer -g" and answer the questions.
If Explorer has been installed a while and has worked previously, does it hang?
If so, then running ptree(1M) against the parent explorer PID will show what command is currently hanging and from there you/we can try to understand what it's waiting for. Also collect a pstack(1M) output and provide the ptree and pstack outputs for analysis by support.
If explorer is hanging then this script may hang as well but it can still be tried and/or you can run commands manually after killing the hung explorer process.
One reason a explorer may not run is default file has not been properly created, see doc:
explorer: FATAL EXPL-10101: EXP_SERIAL_8xxxxxxx not in the Explorer defaults file (Doc ID 1995470.1)
The procedure below will create a script to gather useful SAN/HBA troubleshooting data.
Must be logged in as root.
NOTE: Help to improve this document and knowledge base by selecting "Comments" and/or "Rate this document".
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document