[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

Modifies an existing route that connects network regions within a call admission control (CAC) configuration.

Syntax

Set-CsNetworkInterRegionRoute [-Identity <XdsGlobalRelativeIdentity>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-NetworkRegionID1 <String>] [-NetworkRegionID2 <String>] [-NetworkRegionLinkIDs <String>] [-NetworkRegionLinks <PSListModifier>] [-WhatIf [<SwitchParameter>]]

Set-CsNetworkInterRegionRoute [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Instance <PSObject>] [-NetworkRegionID1 <String>] [-NetworkRegionID2 <String>] [-NetworkRegionLinkIDs <String>] [-NetworkRegionLinks <PSListModifier>] [-WhatIf [<SwitchParameter>]]

Parameters

Parameter Required Type Description

Identity

Optional

XdsGlobalRelativeIdentity

The unique identifier for the network region route you want to modify. 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 that route.

Confirm

Optional

SwitchParameter

Prompts you for confirmation before executing the command.

Instance

Optional

PSObject

An object reference to an existing region route. This object must be of type Microsoft.Rtc.Management.WritableConfig.Settings.NetworkConfiguration.InterNetworkRegionRouteType, which can be retrieved by calling the Set-CsNetworkInterRegionRoute cmdlet.

NetworkRegionID1

Optional

String

The Identity (NetworkRegionID) of one of the two regions connected through this route. The value passed to this parameter must be a different region from the value of the NetworkRegionID2 parameter. (In other words, you can’t route a region to itself.) In addition, the combination of NetworkRegionID1 and NetworkRegionID2 must be unique (for example, you can’t have two routes defined that connect NorthAmerica and EMEA).

NetworkRegionID2

Optional

String

The Identity (NetworkRegionID) of one of the two regions connected through this route. The value passed to this parameter must be a different region from the value of the NetworkRegionID1 parameter. (In other words, you can’t route a region to itself.) In addition, the combination of NetworkRegionID1 and NetworkRegionID2 must be unique (for example, you can’t have two routes defined that connect NorthAmerica and EMEA).

NetworkRegionLinkIDs

Optional

String

Allows you to specify all the links for this route as a string of comma-separated values. The values are the identities (NetworkRegionLinkIDs) of the region links. If you enter values for both NetworkRegionLinkIDs and NetworRegionLinks, NetworkRegionLinkIDs will be ignored. Any links modified using this parameter will replace all existing links in the route.

NetworkRegionLinks

Optional

PSListModifier

A list object containing the identities (NetworkRegionLinkIDs) of the region links that apply to this route. For this cmdlet, this parameter differs from the NetworkRegionLinkIDs in that in addition to allowing you to replace all existing links for this route, you can also add or remove links.

WhatIf

Optional

SwitchParameter

Describes what would happen if you executed the command without actually executing the command.

Detailed Description

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, a route determines which linked path the connection will traverse from one region to another. This cmdlet modifies that route association.

Return Types

This cmdlet does not return a value. It modifies an object of type Microsoft.Rtc.Management.WritableConfig.Settings.NetworkConfiguration.InterNetworkRegionRouteType.

Examples

-------------------------- Example 1 --------------------------

Copy Code 
Set-CsNetworkInterRegionRoute -Identity NA_APAC_Route -NetworkRegionLinkIDs "NA_SA,SA_APAC"

This example modifies the route NA_APAC_Route by changing the region links that will be traversed along the route. The NetworkRegionLinkIDs parameter is used with a value of “NA_SA,SA_APAC”, which replaces any existing links with the two specified in that string.

-------------------------- Example 2 --------------------------

Copy Code 
Set-CsNetworkInterRegionRoute -Identity NA_APAC_Route -NetworkRegionLinks @{add="SA_EMEA"}

Like Example 1, Example 2 modifies the links within the NA_APAC_Route route. However, in the example instead of replacing all links for that route by using the NetworkRegionLinkIDs parameter, the NetworkRegionLinks parameter is used to add a link to the list of links that already exists on that route. In this case, the link SA_EMEA is added to the route. The syntax @{add=<link>} adds an element to the list of links. You can also use the syntax @{replace=<link>} to replace all existing links with those specified by <link> (which essentially behaves the same as using NetworkRegionLinkIDs), or the syntax @{remove=<link>} to remove a link from the list.

-------------------------- Example 3 --------------------------

Copy Code 
Set-CsNetworkInterRegionRoute -Identity NA_Route5 -NetworkRegionID2 SoutAmerica NetworkRegionLinkIDs "NA_SA,SA_APAC"

Example 3 modifies the route named NA_Route5. This example changes one of the regions that makes up this route. The NetworkRegionID2 parameter is used to specify the new region, then the NetworkRegionLinkIDs parameter is used to create a new list of links to connect the regions of this route.