How to use DAMP/SNM/HSNM2 CLI
Mike Le Voi
Technical Specialist, APAC TRC Group
4th November, 2008
Introduction
Most users of Storage Navigator Modular (SNM or HSNM2 – previously known as DAMP or 9500V Resource Manager) install the GUI version only.
This short document describes how easy it is to install the CLI. It also describes useful tasks which can be automated with the CLI, such as collecting Thunder configuration information. GSC require standard information to debug 9500V/AMS/WMS problems. Installing the CLI makes it easy for SEs, CEs and customers to obtain this information.
We also discuss how to use the CLI to define a 9500V array to SNM. When these actions are done on the HDvM server, it makes debugging HDvM issues a lot easier for 2 reasons:
1 Cut and paste of the CLI sessions makes problem analysis easy for GSC staff as they then know exactly how the product has been used.
2 It confirms subsystem communication from the HDvM server to the 9500V or AMS/WMS using the DAMP API.
SNM GUI Installation
First, double click the installation executable – just follow the bouncing ball. Do not install DAMP GUI. SNM GUI is backward compatible and supports 9500V as well as AMS/WMS. Use SNM Version 7.0 or later.
If you have already installed DAMP GUI, these are the steps to migrate from DAMP to SNM.
· Copy your subsystem definition file:
From: C:\Program Files\DA Manager GUI\utlprm.inf
To: C:\Program Files\Storage Navigator Modular GUI\utlprm.inf
· Copy your password file:
From: C:\Program Files\DA Manager GUI\dfutil.pas
To: C:\Program Files\Storage Navigator Modular GUI\dfutil.pas
Now, uninstall DAMP GUI.
To install HSNM2, follow the procedures in the manual.
SNM or HSNM2 CLI Installation
First, double click the installation executable – just follow the bouncing ball. Do not install DAMP CLI. SNM/HSNM2 CLI is backward compatible and supports 9500V as well as AMS/WMS. Use SNM Version 7.0 or later. Use HSNM2 4.0 or later.
You need HSNM2 CLI for AMS2000 series support. However, HSNM2 does not support 9200. Install both versions of the CLI if you have both 9200 and AMS2000.
If you took all the defaults, the programs are installed in the following directory:
C:\Program Files\Storage Navigator Modular CLI
or
C:\Program Files\Storage Navigator Modular 2 CLI
In this directory is a bat file called “startsnmen.bat”. Right Click it and make a shortcut. Drag the shortcut onto your desktop. Rename it “SNM CLI”. Right Click the shortcut and change the ICON to something pleasing.
SNM Customisation
When you now double click the shortcut, you will get something boring like this:
Right Click the ICON in the top left hand corner and choose Properties.
Turn on QuickEdit Mode. This makes cut and paste easier to use
.
Assuming you are using a screen resolution of 1024x768, change Buffer width and height to 200 and 3000, and Window width and height to 100 and 50 – you want to make this easier to use.
Change the Screen Text colour to turquoise or your favourite colour.
Now press OK.
Modify shortcut to make change permanent.
Finally, edit “startsnmen.bat” like this:
@ECHO OFF
SET STONAVM_HOME=.
SET LANG=en
SET Prompt=CLI$G
IF "%OS%"=="Windows_NT" GOTO NT
…
Now you get something like the following:
Define SNM CLI password
First, you must define a password for SNM CLI. It serves no practical purpose but it is required. My recommendation is as follows:
CLI>aupasswd
New password:
Retype new password:
I use the letter “y”. You must choose at least one letter, and this CLI is going to prompt you over and over again with “Are You Sure?” messages, to which your reply is going to be “y” – so you may as well make both letters the same and then you can happily hit “y, Enter” over and over again as you use this product.
Add array to SNM CLI
CLI>auunitref
DMEC002006: No entry.
No entries are defined after SNM CLI installation. Arrays are defined with the command “auunitadd”.
CLI>auunitadd -help
Storage Navigator Modular
Version 2.00
Copyright (C) 2005, Hitachi, Ltd.
Usage:
Single system
auunitadd [ -unit unit_name ] [ -group group_name ]
[ -RS232C | -LAN ]
-ctl0 device | address [ -ignore ]
Dual system
auunitadd [ -unit unit_name ] [ -group group_name ]
[ -RS232C | -LAN ]
-ctl0 device | address [ -ctl1 device | address ] [ -ignore ]
Here is an example for a 9570V.
CLI>auunitadd -unit BNE9570V -group BNE -LAN -ctl0 10.129.148.59 -ctl1 10.129.148.60
Unit BNE9570V has been registered.
Please ignore the “word wrap” in the above example.
Now you can issue auunitref.
CLI>auunitref
Name Group Type Construction Connection Type Error Monitoring IP Address/Host Name/Device Name
BNE9570V BNE DF600 Dual TCP/IP(LAN) Enable 10.129.148.59 10.129.148.60
Alternatively, copy your subsystem definition file from SNM GUI:
From: C:\Program Files\Storage Navigator Modular GUI\utlprm.inf
To: C:\Program Files\Storage Navigator Modular CLI\utlprm.inf
Useful SNM Commands
aulogin
Always login to the array first before issuing any other commands. I am assuming that you have installed the Password Protect feature. This should be mandatory for all new 9500V/AMS/WMS installations.
Account Authentication (AA) is optional for the AMS200/500/1000 and mandatory for the AMS2000 series. If you use AA, use auaccountenv to set your userid and password instead of aulogin.
I recommend that you define at least 3 userids:
· one for customers
· one for HDS CEs
· one for HDvM.
Then, when you cannot connect, because another user is already connected, the resultant error message will tell you who is connected and what their IP address is.
CLI>aulogin -unit BNE9570V
Password:
User ID for array unit : mike
Password for array unit :
Note the initial “Password” prompt for “y” in this example.
Always logout when you have finished a session.
CLI>aulogout -unit BNE9570V
Password:
Note: One nice feature of aulogin is the following:
aulogin -unit BNE9570V –discon
You can forcibly disconnect a user who is logged into the array.
aurgref
CLI>aurgref -unit BNE9570V
RAID RAID Start Location Number of HDU Number of Free Capacity
Group Level [Unit No. HDU No.] in parity group parity group [block] Type
0 5 0 0 4 1 927744 FC
1 5 0 4 5 1 37445632 FC
2 5 1 0 5 1 71004160 FC
CLI>aurgref -unit BNE9570V -g
RAID RAID Start Location Number of HDU Number of Free Capacity
Group Level [Unit No. HDU No.] in parity group parity group [Gbyte] Type
0 5 0 0 4 1 0.4 FC
1 5 0 4 5 1 17.8 FC
2 5 1 0 5 1 33.8 FC
auluref
CLI>auluref -unit BNE9570V -g
Capacity RAID RAID
LU [Gbyte] C-CTL D-CTL Group Level Type Status
0 10.0 0 0 0 5 FC Normal
1 100.0 0 0 0 5 FC Normal
2 20.0 0 0 0 5 FC Normal
3 10.0 0 0 0 5 FC Normal
4 10.0 0 0 0 5 FC Normal
5 0.0 0 0 0 5 FC Normal
etc
There are many other useful commands. auhelp will display them all. All commands take the -help operand to display the syntax.
SNM supports the following Thunder subsystems. The help texts use the factory names for the subsystem types. Specifically:
DF500 9200
DF600 9500V
DF700 AMS200/500/1000
SA800 WMS100
HSNM2 adds support for the AMS2000 generation of subsystems. Support for the 9200 subsystem has been dropped. AMS2000 is shown as follows:
DF800 AMS2100/2300/2500
Configuration Output
Whenever you report a problem to Product Support (GSC), it makes everyone’s life easier if we all have the configuration information to look at. Here is the syntax to do this.
9500V
ausyspout -unit BNE9570V -file ausyspout.txt
auconfigout -unit BNE9570V -file auconfigout.txt
auhgout -unit BNE9570V -file auhgout.txt
aumluref -unit BNE9570V > aumluref.txt
AMS200/500/1000/WMS100
auconstitute -unit AMS500 -export -config AMSconfigout.txt
auconstitute -unit AMS500 -export -sysp AMSsyspout.txt
auconstitute -unit AMS500 -export -hg AMShgout.txt
auconstitute -unit AMS500 -export -parts AMSpartsout.txt
auconstitute -unit AMS500 -export -bootopt AMSbootoptout.txt
aumluref -unit AMS500 > aumluref.txt
AMS2100/2300/2500
auconstitute -unit AMS2100 -export -config AMSconfigout.txt
auconstitute -unit AMS2100 -export -sysp AMSsyspout.txt
auconstitute -unit AMS2100 -export -port AMShgout.txt
auconstitute -unit AMS2100 -export -parts AMSpartsout.txt
auconstitute -unit AMS2100 -export -bootopt AMSbootoptout.txt
aumluref -unit AMS2100 > aumluref.txt
Performance monitoring
Refer to the document on Performance Data Procedures.
Comentarios
Publicar un comentario