Traffic Mapping Troubleshooting
The following procedures help you resolve traffic mapping problems with the network design.
Wavelength Exceeded
Symptom: Cisco Transport Planner warns you that all network analysis solutions exceed the wavelengths.
The following table describes the potential causes of the symptom and the solution.
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:
|
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:
|
Invalid Routing
Symptom: Cisco Transport Planner warns you of invalid routing (out of network boundary).
The following table describes the potential causes of the symptom and the solution.
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:
|
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.
The following table describes the potential causes of the symptom and the solution.
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:
|
Cannot Route Service
Symptom: Cisco Transport Planner warns you that it cannot route service through a hub node.
The following table describes the potential causes of the symptom and the solution.
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:
To remove the hub functionality constraints:
|
Overlapped Services Assigned to the Same Wavelength
Symptom: Cisco Transport Planner warns you that overlapped services are assigned to the same wavelength.
The following table describes the potential causes of the symptom and the solution.
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:
To remove the wavelength forcing:
|
Protected Services Assigned to the Same Wavelength
Symptom: Cisco Transport Planner warns you that protected services are assigned to the same wavelength.
The following table describes the potential causes of the symptom and the solution.
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:
|
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.
The following table describes the potential causes of the symptom and the solution.
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.
|
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.
The following table describes the potential causes of the symptom and the solution.
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:
To change site functionality and type forcing:
To unlock OADM equipment:
|