BLOG: Information Experience (iX)
Juniper Employee , Juniper Employee Juniper Employee
BLOG: Information Experience (iX)
iX Pro Tip: Using the PR Search Database
Feb 11, 2014

Did you know that you can quickly and easily search for the status of a Problem Report (PR) using the Juniper Networks PR Search database?

 

pr-search-welcome.jpg 

Benefits of Using Search to View the Status of a PR

Descriptions are Up-To-Date: Although the PR summary in the Release Notes provides a snapshot of the PR status as of that particular software release, the PR Search Database provides up-to-date information each time you search.

 

Ability to Receive Notifications: Users can stay informed about a specific PR by subscribing to it. Once they have subscribed, they will receive e-mail updates when that PR has been updated. To receive notifications, click the Subscribe button at the top of the Problem Report window of each PR.

 

Searching for PRs

After logging in with your e-mail address and password, you can search the database using the following criteria:

  • Operating System: Junos, Secure Access, or ScreenOS
  • Base Version: Select a base release number. The results will list both resolved and unresolved issues in the base and later releases.
  • Additional Search Options:
    • Enter the PR number, if known.
    • Enter a keyword (bgp vpn, for example).
    • Upgrade Analysis: select both a base release number and a release number in this field to analyze the differences between releases.
    • Date Modified: Last 7 days, Last 30 days, Last 90 days, or Last 1 year.

When you are ready to run your query, click Search in the upper right corner. The search results will display any PRs that match your search criteria. You can sort the search results by PR number or last modified date using the drop-down at the top right of the results.

 

To view the details of a PR, click the number in the first column.

 

pr-example.jpg 

 

The PR displays the following details for each PR:

  • Number: Unique identifier for each PR. The number is prefixed with PR, for example, PR12345.
  • Title: Brief summary of the problem.
  • Release Note: Short, simple description of the defect from an operational viewpoint. This field is used in the Release Notes documentation that accompanies the software.
  • Severity: Objective classification of the potential impact of a software defect if it were to be encountered. Valid values for this field are:
    • Critical: Conditions that could severely affect service, capacity/traffic, billing, and maintenance capabilities.
    • Major: Conditions that seriously affect system operation, maintenance and administration.
    • Minor: Conditions that would not significantly impair the functioning of the system and or significantly affect service.
  • Status: Indicates if Juniper is still considering work on this PR. Valid values for this field are Open, or Closed.
  • Last Modified: Date that the PR's published content was last modified.
  • Affected-Releases: Release(s) in which the problem was originally introduced if known.
  • Resolved In: Identifies which releases contain the fix for this PR.
  • Operating System: The software base of the Juniper Product.
  • Product: One or more products affected by this PR.
  • Functional Area: Functional area affected by this PR such as hardware or software.
  • Feature Group: High level functional area with which this PR is associated.
  • Configuration: Minimal software configuration items for which the software is susceptible to the problem reported in the PR, if known or applicable.
  • Workaround: Plan or method to temporarily circumvent the problem until a permanent fix can be provided.
  • Problem: Detailed description of the problem.
  • Triggers: High level overview of the circumstances that present susceptibility to the issue.

Finding PRs in the Release Notes

You can also find a description of PRs in the Known Issues section of the Release Notes.

 

prs-in-release-notes.jpg 

One of our goals for future versions of the Release Notes is to use a short and clear problem statement for each PR. If applicable, the description will also include causes, warnings about any potential issues or risks, workarounds, and a list of affected hardware.

 

Need more information about the status of the PR? Simply click the PR number at the end of the description to view the PR in the PR Search Database.

 

For more information about using the PR Search Database, see the Help page

 

Finding PRs in Feature Explorer

For convenience, you can also find a link to the PR Search Database on the right-hand side of Feature Explorer

pr-in-feature-explorer.jpg

 

Want More?

Want to see more tips like these? Subscribe to our Information Experience (iX) blog using the Blog Options menu at the top of our channel!

0 Kudos
Feb 13, 2014
Distinguished Expert

The PR database is much more user friendly than in the past.  This is now a good system for finding if a problem I am experiencing is a reported bug.

 

I also like the linkages created to the release notes in the new format.  This makes determining if bugs are relevant a lot easier in the OS upgrade reviews.

 

Steve Puluka BSEET 
Juniper Ambassador 
Senior Network Engineer - UPMC Pittsburgh, PA
JNCIA-ER JNCIA-EX JNCIS-SEC JNCIP-SEC
JNCIS-FWV JNCIS-SSL 
MCP - Managing Server 2003 MCP - Windows XP Professional
MCTS Windows 7
http://puluka.com/home

Feb 14, 2014
Juniper Employee

Great to hear, Steve!

 

For convenience, you can also find a link to the PR Search Database on the right-hand side of Feature Explorer. I've added a screenshot to the post.

 

Thanks for the feedback!