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 |
---|---|
Fabric design | |
Support IXR D5 spine | Supported hardware and roles now lists IXR
D5 as spine node type. Manual fabric topology parameters also lists IXR D5 as an option. |
Enable VLAN on ISL | Manual fabric topology parameters |
Contextual configuration override |
Contextual configuration overrides Contextual configuration override parameters |
Support for Port Active EVPN Multi-home LAG | Creating LAGs |
Support IXR-D5 Breakout Ports | Elements of a topology file |
Workloads intents | |
Support for enabling multi-hop for BGP PE-CE | |
Multiple router support per workload intent | |
Support for disabling the prepending global AS when neighbor based local AS override is enabled | BGP parameters |
Support for loopback interfaces within a workload router | Subnets |
Operations | |
Support for making neo4j and mongodb passwords configurable post installation | Changing internal passwords |
Support for recovery after node failure |
Recovery after application node failure |
Alarm: network instance down Alarm: LAG member down |
|
Device management | |
Support SR Linux 22.11 | Required parameters for fabric intents identifies SR Linux 22.11.1-3 as a software image option |
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.