Pando Smart Alerting

Pando Smart Alerting

PAR Logo (1).jpeg

Alert Name: Basic Alert

Purpose:

A DAS is configured with a wide variety of alarms - many of which don’t impact service coverage. Depending on the users NOC strategy(alert grouping, alert pipeline, etc.) individual basic alerts may not result in a ticket being created. However, it’s best practice to, at a minimum, record each for historical review.

Trigger Conditions:

  • DAS throws an alarm

Severity:

☐ Critical  ☐ High  ☐ Medium  ✅ Low

Alert Philosophy:

Every alert a DAS is capable of producing is captured, stored, and visualized. This includes critical failures, warnings, informational events, transient alarms, and self-clearing conditions. Recording all alerts ensures complete system visibility, preserves operational history, and enables meaningful trend analysis over time.


Alert Name: ICMP Alert

Purpose:

PAR™ sends ICMP requests to all monitored systems every minute to check in and ensure they are responsive and remain connected. This alert signifies an issue with this network request.

Trigger Conditions:

  • Network latency is high from PAR™ to the DAS, DAS is offline from our network or the SNMP agent on a device is down

Severity:

☐ Critical  ☐ High  ✅ Medium  ☐Low

Alert Philosophy:

ICMP alerting exists to provide visibility into overall system and site reachability. A DAS or device may become unreachable for a variety of reasons including network outages, cellular service disruptions, routing changes, or device-level communication failures such as SNMP service interruption.


Alert Name: Remote Communication Alert

Purpose:

Remote unit communication is a key indicator of overall DAS health and system uptime. Monitoring remote communication allows us to detect when a portion of a DAS begins experiencing connectivity or operational issues.

Alerting on degraded remote communication provides early visibility into potential coverage, capacity, or equipment performance issues before they escalate into broader system outages.

Trigger Conditions:

  • Over 10% of DAS’ remotes stop being reported to PAR.

Severity:

☐ Critical  ✅ High  ☐ Medium  ☐Low

Alert Philosophy:

Remote units can fail or become unreachable in several ways that may contribute to DAS performance degradation or downtime. This alert is designed to detect when a remote experiences communication loss or becomes physically disconnected from the DAS.

When a remote is no longer communicating with the headend, there is a potential loss or degradation of RF output at that remote location, which may result in reduced coverage, capacity limitations, or complete service outage within that coverage area.


Alert Name: Inventory Alert

Purpose:

This alert is generated when a DAS stops reporting a portion of its expected inventory. Monitoring inventory reporting allows us to detect when system components are no longer visible to the monitoring platform and helps quantify the percentage of the DAS that is not communicating.

This visibility supports early identification of partial system failures, communication issues, or configuration changes that may impact overall system performance and uptime.

Trigger Conditions:

  • Over 10% of DAS' total inventory stop being reported by a device.

Severity:

☐ Critical  ☐ High  ✅ Medium  ☐Low

Alert Philosophy:

Native DAS alarms do not always reflect the full scope or severity of an issue. For example, if a BIU becomes disconnected in a Solid Alliance system, the DAS may generate only a single alarm even though a significant portion of the system may be offline.

This alert compares a device’s expected baseline inventory against the inventory currently being reported. By evaluating the difference, it provides a more accurate representation of the true scale and impact of an issue.


Alert Name: DAS Uptime Alert

Purpose:

If a significant portion of active amplifiers on a system are in alarm that indicate they are not functioning properly, this alarm will fire.

Trigger Conditions:

  • DAS' active amplifiers are throwing alarms determined to be DAS uptime impacting.

Severity:

☐ Critical  ✅ High  ☐ Medium  ☐Low

Alert Philosophy:

Alarms generated by remotes or the amplifiers within those remotes may indicate degraded or failed operation that directly impacts DAS uptime and RF coverage. When amplifiers are in alarm, the affected coverage area may experience reduced or lost service proportional to the number of amplifiers impacted.

Rather than evaluating these alarms individually, this alert aggregates alarms classified as “DAS uptime impacting” (as defined in the Alarm Settings page). The alert triggers when the volume of active alarms indicates that a significant portion of the DAS is degraded or offline, based on the number of active amplifiers within the system.

 


Alert Name: Carrier Uptime Alert

Purpose:

This alert is triggered when a significant portion of active carrier signal inputs on a system generate errors indicating degraded or failed operation.

Trigger Conditions:

  • DAS' active carrier inputs are throwing alarms determined to be carrier uptime impacting.

Severity:

☐ Critical  ✅ High  ☐ Medium  ☐Low

Alert Philosophy:

Carrier input alarms indicating degraded or failed operation contribute directly to carrier uptime, as they may result in reduced RF coverage or capacity depending on the number of affected inputs.

Rather than evaluating these alarms individually, this alert aggregates alarms classified as “carrier uptime impacting” (as defined in the Alarm Settings page). The alert triggers when the volume of active alarms indicates that a significant portion of carrier signals are degraded or offline, based on the estimated number of active carrier inputs within the DAS.