Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Step 2: Up and Running

 

Now that the QFX5130-32CD is powered on, let’s do some initial configuration to get it up and running on the network. It’s simple to provision and manage the QFX5130 using the CLI.

Plug and Play

The QFX5130-32CD switch ships with factory-default settings that enable plug-and-play operation. The default settings enable the Link Layer Discovery Protocol (LLDP). These settings load as soon as you power on the QFX5130-32CD switch.

Customize the Basic Configuration

You can easily customize the factory-default configuration using CLI commands. Initially, you must make changes through the console port. After you configure the management port, you can access the device using SSH to make additional configuration changes. You can revert to the factory-default configuration whenever you want.

Have the following information ready before you begin to configure custom settings for the switch:

  • Hostname

  • Root authentication password

  • Management port IP address

  • Default gateway IP address

  • (Optional) SNMP read community, location, and contact information

  1. Verify that your laptop or desktop PC has these default serial port settings:
    • Baud Rate—9600

    • Flow Control—None

    • Data—8

    • Parity—None

    • Stop Bits—1

    • DCD State—Disregard

  2. Connect the console port on the QFX5130-32CD to a laptop or desktop PC using the supplied RJ-45 cable and RJ-45 to DB-9 adapter. The console (CON) port is located on the upper right corner of the port panel.Note

    If your laptop or desktop doesn't have a serial port, use a serial-to-USB adapter (not provided).

  3. At the Junos OS login prompt, type root to log in. You don't need to enter a password. If the software booted before you connected the laptop or desktop to the console port, you might need to press the Enter key for the prompt to appear.
    login: root
  4. Start the CLI.
    root@% cli
  5. Enter configuration mode.
    root> configure
  6. Add a password for the root administration user account.
    [edit]
    root@# set system root-authentication plain-text-password
    New password: password
    Retype new password: password
  7. (Optional) Configure the name of the switch. If the name includes spaces, enclose the name in quotation marks (“ ”).
    [edit]
    root@# set system host-name host-name
  8. Configure the IP address and prefix length for the management port on the switch. On the QFX5130-32CD, the management port re0:mgmt-0 is the lower RJ-45 port on the right side of the port panel and is labeled MGMT.Note

    Although the CLI permits you to configure two management Ethernet interfaces within the same subnet, only one interface is usable and supported at any point of time.

    [edit]
    root@# set interfaces re0:mgmt-0 unit 0 family inet address address/prefix-length
  9. Create a routing instance.
    [edit]
    root@# edit routing-instances mgmt_junos
    root@# set routing-instances mgmt_junos routing-options static route 0.0.0.0/0 next-hop 10.102.70.254
  10. Configure the static routes to remote prefixes.
    [edit]
    root@# set routing-options static route remote-prefix next-hop destination-ip
  11. Enable the management instance.
    [edit]
    root@# set system management-instance
  12. Enable Telnet service if needed.
    [edit]
    root@# set system services telnet
    Note

    When Telnet is enabled, you cannot log in to the QFX5130-32CD through Telnet using root credentials. Root login is allowed only for SSH access.

  13. Enable SSH service.
    [edit]
    root@# set system services ssh
  14. To allow users to log in to the switch as root through SSH, include the root-login statement.
    [edit system services ssh]
    root@# root-login (allow | deny | deny-password)
    Note

    By default, users are not allowed to log in to the switch as root through SSH.

  15. Commit the configuration. Your changes become the active configuration for the switch.
    [edit]
    root@# commit