Alarm
Code | Error | Description/Possible Action |
|---|---|---|
5000 5061, Invalid specification between NP/BP | An unexpected internal error has occurred in NP handling of a network change. The BP provided data that the NP fails to handle. The specified network element is desynchronized, please launch the configuration script called npresynch and check that there’s no new alarm and the npresynch succeeds. Please report this error to the Customer support. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem. | |
5000 | «Received invalid Section specification from BP, named '%s'. (ExceptionMsg: A end TP already in use, Z end TP already in use, NE '%s' not found in database, connectivity problems after scanning the Trail)» | |
5020 | «Received invalid TTP specification from BP, in NE named '%s'» | |
5021 | «Received invalid MC specification from BP, in NE named '%s'» | |
5022 | «Received invalid Internal Section specification from BP, in NE named '%s'» | |
5040 | «Received invalid TTP specification from BP, in NE named '%s'» | |
5041 | «Received invalid MC specification from BP, in NE named '%s'» | |
5042 | «Received invalid Internal Section specification from BP, in NE named '%s'» | |
5060 | «Received invalid TTP specification from BP, in NE named '%s'» | |
5061 | «Received invalid MC specification from BP, in NE named '%s'» | |
5063 | «Process notification failed, received the internal error '%s'» | An unexpected internal error occurred during the processing of a network change : Please report this error to the Customer support. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem. Launch the configuration script called npresynch. |
5064 | «Process notification failed, received the Database error '%s'» | An database error occurred while managing a network change. Please report this error to the Customer support. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem. |
5065 | «Process notification failed, received the CORBA error : '%s'» | An unexpected communication error occurred between FOXMAN-UN NP and FOXMAN-UN BP. Launch npresynch, if the trouble still exists then contact the Customer support. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem. |
5066 | «Process notification failed, unknown error» | This is a critical Alarm, unidentified error occurred. Please report this error to the Customer support. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem. |
5081 5083, unexpected communication failure with BP | The FOXMAN-UN NP failed to get a Network Element from BP. One of this error has desynchronized the specified network element. Please synchronize using npresynch. | |
5081 | «Create Element Manager failed on NE '%s'. BP exception: '%s'» | |
5082 | «Create Element Manager failed on NE '%s'. CORBA exception: '%s'» | |
5083 | «Create Element Manager failed on NE '%s'. Unhandled exception» | |
5087 5089, unexpected communication failure with BP | Please report this error to the Customer support. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem. | |
5087 | «Release Element Manager failed on NE '%s'. BP exception: '%s'» | |
5088 | «Release Element Manager failed on NE '%s'. CORBA exception: '%s'» | |
5089 | «Release Element Manager failed on NE '%s'. Unhandled exception» | |
5090 | «Failed to retrieve Network Query Manager, BP exception, '%s'» | |
5091 | «Failed to retrieve Network Query Manager, unhandled error» | |