3.5. Mini-USB Console Port Connection

Home Prev	NetWall E80B Getting Started Guide	Next

	Note: Skip this section if using the Web Interface for set up
	Console port connection can be skipped if cOS Core setup is going to be done using the cOS Core Web Interface since neither CLI or boot menu access will be needed.

The local console port allows direct management connection to the E80B, either from a separate computer acting as a console terminal. Local console access can then be used for both management of cOS Core with CLI commands or to enter the boot menu in order to access E80B firmware loader options.

The local console port is a physical mini-USB port (type mini-B) on the E80B hardware.

Figure 3.1. The E80B Mini-USB Local Console Port

Connection Steps

To connect a computer to the local console port, perform the following steps:

Connect a mini-USB connector directly to the local console port on the E80B.
Connect the other end of the cable to a USB port on computer running console emulation software.
After connection to a PC, Windows will try to recognize the device and automatically install the appropriate driver through the Windows Update™ feature. If Windows is unable to do this automatically, the driver should be downloaded and installed manually.

To download micro-USB drivers manually, log into the relevant MyClavister account at https://my.clavister.com and go to Downloads > Tools & Utilities.
Direct the console emulator on the computer to connect to the newly installed device. After successful connection, commands can be issued to the cOS Core Command Line Interface (CLI).

Issuing CLI Commands

CLI commands can be issued via the local console port for both initial cOS Core setup as well as for ongoing system administration.

The local console port need not be used if setup is done through a web browser as described in Section 4.1, Web Interface and Wizard Setup. If the local console port is used for setup, no password is initially needed and the CLI commands required are described in Section 4.3, Manual CLI Setup.

Remote Console Connection Using SSH

An alternative to using the local console port for CLI access is to connect over a network via a physical Ethernet interface and using a Secure Shell (SSH) client on the management computer to issue CLI commands. This is discussed further in Section 3.4, Management Computer Connection.

	Note: Setting a local console password is recommended
A local console password need not be set. However, if it is not, anyone with physical access to the local console will have full administrator rights. Unless the hardware is placed in a secure area, it is therefore recommended to set a local console password. This is done by entering the console boot menu at system startup by pressing any console key before cOS Core has fully started. The boot menu and its options is discussed further in the separate cOS Core Administrators Guide.

Note: Setting a local console password is recommended

A local console password need not be set. However, if it is not, anyone with physical access to the local console will have full administrator rights.

Unless the hardware is placed in a secure area, it is therefore recommended to set a local console password. This is done by entering the console boot menu at system startup by pressing any console key before cOS Core has fully started. The boot menu and its options is discussed further in the separate cOS Core Administrators Guide.