Route Index = 0 Application Name = S6a Default Route Flag = NO Mode = SELMODE_MASTER_SLAVE Peer Entity Realm Name = tdhss.com Peer Entity Index = 0 Route Name = RX
the tdhss.com is set up on eUDC ... what could be the problem?
This alarm is generated when the mobility management entity (MME) cannot send messages to all the Diameter peers in the destination realm if the route to the next-hop Diameter peer in the destination realm is unavailable. This alarm is cleared when the route to the next-hop Diameter peer in the destination realm is available.
Attribute
Alarm ID
Alarm Severity
Auto Clear
80592
Major
Yes
Parameters
Name
Meaning
Route index
Indicates the index of the Diameter route.
Route name
Indicates the name of the Diameter route.
Destination entity realm name
Indicates the name of the destination entity realm.
RU Name
Indicates the name of the virtual machine for which the alarm is generated
Process Type
Indicates the type of the process for which the alarm is generated. The process can be:
SPP
Process No.
Identifies the process for which the alarm is generated.
Fault Cause
Indicates the cause value of the fault.
The cause value can be:
USER_DISCONNECT
REL_FROM_NET
DWR_NO_ANSWER
REC_STATUS_INDICATION
CM_SMOOTH
REC_DPR
REC_STATUS_ANSWER
REC_DEVICE_MES
PARSE_ERR
RECV_MAX_DATA
DELETE_CONN
MODIFY_CONNGRP
MODIFY_ROUTE
DELETE_ROUTE
USER_RESTART
DWR_SEND_FAILURE
RM_SMOOTH
CONN_REBOOTING
RECV_DWR_FORM_UNKNOWNPE
FAL_IN_OPEN_ST
RECV_NON_CEA
PRO_CEA_FAILED
SES_STATE_CHG
CREATE_TRANS_CONN_FAIL
CREATE_CONN_TIMEOUT
CONN_ESTABLISH_FAILURE_NACK
RECV_CEA_TEMPORARY_FAILURE
WAIT_I_CEA_TIMEOUT
SEND_CER_FAILED
RECV_PEER_DISC_IN_WAIT_I_CEA_STATE
TLS_DEL_CONN_FAILURE
TLS_CLOSING_STATE_TIME_OUT
SUSPECT_RCV_MSG
REOPEN_RCV_DWA_MSG
OPEN_TO_SUSPECT
RCV_TOO_BUSY_RSP
CONFIG_UPDATE
CAUSE_BUTT
Impact on the System
The MME cannot send messages to the peer entity and services related to the peer entity are interrupted.
Possible Causes
The Diameter link is abnormal.
The peer entity in the destination realm is faulty.
The Diameter route is Down.
Procedure
In the MML Command - OMO_VNFC window, run DSP DMPE to check the status of the next-hop Diameter peer in the destination realm.
This alarm is generated when the mobility management entity (MME) cannot send messages to all the Diameter peers in the destination realm if the route to the next-hop Diameter peer in the destination realm is unavailable. This alarm is cleared when the route to the next-hop Diameter peer in the destination realm is available.
Attribute
Alarm ID
Alarm Severity
Auto Clear
80592
Major
Yes
Parameters
Name
Meaning
Route index
Indicates the index of the Diameter route.
Route name
Indicates the name of the Diameter route.
Destination entity realm name
Indicates the name of the destination entity realm.
RU Name
Indicates the name of the virtual machine for which the alarm is generated
Process Type
Indicates the type of the process for which the alarm is generated. The process can be:
SPP
Process No.
Identifies the process for which the alarm is generated.
Fault Cause
Indicates the cause value of the fault.
The cause value can be:
USER_DISCONNECT
REL_FROM_NET
DWR_NO_ANSWER
REC_STATUS_INDICATION
CM_SMOOTH
REC_DPR
REC_STATUS_ANSWER
REC_DEVICE_MES
PARSE_ERR
RECV_MAX_DATA
DELETE_CONN
MODIFY_CONNGRP
MODIFY_ROUTE
DELETE_ROUTE
USER_RESTART
DWR_SEND_FAILURE
RM_SMOOTH
CONN_REBOOTING
RECV_DWR_FORM_UNKNOWNPE
FAL_IN_OPEN_ST
RECV_NON_CEA
PRO_CEA_FAILED
SES_STATE_CHG
CREATE_TRANS_CONN_FAIL
CREATE_CONN_TIMEOUT
CONN_ESTABLISH_FAILURE_NACK
RECV_CEA_TEMPORARY_FAILURE
WAIT_I_CEA_TIMEOUT
SEND_CER_FAILED
RECV_PEER_DISC_IN_WAIT_I_CEA_STATE
TLS_DEL_CONN_FAILURE
TLS_CLOSING_STATE_TIME_OUT
SUSPECT_RCV_MSG
REOPEN_RCV_DWA_MSG
OPEN_TO_SUSPECT
RCV_TOO_BUSY_RSP
CONFIG_UPDATE
CAUSE_BUTT
Impact on the System
The MME cannot send messages to the peer entity and services related to the peer entity are interrupted.
Possible Causes
The Diameter link is abnormal.
The peer entity in the destination realm is faulty.
The Diameter route is Down.
Procedure
In the MML Command - OMO_VNFC window, run DSP DMPE to check the status of the next-hop Diameter peer in the destination realm.
Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
Politically sensitive content
Content concerning pornography, gambling, and drug abuse
Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."