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, workload intents, maintenance intents, and their supporting components.
This document is intended for network technicians, administrators, operators, service providers, and others who use the Fabric Services System.
What's new
This section lists the changes that were made in this release.
Feature | Location |
---|---|
Fabric intents | |
A static management IP address is now mandatory for nodes within a managed fabric. | Fabric intents |
Contextual Configuration Overrides | |
Label-based CCO association |
Contextual configuration override parameters Now defines various parameters associated with specifying a label to indicate CCO targets. Creating a contextual configuration override CCO creation procedure now includes a branch for label vs. node selection, and describes label selection to identify CCO targets. |
CCO auto-deploy |
Contextual configuration override parameters "Auto-deploy" parameter now active, and defined here. Creating a contextual configuration override CCO creation procedure now mentions that the auto-deploy parameter is working for CCOs. |
Display CCOs per node | Adds a mechanism to see the set of CCOs affecting any single node, as well as the cumulative effect of all active CCOs on the configuration. |
Workload intents | |
Changes to behavior after workload intent deletion failure | Deleting a workload VPN intent |
Security | |
Updates related to Kafka and ZooKeeper services | Updated the topic Recovering an application after node failure and removes the topic Recovering an application after node reboot |
Updated the example to show use of the --no-prechcek
option |
Deploying a user-provided CA certificate |
Alarms | |
Adds new alarms for failed image download, health monitoring, and certificate expiry | Appendix A: Supported alarms |
Precautionary and information messages
The following are information symbols used in the documentation.
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.