J-90
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
AppendixJ Troubleshooting
J.10.8 Connection Management Problems
CMSCclient.log file under the D:\Documents and Settings\<username>\log directory.
Java Console information; in particular, any Java-raised exceptions.
Screen snapshots; in particular, error/information messages dialog boxes.
Cmsvr.log file under the /opt/svplus/log directory.
Configserver.log file under the /opt/svplus/log directory.
Possible alternative workaround—None.
J.10.8.3 Cmsvr Errors
The following are some of the most common errors seen when a provisioning request is issued:
J.10.8.3.1 End-to-End Type Cannot Be PVC for Connections with PNNI Segment, page J-90
J.10.8.3.2 Unsupported Service Type for the Foresight Connections for PNNI/SPVC Endpoints,
page J-91
J.10.8.3.3 CE-CE Connection Port Speed Should Be the Same on Both Endpoints, page J-91
J.10.8.3.4 Cannot Create One-Segment Hybrid, page J-91
J.10.8.3.5 Cannot Add Connection Between -byte Port Header and -byte Port Header for chan type
NIW and NIW-replace, page J-91
J.10.8.3.6 Unsupported Service Type—General node-slot-port-version, page J-92
J.10.8.3.7 Endpoint Is Not Present in One of the Connection Tables During a Modify Operation,
page J-92
J.10.8.3.8 Cmsvr—Connection Diagnostic Issues, page J-93
J.10.8.3.9 TestConn or TestDelay Failed with Switch Error, page J-93
J.10.8.3.10 Connection Up/Down/Reroute Failed, page J-94
J.10.8.3.11 Connection Trace Failures, page J-94

J.10.8.3.1 End-to-End Type Cannot Be PVC for Connections with PNNI Segment

When an add connection is attempted, cmsvr checks its the endpoints and the end-to-end type to make
sure it is supported. The error message states "EndtoEndType cannot be PVC for connections with a
PNNI segment."
The problem must be fixed on the CM GUI while adding the connection.
Step 1 Verify that the endpoints that are being used to add the connection are not on PNNI nodes or feeders to
PNNI nodes.
Step 2 Change the end-to-end type in the CM GUI to either SPVC or Hybrid.
Defect Information—Collect the cmsvr logs from the /opt/svplus/log directory.
Possible alternative workaround—None.