HiPath 4000 V2 GENDB - What am I missing? 1

[TKfan]

In order to mass-delete a lot of stations configured on my lab-system I plan to do a regen, edit out all the stuff I want to remove and finally gendb it.
To test the procedure, I did the following:
[ul]
[li]Deleted the VEGAS file and performed a complete REGEN[/li]
[li]Deleted the SWU database: ae-dbc:resswudb=j; and reloaded[/li]
[li]Reload stopped at an error on the 7-segment led: [1] (I assume this means no SWU database found)[/li]
[li]Deleted the VEGAS file again and ran sta-gendb:"as:/Lxxx/yyy/RE/ALL","TKfan",SWU;[/li]
[li]And finally did another reload[/li]
[/ul]
The system came up with the same error display [1] as before.
What else do I have to do to activate the newly generated database? The manuals is a bit brief on that...

[1] Error message:

| |
 _|.

 

[Iamnothere]

I dislike the GENDB process due to this very situation - you do not have "control"!!!!! Try using the ComWin "Macro" process, or use Copy/Paste and utilize the "execute clipboard - amo by amo" technique. Both of these processes allow YOU to be in control, because YOU are controlling the processing of the 4K database MANUALLY. This process may take some time if the database is HUGE, but the process is actually very quick if you can establish a "Direct" session via the Atlantic LAN using ComWin/Expert Access "Connect". Typically it takes about 5 minutes to process 2000 AMO commands.

To use either of these processes, you will need to clean up the REGEN file by removing the "M2 1 " type characters on each line, and the gibberish at the top of the file, so that you have nothing but AMO commands, starting with the ADD-CODEW command. The best tool to use for this cleanup is "Wordpad", using the FIND/REPLACE process to remove "M1 1 " and "M2 1 ".

To use the ComWin "Macro" tool (you must have an active session), click "Macro" on the top action bar, then "Start", then "Open". Locate your edited REGEN file. You may need to change the "file type" from "commandfiles" to "All files". When your REGEN file loads into the "Macro" window, look it over to ensure that everything looks OK, then click "Start" then "Start". AMO by AMO will be processed, until the final command.
When completed, you must type "ACT-USSU:LTG,1;" to load this new database. After the system comes UP, be sure to perform two EXE-UPDAT:BP,ALL; commands and two EXE-UPDAT:A1,ALL; commands!!!!!

If there are any errors encountered during the macro procedure, you will need to quickly STOP sending AMOs by clicking the red STOP sign, then go to ComWin and resolve the issue, then return to the Macro window, locate the next command, and continue. Using "Macro" for the first time can be tricky. Typically if you click the STOP sign, the macro window may disappear, and you cannot locate it. No worries - from the ComWin window, click "Window", then select "Macro Window", and voila - the Macro window re-appears. Also, in the Macro window, there is a very useful tool called "Go To Line..." located under "Start". So if you encounter a problem during the processing of your REGEN file, and the script blasts through several hundred commands before you notice, FIRST repair the problem in ComWin, then locate the next command in your REGEN/command file (use your mouse and click on the command that should be processed next -you will see the "line" number in the lower LEFT corner of the window), then use the "Go To Line" tool to reset the Macro to begin from the appropriate line number.

Or if you do not like using this Macro tool, try using simple "copy/paste". Again, the command file must be cleaned up, and must start with the ADD-CODEW command (unless this is HiPath 4000 V6!!!!).
Use the Windows "copy" process to copy ALL of the AMO commands. Then open an active ComWin session. In the "buffer" area (where you type), RIGHT-CLICK, and select "EXECUTE CLIPBOARD" -> "AMO by AMO".

Now watch as the commands are processed. Again, you will need to repair any problems as they are encountered, then restart the copy/paste procedure from where the process was last successful. As with the Macro process, you MUST type "ACT-USSU:LTG,1;" to load this new database. After the system comes UP, be sure to perform two EXE-UPDAT:BP,ALL; commands and two EXE-UPDAT:A1,ALL; commands!!!!!

Good luck!!!!!!!!!!!!!!!

 

[sbcsu]

Sometimes it can happen that you lose the data that you have put in if you ACT-USSU:LTG;
so do update BEFORE you ACT-DSSU:LTG; as well
(EXE-UPDAT:BP,ALL;
EXE-UPDAT:A1,ALL;
ACT-USSU:LTG;
WAIT UNTIL LOADED
THEN
EXE-UPDAT:BP,ALL;
EXE-UPDAT:A1,ALL

 

[TKfan]

Thanks, Iamnothere!
"ACT-USSU:LTG,1;" was what I was missing. After typing that command the system completed its startup.
I had been looking for a dedicated command to load the database. The documentation is really scarce on this subject.
At least with an empty database the Hipath 4000 starts up to the point where you can enter the necessary commands manually if you have to. On a Bosch/Tenovis/avaya Integral 33/55/Enterprise for example you have to create the customer database files (at least for the basic system definition including shelfs and boards) offline with a special tool (CAT) before starting the system.

Out of curiosity: What is the t

http://www.tek-tips.com/viewthread.cfm?qid=1698874echnical

reason for executing each EXE-UPDAT twice?

Your Macro-process looks like the way to go for me. Reading the online help for macros the 'WHEN' command appears promising for error handling.
I have found a really great tool in the HP4K Expert Access package: the MML Translator. Not only can it remove the "M2 1 " from the AMO file automatically, it can at the same time translate from position oriented to keyword oriented notation, which is much more readable for me!

Not that I think I need to do this here, but how would I reset the ADS database (there is no AE-DBC:RESADSDB=J)?

 

[TKfan]

Weird display error. The question should read (without the link): What is the technical reason for executing each EXE-UPDAT twice?

 

[Iamnothere]

Why do the EXE-UPDAT twice? There are two copies of the Switching Unit database (and A1 database) on the system hard drive - one is flagged as "active", the other as "standby". Typically only the ACTIVE copy is used. When you perform the first EXE-UPDAT, the database is written to the standby copy of the hard drive's database. When done, the standby copy is changed to be the ACTIVE copy. The previous ACTIVE copy is now the Standby, but it continues to reflect the OLD copy of the database. So if you perform the EXE-UPDAT a second time, again the database is written to the Standby database. When completed, the Standby becomes Active, and now BOTH copies of the database are equal. Only once in my career have I seen the system load the OLD database, when someone neglected to perform EXE-UPDAT twice the previous afternoon after making many moves, adds, and changes. But it DID HAPPEN, freaked us all out, and ever since I have ALWAYS performed the EXE-UPDAT commands twice!!

Yes, you can read the HELP files and learn how to utilize logic within the Macro. One command I use is: IF (" NOT COMPLETED ") THEN DIALOG
So if I am running a Macro, and an AMO returns a message that includes "NOT COMPLETED", then the Macro stops and allows me to correct the problem. On very long REGEN files, this saves much time, as I do not have to continuously STOP the macro, locate the last successful command, GO TO that line, etc. You can substitute any alpha-numeric characters inside the quotes, but the command MUST be in CAPs!!!!

Expert Access/ComWin is a wonderful tool. Also handy is the MML Editor, in the event that you forget an AMO name or parameter.

 

[Iamnothere]

Just noticed that I did not address the ADP database comment. You are correct - the A1 database is NOT touched if/when you CHA-DBC:RESSWUDB=Yes;
To delete the A1 database, there is a process to follow, which involves manipulating two files within the RMX hard drive partition F. I have only done this
once, so I would have to refer back to some very old notes to recall the specifics. Perhaps someone else may know it immediately. This task may become more
necessary as HiPath 4000 V6 is introduced around the world. In V6, the System Number for the A1 can be entered using ADD-ANUM one time ONLY. Therefore if entered incorrectly,
the licensing process will not work properly, and the entire A1 database must be deleted in order to try again with the ADD-ANUM command.

Also, SBCSU's comment above is pertinent. If someone has implemented a new database using GENDB or manual entry, if the system is reloaded before a EXE-UPDAT is performed,
then the database is lost, and the process to install the database must be repeated. So performing a quick EXE-UPDAT prior to the ACT-USSU:LTG,1; would prevent that from happening.
The key is to remember to perform EXE-UPDAT (twice) AFTER performing the ACT-USSU:LTG,1; command, because if you DO FORGET THIS, then on the next system reload, the SWU will indicate a NULL database (the "code" that you showed us above, a.k.a "hockey stick"). Many techs would then think that the database is LOST, when actually it IS PRESENT, but the database will not LOAD without the ACT-USSU:LTG,1; command!!!
To resolve this situation, you would manually type ACT-USSU:LTG,1; followed by two EXE-UPDAT:BP,ALL; and two EXE-UPDAT:A1,ALL; From that point forward, the database should LOAD properly.

Cheers!