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.
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.
| Description | Location |
|---|---|
| Recovering an application a node failure |
Recovery after application node failure |
| Description | Location |
|---|---|
| Support for including nodes running SR Linux 22.6 within fabrics | |
| Alarm support for BGP neighbor events | Appendix: Supported alarms |
| Alarm support for BDP neighbor events | Appendix: Supported alarms |
| Support breakout port configuration on IXR 7220 D3 and D3L | Configuring a breakout port |
| Support for importing manual topologies, and creating fabrics based on those topologies | |
| Support for global configurartion overrides | |
| Support for MAC duplication detection | |
| Support for PE-CE BGP reference by policy name | Configuring BGP, Steps 8 and 9 |
| Support for untagged and "any" tagged sub-interfaces | Adding sub-interfaces to the workload VPN intent, Step 2 |
| Support for enabling BFD on subinterfaces | |
| Support for management profiles |
Associating a planned node, Step 2 Disassociating planned nodes from real hardware Exporting association data from the overall inventory, Step 4 |
|
Support for gNMI management profiles |
|
| Support for SNMPv3 management profiles | |
| Support primary IP selection on multinetted interfaces | Adding sub-interfaces to the workload VPN intent, Step 2 |
| Enable BGP peering on bridged subnets with anycast IPs | Configuring BGP, Step 9 |
| Disable prepend global AS when neighbor-based local-AS override is enabled | Configuring BGP, Step 9 |
| Support for configurable VNI for VXLAN tunnel | Routers |
| Support for defining specific route targets (RT) for workload intent mac-vrf / ip-vrf | |
| Support for configurable VNI ranges to use for a VXLAN tunnel | |
| Support for defining the EVI pool for a workload intent mac-vrf / ip-vrf | |
| Support for backup and restore of the Digital Sandbox | Restoring Digital Sandbox fabrics |
| Support for backup and restore execution from the deployer VM | |
| Update of SRL software catalogue using ConfigMaps | Updating the software catalog to include new versions |
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
Couriertext. - 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.