Chapter 14. Network Setup
174

14.7.3. Storage Network Topology Requirements

The secondary storage NFS export is mounted by the secondary storage VM. Secondary storage
traffic goes over the management traffic network, even if there is a separate storage network. Primary
storage traffic goes over the storage network, if available. If you choose to place secondary storage
NFS servers on the storage network, you must make sure there is a route from the management traffic
network to the storage network.

14.7.4. External Firewall Topology Requirements

When external firewall integration is in place, the public IP VLAN must still be trunked to the Hosts.
This is required to support the Secondary Storage VM and Console Proxy VM.

14.7.5. Advanced Zone Topology Requirements

With Advanced Networking, separate subnets must be used for private and public networks.

14.7.6. XenServer Topology Requirements

The Management Servers communicate with XenServer hosts on ports 22 (ssh), 80 (HTTP), and 443
(HTTPs).

14.7.7. VMware Topology Requirements

• The Management Server and secondary storage VMs must be able to access vCenter and all ESXi
hosts in the zone. To allow the necessary access through the firewall, keep port 443 open.
• The Management Servers communicate with VMware vCenter servers on port 443 (HTTPs).
• The Management Servers communicate with the System VMs on port 3922 (ssh) on the
management traffic network.

14.7.8. KVM Topology Requirements

The Management Servers communicate with KVM hosts on port 22 (ssh).
14.8. Guest Network Usage Integration for Traffic Sentinel
To collect usage data for a guest network, CloudPlatform needs to pull the data from an external
network statistics collector installed on the network. Metering statistics for guest networks are available
through CloudPlatform’s integration with inMon Traffic Sentinel.
Traffic Sentinel is a network traffic usage data collection package. CloudPlatform can feed
statistics from Traffic Sentinel into its own usage records, providing a basis for billing users of cloud
infrastructure. Traffic Sentinel uses the traffic monitoring protocol sFlow. Routers and switches
generate sFlow records and provide them for collection by Traffic Sentinel, then CloudPlatform queries
the Traffic Sentinel database to obtain this information
To construct the query, CloudPlatform determines what guest IPs were in use during the current query
interval. This includes both newly assigned IPs and IPs that were assigned in a previous time period
and continued to be in use. CloudPlatform queries Traffic Sentinel for network statistics that apply
to these IPs during the time period they remained allocated in CloudPlatform. The returned data is
correlated with the customer account that owned each IP and the timestamps when IPs were assigned
and released in order to create billable metering records in CloudPlatform. When the Usage Server
runs, it collects this data.