|
| 1 | +.rule_1_1_ensure_device_is_running_current_junos_software |
| 2 | + |
| 3 | +Reference: DATA |
| 4 | +ORIES |
| 5 | +S&cat=SIRT_1&detail=content |
| 6 | + |
| 7 | +Remediation: Software patching procedures may vary between different platforms or organizations and |
| 8 | +can be accomplished using the CLI, the JWeb GUI, centrally through Junos Space or other |
| 9 | +management platforms. |
| 10 | +To update a standalone JUNOS Device through the CLI, first upload the desired software |
| 11 | +image (downloaded from Juniper or your Support Partner) to the JUNOS Device in the |
| 12 | +/var/tmp/ folder. |
| 13 | +In most cases an upgrade is performed with the following command, issued from |
| 14 | +Operational Mode: |
| 15 | +user@host> request system software add /var/tmp/<image name> |
| 16 | +Where <image name> is the filename of the JUNOS image provided by Juniper. |
| 17 | +NOTE - Updating JUNOS Software with this command will result in a reboot of the system |
| 18 | +and loss of service. |
| 19 | +In platforms deployed with redundant Routing Engines, as Virtual Chassis or as HA |
| 20 | +Clusters, an In-Service Software Updates (or ISSU) may be supported. An ISSU update |
| 21 | +updates and reboots each node or RE separately, failing services on to the other node/RE |
| 22 | +prior to the reboot. |
| 23 | +To perform an ISSU Update, on most platforms, issue the following command from |
| 24 | +Operational Mode: |
| 25 | +user@host> request system software in-service-upgrade /var/tmp/<image name> |
| 26 | + |
| 27 | + |
| 28 | + |
| 29 | +NOTE - The specific procedure and prerequisites for ISSU varies by platform and deployment |
| 30 | +type. If some prerequisites (such as NSR or GRES) are not correctly configured a loss of |
| 31 | +service may still occur. |
| 32 | +Please refer to the documentation for your platform and network enviroment before |
| 33 | +attempting to update software. |
| 34 | + |
| 35 | +. |
0 commit comments