Overview
Structure
Section titled “Structure”The IOS-XE configuration is divided into the following sections:
entity: Different entities that can be configured in the data model, such asdevices,device groups, etc.device: Device level configuration, such as VLANs, VRFs, routing protocols, etc.interface: Interface level configuration, such as IP addresses, VLANs, etc.
Known Issues and Limitations
Section titled “Known Issues and Limitations”IOS-XE 17.15.1 - table-map Configuration Triggers DMI Synchronization Bug
Section titled “IOS-XE 17.15.1 - table-map Configuration Triggers DMI Synchronization Bug”Defect ID: CSCws49182
Affected IOS-XE Version: 17.15.1
Issue: When configuring table_maps with explicit default: copy, IOS-XE triggers a DMI (Device Management Interface) synchronization issue that can cause idempotency problems and unintended deletion of certain configuration attributes (such as ip domain lookup nsap). This results in persistent idempotency issues where the configuration must be reapplied on every run.
Workaround: Omit the default field from table_maps configuration. Since the YANG model default value for table-map default is already copy, explicitly specifying it is unnecessary and triggers the DMI sync bug.
Example - Problematic Configuration:
iosxe_system: table_maps: - name: TABLE-MAP-1 default: copy # ← Triggers DMI sync bug mappings: - from: 18 to: 18Status: This is an IOS-XE platform defect. A fix will be available in a future IOS-XE release. Until then, use the workaround above.
IOS-XE 17.15 - RESTCONF Database Sync Failure with logging persistent Attributes
Section titled “IOS-XE 17.15 - RESTCONF Database Sync Failure with logging persistent Attributes”Defect ID: CSCwt04022
Affected IOS-XE Version: 17.15
Issue: When configuring logging with both buffered_severity and persistent attributes (persistent_url, persistent_size, persistent_filesize) via RESTCONF PUT operations, IOS-XE fails to persist the buffered_severity value to the RESTCONF operational database. The configuration applies correctly to the running-config (visible via CLI), but RESTCONF GET operations return incomplete data with buffered_severity missing. This creates a discrepancy between CLI and RESTCONF database, causing Terraform idempotency failures where configuration drift is detected on every subsequent apply.
Example - Problematic Configuration:
iosxe_logging: buffered_size: 16384 buffered_severity: debugging persistent_url: bootflash:/logs # ← Triggers RESTCONF sync bug persistent_size: 1500000 # ← Triggers RESTCONF sync bug persistent_filesize: 750000 # ← Triggers RESTCONF sync bugExample - Working Configuration:
iosxe_logging: buffered_size: 16384 buffered_severity: debugging # ← Persists correctly # persistent attributes omitted as workaround monitor_severity: debugging console_severity: errors count: true # ← All other attributes work correctly rate_limit_all: 180CLI Verification:
Switch#show running-config | include bufferedlogging buffered 16384 debugging
! RESTCONF GET shows incomplete data (severity missing):! GET /restconf/data/Cisco-IOS-XE-native:native/logging/buffered-config! Returns: {"size-value": 16384} ← severity-level missingStatus: This is an IOS-XE RESTCONF platform defect. A fix will be available in a future IOS-XE release.
Additional Resources
Section titled “Additional Resources”The Data Model describes how to create resources but not what functional purpose they serve within the IOS-XE configuration. For more information about IOS-XE please visit the documentation.