Noria Port Viewer: A Complete User’s Guide
Overview
Noria Port Viewer is a hypothetical (or unspecified) port monitoring and management tool for viewing port statuses, traffic, and device connections on networked systems. This guide assumes a typical feature set: live port status, historical logs, filtering, alerts, and basic configuration.
System requirements
- OS: Windows ⁄11 or Linux (Ubuntu 20.04+)
- CPU: Dual-core 2.0 GHz+
- RAM: 4 GB minimum (8 GB recommended)
- Storage: 200 MB application + space for logs
- Network: TCP/IP connectivity to monitored devices; SSH or SNMP access as required
Installation
- Download installer for your OS (choose 64-bit).
- Run installer with administrative privileges.
- During install, select default components: Core Viewer, SNMP plugin, Log Collector.
- Open firewall ports if prompted (typically TCP 8080 for web UI, SSH for device access).
- Start the Noria Port Viewer service/daemon.
First-time setup
- Launch the web UI at http://localhost:8080 or the desktop app.
- Create an admin account (strong password + 2FA if available).
- Add monitored hosts:
- Use IP address or DNS name.
- Choose access method (SNMP v2/3, SSH, API).
- Provide credentials or community strings.
- Configure polling interval (default 60s). Lower for near-real-time, higher to reduce load.
- Import or configure alert rules (thresholds, severity, notification channels).
Key features & how to use them
- Live Port Status
- View open/closed ports per host in the Hosts -> Ports view.
- Color codes: green=open, red=closed/filtered, yellow=unresponsive.
- Traffic and Throughput
- Select a host and open the Traffic tab to see Mbps, packet rates, and peak times.
- Use time-range selector to inspect last 1h/24h/7d.
- Logs & Historical Data
- Access Logs -> Port Events to search by host, port, or time.
- Export CSV for auditing.
- Filtering & Search
- Use filters to show only TCP/UDP, specific port ranges, or service names (e.g., 80/http).
- Alerts & Notifications
- Create alert: condition (e.g., port 22 closed), severity, frequency.
- Notification channels: email, webhook, Slack. Test each after creation.
- Dashboards & Reports
- Build a dashboard with widgets: Top open ports, Alert count, Bandwidth per host.
- Schedule daily/weekly PDF reports.
Common workflows
- Daily check
- Open Dashboard.
- Scan red/yellow items.
- Review Alerts for critical changes.
- Troubleshoot a closed port
- Confirm host connectivity (ping/SSH).
- Check firewall rules and local service status.
- Review Logs -> Port Events for recent changes.
- Re-scan the host from Noria.
- Onboard a new site
- Add host with credentials.
- Assign to a group (e.g., Datacenter A).
- Apply baseline alert policy and dashboard.
Best practices
- Use SNMPv3 or SSH where possible for secure access.
- Keep polling interval balanced: 30–120s for most networks.
- Limit log retention for storage control; archive old logs.
- Restrict admin UI access with IP allowlists and 2FA.
- Test alert delivery regularly.
Troubleshooting
- Web UI not loading: ensure service running, check port (8080), verify firewall.
- Hosts show as unresponsive: verify credentials, network routes, and device ACLs.
- Missing historical data: check Log Collector service and disk space.
- False alerts: tune thresholds and add suppression windows.
Exporting & integration
- Export formats: CSV for logs, PDF for reports, JSON for API queries.
- Integrations: SIEM (via webhook), ticketing systems (Jira/ServiceNow), Slack/MS Teams.
Security considerations
- Encrypt communications (TLS) for web UI and API.
- Rotate credentials and SNMP community strings periodically.
- Limit user roles — give least privilege necessary.
Example quick commands (CLI)
- Start service:
Code
# Linux systemd sudo systemctl start noria-port-viewer
- Check status:
Code
sudo systemctl status noria-port-viewer
- Trigger a re-scan for host 10.0.0.5:
Code
noriactl rescan –host 10.0.0.5
Further reading
- View built-in help (Help -> Documentation in app).
- Use API docs at http://localhost:8080/api-docs for automation.
Leave a Reply