Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Contents of a JMB

 

A Juniper Message Bundle (JMB) is data in a structured format generated by AI-Scripts to provide information for troubleshooting an event that occurred on a device or to provide the trend data of the device. A JMB contains all or some of the following sections:

Manifest

This section of a JMB contains information about the event for which the JMB is generated, the Routing Engine and router on which the event occurred, the core files collected from the router, and the current values of parameters that are configured in AI-Scripts. The information in the Manifest section is used primarily for creating a case in JSS for the event.

Figure 1 is a snapshot of the Manifest section of a JMB.

Figure 1: Manifest Section of a JMB
Manifest Section of a JMB

Table 1 describes the elements in the Manifest section.

Table 1: Elements in the Manifest Section of a JMB

Element

Description

Event Information

Host Event-ID

Specifies the ID of the event in response to which the JMB is generated

Host Event-ID is represented in the following format:

<router-name>-<chassis-serial-number> -<YYYYMMDD-HHMMSS>-<sequence number>, where:

  • router-name specifies the hostname of the router.

  • chassis-serial-number specifies the serial number of the router chassis.

  • YYYYMMDD-HHMMSS specifies the date and time the event occurred on the device.

  • sequence number varies from 001 through 999 and indicates the sequence of events when multiple events occur at the same time.

    The sequence number is present only if multiple events occur at the same instance on the device.

Problem Class

Specifies the problem class; the value is always set to Support.

This field is used to populate the Problem Class field in the Customer Relationship Management System (CRM) of Juniper Support System (JSS).

This field is not applicable for an iJMB.

Service Type

Specifies whether a JMB is generated as a proactive measure or a reactive measure.

Possible values are:

  • Event: The JMB is generated in response to an event that occurred on the device. (This is a reactive measure.)

  • Intelligence: The JMB is generated and collected periodically to monitor the vital functions of the device. (This is a proactive measure.)

  • On-demand: The JMB is generated in response to a request from a user.

  • Event-RMA: The JMB Is generated in response to an Return Material Authorization (RMA) event on the device. This is a reactive measure.

  • Health-check: The JMB is generated and collected periodically to check the integrity of the BIOS or for any errors related to the AI-Scripts installed on the device. This is a proactive measure.

Time Occurred

Specifies the time at which the event occurred

Event Type Group

Classifies the events that occurred on the device under the following categories:

  • Hardware failure

  • Software failure

  • Resource exhaustion

This field is not applicable for an iJMB.

Event Type

Specifies the type of event that occurred on the device; for example, MAC error or Process error

This field is not applicable for an iJMB.

Problem Synopsis

Specifies a summary of the event; this field is used to populate the Problem Synopsis field in the CRM.

This field can be appended with your text while submitting the incident for resolution to JSS or a Service Now partner.

This field is not applicable for an iJMB.

Problem Description

Describes the event; this field is used to populate the Problem Description field in the CRM.

This field can be appended with your text while submitting the incident for resolution.

This field is not applicable for an iJMB.

Problem Severity

Specifies JTAC’s assessment of the impact that the event has on the customer’s network

Possible values are:

  • 1 - Critical

  • 2 - High

  • 3 - Medium

  • 4 - Low

This field is not applicable for an iJMB.

Problem Priority

Specifies the customer’s perception of the impact that the event has on the network; this field is used to populate the Problem Priority field in the CRM system.

Possible values are:

  • 1 - Critical

  • 2 - High

  • 3 - Medium

  • 4 - Low

This field is not applicable for an iJMB.

KBURL

Specifies the link to the knowledge base (KB) article related to the event

This field is not applicable for an iJMB.

AI Script Version

Specifies the version of the AI-Scripts that generated the JMB

Associated Core File

Specifies the core files included in the JMB

This field is not applicable for an iJMB.

Router Information

Product Name

Specifies the name of the product; this field is used to populate the Platform field in CRM.

Host Name

Specifies the hostname assigned to the device

OS Platform

Specifies the routing OS installed on the device

Routing Engine

Name

Specifies the name of the Routing Engine

Mastership State

Specifies whether the Routing Engine serves as the primary or the backup Routing Engine of the device

Component

Specifies the components of Junos OS such as rpd and chassisid

Version

Version of Junos OS component executing on the Routing Engine

Builder

User who created the Junos OS build

Build Date

Date and time the Junos OS build was created

Service Now Information

RSI Collection

Specifies the configuration for collecting Request Support Information (RSI) from the device—whether RSI collection is enabled or disabled and the interval for collecting RSI

BIOS Validation

Specifies whether BIOS validation is enabled or disabled on the device

Log Collection

Specifies whether log collection is enabled or disabled on the device

True indicates that log collection is enabled and False indicates that log collection is disabled.

Space Platform Version

Specifies the version of Junos Space Network Management Platform managing the device

Service Insight

Specifies the version of Service Insight installed with Service Now

Service Now

Specifies the version of Service Now managing the device

AI-Scripts Information

RSI Collection

Specifies the configuration for collecting Request Support Information (RSI) from the device—whether RSI collection is enabled or disabled and the interval for collecting RSI

Log Collection Enabled

Specifies whether log collection is enabled or disabled on the device

True indicates that log collection is enabled and False indicates that log collection is disabled.

BIOS Validation

Specifies whether BIOS validation is enabled or disabled on the device

PHD Collection

Specifies whether collection of product health data (PHD) is enabled or disabled on the device. It also states the location of the XML file used by AI-Scripts to determine the CLI commands that are to be run and the time interval during which each command is run.

PHD Collection Commands File

Specifies the file that contains the commands to collect PHD on the device

JMB Cleanup Interval

Specifies the interval in seconds after which JMBs generated due to PHD collection are deleted

Trend Data

This section of a JMB contains information about hardware and software operating parameters such as CPU and memory utilization of the Routing Engine and traffic statistics of the device. This section is present only in iJMBs.

Trend data is provided for the following components of a device:

  • Routing Engine

  • Line-card chassis (LCC)

  • Switch-card chassis (SCC)

  • Flexible PIC Concentrator (FPC)

  • Packet Forwarding Engine

  • Switch Control Board (SCB)

  • Routing protocol process (rpd)

  • Kernel

Figure 4 shows the Trend Data section of a JMB.

Figure 2: Trend Data Section of a JMB
Trend Data Section of a JMB

Attachments

Only files that are relevant to the type of event that triggered the JMB are present in this section. This section provides pointers to the files that contain the output of specific Junos OS commands executed to retrieve specific data pertaining to the event. Some Junos OS commands executed are standard—that is, they are executed for every platform, whereas some are executed for a specific platform.

The following standard Junos OS commands are executed to compile data in this section of the JMB:

  • show system processes extensive

  • show pfe statistics error

  • show system boot-messages

  • show system virtual-memory

  • show system buffer

  • show system queues

  • show system statistics

  • show task io

  • show configuration

  • show chassis hardware

    Note

    This command is applicable only on the master Routing Engine.

  • request support information

    Note

    This command is dependent on the AI-Scripts parameters governing the collection of the RSI output.

  • show system commit

  • show system uptime

  • file list /var/log/ detail

Figure 3 is a snapshot of the Attachments section of a JMB.

Figure 3: Attachments Section of a JMB
Attachments Section of a JMB

The attachment files are named host-event-id_attachmentname, where host-event-id specifies the hostname, the event-id specifies the date and time the event occurred, and attachmentname specifies the type of attachment (for example, cfg, rsi, ver).

The type of JMB determines what attachment files are included in the JMB. For example, an iJMB does not contain the RSI attachment file.

A JMB generally contains the following files as attachments:

  • *_AISESI.txt—Contains event support information; output of multiple Junos OS show commands

    Note

    This command is dependent on the AI-Scripts parameters governing the collection of the RSI output.

  • *_rsi.txt—Contains RSI of the device

    Note

    If this attachment is dampened, the file contains a string that explains the reason.

  • *_cfg_xml.xml—Contains device configuration information in XML format

  • *_shd_xml.xml—Contains output of the show chassis hardware command in XML format

  • *_ver_xml.xml—Contains the hostname and version information about the software (including the software help files and AI-Scripts bundle) running on the device

  • *_ais_attach_statusmsgs.txt—Displays the status of each JMB attachment generation

You can view or download the attachments using the View or Download link. The attachments are downloaded in the *.gz format.

Logs

This section of a JMB contains a compressed view of the /var/log directory of the device. The log files are retrieved from the device and stored in the Service Now database.

The log files are collected as an attachment if the /var directory of the device has more than 20% free space; otherwise, the log files are listed individually and the links to view and download the log files are listed in the JMB.

Figure 4 shows the Logs section of a JMB.

Figure 4: Logs Section of a JMB
Logs Section of a JMB