Specify Network Locations to Monitor
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
You can let the QoE Monitoring Server automatically determine which subnets it will monitor. If your network is large or if the subnets are organized hierarchically, you may want to configure the monitoring locations yourself. These locations will be used for monitoring and reporting purposes.
The following options are available for determining the network locations that will be monitored:
Automatic. The QoE Monitoring Server automatically chooses which endpoint subnets to monitor.
Endpoint subnets (the default). The monitoring server will create subnet locations according to the subnet mask and IP address that are sent from supported call endpoints. This can be a good option for small organizations with a flat organization of subnets.
Single Subnet Mask. The QoE Monitoring Server will create subnet locations by applying a single administrator-configured subnet mask to the IP addresses that are sent from supported endpoints. When you choose this option, the systems list of subnets to be monitored will be reset. This is a good option if you want to break up the subnets for monitoring purposes.
Imported. You can define a list of locations that you want to monitor. The list is enclosed in a comma-separated values file (.csv), and the file is imported by the QoE Monitoring Server. You can use such a list to logically group one or more subnets together, such as all wireless networks for a building or all subnets for a site. The following table shows the values, in order, that the 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.
Table 14. CSV Fields
| 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
To specify locations for monitoring
On the computer that is running the QoE Monitoring Server, log on as a member of the RTCUniversalServerAdmins group.
Click Start, point to All Programs, point to Administrative Tools, and then click Quality of Experience Monitoring Server.
In the console tree, expand QoE Monitoring Servers.
Right-click the monitoring server you want to configure, and then click Properties.
In the Properties dialog box, click the Locations tab.
.jpg "6102914c-9fb8-44f8-8f66-a60b786c5072")
Do one of the following:
To allow the locations to be automatically discovered from endpoint call quality reports, click Automatic. Click the type of automatic location discovery that you want to use. If you click Single subnet mask, type a subnet mask in the corresponding box. When the settings are as you want them, click OK. Skip the rest of this procedure.
To logically group one or more subnets together, click Imported, and then click Import.
Note
Whenever you change the way that monitoring locations are discovered, the QoE Monitoring Server will stop monitoring the old locations and start monitoring the new locations as endpoint call quality reports arrive.
On the Welcome to the QoE Monitoring Server Location Import Wizard page, click Next.
On the Choose Source Location page, enter a location, or click Browse to select a location. Click Next to continue.
On the Confirm Import page, click Next.
When the wizard has completed, select the View the log when you click Finish check box, and then click Finish.
In the log file, verify that <Success> appears under the Execution Result column. Look for <Success> Execution Result at the end of each task to verify the locations were imported successfully. Close the log window when you finish.