Follow the steps below to create a CSV file that specifies the IPv4 client networks that you want to monitor.
When creating a CSV file:
Follow these steps:
network_name,subnet,mask,regions,network_type
Note that in the example below, the Houston Office entry does not specify a network type, so it defaults to Unassigned in the management console:
"Atlanta Lab",192.168.100.0,24,1,LAN "Houston Office",192.168.200.0,24,1
Defines the name the actual client network, up to 50 characters. We recommend using a naming convention, for example, Location-Description.
If you are planning to use network regions to convert the network subnet into /24 subnets, we recommend using a naming convention, for example, Location-Region-Bandwidth.
Defines the IPv4 address of the network in four-part, dotted-decimal notation, for example, 192.168.100.0.
Specifies a subnet mask for the actual client network.
Note that the management console automatically creates a /32 network for each server to monitor servers that act as both a server to client requests and a client to another server.
(Optional) Specifies the number of /24 subnets that can be converted from the broader network subnet. For example, if the network subnet is /22, four regions would convert the /22 into four /24 subnets.
(Optional) Specifies the network type you want to assign to the network and if applicable, its network regions. If you do not specify a network type, it is set to Unassigned.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|