Universal Trace Analyzer
Error codes › GTPv2-C cause

GTPv2 cause 91 No memory available

GTPv2-C cause3GPP TS 29.274 §8.4 (Table 8.4-1)

What it means

The responding node ran out of memory processing this request (No memory available) -- an internal resource issue, not a policy rejection.

Where you see it

In the Cause IE of a GTPv2-C response (Create Session, Modify Bearer, Delete Session…) on S11, S5 or S8.

What to check

Report to the responding operator to check the state of their node(s).

Check which node sent the response (MME, SGW or PGW): the cause belongs to that node's decision.

Got a trace with GTPv2 cause 91 No memory available? Drop it in the analyzer: it finds the step that really failed first, which node sent the code and what to ask the other side. Captures, test-system PDFs and vendor exports. 5 free analyses a month, no sign-up.

Analyze a trace free

Related codes

GTPv2 cause 90 Unable to page UEThe network was unable to page the UE (Unable to page UE) -- it couldn…GTPv2 cause 92 User authentication failedThe subscriber failed authentication (User authentication failed) — al…GTPv2 cause 89 Service deniedThe network explicitly denied this service (Service denied).…GTPv2 cause 93 APN access denied - no subscriptionAccess denied — no subscription to this APN (APN access denied – no su…GTPv2 cause 88 UE refusesThe UE explicitly refused the request (UE refuses).…GTPv2 cause 94 Request rejected (reason not specified)The request was rejected without a more specific reason given (Request…