- 1.1 Error Messages
- 1.2 Warning Messages
- 1.3 Information Messages
- 1.4 Traffic Mapping Troubleshooting
- 1.4.1 Wavelength Exceeded
- 1.4.2 Invalid Routing
- 1.4.3 Cannot Find Alternate Route
- 1.4.4 Cannot Route Service
- 1.4.5 Overlapped Services Assigned to the Same Wavelength
- 1.4.6 Protected Services Assigned to the Same Wavelength
- 1.4.7 Cannot Route Service Because of Add/Drop Constraints
- 1.4.8 Design Requires a ROADM or Full Mux/Demux Site
- 1.5 Amplifier Troubleshooting
- 1.5.1 Incompatible DCUs (C-Band)
- 1.5.2 MMU Does Not Have Correct Amplifier (L-Band)
- 1.5.3 MMU Does Not Have Correct Amplifier (C-Band)
- 1.5.4 Output Power or Tilt are Out of Range
- 1.5.5 Invalid Fiber Values, Types, and Loss Values
- 1.5.6 Attenuator Forcing Not Allowed
- 1.5.7 Unavailable Add/Drop Channels
- 1.5.8 Tilt Forced When No Tilt Design Is Selected
- 1.5.9 Cannot Replace 32-DMX with 32DMX-O
- 1.5.10 Preamplifier Working in Invalid Mode
- 1.5.11 Gain Too Low for an Amplifier
- 1.5.12 Gain Too High for an Amplifier
- 1.5.13 User Forcing Overridden
- 1.5.14 Unsupported Configuration
- 1.5.15 Channel Power Near the Fail Threshold
- 1.5.16 Channel Power Below the Fail Threshold
- 1.5.17 OSC Channel Power Below the Fail Threshold
1
This chapter lists the system messages for Cisco Transport Planner. They are classified as:
- Error Messages
- Warning Messages
- Information Messages
- Traffic Mapping Troubleshooting
- Amplifier Troubleshooting
Note
In the System Messages, Cisco Transport Planner will replace {n} with a Site name, an Unit name, an Optical design rule, or a Number as applicable.
1.1 Error Messages
Error Messages for Cisco Transport Planner are listed in Table 1-1 :
|
|
|
|---|---|
Encryption property has changed. Network must be re-analyzed for this new property to be applied on the card. Do you wish to continue? |
|
Revert back encryption to old value or allow re-analysis of network. |
|
Current Int/Deint forcing is not supported in current configuration. |
|
Demand {0} built from OCHNC is in invalid status,Edit as required and right click and validate to analyze. |
|
With 'Activate AR-XPE' Flag Active, we cannot have ClientPayG option enabled. Please disable it. |
|
Verify if in Add/Drop sites, OADM units are forced and compatible with the traffic. |
|
No available wavelength due to units forced on optical bypass site {0} |
|
Verify if in the optical bypass interfaces there are wavelengths compatible units |
|
The network is broken: please connect all the sites together. |
|
The traffic model is empty: please add at least one service request. |
|
Number of add/drop nodes exceeded the maximum ({0}) allowed in the network. |
|
ONS15454 DWDM platform supports up to {0} non-pass-though sites. |
|
Line+ sites can’t support DMX-O units due to layout constraints. |
|
Line+ sites can’t support Individual Shelf with DCC chain option due to layout constraints. |
|
Can't find a valid path between site {0} and site {1} due to ROADM demand strategy |
|
Any to Any traffic requires ROADM units but ROADM is not allowed by restricted equipment list. |
|
Can't place ROADM units in site {0} to support Any to Any traffic. |
|
ROADM configuration is not allowed by restricted equipment list. |
|
Mux Demux configuration is not allowed by restricted equipment list. |
|
Only ROADM configuration is allowed with selected design rules. |
|
Line+ or Terminal+ site topologies are not allowed by selected design rules. |
|
Line+ or Terminal+ site topologies require ROADM units but ROADM is not allowed by restricted equipment list. |
|
OADM unit {0} defined in {1} is not allowed by restricted equipment list. |
|
Interface Type {0} is not supported by the selected Design Rules. |
|
All solutions exceed {0} wavelengths. See the “Wavelength Exceeded” section. |
|
The anti ASE option is available only in sites with add/drop capability. |
|
In a network with hub nodes protected services are allowed only between hub sites. |
|
Invalid routing (out of network boundary). See the “Invalid Routing” section. |
|
Can’t find alternate route due to multiple HUB nodes along the path. See the “Cannot Find Alternate Route” section. |
|
Can’t route service through HUB node {0}. See the “Cannot Route Service” section. |
|
Overlapped services assigned to the same wavelength. See the “Overlapped Services Assigned to the Same Wavelength” section. |
|
Protected services assigned to the same wavelength. See the “Protected Services Assigned to the Same Wavelength” section. |
|
Can’t route service due to add drop equipment constraints. See the “Cannot Route Service Because of Add/Drop Constraints” section. |
|
Design requires forcing a site as ROADM or Full Mux/Demux but no valid site was found. |
|
Design requires forcing site as ROADM or Full Mux/Demux: remove equipment constraints. |
|
In a linear network, terminal sites must have structure Terminal |
|
The Network is broken: please connect all the sites together |
|
The traffic model is empty: please add at least one service request |
|
Number of add/drop nodes exceeded the maximum ({0}) allowed in the network |
|
ONS15454 DWDM platform supports up to {0} non-pass-though sites |
|
Line+ sites can’t support DMX-O units due to layout constraints |
|
Line+ sites can’t support Individual Shelf with DCC chain option due to layout constraints |
|
Any to Any traffic requires ROADM units but ROADM is not allowed by restricted equipment list |
|
Can’t place ROADM units in site {0} to support Any to Any traffic |
|
ROADM configuration is not allowed by restricted equipment list |
|
WXC configuration is not allowed by restricted equipment list |
|
Mux Demux configuration is not allowed by restricted equipment list |
|
Only ROADM configuration is allowed with selected design rules |
|
Multidegree structure in site {0} is not allowed with selected design rules |
|
Line+ or Terminal+ site topologies are not allowed by selected design rules |
|
Line+ or Terminal+ site topologies require ROADM units but ROADM is not allowed by restricted equipment list |
|
OADM unit {0} defined in {1} is not allowed by restricted equipment list |
|
In mesh network user must force OADM units for site configured as OADM |
|
Interface Type {0} is not supported by the selected Design Rules |
|
The anti ASE option is available only in sites with add/drop capability |
|
No specific anti-ASE node is required for this traffic matrix requirement |
|
In a network with hub nodes protected services are allowed only between hub sites |
|
Routing for some of the services cannot be completed with the given constraints. Please use the link aside for details about the problem. |
|
Design requires forcing a site as ROADM or Full Mux/Demux but no valid site was found |
|
Design requires forcing site as ROADM or Full Mux/Demux: remove equipment constraints |
|
PP4 is not allowed in site {0} (fiber interfaces are limited to A,B,C and D) |
|
Unit options are not compatible with design rule {0} in site {1} |
|
Unit options are not compatible with design rules in site {0} |
|
Protected circuits are not allowed in a linear traffic subnet |
|
Client protection is not allowed if all nodes are single card configuration |
|
Trunk protection with no client protection is not allowed if at least one node is double card configuration |
|
Errors were found on {0}: please run the checker and fix all problems |
|
Client and trunk protections are not allowed at the same time on port {0} in site {1} |
|
50 GHz scalability is not supported with Ethernet or TDM aggregated demands |
|
Cards required for {0} demand are not available in the equipment list |
|
Impossible to find two independent paths for protected service |
|
Demand {0} defined on traffic subnet {1} is in an invalid status |
|
32MUX-O/32-DMX-O cards are not allowed for PSM configuration |
|
Terminal or Terminal Plus configurations are not allowed for PSM Och protection |
|
Is not allowed to insert circuit from site {0} to site {1} because is tagged as Omnidirectional Entry Point configuration |
|
Is not allowed to insert Any to Any Group contains site {0} and site {1} because is tagged as Omnidirectional Entry Point configuration |
|
No Interoperable group found for the card selection. Please check if its a valid card selection |
|
Restricted Equipment forced by user tm.client_restricted2.details = Client {0} is not available in the equipment list |
|
Cannot force different cards for protection {0} in demand {1} |
|
Trunk pluggable not found. The pluggable(s) may be restricted by the user. |
|
OTU2 XP can have both in/out going trunks in EFEC only in Enhanced Regen Mode |
|
Mux-Demux should not be forced for site ( {0}) as it is not supported by the site type. |
|
For hybrid 216 {0} only FLA8 and MD-40 Mux/Demux is allowed. |
|
The express loss in the site {0} is High. Please reduce the number of FLAs. |
|
The add/drop loss in the site {0} is High. Please reduce the number of FLAs. |
|
We cannot mix hybrid 15216 sites with non-hybrid pure MSTP site {0}. |
|
L-Band optical subnet rule is not supported in 15216 network. |
|
Multiple optical subnets are not supported in single 15216 cluster. |
|
A 15216 network is capable only till C Band odd 40ch. Please remove any higher capacity selected {0}. |
|
Site type Mux/Demux not allowed for {0} in 8 ch optical subnet. |
|
PSM Line or Section protection at {0} is not allowed with 15216 network. |
|
There is an overlap in the Route involving {0}. This may be due to the order of regeneration selected. |
|
Trunk protection with no client protection is not allowed for selected traffic type. |
|
ROADM demand is not supported for PSM Line, PSM Section topology. |
|
SMR Multidegree site {0} cannot have an omni-direction entry interface. |
|
SMR Multidegree is not allowed in site {0} (fiber interfaces are limited to A,B,C and D) |
|
PP-Mesh-4-SMR is restricted. SMR Multidegree is not possible in site {0} |
|
Incorrect Client Interface forcing for LAN-WAN Conversion traffic. |
|
A demand Added or Dropped to a Remote Add/Drop Site cannot be Colorless. |
|
This demand is conflicting with the Wavelength {0} with some other new demand.Please unlock the demand and re-analyze. |
|
50Ghz design is not allowed for site {0} with Remote Add/Drop. |
|
Invalid Structure for {0}. Only Multidegree Site can be OmniDirectional. |
|
Cannot Route demand! Didn't find any valid OmniDirectional Side. |
|
OmniDirectional Sides not possible for this protected demand in {0}. Atleast two sides needs to be available. |
|
Cannot Route demand! Didn't find any OmniDirectional Side for {0}. |
|
OmniDirectional Side not possible in {0}. No Free side left. |
|
Optical ByPass is not allowed for OmniDirectional or(and) Colorless Demand. |
|
No Colorless Ports found in {1}. Please force the {0} as OmniDirectional or force any Line Side in the site with Colorless Ports. |
|
Atleast one colorless port must be forced for demand {0} at {1}. |
|
Demand {0} defined on traffic subnet {1} is in an invalid status. |
|
Side/Side Cabling option should be Auto for SMR2 type in site {0}. |
|
Omni-directional interface is not allowed for site type {0}. |
|
Omni-directional interface is not allowed for site functionality {0}. |
|
0} has only {1} Layer-I Colorless Ports against the needed {2} ports.Please update the forcings. |
|
{0} has only {1} Colorless ports available.Layer-II units are not allowed for non-omnidirectional OXC/SMR interface. |
|
Site Connected to Remote Spur Duct should be of functionality Add/Drop and type Mux-Demux. |
|
Selected functionality or type does not support Remote Add/Drop Port on it. |
|
Mux-Demux should not be forced on side ( {0}) which is not connected to any duct and not forced as omnidirectional. |
|
Mux-Demux cards cannot be forced on {0},Since second layer cascade is not allowed on {1} site. |
|
Forcing of mux/demux is not allowed on {0},since all available add/drop ports has been remotize'd. |
|
Forced Site type does not allow to remotize more than {0} add/drop ports. |
|
Preamplifier setting on {0} is not compatible with M2 chassis type setted on this site. |
|
Booster amplifier setting on {0} is not compatible with M2 chassis type setted on this site. |
|
In {0}, OSC-CSM forcing is not compatible with OSC frame type selected. |
|
[SiteName1], [SiteName 2] do not have 2 Omni Interfaces with at least 1 colorless port each. |
|
[SiteName1], [SiteName 2] do not have Omni Interfaces with at least 2 colorless ports each. |
|
Measurement unit (e.g. k.m., miles etc.) of the two fibers are not same. |
|
Do you want the ducts connected to be merged Click Yes if you want to Merge or else No to delete the Ducts Apply Changes. |
|
Can only Merge Fibers for Line or Line Plus site [SiteName] is [topology]. |
|
No free colorless port is available in {0} for {1} ROADM demand |
|
Site Connected to Remote Spur Duct should be of functionality Add/Drop and type Mux-Demux (OR) OADM with FLD Units Forced. |
|
OADM units forced after unlocking the Node Add/Drop Mux/De-Mux, Unlock the service demands which are adding or dropping for site {0} interface {1} |
|
Either OADM units changed to FLD or FLD units changed to oadm cards, Unlock the service demands which are adding or dropping for site {0} interface {1} |
|
Site {0} is forced with non FLD4 Units. Multiple Optical ByPass is allowed only with FLD4 units. |
|
The configuration requires upgrade of Line site {0} to multi-degree. Please unlock the site to proceed. |
|
There is no {0} -> {1} configuration supporting colorless non-100G traffic. |
|
The present number of Omnidirectional Sides exceeds the number which can be supported by the selected 'Scalable Upto Degree' parameter at {0}. Maximum omnidirectional sides supported is {1}. |
|
Traffic matrix at {0} is not supported. There is no Mux/Demux configuration supporting termination of colored and colorless traffic. |
|
Traffic matrix at {0} is not supported. No free ports available to route the configured demands. |
|
Forced 100G+non-100G colorless ports can''t be supported at {0}. Maximum colorless ports allowed at this interface is {1}. |
|
{0} cannot have more than {1} Non-100G colorless ports forced |
|
Side {0} of MSTP Site {1} is forced with 48 /96 channel rule which is not supported. Please create a MSTP supported optical subnet rule. |
|
Auto Upgrade of Site {0} from Line to Multidegree is not possible as total number of colorless 100 G ports and non 100G ports exceeds 13 at the interface {1} |
|
Client interface {0} is not supported on sites of node type NG-DWDM. |
|
DWDM Trunk adapter {0} is not supported on sites of node type NG-DWDM. |
|
Traffic matrix at {0} is not supported. Sum of forced 100G, non-100G colorless ports and colored demands can''t be greater than the number of channels supported by the optical subnet rule. |
|
Traffic matrix at {0} is not supported. Sum of forced 100G, non-100G colorless ports and colored demands (including A2A demand) can''t be greater than 96 for omnidirectional sides. |
|
Traffic matrix at {0} is not supported. No free wavelength available to route the configured number of omnidirectional demands. |
|
Traffic matrix at {0} is not supported. For A2A colored to be simulated, there should be at least one unreserved wavelength. |
|
Could not find any valid flex configuration for the traffic matrix defined at {0}. This could be because of configuration limitations, invalid forcings or equipment restrictions. |
|
Number of sides are more than 8 at MSTP site {0}. This is not allowed. |
|
The present number of line Sides exceeds the number which can be supported by the selected 'Scalable Upto Degree' parameter at {0}. |
|
Invalid number of colorless 100G ports at {0}. There is no {1} -> Mux/Demux configuration supporting more than 64 colorless 100G demands. |
|
Remote spur is present at Site {0}. NG-DWDM does not support remote spur. |
|
Invalid Omni Side forcing at {0}. 4x4-COFS can't support omnidirectional functionality for more than 4 degree node. |
|
Traffic matrix at {0} is not supported. There is no sufficient 100G ports available for the configuration. |
|
No valid Omnidirectional side with colorless ports to route the Roadm demand. |
|
Traffic matrix at Site {0} is not supported. Configuration at Side {1} is incompatible with configurations at other omni sides due to Optical restrictions. |
|
The current traffic matrix at side {0} cannot be supported with locked flex configuration at the side. Please unlock the corresponding site or change route of newly added demands. |
|
This demand is not allowed to pass through nodes having FLD-OSC and nodes having active Add/Drop or ROADM cards because of Automatic Laser Shutdown (ALS). |
|
Forced colorless ports can''t be greater than {0}, the number of channels supported by the optical subnet rule {1} |
|
Y-Cable protection is not allowed on Falco cards SFP and QSFP ports |
|
PSM demands are being added to/dropped from contentionless unit in interface is not allowed for this demand. |
|
Configuration not SVT tested/Unsupported: {0}. Please contact Custom Design for validation. |
|
The sum of forced CoDem and Non-CoDem colorless ports and colored demands can't be greater than 20 for type SMR-20. |
|
The sum of CoDem and Non-CoDem colorless ports, Colored Ports and ports used for Omni sides cannot exceed 16 when the TYPE is SMR-20. |
|
The sum of CoDem and Non-CoDem colorless ports, Colored Ports and ports used for Omni sides cannot exceed 8 when the TYPE is SMR-9. |
|
Traffic matrix at {0} is not supported. The maximum number of Non-CoDem colorless ports allowed is 20. |
|
Traffic matrix at {0} is not supported. The maximum number of colorless ports allowed is 96. |
|
The number of Omnidirectional and Contentionless sides at site {0} exceeds the maximum allowed number of 8. |
|
The sum of CoDem and Non-CoDem colorless ports, Colored Ports and ports used for Omnidirectional and Contentional sides cannot exceed 20 when the TYPE is SMR-20. |
|
The sum of CoDem and Non-CoDem colorless ports, Colored Ports and ports used for Omnidirectional and Contentional sides cannot exceed 9 when the TYPE is SMR-9. |
|
The Number of Omnidirectional + Contentionless sides have exceeded the capacity of the PP-Mesh, Please decrease the number of Omni or contentionless sides to a <= 9. |
|
The sum of CoDem and Non-CoDem colorless ports, Colored Ports and ports used for Omnidirectional and Contentional sides cannot exceed 20 when the TYPE is PP-MESH-AD5. |
|
The sum of forced CoDem and Non-CoDem colorless ports can't be greater than 20 when Type is forced as AUTO or SMR-20. |
|
The sum of forced CoDem and Non-CoDem colorless ports can't be greater than 9 when Type is forced as SMR-9. |
|
The sum of CoDem and Non-CoDem colorless ports and ports used for Omni sides cannot exceed 16 when the TYPE is forced as AUTO or SMR-20. |
|
The sum of CoDem and Non-CoDem colorless ports and ports used for Omni sides cannot exceed 8 when the TYPE is forced as SMR-9. |
|
The sum of CoDem and Non-CoDem colorless ports and ports used for Omnidirectional and Contentional sides cannot exceed 20 when the TYPE is SMR-20. |
|
The sum of CoDem and Non-CoDem colorless ports and ports used for Omnidirectional and Contentional sides cannot exceed 9 when the TYPE is SMR-9. |
|
The sum of CoDem and Non-CoDem colorless ports and ports used for Omnidirectional and Contentional sides cannot exceed 20 when the TYPE is PP-MESH-AD5. |
|
The Number of Omnidirectional + Contentionless sides have exceeded the capacity of the PP-Mesh with Scalable Upto Degree set to 4, Please decrease the number of Omni or contentionless sides to a <= 9 |
|
The Number of Omnidirectional + Contentionless sides have exceeded the capacity of the PP-Mesh with Scalable Upto Degree set to 8, Please decrease the number of Omni or contentionless sides to a <= 5 |
|
PP-MESH-AD5 is valid only for Scalable upto degree of 4 and 8 |
|
The CoDem Ports are supported in range of 0-4 in case of Scalable up to Degree-4, else if not Scalable upto 4 Codem colorless ports are not applicable for Omnidirectional side. |
|
The Non-Codem colorless ports is not applicable for Omnidirectional side. |
|
The CoDem Ports are supported in range of 0-4 in case of 12-AD and 0-16 in case of 16-Ad. |
|
The Non-Codem colorless ports is not applicable for Contentionless side. |
|
The CoDem Ports are supported in range of 0-4 in case of 12-AD and 0-16 in case of 16-Ad. |
|
The CoDem Ports are supported in range of 0-4 in case of Scalable up to Degree-4, else if not Scalable upto 4 Codem colorless ports are not applicable for Omnidirectional side. |
|
The 12-AD Contentionless Side Type id not supported for Terminal config. |
|
The Non-Codem colorless port are not applicable for Contentionless side. |
|
Preamplifier setting on {0} is not compatible with M2 chassis type setted on this site. |
|
FLD-OSC is not supported on the selected site type of Site{0}. FLD-OSC is allowed only on OLA/OADM/Mux-Demux Site types with passive Mux-Demux units. |
|
Booster amplifier setting on {0} is not compatible with M2 chassis type setted on this site. |
|
In {0}, OSC-CSM forcing is not compatible with OSC frame type selected. |
|
Node {0} is attached to SMR-2 site {1} through an interface tagged as Omnidirectional Entry Point and therefore no amplifier can be forced. |
|
{0} is configured as a Remote Add/Drop side and therefore no amplifier can be forced. |
|
Link {0}-{1} is a remote spur and therefore no amplifier can be forced. |
|
Link {0}-{1} is a remote spur and therefore Raman amplification is not supported. |
|
Link {0}-{1} is a remote spur and therefore DCN must be enabled. |
|
Interface {0} is configured as Omnidirectional and therefore amplifiers cannot be forced as None. |
|
Interface {0} is configured as Omnidirectional and therefore the OSC unit is not allowed. |
|
In {0} is impossible to find an OSC unit that supports selected OSC frame type and site constraints. |
|
Raman amplification is not supported on duct {0}, connecting two hybrid sites. |
|
Some circuit exceeded the maximum number of allowed amplified spans. Please contact Custom Design team for validating the design. |
|
Service type {0} does not allow DCU on its optical path. Please force related DCU positions to NONE. |
|
Omni-directional side {0} - {1} is not used by any Service Demand. |
|
Installation parameters for this side cannot be generated; please take corrective actions before loading ANS file to this node. |
|
Service type {0} does not allow DCU on its optical path. Please force related DCU positions to NONE. |
|
All available Add-Drop Amplifiers are restricted by the user. |
|
The booster amplifier forced on at {0} is incompatible with the EDRA1 |
|
Both Pre and Booster amplifiers at {0} are forced to none, hence OSC seperation can't be done. |
|
{0} has booster amplifier forced to none; Allow booster or force the OSC card. |
|
The side {0} is facing a MSTP Site and hence EDRA forcing is not allowed. Pls check the Amplifier forcings. |
|
EDRA cannot be forced on the Omni Side {0}. Please check the Amplifier Forcings. |
|
{0} has a non-EDRA amplifier while both sides of duct should have EDRA |
|
Raman Flag is enabled on duct {0}. However the amp forcings are incompatible.Please check the amplifier forcings. |
|
Only EDFA-24 and EDFA-17 compatible with 96 Channel and 48 Channel Rules. |
|
Automatic Node Turn-Up: In {0}, 32 channels cards are not supported in WXC site. |
|
Automatic Node Turn-Up: In {0}, different design rules for different spans are not supported |
|
Automatic Node Turn-Up: In {0}, Line+ node does not support the selected design rule |
|
Automatic Node Turn-Up: In {0}, multidegree node does not support the selected design rule. |
|
Automatic Node Turn-Up: In {0}, only WXC functionality is supported |
|
Automatic Node Turn-Up: In {0}, 40-MUX-C or 40-DMX-C is not supported. |
|
In {0}, cannot force a demux if it is not supported by site type. |
|
In {0}, cannot force a mux if it is not supported by site type. |
|
In {0}, cannot force an in-line attenuator if it is not supported by site type. |
|
In {0}, cannot force an in-line attenuator because of presence of OADMs in the other side. |
|
Node {0} is set as Pass-through and therefore no hardware or setpoint can be forced |
|
Forcing of Raman on {0} is not compatible with the amplifier forcing done in Node {1}. Please correct the forcings done. |
|
Selection of OPT-BST or OPT-BST-E units as pre-amplifier is allowed only if Raman is used on {0}. Please correct the forcings done. |
|
Raman Amplifier configuration for {0} is not allowed by restricted equipment list |
|
In {0}, cannot force output power or tilt setpoint without the related amplifier forced. |
|
Invalid forcing in amplifier node of {0} because of Pass-through site forcing. |
|
In {0}, cannot force unplaced OSC card in a non Pass-through site. |
|
Cannot force input attenuator in {0} without the related amplifier forced. |
|
Cannot force DCUs in {0} without forcing an amplifier that supports them. |
|
In {0}, output power is out of limits of amplifier selected. |
|
Fiber between {0} and {1} has SOL total loss greater than EOL total loss. |
|
In {0} interfaces selected for add channels cannot be equalized with 40-MUX-C. |
|
Try selecting fewer or more similar interface types, and/or do not use the 40-MUX-C card |
|
Can't respect forcing on {0} attenuator (on channel {1}) in {2} {3} {4}. No A/D ports are available |
|
Only EDFA-17/24 and EDRA cards compatible with 96Channel and 48Channel Rules |
|
Tilt forced on {0} in {1} {2} {3} when no-tilt design option is selected |
|
DMX-O is suggested as drop unit in {0} instead of the forced DMX. |
|
DMX might cause problems during channels provisioning and or in case of equipment failures. |
|
Fail low channel threshold cannot be set in {0} {1} {2}; please allow placement of booster amplifier. |
|
In {0}, {1} is working with a gain of {2} dB: this value is below its minimum allowed gain. |
|
In {0}, {1} in EOL condition will be working with a gain of {2} dB: this value is below its minimum allowed gain. |
|
In {0}, {1} is working with a gain of {2} dB: this value exceeds its maximum allowed gain. |
|
In {0}, {1} in EOL condition will be working with a gain of {2} dB: this value exceeds its maximum allowed gain. |
|
Site {0} cannot be installed without Cisco Transport Planner configuration file. |
|
Unsupported configuration due to excessive number of amplifiers (max {0} per directions). |
|
Unsupported configuration due to excessive number of OSC regen sites (max {0}). |
|
In {0}, minimum channel power is below the fail low threshold. |
|
Network cannot be installed as one or more OSC links are unfeasible. |
|
If possible, try selecting DCN extension option on the longest spans. |
|
Try to unfreeze amplifier or DCUs in site {0}, interface {1}, {2} position. |
|
Transmission error on channel {0}. Please contact custom design. |
|
Excessive ROADM crossTalk penalty on channel {0}. Try to lower the output power of the preamplifier in the ROADM site in which the failed channels are added. |
|
Excessive filtering penalty on channel {0}. Please contact custom design |
|
Filtering problem on channel {0}. Please contact custom design |
|
In site {0} the Pass Through forcing and DCN Extension option are incompatible |
|
In {0}, DCN Extension option have to be set on both fiber couples facing a Pass-Through node |
|
Automatic Node Turn-Up: node {0} mandatory requires preamplifiers (otherwise this node must be set as Pass-Through). |
|
Automatic Node Turn-Up: In {0}, amplifier output power cannot be forced. |
|
Automatic Node Turn-Up: In {0}, Fiber Switch protection scheme is not supported. |
|
Automatic Node Turn-Up: In {0}, only “32 Chs +5 dbm/Ch” and “40 Chs +4 dbm/Ch” design rules are supported. |
|
Automatic Node Turn-Up: In {0}, only “32 Chs +5 dbm/Ch” design rule is supported. |
|
Automatic Node Turn-Up: In {0}, C + L band upgradeability is not supported. |
|
Automatic Node Turn-Up: In {0}, OADM output power cannot be forced. |
|
Automatic Node Turn-Up: node {0} cannot be set as OADM full mux/demux. |
|
In {0}, with SMR 9/20 units cannot force the "Attenuator OUT" Pre amplifier. |
|
In {0}, with SMR 9/20 unit cannot force the "Attenuator IN" Booster amplifier. |
|
Flex SMR cards have pre and booster amps and hence can't have other pre/bst amp forcings. |
|
Couple {0} has Raman enabled on the duct but corresponding Raman Forcing is missing. |
|
Site {0} Dithering value cannot be less than Lower Dithering limit {1} |
|
Site {0} Dithering value cannot be greater than Upper Dithering limit {1} |
|
Number of available Dithering values {0} cannot be less than number of MultiDegree sites {1} |
|
The AC2 power module is not supported by M2 chassis in Site {0}, hence AC power module is being used. |
|
Shelves in site {0} exceeds maximum number of supported Shelves({1}) by a huge number. Layout is not built for the site. |
|
Unit in the Rack {0} - Shelf {1} for site {2} requires FAN TRAY 4. |
|
Maximum number of shelves for site {0} crosses the maximum allowed limit of {1}. |
|
The placement for cards in the site {0} and side {1} having the SMR2 Omnidirectional configuration might have discrepancies. Please verify. |
|
The network has osmine enabled nodes but the release does not support Osmine Configurations. Please upgrade to an Osmine compatable release. |
|
Layout for Site {0} has incompatible Y-cable/100G/Others which conflict Bay Layout Forcing. Please go back to design or upgrade mode, unlock layout for the associated site. |
|
Layout for Site {0} has incompatible forcings - M12 forced as chassis type and 100G Cards. Please force Chassis type as Auto. Also, Check for other sites in the network for similar forcing. |
|
Layout for Site {0} has incompatible forcings - M2 forced as chassis type and 100G Combination Cards like Fumailo or Carpegna. Please force Chassis type as Auto. Also, Check for other sites in the network for similar forcing. |
|
Power Exceeded the max limit of shelf with id {0} in Site {1}. Please move cards from this shelf. |
|
{0} layout cannot be built as M6 and M2 chassis are restricted. Required 100G cards can be placed only in M6 and M2 chassis. |
|
Chassis has insufficient power to support 100G cards with Y-cable at site {0}. |
|
{0} layout cannot be built as M6 chassis is restricted. Required 100G cards can be placed only in M6 chassis. |
|
MSTP shelves number in site {0} exceeds maximum MultiShelf configuration ({1}). |
|
Layout not feasible for {0} Individual Shelf configuration - No room in the optical shelf to host all the OTS units |
|
Hybrid Layout in Site {0} is allowed with Individual Shelf only |
|
Node protection in Site {0} is not allowed with Individual Shelf |
|
Site {0} layout must be unlocked to allow Patch Panel/DCU insertion |
|
Layout in site {0} cannot be built due an internal error. Other reports for the same site may be wrong or incomplete. Please contact support. |
|
{0} site layout must be unlocked to apply modified properties |
|
A/D cards configuration in site {0} is not allowed: please select “Multi Shelf External Switch” or force 32-DMX card |
|
Units equipped in site {0} shelf {1} need FTA4. Please replace current fan tray before equipping the units into the shelf |
|
Card in Rack {0} - Shelf {1} - Slot {2} cannot be moved to Rack {3} - Shelf {4} - Slot {5} (Site {6}) |
|
Just one move is allowed for Card in Rack {0} - Shelf {1} - Slot {2} (Site {3}) |
|
Cards in Rack {0} - Shelf {1} - Slot {2} and Rack {3} - Shelf {4} - Slot {5} (Site {6}) belong to a YCable Protection Group and must be moved to the same destination shelf |
|
Multidegree topology in site {0} is not supported with Individual Shelf configuration |
|
Y cable protection with GE XP / 10GEXP / GE EXP / 10GE EXP traffic demand in site {0} is not supported with Osmine Configuration |
|
Y cable protection with GE XP / 10GEXP traffic demand in site {0} is not supported with Osmine Configuration |
|
Network not managed by Osmine: Site {0} with WXC and WSS is not admitted. |
|
Layout not feasible for {0} M2 Shelf cannot go in MSM Configuration. |
|
Layout not feasible for {0},M2 chassis is in Restricted List and is forced. |
|
Layout not feasible for {0},M6 chassis is in Restricted List and is forced. |
|
Layout not feasible for {0},M12 chassis is in Restricted List and is forced. |
|
Layout not feasible M12 chassis and M6 Chassis are in Restricted List. |
|
In Site: {0} and Side: {1} with the current configuration, M6 chassis has been forced, either due to Chassis type forcing of GE frame forcing, whereas M12 chassis is the suggested option. |
|
Layout not feasible for Site: {0} and Side: {1},M6 is not supported for the site configuration and M12 Chassis is in Restricted Equipment List. |
|
Extra M2 Shelf cannot go in MSM Configuration for site {0}, hence ignoring additional M2 chassis. |
|
MSM External Configuration for site {0} and M6 Forced, M6 Chassis has integrated MSM capability. |
|
OSC frame type is forced to GE for site {0} and Interface {1}, Power is not sufficient with the available GE Module. |
|
Layout not feasible for {0},Single Controller card doesn't support MSM. |
|
The forced {0} is not compatible with the {1} forced for the {2}. |
|
M2 Chassis cannot have more than one neighbour with ONS 15454 chassis forced. |
|
When M2 chassis is forced, all the connected ducts with only one exception, should have couples forced with valid OSC Frames. |
|
The frame forcings across {0} are not compatible because the site is a passthrough site. The current values will be ignored and best defaults would be chosen. |
|
The OSC frame forcing in the couples connecting the PSM Line {0} need to be same. |
|
The {0} is a OSC regen site hence the connected couples should not have GE frame type forced. |
|
The {0} has OSC-CSM forced which is not compatible with GE frame forcing on the couple in {1}. |
|
The {0} has WSS card with DMX and M2 forced which is not compatible. Analysis not feasable. |
|
MSTP shelves number in site {0} exceeds maximum MultiShelf configuration ({1}). |
|
Racks in site {0} exceeds maximum number of supported Racks({1}). Layout is not built for the site. |
|
Layout not feasible for {0} Individual Shelf configuration - No room in the optical shelf to host all the OTS units. |
|
Hybrid Layout in Site {0} is allowed with Individual Shelf only. |
|
Node protection is not allowed in PSM Line/Section Site {0}. |
|
DCC Chain in Site {0} is allowed with Individual Shelf only. |
|
Node protection in Site {0} is not allowed with Individual Shelf. |
|
Node protection in Site {0} is not allowed without ADD/DROP. |
|
Site {0} layout must be unlocked to allow Patch Panel/DCU insertion. |
|
Layout in site {0} cannot be built due an internal error. Other reports for the same site may be wrong or incomplete. Please contact support. |
|
{0} site layout must be unlocked to apply modified properties. |
|
A/D cards configuration in site {0} is not allowed: please select “Multi Shelf External Switch” or force 32-DMX card. |
|
Units equipped in site {0} shelf {1} need FTA4. Please replace current fan tray before equipping the units into the shelf. |
|
Card in Rack {0} - Shelf {1} - Slot {2} cannot be moved to Rack {3} - Shelf {4} - Slot {5} (Site {6}). |
|
Multidegree topology in site {0} is not supported with Individual Shelf configuration. |
|
Invalid Alien Shelf Height for site {0}, Alien Shelves Could not be added. |
|
Alien Shelf Height is more than Rack Height for site {0}, Alien Shelves Could not be added. |
|
Unit in the Rack {0} - Shelf {1} - Slot {2} for site {3} requires FAN TRAY 4. |
|
SMR2 in Separate Shelf is not Feasible for Site {0} due to cable unavailable with appropriate length. |
|
Layout not feasible for {0} M2 Shelf cannot go in MSM Configuration. |
|
The interface {0} has Raman CTP forced with M12 chassis. This is not compatible. |
|
The interface {0} has Raman CTP, which needs high power cables to connect, Only cables of length 2m are bundled with the card. |
|
Raman-CTP or Raman-COP cards forced with M12 chassis in the interface {0} is not a supported configuration. |
|
Raman-CTP or Raman-COP cards forced with M2 chassis in the interface {0} is not a supported configuration. |
|
Raman-CTP or Raman-COP cards placed in {0} because M6 chassis is restricted. |
|
Raman-CTP or Raman-COP cards placed in M12 chassis in the interface {0} is not a supported configuration. |
|
The Site {0} has TCC 2p as node controller. So it cannot subtend M6/M2 Shelves. |
|
Some of the passive devices in the site {0} has unit id greater than the allowed range 1. 126. Change the unit id's by double clicking on the passive device. |
|
The length of MPO-MPO cables may not be sufficient for Separated Shelf configurations in NGDWDM Network |
|
OSC frame type is forced to GE for site {0} and Interface {1},Edra is not compatible with GE Module. |
|
Layout not feasible for {0} as chassistype forced to M2 or M12 for a flex node. |
|
Layout not feasible for {0} as Extrachassis is forced for M2 or M12 for a flex node. |
|
Layout not feasible for {0} as nodeController Type forced to M12 for a flex node. |
|
The configuration requires M12 chassis to be placed. Either force M12 as chassis type or force OSC to proceed. |
|
Layout for site {0} has incompatible forcings - WXC16/EDRA cards will not be supported on chassis with old fan tray. Change the fan tray forcings at the site. |
|
Layout not feasible for {0},M15 chassis is in Restricted List and is forced. |
|
Layout not feasible M15 chassis and M6 Chassis are in Restricted List. |
|
Extra M15 Shelf cannot be added for site {0}, M15 chassis is Restricted. |
|
Layout not feasible for {0} as chassis type forced to M15 for a MSTP site. |
|
{0} layout cannot be built as M6 and M15 chassis are restricted. Required 100G/WSE cards can be placed only in M6 and M15 chassis. |
|
{0} layout cannot be built as M6 chassis and M15 chassis are restricted. Required 100G cards can be placed either in M6 chassis or M15 chassis. |
|
Layout for site {0} has incompatible forcing’s - SMR9/SMR20 cards will not be supported on chassis with old fan tray. Change the fan tray forcing at the site. |
|
{0} not supported with M15 Chassis for {1}. Please force M15 Chassis specific Fan Tray. |
|
Force either Gain Equality or Line Amplifier as site functionality when M2 is forced. |
|
M15 cannot be forced as the node controller of M6 Chassis. Unsupported config for R10.5. Please contact custom design team for validating the design {0}. |
|
M15 with ROADMs 80-WXC/SMR1/SMR2 in MSTP {0} is not a supported configuration. |
|
{0} card forced in {1} is untested card in M15 for R10.5. Please contact custom design team for validating the design. |
|
In {0}, can’t force a demux if it is not supported by site type. |
|
In {0}, can’t force an inline attenuator if it is not supported by site type. |
|
In {0}, can’t force an inline attenuator because of presence of OADMs in the other side. |
|
Invalid forcing in amplifier node of {0} because of Pass-through site forcing. |
|
In {0}, can’t force unplaced OSC card in a non Pass-through site. |
|
Can’t force power output or tilt in {0} without the related amplifier forced. |
|
Cannot force input attenuator in {1} without the related amplifier forced. |
|
Can’t force DCUs in {0} without forcing an amplifier that supports them. See the “Incompatible DCUs (C-Band)” section. |
|
Incompatible types for DCU couple in {0}. See the “Incompatible DCUs (C-Band)” section. |
|
Incompatible dispersion modules in {0}. See the “Incompatible DCUs (C-Band)” section. |
|
In {0}, MMU presence requires OPT-AMP-L forcing in bst and pre position. See the “MMU Does Not Have Correct Amplifier (L-Band)” section. |
|
In {0}, MMU presence requires OPT-PRE and OPT-BST-E forcing. See the “MMU Does Not Have Correct Amplifier (C-Band)” section. |
|
In {0}, output power setting is not supported by the amplifier. See the “Output Power or Tilt are Out of Range” section. |
|
In {0}, amplifier tilt is out of limits. See the “Output Power or Tilt are Out of Range” section. |
|
Couple between {1} and {2} has an invalid value in {0}. See the “Invalid Fiber Values, Types, and Loss Values” section. |
|
Couple between {0} and {1} is of invalid type. See the “Invalid Fiber Values, Types, and Loss Values” section. |
|
Fiber between {1} and {2} has an invalid value in {0}. See the “Invalid Fiber Values, Types, and Loss Values” section. |
|
Fiber between {0} and {1} has SOL total loss greater than EOL total loss. See the “Invalid Fiber Values, Types, and Loss Values” section. |
|
A {0} attenuator (on channel {1}) in {2} {3} {4} was present, but A/D ports on this channel are no longer available. See the “Unavailable Add/Drop Channels” section. |
|
Tilt forced on {0} in {1} {2} {3} when no-tilt design option is selected. See the “Tilt Forced When No Tilt Design Is Selected” section. |
|
Can’t change DMX with DMX-O as needed in {1} because user forcing. See the “Cannot Replace 32-DMX with 32DMX-O” section. |
|
Low threshold on channels power in {0} {1} {2} because passive user forcing on OPT-BST position. |
|
In {0}, {1} is working in an invalid mode. See the “Preamplifier Working in Invalid Mode” section. |
|
In {0}, {1} is working with a gain of {2} dBm: this is too low. See the “Gain Too Low for an Amplifier” section. |
|
In {0}, {1} will be work (in EOL condition) with a gain of {2} dBm: this is too low. See the “Gain Too Low for an Amplifier” section. |
|
In {0}, {1} is working with a gain of {2} dBm: this is too high. See the “Gain Too High for an Amplifier” section. |
|
In {0}, {1} will be work (in EOL condition) with a gain of {2} dBm: this is too high. See the “Gain Too High for an Amplifier” section. |
|
In {0}, {1} cannot respect user forcing. See the “User Forcing Overridden” section. |
|
In {0}, {1} cannot respect user forcing due to {2}. See the “User Forcing Overridden” section. |
|
Unsupported configuration due to excessive number of amplifiers (max {0} per directions). See the “Unsupported Configuration” section. |
|
Unsupported configuration due to excessive number of OSC regen sites (max {0}). See the “Unsupported Configuration” section. |
|
In {0}, channel power is near the fail threshold. See the “Channel Power Near the Fail Threshold” section. |
|
In {0}, channel power is below the fail threshold. See the “Channel Power Below the Fail Threshold” section. |
|
In {0}, OSC channel power is near the fail threshold. See the “Channel Power Near the Fail Threshold” section. |
|
In {0}, OSC channel power is below the fail threshold. See the “OSC Channel Power Below the Fail Threshold” section. |
|
Network unfeasible due to OSC channel. See the “OSC Channel Power Below the Fail Threshold” section. |
|
Try to unfreeze amplifier or dcus in site {0}, interface {1}, {2} position |
|
Transmission error on channel {0}. Please contact custom design. |
|
Excessive ROADM crossTalk penalty on channel {0}. Try to lower the output power of the preamplifier in the Roadm site in which the failed channels are added. |
|
Excessive filtering penalty on channel {0}. Please contact custom design. |
|
Filtering problem on channel {0}. Please contact custom design. |
|
One or more demands present unexpected results at the end of the analysis. Refer to channels errored on system. |
|
Node {0} is set as Pass-Through and therefore no hardware or setpoint can be forced |
|
Forcing of tilt in {0} is not allowed in case of Raman amplified span |
|
Forcing of Raman ({0}) is not allowed in PSM Topology. Please correct the forcings done. |
|
In {0} Raman embedded amplifier has dispersion modules with MAL greater then supported |
|
In {0} Raman post amplifier has total dispersion modules with MAL greater then supported |
|
Network analysis must be validated. Please contact custom design. |
|
In network with PSM-Line protection and different fiber types, DCU placement must be validated. |
|
Site {0} connected to duct with DCN extension property enabled must have functionality Add/Drop. |
|
Couple under duct {0} must have DCN extension property disabled |
|
In site {0} between fibers DCN extension, no OSC and no Booster are allowed |
|
In Add/Drop site {0}, OSC cannot be forced since the facing fiber has DCN extension enabled |
|
In Add/Drop site {0} facing a fiber with DCN extension enabled, Booster cannot be forced as None |
|
The DCN path from {0} to {1} contains too many Line Amplifier sites |
|
In interfaces tagged as Omnidirectional Entry Point is not allowed set Mux or Demux |
|
In interfaces tagged as Omnidirectional Entry Point a Terminal site must be connected |
|
Node {0} refers to an interface tagged as Omnidirectional Entry Point and therefore no amplifier can be forced |
|
Node {0} refers to an interface tagged as Omnidirectional Entry Point and therefore no OSC card can be forced |
|
Forcing of amplifier in {0} is not allowed in case of Raman amplified span. |
|
Node {0} faces a raman amplified span, only OPT-BST unit can be forced. |
|
Span {0} must be configured as Raman to allow Raman amplifier {1} in node {2}. |
|
Forcing of Raman on {0} is not compatible with the amplifier forcing done in Node {1}. Please correct the forcings done. |
|
Selection of OPT-BST or OPT-BST-E units as pre-amplifier is allowed only if Raman is used on {0}. Please correct the forcings done. |
|
Raman Amplifier configuration for {0} is not allowed by restricted equipment list. |
|
Node {0} faces a raman amplified span, only OPT-BST unit can be forced. |
|
Span {0} must be configured as Raman to allow Raman amplifier {1} in node {2}. |
|
Forcing of Raman on {0} is not compatible with the amplifier forcing done in Node {1}. Please correct the forcings done. |
|
Selection of OPT-BST or OPT-BST-E units as pre-amplifier is allowed only if Raman is used on {0}. Please correct the forcings done. |
|
Raman Amplifier configuration for {0} is not allowed by restricted equipment list. |
|
In {0} is not allowed forcing a booster or setting DCN extension enabled. |
|
In Add/Drop site {0} facing a fiber with DCN extension enable, OSC cannot be forced |
|
Site {0} is facing spans with different optical design rules: an Add/Drop functionality is required. |
|
{0} is an hybrid 15454 MSTP site : selection of OPT-BST or OPT-BST-E units as pre-amplifiers is not allowed. |
|
Span is too short for Raman amplification. If possible, lower the output power setpoint of the booster. |
|
In {0} is not allowed forcing a pre-amplifier or setting DCN extension enabled. |
|
In {0}, cannot force OSCM card without an amplifier or SMR forced. |
|
Forcing of T-DCU on both {0} is not allowed.Please remove T-DCU forcing either from {1}. |
|
{0} - side{1} is connected to a span not used by any Service Demand. |
|
In multidegree site {0} configured as SMR2 type with Individual Shelf, only first two sides can have OSC-CSM unit forcing. |
|
{0} has OSC functionality : side {1} can’t face a fiber with DCN extension enabled. |
|
Raman amplification is not supported on duct {0}, connecting two hybrid sites. |
|
Some circuit exceeded the maximum number of allowed amplified spans. Please contact Custom Design team for validating the design. |
|
In {0} the amplifier {1} doesn’t support DCU modules: please unlock or reset to Auto any related DCU. |
|
In {0}, DFB power fail is near the minimum allowed threshold. |
|
In {0}, DFB power fail is below the minimum allowed threshold. |
|
Duct {0} is connecting two hybrid sites: Raman amplification is not supported. |
|
Some circuit exceeded the maximum number of allowed amplified spans. Please contact Custom Design team for validation of the design. |
|
The Raman amplifier at {0} is not compatible with the Raman amplifier at the other end of the line |
|
The Raman amplifier at {0} requires an equalization unit (e.g. SMR, WSS or WXC) |
|
The Raman amplifier at {0} requires DCN extension on the facing fiber |
|
Some circuits are traversing {0} RAMAN-CTP amplified spans (max {1} allowed) |
|
Some circuits are traversing {0} RAMAN-COP + RAMAN-CTP amplified spans (max {1} allowed) |
|
Duct {0} is a Raman amplified span using RAMAN-COP: all circuits must be terminated in {1} and {2} |
|
MSTP shelves number in site {0} exceeds maximum MultiShelf configuration (12). |
|
Layout not feasible for {0} Individual Shelf configuration - No room in the optical shelf to host all the OTS units. |
|
Hybrid Layout in Site {0} is allowed with Individual Shelf only. |
|
DCC Chain in Site {0} is allowed with Individual Shelf only. |
|
Node protection in Site {0} is not allowed with Individual Shelf. |
|
Site {0} layout must be unlocked to allow Patch Panel/DCU insertion. |
|
Layout in site {0} cannot be built due an internal error. Other reports for the same site may be wrong or incomplete. Please contact support. |
|
Y cable protection with GE XP / 10GEXP traffic demand in site {0} is not supported with Osmine Configuration |
|
Network not managed by Osmine: Site {0} with WXC and WSS is not admitted. |
|
Invalid Alien Shelf Height for site {0}, Alien Shelves Could not be added. |
|
Alien Shelf Height is more than Rack Height for site {0}, Alien Shelves Could not be added. |
|
SMR with Raman Amplification is Not Supported on Side {0} for Site {1}. |
|
SMR2 in Separate Shelf is not Feasible for Site {0} due to cable unavailable with appropriate length. |
|
At least one optical bypass point is defined in this site. The site can not be deleted until the optical bypass is removed. |
|
Fiber Bragg DCU on {0} is incompatible with the client card. |
|
Fiber Bragg DCU on {0} is incompatible with the trunk pluggable. |
|
FBGDCU option is set to Always at the project level and channel spacing is 50 Ghz for {0}. |
|
No free port found to connect {0} to {1} in Side {2}. Please unlock the site or change the route of the demands. |
1.2 Warning Messages
Warning Messages for Cisco Transport Planner are listed in Table 1-2 :
|
|
|
|---|---|
In {0}, add/drop input power must be modified from {2} to {1}. |
|
Please turn ON the Automatic Laser Shutdown (ALS) on the TXPs having the wavelength {0} on sites Site{0} and Site{0} for Optical protection. |
|
In {0}, minimum channel power for port {1} of {2} is below the fail low threshold. |
|
In {0}, minimum channel power for port {1} of {2} is near the fail low threshold. |
|
Can’t respect forcing on {0} attenuator (on channel {1}) in {2} {3} {4}. No A/D ports are available. See the “Attenuator Forcing Not Allowed” section. |
|
In {0}, minimum channel power is near the fail low threshold |
|
In {0}, 32-DMX might have problem as drop unit. If supported by node type try 32-DMX-O. |
|
32-DMX might cause problems during channels provisioning and/or in case of equipment failure. |
|
40-DMX might cause problems during channels provisioning and/or in case of equipment failure. |
|
PSM switching threshold on port {0}-RX {1} is close to minimum channel power |
|
PSM switching on port {0}-RX {1} might not be completely reliable |
|
PSM switching on port {0}-RX is based on EDFA safety shutdown procedure and might be longer than 50 ms |
|
PSM unit might not correctly switch on port {0}-RX in case of fiber cut |
|
OPT-RAMP-C on {0} side is facing a span with an excessive loss. |
|
OPT-RAMP-CE on {0} side is facing a span with an excessive loss. |
|
Forcing of T-DCU on {0} in L-Band network is not allowed.Please check the TDCU forcing in Options Explorer. |
|
In {0}, MMU mandatory requires OPT-PRE and OPT-BST-E. Please remove any other amplifier type forcing |
|
In {0} an external DCN access must be provided for DCN functionality |
|
A {0} attenuator (on channel {1}) in {2} {3} {4} was present, but A/D ports on this channel are longer available |
|
In {0}, control mode of {3} amplifier must be modified from {2} to {1} |
|
Output tilt is forced on {0} in {1} {2} {3} but no-tilt design option is selected |
|
In {0}, MMU mandatory requires OPT-AMP-L in booster and pre position. Please remove any other amplifier type forcing |
|
In {0}, RX amplifier power fail threshold must be modified from {2} to {1} |
|
In {0}, TX amplifier power fail threshold must be modified from {2} to {1} |
|
In {0}, channel LOS threshold must be modified from {2} to {1}. |
|
In {0}, minimum expected span loss must be modified from {2} to {1} |
|
In {0}, maximum expected span loss must be modified from {2} to {1} |
|
In {0}, band drop power at {3} must be modified from {2} to {1} |
|
In {0}, channel drop power at {3} must be modified from {2} to {1} |
|
In {0}, 32-DMX might have problem as drop unit. If supported by node type try 32-DMX-O |
|
32-DMX might cause problems during channels provisioning and/or in case of equipment failure |
|
40-DMX might cause problems during channels provisioning and/or in case of equipment failure |
|
In case of fiber cut or equipment failure, channels survivability might not be guaranteed |
|
In {0}, {1} cannot respect user forcing. See User Forcing Overridden. |
|
The forced setpoint/item has been overwritten by CTP with a feasible value. |
|
The forced setpoint/item has been overwritten by CTP with a feasible value. |
|
Between nodes {0} and {1}, {2} gain equalizer node(s) is (are) suggested for an optimal design |
|
Excessively long chains of OLA nodes (>{0}) might cause problems in LOS detection at receivers in case of channels failure. |
|
In {0}, 32-DMX-O is suggested as drop unit in instead of the forced 32-DMX. |
|
32-DMX might cause problems during channels provisioning and/or in case of equipment failure. |
|
Osmine configuration in site {0} is not supported with L-Band |
|
Hybrid Site Config in a Single-Shelf configuration is only supported for an OADM Site Type |
|
Osmine configuration in site {0} is not supported with L-Band. |
|
Forced M12 Chassis is not compatible with FLD-OSC. Please force M6 Chassis to complete the analysis. |
|
M6 Chassis is restricted. Unforce FLD-OSC to complete the analysis or force Individual Shelf management. |
|
M6 Chassis and M2 Chassis are restricted. Unforce FLD-OSC to complete the analysis or remove M6 Chassis or M2 Chassis from restricted list. |
|
Hybrid Site Config in a Single-Shelf configuration is only supported for an OADM Site Type |
|
Unit in the Rack {0} - Shelf {1} - Slot {2} for site {3} requires FAN TRAY 4. |
|
Extra M6 Shelf cannot be added for site {0}, M6 chassis is Restricted. |
|
Extra M12 Shelf cannot be added for site {0}, M12 chassis is Restricted. |
|
M6 Chassis with integrated MSM capability, is forced in {0} with MSM External Switch. This adds extra to BOM. |
|
Requested number of extra shelves could not be added due to MSM configuration restrictions. Please check the layout for details. |
|
TNC pluggable {0} forced with ONS 15454 chassis in {1}, hence ignoring pluggable forcing. |
|
The chassis type set to M6 due to the forcing of OSC Pluggables at {0}. |
|
Auto Option for Shelf Management is assigned Single Shelf Configuration by the algorithm as Site {0} is a non add drop site. |
|
Osmine configuration in site {0} is not supported with L-Band. |
|
Network not managed by Osmine: Site {0} with WXC and WSS is not admitted. |
|
Hybrid Site Config in a Single-Shelf configuration is only supported for an OADM Site Type. |
|
If traffic subnet will be deleted, this traffic will be unlocked and if it requires a specific traffic subnet topology, it will not be editable until it will associated to another traffic subnet. |
|
This traffic cannot be edited. It needs to be associated to a valid traffic subnet. |
|
Fiber Bragg DCU is forced on {0} with traffic generating out of it expressing through non-OLA/PT site {1}. |
1.3 Information Messages
Information Messages for Cisco Transport Planner are listed in Table 1-3 :
1.4 Traffic Mapping Troubleshooting
The following procedures help you resolve traffic mapping problems with the network design.
1.4.1 Wavelength Exceeded
Symptom Cisco Transport Planner warns you that all network analysis solutions exceed the wavelengths.
Table 1-4 describes the potential causes of the symptom and the solution.
1.4.2 Invalid Routing
Symptom Cisco Transport Planner warns you of invalid routing (out of network boundary).
Table 1-5 describes the potential causes of the symptom and the solution.
1.4.3 Cannot Find Alternate Route
Symptom Cisco Transport Planner warns you that it cannot find an alternate route due to multiple hub nodes along the path.
Table 1-6 describes the potential causes of the symptom and the solution.
1.4.4 Cannot Route Service
Symptom Cisco Transport Planner warns you that it cannot route service through a hub node.
Table 1-7 describes the potential causes of the symptom and the solution.
1.4.5 Overlapped Services Assigned to the Same Wavelength
Symptom Cisco Transport Planner warns you that overlapped services are assigned to the same wavelength.
Table 1-8 describes the potential causes of the symptom and the solution.
1.4.6 Protected Services Assigned to the Same Wavelength
Symptom Cisco Transport Planner warns you that protected services are assigned to the same wavelength.
Table 1-9 describes the potential causes of the symptom and the solution.
1.4.7 Cannot Route Service Because of Add/Drop Constraints
Symptom Cisco Transport Planner warns you that it cannot route service because of add/drop equipment constraints.
Table 1-10 describes the potential causes of the symptom and the solution.
1.4.8 Design Requires a ROADM or Full Mux/Demux Site
Symptom Cisco Transport Planner warns you that the design requires a ROADM or full multiplexer/demultiplexer site, but no valid site was found.
Table 1-11 describes the potential causes of the symptom and the solution.
1.5 Amplifier Troubleshooting
The following procedures help you resolve amplifier-related problems with the network design.
1.5.1 Incompatible DCUs (C-Band)
Symptom Cisco Transport Planner warns you that DCUs are incompatible.
Table 1-12 describes the potential causes of the symptom and the solution.
1.5.2 MMU Does Not Have Correct Amplifier (L-Band)
Symptom Cisco Transport Planner warns you that an L-band node with an MMU requires that the OPT-AMP-L card is forced as the preamplifier (PRE) and booster amplifier (BST).
Table 1-13 describes the potential causes of the symptom and the solution.
1.5.3 MMU Does Not Have Correct Amplifier (C-Band)
Symptom Cisco Transport Planner warns you that a C-band node with an MMU requires both a preamplifier (OPT-PRE) and a booster (OPT-BST).
Table 1-14 describes the potential causes of the symptom and the solution.
1.5.4 Output Power or Tilt are Out of Range
Symptom Cisco Transport Planner warns you that the output power or tilt are out of range for the amplifier selected.
Table 1-15 describes the potential causes of the symptom and the solution.
1.5.5 Invalid Fiber Values, Types, and Loss Values
Symptom Cisco Transport Planner warns you of one of the following:
Table 1-16 describes the potential causes of the symptom and the solution.
1.5.6 Attenuator Forcing Not Allowed
Symptom Cisco Transport Planner warns you that attenuator forcing on channels is not allowed; no add/drop ports are available.
Table 1-17 describes the potential causes of the symptom and the solution.
1.5.7 Unavailable Add/Drop Channels
Symptom Cisco Transport Planner warns you that an attenuator was present, but add/drop channels are no longer available.
Table 1-18 describes the potential causes of the symptom and the solution.
1.5.8 Tilt Forced When No Tilt Design Is Selected
Symptom Cisco Transport Planner warns you that tilt is forced for an amplifier although No Tilt Design was selected for the network.
Table 1-19 describes the potential causes of the symptom and the solution.
1.5.9 Cannot Replace 32-DMX with 32DMX-O
Symptom Cisco Transport Planner warns you that 32-DMX cannot be replaced with 32DMX-O as needed because of user forcing.
Table 1-20 describes the potential causes of the symptom and the solution.
1.5.10 Preamplifier Working in Invalid Mode
Symptom Cisco Transport Planner warns you that a preamplifier is working in an invalid mode.
Table 1-21 describes the potential causes of the symptom and the solution.
1.5.11 Gain Too Low for an Amplifier
Symptom Cisco Transport Planner warns you that an amplifier is working with a gain that is too low.
Table 1-22 describes the potential causes of the symptom and the solution.
1.5.12 Gain Too High for an Amplifier
Symptom Cisco Transport Planner warns you that an amplifier is working with a gain that is too high.
Table 1-23 describes the potential causes of the symptom and the solution.
1.5.13 User Forcing Overridden
Symptom Cisco Transport Planner warns you that user forcing will not be allowed.
Note This is a warning and does not prevent the network from being fully functional. The message is displayed in situations where a forcing configured by the user cannot be respected due to physical constraints since the problem may appear only after several calculation steps. The algorithm notifies the user and ignores the setting to avoid interrupting the analysis.
Table 1-24 describes the potential causes of the symptom and the solution.
Note In the upgrade mode, Cisco Transport Planner remembers all the parameters from last analysis and not from its parent network. A warning with respect to the installation parameters is displayed only when there is a difference between the new values and the values from previous analysis.For example: Create a network design and analyse it. Upgrade the network design and modify some spans. Analyse the upgraded network. A warning message is displayed since some of the installation parameters have changed. Re-analyse the network with making modifications. The warning is no longer displayed since none of the installation parameters have changed. You can create a diff report to identify all the modified installation parameters.
1.5.14 Unsupported Configuration
Symptom Cisco Transport Planner warns you that the configuration is unsupported because of an excessive number of amplifiers or OSC regeneration sites.
Table 1-25 describes the potential causes of the symptom and the solution.
1.5.15 Channel Power Near the Fail Threshold
Symptom Cisco Transport Planner warns you that the channel power is near the fail threshold.
Table 1-26 describes the potential causes of the symptom and the solution.
1.5.16 Channel Power Below the Fail Threshold
Symptom Cisco Transport Planner warns you that the channel power is below the fail threshold.
Table 1-27 describes the potential causes of the symptom and the solution.
1.5.17 OSC Channel Power Below the Fail Threshold
Symptom Cisco Transport Planner warns you that the OSC channel power is below the fail threshold and that the network is not feasible.
Table 1-28 describes the potential causes of the symptom and the solution.
Feedback