A tmnxMobGwPathMgmtPeerState notification is generated when there
has been a change in the reference point peer state during path
management.

A tmnxMobGwCfCapacityAlmMjrClear notification is generated when 
compact flash capacity drops below 90% limit.

A tmnxMobGwSysGrpRedStateChange notification is generated when the 
the redundancy state of a group changes. 
          
[CAUSE] A working card failure, changing the redundancy configuration,
        or adding a protection card will trigger a change to the 
        group's redundancy state.
          
[EFFECT] When the value of tmnxMobGwSysGroupRedState changes from
         'hot' to 'cold', a switchover has happened. No services are 
         affected when the value of tmnxMobGwSysGroupRedState changes.
          
[RECOVERY] After a switchover has happened, no backup card will be up.
           The operator needs to bring a backup card online to avoid
           any disruption to services in case of further failures.

A tmnxMobGwSysGrpCardRedStChange notification is generated when the 
the redundancy state of this card changes.
          
[CAUSE] A card failure will change the card redundancy state to 
        'notValid'. When an active card goes down, standby card will 
        become active which will trigger a state change to 'active'. 
        When a 'standbyInProg' card becomes in sync with the active 
        card, state will be changed to 'standby'.
          
[EFFECT] When card goes down, it will not be able to provide any
         mobile gateway services supported by the system.
          
[RECOVERY] If the card goes down, operator's assistance is needed to 
           get the card back online.

A tmnxMobGwGtpPriServFailAlarm notification is generated when GPRS 
Tunneling Protocol (GTP) Prime Server failure is detected.

A tmnxMobGwGtpPriServFailAlarm notification is generated when GPRS 
Tunneling Protocol (GTP) Prime Server is recovered from the previous 
failure.

A tmnxMobGwGtpPriServFailAlarm notification is generated when a new
GPRS Tunneling Protocol (GTP) Prime Server is selected after the
failure of the active server.

A tmnxMobGwGtpPriGrpFailAlarm notification is generated when all GPRS 
Tunneling Protocol (GTP) Prime Server have failed in the GTP Prime
Server Group.

A tmnxMobGwGtpPriGrpFailAlarmClrd notification is generated when 
a previously failed GTP Prime Server Group has at least one
operational GTP Prime Server.

A tmnxMobGwRadPeerFailAlarm notification is generated when the Radius
Server failure is detected.
          
[CAUSE] This happens when the operating state for radius server is 
changed to 'down' state
          
[EFFECT] When the radius server fails, radius messages may not be 
sent to the radius-server
          
[RECOVERY] If the radius server goes down, the radius server will 
allow radius-messages to be sent to it when its operating state is 
changed to 'up' state or after deadtimer expiring.

A tmnxMobGwRadPeerFailAlarm notification is generated when the Radius
Server is recovered from the previous failure.
          
[CAUSE] The radius server is recovered from the previous failure
and its Operating-State is changed to 'up' state. 
          
[EFFECT] When the radius server is recovered from the previous failure, 
and operation for the radius-server is back to normal.
          
[RECOVERY] If the radius server is recovered from the previous failure, 
no further action is needed.

A tmnxMobGwDiameterPeerState notification is generated when there
has been a change in the reference point peer state for the diameter 
application.

A tmnxMobGwRadGrpFailAlarm notification is generated when all the 
radius servers have failed in the radius server group.
          
[CAUSE] This event will be generated when all the radius servers 
for the group are in operating 'down' state. 
          
[EFFECT] When the group of radius servers fails, radius messages 
may not be sent to the group.
          
[RECOVERY] The radius group will recover from this failure mode when 
one of its server is going back to operating 'up' state.

A tmnxMobGwRadGrpFailAlarmClrd notification is generated when 
a previously failed Radius Server Group has at least one
operational Radius Server.
          
[CAUSE] The radius server group is recovered from the previous failure
and at least one of its servers has transitioned to operating 'up' 
state.
          
[EFFECT] When the radius server group is recovered from the previous 
failure and operation for the radius-group is back to normal.
          
[RECOVERY] If the radius group is recovered from the previous failure, 
no further action is needed.

A tmnxMobLiDf2OperStateChange notification is generated when the 
current operational state of the Delivery Function 2 peer changes.
          
[CAUSE] The df2-peer's operational state will change when the TCP
connection's state to the df2-peer changes.
          
[EFFECT] When the df2-peer's state is down, the Intercept Related
Information (IRI) packets are not sent to the peer. When the  
df2-peer's state is up, the IRI packets are sent to the peer. 
          
[RECOVERY] If the df2-peer goes down, then the IRI packets being sent 
to the peer will be buffered until it comes up. Then, all the packets 
will be sent to the peer.

A tmnxMobGwGtpPriServerState notification is generated when there
has been a change in the when GPRS Tunneling Protocol (GTP) Prime
Server state for all mobile system groups.
          
[CAUSE] When there is a change in GTP Prime Server State.
          
[EFFECT] When the GTP Prime Server State is add, the server has been
added to the system. When the state is delete, the server has been
deleted from the system. When the state is down, Charging Data
Record (CDR) packets are not sent to the peer. When the state is up,
CDR packets can be sent to the peer. 
          
[RECOVERY] If a GTP Prime server state is down, then Charging Data
Request(CDR) packets will be sent to an alternate GTP Prime server.
If no servers are available, CDR packets will be written to CDR files.

A tmnxMobGwSysGrpGtpPriServerState notification is generated when there
has been a change in the when GPRS Tunneling Protocol (GTP) Prime
Server state per mobile system group.
          
[CAUSE] When there is a change in GTP Prime Server State.
          
[EFFECT] When the GTP Prime Server State is add, the server has been
added to the system. When the state is delete, the server has been
deleted from the system. When the state is down, Charging Data
Record (CDR) packets are not sent to the peer. When the state is up,
CDR packets can be sent to the peer. 
          
[RECOVERY] If a GTP Prime server state is down, then Charging Data
Request(CDR) packets will be sent to an alternate GTP Prime server.
If no servers are available, CDR packets will be written to CDR files.

A tmnxMobGwGtpPriSrvGrpState notification is generated when there
has been a change in the when GPRS Tunneling Protocol (GTP) Prime
Server state for all mobile system groups. 
          
[CAUSE] When there is a change in GTP Prime Server Group State.
          
[EFFECT] When the GTP Prime Server Group State is add, the group has
been added to the system. When the state is delete, the group has been
deleted from the system. When the state is down means all GTP Prime 
Servers in the group are down, and Charging Data Record (CDR) packets
are not sent to the group server. When the state is up, CDR packets can
be sent to the group server. 
          
[RECOVERY] If a GTP Prime server group state is down, CDR packets will
be written to CDR files until at least one server becomes available.

A tmnxMobGwGtpPriSrvGrpState notification is generated when there
has been a change in the when GPRS Tunneling Protocol (GTP) Prime
Server state per mobile system group. 
          
[CAUSE] When there is a change in GTP Prime Server Group State.
          
[EFFECT] When the GTP Prime Server Group State is add, the group has
been added to the system. When the state is delete, the group has been
deleted from the system. When the state is down means all GTP Prime 
Servers in the group are down, and Charging Data Record (CDR) packets
are not sent to the group server. When the state is up, CDR packets can
be sent to the group server. 
          
[RECOVERY] If a GTP Prime server group state is down, CDR packets will
be written to CDR files until at least one server becomes available.

A tmnxMobGwSysGrpWriteCdrToCfAlarm notification is generated when the
SGW or PGW starts to write Charging Data Record (CDR) packets to the
local compact flash for the mobile system group.
          
[CAUSE] When there is a change in action to write Charging Data
Record (CDR) packets to compact flash.
          
[EFFECT] When the action is start, the system has started writing CDR
packets to files on compact flash. the system has stopped writing CDR
packets to files on compact flash.
          
[RECOVERY] Retrieve CDR files from compact flash.

The tmnxMobGwSysGrpDiameterPeerState notification is generated when
there has been a change in the state of a reference point peer in
the diameter application per mobile system group.        
          
[CAUSE] When there is a change in Diameter Peer State.
          
[EFFECT] If the value of tmnxMobGwNtfyDiameterPeerState is 'pathDown'
for the mobile system group, then the diameter application supported on
that connection will not function between the given mobile system group
and the given diameter peer.
          
[RECOVERY] If the value of tmnxMobGwNtfyDiameterPeerState is 'pathDown'
for a mobile system group, the operator may have to take an action to
investigate and recover the connection between the mobile system
group and the diameter peer.

A tmnxMobGwAcrFailuresAlarmMajor notification is generated when 2 
ACR transmission failures occur in a 10 second interval or 5 
ACR transmission failures occur in a 60 second interval to the peer. 
          
[CAUSE] Charging Data Functions (CDF) peer is slow to respond to RF ACR
        message requests or it is not responding to RF ACR message
        requests but from a diameter connection perspective the peer
        is still in service.
          
[EFFECT] The gateway will choose a secondary CDF peer to send the RF
         accounting messages for the failure attempts.
          
[RECOVERY] Diagnose why the CDF peer is slow to respond or why it is
           not responding to RF accounting message requests.

A tmnxMobGwCdfDownAlarm notification is generated when both 
the primary and the secondary Charging Data Functions (CDFs) are down 
for active Rf diameter sessions.
          
[CAUSE] CDF peers are down or communication paths to the peers are
        down.
          
[EFFECT] RF accounting messages will be stored locally on compact
         flash of the gateway.
          
[RECOVERY] Recover CDF peers or communication links with the peers.

A tmnxMobGwCdfDownAlarmCleared notification is generated when one of  
the primary and the secondary Charging Data Functions (CDFs) becomes up 
for active Rf diameter sessions.

A tmnxMobGwAcrFailuresAlarmClear notification is generated after the
tmnxMobGwAcrFailuresAlarmMajor notification when the first time less 
then 2 Accounting Request (ACR) transmission failures occurred in a 10
seconds interval or the first time less then 5 ACR transmission 
failures occurred in a 60 seconds interval to the peer.

A tmnxMobGwCfCapacityAlarmMinor notification is generated when compact 
flash capacity reaches 85% limit.
          
[CAUSE] Compact flash capacity is low because a CDF outage has occurred
        and accounting messages are stored locally on the compact
        flash of the gateway.
          
[EFFECT] There is limited space to store accounting messages on the
         compact flash of the gateway. Accounting messages will be lost
         when the compact flash has no space left.
          
[RECOVERY] Pull Accounting files from the gateway and them delete the
           files from the compact flash.

A tmnxMobGwCfCapacityAlmMnrClear notification is generated when 
compact flash capacity drops below 80% limit.

A tmnxMobGwCfCapacityAlarmMajor notification is generated when compact 
flash capacity reaches 95% limit. 
          
[CAUSE] Compact flash capacity is low because a CDF outage has occurred
        and accounting messages are stored locally on the compact
        flash of the gateway.
          
[EFFECT] There is limited space to store accounting messages on the
         compact flash of the gateway. Accounting messages will be lost
         when the compact flash has no space left.
          
[RECOVERY] Pull Accounting files from the gateway and them delete the
           files from the compact flash.