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

Revision 357

allow vict to show millisecond timestamps and expand both VIWC and VICT to support such degree of timestamp accuracy

Posted in Uncategorized

Revision 345 – How to Read Nicknames from a BNA Server

Part of our task when installing the VirtualWisdom product is that last-gap: how to make it work within the customer’s ecosystem.

Sure, we don’t have to, but then the customer has a whole lot of extra work to maintain the product. This care-and-feeding, this sort of subtle extra work, is often referred as “friction”.

Revision 345 reduces the friction where there is an exploitable Brocade Network Administration service… and by “exploitable”, I’m not saying this as a bad thing, just something we can leverage.

It’s this simple:

Consider Mike. Poor guy, this guy has no time. He’s busy. He’s got BNA, SanScreen, and VI, and he’d love if any one of those guys read from the others.

Mike’s BNA server is at bna.example.com

Mike grabs a copy of the latest “vict.jar”, the Client Tool, and his Java at java.exe, and runs:

java.exe -jar vict.jar --nickname=bnapsql://bna.example.com

So that’s great, but Mike can’t really do anything with that. OK. Let’s check that out in Revision 346, where there will be rainbows, pots of gold, and something else added to the tools.

With my obsession for standards, yes this is a RFC-1738 -compliant URL. Intentionally. You can indeed give a username, password, and port number in there, if you really want to. I wouldn’t want to lead you astray 🙂

Revision 341

incorporating ER-414 changes based on testing against 10 different versions to yield schema versions (license-permitting)

Posted in Uncategorized