Application
Code | Error | Description/Possible Action |
|---|---|---|
1000 | «A loop is detected while analyzing connectivity» | This error may happen in two contexts: the user has created a Transport Entity that leads to the creation of a loop in the network =>The FOXMAN-UN NP forbids the creation of loops in the network through the GUI. If a loop is required, then the user has to create individually each MC in the FOXMAN-UN BP. It will be immediately identified as an Unknown. during the initialization of the network npresynch while processing npfotool_crossconnect.csv and npfotool_termination.csv, an existing loop is detected, the loop should be detected and removed. The FOXMAN-UN NP will not allow the user to create Transport Entities that are not End-To-End through the FOXMAN-UN NP using : the user interface. npfotool_crossconnect.csv and npfotool_termination.csv |
1010 | «A loop is detected while analyzing connectivity» | See 1000 |
1011 | «Connectivity linked to Trail '%s' without Z End Point» | The requested action is not possible because the FOXMAN-UN NP has detected that a Transport Entity being created is bound to an existing trail that doesn’t have a Z extremity. Locate and delete this trail first before creating any Transport Entity. |
1012 | «Connectivity linked to SNC '%s' without Z End Point» | The requested action is not possible because the existing connectivity of the TE being created is bound to an existing SNC that doesn’t have a Z extremity. Locate and delete this SNC to remove this error. |
1013 | «Found '%s' with incompatible direction while analyzing connectivity» | Happens during the processing of npfotool_crossconnect.csv and npfotool_termination.csv generation or through the user interface. The processing has raised an error because of a directionality mismatch with MC or SNC in the network. Please check that the directionality of the specified MC or SNC is correct. |
Found | %s |
|---|---|
MC | ‘MC(« MC Label »)’ |
SNC | ‘SNC(« SNC Label »)’ |
Code | Error | Description/Possible Action |
|---|---|---|
1020 1025, Integrity problem. | ||
1020 | «Affects integrity of more than one TE» | The FOXMAN-UN NP is designed such that it will prevent the user from creating non End-to-End connectivity. Invalid End-to-End connectivity may be: Loops : the signal doesn’t have an origin and a destination SNCs : between two extremities used for Circuits (Subla/Exlic/..) … « Integrity » troubles are related to those Transport Entities created or modified that are not valid. |
1021 | «Affects integrity of the Unknown TE '%s'» | |
1022 | «Affects integrity of TE '%s' in Application '%s'. Current Application '%s'» | |
1023 | «Affects integrity of Circuit '%s' in Application '%s'. Current Application '%s'» | |
1024 | «Affects integrity of a TE in a different Application. Current Application '%s'» | |
1025 | «Found SNC with incompatible direction while analyzing connectivity» | |
1026 | «Connectivity linked to SNC '%s' without Z End Point» | The user has created a Transport Entity which is impacting a SNC without Z. The operator should first clean up the network : Identify the SNC : why is it there ? is it used ? can it be deleted ? Delete it or set its Z extremity. |
1040 | «Detected incompatible directionality while autogenerating '%s' '%s'» | This error happens during the processing of npfotool_crossconnect.csv and npfotool_generation.csv files or using the User Interface. First %s = « bidirectional » or « unidirectional » Second %s = « Circuit », « Trail », « SNC » During a « connectivity analysis » a directionality mismatch has been detected that should generate an Unknown if the user request would be accepted. Existing Unidirectional cross-connections are bearing the signal in opposite directions. |
1041 | «Detected incompatible directionality while autogenerating '%s' '%s'. Found Unidirectional MC '%s'» | See 1040 |
1042 | «Detected incompatible directionality while autogenerating '%s' '%s'. Found Unidirectional SNC '%s'» | See 1040 |
1043 | «Detected incompatible directionality while autogenerating a Trail. Cannot generate a Unidirectional Trail» | The Trail is bidirectional bearer, the FOXMAN-UN NP does not allow a user to create a unidirectional Trail. |
1050 | «Invalid point for SNC demotion, demoted SNC cannot start with a protected MC» | This is a limitation of the FOXMAN-UN NP. The operator has requested a special demotion not managed by the FOXMAN-UN NP. The set of path elements to be demoted should not start or end with a protected Cross Connection. The demotion always leads to gathering Path Elements into a new non protected SNC. |
1051 | «Invalid Z end point for SNC demotion, demoted SNC cannot end with a protected MC» | See 1050. |
1052 | «Invalid call to SNC demotion, cannot demote whole content of '%s' path of TE '%s' (A end NE , A end TP '%s', Z end NE '%s', Z end TP '%s' )» | This is a limitation of the FOXMAN-UN NP that considers meaningless to demote all Path Elements of a Transport Entity. |
1060 | «Cannot get channel list, number of remaining timeslots (%d) in trail '%s' is lower than TE '%s' number of timeslots (%d)» | The operator has requested the list of available channels for a LC but the Trail providing the LC doesn’t have enough capacity for setting the specified LC. Ex : a P12 Trail has 4 timeslots available whereas the current Transport Entity will use more than 4 timeslots. |
1061 | «A loop is detected while analyzing connectivity» | This error occurs during the processing of npfotool_crossconnect.csv and npfotool_termination.csv files or through the FOXMAN-UN NP user interface. The FOXMAN-UN NP doesn’t allow the creation of loops, they are not end-to-end constructs. |
1071 | «Nb of 64 kbits incompatible between A('%s') and Z('%s') end points» | The operator has specified A and Z extremities of a Transport Entity which have different number of P0 channels. Different number of P0 channels is allowed only for circuit between an ISDN unit and a G.703 data termination unit (GECOD). |
1072 | «CAS incompatibility between A end TP ('%s') CAS '%s' and Z end TP ('%s') CAS '%s'» | The FOXMAN-UN NP takes care of the CAS flag to ensure its compatibility when needed : Circuit : when a circuit is created, the CAS should be either ON or OFF on both extremities. If the CAS is ON, the FOXMAN-UN NP provides only SNC and Trails which CAS is ON at both extremities, whereas a CAS OFF Circuit doesn’t care about CAS parameter for routing. Trail : when the user creates a PDH trail, the CAS should be either ON or OFF on both extremities of the Trail SNC : when a SNC is created, CAS should be either ON or OFF on both extremities except if « np_incompatible_cas_allowed_for_snc » is set to « true » in the configuration file (np.conf). Note: FOXMAN-UN NP does not check whether both extremities of a Circuit have the same CAS setting. NP only checks whether the SNC/Trail can transport CAS. |
Transport Entity | Extremity CAS | Routing |
|---|---|---|
Circuit | ON/OFF | |
OFF/ON | ||
ON/ON | Only ON/ON Trail and SNCs | |
OFF/OFF | ||
Trail | ON/ON | |
OFF/OFF | ||
SNC | ON/OFF | |
OFF/ON | ||
ON/ON | Only ON/ON Trail and SNCs | |
OFF/OFF |
Code | Error | Description/Possible Action |
|---|---|---|
1073 | «Invalid TE end points for an SNC, A and Z end points are two TTPs. Please change A ('%s') or Z ('%s') end points (at least one must be a CTP), or change the type of the TE» | The operator has requested the creation of an invalid Transport Entity. The specified extremities are matching Trail criteria. The FOXMAN-UN NP prevents from creating a SNC which extremities are matching for a Trail Transport Entity type. See 1074, the same rule is applied for Circuits, a SNC can’t be created instead of a Circuit. |
1074 | «Invalid endpoints for an SNC, A and Z end TP are Circuit end points. Please create a Circuit instead of an SNC» | The operator has requested the creation of an invalid Transport Entity. The specified extremities are matching Circuits criteria. The FOXMAN-UN NP prevents from creating a SNC instead of a Circuit. See 1073, the same rule applies for Trails. |
1075 | «A and Z end points are identical (NE '%s', TP '%s'). Please change value of A or Z end point» | The operator has requested the creation of an invalid Transport Entity. The operator has specified two TPs which refer to the same point in the network. The FOXMAN-UN NP doesn’t allow the user to create a loop through the User Interface. Loops are not valid End-to-End Transport Entities. |
1076 | «Invalid end point (NE '%s', TP '%s') that uses timeslots partially used by the TE named: '%s'» | The operator has requested the creation of an invalid Transport Entity. The operator has specified a TP extremity or rate P0nc which is already partially used by another existing Transport Entity. Example: an existing P0nc Transport Entity starts on a LEDE1 using timeslots T1-6 and the operator has requested the creation of a Transport Entity starting on the same LEDE1 sbu with timeslots T4-7. An overlapping is detected for T4-6. This is forbidden by the system. |
1090 | «Cannot promote a protected SNC ('%s')» | The promotion requested by the operator is not valid. The promotion of a SNC is allowed only if the SNC is completely routed and not protected. Promotion of protected a SNC is not allowed. |
1100 | «Cannot remove fixed sub path from bidirectional TE '%s'» | The user requested that elements of a path (SNC or LC) are removed from a selected Path. One or more elements can’t be removed because they are part of the configuration that can’t be modified. Ex : The user has created a circuit from a SULIC on a Network Element A to another SULIC in another network element. Once created the Path of the circuit is : [ MC LC Hole LC MC ]. LCs in the Path are associated to the link between the NT and the Mux and can’t be removed from the Circuit at FOXMAN-UN NP level. |
1101 | «Invalid call, cannot remove fixed sub path from TE '%s'» | See error 1100 |
1120 | «Channel selection failed on protecting path of TE ''%s''» | Automatic channel selection action failed because the FOXMAN-UN NP did not find a set of possible channels for the protecting path. Check that the network capacity allows the Transport Entity to be completed. |
1121 | «Failed to select channels in TE '%s'» | Automatic channel selection failed for the working path, existing network capacity does not allow completing the Transport Entity. |
1122 | «Cannot set channel, more than one channel furnished and TTP '%s' cannot be grouped» | The user has tried to set multiple channels to a LC, the trail forbids the usage of multiple channels once. Ex using multiple KLMs for one LC. VC12/VC3 Transport Entities are bearing only one VC12 or VC3. N*VC12 or n*VC3 Trails are allowed, only n*P0 Transport Entities may be allowed. |
1123 | «Cannot set channel, number of timeslots in channel list (%d) different of TE number of timeslots (%d)» | In the case of P0nc, the channel of a LC has to be set to the same number of timeslots than the Transport Entity using the LC. |
1124 | «Cannot set channel, number of timeslots in TTP channel list (%d) different of TE number of timeslots (%d) and TTP '%s' can not be grouped» | The user interface did an invalid call to the server. 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. |
1140 | «Invalid channel %d for LC in trail '%s', connectivity problem» | The user interface has allowed performing an invalid request. The FOXMAN-UN NP has failed to set the specified channel to a Trail (the name is provided). The operator has asked to set a LC with a channel from the channel list window where all possible channels have been computed by the FOXMAN-UN NP. This channel should not have been provided by the server. 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. |
1150 | «Cannot change the A end point of a TE without Z end point» | This is a limitation of the FOXMAN-UN NP. The operator can create a Transport Entity without setting the Z extremity at creation time. For such Transport Entities it’s not possible to modify the A extremity unless Z is set. |
1151 | «Cannot change TE end point of a topological TE» | A topological Transport Entity is the physical cable (electrical or optical), the FOXMAN-UN NP is not intended to configure the topology of the network. Please, remove the cable in the BP and the FOXMAN-UN NP will be notified of the deletion. |
1152 | «Cannot change TE A End Point of a unidirectional TE» | This is a limitation of the FOXMAN-UN NP. |
1153 | «A Foreign to Foreign Transport Entity must be a SNC ( '%s' )» | Rules applied to Transport Entity extremities. |
Source to destination | SNC | Circuit | Trail |
|---|---|---|---|
Foreign to Foreign | OK | ||
Foreign to Mux | OK | OK | |
Mux to Foreign | OK | OK | |
Mux to Mux | OK | OK | OK |
Code | Error | Description/Possible Action |
|---|---|---|
1154 | «Cannot set the A end point of a simple TE» | This is a limitation of the FOXMAN-UN NP. A simple Transport Entity has a Path made of one MC only, the A extremity for such Transport Entity can’t be modified. |
1155 | «Setting A and Z points in the same NE is not allowed when the TE is protected (TE is ' %s ')» | The FOXMAN-UN NP does not allow creating a protected Transport Entity which extremities are inside the same Network Element. Such a Transport Entity is useless. |
1156 | «Cannot set TE end point to NE '%s' already used in its path. Please remove elements in path using this NE before» | The FOXMAN-UN NP prevents the user creation of loops. This happens typically in next configuration : A Transport Entity has a Path starting into a Network Element NEA, ending in NEZ and crossing { NE1 NE2 NE3 }. { NEA NE1 NE2 NE3 NEZ } It’s not possible to modify Z Extremity to NEA, NE1, NE2 and NE3. To modify Z to be into NE2, the user has to remove elements into the path such that the path reaches NE2 and doesn’t leave it. |
1157 | «Cannot change the A or Z end points of a TE in use. SNC '%s' is used at least by TE '%s'» | See 1158 |
1158 | «Invalid call, cannot change the A or Z end points of a TE in use. Trail '%s' is used at least by TE '%s'» | SNC/Trails are Transport Entities which are intended to be used by other Transport Entities. Their A and Z extremity can be set to any other valid extremity only if the TE is not used. |
1159 | «Invalid call, cannot set A or Z end points into a foreign element because the SNC is not topological» | A SNC is either FOX51x to FOX51x, FOX61x to FOX61x or Foreign to Foreign. It’s not possible to move modify the A or Z of a SNC from one NE Type (FOX51x/FOX61x/Foreign) to another. see 1153 for rule extremities. |
1170 | «Cannot delete fixed or autogenerated TE '%s'» | The FOXMAN-UN NP gives ALL existing Transport Entities in the network. Transport Entities are either : Created by the user: using FOXMAN-UN NP or BP. Those Transport Entities can be managed: deleted, modified, rerouted Fixed : they can’t be managed by the user because they are physical cables (Optical, Electrical). Autogenerated : logical connectivity defined by the SDH/PDH/DSL hierarchies that can’t be modified. Example : SDH provides Regeneration/Multiplexing/VC4 layers. The latter two can’t be managed (deleted/modified) through the FOXMAN-UN NP. |
1171 | «Invalid parameters, A and Z end points are identical» | The user required to create a Transport Entity which extremities are referencing the same point, therefore creating a loop in the network. Creating loop is not allowed from the user interface. |
1172 | «Invalid call, promotion requires the TE and the SNC to be in the same application» | Check that the selected SNC is in the Application of the selected Transport Entity. Double click on the SNC : if the SNC is in the same Application a message window is opened if the SNC is in another Application, the associated Application window is opened or created. The operator should move the SNC into the current Application window to perform the promotion of the SNC. |
1175 | «Specified TP does not exist in Foreign NE '%s'. Please specify a correct TP Label in Foreign NE '%s'» | See 1176 |
1176 | «Specified TP does not exist in NE '%s'. Please specify a correct TP Label in NE '%s'» | The FOXMAN-UN NP provided a TP that doesn’t exist in the database any more, the network may have been modified between the query and the usage of the TP. Please query again the TP, it should not exist anymore. 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. |
1190 | «Application already opened by another client» | Someone is already editing the Application. The FOXMAN-UN NP is a client/server application, the server may be contacted by multiple clients in parallel but the same Application can’t be opened twice. |
1191 | «Cannot accept the connection, maximum number of connections %d reached» | The FOXMAN-UN NP has a maximum number of edited Applications at the same time. This maximum has been reached. |
1200 | «Application not found in database. Please retrieve new data» | The user has requested the visualization of an Application that’s doesn’t exist in the database anymore. The Application may have been : previously deleted by the user a network configuration has been detected which led to the deletion of the Application. |