Expanded the option “-w” from Suggested Nicknames for Known WWN Patterns to vict.jar such that vict.jar -w 50000972081349AD shows “VMax-HK192601234-12gB” per https://community.emc.com/thread/118881
Category Archives: Uncategorized
Revision 554 – Suggested Nicknames for Known Clariion WWN Patterns
Expanded the option “-w” from Suggested Nicknames for Known WWN Patterns to vict.jar such that vict.jar -w 5006016012345678 shows “CL-12345678-SPA0” per http://blog.fosketts.net/toolbox/emc-symmetrix-wwn-calculator/
Revision 552 – Suggested Nicknames for SVCs
Expanded the option “-w” from Suggested Nicknames for Known WWN Patterns to vict.jar, expanding on the Symmetrix name pattern by adding recognition of SVC nodes. For example, vict.jar -w 5005076801234567 shows “SVC45_Node67_Port2”
Revision 551 – Suggested Nicknames for Known WWN Patterns
In deployments, very often customers zone their storage based only on a zone-name and WWPN members. Typically this causes a need for the Zone-Vote Algorithm to be used, but that’s an approximation that requires the user to be consistent in Zone names, consistent in zone membership (ie anywhere one FA or HBA is used for an entity, all the others need to be used at the same time).
There are some cases where the WWN is entirely predictable; in such cases, the option “-w” to vict.jar (such as vict.jar -w 50060482B82F9654) shows a suggested nickname or alias such as “Symm-182500953-05bA” (per http://www.emcstorageinfo.com/2007/08/how-to-decode-symmetrix-world-wide.html) which can be leveraged to provide for missing nicknames.
Revision 550 – Dupe-Links-NPIVIgnore Script
Where possible, PHC.jar avoids simple things such as forgetting to set the LinkNames-From-Nicknames setting in Views::Setup::FabricManagement.
Not running the PHC.jar both skips the FAE’s Deployment Checklist, and risks the issues that the PHC checks for.
In this case, the FAE didn’t run the PHC, didn’t set the LinkNames-from-Nicknames, and the links don’t reflect the NPIV names. This is a serious problem in Analysis which is why Stuart Bridger asked for this to be added.
The input to this filter is a list of links and names (the script itself includes a viwc.jar sample). The result is a filter which can be used to ignore the NPIV ports in ProbeSW.
Revision 547 – OUISignatureList Works with our Parser
Para 3.1 of the XML specification says that the order of attributes to an XML element is not significant; for example, the following two statements are equal:
<A left=”one” right=”two”/>
<A right=”two” left=”one”/>
Unfortunately, it seems we wrote our own parser, and missed that part. For what it’s worth, we’re probably using some sort of SAX which leverages the exactness of XML’s syntax markup, so there’s a certain portability and disambiguation there, but the VW parser gets confused when attributes to OUISignature are not in the order it understands.
Similarly unfortunately, I had to break the OUISignatureList writer to accommodate that. The risk is not that other XML parsers will not understand — they will, because they don’t care about ordering. The risk is that I’m building a basic “just print the text” writer, I might make an error such as URLEscaping output. In jumping on a leaky boat, I may also sink.
In the meantime, OUISignatures written by these tools are directly replaceable into VW’s config.
Revision 546 – Summarize-Idle Added
A quick Awk script was added to show how to post-process a CSV exported from a trend report. In many cases, reuse of a data export would be nice, but it’s somewhat opaque: there’s a report, or a CSV. CSVs tend to show just the one summary such as a 1-day rollup.
In order to get more meaningful data, a post-process of an export might be useful. This is the sort of thing that can be coupled behind an email sent to a which later asynchronously executes a BAT file to contain this logic.
I may need to create a writeup of how to leverage this, but in the meantime, this example is added.
Revision 544 – Improved DOS BAT Convenience Scripts
Previously, all the BAT files provided for convenience assumed that the JAR files you want to use are in the current directory as opposed to the directory holding the BAT file.
Sorry about that.
In this revision I fixed that, noting “All .bat convenience scripts updated to be able to run using an absolute path to the BAT file rather than assume contents are in local directory”
Revision 542 – VR Can Help You Sync
Added a hack to VR to allow it sync your repository.
VR, The “VirtualRegent” was a start of a helpful bot before there was such a thing as RemoteWisdom. As a bot that would contact outward, it could maintain a bidirectional channel for status and payloads — basically for information and uploads or downloads. It even has a Jabber bot so the the tools we already have can talk to it.
I created a way to self-test commands — such as “checksum XX file” and a “fetch” topic to test download such as software updates.
This test function became the more common usage: for example “VR –demofetch” will fetch you everything you need to set up a demo, except for the license file.
I’ve added the command “syncfae” so that “VR –cmd syncfae” does what’s needed to sync the FAE Toolkit on windows. This is abbreviated with the option “–sync” to VR.jar, expanding to “–cmd syncfae”, so that fewer keypresses are needed ot get the sync started. It’s not that I think people are not intelligent, it’s that the fewer buttons on the remote control, the better the chance that the user will choose the right one.
“VR –sync” will download rsync.exe, cygwin1.dll, and use them to synchronize the contents to a local directory called FAE.
Revision 541 – Added Parsing of DCNM Data for Nicknames
In revision 541, the basic capability to ask a DCNM service for the Nickname/WWPN mapping has been started. This has the potential to reuse the information entered into DCNM rather than re-entering manually, and avoid pulling zonefiles from each zone for parsing using a –nickname=file:// or –nickname=http:// method. As well, in situations where aliases are not used, we can collect the port labels or private aliases that DCNM may not share down to the switch.
This method is only initially defined, but requires a bit more work.
The same parser logic is used as was added for OnCommand in OnCommand Query and for BNA in BNA Query. Like the BNA and OnCommand work, the DCNM query simply reformats a query and sends it through the array of parsers to vote upon:
java -jar vict.jar --nickname=dcnmsql://user:pass@server:port/ --nicknameout=\VirtualWisdomData\DeviceNickname\nicknames.csv
Default user/pass should be accurate but need additional testing to confirm. Like the BNA parser, this method hits the underlying database directly, so it needs (firewalls/filters) direct access to the server, and is vulnerable to schema changes. Schema is based on 5.2 documentation.
In the meantime, cisco-shows2wwncsv.awk is also provided to build portlabel nicknames as import CSVs; this awk file needs two “show” commands on every switch. NOTE: every switch, not just every fabric, and it needs to see the output of “show flogi database” before it sees “show interface description”.