| external help file | online version | applicable | title | schema | manager | author | ms.author | ms.reviewer |
|---|---|---|---|---|---|---|---|---|
Microsoft.Rtc.Management.dll-help.xml |
Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 |
Get-CsNetworkInterRegionRoute |
2.0.0 |
rogupta |
hirenshah1 |
hirshah |
Retrieves one or more routes that connect network regions within a call admission control (CAC) configuration. This cmdlet was introduced in Lync Server 2010.
Get-CsNetworkInterRegionRoute [[-Identity] <XdsGlobalRelativeIdentity>] [-LocalStore] [<CommonParameters>]
Get-CsNetworkInterRegionRoute [-Filter <String>] [-LocalStore] [<CommonParameters>]
Every region within a CAC configuration must have some way to access every other region. While region links set bandwidth limitations on the connections between regions and also represent the physical links, a route determines which linked path the connection will traverse from one region to another. This cmdlet retrieves information about these route associations.
Get-CsNetworkInterRegionRoute -Identity NA_APAC_Route
Example 1 retrieves the route with the Identity NA_APAC_Route.
Get-CsNetworkInterRegionRoute -Filter *APAC*
In Example 2, we use the Filter parameter to retrieve all routes that contain the string APAC anywhere within the Identity.
Get-CsNetworkInterRegionRoute | Where-Object {$_.NetworkRegionLinks -eq "NA_EMEA"}
This example retrieves all region routes that use the network region link NA_EMEA. The command begins by calling the Get-CsNetworkInterRegionRoute cmdlet. Calling this cmdlet with no parameters retrieves all routes defined with the CAC configuration. This collection of routes is then piped to the Where-Object cmdlet. The Where-Object cmdlet takes the collection and retrieves all items in the collection that have the value NA_EMEA within their NetworkRegionLinks list.
Get-CsNetworkInterRegionRoute | Where-Object {$_.NetworkRegionID1 -eq "NorthAmerica" -or $_.NetworkRegionID2 -eq "NorthAmerica"}
Example 4 retrieves all region routes that include the NorthAmerica region. The first part of the command is a call to the Get-CsNetworkInterRegionRoute cmdlet. This cmdlet, called with no parameters, will retrieve all region routes. Next, this collection of routes is piped to the Where-Object cmdlet. The Where-Object cmdlet will narrow the collection down to only those routes that have NorthAmerica defined as one of the regions in the route. It does this by checking to see if the route has a NetworkRegionID1 value equal to (-eq) NorthAmerica, or (-or) a NetworkRegionID2 value equal to NorthAmerica.
The unique identifier for the network region route you want to retrieve. Network region routes are created only at the global scope, so this identifier does not need to specify a scope. Instead, it contains a string that is a unique name that identifies a particular route.
Type: XdsGlobalRelativeIdentity
Parameter Sets: Identity
Aliases:
Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
Required: False
Position: 2
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseA string that allows you to retrieve routes based on matching the Identity values to the wildcard string passed as a value to this parameter.
Type: String
Parameter Sets: Filter
Aliases:
Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseRetrieves the network interregion route information from the local replica of the Central Management store, rather than the Central Management store itself.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/?LinkID=113216).