Skip to content

Device

Location in GUI: Provision » Inventory

Diagram
NameTypeConstraintMandatoryDefault Value
devicesList[devices]No

NameTypeConstraintMandatoryDefault Value
nameStringYes
fqdn_nameStringNo
device_ipIPNo
pidAnyString or NullNo
serial_numberAnyString or NullNo
stateChoiceINIT, PNP, PROVISION, REPROVISION, ASSIGNYes
device_roleChoiceACCESS, CORE, DISTRIBUTION, BORDER ROUTERYes
siteStringYes
fabric_siteStringNo
fabric_rolesListChoice[BORDER_NODE, CONTROL_PLANE_NODE, EDGE_NODE, WIRELESS_CONTROLLER_NODE]No
onboarding_templateClass[onboarding_template]No
dayn_templatesClass[dayn_templates]No
primary_managed_ap_locationsListStringNo
secondary_managed_ap_locationsListStringNo
port_assignmentsList[port_assignments]No
tagsListStringNo

onboarding_template (catalyst_center.inventory.devices)

Section titled “onboarding_template (catalyst_center.inventory.devices)”
NameTypeConstraintMandatoryDefault Value
nameStringYes
variablesList[variables]No

dayn_templates (catalyst_center.inventory.devices)

Section titled “dayn_templates (catalyst_center.inventory.devices)”
NameTypeConstraintMandatoryDefault Value
regularList[regular]No
compositeList[composite]No
redeploy_templateChoiceALWAYS, NEVER, ON_CHANGENo

port_assignments (catalyst_center.inventory.devices)

Section titled “port_assignments (catalyst_center.inventory.devices)”
NameTypeConstraintMandatoryDefault Value
interface_nameStringNo
connected_device_typeChoiceUSER_DEVICE, ACCESS_POINT, TRUNKING_DEVICE, AUTHENTICATOR_SWITCH, SUPPLICANT_BASED_EXTENDED_NODEYes
data_vlan_nameStringNo
voice_vlan_nameStringNo
security_group_nameStringNo
authenticate_template_nameChoiceNo Authentication, Open Authentication, Closed Authentication, Low ImpactNo

variables (catalyst_center.inventory.devices.onboarding_template)

Section titled “variables (catalyst_center.inventory.devices.onboarding_template)”
NameTypeConstraintMandatoryDefault Value
nameStringYes
valueStringYes

regular (catalyst_center.inventory.devices.dayn_templates)

Section titled “regular (catalyst_center.inventory.devices.dayn_templates)”
NameTypeConstraintMandatoryDefault Value
nameStringYes
variablesList[variables]No
redeploy_templateChoiceALWAYS, NEVER, ON_CHANGENo
copying_configBooleantrue, falseNo
force_push_templateBooleantrue, falseNo

composite (catalyst_center.inventory.devices.dayn_templates)

Section titled “composite (catalyst_center.inventory.devices.dayn_templates)”
NameTypeConstraintMandatoryDefault Value
nameStringYes
variablesList[variables]No
redeploy_templateChoiceALWAYS, NEVER, ON_CHANGENo
copying_configBooleantrue, falseNo
force_push_templateBooleantrue, falseNo

variables (catalyst_center.inventory.devices.dayn_templates.composite)

Section titled “variables (catalyst_center.inventory.devices.dayn_templates.composite)”
NameTypeConstraintMandatoryDefault Value
nameStringYes
valueStringYes
template_nameStringYes

Example-1: SD-Access Border Router Device Configuration

This example demonstrates how to configure a border router device in Catalyst Center inventory with SD-Access fabric capabilities. Border routers serve as critical infrastructure components that connect the SD-Access fabric to external networks and provide advanced routing and policy enforcement functions.

The border router device configuration includes:

  • Device name (BR01) for identification and inventory management
  • Management IP address (192.168.10.1) for device communication and monitoring
  • PROVISION state for active deployment and configuration management
  • Border router role designation for network function
  • Site assignment (Global/Canada) for geographic and organizational placement
  • Fabric site association (Global/Canada) for SD-Access fabric membership
  • Multiple fabric roles including BORDER_NODE for external connectivity and CONTROL_PLANE_NODE for fabric control plane operations
catalyst_center:
inventory:
devices:
- name: BR01
fqdn_name: BR01.company.local
device_ip: 192.168.10.1
state: PROVISION
device_role: BORDER ROUTER
site: Global/Canada
fabric_site: Global/Canada
fabric_roles:
- BORDER_NODE
- CONTROL_PLANE_NODE

Example-2: Access Switch with Edge Node Functionality

This example shows how to configure an access layer switch with SD-Access edge node capabilities for endpoint connectivity and policy enforcement at the network edge.

catalyst_center:
inventory:
devices:
- name: ACCESS-SW01
fqdn_name: ACCESS-SW01.company.local
device_ip: 192.168.20.10
serial_number: FOC2644021A
pid: C9300-24P
state: PROVISION
device_role: ACCESS
site: Global/North America/Campus/Building A/Floor 1
fabric_site: Global/North America/Campus
fabric_roles:
- EDGE_NODE
tags:
- FLOOR1_DEVICES
- EMPLOYEE_ACCESS