3.5. RJ45 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 6000 Series 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.

NetWall 6000 Series RJ45 Local Console Port Connection

Figure 3.6. NetWall 6000 Series RJ45 Local Console Port Connection

Note that the NetWall 6000 Series has both an RJ45 console port and a micro-USB port (described in Section 3.6, Micro-USB Console Port Connection). Both can be used but if both are connected then the micro-USB port will automatically take precedence.

Requirements for NetWall 6000 Series 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 6000 Series.

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

The Default Local Console Login Credentials

The console user credentials for logging in are specified by the predefined admin user and are the same as the credentials for initial network access via the management Ethernet interface:

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.