GTPv2 Cause Code Change for S6b Interface

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

  • P-GW

  • SAEGW

Applicable Platform(s)

  • ASR 5500

  • VPC-DI

Feature Default

Disabled - Configuration Required

Related Changes in This Release

Not Applicable

Related Documentation

  • Command Line Interface Reference

  • P-GW Administration Guide

  • SAEGW Administration Guide

  • Statistics and Counters Reference

Revision History

Revision Details

Release

First introduced.

21.24

Feature Description

When the S6b service is unreachable or connections are unstable while sending the Create Session Response, the S6b interface modifies the existing GTPv2 cause code 92/0x5C (user authentication failed) to cause code 73/0x49 (no resources available).

Configuring S6b Retry Code

Use the following configuration to apply S6b retry code from Diameter:

configure 
   context context_name 
      pgw-service service_name 
         egtp { reject-cause { no-resource [ s6b-link-failure ] { s6b-retry-code } } 
         [ no | default ] egtp reject-cause no-resource 
         end

NOTES:

  • reject-cause : Configures options for handling response with reject-cause.

  • no-resource : Configures handling for Create Session Response with cause code no-resource.

  • s6b-link-failure: Responds with no-resource for S6b server unreachability during authentication.

  • s6b-retry-code: Responds with no-resource for S6b diameter result-codes—3002, 3004, 3005 and 5198.

Monitoring and Troubleshooting

This section provides information regarding show commands and/or their outputs.

Show Command and Output

show pgw-service name <pgw_service_name>

The output of this command is enhanced to include the following fields. These fields indicate whether EGTP-C cause code mapping for S6b Link Failure and S6b Retry Code is enabled or disabled.

  • EGTP-C Cause Code Mapping (S6b Link Failure) : Enabled or Disabled

  • EGTP-C Cause Code Mapping (S6b Retry Code) : Enabled or Disabled