Skip to content

Inventory overview

The Inventory section centralizes Avalon's data model to represent your network.

To ensure clarity and scalability, the inventory is organized into four logical categories:

  • Infrastructure Your physical and logical topology: Sites, Devices, Redundancy groups, and ZTP provisioning.
  • Network Services Configurations and services deployed on the infrastructure: VLANs and Custom Services.
  • Access & Policies Security and identity management: RADIUS Management and Users.
  • Hardware Catalog Global library of device templates: Vendors, Families, Models, Images, and Interface Lists.

Resource scope

In the inventory, data visibility depends on the resource type. You need to distinguish between Global Definitions (templates) and Tenant Data (instances).

Global Resources

Shared across all tenants, available regardless of the selected tenant.

  • Hardware Catalog: Vendors, Families, Models, Images, Interface Lists.
  • Service Templates: Custom service template definitions (their application remains local).

Single-Tenant Resources

Data specific to your environment, strictly isolated to the currently selected tenant.

  • Infrastructure: Sites, Devices, Redundancy groups.
  • Services & Policies: VLANs, RADIUS servers, Users.
  • Service Instances: Deployment of a custom service on a device.

Prerequisites

AutoDiscovery automatically populates certain data (Devices, Device Models, Interface Lists), but most Hardware Catalog data must be entered manually.

Before manually adding a "Static" device or provisioning a "ZTP" device, the Vendor, Device Family, and Device Model data must exist in the Hardware Catalog.

Roadmap: IPAM Integration

As Avalon evolves, new data (Subnets, Aggregates, VRFs) will integrate seamlessly into the Network Services section.