How do I remove the SSC flash database

[nortelblue]

My issue is that I need to have a completley fresh install and it always seems to grab the dbase from the SSC flash. I have even f-bug'd the daughterboard and it still has all the patches coming down from I assume the z: drive, any help would be great. I would like to do the restore by copying database.rec and config.rec they have no nodes and the original issue is that they have no disk recs

It is an opt11 cab, SSC, runnning 5.5

 

[Firebird Scrambler]

When you do the installation from the PCMCIA card in slot A, do you select the default configurtion database?.

http://www.ghtrout.com/files/Restore_Guide_Opt11c.zip

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[nortelblue]

I have, this doesn't seem to completley remove everything, patches,etc... I am going to try to delete some of it from the z:/ drive using pdt. I had this problem fixed in the lab, but it required everything to be clean and fresh. The SSC onsite is not, the daughterboard was formatted. I have had Avaya in there but they can not tell me where the space is used. Something in the software is consuming RECS in the database. For instance I deleted 100 SCL and got 17 recs, they were gone in less than an hour.

 

[j68maro]

what option did you choose in fbug?

 

[NortelGuy1979]

I've never seen an Opt11C hold its programming when you do a complete install and choose no database - it erases the Z and C for you. You shouldn't even have to erase the C drive in FBUG ...

Matthew - Technical Support Engineer Sr.

http://www.linkedin.com/in/matty79

 

[nortelblue]

I can say without a doubt that it retains all the patches and probably some other files in the z: drive

I have done a basic install and a default north american install

This is a cs1000 5.5

It actually recovered its patches from z:/patch (not sure on the exact directory. But I also choose not to load a deplist and it came up with all 197 patches.

I agree, this is strange, don't know what to say!

i only used f-bug to delete the daughterboard, it then recovered the patches from z: when the software was reloaded and it came back online. It did not restore the the dbase info though.

i saw in PDT that the files were from the same day, so the EDD that was done wrote them before the two attempts at the install.

 

[NortelGuy1979]

Delete the Z drive in FBUG. It's the 5th option I think? 5 is the Z drive, 6 & 7 are the C drive.

5 = ALT BOOT (should be the main cabinet SSC itself)
6 = flash drive on DB
7 = flash prog store on DB

If you do all 3, you're looking at a wiped ssc & daughterboard.

Matthew - Technical Support Engineer Sr.

http://www.linkedin.com/in/matty79

 

[kstaff22]

I'm a little confused---do you want to totally blow everything away?---if so in fbug choose options 5 for z drive--then 6 and 7 for the DB.

 

[NortelGuy1979]

'zactly kstaff22 - he wants to blow it away; I forgot until 5 minutes ago that in FBUG opt #5 will erase Z. Was trying to rebuild a 1.07 CP and think at the same time... and it wasn't happening hehe.

Matthew - Technical Support Engineer Sr.

http://www.linkedin.com/in/matty79

 

[nortelblue]

Thanks guys, did the trick for sure. One weird thing with the "restore"

I didn't actually use the archive, I simply copied Database.rec and Config.rec. The whole database came back except the elans and host ip's. i have done this before and it worked, i know it doesn't if they have node data but this is straight TDM.

Again, the reason this is being done this way is because the database had no RECS available and was complaining about a low disk. In the lab this proceedure freed almost 256 recs

 

[Firebird Scrambler]

I think you may have needed to copy across the zone.db file.
It's worthwile reducing some of the parameters in LD 86 under ESN, along with removing any old Model sets and the MSCL size in LD 17.
There was a patch at 4.x that stopped the patches from being dumped to the Z Drive.

Option 11C / CS1000 Small System
System with large database goes into reboot loop if rebooted.

mplr20913 rls 4.00T and 4.50W SSC only

System with large database goes into reboot loop if rebooted

SETUP FOR THE PROBLEM:
SSC system with a large database.

Actions:
Reboot the system after a ISM or Feature upgrade (or because of power failure).

Expected Response:
The system to reboot, and to work OK afterwords.

Actual Response:
The system goes into a reboot loop, and does not come up again:

Backing up c:/u/patch/p18811_1.ssc

TEMU115 zdrv: Drive full, file c:/u/patch/p20144_1.ssc not backed up
Backing up c:/u/patch/p19096_1.ssc
Backing up reten.bkp

Internal backup complete
All files are backed up!
DATADUMP COMPLETE

Sysload the system!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

System Controller
Pre-Boot: 03 dev2.37
Flash Boot: NTDK34FA_r11 dev2.54
Reset Reason: C0, 0 - Reset due to Power Up
SRAM: 128 kBytes
DRAM: 32 MBytes, speed=60 ns
Security ID: 10000428 type: NT_STD
System ID: 10000428
Backup Flash: 1572 kBytes
Program Store: 32 MBytes
Flash Drive: 16 MBytes
Expansion board #1 not installed.
Expansion board #2 not installed.
Ethernet MAC address: 00:00:75:4A:6E:5B
PCMCIA card installed in drive A.
PCMCIA card not installed in drive B.

*** To invoke install setup program from PCMCIA enter CONTROL-I ***

Executing power up self tests
Power up self test passed
DISKOS to be run.
Verifying Diskos.


*** OS RESTART ***


Succession Enterprise System Software
Release : x210300
Created : Friday October 3 16:27:54 EDT 2003
Loaded : 29/6/05 13:28:57

Copyright(C) 1972-2003 Nortel Networks. All Rights Reserved.
VxWorks 5.2
Copyright(C) 1984-1997 Wind River Systems, Inc. All Rights Reserved.
Use of the above software subject to terms of a license agreement.
U.S. Government users subject to "Restricted Rights" under FAR & DFAR.

Exception: Vnum=2, PC=0x10168a04, Addr=0x200000, SSW=0x0505, Task="tStartup"(0x207373b8)

BUG7429 OS 0: ERROR "EXC in tExc". Restarting with code: 49

Warm Start begun - reason 49
====================================================================================

mplr21970 is included in the Core deplist for X21 4.00T and 4.50W to prevent the reboot loop: it stops the backup once the limit of the Z drive is reached, thus preventing the reboot issue from occurring.
MPLR21970 will however output TEMU115 message for each patch not backed up due to reaching Z drive capacity.

mplr20913 (for rls 4.00T and 4.50W SSC) prevents the reboot loop by preventing the backup of any patches to the Z drive. The patches will, however, still be backed to the C drive (software daughterboard).
This new pep will also be included in the core deplist in future.

If the customer wishes MPLR20913 can be POOS and POUTed, then MPLR21970, which will remain a Public
patch and on the Dependency List, will take over and begin the Patch backups.

=================================================================================
Patch installation


If you have "TEMU115 zdrv: Drive full, " message during backup, just remove all patches from z: drive and install this patch.

If you encountered problem indicated by a BUG7429, invoke the following z: drive recovery process:-

1- Power off the system
2- Power on the system
3- Press key "ctrl B"
4- Access to prompt FBUG>
5- At the prompt FBUG> type the command ct
6- SYSTEM TEST MENU
-------------------------------
Enter 'p' for Production test
or 'd' for Daughter board test
or 't' for Troubleshoot
or 's' for System power up test
Return key to exit

Enter selection: p "SELECT OPTION p"
LED ->PASS
Clock ->PASS
DRAM 32 Mb ->
:
:
etc
:
:

Testing FLASH drive D/B
-Checking for previous data
-Flash d/b is not blank
7- Enter y to erase and test: n !!!! <--- Enter no!!!!!!!
FAIL
8- Power off then on the system
9- The system will be loaded but no z drive in devs
10- pdt> foxDriveBackupMount
11- pdt> reboot -1
12- pdt> zdrvEraseAll
13- pdt> reboot -1
14- Install mplr20913 on the ssc card
15- Do an EDD in ld 43



All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[nortelblue]

Thanks for all the info.

The disk is not actually out of space, the database keeps filling up.

for instance there is ton off bytes left on both disks, but if you go into ld 10 you will see no disk recs (disk reqs:0) followed by "low disk". Its like the db is filling up, not the disk. It is really strange.