C.1 Traffic Mapping Troubleshooting
The following procedures help you resolve traffic mapping problems with the network design.
C.1.1 Wavelength Exceeded
Symptom Cisco Transport Planner warns you that all network analysis solutions exceed the wavelengths.
Table C-1 describes the potential causes of the symptom and the solution.
Table C-1 Wavelength Exceeded
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. Reanalyze 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. Reanalyze the network. |
C.1.2 Invalid Routing
Symptom Cisco Transport Planner warns you of invalid routing (out of network boundary).
Table C-2 describes the potential causes of the symptom and the solution.
Table C-2 Invalid Routing
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. Reanalyze the network. |
C.1.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 C-3 describes the potential causes of the symptom and the solution.
Table C-3 Cannot Find Alternate Route
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. Reanalyze the network. |
C.1.4 Cannot Route Service
Symptom Cisco Transport Planner warns you that it cannot route service through a hub node.
Table C-4 describes the potential causes of the symptom and the solution.
Table C-4 Cannot Route Service
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. Reanalyze 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. Reanalyze the network. |
C.1.5 Overlapped Services Assigned to the Same Wavelength
Symptom Cisco Transport Planner warns you that overlapped services are assigned to the same wavelength.
Table C-5 describes the potential causes of the symptom and the solution.
Table C-5 Overlapped Services Assigned to the Same Wavelength
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. Reanalyze 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. Reanalyze the network. |
C.1.6 Protected Services Assigned to the Same Wavelength
Symptom Cisco Transport Planner warns you that protected services are assigned to the same wavelength.
Table C-6 describes the potential causes of the symptom and the solution.
Table C-6 Protected Services Assigned to the Same Wavelength
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. Reanalyze the network. |
C.1.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 C-7 describes the potential causes of the symptom and the solution.
Table C-7 Cannot Route Service Because of Add/Drop Constraints
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. Reanalyze the network. |
C.1.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 C-8 describes the potential causes of the symptom and the solution.
Table C-8 Cannot Route Service Because of Add/Drop Constraints
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. Reanalyze 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. Reanalyze the network. |
C.2 Amplifier Troubleshooting
The following procedures help you resolve amplifier-related problems with the network design.
C.2.1 Incompatible DCUs (C-Band)
Symptom Cisco Transport Planner warns you that DCUs are incompatible.
Table C-9 describes the potential causes of the symptom and the solution.
Table C-9 Incompatible DCUs (C-Band)
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. Reanalyze 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. |
C.2.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 C-10 describes the potential causes of the symptom and the solution.
Table C-10 MMU Does Not Have the Correct Amplifier (L-Band)
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. Reanalyze the network. |
C.2.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 C-11 describes the potential causes of the symptom and the solution.
Table C-11 MMU Does Not Have the Correct Amplifier (C-Band)
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. Reanalyze the network. |
C.2.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 C-12 describes the potential causes of the symptom and the solution.
Table C-12 Output Power or Tilt are Out of Range
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. Reanalyze the network. |
C.2.5 Invalid Fiber Values, Types, and Loss Values
Symptom Cisco Transport Planner warns you of one of the following:
- Fiber pairs are of invalid types or values
- Fibers have a start of life (SOL) total loss greater than an end of life (EOL) total loss
Table C-13 describes the potential causes of the symptom and the solution.
Table C-13 Invalid Fiber Values, Types, and Loss Values
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:
- Choose Auto from the Attenuator drop-down list in the From Fiber area to remove the forcing.
- Verify that the attenuator is inserted on the correct side and wavelength. If not, revise accordingly.
3. Reanalyze the network. |
C.2.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 C-14 describes the potential causes of the symptom and the solution.
Table C-14 Attenuator Forcing Not Allowed
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:
- Choose Auto from the Attenuator drop-down list for the appropriate amplifier.
- Verify that the attenuator is inserted on the correct side and wavelength. If not, revise accordingly.
3. Reanalyze the network. |
C.2.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 C-15 describes the potential causes of the symptom and the solution.
Table C-15 Unavailable Add/Drop Channels
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. Reanalyze the network. |
C.2.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 C-16 describes the potential causes of the symptom and the solution.
Table C-16 Tilt Forced When No Tilt Design is Selected
Possible Problem |
Solution |
The user forced one or more amplifier tilt setting, but the No Tilt Design option is also selected. Note To view that No Tilt Design is selected in the Project Explorer, click the appropriate system release under DWDM Design Rules settings in the Subnets folder. |
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. Reanalyze the network. |
C.2.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 C-17 describes the potential causes of the symptom and the solution.
Table C-17 Cannot Replace 32-DMX with 32DMX-O
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. Reanalyze 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. Reanalyze the network. |
C.2.10 Preamplifier Working in Invalid Mode
Symptom Cisco Transport Planner warns you that a preamplifier is working in an invalid mode.
Table C-18 describes the potential causes of the symptom and the solution.
Table C-18 Preamplifier Working in Invalid Mode
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. Reanalyze 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. Reanalyze the network. If span is greater than 30 dB, the error is unavoidable. |
C.2.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 C-19 describes the potential causes of the symptom and the solution.
Table C-19 Gain Too Low for an Amplifier
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. Reanalyze the network. |
C.2.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 C-20 describes the potential causes of the symptom and the solution.
Table C-20 Gain Too High for an Amplifier
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. Reanalyze the network. |
C.2.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 C-21 describes the potential causes of the symptom and the solution.
Table C-21 User Forcing Overridden
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. |
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, see “Viewing Report Differences” section.
C.2.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 C-22 describes the potential causes of the symptom and the solution.
Table C-22 Unsupported Configuration
Possible Problem |
Solution |
The system is working over its specifications. |
Revise the design and reanalyze. |
C.2.15 Channel Power Near the Fail Threshold
Symptom Cisco Transport Planner warns you that the channel power is near the fail threshold.
Table C-23 describes the potential causes of the symptom and the solution.
Table C-23 Channel Power Near the Fail Threshold
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. Reanalyze the network. |
C.2.16 Channel Power Below the Fail Threshold
Symptom Cisco Transport Planner warns you that the channel power is below the fail threshold.
Table C-24 describes the potential causes of the symptom and the solution.
Table C-24 Channel Power Below the Fail Threshold
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. Reanalyze the network. |
C.2.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 C-25 describes the potential causes of the symptom and the solution.
Table C-25 OSC Channel Power Below the Fail Threshold
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. Reanalyze the network. If the span where the OSC fails is longer than 37 dB, the error is unavoidable. |