This chapter describes messages with the LIBMSPRPC prefix. They are generated by the mspinfo process, which is responsible for RPC communication between the Routing Engine (RE) and the Multiservcies Physical Interface Cards (PICs).
Can't create msprpc client: error-message
A JUNOS process (mspinfo) could not establish initialization of the RPC client.
Error: An error occurred
error
Possible reasons: process is out of memory
Contact your technical support representative.
Can't initialize kcom for msprpc client: error-message
A JUNOS process (mspinfo) could not establish initialization of the kcom subsystem.
Error: An error occurred
error
Possible reasons: can't initialize kcom services.
Contact your technical support representative.
Failed connecting fpc=fpc-slot, pic=pic-slot
Remote execution of the command given from the RE to the PIC failed, can not connect to the PIC.
Error: An error occurred
notice
Possible reasons: a)PIC appears online but is not responding b)msprpc server is not running on the PIC.
Contact your technical support representative.
Error executing "command": no reply from the PIC
Remote execution of the command given from the RE to the PIC failed, no reply from the PIC.
Error: An error occurred
notice
Possible reasons: a)wrong command b)insufficient permissions c)wrong arguments d)PIC appears online but is not responding e)msprpc server is not running on the PIC.
Contact your technical support representative.
Interface interface-name is down
Remote execution of the command given from the RE to the PIC failed, the PIC is down.
Error: An error occurred
error
Possible reasons: the given PIC is not responding and/or is offline.
Contact your technical support representative.
Error executing "command": output length exceeds correct-length characters
Remote execution of the command given from the RE to the PIC failed, PIC returned unexpected output.
Error: An error occurred
notice
Possible reasons: a)wrong command b)wrong arguments.
Contact your technical support representative.