Config Router

  • Google Sheets
  • CCNA Online training
    • CCNA
  • CISCO Lab Guides
    • CCNA Security Lab Manual With Solutions
    • CCNP Route Lab Manual with Solutions
    • CCNP Switch Lab Manual with Solutions
  • Juniper
  • Linux
  • DevOps Tutorials
  • Python Array
You are here: Home / Juniper / LIBMSPRPC_CLIENT_NO_REPLY

LIBMSPRPC_CLIENT_NO_REPLY

June 8, 2016 by Marques Brownlee

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:

mspinfo: LIBMSPRPC_CLIENT_NO_REPLY: Error executing "<command>": no reply from the PIC

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:

show log messages

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.

Related

Filed Under: Juniper Tagged With: PIC, Remote Procedure Call, Routing Engine, RPC

Recent Posts

  • How do I give user access to Jenkins?
  • What is docker volume command?
  • What is the date format in Unix?
  • What is the difference between ARG and ENV Docker?
  • What is rsync command Linux?
  • How to Add Music to Snapchat 2021 Android? | How to Search, Add, Share Songs on Snapchat Story?
  • How to Enable Snapchat Notifications for Android & iPhone? | Steps to Turn on Snapchat Bitmoji Notification
  • Easy Methods to Fix Snapchat Camera Not Working Black Screen Issue | Reasons & Troubleshooting Tips to Solve Snapchat Camera Problems
  • Detailed Procedure for How to Update Snapchat on iOS 14 for Free
  • What is Snapchat Spotlight Feature? How to Make a Spotlight on Snapchat?
  • Snapchat Hack Tutorial 2021: Can I hack a Snapchat Account without them knowing?

Copyright © 2025 · News Pro Theme on Genesis Framework · WordPress · Log in