Revision 476 – Added Auto Mode to PHC

For revision 476, I wrote “made PHC “do the right thing” a bit better by dropping out some config in the bat file and activating an “auto” mode; may have issues in a “-h uri” mode”

In short, there it is: the PHC becomes “Automatic-er” and allows me to be lazier. Avoiding possible user-error is merely a stretch-goal 🙂

Consider the 7 characters:

PHC.BAT

What this does is:

  1. find your java.exe in a list of 12 most likely places
  2. if PHC-XLSX.jar is available, use it; otherwise, use PHC.jar
  3. runs it in “-A” or “–auto” mode

Auto Mode

Auto Mode simply does the smarter things for you, so that fewer choices are necessary:

  1. if PHC-XLSX.jar has enabled XLSX creation, build phc.xlsx
  2. if any OUIs are missing, look them up, and create phc-OUISignatureList.xml which can be used as the basis of edits to OUISignatureList.xml
  3. if VMs are present, and some HBAs are not set, produce phc-vm.csv which can define HBA speeds based on having all HBAs under ProbeSW
  4. pri

Revision 423 – Dump Current Detected ESX

In revision 423, I added the ability to dump out physicalserver table as esx.csv or esx.xml similar to dumping roving.xml and roving.csv. The outputs are self-documenting in #comments in the CSV, or as XML self-documents already. Note that the XML has no whitespace, so “xmllint -format esx.xml” is your friend.

For example:

(typically running locally: the MySQL is configured to only accept local connections)

java -jar vict.jar -D esx.csv

or

java -jar vict.jar -D esx.xml

…and in long-options too:

java -jar vict.jar -D esx.xml

…but since the JRE is typically hidden below the VirtualWisdom directory, use vict.bat:

VICT.BAT -D esx.xml

Revision 368 – Kerberos Config Helper

Due to frustration on people updating Kerberos config data without actually, well, being correct, I’ve added a helper to vict.jar: “Created a quick tool to dump out Kerberos config information in text and XML format to help reduce ambiguity in documented AD authentication via Kerberos”.

I hope this avoids further misguided dependence on Jambons who just cannot check a detail.

Try it out on your server:

java -jar vict.jar --kerberos

There’s an article (How to Enable Active Directory Authentication via Kerberos) describing the process of adding a Kerberos user, but this output accelerates the process.

Revision 365 – Inflight BNAPSQL Changes

Revision 365 improves the BNAPSQL Client to avoid null nicknames, and avoid quoting those nicknames that are already quoted.

This was performed live with a customer on the conference call; really great debugging experience.

As a reminder:

 java -jar vict.jar --nickname=bnapsql://user:pass@server:port/resource

where the default is:

 java -jar vict.jar
   --nickname=bnapsql://dcmadmin:passw0rd@localhost:5432/dcmdb

…and if you just want to spit the nicknames right back out from two servers:

java -jar vict.jar
--nickname=bnapsql://server1/
--nickname=bnapsql://server2/
--nicknameout=output.csv