Hitachi Energy
System
 
Code
Error
Description/Possible Action
4000
«Cannot add a Trail in the '%s' path of TE '%s', there is no  hole»
The User Interface has allowed an invalid action : the operator has requested to add a Trail in the route of a Transport Entity which is already routed.
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.
4020
«SNC '%s' is not a possible hop for TE '%s'»
The FOXMAN-UN NP has provided a possible SNC for manual or automatic routing that is rejected when used.
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.
4040
«Cannot add a TE in protecting path of the non protected TE '%s'»
The User Interface has allowed an invalid action.
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.
4041
«Cannot add a TE in '%s' path of TE '%s', there is no hole»
The User Interface has allowed an invalid action.
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.
4060 4071, internal error
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.
4060
«Cannot find Internal Section '%s', A End TTP not found in NE '%s'»
4061
«Cannot find Internal Section '%s', A End TTP not found in NE '%s'. '%s'»
4062
«Cannot create MC '%s' in NE '%s', received incorrect specification from BP. '%s'»
4063
«Cannot create Internal Section in Trail '%s' NE '%s', invalid A or Z End TTP. '%s'»
4064
«Cannot create Internal Section, A End TP '%s' in NE '%s' already used by trail '%s'»
4065
«Cannot create Internal Section, Z End TP '%s' in NE '%s' already used by trail '%s'»
4066
«Cannot modify Unit '%s' in NE '%s', Unit not found in database»
4067
«Cannot modify TTP '%s' in NE '%s', TTP not found in database»
4068
«Cannot modify MC '%s' in NE '%s', MC not found in database»
4069
«Cannot modify InternalSection '%s' in NE '%s', InternalSectionInfo not found in database»
4070
«Cannot destroy Unit '%s' in NE '%s', Unit not found in database»
4071
«Cannot destroy TTP '%s' in NE '%s', TTP not found in database»
4080
«Detected incompatible directionality while autogenerating '%s' '%s'»
This error occurs during the processing of npfotool_termination.csv and npfotool_crossconnect.csv or through the user interface during the autogeneration of new Transport Entities. Directionality mismatch between unidirectional MCs has been detected. The FOXMAN-UN NP prevents the operator from creating an invalid Transport Entity.
4100
«Cannot auto-generate a TE with both null A and Z End NE»
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.
4101
«Cannot auto-generate a Unidirectional TE with null A End NE»
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.
4102
«Cannot auto-generate a P0nc TE with A and Z End TP with incompatible nb of 64k»
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.
4120
«Invalid call to clear channels in protecting path, TE '%s' not protected»
The User Interface has allowed an invalid action.
4130
«Creation of topological Circuits not supported»
This error is due to an invalid call to the server. A topological Transport Entity does not have a path. Only SNCs between two Foreigns can be topological.
4131
«Creation of topological Trails not supported»
See 4130
4132
«Null Z end NE, in a topological SNC both A and Z end points must be specified»
Invalid call to the server. The FOXMAN-UN NP supports the creation of Transport Entities which Z is not specified for Transport Entities that are not topological.
4133
«Invalid end points for a topological TE creation, end points must be located into Foreigns NEs»
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.
4134
«Invalid parameters for TE creation, a TE between two Foreign NEs ( '%s' and '%s' ) must be topological»
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.
4135
«Cannot create a fixed TE»
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.
4150 4155, demotion failed
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.
4150
«Invalid A end point for SNC demotion, A end channel '%s' of TE '%s' different of A end channel '%s' of SNC '%s' and the SNC is at the beginning of the TE»
4151
«Invalid A end point for SNC demotion, channel '%s' of previous LC in TE '%s' different of A end channel '%s' (NE '%s' TP '%s') of the SNC to demote»
4152
«Invalid A end point for SNC demotion, channel '%s' in TE '%s' different of A end channel '%s' (NE '%s' TP '%s') of the SNC to demote»
4153
«Invalid A end point for SNC demotion, failed to find matching A end point (NE '%s' TP '%s') of the SNC to demote in TE '%s'»
4155
«Invalid Z end point for SNC demotion, failed to find matching Z end point (NE '%s' TP '%s') of SNC in TE '%s'»
4156
«Invalid call to SNC demotion, cannot demote only a SNC»
This is a limitation of the FOXMAN-UN NP.
The user requested that a SNC is demoted which will lead to the creation of a SNC having one SNC in the path. No use case has been defined for this action.
4170
«Unexpected Database Error: '%s'»
A database error occurred. The error message as provided by the database is in the %s.
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.
4180 4322, Invalid calls
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.
4180
«Invalid call, path must have a hole to obtain next trails to route. TE '%s' has no hole»
4190
«Invalid call, path must have a hole to obtain next sncs to route. TE '%s' has no hole»
4200
«Cannot get channel list, LC using Trail '%s' in path '%s' of TE '%s' not found»
4220
«Invalid call, path must have a hole to get possible end TTP for server layer Trail. TE '%s' has no hole»
4240
«Invalid call, path must have a hole to be routed. TE '%s' has no hole»
4260
«Invalid call, path must have a hole to get possible ServerLayer Hops. TE '%s' has no hole»
4280
«Invalid in channels for SNC '%s', timeslots of channel %d are not included in A end TP timeslots channel '%s'»
4300
«TPs to be grouped do not belong to the same TTP (reference TTP '%s')»
4320
«Null Z NE specified with a Z TP not null ('%s'). Please specify the NE»
4321
«Incompatible layer rate between A end point ( '%s' rate '%s' ) and Z end point ( '%s' rate '%s' )»
4322
«Invalid rate for a Trail. Please use a rate different of '%s'»
4323
«Invalid directionality, unidirectional Trails are not supported»
The FOXMAN-UN NP does not allow unidirectional Trails. All Trails are bidirectional.
4324 4341, Transport Entity creation failed
The operator has specified TPs that can’t be used for the creation of the user Transport Entity.
4324
«TP '%s' is not a TTP»
4325
«TTP of TP '%s' already bound to Trail '%s'»
4326
«Invalid Z end point, Z end TP '%s' is not a TTP»
4327
«Invalid Z end point, Z end TTP of TP '%s' already bound to Trail '%s'»
4328
«Invalid rate for a Circuit. Please use a rate different of '%s'»
4329
«Invalid TE end point (TP '%s'), a TTP cannot be a Circuit end point»
4330
«Invalid TE end point (NE '%s' TP '%s'), end points of a Circuit need to be CTPs that are not end point of an LC»
4331
«Invalid Z end point (TP '%s'), a TTP cannot be a Circuit end point»
4332
«Invalid TE end point (TP '%s'), end points of a Circuit need to be CTPs that are not end point of an LC»
4333
«Invalid Z end point, Z end TP '%s' is already a end point of a Circuit»
4334
«Invalid A end point, A end TP '%s' is already a end point of a Circuit»
4335
«Invalid A end point, A end TP '%s' has common slots with an existing TE»
4336
«Invalid rate for a SNC. Please use a rate different of '%s'»
4337
«Invalid A end point, A end TP '%s' is already a Circuit end point or in the middle of an existing TE»
4338
«Invalid Z end point, Z end TP '%s' is already a Circuit end point or in the middle of an existing TE»
4339
«Invalid Z end point, Z end TP '%s' has common slots with an existing TE»
4340
«Invalid Z end point, SNCs finishing in a Foreign NE must have a defined TP. Please specify Z end TP»
4341
«Invalid Z end point, not enough unused capacity Z end TP '%s'»
4360 4376, Invalid call for routing
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.
4360
«Deleted TE '%s' cannot be a possible hop»
4361
«No TE can be hop of TE '%s' without hole»
4362
'%s' '%s' is not a possible hop for TE '%s', only SNC/Trails can be candidates for a hop»
4363
«TE '%s' is not a possible hop for TE '%s', only connectable TEs can be candidates for a hop»
4364
«TE '%s' is not a possible hop for TE '%s', left NE of TE ('%s') is different from left NE of hole ('%s')»
4365
«'%s' named ' '%s' ' is not a possible hop for TE '%s', CAS should be ON»
4366
«Trail '%s' is not a possible hop for TE '%s', only connectable TEs can be candidates for a hop»
4367
«Trail '%s' is not a possible hop for TE '%s', left NE/TP of Trail must be different of Z end point of TE»
4368
«SNC '%s' is not a possible hop for TE '%s', bidirectional protected TE cannot begin with a SNC»
4369
«SNC '%s' is not a possible hop for TE '%s', left TTP of possible hop ('%s') different of A end TTP of TE ('%s') and hop must be inserted at the beginning of the path»
4370
«SNC '%s' is not a possible hop for TE '%s', timeslots of left TP channel of hop ('%s') don't include all slots of A end channel of TE ('%s') and hop must be inserted at the beginning of the path»
4371
«SNC '%s' is not a possible hop for TE '%s', left TP of possible hop ('%s') different of A end TP of TE ('%s') and hop must be inserted at the beginning of the path»
4372
«SNC '%s' is not a possible hop for TE '%s', inserting this SNC leads to a connectivity problem»
4373
«SNC '%s' is not a possible hop for TE '%s'. Left TP channel of SNC ('%s') is incompatible with A end channel of hole ('%s'), rate is P0nc and TE EndPoint cannot be grouped»
4374
«SNC '%s' is not a possible hop for TE '%s', timeslots of left TP channel of hop ('%s') don't include all slots of A end channel of hole ('%s')»
4375
«SNC '%s' is not a possible hop for TE '%s', left TP channel of hop ('%s') different of A end channel of hole ('%s')»
4376
«SNC '%s' is not a possible hop for TE '%s', left TTP of possible hop ('%s') different of A end TTP of hole in TE ('%s')»
4390 4405, Protecting a Transport Entity
 
4390
«Cannot protect simple TE '%s'»
This is a limitation of the FOXMAN-UN NP.
Simple Transport Entity are made of one MC. The FOXMAN-UN NP does not allow protecting such Transport Entities.
4391
« Cannot protect already protected TE '%s'. »
4392
« Cannot protect topological TE '%s'. »
4393
« Cannot protect fixed TE '%s'. »
4394
«Cannot protect TE '%s' with identical A and Z end NE '%s'»
4395
«Cannot protect TE '%s' with SNC '%s' as last path element»
4396
«Cannot protect a TE ('%s') with Z Endpoint at a SNC ('%s') Endpoint»
4397
«Cannot protect a bidirectional TE ('%s') with a SNC ('%s') as first path element»
4398
«Cannot protect a TE ('%s') with a fixed MC ('%s') as last path element»
4399
«Cannot protect a bidirectional TE ('%s') with a fixed MC ('%s') as first path element»
4400
«Cannot protect TE '%s', A end TP '%s' does not support protection»
4401
«Cannot protect TE '%s', Z end TP '%s' does not support protection»
4402
«Cannot protect TE '%s', protection mode incompatibility between A and Z end points»
4403
«Cannot protect TE '%s', existing route from A Endpoint prevents path protection»
4404
«Cannot protect TE '%s', existing route from Z Endpoint prevents path protection»
4405
«Cannot protect TE '%s' which is an Unknown»
4440 4453, internal errors during network synchronization
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.
4440
«A NE with name '%s' that is not a Proprietary NE already use the key '%d'»
4441
«A NE with name '%s' that is not a Foreign NE already use the key '%d'»
4442
«Cannot find A end NE of Section '%s' with object key %d and name '%s'. BP error: '%s'»
4443
«Cannot find Z end NE of Section '%s' with object key %d and name '%s'. BP error: '%s'»
4444
«Cannot find A end TTP of Section '%s' with TTP Label '%s'. BP error: '%s'»
4445
«Cannot find Z end TTP of Section '%s' with TTP Label '%s'. BP error: '%s'»
4446
«Cannot create Section '%s' with A end TTP '%s', TTP already in use by Trail '%s'»
4447
«Cannot create Section '%s' with Z end TTP '%s', TTP already in use by Trail '%s'»
4448
«Proprietary NE with key %d and name '%s' not found in database»
4449
«Foreign NE with key %d and name '%s' not found in database»
4450
«Section named '%s' not found in database»
4451
«Proprietary NE with key %d and name '%s' not found in database»
4452
«Foreign NE with key %d and name '%s' not found in database»
4453
«Section named '%s' not found in database»
4470 4476,Invalid call during SNC promotion
SNC promotion failed.
4470
«Cannot promote SNC '%s' not used by TE '%s'»
4471
«Cannot promote a topological SNC ('%s')»
4472
«Cannot promote a SNC ('%s') with a hole»
4473
«Cannot promote an incomplete SNC ('%s')»
4474
«Cannot promote SNC '%s' with capacity %d different of the TE using it capacity %d»
4475
«Cannot promote SNC ('%s') used in multiples TEs»
4476
«Cannot promote Bidirectional SNC ('%s') into Unidirectional TE ('%s')»
4490 4491, Removes TEs from Path
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.
4490
«Cannot remove elements into protecting path of TE '%s' not protected»
4491
«Cannot remove the elements list from TE '%s', at least one element is not included in the path»
4500 4510, Connectivity analysis
 
4500
«Detected an unidirectional Trail, case not supported»
The FOXMAN-UN NP has detected that the last user action would lead to created Transport Entities that not valid end-to-end. Therefore, the user action is refused.
4501
«A TE without Z is linked to left or right connectivity»
4502
«Incompatible direction found during auto-generation processus»
4510
«Detected incompatible directionality while scanning b '%s'»
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.
4520 4545, Automatic channel selection
Automatic channel selection failed.
4520
«Cannot select channels in working path of TE '%s' with a hole in working path»
4521
«Cannot select channels in protecting path of TE '%s' with a hole in protecting path»
4522
«Cannot set the channel, LC path element corresponding to Trail '%s' not found in path of TE '%s'»
4523
«Invalid channel list furnished to set channel, at least channel '%s' does not exist in trail TTP '%s'»
4524
«Invalid channel list furnished to set channel, there is at least one null channel. Null Channels not allowed»
4540
«Invalid call to set path element channel, specified channel '%s' already used by LC in trail '%s'»
4541
«Cannot set channel %d for LC in trail '%s', found fixed MC '%s' as previous and first path element with channel '%s'»
4542
«Cannot modify the channel of LC in Trail '%s', found SNC '%s' with incompatible channels»
4543
«Cannot modify the channel of LC in Trail '%s', found SNC '%s' with incompatible channels»
4544
«Cannot modify the channel of LC in Trail '%s', found fixed MC '%s' with incompatible channel»
4545
«Cannot set channel because protecting or working path start with a MC not followed by a LC»
4550
«Cannot set TE end point to null»
This is a limitation of the FOXMAN-UN NP.
The operator is allowed to create a Transport Entity without specifying the Z TP, but he is not allowed to set it to an unspecified value once set.
4560
«Cannot unprotect non protected TE '%s'»
Please report the trouble 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.
4570
«Invalid internal parameter Circuit identifier ('%s'), the specified TE is not a Circuit»
Invalid call, a setting of Circuit user data has been requested on a Transport Entity that is not a Circuit.
Please report the trouble 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.
4571
«Invalid internal parameter, NE with null NEKey doesn't exist»
Invalid call. For the creation of a new Transport Entity, the A end Network Element has not been specified correctly.
Please report the trouble 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.
4572 4573, Invalid call, TE creation
Invalid call to the creation of a Transport Entity, an invalid channel is specified.
Please report the trouble 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.
4572
«Invalid internal parameter, the proposed channel ('%s') for the A end point doesn't exist for the TTP ('%s')»
4573
«Invalid internal parameter, the proposed channel ('%s') doesn't exist for the Z TTP ('%s')»
4574 4578, Invalid call, Routing
The user interface has allowed to perform routing actions on a Transport Entity that is not manageable, i.e. can’t be modified
Please report the trouble 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.
4574
«Cannot route a non manageable TE»
4575
«Cannot add a TE in the path of TE '%s', TE is a non manageable TE»
4576
«Cannot remove TEs from TE '%s', the TE is non manageable»
4577
«Cannot remove TEs from protecting path of the non protected TE '%s'»
4578
«Cannot modify TE '%s', cannot modify a non manageable TE»
4580 4581, Invalid call, Automatic channel selection
The user interface has allowed to perform routing actions on a Transport Entity that is not manageable, i.e. can’t be modified
Please report the trouble 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.
4580
«Cannot select channels of TE '%s', cannot modify a non manageable TE»
4581
«Cannot select channels of TE '%s', the path contains a hole element»
4582
«Cannot clear channels of TE '%s', cannot modify a non manageable TE»
Invalid Call, a non manageable TE can’t be modified by the operator.
Please report the trouble 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.
4583 4584, invalid call, get channel list
 
4583
«Cannot get possible channels of TE '%s', TE is not manageable»
4584
«Cannot get possible channels of TE '%s', TE is not a Trail»
4585 4587, invalid call, channel setting
Invalid Call, a non manageable TE can’t be modified by the operator.
Please report the trouble 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.
4585
«Invalid internal call to set channel, the channel list is empty»
4586
«Cannot set channel of TE '%s', TE is not manageable»
4587
«Cannot set channels of Hop '%s' in TE '%s', the Hop is not a Trail»
4588 4589, invalid call, protection/unprotection
Invalid Call, a non manageable TE can’t be modified by the operator.
Please report the trouble 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.
4588
«Cannot protect TE '%s', TE is not manageable»
4589
«Cannot unprotect TE '%s', TE is not manageable»
4590 4598, invalid call, invalid elements provided
Invalid Call, the user interface has provided invalid data to the FOXMAN-UN NP server.
Please report the trouble 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.
4590
«Invalid internal parameter, application with Id '%s' not found in database»
4591
«The requested element with Id '%s' is not a TE but a MC»
4592
«The requested element with Id '%s' is an internal non-manageable SNC included in a Foreign NE»
4593
«Requested TE with teId '%s' not found in database»
4594
«Requested Path with pathId '%s' not found in database»
4595
«Requested NE with NEKey '%s' not found in database»
4596
«Specified a transport entity Id '%s' that does not belong to current application»
4597
«The path of TE '%s' is invalid, it contains many times the same trail»
4598
«Requested TE with teId '%s' is already deleted»
4599
«Routing an Unknown TE is not possible»
Invalid Call, a non manageable Transport Entity can’t be modified by the operator.
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.
4610 4637, unexpected internal error during synchronization
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.
4610
«WARNING !! An error occurred during NE '%s' units generation. Look at the traces and launch again the resynchronization»
4611
«WARNING !! An error occurred during NE '%s' TTPs generation. Look at the traces and launch again the resynchronization»
4612
«WARNING !! An error occurred during NE '%s' MCs generation. Look at the traces and launch again the resynchronization»
4613
«WARNING !! An error occurred during NE '%s' Internal Sections generation. Look at the traces and launch again the resynchronization»
4614
«WARNING !! Database error occurred during NE '%s' units generation: '%s'»
4615
«WARNING !! Database error occurred during NE '%s' TTPs generation: '%s'»
4616
«WARNING !! Database error occurred during NE '%s' MCs generation: '%s'»
4617
«WARNING !! An error occurred during NE '%s' Internal Sections generation: '%s'»
4630
«WARNING !! An error occurred during NE '%s' Units synchronization. Look at the traces and launch again the resynchronisation»
4631
«WARNING !! An error occurred during NE '%s' TTPs synchronization. Look at the traces and launch again the resynchronisation»
4632
«WARNING !! An error occurred during NE '%s' MCs synchronization. Look at the traces and launch again the resynchronisation»
4633
«WARNING !! An error occurred during NE '%s' Internal Sections synchronization. Look at the traces and launch again the resynchronisation»
4634
«WARNING !! Database error occurred during NE '%s' Units synchronization: '%s'»
4635
«WARNING !! Database error occurred during NE '%s' TTPs synchronization: '%s'»
4636
«WARNING !! Database error occurred during NE '%s' MCs synchronization: '%s'»
4637
«WARNING !! Database error occurred during NE '%s' Internal Sections synchronization: '%s'»
4650 4660, unexpected communication error
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.
4650
«Cannot get a reference on the BPQueryNetworkMgr»
4660
«Corba exception prevents the Event Handler to attach the Observer. Please verify all process are running»
4670 4672, unexpected database error
The system error message as provided by the database is in the %s.
 
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.
4670
«Unexpected Database Error while generating Proprietaries NEs: '%s'»
4671
«Unexpected Database Error while generating Foreigns: '%s'»
4672
«Unexpected Database Error while generating Sections: '%s'»
4673
«Invalid call to group TPs with an empty TPs list, please select the list of TPs to group»
The user interface has allowed an invalid call.
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.
4674 4687, invalid calls to Network Query Manager
4674
«Invalid internal parameter, Application with Id '%s' not found in database»
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.
4675
«Invalid internal parameter, Application with Id '%s' not found in database»
4676
«Invalid internal parameter neKey (%d), Network Element not found in database»
4677
«Invalid internal parameter neKey (%d), Network Element not found in database»
4678
«Invalid internal parameter neKey (%d), it doesn't correspond to a Network Element»
4679
«Invalid internal parameter neKey (%d), Foreign Network Element not found in database»
4680
«Invalid internal parameter neKey (%d), Network Element not found in database»
4681
«Invalid internal parameter TTPAddress (%d|%d|%d|%d), TTP not found inside the NE '%s'»
4682
«Invalid internal parameter TE identifier (%d), the TE is a topological SNC (MC '%s') inside the foreign NE '%s'»
4683
«Invalid internal parameter TE identifier (%d), the identifier corresponds to MC '%s' not a TE»
4684
«Invalid internal parameter TE identifier (%d), TE not found in database»
4685
«Invalid internal parameter TE identifier (%d), the TE is a topological SNC (MC '%s') inside the foreign NE '%s'»
4686
«Invalid internal parameter TE identifier (%d), the identifier corresponds to MC '%s' not to a TE»
4687
«Invalid internal parameter TE identifier (%d), TE not found in database»
4700
«The BP provided 0 network elements»
This error is issued by npresynch/npinitdb scripts.
The BP provided an empty list of network element. Instead of clearing all existing data, the NP raised this error to prevent loosing the database in case of an error in the BP.
If the operation is correct, i.e. no equipment has already been configured, the user can bypass this error using the genapp command with –f option.
Please contact support to confirm.
4701 4702, Synchronization trouble
possible causes :
one of the specified NE name (-l flag used) does not exist in the database
retrieving Network Elements from the BP has failed
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.
4701
«WARNING !! An error occurred during NEs synchronization. Look at the traces and launch again the resynchronisation»
4702
«WARNING !! An error occurred during Proprietary NE '%s' synchronization. Look at the traces and launch again the resynchronisation»
4703 4704, Unexpected database error
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.
4703
«Database error '%s' occurred during Proprietary NEs synchronization»
4704
«Database error '%s' occurred during Foreign NEs synchronization»
4706
«Database error '%s' occurred during Sections synchronization»
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.
4707
«Generic resynchronisation is required, NE name mismatch is detected»
This error may happen when the operator has requested a synchronization of a specific set of Network Elements. The error means that one of the specified Network Element has the same name as an existing Network Element in the NP database but those Network Elements are not the same.
A global resynchronisation (npresynch command called without option) will give clean up mismatches in Network Element lists.
4720
«Received system database error: '%s'»
Database engine raised a system error which is put in %s.
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.
4730 4803, Internal error in database layer
 
4730
«Unsatisfying criteria, cannot specify a TP without its NE»
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.
4731
«Unsatisfying criteria, cannot specify a Slot without its NE»
4732
«The specified NE '%s' is a foreign and foreign NEs have no slots»
4733
«Specified Slot %d in NE '%s' is empty, there is no unit inside it»
4734
«Invalid internal call, the specified NE '%s' is a foreign and Foreigns have no slots»
4735
«Unit type '%s' does not exist in specified NE '%s'»
4736
«Unit type '%s' does not exist in specified slot %d of the NE '%s'»
4737
«Incompatible slot criteria, specified slot %d and TP slot (%d) are incompatible»
4738
«Specified NE '%s' is a foreign and foreign NEs have no slots»
4750
«Specified Slot '%s' in NE '%s' is empty, there is no unit inside it»
4751
«ALERT!!! More than one Unit matches the criteria NE '%s' Slot %d, the database needs to be re-synchronized»
4752
«More than one Section Protection matches the criteria (MC '%s'), the database needs to be re-synchronized»
4753
«Unit type not found in NE '%s'»
4760
«Failed to find TTP with address (%d/%d/%d/%d) in NE '%s'»
4761
«ALERT!!! More than one TTP matches the criteria TTP address (%d/%d/%d/%d) in NE '%s', the database needs to be re-synchronized»
4762
«MC '%s' in NE '%s' not found in database»
4763
«MC with TP '%s' in NE '%s' not found in database»
4764
«ALERT!!! More than one MC matches the criteria TP '%s' in NE '%s', the database needs to be re-synchronized»
4765
«NE with NE key %d not found in database»
4780
«Cannot determine if protecting path of TE '%s' is complete, the TE is not protected»
4790
«Trail '%s' is not a topological one, only topological Trails have a Section Address»
4800
«Invalid internal parameter, to find a CTP in a TTP you must specify a valid channel (not null)»
4801
«CTP with channel %d in TTP '%s' not found in database»
4802
«More than one CTP with channel %d in TTP '%s' matches the criteria, the database needs to be re-synchronized»
4803
«Invalid criteria to find TTPs. Specified Null NE key for Unit '%s'»
4810 4917, internal error
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.
4810
«Cannot delete LC with channel '%s' in Trail '%s', it is used by TE '%s' and recursive mode is off»
4820
«Cannot delete TTP, only TTPs in Foreigns can be deleted. TTP '%s' is in the proprietary NE '%s'»
4840
«Cannot get the TE using MC '%s', the MC is not used by a TE»
4841
«Cannot delete fixed MC '%s'»
4850
«Received Database Error: '%s'»
4860
«Cannot get protecting path of TE '%s', the TE has not a protecting path»
4861
«Cannot get hole in protecting path of TE '%s', the TE has not a protecting path»
4862
«Cannot get hole of TE '%s', the TE has no hole in '%s' path»
4863
«Path element in '%s' path of TE '%s' not found»
4870
«Path element is not a hole in path»
4871
«Path element is not a MC in path»
4872
«Path element is not a SNC in path»
4873
«Path element is not a LC in path»
4874
«Path element is not a Section Protection in path»
4880
«Path element info is not a MC in path»
4881
«Path element info is not a SNC in path»
4882
«Path element info is not a LC in path»
4883
«Path element info is not a Section Protection in path»
4890
«Invalid call, unidirectional Section Protection cannot be inverted»
4900
«Cannot detach SNC '%s'. Only simple and fixed SNCs can be detached»
4910
«TE '%s' has no application»
4911
«TE '%s' has no path»
4912
«Cannot get MC of TE '%s'. Only simple TEs have a MC as path»
4913
«Cannot set path of TE '%s', topological TEs have no path»
4915
«There is no a LC with channel %d in Trail '%s'»
4916
«Cannot delete TTP '%s'. TTPs used by TEs cannot be deleted if recursive mode is off»
4917
«Cannot delete the Unknown '%s' containing a fixed protected MC»
4920
«Cannot modify the name of an internal section»
This is a limitation in the FOXMAN-UN.
The name of an internal section (NT to LT cable) can’t be modified. A check is performed by the FOXMAN-UN NP.