Table Of Contents

Starting and Stopping Cisco Multi NetFlow Collector

The Main MNFC Components

The cscomnfc Script

The mnfc Script

Starting and Stopping the MNFC Storage Manager

Starting and Stopping the MNFC Database

Starting and Stopping Cisco Multi NetFlow Collector

---

This chapter describes how to start and stop the Cisco Multi NetFlow Collector application and then validate that it is operating properly. It includes the following sections:

•The Main MNFC Components

•The cscomnfc Script

•The mnfc Script

•Starting and Stopping the MNFC Storage Manager

•Starting and Stopping the MNFC Database

The Multi NetFlow Collector server contains number of processes which are expected to remain up and running without interruption 24/7 unless there is a need to perform a system maintenance. It also needs its database server (Informix IDS 9.40 relational database) to remain operational.

The Main MNFC Components

The Multi NetFlow Collector is implemented in Java and includes the following processes executed in separate instances of JVM:

•Storage Manager (or nfcdb) executed with userid informix

•Process Watcher

•Concentrator

•Web GUI process (as Tomcat by Apache with web application mnfc)

•Report Daemon

•VPN MIB Collector

•CLI Collector

Storage Manager is the only process executed with user id informix.All other processes are executed with user id nfcuser. See Table 1 for information about MNFC component processes.

Table 1 MNFC Component Processes 

Short Name	Full Name	Purpose	UNIX User ID*	Default Presence**	Log Properties file in config directory
nfcdb	Storage Manager	Run-time maintenance of nfc_db database in IDS	informix	Mandatory	mnfcdb-log4j
pw	Process Watcher	Running of all processes except Storage Manager	nfcuser	Mandatory	mnfcpw-log4j
concentrator	Concentrator	MNFC back-end server	nfcuser	Mandatory	mnfc-log4j
web	Web GUI	Tomcat with mnfc webapp, MNFC front-end server	mfcuser	Mandatory	mnfcweb-log4j
rd	Report Daemon	Execution of reports	nfcuser	Mandatory	mnfcrd-log4j
vpnmibcltr	VPN MIB Collector	SNMP-based collection of CE-CE data	nfcuser	Optional	vpnmibcltr-log4j
clicollector	CLI Collector	CLI Collector	nfcuser	Optional	clic-log4j

* Instead of nfcuser, another id can be designated by the operator executing MNFC installation.

** With exception of Storage Manager and Process Watcher the presence flag is configurable via the Process Watcher's controls.

The cscomnfc Script

The script cscomnfc is intended as a single invocation point for starting up or shutting down all MNFC processes, including those executed using user ids informix and nfcuser. Run this script as the user root. When running this script, you must use either the start or stop parameter.

The location of the cscomnfc script is under /opt/CSCOmnfc/bin or $MNFC_DIR/bin.

The mnfc Script

The script mnfc is intended for starting and stopping of MNFC processes executed by Process Watcher using user if nfcuser. The script accepts mandatory verb parameter start, stop, shutdown, and status. If you use start or stop, then a second parameter is needed. Use the short name for the MNFC process. For a listing of MNFC processes, see Table 1.

When starting and stopping all MNFC processes for the id nfcuser, you must use the following:

•For starting: mnfc start all

•For stopping: mnfc shutdown

The location of the mnfc script is under /opt/CSCOmnfc/bin or $MNFC_DIR/bin.

Starting and Stopping the MNFC Storage Manager

To start the MNFC storage manager, as user informix enter the shell command startnfcdb.sh.

To stop the MNFC storage manager, as user informix enter the shell command stopProcess.sh nfcdb.

The location of the startnfcdb.sh and stopProcess.sh script is under /opt/CSCOmnfc/bin or $MNFC_DIR/bin.

Starting and Stopping the MNFC Database

Before the Informix database is shutdown or restarted, the Multi NetFlow Collector application must be shutdown.

For information on operating the Informix server, refer to IDS 9.40 documentation by IBM.