berrybta.blogg.se

In the end, only the final respin will be officially released.

Every time when a new build of the same release is compiled, the new build will get its respin number increased by one. The reason why the respin number is there is that during quality assurance testing before releasing the image, some issues may be found and addressed before release. However, for official releases the respin number can be disregarded. You will see this number in the Junos image file name and in the CLI command output for 'show version'. For example Junos release 12.1X44-D10 can also be written as 12.1X44-D10.4, where the.

If needed, some of these in-between numbers can also be allocated to customer special releases.Īll Junos releases have a respin number at the end of the image name. Service releases get the numbers allocated between the maintenance release numbers. Generally, service releases(*) are planned in between the maintenance releases. So the maintenance release number counts up with steps of 10 at a time. The third maintenance release is D30 and so on. From 15.1X49 release onward, the second maintenance release will be D20. So the maintenance release number counts up with steps of 5 at a time. The third maintenance release is D20 and so on. From 12.1X44 release till the 12.3X48 release, the second maintenance release will be D15. The first release shipping (FRS) in X-releases is the D10 release. Unlike with "R" numbers in common Junos, the "D" numbers do not start at 1 and count up from there. This is comparable with R1 in common Junos.Īs mentioned above, the X-releases use the "Dxx" suffix instead of "Rxx" to indicate the maintenance release(*) number. This is comparable with for example 11.4 in common Junos.ĭ10 - this suffix designates the specific release number. | | | D10 - the maintenance release numberġ2.1 - the Junos version that this X-release is based uponġ2.1X44 - the base Junos version and X-release number together designates the major release (version) number. This release name consists of the following components. Let's take release 12.1X44-D10 as an example. Note that from Junos version 17.3 onwards, SRX platforms returned to using the regular Junos releases again, which are also used by other Juniper Networks platforms. Since the beginning of 2013 new Junos releases for SRX have adopted a naming convention using the letter 'X'. Like other Juniper Networks platforms, SRX security gateways are running Junos software.