9006 backup failure. One or more servers unreachable. any assistance would be appreciated.

[telcomsal]

I have a 9006 single cabinet mod 80 that i took over the maintenance on. I can not get a UBA backup to complete. When i display hista it has the following error.

F2106 M4 N4768 NO ACT A1 IX UNIX APPL MESSAGE 19-01-11 13:03:27

ALARM CLASS:CENTRAL:027
FORMAT:3A
UNIX NAME:ROLMA1 UNIX TIME:19-01-11 13:03:28 RESTART COUNT:0
-- :-- :-- :000: -- -- BST:-- FW: --
XUBA0 UBBMaster.c 1196
USV_EH_REP_ERR
... continue ...






F2106 M4 N4769 NO ACT A1 IX UNIX APPL MESSAGE 19-01-11 13:03:27

ALARM CLASS:CENTRAL:027
FORMAT:3A
UNIX NAME:ROLMA1 UNIX TIME:19-01-11 13:03:28 RESTART COUNT:0
-- :-- :-- :000: -- -- BST:-- FW: --
Could not run Backup; One or more servers unreachable


Any suggestions. I try to connect to the U4 server and a message states that it is not installed or is loading.

thanks

 

[adibv]

Looks like U4 (ACD) server connected to Hicom300H (9006) is down. Try to reboot it.

Err logs under Unix:
# tail /opt/uba/errs.rsca

Try to connect to U4 server from Unix:
# clogin U4

The backup script checks to make sure all configured servers are communicating.
If they are not communicating, the backup script aborts.
If they are communicating, the following RMX commands are performed in this order:
• REGEN-UCSM;
• REGEN-XAPC:A1;
• REGEN-SPES;
• DEACT-RTAPE:UBA;
• EXEC-UPDAT:BP,ALL;
• EXEC-UPDAT:A1,ALL;
• CHANGE-UPDAT:BP,OFF;
• STA-TINIT:"T:TEST/TEST";
• ACT-RTAPE:"T:*",UBA;
• DUMP-SWUPG:":UBA:";
• STA-FCOPY:"DSATCH100/*",":UBA:*";
• DEACT-RTAPE:UBA;
• CHANGE-UPDAT:BP,ON;
The next step backs up the A1 Unix data (UBA, UDSC, EMML and CCMS if on the A1).
If there is a CCMS/ACDAPP server (V1, U1 or U4), then that data (UBA, UDSC and CCMS/ACDAPP) is backed up next.

 

[telcomsal]

Thanks for the info. It appears that the server that is unreachable is the U1 server. I tried performing the following commands without success. I tried deactivating CCMS and activating CCMS. Below are the results. Any other suggestions?

in direct AMO:
EXE-XAPC:A1,DEACT.CCMS,MONO;
H500: AMO XAPC STARTED
F12: ERROR IN IX, ERROR CODE H'0001
AMO-XAPC -111 IX APPLICATION CONFIGURATION
EXEC NOT COMPLETED;

EXE-XAPC:A1,DEATC.CCMS,COP1;
H500: AMO XAPC STARTED
F04: BASE-IX IN STARTUP OR IS NOT STARTED
AMO-XAPC -111 IX APPLICATION CONFIGURATION
EXEC NOT COMPLETED;

EXE-XAPC:A1,ACT.CCMS,MONO;
H500: AMO XAPC STARTED
F12: ERROR IN IX, ERROR CODE H'0001
AMO-XAPC -111 IX APPLICATION CONFIGURATION
EXEC NOT COMPLETED;

EXE-XAPC:A1,ACT.CCMS,COP1;
H500: AMO XAPC STARTED
F04: BASE-IX IN STARTUP OR IS NOT STARTED
AMO-XAPC -111 IX APPLICATION CONFIGURATION
EXEC NOT COMPLETED;
<

 

[adibv]

First:
Log on to UW7 shell via SSH or similar
- execute the following command
vk_activate -c ACDAPP

Next:
act-xapc:a1,base;
act-xapc:a1,base,cop1;

IF any errors/hung here,check if Base Stuck in Startup:
o The AMO 'sta-flist' command for 'a1h1a' or 'v1h1a' shows the state bytes as a '4' - indicating startup.
This indicates that the file 'etc/inittab' is corrupted.
o The sta-fdel command to determine this is :
STA-FLIST:":a1h1a:",800,400,B;
Check bytes 011E and 011F, they should be 02 and 05.
If byte 011F (the last value on line 0110 is a "04", UNIX base is "stuck" in a startup state.

IF Error Reading State Bytes When Activating Base
o "Error reading state bytes" is displaying during activation of UNIX base using AMO 'act-xapc'.
This usually indicates that a 'fsck' - file system check needs to be done.

IF Checksum Errors When Activating Base
When activating UNIX "base" the AMO aborts with the message:
H500 AMO XAPC Started
F22 Loader Error Detected: Checksum Error
AMO - XAPC - 246 IX Application Configuration
ACTIVATE NOT COMPLETE
This usually is an indication that the file /unix (kernel) is missing.

Next:
If BASE is successfully activated, check for F6701 error in hista.
If so:
1) exe-xapc:a1,deact.ccms - deactivate ccms. a1 = server
2) dea-dskx:a1,1,g; - deactivate the g partition of the drive
3) sta-dskin:a1,a1h1g; - initialize the g partition.
4) act-dskx:a1,1; - activate all partitions.
5) dea-xapc:a1; - deactivate UNIX.
6) exe-rest:a1,unit,a1,soft; - soft restart the ADS.
7) act-xapc:a1,base; - activate UNIX.
8) exe-xapc:a1,dbinit.ccms; - should now complete ok.

Last:
check again connectivity with U server.

I assume this answer also to:

https://www.tek-tips.com/viewthread.cfm?qid=1792092

Be careful with your actions !
If connectivity still not working, than issue must be on U1 server or corrupted UNIX database (fresh reinstall/restore perhaps)
Just let me know the results (eventual errors)

 

[telcomsal]

OK, this seems a little out of my realm of knowledge. I only have remote access to this system at this time. What if any of this can I do remotely without bringing the system to its knee's. I am not that familiar with most of the commands you have listed. When i display the hardware map (BCSU) I don't see a U1 processor. Is there a command to confirm that there is actually a U1 server on this switch.
I appreciate all your help on trying to figure out why the backups will not complete.

 

[adibv]

There is no significant difference if you have a U1 or U4 back up server.
My analysis were based on the info you have provided.

If you are no sure of actions to take , you don't feel comfortable with them and indeed there is a risk in "bringing the system to its knee's", I suggest to ask for official support (Unify) considering that this is a sensitive issue and more , this is a legacy system, not easy to admin.
I cannot tell for sure which network architecture is on site and I don't know if you are in contact with the network architect who installed the system.

Forum goal I think is to give hints,knowledge share and not to provide ultimate solutions or training
(as some of forum users expects )

 

[donb01]

Sal,

Are you trying to do your backup to the DAT drive? If so, those DAT drives can get flaky, but I was told by a tech once upon a time to "clean the pi$$ out of it". I went through my fair share of ~ $300 replacements before I bought the $30 cleaning tape and ran the cleaning procedure 10 times in a row and they would magically start working again. Also try it with NEW tapes. The DDS60 were getting hard to find at the end, but I was using DDS90 and they were still OK. I always formatted the tapes on the exact drive I was going to use them in (STA-TINIT but I don't remember the exact command string - something like DS:"BACKUP1",Y; or something along those lines. I rotated the tapes once a week, and after I did the major cleanings I typically cleaned the drive once a month. The backups ran automatically around 8PM on Saturday nights. I know on the HP4K you have to stay away from 2AM because that's when it cleans itself, but on the HICOM I'm pretty sure that 4AM is the witching hour. I do have all the manuals laying around somewhere so if I have to look up the syntax of that format command I probably can. If you are going to do many cleanings you will need someone onsite to put the tape in, and it will eject it when it's done, and then just remove it and put it back in again. That's the most I have for you. The only ACT and DEACT commands I ever used were for XAPC as shown above, but I always used just BASE - I don't know what that CCOP1 thing is unless it is a second server. On the last one I had I also had to activate and deactivate the ACD server, but I don't remember how to do that at all!


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