2.4. RJ45 Console Port Connection

Home Prev	NetShield 500 Series Getting Started Guide	Next

The local console port allows direct management connection to the NetShield 500 Series unit from an external computer acting as a console terminal. This local console access can then be used for both management of cOS Stream 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 Stream Administration Guide.

The local console port is the physical RJ45 RS-232 port on the left-hand side of the NetShield 500 Series's connector panel and is marked |O|O|.

Figure 2.6. NetShield 500 Series RJ45 Local Console Port Connection

Note that the NetShield 500 Series has both an RJ45 console port and a micro-USB port (described in Section 2.5, 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 NetShield 500 Series Local Console Connection

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

An external computer with a serial port and the ability to emulate a console terminal (for example, using the open source puTTY software).
The terminal console should have the following settings:
1. 115,200 bps.
2. No parity.
3. 8 bits.
4. 1 stop bit.
5. No flow control.
An RS-232 cable with appropriate terminating connectors.

Connection Steps

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

Check that the console connection settings are configured as described above.
Connect one of the connectors on the cable directly to the local console port on the 500 Series.
Connect the other end of the cable to a console terminal or to the serial connector of a computer running console emulation software.

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 2.3, Management Computer Connection.