Powering Off a QFX3008-I Interconnect Device


To gracefully shut down a QFX3008-I Interconnect device on a QFX3000-G QFabric system:

  1. Log into the QFabric default partion on the Director device and start the CLI.
  2. Discover the device connection status and the alias name (identifier) by issuing the show fabric administration inventory command.

    The Interconnect device must show as connected and configured in order to have an orderly shutdown.

  3. Start the orderly shutdown of the QFX3008-I Interconnect device by issuing the request fabric power-off interconnect-device serial-id | alias-name operational mode command from the QFabric default partition CLI. This command systematically takes the interconnect offline and gracefully shuts down the device while preserving system state information. A message appears on the console or console log, confirming that the operating system has stopped on the device.

    You see output similar to the following after entering the command:


    The final output of the request fabric administration power-off interconnect-device command is the following message: The device is shutting down and can be removed when the LCDs are off. Wait at least 3 to 4 minutes after first seeing this message before following the instructions in Step 5 to power off the device.

  4. Attach the ESD grounding strap to your bare wrist, and connect the strap to the ESD point on the chassis.
  5. Set the wiring tray switch to the OFF (O) position. Observe the wiring tray LEDs. The power supply LEDs should turn off (appear unlit). Repeat this step for the second wiring tray.

After you power off a wiring tray, wait for at least 60 seconds before you turn it back on. After you power on a wiring tray, wait for at least 60 seconds before you turn it back off.


The power supplies in a QFX3008-I Interconnect device continue to use a small amount of power when the C19 wiring tray power switch is in the off position. The status LEDs on each power supply blink amber because the power supply fans are not operating. This is expected behavior.