Possible Problem

Solution

A span in the ring must carry more than 32 wavelengths to implement the traffic demands.

Remove the forced path routing on unprotected channels:

1. In the Project Explorer pane under the Service Demands folder, right-click the appropriate demand and choose Edit from the shortcut menu.
2. In the Path column, choose Auto from the drop-down list.
3. Re-analyze the network.

A span in the ring must carry more than 16/8 wavelengths.

Change the traffic mapping design rules under the related subnet and choose an option that allows a greater number of channels:

1. In the Project Explorer pane under the Subnets folder, expand Traffic Mapping and click System Release.
2. In the Properties pane, choose the new rules option from the C-Band Rules or L-Band Rules drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

In a linear network, the direction of each service demand is restricted by the topology but the user applied an unfeasible direction forcing.

Remove the forced path routing:

1. In the Project Explorer pane under the Service Demands folder, right-click the appropriate demand and choose Edit from the shortcut menu.
2. In the Path column of the Edit <demand> dialog box, choose Auto from the drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

Because a hub node does not allow express channels, if multiple hub nodes are present, not all point-to-point connections are possible.

Remove the hub functionality constraints:

1. In the Project Explorer pane under the Sites folder, click C-Band or L-Band for the appropriate site.
2. In the Properties pane, choose Auto from the Functionality drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

Since a hub node does not allow express channels, not all service routes are possible.

Remove the path routing forcing or the hub functionality constraints.

To remove the path routing forcing:

1. In the Project Explorer pane under the Service Demands folder, right-click the appropriate demand and choose Edit from the shortcut menu.
2. In the Path column of the Edit <demand> dialog box, choose Auto from the drop-down list.
3. Re-analyze the network.

To remove the hub functionality constraints:

1. In the Project Explorer pane under the Sites folder, click C-Band or L-Band for the appropriate site.
2. In the Properties pane, choose Auto from the Functionality drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

Some unprotected channels with assigned wavelengths and directions overlap along the ring.

Remove path routing forcing and/or wavelengths on the specific channels.

To remove the path routing forcing:

1. In the Project Explorer pane under the Service Demands folder, right-click the appropriate demand and choose Edit from the shortcut menu.
2. In the Path column of the Edit <demand> dialog box, choose Auto from the drop-down list.
3. Re-analyze the network.

To remove the wavelength forcing:

1. In the Project Explorer pane under the Service Demands folder, right-click the appropriate demand and choose Edit from the shortcut menu.
2. In the Wavelength column of the Edit <demand> dialog box, choose Auto from the drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

In ring networks, each protected/P-ring request allocates one wavelength. If more than one protected service is forced on the same wavelength and aggregation is not possible, the network is not feasible.

Remove forced wavelengths on the specific channels:

1. In the Project Explorer pane under the Service Demands folder, right-click the appropriate demand and choose Edit from the shortcut menu.
2. In the Wavelength column of the Edit <demand> dialog box, choose Auto from the drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

Add/drop equipment forcing might prevent express channels in a node, which makes unfeasible some channel routes.

Remove add/drop equipment constraints.

1. In the Project Explorer pane under the Sites folder, click C-Band or L-Band for the appropriate site.
2. In the Properties pane, choose Auto from the Functionality drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

The traffic mapping algorithm might not be able to find a valid solution that respects both the user forcing and the system specifications (in terms of maximum site losses and layout constraints). In such cases, the only possible countermeasure for the algorithm is to upgrade one node to a full capacity node (ROADM or full Mux/Demux). If no valid node is found due to user forcing or equipment locking, the process stops and the network is unfeasible.

Remove any forcing/locking that prevents at least one node from being upgraded to ROADM or full multiplexer/demultiplexer. Conditions that prevent upgrading a node to ROADM or full multiplexer/demultiplexer are:

• Site functionality is forced to Add/Drop and site type is forced to OADM
• During an upgrade procedure, OADM equipment is locked it the site

To change site functionality and type forcing:

1. In the Project Explorer pane under the Sites folder, click C-Band or L-Band for the appropriate site.
2. In the Properties pane, choose Auto from the Functionality drop-down list.
3. Choose Auto from the Type drop-down list.
4. Re-analyze the network.

To unlock OADM equipment:

1. In the Project Explorer pane under the Sites folder, click Add/Drop under the appropriate site.
2. In the Properties pane, choose Auto from the OADM Forcing drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

If the DCUs in the same site are both SMF slope compensating, the cumulative negative dispersion should not be over 1600 ps/nm.

Remove or change one of the forced DCUs:

1. In the Project Explorer pane, click C-Band Amplifiers.
2. In the Properties pane, choose the desired DCU from the DCU1 and/or DCU2 drop-down lists.
3. Re-analyze the network.

If the DCUs in the same site belong to different types, only the following DCU combinations are allowed: DCU-E-200 and DCU-100, or DCU-E-350, and DCU-100.

Two E-LEAF slope compensating DCUs are not allowed at the same site.

Possible Problem

Solution

In L-band, a node with an MMU installed has amplifier forcing other than two OPT-AMP-L amplifier units, one as PRE and one as BST.

Remove any amplifier forcing in the node:

1. In the Project Explorer pane under the Sites folder, click L-Band Amplifiers for the appropriate site.
2. In the Properties pane, choose Auto from the PRE and BST drop-down lists.
3. Re-analyze the network.

Possible Problem

Solution

In C-band, a node with an MMU installed requires both OPT-PRE and OPT-BST.

Remove any amplifier forcing in the node:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers for the appropriate site.
2. In the Properties pane, choose Auto from the PRE and BST drop-down lists.
3. Re-analyze the network.

Possible Problem

Solution

The output power or tilt forced by the user is not within the allowed range based on the algorithm selected and the type of amplifier selected.

Remove or change the forced value:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers or L-Band Amplifiers for the appropriate site.
2. In the Properties pane, choose Auto from the Tilt drop-down list in the From Fiber and To Fiber areas. If you force a value, the tilt value limits are -3.0 to +3.0.
3. Re-analyze the network.

Possible Problem

Solution

An attenuator is forced in a site where there is no place to connect.

Remove the attenuator forcing or verify that the attenuator is inserted on the correct side and wavelength:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers or L-Band Amplifiers for the appropriate site.
2. In the Properties pane, complete one of the following:
3. Choose Auto from the Attenuator drop-down list in the From Fiber area to remove the forcing.
4. Verify that the attenuator is inserted on the correct side and wavelength. If not, revise accordingly.
5. Re-analyze the network.

Possible Problem

Solution

Cisco Transport Planner has an attenuator forced in a site where there is no place to connect.

Remove the attenuator forcing or verify that the attenuator is inserted on the correct side and wavelength:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers or L-Band Amplifiers for the appropriate site.
2. In the Properties pane, complete one of the following:
3. Choose Auto from the Attenuator drop-down list for the appropriate amplifier.
4. Verify that the attenuator is inserted on the correct side and wavelength. If not, revise accordingly.
5. Re-analyze the network.

Possible Problem

Solution

After a network upgrade, a client was removed but the add/drop attenuator is still forced.

Unlock the add/drop attenuator:

1. In the Project Explorer pane under the Sites folder, click Client for the appropriate site.
2. In the Properties pane, choose Auto from the drop-down list for the appropriate Rx and Tx attenuator.
3. Re-analyze the network.

Possible Problem

Solution

The user forced one or more amplifier tilt setting, but the No Tilt Design option is also selected.

Remove forced tilt for the amplifier:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers or L-Band Amplifiers for the appropriate site.
2. In the Properties pane, choose Auto from the Tilt drop-down list for the appropriate amplifier.
3. Re-analyze the network.

Possible Problem

Solution

Cisco Transport Planner attempts to use the 32DMX-O card but the 32-DMX card is forced by the user. This could cause an overload of alarms or, if no channel is alarmed, problems during network installation.

If channels dropped at the site are alarmed, allow the use of add/drop attenuators:

1. In the Project Explorer pane under the Subnets folder, expand DWDM Design Rules and click System Release.
2. In the Properties pane, uncheck No TXT/Line-Card RX Bulk Attenuator Design.
3. Re-analyze the network.

If no channel is alarmed, remove the 32-DMX forcing:

1. In the Project Explorer pane under the Sites folder, click Add/Drop for the appropriate site.
2. In the Properties pane, choose Auto from the Demux drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

A preamplifier is working in power control mode. Based on the traffic matrix, channel survivability might not be guaranteed if the fiber is cut or the equipment fails.

If the booster amplifier preceding the preamplifier is forced as None by the user, remove the None forcing on the booster amplifier:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers or L-Band Amplifiers for the appropriate site.
2. In the Properties pane, choose Auto from the Tilt drop-down list for the From Fiber (BST) amplifier.
3. Re-analyze the network.

If the span preceding the preamplifier is within the 27 to 30 dB range, use a higher powered C- or L-band rules algorithm (such as, 32 Chs + 5 dBm/ch):

1. In the Project Explorer pane under the Subnets folder, expand Traffic Mapping and click System Release.
2. In the Properties pane, choose the new rules option from the C-Band Rules or L-Band Rules drop-down list.
3. Re-analyze the network.

If span is greater than 30 dB, the error is unavoidable.

Possible Problem

Solution

An amplifier is working with a gain lower than its minimum capabilities. This could be caused by a span that is too short or by compensation problems (L-band only) coupled with the “Use in-line attenuator” option not selected.

If attenuators are forced or inline attenuators were disabled, remove the forcing on the attenuators:

1. In the Project Explorer pane under the Sites folder, click Add/Drop for the appropriate site.
2. In the Properties pane, choose Auto from the Attenuator drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

An amplifier is working with a gain that is greater than its physical capabilities.

Remove the forcing on the attenuators:

1. In the Project Explorer pane under the Sites folder, click Add/Drop for the appropriate site.
2. In the Properties pane, choose Auto from the Attenuator drop-down list.
3. Re-analyze the network.

Possible Problem

Solution

If the warning appears during a network upgrade, this means the installation parameters must be updated because the upgrade is traffic affecting. This warning could also appear after importing a Cisco MetroPlanner 2.5.x network with all output as forcings.

For a network upgrade, unlock the site with the warning.

For a 2.5.x import, if you cannot update the installation parameters, open the design in Cisco MetroPlanner 2.5.x.

Possible Problem

Solution

The system is working over its specifications.

Revise the design and re-analyze.

Possible Problem

Solution

Some thresholds are set to the minimum value allowed; this could lead to some false alarms during network life.

Remove the forcing:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers or L-Band Amplifiers for the appropriate site.
2. In the Properties pane, choose Auto from the PRE and BST drop-down lists.
3. Re-analyze the network.

Possible Problem

Solution

The channel power received by the site is too low, and the fail threshold cannot be set.

Remove the forcing:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers or L-Band Amplifiers for the appropriate site.
2. In the Properties pane, choose Auto from the PRE and BST drop-down lists.
3. Re-analyze the network.

Possible Problem

Solution

The OSC channel is not working.

Remove the forcing:

1. In the Project Explorer pane under the Sites folder, click C-Band Amplifiers or L-Band Amplifiers for the appropriate site.
2. In the Properties pane, choose Auto from the OSC drop-down list.
3. Re-analyze the network.

If the span where the OSC fails is longer than 37 dB, the error is unavoidable.