Event Generation Scripts
This section lists the files that are executed at different stages of a JMB generation and collection.
Event Initiation
Table 1 lists the files executed for detecting the occurrence of an event and triggering data collection when an event is detected.
Table 1: Files Executed for Detecting an Event and Triggering Data Collection
Directory Location Under | File Name | Description |
---|---|---|
|
| Passively monitors event notifications from Junos OS; no code is executed until triggered by Junos OS |
|
| For future use to passively monitor event notifications from Junos OS as a Restricted User |
|
| Initiates data collection when core file copying is not required |
|
| Initiates data collection when core file copying is not required |
|
| Initiates data collection when core file copying is required |
|
| Initiates data collection when core file copying is required |
Event Data Collection Management
Table 2 lists the files used for managing data collection when an event is detected on a device.
Table 2: Files that Manage Data Collection
Directory Location Under | File Name | Description |
---|---|---|
|
| Manages all JMB attachment generation |
|
| Parses CLI commands as listed in the events database file provided by Service Now |
Event Data Collection
Table 3 lists the files
used for collecting data when an event is detected on a device. All
files have *.slax
extension.
Table 3: Files that Collect Event Data
Directory Location Under | File Name | Description |
---|---|---|
|
| Generates Table of Contents in a JMB |
|
| Generates device family-specific JMB manifest section |
|
| Generates device family-specific JMB manifest section |
|
| Generates device family-specific JMB manifest section |
|
| Generates device family-specific JMB manifest section |
|
| Generates device family-specific JMB manifest section |
|
| Generates device family-specific JMB manifest section |
|
| Generates device family-specific JMB manifest section |
|
| Generates device family-specific JMB manifest section |
|
| Generates JMB manifest data related to core files on the device. |
|
| Generates device family-specific JMB manifest section |
|
| Generates device family-specific JMB manifest section |
|
| Generates RMA request-specific JMB manifest section |
|
| Collects express RMA data; see above |
|
| Creates intermediate files for use by |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devicies; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific platforms; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
|
| Executes commands for generating Extended Support Information
(ESI) for specific devices; invokes |
Core File Management
Table 4 lists the scripts used for managing core files when an event is detected on a device.
Table 4: Files that Manage Core Files
Directory Location Under | File Name | Description |
---|---|---|
|
| Temporary file generated by |
|
| Executes only on a non-master Routing Engine to transfer JMBs to the master Routing Engine |
|
| Records errors as Junos OS system log messages and in the |
|
| Creates a system log message signalling that the JMB is complete; this system log message triggers Service Now to copy the JMB from the device |
Utility Functions
Table 5 lists the scripts used for performing miscellaneous functions such as checking disk usage while generating the JMB, record time of the event, obtain Junos OS version of the device on which the event occurred, and so on.
Table 5: Files that Perform Utility Functions
Directory Location Under | File Name | Description |
---|---|---|
|
| Checks if RSI should be added to the JMB |
|
| Obtains Junos OS version running on the device for all types of JMBs |
|
| Checks if the device has dual Routing Engines |
|
| On a device with multiple Routing Engines, obtains the host name of the other Routing Engine for all types of JMBs |
|
| Checks utilization of disk space on a device |
|
| Checks the usage of disk space while JMB is generated for all types of JMBs |
|
| Utility for unstructured events |
|
| Reads event parameters for all types of JMBs |
|
| Records time of the event in the JMB |
|
| Creates system logs indicating the progress of creating the attachments, for tracking and troubleshooting purposes |
|
| Introduces pause between commands while generating the ESI attachment for a JMB |
|
| For future use to validate commands from a restricted user |