Guest

Preview Tool

Cisco Bug: CSCun36895 - PGW rejecting all IPv6 PDP Requests

Last Modified

Dec 26, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

14.0(1)

Description (partial)

Symptom:
W0575CnBPGP2 is rejecting all IPv4v6 requests with single-bearer-only-allowed, and all IPv6-only requests with no dynamic PDP address available. W0575CnBPGP1 has effectively same configuration, and works fine. This started after the IPv6 routing issues on Feb-11 and is still happening.

We have a mon sub from both PGW1(working) and PGW2(not working). In the failed case, we get a few errors:

***CONTROL*** 19:46:43:691 Eventid:10539
Destination context sgi_ctx has no IPv6 interface. Rejecting call

***CONTROL*** 19:46:43:691 Eventid:10755
Sessmgr-253 -- Local Pool IP Validation FAILED with disconnect reason <lpool-ip-validation-failed>, IP Address <::/0>, imsi <302610012405789>, apn <proxy1.bell.ca>

<<<<OUTBOUND  19:46:43:692 Eventid:47001(3)
GTPC Tx PDU, from 184.151.126.84:2123 to 184.151.62.105:19005 (14)
TEID: 0x830C8005, Message type: GTP_CREATE_PDP_CONTEXT_RES_MSG (0x11)
Sequence Number:: 0x54F4 (21748)
GTP HEADER FOLLOWS:
            Version number: 1
              Protocol type: 1 (GTP C/U)
       Extended header flag: Not present
       Sequence number flag: Present
           NPDU number flag: Not present
               Message Type: 0x11 (GTP_CREATE_PDP_CONTEXT_RES_MSG)
             Message Length: 0x0006 (6)
                  Tunnel ID: 0x830C8005
            Sequence Number: 0x54F4 (21748)
GTP HEADER ENDS.
INFORMATION ELEMENTS FOLLOW:
                      Cause: 0xD3 (GTP_ALL_DYNAMIC_PDP_ADDR_OCCUPIED)
INFORMATION ELEMENTS END.

All the IPv6 interfaces are down (intentionally) on both PGW1 and PGW2 due to the Feb-11 outages:

Conditions:
IP pool seems to be ok:

[sgi_ctx]W0575CnBPGP2# show ipv6 pool pool-name test_pool_v6 verbose
Tuesday February 18 19:51:45 UTC 2014
    Pool Name:     test_pool_v6
    Group Name:
    Pool Type:     Public        Priority: 1
    Pool Id:       2001
    Pool Status:   Good
    Start Prefix:  2605:b100:f300::/64
    End Prefix:    2605:b100:f300:ff::/64
    Total Prefix:  256        Used Prefix: 2      Free Prefix: 254
    Pool Address Type: Normal
    Configured Prefix: 2605:b100:f300::/56
                 Nexthop Forwarding Address: Disabled
                   Suppress-Switchover-ADVS: Disabled
                    Allow-Static-Allocation: Enabled
                   Duplicate-Addr-Detection: Disabled
                  Group Available Threshold: Disabled    Clear: Disabled
                        Pool-Free Threshold: Disabled    Clear: Disabled
                        Pool-Used Threshold: Disabled    Clear: Disabled

[sgi_ctx]W0575CnBPGP1# show ipv6 interface summary
Tuesday February 18 19:59:42 UTC 2014
Interface Name                 Address/Mask        Port               Status
============================== =================== ================== ======
int1_sgi_v6                    2605:b100:f2f6:20::2/64 20/1 vlan 1619     DOWN
int2_sgi_v6                    2605:b100:f3f6:20::2/64 21/1 vlan 1621     DOWN
int3_sgi_v6                    2605:b100:f2f6:21::2/64 22/1 vlan 1620     DOWN
int4_sgi_v6                    2605:b100:f3f6:21::2/64 23/1 vlan 1622     DOWN

Total interface count: 4

[sgi_ctx]W0575CnBPGP2# show ipv6 interface summary
Tuesday February 18 19:59:48 UTC 2014
Interface Name                 Address/Mask        Port               Status
============================== =================== ================== ======
int1_sgi_v6                    2605:b100:f2f6:30::2/64 20/1 vlan 1623     DOWN
int2_sgi_v6                    2605:b100:f3f6:30::2/64 21/1 vlan 1625     DOWN
int3_sgi_v6                    2605:b100:f2f6:31::2/64 22/1 vlan 1624     DOWN
int4_sgi_v6                    2605:b100:f3f6:31::2/64 23/1 vlan 1626     DOWN

Total interface count: 4

But only PGW2 is rejecting the PDPs, and we know it started doing this after the Feb-11 outage.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.