User Guide for the Cisco NetFlow Generation Appliance
Troubleshooting
Downloads: This chapterpdf (PDF - 410.0KB) The complete bookPDF (PDF - 1.16MB) | Feedback

Troubleshooting

Table Of Contents

Troubleshooting

Reading the LEDs

Front-Panel LEDs

Built-In NIC LEDs


Troubleshooting


This appendix includes

Troubleshooting Tips, Table A-1

Reading the LEDs

Table A-1 Troubleshooting Tips 

Problem Description 
What to Check?
What Should You Do?

Cisco NetFlow Generation Appliance does not appear in your collectors list of NetFlow devices.

Is the SNMP community string configured to the same value on both the collector and Cisco NGA?

Check your collector documentation to find out what community string it is using. Choose Administration > System > SNMP Agent to set the same community string (or use the CLI command snmp community <string> ro|rw).

Cannot enable flow monitor.

Are there error messages indicating any missing components?

Execute the command show debug messages and look for diagnostic messages.

Ensure you configure the missing component and include it in the flow monitor configuration using Advanced Setup or CLI.

Are there any other flow monitors active in the system?

Enter show flow monitor and check the cache size assigned to the already activated monitors. Ensure the total cache size is less than 100%.

Are there already four flow monitors activated?

Deactivate one of the flow monitors to allow a new one to become active.

User interface layout behaves strangely, or content does not change when navigating to a different menu area.

Are you using a supported browser and version?

Ensure that your browser version is supported.

Has your browser session timed out?

Click your browser's Refresh button and log in again if prompted to do so.

Is stale data cached in your browser?

Clear your browser cache and restart the browser.

No NetFlow data is reaching the collector (collector side).

Is the Cisco NGA sending data on the same UDP port that the collector is listening on?

Consult your collector documentation to determine which UDP port it is listening on. Use the GUI or CLI to modify the collector configuration with the same UDP port number. By default, the value is 3000 on Cisco NGA. Third party collectors may listen on a different UDP port.

Was the collector application properly installed and configured?

Check your collector and see your collector user documentation for verification. Check the collector configuration to ensure it is accurate.

Is Cisco NGA reachable from the collector server?

Use ping to ensure the collector and IP addresses successfully reach each other. If they are unreachable, check your network connection and configuration.

Does SPAN traffic forward to the switch ports that are connected to the data ports?

On the Nexus switch console, check the SPAN configuration. Read the interface counters and ensure traffic is being forwarding to the collector.

Is the collector reachable from the appliance?

Use ping to check the collector IP address. If ping does not work, check your network connectivity and configuration.

Is the collector listening to the correct UDP port?

Ensure the collector is listening to the same UDP port that is configured in the flow collector.

Is SPAN traffic received by the appliance?

On the console, run show dataport statistics rate and ensure there is sufficient traffic arriving at the connected data ports. If not, check the traffic source on the switch side (SPAN configuration, physical network connections between the switch and device. Run show dataport statistics cumulative and check for packet drops.

If there are many namelookup connection issue messages, disable name resolution from the UI, clear the browser cache, and see what is the result for the span page.

Does traffic get passed to the cache engine?

On the console, run show cache statistics rate monitor_name and ensure the cache engine is processing traffic. You can run show cache statistics cumulative monitor_name to check for packet drops. If the Packet Dropped (no record) counter is high and continues to increase, ensure the defined flow record type is compatible with the incoming traffic type.

Does the exporter export NetFlow data?

On the console, run show collector statistics collector_name and ensure no flow traffic was dropped and that flow rates are sufficient.

Did you wait long enough?

Check Cache Active Timeout configuration. The default setting is 30 minutes and if SPAN traffic is slow, this may take up to 30 minutes to export some NetFlow data. For quick verification, we recommend you edit the cache active timeout to 60 seconds to enable the appliance to export NetFlow data more often.

Is your filtering configured correctly?

On the console, run show flow filters and show flow records to ensure filtering fields are in the record.

The power LED on the front panel is not on.

Is the AC power cord connected properly?

If the power LED is still off, the problem might be a power supply failure.

The appliance shuts down after being on for only a short time.

Check for an environmentally induced shutdown (see the "Reading the LEDs" section).

Check the fans. If the fans are not working, the appliance will overheat and shut itself down.

Ensure that the appliance intake and exhaust vents are clear.

If the fans are not working, you might need to check the power supply connections to the fans.

Check the environmental site requirements in the "Maintain Your Appliance" section.

The appliance partially boots, but the LEDs do not light.

Check for a power supply failure by inspecting the power LED on the front panel of the appliance. If the LED is on, the power supply is functional.

If the LED is off, refer to the Cisco Information Packet for warranty information or contact your customer service representative.

Power supply shuts down or latches off.

Check to see if the fan has failed, the air conditioning in the room has failed or airflow is blocked to cooling vents.

Take steps to correct the problem. For information about environmental operating conditions, see Cooling.

Adapter card is not recognized by the appliance.

Make sure that the adapter card is firmly seated in its slot.

Check the LEDs on the adapter card. Each adapter card has its own set of LEDs. For information on these LEDs, see the "Reading the LEDs" section.

Make sure that you have a version of software that supports the adapter card.

For information, see the documentation that was included with your adapter card.

Adapter card is recognized, but interface ports do not initialize.

Make sure that the adapter card is firmly seated in its slot.

Check external cable connections.

Make sure that you have a version of software that supports the adapter card. Refer to the documentation that was included with your adapter card.

For information, see the documentation that was included with your adapter card.

The appliance does not boot properly, or it constantly or intermittently reboots.

Make sure that the adapter card is firmly seated in its slot.

Check the appliance chassis or the application software.

For information, see the documentation that was included with your adapter card.

For warranty information, see the Cisco Information Packet publication that shipped with your appliance or contact your customer service representative.

If you are using the console port with a terminal, and the appliance boots but the console screen is frozen.

Check the external console connection.

Verify that the parameters for your terminal are set as follows:

(a) The terminal should have the same data rate that the appliance has (9600 bps is the default).

(b) 8 data bits.

(c) No parity generated or checked.

(d) 1 stop bit.

 

The appliance powers up and boots only when an adapter card is removed.

Check the adapter card. There might be a problem with the adapter card. Refer to the documentation that was included with your adapter card.

For warranty information, refer to the Cisco Information Packet publication that shipped with your appliance or contact your customer service representative.

The Cisco NAM appliance powers up and boots only when a particular cable is disconnected.

There might be a problem with the cable.

For warranty information, see the Cisco Information Packet publication that shipped with your appliance or contact your customer service representative.

Cannot locate the product serial ID on the Cisco NGA.

Before you submit a request for service online or by phone, use the CPI tool to locate your product serial number.

This tool offers three search options:

Search by product ID or model name

Browse for Cisco model

Copy and paste the output of the show command to identify the product

On the Cisco NAM appliance, the serial number label is located on the right-hand corner above the RJ-45 serial connector on the front of the appliance.


Reading the LEDs

The Cisco NetFlow Generation Appliance LEDs serve the following purposes:

Indicate that basic power is available to the appliance

Guide you to a broken adapter card, or to one that has failed its diagnostics

Give an indication that traffic is flowing through the adapter card to the appliance

The LEDs on the front panel of the Cisco NAM appliance and corresponding adapter card are aids for determining appliance and adapter performance and operation.

This section contains:

Front-Panel LEDs

Front-Panel LEDs

Front-Panel LEDs

Figure 1 depicts the Cisco NGA front panel. Table 2 describes the appliance LEDs.

Figure 1 Front Panel Cisco NGA

3

Operations panel LEDs, left to right:

System status LED

Fan status LED

Temperature status LED

Power supply status LED

Network activity LED

5

Power button/LED. Use only when a forced shutdown is necessary. Hold down for several seconds until light is no longer lit with a green color.

4

Identification button/LED

   

Table 2 Front-Panel LEDs 

LED
Color
State
Description

Operations panel LEDs, left to right (location 3):

System status LED

Fan status LED

Temperature status LED

Power supply status LED

Network activity LED

Green

On

Standby or ready for operation

Green

Blinking

Traffic occurring

Amber

On

One or more critical fault conditions

Amber

Blinking

One or more noncritical fault conditions

Appliance Status
(location 4)

Green

On

Standby or ready for operation

Green

Blinking

Traffic occurring

Amber

On

One or more critical fault conditions

Amber

Blinking

One or more noncritical fault conditions

Appliance Power (location 5)

Green

On

Power on

Off

Off

Power off


Built-In NIC LEDs

Figure 2 shows the NIC 1 and NIC 2 LEDs located on the rear of the appliance. These LEDs indicate the connection activity and speed of the NIC ports. Table 3 describes the activity and connection speed associated with each LED state.

Figure 2 NIC 1 and NIC 2 LEDs

Table 3 NIC 1 and NIC 2 LED Descriptions 

LED
Color
State
Description

Left (location 1)

 

Off

No network connection

Green

Solid

Network connection

Green

Blinking

Transmit/receive activity

Right
(location 2)

 

Off

10-Mb/s connection (if left LED is on or blinking)

Green

Solid

100-Mb/s connection

Amber

Solid

1000-Mb/s (or 1-Gb/s) connection