Hi Path 4000 V1.0 boot trouble 2

[cuecuito]

Help,

I had a trouble: a Hi Path 4000 had to be turned off for changing its position into the telecommunications site.

When it was connected to power supply again, system could not be booted. Display got boot process until number 6, and again 0...6.

So, I used a MO disk that initially was created as backup and I achieved the PBX boot well again but with the ancient configuration.

I deleted the MO ancient configuración from LDPLN until BUEND in order to restore settings; finally I configured all again with today settings.

The MO disk is adjacent to hard disk when it originally booted before.

I guess this PBX has a DSCXL card with a DB-25 dongle connector.

At the end I saved my settings with the typical AMO when hard disk running:

EXEC-UPDAT: BP,ALL;

The big question is.....if the PBX were turned off again, would it run with new settings booting from the MO?

I shall appreciate your comments, I apologize my lack of enough knowledge

 

[Moriendi]

When the 4K is powered up, it will try to boot from HD-PDS. If that fails it will try to boot from MO (and after that, another area called HD-GLA). You can also boot from MO manually even if the HD is good.

The exe-updat:bp,all; will write to whichever device is marked "ACTIVE LOAD DEVICE" if you make a DIS-DDSM:A1; If you booted from the MO, the MO will be the active load device.

If the 4K is turned off, it will again try to boot from HD, then MO.

If you are sure the HD is corrupt, you need to boot from MO and make a COPY-DDRSM:A1,6,E,1,E,N,; This will copy the bootable area from MO to HD. assuming all disk areas are OK etc.

After that, it should be OK to boot from HD.

The Unixware (Hipath Assistant) partitions are also on the HD, so maybe they are running, maybe not, you don't say. The copy-ddrsm will have no effect on them.

 

[cuecuito]

Thanks a lot. I have thought the HD is damaged or corrupt as you said because displays goes to 0 to 6 on and on. I isolated the HD and booted from MO. All cards in LTU turned OK and Q2270-X turned A. This means that MO works fine.

Unfortunately, when I want to display configuration, there is an error about a “inconsistency of contracted software....” that usually is resolved by CHA-DATE, but access to AMOs is denied because there is a problem with Dongle.

When I type DIS-CODEW, I see rows at FREE column the signs !!!!!!

Besides a message in red words that days CODEWORD INVALID THE AMO INTERFACE WILL BE LOCKED!!!

I typed again CHA-DATE and in despite of message of “change completed” is shown, brown words appear and say “exception 5 when changing time/date- battery buffering of the hw clock”

How can it be possible? Dongle has never been removed or change from this PBX. Besides that, all cards at LTU turned ON and enable, that means that BCSU command at the MO configuration is OK”.

I will appreciate you share support once again, otherwise I would have to give up since we have no enough budget to repair it.

Regards

 

[cuecuito]

Hi.

I have resolved this issue.

I asked a friend to share the latest backups from general REGEN by VEGAS, etc, etc.

I realised that the DONGLE codewords were different between 2006 backup and 2007. How could it be possible if no Siemens support was given at that time?

ADD-CODEW: (new code) and voilà.
Amazing

 

[cuecuito]

How can I save a copy from HD to MO in V1 and flash card in V4? Using DDSRM?

Thank you

 

[Moriendi]

Yes DDRSM

The same as above, COPY-DDRSM:A1,6,E,1,E,N; copies area E (PDS) from device 6 (MO) to device 1 (HD), the same command with device numbers reversed copies the other way, so you want COPY-DDRSM:A1,1,E,6,E,N; to copy area E from HD to MO/CF.

Area E is all you need to boot the PBX. Area F can have regens on it so that is worth copying across too.

If you put a blank MO/CF in, you need to initialize it first STA-INIT:A1,A1H61;

To use copy ddrsm, the destination must be deactivated with DSSM first. So if device 6 was IN SERVICE and the ddrsm failed, you would DEA-DSSM:A1,6; to deactivate it, then you could copy from 1 to 6. It will let you deactivate the active load device, the 4K will stay working, but you will have no AMOs, so you would have to activate it with ACT-DSSM:A1,etc. If the media goes defective due to you changing the card/mo, CHA-DSSM:A1,6; will change it from DEFECT to deactivated. Then you can init and copy ddrsm..

Your post above. The 4K will load with an expired/exceeded codeword, the boards will all go green. Bad codeword just stops the administration and after 30 days, some features. But it will always load the boards.

 

[cuecuito]

Oh I appreciate you took time to reply my post. I am going to apply your advices and procedure. Then only thing I do not certainly know is whether the CF is blank or empty in order to DEACT with DSSM. The CF was added by Siemens when the enterprise bought the Hi Path 4000 but has never been used.

Regards

 

[Moriendi]

Before you remove the MO or CF the device should be blocked by AMO, with DEA-DSSM:A1,6;

It will then show as blocked.

DIS-DDSM:A1,C,6;
H500:  AMO DDSM  STARTED
CONTROLLER: 6           
         TYPE: HD  SS-NO : <STDH7>  SIZE :  2860 MB (  45775*64KB) GRAN : 512
AREA: A  NAME     : A1H6A       STATUS    : B L O C K E D  B Y  A M O   
         AREA-SZ: 0     MB  (2    *64KB)        A-GRAN: 512  
AREA: E  NAME     : A1H6E       STATUS    : P R E S E N T               
         CONFIGURED LOGICAL NAMES:
            :PDS:                                                  
         NO LOGICAL NAMES ACTIVATED
         AREA-SZ: 450   MB  (7200 *64KB)        A-GRAN: 4096

If you forget to block it (and it wasn't already blocked) it will probably show as DEFECT instead. That's the time to use CHA-DSSM:A1,6; which will change it from defective to blocked.

If you are not sure of the status of the CF, just make a STA-INIT:A1,A1H61; and then a copy-ddrsm from 1 to 6. It doesn't matter if the media is new,old, blank, not blank, the sta-init will just reinitialize it.

 

[cuecuito]

Thank you Moriendi. I assume the CF (Hi Path 4000 V4) is empty, because the PBX had no inicial configuration but only Dongle values, BCSU equipment including all CSPi modules. I am going to do what you adviced based on STA-INIT AMO command.

By the way, an error was shown when I typed COPY-DDS as shown in attachment.

Would I have forgotten a step in process (STA-INIT or DEACT-DDSM)

 

[Moriendi]

If I saw that error I would try a sta-init:a1,a1h61; next.

 

[cuecuito]

I’ll try and then after results I will tell if it worked out.

Regards

 

[cuecuito]

 

[sbcsu]

It may be that your system is configured for MO but you are using CF

HiPath 4000 Change from MO Magneto Optical to CF Compact Flash

REG-DDSM;

Delete the MO Disk:
DEL-DLSM:A1,":MOD-SCR:";
DEL-DLSM:A1,"MS:"&"SY:";
DEL-DLSM:A1,":CGD:";
DEL-DLSM:A1,"BDA:"&"BD:"&":TMD:"&"AS:"&":AMD:"&"MP:";
DEL-DLSM:A1,"DS:";
DEL-DASM:A1,6;
DEL-DCSM:A1,6;

Add the CF Disk: V3 and V4 Only
ADD-DTSM:A1,HD,18932,512,"CF1G3";
ADD-DCSM:A1,6,HD,"CF1G3";
ADD-DASM:A1,6,3200&992&2400&1120&11217&3200&9868,4096&4096&4096&4096&4096&4096&4096;
ADD-DLSM:A1,6,E,"DS:";
ADD-DLSM:A1,6,F,"BDA:"&"BD:"&":TMD:"&"AS:"&":AMD:"&"MP:";
ADD-DLSM:A1,6,G,":CGD:";
ADD-DLSM:A1,6,H,"MS:"&"SY:";
ADD-DLSM:A1,6,I,":SCR:";


Add the CF Disk: V2 V2 V2 ONLY
ADD-DCSM:A1,6,HD,"CF1G3";
ADD-DASM:A1,6,3200&992&800&1120&12817,4096&4096&4096&4096&4096;
ADD-DLSM:A1,6,E,"DS:";
ADD-DLSM:A1,6,F,"BDA:"&"BD:"&":TMD:"&"AS:"&":AMD:"&"MP:";
ADD-DLSM:A1,6,G,":CGD:";
ADD-DLSM:A1,6,H,"MS:"&"SY:";
ADD-DLSM:A1,6,I,":MOD-SCR:";


On V4 you can COPY area's E and I to the CF to make a startup V4 CF disk
COPY-DDRSM:A1,1,E,6,E,N;
COPY-DDRSM:A1,1,I,6,I,N;


To find out the ones you can add:
DISP-DTSM:A1,HD;

If the system does not take the "CF1G3" then try "CF2G0" then try "2GIGA" or "STHD5"
If it is a Version 2 you will have to update the Unixware for the CF1G3 to be accepted