Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
System error
- Thread starter mystr
- Start date
It's been many years since I've worked on a Siemens system but I've experienced that on a 9006 system when the hard drive was bad or 'In defect'. There's a way to effectively reset the status and put it back in service as long as there's not a hardware error, It was CHA-DSSU... I think followed by the controller number. I think 6 was that DAT drive (that's how long ago it was). There are others here that are familiar with the system that will hopefully see this and give you the correct information. In that mode certain RMX commands would still work, such as to reactivate the hard drive, but not database commands as shown above.
This is nothing to do with date/time. The hard disc has been marked defective by the RMX. It might be bad, or it might not.
First step is to try and change it from blocked by dependability (which it probably is, but might just be deactivated (unlikely)).
cha-dssm:a1,1;
act-dssm:a1,1;
That will try and bring the HD in service. If the HD is physically dead, it won't help. Put your hand on it - is it hot/cold? Is it spinning? V3 4K is what, 20 years old now? HD failure seems likely.
If the HD is dead, you need to try and get a replacement. If you have taken regular backups (DDRSM) to MO/CF, you are OK. If not, you have a problem.
First step is to try and change it from blocked by dependability (which it probably is, but might just be deactivated (unlikely)).
cha-dssm:a1,1;
act-dssm:a1,1;
That will try and bring the HD in service. If the HD is physically dead, it won't help. Put your hand on it - is it hot/cold? Is it spinning? V3 4K is what, 20 years old now? HD failure seems likely.
If the HD is dead, you need to try and get a replacement. If you have taken regular backups (DDRSM) to MO/CF, you are OK. If not, you have a problem.
The symptom with the time and date not set I thought was bars on the displays of Optisets. Glad someone with knowledge of the system came in. Sorry about the wrong AMOs. I recall years ago I had several Mod 30 9006s where the hard drives started getting quite noisy. Suspecting the worse - I took the DAT backup (the common media back then) and built replacement hard drives in a spare 9006 I had. One day the tech that visited one site routinely let me know the hard drive was now quiet. Sure enough, it wasn't running anymore. I went there the next morning and was able to install and load the system from the replacement hard drive.
Last edited:
Yes, there is a flow of tests - Clock, Hard Drive, Codeword etc.
V3's are nearly 20 years out now, you can replace the hard disk/magneto optical with either laptop hard drive and Compact Flash or SSD Drive and CF.
You should be backing up to Area J of the drive as well just in case.
V3's are nearly 20 years out now, you can replace the hard disk/magneto optical with either laptop hard drive and Compact Flash or SSD Drive and CF.
You should be backing up to Area J of the drive as well just in case.
- Thread starter
- #8
Did commands this is what I got does this confirm HDD is dead ?
Attachments
It doesn’t look good but you would not normally expect the F17 error with a dead HD. It is telling you the disk partition structure it has loaded in memory (the DB) does not match what it sees physically on the disc. But reason for that would be unknown, perhaps the disc structure is corrupted.
Make a DIS-DDSM:A1;
If this is a CPCI chassis not the older H300/Atlantic architecture you can’t physically touch the disc so hard to tell if it’s running. What is the 2nd device in the disc plate - MO or CF? Have you ever made a backup to that device ?
Can you ping the Assistant from that PC? 192.0.2.5.
Make a DIS-DDSM:A1;
If this is a CPCI chassis not the older H300/Atlantic architecture you can’t physically touch the disc so hard to tell if it’s running. What is the 2nd device in the disc plate - MO or CF? Have you ever made a backup to that device ?
Can you ping the Assistant from that PC? 192.0.2.5.
- Thread starter
- #10
Doesn't seem I can load any AMO.
192.0.2.5 gives 100% paquet loss.
We using h350e the hd is visible from chassis.
No one ever did backup but a backup "should be" in optical disk that I have ...
Just need to confirm if hd is faulty to ask for a change and if it has to be a specific hd (for exemple current one is 9gb storage)
192.0.2.5 gives 100% paquet loss.
We using h350e the hd is visible from chassis.
No one ever did backup but a backup "should be" in optical disk that I have ...
Just need to confirm if hd is faulty to ask for a change and if it has to be a specific hd (for exemple current one is 9gb storage)
- Thread starter
- #11
It seems to me that this is the Hicom 300H V3.0.6 software version (P30252-N4106-B000-00). Take a high-resolution photo of all the system shelf modules for a complete understanding and photo of the processor board. You will have big problems by yourself-recovery of a disk that has a SCSI-1 interface.
OK, when I asked if the hard drive was warm/spinning, and you didn't answer, I thought it was because it was maybe a CPCI chassis. But you just didn't do it.
So again - is that hard drive spinning or not? Touch it. Is it cold.
I suppose it doesn't matter, I think the hard drive is dead.
The MO drive is empty. Where is the MO that should be in that device? If someone has made at some time a bootable backup (copy-ddrsm) to the MO, you will be able to reload the ADS separately, and then make an exe-updat to copy the current DB onto the MO. You can only do that if the H300 is a simplex or duplex processor (ADS is then separate). If it's a mono processor, ADS and BP are in the same processor and you can't treat them separately. As Masviss says, photo of full processor shelf would reveal.
Ping is bad. 192.0.2.3 was not the address to check - that's the ADS, we know it's working, you are talking to it with Comwin. 192.0.2.5 is the Assistant, which should be running on the HD. If it was pingable, HD is good. Of course there are other reasons for Assistant to not be running but, normally it is. If you can't ping 192.0.2.5, either Assistant is not running or HD is dead.
First step is to try and preserve the database by copying it to the MO. Then you probably need to find a replacement HD. Maybe the HD is just corrupted and you could copy from MO to HD, but who knows.
So again - is that hard drive spinning or not? Touch it. Is it cold.
I suppose it doesn't matter, I think the hard drive is dead.
The MO drive is empty. Where is the MO that should be in that device? If someone has made at some time a bootable backup (copy-ddrsm) to the MO, you will be able to reload the ADS separately, and then make an exe-updat to copy the current DB onto the MO. You can only do that if the H300 is a simplex or duplex processor (ADS is then separate). If it's a mono processor, ADS and BP are in the same processor and you can't treat them separately. As Masviss says, photo of full processor shelf would reveal.
Ping is bad. 192.0.2.3 was not the address to check - that's the ADS, we know it's working, you are talking to it with Comwin. 192.0.2.5 is the Assistant, which should be running on the HD. If it was pingable, HD is good. Of course there are other reasons for Assistant to not be running but, normally it is. If you can't ping 192.0.2.5, either Assistant is not running or HD is dead.
First step is to try and preserve the database by copying it to the MO. Then you probably need to find a replacement HD. Maybe the HD is just corrupted and you could copy from MO to HD, but who knows.
- Thread starter
- #14
Attachments
- Thread starter
- #15
About hd spinning I did what said just forgot to answer... I touched it seems to be spinning and not too hot average temperature looks normal to me but I don't really know.
I have MO but not inserted which what It used to be. From what I learned it supposed to hold a back up.
OK so here is where you have to take a risk. If you are confident the MO contains a bootable backup, you can attempt to reload the ADS from the MO, which will bring AMOs back (and reload the ADS with whatever config is on the MO), but the telephony (SWU) DB will remain the same. Then you can save the current telephony DB to the MO, and you have then a good current backup. Your picture shows you have a duplex processor (ADS, BPA, BPB), but also shows your standby processor (BPA) is not in standby state. It also shows no SL100 NIC in the DPC5s so no customer LAN connection, and only one connection to the HUBC, which is your admin PC? Hopefully not a HPPC/OSCC contact centre, because if so, reloading the ADS will stop the CSTA connection.
Bad case for this, the MO does not load. Then you have a SWU working still on BPB only, but no ADS or BPA. Now you will need a replacement HD/good MO disc. Not so easy to get for this old software.
Posts like this really show the need for good, regular backups.
Bad case for this, the MO does not load. Then you have a SWU working still on BPB only, but no ADS or BPA. Now you will need a replacement HD/good MO disc. Not so easy to get for this old software.
Posts like this really show the need for good, regular backups.
- Thread starter
- #17
- Thread starter
- #18
What commends to load back up from MO ?
You can't use the EXE-RELOAD command because of the defective HD - no AMOs.
If you press the reset key on the ADS DPC5 (left most processor) the processor will try to reload off the HD. It might even work, depends what is wrong. But when it fails to load off the HD (SCSI ID 0, RMX device 1), it will try and load from the inserted MO (SCSI ID 5, RMX device 6). The MO drive should be set as that device already, but.. cannot be sure. Usually is.
You will know if that has worked because the MO drive LED will be flashing/blinking as it loads, and the ADS processor will reload to the -. sign like you see now.
If it can't load, it will flash 3 bars, 0,1, and an error code. Then you have a real problem. The SWU will still be working, but if there is a power cut or the SWU tries to reload, you will have a dead switch. So you must be sure you have a good bootable backup (created with DDRSM AMO).
If you press the reset key on the ADS DPC5 (left most processor) the processor will try to reload off the HD. It might even work, depends what is wrong. But when it fails to load off the HD (SCSI ID 0, RMX device 1), it will try and load from the inserted MO (SCSI ID 5, RMX device 6). The MO drive should be set as that device already, but.. cannot be sure. Usually is.
You will know if that has worked because the MO drive LED will be flashing/blinking as it loads, and the ADS processor will reload to the -. sign like you see now.
If it can't load, it will flash 3 bars, 0,1, and an error code. Then you have a real problem. The SWU will still be working, but if there is a power cut or the SWU tries to reload, you will have a dead switch. So you must be sure you have a good bootable backup (created with DDRSM AMO).
I remember those days - more than once where the processor would flash 3 bars, then keep repeating the process. I had times where the RMX backup wouldn't load from the DAT, and had to run the cleaning tape through a few times. At least this system has a MO, that must be much more reliable and less prone to degradation. Speaking of that - after the weekly DAT backup was done I'd look at HISTA, If I saw 'Quality degradation' at least once I'd change run the cleaning tape through and insert a new or different DAT.
Hoping for the best with this situation.
Hoping for the best with this situation.