Revision 672 – OnCommand and DCNM Clients Migrated

In this revision, minor changes were done to move the OnCommand and DCNM client code outside of the non-public source base and into the public source base at OSMURLConnection.java and DCNMURLConnection.java. This allows for external audit of the code and may improve trust and reduce concern. This is very similar to the work done in Revision 670 – BNA Client Migrated

As with Revision 670, the project retains all the test cases involving this and other parsers, so functionality is verified retained, there should be very little change in behavior. The DCNM backend-database client remains beta-quality and requires further testing if a user is willing; the OnCommand client has been heavily tested.

The OSM or OCI backend-database client was added 14 months ago (Revision 516 – Added parsing of OnCommand Data for Nicknames); DCNM backend-database client was added 13 months ago Revision 541 – Added parsing of DCNM Data for Nicknames). The OnCommand client was altered to append a fabric name for a specific environment 11 months ago (Revision 578 – NetApp msosmsql Pseudo-Protocol Adds Fabric Suffix) but can be used to show how easily the output can be transformed.

Revision 670 – BNA Client Migrated

In this revision, minor changes were done to move the BNA client code outside of the non-public source base and into the public source base at BNAPURLConenction.java. This allows for external audit of the code and may improve trust and reduce concern. Also, if I’m doing something very wrong, others may notice.

The project retains all the test cases involving this and other parsers, so functionality is verified retained, there should be very little change in behavior.

The BNA backend-database client was added 21 months ago (Revision 345 – How to Read Nicknames from a BNA Server) and was improved 3 months later (Revision 450 – bnapsql Improvements).

Revision 666 – vw4tools.jar, vw4tool.bat, more parameters, and DeviceAliasParser

This revision was a rollup of a few updates, as follows:

vw4tools.jar and vw4tool.bat allow a basic windows user to locate and run their JRE against the vw4tools.jar file to non-interactively execute a function. This is very similar to the way vict.bat works, except that vw4tools.jar is rolled into vict.jar so both are available in the same package. vw4tool.bat does the right thing.

In order to allow more command line parameters, the convenience BAT files have swapped %# to %* for parameters. If you never ran into this, it’s no problem 🙂

DeviceAliasParser now ignores newlines; this was done in the FibreChannel-Parsers project externally, but testcases were corrected to confirm the behavior.

Revision 665 – Handle Brocade Hanging F-ports

The underlying fibrechannel-parsers project added the ability to properly handle H{xxx} markup, which seems to be Brocade marking out Hanging fabric members (disappeared, never rejoined). In vitools, a testcase confirms functionality absorbed into vict.jar “-N” behavior.

In short, the ability to ignore hard-zoning was improved to get the WWPN from a hanging member as well.

Revision 664 – Sync VW4 Content

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

Revision 659 – Added a JAASTOOL.BAT helper file

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.

Revision 657 – Cisco Show Zone

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.

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.