Table Of Contents

Troubleshooting the Multi NetFlow Collector

Solving Multi NetFlow Collector Problems

Troubleshooting the Multi NetFlow Collector

---

This appendix provides helpful information and procedures in case you encounter problems while using Cisco Multi NetFlow Collector (MNFC).

Solving Multi NetFlow Collector Problems

This section discusses some basic problems that you might encounter while attempting to run Multi NetFlow Collector.

---

Symptom Licensing errors in /opt/CSCOmnfc/logs/mnfc.log.

Possible Cause Either the license file is missing or invalid; or system hostname and address information is not configured properly on the host.

Recommended Action

1. Determine the following:

–The host IP address

–The license file contents in the /opt/CSCOmnfc/config/mnfc.lic file

–The /etc/hosts file content

–The result of running the hostname command.

2. Verify that the IP address matches the mnfc.lic line HOSTID=INTERNET=ipaddress. If not, the license file is not valid for this host.

3. Verify that the hostname is set, determined from the results from the hostname command, and is some value other than localhost, localhost.localdomain, etc.

4. Verify that the /etc/hosts file contains an entry for this hostname, and that the IP address in the entry is the same IP address in the mnfc.lic file. Also verify that the loopback address 127.0.0.1 in the /etc/hosts file does not contain this hostname, which is the default for Red Hat Enterprise Linux.

---

Symptom Unable to login to the web UI with a general error message on the login screen about checking for errors in collector log files.

Possible Cause A licensing or configuration error has prevented the collection process from starting, and the concentrator process must be running for the user to log in.

Recommended Action

1. Check the log files for errors

–On the Linux platform: grep -e ERR -e WARN -e FATAL /opt/CSCOmnfc/logs/mnfc.log

–On the Solaris platform: enter /usr/xpg4/bin/grep to specify multiple -e options

2. If you find a licensing error, see the licensing symptom and Recommended Action above.

3. If you find a configuration error, you need to fix the error by editing the XML file, and then restarting the concentrator process.

---

Symptom The script configuredb.sh fails to start Informix; the file /opt/informix/online.log has information on shared memory failure similar to the following:

11:38:42 IBM Informix Dynamic Server Started.

11:38:42 Contiguous shared memory segment allocation failed at 0x44000000.

Allocation successful at 0x19658000.

Check SHMBASE is consistent with the value in $INFORMIXDIR/etc/onconfig.std.

If you are using the correct SHMBASE value in your ONCONFIG file, then consider this message informational only.

11:38:46 OS couldn't allocate first resident segment at SHMBASE (0x8539ed0).

Possible Cause On certain Linux platforms the default value of SHMBASE set to 0x44000000 is taken by other libraries or utilities.

Recommended Action Set the SHMBASE to a value of 0xB000000L in the file $MNFC/db/config/onconfig-Linux.nfc and then re-run the configuredb.sh script.

---