Performing Migration

12.The Edit Profile commands, Edit Site Profile (edsp), Edit Device Profile (eddp), Edit Facility Profile (edfp), and the Identity (id) command provide mechanisms for changing or correcting the migrated data. When migration completes successfully, the messages sent to the console can be reviewed to take note of any warning messages as follows:

cd /usr/tmp pg initdb.log pg restorelog

Upon completion of the migration script, perform the following:

Shutdown the NMS and restart it.

Turn polling on again with the edams command.

If your NMS has ANALYSIS systems connected and you wish to change or add systems, perform the configuration steps now as specified in the Configuration section.

Backup the 4.2 database onto new cartridge tapes.

Release 4.0/4.1 Database Migration

When a customer migrates from a Release 4.0 or Release 4.1 6800 Series NMS to a Release 4.2 6800 Series NMS, all device profiles, site profiles, vendor profiles, historical alerts, trouble tickets, user profiles and user groups, filter values, and channel group tables are transferred.

Databases Migrated

The following databases will be migrated:

Device Profiles

Vendor Profiles

Site Profiles

Facility Profiles

User Profiles

System Configuration Data

External System Configuration Data

Workstation Data

Filter Values

Alert Monitoring States

Alert Colors and Alert Group Attributes

ATR Phone Directories

Historic Alerts

Network Summary Categories and Labels

Trouble Tickets

Routines

6800-A2-GN22-30

January 1997

7-33

Page 304
Image 304
Paradyne 6800 manual Release 4.0/4.1 Database Migration, Cd /usr/tmp pg initdb.log pg restorelog