Hipath4000 V6 unable to do Regen and Persdata

[Koolcom]

Hi maybe someone could come up with a solution everything was fine until a power failure, then I noticed that I could not import a file into Persdata and in Comwin you cannot regen-scsu; but you can do a regen-scsu:1234; you can display the extensions as well, what I have done is reloaded the system from a backup and I have reinstalled the Assistant but alas all is still the same. Any ideas please

The Kool Guy

 

[sbcsu]

DIS-CODEW;

ACT-DSSM:A1,1;

 

[Koolcom]

Thanks SBCSU but date is correct codew is fine and HD is in service

The Kool Guy

 

[sbcsu]

What does it say when you
REG-SCSU:1234;

 

[sbcsu]

You say you reloaded it from a backup - when was the backup from - why did you reload it and how did you reload it from a backup.
Was extension 1234 available on that backup or was it more recent.

 

[Koolcom]

REG-SCSU:4001;
H500: AMO SCSU STARTED
ADD-SCSU:4001,1-2-13-22,ANATE&FAX,0,0,30,35,10,10,10,15,0,1,1,10,0,,,VAR,,,,ENGL
ISH,YES,,NO,,,,0,DIR,YES,NO,0,;

AMO-SCSU -111 STATION CONFIGURATION OF SWITCHING UNIT
REGENERATE COMPLETED;

This gives no result

REG-SCSU;
H500: AMO SCSU STARTED

AMO-SCSU -111 STATION CONFIGURATION OF SWITCHING UNIT
REGENERATE COMPLETED;

Reloaded from HD-2 same results but thats because they are synchronized just thought I would try

The Kool Guy

 

[Moriendi]

This looks nasty, but difficult to say what your problem is, because you said you can't reg-scsu (which is RMX) and can't import persdata (which is the Assistant). They are two different things, I can't see why a problem with one would affect the other.

But reg-scsu:4001; working, and reg-scsu does not, it looks like DB corruption. What do you get if you try to make a sta-regen? Even if it fails it can sometimes give you a clue as to where the corruption is by looking at how far it got. Doesn't mean that would help.

Even if updating the 4K might help (you don't say what software you are), the damage is already done. By that I mean update might prevent but not cure.

It also doesn't make much sense that a restore has the problem also, I wonder if the issue was there a bit longer than you think, and it just got noticed after the power off.

You said dis-scsu works? Maybe it's worth making a dis-scsu for the whole DB, using a macro to convert the output to a reg-scsu for each number, and testing if each extn will regen individually. If you find one that can't, maybe make a del-scsu on it. Might work, might restart the 4K. If you can't dis-scsu for all of them, try an individual reg-scsu for each one, look for a different behaviour in the response... see if there's one worth deleting.

 

[sbcsu]

It MAY also be your loadware or lack of loadware.
In the past for example there was a problem with the LDPLN AMO where you could delete them and they did not REGEN-LDPLN but they were still there.
The loadware fix - fixed that problem.

Please supply us with the Version of HiPath you are using.

In Comwin try 'macro' then retrieve system variant

 

[Koolcom]

RMX V6 R1.12.73 / Assistant V6 R1.13.11
Platform V6 R1.12.2 / CSTA

Found the extension that's causing the problem see below:
Now the problem is to delete the wabe entry


DIS-WABE:GEN,,,,STN;
H500: AMO WABE STARTED
------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| | CALL PROGRESS STATE |NODE/DIGIT| RESERVED/CONVERT |
| CODE | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| 4441 |. .**** ***** **... ..... .*| STN | |
| | | |DESTNO 0 |
| | | |DNNO 0- 0- 1*|
------------------------------------------------------------------------------

AMO-WABE -111 DIALLING PLANS, FEATURE ACCESS CODES
DISPLAY COMPLETED;
<dis-sdsu:all,,stno,per3,4441;
DIS-SDSU:ALL,,STNO,PER3,4441;
H500: AMO SDSU STARTED

STATION NUMBER ACCORDING TO PORT EQUIPMENT NUMBER
-------------------------------------------------
MOUNTING LOCATION MODULE NAME BDL BD(#=ACT) STATUS
H13: NO PORT EQUIPMENT NUMBER FOUND FOR THE COMBINATION OF STNO/SVC
H01: SPECIFIED STATUS NOT FOUND

AMO-SDSU -111 STATUS DISPLAY IN SWITCHING UNIT
DISPLAY COMPLETED;
<reg-scsu:4441;
REG-SCSU:4441;
H500: AMO SCSU STARTED

AMO-SCSU -111 STATION CONFIGURATION OF SWITCHING UNIT
AMO ABORTED; PROCESSOR FAILURE IN TARGET UNIT;
<reg-sbcsu:4441;
REG-SBCSU:4441;
H500: AMO SBCSU STARTED

AMO-SBCSU-111 STATION AND S0-BUS CONFIGURATION OF SWITCHING UNIT
AMO ABORTED; PROCESSOR FAILURE IN TARGET UNIT;
<dis-scsu:4441;
DIS-SCSU:4441;
H500: AMO SCSU STARTED

AMO-SCSU -111 STATION CONFIGURATION OF SWITCHING UNIT
AMO ABORTED; PROCESSOR FAILURE IN TARGET UNIT;
<dis-sbcsu:4441;
DIS-SBCSU:4441;
H500: AMO SBCSU STARTED


The Kool Guy

 

[Koolcom]

I deleted all the extensions however doing a regen there are no entries for extensions lucky this is a test unit so I can play at random. I can add a extension and regen it and display it and it's there but will not appear if I do Reg-scsu; or reg-sbcsu;

The Kool Guy

 

[Koolcom]

SYSTEM VARIANT

DISPLAY-VEGAS:LIST=SHORT,UNIT=SWU&ADS;
H500: AMO VEGAS STARTED
SYSTEM NO. AMO APS NO. START USER STATUS
SWU: L31912Q1427A00001 REGEN P30252B4800B00101 27.08.20 07:18 JOE FINISHED
ADS: L31912Q1427A00001 REGEN P30252B4800A00101 27.08.20 07:19 JOE FINISHED

AMO-VEGAS-111 ADMIN. OF DATABASE GENERATION RUNS ON SUPPORT SYSTEM
DISPLAY COMPLETED;
<DISPLAY-APS:TYPE=PSGL,SP="Y0-*";
DISPLAY-APS:TYPE=PSGL,SP="Y0-*";
H500: AMO APS STARTED
ADINIT STARTED
PROGRAM SYSTEM : Y0-E30YC
VERSION NUMBER : 60
CORRECTION VERSION NUMBER : 001
PART NUMBER : P30252N4801BH7312|V6 R1.12.73
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

DIR SUBSYSTEM | | OMF SUBSYSTEM
-----------------------+-+-----------------------
ZMITSC00.Y0-EM0.10.001 |*|ZMITSC00.Y7-PMT.10.001

ADINIT COMPLETED
STATUS = H'0000
AMO-APS -111 SOFTWARE LOAD UPGRADE
DISPLAY COMPLETED;
HicomVariant=UV6.0-SA01


The Kool Guy

 

[Moriendi]

If this is in the lab, my next step would be to update to V6 R2 and see what it looked like then, although it does look like DB corruption and you can't always fix that.

 

[Moriendi]

Also might be worth testing if you can regen in chunks, reg-scsu:4000&&4100; that kind of thing. Find out if it works and if it does, where it stops working.

 

[Koolcom]

Thank you all for your input I have upgraded the system to V6 R2 however you could regen-scsu:4000&&4400;

The Kool Guy