About this document

This Fabric Services System User Guide describes the system's user interface (UI), and includes procedures that guide you through the design and deployment of a fabric intent.

This document is intended for network technicians, administrators, operators, service providers, and others who use the Fabric Services System.

Note:

This manual 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 24.5.1
Description	Location
System administration
Support for geo-redundancy	Geo-redundancy Sync failure and recovery Geo-redundancy operations REST API geo-redundancy operations Geo-redundancy parameters Realigning certificates Configuring geo-redundancy Initiating failover: switching between the active and standby clusters Making the standby system active - standalone operation Converting a geo-redundant system to a standalone system Geo-redundancy status and statistics Predefined resource groups, added the RG-sync group Predefined roles, added the geored user Restore a backup and install the Fabric Services System application
Added a note about Keycloak handling of user passwords	Users
Fabric intents
IXR-D4 is supported as a leaf and spine node. IXR-D5 is supported as a leaf, spine, and border-leaf node.	Supported hardware
Workload intents
Support for static MAC address on subnet gateway (IRB)	Workload VPN intent parameter descriptions
Support for configurable BFD timers	Workload VPN intent parameter descriptions
Security
Updated the procedure to include connect and geored users	Resetting internal passwords
Updated the validity of northbound server certificates from 90 to 365 days	Certificate management
Alarms
New alarms are supported in this release	Appendix A: Supported alarms

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 simple command sequence (often selected from a user interface). Example: start > connect to
Angle brackets (< >) indicate an item that is not used verbatim. For example, for the command show ethernet <name>, name should be replaced with the name of the interface.
A vertical bar (|) indicates a mutually exclusive argument.
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 appropriate IP addresses used in your system.