Creating a .CSV File to Specify Monitoring Locations
Topic Last Modified: 2009-03-04
One option for specifying what network locations to monitor using Monitoring Server is to create a .csv file to list the locations. The following table shows the values, in a specific order, that a .csv file must contain for each location that you want to monitor.
Note
The following encodings are supported: ANSI, UTF-8, UTF-16-LE. UTF-16-BE can be converted to UTF-16-LE by using the Save As option in Notepad.
CSV Fields to Specify Monitoring Locations
| Field | Name | Description | Mandatory | Format |
|---|---|---|---|---|
1 |
Monitor Flag |
Indicates whether the location will be monitored. Individual call quality reports from this location are available even if monitoring is disabled. |
Yes |
True, False, 1, or 0 True | 1 : Enable monitoring for this location False | 0 : Disable monitoring for this location |
2 |
Location Name |
Name of the location. This name will be used as the performance counter instance name. |
Yes |
May be up to 128 characters in length, of valid characters and numbers. Location names must start with an alphabetic character. The following special characters are not allowed: "(", ")", "#", "\", or "/". |
3 |
Subnet 1 |
A subnet. |
Yes |
A valid IPV4 subnet address. |
4 |
Subnet bits 1 |
The number of bits that will be used by the network portion of the subnet address in the Subnet 1 field. |
Yes (if previous subnet address is present) |
A number between 1 and 32. |
5 |
Subnet 2 |
The second subnet for the location. If no location is specified, this subnet is treated as a separate location for monitoring purposes. |
No |
A valid IPV4 subnet address. |
6 |
Subnet bits 2 |
The number of bits that will be used by the network portion of the subnet address in the Subnet 2 field. |
Yes (if previous subnet address is present) |
A number between 1 and 32. |
5 |
Subnet <n> |
The last subnet for the location. If no location is specified, this subnet is treated as a separate location for monitoring purposes. |
No |
A valid IPV4 subnet address. |
6 |
Subnet bits <n> |
The number of bits used that will be used by the network portion of the subnet address in the Subnet <n> field. |
Yes (if previous subnet address is present) |
A number between 1 and 32. |
The following example shows what the .csv file would look like for four locations named S-10.10.1.10, Contoso, Contoso-Wireless, and Contoso-VPN:
1,S-10.10.1.10,10.10.1.10,24
1,Contoso,10.20.1.1,24,10.20.2.1,24
0,Contoso-Wireless,10.80.1.1,24,10.80.2.1,24
False,Contoso-VPN,10.50.1.1,16
In the first line of this example, one location is being monitored, and it is named S-10.10.1.10. The location contains one subnet, with the address 10.10.1.10, and 24 bits will be used by the network portion of the subnet address.