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

    Running the Junosphere Connector in Linux

    Before you can run Junosphere Connector, you must have successfully started and joined a topology. For information on starting and running a topology, see the Junosphere Network Topology Guide.

    Downloading and Installing the Junosphere Connector

    To install and run the Junosphere Connector, you must be logged in as root.

    1. Download the Junosphere Connector.
    2. Extract the .zip file to a directory where you can access the Junosphere Connector .vmx file. For example: unzip connector-1201.zip

    Downloading and Installing the VMware Player

    To install and run the VMware Player, you must be logged in as root.

    1. Download the VMware for the appropriate OS on your PC.
    2. Run the VMware Player bundle by entering the following command, using the appropriate version number for your VMware Player:

      [root@skykvm4 VMwarePlayer]# ./ 5.0.0-812388.x86_64.bundle

      Extracting VMware Installer...done.

    3. Enter No for the first two prompts.

      Would you like to check for product updates on startup? [yes]: no

      Would you like to help make VMware software better by sending anonymous system data and usage statistics to VMware? [yes]: no

    4. Press Install to begin.

      The product is ready to be installed. Press Enter to begin installation or Ctrl-C to cancel.

      Installing VMware Player Application 3.1.3

      Copying files...

      [##################################### ] 53%

    Configuring VMware Player to Use eth1 as Bridge

    1. Enter the following command to view the vmnet-bridge processes on your PC:

      ps aux | grep vmnet-bridge

      root 4138 0.0 0.0 59292 504 ? Ss 13:08 0:00 /usr/bin/vmnet-bridge -s

      14 -d /var/run/vmnet-bridge-0.pid -n 0

      root 4211 0.0 0.0 61164 736 pts/7 S+ 13:09 0:00 grep bridge

    2. Enter the following command to stop the vmnet-bridge process so you can start a new process on the second Ethernet (eth1):

      kill -9 process-id

      Example:kill -9 4138

    3. Enter the following command to start a new vmnet-bridge process on the interface (eth1) that will be used to send or forward traffic from a physical device:

      vmnet-bridge -n 0 -i eth1 -d /var/run/vmnet.pid

    Launching and Configuring VMware Player

    1. Open a terminal window and log in as root.
    2. Enter the following command to launch VMware Player:

      vmplayer &

    3. Open the Junosphere Connector .vmx file in VMware Player by selecting File > Open.
      1. Navigate to the Junosphere Connector .vmx file.
      2. Select the Junosphere Connector .vmx file and click Open.
    4. Click Edit virtual machine settings.
    5. In the Virtual Machine Settings dialog box, change the Network Adapter from Bridged to NAT.
    6. Set Network Adapter2 to Bridged.
    7. Click Save.

    Establishing the Physical Connection

    The computer you are using to log in to Junosphere must have two Ethernet cards: eth0 and eth1.

    • eth0 is used to connect to the UI and user topology via Network Connect.
    • eth1 is used to connect to the external device that will talk to the virtual network topology via Junosphere Connector.

    To establish the physical connection:

    1. To connect your LAN to eth1, connect one end of a cable to eth1.
    2. Connect the other end to a switch.
    3. Connect your other physical devices to that switch.

    Launching and Joining a Topology

    For information on starting and running a topology, see the Junosphere Network Topology Guide.

    1. When the topology is active, click Join.
    2. On the Junosphere Access Portal page, enter your username and password and click Sign In.
    3. Click Start to launch the Secure Access SSL VPN and connect to your topology.

    Running the Junosphere Connector in Linux

    To start the Junosphere Connector:

    1. Open a terminal window and log in as root.
    2. Enter the following command at the prompt to launch VMware Player if not already running:

      vmplayer &

    3. Select connector and click Play virtual machine.
    4. At the command prompt, log in as user=hconnect; password=hconnect. The following information appears:

      Last login: Thu Mar 10 18:19:01 2011

      Welcome to the Junosphere Connector virtual appliance. To get started, type:

    5. To connect to your bridge on your virtual topology, issue the following commands:

      /vmm/bin/hconnect -c <customer name> I-b <bridge to connect to> -s <pod to connect to>

      For example:

      [hconnect@localhost ~]$ hconnect -u hconnect -b private0 –s junosphere.net

      Junosphere Connector Version: 1.1194-3

      Checking connection to 10.233.255.254 [ok]

      Starting Junosphere config connecting to 10.233.255.254

      This command does not return. Ctrl-C to terminate the Hybridge connection.

      The stats of the Hybridge connection will be displayed every 10 seconds

      until the connection is terminated

      --------------------------------------

      date: Mon Apr 11 19:37:50 2011

      --------------------------------------

      Port 0001: Local Hybridge connection

      Port 0002: Remote Hybridge connection

      Port 0001 untagged_vlan=0000 QnQ,Strict=0000,0 ACTIVE - Unnamed Allocatable

      IN: pkts 27 bytes 2358

      OUT: pkts 20 bytes 1904

      Port 0002 untagged_vlan=0000 QnQ,Strict=0000,0 ACTIVE - Unnamed Allocatable

      IN: pkts 20 bytes 1904

      OUT: pkts 27 bytes 2358

    Note: If Junosphere Connector fails to start, check to make sure you successfully joined and started Network Connect. You should see a lock/key icon at the bottom of your screen. Junosphere Connector will fail if it cannot reach the NAT IP ( 10.233.255.254). If you successfully join the topology, at the prompt you should be able to successfully ping 10.233.255.254.

    At this point, packets from your VDE in your topology will now go to your switch and then to your physical device.

    In Junosphere, the Active Topology Connectors tab should resemble Figure 1, with the Active column of private0 showing “true”.

    Warning: To prevent IP address conflicts between your physical lab and your Junosphere topology, make sure you configure the IP address of your Junosphere VMs before you launch the Junosphere Connector.

    Figure 1: Active Column

    Active Column

    Published: 2013-08-15