4c5003f9fc
- Update OLLAMA_URL from 192.168.178.169 to https://ollama.fichtmueller.org - Fix port from 3100 to 3103 (3100 was taken by Docker proxy on Erik) - Fix DATABASE_URL password to llm_secure_2026 - Add GITEA_URL env var for ban list sync - Add 35 prompt templates: TIP (10), EO Global Pulse (8), SwitchBlade (9), PeerCortex (3), internal (3), ShieldX (1), general (1)
147 lines
6.3 KiB
YAML
147 lines
6.3 KiB
YAML
id: sb_bandwidth_report
|
|
version: "1.0.0"
|
|
task_type: sb_bandwidth_report
|
|
description: Convert interface traffic statistics into a bandwidth utilization report with capacity planning recommendations
|
|
model_preference: qwen2.5:14b
|
|
model_minimum: qwen2.5:7b
|
|
temperature: 0.4
|
|
max_tokens: 2000
|
|
output_format: markdown
|
|
|
|
system_prompt: |
|
|
You are a network capacity planning analyst for SwitchBlade infrastructure management.
|
|
Convert interface traffic statistics into a clear bandwidth utilization report with actionable capacity planning recommendations.
|
|
|
|
Structure (always use these sections):
|
|
|
|
## Bandwidth Utilization Report: {{report_period}}
|
|
Generated: {{current_date}}
|
|
|
|
## Executive Summary
|
|
2-3 sentences: overall utilization health, critical findings, immediate actions needed.
|
|
|
|
## Interface Utilization Summary
|
|
Table: Interface | Link Speed | 95th Percentile In | 95th Percentile Out | Peak In | Peak Out | Utilization % | Status
|
|
|
|
## Critical Interfaces (>80% utilization)
|
|
Detail analysis for interfaces approaching capacity.
|
|
|
|
## Traffic Trends
|
|
Growth trends per interface: daily/weekly/monthly growth rate.
|
|
Projected date of capacity breach (if >80% trend).
|
|
|
|
## Peak Time Analysis
|
|
When do peaks occur? Day of week, time of day patterns.
|
|
|
|
## Capacity Planning Recommendations
|
|
Specific, actionable recommendations ranked by urgency.
|
|
|
|
## Capacity Planning Timeline
|
|
Projected upgrade needs with estimated dates.
|
|
|
|
Rules:
|
|
- Use exact numbers from the input data
|
|
- 95th percentile is the standard metric for interface utilization — use it
|
|
- Critical threshold: >80% 95th percentile utilization
|
|
- Warning threshold: >60% 95th percentile utilization
|
|
- Growth rate: extrapolate from historical trend in data
|
|
- Recommendations must be specific: "Upgrade et-0/1/2 from 10G to 100G" not "consider upgrading"
|
|
- Current date: {{current_date}}
|
|
|
|
user_template: |
|
|
Device: {{device}}
|
|
Report period: {{report_period}}
|
|
|
|
Interface statistics:
|
|
{{interface_stats}}
|
|
|
|
Historical trend data:
|
|
{{trend_data}}
|
|
|
|
Generate bandwidth report:
|
|
|
|
few_shot_examples:
|
|
- user: |
|
|
Device: core-router-01.fra
|
|
Report period: March 2026
|
|
|
|
Interface statistics:
|
|
et-0/0/0 (10G uplink to transit-A):
|
|
95th pct in: 7.8 Gbps | 95th pct out: 6.2 Gbps | peak in: 9.1 Gbps | peak out: 8.4 Gbps
|
|
et-0/0/1 (10G uplink to transit-B):
|
|
95th pct in: 2.1 Gbps | 95th pct out: 1.8 Gbps | peak in: 3.2 Gbps | peak out: 2.9 Gbps
|
|
et-0/1/0 (100G core to dist-01):
|
|
95th pct in: 18.4 Gbps | 95th pct out: 22.1 Gbps | peak in: 29.8 Gbps | peak out: 34.2 Gbps
|
|
|
|
Historical trend data:
|
|
et-0/0/0: 6.1 Gbps (Jan), 7.0 Gbps (Feb), 7.8 Gbps (Mar) — 95th pct in, monthly avg
|
|
et-0/1/0: 14.2 Gbps (Jan), 16.3 Gbps (Feb), 18.4 Gbps (Mar) — 95th pct in, monthly avg
|
|
assistant: |
|
|
## Bandwidth Utilization Report: March 2026
|
|
Generated: 2026-04-02
|
|
|
|
## Executive Summary
|
|
et-0/0/0 (transit-A uplink) is at 78% 95th percentile utilization — approaching the 80% critical threshold within approximately 5 weeks at current growth rate. The 100G core link (et-0/1/0) shows 34% outbound utilization — healthy, but growing at 15% per month. Immediate action: evaluate transit-A upgrade path before June 2026.
|
|
|
|
## Interface Utilization Summary
|
|
|
|
| Interface | Speed | 95th % In | 95th % Out | Peak In | Peak Out | Util % (max) | Status |
|
|
|---|---|---|---|---|---|---|---|
|
|
| et-0/0/0 (transit-A) | 10G | 7.8 Gbps | 6.2 Gbps | 9.1 Gbps | 8.4 Gbps | 91% | CRITICAL |
|
|
| et-0/0/1 (transit-B) | 10G | 2.1 Gbps | 1.8 Gbps | 3.2 Gbps | 2.9 Gbps | 32% | OK |
|
|
| et-0/1/0 (core dist-01) | 100G | 18.4 Gbps | 22.1 Gbps | 29.8 Gbps | 34.2 Gbps | 34% | OK |
|
|
|
|
## Critical Interfaces (>80% utilization)
|
|
|
|
**et-0/0/0 — transit-A uplink (10G)**
|
|
95th percentile inbound: 7.8 Gbps (78% of link capacity). Peak inbound: 9.1 Gbps (91% — bursts are saturating the link). The interface is already dropping packets during peak hours. Growth rate: +0.85 Gbps/month average over Q1 2026.
|
|
|
|
At this rate, 80% 95th percentile is breached in approximately 3 weeks (late April 2026).
|
|
|
|
## Traffic Trends
|
|
|
|
| Interface | Jan 95th % | Feb 95th % | Mar 95th % | Monthly Growth | Capacity Breach |
|
|
|---|---|---|---|---|---|
|
|
| et-0/0/0 | 6.1 Gbps | 7.0 Gbps | 7.8 Gbps | +0.85 Gbps/mo | ~April 2026 |
|
|
| et-0/1/0 | 14.2 Gbps | 16.3 Gbps | 18.4 Gbps | +2.1 Gbps/mo | ~Nov 2027 |
|
|
| et-0/0/1 | (no trend data) | | | — | No risk |
|
|
|
|
## Peak Time Analysis
|
|
|
|
Based on the peak values, et-0/0/0 reaches near-saturation during peak hours. The 10G transit link to transit-A is the immediate bottleneck. No peak time breakdown was provided in the input data — recommend enabling per-hour traffic logging for granular analysis.
|
|
|
|
## Capacity Planning Recommendations
|
|
|
|
**1. URGENT — Upgrade et-0/0/0 transit-A circuit to 100G (or 10G LAG)**
|
|
The link breaches 80% in approximately 3-5 weeks. Options:
|
|
- Request 100G upgrade from transit-A provider (preferred, future-proof)
|
|
- Immediately: traffic-engineer to shift load to et-0/0/1 (transit-B has 68% headroom)
|
|
- Short-term: enable ECMP load balancing between transit-A and transit-B to buy 4-6 weeks
|
|
|
|
**2. Monitor et-0/1/0 core link — no action yet**
|
|
100G core link at 34% outbound utilization is healthy. At 15% monthly growth, the 80% threshold is approximately 19 months away (November 2027). Plan 100G LAG or 400G upgrade in 2027 budget.
|
|
|
|
**3. Enable hourly traffic sampling on all critical interfaces**
|
|
Current data does not include time-of-day breakdown. Hourly data would identify specific peak windows and enable more targeted traffic engineering.
|
|
|
|
## Capacity Planning Timeline
|
|
|
|
| Action | Urgency | Target Date |
|
|
|---|---|---|
|
|
| Traffic-engineer load shift to transit-B | Immediate | This week |
|
|
| Request 100G upgrade from transit-A provider | Urgent | April 2026 |
|
|
| et-0/0/0 100G cutover | High | June 2026 |
|
|
| et-0/1/0 capacity review | Medium | Q3 2027 |
|
|
|
|
variables:
|
|
- device
|
|
- report_period
|
|
- interface_stats
|
|
- trend_data
|
|
- current_date
|
|
- few_shot_examples
|
|
|
|
validation_rules:
|
|
output_format_check: markdown
|
|
required_sections: ["Executive Summary", "Interface Utilization Summary", "Capacity Planning Recommendations"]
|