Define Golden Intent

Start with Feature and Extend with Device Role

By default, an empty feature node is displayed. To proceed:

1. Open the Golden Engineering Studio and go to Golden Intent > Staging.
2. From the Golden Intent manager pane (left side pane), open the drop down menu of a folder and select New Golden Intent.



3. Rename the default name of the golden intent as per your use case (eg: Monitor Failover State).
4. An empty feature node will appear in flowchart pane to begin the golden intent, click icon. 
5. Select a feature for the current empty node.



6. Next, select the device roles defined in this feature and it will be applied to the current golden intent.
7. Click OK to save and close the window.

Extend Device Role with Parser/Golden Config Check/ Neighbor Device

From the device role node, you can extend the following actions:

1. Parser
2. Golden Config Check
3. Neighbor Device

1. Parser

   Choose the action type Parser to retrieve the command data and variables as follows:

   1. Select the Parser as the action type and the matched parsers will be listed.
   2. Select a visual parser to retrieve the command data and variables for analysis.
      
      
   3. Click OK to save and close the window.
   4. You can define more settings of the data in the property pane, such as:
      1. Define the Macro Variable and assign value to it (if the macro variable exists).
      2. Customize the parser from Edit option.
      3. Add a new column to the parser table with a customized variable using +Add Formula column.
         
         
         

   In addition, all the parser variables will be available in the subsequent diagnosis nodes.

2. Golden Config Check

   You can also extend the Golden Config Check node from the device role node.

   1. Select the action type as Golden Config Check.
   2. Select a golden config rule to check, eg: Failover rule.
      
      
      

3. Neighbor Device

   The device role defined in the feature are independent of each other and have no network relationship. You can extend neighbor devices from the device role node as follows:

   

   1. Select the action type as Neighbor Device.
   2. Related Device by: Determine one of the following ways to extend the neighbor device:
      • IPv4 L3 Neighbor/IPv6 L3 Neighbor/L2 Neighbor: You can extend all the neighbor devices based on topology and no additional configuration is required.
      • Command Table: Refer to the table variables parsed from CLI commands. You can define formula columns for command table.
      • Golden Neighbor: This can be chosen to dynamically find neighbors depending on the structure of the golden table. Specify a golden neighbor table.
   3. Filter Neighbor Device: Define the table column in the current device table match with Neighbor (when Golden Neighbor is selected).
   4. From the property pane, define Formula Columns in Command Table:
      1. Click icon in the Neighbor Device node to view the current command table structure, it provides an entry to +Add Formula Column.
      2. Click +Add Formula Column, a dialog Add Formula Column will pop up. The available variables are limited to the current table columns.

   Note:The newly added formula column can be deleted or edited, but it can be used only in the subsequent nodes.

Extend Parser node with Compound Table

You can also add the Compound Table nodes from the golden parser node. The compound table supports four types of nodes:

1. Merge Table
2. Sub Table
3. Append Table
4. Neighbor Join

1. Merge Table

   The merge table node merges multiple command tables using specific keys.

   

   1. Table Operator: Select Merge Table from the drop down menu.
   2. Source Tables: Choose from multiple parsers under the same device role, or between the current and parent device roles. But they cannot be different feature device roles.
      
      • The scope of the source table 1 is all table variables of the triggered parser or the compound table itself, and
      • The scope of the source table 2 can be all table variables of the triggered parser, as well as compound tables of all parsers under the current device role.
        
   3. Add paired keys: Define the paired keys from each table.
   4. Add a name to the merged table.
   5. Go to Advanced Settings and define a rule to display the columns in merging table: 
      • Full Join: Returns all rows when there is a match in left (Table 1) or right (Table 2) table rows.
      • Inner Join: Returns all rows that have matching values in both tables.
      • Left Join: Returns all rows from the left table (Table 1), and the matching rows from the right table (Table 2).
   6. Click OK to save and close the window.

   

2. Sub Table

   This node will be used to obtain a subset table from the selected table by filtering with a condition. And the derived sub table will be used for subsequent diagnosis.

   

   1. Source Table: The scope is all table variables of the triggered parser, or the compound table itself.
   2. Filtering Logic: Select a logic either to keep certain rows or remove all rows when a value matches the defined Condition.
   3. Condition: Define the logic using the boolean expression.
      
      • Table Column: Select a column of the current source table.
      • Manual Input: Enter the variables manually.
   4. Add a name to the sub table.

3. Append Table

   This node is used to select two tables and merge their data according to the specified rules.

   1. Select Source Table 1: The scope is triggered parser, or the compound table itself.
   2. Select Source Table 2: The scope can be all variables of the triggered parser table or the compound tables under the current device role.
   3. (Optional) You can click Add Mappings to define more column mappings between the two source tables.
   4. Click Advanced Settings to select the columns to keep in the generated appended table.
   5. Add a name to the Append table.

   

   
   

4. Neighbor Join
   
   The join table node is used to merge two parser tables and one global neighbor table based on the specified mapping rules. Merging can occur between multiple parsers under the same device role, or between the current device role and the parent device role, but not between different feature device roles.
   

   Note: Neighbor Join is only supported for parsers extended by the neighbor device role.

   
   
   1. Select the action type as a compound table.
   2. Select table operation type.
   3. Define the logic for neighbor join.

The variable scope of the neighbor and source tables are as follows:

• Neighbor Table: The scope is all table variables of the triggered parser, or the compound table itself. In addition, the neighbor table extended by the current neighbor device node can also be used.
• Source Table1: The scope is all table variables of the triggered parser, or the compound table itself.
• Source Table2: The scope can be all table variables of the triggered parser, as well as the table variables and compound tables of all parsers under the device role to which the current parser belongs.

When the command table is used to expand neighbors, If the generated neighbor table does not contain a column named 'this_device,' a 'this_device' column will be created automatically, using the device from the command table as 'this_device’; if a column named 'this_device' already exists, it will not be generated.

Extend More Actions

You can add an external intent or a follow-up diagnosis from .  Select an NIT and device role and the system will generate a device section and a device diagnosis for all devices in the selected device role.

1. Select External Intent / Follow-up Diagnosis from to open the configuring dialogue.
2. Rename the node name as per use case.
3. Select the Primary/Secondary device role to add the external intent.
4. Select an Intent Template.
5. Click OK to save and close the window.

If the selected NIT has macro variables, assign values to the macro variables. If you are assigning values using ADT, then set the device key for ADT.