Download COMSPHERE 6800 SERIES NETWORK MANAGEMENT SYSTEM

File Export to ACCUMASTER Integrator
4. Select all the equipment from the ‘‘unassigned” equipment list that belongs in the new
location and move it to the new location. Each piece of equipment that was formerly
assigned to the old location must be assigned to a new (existing) location.
5. Delete the old location after each piece of equipment that was formerly at the old location
has been reassigned to another location.
NMS Mail Message for a Successful File Transfer
The NMS admin login will receive a mail message from uucp when an export file is successfully
sent. The format of the mail message is:
REQUEST: <machine name>!/usr/nms/RNMS/file_export/<filename>--><AMI
name> !”iadm/(admin)
(SYSTEM: <AMI name>) copy succeeded
The admin login may also receive a mail message if a transfer failed due to a problem (e.g., nuucp
login failure, no connection) that the uucp utility can detect.
Therefore if a mail message is not received you should:
1. Verify that the file was NOT received by the AMI.
2. Try to resend the file. If the file was an update file, do not re-execute the Create Export
File command or make any further changes in device, facility or site profiles until the file is
sent and received by the AMI. Otherwise, the changes that were logged in the ‘‘lost” update
file will be overwritten and cannot be recovered unless you create and send a new base file.
Troubleshooting and Miscellaneous Notes
If the file export connection is down when the Send Export File (snef) command is executed,
export files will be queued at the NMS by the uucp function. When the connection is
re-established, all export files which have been queued will be sent sequentially. This behavior
does not cause problems when sending base files; however, if multiple update files are queued, the
latest file will overwrite any previous files when the files are finally sent to the AMI.
Consequently, only the changes contained in the last update file written will be retained; all others
will be lost. Therefore, it is important to verify that each file sent by the NMS is received by the
AMI.
If you are using device name mapping, you cannot create a device profile for a device with a
link-level address longer than 21 characters.
6800-A2-GE26-20
January 1997
H-7