1. Alarms and KPIs
  2. Alarms and Events
  3. Diameter Alarms and Events (8000-8299, 22000-22350, 22900-22999, 25600-25899)
  4. 22349 - IPFE Connection Alarm Aggregation Threshold

3.9.102 22349 - IPFE Connection Alarm Aggregation Threshold

Alarm Group:
DIAM
Description:

This alarm occurs when there are a ‘Critical’ number of IPFE connection alarms for the network element.

The Alarm Thresholds are configurable using the Alarm Threshold Options tab on Diameter, and then Configuration, and then System Options.

The IPFE connection may not be established for a variety of reasons. The operational status of this connection is displayed on the GUI as unavailable and Alarm 22101 Connection Unavailable is raised.

When the number of unavailable IPFE connections exceeds the defined threshold, IPFE Connection Failure Major/Critical Aggregation Alarm Threshold (default is 100/200), alarm 22349 is raised by the DSR.

Severity:
Major, Critical

Note:

The Critical threshold may be disabled by setting the Critical Threshold to zero using the Alarm Threshold Options tab on Diameter, and then Configuration, and then System Options.
Instance:
<NetworkElement>
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
eagleXgDiameterIPFEConnUnavailableThresholdReachedNotify
Cause:
The IPFE connection may not be established for a variety of reasons. The operational status of this connection is displayed on the GUI as unavailable and Alarm 22101, Connection Unavailable is raised.
img/alarm_22349.png
When the number of unavailable IPFE connections exceeds the defined threshold, IPFE Connection Failure Major/Critical Aggregation Alarm Threshold (default is 100/200), alarm 22349 is raised by the DSR.
Diagnostic Information:
Perform the following:
  • Use Wireshark to capture the diameter traffic on all MPs under the concerned TSA list and the primary IPFE. Save the PCAP traffic capture generated by Wireshark.
  • Verify the connection configurations (IP addresses, ports, peer node, protocol) are correct.
  • Verify peer-connection configurations (protocol, remote/local IP address, remote/local port) matches local connection configurations.
  • Verify the connection's transport protocol and/or port are not being blocked by a network firewall or other ACL in the network path.

Recovery:

  1. Navigate to Diameter, and then Maintenance, and then Connection to monitor IPFE Connection status.
  2. Confirm peer connection configuration (protocol, remote/local IP address, remote/local port) matches the local connection configuration.
  3. Confirm the connection’s transport protocol and/or port are not being blocked by a network firewall or other ACL in the network path.
  4. Verify the peers in the Route List are not under maintenance.
  5. Use Wireshark to analyze all the captured PCAP data to find where the message exchange is broken or failed. Wireshark should be the main tool used to diagnose the unavailable connection.
  6. Based on the PCAP file, correct the configuration if the issue is on the DSR side. The Alarm will be cleared automatically when the numbers of unavailable IPFE connections are under the IPFE Connection Failure Critical/Major Aggregation Alarm Threshold.
  7. If the issue is on the DSR side or you are not sure, it is recommended to contact My Oracle Support for assistance.