ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
cbs_flow_dump analysis for active flows
Article ID: 168542
Updated On:
Products
XOS
Issue/Introduction
This article describes how to collect cbs_flow_dump data on the NPM to analyze the traffic profile
Cause
In some scenarios, the traffic profile might be causing uneven flow distribution between NPMs.
Resolution
The cbs_flow_dump analysis will show the source and destination IPs for all current flows and a clear picture of the actual traffic profile.
Use these steps to collect the flow dump data from each NPM.
1. Collect the flow dump files from each NPM.
From the CPM Unix prompt execute the following commands:
2. The 'flowd_debug.log' file will be created in the CPM /tftpboot/npm6_X/cbs_flowd directory (where X is 1, 2, 3, or 4).
Make sure the /tftpboot/npm6_X/cbs_flowd/flowd_debug.log file is no longer increasing in size. In some cases this file can be bigger than 7Gb depending on the actual flow.
3. When the file stops growing rename it to avoid confusion
4. Provide the data to support for the analysis
Use these steps to collect the flow dump data from each NPM.
1. Collect the flow dump files from each NPM.
From the CPM Unix prompt execute the following commands:
# telnet npmX (where X is 1, 2, 3, or 4)
# cbs_query_flowd dump_flow_paths
# exit
2. The 'flowd_debug.log' file will be created in the CPM /tftpboot/npm6_X/cbs_flowd directory (where X is 1, 2, 3, or 4).
Make sure the /tftpboot/npm6_X/cbs_flowd/flowd_debug.log file is no longer increasing in size. In some cases this file can be bigger than 7Gb depending on the actual flow.
3. When the file stops growing rename it to avoid confusion
# mv flowd_debug.log npm1path.dat
4. Provide the data to support for the analysis
Feedback
Yes
No
Powered by
