Creating region links and routes

Having created sites, subnets, and regions, we have still not told Lync how sites connect to each other. This is what region links and routes are for. Region links define bandwidth policies between sites, and region routes are used to connect sites by creating possible audio paths.

Note

When an audio path is chosen for the media stream, Lync will look at all the bandwidth policies in the path and select the most restrictive one for the call.

How to do it

The following are the five steps to add region links:

  1. Launch the Lync Server Control Panel with an account with the RTCUniversalServerAdmins rights, and navigate to Network Configuration | Region Link.
  2. Select New.
  3. Enter a name for the link, select the two sites that will be connected through this link, and enter which Bandwidth policy should apply, as shown in the following screenshot:
    How to do it
  4. Press Commit to save.
  5. This process is complete when all the links are added.

The following are the steps to add region routes:

  1. Navigate to Network Configuration | Region Route.
  2. Select New to add a new route.
  3. Add the two regions to be connected and the selected route, as shown in the following screenshot:
    How to do it
  4. The task is complete when all the regions and their links have been added to the configuration.

    Note

    The preceding example does not show a complete configuration; all regions must have links and routes.

There's more…

As with the other tasks, this task can also be completed using PowerShell.

The following are the three steps to add region links using PowerShell:

  1. Create a CSV file with all the information required, which looks similar to this:
    There's more…
  2. Save the file (the example shows C:LyncScriptssubnets.csv).
  3. Run the following PowerShell command to import and configure:
    Import-Csv C:LyncScripts
egionlinks.csv | foreach {
New-CsNetworkRegionLink -Identity $_.Identity`
 -NetworkRegionID1 $_.NetworkRegionID1`
 -NetworkRegionID2 $_.NetworkRegionID2`
 -BWPolicyProfileID $_.BWPolicyProfileID
}

Proceed with the following steps to add region routes using PowerShell:

  1. Create a CSV file with all the information required, which looks similar to this:
    There's more…

    Note

    The NetworkRegionLinkIDs field will be populated with two or more existing links. Make sure they are separated by ; in the CSV file. The –replace command will take care of changing the ; into , before executing the commands.

  2. Save the file (the example shows "C:LyncScriptsRegionRoutes.csv).
  3. Run the following PowerShell command to import and configure:
    Import-Csv C:LyncScriptsRegionRoutes.csv| foreach {
$_.NetworkRegionLinkIDs = $_.NetworkRegionLinkIDs`
 -replace ';',','
New-CsNetworkInterRegionRoute -Identity $_.Identity`
 -NetworkRegionID1 $_.NetworkRegionID1`
 -NetworkRegionID2 $_.NetworkRegionID2`
 -NetworkRegionLinkIDs $_.NetworkRegionLinkIDs
}
  4. It is also possible to connect two sites that are directly connected through WAN but do not belong to any region. For this, we must use the New-CsNetworkInterSitePolicy command (it is not available through Lync CSCP). Simply run the following in an elevated administrative prompt (the Medium bandwidth policy is just an example):
    New-CsNetworkInterSitePolicy`
 -InterNetworkSitePolicyID Southwest_Southeast`
 -NetworkSiteID1 Southwest`
 -NetworkSiteID2 southeast`
 -BWPolicyProfileID Medium

See also

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.135.191.86