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 |
|---|---|
| Region management | |
| DHCP settings are now visible from the Regions map. | Viewing DHCP settings |
| Fabric design | |
| Manual topology import | Manual fabric topologies |
| Support for configuring LACP fallback properties for LAGs | Creating LAGs |
| Support for edge links on spine nodes in manual topologies | Elements of a topology file |
| Support for Forward Error Correction (FEC) as a configurable parameter in manual topologies | Elements of a topology file |
| New topology validations for manual topologies | Elements of a topology file |
| Supported hardware includes 7220 IXR H2, 7220 IXR H3 | Supported hardware |
| Workload intents | |
|
Support for the deployment of an empty workload intent |
Workload VPN intent creation |
|
Allowing ACL to be applied on ingress and egress |
|
| Support for creating single ACL for multiple sub-interfaces vs one per sub-interface | |
| Support for QoS node configuration management independent of the workload intent | |
|
Allowing QOS policies to be applied in either ingress or egress |
|
| Layer-3 Proxy ARP | Subnets Adding subnets to the workload VPN intent Sub-interface parameters |
| Layer-3 Proxy ND | |
| Layer-2 Dynamic Proxy ARP | Subnets |
|
Support for auto-deployment of workload intents |
|
| Maintenance intents | |
|
Support for a configurable timer to run before rebooting the device undergoing an upgrade Support for configurable timer to run after the device comes back online from a node |
Creating a maintenance intent |
| Operations | |
| Support for traffic mirroring |
Configuring a mirror destination Configuring a mirroring instance Related topics updated to support mirroring: |
| Support for adding NOS versions to the catalog using the UI | Adding a new network operating system version to the software catalog |
| Support for the gNMl management profile Support for username and passwords configuration |
Assigning a management profile to a node |
| Security | |
| Support for LDAP integration |
Federation Provider parameters |
|
Support for remote syslog for user audit logs |
|
| Configuration overrides | |
| Global Configuration Overrides support automatic deployment | Global configuration override parameters |
| Contextual Configuration Overrides support router configurations | Creating a contextual configuration override Contextual configuration override parameters |
| Fabric deviations are now handled as Global Configuration Overrides | |
| Network Resources (multiple IP and ASN pools) | |
| Configuring IP or ASN pools on the new Network Resources page | Network resources |
| IP and ASN Pools are configurable parameters for fabric intents using manual topologies | Fabric intent parameters |
| System administration | |
| Support for monitoring the health of Fabric Services System software components | Health monitoring |
| Alarms | |
New alarms added to Alarms appendix to support:
|
Appendix A: Supported alarms |
|
Enabling third-party tools to subscribe to the Fabric Services System alarm Kafka message bus |
Third-party tool access to Fabric Services System 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
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.