Home » IPAM » SFBS – define environment for monitoring

Deployment of skype for business server infra has been taken up carefully with the objective of meeting or exceeding user expectation. However, in real world a real time communication can breakdown to a bad experience one from one or more weak point in the path from server to end device. Fortunately, Lync/skype for business server comes with monitoring and a rich set of tools to help identify these problem areas. Configuration of monitoring service brings in the Call Detail Recording (CDR) and Quality of Experience (QoE) that provides lot of details about every conversation. What needed is to define the network topology so that these details can be drilled down to specific area of focus instead searching across the enterprise. In this part of the blog series on skype for business server, I will be defining the environmental aspects of the enterprise to get the required correlation for analysing the service usage.

In my earlier post, I have discussed inventorying the enterprise network space using IPAM. I will be using the information obtained here in skype for business to define

  • LIS information
  • Network Region, Site and subnets
  • Building and network definition in Skype Call Quality Dashboard (CQD)

The format of the CSV file that is used to define these details is essentially as bellow

Location NetSubnet Name Type Site Region Country CQDBuildingKey
EC EC-projectsfb-BB LAN BLR_EC India India 2

In this, the column CQDBuildingkey is for defining call quality dashboard and the same I will describe in the subsequent post on CQD.

To enable clients to automatically detect their location within a network, I need to configure the location database(LIS). Using the script as bellow, records from the CSV files are parsed and updated into the Location Information Service (LIS) databse.

For all the sites in the CSV file, the switch statement need to be updated so that corresponding set-listsubnet cmdlet with predefined parameters for the site is executed for the subnet.

LIS may not help in monitoring; however, it helps to identify any mismatch or missing subnet definition through user feedback. Subnets and their grouping into sites and region is done for getting the location report. Location report can help to determine if the problems are widespread or if they are largely confined to a given network segment and thus rework of bandwidth allocation and/or Quality of Service(QOS) can be taken up.

This script here would consume the CSV file above to define the network sites subnet so that the location reports aligns with enterprise network. Regions were created prior to this as per the MPLS network and Skype for business Pool.

Location NetSubnet Name Site Region Country CQDBuildingKey
EC EC-projectsfb-BB BLR_EC India India 2


With this done my location reports comes something like this, suggesting packet drops are worrying factor in India region. Expanding that further would give site specific details so that I can take corrective action on them instead of trying on something impossible like altering entire enterprise network.

Leave a Reply

Your email address will not be published. Required fields are marked *