An MX BRAS device continuously reports a syslog message caused by an invalid license.
An MX BRAS device continuously reports the following syslog message: Nov 9 11:10:11 2016 MX960-1-re0 rshd[19888]: root@re1 as root: cmd='rcp -T -f /config/usage.db' Nov 9 11:10:21 2016 MX960-1-re0 rshd[19892]: root@re1 as root: cmd='rcp -T -f /config/usage.db' There was no impact to service. After disabling GRES/NSR, the syslog messages stopped being reported.
Nov 9 11:10:11 2016 MX960-1-re0 rshd[19888]: root@re1 as root: cmd='rcp -T -f /config/usage.db' Nov 9 11:10:21 2016 MX960-1-re0 rshd[19892]: root@re1 as root: cmd='rcp -T -f /config/usage.db'
The usage.db file is used to store the license usage information. It is stored under /config. This syslog message may be caused by license synchronizing failure. Checking the system license status, it was discovered that one license became invalid.
usage.db
user@MX960-1-re0> show system license License usage: Licenses Licenses Licenses Expiry Feature name used installed needed ... scale-subscriber 13554 32000 0 invalid ... {BACKUP.EN_US} user@MX960-1-re1> show system license License usage: Licenses Licenses Licenses Expiry Feature name used installed needed ... scale-subscriber 13561 32000 0 invalid ...
To find the reason for why a license becomes invalid and how to reinstall a license, refer to KB26839 - [Subscriber Management] scale-subscriber license starts showing expiry when subscribers are reaching license limit [juniper.net]