Docs home
Company Admin — NOC Enable and operate the full ISP NOC Monitor
EN বাংলা

Company Admin — NOC

Enable and operate the full ISP NOC Monitor

Opt-in NOC suite for every company—dashboard, topology, NetFlow, BGP, live wall, security, alerts and Telegram. Off by default until you enable it.

Step-by-step With screens EN
Enable and operate the full ISP NOC Monitor

Portal

Company Admin → NOC Monitor (same suite is available under Zone/POP Admin when your role can open those panels). Base path: /noc-monitor.

Prerequisites

  • Company staff login with permission to change NOC Settings.
  • At least one reachable MikroTik (API/management IP) you already use for billing/RADIUS.
  • Optional: Telegram bot token + chat ID for the NOC group.
  • Optional network ingress (when the API host is reachable): NetFlow UDP 2055, syslog UDP 5514, SNMP traps UDP 1620—only collected for companies that enable NOC.
Important

NOC Monitor is available to every company but stays OFF by default (company setting noc_enabled). Until you enable it, the sidebar shows only NOC Settings—no collectors, NetFlow, syslog or SNMP ingest run for that company.

1. Enable NOC for your company

  1. Open NOC Monitor → NOC Settings.
  2. Turn on the master Enable NOC Monitor checkbox (it saves immediately).
  3. After refresh, the full NOC sidebar appears (Dashboard, Topology, NetFlow, BGP, Alerts, …).
  4. Leave NOC off on tenants that do not need collectors—this keeps noise and ingest load off those companies.
NOC Settings — master enable plus Telegram bot / chat
NOC Settings — master enable plus Telegram bot / chat

2. Register MikroTik routers and target IPs

  1. NOC Monitor → MikroTik Routers → Add. Enter management IP, credentials and a clear label (core / edge / POP).
  2. Use Test / connect to confirm RouterOS API before relying on live charts.
  3. NOC Monitor → Target IPs → add ICMP/host probes for upstream gateways, critical NAS management IPs and any VIP customer CPE you want on the morning board.
  4. Optional: IP Pool library for quick picks when adding targets.

3. Connect Telegram alerts

  1. NOC Monitor → Telegram Settings (also mirrored on NOC Settings).
  2. Paste bot token and chat/group ID. Send a test message.
  3. Enable notify-on-loss if you want scheduled ping loss to hit the channel.
  4. During planned work, use Maintenance windows so the channel is not flooded.
Telegram Settings — bot token, chat ID and notify-on-loss
Telegram Settings — bot token, chat ID and notify-on-loss

4. Daily ops views

  1. Dashboard — router health, bandwidth KPIs, open alerts and probe status.
  2. Topology — map how devices hang together for triage.
  3. Looking Glass — ping / traceroute / DNS from a selected MikroTik.
  4. Live wall — multi-router ~2s charts for the NOC screen.
  5. Interfaces & SFP — RX/TX, errors and optical power per interface.
  6. Queue Monitor — live MikroTik queue pressure.
NOC Dashboard — device health, interfaces and live traffic
NOC Dashboard — device health, interfaces and live traffic
Live wall — multi-interface Mbps at a glance
Live wall — multi-interface Mbps at a glance
Topology — how core / edge devices hang together
Topology — how core / edge devices hang together

5. Traffic intelligence

  1. NetFlow — top talkers from Traffic Flow / NetFlow v5/v9/IPFIX (point exporters at the neXor API host :2055 when NOC is on).
  2. NetFlow apps — port/app breakdown from the same flows.
  3. Online heat-map — where online density concentrates.
  4. Link capacity — utilization and 95th-percentile style capacity views.
  5. Customer impact — which subscribers sit behind a flapping link or device.
NetFlow — top sources / destinations after Traffic Flow export to :2055
NetFlow — top sources / destinations after Traffic Flow export to :2055

6. Routing, path and websites

  1. BGP Status — live sessions from a selected MikroTik.
  2. BGP uplink watch — uplink/BGP watch insights for morning checks.
  3. Path probes — latency/path matrix between important points.
  4. Website Monitor — HTTPS/service URL checks for portals and payment hosts.
  5. VPN Manager and DNS — VPN session/config and DNS ops via router-ops where configured.
BGP Status — live sessions from a selected MikroTik
BGP Status — live sessions from a selected MikroTik

7. Telemetry, config and history

  1. Syslog — search ingested router syslog (UDP 5514 when NOC is on).
  2. SNMP traps — traps plus OLT/device inventory hooks (UDP 1620).
  3. Config drift — compare live RouterOS against backups.
  4. Config backups — .rsc export archive with checksum/retention.
  5. Time Machine — historical router state at a chosen timestamp.
  6. Ping Logs — history of NOC ping checks.

8. Security, alerts and reporting

  1. Security — firewall and security event views.
  2. Mitigation — review/approve DDoS mitigation proposals.
  3. DDoS / SLA (anomaly) — bandwidth/PPS anomalies, guidance and short-window SLA.
  4. Alert Rules — define when incidents fire.
  5. Alerts & Incidents — acknowledge and resolve.
  6. Maintenance — silence windows for planned work.
  7. Reports — SLA reports, CSV export and complaint draft helpers.
Alerts & Incidents — acknowledge and resolve from one queue
Alerts & Incidents — acknowledge and resolve from one queue

Module map

  1. NOC Settings · Dashboard · Topology · Looking Glass · Interfaces & SFP · Queue Monitor
  2. NetFlow · NetFlow apps · BGP Status · BGP uplink watch · Live wall · Online heat-map · Link capacity · Customer impact
  3. Syslog · SNMP traps · Path probes · Config drift · Website Monitor · VPN Manager · DNS · IP Pool
  4. Security · Mitigation · DDoS / SLA · Alerts & Incidents · Alert Rules · Maintenance
  5. Time Machine · Config backups · Reports · Target IPs · MikroTik Routers · Telegram Settings · Ping Logs

Verify

  • After enable, sidebar lists the full module set (not Settings alone).
  • A registered router shows health on Dashboard / Live wall.
  • A test target failure (or test Telegram) reaches the NOC chat, then restores cleanly.
  • Planned maintenance silences noise; alerts resume after the window.

If it fails

  • Only Settings visible → NOC is still off; enable under NOC Settings and refresh.
  • 403 / empty collectors → feature still disabled for that company, or staff lacks permission.
  • No Telegram → wrong bot token/chat ID, or the bot was never started in the group.
  • False downs → probe interval too aggressive, ICMP blocked, or wrong management IP.
  • No NetFlow/syslog/SNMP data → exporters not pointed at the API host, wrong UDP ports, or NOC still off (ingest is company-scoped).