3.5. Local Console Port Connection

[Tip] Tip: 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 NetWall W50 unit from an external computer acting as a console terminal. This 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 firmware loader options. The boot menu is described further in the separate cOS Core Administration Guide.

The local console port is the physical RJ45 RS-232 port on the left-hand side front panel of the NetWall W50 and this is marked with the letter "C".

The W50 Local Console Port

Figure 3.1. The W50 Local Console Port

Requirements for NetWall W50 Local Console Connection

To get management access via the local console port, the following is needed:

Connection Steps

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

  1. Check that the console connection settings are configured as described above.

  2. Connect one of the connectors on the cable directly to the local console port on the W50.

  3. Connect the other end of the cable to a console terminal or to the serial connector of a computer running console emulation software.

[Note] 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 are discussed further in the separate cOS Core Administration Guide.

It is recommended to change the password for this user during initial cOS Core configuration.

Remote Console Connection Using SSH

An alternative to using the local console port for CLI access is to connect remotely 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.