Large campus and data center networks might have many similar network topology instances. These instances can be Virtual Chassis Fabrics (VCFs), Layer 3 Fabrics, or Junos Fusion Enterprise, or Junos Fusion Data Center. 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:
You can perform the following tasks from the Manage Fusion Configuration Templates page.
To create a Junos Fusion Enterprise configuration template:
Note: Do not select Dashboard View, Datacenter View, or Topology View.
The Manage Fusion Configuration Templates page opens.
The Create Fusion Configuration Template wizard opens.
For a Junos Fusion Data Center, select Fusion Data Center Multiple Aggregation Devices.
Network Director lists the satellite software image only if you have uploaded the software image in Network Director Image Repository.
The Settings page opens.
If you chose to configure with multiple aggregation devices, the Settings page displays two tabs—Aggregation Device 1 and Aggregation Device 2.
Network Director supports the following as aggregation devices:
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.
To create a 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.
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.
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.
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.
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.
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.
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:
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.
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.
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.
To create a Junos Fusion Data Center configuration template:
Note: Do not select Dashboard View, Datacenter View, or Topology View.
The Manage Fusion Configuration Templates page opens.
The Create Fusion Configuration Template wizard opens.
Network Director lists the satellite software image only if you have uploaded the software image in the Network Director Image Repository.
The Settings page opens.
If you chose to configure with multiple aggregation devices, the Settings page displays two tabs—Aggregation Device 1 and Aggregation Device 2.
Network Director supports the following as aggregation devices:
Note: In a Fusion Data Center Multiple Aggregation Device topology, when you select a device as the first aggregation device, Network Director interprets the second aggregation device also to be of the same device model.
The Select Ports window appears.
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.
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.
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.
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 Ports and perform the following steps to select the ports:
Note: The port type is selected as the ICL port.
When you select an ICL port as the LAG interface, there is no additional configuration required for the LAG on the selected ICL port. A default configuration is generated by Network Director 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.
If you want to modify the setting for the second aggregation device, click Aggregation Device 2 and click Edit. Select a device model and follow steps Step 11 through Step 12 to specify details for the second aggregation device.
Network Director creates the template and displays it in the Manage Fusion Configuration Templates page.
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 or Junos Fusion Data Center template:
The Clone Fusion Configuration Template page opens.
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.
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.
To apply a configuration template to Junos Fusion Enterprise or Junos Fusion Data Center devices:
Skip to Step 4 and follow the instructions to apply the template to managed devices.
Table 156: 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:
|
DHCP User | Username to log in to the DHCP server. |
DHCP Password | Password for the specified username. |
Confirm Password | Confirm the DHCP server password. |
Table 157: 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. |
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.
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.
Note: When you use the Import option, you must specify either the MAC address or the Serial number, but not both.
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.
Note: When you use the Import option, you must specify either the MAC address or the Serial number, but not both.
Note: This field is available only when you choose to configure the ICCP port manually for a Junos Fusion Enterprise device.
Click the text link in the Password column to set or modify the password for the aggregation device.
Select Edit Custom if you want to specify a different password for the aggregation device. Specify the password, confirm the password, and click Set.
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.
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:
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
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.
For a Junos Fusion Data Center 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 cascade ports and ICL ports.
To delete a Junos Fusion Enterprise or Junos Fusion Data Center configuration template, select the template and click Delete.