Home > Cloud Cruiser 4 > Collecting, transforming, and publishing > Network Traffic > Limitations

Limitations

Table of contents
No headers

The CCR output generated by the Network Traffic Collector is completely dependent on the NetFlow records it receives and the amount of data it is able to extract from them. The following is a list of known limitations:

  • The NetFlow data must be in Version 9 format.

  • NetFlow records must contain the fields IPV4_SRC_ADDRIPV4_DST_ADDR, and IN_BYTES.

  • IN_BYTES must be a 32-bit or 64-bit field.
    The NetFlow v9 default is 32-bit.
  • Exported CCRs are representative of the NetFlow records that could be successfully parsed. This means that if the NetFlow generator is using a sample-based algorithm to create the DataFlow records, the CCRs only reflect the output of that sampling.

  • Only one attempt is made to push an exported CCR to the Cloud Cruiser REST API. If this fails, the failure is logged, but a manual process is required to perform the data transfer to Cloud Cruiser​. A Perl script is provided for this purpose.

  • Due to a limitation in the Cloud Cruiser REST API it is not possible to push data for any day other than the current day.

  • Timestamps in the CCR file are always generated using the system clock on the server running the collector.

  • Usage is only reported against the IP addresses contained in the NetFlow records. If the router generating these records is outside a NAT gateway, the IP addresses in the CCR file are post-NAT. In such cases, you must establish​ a means of correlating these post-NAT addresses to internal tenants or VMs as part of your deployment process.

  • Spaces are not currently supported in the cc_username or cc_password configuration item values.

Last modified

Tags

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP