Cisco Network as Code

https://netascode.cisco.com/docs/
Admin
Cisco Network as Code is an infrastructure-as-code framework that enables teams to manage, automate,...
Tokens:1,919,249
Snippets:11,752
Trust Score:10
Update:1 month ago
Show doc for...
Tokens:
Raw
### Clone the nac-sdwan-simple-example repository

Source: https://netascode.cisco.com/docs/start/sdwan/first_steps

Clones the example repository to your local system. Requires Git to be installed.

```bash
git clone https://github.com/netascode/nac-sdwan-simple-example.git
```

--------------------------------

### Install and initialize pre-commit

Source: https://netascode.cisco.com/docs/guides/concepts/validation

Installs and initializes pre-commit. The pre-commit install command must be run from the root of the repository.

```bash
> pip install pre-commit
> pre-commit install
pre-commit installed at .git/hooks/pre-commit
```

--------------------------------

### Clone the example repository

Source: https://netascode.cisco.com/docs/start/catalystcenter/first_steps

Clones the example repository from GitHub to your local system.

```bash
git clone https://github.com/netascode/nac-catalystcenter-simple-example.git
```

--------------------------------

### Initialize Terraform with terraform init

Source: https://netascode.cisco.com/docs/start/catalystcenter/first_steps

Run terraform init to configure the backend, download provider plugins, install modules, and check version compatibility. The output shows successful initialization and the creation of the .terraform.lock.hcl file.

```bash
terraform init

```

```text
➜  nac-catalystcenter-simple-example git:(main) ✗ terraform init
Initializing the backend...
Initializing modules...
Downloading registry.terraform.io/netascode/nac-catalystcenter/catalystcenter 0.1.1 for catalyst_center...
- catalyst_center in .terraform/modules/catalyst_center
Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform
- Finding hashicorp/local versions matching ">= 2.3.0"...
- Finding hashicorp/time versions matching ">= 0.12.1"...
- Finding ciscodevnet/catalystcenter versions matching ">= 0.3.0, 0.3.0"...
- Finding netascode/utils versions matching ">= 1.0.0"...
- Installing hashicorp/local v2.5.3...
- Installed hashicorp/local v2.5.3 (signed by HashiCorp)
- Installing hashicorp/time v0.13.1...
- Installed hashicorp/time v0.13.1 (signed by HashiCorp)
- Installing ciscodevnet/catalystcenter v0.3.0...
- Installed ciscodevnet/catalystcenter v0.3.0 (signed by a HashiCorp partner, key ID 974C06066198C482)
- Installing netascode/utils v1.0.2...
- Installed netascode/utils v1.0.2 (self-signed, key ID 48630DA58CAFD6C0)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.


Terraform has been successfully initialized!


You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.


If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

```

--------------------------------

### Install GitLab Runner (Debian/Ubuntu/Mint)

Source: https://netascode.cisco.com/docs/start/aci/adding_cicd

Installs the latest version of GitLab Runner using apt-get.

```bash
sudo apt-get install gitlab-runner
```

--------------------------------

### Install GitLab Runner (RHEL/CentOS/Fedora)

Source: https://netascode.cisco.com/docs/start/aci/adding_cicd

Installs the latest version of GitLab Runner using yum.

```bash
sudo yum install gitlab-runner
```

--------------------------------

### Example data/sites.nac.yaml configuration for sites hierarchy (areas, buildings, floors)

Source: https://netascode.cisco.com/docs/start/catalystcenter/first_steps

Navigate to data/sites.nac.yaml and inspect its structure. This example contains five areas, four buildings, and six floors. Use this file to define the site hierarchy in your Cisco Catalyst Center automation.

```YAML
---
catalyst_center:
  sites:
    areas:
      - name: United States
        parent_name: Global
      - name: Golden Hills Campus
        parent_name: Global/United States
      - name: Lakefront Tower
        parent_name: Global/United States
      - name: Oceanfront Mansion
        parent_name: Global/United States
      - name: Desert Oasis Branch
        parent_name: Global/United States
    buildings:
      - name: Sunset Tower
        latitude: 34.099
        longitude: -118.366
        address: 8358 Sunset Blvd, Los Angeles, CA 90069
        country: United States
        parent_name: Global/United States/Golden Hills Campus
        ip_pools_reservations:
          - ST_CORP
          - ST_TECH
          - ST_GUEST
          - ST_BYOD
      - name: Windy City Plaza
        latitude: 41.878
        longitude: -87.630
        address: 233 S Wacker Dr, Chicago, IL 60606
        country: United States
        parent_name: Global/United States/Lakefront Tower
        ip_pools_reservations:
          - WCP_CORP
          - WCP_TECH
          - WCP_GUEST
          - WCP_BYOD
      - name: Art Deco Mansion
        latitude: 25.782
        longitude: -80.133
        address: 123 Ocean Drive, Miami Beach, FL 33139
        country: United States
        parent_name: Global/United States/Oceanfront Mansion
        ip_pools_reservations:
          - ADM_CORP
          - ADM_TECH
          - ADM_GUEST
          - ADM_BYOD
      - name: Desert Oasis Tower
        latitude: 33.448
        longitude: -112.074
        address: 1235 Cactus Ave, Phoenix, AZ 85001
        country: United States
        parent_name: Global/United States/Desert Oasis Branch
        ip_pools_reservations:
          - DOT_CORP
          - DOT_TECH
          - DOT_GUEST
          - DOT_BYOD
    floors:
      - name: FLOOR_1
        floor_number: 1
        parent_name: Global/United States/Golden Hills Campus/Sunset Tower
      - name: FLOOR_2
        floor_number: 2
        parent_name: Global/United States/Golden Hills Campus/Sunset Tower
      - name: FLOOR_1
        floor_number: 1
        parent_name: Global/United States/Lakefront Tower/Windy City Plaza
      - name: FLOOR_2
        floor_number: 2
        parent_name: Global/United States/Lakefront Tower/Windy City Plaza
      - name: FLOOR_1
        floor_number: 1
        parent_name: Global/United States/Oceanfront Mansion/Art Deco Mansion
      - name: FLOOR_1
        floor_number: 1
        parent_name: Global/United States/Desert Oasis Branch/Desert Oasis Tower
```

--------------------------------

### ip_pools.nac.yaml configuration example

Source: https://netascode.cisco.com/docs/start/catalystcenter/first_steps

Example YAML file defining four IP pools (US_CORP, US_TECH, US_GUEST, US_BYOD) with DHCP and DNS servers and reserved subpools. It is used to validate the structure of the network settings.

```yaml
---
catalyst_center:
  network_settings:
    ip_pools:
      - name: US_CORP
        ip_address_space: IPv4
        ip_pool_cidr: 10.201.0.0/16
        dhcp_servers:
          - 10.201.0.1
        dns_servers:
          - 10.201.0.1
        ip_pools_reservations:
          - name: DOT_CORP
            prefix_length: 24
            subnet: 10.201.1.0
          - name: ST_CORP
            prefix_length: 24
            subnet: 10.201.2.0
          - name: WCP_CORP
            prefix_length: 24
            subnet: 10.201.3.0
          - name: ADM_CORP
            prefix_length: 24
            subnet: 10.201.4.0
      - name: US_TECH
        ip_address_space: IPv4
        ip_pool_cidr: 10.202.0.0/16
        dhcp_servers:
          - 10.202.0.1
        dns_servers:
          - 10.202.0.1
        ip_pools_reservations:
          - name: DOT_TECH
            prefix_length: 24
            subnet: 10.202.1.0
          - name: ST_TECH
            prefix_length: 24
            subnet: 10.202.2.0
          - name: WCP_TECH
            prefix_length: 24
            subnet: 10.202.3.0
          - name: ADM_TECH
            prefix_length: 24
            subnet: 10.202.4.0
      - name: US_GUEST
        ip_address_space: IPv4
        ip_pool_cidr: 10.203.0.0/16
        dhcp_servers:
          - 10.203.0.1
        dns_servers:
          - 10.203.0.1
        ip_pools_reservations:
          - name: DOT_GUEST
            prefix_length: 24
            subnet: 10.203.1.0
          - name: ST_GUEST
            prefix_length: 24
            subnet: 10.203.2.0
          - name: WCP_GUEST
            prefix_length: 24
            subnet: 10.203.3.0
          - name: ADM_GUEST
            prefix_length: 24
            subnet: 10.203.4.0
      - name: US_BYOD
        ip_address_space: IPv4
        ip_pool_cidr: 10.204.0.0/16
        dhcp_servers:
          - 10.204.0.1
        dns_servers:
          - 10.204.0.1
        ip_pools_reservations:
          - name: DOT_BYOD
            prefix_length: 24
            subnet: 10.204.1.0
          - name: ST_BYOD
            prefix_length: 24
            subnet: 10.204.2.0
          - name: WCP_BYOD
            prefix_length: 24
            subnet: 10.204.3.0
          - name: ADM_BYOD
            prefix_length: 24
            subnet: 10.204.4.0
```

--------------------------------

### GitLab Runner registration output

Source: https://netascode.cisco.com/docs/start/aci/adding_cicd

Example output from the registration command, showing the prompts and successful registration. The actual output may vary by operating system.

```text
gitlab-runner register  --url https://gitlab.com  --token glrt-xxxx


Enter the GitLab instance URL (for example, https://gitlab.com/):
[https://gitlab.com]:
Verifying runner... is valid                        correlation_id=ee674944d1ac4090a5ec961320c70e8b runner=Py8QHuPeT
Enter a name for the runner. This is stored only in the local config.toml file:
[centos-stream10-runners]: cicd-nac-runner
Enter an executor: virtualbox, docker-windows, docker+machine, kubernetes, ssh, docker, docker-autoscaler, instance, custom, shell, parallels:
docker
Enter the default Docker image (for example, ruby:3.3):
docker
Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!


Configuration (with the authentication token) was saved in "/home/<user>/.gitlab-runner/config.toml"
```

--------------------------------

### GitLab Runner status and verify output

Source: https://netascode.cisco.com/docs/start/aci/adding_cicd

Example output from the status and verify commands, showing the runner is running and valid. Actual output may vary.

```text
[root@localhost ~]# gitlab-runner status
Runtime platform                                    arch=amd64 os=linux pid=1598 revision=9ba718cd version=18.3.0
gitlab-runner: Service is running


[root@localhost ~]# gitlab-runner verify
Runtime platform                                    arch=amd64 os=linux pid=1606 revision=9ba718cd version=18.3.0
WARNING: Running in user-mode.
WARNING: The user-mode requires you to manually start builds processing:
WARNING: $ gitlab-runner run
WARNING: Use sudo for system-mode:
WARNING: $ sudo gitlab-runner...


Verifying runner... is valid                        correlation_id=8f7a6ca9a3794e5aa31d8af0aac9f0b4 runner=Py8QHuPeT
```

--------------------------------

### Example import commands for provision devices

Source: https://netascode.cisco.com/docs/changelogs/catalystcenter/upgrade_procedures

Example import commands for each device using the new resource name and the site_id,network_device_id format.

```bash
terraform import 'module.catalyst_center.catalystcenter_provision_device.provision_device["BR10"]' "d3fa2852-cbca-4387-93c9-f1e47b6f7340,e7869917-cf34-44ed-998a-e72ef9866eeb"
terraform import 'module.catalyst_center.catalystcenter_provision_device.provision_device["EDGE01"]' "d3fa2852-cbca-4387-93c9-f1e47b6f7340,7ef492ca-b008-479a-9de4-7e40438c7d10"
terraform import 'module.catalyst_center.catalystcenter_provision_device.provision_device["FIAB"]' "944b4c7e-e9ed-4ec3-8d1f-e8d065a8c4b3,28a9f0f0-2834-4f12-8409-26d34a7f5bbb"
terraform import 'module.catalyst_center.catalystcenter_provision_device.provision_device["Transit-CP-1"]' "944b4c7e-e9ed-4ec3-8d1f-e8d065a8c4b3,e9272b6f-6ef0-487c-92dd-bce5c21747d7"
```

--------------------------------

### Clone the nac-meraki-simple-example repository

Source: https://netascode.cisco.com/docs/start/meraki/first_steps

Clones the example repository and changes into its directory. Requires Git to be installed.

```bash
git clone https://github.com/netascode/nac-meraki-simple-example.git
cd nac-meraki-simple-example

```

--------------------------------

### Clone the nac-aci-simple-example repository

Source: https://netascode.cisco.com/docs/start/aci/first_steps

Clones the example repository to your local system. Requires Git to be installed.

```bash
git clone https://github.com/netascode/nac-aci-simple-example.git
```

--------------------------------

### Example plan output for new provision device

Source: https://netascode.cisco.com/docs/changelogs/catalystcenter/upgrade_procedures

Example plan output showing the new resource creation with the network_device_id and site_id values to save for the import step.

```hcl
# module.catalyst_center.catalystcenter_provision_device.provision_device["BR10"] will be created
+ resource "catalystcenter_provision_device" "provision_device" {
    + id                = (known after apply)
    + network_device_id = "e7869917-cf34-44ed-998a-e72ef9866eeb"
    + reprovision       = false
    + site_id           = "d3fa2852-cbca-4387-93c9-f1e47b6f7340"
  }
```

--------------------------------

### Basic Network Creation

Source: https://netascode.cisco.com/docs/data_models/meraki/networks/create

Example demonstrating basic network creation with product types, timezone, notes, and tags.

```yaml
meraki:
  domains:
    - name: !env domain
      administrator:
        name: !env org_admin
      organizations:
        - name: !env org
          networks:
            - name: !env network_name
              product_types:
                - appliance
                - switch
                - wireless
                - camera
                - sensor
                - cellularGateway
              time_zone: Europe/Berlin
              notes: Example data.yaml file
              tags:
                - admin
                - dev
                - emea

```

--------------------------------

### Prerequisites: FMC Device and Policy Setup

Source: https://netascode.cisco.com/docs/data_models/fmc/devices/device_sub_interface

Defines the required FMC domain configuration with an access control policy, security zone, and a device with a physical interface. This setup is a prerequisite for the sub-interface example.

```yaml
fmc:
  domains:
    - name: Global
      policies:
        access_control_policies:
          - name: MyAccessPolicyName2
            default_action: BLOCK
      objects:
        security_zones:
          - name: MySecurityZoneName1
      devices:
        devices:
          - name: MyDeviceName1
            host: 10.1.120.203
            access_control_policy: MyAccessPolicyName2
            registration_key: cisco123
            deploy: true
            licenses:
            - ESSENTIALS
            - IPS
            performance_tier: FTDv5
            vrfs:
              - name: Global
                physical_interfaces:
                  - name: GigabitEthernet0/2

```

--------------------------------

### Full Redirect Policy Example with All Attributes

Source: https://netascode.cisco.com/docs/data_models/apic/tenants/redirect_policy

Full example defining three redirect policies with all available attributes: PBR1 (L3) with hashing, thresholds, backup policy, and L3 destinations; PBR_L1 (L1) with hashing and L1/L2 destination; PBR_L2 (L2) with hashing, resilient hashing, and L1/L2 destination. Shows optional fields like alias, description, anycast, threshold settings, and concrete interface references.

```yaml
apic:
  tenants:
    - name: ABC
      services:
        redirect_policies:
          - name: PBR1
            alias: PBR1
            description: My Desc
            type: L3
            anycast: false
            hashing: sip-dip-prototype
            threshold: false
            max_threshold: 0
            min_threshold: 0
            threshold_down_action: permit
            resilient_hashing: false
            redirect_backup_policy: L4L7_REDIRECT_BACKUP1
            rewrite_source_mac: false
            l3_destinations:
              - description: My Desc
                name: L3_DEST1
                ip: 1.1.1.1
                ip_2: 2.2.2.2
                mac: 00:00:00:11:22:33
                pod: 1
                redirect_health_group: HEALTH_GROUP_1
          - name: PBR_L1
            alias: PBR_L1
            description: My Desc
            type: L1
            hashing: sip-dip-prototype
            resilient_hashing: false
            l1l2_destinations:
              - description: L1 destination
                name: L1_DEST1
                redirect_health_group: HEALTH_GROUP_L1
                concrete_interface:
                  l4l7_device: DEV-L1
                  concrete_device: DEV1-L1
                  interface: INT1
          - name: PBR_L2
            alias: PBR_L2
            description: My Desc
            type: L2
            hashing: sip-dip-prototype
            resilient_hashing: false
            l1l2_destinations:
              - description: L2 destination
                name: L2_DEST1
                mac: 00:00:00:11:22:34
                weight: 1
                pod: 1
                redirect_health_group: HEALTH_GROUP_L2
                concrete_interface:
                  l4l7_device: DEV-L2
                  concrete_device: DEV1-L2
                  interface: INT1
```

--------------------------------

### Terraform version output

Source: https://netascode.cisco.com/docs/labs/meraki/02_setup-mac

Example output of 'terraform -v' showing Terraform v1.13.4 and the installed providers. The version may differ; the lab does not require a specific version.

```bash
Terraform v1.13.4
on linux_amd64
+ provider registry.terraform.io/ciscodevnet/meraki v1.9.0
+ provider registry.terraform.io/hashicorp/local v2.7.0
+ provider registry.terraform.io/netascode/utils v1.0.2


Your version of Terraform is out of date! The latest version
is 1.14.7. You can update by downloading from https://developer.hashicorp.com/terraform/install
```

--------------------------------

### Simple HSRP group policy example

Source: https://netascode.cisco.com/docs/data_models/apic/tenants/hsrp_group_policy

Minimal HSRP group policy configuration with only the required name and preempt fields. Use this as a starting point for a simple policy.

```yaml
apic:
  tenants:
    - name: ABC
      policies:
        hsrp_group_policies:
          - name: HSRP_GRP1
            preempt: true

```

--------------------------------

### Clone example repository with git

Source: https://netascode.cisco.com/docs/labs/meraki/02_setup-mac

Clone the example repository into the network-as-code directory using the v0.1 tag.

```bash
cd ~/network-as-code
git clone --branch v0.1 --depth 1 https://github.com/netascode/nac-meraki-example meraki-as-code
```

--------------------------------

### Full Example

Source: https://netascode.cisco.com/docs/data_models/apic/tenants/l3out

Comprehensive L3Out configuration with QoS, BGP, OSPF, route leaking, redistribution, dampening, and detailed interface settings including VPC and port-channel. Use for full-featured L3Out setups.

```yaml
apic:
  tenants:
    - name: ABC
      l3outs:
        - name: L3OUT1
          alias: L3OUT1-ALIAS
          description: My Desc
          target_dscp: AF13
          qos_class: level3
          import_route_control_enforcement: true
          export_route_control_enforcement: true
          custom_qos_policy: QOS_POLICY
          vrf: VRF1
          domain: ROUTED1
          bfd_policy: BFD1
          dhcp_labels:
            - dhcp_relay_policy: DHCP-RELAY1
              dhcp_option_policy: DHCP-OPTION1
              scope: tenant
          bgp:
            timer_policy: BGP_TIMER1
            as_path_policy: BGP_AS_PATH1
          ospf:
            area: 0
            area_type: regular
            area_cost: 1
            auth_type: simple
            auth_key: cisco
            auth_key_id: 1
            policy: OIP1
          interleak_route_map: ROUTE_MAP1
          default_route_leak_policy:
            always: false
            criteria: 'in-addition'
            context_scope: false
            outside_scope: false
          redistribution_route_maps:
            - source: direct
              route_map: ROUTE_MAP2
          dampening_ipv4_route_map: ROUTE_MAP3
          dampening_ipv6_route_map: ROUTE_MAP4
          nodes:
            - node_id: 101
              router_id: 5.5.5.5
              router_id_as_loopback: true
              static_routes:
                - prefix: 2.2.2.0/24
                  description: My Desc
                  preference: 1
                  next_hops:
                    - ip: 6.6.6.6
                      description: My Next Hop Desc
              interfaces:
                - channel: VPC1
                  svi: true
                  scope: local
                  vlan: 301
                  ip_a: 14.14.14.1/24
                  ip_b: 14.14.14.2/24
                  ip_shared: 14.14.14.3/24
                  ip_shared_dhcp_relay: true
                  link_local_address: fe80::ffff:ffff:ffff:ffff
                  mode: native
                  bgp_peers:
                    - ip: 14.14.14.14
                      remote_as: 65010
                      description: My Desc
                      allow_self_as: true
                      as_override: true
                      bfd: true
                      disable_connected_check: true
                      remove_private_as: true
                      remove_all_private_as: true
                      multicast_address_family: true
                      ttl: 1
                      weight: 0
                      password: C1sco123
                      local_as: 1234
                      as_propagate: dual-as
                      peer_prefix_policy: BGP_PP1
                      export_route_control: ROUTE_MAP1
                      import_route_control: ROUTE_MAP2
                - channel: PC1
                  vlan: 311
                  ip: 24.24.24.1/24
                  bgp_peers:
```

--------------------------------

### Sample CLI Configuration for Line Console, Default, and Template

Source: https://netascode.cisco.com/docs/data_models/iosxr/device/line

The sample CLI configuration demonstrates how to configure console, default, and template lines with various settings such as access-class, exec-timeout, session-limit, transport, and user groups. Use this as a reference for generating configuration commands.

```text
line console
 access-class ingress ACL1
 access-class egress ACL1
 exec-timeout 30 0
 session-limit 15
 session-timeout 1440 output
 timeout login response 60
 absolute-timeout 3600
 width 80
 length 25
 transport input ssh
 transport output ssh telnet
 transport preferred ssh
 timestamp disable
 pager none
 telnet transparent
 cli-whitespace-completion
 users group cisco-support
 users group netadmin
!
line default
 access-class ingress ACL1
 access-class egress ACL1
 exec-timeout 30 0
 session-limit 15
 session-timeout 1440 output
 timeout login response 60
 absolute-timeout 3600
 width 80
 length 25
 transport input ssh
 transport output ssh telnet
 transport preferred ssh
 timestamp disable
 telnet transparent
 cli-whitespace-completion
 users group cisco-support
!
line template template-1
 access-class ingress ACL1
 access-class egress ACL1
 exec-timeout 30 0
 session-limit 15
 session-timeout 1440 output
 timeout login response 60
 absolute-timeout 3600
 width 81
 length 25
 transport input ssh
 transport output ssh telnet
 transport preferred ssh
 timestamp disable
 telnet transparent
 cli-whitespace-completion
 users group cisco-support
!
```

--------------------------------

### Adding a leaf switch entry to node_policies.nac.yaml

Source: https://netascode.cisco.com/docs/start/aci/full_configuration

Example block to insert into the 'nodes:' section of 'node_policies.nac.yaml' to add an additional leaf switch. Must include the serial number and update the section starting at line 18.

```yaml
      - id: 1103
        pod: 1
        role: leaf
        serial_number: SN-1-1103
        name: leaf-1103
        oob_address: 10.51.77.96/24
        oob_gateway: 10.51.77.254
        update_group: MG1
        fabric_policy_group: all-leafs
        access_policy_group: all-leafs

```

--------------------------------

### Simple LDAP provider configuration

Source: https://netascode.cisco.com/docs/data_models/apic/fabric_policies/ldap

Minimal LDAP provider configuration with a single provider, one group map rule, and one group map. Use this as a starting point for basic LDAP authentication setup.

```yaml
apic:
  fabric_policies:
    aaa:
      ldap:
        providers:
          - hostname_ip: 2.2.2.2
            bind_dn: CN=testuser,OU=Employees,DC=example,DC=com
            base_dn: OU=Employees,DC=example,DC=com
            password: test@1234
            attribute: memberOf
        group_map_rules:
          - name: test-users-rules
            group_dn: CN=test-users,DC=example,DC=com
            security_domains:
              - name: all
                roles:
                  - name: admin
        group_maps:
          - name: test-users-map
            rules:
              - name: test-users-rules
```

--------------------------------

### Configure Minimal Power Policy

Source: https://netascode.cisco.com/docs/data_models/compute/intersight/organizations/policies/power_policy

This example demonstrates a minimal power policy using all default settings, including grid redundancy and no budget cap.

```yaml

compute:
  intersight:
    organizations:
      - name: MyOrganization
        policies:
          power:
            - name: default-power
```

--------------------------------

### Interface group policy replace example with device groups

Source: https://netascode.cisco.com/docs/data_models/iosxe/entity/interface_group

Shows an interface group policy example where a device uses 'interface_group_policy: replace' to override inherited interface groups. The device group PLATFORM_C9300 assigns IFG_FREE_PORT to three GigabitEthernet interfaces, but the device redefines Gi1/0/3 with IFG_TRUNK_PORT, so it gets only that group. Interfaces not redefined at the device level (like Gi1/0/1) keep the inherited groups.

```yaml
iosxe:
  interface_groups:
    - name: IFG_FREE_PORT
      configuration:
        description: "Z;FREE_PORT"
        switchport:
          mode: access
          access_vlan: 999
        shutdown: true


    - name: IFG_TRUNK_PORT
      configuration:
        switchport:
          mode: trunk
        shutdown: false
        auto_qos:
          trust_dscp: true


  device_groups:
    - name: PLATFORM_C9300
      configuration:
        interfaces:
          ethernets:
            - type: GigabitEthernet
              id: "1/0/1"
              interface_groups: [IFG_FREE_PORT]
            - type: GigabitEthernet
              id: "1/0/2"
              interface_groups: [IFG_FREE_PORT]
            - type: GigabitEthernet
              id: "1/0/3"
              interface_groups: [IFG_FREE_PORT]


  devices:
    - name: Switch-01
      host: 10.1.1.1
      device_groups: [PLATFORM_C9300]
      interface_group_policy: replace
      configuration:
        interfaces:
          ethernets:
            # Gi1/0/3 gets ONLY IFG_TRUNK_PORT (replace policy, device redefines this interface)
            - type: GigabitEthernet
              id: "1/0/3"
              interface_groups: [IFG_TRUNK_PORT]
            # Gi1/0/1 still gets IFG_FREE_PORT (not redefined at device level, so inherited groups apply)

```

--------------------------------

### VXLAN Underlay General Configuration Example

Source: https://netascode.cisco.com/docs/data_models/vxlan/underlay/underlay_general

YAML example showing the default configuration for the vxlan.underlay.general class. All properties are set to their default values as listed in the table.

```yaml
vxlan:
  underlay:
    general:
      routing_protocol: ospf
      enable_ipv6_underlay: false
      replication_mode: multicast
      manual_underlay_allocation: false
      underlay_routing_loopback_id: 0
      underlay_vtep_loopback_id: 1
      underlay_routing_protocol_tag: UNDERLAY
      intra_fabric_interface_mtu: 9216
      layer2_host_interface_mtu: 9216
      unshut_host_interfaces: true

```

--------------------------------

### Clone the example repository

Source: https://netascode.cisco.com/docs/start/vxlan/first_steps

Clones the example repository into the directory nac-vxlan. Requires git client.

```bash
git clone https://github.com/netascode/ansible-dc-vxlan-example.git nac-vxlan

```

--------------------------------

### Virtual Media Policy with NFS Mapping

Source: https://netascode.cisco.com/docs/data_models/compute/intersight/organizations/policies/virtual_media_policy

Creates a virtual media policy that mounts an OS installation ISO from an NFS share. The example defines a policy named 'os-install-media' with a mapping to an NFS file location and a tag for environment.

```yaml
compute:
  intersight:
    organizations:
      - name: MyOrganization
        policies:
          virtual_media:
            - name: os-install-media
              description: Mount RHEL 9 ISO from NFS
              mappings:
                - volume_name: rhel9-iso
                  device_type: cdd
                  mount_protocol: nfs
                  file_location: "nfs://10.0.0.10/exports/iso/rhel-9.4-x86_64-dvd.iso"
              tags:
                - key: env
                  value: prod

```
Tokens:
Raw