Knowledge Search


×
 

Syslog message: KERNEL:.*jsr_prl_recv_ack_msg.* received PRL ACK message

  [KB18195] Show Article Properties


Summary:

The "jsr_prl_recv_ack_msg(): received PRL ACK" message is reported into the system message file to indicate the REs are communicating correctly and this message is harmless. This article documents an approach to understand this message.

Symptoms:

The problem related to this syslog message is described in the following sections:

  • Symptoms
  • Possible Causes
  • Confirm Causes
The "jsr_prl_recv_ack_msg(): received PRL ACK" message is reported into the system message file to indicate the REs are communicating correctly. 

Symptoms:

Messages similar to the following are reported:

Aug 4 01:03:32 router-1 /kernel: %KERN-3: jsr_prl_recv_ack_msg(): received PRL ACK message on non-active socket w/handle 0x100015000000043 -
Aug 4 21:33:48 router-1 /kernel: %KERN-3: jsr_prl_recv_ack_msg(): received PRL ACK message on non-active socket w/handle 0x100017500000028 -
Aug 5 00:47:34 router-1 /kernel: %KERN-3: jsr_prl_recv_ack_msg(): received PRL ACK message on non-active socket w/handle 0x10000fe00000030

Possible Causes:

In the NSR (Non-Stop Routing) enabled environment, incoming TCP segments (for sockets with replication enabled) get replicated to the backup Routing Engine (RE), done at the PRL layer, by the master RE, and once the backup RE acknowledges the segment, it is handed over to the TCP layer. This message is an alert and is indicating that the REs are communicating correctly.

Confirm Causes :

These messages are generated to indicate the RE's are communicating correctly. The show chassis routing-engine command will show the current Routing Engine configuration. Confirm that the RE's are configured properly.
Solution:

The message is just an alert and is harmless; therefore it can be ignored.

Modification History:
2019-08-22: Minor, non-technical edit.
Related Links: