JUNOScope System Log Messages
JUNOScope events are stored in the JUNOScope database and are subsequently sent to the system log server and an optional RADIUS accounting server if one is configured (see Figure 13).
The JUNOScope software generates events or system log messages based on the status of the following operations, and forwards them to the local system log server.
- User login success
- User login failure attempt
- User account automatically locked
- User account locked and unlocked by the JUNOScope administrator using Users > Authentication Policy
- A new user account added, existing user account deleted, or existing user account password changed using Users > Local Authentication
- A new device is deleted or existing device is edited or deleted using Settings > Devices
- A label association is changed using Settings > Labels
- A configuration is committed to a device using Configuration > Current > Edit
- Completed Archive operations—When an archive of a device is performed the first time or some change in configuration is done after the last successful archive of that device.
- Completed Inventory Scan operations—When an inventory scan is performed the first time or after a change in the inventory after the last successful scan.
- Completed Restore operations—When a configuration is successfully restored on a device.
- The success or failure of a JUNOScope operation—This information is reflected in the system log message severity level.
- The final status of each leaf operation shown on the Monitor Status Page. For example, for an operation named
archive edge routers, which consists of a group of edge routersedge1,edge2, andedge3, the success (or failure) status ofarchive edge1,archive edge2, andarchive edge3will be forwarded to the system log. - All information recorded in the JUNOScope View Status page (Monitor > Status).
Each system log message identifies the JUNOScope software process that generated the message and briefly describes the operation or error that occurred.
