R12.3-2026Apr21

Before Change: Pre-verification

  1. Create a network change task on your map.

  2. Define the Planning node to request approval within the NetBrain system.

  3. Configure the Define Change node.
    1. Select the target devices for this change.
    2. Define the command.
    3. In the Rollback tab, enter the rollback commands in case you need to cancel the change.
    4. Click Append to apply the command to the target devices.

  4. Define nodes for pre-verification.
    Information
    Prerequisites:
    • Prepare a Config Change Intent to verify that the current QoS and ACL configurations match the baseline.
    • Prepare a Critical Design Intent to verify whether HTTPS (port 443) traffic is permitted.
    1. Add an intent node to verify the current QoS and ACL configurations.

      1. Add an intent node, and change its name to Pre - Verify Config Change.
      2. Select the target devices.
      3. Select the Vefiy_Config_QoS_ACL intent for this intent node.
      4. Use the Live Data in the setting.
      5. Click Run to run the intent.
      6. View the result: Success. The configuration has not been changed yet and still matches the baseline.
    2. Add an intent node to verify critical design.

      1. Add an intent node and change its name to Pre - Verify Critical Design.
      2. Select the map devices as the target devices.
      3. Select a Critical_Design_ACL intent for this intent node.
      4. Use the Live Data in the setting.
      5. Click Run to run the intent.
      6. View the intent result: Alert. ACL 193 does not allow HTTPS traffic as the design has not been implemented.
    3. Define the Benchmark Before node to retrieve data of the target devices before the network change, and to store the data for comparison after the change.

      1. Select the target devices.
      2. Add CLI command.
      3. Select a data type
      4. Click Run.
      5. Select a device to view results.

See also:



    Use Case: Triple Defense for Network Change Safety Execute Change