This document contains data used by the tools and about buttons.

!!!!!!!!!!!!!  for use by vlsParse development team only !!!!!!!!!!!!!!
 
DO NOT change the lines with the asterisks.

The data below each header will be displayed when the associated button is pressed.
Data will appear as it appears here.  Use tabs or spaces to align text.
$VERSION in the about_information section will be translated to the version and mod date of the main script so don't delete it.

********************** firmware_links *************************

VLS6800 	http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=1144251&prodTypeId=12169&prodSeriesId=470405&swLang=13&taskId=135&swEnvOID=54
VLS300		http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3303463&prodTypeId=12169&prodSeriesId=3303462&swLang=13&taskId=135&swEnvOID=54
VLS12000	http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3542989&prodTypeId=12169&prodSeriesId=3542988&swLang=13&taskId=135&swEnvOID=54
VLS6100		http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=470419&prodTypeId=12169&prodSeriesId=470405&swLang=13&taskId=135&swEnvOID=54
VLS6500		http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=470421&prodTypeId=12169&prodSeriesId=470405&swLang=13&taskId=135&swEnvOID=54
VLS6200		http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3542993&prodTypeId=12169&prodSeriesId=470405&swLang=13&taskId=135&swEnvOID=54
VLS6600		http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3542997&prodTypeId=12169&prodSeriesId=470405&swLang=13&taskId=135&swEnvOID=54
VLS9000		http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swItem=co-60408-1&jumpid=reg_R1002_USEN
MSA_FW		http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=420470&prodTypeId=12169&prodSeriesId=420469&swLang=8&taskId=135&swEnvOID=1005#29214
Smart_Array_FW	http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=378442&prodTypeId=329290&prodSeriesId=1132643&swLang=8&taskId=135&swEnvOID=1005#29214




********************** vls_rev_history ************************

Version  2.2.0	Release Date 6/4/08
Version  2.1.1	Engineering/Manufacturing release only
Version  2.1.0	Engineering/Manufacturing release only
Version  2.00	Engineering/Manufacturing release only
Version 1.2.0 	Release Date 6/11/07
Version 1.1.0 	Release Date 12/19/06
Version 1.0.13 	Release Date 4/25/06
Version 1.0.12 	Release Date 11/18/05
Version 1.0.9 	Release Date 9/12/05
Version 1.0.8 	Release Date 8/11/05
Version 1.0.4 	Release Date 7/19/05


********************** msa_rev_history **************************

Version 2.06 Release Date 8/2/2007
Version 2.02 Release Date 2/6/2007
Version 1.52 Release Date 6/16/06
Version 1.48 Release Date 3/22/06
Version 1.40 Release Date 10.7/05
Version 1.28 Release Date 4/6/05
Version 1.26 Release Date 2/23/05
Version 1.24 Release Date 11/18/04
Version 1.22 Release Date 10/07/04


********************** sa_rev_history *****************************

Version 2.76 Release Date 3/20/07
Version 2.74 Release Date 1/10/07
Version 2.68 Release Date 6/22/06
Version 2.62 Release Date 4/7/06
Version 2.58 Release Date 10/7/05
Version 2.48 Release Date 8/30/05
Version 2.34 Release Date 12/17/04
Version 2.32 Release Date 10/28/04
Version 2.26 Release Date 7/14/04
Version 1.92 Release Date 4/8/04
Version 1.60 Release Date 10/2/03
Version 1.58 Release Date 9/4/03


********************** debug_Value_info *****************************

01 Base logging level
02 Increased SCSI logging
03 Enables WWPN logging. With all modules selected, use for only short periods
   or message logging may hang. Suggested alternative is to only select the
   IOM, VTAPE, and VLIB modules if long term monitoring is needed.
04 Unknown at this time
05 Unknown at this time
06 Unknown at this time
07 Unknown at this time
08 Unknown at this time
09 Unknown at this time
99 Unknown at this time


********************** documentation_info ****************************

Value				Source
__________________________________________________________________
ATIO Que		proc.txt > /proc/sepaton/iom/triad0/atio:
Debug Values		proc.txt > Debug levels:
Email Server Name	S2100\s2xmgr_java\persist\EmailServers.xml
Host Table		proc.txt > /proc/sepaton/iom/triad0/hosts
IP Address		etc\\sysconfig\\network-scripts\\ifcfg-eth0
IP DNS Server		S2100\\s2xmgr_java\\persist\\Head_0.xml
IP Gateway		etc\\sysconfig\\network-scripts\\ifcfg-eth0
IP Net Mask		etc\\sysconfig\\network-scripts\\ifcfg-eth0
MSA Firmware		S2100\\s2xmgr\\HPDiskDiscovered.prop
MSA Shelf Number	S2100\\s2xmgr\\HPDiskDiscovered.prop
SA Firmware		S2100\\s2xmgr_java\\persist\\DiskArray_127.0.0.1.xml
VLS Chassis Name	S2100\\s2xmgr_java\\persist\\EmailServers.xml
VLS Firmware		S2100\\s2xmgr_java\\persist\\ChassisInfo.xml
VLS Model		S2100\\s2xmgr_java\\persist\\ChassisInfo.xml


********************** message_tab_help ******************************

The messages tab is separated into an upper and lower section, seperated by a horizontal line(The adjuster).
You can adjust the height of the viewing area by dragging the adjuster up or down.
It's easiest to do this while the mouse pointer is over the small square box on the right side of the adjuster.

The upper section has the predefined search strings and a text box where you can enter any string to search for.
You can select multiple search strings using ctrl-click or shift-click. 
Select "No Selection" to clear out the search options.
When changing pages on large message files, any active search strings will be re-highlighted on the new page.

For a VLS 300 ticket, select which head you want to look at using the radio buttons at the top of the screen.
You can have only one messages file open for viewing at a time. .
Click "Load Messages File" to read in the file.
If the messages file is very large you will be asked if you want to continue.
If you want to view it, it will be opened in 20,000 line pages.
The current file name and date ranges for the current page will appear.
There will be a slider to load the different pages into the display.
Place the cursor anywhere over the slider. A outline border will appear. Then use the left-right arrows or mouse to select a new page.
The left or right arrows will load the previous or next page. 
If the pointer is anywhere in the scale trough(gray area on either side of the slider) you can left click to go to the next or previous page.
Point to a page number and Right click to jump directly to a page. No need to be in the trough for the right-click.
These operations may take a while to complete and it may look like nothing is happening. Be patient.
The new page will be fully loaded when you see the slider move to the new page number.

You may want to use an editor outside of this script, like VIM, to view a very large message file.




********************* about_information ********************************

VLS Support Ticket Data Parser
Version $VERSION
Copyright Hewlett-Packard Company 2006
Hewlett-Packard Company

This utility will parse the relevant data out of a
VLS support ticket for use by Hewlett-Packard
support personel in troubleshooting and
maintaining the VLS product line. Unauthorized
use is strictly prohibited.

********************* help_information ********************************
How to use VLS-DP:
1. Obtain a vls support ticket and unzip into a local directory
2. Launch VLS-DP and use the browse button to point the tool to the support ticket.
3. Press the Parse button to obtain the data from the support ticket.

Menu Items:
	File:
	-Save as HTML file
	>This is how you can get the VLS-DP data into a format you can search, cut, and paste. 
	-View ADU report
	>You can view the ADU report in either native mode or interpreted. Very useful for finding additional information from the MSA20's
	-Show Parse Log
	>This gives VLS-DP developer information on any problems that occur while parsing a support ticket.
	-Show Directory Tree
	>Useful tool for navigating the directoy structure of a support ticket. Let's you open some files.
	-View Auto Migration Report
	>Currently under construction
	-Create SCSI Commands table from messages file
	>This tool will create a table of the scsi commands issued by each server. The servers are id's by the WWPN. 
	>To use the tool you need to set the debug level to 4 for the SCSI module and run for a period of time. Extremely useful. 
	-Create Lun Masking HTML File
	>This will create the lun masking tables in a seperate html file. It contains the hosts and all devices mapped to 
	>those hosts along with the lun and port information.

	Definitions:
	-Handy definitions for things like firmware release dates, data sources, and useful message file search strings.

	User Interfaces:
	-This allows you to maintain a list of VLS's and access them thru either CV-VLS or Putty. This will make the tool
	-a little more useful on a day to day basis to lab engineers and customer's with multiple VLS's.

	


Diagnosing common problems:

Excessive Test Unit Readies

- Log onto the VLS CLI
- Issue the enablevlslog -d 4 command to enable debugging at level 4
- Wait 15 minutes
- Issue the enablevlslog -d 2 command to set debugging back to default
- Create a Support Ticket from the GUI
- Load the ticket into VLS-DP
- From the File menu, select "Create SCSI Commands table from messages file"
- The report will list nodes by WWID that are sending TUR's 
- TUR's are a normal EBS function so look for nodes that are sending an excessive (1 per second per device) amount.

A storage lun is missing
-Go to the report page, SLUN tab and see if all of the luns present. There is a summary
-at the top of the SLuns tab that will display the Tray Id's and any Sluns in that tray.

An MSA20 cache battery is bad but you don't know which one.
-With a 1.2 or later support ticket you can pull up the MSA20 ADU report from the Main page File option. 
-With the report open there's a table of contents listed as the first thing. At the bottom of the table 
-of contents is Serial Output Log. There's a Serial Output log for each shelf and complete status for each battery.

The VLS shows zero capacity.
-This indicates either a problem with the licensing or a problem with one or more of 
-the Storage Pools. Please see the appropriate troubleshoooting section.

Storage Pool problems
-Storage Pools are created when the VLS is configured. The Storage Pool consists of a list 
-of storage luns (SLUNS). For the pool to be available, all SLUNs in it's membership list
-must be present. If the Storage Pool is unavailable the VLS will show zero capacity.
-
-To verify the Storage Pool go to the Report page and open the Pools tab. The id entry tells
-you the name of the stroage pool and the lunCount entry tells you how many SLUNS are 
-configured to this storage pool. If a SLUN is missing, please proceed to that section.
-Open the SLUN tab and verify that there are the correct number of SLUNS that are members
-of the storage pool id found earlier and showing the mounted entry as true. 


License problems
-The VLS ships with a base license plus any additional capacity licenses needed to cover 
-all of the storage on the VLS. On the main screen you can find the number of licensed luns
-the vls has in addition to the number of luns present. If the Lun count exceeds the 
-Licensed lun count then there is a license violation and the VLS will show zero capacity.
-The tool will flag this condition if it exists. Please load the additional capacity licenses via CV-VLS
 or with CV-TL prior to VLS firmware 2.2.0.

VLS hangs while troublshooting with debug levels set greater than default
-The amount of data the VLS gathers can be changed by modifiying the debug levels using the 
-./set_debug 'module' 'level' command form root or the enablevlslog -d from the CLI. It's 
-possible to gather so much data that the VLS system disk becomes full and the VLS will hang. 
-Use caution when running at high debug levels.
-The recovery is to reinstall the VLS software. The customer data is not affected and is safe.

The messages file doesn't show data far enough in the past.
-The VLS checks the log files each night and if the messages file has become too full it will
-archive the file and create a new one. Check in the GUI under Log Viewer for files with a numeral 
-added to the file name. These are the archived files. Example: messages.1.txt 
