Diameter Tab
Click here to see this page in full context

Landslide Performance Test System – Release 24.3 September 2024

Diameter Tab

The following parameters are available in all test cases that support Diameter testing. With them you can provision mandatory Diameter AVPs, optional and vendor-specific AVPs, and other options that are always available with Diameter.

NOTES:

  • Although defined slightly different in their associated standards, both the 3GPP and 3GPP2 organizations have implemented a policy decision function and associated reference points. 3GPP2 defines the reference points as Tx and Ty, while 3GPP defines them as Rx and Gx.

  • In WIMAX Forum testing, PCC-T3-P is an extension of Ty/Gx reference points.

Parameter Index

Failover Simulation (OCS Node (Ro), PGW Node (Gx), IMS Node (Rx))
    		T4 Options (SMS Network)
 

Related Measurements

Diameter Base processing measurements are reported on various report tabs with the Diameter node measurements.

 

Product Name

 

Provisions the Product-Name AVP in CER and CEA messages. The default server name depends on the test case.

Range: N/A

Default: Landslide NAS or Landslide DCCA,  Landslide HSS, Landslide OFCS_Server, Landslide BBERF, Landslide PCRF, Landslide MSC, Landslide MSC S6c, Landslide SMS-SC T4

Tcl Parameter:

DiaSrvProductName

HssSrvProductName
GxcCInProductName

DiaClnProductName

 

Application ID

Provisions the Application, Auth-Application and Acct-Application AVPs in messages sent by a node and identifies the Diameter application supported by the node. The Application selection determines which Authentication algorithms display for your selection.

In HSS Node test case and DRA Nodal HSS Interfaces, the Application ID for:

Cx is 16777216

S13/S13' is 16777252

S6a/S6d is 16777251

S6c is 16777312

SGd is 16777313

S6t is 16777345

SLh is 16777291

Sh is 16777217

SWx is 16777265

Wx is 16777219

Zh is 16777221

MB2 is 16777335 (IP Application Node and eMBMS Node test cases)

T4 is 16777311 (Service Based Node and SMS Network test cases)

In DRA Nodal test case the application ID differed based your selection of PCRF Interfaces | Emulate option:

  • PCRF Interfaces > Emulate AGW I/F - Gx Interface : the Application ID is 16777238
  • PCRF Interfaces > Emulate AGW I/F - S9 Interface : the Application ID is 16777267
  • PCRF Interfaces > Emulate AF I/F - Rx Interface : the Application ID is 16777236
  • PCRF Interfaces > Emulate BBERF I/F - Gxc Interface : the Application ID is 16777266
  • PCRF Interfaces > Emulate OCS I/F - Sy Interface : the Application ID is 16777302
  • PCRF Interfaces > Emulate TDF I/F Sd Interface : the Application ID is 16777303
  • SCEF Interfaces > Emulate MME I/F T6a Interface : the Application ID is 16777346
  • SCEF Interfaces > Emulate SGSN I/F T6a Interface : the Application ID is 16777346

 

In DRA Nodal test case, you may configure multiple diameter application Ids, one for each enabled interface. (See DRA Nodal Test Configuration).  

NOTE: Configured application Ids for each enabled interface allows PCRF to use the configured values (instead of fixed default values) in Diameter capability exchange messages.

 

Parameter Class: Basic: Custom Multiple Choice Values:

Tcl Parameter:

DiaSrvCcApplicationId

HssSrvS6aApplicationId
DiaCInCcApplicationId

HssSrvS6dApplicationId
HssSrvGrApplicationId

HssSrvSwxApplicationId

 

Application

Options Displayed for AAA Server Nodal

Parameter Name Value

NASREQ

PAP and CHAP options are enabled. EAP is disabled

NASREQ : 1

Diameter BASE Accounting

All Authentication options are disabled and AAA Test is forced to Accounting ONLY

Diameter Base Accounting : 3

Diameter EAP

EAP is enabled. PAP and CHAP are disabled

Diameter EAP : 5

WiMAX MIP4

PAP and CHAP are enabled. EAP is disabled

WiMAX MIPv4 : 0xfffffffd

Wm Interface

PAP and CHAP are enabled. EAP is disabled

Wm Interface : 0x1000030

S6b Interface

EAP is enabled. PAP and CHAP are disabled

S6b Interface : 0x1000038

STa Interface

EAP is enabled. PAP and CHAP are disabled

STa Interface : 0x1000022

S6b/STa/SWx Interfaces

EAP is enabled. PAP and CHAP are disabled (AAA Server Node)

S6b/STa/SWx Interfaces : 0xfffffffc

S6b/STa Interfaces

EAP is enabled. PAP and CHAP are disabled

S6b/STa Interfaces : 0xfffffffc

  • When you select the WiMAX MIP4, the AAA Nodal is only used to simulate HA NAS. You can create another NAS to simulate FA NAS by configuring the application as EAP.

  • To configure EAP Authentication and any auth-request-type as part of the same session:

You may select the Wm interface to allow EAP authentication, you can also configure any Auth-request-type as part of the same session (for example, you can configure the NASREQ/NASResponse Auth-request-type via  AVP Configuration).  

  • Selecting S6b/STa Interfaces supports both STa and S6b interfaces simultaneously for the same UEs.
NOTES:
  • The number of tunnels set/changed depending on the Diameter application you select: two tunnels for Wm Interface and one tunnel for all other applications.
  • The S6b interfaces between the 3GPP AAA Server and the PDN-GW.
  • The STa interface connects the trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and transports access authentication, authorization, mobility parameters and charging-related information in a secure manner.

Related Measurements

WiMAX H4 Command Code

 

WiMAX HA4 Command Code checkbox is only available when the Wimax Mip4 option is selected from the Application dropdown list. Select the checkbox and enter the Command Code of the message type not defined by IANA official codes.

Tcl Parameter: DiaCmdCodeWha4En

 

Origin Realm

 

Provisions the Origin-Realm AVP in all messages sent by a node, identifying the realm that is serviced by the client or server. When secondary nodes or SUTs are supported, a realm field is also provided for the secondary device.

Range: N/A

Default: Spirent.com

Tcl Parameter: DiaSrvOriginRealm

Related Measurements

Origin Host

The node's FQDN, which is used to provision the Origin-Host AVP in all messages sent by a node, uniquely identifying the node as the originator of a request and a member of the Origin Realm.  When secondary nodes or SUTs are supported, a host field is also provided for the secondary device.

Range: N/A

Default: NAS.Spirent.com or DCCA.Spirent.com

Tcl Parameter: DiaSrvOriginHost

Related Measurements

Vendor ID

The application's vendor-specific ID or enterprise code, which is used to provision the Vendor-ID AVP in CER or CEA messages sent by a node. The IANA maintains the official list of enterprise codes here. Applications defined by the IETF, such as NASREQ, are identified with a 0.

Range: N/A

Default: 10415

Tcl Parameter:

DiaSrvVendorId DiaClnVendorId DraAppVendorId

 

AVP Configuration

Click the View/Edit button to view or modify the AVP configuration for the test.

During OFCS testing, the Offline Charging node supports both event-based and session-based charging activities concurrently. The type of activity is explicitly defined by Accounting-Record-Type AVP.

In the DRA Nodal, node-specific functionality has been added to the Generic Interface Tabs to support message types CER/CEA for the generic client and the generic server.

Since the DRA Node is a Diameter agent, it processes all Diameter messages associated with all supported Diameter network elements.

AVP Criteria

Select to View/Edit criteria based on APVs. Define AVP Criteria, that get associated with AVP Criteria measurements which increment when Criterion is not met.

See additional details in AVP Criteria in VSA/AVP Template Parameters:

Able to:

  • determine if certain AVPs are present, not present or have certain values in specific messages.    

  • define AVP Criteria, that get associated with AVP Criteria measurements.  

  • setup Pass/Fail Criteria against these measurements, to tie it into the Pass/Fail Criteria. 

NOTE:

  • Define up to 32 AVP Criteria per test case, which will result in up to 32 simple count measurements that increment each time a criteria is not met.  Measurements names are AVP Criterion 1 through AVP Criterion 32. 

  • Measurements are Summarized across all test cases in Summary view, and individual counts for each test case are available in the test case view.   (e.g. "The # of AVP that Failed to meet Criteria #N" )

  • Up to the user to put the AVPs in the same order in each test case to achieve same meaning.   

  • AVP Criteria can be setup easily in one Test Case, then copy/pasted to the others via QuickList, to maintain the same exact setup.  

  • Can also be synchronized across test cases using the Cross Reference.

AVP Database Size (bytes)

Indicates the AVP size allocated for authentication packet flow descriptors and allows you to define the database memory to run AVP packets. This is the memory allocated for the overflow data caused by AVP values that take up > 4 bytes. All AVPs that have values larger than 4 bytes will be stored in the Database. In the example below:

The UNIT32 is just 4 bytes  4*8=32 bits thus it will not use the database. The HEX_STRING is empty and the USE_PRECONDITION has no value. Only the Text and String Values that are highlighted below will use the database and would require about 128 bytes for the Database size.

DB Size (bytes) has been added to the VSA/AVP configuration window. This is the value the AVP Database estimator calculates that is required for the AVP Database size. It should be used when determining the size of the AVP Database Size in Bytes.

 

Range: 200 — 4,000

Default: 200

Tcl Parameters:  

DiaAvpDataSize

HssSrvS6aDiaAvpDataSize

HssCxIcscfClnVsaDbSize

HssSrvS6dDiaAvpDataSize

HssSrvSwxDiaAvpDataSize

HssCxScscfClnVsaDbSize

SlhSrvDiaAvpDataSize

CxSrvDiaAvpDataSize

CxClnDiaAvpDataSize

ShSrvDiaAvpDataSize

  

ShClnVsaDbSize

EirSrvMmeDiaAvpDataSize

EirSrvSgsnDiaAvpDataSize

 

 

AVP Criteria DB Size (bytes)

Indicates the AVP Criteria Database size.

Range: 200 — 4,000

Default: 200

DiaSrvAttrCritDataSize

HssSrvAttrCritDataSize

HssClnAttrCritDataSize

HssSrvS6dAttrCritDataSize

HssSrvSwxAttrCritDataSize

HssCxScscfAttrCritDataSize

SlhSrvAttrCritDataSize

CxSrvDiaAttrCritDataSize

CxClnDiaAttrCritDataSize

ShSrvDiaAttrCritDataSize

  

ShClnAttrCritDataSize

EirSrvMmeAttrCritDataSize

EirSrvSgsnDiaAttrCritDataSize

 

 

Auth AVP DB Size (bytes)

Available in AAA node Test. During AAA Server Node testing, you may specify separate AVP size allocated for authentication (Auth AVP) and accounting (Acct AVP) packet flow descriptors.

Range: 200 — 4,000

Default: 200

Tcl Parameter: DiaSrvAuthAvpDataSize

Acct AVP DB Size (bytes)

Available in AAA node Test. During AAA Server Node testing, you may specify separate AVP size allocated for authentication (Auth AVP) and accounting (Acct AVP) packet flow descriptors.

Range: 200 — 4,000

Default: 200

Tcl Parameter: DiaSrvAcctAvpDataSize

Max Number of AVPs

Enter the maximum number of AVPs that can be included in a CCR message.

Also available on PGW Node - Ro Interface.

Range : 0 to 30

Default : 0

Tcl Parameters:

HssSrvS6aVsaDbList

HssSrvS6dVsaDbList

 DiaClnVsaDbList

HssSrvSwxVsaDbList

TyCcClnVsaDbList

  

 

Include Failed-AVP

Select to include the "Failed AVP" in the Diameter Error Answer message. Only error codes that are checking for mandatory AVPs (such as Missing AVP 5005, or Invalid AVP value 5004 ) will be considered.

NOTE: Include Failed-AVP is not applicable for CER/CEA message types. By default, CEA message includes Failed AVP.

 

Supported in following Interfaces/Test Cases.

Gx - PCRF Node/Nodal, PDF Nodal, PGW Node

Gy - DCCA Node/Nodal, OCS Node

Sy - PCRF Node, OCS Node

S6a - HSS Node/Nodal, SGW Nodal

S6b - AAA Node/Nodal

Rf - OFCS Node, PGW Node, SGW Nodal

Ro- OCS Node , PGW Node

TyCcClnAddFailedAvpEn

TyCcSrvAddFailedAvpEn

DiaCcClnAddFailedAvpEn

DiaCcSrvAddFailedAvpEn

SyCcClnAddFailedAvpEn

SyCcSrvAddFailedAvpEn

DiaClnAddFailedAvpEn

DiaSrvAddFailedAvpEn

HssClnS6aAddFailedAvpEn

HssSrvS6aAddFailedAvpEn

 

Do Not Initiate DPR

The Do Not Initiate DPR (Disconnect Peer Request) applies in AAA node, DRA Nodal (Generic Interfaces), HSS Node, PCRF Node and PGW Node test cases. When the AAA, DRA , HSS, PCRF, or PGW  node test is stopped, a disconnect peer request is sent, which stops the SUT from communicating with the emulated HSS or PCRF.

Use this parameter to stop initiation of Disconnect Peer Request and keep the communication channels open.

Type: True/False

Default: False

Tcl Parameter: DoNotInitiateDprEn

DPR Cause

Specify a cause value when stopping a test case. (See RFC 3588, 5.4.3 Disconnect Cause AVP). The Disconnect-Cause AVP is added to the Diameter DPR (Disconnect-Peer-Request defined in RFC 6733) for the test cases that support DPR Cause.

Available only when you do not select Do Not Initiate DPR. Available in several Test Cases- AAA Node, RA Nodal (Generic Interfaces), HSS Node, OCS Node, PCRF Node, PGW Node, and IMS Node.

Options: REBOOTING (0); BUSY (1); DO_NOT_WANT_TO_TALK_TO_YOU (2)

Tcl Parameter: HssSrvS6aDprCause

(HssSrvxxx+DprCause, where xxx depends on the Interface you select on the Emulator Configuration tab. That is, S6b, S6d, Swx, and so on).

Tcl Parameter: TxSrvDprCause, DiaSrvDprCause, TxClnDprCause, TyCcClnDprCause (based on Test Case and interface)

Disconnect Wait Time (s)

Enter Disconnect Wait time in Seconds. This field is only available when Do Not Initiate DPR is enabled. This will enable Automation Control to be able to stop test cases as the disconnect time will prevent waiting on DPR.

Default = 10 (seconds)

Tcl Parameter: DiaSrvDisconnectWaitTime

Include Destination-Host AVP if Known

Select to include the appropriate destination Host AVP in messages:

  • In DRA Nodal test case (Gx/Rx | Diameter tab), select to include the Destination Host AVP in the the CCR-T message.
  • In DRA Nodal test case when PCRF Emulation is enabled, select to include/exclude the Destination Host AVP.
  • In IMS Node test case (Rx | Diameter tab), select to include the Destination Host AVP in the STR message.
  • In SGW Nodal test case (when PGW Gx Interface enabled: Gx | Diameter tab), select to include the Destination Host AVP in the CCR-T message.
  • In PGW and SGW Nodal test cases (when VoLTE tab is enabled, IMS Node = Local, Enable Rx  | Diameter tab) to include Destination Host AVP in the AAR message (but not in the first AAR message)
  • In PGW Node test case (when Gx Interface enabled: Gx | Diameter tab), select to  include the Destination Host AVP in the CCR-T message.

Apply Test Data File to AVP Configuration

See Test Data Files for further explanation and sample files. If a sample is not found for the specific TDF, you can obtain a sample file from your Technical Support representative. You may also use the following options to select an existing TDF or create/edit TDF-CSV files (TDF-CSV Editor). 

For most TDF Parameters used for Applying Parameters, each row in the file is the overridden value for a different “Session”, aka a different UE. But some TDFs are done in other dimensions, like Bearers, eNodeBs, Subscribers (2 per UE sometimes) or even Hosts, etc. Tooltips on the TDF Parameter: 

Note that the “ID” is a unique ID. Please Provide the ID when reporting issues with a TDF. For TDFs that do not apply / override Parameters, but instead are just their own configuration or data or media files you won’t see TDF ID row details.

TIP: When including large files, please be aware of memory limitations, since the TDF Editor shares memory with the Client.

NOTE: The available TDF options vary. on the L3-7 | IPSec tab > IKE with RSA Settings you may only select the Certificate TDF from TAS (these are non-CSV TDFs).

In addition, where applicable, any rules for defining TDFs are included in specific Test Cases. (For example, In MME Node test case, see MME Node - Provisioning TDF.)

From the DMF Window, press Shift+Alt+A to display the  Save DMF as Tcl window. Click the Save to File button to save as Tcl file. See additional details on Using the Tcl API.

 

Select/Create a new TDF-CSV

Allows you to create a new TDF by entering a file name that doesn’t already exist or select an existing file by entering a file name that already exists.

Click to open the Select Existing or Create window.

  • Navigate to the relevant library/folder,

  • Enter the name of the file:

  • If the file name already exists, the file is selected and applied in the test case.

  • If the file name does not exist, a message displays that says you are creating a new TDF and the embedded TDF-CSV will be launched.

    • Click Yes to launch the TDF-CSV Editor and create/save the new TDF-CSV.

    • Click No to select a different file

NOTE: If you do not have permission to save in the selected library, an error displays when you try to create a new file.
TIP: You may also navigate to the relevant library/folder and select file, and click OK.

 

Upload a New TDF to TAS

Click to import a new TDF file from your local folder and select in the test Case (instead of having to go to TDF Admin).

  • Navigate to the file on your local folder and select.
  • Then navigate to the location (library) where you want to save it on the TAS. You may rename the file, if required.  

View Edit Selected TDF in TDF-CSV Editor

Available only when you have selected a TDF on TAS. Click to open the selected file in TDF-CSV Editor (in place, that is, within the Test Case).

Edit the file and save. You may also click Save As to save the edited TDF-CSV to a different library and also rename the file, if required.

NOTE: You may also select a TDF from a library to which you do not have write permissions, edit the file as required, and save (Save As) only to a different library with the same file name or a different name.

The only options available are Save As and Cancel.

Open Selected TDF in Standalone TDF-CSV Editor

Available only when you have selected a TDF on TAS. Select to retrieve the CSV file and open it in the stand alone TDF-CSV Editor.

Generate Stub TDF-CSV

TIP: Available only when a CSV specification has been defined for in the Test Case for the TDF widget ( View TDF Actions/Options Menu)

 

Opens an example context specific test data parametersexample context specific test data parameters, which you may save as a .CSV file or open in the TDF-CSV Editor.

 

Launch Standalone TDF-CSV Editor

Click to open a blank TDF-CSV Editor.

The Launch Standalone TDF-CSV editor options handles very large TDFs that may use too much Client memory if opened within the Test Case/in the embedded editor.  You may set the standalone TDF-CSV Editor memory high to edit large TDFs.

 

How to define VSA/AVP in TDF 

IPSec

When your test system is licensed for the Dynamic IPSec feature, you can use the checkbox to add IPSec encryption to Diameter messages. When you check the box, the Diameter IPSec tab is added to the test case.

Tcl Parameter: DiaSrvIpsecEn

In DCCA Nodal test Case, Diameter IPSec is only available when the test is configured with 1 Client Node, Primary Server only, and 1 Port.

Related Measurements

Number of Ports

Default is one port. When failover is supported, use the number of ports to enable transport layer communications for the secondary links (for failover purposes).

The number of ports allows opening of a multiple TCP connections to the DCCA Server node/DRA Node using different source ports.  The Number of Ports parameter applies to Primary Server only configurations and allows a MS to establish a DCC session for each port provisioned.  

For example, if Number of Ports is configured as 30 and MS is configured as 1, the test will perform 30 CER/CEA exchanges. Similarly, setting Number of Ports to 1 will result in 1 CER/CEA exchange. The source port will be unique for each exchange. A maximum of 30 unique ports is supported.

Select the number of ports.

Option: 1 — 30

Default: 1

Connected to Proxy Server

Use the checkbox to indicate that a Diameter proxy server is between the peers.

Tcl Parameter: DiaSrvProxyEn

 

 

 

^ Back to Top

 

Transmission Protocol

Use the drop-down list to select the underlying protocol layer.

Options: TCP or SCTP

Default: TCP

Tcl Parameter: DiaSrvProtocol
Number of Peers

Use the drop-down list to select the maximum number of peers that can establish a connection with a server node in a Diameter test. The server node will refuse any attempted TCP connections once the maximum number of connections have been established.

NOTES:
  • When you select the Diameter If IPSec checkbox, the number of tunnels is set by the Number of Peers.
  • If the Number of Peers is > 4, the Diameter IPSec will be turned off and the checkbox disabled on the DCCA Server Node Emulator Configuration tab.
  • Used in PCRF Node (Rx/Tx) Interfaces as of Release 15.0 - replaces Number Of Ports.

Options: 1 — 30

Default: 1

Tcl Parameter: DiaSrvNumPeers

Tcl Parameter: TxSrvNumPeers

Tcl Parameter: RxSrvNumPeers

Related Measurements
Wait Response Time/Retry Time

The amount of time, in milliseconds, that the node will wait for a response from a peer if a response is expected. When the time expires and the Retry Count has not been exceeded, the message is re-transmitted. Enter 0 to disable the timer.

Range: 0 — 65535

Default: 30

Tcl Parameter:

(Prefix + Cin/Srv+ RetryTime; Prefix=the application, for example: HSS, Tx, Rx, Gcx, and so on)

DiaSrvRetryTime

TxInRetryTime
NOTE: The Retry Time is used for timing of RAR/RAA transactions. As the Stop procedure consists of RAR / RAA plus

CCR-T / CCA-T, the Retry Time is also used for graceful stop of a test session (Stop-Timer = Retry-Timer*2). For example, when you click STOP on the Test Session window.

In DRA Nodal test case, if there is no response from the SUT, MN may resend requests multiple times based on the retry-time and retry-count value.

AAA Testing

This timer also controls the amount of time the node will reserve an IP address until an accounting session is started when the IP Address Allocation Feature is enabled.

Related Measurements
Retry Count

The maximum number of times a message will be sent/retransmitted. The default (1) disables retries.

The Retry Count does not apply in DRA Node TC.

Range: 1 - 65535

Default: 1
Watchdog Time

The number seconds to wait before sending a Device Watchdog Request to a peer. If any Diameter message is received from the peer before the time expires, the timer is reset. Enter 0 to disable the timer.

Range: 0 — 1000

Default: 30

Tcl Parameter: DiaSrvWatchTime

Related Measurements
Session ID Format

Only enabled on eMBMS node's SGmb|Diameter Tab (when mode = BMSC).

Options: Diameter Identity;high 32 bits;low 32 bits or Diameter Identity;IP Address;Auto Increment

Tcl Parameter : BmscSrvSessionIdFmt
Initiate Connection

Enable (checked)  to indicate whether a node should initiate a connection toward a DRA agent or should wait (unchecked) for new connect requests (i.e wait for receiving TCP SYNC packets) from a DRA agent.

Available on HSS Nodal test case when emulated interface = S6a, S6d, Sh, Cx, S13, S13'. Default = checked (True).

HssClnInitConnectionEn

 HssCxIcscfClnInitConnectionEn HssCxScscfClnInitConnectionEn

ShClnInitConnectionEn

 EirClnInitConnectionEn  

 
 Enable TLS

Available when Transmission Protocol is TCP, Test case = DRA Nodal, HSS  (S6a/S6d), PCRF, Gx, RX, Sd, Sy and S9 Tabs.

Enable (checked)  to support Diameter protocol over  TLS. The TLS tab will appear just below the Diameter tab.

Tcl Parameter:

HssClnTlsEn

HssSrvTlsEn

TyCcClnTlsEn

TyCcSrvTlsEn

 S9ClnTlsEn SdSrvTlsEn

SyClnTlsEn

 TxClnTlsEn  

 

^ Back to Top

Include Charging Information AVP

In PCRF Node test case, select to configure the grouped Charging-Information AVP to be included in CCA(I) as part of the initial PCC rule provisioning.

Select the charging information AVP and enter the required text as required.

  • Primary Event Charging Function Name
  • Secondary Event Charging Function Name
  • Primary Charging Collection Function Name
  • Secondary Charging Collection Function Name

Option: 1 - 255 characters

Tcl Parameters:

TyCcSrvPriChrgFuncNameEn TyCcSrvPriChrgFuncName
TyCcSrvSecChrgFuncNameEn TyCcSrvSecChrgFuncName
TyCcSrvPriCollFuncNameEn TyCcSrvPriCollFuncName
TyCcSrvSecCollFuncNameEn TyCcSrvSecCollFuncName

 

^ Back to Top

Failover Simulation

Failover

When OCS Node Configuration supports primary and secondary servers or proxies, you can enable or disable failover support. Transport layer failure on the primary node can be simulated at a time that you define. The node notifies the client whether failover is supported or not with the CC-Session-Failover AVP

On PGW Node test case, Failover Simulation is available for the Gx Interface when Secondary PCRF AGW is enabled on Network Devices.

On IMS Node test case, Failover Simulation is available for the Rx Interface when Secondary AF SUT is enabled on Network Devices.

 

Options: Not Supported or Supported

Default: Supported

TyCcClnFailover

TxClnFailover

DiaSrvCcFailover

 

Simulate Failover

Use the drop-down list to enable failure simulation.

Options: No, Transport Loss , Communication Loss

Default: No

Enter Duration (s) in seconds for the Failover Simulation.

Range : 1 to 100000

Default: 1000

NOTES:
  • Transport Loss option is available and may be simulated when you select Secondary Proxy on the OCS Node Emulator Configuration tab.
  • Communication Loss option is available and may be simulated when you select Secondary OCS Node on the Emulator Configuration tab.
Transport Loss

An established connection experiences packet transmission loss or impairment, where the failover mechanism may be set to trigger immediately, After X sessions established or X seconds after all sessions have established.
Communication Loss

An established connection experiences communication loss, where the failover mechanism may be set to trigger immediately, After X sessions established or X seconds after all sessions have established.  

 

TyCcClnFailoverType

TxClnFailoverType

DiaSrvCcFailoverType

TyCcClnFailoverDuration

TxClnFailoverDuration

DiaSrvCcFailoverDuration

 

Start Failover

Use the drop-down list to select the simulated failure trigger.

Options:

  • Before Any Sessions Established — The node will stop responding after the Capabilities Exchange.

NOTE: This option applies to permanent transport loss as the failover mechanism is triggered before socket connections were established.     In the case of temporal transport loss, the option to start failover Before Any Sessions Established doesn't apply, as the failover mechanism starts as soon as connection establishment is attempted.

  • After X Sessions Established — The node will stop responding after the number of sessions provisioned in X have been established.

  • X Seconds After All Sessions Established — The node will wait for X seconds after the maximum Number of Sessions have been established and then stop responding. If all sessions are not successfully established, the failure will not be triggered. Range of X = 1 to 400000 seconds.

Default: Before Any Sessions Established

TyCcClnFailoverStart

TxClnFailoverStart

DiaSrvCcFailoverStart

TyCcClnFailoverDelay

TxClnFailoverDelay

DiaSrvCcFailoverDelay

 

 

T4 Options

Send Experimental Result 

 

Delay Message Delivery Report (ms)

Available in the SMS Network test case when SMS-SC   T4

 is enabled. Enable to send an experimental result.

Options: DIAMETER_ERROR_USER_UNKNOWN (5001), 
DIAMETER_ERROR_INVALID_SME_ADDRESS (5530), 
DIAMETER_ERROR_SC_CONGESTION (5531), 
DIAMETER_ERROR_TRIGGER_REPLACE_FAILURE (5533), 
DIAMETER_ERROR_TRIGGER_RECALL_FAILURE (5534), 
DIAMETER_ERROR_ORIGINAL_MESSAGE_NOT_PENDING (5535)

Default: DIAMETER_ERROR_USER_UNKNOWN (5001)

Enter the Delay Message Delivery Report in milliseconds.

Range : 0 to 65535

Default : 0

T4SendExpResEn

T4SendExpResCode

T4DelayMsgDelRptTime

^ Back to Top

© 2024 Spirent Communications Inc. All Rights Reserved.