Cisco Application Performance Assurance Troubleshooting Guide - Troubleshooting Specific Scenarios [Cisco Application Networking Services Modules]

Table Of Contents

Troubleshooting Specific Scenarios

Accessing the NME-APA module

How to Access the NME-APA Module via Telnet

How to Access the NME-APA Module via the ISR Router

How to Access the NME-APA Module via APADC

APADC Login Fails

First time login fails

Problem Persists

Subsequent login fails

Problem Persists

ISR/NME-APA Platform Troubleshooting

The NME-APA does not come up

The NME-APA does not power up

During installation of the NME-APA image, the NME-APA card does not come up

Cannot ping the NME-APA management interface from the ISR Router

Cannot Telnet to NME-APA management interface from other station

During installation of the NME-APA image, an error is received

The NME-APA does not see any diverted traffic

APADC Application Troubleshooting

Connect Screen Troubleshooting

Cannot connect to "Available" device

Cannot disconnect a "Connected" device

Cannot add a device

Device stays "Offline"

Device Configuration Screens Troubleshooting

Cannot access Device Configuration Screen

Device Configuration is erased

Apply fails

Retrieve fails

Fault Management Screen Troubleshooting

Notification is not received

Statistics Screen Troubleshooting

Statistics Screen Problems

Installation Screen Troubleshooting

Install process fails with the error `Cannot connect to device'

Install process fails with the error "Image file type and file mismatch"

Traffic Management Screen Troubleshooting

Cannot apply TM configuration to device

Reporting Screen Troubleshooting

RDR retrieval ("RetrieveNow") fails

Can not "Activate" scheduled task

Cannot "Add" a scheduled task

RDR Retrieval continues to be in "In Progress" state

No "Last Retrieval" information is displayed

Report fails to generate output (PROCESS_ERROR)

Cannot create report instance

"Run report JPEG" is disabled for certain reports

Report results are empty

Report fails to generate output (PROCESS_ERROR)

User Management Screen Troubleshooting

Users not matched between Scate and Device after apply

Error stating FTP not available when retrieving or applying

Admin Screen Troubleshooting

Cannot Add a new APADC user

Traffic Classification Troubleshooting

No RDRs after pushing the traffic

Some RDRs are not received

RDRs are received with incorrect values for some parameters

RDR File Troubleshooting

No RDRs are received by the external entity

No RDR files are generated

The RDR files are not retrieved

SNMP Troubleshooting

Cannot get MIB values

SNMP Troubleshooting on APADC

SNMP agent is running but no MIB values are displayed on the Device Statistics pages

Troubleshooting Specific Scenarios

This module includes procedures that operators can use to troubleshoot issues when using the Cisco Network Enhanced Module for Application Performance Assurance (NME-APA) and the Cisco Application Performance Assurance Device Console (APADC).

•Accessing the NME-APA module

•ISR/NME-APA Platform Troubleshooting

•APADC Application Troubleshooting

•RDR File Troubleshooting

•SNMP Troubleshooting

Accessing the NME-APA module

You can access the NME-APA module:

•by telnet

•through the ISR router

•through a web-based application (APADC)

APADC is the preferred method of access.

How to Access the NME-APA Module via Telnet

You can access the NME-APA module by Telnet.

Step 1 Configure the IP address from the ISR router.

Step 2 Telnet to the NME-APA module, to get the CLI login prompt.

Step 3 Execute the CLI commands based on the level (5, 10, or 15) being enabled.

The CLI debug commands can only be executed under level 15 (ROOT level).

How to Access the NME-APA Module via the ISR Router

You can access the NME-APA module through the ISR router.

Step 1 Run the ISR session command, service-module integrated-Service-Engine <slot/0>session. (The term shellConn is used for referring to the NME-APA console.)

All the engineering commands are used for debugging purpose. They should be used with care so that they do not interfere with live traffic.

How to Access the NME-APA Module via APADC

You can access the NME-APA module by APADC.

Step 1 Click on the APADC icon on the desktop of the server.

For the first-time login, use username: root, password: cisco.

APADC Login Fails

•First time login fails

•Subsequent login fails

First time login fails

First time login (username: root, password: cisco) fails.

Step 1 Verify that MySQL is correctly installed.

Verify that the C:\ mysql-enterprise-5.0.44-win32\ folder exists.

Step 2 Verfiy that the MySQL Windows service is running.

Check under Windows services that SCAtE-MySQL is running.

Step 3 Query the MySQL dbase.

•username: scate

•password: scate

•dbase: scate

•table: scate_user

Step 4 Validate the table.

Verify that a row exists in this table with:

•username=root

•password=Cisco

Problem Persists

If the problem persists, completely uninstall and reinstall APADC.

Subsequent login fails

Step 1 Verify that MySQL is correctly installed.

Verify that the C:\ mysql-enterprise-5.0.44-win32\ folder exists.

Step 2 Verfiy that the MySQL Windows service is running.

Check under Windows services that SCAtE-MySQL is running.

Step 3 Query the MySQL dbase.

•username: scate

•password: scate

•dbase: scate

•table: scate_user

Step 4 Validate the table.

Verify that a row exists in this table with username and password.

Step 5 Try a different scate user login.

Step 6 Go to Admin; delete and add the user that failed to login.

Problem Persists

If the problem persists, completely uninstall and reinstall APADC.

Warning This will delete all of the saved data on the application.

ISR/NME-APA Platform Troubleshooting

•The NME-APA does not come up

•The NME-APA does not power up

•During installation of the NME-APA image, the NME-APA card does not come up

•Cannot ping the NME-APA management interface from the ISR Router

•Cannot Telnet to NME-APA management interface from other station

•During installation of the NME-APA image, an error is received

•The NME-APA does not see any diverted traffic

The NME-APA does not come up

Step 1 Verify that the NME-APA has a service-module IP address and default gateway configured on the ISR.

The NME-APA does not power up

Step 1 Verify that the NME-APA is firmly seated in the ISR slot and that the retaining screws are tightened.

Step 2 Make sure the slot being used can support the NME-APA card.

Step 3 Verify that you are not attempting to use an NME-APA-E3 card in an ISR 2800 or an NME-APA-E2 card in an ISR 3800.

During installation of the NME-APA image, the NME-APA card does not come up

Step 1 Check the IOS version on the ISR using the show version command.

Step 2 Make sure that the IOS version supports the NME-APA card.

Step 3 If the IOS version does not support the NME-APA card, update the ISR IOS image to a version that supports the NME-APA card.

Cannot ping the NME-APA management interface from the ISR Router

Step 1 Verify that there is a valid route to and from the NME-APA. (This might require a static route to the NME-APA on the ISR if the Integrated Service Engine interface is set to ip unnumbered.)

Cannot Telnet to NME-APA management interface from other station

Step 1 Verify that there is a valid route to and from the NME-APA.

Step 2 Use the NME-APA ShellConn command i to see whether the telnetServer process is up and running.

Step 3 If the telnetServer process is not running, leave the card in its current state for DEs to debug.

During installation of the NME-APA image, an error is received

During installation of the NME-APA image, the following error is received:
Pycurl.error: invalid return value for write callback 
Error: Operation Aborted.
Step 1 The package name has the wrong extension. Change the extension to .pkg.

The NME-APA does not see any diverted traffic

Step 1 From the ISR IOS CLI run show running-config interface integrated-Service-Engine <slot/0>. If !SCE traffic-management Disabled appears in the output, the NME-APA card is currently not enabled. Wait a few minutes and then try again. Also, verify that you have the correct card for this ISR model.

Step 2 Make sure that traffic diversion is enabled on the designated interface. You should see that the configuration, service-module apa traffic-management monitor, is set to that interface.

Step 3 Make sure that traffic is arriving from the designated interface. (Use the ISR IOS CLI show interfaces <fastEthernet or GigabitEthernet><slot><port>counters. The counters should increase when you pump the traffic. If there is no increase, the traffic is not getting to the ISR chassis.)

Step 4 Use the NME-APA CLI show interface fastEthernet 0/1 counters to see whether traffic has been diverted to NME-APA from ISR. The output will indicate whether the packets are diverted to NME-APA or are discarded by NME-APA.

APADC Application Troubleshooting

•Connect Screen Troubleshooting

•Device Configuration Screens Troubleshooting

•Fault Management Screen Troubleshooting

•Statistics Screen Troubleshooting

•Installation Screen Troubleshooting

•Traffic Management Screen Troubleshooting

•Reporting Screen Troubleshooting

•User Management Screen Troubleshooting

•Admin Screen Troubleshooting

•Traffic Classification Troubleshooting

Connect Screen Troubleshooting

•Cannot connect to "Available" device

•Cannot disconnect a "Connected" device

•Cannot add a device

•Device stays "Offline"

Cannot connect to "Available" device

Step 1 Go to Admin >Admin User Management.

Step 2 Verify that the logged-in scate user appears in the "User" column.

Step 3 Verify that the NME-APA trying to connect is a "configured device" for the scate user.

Step 4 Click on the device name in the "configured device" column.

Step 5 Verify that the device user name is correctly configured and is the same as the username configured on the NME-APA (by Telnet).

Step 6 If the problem persists, create a new user account on the device and use this account to connect to the device by configuring it under Admin >Admin User Management.

Step 7 Click Help, to review integrated help for more details.

Step 8 If the problem persists, report to Cisco Systems, Inc.

Cannot disconnect a "Connected" device

Step 1 Select the device and delete it.

Step 2 Reset the device.

Step 3 Click Help, to review integrated help for more details.

Step 4 If the problem persists, report to Cisco Systems, Inc.

Cannot add a device

Step 1 Verify that there are no more than five devices already added to the APADC application.

Step 2 If more than five devices are already added to the APADC application, delete an existing device to add a new device.

Step 3 Verify the correct network address for the device to be added.

Step 4 Click Help, to review integrated help for more details.

Step 5 If the problem persists, report to Cisco Systems, Inc.

Device stays "Offline"

Step 1 Ping the device from the web server running APADC.

Step 2 Restart the Tomcat Windows service from Windows Administrative Tools > Services.

Step 3 Restart the application server.

Step 4 Click Help, to review integrated help for more details.

Step 5 If the problem persists, report to Cisco Systems, Inc.

Device Configuration Screens Troubleshooting

•Cannot access Device Configuration Screen

•Device Configuration is erased

•Apply fails

•Retrieve fails

Cannot access Device Configuration Screen

Step 1 Verify that at least one device is in the "Connected" state.

Step 2 Verify that the user role allows access to this screen. Refer to the SFS for details.

Device Configuration is erased

Step 1 Click Savebefore toggling to a different tab after making configuration changes.

Step 2 Click Apply to commit configuration data to NME-APA.

Step 3 Any configuration on a tab is lost if it is not saved before user moves to a different tab.

Step 4 Click Help, to review integrated help for more details.

Step 5 If the problem persists, report to Cisco Systems, Inc.

Apply fails

Step 1 Verify that the "Connected " device is still available and alive.

Step 2 Click Help, to review integrated help for more details.

Step 3 If the problem persists, report to Cisco Systems, Inc.

Retrieve fails

Step 1 Verify that the "Connected" device is still available and alive.

Step 2 Click Help, to review integrated help for more details.

Step 3 If the problem persists, report to Cisco Systems, Inc.

Fault Management Screen Troubleshooting

Notification is not received

Step 1 Verify that the Notification is not suppressed:

a. Go to the Fault Configuration screen.

b. Look for the Notification ID for the missing notification.

c. Verify that the Notification ID is present in the table.

d. Check to see that the "Suppressed" column has the value "No", rather than "Yes".

Step 2 Click "Refresh" .

Step 3 Verify that NME-APA is sending a Notification.

Step 4 Click Help, to review integrated help for more details.

Step 5 If the problem persists, report to Cisco Systems, Inc.

Statistics Screen Troubleshooting

Statistics Screen Problems

Step 1 All Statistics are accumulated via SNMP queries. See SNMP Troubleshooting on APADC.

Installation Screen Troubleshooting

•Install process fails with the error `Cannot connect to device'

•Install process fails with the error "Image file type and file mismatch"

Install process fails with the error `Cannot connect to device'

Step 1 Ensure the Web user has credentials on the device as a level-15 user. (If the device user corresponding to the Web user has a level 0/5/10 credentials, the install process will fail.)

Install process fails with the error "Image file type and file mismatch"

The image file type selected for install (pqi or pqb) must have a filename extension of .pqi or .pqb . The files are not transferred from the user PC to the scate server if a filename mismatch occurs. (Further semantic checks are performed in the next stage of the process to verify that the image files are of the expected type.)

Step 1 Verify that the installation file has the correct filename extension.

Traffic Management Screen Troubleshooting

Cannot apply TM configuration to device

Step 1 Check the server log for a connection-related exception.
2007-07-25 11:09:11,929  INFO [http-8080-Processor20] com.pcube.apps.engage.Engage - 
Sending configuration to SCE ... 
connection to SCE failed: server refused connection: unable to open connections - max 
number of sessions exceeded 
com.pcube.apps.engage.ConnectionFailedException: server refused connection: unable to open 
connections - max number of sessions exceeded 
	at com.pcube.apps.engage.Connection.login(Connection.java:414) 
	at com.pcube.apps.engage.Engage.login(Engage.java:138) 
	at com.cisco.scabb.servconf.mgmt.SCABB.login(SCABB.java:81) 
	at 
com.cisco.scate.web.mgt.tm.ServiceConfigManager.applyServiceConfig(ServiceConfigManager.ja
va:115) 
	at 
com.cisco.scate.web.ui.tm.service.ClassTreeAction.showClassTree(ClassTreeAction.java:159)
If there is such a connection-related exception and reapplying the TM config to the device still fails, the connection between the SCAtE server and the device is maxed out.

Step 2 Restart the SCAtE server (Tomcat).

Reporting Screen Troubleshooting

•RDR retrieval ("RetrieveNow") fails

•Can not "Activate" scheduled task

•Cannot "Add" a scheduled task

•RDR Retrieval continues to be in "In Progress" state

•No "Last Retrieval" information is displayed

•Report fails to generate output (PROCESS_ERROR)

•Cannot create report instance

•"Run report JPEG" is disabled for certain reports

•Report results are empty

•Report fails to generate output (PROCESS_ERROR)

RDR retrieval ("RetrieveNow") fails

Step 1 Verify that the "Connected " device is still available and alive.

Step 2 Verify that it is possible to FTP to the NME-APA from the APADC server using the device username and password associated with the APADC user from the Admin screen.

If this step fails, refer to Device Configuration Screens Troubleshooting and verify users configured on the device. Retrieval will fail if an FTP attempt is made with a username and password that do not exist on the NME-APA device.

Step 3 Verify that enough hard-disk space is available on the APADC server.

Can not "Activate" scheduled task

Step 1 Verify that the task has not expired.

if the start time is in the past, make sure that the difference between current time and the task start time is greater than the task recurrences times task interval.

Step 2 Verify that the NME-AP device is still available and alive.

Step 3 Verify that it is possible to FTP to the NME-APA from the APADC server using the username "admin" and enable15 password.

If this step fails, refer to Device Configuration Screens Troubleshooting, and reconfigure the enable15 password on the device.

Step 4 Verify that enough hard-disk space is available on the APADC server.

Cannot "Add" a scheduled task

Step 1 Verify that at least one NME-AP device is added to APADC.

Step 2 Only one scheduled task can be added at a time. If there is a task, delete the task and try again.

RDR Retrieval continues to be in "In Progress" state

Step 1 Verify that the NME-AP device is still available and alive.

Step 2 Verify that it is possible to FTP to the NME-APA from the APADC server using the username "admin" and enable15 password.

Step 3 Verify that enough hard-disk space available on the SCAtE server

If this step fails, refer to Device Configuration Screens Troubleshooting, and reconfigure the enable15 password on the device.

Step 4 Check the server logs for OutOfMemory Errors.

Restart the Tomcat server in the case of such errors.

No "Last Retrieval" information is displayed

Step 1 Verify that the <SCATE_ROOT_DIR>/scate-config/rdrloader.xml file exists and is not empty.

Step 2 Try "RetrieveNow" to see if the information gets updated.

If the information is notupdated, there could be problems retrieving data from the NME-APA. See RDR retrieval ("RetrieveNow") fails.

Step 3 If there is a "Scheduled Task", make sure that it is still active.

Report fails to generate output (PROCESS_ERROR)

Step 1 Verify that report parameters do not contain invalid characters.

Step 2 Open a command prompt, cd to the SCA Reporter folder and run the report command.

The report command line can be found in the scate log. It should be as follows:
reportercmd -o 
../apache-tomcat-5.5.20/webapps/ROOT/report_results/Global_Bandwidth_per_IM_type[1]--NME-A
PA--2007-Aug-01-13-23-58 -format jpeg -template "Global Bandwidth per IM type" -params 
"numhours=24;im_message_type=MSN TEXT;seip=10.6.1.19;starttime=;link=Link 1,Link 
0;avgdata=false;units=Kbit/s;endtime=;trafficdir=Both Directions;" -dbuser scate 
-dbpassword scate -dburl "jdbc:mysql://localhost:3306/scateinfra" -dbdriver 
"com.mysql.jdbc.Driver" -policysce 10.6.1.19
Step 3 Remove all optional parameters and try again.

Cannot create report instance

Step 1 Traffic management configuration must be applied by APADC. Verify that the NME-APA TM was configured using the APADC. Verify that the scateinfra.INI_VALUES table in MySQL is not empty.

Step 2 Verify that the "Last Retrieval" information (Device IP and time) on the Data Retrieval page is not "Unknown".

Step 3 Verify that there is RDR data in the DB. If the DB is empty, go to the RDR Retrieval page and perform "RetrieveNow".

"Run report JPEG" is disabled for certain reports

Step 1 This behavior is by design. A few report types do not support the JPEG format and so "Run Report JPEG" is disabled. CSV reports can be generated for these report types.

Report results are empty

Step 1 Traffic management configuration must be applied by APADC. Verify that NME-APA TM was configured using the APADC. Verify that the scateinfra.INI_VALUES table is not empty in the MySQL database.

Step 2 Verify that the "Last Retrieval" was done within the last 24 hours.

Step 3 Verify that there is RDR data in the DB.

Step 4 Verify that the APADC server time zone is set correctly.

Report fails to generate output (PROCESS_ERROR)

Step 1 Verify that the report parameters do not contain invalid characters.

Step 2 Open a command prompt, cd to the SCA Reporter folder and run the report execution command. The report execution command line can be found in the scate log.

Step 3 If the previous step successfully generates a report result, remove all optional parameters and try again.

User Management Screen Troubleshooting

Users not matched between Scate and Device after apply

Step 1 Check the server log for errors after applying. Since the UM creates users by importing the whole list from Scate, there might be a conflict with the existing users.

Error stating FTP not available when retrieving or applying

Step 1 Try again. A new FTP connection to the device will be created to continue the operation.

Admin Screen Troubleshooting

The Admin Screen is used to:

•Add/Edit/Delete new APADC users

•Add/Edit/Delete new devices to APADC users

•Program device username, password, and access-level to APADC users

Cannot Add a new APADC user

Step 1 Verify that the maximum number of APADC users (100) has not been reached.

Traffic Classification Troubleshooting

•No RDRs after pushing the traffic

•Some RDRs are not received

•RDRs are received with incorrect values for some parameters

No RDRs after pushing the traffic

Step 1 Make sure that traffic is diverted to NME-APA and not discarded by NME-APA.

See The NME-APA does not see any diverted traffic.

Step 2 Make sure that the packets are not filtered (bypassed or dropped) by NME-APA.

Use the NME-APA CLI debug slot 0 ppc 0 func RC_Cls to keep track of the counters. If the numbers for drop or bypass increase after the traffic is sent, packets have been filtered.

The filtered traffic from SCAtE is used to configure the flow filter. For example, DNS packets are bypassed by default, so no RDRs will be generated by DNS traffic.

You can also use the CLI command, debug slot 0 ppc 0 show-counters.

Step 3 Ensure that the line card is not shut down.

Step 4 Make sure that the SML application is installed.

Use the NME-APA CLI show version to see whether the information about SML application is displayed.

Step 5 If the SML application is not installed, install the PQI file from the SCAtE.

Step 6 Make sure that traffic is delivered to SML Application.

Check the value of Traversed PDUs from the output of the NME-APA ShellConncommand, debug slot 0 ppc 0 func sr. If the value is 0, the SML application is not receiving traffic and no RDRs will be generated. In this case, it is possible that the traffic is not classified as a flow in SCOS. Turn on the debugging flag for the HwSim module.

1. Before you push traffic, enter the shellConn command, LC_CS_on

2. After the traffic is pushed, enter the ShellConn command, LC_CS_off

Note This command should be used in a controlled environment; it may interfere with live traffic.

The log is in the file /root/tffs0/cs.txt. Send this file to DEs for analysis.

Step 7 Save the RDRs.

The RDRs can either be saved to a file (default) or sent to an external entity such as the CM or rdrHandler. If the destination IP address of the RDR-Formatter is configured, the RDRs are sent to the external entity. Otherwise, they are saved to a file. See RDR File Troubleshooting for details.

Some RDRs are not received

Step 1 If the traffic has been processed by SML application, make sure that the corresponding RDRs are enabled in the service configuration.

Check the RDR Settings in the SCAtE, make any necessary corrections, and apply the service configuration again. Use the NME-APA CLI show running-config-application to see whether the service configuration is applied.

Note It may take some some time for the RDRs to be generated for certain traffic. For example, some RDRs for the UDP flows are generated at the close of the flow, which may take several minutes after the last packet of the traffic is sent.

Step 2 Check that the correct CAP file is being used.

If necessary, replace the cap file.

Step 3 Check the setup for traffic generate tools such as kiwi.

Make sure that kiwi is set up correctly.

Step 4 Load a debug SML image to capture traces for the Protocol Library.

Contact the DE team to see if you need to load an SML debug image and to find out which debug flags need to be turned on for this particular protocol or application.

RDRs are received with incorrect values for some parameters

Step 1 Check that the traffic contains the expected packets.

Capture the packets and then examine them.

Step 2 Compare the signature, protocol, and service ID values of the RDRs with the values in the table.

Stop as many applications in the network as possible, in order to debug and see if any application generates conflicting traffic that causes the error. Record traffic and check the CAP files.

Step 3 Load a debug SML image to capture traces for the Protocol Library.

Contact the DE team to see if you need to load an SML debug image and to find out which debug flags need to be turned on for this particular protocol or application.

Step 4 Load an SML debug image and turn on debug flags.

If necessary, contact the DE team.

Step 5 Look through the traces on the NME-APA to find the cause of the errors.

RDR File Troubleshooting

•No RDRs are received by the external entity

•No RDR files are generated

•The RDR files are not retrieved

No RDRs are received by the external entity

Step 1 Make sure that the configuration of the RDR-Formatter is correct (for instance, the IP address and the port number).

Use the NME-APA CLI show RDR-Formatter to see whether the connection between the NME-APA and the external entity is up. If the connection is down, the RDRs are queued. Check the connection between NME-APA and the external entity. (Note that this is for debugging purposes only. The RDRs should be written to files in the normal case.)

The same command will also show the number of RDRs being queued. If no RDRs are queued, refer to Traffic Classification Troubleshooting to see why no RDRs are generated.

No RDR files are generated

Step 1 Check if an IP address is configured for the RDR-Formatter.

If no IP address is configured, the RDRs are queued in the buffers and will never be written to a file even if the connection is up.

Step 2 Confirm that RDRs are being generated.

Use the NME-APA CLI show RDR-Formatter to see whether the RDRs are queued. If no RDRs are queued, refer to Traffic Classification Troubleshooting to see why no RDRs are generated.

Step 3 Use the ShellConn command, rdrShowSts, to see how much longer it has to wait before the RDRs are written to a file.

By default, these RDRs are written to a file every 30 minutes.

Step 4 After this time has elapsed, use the ShellConn command rdrShowAllFiles to see whether the file has been created.

The ShellConn command, rdrHelp, provides a list of commands for debugging RDRs.

The RDR files are not retrieved

Step 1 Make sure that the ftp server is enabled.

Use the NME-APA CLI show ip ftp-server to see whether the server is enabled.

SNMP Troubleshooting

•Cannot get MIB values

•SNMP Troubleshooting on APADC

Cannot get MIB values

Step 1 Make sure that SNMP Agent is enabled.

Use the NME-APA CLI show snmp to see whether SNMP Agent is enabled. If not, use the CLI snmp enable under configuration mode to enable it.

Step 2 Check that the console displays SNMP Server started.

If not, enter the ShellConn command debugScripts 1 from the console, and then disable and enable SNMP Agent again.

Step 3 Capture the communication between Agent and AgentX.

Enter the ShellConn command SNMP_Agentx_logging 0. The logs are stored in the file /root/tffs0/system/p3hidden/net-snmp/agentxDebug.log. Send this file to DEs for analysis.

Step 4 The ShellConn commands SNMP_AGENTX_Help and SNMP_AGENT_Help provide a list of commands for SNMP debugging.

SNMP Troubleshooting on APADC

SNMP agent is running but no MIB values are displayed on the Device Statistics pages

Step 1 Use command line utilities like snmpget, snmpwalk, or a third party MIB browser to connect to the NME-APA and verify if you are able to view the MIB-II system group.

Step 2 If you are not able to see the system group values, this indicates that the SNMP agent is not functioning properly.

Step 3 If you are able to view the MIB-II system group as well as some tables such as user counters and package counters, the most likely problem is incorrect community strings.

Step 4 If you are able to view MIB-II system group and snmp counters but not NME-APA counters such as user counters, package, and rdr counters, the problem lies with the subagent implementing the enterprise specific objects. Contact Cisco systems technical support with the relevant information.

	Cisco Application Performance Assurance Troubleshooting Guide
	Troubleshooting Specific Scenarios
Cisco Application Performance Assurance Troubleshooting Guide About this Guide NME-APA Troubleshooting Concepts Troubleshooting Specific Scenarios	Download this chapter Troubleshooting Specific Scenarios Download the complete book Cisco Application Performance Assurance Troubleshooting Guide (PDF - 1 MB) Table Of Contents Troubleshooting Specific Scenarios Accessing the NME-APA module How to Access the NME-APA Module via Telnet How to Access the NME-APA Module via the ISR Router How to Access the NME-APA Module via APADC APADC Login Fails First time login fails Problem Persists Subsequent login fails Problem Persists ISR/NME-APA Platform Troubleshooting The NME-APA does not come up The NME-APA does not power up During installation of the NME-APA image, the NME-APA card does not come up Cannot ping the NME-APA management interface from the ISR Router Cannot Telnet to NME-APA management interface from other station During installation of the NME-APA image, an error is received The NME-APA does not see any diverted traffic APADC Application Troubleshooting Connect Screen Troubleshooting Cannot connect to "Available" device Cannot disconnect a "Connected" device Cannot add a device Device stays "Offline" Device Configuration Screens Troubleshooting Cannot access Device Configuration Screen Device Configuration is erased Apply fails Retrieve fails Fault Management Screen Troubleshooting Notification is not received Statistics Screen Troubleshooting Statistics Screen Problems Installation Screen Troubleshooting Install process fails with the error `Cannot connect to device' Install process fails with the error "Image file type and file mismatch" Traffic Management Screen Troubleshooting Cannot apply TM configuration to device Reporting Screen Troubleshooting RDR retrieval ("RetrieveNow") fails Can not "Activate" scheduled task Cannot "Add" a scheduled task RDR Retrieval continues to be in "In Progress" state No "Last Retrieval" information is displayed Report fails to generate output (PROCESS_ERROR) Cannot create report instance "Run report JPEG" is disabled for certain reports Report results are empty Report fails to generate output (PROCESS_ERROR) User Management Screen Troubleshooting Users not matched between Scate and Device after apply Error stating FTP not available when retrieving or applying Admin Screen Troubleshooting Cannot Add a new APADC user Traffic Classification Troubleshooting No RDRs after pushing the traffic Some RDRs are not received RDRs are received with incorrect values for some parameters RDR File Troubleshooting No RDRs are received by the external entity No RDR files are generated The RDR files are not retrieved SNMP Troubleshooting Cannot get MIB values SNMP Troubleshooting on APADC SNMP agent is running but no MIB values are displayed on the Device Statistics pages Troubleshooting Specific Scenarios This module includes procedures that operators can use to troubleshoot issues when using the Cisco Network Enhanced Module for Application Performance Assurance (NME-APA) and the Cisco Application Performance Assurance Device Console (APADC). •Accessing the NME-APA module •ISR/NME-APA Platform Troubleshooting •APADC Application Troubleshooting •RDR File Troubleshooting •SNMP Troubleshooting Accessing the NME-APA module You can access the NME-APA module: •by telnet •through the ISR router •through a web-based application (APADC) APADC is the preferred method of access. How to Access the NME-APA Module via Telnet You can access the NME-APA module by Telnet. Step 1 Configure the IP address from the ISR router. Step 2 Telnet to the NME-APA module, to get the CLI login prompt. Step 3 Execute the CLI commands based on the level (5, 10, or 15) being enabled. The CLI debug commands can only be executed under level 15 (ROOT level). How to Access the NME-APA Module via the ISR Router You can access the NME-APA module through the ISR router. Step 1 Run the ISR session command, `service-module integrated-Service-Engine` <slot/0>session. (The term `shellConn` is used for referring to the NME-APA console.) All the engineering commands are used for debugging purpose. They should be used with care so that they do not interfere with live traffic. How to Access the NME-APA Module via APADC You can access the NME-APA module by APADC. Step 1 Click on the APADC icon on the desktop of the server. For the first-time login, use username: root, password: cisco. APADC Login Fails •First time login fails •Subsequent login fails First time login fails First time login (username: root, password: cisco) fails. Step 1 Verify that MySQL is correctly installed. Verify that the C:\ mysql-enterprise-5.0.44-win32\ folder exists. Step 2 Verfiy that the MySQL Windows service is running. Check under Windows services that SCAtE-MySQL is running. Step 3 Query the MySQL dbase. •username: scate •password: scate •dbase: scate •table: scate_user Step 4 Validate the table. Verify that a row exists in this table with: •username=root •password=Cisco Problem Persists If the problem persists, completely uninstall and reinstall APADC. Subsequent login fails Step 1 Verify that MySQL is correctly installed. Verify that the C:\ mysql-enterprise-5.0.44-win32\ folder exists. Step 2 Verfiy that the MySQL Windows service is running. Check under Windows services that SCAtE-MySQL is running. Step 3 Query the MySQL dbase. •username: scate •password: scate •dbase: scate •table: scate_user Step 4 Validate the table. Verify that a row exists in this table with username and password. Step 5 Try a different scate user login. Step 6 Go to Admin; delete and add the user that failed to login. Problem Persists If the problem persists, completely uninstall and reinstall APADC. Warning This will delete all of the saved data on the application. ISR/NME-APA Platform Troubleshooting •The NME-APA does not come up •The NME-APA does not power up •During installation of the NME-APA image, the NME-APA card does not come up •Cannot ping the NME-APA management interface from the ISR Router •Cannot Telnet to NME-APA management interface from other station •During installation of the NME-APA image, an error is received •The NME-APA does not see any diverted traffic The NME-APA does not come up Step 1 Verify that the NME-APA has a service-module IP address and default gateway configured on the ISR. The NME-APA does not power up Step 1 Verify that the NME-APA is firmly seated in the ISR slot and that the retaining screws are tightened. Step 2 Make sure the slot being used can support the NME-APA card. Step 3 Verify that you are not attempting to use an NME-APA-E3 card in an ISR 2800 or an NME-APA-E2 card in an ISR 3800. During installation of the NME-APA image, the NME-APA card does not come up Step 1 Check the IOS version on the ISR using the show version command. Step 2 Make sure that the IOS version supports the NME-APA card. Step 3 If the IOS version does not support the NME-APA card, update the ISR IOS image to a version that supports the NME-APA card. Cannot ping the NME-APA management interface from the ISR Router Step 1 Verify that there is a valid route to and from the NME-APA. (This might require a static route to the NME-APA on the ISR if the Integrated Service Engine interface is set to ip unnumbered.) Cannot Telnet to NME-APA management interface from other station Step 1 Verify that there is a valid route to and from the NME-APA. Step 2 Use the NME-APA ShellConn command i to see whether the telnetServer process is up and running. Step 3 If the telnetServer process is not running, leave the card in its current state for DEs to debug. During installation of the NME-APA image, an error is received During installation of the NME-APA image, the following error is received: Pycurl.error: invalid return value for write callback Error: Operation Aborted. Step 1 The package name has the wrong extension. Change the extension to .pkg. The NME-APA does not see any diverted traffic Step 1 From the ISR IOS CLI run `show running-config interface integrated-Service-Engine` <slot/0>. If `!SCE traffic-management Disabled` appears in the output, the NME-APA card is currently not enabled. Wait a few minutes and then try again. Also, verify that you have the correct card for this ISR model. Step 2 Make sure that traffic diversion is enabled on the designated interface. You should see that the configuration, service-module apa traffic-management monitor, is set to that interface. Step 3 Make sure that traffic is arriving from the designated interface. (Use the ISR IOS CLI `show interfaces` <fastEthernet or GigabitEthernet><slot><port>counters. The counters should increase when you pump the traffic. If there is no increase, the traffic is not getting to the ISR chassis.) Step 4 Use the NME-APA CLI `show interface fastEthernet 0/1 counters` to see whether traffic has been diverted to NME-APA from ISR. The output will indicate whether the packets are diverted to NME-APA or are discarded by NME-APA. APADC Application Troubleshooting •Connect Screen Troubleshooting •Device Configuration Screens Troubleshooting •Fault Management Screen Troubleshooting •Statistics Screen Troubleshooting •Installation Screen Troubleshooting •Traffic Management Screen Troubleshooting •Reporting Screen Troubleshooting •User Management Screen Troubleshooting •Admin Screen Troubleshooting •Traffic Classification Troubleshooting Connect Screen Troubleshooting •Cannot connect to "Available" device •Cannot disconnect a "Connected" device •Cannot add a device •Device stays "Offline" Cannot connect to "Available" device Step 1 Go to Admin >Admin User Management. Step 2 Verify that the logged-in scate user appears in the "User" column. Step 3 Verify that the NME-APA trying to connect is a "configured device" for the scate user. Step 4 Click on the device name in the "configured device" column. Step 5 Verify that the device user name is correctly configured and is the same as the username configured on the NME-APA (by Telnet). Step 6 If the problem persists, create a new user account on the device and use this account to connect to the device by configuring it under Admin >Admin User Management. Step 7 Click Help, to review integrated help for more details. Step 8 If the problem persists, report to Cisco Systems, Inc. Cannot disconnect a "Connected" device Step 1 Select the device and delete it. Step 2 Reset the device. Step 3 Click Help, to review integrated help for more details. Step 4 If the problem persists, report to Cisco Systems, Inc. Cannot add a device Step 1 Verify that there are no more than five devices already added to the APADC application. Step 2 If more than five devices are already added to the APADC application, delete an existing device to add a new device. Step 3 Verify the correct network address for the device to be added. Step 4 Click Help, to review integrated help for more details. Step 5 If the problem persists, report to Cisco Systems, Inc. Device stays "Offline" Step 1 Ping the device from the web server running APADC. Step 2 Restart the Tomcat Windows service from Windows Administrative Tools > Services. Step 3 Restart the application server. Step 4 Click Help, to review integrated help for more details. Step 5 If the problem persists, report to Cisco Systems, Inc. Device Configuration Screens Troubleshooting •Cannot access Device Configuration Screen •Device Configuration is erased •Apply fails •Retrieve fails Cannot access Device Configuration Screen Step 1 Verify that at least one device is in the "Connected" state. Step 2 Verify that the user role allows access to this screen. Refer to the SFS for details. Device Configuration is erased Step 1 Click Savebefore toggling to a different tab after making configuration changes. Step 2 Click Apply to commit configuration data to NME-APA. Step 3 Any configuration on a tab is lost if it is not saved before user moves to a different tab. Step 4 Click Help, to review integrated help for more details. Step 5 If the problem persists, report to Cisco Systems, Inc. Apply fails Step 1 Verify that the "Connected " device is still available and alive. Step 2 Click Help, to review integrated help for more details. Step 3 If the problem persists, report to Cisco Systems, Inc. Retrieve fails Step 1 Verify that the "Connected" device is still available and alive. Step 2 Click Help, to review integrated help for more details. Step 3 If the problem persists, report to Cisco Systems, Inc. Fault Management Screen Troubleshooting Notification is not received Step 1 Verify that the Notification is not suppressed: a. Go to the Fault Configuration screen. b. Look for the Notification ID for the missing notification. c. Verify that the Notification ID is present in the table. d. Check to see that the "Suppressed" column has the value "No", rather than "Yes". Step 2 Click "Refresh" . Step 3 Verify that NME-APA is sending a Notification. Step 4 Click Help, to review integrated help for more details. Step 5 If the problem persists, report to Cisco Systems, Inc. Statistics Screen Troubleshooting Statistics Screen Problems Step 1 All Statistics are accumulated via SNMP queries. See SNMP Troubleshooting on APADC. Installation Screen Troubleshooting •Install process fails with the error `Cannot connect to device' •Install process fails with the error "Image file type and file mismatch" Install process fails with the error `Cannot connect to device' Step 1 Ensure the Web user has credentials on the device as a level-15 user. (If the device user corresponding to the Web user has a level 0/5/10 credentials, the install process will fail.) Install process fails with the error "Image file type and file mismatch" The image file type selected for install (pqi or pqb) must have a filename extension of .pqi or .pqb . The files are not transferred from the user PC to the scate server if a filename mismatch occurs. (Further semantic checks are performed in the next stage of the process to verify that the image files are of the expected type.) Step 1 Verify that the installation file has the correct filename extension. Traffic Management Screen Troubleshooting Cannot apply TM configuration to device Step 1 Check the server log for a connection-related exception. 2007-07-25 11:09:11,929 INFO [http-8080-Processor20] com.pcube.apps.engage.Engage - Sending configuration to SCE ... connection to SCE failed: server refused connection: unable to open connections - max number of sessions exceeded com.pcube.apps.engage.ConnectionFailedException: server refused connection: unable to open connections - max number of sessions exceeded at com.pcube.apps.engage.Connection.login(Connection.java:414) at com.pcube.apps.engage.Engage.login(Engage.java:138) at com.cisco.scabb.servconf.mgmt.SCABB.login(SCABB.java:81) at com.cisco.scate.web.mgt.tm.ServiceConfigManager.applyServiceConfig(ServiceConfigManager.ja va:115) at com.cisco.scate.web.ui.tm.service.ClassTreeAction.showClassTree(ClassTreeAction.java:159) If there is such a connection-related exception and reapplying the TM config to the device still fails, the connection between the SCAtE server and the device is maxed out. Step 2 Restart the SCAtE server (Tomcat). Reporting Screen Troubleshooting •RDR retrieval ("RetrieveNow") fails •Can not "Activate" scheduled task •Cannot "Add" a scheduled task •RDR Retrieval continues to be in "In Progress" state •No "Last Retrieval" information is displayed •Report fails to generate output (PROCESS_ERROR) •Cannot create report instance •"Run report JPEG" is disabled for certain reports •Report results are empty •Report fails to generate output (PROCESS_ERROR) RDR retrieval ("RetrieveNow") fails Step 1 Verify that the "Connected " device is still available and alive. Step 2 Verify that it is possible to FTP to the NME-APA from the APADC server using the device username and password associated with the APADC user from the Admin screen. If this step fails, refer to Device Configuration Screens Troubleshooting and verify users configured on the device. Retrieval will fail if an FTP attempt is made with a username and password that do not exist on the NME-APA device. Step 3 Verify that enough hard-disk space is available on the APADC server. Can not "Activate" scheduled task Step 1 Verify that the task has not expired. if the start time is in the past, make sure that the difference between current time and the task start time is greater than the task recurrences times task interval. Step 2 Verify that the NME-AP device is still available and alive. Step 3 Verify that it is possible to FTP to the NME-APA from the APADC server using the username "admin" and enable15 password. If this step fails, refer to Device Configuration Screens Troubleshooting, and reconfigure the enable15 password on the device. Step 4 Verify that enough hard-disk space is available on the APADC server. Cannot "Add" a scheduled task Step 1 Verify that at least one NME-AP device is added to APADC. Step 2 Only one scheduled task can be added at a time. If there is a task, delete the task and try again. RDR Retrieval continues to be in "In Progress" state Step 1 Verify that the NME-AP device is still available and alive. Step 2 Verify that it is possible to FTP to the NME-APA from the APADC server using the username "admin" and enable15 password. Step 3 Verify that enough hard-disk space available on the SCAtE server If this step fails, refer to Device Configuration Screens Troubleshooting, and reconfigure the enable15 password on the device. Step 4 Check the server logs for OutOfMemory Errors. Restart the Tomcat server in the case of such errors. No "Last Retrieval" information is displayed Step 1 Verify that the <SCATE_ROOT_DIR>/scate-config/rdrloader.xml file exists and is not empty. Step 2 Try "RetrieveNow" to see if the information gets updated. If the information is notupdated, there could be problems retrieving data from the NME-APA. See RDR retrieval ("RetrieveNow") fails. Step 3 If there is a "Scheduled Task", make sure that it is still active. Report fails to generate output (PROCESS_ERROR) Step 1 Verify that report parameters do not contain invalid characters. Step 2 Open a command prompt, `cd` to the SCA Reporter folder and run the report command. The report command line can be found in the scate log. It should be as follows: reportercmd -o ../apache-tomcat-5.5.20/webapps/ROOT/report_results/Global_Bandwidth_per_IM_type[1]--NME-A PA--2007-Aug-01-13-23-58 -format jpeg -template "Global Bandwidth per IM type" -params "numhours=24;im_message_type=MSN TEXT;seip=10.6.1.19;starttime=;link=Link 1,Link 0;avgdata=false;units=Kbit/s;endtime=;trafficdir=Both Directions;" -dbuser scate -dbpassword scate -dburl "jdbc:mysql://localhost:3306/scateinfra" -dbdriver "com.mysql.jdbc.Driver" -policysce 10.6.1.19 Step 3 Remove all optional parameters and try again. Cannot create report instance Step 1 Traffic management configuration must be applied by APADC. Verify that the NME-APA TM was configured using the APADC. Verify that the scateinfra.INI_VALUES table in MySQL is not empty. Step 2 Verify that the "Last Retrieval" information (Device IP and time) on the Data Retrieval page is not "Unknown". Step 3 Verify that there is RDR data in the DB. If the DB is empty, go to the RDR Retrieval page and perform "RetrieveNow". "Run report JPEG" is disabled for certain reports Step 1 This behavior is by design. A few report types do not support the JPEG format and so "Run Report JPEG" is disabled. CSV reports can be generated for these report types. Report results are empty Step 1 Traffic management configuration must be applied by APADC. Verify that NME-APA TM was configured using the APADC. Verify that the scateinfra.INI_VALUES table is not empty in the MySQL database. Step 2 Verify that the "Last Retrieval" was done within the last 24 hours. Step 3 Verify that there is RDR data in the DB. Step 4 Verify that the APADC server time zone is set correctly. Report fails to generate output (PROCESS_ERROR) Step 1 Verify that the report parameters do not contain invalid characters. Step 2 Open a command prompt, `cd` to the SCA Reporter folder and run the report execution command. The report execution command line can be found in the scate log. Step 3 If the previous step successfully generates a report result, remove all optional parameters and try again. User Management Screen Troubleshooting Users not matched between Scate and Device after apply Step 1 Check the server log for errors after applying. Since the UM creates users by importing the whole list from Scate, there might be a conflict with the existing users. Error stating FTP not available when retrieving or applying Step 1 Try again. A new FTP connection to the device will be created to continue the operation. Admin Screen Troubleshooting The Admin Screen is used to: •Add/Edit/Delete new APADC users •Add/Edit/Delete new devices to APADC users •Program device username, password, and access-level to APADC users Cannot Add a new APADC user Step 1 Verify that the maximum number of APADC users (100) has not been reached. Traffic Classification Troubleshooting •No RDRs after pushing the traffic •Some RDRs are not received •RDRs are received with incorrect values for some parameters No RDRs after pushing the traffic Step 1 Make sure that traffic is diverted to NME-APA and not discarded by NME-APA. See The NME-APA does not see any diverted traffic. Step 2 Make sure that the packets are not filtered (bypassed or dropped) by NME-APA. Use the NME-APA CLI `debug slot 0 ppc 0 func RC_Cls` to keep track of the counters. If the numbers for `drop` or `bypass` increase after the traffic is sent, packets have been filtered. The `filtered traffic` from SCAtE is used to configure the flow filter. For example, DNS packets are bypassed by default, so no RDRs will be generated by DNS traffic. You can also use the CLI command, `debug slot 0 ppc 0 show-counters`. Step 3 Ensure that the line card is not shut down. Step 4 Make sure that the SML application is installed. Use the NME-APA CLI `show version` to see whether the information about SML application is displayed. Step 5 If the SML application is not installed, install the PQI file from the SCAtE. Step 6 Make sure that traffic is delivered to SML Application. Check the value of `Traversed PDUs` from the output of the NME-APA ShellConncommand, `debug slot 0 ppc 0 func sr`. If the value is 0, the SML application is not receiving traffic and no RDRs will be generated. In this case, it is possible that the traffic is not classified as a flow in SCOS. Turn on the debugging flag for the HwSim module. 1. Before you push traffic, enter the shellConn command, `LC_CS_on` 2. After the traffic is pushed, enter the ShellConn command, `LC_CS_off` Note This command should be used in a controlled environment; it may interfere with live traffic. The log is in the file `/root/tffs0/cs.txt`. Send this file to DEs for analysis. Step 7 Save the RDRs. The RDRs can either be saved to a file (default) or sent to an external entity such as the CM or rdrHandler. If the destination IP address of the RDR-Formatter is configured, the RDRs are sent to the external entity. Otherwise, they are saved to a file. See RDR File Troubleshooting for details. Some RDRs are not received Step 1 If the traffic has been processed by SML application, make sure that the corresponding RDRs are enabled in the service configuration. Check the RDR Settings in the SCAtE, make any necessary corrections, and apply the service configuration again. Use the NME-APA CLI `show running-config-application` to see whether the service configuration is applied. Note It may take some some time for the RDRs to be generated for certain traffic. For example, some RDRs for the UDP flows are generated at the close of the flow, which may take several minutes after the last packet of the traffic is sent. Step 2 Check that the correct CAP file is being used. If necessary, replace the cap file. Step 3 Check the setup for traffic generate tools such as kiwi. Make sure that kiwi is set up correctly. Step 4 Load a debug SML image to capture traces for the Protocol Library. Contact the DE team to see if you need to load an SML debug image and to find out which debug flags need to be turned on for this particular protocol or application. RDRs are received with incorrect values for some parameters Step 1 Check that the traffic contains the expected packets. Capture the packets and then examine them. Step 2 Compare the signature, protocol, and service ID values of the RDRs with the values in the table. Stop as many applications in the network as possible, in order to debug and see if any application generates conflicting traffic that causes the error. Record traffic and check the CAP files. Step 3 Load a debug SML image to capture traces for the Protocol Library. Contact the DE team to see if you need to load an SML debug image and to find out which debug flags need to be turned on for this particular protocol or application. Step 4 Load an SML debug image and turn on debug flags. If necessary, contact the DE team. Step 5 Look through the traces on the NME-APA to find the cause of the errors. RDR File Troubleshooting •No RDRs are received by the external entity •No RDR files are generated •The RDR files are not retrieved No RDRs are received by the external entity Step 1 Make sure that the configuration of the RDR-Formatter is correct (for instance, the IP address and the port number). Use the NME-APA CLI `show RDR-Formatter` to see whether the connection between the NME-APA and the external entity is up. If the connection is down, the RDRs are queued. Check the connection between NME-APA and the external entity. (Note that this is for debugging purposes only. The RDRs should be written to files in the normal case.) The same command will also show the number of RDRs being queued. If no RDRs are queued, refer to Traffic Classification Troubleshooting to see why no RDRs are generated. No RDR files are generated Step 1 Check if an IP address is configured for the RDR-Formatter. If no IP address is configured, the RDRs are queued in the buffers and will never be written to a file even if the connection is up. Step 2 Confirm that RDRs are being generated. Use the NME-APA CLI `show RDR-Formatter` to see whether the RDRs are queued. If no RDRs are queued, refer to Traffic Classification Troubleshooting to see why no RDRs are generated. Step 3 Use the ShellConn command, rdrShowSts, to see how much longer it has to wait before the RDRs are written to a file. By default, these RDRs are written to a file every 30 minutes. Step 4 After this time has elapsed, use the ShellConn command rdrShowAllFiles to see whether the file has been created. The ShellConn command, rdrHelp, provides a list of commands for debugging RDRs. The RDR files are not retrieved Step 1 Make sure that the ftp server is enabled. Use the NME-APA CLI `show ip ftp-server` to see whether the server is enabled. SNMP Troubleshooting •Cannot get MIB values •SNMP Troubleshooting on APADC Cannot get MIB values Step 1 Make sure that SNMP Agent is enabled. Use the NME-APA CLI `show snmp` to see whether SNMP Agent is enabled. If not, use the CLI `snmp enable` under configuration mode to enable it. Step 2 Check that the console displays `SNMP Server started`. If not, enter the ShellConn command `debugScripts 1` from the console, and then disable and enable SNMP Agent again. Step 3 Capture the communication between Agent and AgentX. Enter the ShellConn command `SNMP_Agentx_logging 0`. The logs are stored in the file `/root/tffs0/system/p3hidden/net-snmp/agentxDebug.log`. Send this file to DEs for analysis. Step 4 The ShellConn commands SNMP_AGENTX_Help and SNMP_AGENT_Help provide a list of commands for SNMP debugging. SNMP Troubleshooting on APADC SNMP agent is running but no MIB values are displayed on the Device Statistics pages Step 1 Use command line utilities like snmpget, snmpwalk, or a third party MIB browser to connect to the NME-APA and verify if you are able to view the MIB-II system group. Step 2 If you are not able to see the system group values, this indicates that the SNMP agent is not functioning properly. Step 3 If you are able to view the MIB-II system group as well as some tables such as user counters and package counters, the most likely problem is incorrect community strings. Step 4 If you are able to view MIB-II system group and snmp counters but not NME-APA counters such as user counters, package, and rdr counters, the problem lies with the subagent implementing the enterprise specific objects. Contact Cisco systems technical support with the relevant information.
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.