Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
QFX5210 Switch Hardware Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Performing the Initial Software Configuration for the QFX5210

date_range 25-May-24

Before you begin connecting and configuring a QFX5210, set the following parameter values on the console server or PC:

  • Baud Rate—9600

  • Flow Control—None

  • Data—8

  • Parity—None

  • Stop Bits—1

  • DCD State—Disregard

You must perform the initial configuration of the QFX5210 through the console port using the command-line interface (CLI) or through Zero Touch Provisioning (ZTP). In order to use ZTP to provision the device, you must have access to a Dynamic Host Control Protocol (DHCP) server and a File Transfer Protocol (anonymous FTP), Hypertext Transfer Protocol (HTTP), or Trivial File Transfer Protocol (TFTP) server on which the software image and configuration files are stored. For more information about using ZTP for provisioning the device, see Understanding Zero Touch Provisioning.

Note:
We no longer include the RJ-45 console cable with the DB-9 adapter as part of the device package. If the console cable and adapter are not included in your device package, or if you need a different type of adapter, you can order the following separately:
  • RJ-45 to DB-9 adapter (JNP-CBL-RJ45-DB9)
  • RJ-45 to USB-A adapter (JNP-CBL-RJ45-USBA)
  • RJ-45 to USB-C adapter (JNP-CBL-RJ45-USBC)

If you want to use RJ-45 to USB-A or RJ-45 to USB-C adapter you must have X64 (64-Bit) Virtual COM port (VCP) driver installed on your PC. See, https://ftdichip.com/drivers/vcp-drivers/ to download the driver.

To connect and configure the switch from the console:

  1. Connect the console port to a laptop or PC using an RJ-45 cable and RJ-45 to DB-9 adapter. The console (CON) port is located on the management panel of the switch.
  2. Log in as root. There is no password. If the software booted before you connected to the console port, you might need to press the Enter key for the prompt to appear.
    content_copy zoom_out_map
    login: root
  3. Start the CLI.
    content_copy zoom_out_map
    root@% cli
  4. Enter configuration mode.
    content_copy zoom_out_map
    root> configure
  5. Add a password to the root administration user account.
    content_copy zoom_out_map
    [edit]
    root@# set system root-authentication plain-text-password
    New password: password
    Retype new password: password
  6. (Optional) Configure the name of the switch. If the name includes spaces, enclose the name in quotation marks (“ ”).
    content_copy zoom_out_map
    [edit]
    root@# set system host-name host-name
  7. Configure the default gateway.
    content_copy zoom_out_map
    [edit]
    root@# set routing-options static route default next-hop address
  8. Configure the IP address and prefix length for the switch management interface.
    content_copy zoom_out_map
    [edit]
    root@# set interfaces em0 unit 0 family inet address address/prefix-length
    Note:

    The management port em0 (C0) is found on the FRU end of the QFX5210 switch.

  9. (Optional) Configure the static routes to remote prefixes with access to the management port.
    content_copy zoom_out_map
    [edit]
    root@# set routing-options static route remote-prefix next-hop destination-ip retain no-readvertise
  10. Enable telnet service.
    content_copy zoom_out_map
    [edit]
    root@# set system services telnet 
    Note:

    When Telnet is enabled, you cannot log in to a QFX5210 switch through Telnet using root credentials. Root login is allowed only for SSH access.

  11. Enable SSH service for root login.
    content_copy zoom_out_map
    [edit]
    root@# set system services SSH 
  12. Commit the configuration to activate it on the switch.
    content_copy zoom_out_map
    [edit] 
    root@# commit
footer-navigation