Device Details for Installed Base

Overview Information

For general device information and contract information, click the Overview tab.

This page displays the following information:

• General

  • Model—The device model. Example: EX2300-24P.

  • Installed Address—Device location address, as maintained by Juniper support services.

  • Product Number—The part number (stock keeping unit) associated with the device.

  • Recommended Release—The recommended Junos OS software version for the device.

  • Last updated—The date on which the recommended Junos OS software was last updated.

  • Recommender Link—Link to a Juniper Support Portal (JSP) Knowledge Base (KB) article with a list of recommended Junos OS version for each Juniper platform.

• Contracts

  • Contract SKU—The stock keeping unit (SKU) assigned to the active support coverage associated with the device.

  • Contract Type—The type of active support coverage provided for the device. Example: Maintenance.

  • Start Date—The date on which the support contract begins.

  • Reseller— Name of the reseller through which your company acquired the device.

• Hardware End of Life Dates

  • End of Life—The date on which the device reaches EOL.

  • End of Support—The date on which the device reaches EOS.

SIRT (Security Incidence Response Team Tickets)

To view Security Incidence Response Team Tickets, click the SIRT tab.

You can view this information:

• JSA ID—The Unique value that identifies the security advisory on Juniper Networks Support Portal.

• Title—A synopsis of the security advisory.

• Severity—Severity rating of the security advisory. The values are critical, high, medium, and low.

• Affected Models—The device models affected by the security advisory.

• OS Versions Affected—The Junos or Junos Evo software versions affected by the security advisory.

• Release Date—The date on which the security advisory was first published.

• JSA Updated Date—The date on which the security advisory was last updated.

• Problem—A description of the security advisory.

• Solution—The solution for the security vulnerability described in the advisory.

• Workaround—Detailed instructions on how to temporarily circumvent the problem.

• Affected Series—Identifies one or more product series affected by the security advisory.

• Release Notes—Short description of the security advisory.

You can perform these actions:

• Filter the tickets by security vulnerability using the filter button on the quick summary (For example, High Vulnerabilities) on the page banner.

• Open a Quick View panel to view more information about the SIRT ticket. Click on any of the SIRT tickets to view the Quick View panel for the SIRT ticket.

  

PBN (Proactive Bug Notification)

To view proactive bug notifications, click the PBN tab.

You can view this information:

• ID—The unique value that identifies the bug.

• Headline—The synopsis of the problem.

• Bug Type—Indicates the phase or activity during which the problem was discovered. For example, Day-1.

• Trigger—Describes the events that happened before or at the time the problem occurred, or the event that caused the problem.

• Introduced In—The Junos or Junos Evo software release where the problem was first found and reported.

• Fixed In—The Junos or Junos Evo software release in which the problem was resolved.

• Release Notes—A short description of the problem.

• Restoration—Indicates how the service can be restored when the problem occurs. Values include:

  • Self-recovery—Service, traffic, or operation disruptions are automatically restored without any user intervention.

  • Not-possible—It is not possible to restore the service or traffic.

  • Manual—User intervention is required to restore the service, traffic, or operation disruption.

• Restoration Steps—Steps to restore the service when the problem occurs.

• Workaround—Detailed explanation of how to temporarily circumvent the problem until a permanent resolution is available.

• Workaround Provided—Indicates whether a workaround for the problem is provided or not. Values include:

  • Yes—Workaround is available and is described in the Workaround field.

  • Not-possible—There are no workarounds to the problem.

• Product Family—Identifies one or more products affected by the problem.

You can perform these actions:

• Filter the tickets by risk level using the filter button on the quick summary (For example, Major Customer Risk) on the page banner.

• Open a Quick View panel to view more information about the PBN ticket. Click on any of the PBN tickets to view the Quick View panel for the PBN ticket.