Defining Network Sites

Not unlike Active Directory or Exchange, Lync Server needs to define network sites and associated subnets to make decisions about where to access a resource or how to route a call. All subnets in a network should be defined and associated with a correct network site in Lync Server. This is easily handled by a simple comma-separated value file and the Lync Server cmdlets in PowerShell. For example, the CSV file might be called subnet.csv and contain

IPAddress, mask, description, NetworkSiteID
10.1.1.0, 24, "NA:Subnet in Dublin", Dublin
10.1.2.0, 24, "NA:Subnet in Lompoc", Lompoc
10.1.3.0, 24, "NA:Subnet in Ocean Springs", Ocean_Springs
10.1.4.0, 26, "EU:Subnet in London", London

These values can be easily imported into the Lync Server network’s definitions via this command:

import-csv subnet.csv | foreach {New-CSNCSSubnet $_.IPAddress -MaskBits $_.mask
–Description $_.description -NetworkSiteID $_.NetworkSiteID}

This script can be scheduled to run regularly, and when new sites or subnets are added to the network, the csv file is updated and the script keeps the network definitions current.