You can let the Monitoring Server automatically determine which subnets it will monitor. However, if your network is large or if the subnets are organized hierarchically, you may want to configure the monitoring locations yourself.
The following options are available for determining the network locations that will be monitored:
-
Automatic.The Monitoring Server automatically chooses which
endpoint subnets to monitor, according to one of the following
strategies:
-
Endpoint subnets (the default).The Monitoring Server creates
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 Monitoring Server creates 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 system’s 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.
The 32-bit binary subnet mask you use must begin with a block of at least two consecutive ones, followed by a block of consecutive zeros.
-
Endpoint subnets (the default).The Monitoring Server creates
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.
-
Imported.You define a list of locations that you want to
monitor. You create the list in a comma-separated values (.csv)
file, and the file is imported by the Monitoring Server. You can
use this list to logically group one or more subnets together, such
as all wireless networks for a building or all subnets for a site.
For details on how to create a valid .csv file, see
Creating a .CSV
File to Specify Monitoring Locations.
To specify locations for monitoring
-
Using an account that is a member of the RTCUniversalServerAdminsgroup, open the Office Communications Server 2007 R2 snap-in: Click Start, point to Administrative Tools, and then click Office Communications Server 2007 R2.
-
In the console tree, expand the Forestnode, and then expand Monitoring Servers.
-
Right-click the monitoring server you want to configure, and then click Properties.
-
In the Propertiesdialog box, click the Locationstab.
-
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. After you configure the settings, click
OK. Skip the rest of this procedure.
- To use a .CSV file to specify locations to monitor, click
Imported, and then click
Import.
Note: Whenever you change the way that monitoring locations are discovered, Monitoring Server stops monitoring the old locations and starts monitoring the new locations as endpoint call quality reports arrive.
- 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. After you configure the settings, click
OK. Skip the rest of this procedure.
-
On the Welcome to the Monitoring Server Location Import Wizardpage, click Next.
-
On the Choose Source Locationpage, enter the location of the .CSV file or click Browseto select a location, and then click Next.
-
On the Import Confirmationpage, click Next.
-
When the wizard has completed, select the View the log when you click Finishcheck box, and then click Finish.
-
In the log file, verify that <Success> appears under the Execution Resultcolumn. 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.