Previous Topic: Managing Client NetworksNext Topic: How the Network List Works


How Client Networks Work

A client network specifies a range of client IPv4 addresses that you want to monitor and corresponds to a physical location or group of users in your environment.

We recommend creating a client network based on where the client traffic originates, such as a remote site, the data center, or for an externally facing application (the Internet). For example, if you have a client network in Austin that is defined as 192.168.0.0/22, use the management console to create an Austin client network with the same network address and subnet mask.

To enable a management console user to quickly analyze and respond to performance issues on a client network, create client networks that correspond to the actual client networks in your environment.

When a server is added to the Server List, the management console automatically creates a corresponding /32 client network to monitor traffic between servers in a multi-tier application.

Properly specifying the client networks of interest optimizes available system resources.

Application Delivery Analysis includes the following default entries for catch all default client networks:

Note: When client networks overlap, the management console reports the application traffic in the more specific client network.

More information:

How /32 Client Networks Work

How the Management Console Manages Database Growth