Table Of Contents

Troubleshooting the Service Agent

Error Group

cwmErrorTable

Example Using the Error Table

Deprecated MIBs

cwmErrorScalars

Deprecated MIBs

Common Errors

Troubleshooting the Service Agent

---

This appendix describes the error tables used to troubleshoot errors with the Service Agent. See these sections:

•Error Group

•Common Errors

Error Group

When an SNMP request fails, a standard SNMP error code is returned by the Service Agent to the SNMP user. Sometimes the standard error code is not sufficient to troubleshoot the request, especially for SET requests with an SNMP failure code as GenError.

The Service Agent supports a MIB that can assist in providing more information on the error encountered for the SET requests on any of the various Service Group MIB tables.

The Error Group contains an error table and an error scalar group.

cwmErrorTable

The cwmErrorTable contains the following objects:

•cwmErrorEcode (integer error code)

•cwmErrorDesc (ASCII error detail string)

•cwmErrorLogfile (Service Agent log file name, for example, ConnProxy2.log)

This table is indexed by the standard request ID that is used in the original SET request.

Example Using the Error Table

The example shows finding the cause of the failure of a SET request on the cwmRsrcPartTable.

This example uses the following setup:

•CWM host = cwmult64

•RequestId = 31666 (used in the SET request PDU)

The following example shows a GET request on the error table

snmpget -p 8161 -t 60 -c public<cwmult64> \ 
cwmErrorLogfile.<31666> cwmErrorDesc.<31666> cwmErrorEcode.<31666>

The following example shows a GET response from the Service Agent:

cwmErrorLogfile.31666 : DISPLAY STRING- (ascii):  PortProxy.log 
cwmErrorDesc.31666 : DISPLAY STRING- (ascii):  [04/02/2003 15:53:44] Attempt to add 
duplicate resource partition 
cwmErrorEcode.31666 : INTEGER: node-error

Deprecated MIBs

With the introduction of cwmErrorTable, the following MIBs have been deprecated:

•svCmpaErrorTable

•psaErrorTable

•cwmLineErrTable

•cardPaErrorTable

cwmErrorScalars

The cwmErrorScalars group contains the same information as that of the cwmErrorTable, but the scalar group contains the error details only for the last or latest error that occurs on the Service Agent.

If multiple users are doing SET requests on the Service Agents. a GET on these objects might return details for a different error since the cwmErrorScalars objects maintain only the last or latest error details. But it is convenient to use if there is only one user per CWM workstation.

The objects in this group do not have an index. You do not need to supply a requestID for GET requests.

The following objects are supported in this group:

•cwmErrorLastLogfile

•cwmErrorLastDesc

•cwmErrorLastEcode

The example in this section uses the following setup:

CWM host = cwmult64

To obtain the last Service Agent error, enter the following command:

snmpget -p 8161 -t 60 -c public <cwmult64> \ 
cwmErrorLastLogfile.0 cwmErrorLastDesc.<0> cwmErrorLastEcode.<0>

Deprecated MIBs

With the introduction of cwmErrorScalars, the following scalar objects have been deprecated:

•svCmpaErrorLastIndex

•svCmpaErrorFlushAll

•svCmpaErrorLastDesc

•svCmpaErrorLastEcode

•psaErrorLastIndex

•psaErrorFlushAll

•psaErrorLastDesc

•psaErrorLastEcode

•cardPaErrorFlushAll

•cardPaErrorLastDesc

•cardPaErrorLastEcode

•cwmLineErrFlushAll

•cwmLineErrLastReqId

•cwmLineErrLastErrDesc

•cwmLineErrLastErrCode

Common Errors

Table D-1 lists some of the common errors returned by the Service Agent and possible solutions to the problems.

Table D-1 Service Agent Errors 

Error	Possible Remedy
Agent is not responding.	1. Check that the SNMP Service Agent is running on the host to which the request is being sent. 2. When the SNMP Service Agent is running, check that the correct UDP port is used for sending the requests. 3. When the UDP port is ok, check the community strings.
Agent returns noSuchName error.	If a SET request returns noSuchName error, and no information is returned by the error table, then the OID used in the SET request is incorrect 1. Check the OID. The OID of the object used could be wrong. For example, OID 1.3.6.1.4.1.351.1.101.2.25.1.7 represents a valid object in cwmRsrcPartTable. However, OID 1.3.6.1.4.1.351.1.101.2.25.1.50 is invalid because object with ID of 50 does not exist in the cwmRsrcPartTable. 2. Verify that all the INDICES are supplied as part of the OID. For example, OID 1.3.6.1.4.1.351.1.101.2.25.1.7.8.49.48.53.112.50.99.119.50.0.14.255.1 is not valid because the SET request on cwmRsrcPartRowStatus has incorrect number of INDICES: Another example is for OID: 1.3.6.1.4.1.351.1.101.2.25.1.7.<8.49.48.53.112.50.99.119.50>.<0>.<14>.<255>.<1> The INDICES cwmRsrcPartNode, cwmRsrcPartShelf, cwmRsrcPartSlot, cwmRsrcPartPort, and cwmRsrcPartID are included, but INDEX cwmRsrcPartController is missing. This missing index can cause the noSuchName error 3. When the OID specified is valid, check whether you are using the correct UDP port for sending the request. 4. When the UDP port is correct, check whether the Service Agent is running. (ConnProxy for Connection MIB and PortProxy for the Port MIB.) Use the "Start SNMP Agent" option from the Cisco WAN Manager to start the missing Service Agent.