eCNS integratied and no response from the AF

BetterMing · Created Sep 16, 2020 11:20:35

You can refer to the following information

ALM-81175 No response from the AF

Description

Applicable NEs

P-GW

This alarm is generated when the eCore receives no response from the AF after retransmitting heartbeat messages and considers the communication path to the AF disconnected, the alarm cause is "Connection".

This alarm is cleared when the link between the eCore and the AF functions properly or the configurations for the AF, DIAMLOCINFO, DIAMPEERADDR, DIAMCONNGRP, DIAMCONNECTION are deleted.

Attribute

Alarm ID	Alarm Severity	Auto Clear
81175	Critical	Yes

Parameters

Name	Meaning
Local IP Address	Indicates the IP address of the local end generating the alarm.
Local Sub IP Address	Indicates the sub IP address of the local end generating the alarm. 255.255.255.255 indicates that the local sub IP address is not configured.
AF Host Name	Indicates the host name of the AF.
Peer IP Address	Indicates the IP address of the peer end generating the alarm.
Peer Sub IP Address	Indicates the sub IP address of the peer end generating the alarm. 255.255.255.255 indicates that the peer IP address is not configured.
Peer Port No.	Indicates the the number of the peer end generating the alarm.
Cause	Indicates the alarm cause.
VPN	Indicates the name of the VPN instance corresponding to the AF.

Impact on the System

The IP-CAN sessions associated with the AF are not affected, but subsequent AA-Request(AAR) and Re-Auth-Request(RAR) will be rejected.

Possible Causes

The physical link does not function properly.
The AF configurations on the eCore are incorrect.
The route to the AF is incorrectly configured on the eCore.
The communication path between the eCore and the AF is faulty.
The network between the eCore and the AF is congested.

Procedure

Check whether correlated alarms are generated.

Check whether correlated alarms are generated, including VM fault alarms, physical line down alarms, CPU overload alarms, interface probe fault alarms, and IP probe fault alarms.

Yes: Clear the alarms by following the handling procedures for these alarms.
No: Go to 2.

Check whether the eCore communicates with the AF properly.

Run LST DIAMPEERADDR to view the IP address of the AF and PING to initiate ping detection. Then check whether all ping requests time out.

Yes: Go to 3.
No: Go to 13.

Check whether AF configurations on the eCore are correct.

Run LST AF to check whether AF Host Name, AF Domain Name and VPN Instance Name on the eCore are correct.

Yes: Go to 5.
No: Go to 4.

Run RMV AF to delete the AF configurations, then run ADD AF to add the AF configurations, and check whether this alarm is cleared.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by incorrect AF configurations on the eCore.
No: Go to 5.

Check whether the route to the AF is correctly configured on the eCore.

Run DSP ROUTE to check whether whether the route to the AF is correctly configured on the eCore. Note that the VPN parameter must be configured correctly.

Yes: Go to 7.
No: Go to 6.

Update route configuration. Run RMV SRROUTE and ADD SRROUTE to modify the routing table on the eCore.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by the route failure between the eCore and the AF.
No: Go to 7.

Check whether the operating mode and rate of the eCore's physical interface for interworking with the AF match those configured on the peer switch.

Run LST INTERFACE to check whether the operating mode and rate of the eCore's physical interface for interworking with the AF match those configured on the peer switch.

Yes: Go to 9.
No: Go to 8.

Configure the operating mode and rate for the physical interface on the eCore. Check whether this alarm is cleared.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by the incorrect operating mode or rate of the physical interface.
No: Go to 9.

Check whether the eCore's physical interface for interworking with the AF functions properly.

Run LST INTERFACE to check whether the eCore's physical interface for interworking with the AF functions properly.

If both the physical status and the link protocol status of the physical interface are Up, the physical interface functions properly. If either the physical status or the link protocol status is Down, the physical interface does not function properly.
If the physical status of the physical interface is administratively Down, run MOD INTERFACE to enable the physical interface.

Yes: Go to 12.
No: Go to 10.

Check whether the network cable or optical fiber is faulty.

Reseat the network cable or optical fiber, and ensure that it is connected to the interface properly. Check whether this alarm is cleared.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by the loose connection of the network cable or optical fiber.
No: Go to 11.

Replace the faulty network cable or optical fiber with a sound one. Check whether this alarm is cleared.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by the network cable or optical fiber fault.
No: Go to 12.

Check whether the transmission path between the eCore and the AF functions properly.

Contact technical support engineers of the AF to capture packets on the AF. Check whether the AF receives the Diameter heartbeat request messages sent by the eCore at a regular interval.

Yes: Go to 13.
No: Go to 18. The alarm is caused by the transmission path fault between the eCore and the AF.

Contact technical support engineers of the AF to capture packets on the AF. Check whether the AF responds to all request messages from the eCore.

Yes: Go to 14.
No: Go to 15.

Check whether the quality of data transmission between the eCore and the AF is good.

On the WebLMT, capture packets on the Rx interface (using Gy interface trace) to check whether the eCore receives response messages to all request messages.

Yes: Go to 18. The alarm is caused by the packet loss due to network congestion between the eCore and the AF.
No: Go to 18. The alarm is caused by the packet loss due to incorrect router or firewall policy settings between the eCore and the AF.

Contact technical support engineers of related devices.

Contact technical support engineers of the AF to check whether the parameters for interworking with the eCore are configured correctly and whether the alarm is caused by wrong interworking parameter settings.

Yes: Go to 17. The alarm is caused by a fault on the AF.
No: Go to 16.

Contact technical support engineers.

Contact technical support engineers of the AF.

Contact technical support engineers of routers, switches, or transmission devices.

Related Information

To query AF configurations on the eCore, run LST AF.

To configure AF information on the eCore, run ADD AF or MODAF.

Unicef · Created Sep 16, 2020 10:19:10

Dear User, please find below:

Root Cause:
configuration error Of Local port Diam-connection
Handling Process:
check the script of eCNS280,found the local port has config error
Solution:
after modify the local port of DIAM-CONNECTION, the issue is solved.

port

Thanks!

BetterMing · Created Sep 16, 2020 11:20:35

You can refer to the following information

ALM-81175 No response from the AF

Description

Applicable NEs

P-GW

This alarm is generated when the eCore receives no response from the AF after retransmitting heartbeat messages and considers the communication path to the AF disconnected, the alarm cause is "Connection".

This alarm is cleared when the link between the eCore and the AF functions properly or the configurations for the AF, DIAMLOCINFO, DIAMPEERADDR, DIAMCONNGRP, DIAMCONNECTION are deleted.

Attribute

Alarm ID	Alarm Severity	Auto Clear
81175	Critical	Yes

Parameters

Name	Meaning
Local IP Address	Indicates the IP address of the local end generating the alarm.
Local Sub IP Address	Indicates the sub IP address of the local end generating the alarm. 255.255.255.255 indicates that the local sub IP address is not configured.
AF Host Name	Indicates the host name of the AF.
Peer IP Address	Indicates the IP address of the peer end generating the alarm.
Peer Sub IP Address	Indicates the sub IP address of the peer end generating the alarm. 255.255.255.255 indicates that the peer IP address is not configured.
Peer Port No.	Indicates the the number of the peer end generating the alarm.
Cause	Indicates the alarm cause.
VPN	Indicates the name of the VPN instance corresponding to the AF.

Impact on the System

The IP-CAN sessions associated with the AF are not affected, but subsequent AA-Request(AAR) and Re-Auth-Request(RAR) will be rejected.

Possible Causes

The physical link does not function properly.
The AF configurations on the eCore are incorrect.
The route to the AF is incorrectly configured on the eCore.
The communication path between the eCore and the AF is faulty.
The network between the eCore and the AF is congested.

Procedure

Check whether correlated alarms are generated.

Check whether correlated alarms are generated, including VM fault alarms, physical line down alarms, CPU overload alarms, interface probe fault alarms, and IP probe fault alarms.

Yes: Clear the alarms by following the handling procedures for these alarms.
No: Go to 2.

Check whether the eCore communicates with the AF properly.

Run LST DIAMPEERADDR to view the IP address of the AF and PING to initiate ping detection. Then check whether all ping requests time out.

Yes: Go to 3.
No: Go to 13.

Check whether AF configurations on the eCore are correct.

Run LST AF to check whether AF Host Name, AF Domain Name and VPN Instance Name on the eCore are correct.

Yes: Go to 5.
No: Go to 4.

Run RMV AF to delete the AF configurations, then run ADD AF to add the AF configurations, and check whether this alarm is cleared.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by incorrect AF configurations on the eCore.
No: Go to 5.

Check whether the route to the AF is correctly configured on the eCore.

Run DSP ROUTE to check whether whether the route to the AF is correctly configured on the eCore. Note that the VPN parameter must be configured correctly.

Yes: Go to 7.
No: Go to 6.

Update route configuration. Run RMV SRROUTE and ADD SRROUTE to modify the routing table on the eCore.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by the route failure between the eCore and the AF.
No: Go to 7.

Check whether the operating mode and rate of the eCore's physical interface for interworking with the AF match those configured on the peer switch.

Run LST INTERFACE to check whether the operating mode and rate of the eCore's physical interface for interworking with the AF match those configured on the peer switch.

Yes: Go to 9.
No: Go to 8.

Configure the operating mode and rate for the physical interface on the eCore. Check whether this alarm is cleared.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by the incorrect operating mode or rate of the physical interface.
No: Go to 9.

Check whether the eCore's physical interface for interworking with the AF functions properly.

Run LST INTERFACE to check whether the eCore's physical interface for interworking with the AF functions properly.

If both the physical status and the link protocol status of the physical interface are Up, the physical interface functions properly. If either the physical status or the link protocol status is Down, the physical interface does not function properly.
If the physical status of the physical interface is administratively Down, run MOD INTERFACE to enable the physical interface.

Yes: Go to 12.
No: Go to 10.

Check whether the network cable or optical fiber is faulty.

Reseat the network cable or optical fiber, and ensure that it is connected to the interface properly. Check whether this alarm is cleared.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by the loose connection of the network cable or optical fiber.
No: Go to 11.

Replace the faulty network cable or optical fiber with a sound one. Check whether this alarm is cleared.

Yes: Alarm handling is complete, and no further action is required. The alarm is caused by the network cable or optical fiber fault.
No: Go to 12.

Check whether the transmission path between the eCore and the AF functions properly.

Contact technical support engineers of the AF to capture packets on the AF. Check whether the AF receives the Diameter heartbeat request messages sent by the eCore at a regular interval.

Yes: Go to 13.
No: Go to 18. The alarm is caused by the transmission path fault between the eCore and the AF.

Contact technical support engineers of the AF to capture packets on the AF. Check whether the AF responds to all request messages from the eCore.

Yes: Go to 14.
No: Go to 15.

Check whether the quality of data transmission between the eCore and the AF is good.

On the WebLMT, capture packets on the Rx interface (using Gy interface trace) to check whether the eCore receives response messages to all request messages.

Yes: Go to 18. The alarm is caused by the packet loss due to network congestion between the eCore and the AF.
No: Go to 18. The alarm is caused by the packet loss due to incorrect router or firewall policy settings between the eCore and the AF.

Contact technical support engineers of related devices.

Contact technical support engineers of the AF to check whether the parameters for interworking with the eCore are configured correctly and whether the alarm is caused by wrong interworking parameter settings.

Yes: Go to 17. The alarm is caused by a fault on the AF.
No: Go to 16.

Contact technical support engineers.

Contact technical support engineers of the AF.

Contact technical support engineers of routers, switches, or transmission devices.

Related Information

To query AF configurations on the eCore, run LST AF.

To configure AF information on the eCore, run ADD AF or MODAF.

eCNS integratied and no response from the AF

Best answer

Recommended answer

Description

Attribute

Parameters

Impact on the System

Possible Causes

Procedure

Related Information

Description

Attribute

Parameters

Impact on the System

Possible Causes

Procedure

Related Information

Third Party’s Trade Secret

My Followers

Enterprise

Consumer

Corporate

Carriers

eCNS integratied and no response from the AF

Best answer

Recommended answer

Description

Attribute

Parameters

Impact on the System

Possible Causes

Procedure

Related Information

Description

Attribute

Parameters

Impact on the System

Possible Causes

Procedure

Related Information

Third Party’s Trade Secret

My Followers