About this document

This document describes how to deploy the Fabric Services System software and the required software components such as the Kubernetes cluster and storage volumes.

This document is intended for network technicians, administrators, operators, service providers, and others who need to understand how to configure bare metal servers and provision the Fabric Services System for deployment.

Note: This document covers the current release and may also contain some content that will be released in later maintenance loads. See the Fabric Services System Release Notes for information about features supported in each load.

What's new

This section lists the changes that were made in this release.

Table 1. What's new in Release FSS 22.8.2
Topic Location
Support for software upgrade from Release FSS 22.8.1 to FSS 22.8.2 Software upgrade and rollback

Preparing for software upgrade

Performing a software upgrade

Performing a software rollback

Table 2. What's new
Topic Location
Support for deployment on a single VM without DS for small scale environments

Supported deployment models

Fabric Services System nodes
Support for deployment on VMware vSphere Updated topics in the following sections:
Removed the section Bare metal-based installation: Preparing the Fabric Services System nodes.

Precautionary and information messages

The following are information symbols used in the documentation.

DANGER: Danger warns that the described activity or situation may result in serious personal injury or death. An electric shock hazard could exist. Before you begin work on this equipment, be aware of hazards involving electrical circuitry, be familiar with networking environments, and implement accident prevention procedures.
Warning: Warning indicates that the described activity or situation may, or will, cause equipment damage, serious performance problems, or loss of data.
CAUTION: Caution indicates that the described activity or situation may reduce your component or system performance.
Note: Note provides additional operational information.
Tip: Tip provides suggestions for use or best practices.

Conventions

Commands use the following conventions.

  • Bold type indicates a command that the user must enter.

  • Input and output examples are displayed in Courier text.

  • An open right angle bracket indicates a progression of menu choices or a simple command sequence (often selected from a user interface; for example, start > connect to).

  • Angle brackets (< >) indicate an item that is not used verbatim. For example, for the command show ethernet <name>, name must be replaced with the name of the interface.

  • A vertical bar (|) represents an OR, indicating that only one of the parameters can be selected.

  • Square brackets ([ ]) indicate optional elements.

  • Braces ({ }) indicate a required choice. When braces are contained within square brackets, they indicate a required choice within an optional element.

  • Italic type indicates a variable.

Examples use generic IP addresses. Replace these with the applicable IP addresses used in your system.