From the Start – How to Setup Device42 from the Beginning on a Mac
To use Device42 you will need a hypervisor like Virtualbox, VMWare Workstation, or VMware Player, etc. that can run virtual machines. If you do not have one, you can download VirtualBox for free [it’s Open Source] on their website, https://www.virtualbox.org
To install VirtualBox, open the downloaded file and double click the “VirtualBox.pkg” icon. You should then be able to find VirtualBox in your Applications list.
To download Device42, visit Device42 and enter your name and work email address. You will receive a download link in your email momentarily. Once you receive the link, choose the download labeled ‘VirtualBox’ from the download options given, as seen in the screenshot below:
Once the file has downloaded, you will need to unzip it. You can unzip it using Keka, which is a free program available through the App store or from their website, Keke.
From VirtualBox, click the “New” icon, and name your virtual machine, we will use “device42Setup” in this tutorial:
We recommend 2GB of memory at a minimum and suggest 4GB to be sure Device42 runs smoothly.
On the Hard Disk screen, choose “Use an existing virtual hard disk file” and browse to the Device42 vmdk file that you extracted using keka.
After choosing the hard disk you can follow through with any further default settings, but uncheck “Power on after Create” if it is selected.
Additional VM Settings
Right click on the newly created virtual machine in VirtualBox that appears on the left and choose “Settings”.
In the window that pops up, select the “System” tab, and then “Processor”, and click the checkbox in “Extended Features” to “Enable PAE/NX”:
Continuing to the “Network” tab, enable adapter 1 and set it to bridged (note, NAT will also work), and choose the physical NIC/network card you will be using. You can then click OK and close the settings window.
Starting the Virtual Machine
Once the VM settings have been configured you can power on the virtual appliance. If you receive an audio driver warning you can ignore it.
At the login screen the username is “device42” and the password is “adm!nd42”. Please change these when you first log in under option 10.
After you are logged in, you can configure your ip settings [Please use a STATIC IP for all production Device42 VMs to avoid connectivity issues] under option 1:
You can apply updates and do other menu-related work using by connecting through ssh using the terminal. Please note that root login has been disabled via ssh.
Last, point your browser to the address at the top of the console menu and you’re ready to go…
You will receive a “Your Connection is not private” warning in your browser because you are accessing a local server that does not have an ‘offically’ signed security certificate. Your connection is secure, and it is completely safe to click “show advanced” in Chrome or “I understand the risks” in Firefox and proceed through to the Device42 login screen:
At the login screen you can login using the default name and password: admin/adm!nd42
At this point, you should be logged in, and can now start using Device42!
To continue through our documentation, you may want to view our tutorials next.