The NW content is still synchronizing, as well as VW3 of course, but VW4 hasn’t been synching. That’s been added to the FTP server to push content to the EU staging, and provide a VW4 directory as requested by Stu Heron.
It’s great when I can rely on good friends to catch my oversight 🙂
It should now be present when you sync
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.
On Dom’s request, I added a JAASTOOL.BAT file similar to VICT.BAT, VIFT.BAT, VIUPLOAD.BAT, etc to get over the nuisance of finding the install path and using it to run the JAR file.
Sure, people slag Java as though it’s as bad as PHP, but it really does run everywhere: Unix, Linux, Windows. Same code. The hard part is looking for the java.exe. If the problem is simply “find the file ‘java.exe’ on your computer”, and you cannot find a file on your PC, perhaps you should be ashamed! In cases where we are simply really, really tired/jet-lagged, this script iterates the most common known locations, and when upon finding the JAVA.EXE, uses it to execute the JAASTOOL.JAR file with the options given on the command line.
Yeah, it’s still a command line. I’m not so good at GUIs.
Added the ability to parse nicknames from a Cisco Show Zone. In short: blindly parse a “show zone” output, and if the text stream isn’t overly butchered, nicknames will be detected and imported to the VICT space for writing using -n file.csv or --nicknameout=file.csv
in fibrechannel-parsers version 0.3.39, a parser was added for the result of a cisco show zone:
zone name SANASVR001_FabA vsan 100
fcalias name Oracle_123466 vsan 100
pwwn 10:00:00:00:c9:12:34:66
fcalias name HDS0123457_CL7F vsan 100
pwwn 50:06:0e:80:12:34:56:78
This differs from a show device-alias database or a show fcalias in that the zone entries are present, and may contain vsan verbs. Implemented as a stream, it should be a bit more robust and accepting than a pure-scripted variant, so that content provided by (oh, my favorite!) a user cutting a session out to log and submitting that (because it’s just as good… nah, with the ANSI markers and color formatting, it’s better!). This isn’t a substitution for ignoring the very detail when (not) reading directions, but it should give us a fighting chance.
The addition is available in the same array of parsers, so it works without any new user-config. For example, list like the parsing of cisco device-alias database as a simple text stream (from FTP, HTTP, or FILE:// URLs), a simple --nickname= or -N will work:
java -jar vict.jar --nickname=file:///file/name.txt
(or the convenience fallback)
java -jar vict.jar --nickname=/file/name.txt
(or in short-form options)
java -jar vict.jar -N name.txt
(or in Windows)
VICT.BAT -N name.txt
The matching actions in the main toolkit using the fibrechannel-parsers project involves a test case to ensure the code is resident and functioning; by that method, whatever version of fibrechannel-parsers is found during the build will offer at minimum a functioning version of this extension.
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.
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.
Besides bumping DataVersion checking in PHC, VIFT also gains the ability to wipe and reset a 3.6.0 Administrator password
Extended fcparsers.jar and added a test to confirm that fcparser.jar fixes the parser abort on multiple “cfg:” sections
In this revision, the FAE tools gain the ability to filter or replace automatically-provided nicknames in the imported nicknames. This includes:
Filter (-f) removes these nicknames, allowing a cleaned-up nickname file to be imported without accidentally setting generated nicknames to be user-provided (hence “sticky”).
Replace (-S, for Suggested) swaps with Suggested Nicknames (SNICKs) — nicknames based on well known patterns of WWPNs by deliberate manufacturer habit or design.
Nicknames that do not look like predictable/default nicknames are not affected: this is intended for cleaning up a Portal Service export that includes all sorts of additional information.
Expanded the option “-w” from Suggested Nicknames for Known WWN Patterns to vict.jar such that vict.jar -w 52:4a:93:7d:74:f1:14:00 offers “Pure-d74f114-CT0.FC0” or “Pure-d74f114:0:0” in brief, giving (weak) nicknames to Pure Storage Flash-based storage targets.
Note that since WWN patterns are moved to the external WWNDesc project, this is merely test code to ensure that the parallel work in the external project is functioning as required today and henceforth.
This nickname pattern is based on what I’ve seen deployed, and has no clear direction or description from Pure Storage. Pure is actually shipping QLogic HBAs as storage target FA ports, like many other vendors, however they have the decency and class to re-brand the OUI as their own OUI, making them easier to identify. THANKS, Pure! You make our lives a bit easier by taking that extra step.