Parameter: Replication Mode - Revision history

Sylvain Fontaine at 17:01, 11 May 2012

2012-05-11T17:01:55Z

Sylvain Fontaine at 19:42, 2 May 2012

2012-05-02T19:42:20Z

Allyntree at 17:05, 23 August 2010

2010-08-23T17:05:46Z

Allyntree: Created page with 'The Replication Mode parameter is used to define the algorithm that will be used to select a point code/subsystem from the list of available point codes/subsystems. Values for th…'

2010-08-18T16:12:06Z

Created page with 'The Replication Mode parameter is used to define the algorithm that will be used to select a point code/subsystem from the list of available point codes/subsystems. Values for th…'

New page

The Replication Mode parameter is used to define the algorithm that will be used to select a point code/subsystem from the list of available point codes/subsystems. Values for this parameter are selected from a drop-down list. The Replication Mode parameter can take on the following values:

* DOMINANT
* LOADSHARE
* DOMINANT_ALTERNATE
* LOADSHARE_ALTERNATE

@@ Line 7: / Line 7: @@
 | DOMINANT|| In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem on this route is the primary node/subsystem and is selected as the preferred node/subsystem when accessible. On failure of the preferred node/subsystem the next higher priority available backup node/subsystem is selected as the preferred node/subsystem.
 |-
-| LOADSHARE||  In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class1 traffic, and 2) in round-robin fashion for class 0 traffic. '''Loadshare mode is applicable in TELCORDIA only'''.
+| LOADSHARE||  In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for [[SCCP class|class1]] traffic, and 2) in round-robin fashion for [[SCCP class|class 0]] traffic. '''Loadshare mode is applicable in TELCORDIA only'''.
 |-
-| DOMINANT_ALTERNATE|| This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible but congested node. For class 1 traffic, this mode is same as DOMINANT mode. In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem configured on the route is selected as the primary node/subsystem and is the preffered node/subsystem when accessible and not congested. On failure or congestion of the preferred node/subsystem the next higher priority available and uncongested backup node/subsystem is selected as the preferred node/subsystem. '''This mode of operation is applicable only in ANSI96 and TELCORDIA'''.
+| DOMINANT_ALTERNATE|| This mode is significant only for [[SCCP class|class 0]] traffic. In this mode, [[SCCP class|class 0]] traffic is prevented from reaching an accessible but congested node. For [[SCCP class|class 1]] traffic, this mode is same as DOMINANT mode. In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem configured on the route is selected as the primary node/subsystem and is the preffered node/subsystem when accessible and not congested. On failure or congestion of the preferred node/subsystem the next higher priority available and uncongested backup node/subsystem is selected as the preferred node/subsystem. '''This mode of operation is applicable only in ANSI96 and TELCORDIA'''.
 |-
-| LOADSHARE_ALTERNATE|| This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible, but congested node. For class 1 traffic, this mode is same as LOADSHARE mode. In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class 1 traffic, and 2) in round-robin fashion for class 0 traffic. For class 0 traffic, a node/subsystem is selected when it is accessible and uncongested. On failure or congestion of the node, next available and uncongested node/subsystem is selected. '''This mode of operation is applicable only in TELCORDIA'''.
+| LOADSHARE_ALTERNATE|| This mode is significant only for [[SCCP class|class 0]] traffic. In this mode, [[SCCP class|class 0]] traffic is prevented from reaching an accessible, but congested node. For [[SCCP class|class 1]] traffic, this mode is same as LOADSHARE mode. In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for [[SCCP class|class 1]] traffic, and 2) in round-robin fashion for [[SCCP class|class 0]] traffic. For [[SCCP class|class 0]] traffic, a node/subsystem is selected when it is accessible and uncongested. On failure or congestion of the node, next available and uncongested node/subsystem is selected. '''This mode of operation is applicable only in TELCORDIA'''.
 |}
 [[Category:Parameters]]

← Older revision		Revision as of 17:05, 23 August 2010
Line 5:		Line 5:
	* DOMINANT_ALTERNATE		* DOMINANT_ALTERNATE
	* LOADSHARE_ALTERNATE		* LOADSHARE_ALTERNATE
		+
		+	[[Category:Parameters]]

@@ Line 1: / Line 1: @@
 The Replication Mode parameter is used to define the algorithm that will be used to select a point code/subsystem from the list of available point codes/subsystems. Values for this parameter are selected from a drop-down list. The Replication Mode parameter can take on the following values:
-* DOMINANT
+{| class="wikitable" border="1"
-* LOADSHARE
+! width="150" style="background:#efefef;" |Replicate mode
-* DOMINANT_ALTERNATE
+! width="350" style="background:#efefef;" |Description
-* LOADSHARE_ALTERNATE
+|-
 [[Category:Parameters]]