Understanding Network Bandwidth Requirements

Filed under: Notification Server System Requirements

Submitted by vortex0007 on Wed, 2008-05-14 13:43.

During the architecture and design of an Altiris solution, network traffic is a key factor to determining server placement. The following chart shows the typical network traffic generated between the Altiris Notification Server and the Altiris Notification Server Agent. Use this as a guideline to help plan the placement of Altiris architecture components.

Component	Traffic	Frequency
Configuration Update	232 bytes	Once every 12 hours
Basic Inventory	6 Kb	Once a day
Package Installation	Depends on Package size For example a 100 MB package will generate 100 MB of traffic.	Depends on number of packages
Creating Package from Source Files	Varies by Package size. For example a 100 MB package will generate 100 MB of traffic. This is a one time hit on the network to the distribution points located on the far side of the WAN.	Depends on number of packages and update frequency to distribution points.
Hardware Inventory	400 KB for support files installed on client, 100 - 200 KB (Initial Complete Inventory) Subsequent Inventories only send the deltas on the network	Depends on the frequency that the organization will perform hardware inventory. The once per day will be the initial setting, this can be tuned (less frequent) based on network utilization. Also traffic is dependent of number of clients sending traffic at the same time.
Inventory (Full)	377 Kb (varies on each client)	1st Tuesday of Feb, Apr, Jun, Aug, Oct and Dec. at 2:00 am
Inventory User (Full)	N/A	First Wednesday of every month
Software Inventory (Delta)	43 Kb (varies on each client)	Once every 10 days at 7 PM
Hardware Inventory (Delta)	N/A	Weekly every Friday at 12:00 pm
User Inventory (Delta)	N/A	Every Monday at 2:00 pm
Advertisement	1543 bytes	N/A
NS Agent Foot Print (Win32)	10.7 MB depending on installed solutions	Once for client installation