Paradyne 6800 - Manual (Page 285)

COMSPHERE 6800 Series Network Management System
7-14 January 1997 6800-A2-GN22-30
3. Execute the Display Device Profile (dsdp) command to verify profiles for three devices.
Verify the accuracy of the information.
4. Execute the Display Site Profile (dssp) command to examine profiles for three sites.
Verify the accuracy of the information.
5. Execute the Display Facility Profile (dsfp) command to examine facility profiles
associated with three devices.
6. If the ACCULINK Network Manager (ANM) is installed, execute the List Facility
Profile (lsfp) command, selecting T1 for the facility type and m2/* for Device(s).
Compare the screen results with a hard copy output from the List Node Connectivity
(lsnc) command on the source system.
7. If ANM is installed, execute the Hardware Module Summary (hms) command on three
ACCULINK devices.
8. Execute the Device Health Status (dhs) command on available device types, e.g., three
DATAPHONE II devices, and three COMSPHERE devices.
9. Run Alert History reports to list Historical Alerts using the Detailed Alert Report (dar)
and Alert Report Summary (ars) commands.
10. When the migration is complete, execute the Edit Alert Monitoring State (edams)
command to turn on polling. NMS will then automatically acquire the current feature
packages/versions for the multiplexer network, if ANM is installed.
Profile Data Changes and Corrections
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. The following is a list of changes to consider:
1. 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 migrate.err
pg migrate.out
The above files are eventually deleted by the NMS.
The warning messages indicate any significant deletions or modifications of profiles or
fields. You should determine if corrective action is necessary.
2. If 3600 Series DSUs are managed by the NMS, the Release 4.2 network commands for
these devices will fail if the Model Number field is not populated. This can be done
automatically via an Identity (id) command, in which the update device profile option is
selected.
An Identity (id) command can be executed globally (e.g., to update all devices on one or
more control channels). However, a global command affecting a large number of devices
may take hours to complete. If only a few of the affected devices are 3600 Series DSUs,
manually updating these profiles via the Edit Device Profile (eddp) command may be
quicker.