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

    Creating the Virtual Machine Configuration

    To configure the virtual machines:

    • For Junos OS network devices such as the VJX1000, write, build, and edit the Junos OS configurations.
    • For other virtual machines, configure and boot those virtual machines.

    This topic contains the following sections:

    Configuring Junos OS Network Devices

    To configure a Junos OS network device:

    1. Manually compose a new Junos OS configuration file or edit an existing one for each virtual machine that uses a text editor.
    2. Submit the virtual machine configuration files with the topology.vmm file as part of the topology file set, as listed in Building a Topology File Set.

    Subsequent to the initial submission, log in to the network devices and use the CLI to update the configurations, as discussed in Connecting to the Network Topology.

    Rules for Junos OS Configuration Files

    The following rules apply to the Junos OS configuration files:

    • The topology.vmm file must be coded to install each virtual machine configuration file from its library location, as noted in the following coding example:
      install "ENV(HOME)/active/configset/vrouter001.conf" "/root/junos.conf";

      The install command defines the active configuration. As part of the virtual machine’s bootup process, the configuration file will be applied.

    • Junosphere applies a default configuration to each Junos OS network device:
      • A default configuration file is prepended to the configuration file you supply.
      • Your configuration takes precedence over the default file.
      • The default configuration will set up a root name and password, as well as basic services such as telnet and ssh.
      • The default configuration is found in Default Configuration File.
    • Interface ge-0/0/0 gets an assigned management IP address:
      • Do not otherwise configure this management interface.
      • Do not enable the interior gateway protocol (IGP) on this interface.

    Configuring Other Virtual Machines

    For other virtual machines, such as WANDL and Junos Space, configure and boot those virtual machines. Refer to the device user documentation.

    Configuring CentOS Servers

    To configure CentOS servers, you must have the following software installed on your local machine:

    • Virtual network computing client, such as RealVNC.
    • A file transfer application, such as FileZilla.

    Make sure that you have an active topology and know the IP address. To configure CentOS servers:

    1. On the Active Topology tab, click Join. The Junos Space Access Portal appears.
    2. Enter your Junosphere credentials to log in to the portal.
    3. When the Network Connect screen appears, click Start. When connected, a “lock” icon appears in the bottom right part of your screen.
    4. Launch your VPN client.
    5. Enter the IP address of the CentOS machine(s) to which you want to connect and add :1 to the address. This gives you access to port 1.
    6. Click OK.
    7. When prompted to enter your password, enter Clouds and click OK. The CentOS desktop appears.
    8. Click the browser icon in the menu bar.
    9. When the browser appears, enter the Space IP address in the address field.
    10. Double-click the lock icon. When the Network Connect dialog box appears (Figure 1), click Sign Out.

      Figure 1: Network Connect Dialog Box

      Network Connect Dialog
Box

    Note: If you do not sign out from your session, any unused secure access sessions will time out and the topology will be inaccessible until you re-establish the secure access session.

    Default Configuration File

    The following example shows the default Junos OS configuration file that is prepended to the configuration files that you submit.

    groups {
        member0 {
            system {
                host-name XXXhostnameXXX;
            }
        }
        global {
            system {
                root-authentication {
                    encrypted-password "$1$SGUyJfYE$r5hIy2IU4IamO1ye3u70v0"; ## SECRET-DATA
                }
    	    login {
    		message "Welcome to the cloud\npassword is Clouds\n";                       }
                time-zone America/Los_Angeles;
                debugger-on-panic;
                debugger-on-break;
                dump-on-panic;
                name-server {
                   8.8.8.8;
                }
                services {
                    finger;
                    ftp;
                    rlogin;
                    rsh;
                    ssh;
                    telnet;
                    xnm-clear-text;
                }
                security {
                    forwarding-options {
                        family {
                            inet6 {
                                mode packet-based;
                            }
                            mpls {
                                mode packet-based;
                            }
                            iso {
                                mode packet-based;
                            }
                        }
                    }
                }
                syslog {
                    host log {
                        kernel info;
                        any notice;
                        pfe info;
                        interactive-commands any;
                    }
                    file messages {
                        kernel info;
                        any notice;
                        authorization info;
                        pfe info;
                        archive world-readable;
                    }
                    file security {
                        interactive-commands any;
                        archive world-readable;
                    }
                }
                processes {
                    routing enable;
                    management enable;
                    watchdog enable;
                    snmp enable;
                    inet-process enable;
                    mib-process enable;
                }
            }
            chassis {
                dump-on-panic;
            }
        }
    }
    apply-groups [ global member0 ];
    system {
        archival {
            configuration {
                transfer-on-commit;
                archive-sites {
                    "ftp://tftp:tftp@XXXgatewayXXX/active/configset";
                }
            }
        }
    }
    

    Loading a Junos OS Configuration File

    For all Juniper Networks virtual routers, you can load an existing interface configuration file from the terminal by using the load configuration mode command at the [edit interfaces] hierarchy level.

    1. Copy an existing interface configuration file from the terminal, making sure the syntax of the configuration file is correct.
    2. At the console of the Juniper Networks virtual router, enter configuration mode:
      user@host> cli
      [edit]
      user@host#
    3. From configuration mode, issue the load merge terminal relative command at the [edit interfaces] hierarchy level.
      [edit interfaces]
      user@host# load merge terminal relative
    4. At the prompt, paste the contents of the clipboard and press Enter.
    5. Press Ctrl D.
    6. Commit the configuration to activate it on the virtual router.

    For more information about the load command, see the Junos OS CLI User Guide. To learn more about loading a configuration from a file for Junos OS routers, see Loading a Configuration from a File and Examples: Loading a Configuration from a File.

    Modified: 2015-06-15