How to Use DataOne Bandwidth Usage Finder — Formerly DataOne Tool

How to Use DataOne Bandwidth Usage Finder — Formerly DataOne Tool

This guide shows a clear, step-by-step workflow to locate and analyze bandwidth usage with DataOne Bandwidth Usage Finder (formerly DataOne Tool). It assumes you have access to the tool and basic network permissions. Follow each section for setup, usage, interpretation, and common troubleshooting.

1. What the tool does

• Purpose: Detect and report bandwidth consumption per device, application, or subnet.
• Outputs: Real-time usage, historical graphs, top talkers, protocol breakdowns, and exportable reports.

2. Prerequisites

• Network access with permission to query routers/switches or span ports.
• Credentials for any devices monitored (SNMP, SSH/API).
• A host (server or VM) meeting the tool’s system requirements (CPU, RAM, storage) — typically light-weight.
• Optional: Access to your monitoring database (InfluxDB, Prometheus) or visualization tool (Grafana) if integrating.

3. Installation (quick)

1. Download the latest package from your internal software repository or the official distribution.
2. On the host, unpack and run the installer:
   • Linux (example):

     Code
     Copy CodeCopied
     sudo tar -xzf dataone-bandwidth-*.tar.gz -C /opt/ sudo /opt/dataone/install.sh 

3. Start the service:

   Code
   Copy CodeCopied
   sudo systemctl enable –now dataone-bandwidth 

4. Open the web UI at http://:8080 and log in with provided admin credentials.

4. Initial configuration

• Add monitored devices: In the UI, go to Devices → Add Device. Enter IP, SNMP version/community or SSH/API credentials, polling interval.
• Define interfaces: Select which interfaces to track (e.g., eth0, Gi0/1) and set speed if not auto-detected.
• Set retention and granularity: Configure how long to keep metrics and sampling frequency (e.g., 1 min samples, 90 days retention).
• Alerting: Configure thresholds for bandwidth usage and set notification channels (email, webhook, Slack).

5. Running a basic bandwidth scan

1. From the dashboard, click Start Scan or New Scan.
2. Choose target scope: Single device, IP range, or subnet.
3. Select scan type:
   • Quick: Top talkers in last hour.
   • Full: Per-host and per-protocol analysis over selected range.
4. Set time range and start. Scan progress shows live discovered hosts and traffic counters.

6. Interpreting results

• Top talkers: Ranked list of IPs/hosts by bytes transferred. Use this to identify heavy consumers.
• Protocol breakdown: Pie or bar chart showing traffic by protocol (HTTP, HTTPS, SMB, etc.).
• Interface utilization: Percentage of link capacity used; sustained high utilization indicates contention.
• Historical graphs: Time-series plots for throughput, packets, errors — look for spikes, trends, and recurring patterns.
• Exports: CSV/JSON export for offline analysis or import into BI tools.

7. Common use cases and examples

• Identify a sudden spike: Filter by time window covering the spike, view top talkers, and inspect process/application tags.
• Capacity planning: Use 95th percentile reports over ⁄₉₀ days to estimate required link upgrades.
• Security triage: Unusual protocol use or unexpected external endpoints can indicate compromise—export flow details and correlate with firewall logs.

8. Best practices

• Poll at 60–300 second intervals for a balance of detail and storage.
• Use SNMP counters or flow exports (NetFlow/IPFIX) where available for accuracy.
• Keep retention for raw high-resolution data short (30–90 days) and store aggregated metrics longer.
• Tag devices with roles (user-lab, servers, DMZ) to simplify filtering.
• Schedule regular scans and automated alerts for threshold breaches.

9. Troubleshooting

10. CLI usage (example commands)

• Start a scan:

  Code
  Copy CodeCopied
  dataone scan start –target 192.0.2.0/24 –type full –duration 1h 

• List devices:

  Code
  Copy CodeCopied
  dataone devices list 

• Export top talkers:

  Code
  Copy CodeCopied
  dataone export toppers –device-id 12 –format csv –out top-talkers.csv 

11. Integrations

• Grafana for dashboards (use provided data source plugin).
• SIEM for security alerts (send exported flow records).
• Automation via webhooks or API for incident workflows.

12. Quick checklist before major analysis

• Ensure device credentials and SNMP/flow exports are configured.
• Confirm sampling interval and retention are appropriate.
• Validate time synchronization across devices (NTP).
• Backup configuration and export last 7 days of raw data.

If you want, I can produce a shorter quick-start checklist or a ⁄₉₀-day capacity planning template based on your environment size.