LIBMSPRPC_CLIENT_NO_REPLY

LIBMSPRPC_CLIENT_NO_REPLY

Remote execution of the command given from the Routing Engine (RE) to the PIC failed. There was no reply from the PIC. This message is generated by the mspinfo process, which is responsible for RPC (Remote Procedure Call) communication between the Routing Engine and the Multiservices PICs. This only applies to M-series and T-series routers, and MX-series routers with an MS-DPC in use.

The LIBMSPRPC_CLIENT_NO_REPLY message is logged each time the mspinfo process does not receive an expected reply from a Multiservices PIC.

When a LIBMSPRPC_CLIENT_NO_REPLY event occurs, a message similar to the following is reported:

The message reports the command that was sent to the Multiservices PIC.

The cause may be due to one or more of the following:

• Incorrect command sent to Multiservices PIC
• Insufficient permissions to send command
• Incorrect arguments sent to PIC
• PIC appears online but is not responding
• The msprpc server is not running on the PIC

Examine the following output to help determine the cause of this message:

Look for any related events that occurred at or just before the LIBMSPRPC_CLIENT_NO_REPLY message.

Perform these steps:

1. If this issue is time critical or if you will need a root cause analysis then open a case with your technical support representative to troubleshoot further. Otherwise the following steps can be used to attempt to resolve the issue.
2. During a maintenance window, as it will impact transit traffic, try the following:

• Reset the Multiservices PIC.
• Reseat the PIC in its slot.
• Move the PIC to another FPC slot, and if possible on a different FPC.
• Replace the PIC with a spare.
• Otherwise reset the FPC the PIC is in.

3. If the failure messages continue, open a case with Juniper technical support.