Member Avatar for tennymatt

Hi all,
I am a reseller for ISPs in my locality and do point tot point installation for clients who happen to be very critical and needs it running 24/7. Please is there a way i could monitor my clients who are not in thesame class as the one in my office but in a far distant area who are using point to point link and Vsat links respectively. attached is a diagrammatic view of the scenario
I have workers stationed in these states to do a quick repair or maintenance of the link but i can't monitor the links and wouldn't know wen the link is out until my clients calls. Sometimes is false claims to claim damages or exaggerated claims as well. So to be able to defend myself and see things clearly for myself i have decided to monitor the links without disruptting their day to day operation and do this visually on the display monitor.
Almost thesame applies to Vsat. I have Vsat links that i have deployed for different ISP so i manage them or do maintenance on them. I want to be able to monitor these Vsat links from my office and know when they are down. the Vsat links are on different ISPs and different IP Class.
Please i really need a hand here because i dont know what to do anymore.

Thanks,

Matthias

Monitoring.jpg 106.73 KB
  • 2 Contributors
  • 4 Replies
  • 100 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by tennymatt

Dani AI

Generated

Two practical architectures will solve the problem reliably: run a small outbound “agent/proxy” at each site that reports into a central monitoring server, or create a secure site-to-center tunnel so the central system can poll. The agent/proxy approach is usually simplest across multiple providers because the remote device initiates a single encrypted outbound connection (no inbound holes needed) and can send heartbeats, interface counters, modem signal metrics and syslog entries back to the office.

Implementation checklist:

  • Pick an NMS that supports active/proxy mode (agents or probes that push data). Install the probe on the customer edge box or a tiny local host (low-cost Linux box or appliance).
  • Monitor items: interface operational state, interface error/collision counters, traffic rates, and device-specific MIBs for the access modem (signal-to-noise, BER, carrier alarms). Store graphs and event timestamps so you can prove historical uptime.
  • Alerts: require short confirmation windows and multi-check logic (avoid a single transient alert). Use escalation rules and include exact timestamps and graphs in notifications to counter disputed claims.

Operational and security notes:

  • Use authenticated, encrypted transport (SNMPv3, TLS or the agent’s built-in encryption). Avoid opening management ports on remote firewalls unless absolutely necessary.
  • Centralize logs (syslog) and SNMP traps so outages are correlated with carrier-side events; keep retention long enough to support dispute investigations.
  • For remote recovery, consider an out-of-band path (cellular or a small backup modem) to allow console access when the primary link is down.

This approach addresses the reachability question raised by and gives a defensible, timestamped record of link behavior for technicians and customers.

Recommended Answers

All 4 Replies

Member Avatar for HITMANOF44th

are these ip addresses wan ips ? and can they be pinged from a wan source ?

Member Avatar for tennymatt

they are WAN ip addresses. From a WAN source, you mean?

Member Avatar for HITMANOF44th

yes like you can access them on the internet or see them from the internet

Member Avatar for tennymatt

thats if they are public IPs u mean? some Vsat links could be pinged from the internet but the point tp point can not.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.