system service update

Updates the service to a different version with minimal downtime.

Syntax

system service update {{scp:// | sftp:// } username:password@ hostname[:port]/filepath }} | {{ http:// | https:// } username:password@ hostname[:port]/filepath }}

Parameters

scp://: Specifies use of the Session Control Protocol (SCP).
sftp://: Specifies use of Secure File Transfer Protocol (SFTP).
http: Specifies use of HTTP.
https: Specifies use of HTTP secure.
username: Account name of the authorized user.
password: Password of the authorized user.
Note
As a best practice, do not list the password in the command line for security purposes. The user will be prompted for the password.
hostname: Specifies the server by name or by IPv4 address. IPv6 is not supported.; Hostname usage requires that DNS resolution is configured on the device.
port: Specifies the port number, which must be preceded by a colon. If the port is not included, the default port is assumed.
filepath: Specifies the path to the file.

Modes

Exec mode

Usage Guidelines

Services release versions follow a three-part version number format: major version.minor version.patch.

major version.minor version numbers must be identical for service update to be successful, which means that only the patch-version number can be different.
For example, this mean you cannot update version 1.0.0 with 1.1.n but you can update version 1.0.0 with 1.0.1.

Table 1. Error Messages
Error	Reason
`Error: No such host test.example.com`	DNS resolution is not configured on the device or the address is poorly formed.
`Error: Host IP not reachable`	Host is down or IPv4 address entered incorrectly.
`Error: Invalid user credentials`	User does not have permissions or credentials were typed incorrectly.
`Error: File abc.txt is not the correct format for service images`	Valid file format is tar.gz.
`Service update failed. Current Version: 1.0.0, Error: Current version is already running`	The version you are attempting to upgrade to is already installed and running.
`Service update failed. Major/Minor version mismatch. Current version: 1.0.0, New version: 1.1.0`	Version numbers in the first two places of the three-part version format must be the same as the installed version. Only the last number can be different for the update to succeed.

Examples

The following example updates system service via HTTP.

device# system service update http://1.1.1.1:8000/path/pktmgr-ms.tar.gz

The following examples show error messages for system service update.

Invalid URL format:

device# system service update temp.tar.gz                   
temp.tar.gz is not a valid URL format

Image cannot be downloaded:

device# system service update http://engartifacts1.extremenetworks.com:8081/artifactory/tierra-local-snapshots/NGNPB/NGNPB_Feature/MS-Images/chassis.tar.gz 
Failed to retrieve file: engartifacts1.extremenetworks.com:8081/artifactory/tierra-local-snapshots/NGNPB/NGNPB_Feature/MS-Images/chassis.tar.gz err: 404 Not Found

Service version is already running:

device# system service update flash://ms_images/chassis-ms.tar.gz 
Activating Microservice...  
Service update failed. Current version: 0.1.0, Error: Current version is already running