Hey, Wow, I hadn’t bumped the internal version-check to 3.7.0.
So that’s done, and the PHC should no longer worry about the latest VW3 release when sanity-checking an environment.
Tag Archives: PHC
Revision 663 – ExceptionInInitializerError in PHC.jar
A customer used the PHC.jar behavior which should recognize that it cannot create a XLSX file and silently do the right thing.
It failed.
I applied the same logic so that a ExceptionInInitializerError will automatically skip the DocReporter instantiation, skipping creation of a XLSX as it should.
Revision 652 – Just a Few More Debug Statements
Built using fibrechannel-parsers v0.3.49 which adds a few debugger options to ZoneParsers — the quick summary on that is when things go sideways, I might be able to get a clue more quickly rather than “pulling teeth” to get screen caps (understanding that our users tend to be in closed-off VLANs and such).
Builds against JDK-1.6 to JDK-1.8.
A certain Texan asked for an alternative query, and even though that thread went a little quiet, a different query statement gets run against a BNA server when using the bna:// or bnapsql:// protocols in a “-N” or “–nickname=” statement to VICT when the java option -Ddebug.carleton=true is used.
Revision 648 – alishow/zoneshow Parser Safely Ignores HardZoning, Multiple cfg:
Hard-zoning records are no longer an issue in the alishow parser.
The external fibrechannel-parsers (fcparser.jar) recently safely ignored multiple cfg: sections, but was still hanging up on hard zoning records.
hard-zoning records — basically “the zone includes blade X, port Y” — not even recommended by Brocade, is occasionally seen in “in the wild”, typically in environments merged into the current one through corporate merger/acquisition of an older SAN. Few support the additional effort and logistical challenge of maintaining hard-zoning of any significant size. It’s those “attritioning out” systems that administrators are nicely letting be until they roll off their life-cycle into recycle.
For now, those hard zoning records would stop the parser immediately. Now, the parser ignores them, still reads the zoning record if available, and carries on.
Revision 645 – Admin-wipe a Password file for Analysis
Besides bumping DataVersion checking in PHC, VIFT also gains the ability to wipe and reset a 3.6.0 Administrator password
Revision 631 – Suggested Nicknames for 3Par WWN Patterns
Expanded the option “-w” from Suggested Nicknames for Known WWN Patterns to vict.jar such that vict.jar -w 20120002AC000C3A shows “3Par-3130:0:1:2” giving suggested nicknames to 3Par storage devices
Revision 628 – Suggested Nicknames for RamSAN WWN Patterns
Expanded the option “-w” from Suggested Nicknames for Known WWN Patterns to vict.jar such that vict.jar -w 21080020C2078332 shows “RamSan-G8332-FC-2B” giving suggested nicknames to IBM RamSan/V3700 Storage, also known as Texas Memory Systems.
Revision 599 – (weak) Suggested Nicknames for Apparent VPLEX WWN Patterns
Expanded the option “-w” from Suggested Nicknames for Known WWN Patterns to vict.jar such that vict.jar -w 50001442607a3b00 shows “VPlex-07a3b-A0-FC00” giving suggested nicknames to EMC VPLEX devices similar to the output of the CLI command ls -l /engine/**/ports.
This WWN Descriptor is not very precise, but is empirically-based. Additional WWPN samples would help guide a better, more precise solution.
Revision 587 – Abbreviate the Suggested Nicknames (SNICKs) in PHC
Provided a way to generate abbreviated “Suggested Nicknames” (which I call “Estimates” in code, and “SNICK” or “Suggested NICKnames” in PHC).
A customer found that our generated nicknames for missing nicknames was entirely sufficient for his needs, but the names are very long; to make it a bit easier, the VICT will now allow –briefestimate to set for brief suggested nicknames, and –nobriefestimate to counter the setting back to verbose estimates. This is useful when using the -w or –wwn option.
The similar option in PHC is either –briefestimate or –briefsnicks when using the generated phc-Nicknames.csv file.
Revision 586 – UnAssigned Switches
Switch discovery doesn’t always discover hints to a fabric’s name, and lacking burrowing into the switch in a wholly instrusive and needs-root-access manner, some switches get tossed into “VirtualFabric”. Removing and re-adding switches, I found a user having to re-specify these repeatedly, and forgetting whether it was done.
When I forget things, I get worried. What if someone else does?
…so I added a check in PHC for ProbeSW in Virtual Fabric to catch where the user has not yet named a fabric.