Cisco In-Service Model Update: Руководство по обновлению данных и инструкции по установке (EN)

Compatibility of In-Service Model Update Packages

In-Service Model Update This module describes how to update the YANG data models on a device through an In-Service Model Update. Restrictions for In-Service Model Update, on page 1 Information About In-Service Model Update, on page 1 How to Manage In-Service Model Update, on page 4 Configuration Examples for In-Service Model Updates, on page 5 Feature Information for In-Service Model Update, on page 9 Restrictions for In-Service Model Update • High availability or In-Service Software Upgrade (ISSU) is not supported. After a switchover, users must install the Software Maintenance Update (SMU) on standby device.

Information About In-Service Model Update Overview of In-Service Model Updates In-Service Model Update adds new data models or extend functionality to existing data models. The In-Service Model Update provides YANG model enhancements outside of a release cycle. The update package is a superset of all existing models; it includes all existing models as well as updated YANG models. The data model infrastructure implements the YANG model-defined management interfaces for Cisco IOS XE devices. The data model infrastructure exposes the NETCONF interface northbound from Cisco IOS XE devices.

The supported data models include industry standard models such as IETF, and Cisco IOS XE device-specific models. The functionality provided by the In-Service Model Update is integrated into the subsequent Cisco IOS XE software maintenance release. Data model update packages can be downloaded from the Cisco Download Software Center . Compatibility of In-Service Model Update Packages An update package is built on a per release basis and is specific to a platform. This means that an update package for Cisco ASR 1000 Series Aggregation Services Routers cannot be installed on Cisco CSR 1000V In-Service Model Update 1

Стр. 1

Installing the Update Package

Series Cloud Services Routers. Similarly, an update package built for Cisco IOS XE Fuji 16.7.1 cannot be applied on a device that runs the Cisco IOS XE Everest 16.5.2 version. All contents of an update package will be part of future mainline or maintenance release images. The image and platform versions are checked by the In-Service Model Update commands during the package add and activate. If an image or platform mismatch occurs, the package install fails. Update Package Naming Conventions In-Service Model Updates are packaged as a .bin files. This file includes all updates for a specific release and platform and the Readme file.

These files have a release date and are updated periodically with additional model updates. The naming convention of the data model update package follows the format—platform type-license level.release version.DDTS ID-file. The following is an example of a data model update file: • isr4300-universalk9.16.05.01.CSCxxxxxxx.dmp.bin • asr1000-universalk9.2017-08-23_17.48.0.CSCxxxxxxx.SSA.dmp.bin The readme file provides the following information:

• Console and error messages during data model activation or deactivation • Data model installation impact • Side effects and possible workarounds • Package(s) that the In-Service Model Update impacts • Restart type Installing the Update Package You can install the In-Service Model Update package on a device by using the install add , install activate , and install commit commands in privileged EXEC mode. The install add command copies the update package from a remote location to the device. You can also use other methods to copy the package; however, you must still enable the install add command for the installation to work.

For the install activate command to work, the package must be available in the device bootflash. Enable the install commit command to make updates persistent over reloads. Installing an update replaces any previously installed data models. At any time, only one update is installed on the device. A data model package includes all updated YANG models and all existing YANG models previously installed on the device. The following flow chart explains how the model update package works: In-Service Model Update Update Package Naming Conventions In-Service Model Update 2

Стр. 2

Rollback of the Update Package

Figure 1: Committing a Model Update Package If NETCONG-YANG is enabled during package activation, NETCONF processes are restarted. All active NETCONF sessions are killed during package activation. Failure during a package verification terminates the activation process. Deactivating the Update Package You can deactivate an update package by using the install deactivate command. Enable the install commit command to make changes persistent. Table 1: Deactivating a Model Update Package When you deactivate an update, if more than one model update package is installed, the most recently committed model update package becomes the model package used by the device.

If there are no other previously committed model packages, then the base version of data models included with the standard image is used. Rollback of the Update Package Rollback provides a mechanism to move a device back to the state in which it was operating prior to an update. After a rollback, NETCONF-YANG processes are restarted before changes are visible. You can roll back an update to the base version, the last committed version, or a known commit ID by using the install rollback command. In-Service Model Update Deactivating the Update Package Action Command to Use To remove a package. Use the install remove command. Note Deactivate a package before removing it.

To deactivate a package Use the install deactivate command, followed by the install commit command. Note The install commit command must be used to ensure that the deactivation of the model package is persistent across reloads. Subsequent attempts at removal of the package will fail, if the deactivation is not committed. In-Service Model Update 3

Стр. 3

Managing the Update Package

How to Manage In-Service Model Update Managing the Update Package SUMMARY STEPS 1. enable 2. install add file tftp: filename 3. install activate file bootflash: filename 4. install commit 5. install deactivate file bootflash: filename 6. install commit 7. install rollback to { base | committed | id commit-ID } 8. install remove { file bootflash: filename | inactive } 9. show install summary DETAILED STEPS Procedure In-Service Model Update How to Manage In-Service Model Update Command or Action Purpose Step 1 enable Example: Device> enable Enables privileged EXEC mode. • Enter your password if prompted. Step 2 install add file tftp: filename Example:

Device# install add file tftp://172.16.0.1//tftpboot/folder1/ isr4300-universalk9.16.05.01.CSCxxxxxxx.dmp.bin Device# install add file tftp://172.16.0.1//tftpboot/folder1/ asr1000-universalk9.2017-08-2317.48.0.CSCxxxxxxx.SSA.dmp.bin _ Copies the model update package from a remote location (via FTP, TFTP) to the device, and performs a compatibility check for the platform and image versions. • You can use other methods to copy the update package from the remote location to the device, however; you still have to execute the install add command before the package is activated. Step 3 install activate file bootflash: filename Example: Device# install activate file bootflash:

isr4300-universalk9.16.05.01.CSCxxxxxxx.dmp.bin Device# install activate file bootflash: asr1000-universalk9.2017-08-2317.48.0.CSCxxxxxxx.SSA.dmp.bin _ Validates whether the update package is added through the install add command, and restarts the NETCONF processes. • Perform the install add operation prior to activating an update package. Step 4 install commit Example: Device# install commit Makes the changes persistent over reload. • NETCONF processes are not restarted. In-Service Model Update 4

Стр. 4