2000 to 2007, failure while adjusting 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.

2000

«Affects another TE»

2002

«Affects integrity of different path sides of a TE»

2003

«Affects the integrity of TE '%s' without hole»

2004

«Found MC used by TE '%s'. Call demotion first»

2005

«One side connectivity research affects integrity of a TE, other side stopped because no more connectivity was found or a TTP was found»

2006

«Affects directionality of TE '%s'»

2007

«Connectivity problem, existing connectivity linked to a TTP ('%s') that is not the A or Z end point of TE '%s'»

2020

«Connectivity problem while completing path, left extremity of the hole (NE '%s' TP '%s') is a TTP different from TE '%s' end points»

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.

2040

«Incomplete information for a TE starting or finishing in a Foreign NE. Please specify A and Z end points»

This error is raised because the operator has requested the creation of an invalid Transport Entity.

The Transport Entity is invalid because the A extremity is set to a TP into a Foreign and the Z extremity is not specified. Such Transport Entity is not allowed.

2041

«Incomplete information for a topological SNC creation. Please specify A and Z end TP Labels»

This error is raised because the operator has requested the creation of an invalid Transport Entity.

The operator has requested the creation of a Transport Entity where both A and Z network elements are Foreign. The Transport Entity is invalid because the A or Z TP is not specified.

When creating a Transport Entity between two Foreigns, the TP extremities have to be set to existing TPs different from « Undefined Unit < 0> Null TP »

2042 to 2043, Autogeneration failure

An error occurred during network analysis.

The operator has requested the creation of a Trail or SNC which is followed by an analysis of the network to detect if new Transport Entity should be created as a consequence of the newly created Transport Entity. This analysis raised an error which is appended to this error.

2042

«Problem detected while analyzing connectivity after Trail '%s' creation»

2043

«Problem detected while analyzing connectivity after SNC '%s' creation»

2060

«Invalid call, channels cannot be grouped for TP '%s'»

2080 to 2085, initial connectivity failure

A user action can not be completed because the FOXMAN-UN NP has found an existing Transport Entity or MC that is preventing the action to be performed correctly.

The Transport Entity or MC should be deleted to complete the user action.

 

2080

«Found already used bidirectional SNC connected to TP '%s' while analyzing initial connectivity»

2081

«Connectivity linked to more than one SNC at TP '%s'»

2082

«Connectivity linked to Unknown TE ''%s''»

2083

«Connectivity linked to Circuit '%s'»

2084

«Connectivity linked to SNC '%s'»

2085

«Connectivity linked to a used MC»

2086

«Found an unknown transport entity during auto-generation processus»

The FOXMAN-UN NP forbids connecting a valid Transport Entity to any Unknown. Those valid Transport Entity are :

created by the operator

created by the FOXMAN-UN NP as a consequence of a Transport Entity created by the operator (SNC or Trails)

2100

«Cannot build a SNC including only another SNC ('%s')»

This is a limitation of the FOXMAN-UN NP.

The user as requested the creation of a SNC type Transport Entity which A and Z extremities are matching the A/Z of an existing SNC, this user action is not allowed.

2120 to 2140, Transport Entity integrity impact

The operator has requested the creation of a Transport Entity which conflicts with existing Transport Entities.

2120

«Connectivity problem, affects integrity of more than one TE»

2140

«Connectivity problem, affects integrity of another TE with different number of 64k»

2160

«Cannot delete a MC used by a TE. MC '%s' is used by TE '%s' and recursive mode is off»

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.

2180

«Invalid channel '%s', please perform a ClearChannel at point NE '%s' TTP '%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.

2200

«Cannot delete SNC '%s'. The SNC is used by TE '%s' and recursive mode is off»

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.

2210

«Cannot delete a trail ('%s') used by an unknown 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.

6000 to 6009, errors during processing of npfotool_termination.csv and npfotool_crossconnect.csv

6000

«Failed to find section '%s'»

This errors is raised during the processing of an entry in npfotool_crossconnect.csv.

The Section label provided in the csv file does not exist. Please check the section name. Typos are a common error, the name matching is case sensitive.

Check the label name and call npresynch.

6001

«Section called '%s' found multiple times»

This error is raised during the processing of an entry in npfotool_crossconnect.csv.

This is a limitation of the FOXMAN-UN NP, multiple sections called ‘%s’ connect the same Foreign. A unique name should be provided to sections connecting a Foreign.

Please, provide a unit name in FOXMAN-UN BP or modify section name in the FOXMAN-UN NP user interface and call npresynch.

6002

«TTP '%s' has no channel»

This error is raised during the processing of an entry in npfotool_crossconnect.csv.

The processing has found a TTP which does not have any channel and the cross-connect entry in the csv file specifies one.

Check the entry, if the trouble still exists then 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.

6003

«A channel should be provided to break ambiguity on TTP '%s'»

This error is raised during the processing of an entry in npfotool_crossconnect.csv.

An entry in the csv is ambiguous, please check the User Manual to find which channel is missing.

Please, report the trouble to the Customer support if it is not solved. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem.

6004

«Failed to match channel '%s' on TTP '%s'»

This error is raised during the processing of an entry in npfotool_crossconnect.csv.

A channel name has been specified in the csv that does not exist on a TTP in the database.

Check the channel name in the csv entry, typos are a common error

Check the csv entry using the User Manual.

Please, report the trouble to the Customer support if it is not solved. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem.

6005

«Failed because Trail '%s' should support channel '%s'»

This error is raised during the processing of an entry in npfotool_crossconnect.csv.

Specified trail in the network doesn’t have then channel provided in last %s available on both extremities. In most cases it is due to CAS availability on a P12 Trail where the CAS setting is different on Trail extremities (ON/ OFF) thereby making available the T16 timeslot on one side but not on the other.

Please set the CAS to the same configuration on both extremities.

Please, report the trouble to the Customer support if it is not solved. Refer to «Support» at the beginning of this appendix for the information to be provided for an efficient analysis of the problem.

6006

«Reached invalid Termination Point, a SNC was expected here. '%s'/'%s'»

This error is raised during the processing of an entry in npfotool_crossconnect.csv.

This is an 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.

6007

«Reached invalid Termination Point, SNC prevents creation of Trail at '%s'/'%s'»

This error is raised during the processing of an entry in npfotool_crossconnect.csv.

The network contains an SNC that prevents the handling of a csv entry.

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.

6008

«Failed to find foreign called '%s'»

This error is raised during the processing of an entry in npfotool_termination.csv.

Typos are a common error, please check that the Foreign name is matches the real Foreign name of FOXMAN-UN NP.

6009

«Found multiple Foreigns called '%s'»

This error is raised during the processing of an entry in npfotool_termination.csv.

The Foreign names specified in the csv should be unit in the network. Please provide a different name.