Network Discovery Best Practices

Time to complete: 45 minutes (reading) + implementation time

Difficulty: Intermediate to Advanced

Prerequisites: Connect app installed, network access


Overview

Valethon Connect discovers devices on customer networks using multiple protocols. This guide covers configuration, optimization, and troubleshooting for comprehensive network discovery.


Discovery Protocols

Connect uses several protocols to build a complete picture:

ProtocolLayerDiscoversRequirements
ARP Scan2Active hostsSubnet access
SNMP7Device detailsCommunity string
CDP/LLDP2Network topologyManaged switches
DNS7HostnamesDNS server access
WMI7Windows detailsDomain credentials
NMOS7Broadcast AVIS-04 registry
Dante7Audio networkmDNS/DNS-SD

Initial Setup

Step 1: Define Subnet Ranges

In Connect settings, specify which subnets to scan:


# Common configurations
192.168.1.0/24      # Single /24 subnet
10.0.0.0/16         # Large corporate network
172.16.0.0/12       # Full private range (careful!)

# Multiple specific subnets
192.168.10.0/24     # Management VLAN
192.168.20.0/24     # User VLAN
192.168.100.0/24    # Server VLAN

Best Practice: Start with known subnets. Expand gradually.

Step 2: Configure SNMP

SNMP provides the richest device information.

Read-Only Community Strings:


public          # Default (often disabled)
monitoring      # Common alternative
{company}ro     # Company-specific

Add community strings in Connect → Discovery Settings → SNMP.

SNMP Versions:

VersionSecurityRecommendation
v1NoneAvoid if possible
v2cCommunity stringAcceptable for isolated networks
v3Auth + encryptionRecommended for production

Step 3: Enable Topology Protocols

For network mapping, enable CDP/LLDP discovery:

Note: Requires managed switches with CDP/LLDP enabled.


Discovery Modes

Continuous Discovery

Runs discovery at regular intervals:

IntervalCPU ImpactBest For
5 minHighDynamic environments
15 minMediumStandard networks
60 minLowStable environments

Configure in Connect → Schedule → Continuous.

Scheduled Discovery

Runs at specific times:


# Example schedule (cron syntax)
0 6 * * *    # Daily at 6 AM
0 */4 * * *  # Every 4 hours
0 8 * * 1    # Monday at 8 AM

Best for:

Manual Discovery

Triggered on-demand from:

Use for:


Device Categorization

Connect automatically categorizes discovered devices:

Automatic Classification

Detection MethodCategory
SNMP sysDescr contains "Cisco IOS"Network Switch
SNMP sysDescr contains "FortiGate"Firewall
WMI returns OS versionWindows Workstation/Server
PJLink respondsProjector
Dante mDNS serviceAudio Device

Manual Override

When auto-classification fails:

Classification Rules

Create rules for your environment:


# Example rule
name: "Crestron Processors"
match:
  - field: snmp_sysdescr
    contains: "Crestron"
  - field: open_ports
    includes: [41794]
action:
  set_type: "Control Processor"
  set_manufacturer: "Crestron"

VLAN Discovery

Connect discovers VLANs through multiple methods:

Via SNMP (Recommended)

SNMP VLAN tables provide:

Required MIBs:

Via CDP/LLDP

Neighbor discovery reveals:

Manual Entry

For VLANs not discovered automatically:


Topology Mapping

Connect builds network topology from discovered relationships.

Data Sources

SourceProvides
CDP neighborsSwitch-to-switch connections
LLDP neighborsMulti-vendor topology
MAC address tablesDevice-to-port mapping
ARP tablesIP-to-MAC relationships
Spanning TreeRoot bridge, port roles

Viewing Topology

Features:

Topology Accuracy

Factors affecting accuracy:


AV Protocol Discovery

For AV integrators, Connect discovers professional AV equipment.

NMOS IS-04 (Broadcast Video)

Discovers video-over-IP devices:

Configuration:

Dante/AES67 (Network Audio)

Discovers Dante-enabled devices:

Configuration:

PJLink (Projectors)

Discovers and monitors projectors:

Configuration:

ONVIF (IP Cameras)

Discovers ONVIF-compliant cameras:

Configuration:


Performance Optimization

Reducing Discovery Time

OptimizationImpactTrade-off
Narrow subnet rangesFaster scansMay miss devices
Increase timeoutMore devices foundSlower completion
Parallel scanningMuch fasterHigher CPU/network load
Skip inactive hostsFasterMay miss sleeping devices

Network Impact

Discovery generates network traffic:

ProtocolTraffic LevelMitigation
ARP scanLowN/A
SNMP walkMediumLimit OIDs
WMI queriesMediumBatch requests
Full port scanHighTarget specific ports

Recommendation: Schedule intensive discovery during off-hours.

Connect Resource Usage

Monitor Connect's resource consumption:

MetricNormalAction if High
CPU< 20%Reduce parallel scans
Memory< 500MBReduce cache size
Network< 10 MbpsIncrease intervals

Troubleshooting

No Devices Discovered

Incomplete Topology

Slow Discovery


Security Considerations

Credential Security

Network Segmentation

Audit Trail

All discovery activity is logged:

View in: Admin → Logs → Discovery Activity


What's Next?

TopicGuide
Managing discovered assetsAsset Management
Setting up monitoring alertsMonitoring & Alerts
AV-specific discoveryAV Discovery Guide

Last updated: January 2026