Skip to content

Overview

The IOS-XE configuration is divided into the following sections:

  • entity: Different entities that can be configured in the data model, such as devices, device groups, etc.
  • device: Device level configuration, such as VLANs, VRFs, routing protocols, etc.
  • interface: Interface level configuration, such as IP addresses, VLANs, etc.

IOS-XE 17.15.1 - table-map and ip_domain_lookup_nsap

Section titled “IOS-XE 17.15.1 - table-map and ip_domain_lookup_nsap”

Defect ID: CSCws49182

Affected IOS-XE Version: 17.15.1

Issue: When configuring both table_maps with explicit default: copy and ip_domain_lookup_nsap: true in the same data model, IOS-XE triggers a DMI (Device Management Interface) synchronization that incorrectly deletes ip domain lookup nsap from the device configuration. This results in persistent idempotency issues where the configuration must be reapplied on every run (up until the third terraform apply).

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: 18
ip_domain_lookup_nsap: true # ← Gets deleted by DMI sync

Example - Working Configuration:

iosxe_system:
table_maps:
- name: TABLE-MAP-1
# default field omitted - relies on YANG default value of "copy"
mappings:
- from: 18
to: 18
ip_domain_lookup_nsap: true # ← Persists correctly

Status: This is an IOS-XE platform defect. A fix will be available in a future IOS-XE release. Until then, use the workaround above.

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.