Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

Firefly Perimeter Cluster Staging and Provisioning for VMware

Deploying the VMs and Additional Network Interfaces

• ge-0/0/0 is the Out-of-band Management Interface (fxp0).
• ge-0/0/1 is the Cluster Control-Link (fxp1).
• ge-0/0/2 is the Cluster Fabric-Link (fab0 on node0, fab1 on node1).

1. On the VMware vSphere Client, click Edit Virtual Machine Settings to create additional interfaces for the VM. See Figure 1 and Figure 2 for Virtual Machine Properties of the two Firefly Perimeter VMs.

   Figure 1: Virtual Machine Properties 1

   

   Figure 2: Virtual Machine Properties 2

   
2. Click Add Hardware and use the attributes in Table 1.

   Table 1: Hardware Attributes

   Attribute	Description
   Adapter Type	Select e1000 from the drop down.
   Network label	Select the network label from the drop down.
   Connect at power on	Ensure that there is a tick mark next to this option.

   See Figure 3.

   Figure 3: Adding Hardware

   

Creating the Control Link Connection Using VMware

1. Choose Configuration->Networking.
2. Click Add Networking to create a vSwitch for control link.

   Choose the following attributes:

   • Connection Type
     • Virtual Machines
   • Network Access
     • Create a vSphere stand switch
     • No physical adapters
   • Port Group Properties
     • Network Label: chassis cluster Control
     • VLAN ID: None(0)

     Note: Port groups are not VLAN. The port group does not segment the vSwitch into separate broadcast domains unless they have different VLAN tags. To use VLAN as a dedicated vSwitch, you can use the default VLAN tag (0) or specify a VLAN tag. To use VLAN as a shared vSwitch and use port group, you must assign a VLAN tag on that port group for each chassis cluster links.

   After creating the control vSwitch, you can use the vSwitch default settings.

3. Click Edit Settings of both Firefly VMs to add the control interface (Network adapter 2) into control vSwitch.

See Figure 4 for vSwitch Properties and Figure 5 for Virtual Machine Properties for Control vSwitch.

Figure 4: Control vSwitch Properties

Figure 5: Virtual Machine Properties for Control vSwitch

The control interface will be connected via the control vSwitch. See Figure 6.

Creating the Fabric Link Connection Using VMware

1. Choose Configuration->Networking.
2. Click Add Networking to create a vSwitch for fabric link.

   Choose the following attributes:

   • Connection Type
     • Virtual Machines
   • Network Access
     • Create a vSphere stand switch
     • No physical adapters
   • Port Group Properties
     • Network Label: chassis cluster Fabric
     • VLAN ID: None(0)

     Note: Port groups are not VLAN. The port group does not segment the vSwitch into separate broadcast domains unless they have different VLAN tags. To use VLAN as a dedicated vSwitch, you can use the default VLAN tag (0) or specify a VLAN tag. To use VLAN as a shared vSwitch and use port group, you must assign a VLAN tag on that port group for each chassis cluster links.

   Click Properties to turn on the following features:

   • General-> Advanced Properties:
     • MTU: 9000
   • Security-> Effective Polices:
     • MAC Address Changes: Accept
     • Forged Transmits: Accept
3. Click Edit Settings of both Firefly VMs to add the fabric interface into fabric vSwitch.

   Note: Network adaptor 4 is used in this example, which is configurable in Junos OS.

See Figure 7 for vSwitch Properties and Figure 8 for Virtual Machine Properties for Fabric vSwitch.

Figure 7: Fabric vSwitch Properties

Figure 8: Virtual Machine Properties of Fabric vSwitch

The fabric interface will be connected via the fabric vSwitch.

Figure 9: Control Interface Connected via Control vSwitch

Creating the Data Interfaces Using VMware

1. Choose Configuration->Networking.
2. Click Add Networking to create a vSwitch for fabric link.

   Choose the following attributes:

   • Connection Type
     • Virtual Machines
   • Network Access
     • Create a vSphere stand switch
     • No physical adapters
   • Port Group Properties
     • Network Label: chassis cluster Reth
     • VLAN ID: None(0)

     Click Properties to turn on the following features:

     • General-> Advanced Properties:
       • MTU: 9000
     • Security-> Effective Polices:
       • MAC Address Changes: Accept
       • Forged Transmits: Accept

See Figure 10 for Virtual Machine Properties for Data vSwicth.

Figure 10: Virtual Machine Properties for Data vSwitch

The data interface will be connected via the data vSwitch using the above procedure.

Installing Pre-Staging Configuration from the Console

1. Log in as the root user. There is no password.
2. Start the CLI.
   root#cliroot@>
3. Enter configuration mode.
   configure [edit]root@#
4. Copy the following commands and paste them into CLI:
   set groups node0 interfaces fxp0 unit 0 family inet address 192.168.42.81/24set groups node0 system hostname fireflyperimeter-node0set groups node1 interfaces fxp0 unit 0 family inet address 192.168.42.82/24set groups node1 system hostname fireflyperimeter-node1set apply-groups "${node}"
5. Set the root authentication password by entering a cleartext password, an encrypted password, or an SSH public key string (DSA or RSA).
   root@# set system root-authentication plain-text-passwordNew password: passwordRetype new password: password set system root-authentication encrypted-password "$ABC123”
6. To enable SSH remote access:
   user@host#set system services ssh
7. To enable IPV6:
   user@host#set security forwarding-options family inet6 mode flow-based

   This step is optional and requires a system reboot.

8. Commit the configuration to activate it on the device.
   user@host#commitcommit complete
9. When you have finished configuring the device, exit configuration mode.
   user@host#exit

Connecting and Installing the Staging Configuration

After the Firefly Cluster initial setup, set the cluster ID and the node ID. For commands on setting the cluster id and the node id, see Configuring Chassis Cluster for Firefly Perimeter with VMware.

After reboot, the two nodes are reachable on interface fxp0 (ge-0/0/0) with SSH. If the configuration is okay, the Cluster Status is displayed as shown in Figure 11.

Figure 11: Cluster Status

A cluster is healthy when both primary and secondary are present and when both have a priority >0.