Establishing a first-time connection to the console port

You can use either the USB Type-C console port or the RJ-45 serial console port to establish the first time connection to the device. The console port allows you to configure and manage the device using a third-party terminal emulation application from a workstation that is directly connected to the port using a standard USB Type-C cable or RJ-45 serial cable. Perform the following steps to log in to the device for the first time through the console connection.
  1. Do one of the following:
    • Connect a standard USB cable to the USB Type-C console connector on the device and to a USB port on the workstation. To connect the USB Type-C console port on the device to a USB port on the workstation, you need a standard USB cable that has a USB Type-C connector on one end and a USB connector on the other end that matches the USB port on your workstation.
    • Connect a standard RJ-45 cable to the RJ-45 serial console connector on the device and to a USB port on the workstation. To connect the RJ-45 serial console port on the device to a USB port on the workstation, you need a standard RJ-45 cable that has a RJ-45 connector on one end and a USB connector on the other end that matches the USB port on your workstation.
  2. Allow the workstation to automatically discover and configure the newly found USB device.
    NOTE
    If the workstation is unable to automatically discover and configure the newly found USB device, you can manually download the necessary device drivers for Windows, MacOS, and Linux from the following website: https://support.ruckuswireless.com//
  3. Open a terminal emulator application such as HyperTerminal on a Windows PC, or TERM, TIP, or Kermit in a UNIX environment, and configure the sessions parameters as follows:
    • In a Windows environment, use the following values:

      Parameter

      Value

      Baud: Bits per second

      9600

      Data bits

      8

      Parity

      None

      Stop bits

      1

      Flow control

      None

      NOTE
      Flow control is not supported on the console connection when attached to a remote terminal and must be disabled on the customer-side remote terminal server in addition to the host-side clients.
    • In a UNIX environment using TIP, enter the following string at the prompt:
      tip /dev/ttyb -9600.
      

      If ttyb is already in use, use ttya instead and enter the following string at the prompt:

      tip /dev/ttya -9600
      
  4. When the terminal emulator application stops reporting information, press Enter to display the device prompt.

    Depending on the device you purchased, and the code (Layer 2 or Layer 3) loaded on your system, the device prompt is displayed accordingly.

    device>

    When the device prompt is displayed, you are connected to the device. You can customize the prompt by changing the device name. If you do not see this prompt, make sure the cable is securely connected to your workstation and to the device and check the settings in your terminal emulation program. In addition to the previously configured session settings, make sure the terminal emulation session is running on the same serial port you attached to the device.

    The device CLI prompt has the following access levels:

    • User EXEC: This is the level you enter when you first start a CLI session. At this level, you can view some system information but you cannot configure system or port parameters.
    • Privileged EXEC: This level is also called the Enable level and can be secured by a password. You can perform tasks such as managing files on the flash module, saving the system configuration to flash, and clearing caches at this level.
    • CONFIG: The configuration level. This level allows you to configure the system IP address and configure switching and routing features. To access the CONFIG mode, you must already be logged in to the privileged EXEC level.
  5. At the opening CLI prompt, enter the following command to change to the Privileged EXEC mode:
    device> enable
    device#  

    By default, the CLI is not protected by passwords. To secure CLI access, Ruckus strongly recommends assigning passwords. You can set the following levels of passwords:

    • Super User: Allows complete read-and-write access to the system. This is generally for system administrators and is the only password level that allows you to configure other passwords.
      NOTE
      You must set a Super User password before you can set other types of passwords. You can also assign other passwords using Brocade Network Advisor after an enable password has been configured for a Super User on the device using the CLI.
    • Port Configuration: Allows read-and-write access to specific ports but not for global (system-wide) parameters.
    • Read-Only: Allows access to the privileged EXEC mode and CONFIG mode but only with read access.
      NOTE
      Passwords can be up to 32 characters long. They must begin with an alphabetic character. They can include numeric characters, the period (.), and the underscore (_) only. Passwords are case-sensitive, and they are not displayed when you enter them on the command line.
  6. Access the configuration mode of the CLI by entering the following command:
    device# configure terminal
    device(config)#
  7. Enter the following command to set the Super User password:
    device(config)# enable super-user-password joe
    NOTE
    Make sure to write down the new passwords and keep the information in a secure location.
  8. Enter the following commands to set the port configuration and read-only passwords.
    device(config)# enable port-config-password john
    device(config)# enable read-only-password sam