Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width400px

Introduction

This guide describes what steps have to be taken when a customer wants to install Site Controller Version 1.3 on a running system, which is already connected to the azeti Engine. There is no automatic upgrade for version 1.2 to 1.3. Instead the customer has to do a fresh installation and migrate the existing configuration, as there have been structural changes in 1.3 that avoid an automatic approach. This guide explains the steps necessary and gives some guidelines on things to keep in mind. 

 

Info

This update guide is intended for standard linux OS like Ubuntu. Other platforms, like Cisco IOX and GOS,  require different steps to do the upgrade.

Column
width400px
Panel
borderColorlightgrey
bgColor#f0f0f0
titleOn this page:

Table of Contents

Related pages:

  • Content by Label
    showLabelsfalse
    showSpacefalse
    sortcreation
    cqllabel = "getting-started" and space = currentSpace()

...

Info

Please note, that this guide assumes you have already used the azeti Control Panel in combination with Site Controller. If you are absolutely new to these topics, please refer to this guide instead: Get StartedQuick Start to the Engine

Prerequisites

  1. The customer needs access to the corresponding azeti Control Panel and admin-rights for her / his account
  2. The customers needs ssh-access for the system, which is to be updated.
    1. It is also possible to transfer data (e.g. the installer) via other methods, depending on the system, but this guide will focus on SSH-based access
  3. Installer-Tar.gz for SiteController-1.3 (can be requested in the online Service Desk)
  4. The customer needs to know, where the current version of Site Controller is installed. By default this should be /opt/azeti/SiteController/, but some systems might differ.

...