SBC - Session Border Controller
Overview
Cisco Unified Border Element (CUBE) provides the session-border function for SIP routing, carrier handoff, and media anchoring. Inventory uses cube and cube8kv roles.
Monitoring
Method
Prometheus SNMP Exporter plus sbc-exporter API collection through network-prometheus.
Metrics Collected
- SIP trunk and dial-peer state
- Call, session, and response-code indicators
- Interface, CPU, memory, and media resource health
- Exporter and scrape health
Grafana Dashboards
- WxCDI CUBE Detail — expected by the audit; the dashboard link is not yet recorded.
Logging
Log Source
CUBE/SBC devices forward network syslog and SNMP traps.
Splunk Index
network_syslog for syslog and snmp_traps for traps.
Key Log Queries
index=network_syslog device_type="cube" node_type IN ("cube","cube8kv") device_name="<device_name>"
Alerting
Grafana Alert Rules
| Alert Name | Severity | Description |
|---|---|---|
| CUBE/SBC health | Varies | SIP, session, interface, and resource conditions. |
| Scrape-down coverage | Gap | The audit currently records this control as disabled. |
Splunk Alerts
| Alert Name | Severity | Description |
|---|---|---|
| CUBE/SBC SIP events | Varies | Voice-edge events from network_syslog. |
Notification Flow
SBC → Grafana/Splunk → EMS (KeepHQ) → [notification channels]
Inventory
- Repository: csr-cube-inventory
- Update Method: Generated from the managed CSR/CUBE Ansible inventory.
- Update Cadence: On inventory change through pull request.