- General Workflow
- play_arrow Apstra GUI
- play_arrow Devices
- Device Configuration Lifecycle
- play_arrow Managed Devices
- play_arrow System Agents
- play_arrow Pristine Configuration
- play_arrow Telemetry
- play_arrow Apstra ZTP
- play_arrow Resources Introduction
- play_arrow Datacenter Reference Design
- Create / Delete Datacenter Blueprint
- Datacenter Blueprint Summary and Dashboard
- Assign Physical Resources (Datacenter)
- Assign Device Profiles
- play_arrow Configlets (Datacenter Blueprint)
- Topology (Datacenter)
- play_arrow Nodes (Datacenter)
- Assign Device (Datacenter)
- Unassign Device (Datacenter)
- Set Deploy Mode (Datacenter)
- Generic Systems vs. External Generic Systems
- Add Generic System
- Add External Generic System
- Add Access Switch
- Update Node Tags
- Update Port Channel ID Range
- Edit Hostname (Datacenter)
- Edit Generic System Name
- Edit Device Properties (Datacenter)
- View Node's Static Routes
- Delete Node
- play_arrow Links (Datacenter)
- Add Links to Leaf
- Add Links to Spine
- Add Links to Generic System
- Add Links to External Generic System
- Add Leaf Peer Links
- Form LAG
- Break LAG
- Update LAG Mode
- Update Link Tags
- Update Link Speed
- Update Link Properties
- Delete Link (Datacenter)
- Import / Export Cabling Map (Datacenter)
- Edit Cabling Map (Datacenter)
- Fetch Discovered LLDP Data (Datacenter)
- play_arrow Racks (Datacenter)
- play_arrow Pods (Datacenter)
- play_arrow Planes (Datacenter)
- play_arrow Virtual Networks
- play_arrow Routing Zones
- Static Routes (Virtual)
- Protocol Sessions (Virtual)
- Data Center Interconnect (DCI) / Remote EVPN Gateways (Virtual)
- play_arrow Virtual Infra (Virtual)
- play_arrow Endpoints Overview (Virtual)
- play_arrow Policies (Datacenter) Staged
- Logical Devices (Datacenter Blueprint)
- Interface Maps (Datacenter Blueprint)
- play_arrow Property Sets (Datacenter Blueprint)
- AAA Servers (Datacenter Blueprint)
- Tags (Datacenter Blueprint)
- Tasks (Datacenter) Staged
- play_arrow Connectivity Templates
- play_arrow Primitives
- Virtual Network (Single) Primitive
- Virtual Network (Multiple) Primitive
- IP Link Primitive
- Static Route Primitive
- Custom Static Route Primitive
- BGP Peering (IP Endpoint) Primitive
- BGP Peering (Generic System) Primitive
- Dynamic BGP Peering Primitive
- Routing Policy Primitive
- Routing Zone Constraint Primitive
- User-defined
- Pre-defined
- Create Connectivity Template for Multiple VNs on Same Interface (Example)
- Create Connectivity Template for Layer 2 Connected External Router (Example)
- Assign Connectivity Template
- Edit Connectivity Template
- Delete Connectivity Template
- play_arrow Active (Datacenter Blueprint)
- BGP Route Tagging
- play_arrow Freeform Reference Design
- Create / Delete Freeform Blueprint
- Freeform Blueprint Summary and Dashboard
- Topology (Freeform)
- play_arrow Systems (Freeform)
- Device Context (Freeform)
- play_arrow Links (Freeform)
- play_arrow Resource Management
- play_arrow Config Templates (Freeform Blueprint)
- Import Device Profile (Freeform)
- play_arrow Property Sets (Freeform Blueprints)
- play_arrow Tags (Freeform Blueprint)
- Tasks - Staged (Freeform)
- play_arrow Active
- Commit Blueprint
- Time Voyager
- play_arrow Analytics
- Configure Auto-Enabled Dashboards
- Instantiate Predefined Dashboard
- Create Analytics Dashboard
- Edit / Delete Dashboard
- Anomalies (Analytics)
- Widgets Overview
- Create Anomaly Heat Map Widget
- Create Stage Widget
- Edit / Delete Widget
- Probes
- Instantiate Predefined Probe
- Create Probe
- Import / Export Probe
- Edit / Delete Probe
- play_arrow Providers (External Systems)
- play_arrow Platform
- play_arrow User/Role Management (Platform)
- play_arrow Security (Platform)
- Syslog Configuration (Platform)
- Receivers (Platform)
- Global Statistics (Platform)
- Event Log (Platform)
- play_arrow Apstra VM Clusters
- play_arrow Developers (Platform)
- play_arrow Juniper Technical Support
- Favorites & User
- play_arrow Apstra Server Management
- Monitor Apstra Server via CLI
- Restart Apstra Server
- Reset Apstra Server VM Password
- Reinstall Apstra Server
- Apstra Database Overview
- Back up Apstra Database
- Restore Apstra Database
- Reset Apstra Database
- Migrate Apstra Database
- Replace SSL Certificate on Apstra Server with Signed One
- Replace SSL Certificate on Apstra Server with Self-Signed One
- Change Apstra Server Hostname
- Apstra CLI Utility
- play_arrow Guides
- play_arrow References
- play_arrow Apstra Feature Matrix
- Qualified Devices and NOS Versions
- NOS Upgrade Paths (Devices)
- play_arrow Predefined Dashboards (Analytics)
- Device Environmental Health Summary Dashboard (New in 4.1.2)
- Device Health Summary Dashboard
- Device Telemetry Health Summary Dashboard (New in 4.1.2)
- Drain Validation Dashboard
- Throughput Health MLAG Dashboard
- Traffic Trends Dashboard
- Virtual Infra Fabric Health Check Dashboard
- Virtual Infra Redundancy Check Dashboard
- play_arrow Predefined Probes (Analytics)
- BGP Session Flapping Probe
- Bandwidth Utilization Probe
- Critical Services: Utilization, Trending, Alerting Probe
- Device Environmental Checks Probe (New in 4.1.2)
- Device System Health Probe
- Device Telemetry Health Probe
- Device Traffic Probe
- Drain Traffic Anomaly Probe
- ECMP Imbalance (External Interfaces) Probe
- ECMP Imbalance (Fabric Interfaces) Probe
- ECMP Imbalance (Spine to Superspine Interfaces) Probe
- ESI Imbalance Probe
- EVPN Host Flapping Probe
- EVPN VXLAN Type-3 Route Validation Probe
- EVPN VXLAN Type-5 Route Validation Probe
- External Routes Probe
- Hot/Cold Interface Counters (Fabric Interfaces) Probe
- Hot/Cold Interface Counters (Specific Interfaces) Probe
- Hot/Cold Interface Counters (Spine to Superspine Interfaces) Probe
- Hypervisor and Fabric LAG Config Mismatch Probe (Virtual Infra)
- Hypervisor and Fabric VLAN Config Mismatch Probe (Virtual Infra)
- Hypervisor MTU Mismatch Probe (Virtual Infra NSX-T Only)
- Hypervisor MTU Threshold Check Probe (Virtual Infra)
- Hypervisor Missing LLDP Config Probe (Virtual Infra)
- Hypervisor Redundancy Checks Probe (Virtual Infra)
- Interface Flapping (Fabric Interfaces) Probe
- Interface Flapping (Specific Interfaces) Probe
- Interface Flapping (Specific Interfaces) Probe
- Interface Policy 802.1x Probe
- LAG Imbalance Probe
- Leafs Hosting Critical Services: Utilization, Trending, Alerting Probe
- Link Fault Tolerance in Leaf and Access LAGs Probe
- MLAG Imbalance Probe
- Multiagent Detector Probe
- Optical Transceivers Probe
- Packet Discard Percentage Probe
- Spine Fault Tolerance Probe
- Total East/West Traffic Probe
- VMs without Fabric Configured VLANs Probe (Virtual Infra)
- VXLAN Flood List Validation Probe
- play_arrow Probe Processors (Analytics)
- Processor: Accumulate
- Processor: Average
- Processor: Comparison
- Processor: EVPN Type 3
- Processor: EVPN Type 5
- Processor: Extensible Service Data Collector
- Processor: Generic Graph Collector
- Processor: Generic Service Data Collector
- Processor: Interface Counters
- Processor: Logical Operator
- Processor: Match Count
- Processor: Match Percentage
- Processor: Match String
- Processor: Max
- Processor: Min
- Processor: Periodic Average
- Processor: Range
- Processor: Ratio
- Processor: Service Data Collector
- Processor: Set Comparison
- Processor: Set Count
- Processor: Standard Deviation
- Processor: State
- Processor: Subtract
- Processor: Sum
- Processor: System Utilization
- Processor: Time in State
- Processor: Traffic Monitor
- Processor: Union
- Processor: VXLAN Floodlist
- Configlet Examples (Design)
- Apstra-CLI Commands
- Apstra EVPN Support Addendum
- Apstra Server Configuration File
- Agent Configuration File (Devices)
- Graph
- Juniper Apstra Technology Preview
Interface Maps (Datacenter Design)
Interface Map Overview
Interface maps consist of interfaces used for achieving the intended network configuration rendering. They map interfaces between logical devices and physical hardware devices (represented with device profiles) while adhering to vendor specifications.
Some characteristics and capabilities of interface maps include:
- Precisely select device ports, transformations and interfaces.
- You are not restricted to selecting interfaces in a contiguous manner.
- Provision QSFP+ breakout ports to transform ports, such 40GbE ports to 10GbE, 100GbE ports to 25GbE, and so on.
- Port breakouts and available speeds affect possible values of the mapping fields.
- The logical device enables you to plan port and panel mappings accordingly. For example, you can assign a network policy that ensures that spine uplink ports on a leaf switch are always the furthest right ports on a panel.
- If a smaller logical device is mapped to a larger physical device, the unmapped ports in the device profile are marked as Unused in the interface map.
From the left navigation menu, navigate to Design > Interface Maps to go to interface maps in the global catalog. You can create, clone, edit and delete interface maps.
Click an interface map name to go to its details.
Click a port to go to interface details. Interface maps include the following details:
Logical Device | Abstraction of the physical device. |
Device Profile | Physical device characteristics. |
Interfaces | Mapping between logical devices and physical devices (device profile) |
Create Interface Map
- From the left navigation menu, navigate to Design > Interface Maps and click Create Interface Map.
- Enter a unique name (64 characters or fewer). This field can be left blank for the name to be created for you that consists of the concatenation of the names of the selected logical device and device profile.
- Select a logical device from the drop-down list. If you don't see a logical device that fits your requirements, you can create one.
- Select a device profile from the drop-down list. If you don't see a device profile that fits your requirements, you can create one.
- Map the logical device to the device profile. See example below for details.
- Click Create to create the interface map and return to the table view.
Example: Create Interface Map with Breakout Ports
To create dense server connectivity, let's create an interface map that breaks out the twenty-four 40 GbE transformable ports of an Arista DCS-7050QX-32 physical device to ninety-six 10 GbE ports of a 96x10-8x40-2 logical device.
96x10-8x40-2 is not one of the predefined logical devices that ships with Apstra software, so if you have not created it you won't find it in the drop-down list. If you'd like to follow along with this example, you can create the logical device before continuing.
- From the left navigation menu, navigate to Design > Interface Maps and click Create Interface Map. Leave the name blank. It will populate automatically as you enter more information.
- From the Logical Device drop-down list, select 96x10-8x40-2. This logical device has 96-10 GbE ports for servers and 8-40 GbE ports for uplinks to spine switches or external routers.
- From the Device Profile drop-down list, select Arista DCS-7050QX-32. This device has 24-40 GbE QSFP+ ports that are transformable (4x10 GbE or 1x40 GbE) and 8-40 GbE QSFP+ ports that are not transformable. As soon as both the logical device and device profile are selected, the interface map name is automatically populated.
- Under Device profile interfaces (middle-right) click Select Interfaces for the 10 GbE logical ports. This displays the port layout.
- Drag to select the first 24 ports. As the ports are selected the white numbers turn gray. When all interfaces are selected the red circle turns green.
- Under Device profile interfaces (middle-right) click Select Interfaces for the 40 GbE ports. This displays the port layout.
- Drag to select the remaining 8 ports. As the ports are selected the white numbers turn gray. When all interfaces are selected the red circle turns green.
- Click Create to create the interface map and return to the table view. The new interface map is shown in the overview screenshot above.
Example: Inter Port Constraints - Disabled Ports
Inter Port Constraint Overview
(Cumulus is no longer supported as of Apstra version 4.1.0, although Cumulus examples remain for illustrative purposes.) Inter port constraints for Cumulus devices are handled in both the device profile and the interface map. For Apstra to generate the correct ports.conf file with these constraints, the unused interfaces must be disabled in the interface map.
For example, if each of the top (odd-numbered) QSFP28 ports in a Mellanox 2700 device are split into four SFP28 ports, the bottom (even-numbered) QSFP28 ports are blocked. (Source: https://docs.mellanox.com/display/sn2000pub/Cable+Installation) The blocked interfaces must be disabled. Using the predefined interface map Mellanox_MSN2700_Cumulus__AOS-48x10_8x100-1 as an example, ports 1,3,5,7,9,11,13,15,17,19,21, and 23 were used to generate the 4x10G interfaces, and the 5th transformation for ports 2,4,6,8,10,12,14,16,18,20,22, and 24 have been disabled.
Disable Unused Ports
When creating an interface map that requires disabling ports for inter port constraints, the prompt Do you want to select the disabled interfaces for unused device profile ports? is displayed. To disable the corresponding ports, click OK.
Edit Interface Map
Any changes made to predefined interface maps (the ones that ship with Apstra software) are discarded when Apstra is upgraded. To retain a customized interface map through Apstra upgrades, clone the predefined interface map, give it a unique name, and customize it instead of changing the predefined one directly.
- Either from the table view (Design > Interface Maps) or the details view, click the Edit button for the interface map to edit.
- Make your changes.
- Click Update (bottom-right) to update the interface map and return to the table view.