Gaining Access to the QFabric System Through the Default Partition
This topic explains how to log in to the QFabric system default partition so you can access the Junos OS command-line interface (CLI) and configure the system.
Before you access the QFabric system default partition:
Install the QFabric system hardware components, including connecting the network and power cables.
Convert any QFX3500 and QFX3600 standalone devices to node-device mode.
Connect all components to the control plane Ethernet network.
Turn on the Director group and run the initial setup script. Remember to write down the IP address of the default partition, which must be on the same subnetwork as your management network.
To access the default partition:
- Open an SSH connection to the QFabric default partition.
Use the IP address you set for the default partition as part of the
QFabric initial setup procedure. In your network, you can simplify
access to the QFabric system by mapping the default partition IP address
to a name.
[root@customer ~]# ssh root@192.168.1.49Last login: Fri Sep 2 21:34:54 2011 from customer Juniper QFabric Director 11.3.5043 2011-08-26 18:05:21 UTC RUNNING ON DIRECTOR DEVICE : dg1 root@qfabric>
Note The QFabric system is load balanced, so the CLI session might be hosted on either Director device DG0 or DG1.
- Enter configuration mode (the default mode in the QFabric
system is configure private), configure a root password
and hostname for the default partition, and assign QFabric administrator
privileges to the root user.
root@qfabric> configurewarning: Using private edit on QF/Director warning: uncommitted changes will be discarded on exit Entering configuration mode [edit]
root@qfabric# set system root-authentication plain-text-passwordNew password: My-Password Retype new password: My-Password
root@qfabric# set system root-authentication remote-debug-permission qfabric-adminroot@qfabric# set system host-name my-qfabric[edit]
root@qfabric# commitcommit complete [edit] root@my-qfabric#
- Configure your QFabric system as needed. You can configure routing protocols, interfaces, VLANs, and other features as needed. Keep in mind that interfaces require the four-level interface naming convention (device-name:fpc/pic/port).