How NetMapAir Improves Network Visibility and Troubleshooting

NetMapAir: The Complete Guide to Features and Setup

What is NetMapAir

NetMapAir is a network mapping and monitoring tool designed to visualize, document, and troubleshoot network infrastructures. It automatically discovers devices and connections, displays topology maps, and provides status indicators for quick assessment of network health.

Key Features

• Automatic Discovery: Scans networks via SNMP, ICMP, LLDP, and ARP to find devices and links.
• Topology Mapping: Generates layered maps (physical, logical, VLAN, wireless) with drag-and-drop editing.
• Real-Time Status: Live status indicators (up/down, latency, packet loss) and historical trends.
• Customizable Alerts: Threshold-based alerts via email, SMS, or webhook integrations.
• Device Inventory: Detailed device records including vendor, model, firmware, interfaces, and serial numbers.
• Multi-Site Support: Aggregate maps and per-site views for distributed networks.
• Role-Based Access: User roles and permissions for secure team collaboration.
• Integration APIs: REST API and syslog/NetFlow ingestion for external tools and automation.
• Reporting & Export: PDF/CSV exports of maps, inventories, and uptime reports.
• Cloud & On-Prem Options: Available as SaaS or self-hosted appliance.

System Requirements and Supported Protocols

• Server: 4+ CPU cores, 8–16 GB RAM (scale up for large networks), 200 GB storage.
• Clients: Modern browsers (Chrome, Edge, Firefox).
• Protocols: SNMP v1/v2c/v3, ICMP, LLDP, CDP, ARP, NetFlow, sFlow, syslog, SSH.

Installation and Setup (Self-Hosted)

1. Prepare Server: Provision a Linux server (Ubuntu 22.04 or CentOS 8) with recommended CPU, RAM, and disk.
2. Install Dependencies: Ensure Java, PostgreSQL, and required libraries are installed (follow vendor docs for exact packages).
3. Download NetMapAir: Obtain the latest package from vendor portal and verify checksum.
4. Database Setup: Create PostgreSQL database and user; run schema migrations included with the installer.
5. Install Application: Run installer or deploy container image; configure systemd service for automatic startup.
6. Network Access: Open required ports (web UI, API, SNMP) and allow SNMP/ICMP probing from the server.
7. Initial Login: Access web UI, create admin account, set base URL and email server for alerts.
8. License Activation: Apply license key if required.

Quick Start: Adding Your First Site and Devices

1. Create Site: In the UI, add a site with location, IP range(s), and SNMP credentials.
2. Add Credentials: Enter SNMP community strings or SNMPv3 credentials and SSH keys if needed.
3. Start Discovery: Launch discovery for the site’s IP ranges; monitor progress and resolve any credential errors.
4. Review Topology: Open generated map, verify device placement, and adjust links or groupings with drag-and-drop.
5. Tag & Categorize: Apply tags (e.g., core, edge, wireless) and device roles for filtering and reports.
6. Set Alerts: Configure thresholds for interface utilization, latency, and device availability; assign notification channels.

Best Practices for Configuration

• Use SNMPv3 where possible for secure device polling.
• Limit Discovery Scopes to known IP ranges to avoid long scans and false positives.
• Maintain Credential Vault and rotate SNMP/SSH credentials regularly.
• Organize with Tags and Sites to simplify management of large estates.
• Enable Backups of the application configuration and PostgreSQL database.
• Integrate with Monitoring (Prometheus, SIEM) via the REST API or syslog for consolidated alerting.

Troubleshooting Common Issues

• No Devices Found: Verify network reachability (ping), SNMP credentials, and firewall rules allowing SNMP/ICMP to the server.
• Incomplete Topology: Ensure LLDP/CDP enabled on switches; check SNMP walk permissions for interface data.
• Slow Discovery: Narrow IP ranges, increase server resources, or run discovery during low-traffic windows.
• Alert Flooding: Raise thresholds, add maintenance windows, or create alert suppression rules for planned changes.

Integrations and Automation

• REST API: Automate device onboarding, export inventories, and query topology programmatically.
• SIEM/ITSM: Forward syslog and alerts to SIEMs or create incidents in ticketing systems via webhook integrations.
• NetFlow/sFlow: Ingest flow data to correlate traffic patterns with topology.
• Configuration Management: Link with tools like Ansible for inventory-driven automation.

Security Considerations

• Restrict UI and API access via VPN or IP allowlists.
• Use HTTPS with a trusted certificate and enable HSTS.
• Apply least-privilege roles and audit user activity.
• Regularly update the application and underlying OS for patches.

Maintenance and Scaling

• Monitor database growth and archive old logs/reports.
• Scale vertically (CPU/RAM) or horizontally (read replicas) for large environments.
• Use external object storage for map and report archives.
• Schedule regular backups and test restore procedures.

Conclusion

NetMapAir provides automated discovery, rich topology visualization, and integrations for operational workflows. Follow secure deployment practices, use SNMPv3, organize with sites/tags, and automate via APIs to get the most value from the platform.