C-74
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
Defect Information—Collect the following information for further analysis:
• Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory.
• Collect screen snapshots. In particular, error/information message dialog boxes.
• Collect Java Console information (In particular any java raised exceptions).
• Collect cmsvr.log file under the /opt/svplus/log directory.
• Collect configserver.log file under the /opt/svplus/log directory.
Possible alternative workaround—None
C.9.3 Cmsvr Errors
The following are some of the most common errors seen when a Provisioning request is issued:
• C.9.3.1 End to End Type Cannot Be PVC for Connections with PNNI Segment
• C.9.3.2 Unsupported Service Type for the Foresight Connections for PNNI/SPVC Endpoints
• C.9.3.3 Ce-Ce Connection Port Speed Should Be Same on Both
• C.9.3.4 Cannot Create One Segment Hybrid
• C.9.3.5 Cannot Add Connection Between -byte Port Header and -byte Port Header for chan type
NIW and NIW-replace
• C.9.3.6 Unsupported Service Type - General node-slot-port-version
• C.9.3.7 End Point Not Present in One of the Connection Tables During Modify
• C.9.3.8 Cmsvr—Connection Diagnostics Issues
• C.9.3.9 TestConn or TestDelay Failed With Switch Error
• C.9.3.10 Connection Up/Down/Reroute Failed
• C.9.3.11 Connection Trace Failures
C.9.3.1 End to End Type Cannot Be PVC for Connections with PNNI Segment
When a connection addition is attempted, cmsvr checks its the endpoints and the End to End Type to
make sure it is supported. The return error window on the screen states "EndtoEndType cannot not 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 (as the case might be).
Defect Information—Collect the cmsvr logs, in the directory /opt/svplus/log.
Possible alternative workaround—None.
Comments to this Manuals