does anybody knows the default and definition of upcc h// parameter vrm_diamtimethrd?

[Tomas Delgado]

does anybody knows the default value and definition of upcc h// parameter vrm_diamtimethrd?

[live_energy]

does anybody knows the default value and definition of upcc h// parameter vrm_diamtimethrd?

Hey! For your reference.

Diameter Response Threshold (VRM_DIAMTIMETHRD)

This parameter specifies the threshold of the time taken for the PCRF to return a Diameter response. After this software parameter is specified, the value of the associated measurement entity increases by 1 when the time taken for the PCRF to return a Diameter response exceeds the value of this software parameter.


Value range: 0-10000


Unit: millisecond


Default value: 100


NOTE:
The setting of this software parameter depends on the network condition and the carrier's requirement on the network condition.


The default value is recommended if the carrier does not have special requirement on the network condition.
Set the parameter to a small value if the network condition is good and the carrier has a high requirement on the network condition.
Set the parameter to a larger value if the network condition is not good and the carrier has a high requirement on the network condition. This is to temporarily clear the associated alarms. After the network condition is improved, you can change the value of the parameter.


To simplify product maintenance, the carrier needs to set the threshold of the time taken for the PCRF to return a Diameter response.


To set VRM_DIAMTIMETHRD to 500 ms, perform the following steps:


In the MML Command - UPCC window, run LST INSP to query the value of this parameter:


LST INSP: SYSCP=SYSPARAMETER, INSPN=VRM_DIAMTIMETHRD;
If the value is not 500, you need to change it.


Run MOD INSP to change the value to 500.


MOD INSP: SYSCP=SYSPARAMETER, INSPN=VRM_DIAMTIMETHRD, INSPV=500;

[Tomas Delgado]

Thanks a lot friend, this has been very helpfull. If you know about something like this for HSS or any other DIAMETER network element, please let me know.

[live_energy]

Thanks a lot friend, this has been very helpfull. If you know about something like this for HSS or any other DIAMETER network element, please let me know.

For your reference:

HSS9860 (ATCA):

%%LST DIAMPP:;%%RETCODE = 0 Operation succeeded

The result is as follows
------------------------
Diameter parameter name Diameter parameter value Default parameter value Parameter value flag

UnanswerReqQueueLen 2536 2536 UNMODIFIED
RepeatCheckQueueLen 2536 2536 UNMODIFIED
PeerResponseTimer 20000 20000 UNMODIFIED
ApplicaResponseTimer 15000 15000 UNMODIFIED
ResponseBufferTimer 60000 60000 UNMODIFIED
InBandSecurityId 0 0 UNMODIFIED
FirmwareRevision 0 0 UNMODIFIED
Diameter heartbeat duration 60000 60000 UNMODIFIED
Diameter heartbeat timeout number 1 1 UNMODIFIED
Diameter send lower buffer size 10240 10240 UNMODIFIED
Link basic load (packets per second) 5000 5000 UNMODIFIED
Whether to use IP addresses of BSG type 1 1 UNMODIFIED
Whether to add Supported-Vendor-Id in CER 0 0 UNMODIFIED
Timeout for resend message when receive too busy 0 0 UNMODIFIED
Not relay message to the DRA 1 1 UNMODIFIED
Check IMS link port 1 1 UNMODIFIED
(Number of results = 16)
--- END

[Tomas Delgado]

Does somebody know the default vallue and/or description of timer T3 in UGW9811 SGW PGW? thanks

[Tomas Delgado]

Thanks brother, do you know the default vallue and/or description of timer T3 in UGW9811 SGW PGW? thanks. If by some case do you know what is the expected time between a gtpv2 request message and response. Maybe theres a kpi somewhere in an implementation guide or kpi troubleshooting guide. Thanks again.

[live_energy]

Thanks brother, do you know the default vallue and/or description of timer T3 in UGW9811 SGW PGW? thanks. If by some case do you know what is the expected time between a gtpv2 request message and response. Maybe theres a kpi somewhere in an implementation guide or kpi troubleshooting guide. Thanks again.

Hey! For your reference.

Using the undo t3-timer command, you can restore the interval at which the UGW9811 retransmits GTP request messages to the peer NE (MME, eNodeB, SGSN, S-GW, P-GW, or trusted non-3GPP gateway) and the maximum number of attempts to default values.

The granularity of the T3N3 (T3 and N3 are respectively the interval at which the UGW9811 retransmits GTP request messages to the peer NE and the maximum number of attempts) setting is categorized into three levels, namely, the global level, NE-type-based level, and message-type-based level. (In terms of the T3N3 setting specific to echo messages, only two levels are available, excluding the NE-type-based level). The global level has the lowest priority, whereas the message-type-based level has the highest priority. If no message-type-based setting is available, check whether the NE-type-based setting is available. If no NE-type-based setting is available, the global setting applies.


t3-timer timer-interval n3-times attempt-times [ gateway-type { sgw [ csr | mbr | dsr | cnr | mbc | dbc | brc | sn | rn | cbr | ubr | dbr | pdtn | ddn | prn ] * | pgw [ cbr | ubr | dbr | pdtn ] * | spgw [ cbr | ubr | dbr | ddn ] * | ggsn [ upcr | dpcr | apcr ] * } | echo ]


undo t3-timer n3-times [ gateway-type { sgw [ csr | mbr | dsr | cnr | mbc | dbc | brc | sn | rn | cbr | ubr | dbr | pdtn | ddn | prn ] * | pgw [ cbr | ubr | dbr | pdtn ] * | spgw [ cbr | ubr | dbr | ddn ] * | ggsn [ upcr | dpcr | apcr ] * } | echo ]


Usage Scenario
The t3-timer command is used to set the interval at which the UGW9811 retransmits GTP request messages to the peer NE and set the maximum number of attempts. The undo t3-timer command is used to restore the interval and maximum number of attempts to default values.


It is recommended that the T3N3 setting for DDN messages on the S-GW be consistent with that on the combined S-GW/P-GW. Otherwise, the T3N3 setting for DDN messages on the separated S-GW/P-GW or combined S-GW/P-GW applies if the following situation occurs: Two PDN connections are established on the separated S-GW/P-GW and combined S-GW/P-GW respectively for a subscriber. This is because DDN messages vary with subscriber information.


Example
# Set the interval for retransmitting GTP request messages and the maximum number of attempts to 10 seconds and 5 times, respectively.


<UGW> system-view
[UGW] access-view
[UGW-access] t3-timer 10 n3-times 5
# Set the interval at which the UGW9811 retransmits all GTP request messages to the peer NE to 10 seconds and the maximum number of attempts to 5 on the S-GW.


<UGW> system-view
[UGW] access-view
[UGW-access] t3-timer 10 n3-times 5 gateway-type sgw
# Set the interval at which the UGW9811 retransmits a Create Bearer Request message to the peer NE to 10 seconds and the maximum number of attempts to 5 on the S-GW.


<UGW> system-view
[UGW] access-view
[UGW-access] t3-timer 10 n3-times 5 gateway-type sgw cbr
# Set the interval at which the UGW9811 retransmits an Echo Request message to the peer NE to 10 seconds and the maximum number of attempts to 5.


<UGW> system-view
[UGW] access-view
[UGW-access] t3-timer 10 n3-times 5 echo

[Tomas Delgado]

Thanks a lot for your reply, I was checking and this timer is way to long. Does somebody know what is the expected time between a request and response in GTPV2, S1AP and NAS-EPS???