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]

Go to Comwin and logon

EXE-UPDAT:BP,ALL;
EXE-UPDAT:A1,ALL;
RESTART;

This will do a soft restart which will log you out of Comwin and restart the assistant.
It will not affect calls in progress.

 

[jgbmt]

Thank you SBCSU!

How long should I wait after the RESTART; before Assistant is available again?

 

[sbcsu]

It will take a few minutes at least.
Start a PING to the Assistant IP Address with a -t to keep it going.

 

[jgbmt]

I ask this because although the Assistant landing page is available, it will not allow me to sign in...

it states System error! Please try again or contact your system administrator...

Thanks for your help!

 

[jgbmt]

it is responding to ping & http ??

 

[jgbmt]

sbcsu, any additional input?

 

[sbcsu]

If the page is there but does not allow you to log on then it is not fully up and running yet.
If after 15 minutes there is no logon then go back to Comwin and ensure the hard drive is fully activated

ACT-DSSM:A1,1,;

 

[sbcsu]

Well is it back yet ?

 

[jgbmt]

all areas > ALREADY ACTIVATED

... still will not allow me to log in ... ??

 

[sbcsu]

OK then it must have defaulted back.
Try
engr
Siemens2000

 

[jgbmt]

same message:

System error! Please try again or contact your system administrator...

 

[sbcsu]

Did you ACT-DSSM:A1,1; ?

Check the HISTA on Comwin to see any relevant errors - STA-HISTA:SEARCH;

 

[sbcsu]

You can connect to the Service 9 PIN D Type COM Port connector on the ADS (Bottom Processor)
Use Hyperterminal 38400 8N1NN
You should be able to see the status there or do a Unix re-install.

Any errors showing on the STA-HISTA:SEARCH; ?

 

[jgbmt]

yes, performed ACT-DSSM:A1,1; and all areas show ALREADY ACTIVATED

no errors in hista

how can i access unix to do

cs_control stop
cs_control start

 

[sbcsu]

Do you have an engr password or are you logging in as rsta or other username ?
There has to be some errors of relevance in the HISTA after doing a soft restart

 

[jgbmt]

using engr x etc... to access Assistant ... comwin does an autologon so i don't enter creds

STA-HISTA:SEARCH; just listed red cross connect type messages

 

[sbcsu]

donb01 is probably more familiar with your setup and hopefully he will be along soon to give more advice.
the RESTART; has always worked for me, I might have to put in engr/Siemens2000 rather than my normal logon but that is it.
And I always get relevant errors showing up in HISTA
The RESTART; is a soft restart and always produces errors in the HISTA file.

 

[jgbmt]

thank you sbcsu

donb - are you available to assist?

anyone else?

 

[member 1453342]

Hista will tell you nothing apart from Unix boot and base system loaded. DSSM is not going to help here.

You didn't need to give the ADP a soft restart, you could have rebooted the Unixware only, using UBA. But it doesn't matter, it hasn't recovered correctly and so it probably would have died either way.

You need to connect with command line to look further. V5 was SSH not telnet I think so putty will work fine. You should putty to the IP address of the Assistant and try and login with your engr login. Once logged in, you can make the cs_control (you could have done this to start with but too late now) but it won't fix your login issue.

The login issue will be something else but difficult to know what. The Assistant is running but one of the applications is not. I'd first check that you don't have any full partitions, use "df -kh".

If you don't have putty, from comwin you can use "sta-uw7;" and login from there, I think that's still there in V5. If not, get putty.

You can make a manual reinstallation from command line which would solve the problem but you'd need to reconfig IP, gateway, etc afterwards as it would install on the 192.0.2.5 default. That's assuming the install files are still there and I'm sure they will be. Reinstall would be a reliable way to solve it, takes about an hour, no telephony downtime. If you have regular HBR backups you can restore afterwards but no need unless you had any personal data in the CM, room, location, etc. If not, I'd just reinstall and correct IP config.

Check for full partitions first. If there are any, clean up and reboot (reboot/init 6 will work fine).