This edit allows two additional “protocol” values: instead of just http, ftp, bnapsql, dcnmsql, and the formats listed on FibreChannel-Parsers docs, this adds:
- bnacql://user:pass@server:port/path to query a BNA server using CQL
- ie bnacql://bna.example.com/
- ie bnacql://scott:tiger@bna2.example.com:5988/cimv2
- ie dcnmcql://dcnm.example.com/
- ie dcnmcql://scott:tiger@dcnm.example.com:5988/brocade1
- ie dcnmcql://customer:pass@dcnm.example.com/
For example, I’ve been hammering away at it using a command like this:
java -jar vict.jar -N dcnmcql://admin:adminpass@192.168.1.130/ -n nick.csv
… and I would see that the collection extracted 3 DeviceAliases.
The DCNM CQL client draws out Device Aliases, but I haven’t found fcaliases yet.
The BNA CQL client will draw out Zone Aliases, but not Aliases of the non-zone-alias sort.
Why? I needed a CIM-XML client for some work I was doing, and I had the code loosely working so that I could use it to test the other real deliverable. Since I had a DCNM client already, I split the Cisco-specific stuff out, and slotted in a BNA client. The DCNM client (via dcnmcql) is working just fine, but I don’t have a test server to beat up with the BNA client. It works in theory?
How is this useful? Not a whole lot, since VW4 will use a protocol like these to collect information, but I’d like to point out something:
this doesn’t need a license
This would actually let a customer check “will VW4 see all of my aliases?” which — as Application Engineers and Deployment Techs know — is actually a fairly long pole in the circus tent of VW4 deployments.