Cisco ONS 15454 Troubleshooting Manual page 484

3.3.12 DBRESTORE-FAIL
This condition can occur when the server is not able to handle the backup operation due to network or
server issues. Repeat the same operation again and check to see if it is successful. If the backup fails, it
could be due to a network issue or software program failure. Contact TAC for assistance; see the
"Obtaining Documentation and Submitting a Service Request" section on page xliv
3.3.12 DBRESTORE-FAIL
The Database Restore Failed (DBRESTORE-FAIL) condition occurs when the system fails to restore the
backed up database when the restore command is initiated.
This condition can be due to server issues, network issues, or human error (pointing to a file that does
not exist, wrong file name, etc.). Retrying the database restore with the correct file will usually succeed.
If the network issue persists, you must contact network lab support. If the condition is caused by a
network element (NE) failure, contact TAC for assistance. See the
Submitting a Service Request" section on page xliv
3.3.13 EFM-ERR-FRM
The EFM Link Monitoring - Errored Frame Event condition occurs when the number of error frames
detected on the remote NE is equal to or greater than the specified threshold for a specified period, and
the remote NE notifies local NE of the same. A period is specified by time interval.
This transient condition does not result in a standing condition.
3.3.14 EFM-FRM-PER
The EFM Link Monitoring - Errored Frame Period Event condition occurs when the number of errored
frames detected on the remote NE is equal to or greater than the specified threshold for a specified
period, and the remote NE notifies local NE of the same. A period is specified by the number of received
frames.
This transient condition does not result in a standing condition.
3.3.15 EFM-FRM-SEC
The EFM Link Monitoring - Errored Frame Seconds Summary condition occurs when the number of
errored frame seconds (a 1-second interval wherein at least one frame error was detected) on the remote
NE crosses the configured threshold. The remote NE notifies local NE of the condition.
3.3.16 EFM-RLBK-FAIL
The EFM - Remote Loopback Request Failed condition occurs when a request fails. When the user
triggers a remote loopback request on the local NE, the request is forwarded to the remote NE. If the
remote NE does not respond to the request and the local NE times out, this condition notifies the user on
local NE about the failure.
This transient condition does not result in a standing condition.
Cisco ONS 15454 Troubleshooting Guide, R8.5
3-6
Chapter 3
"Obtaining Documentation and
as needed.
Transient Conditions
as needed.
November 2009