Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Creating and Managing Fusion Configuration Templates

Large campus might have many similar network topology instances. These instances can be Layer 3 Fabrics, or Junos Fusion Enterprise. Creating each of these instances afresh can be tedious, time-consuming, and error-prone.

Network Director enables you to create a configuration template for a Junos Fusion Fabric and reuse it in all similar instances. A configuration template combines the common settings that apply to an instance, such as the chassis details, ports to be used as cascade and cluster ports, software image for the satellite devices, and so on. However, you might still specify some additional configuration attributes while applying the template to a fabric or Junos Fusion setup.

Before you create a configuration template:

  • Understand the software requirements for the aggregation devices and the satellite devices. For more information, see Software Requirements for Junos Fusion.

  • Ensure that the software images for the aggregation devices and the satellite devices are uploaded to Network Director using the Image Management > Manage Image Repository in the Deploy mode.

You can perform the following tasks from the Manage Fusion Configuration Templates page.

Create a Configuration Template for Junos Fusion Enterprise

To create a Junos Fusion Enterprise configuration template:

  1. Under Views, select one of these options: Logical View, Location View, Device View, or Custom Group View.
    Tip:

    Do not select Dashboard View or Topology View.

  2. Click in the Network Director banner.
  3. From the Tasks menu, select Network Builder > Manage Fusion Config. Templates.

    The Manage Fusion Configuration Templates page opens.

  4. Click Create.

    The Create Fusion Configuration Template wizard opens.

  5. In the Template Type page of the Create Fusion Configuration Template wizard, select the type of deployment for which you want to create the template. Select Campus to create a template for Junos Fusion Enterprise.
  6. Select one of the following depending on the type of Junos Fusion topology:
    • Fusion Enterprise Single Aggregation Device—Indicates that the one or more satellite devices are connected to a single aggregation device.

    • Fusion Enterprise Multiple Aggregation Devices—Indicates that each satellite device is connected to two aggregation devices forming an MC-LAG cluster at the aggregation layer.

  7. For a Junos Fusion Enterprise, select one of the following depending on the type of Junos Fusion topology:
    • Fusion Enterprise Single Aggregation Device—Indicates that the one or more satellite devices are connected to a single aggregation device.

    • Fusion Enterprise Multiple Aggregation Devices—Indicates that each satellite device is connected to two aggregation devices forming an MC-LAG cluster at the aggregation layer.

  8. Click + in the Available Satellite Images box to ensure that the appropriate satellite software image is available.

    Network Director lists the satellite software image only if you have uploaded the software image in Network Director Image Repository.

  9. Click Next.

    The Settings page opens.

  10. Enter a name for the configuration template.

    If you chose to configure with multiple aggregation devices, the Settings page displays two tabs—Aggregation Device 1 and Aggregation Device 2.

  11. In the Aggregation Device 1 tab, select the device model that you want to use as the aggregation device.

    Network Director supports the following as aggregation devices:

    • EX9204, EX9208, and EX9214 in a Junos Fusion Enterprise setup.

    Note:

    In a Fusion Enterprise Multiple Aggregation Device topology, when you select a device as the first aggregation device, Network Director considers the second aggregation device also to be of the same device model.

  12. When you select a device model in a Junos Fusion Enterprise setup, you need to create a new chassis for the aggregation device model that you selected.

    To create a new chassis:

    1. Click Build New Chassis.

      The Build Chassis window opens. The Build Chassis window has two panes—the Available line cards pane and the Chassis: FPC slots pane.

      The Available line cards pane lists the all the EX9200 line card models and the Chassis: FPC slots pane lists the available FPC slots on the device.

      Note:

      Network Director does not allow you to import chassis details. You must create a chassis for each configuration template irrespective of whether the template is for a single-home or a multihome Junos Fusion topology.

    2. Drag and drop the line cards that you want to add to the chassis from the Available line cards pane to the appropriate FPC slots in the Chassis: FPC slots pane.

      From all the EX9200 line cards that are listed in the Available Line Card list, select at least one line card that is supports the cascade port. If you do not choose any line card that is supported by cascade port, Network Director returns an error message that prompts you to select a line card that is supported by cascade port.

    3. Click Set after you have added all the required line cards to the FPC slots.

      The Build Chassis window closes.

      After you setup the chassis, the line cards that support the cascade ports are listed in the Select Cascade Ports window. All the other line cards are filtered out. For the list of EX9200 line cards that support cascade ports see, Line Cards on EX9200 Switch Cascade Port Support.

    4. Mouse over Preview to preview the chassis with the line cards that you added.
  13. A cascade port is a port on an aggregation device that sends and receives control and network traffic from an attached satellite device. Click Select Cascade Ports and perform the following steps to select cascade ports for the Junos Fusion Enterprise:
    1. To select ports individually from the ports list, click Identify Port > By List or to select ports by specifying a range, click Identify Port > By Range. The Select Ports window opens.
      Note:

      In the Select Ports window, Network Director displays only the Gigabit Ethernet interfaces, 10-Gigabit Ethernet interfaces, and the 40-Gigabit Ethernet interfaces as these are the recommended interfaces for a cascade port.

    2. If you want to select ports individually, select the ports that you want to use as cascade ports on each FPC. Use the left navigation pane to view and select the ports on each FPC slot.
    3. If you want to select ports using a port range, specify the starting and ending port ID.
    4. Click Add.

      Network Director adds the selected ports or the ports that are available on the FPC from the range that you specified, to the list of cascade ports in the Create Template page.

    5. Select a cascade port and optionally, you can enter the corresponding FPC slot ID of the satellite device.

      Specify the FPC slot ID in the range 65-254.

      Note:

      When you add a satellite-enabled device in a Junos Fusion setup, Network Director checks for the FPC slot ID that you specify and uses this ID while Network Director configures the satellite devices. If you have not provided an FPC slot ID, Network Director automatically generates the FPC slot ID for satellite device from the allowed range and provisions the same on the aggregation device.

  14. For a Fusion Enterprise Multiple Aggregation Device topology, you must select the port type as an ICL Port to configure an Inter-Chasis Link (ICL port). However, it is optional to select the ICCP PORT as the port type to configure an Inter-Chassis Control Protocol (ICCP) port. Select the ICCP PORT as the port type, to manually configure the ICCP port. If you do not select the ICCP PORT as the port type, Junos platform automatically assigns one of the ports as an ICCP port and deploys all the necessary configurations to the port. At the time of applying the template to one or more aggregation devices, the ICCP configuration is pushed to the aggregation devices.
    Note:

    Automatic ICCP provisioning is enabled by default and if you manually configure an ICCP parameter that is normally set by default, your configuration automatically overrides the default parameter. If you decide to configure ICCP, you must configure matching configurations on both the aggregation devices.

    An ICL port is used to forward data traffic across the aggregation devices. This link provides redundancy when a link failure occurs in one of the active links.

    An ICCP port is used to exchange the control information between two aggregation devices to ensure that data traffic is forwarded properly.

    Click Select ICL & ICCP Ports and perform the following steps to select the ports:

    1. To select ports individually from the ports list, click Identify Port > By List or to select ports by specifying a range, click Identify Port > By Range. The Select Ports window opens.
    2. If you want to select ports individually, select the ports that you want to use as ICL ports on each FPC. Use the left navigation pane to view and select the ports on each FPC slot.
    3. If you want to select ports using a port range, specify the starting and ending port ID.
    4. Click Add. Network Director adds the selected ports or the ports that are available on the FPC from the range that you specified, to the list of ICL ports in the Create Template page.
    5. For a Junos Fusion Enterprise, specify the port type as ICL port or ICCP port depending on the port usage.

      In Select ICL & ICCP window, you can select more than one ICL and ICCP port as a LAG interface. The LAG interface provides redundancy and load balancing between the two aggregation devices.

      When you select an ICL port as the LAG interface, there is no additional configuration required for the LAG on the selected ICL port. Network Director generates a default configuration for the aggregation devices. This configuration is pushed to the aggregation device at the time of link up event when the connection between the aggregation devices on the ICL interfaces are made.

      When you select an ICCP port as the LAG interface, you must specify the local IP address of the ICCP port. For information on specifying the ICCP local address, see Apply Configuration Template to Devices. If you do not select the ICCP port, Network Director automatically configures the ICCP port to establish ICCP session between the connected aggregated devices.

      Note:

      If ICL or ICCP physical connections are not made between aggregation devices when you apply the template to aggregation devices, Network Director displays the each aggregation device as separate single home Junos Fusion fabrics. When the ICL and ICCP connections between aggregation devices are established, a link up is triggered. Network Director deletes the device, rediscovers the device, and converts the Junos Fusion to a multihome fabric.

  15. If the Junos Fusion Enterprise uses a satellite cluster, you must select the ports on satellite devices that will act as cluster ports. In a satellite cluster, up to 10 satellite devices can be interconnected using the standard 10-Gigabit Ethernet or 40-Gigabit Ethernet interfaces to form a cluster, which in turn can be connected to the aggregation devices over a pair of fiber uplinks. In a cluster, all the satellite devices do not need to be directly connected to the aggregation device. One or two satellite devices in a satellite cluster connects to the aggregation device through cluster ports.

    Click Select Satellite Cluster Ports to select the cluster ports that the satellite devices use to connect to other satellite devices in a satellite cluster. Perform the following steps to add cluster ports:

    Note:

    If you have multiple satellite devices that connect to one or more aggregation devices, the ports that you select in is applied to all the directly connected satellite devices that are part of the cluster.

    1. To select ports individually from the ports list, click Identify Port > By List or to select ports by specifying a range, click Identify Port > By Range. The Select Ports window opens.
    2. Select the device model of the satellite device.
    3. If you want to select ports individually, select the ports that you want to use as cluster ports on the selected satellite device.
    4. If you want to select ports using a port range, specify the starting and ending port ID.
    5. Click Add. Network Director adds the selected ports that you specified or the ports that are available on the device from the range that you specified, to the list of cluster ports in the Create Template page.
  16. Select the software image that you want to install on all the satellite devices from the Satellite Image list. The supported satellite image version is satellite-3.1R1.3. For more information about software images in Junos Fusion, see Software Requirements for Junos Fusion.
  17. For a Fusion Enterprise Multiple Aggregation Device topology, click the Aggregation Device 2 tab.

    Network Director copies the same settings that you specified for the first aggregation device for the second aggregation device. Review the settings.

    If you want to modify the setting including the device model, click Edit. Select a device model and follow steps Step 7 through Step 15 to specify details for the second aggregation device.

  18. Click Next to review the template details.
  19. After you have reviewed the details, click Finish. Network Director creates the template and displays it in the Manage Fusion Configuration Templates page.

Clone a Configuration Template

You can make a copy of an existing template by cloning the template. When you clone a template, Network Director copies all the settings to the cloned template. However, you can modify the settings in the cloned template based on your requirements.

To clone a Junos Fusion Enterprise:

  1. Select the template that you want to clone and click Clone.

    The Clone Fusion Configuration Template page opens.

  2. Network Director copies all the settings in the original template to the cloned template. However, you can modify all the settings in the cloned template as per your requirement. Follow step 6 through 16 in the Create a Configuration Template for Junos Fusion Enterprise for instructions on specifying settings for the configuration template.

Apply Configuration Template to Devices

If you plan to apply the template to a managed device, make sure that the device runs the Junos OS software image that is supported on Junos Fusion systems. For detailed steps on installing or upgrading software image using Network Director, see Managing Software Images. See Network Director release notes to know the Junos OS software version that is supported for Junos Fusion systems.

After you have created a configuration template, you can apply the template to aggregation devices. You can apply the template to aggregation devices that are already managed by Network Director or new aggregation devices.

To apply a configuration template to Junos Fusion Enterprise:

  1. From the Manage Fusion Configuration Template page, select the template that you want to apply to an aggregation device.
  2. Do one of the following:
    • If the aggregation device is not managed by Network Director, click Apply and select Unmanaged Devices. The Apply Fusion Configuration Template page opens.

    • If the aggregation device is already managed by Network Director, but is not part of a fusion fabric, click Apply and select Managed Devices. The Apply Fusion Configuration Template page opens.

      Skip to Step 4 and follow the instructions to apply the template to managed devices.

  3. If you selected to apply the template to Unmanaged devices, perform the following steps to specify details about the aggregation devices:
    1. In the Apply Fusion Configuration Template page, specify the DHCP server settings by following the descriptions given in Table 1.
      Table 1: DHCP Server Settings

      Field

      Description

      DHCP Server

      IP address or the hostname of the DHCP server.

      DHCP Server Type

      The type of DHCP server that provides the necessary information to the aggregation devices. You can choose to use a CentOS DHCP server, an Ubuntu DHCP server, or any other DHCP server.

      Note:

      If you select Other, you must configure the DHCP server settings manually.

      Manually Configure Server

      Select to indicate that you want to manually configure the DHCP server. You can configure the CentOS and Ubuntu DHCP servers manually or from Network Director.

      If you want to use any other type of DHCP server, do the following:

      1. Select the Manually Configure Server check box. Network Director hides all the other details except the DHCP Server Type.

      2. Follow the instructions displayed in this box to configure the DHCP server manually.

      DHCP User

      Username to log in to the DHCP server.

      DHCP Password

      Password for the specified username.

      Confirm Password

      Confirm the DHCP server password.

    2. Specify the File server settings described in Table 2.
      Table 2: File Server Settings

      Field

      Description

      File Server Type

      The type of file server where the software image to be installed on the aggregation device is to be stored. You can choose to use an FTP, HTTP, or an TFTP file server.

      File Server

      IP address or hostname of the file server.

      File Server Root Directory

      The root directory of the file server.

    3. Select the software image that you want to install on the aggregation device from AD Image.
      Note:

      Ensure that the software image is uploaded to Network Director using the Image Management > Manage Image Repository in the Deploy mode. If the software image is not uploaded, Network Director does not display the software image in this field.

    4. ZTP process maps the management interface MAC address or the device chassis serial number of each aggregation device to the software image, IP address, hostname, and the configuration file stored on the file server. This mapping is stored in the DHCP server. When an aggregation device starts up, the device contacts the DHCP server to obtain the IP address and the software image location. The DHCP server looks up in its MAC address or serial number mapping database to identify the device and provide details about the file server that the device must contact to get the software image and configuration file. The device uses this information to contact the file server and obtain the software image and the configuration file for deploying on the device.

      Click Add to add a row to the Device Details table. You specify the aggregation device details in the Device Details table. You can enter the device details manually or you can specify the details in a CSV file and import it.

    5. Do the following to import the device details from a CSV file:
      Note:

      When you use the Import option, you must specify either the MAC address or the Serial number, but not both.

      1. Click Import > By Mgmt MAC addresses to import the MAC addresses of aggregation devices in CSV format. You must enter the MAC addresses in the specified format. Click CSV Sample to download a sample CSV file that you can use to import MAC addresses.

      2. Click Import > By Device Serial Numbers to import the serial numbers of aggregation devices in CSV format. You must enter the serial numbers in the specified format. Click CSV Sample to download a sample CSV file that you can use to import serial numbers.

    6. If you want to specify a password for all the aggregation devices that you add to this fusion fabric, click Set Default Password. The Set Default Password window opens.

      Enter the password, confirm the password and click Set to set the password as the default password for all the aggregation devices that you add to this fusion fabric.

      You can skip this step if you wish to specify the password individually or if you want to use a different password for each of your aggregation device.

    7. Do the following to specify details about the aggregation device manually:
      1. Network Director assigns a host name for the aggregation device. You can modify this name by clicking .

      2. Enter the IP address of the management interface or the MAC address and the device chassis serial number of the aggregation device.

      3. If you are applying the template to a multihome Junos Fusion that has two aggregation devices, enter the ICCP IP address that this device uses to connect to the second aggregation device. If you are applying the template to a single-home Junos Fusion, you can leave this field blank.

      4. Enter the MAC address of the management interface (for example, the em0 interface) or the device chassis serial number of the aggregation device in the MAC Addresses or Serial Number field.

      5. Click Import MAC Address to import the MAC addresses of aggregation devices in CSV format. You must enter the MAC addresses in the specified format. Click CSV Sample to download a sample CSV file that you can use to import MAC addresses.

        Note:

        When you use the Import option, you must specify either the MAC address or the Serial number, but not both.

      6. Click Import Serial Number to import the serial numbers of the aggregation device in CSV format. You must enter the MAC addresses in the specified format. Click CSV Sample to download a sample CSV file that you can use to import serial numbers.

    8. Type the local IP address for the ICCP port. The IP address is used to communicate to the peers that hosts an ICCP port as a LAG interface.
      Note:

      This field is available only when you choose to configure the ICCP port manually for a Junos Fusion Enterprise device.


    9. Click the text link in the Password column to set or modify the password for the aggregation device.

      • If you have not configured a default password for the aggregation device, then click Set Password. The Set Custom Password window opens. Specify the password, confirm the password, and click Set.

      • If you want to override the default password and specify a custom password for the aggregation device, then click Edit. The Edit Custom Password window opens. Select Use Default Password if you want to use the default password.

        Select Edit Custom if you want to specify a different password for the aggregation device. Specify the password, confirm the password, and click Set.

    10. To view the configuration that Network Director deploys on the aggregation device, click View in the Config field.

    11. Repeat above steps, Step d through Step j to add another aggregation device.
  4. If you selected to apply the template to Managed devices, perform these steps:
    1. Select the devices that you want to add as aggregation device from the Select Managed Devices table.
    2. Click on the link in the Backup Config column.

      Network Director creates a ZIP archive file containing the existing configuration of the device. You save a copy of this onto your local machine.

    Note:

    Before you perform this step, make sure that the device is running a Junos OS software image that is supported on Junos Fusion systems. If not, you must upgrade the software image before you proceed. For detailed steps on installing or upgrading software image using Network Director, see Managing Software Images.

  5. Click Apply.

    Network Director converts the device to a fusion fabric aggregation device and deploys all the necessary configurations on the device and opens the Manage Fusion Fabrics page.

    Manage Fusion Fabrics page displays the status and details of all fusion fabrics that are created using Network Director.

    After the template is applied successfully to a Junos Fusion fabric, there are quite a few tasks that Network Director performs internally that makes building your Junos Fusion fabric simple and error-free. Network Director converts the device that you specified in the Apply Template workflow to an aggregation device and applies the port settings on the various ports that you specified in the configuration template. When an EX4300 device is connected to one of the configured cascade ports, a link up event is triggered. The link up event initiates a syslog message to Network Director and Network Director initiates a topology refresh job. Network Director then installs the appropriate satellite software on the satellite device and performs the necessary configurations. If a second satellite device is connected to the first satellite device to form a satellite cluster, or another satellite device is connected to the aggregation device, another link up event is triggered and the same steps are repeated. This process continues for all additional satellite devices that are connected to the aggregation device.

    Note:

    If ICL or ICCP physical connections are not made between aggregation devices when you apply the template to aggregation devices, Network Director displays the each aggregation device as separate single home Junos Fusion fabrics. When the ICL and ICCP connections between aggregation devices are established, a link up is triggered. Network Director deletes the device, rediscovers the device, and converts the Junos Fusion to a multihome fabric.

For Junos Fusion Enterprise, if you want to form a cluster setup and if the cascade port of the Aggregate device is connected to the base port (1 GE) of EX2300, EX3400, or EX4300 devices, you need to configure the cluster-policy manually by logging into the aggregation device. Execute the following commands to configure the cluster policy:

  • If the satellite device is part of a cluster, log in to the CLI of the aggregation device and execute the following commands:

user@aggregation-device# set groups policy-number policy-options satellite-policies port-group-alias port-group-alias-name pic pic-identifier port port-ID1

user@aggregation-device# set groups policy-number policy-options satellite-policies port-group-alias port-group-alias-name pic pic-identifier port port-ID2

user@aggregation-device# set groups policy-number policy-options satellite-policies port-group-alias port-group-alias-name pic pic-identifier port port-ID3

user@aggregation-device# set groups policy-number policy-options satellite-policies port-group-alias port-group-alias-name pic pic-identifier port port-ID4

user@aggregation-device# set groups policy-number policy-options satellite-policies port-group-alias port-group-alias-name set groups policy-number policy-options satellite-policies candidate-uplink-port-policy cluster-policy-name uplink-port-group pic-identifier

user@aggregation-device#set apply-groups policy-number

user@aggregation-device# set chassis satellite-management cluster cluster-number cluster-policy cluster-policy-name

View Details about a Configuration Template

To view details about a configuration template, select the template and click Details.

The Template Details for <template-name> window opens.

For a Junos Fusion Enterprise setup, the Template Details for <template-name> page displays the template name, deployment type, configuration type, software upgrade group details, and details of ports such as satellite cluster ports, cascade ports, ICL, and ICCP ports.

Delete a Configuration Template

To delete a Junos Fusion Enterprise, select the template and click Delete.