Restart HiPath 4000 Assistant

[jgbmt]

Hi all,

I'm getting error 2119 when attempting to access HiPath 4000 v5 Assistant. I've performed manual DB synchronization by getting to SYS-->Upload ... but I can't get to this due to the error.

In the past TAC reset the Config Man and it then allowed me to perform the manual synchronization. Can someone please help me with the commands to perform the Config Man reset?

Thank you!

 

[sbcsu]

HISTA tells you if UNIX is booting or if there is not enough memory for it to boot.
The areas of the hard disk have to be active for the Unix to work therefore ACT-DSSM
If you can not log on to Unixware and it needs to be reloaded then a soft restart is
often the quickest way for standard users to follow.

 

[jgbmt]

thank you very much for your help!

i ran sta-uw7; and see ProcMgr appears to be DOWN ...

how can i correct this?

 

[jgbmt]

df -kh

returns with for amo df not found on disk

 

[Moriendi]

We already know Unixware had booted, because he had the login prompt from the Assistant. So there will be nothing of interest in Hista. Hista can help if it won't boot - but it had. Because we know Unixware had booted, we know PDS is in service, or it wouldn't have found UIXBIOS0. So DSSM won't help either. It'll need DMS area for UPLO2, but after the Assistant reboot he can't login from GUI, so he has bigger problems than DMS at the moment.

 

[Moriendi]

df is a Uniware command, you need to run it from CLI. Use putty to connect via ssh with engr.

 

[jgbmt]

a few drives have 7%, 1 with 10%

 

[Moriendi]

Disappointing. Easy fixes are best. From that prompt you could run the cs_control which would fix the 2119 error, but it wouldn't help with the login problem.

I take it you still can't login ? Give it another reboot for luck - init 6 from that command prompt.

If that doesn't work, easiest thing is to reinstall it. Are you on site or remote ? After a reinstall it will lose the configured IP address and default to 192.0.2.5, so you'll need to be in front of it to connect.

Also look in /var/hf and take off any .tar files in there (hotfixes for Assistant), use WinSCP as an SFTP client. After a reinstall you can put the hotfixes back on.

 

[donb01]

Sorry, I normally do not check in here on the weekends unless I get an E-mail saying there was a thread response or something.

Try to login to Assistant with user rsca and password Siemens2000 and see if you can at least get in there. If you get in it's probably going to want you to change the password. I think I got stuck there once and I just changed it to the same as engr - but I don't think anyone uses that account anymore.

Unfortunately this is V5 and there isn't a portal - otherwise I would have you try to log in there with engr and the regular password just to verify the account is OK.

I never had to do a lot with unixware on V5 - most of the stuff I did on unix vas on a different platform. I am in there more on V7 but that is no longer unix, and the whole topology is different so that won't help much.

I guess as a Hail Mary at some point after hours you could do a hard restart of the whole system (unixware). Sbcsu or someone will have to refresh my memory here - on V7 I know you can login as root and then just type reboot, I think on V5 you go in and type init 6 to restart the unix boot. It will probably take 5 - 10 minutes for the system to come back up for call processing and may take an additional 5 - 10 minutes before Assistant is ready.

Also a strong word of warning... If there is some marginal disk error going on or something else strange there is always a risk your system might not reboot, so I would definitely use that as a last resort, and normally I would say to be sure to have a full backup on your CF card or MO - you can actually do a type of backup that would allow you to boot off of CF/MO in an emergency, but of course you need to have assistant to do that... (




Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[sbcsu]

Thanks Don - I normally put in another user (myself) with own password etc. so if the engr/rsta etc. usernames/passwords are compromised I have that back door.