![]() |
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 300 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.
The local console port is the physical RJ45 RS-232 port on the left-hand side of the NetWall 300 Series's connector panel and is marked |O|O|.
Requirements for NetWall 300 Series Local Console Connection
To get management access via the local console port, the following is needed:The terminal console should have the following settings:
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 300 Series.
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:Username: admin
Password: admin
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.3, Management Computer Connection.