Bandwidth Consumption by Operating System

Discovery bandwidth usage varies significantly across different OS platforms. Key data flows include communication between the MID Server and the ServiceNow instance, as well as between the MID Server and target devices. For example:

• Windows Server editions (2016, 2012, 2008, Windows 10) show total bandwidth ranging from approximately 3 to 5 MB per discovery.
• Linux CentOS, Mac OSX, HP-UX, Solaris, and network devices like Cisco UCS Switches and Load Balancers have lower bandwidth usage, typically under 2 MB.
• Storage devices like EMC Storage consume higher bandwidth, up to nearly 7 MB per discovery.

This data allows customers to estimate network impact based on their environment’s device mix.

Bandwidth for Three-Tier Applications

Discovery of complex three-tier applications (UI, application, and database layers) involves significantly more data transfer, especially during initial discovery:

• Initial discovery can consume nearly 18 MB total, with the Oracle database on Windows contributing the largest portion.
• Subsequent discoveries reduce bandwidth substantially to approximately 3.35 MB total, reflecting incremental updates.

This helps customers plan for heavier network loads during initial application discovery and lighter loads afterward.

Pattern-Based Discovery Bandwidth Over Different OS Types

When using patterns for discovery, bandwidth consumption is measured separately for initial creation and subsequent updates:

• Windows Server pattern discovery consumes the most bandwidth (around 14.7 MB for creation, slightly less for updates).
• Solaris and Citrix Netscaler devices also show moderate bandwidth use (3.7 to 4 MB for creation and updates).
• Other devices like Linux, HP-UX, F5, and L3 Switches have lower bandwidth requirements (under 2.5 MB).

These insights enable customers to anticipate network traffic when configuring pattern-based discoveries across device types.

Practical Implications for ServiceNow Customers

• Use these bandwidth metrics to plan discovery schedules and resource allocation, especially when managing large or diverse environments.
• Expect higher network utilization during initial discoveries and adjust network policies accordingly to avoid congestion.
• Leverage subsequent discovery runs for efficient incremental updates, reducing network impact over time.
• Consider device-specific bandwidth needs when scaling Discovery or integrating new device types.

Note: These measurements were obtained using base operating configurations; actual bandwidth usage may vary depending on local environment and discovery settings.