When running the REGEN AMO on a 9006 system, I wonder are only the current entries generated? For example, ADD-SCSU:3456... was run to add a phone a month ago, but the phone has since been deleted. Same with LDPLN, would entries no longer current not be shown with REGEN?
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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
REGEN question 9006
- Thread starter keyset6
- Start date
Iamnothere
Technical User
Typically a STA-REGEN produces a file containing the AMO commands from the active SWU, or ADS/ADP, or both, based on the AMO REGEN command. I suspect that your system has re-loaded from your alternate boot device (controller 6). I assume that this system is an old US-based Hicom 300 with a MO drive as controller 6. If the AMOs are not what you expected, how long has it been since you performed a backup to MO?
In your system's DIS-DDSM:A1; output, look at controller 6: does it say that controller 6 is the Active Load Device?
If so, you know WHY the AMOs that you previously deleted have returned. But the more important question is: WHY did your system reload from controller 6?
Your hard disk could be dead, in trouble, or perhaps it just needs to be activated.
Using the same DIS-DDSM:A1; command, check the status of controller 1 > Partition "E", also known as
DS:.
Re-post if you need help. If I were in your shoes, I would guard that REGEN file carefully. It could be your only copy of the Switching Unit database - even if it is outdated. An outdated SWU database is much better than NO SWU database!
Good Luck!
In your system's DIS-DDSM:A1; output, look at controller 6: does it say that controller 6 is the Active Load Device?
If so, you know WHY the AMOs that you previously deleted have returned. But the more important question is: WHY did your system reload from controller 6?
Your hard disk could be dead, in trouble, or perhaps it just needs to be activated.
Using the same DIS-DDSM:A1; command, check the status of controller 1 > Partition "E", also known as
DS:.Re-post if you need help. If I were in your shoes, I would guard that REGEN file carefully. It could be your only copy of the Switching Unit database - even if it is outdated. An outdated SWU database is much better than NO SWU database!
Good Luck!
- Thread starter
- #3
Thanks - a MO drive I wish, this is a cave-man 9006.3! Yes, there's still a few of those out there, running Rolmphones. I was running the REGEN commands on them only to save the commands as a document in the event of needing to build s system from scratch. They are actually running fine except for one with a bad DAT drive. Of course hard and DAT drives are becoming scarce.
I've replaced several over the years, I run the old UTIL script to recover RMX only while retaining Unix, I no longer have a good ISYAPS tape that has the Unix with Direct AMO, so I'll keep the Unix on the drive and have to repeatedly go into Debug mode on the script to skip adding files, or to deactivate/active the HD when necessary. I wish I had the Procomm .was file on the script so I could modify it.
I assume REGEN will only show ADD-SCSU (for example) for the stations that were present from the last system load. Next time I have a hard drive going bad - I'm usually warned when the drive starts getting noisy, next time I may try what worked on the 'lab' 9006. That was building a hard drive with the same release Unix/RMX as the defective drive. Preferably, I'd restore from the bad drive's latest backup. If that's not possible, here's what I've done: The lab switch had system A's database running. Properly deactivate the hard drive with the switching unit up, remove the drive and install another hard drive from system B with the same release Unix/RMX, activate the drive, then EXE-UPDAT:BP,ALL; then same for A1. I was able to power down and reload system A's database.
I've replaced several over the years, I run the old UTIL script to recover RMX only while retaining Unix, I no longer have a good ISYAPS tape that has the Unix with Direct AMO, so I'll keep the Unix on the drive and have to repeatedly go into Debug mode on the script to skip adding files, or to deactivate/active the HD when necessary. I wish I had the Procomm .was file on the script so I could modify it.
I assume REGEN will only show ADD-SCSU (for example) for the stations that were present from the last system load. Next time I have a hard drive going bad - I'm usually warned when the drive starts getting noisy, next time I may try what worked on the 'lab' 9006. That was building a hard drive with the same release Unix/RMX as the defective drive. Preferably, I'd restore from the bad drive's latest backup. If that's not possible, here's what I've done: The lab switch had system A's database running. Properly deactivate the hard drive with the switching unit up, remove the drive and install another hard drive from system B with the same release Unix/RMX, activate the drive, then EXE-UPDAT:BP,ALL; then same for A1. I was able to power down and reload system A's database.
One comment about the DAT drives because I found I was replacing them fairly often as well is that the tech suggested I "clean the pi$$ out of them". So I have had bad DAT drives where I have run the cleaning tape through 6 or 7 times in a row and all of a sudden they started working again....
A note one the comment about deactivating the drive, swapping in a new one, and then reactivating it and doing the EXE-UPDAT - I have done hail mary plays that way twice, but since you are talking about 9006.3, I know there was one model hard drive they were using back then - I think it was a quantun fireball, but don't quote me on it, that will not spin up when you put the drive carrier back in the system - it would only power up from a cold start. If you have a system where the hard drive is toast try to use a flashlight to see what drive brand it is before you do that - just so you don't get surprised.
A note one the comment about deactivating the drive, swapping in a new one, and then reactivating it and doing the EXE-UPDAT - I have done hail mary plays that way twice, but since you are talking about 9006.3, I know there was one model hard drive they were using back then - I think it was a quantun fireball, but don't quote me on it, that will not spin up when you put the drive carrier back in the system - it would only power up from a cold start. If you have a system where the hard drive is toast try to use a flashlight to see what drive brand it is before you do that - just so you don't get surprised.
- Thread starter
- #5
Re: the hard drive that wouldn't power up upon insertion, good thing to keep in mind. If possible I'd test it with the lab PBX before bringing it to the site. That reminds me although not completely related, there was either a recovery or upgrade process, maybe it was the 9006.4 or 9006.5 - where you'd need a different CPU (DM3L/DM4L?) to proceed to the next step of the process. Kind of like some of the DAT drives I have now, one will load the ISYAPS, but not an RMX backup. Another may be vice-versa.
I have done system recoveries on 9004 for sure and I don't remember that part. I had 60 30's, several with 2 cabinets, and I replaced one of them with an 80 I bought from another company that was upgrading because I wanted their ACD licenses, so I took the 30 that replaced and gutted it except for the Processor, drive mount and the LTUC and used that to do my system recoveries on. Then I took the drive to the site with the issue, replaced the bad drive and did the EXE-UPDAT several times. I was told by 2 techs there was absolutely no way that would work, but the DAT had been bad for 6 months and I hadn't replaced it because my company wouldn't pay for the drive - then the HD went down and I had no reliable backup so I prayed every day if there was a power outage that the UPS would last longer than that! After I did the first recovery that way (same install tapes the system in question was running on) I later found out from a TAC guy that what I did IS possible, but he told me about the one HD model that was out in the field that definitely would not start back up without a complete power down. Fortunately I didn't have one of those. The second one I did I got cocky and uses a way newer version PP of 9006.4 because I knew it would work with LC-Win after that. That drive accepted the UPDAT as well and worked. I rode on those versions until we finally replaced everything with 4K V7 last year, and when we went to do the snapshots on one of my 9006.5 systems I found out the unix boot file was corrupt and we couldn't login to the system to get the data. I ended up doing a REGEN on the RMX port because the tech didn't want to touch it. I also did a recovery on a 9006.6 one time that a backup tech screwed up because he shut down the system and didn't know it had ACD on it. I don't remember any processor board issues with that one either, but I did have a 3 day old backup of that one.
I'm headed to Irving mid September to continue on with my tech training track for the 4000 series - that stuff is a whole different bird in some cases, yet similar in others!
I'm headed to Irving mid September to continue on with my tech training track for the 4000 series - that stuff is a whole different bird in some cases, yet similar in others!
Iamnothere
Technical User
Congrats donb01. Which course?
Keyset6: Is your hard disk bad?
Good Luck!
Keyset6: Is your hard disk bad?
Good Luck!
Already did the prerequisite online assistant course. Now need the 4K BAS1CS course and the Troubleshooting course. Then when they un waitlist the 4K Advanced course I will need to follow up with that and then I should be at a decent tech level I hope.
- Thread starter
- #9
donb01 - so you've been there/done that, good you had good hard drive! If I were to do the process using EXE-UPDAT, I'd bring another drive, pre-built if possible - in case the process didn't work. Good idea hanging onto essential components from the retired systems.
Iamnothere - currently no bad hard disks, I just wanted to have the REGEN files on hand.
Iamnothere - currently no bad hard disks, I just wanted to have the REGEN files on hand.
- Status
Similar threads
- Locked
- Question
- Locked
- Question