Sandbox Commands

The sandbox command has six subcommands. Not all subcommands are always available in the NetMRI administrative shell. Commands that appear in the shell depend on the current configuration. The following table describes each command and its availability for each platform:

Command	Description	Notes
`sandbox login`	Log in to the sandbox VM environment. By default, superuser privileges are provided in the Sandbox environment. You use the sbuser account by default and the system places you in the local directory for that account.	Available for local and remote sandbox instances.
`sandbox restart`	Restarts the sandbox VM's operating system. Useful in cases where a script is stuck in a loop or otherwise cannot be ended, or the operating system undergoes an upgrade and requires a restart. For remote sandbox instances, you can log in to the VM and run the `reboot` command; or reset the VM from the hypervisor.	Available only for local sandbox instances.
`sandbox reset`	Completely restores and rebuilds the entire local sandbox VM's file system to its default configuration. Considered "the nuclear option" when a Perl script accidentally renders unusable some part of the VM's environment. The larger NetMRI file system, operating system, and functional operations will remain unaffected by a `sandbox reset` directive or by any operations from an errant Perl script in the VM. The system erases any previously installed Perl modules or software utilities; the shared partition remains unaffected by this directive. To reset a remote sandbox instance, you redeploy a downloaded sandbox VM image.	Available only for local sandbox instances.
`sandbox register`	NetMRI administrative shell command that configures NetMRI to communicate with a new remote sandbox VM. Execute this command after installing the remote sandbox VM image into the VMware® server and setting up the remote sandbox. When executing this command you are prompted to enter the IP address of the remote sandbox to be registered. You will also be prompted twice to enter the password for the sbuser account on the remote sandbox (NetMRI prompts twice for the password to make sure no errors are made entering the password).	Available only when a remote sandbox is not currently registered.
`sandbox deregister`	NetMRI administrative shell command that disassociates the remote sandbox from the system.	Available when a remote sandbox is currently registered.
`sandbox show`	NetMRI administrative shell command that shows the status and basic configuration of the local or the remote sandbox. The `sandbox show` command displays the network IP address and its mode: local, remote, or N/A. N/A indicates that the platform is not capable of supporting a local sandbox and that no remote sandbox has been registered. A remote sandbox must be registered to use Perl scripting on platforms that do not support a local sandbox.	Always available.

Given the power and flexibility of the Perl language, Infoblox recommends treating this functionality with the caution and expertise it deserves. Knowledgeable Perl users may install and use different Perl software modules, database management software, and other utilities and write scripts that consume unacceptable amounts of appliance CPU cycles and available memory. If any Perl script runs out of control, the only file system affected is that within the sandbox instance; the NetMRI appliance remains unaffected. You may need to run the sandbox restart or sandbox reset command to halt an errant Perl script on a local sandbox.
The NetMRI appliance strictly limits system disk and memory resource allocations for its local Sandbox instance, and those resources are not extensible from within the Sandbox. If the Sandbox is set up as a remote VM instance, the hypervisor determines memory and other resource allocations.

Note

To close the sandbox and return to the administrative prompt, type exit and press Enter.