Nortel Networks VSN04 manual Common Tops VSN log messages

Page 38

32Common TOPS VSN log messages (0202)

Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If this action doesn't correct the problem, reboot the SRU. If the PRU is still faulty, then reboot the whole system. Document the problem, record all action taken, and then contact NT.

0003/0098 Message: [PRU_name] received an IO error (Bad_File) on path [file/directory_path name]. The error was the result of file identifier not recognized by the server.

Description: The PRU encountered an error during an IO operation on the file or directory. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.

Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If this action doesn't correct the problem, reboot the SRU. If the PRU is still faulty, then reboot the whole system. Document the problem, record all action taken, and then contact NT.

0003/0099 Message: [PRU_name] received an IO error (Consistency_Check) on path [file/directory_path name]. The error was the result of data on the disk is not what the file system thinks is on the disk.

Description: The PRU encountered an error during an IO operation on the file or directory. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.

Action: Reformat the disk. Document the problem, record all action taken, and then contact NT.

0003/009A Message: [PRU_name] received an IO error (Bad_Transaction_ID) on path [file/directory_path name]. The error was the result of an invalid file set transaction identifier.

Description: The PRU encountered an error during an IO operation on the file or directory. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.

Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If this action doesn't correct the problem, reboot the SRU. If the PRU is still faulty, then reboot the whole system. Document the problem, record all action taken, and then contact NT.

0003/009B Message: [PRU_name] received an IO error (Bad_Volume_ID) on path [file/directory_path name]. The error was the result of the specified volume identifier for the fid (file identifier) is for this server.

Description: The PRU encountered an error during an IO operation on the file or directory. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.

TOPS VSN Log and alarm messages

Image 38
Contents Voice service node TopsPage Tops VSN log and alarm messages Page Contents Page Sample Tops VSN log/alarm message IntroductionCritical GErrorLError MajorInformation Number TypeChange history Tops VSN log messages DNC Logs Tops VSN Log Messages Common Tops VSN log messages Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Page Common Tops VSN log messages Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops VSN log messages Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops log messages DNC Logs Common Tops VSN log messages Common Tops VSN log messages Page Common Tops VSN log messages 020A Common Tops VSN log messages 020A Common Tops log messages 020A DNC Logs Common Tops VSN log messages 020A Common Tops log messages 020A DNC Logs Common Tops VSN log messages 020A Common Tops VSN log messages Page Voice interface resource manager log messages Page Alarm Subsystem User 3 InputAlarm Subsystem Acpe resource manager log messages Acpe Resource Manager Log Messages Acpe Resource Manager Log Messages 9440 Acpe Resource Manager Log Messages Control link log messages Control Link Log Messages Application call processing engine log messages Application Call Processing Engine Log Messages Application Call Processing Engine Log Messages 9442 Application Call Processing Engine Log Messages Application Call Processing Engine Log Messages 9442 Message 14. T1 resource manager log messages 66 T1 Resource Manager Log Messages T1 Resource Manager Log Messages 9443 ActionPage Locality database log messages 944E Action NoneLocality Database Log Messages 944E Second string gives additional information on the problem Page Acpe Maintenance Position log messages Page Prompt manager log messages Prompt Manager Log Messages DescriptionSuppressed and Thresholded Logs Suppressed LogsCould not Send Notification 78 3. Suppressed and Thresholded LogsCleaning UP of Alarms Suppressed and Thresholded Logs80 3. Suppressed and Thresholded Logs Vsnalarm DMS noticesPage Abbreviations List of abbreviations used in this Publication followsTops