cc/td/doc/product/rtrmgmt/nfc/nfc_3_0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for NetFlow FlowCollector Release 3.0 and Release 3.0 (2.0)

Release Notes for NetFlow FlowCollector Release 3.0 and Release 3.0 (2.0)

These release notes describe the features, enhancements, and caveats for Release 3.0 and
Release 3.0 (2.0) of NetFlow FlowCollector.

Contents

These release notes include the following topics:

Introduction

NetFlow FlowCollector provides fast, scalable, and economical data collection from multiple NetFlow export-enabled devices that include Cisco routers and Catalyst 5000 and Catalyst 6000 family switches. FlowCollector is a UNIX application supported on Solaris and HP-UX platforms. It:

FlowCollector is a key provider of time-based, granular data measurements to external applications. Service provider and enterprise customers can use FlowCollector as an integral component of their distributed data collection processes. Traffic accounting details gathered by FlowCollector will drive extensive new capabilities in the areas of network planning, accounting, billing, and network and application resource monitoring, with minimal impact on router performance and without extensive (and expensive) polling operations.

System Requirements

FlowCollector 3.0 operates with the following platforms:


Note To prevent NetFlow data export packet loss, the workstation should be dedicated to the NetFlow data export device (router or switch) and should not be running other applications.

FlowCollector requires at least 2 MB of disk space for its binary and configuration files.

FlowCollector generates output files containing aggregated data. These files require additional disk space; the exact amount depends on the flow arrival rate, collection interval, number of aggregation schemes specified, binary versus ASCII data file types, use of compression, and data file retention policies.

Device and IOS Release Support

NetFlow functionality is currently available with the following Cisco devices:


Note The NetFlow FlowCollector Installation and User Guide includes specific information relating to the Catalyst 5000. This information also applies to the Catalyst 6000.

See Table 1 to determine the compatibility among the different Cisco hardware platforms, Cisco IOS software releases, and NetFlow data export versions that are supported.


Table 1: NetFlow Data Export Compatibility Matrix
Cisco IOS Release Supported Cisco Hardware Platform(s) Supported NetFlow Export Version(s)

11.1 CA and
11.1 CC

Cisco 7200, 7500, and RSP7000

V1 and V5

11.2 and 11.2 P

Cisco 7200, 7500, and RSP7000

V1

11.2 P

Cisco Route Switch Module (RSM)

V1

11.3 and 11.3 T

Cisco 7200, 7500, and RSP7000

V1

12.0

Cisco 1720, 2600, 3600, 4500, 4700, AS5800, 7200, uBR7200, 7500, RSP7000, and RSM

V1 and V5

12.0 T

Cisco 1720, 2600, 3600, 4500, 4700, AS5800, 7200, uBR7200, 7500, RSP7000, RSM, MGX 8800 RPM, and BPX 8600

V1 and V5

12.0(3)T and later

Cisco 16001, 1720, 25001, 2600, 3600, 4500, 4700, AS5800, 7200, uBR7200, 7500, RSP7000, RSM, MGX8800 RPM, and BPX 8650

V1, V5, and V8

12.0(6)S

Cisco 12000

V1, V5, and V8

12.0(8)T

Cisco AS5300

V1, V5, and V8

---

Cisco Catalyst 5000 family switches with NetFlow Feature Card (NFFC)2

V7

---

Cisco Catalyst 6000 family switches with Multilayer Switching Feature Card (MSFC)

V7

1Support for NetFlow Export V1, V5, and V8 on Cisco 1600 and 2500 platforms is targeted for Cisco IOS Release 12.0(5)T. NetFlow support for these platforms is not available in the Cisco IOS 12.0 mainline release.
2
Multilayer Switching and NetFlow data export are supported in Catalyst 5000 family supervisor engine software Release 4.1(1) or later.

Installation Notes

The entire installation process is explained in detail in the NetFlow FlowCollector Installation and User Guide in Chapter 2, "Installing and Configuring FlowCollector." Installation troubleshooting information is located in the NetFlow FlowCollector Installation and User Guide in Appendix A, "Troubleshooting FlowCollector."

This section provides the following information:

Upgrade Paths

You can upgrade to FlowCollector 3.0 from any previous version of FlowCollector. Carefully read all prompts during installation to ensure that existing configuration and data files are processed appropriately.

Understanding Installation Modes

By default, FlowCollector 3.0 is installed in FlowCollector 2.0-compatible mode. This prevents potential problems with existing FlowCollector 2.0 installations. After installing FlowCollector, you can turn on all FlowCollector 3.0 features through the nf.resources file. See Chapter 2, "Installing and Configuring FlowCollector," in the NetFlow FlowCollector Installation and User Guide for complete installation details.

Performing a Quick Installation on a Solaris Platform

The following procedure shows an upgrade installation. If you are installing FlowCollector for the first time, the installation is basically the same, but with fewer prompts from the installation script (because there are no files from a previously installed version of FlowCollector). The installation script prompts you for responses to any required steps.


Note During an upgrade installation, existing configuration files and data files are detected and you are given the option of saving them with a .old extension.

To install FlowCollector on a Solaris platform, perform the following steps:


Step 1 Log in as root.

Step 2 Copy the NFC3_0.SOL.tar file from the distribution CD-ROM to a locally mounted directory such as /tmp on the workstation.

Step 3 Extract the FlowCollector files from the tar file.

# tar -xvf NFC3_0.SOL.tar 
 

Step 4 Run the installation script to begin the installation process.

# ./NFC3_0.setup.sh NFC3_0.SOL.Z 
 

Step 5 Follow the prompts as they appear.


Performing a Quick Installation on an HP-UX Platform

The following procedure shows an upgrade installation. If you are installing FlowCollector for the first time, the installation is basically the same as for an upgrade installation, but with fewer prompts from the installation script (because there are no files from a previously installed version of FlowCollector). The installation script prompts you for responses to any required steps.


Note During an upgrade installation, existing configuration files and data files are detected and you are given the option of saving them with a .old extension.

To install FlowCollector on an HP-UX platform, perform the following steps:


Step 1 Log in as root.

Step 2 Copy the NFC3_0.HP_11.tar file from the distribution CD-ROM to a locally mounted directory on the workstation.

Step 3 Extract the FlowCollector files from the tar file.

# tar -xvf NFC3_0.HP_11.tar
 

Step 4 Run the installation script to begin the installation process.

# ./NFC3_0.setup.sh NFC3_0.HP_11.Z 
 

Step 5 Follow the prompts as they appear.


Setting UNIX Environment Variables

Add the following environment variables to the startup files (.cshrc or .profile) of all users wanting to run the FlowCollector application. These environment variables identify the location of the FlowCollector directory structure and the nf.resources file:

For C shell users, the commands (using default installation values) are:

setenv NFC_DIR /opt/CSCOnfc
setenv NFC_RESOURCEFILE $NFC_DIR/config/nf.resources
 

For Bourne or Korn shell users, the commands (using default installation values) are:

NFC_DIR=/opt/CSCOnfc; export NFC_DIR
NFC_RESOURCEFILE=$NFC_DIR/config/nf.resources; export NFC_RESOURCEFILE

Running FlowCollector

To run FlowCollector, you can be logged in as a user or as root.

To run FlowCollector, perform the following steps:


Step 1 Log in.

Step 2 Start the FlowCollector application.

$ $NFC_DIR/bin/nfcollector start all
 

FlowCollector now runs as several processes.



Note Typically, FlowCollector is started and allowed to run until there is some reason to stop it. The NetFlow user interface (NFUI) is separate from FlowCollector and dependent on FlowCollector for current application statistics and resource definitions---such as for threads, filters, and protocols. Once FlowCollector is running, anyone can start the NFUI and use it to review application statistics and resource definitions or to create and modify FlowCollector resource definitions.

Stopping FlowCollector

To stop FlowCollector, perform the following steps:


Step 1 Log in.

Step 2 Enter the following command to stop the FlowCollector application.

# $NFC_DIR/bin/nfcollector stop all
 


Note To stop FlowCollector, you must be logged in as root or as the user who started this FlowCollector session.

Uninstalling FlowCollector

During installation, you are given the option of removing the existing version of FlowCollector before installing the new version. To permanently remove FlowCollector from a workstation, use the commands that are native to your operating system to remove FlowCollector files and directories.

New Features

The following list describes the new features in FlowCollector Release 3.0 and Release 3.0 (2.0) and includes a reference to the NetFlow FlowCollector Installation and User Guide where details on the new feature can be located.

New Features in Release 3.0

New Feature in Release 3.0 (2.0)

A new aggregation scheme named ASPort is included with Release 3.0 (2.0).

The output of the ASPort aggregation scheme consists of one record for each unique combination of source autonomous system number, destination autonomous system number, source source port, destination port, and protocol present in the flow data received by FlowCollector during the current collection period. Each output record contains the following fields:

Key fields: src_as, dst_as, srcport, dstport, protocol

Value fields:packet count, byte count, flow count

Important Notes

This section includes important information regarding the operation of FlowCollector 3.0.

When a FlowCollector workstation receives RawFlow data, FlowCollector always uses the same amount of disk space for that data regardless of the amount of RawFlow data that is received. Table 2 shows the maximum packet size of each datagram version. RawFlow data written by FlowCollector is a fixed size packet, depending on the version of the export datagram received, but regardless of the number of entries in the export flow packet. For example, if FlowCollector receives a V5 RawFlow datagram, it always writes 1464 bytes to disk; if it receives a V1 RawFlow datagram, it always writes 1168 bytes to disk, and so on.


Table 2: RawFlow Data Maximum Packet Sizes
Datagram Version Maximum Packet Size

V1

1168

V5

1464

V7

1428

V8 - RouterAS

1456

V8 - RouterProtoPort

1456

V8 - RouterSrcPrefix

1436

V8 - RouterDstPrefix

1436

V8 - RouterPrefix

1428

Caveats

This section includes the caveats known to exist in FlowCollector Release 3.0.


Note These caveats have been addressed in FlowCollector Release 3.0 (2.0).

Installing FlowCollector 3.0 over an existing FlowCollector 2.0 installation can prevent FlowCollector 3.0 from starting. Failure to start occurs when you choose to retain the log files that exist with FlowCollector 2.0. The FlowCollector 2.0 log files are owned by root, making them unwritable for the NFCollector processes whose effective user identification numbers (UIDs) are those of bin in version 3.0.
Workaround 1: Delete the nfc.log file that was created by FlowCollector 2.0 before installing FlowCollector 3.0.
Workaround 2: Rename the nfc.log file that was created by FlowCollector 2.0 before installing FlowCollector 3.0.
Workaround 3: Change ownership of the nfc.log file that was created by FlowCollector 2.0 before installing FlowCollector 3.0. For example, use the command :
    chown bin nfc.log
     
    
Workaround 4: Specify a different path for the NFCollector log file. Do this either during installation or by editing the nf.resources file after installation.
The nfc_bin_to_ascii utility does not work on binary files with the DetailCallRecord, ASHostMatrix, and HostMatrixInterface aggregation schemes.
Workaround: Download an updated copy of the nfc_bin_to_ascii utility from ftp-eng.cisco.com/ftp/NetFlow/fde/nfc_bin_to_ascii.
When installing Release 3.0 over Release 2.0, the original 2.0 configuration files are retained and a location for the NFCGW log file is not defined. Because of this, anytime a NFCGW event occurs, all log files are written to $NFC_DIR as nfcgwlog, as opposed to a specific log file directory location.
Workaround: Access the nf.resources.default file and look up the NFCGW_LOG entry. Add this entry to your existing nf.resources file.
The nfc_bin_to_ascii utility does not determine the delimiter from the header in the file, forcing users to pass the delimiter as a parameter to the nfc_bin_to_ascii utility.
Workaround: Download an updated copy of the nfc_bin_to_ascii utility from ftp-eng.cisco.com/ftp/NetFlow/fde/nfc_bin_to_ascii.
While installing FlowCollector on an HP-UX system, the installation script looks for a nonexistent directory named $NFC_DIR/doc.
Workaround. None. Ignore the following error message that appears:
    chmod: can't access /opt/CSCOnfc/doc
    /opt/CSCOnfc/doc: No such file or directory
    /opt/CSCOnfc/doc: No such file or directory

Documentation Updates

This section includes corrections, changes, and additions to the NetFlow FlowCollector Installation and User Guide that occurred after the guide was printed.

Corrections exist to the descriptions of some of the NetFlow export datagram formats located in Appendix B of the NetFlow FlowCollector Installation and User Guide. This section provides the old entries and the corrected entries.

Bytes Contents Old Description New Description

12-13

input

SNMP index of input interface

Interface index (ifindex) of input interface

14-15

output

SNMP index of output interface

Interface index (ifindex) of output interface

Table B-2 Version 1 Flow Record Format

Bytes Contents Old Description New Description

12-13

input

SNMP index of input interface

Interface index (ifindex) of input interface

14-15

output

SNMP index of output interface

Interface index (ifindex) of output interface

Table B-4 Version 5 Flow Record Format

Bytes Contents Old Description New Description

12-13

input

SNMP index of input interface; always set to zero.

Interface index (ifindex) of input interface; always set to zero.

14-15

output

SNMP index of output interface

Interface index (ifindex) of output interface

Table B-6 Version 7 (Catalyst 5000) Flow Record Format

Bytes Contents Old Description New Description

20-21

src_as

Source autonomous system number, either origin or peer; always set to zero

Source autonomous system number, either origin or peer

22-23

dst_as

Destination autonomous system number, either origin or peer; always set to zero

Destination autonomous system number, either origin or peer

24-25

input

SNMP index of input interface; always set to zero

Interface index (ifindex) of input interface

26-27

output

SNMP index of output interface

Interface index (ifindex) of output interface

Table B-8 Version 8 RouterAS Flow Record Format

Bytes Contents Old Description New Description

20

prot

IP protocol type (for example,
TCP = 6; UDP = 17); set to zero if flow mask is destination-only or source destination

IP protocol type (for example, TCP = 6; UDP = 17)

24-25

srcport

TCP/UDP source port number; set to zero if flow mask is destination-only or source-destination

TCP/UDP source port number

26-27

dstport

TCP/UDP destination port number; set to zero if flow mask is destination-only or source-destination

TCP/UDP destination port number

Table B-9 Version 8 RouterProtoPort Flow
Record Format

Bytes Contents Old Description New Description

24

dst_mask

Destination address prefix mask; always set to zero

Destination address prefix mask

26-27

dst_as

Destination autonomous system number, either origin or peer; always set to zero

Destination autonomous system number, either origin or peer

28-29

output

SNMP index of output interface

Interface index (ifindex) of output interface

Table B-10 Version 8 RouterDstPrefix Flow
Record Format

Table B-11 Version 8 RouterSrcPrefix Flow Record Format
Bytes Contents Old Description New Description

24

src_mask

Source address prefix mask; always set to zero

Source address prefix mask

26-27

src_as

Source autonomous system number, either origin or peer; always set to zero

Source autonomous system number, either origin or peer

28-29

input

SNMP index of input interface; always set to zero

Interface index (ifindex) of input interface

Table B-12 Version 8 RouterPrefix Flow Record Format
Bytes Contents Old Description New Description

28

src_mask

Source address prefix mask; always set to zero

Source address prefix mask

29

dst_mask

Destination address prefix mask; always set to zero

Destination address prefix mask

32-33

src_as

Source autonomous system number, either origin or peer; always set to zero

Source autonomous system number, either origin or peer

34-35

dst_as

Destination autonomous system number, either origin or peer; always set to zero

Destination autonomous system number, either origin or peer

36-37

input

SNMP index of input interface; always set to zero

Interface index (ifindex) of input interface

38-39

output

SNMP index of output interface

Interface index (ifindex) of output interface

Related Documentation

Refer to the following documents for additional NetFlow information:

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can reach CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.


Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package that ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.



hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Feb 3 20:16:12 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.