Add Test Case Parameters

Now that you've successfully created a Topology file, you'll add parameters to the test cases in your project to run in your specific ACI environment. Well-written test case job files will not hard-code values. Instead, they will use parameters and Topology files to run in different environments.

Step 1 - Add the parameters for Verify External Routes Learned on Border Leafs

From your project's Test Cases page:

1. Locate the test case Verify External Routes Learned on Border Leafs that has identifier 01.02
2. For this test case's row, click on the Yes link under the Job File? column




3. Click on the pencil icon in the upper right-hand corner of the Job File Preview pane to access the editor




4. Insert the parameters below into the Parameter File section of your Job File.

Warning

NOTE: You may need to scroll down to see the Parameter File section.

---
apic:
  tenants:
    - name: pod07
      l3outs:
        - name: pod07-l3out1
          vrf: pod07-vrf1
          external_endpoint_groups:
            - name: pod07-ext-epg1
              subnets:
                - prefix: 0.0.0.0/0
          expected_state:
            learned_prefixes:
              - prefix: 0.0.0.0/0
                route_type: external
                source_protocol: bgp
                administrative_distance: 20
                learned_node_ids:
                  - 1201
                  - 1202


testdata:
  global:
    apic_under_test: apic1

YAML

Copy



5. Scroll back up to the top of the Job File page and click Save

Step 2 - Return to your project's Test Cases page

Step 3 - Add the parameters for Verify Routes Advertised by ACI are Present on External L3 NXOS Device

From your project's Test Cases page:

1. Locate the test case Verify Routes Advertised by ACI are Present on External L3 NXOS Device that has identifier 01.03
2. For this test case's row, click on the Yes link under the Job File? column




3. Click on the pencil icon in the upper right-hand corner of the Job File Preview pane to access the editor




4. Insert the parameters below into the Parameter File section of your Job File.

---
apic:
  tenants:
    - name: pod07
      bridge_domains:
        - name: pod07-bd1
          vrf: pod07-vrf1
          subnets:
            - ip: 10.1.107.1/24
              public: true
          l3outs:
            - pod07-l3out1


testdata:
  global:
    apic_under_test: apic1
  verify_routes_advertised_by_aci_are_learnt_on_external_l3_nxos_device:
    node: L1
    l3_nxos_device: n9k-fanout1
    subnets:
      - tenant: pod07
        vrf: pod07-vrf1
        bridge_domain: pod07-bd1
        bd_subnet: 10.1.107.1/24
        scope: public
        l3out: pod07-l3out1
        internal_subnet: 10.1.107.0/24
        internal_ip: 10.1.107.1
        source_protocol: bgp
        external_vrf: pod07-external

YAML

Copy



5. Scroll back up to the top of the Job File page and click Save

Step 4 - Return to your project's Test Cases page

Step 5 - Add the parameters for Verify Default Gateway

From your project's Test Cases page:

1. Locate the test case Verify Default Gateway that has identifier 01.04
2. For this test case's row, click on the Yes link under the Job File? column




3. Click on the pencil icon in the upper right-hand corner of the Job File Preview pane to access the editor




4. Insert the parameters below into the Parameter File section of your Job File.

---
apic:
  tenants:
    - name: pod07
      bridge_domains:
        - name: pod07-bd1
          subnets:
            - ip: 10.1.107.1/24
              public: true
          l3outs:
            - pod07-l3out1
      l3outs:
        - name: pod07-l3out1
          vrf: pod07-vrf1
          external_endpoint_groups:
            - name: pod07-ext-epg1
              subnets:
                - prefix: 0.0.0.0/0
              contracts:
                consumers:
                  - pod07-contract1
      application_profiles:
        - name: pod07-ap1
          endpoint_groups:
            - name: pod07-epg1
              bridge_domain: pod07-bd1
              contracts:
                providers:
                  - pod07-contract1


testdata:
  global:
    apic_under_test: apic1
  verify_default_gateway:
    device: n9k-fanout1
    device_vrf: pod07-external
    node: L1
    l3outs:
      - next_hop: [192.168.107.1, 192.168.107.3]
        host_ip: 10.1.107.1
        endpoint_group: pod07-epg1
        application_profile: pod07-ap1
        tenant: pod07
        contract: pod07-contract1
        bridge_domain: pod07-bd1
        bd_subnet: 10.1.107.1/24
        scope: public
        l3out: pod07-l3out1
        vrf: pod07-vrf1
        l3out_prefix: 0.0.0.0/0
        external_epg: pod07-ext-epg1
        external_epg_contract: pod07-contract1

YAML

Copy



5. Scroll back up to the top of the Job File page and click Save

Step 6 - Return to your project's Test Cases page

Step 7 - Add the parameters for Verify Port Failure and Recovery Convergence

From your project's Test Cases page:

1. Locate the test case Verify Port Failure and Recovery Convergence that has identifier 01.05
2. For this test case's row, click on the Yes link under the Job File? column




3. Click on the pencil icon in the upper right-hand corner of the Job File Preview pane to access the editor




4. Insert the parameters below into the Parameter File section of your Job File.

FANOUT: n9k-fanout1

spirent_config_file: /tmp/LABATO-2205-user07.xml

streamblocks:
  - pod07_1107-107
  - pod07_107-1107

INTERFACE: 1/33

EXPECTED_FAILURE_CONVERGENCE: 50
EXPECTED_RECOVERY_CONVERGENCE: 1

FAILURE_EVENT_FILE_NAME: vPC-Member-Link-Failure.csv
RECOVERY_EVENT_FILE_NAME: vPC-Member-Link-Recovery.csv

YAML

Copy



5. Scroll back up to the top of the Job File page and click Save

Step 8 - Return to your project's Test Cases page

Continue to the next section to create the Job File and parameters for the last test case in your project.