Filter
Top Products
COMSPHERE 6800 Series Network Management System
7-4 January 1997 6800-A2-GN22-30
The following databases will not be migrated:
• Port configuration database
• User profile databases
• Routines and scheduler databases
• Trouble tickets
The databases that are not migrated must be manually entered into the Release 4.2. For this
purpose, print a hard copy of user profiles, routines, schedules, and trouble tickets that need to be
migrated.
Cleaning Up the Database
A number of device profile fields in the source NMS database should be checked before
migration. If the data in these fields is inaccurate, incomplete, or in a format not suitable for
migration, the impact may be multiple omissions or inaccuracies in the Release 4.2 database.
An additional concern is that many fields are converted to a single case (either lower- or
uppercase). Field values that differ only in the case may create unintentional redundancies. As a
result, a field or an entire record may be discarded.
Such impacts can be corrected following migration by editing or creating Release 4.2 profiles.
However, eliminating potential problems beforehand will minimize effort and contribute to a
smoother transition to Release 4.2.
The following fields require specific attention:
Device Address
• This field is required in Release 4.2 for all migrated device profiles.
• All letters are converted to lowercase.
• All other characters except numbers, periods, hyphens, and slashes, are deleted.
• Only one profile will be accepted for a given address. Later occurrences of the
same address will cause the profile to be discarded (although a warning
message will be displayed).
Device Name
• This field is required in Release 4.2 and must be unique.
• All letters are converted to lowercase.
• All other characters except numbers, periods, and hyphens, are converted to
hyphens, and any successive hyphens are converted to a single hyphen.
• If no device name exists, a name containing the device type and a unique
number is generated automatically.
• If the same device name appears in more than one record, the first record is
migrated without changes, and a unique device name is generated for
successive records of the same name (although a warning message is
displayed).