Specifications

Table Of Contents
Model Conversion
Conversion Programs
Software Release Notes Page 135
../SS-Tools/DBconv <name of vnm host> rc.<abbreviated model type name>
(Example:
../SS-Tools/DBconv monarch ../SS-Tools/rc.cisco)
7 The program will proceed through a short initial phase and a longer
second phase, noting on-screen which phase is in effect. Models that
have not been contacted will not be converted and error messages will
be displayed. Examples of these error messages are shown in
Example 3.
Example 3:
Error in reading model type names
Possible Causes:
1. Specified Model Types don’t exist in the database.
2. SpectroSERVER is not responding.
3. SpectroSERVER doesn’t have a model for your user-id.
8 Repeat this procedure for each model type that needs to be converted.
9 After verifying the success of the conversion, save your SPECTRUM
database
Caution:
Caution:
Archive or remove any database save files left from SPECTRUM
5.0Rev 1. They can no longer be used to recover a database
under the new release. Attempting to restore a SPECTRUM 6.x
database with a 5.x database save file will render the existing 6.x
database unusable.
Note:
Note:
After you have installed SPECTRUM 6.0 and run the DBconv
program for all the old model types, the system “expects” new
model types only. If you then create a model using one of the old
model types (e.g., Rtr_cisco_IGS instead of Rtr_CiscoIGS), it will
generate an Event00010644 model mismatch alarm.