Paradyne 6800 Release 3.0/3.1 Database Migration, Cd /usr/tmp Pg migdbload.log pg migrestore.log

Models: 6800

1 351
Download 351 pages 51.03 Kb
Page 296
Image 296

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 migdbload.log pg migrestore.log

Release 3.0/3.1 Database Migration

When a customer migrates from a Release 3.0 or Release 3.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

Alert Driven Routines

Port Configuration

Scheduled items

6800-A2-GN22-30

January 1997

7-25

Page 296
Image 296
Paradyne 6800 manual Release 3.0/3.1 Database Migration, Cd /usr/tmp Pg migdbload.log pg migrestore.log