PFCP

tmnxPfcpInvalidIe

Table 1. tmnxPfcpInvalidIe properties
Property name	Value
Application name	PFCP
Event ID	2001
Event name	tmnxPfcpInvalidIe
SNMP notification prefix and OID	TIMETRA-SUBSCRIBER-MGMT-MIB.tmnxSubscriberNotifications.56
Default severity	warning
Source stream	main
Message format string	Invalid IE ignored in PFCP request for session $tmnxPfcpSeIdHigh$: $tmnxPfcpSeIdLow$: $tmnxSubAdditionalInfo$
Cause	The system receives a PFCP request containing an Information Element that it considers invalid but still continues processing the rest of the request. The reason why the IE is considered invalid is given in the object tmnxSubAdditionalInfo.
Effect	The system may still set up the PFCP session but without some of the requested properties.
Recovery	Recovery, if any, depends on the cause.

Table 2. tmnxPfcpNoSecondaryInterface properties
Property name	Value
Application name	PFCP
Event ID	2003
Event name	tmnxPfcpNoSecondaryInterface
SNMP notification prefix and OID	TIMETRA-SUBSCRIBER-MGMT-MIB.tmnxSubscriberNotifications.58
Default severity	warning
Source stream	main
Message format string	The secondary GTP interface in network instance $tmnxPfcpVRtrID$ that is indicated in a PFCP request for session $tmnxPfcpSeIdHigh$:$tmnxPfcpSeIdLow$ does not exist: $tmnxSubAdditionalInfo$
Cause	The system receives a PFCP request containing a Traffic Endpoint Information Element with a Network Instance that refers to the secondary GTP interface and this system has no secondary GTP interface configured.
Effect	The system will still set up the PFCP session but using the primary GTP interface.
Recovery	In the network instance indicated by 'tmnxPfcpVRtrID', configure the secondary GTP interface with the object 'TIMETRA-WLAN-GW-MIB::tmnxGtpUpfDataEndptSecItfName'.

Table 3. tmnxPfcpNoSuchCalltraceProfile properties
Property name	Value
Application name	PFCP
Event ID	2002
Event name	tmnxPfcpNoSuchCalltraceProfile
SNMP notification prefix and OID	TIMETRA-SUBSCRIBER-MGMT-MIB.tmnxSubscriberNotifications.57
Default severity	warning
Source stream	main
Message format string	Unknown calltrace trace-profile $tmnxSubNotifName$ in PFCP request for session $tmnxPfcpSeIdHigh$:$tmnxPfcpSeIdLow$: $tmnxSubAdditionalInfo$
Cause	The system receives a PFCP request containing an Information Element that refers to a call-trace trace-profile while there is no such trace-profile present in the system configuration but a default trace-profile is configured for the PFCP association. There is a mismatch between the operation of the Control Plane (CP) and the call-trace configuration in this User Plane (UP) system.
Effect	The system performs call tracing for the session but uses a default trace-profile rather than the requested one.
Recovery	Remove the mismatch between the operation of the Control Plane (CP) and the call-trace configuration in this User Plane (UP) system.