Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All
     

    Related Documentation

     

    Creating a Virtualized SRC Instance

    You can create a virtualized SRC instance by using the iso, qcow2, or vmdk image.

    Note: We recommend you to create a virtualized SRC instance by using the qcow2 image.

    Creating a Virtualized SRC Instance Using qcow2 Image

    To create a virtualized SRC instance on the KVM hypervisor by using the qcow2 image:

    1. Download the qcow2.gz image from https://www.juniper.net/support/downloads/?p=src#sw and place it on the host operating system.
    2. Unzip the image on the host operating system.
      gunzip name.qcow2.gz
    3. Download the SDK+AppSupport+Demos+Samples.tar.gz file from https://www.juniper.net/support/downloads/?p=src#sw and place it on the host operating system.
    4. Untar the file to use the create_vm.py script for creating a virtualized SRC instance.
      tar –xzvf SDK+AppSupport+Demos+Samples.tar.gz
    5. Execute the create_vm.py script from the path where the SDK+AppSupport+Demos+Samples.tar.gz is extracted.
      #$cd <sdk_root_folder>/SDK/vSRC/
      #$./create_vm.py

      Note: The create_vm.py script is not supported for VMware virtual machine creation. To create a virtualized SRC instance on VMware hypervisor, use the iso or vmdk image.

      The script requests various details for creating the virtualized SRC instance.

    6. Enter the requested details. The details requested by the script are:
      • Name for the virtualized SRC instance
      • Number of CPUs to be allocated for the virtualized SRC instance
      • Memory (in megabytes) to be allocated for the virtualized SRC instance
      • Network configuration details:
        • Number of interfaces to be configured
        • Media access control (MAC) address for each interface. You can enter MAC address or allow the script to create the MAC address automatically.
        • Networking mode for each interface. The supported modes are:
          • Direct host device mapping with bridge mode—Use this mode if multiple network interfaces have to be shared with a host device (for example, eth0). This mode is ideal for hosting multiple virtualized SRC instances with multiple interfaces. This is the default mode.
          • Direct host device mapping with passthrough mode—In this mode, one-to-one mapping is done between the host device network interface and virtualized SRC instance’s network interface. You can use this mode when only one virtualized SRC instance is hosted in the server.
          • Shared bridge mapping (bridge has to be manually configured)—In this mode, you have to manually configure the bridge and provide the shared bridge name as an input. This mode provides flexibility to have more complex networking.
      • Path of the qcow2 image file

      The script creates an xml file with the name of the virtualized SRC instance and creates the virtualized SRC instance by using the virsh command. The xml file contains one serial console configuration and one vnc console configuration.

      Note: You must have the virsh management tool in the host operating system for the script to successfully create the virtualized SRC instance.

    7. Log in to the virtualized SRC instance through any hypervisor management tool and set up the initial configuration for the SRC software. For information about the initial configuration, see your C Series Controller Hardware Guide.

    Creating a Virtualized SRC Instance Using iso Image

    To create a virtualized SRC instance on VMware and KVM hypervisors by using the iso image:

    1. Download the iso image from https://www.juniper.net/support/downloads/?p=src#sw and place it in the host operating system.
    2. Start installing the iso image in the virtual machine by using the hypervisor management tool (such as virt-manager, virsh, VMware vSphere client, and VMware Workstation Player). The virtual machine boots from the iso image and prints the following message:
      Welcome to SRC PE Software Installation.
      
      WARNING: This system recovery software replaces all data and software
      on the system disk image. As a result, any data, including data
      previously in the snapshot partition, is lost.
      
      After you run the system installation software, the virtual image
      contains the SRC software, including the SRC operating system,
      but no configuration data.
      
      To continue, press <TAB> and choose the installation type.
      
      To enable serial console enter following after choosing the
      Installation type :
      “console=tty0 console=tty50, 9600
      
      To cancel this operation, power off the system and remove
      the iso image.
      boot:
       AUTO Manual rescue
      boot:
      
    3. At the boot prompt, type the installation option.
      • If the typed option is AUTO, the disk space is partitioned automatically and the packages are installed. The following hard disk partition scheme is used:
        • /—8.5 GB
        • /var—50 percent of remaining hard disk space
        • 50 percent of remaining hard disk space can be used for storing snapshots
      • If the typed option is Manual, you can define the partition scheme and other general settings (such as language) through the displayed dialog boxes to install the SRC software.

        Note: You cannot create snapshot or restore snapshot with custom partition scheme. We recommend you to use the virsh snapshot-create command on KVM hypervisor and use the Snapshot option in the VMware Workstation Pro or VMware ESXi hypervisor to maintain snapshots of disk image.

    4. After the successful installation, reboot the virtual machine.
    5. After the virtual machine reboots, set up the initial configuration. For information about the initial configuration, see your C Series Controller Hardware Guide.

    Creating a Virtualized SRC Instance Using the vmdk Image

    Virtual Machine Disk (vmdk) is a file format that describes containers for virtual hard disk drives to be used in VMware virtual machines. The vmdk image shipped with the SRC software is of the monolithicSparse type, and the image has been tested with monolithicSparse and monolithicFlat types. If you are using VMware ESXi, either the iso image or the vmdk image of monolithicFlat type must be used. To convert the monolithicSparse type to the MonolithicFlat type, use the qemu-img convert -f vmdk vmdk-file-name-MonolithicSparse -O vmdk output-file-name -o subformat={ monolithicFlat } command. To use this command, you must have the qemu-img tool installed in your system.

    Note: The SRC software installation is currently supported and tested over the VMware Workstation 12 Player, VMware Workstation 12 Pro, and VMware ESXi 5.5.0.

    To create a virtualized SRC instance on VMware hypervisor by using the vmdk image:

    1. Download the vmdk image from https://www.juniper.net/support/downloads/?p=src#sw and place it in the host operating system.
    2. Using VMware vSphere client or VMware workstation player, create a new virtual machine with custom configurations (RAM, CPU, network, and so on). Provide the path of the downloaded vmdk image in the Virtual Disk section.

      Note: The following settings have been tested by Juniper Networks:

      • Network Connection—Bridged Networking
      • I/O Controller Type—LSI Logic
      • Virtual Disk Type—SCSI
      • OS—CentOS (64-bit)
    3. Power on the virtual machine to start the SRC software.
    4. After the virtual machine boots, set up the initial configuration. For information about the initial configuration, see your C Series Controller Hardware Guide.

      Note: You cannot create snapshot or restore snapshot with custom partition scheme. We recommend you to use the Snapshot option in the VMware Workstation Pro or VMware ESXi to maintain snapshots of disk image.

      The virtual machine gets paused while creating snapshots. We recommend you to disable the Juniper Networks database (jdb component) and components involved in service activities during snapshot creation.

     

    Related Documentation

     

    Modified: 2016-06-02