gtpp attribute secondary-rat-usage
By default this CLI command is enabled in gtpp group.
|
P-GW sends secondary RAT usage records in CDR including zero volume records.
|
S-GW sends secondary RAT usage records in CDR including zero volume records.
|
[ no ] gtpp attribute secondary-rat-usage
|
P-GW does not send secondary RAT usage records in CDR.
|
S-GW does not send secondary RAT usage records in CDR.
|
gtpp suppress-secondary-rat-usage zero-volume
By Default, this CLI command is disabled in gtpp group.
|
P-GW does not include and send zero volume secondary RAT records in CDR. P-GW sends only secondary RAT records that is having
non-zero volumes.
|
S-GW does not include and send zero volume secondary RAT records in CDR. S-GW sends only secondary RAT records that is having
non-zero volumes.
|
[ no ] gtpp suppress-secondary-rat-usage zero-volume
|
P-GW sends secondary RAT usage records including zero volume records in CDR.
|
S-GW sends secondary RAT usage records including zero volume records in CDR.
|
gtpp limit-secondary-rat-usage
range_1–100 . If not configured, the default value is 32. By default this CLI command is enabled in gtpp group.
Example: gtpp limit-secondary-rat-usage 32
Note
|
This CLI is the modification of the existing CLI command gtpp limit-secondary-rat-usage with range between 1– 100.
|
|
PGW generates CDR immediately when total received secondary RAT records exceeds 32 and reported cause value is maximum change condition .
P-GW generates multiple CDRs if total received secondary RAT records are multiples of 32.
Example: If P-GW receives 100 RAT records between two triggers, PGW generates 3 CDRs and keeps the remaining 4 RAT records for the
next CDR trigger.
|
S-GW generates CDR immediately when total received secondary RAT records exceeds 32 and the reported cause value is maximum change condition .
S-GW generates multiple CDRs if the total received secondary RAT records are multiples of 32.
Example: If S-GW receives 100 RAT records between two triggers, S-GW generates 3 CDRs and keeps the remaining 4 RAT records for the
next CDR trigger.
|
Example:gtpp limit-secondary-rat-usage 40
|
P-GW generates CDR immediately when total received secondary RAT records exceeds 40 and cause value is maximum change condition .
P-GW generates multiple CDRs if total received secondary RAT records are multiples of 40.
Example: If P-GW receives 100 RAT records between two triggers, it will generate 2 CDRs and will keep remaining 20 RAT records for
the next CDR trigger.
|
If the configured value is greater than 32 and sends 32 secondary RAT records in every CDR, Ignores gtpp limit-secondary-rat-usage 40 CLI command.
|
Example:gtpp limit-secondary-rat-usage 20
|
P-GW generates CDR immediately when total received secondary RAT records exceed 20 and cause value is maximum change condition .
P-GW generates multiple CDRs if total received secondary RAT records are multiples of 20.
Example: If P-GW receives 100 RAT records between two triggers, P-GW generates 2 CDRs and will store the remaining 20 RAT records
for next CDR trigger.
|
S-GW generates CDR immediately when the total received secondary RAT records exceeds 20 and cause value is maximum change condition .
S-GW generates multiple CDRs if total received secondary RAT records are in multiples of 20.
Example: If S-GW receives 100 RAT records between two triggers, it will generate 5 CDRs.
|
[ no ] gtpp limit-secondary-rat-usage
|
Generates CDR immediately when the total received secondary RAT records exceed 255 and cause value is maximum change condition .
Generates multiple CDRs if the total received secondary RAT records are multiples of 255.
Example: If 1000 RAT records between two triggers are received, then 3 CDRs are generated. The remaining 235 RAT records are stored
for the next CDR trigger.
|
Ignores the [ no ] gtpp limit-secondary-rat-usage CLI and sends 32 secondary RAT records in every CDR.
Behavior is similar to the gtpp limit-secondary-rat-usage
32 CLI implementation.
Counter and debug logs are not required as it will never exceed the CDR size of 64k.
|
|
Service specific Unit Limit is sending in serviceConditionChange file
|
Record Closure
|