Few specific changes in this release, but a couple of little ones:
Expanded the option “-w” from Suggested Nicknames for Known WWN Patterns to vict.jar such that vict.jar -w 2100000b08123450 shows “Axiom-12345-c0p0” giving suggested nicknames to (Oracle) Pillar Axiom (SLM). This WWN Descriptor is not very precise, but is empirically-based. Additional WWPN samples would help guide a better, more precise solution.
The .BAT files in the toolkit are there to help find a JRE from a number of well-known places.
Oracle installs JRE6 and JRE7 to specific locations, so we check those now if the VI Client and Service are not yet installed.
A JNLP might be a better long-term solution.
Per the conversation at SKO, the “–fixnicknamehistory” is the only art of VIClientTool (vict) that is a writeable action; otherwise, vict is read-only. In order to be sure that vict cannot hurt the database, the writeable portion of vict is moved back into the VIFieldTool (vift). vift is never left with a customer.
In revision 558, I added a logic to PHC that exercises the “-w” from Revision 555: VMax Nickname Suggestion back to Suggested Nicknames framework so that for missing nicknames, a phc-Nicknames.csv file attempts ot provide suggested nicknames for the WWNs of missing nicknames that it understands.
In short, PHC now provides suggestions for missing nicknames, making it possible to have nicknames for hosts the customer may not even be aware are visible by the VW Platform.
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
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/
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”
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.
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.