Technical data

DATA CENTER and CAMPUS NETWORKS DEPLOYMENT GUIDE
Deploying Brocade Networks with Microsoft Lync Server 2010 51 of 52
Links from San Francisco:
New-CsNetworkRegionLink -NetworkRegionLinkID SanFrancisco_Austin -NetworkRegionID1
SanFrancisco -NetworkRegionID2 Austin -BWPolicyProfileID 5Mb_Link
New-CsNetworkRegionLink -NetworkRegionLinkID SanFrancisco_NewYork -NetworkRegionID1
SanFrancisco -NetworkRegionID2 NewYork -BWPolicyProfileID 5Mb_Link
Links from Austin:
New-CsNetworkRegionLink -NetworkRegionLinkID Austin_NewYork -NetworkRegionID1
Austin -NetworkRegionID2 NewYork -BWPolicyProfileID 5Mb_Link
10. Define a route between each pair of network regions. Network inter-region routes specify the region
links that are required for every pair of network regions in the enterprise. In the example topology,
region routes must be defined for Seattle, San Francisco, Austin, and New York.
Run the New-CsNetworkInterRegionRoute command to define the required routes:
Routes from Seattle:
New-CsNetworkInterRegionRoute -Identity Seattle_SFO_Route -NetworkRegionID1 Seattle
-NetworkRegionID2 SanFrancisco -NetworkRegionLinkIDs "Seattle_SanFrancisco”
New-CsNetworkInterRegionRoute -Identity Seattle_Austin_Route -NetworkRegionID1
Seattle -NetworkRegionID2 Austin -NetworkRegionLinkIDs "Seattle_Austin"
New-CsNetworkInterRegionRoute -Identity Seattle_NewYork_Route -NetworkRegionID1
Seattle -NetworkRegionID2 NewYork -NetworkRegionLinkIDs "Seattle_NewYork"
Routes from San Francisco:
New-CsNetworkInterRegionRoute -Identity SFO_Austin_Route -NetworkRegionID1
SanFrancisco -NetworkRegionID2 Austin -NetworkRegionLinkIDs "SanFrancisco_Austin”
New-CsNetworkInterRegionRoute -Identity SFO_NewYork_Route -NetworkRegionID1
SanFrancisco -NetworkRegionID2 NewYork -NetworkRegionLinkIDs "SanFrancisco_NewYork"
Routes from Austin:
New-CsNetworkInterRegionRoute -Identity Austin_NewYork_Route -NetworkRegionID1
Austin -NetworkRegionID2 NewYork -NetworkRegionLinkIDs "Austin_NewYork"
11. Enable Call Admission Control. After you have completed the steps to configure the CAC settings, run
the Set-CsNetworkConfiguration command to enable Call Admission Control:
Set-CsNetworkConfiguration -EnableBandwidthPolicyCheck 1
12. Enable logging and debugging:
Get-CsNetworkConfiguration
In the last line, look for:
EnableBandwidthPolicyCheck : True
Set-CsBandwidthPolicyServiceConfiguration -EnableLogging 1
Locate the following line in the topology file and check the ShareName (usually “mcs”):
<FileStoreService ShareName="mcs"
xmlns="urn:schema:Microsoft.Rtc.Management.Deploy.ServiceRoles.2008" />
Locate the given folder (“mcs”) on the FE or SE box, which is where PDP log files are generated.
For example; ..\mcs\co1-ApplicationServer-1\AppServerFiles\PDP.