Hicom 330H - What will be affected by soft restarting exchange

[nscripta]

We have a Hicom 330H used in a bespoke configuration where we have received specific training by Siemens to carry out basic functions e.g. card swaps, circuit moves, backups. There is a fault on the system at the present time where the exchange is running from the MO drive and the hard drive is blocked. Siemens have attended and their initial investigation has advised that a soft restart is carried out to see if the problem is resolved. What will the effect of carrying out a soft restart, will all traffic be 'lost' for a specific period of time. (It is a single processor system)
If the restart does not resolve the fault, Siemens are advising the next step will be to get a replacement hard drive sourced.

 

[birdseye51]

A soft restart will not disconnect established calls. Calls that are being set up e.g being dialled will be disconnected. Normally a soft restart will take about 10 seconds.

 

[birdseye51]

Have you actually tried activating the Hard Disk

DIS-DDSM:A1;

This will give you the status of the HD & MO and the active load device.

You can try activating the HD

ACT-DSSM:A1,C,1;

On the Hicom 300H, SW-DSSM can be used to switch the active load device back to the HD.

 

[nscripta]

birdseye51,

The following is the output from the DIS-DDSM:A1 command, it implies that both the HDD and the MO drive are blocked!!

------------------------------------------------------------------

<DIS-DDSM:A1;
DIS-DDSM:A1;
H500: AMO DDSM STARTED
CONTROLLER: 1 IS ACTIVE LOAD DEVICE
TYPE: HD SS-NO : <M1300> SIZE : 1300 MB ( 20800*64KB) GRAN : 512
DATA MEDIUM NOT INSERTED, OR NO VALID ADMINISTRATION AREA FOUND
CONFIGURATION FROM DATABASE:
AREA: A NAME : A1H1A 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 : A1H1E STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 131 MB (2100 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 512
AREA: G NAME : A1H1G STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 35 MB (560 *64KB) A-GRAN: 512
AREA: H NAME : A1H1H STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
MS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 60 MB (960 *64KB) A-GRAN: 512
AREA: I NAME : A1H1I STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 10 MB (160 *64KB) A-GRAN: 512
AREA: J NAME : A1H1J STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:GLA:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 131 MB (2100 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 870 MB (13925*64KB) A-GRAN: 4096
CONTROLLER: 4
TYPE: HD SS-NO : <MO500> SIZE : 500 MB ( 8000*64KB) GRAN : 512
DATA MEDIUM NOT INSERTED, OR NO VALID ADMINISTRATION AREA FOUND
CONFIGURATION FROM DATABASE:
AREA: A NAME : A1H4A 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 : A1H4E STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 131 MB (2100 *64KB) A-GRAN: 4096
AREA: F NAME : A1H4F STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 300 MB (4800 *64KB) A-GRAN: 4096
AREA: G NAME : A1H4G STATUS : P R E S E N T
NO LOGICAL NAMES CONFIGURED
AREA-SZ: 68 MB (1097 *64KB) A-GRAN: 512
CONTROLLER: 6
TYPE: HD SS-NO : <500M > SIZE : 500 MB ( 8000*64KB) GRAN : 512
CONFIGURATION FROM DATABASE:
AREA: A NAME : A1H6A STATUS : I N S E R V I C E
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H6E STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
ACTIVATED LOGICAL NAMES:
DS:
AREA-SZ: 131 MB (2100 *64KB) A-GRAN: 4096
AREA: F NAME : A1H6F STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
ACTIVATED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 512
AREA: G NAME : A1H6G STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
ACTIVATED LOGICAL NAMES:
:CGD:
AREA-SZ: 35 MB (560 *64KB) A-GRAN: 512
AREA: H NAME : A1H6H STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:
ACTIVATED LOGICAL NAMES:
MS:
AREA-SZ: 60 MB (960 *64KB) A-GRAN: 512
AREA: I NAME : A1H6I STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
SY:
ACTIVATED LOGICAL NAMES:
SY:
AREA-SZ: 10 MB (160 *64KB) A-GRAN: 512
AREA: J NAME : A1H6J STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
NO LOGICAL NAMES CONFIGURED
AREA-SZ: 201 MB (3225 *64KB) A-GRAN: 512
AMO-DDSM -10 DISK STATUS
DISPLAY COMPLETED;

------------------------------------------------------------------

 

[donb01]

It's interesting that it says blocked by AMO rather than blocked by dependability - almost looks like someone deactivated it by accident...

 

[birdseye51]

The HD is the active load device and is blocked by AMO-DSSM.

De-activate the MO drive,

DEA-DSSM:A1,6;

Then activate the HD

ACT-DSSM:A1,1;

Then make sure you can access AMOs

 

[nscripta]

Update on fault,

As per Siemens recommendations, the soft restart was carried out on the exchange, this made no difference. Siemens engineer attended site, amo blocked MO drive successfully then attempted to activate HDD. This was unsuccessful, response was 'not blocking by dependency (error 2B)'. Siemens carried out a hard reset on the HDD/MO drives by removing/re-inserting the card. A further attempt was made to activate the HDD, the drive could be heard spinning, this happened around 5 or 6 times then the amo response was the HDD could not be activated.
Siemens are arranging for a replacement HDD to be 'built' for subsequent installation.