DESIGNER TOOLS
Help Center User GuideGetting StartedFAQRelease Notes
 
X
User Guide
Getting Started
FAQ
Release Notes
Contents  

Designing Templates with a YANG Configuration

You can design a configuration template either by using your own YANG model or by using the YANG model generated by the Configuration Designer. The Configuration Designer provides a wizard that takes you through a step-by-step procedure to create a configuration template. You can design multiple templates by creating requests and launching respective wizards from them.

To design a template using your own data model, make sure to have your data model schema and Jinja (a template engine for Python) template content ready.

Before You Begin

Before you begin, create a configuration template request. See Creating Requests for Configuration Templates.

Procedure

To design a configuration template with your own YANG model:

  1. From the Configuration Template Request drop-down list, select Begin with YANG.

    The Enter YANG Schema page appears.

  2. Enter or copy and paste your YANG schema in the space provided for it. Click Next.

    The Enter Jinja Template page is displayed.

  3. Enter or copy and paste your Jinja template content in the space provided for it. Click Next.

    Note You can also download a sample template from this page.

    Note  When you paste the Jinja template, the Configuration Designer detects the keywords post_config, pre_config, and diff_config automatically. If the configuration template contains any one of these three keywords, the template will enable the Diff Config feature.

  4. Click Next.

    The Generate UI page appears and generates a UI page based on your YANG schema and displays a read-only view. The fields on this page map to the parameters in the configuration template. You can drag and drop the field labels to reorder the UI.

    Note If you edit an existing template and change its data model, then you can generate a new UI for it by clicking Re-generate ui. If you do not want a new UI, skip to the next step.

  5. Click Next.

    The Validate Template page appears.

  6. Enter values that you want to validate. See Table 7 for sample fields and their descriptions. Click Validate.

    A configuration template is generated using the values that you entered.

  7. In the Validate Template page, make sure your data in the template is complete and correct.
  8. Click Yes, it looks good to close the page. If any parameter value in the configuration template needs to be changed, click No, it needs change to return to the previous page.
  9. Click Next.

    The Review Template page is displayed. It contains three tabs—Jinja Template, Data Model, and View Def. You can click through the tabs to view and update your Jinja template, data model, and view definition.

  10. Click Done to save your configuration template.

The Designs page is updated with the new configuration template and its status shows as Validated. You can monitor and manage the new configuration template from the Configuration Design page.

Note You need to publish the configuration template for it to be available for the Resource Designer to create virtualized network function (VNF) packages. See Publishing Configuration Templates.

Table 7: Sample Fields on the Validate Template Page

Field

Description

Name Servers

Specify the fully qualified domain names (FQDNs) or IP addresses of one or more DNS name servers.

Example: 10.0.2.15

NTP Servers

Specify the FQDNs or IP addresses of one or more NTP servers.

Example: ntp.example.net

Time Zone

Specify the time zone for your virtual machine.

Example: UTC

Enable Default Screens

For a centralized deployment, select True to enable the default screens security profile for the destination zone or False to disable default screening.

Example: False

Note: You cannot configure this setting for a distributed deployment.

Enable Re-filter

Select True to enable a stateless firewall filter that protects the Routing Engine from denial-of-service (DoS) attacks or False to allow DoS attacks.

Example: True

Loopback Addr

Specify an IPv4 or IPv6 loopback address for the management interface of your virtual machine.

Example: 192.0.2.25

Hostname

For a centralized deployment, specify the hostname of your virtual machine that contains the vSRX VNF. The hostname has no limit on the number of characters and accepts letters, numbers, and symbols.

Example: vm-vsrx

Note: For a distributed deployment, the vSRX application resides on the NFX250 device, and you cannot configure this setting.

Syslog Servers

Specify the FQDNs or IP addresses of one or more system log servers.

Example: 192.0.2.55

Right Interface

Specify the identifier of the interface receiving data transmitted by the host.

Example: GigabitEthernet3

Left Interface

Specify the identifier of the interface that transmits data to the host.

Example: GigabitEthernet2

Allowed Prefix List

Ping Prefix List

If you set the Enable Re-filter field to True, specify the routes that the Junos Space Virtual Appliance uses for ping operations when it discovers the vSRX VNF.

Example: 10.0.2.1/24

SNMP Prefix list

If you set the Enable Re-filter field to True, specify the routes that the Junos Space Virtual Appliance uses for SNMP operations when it discovers the vSRX VNF.

Example: 10.0.2.0/24

Space Servers

If you set the Enable Re-filter field to True, specify the IP addresses of the virtual machines that contain the Junos Space Virtual Appliances.

Example: 10.0.2.50

Related Documentation

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit