Storm season is back, bringing with it the potential for significant weather events. If you have clients in areas prone to infrastructure disruption, visit the Disaster Recovery Resources guide for preparedness information. Datto recommends performing proactive disaster recovery testing to mitigate potential downtime. See our articles about the importance of disaster recovery testing and Preparing For A Cloud Virtualization Test: Policies, Procedures, And Partner Responsibilities to learn more. For live updates, follow @datto on Twitter.

Configuring and Administering Your Managed Power Device

Follow

Topic

This article describes the process to manage your Datto Managed Power unit through the Datto Networking portal.

Environment

  • Datto MP60

Overview

1. To access your Managed Power unit, navigate to the Datto Partner Portal in a web browser, and log in with your partner credentials. Click Status → Networking Status, as shown in Figure 1.

Figure 1: Networking Status (click for larger image)

2. Select the Account and Network associated with your Managed Power unit.
3. Select Power.
4. You will see a list of Power Devices. Select the power device you would like to manage.

Figure 2: Selecting an MP60 in the Datto Managed Networking portal (click for larger image)

5. You will see the Power Device Status page shown in Figure 3.

Figure 3: Power Device Status (click for larger image)

The Power Device Status page displays the following information:

A. Device Name: Lists the user-friendly name of the Managed Power unit. Click the edit icon to change the device's name.
B. Device Information: Displays system information about your Managed Power unit. The information shown is:

• Last Checkin: Displays the last time the power device checked in with Datto's monitoring servers.
• Uptime: Provides system uptime since the power device's last reboot.
• Model: Lists the power device's specific hardware mode.
• MAC: Displays the power device's unique MAC address.
• Firmware Version: Provides the firmware version of the power device's onboard software.
• Connection Type: Indicates whether the power device is connected to the local network via Ethernet or WiFi.
• IP: Displays the IP address of the power device.
• Surge Protection: Indicates whether the power device's surge protection features are on or off.

C. Total Power Strip Consumption: Displays a live graph detailing per-outlet power consumption. Mouse over any section of the report for detailed information.
D. Ping Test: Allows you to perform ping tests from the power device to a specified destination. See the Ping Test Power Cycle section of this article for more information.
E. Port Management: Enables an operator to perform the following management actions on a per-outlet basis:

• Label: Allows you to apply a descriptive name to each outlet, so that you can more-readily identify the type of device connected to it.
• Power Enabled: Checking this box powers the selected on. Unchecking the box will immediately power the outlet off.
• Actions: If an outlet has its power enabled, the Power Cycle action will allow you to cycle the power for a specific outlet off and then back on. The Power Cycle action will be unavailable if power to the outlet is not enabled. 
• Power Cycle Delay: Allows you to define in seconds when an outlet will power back on when it has been power cycled. 
• Ping Test Power Cycle: Allows you to automatically have the Managed Power unit reset a power if it determines it cannot reach a particular site or host. See the Ping Test Power Cycle section of this article for more information.

F. Scheduled Activity: Allows you to enable, disable, or power cycle one or more ports on the power device on a designated, recurring schedule. Click Add Action to save the action to the Currently Scheduled Actions queue.
G. Currently Scheduled Actions: Lists scheduled actions created through the Scheduled Activity interface. Click the gear icon next to each action to remove it.

Ping Test Power Cycle 

Overview

The Ping Test Power Cycle feature allows you to configure the power device to reset an outlet automatically if it determines that it cannot reach a particular site or host. A common use case would be to proactively reset a modem or router, but you can also use this feature to reset any other type of unresponsive device.

Procedure

1. Each port in the Port Management interface has a dropdown in the Ping Test Power Cycle column, from which you can select a pre-defined ping test, as shown in Figure 4. By default, the None value is selected, meaning no action will be taken if a test fails. Use the dropdown to select a list, which the power device will check against, and determine if that port should be reset if the ping test fails.

Figure 4: Port Management interface with Ping Test Power Cycle dropdowns highlighted
(click for larger image)

In the above example, the operator has applied the "Default List" to Port 1, the router. Every 5 minutes, the power device will ping the hosts on that list. If the test fails, the appliance will power cycle the router. If any of the pings are successful to any of the hosts on the list, no action is taken, and the test will repeat in 5 minutes. If the ping test fails and the router is rebooted, the appliance will try again in 5 minutes. After 5 consecutive reboots, the Managed Power unit will stop power cycling the port.

2. You can create up to six custom ping test lists by clicking the Ping Test link in the Manage pane. Each list requires one host, and can have up to four hosts. When creating lists, ensure that the host entries are correct and will respond to pings. A host can be any device that is plugged in to the power device which is capable of responding to pings. 

Figure 5: Customizing ping test lists (click for larger image)

You can also configure the following Ping Test Settings that will applied to all ping tests:

A: Power cycle if: This can be either when all hosts fail, or any host fails.
B: Power cycle after: Allows you to define that a ping test will power cycle an outlet after a specified number of fail tests.
C: Time between tests: Allows you to define how many minutes are in-between one test and another.
D: Stop testing after: Allows you to state that, after a set number of consecutive power cycles, all testing will cease.
E: Skip test during maintenance window: If set to Yes, all tests will not run during the maintenance window set for your network. This ensures that routine upgrades or other maintenance will not generate failed ping tests and unwanted port resets.


Was this article helpful?

0 out of 1 found this helpful

You must sign in before voting on this article.

Want to talk about it? Head on over to our Community Forum!