Power Cycle a Switch Port by PoE

Power cycling a Power over Ethernet (PoE) port on a RUCKUS ICX switch involves turning off and then turning on the power supplied to the port. Using the Cycle PoE option in the RUCKUS One web interface, you can enable or disable a PoE port on a switch.
To provide an overview of a feature and its benefits. May require several Concept topics to keep content in short, manageable, and reusable chunks of content.

The intention of this new template is to outline the information that you will need to collect from SMEs and provide to readers.

NOTE: Feature Configuration / Troubleshooting are *not* part of the Feature Concept template. These templates are likely to be part of seperate task/reference templates (to be developed).

General Notes for Concept Topics:
  • Optional sections are to be used with discretion based on the feature characteristics.

Overview

This feature helps to power cycle a PoE port on a RUCKUS ICX switch in one simple operation. Using the RUCKUS One web interface, the user can execute the following operations to power cycle a PoE switch port:

  • Selecting the switch with the specific PoE port you wish to power cycle
  • Editing the port settings of the switch
  • Triggering a power cycle on a specific single port by enabling or disabling PoE
  • Triggering a power cycle on specific multiple ports by enabling or disabling PoE

Following are the benefits of power cycling a switch PoE port:

  • Helps to perform a hard reboot on the PoE-connected power devices (PD), such as Internet Protocol (IP) camera or AP.
  • The Cycle PoE option will still be available even if not all PoE-enabled ports are active or available, and you can perform a power cycle operation without manual adjustments to each port.
This section is required. Providing detailed and accurate information in the feature overview is crucial as it helps users understand the functionality, benefits, and usage of the feature. Moreover, it ensures consistency in communication across all platforms, enhancing user experience and product perception.
  • What is the name of the feature? (What do users call the feature? If the feature is referred to by an acronym, what is the acronym expansion? What is the formal name to be used in documentation?)
    Note: Typically, the name is used as part of the section titles, such as the overview title and the configuration section titles.
  • Where does the feature fit within our taxonomy? (What are the taxonomy group and sub-group? This information is important for categorizing the feature documentation and incorporating it into the existing document sets.)
  • What standard or standards govern the feature? (Sometimes needed.)
  • Is the feature a new feature or an enhancement to an existing feature?
  • Does the feature replace another feature?
  • What does the feature do? (General description)
  • How does the feature benefit the user?
  • What set of terms do the writer and reader need to know to understand the feature and its use?
  • How does the feature work? (Detailed description, if needed.)

Requirements

  • The switch port must be PoE-enabled to use the Cycle PoE option.
  • You must have RUCKUS One administrative access to the switch and necessary administrative permissions to make changes to the switch configuration.
  • The switch must be in the Operational state (meaning, not in the Never contacted the cloud or Disconnected states).
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no requirements, use the following default wording:

This feature has no special hardware or software requirements for feature enablement or usage.

If there are requirements, include the applicable below points (depending on product line):

  • What releases support the feature?
    Note: Typically, this is not documented in the configuration guides; however, we need to know where to include the information.
  • What hardware models support the feature?
  • Does the feature require specific modules?
  • Does the feature run only on certain ports?
  • Does the feature have special memory requirements?
  • In an integrated system, can the feature be managed or configured from another device? What are the related release and system requirements?
  • Does the feature introduce new user requirements?
  • Does the feature introduce physical or location-based requirements?

Considerations

  • When configuring power cycling on multiple switch ports, if all the PoE-enabled ports are either disabled or unavailable (the device is not PoE-compatible), then the power cycle operation cannot be performed.
  • When configuring power cycling on multiple switch ports, if at least one PoE-enabled port is enabled or available, then Cycle PoE option will be available and will skip invalid ports.
  • The power cycle operation will only affect ports that are both PoE-enabled and have a valid PoE device connected, and will skip all other ports not meeting these criteria.
  • If a single port or multiple ports are initially set as PoE Enabled, the Cycle PoE option will be available.
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no considerations, use the following default wording:

This feature has no special considerations or limitations pertaining to feature enablement or usage.

If there are considerations, include the applicable below points (depending on product line).

Note: A separate section on Limitations may sometimes be needed.
  • Does the feature replace an existing feature?
  • Does the feature work only with a certain protocol or with a limited set of protocols?
  • Is the feature meant to be used in combination with another feature or a set of features?
  • Is the feature incompatible with any features?
  • What happens when the feature is enabled?
  • What happens when the feature is disabled?
  • Does enabling/disabling the feature enable/disable another feature?
  • What system behavior changes, if any, does the feature introduce?
  • Are performance issues associated with the feature? How can these be mitigated?

Best Practices

Monitor the power cycling process on the power devices (PD) and check that the operation completes successfully.

This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no best practices (recommendations), use the following default wording:

This feature has no special recommendations for feature enablement or usage.

If there are considerations, include the applicable below points (depending on product line).

  • Brief list of RUCKUS recommendations on product use to optimize performance.

Prerequisites

Ensure that you have valid PoE ports to perform the power cycle operation on a RUCKUS ICX switch.

This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

If there are no prerequisites, use the following default wording:

This feature has no prerequisites to feature enablement or usage.

If there are prerequisites, include the applicable below points (depending on product line).

Note: This section is sometimes part of a general overview and sometimes part of a configuration overview.
  • What are the task prerequisites that the user must ensure are met,for configuration? (For example, must you be running certain protocols, or must you configure other features first?)
Parent topic: harp://6a7214064c282d8ad6c44b90/pr/ORIGINAL/RUCKUS%20One%20Online%20Help_v7_GUID-9D6AEC5D-ECCB-4BE1-8654-7EBA84E164C7/Resetting%20a%20PoE%20Switch%20Port%20Using%20Power%20Cycling=GUID-AD6ABF7C-59A8-4C2E-8C1F-648DFF73E0A6=1=en-US=.xml