Use the master configuration template 编辑

Using a master configuration template is a flexible option for creating and deploying a master configuration on multiple Citrix ADC instances.

As an administrator, you might want to make configuration changes and save licenses, certificates, and other files on the ADC instance. You can save the new configuration as a master configuration template (.conf file).

To save your master configuration template from a an ADC instance, you can do one of the following:

• At the command prompt, enter save ns config. The configuration is saved in the instance’s FLASH memory in the /nsconfig/ns.conf file.

• From the instance’s GUI, navigate to Diagnostics > View Configuration. Choose the kind of configuration you’d like to save. For example, if you want to save the saved configuration of your instance, select Saved configuration.  Click the Save text to a file link to save the ‘ns.conf’ file to your local machine.

When you deploy the master configuration template by using the ‘DeployMasterConfiguration’ configuration template while creating a new job, you can customize it further for each specific ADC instance by adding additional commands, modifying existing commands, and providing different variable values in the input file.

For example, as an administrator you may want to upload certificate keys to your ADC instances in addition ns.conf file and deploy the master configuration on them as well.

Important

You cannot execute a configuration job using the DeployMasterConfiguration template on Citrix ADC CPX instances, instances configured in a cluster, or on partitioned ADC instances.

To create a configuration job using the Master Config configuration template on Citrix ADM:

1. In Citrix ADM, navigate to Networks > Configuration Jobs, and then click Create Job.

2. On the Create Job page, on the Select Configuration tab, specify the Job Name and select the Instance Type from the drop-down list.

3. Select Master Configuration from the Configuration Source drop-down list. Drag and drop the DeployMasterConfiguration template’s commands to the right pane. You can add, modify, or delete commands in the right pane as well. Click Next.

   Note

   You can add put commands to add input files to your template. In our example, we will need to upload certificate and key files in addition to the configuration template file and variable input files.

   

4. You can review all the variables that you have defined while creating or editing a configuration job in a single consolidated view.

5. Do one of the following to view all the variables in a single consolidated view:

   • While creating a configuration job, navigate to Networks > Configuration Jobs, select Create Job. On the Create Job page, you can review all the variables that you have added while creating the configuration job.

   • While editing a configuration job, navigate to Network > Configuration Jobs, select the Job Name and click Edit. On the Configure Job page, you can review all the variables that were added while creating the configuration job.

6. You can then click on the Preview Variables tab to preview the variables in a single consolidated view that you have defined while creating or editing a configuration job.

   

7. A new pop-up window appears and displays all the parameters of variables such as Name, Display Name, Type, and default value in a tabular format. You can also edit and modify these parameters. Click the Done button after you have edited or modified any of the parameters.

   

8. Select the instances on which you want to run the configuration job, and then click Next.

9. On the Specify Variable Values tab, upload the following:

   • Configuration Template File (.conf) - Upload the .conf file that you extracted from an ADC instance.

   • Upload the Input File (.xml/csv) - Upload the input file with values for the variables you have defined in your commands.

   A sample xml file is provided here for your usage. Ensure that the xml files contain the details corresponding to the ADC instances that you are using.

   
   <?xml version="1.0" encoding="UTF-8" ?>
   
   <properties>
   
   <!-- 
   
   Provide inputs for all the parameters defined in the master config file.
   
   -  global. This tag contains all the common parameters and value.
   
   -  devicegroup. This tag contains all the instance group specific parameters and values.
   
   If the same parameters are defined in global and instance tags, the instance specific parameters value will take precedence over the instance group. The instance group specific parameters value will take precedence over global parameters in the execution.	        
   
   -  name. This attribute represents the name of the instance group.
   
   -  device. This tag contains all the instance specific parameters and value. 
   
   If the same parameters are defined in global and instance tags, the instance specific parameters value will take precedence in the execution.
   
   -  name. This attribute represents the IP Address of the instance. Host name is not supported for the attibute.
   
   HA pair should be represented as <primaryip>-<secondaryip>. Example 10.102.2.1-10.102.2.2
   
   In the template file, the parameter name must be specified within the dollar sign,Example: $NSIP$, $CC_Trap_Dest$ and parameters names are case sensitive.
   -->
   
   <global>
   
   </global>
   <devicegroup name="BLR_DEVS">
   </devicegroup>
   <device name="10.106.101.209">
   <param name="IP" value="10.106.101.209"/>
   </device>
   
   <!-- HA PAIR-->
   <!--<device name="10.102.43.154-10.102.43.155">
   <param name="NSIP" value="10.102.43.154"/>
   <param name="HostName" value="NS43HA"/>
   <param name="LBSERVER" value="haserver43http"/>
   <param name="SNMPTrapDest" value="10.102.43.130"/>
   </device>-->
   </properties>
   
   <!--NeedCopy-->