JUNOS High Availability

JUNOS Package Overview

Before looking at how or when to upgrade, we need to talk a bit about the naming conventions used to identify a JUNOS software package.

Software Package Naming Conventions

Most commercially available JUNOS software packages follow a naming convention based on the following model:

Package_name-M.NZNumber-Audience-Validation.tgz

In this model:

Package_name

Identifies the type of package and platform family to which the JUNOS software applies. The software has two major categories of packages: jbundle and jinstall. jbundle comprises just the JUNOS components, while jinstall contains the JUNOS components as well as a revised FreeBSD. The jinstall and jbundle packages are provided in platform-specific variations, as shown in Table 6-1.

M.N

Represents the software major release number.

Z

Indicates the type of software release. In most cases, it is an R, to indicate that this is released software. While not appropriate for a high availability network, alpha and beta software is made available to some customers for testing purposes. Such software is tagged with an A (for alpha-level software), B (for beta-level software), or I (for internal, test, or experimental versions of software) in the Z position.

Number

Describes the incremental release of the major revision or the internal build number for non-R releases.

Audience

Identifies the software package as being suitable for a worldwide audience (marked as export) or as being suitable for a domestic audience. This distinction is ...