StableNet Express vs StableNet: Which Is Right for Your Organization?

Troubleshooting Common Issues in StableNet Express

1. Connectivity problems

• Symptom: Devices not appearing or frequent disconnections.
• Quick checks: Verify device IP, SNMP/SSH credentials, and network reachability (ping/traceroute).
• Fixes: Restart the StableNet Express service, confirm firewall rules allow required ports (SNMP ⁄₁₆₂, SSH 22, HTTP/HTTPS), and adjust SNMP community strings or SNMPv3 credentials.

2. Device discovery failures

• Symptom: Discovery scan completes with no devices or incomplete inventory.
• Quick checks: Ensure discovery range is correct and credentials are valid. Check for rate-limiting on target devices.
• Fixes: Expand discovery credentials (SNMP, SSH, WMI), lower discovery concurrency, whitelist the appliance in device ACLs, and review discovery logs for specific errors.

3. Incorrect or missing metrics

• Symptom: Missing interface stats, CPU/memory, or misreported values.
• Quick checks: Confirm device supports the OIDs or APIs queried and that SNMP access is permitted.
• Fixes: Update MIB support or add custom OIDs, enable relevant telemetry on devices (e.g., NETCONF, RESTCONF), and verify polling intervals and time ranges.

4. Alerting and notification issues

• Symptom: Alerts not firing or notifications not sent.
• Quick checks: Validate alert rules, test notification channels (email, webhook), and inspect the notification queue.
• Fixes: Correct rule thresholds or scopes, reconfigure SMTP/webhook settings, ensure credentials and endpoints are reachable, and clear/backfill any stuck notification backlog.

5. Performance and scalability bottlenecks

• Symptom: UI sluggishness, long load times, or high CPU/memory on the appliance.
• Quick checks: Check system resource utilization, database size, and number of monitored objects.
• Fixes: Increase allocated resources (CPU, RAM, disk I/O), archive old data, optimize polling intervals, and scale horizontally if supported (add collectors).

6. Database and storage errors

• Symptom: Errors writing to DB, corrupt data, or storage full.
• Quick checks: Monitor disk usage and DB connection health, review DB logs for errors.
• Fixes: Increase disk capacity, run DB maintenance (vacuum/cleanup), restore from recent backup if corruption occurs, and verify DB user permissions.

7. UI or dashboard rendering issues

• Symptom: Dashboards fail to load or show stale data.
• Quick checks: Confirm backend services are running and API endpoints return data.
• Fixes: Restart the web service, clear browser cache, update to latest client patches, and rebuild dashboard indices if available.

8. License and activation problems

• Symptom: Features disabled or license warnings.
• Quick checks: Verify license validity and system time synchronization.
• Fixes: Reapply license file/key, contact vendor for license issues, and ensure NTP is configured so license checks succeed.

9. Integration and API failures

• Symptom: External integrations (CMDB, ticketing) failing.
• Quick checks: Test API endpoints and credentials, review integration logs.
• Fixes: Update API tokens/keys, ensure correct endpoint URLs, retry failed jobs, and check for schema/version mismatches.

10. Upgrade and patching issues

• Symptom: Failed upgrades or post-upgrade regressions.
• Quick checks: Review upgrade logs and pre-upgrade compatibility notes.
• Fixes: Restore from backup, follow vendor upgrade guide, apply patches in staging first, and open a support ticket if upgrade fails.

Troubleshooting workflow (recommended)

1. Reproduce the issue and collect timestamps.
2. Gather logs (application, discovery, polling, integration).
3. Check resources (CPU, memory, disk, network).
4. Isolate components (collector, DB, web).
5. Apply targeted fix from the list above.
6. Validate the fix and monitor for recurrence.
7. Document root cause and remediation.

If you want, I can create a printable checklist or a step-by-step runbook tailored to your StableNet Express version.