SUMMARY: HSZ22 controller,password [not completely answered]

From: <Shaun.Racine_at_intier.com>
Date: Wed, 25 Aug 2004 14:33:20 +0100

Dear All,

Thanks to respondents for their suggestions;
Shawn.Cromer
Martin Roende Andersen

Default password is DECRAID.

With regards to stopping alarm, I dare not try the suggestion of deleting
units and re-creating them. I reluctantly resign myself to having the
alarm switch on the rear of the unit switched off.

Best regards
Shaun Racine


Original Question
=================

Hello managers,

I have a HSZ22 disk controller connected to a DS10, TRU64 v5.1 pk4

I moved this equipment between offices today, plugged one of the power
cables into the HSZ and the alarm sounded immediately. I did not
appreciate
the switch was still on.

Unfortunately, plugging the other power cable in has not stopped the alarm.

The DS10 boots fine and I can see all data on the disks for the HSZ, but
have the alarm sounding continuously.

I have plugged in the serial cable to one of the controllers, it asks for a
password,, tells me its invalid and gives me just a browse screen.

I cannot imagine anyone set anything other than the default password, which
brings me to the questions.

What is the default password (for a serial terminal connection) on a HSZ22?
How can I silence the alarm?

Update Question (after finding password)
===============

I believe I have through every menu item, and cannot find a way to turn the
alarm off.
There is a switch on the back of the array, which does mute it, but when
switched back up it is audible again.
I do not want to leave it switched off, in case we need the audible alert
for future problems.

How can I silence the alarm with the menu?



Suggestion from Shawn Cromer
============================
Not familiar with the HSZ22. But other HSZ controllers. Alarms can sound
off for several reasons. How long was the HSZ unplugged. . The alarm can
be cache containing unflushed data. Try deleting a unit number, you can
add it back. But if it gives message cannot delete unit it will give you
the command to clear the unfushed data. Clear it hen add back the unit
number. . Or battery life low.Can you issue the command shoe this and show
other if redundant. This may tell you what he error is. If redundant make
sure it is set for failover. If not set issue commend "set failover copy =
this" IF battery low, check the time set on the controller. IF not set,
set it and run frutil. Answer as if you are replacing the battery.


Suggestion from Martin Roende Anderson
======================================
This is a suggestion from one of the manuals...

See 2.

Cause
Due to the power fail, the RA3000 has lost the configuration settings in
the
controller that assign virtual units to physical scsi target and lun
addresses. The data and devices are still intact.
Solution
Reconfigure the Host Settings, in the password protected RA3000
configuration menu, through a serial laptop terminal, using the following
procedure.

----------------------------------------------------------------------------

----
NOTE: Capture the configuration information
Capture the configuration information and LUN mappings in case this problem
ever occurs again.
----------------------------------------------------------------------------
----
1. Open SWCC for HSZ22 Storage Window and connect to the RA3000. Select
each
virtual units properties and host port settings. Copy everything down, such
as, Host port 0 scsi target assignment and Host port 1 scsi target
assignment. Also, for the virtual unit properties, record the SCSI TARGET
and SCSI LUN assignment and CAPACITY for each virtual unit and document it.
Also document the NAME for each set of redundancy groups, such as U00, U01,
U02.
 Reference: Command Console V2.2 for the RAID Array 3000 (Pedestal and Rack
Mount Models) User's Guide - AA-RBF2C-TE-V22
2. Connect to the RA3000 with HyperTerminal.
While holding the <ESC> and SHIFT keys down, press the number "7" key. The
screen below will show up.
Enter the password: decraid
Top of page
3. Choose "Raid Set Information" from the folowing menu;
4. Choose the N and P keys to scroll up and down the list of virtual disks.
Each one will show a page like the one below. Make a list ofthe following,
as an example, from the group below:
RAID Set Number: 2
Redundancy Grp: 2
Capacity:16736256 blocks which is indicated as 8172mb
RAID Level such as jbod, raid 5 , etc
All of the information for each of the virtual disks
Type control Z to get back to the Main Menu
Top of page
5. From main menu select Setup Parameters, then select Host Parameters. The
host parameter menu determines what addresses that the RA3000's host port 0
and host port 1 present to the host. On an RA3000 a host port is only
capable of presenting one scsi target id. Host port 0 is assigned a target
and host port 1 is assigned a target.
6. Edit Host Parameters to match the old configuration that was recorded
from SWCC. Host Port 0 and Host Port 1 on the RA3000 by default are mapped
as SCSI Target ID 0 and SCSI Target ID 1 respectively. Verify and change if
necessary.
Top of page
7. Type control Z to get back to the Main Menu
Select "Setup Parameters"
Select "Host Lun Mapping".
With the redundancy groups identified, map them to the correct host port 0
or 1 and the correct Lun number 0-31. Edit the table and add the red grp #
found beside the appropriate LUN # in the table.
The page for host port 0 was used in the example, since the rear panel
connector was used to connect to the host.
Redundancy group 0 was added to LUN ID 0.
Redundancy group 2 was added to LUN ID 1.
Both raidsets will be seen from host port 0 as follows.
Group 0 seen as [SCSI Target ID 0 LUN 0]
Group 2 seen as [SCSI Target ID 0 LUN 1]
Type control Z to get back to the Main Menu
8. Restart the RA3000 to make the configuration change take affect, as
follows;
Select "System Functions" and "Restart System".
9. Reboot or reinitialize the system. The devices should now be seen. The
BIOS or Console would see the devices as "DEC HSZ22 ".  If the system sees
the devices again but fails to mount them, modify the lun mappings until
the
configuration of the scsi addressing matches what the system expects. If
using SWCC to verify the old settings, this wont be a problem.
Suggestion from Martin Rønde Andersen
=====================================
 For the beep tones to stop, maybe one of the blowers are not running.

Received on Wed Aug 25 2004 - 13:35:25 NZST