Table of Contents. Web Power Switch For Power over Ethernet

Transcription

1 Web Power Switch For Power over Ethernet June 2016 Congratulations on purchasing the best network controlled power switch available. The iboot-poe provides you the ability to reboot crashed devices with the click of a mouse. Be sure to read up on all the features of the iboot-poe Including: PoE Extender or PoE Injector Function PoE Plus (802.3at) Compliant 25.5 Watts Maximum Web Based setup and control Automatic Reboot using AutoPing and Traffic Monitor. Event Scheduling for real-time power control. Telnet setup and control Management Utility: Easy Setup, Firmware upgrades and Reset to Factory Default iboot Cloud Service: Control all your iboots from one web portal. Table of Contents 1. General Description 2 2. Hardware Installation 5 3. Initial Configuration 7 4. Web Browser Operation Web Setup iboot Cloud Service Command Line Interface DxP Protocol Firmware Upgrades Troubleshooting Specifications Technical Support and Warranty 31

2 1. General Description The iboot-poe is a network attached, IP addressed, web controlled Power Over Ethernet (PoE) power switch. Anyone with a web browser can access iboot-poe to perform power On, Off or Power Cycle (Reboot). iboot-poe uses two levels of password for security. iboot-poe has a web server built in, as well as the ability to be managed through the iboot Cloud Service. A simple Web browser interface makes it easy to control power from anywhere in the world with a click of a mouse. iboot-poe also supports Telnet for text commands, as well as Dataprobe s Exchange Protocol (DxP) for interfacing to a variety of Dataprobe products and custom software development Uses for iboot Automatic reboot of PoE devices Cameras, Access Points, Phones, etc. Range Extender Add 100 meters to PoE runs PoE Injector When used with Power Supply PS-WRI-7 iboot-poe is a complete PoE injector with reboot. The external power supply can also function as back-up power in the event that the PoE power fails. iboot-poe_v160616e iboot-poe Page 2

3 1.2. Automatic Reboot iboot-poe provides two ways to monitor your application and provide automatic reboot when configurable conditions are met AutoPing The AutoPing feature allows iboot-poe to automatically detect failed equipment and perform a timed reboot or other power control function. You set one or two IP addresses to be periodically pinged. When iboot-poe no longer detects a response from these addresses, the programmed power control function is actuated. The two addresses can be AND or OR linked so that both (AND) or either (OR) need to fail in order to take the selected action. With AutoPing, it is also possible to turn ON or OFF the PD when the trigger conditions are met. See Section 5.5 On AutoPing Setup Traffic Monitor Traffic Monitor measures the bandwidth utilization and reboots the PD when the utilization is too low or too high. It is specifically designed to support high speed access points that crash or degrade over time and need a quick reboot to get up and running properly. In addition to setting minimum and (optionally) a maximum traffic, settings allow for monitoring of the Uplink and/or Downlink, and to disable the traffic monitoring function at specific times of the day, like when your coffee shop is closed. See Section 5.5 on Traffic Monitor Setup Scheduling Scheduling provides calendar based control of power, to power up or down devices as needed, or to provide regular reboots to insure proper operation. See Section 5.6 iboot-poe_v160616e iboot-poe Page 3

4 1.3. Automatic Self Configuration In most cases, the iboot-poe will identify all the network elements required to configure itself for automatic monitoring and rebooting of a typical PoE environment. The unit will identify the following: Network Router to obtain an IP address and additional settings for proper network configuration. (DHCP) Downstream PoE device IP address for self-setup of AutoPing monitoring of the PD for automatic reboot when the PD fails. In cases where there are multiple IP addresses on the PD side, as when used to protect a network access point, the iboot-poe will self-configure for bandwidth monitoring to determine when an automatic reboot is necessary. In order for this discovery and self-configuration to take place, the proper installation sequence must be followed. See Section 2.1 for auto configuration procedure Multiple Control Options In addition to the Web control capabilities, iboot-poe features several other means to operate automatically or under computer control. URL Control: You can send a single URL to the iboot-poe containing all the information necessary to query or change the power status. This makes it easy to create a single button on your desktop or embed into a batch file or script. AutoPing: The AutoPing feature allows iboot-poe to automatically detect failed equipment and perform a timed reboot or other power control function. You may set 1 or 2 IP addresses to be periodically pinged. When iboot-poe no longer detects a response from the address(es), the programmed power control function is actuated. Traffic Monitor: In situations where AutoPing is not possible, the iboot-poe provides a traffic monitoring feature that can identify slowdowns or failures in bandwith throughput and auto-reboot when user specified conditions are met. Telnet: iboot s Command Line Interface (CLI) allows direct control and setup through Telnet. Dataprobe Exchange Protocol: iboot-poe supports the Dataprobe Exchange Protocol (DxP) This protocol allows Dataprobe products to communicate across networks, and allows developers to design custom applications to integrate iboot-poe into unique applications. For more information about DxP, contact Dataprobe Support team (support@dataprobe.com). iboot-poe_v160616e iboot-poe Page 4

5 2. Hardware Installation 2.1. Auto Configuration Sequence In most cases, the iboot-poe can completely configure itself on initial installation to identify all network elements and automatic reboot of failed devices. For the best results follow this sequence when installing the iboot-poe for the first time. 1. Connect the OUT connection of the iboot-poe to the PoE powered device to be controlled 2. Connect the IN connection of the iboot-poe to the Network Switch 3. Connect the Power Supply to the iboot-poe when used as an injector Auto Configuration takes approximately 30 seconds. discoverable. During this time, the unit is not accessible or To install the iboot-poe without using the Auto Configuration feature, power up the iboot-poe either by connecting it to the PSE or with the power supply, for at least 30 seconds before connecting the PD to the OUT connector. The iboot-poe will still use DHCP to configure the network if the router supports it. No automatic reboot functions will be enabled. Auto Configuration can also be initiated via the web page setup. See Section Hardware Connections iboot-poe supports 10/100/1000 Ethernet using the cable supplied, or other suitable unshielded twisted pair (Cat 3-6) cabling. It is compliant with IEEE 802.3af and 802.3at for devices up to 25.5 Watts. When Used as a Range Extender In this mode, an external device supplies the power for both the iboot-poe and the Controlled device. Connect the Out connector to the PoE Device to be controlled (PD); Camera, Access Point, Phone, etc. Connect only PoE compatible devices. Connect the IN connector to the PoE Power source (PSE); PoE Switch, Midspan or Injector iboot-poe_v160616e iboot-poe Page 5

6 When Used as a PoE Injector In this mode, the separate power supply PS-WRI-7 supplies power to both the PoE and the Controlled Device. Connect the OUT connector to the PoE Device to be controlled (PD); Camera, Access Point, Phone, etc. Connect only PoE compatible devices. Connect the IN connector to the network router or switch. Then connect the power supply to the iboot-poe. Ethernet LED Displays IN connector Green LED indicates Network Activity Amber LED indicates 1000Mbps Speed OUT connector Green LED indicates Network Activity Amber LED indicates PoE power being used by the PD 2.3. Power Connection When Used as a Range Extender Power is supplied by the Power Source Equipment (PSE) on the IN connector. No external Power Supply is necessary. When Used as a PoE Injector Use only Dataprobe model PS-WRI-7 to power the unit. With either a proper PSE connected to the IN jack, or the PS-WRI-7 powering the unit, the PWR IN LED will be on. With both a PSE and PS-WRI-7 connected to the iboot-poe, the unit will take power from the external power supply Mounting Options iboot-poe is suitable for desktop, shelf or wall mounting. Two screw holes on the housing can be used to secure the iboot-poe to a suitable surface. Insure that the screw heads do not interfere with the attachment and disconnect of the network cables. iboot-poe_v160616e iboot-poe Page 6

7 3. Initial Configuration 3.1. DHCP Configuration If your network supports Dynamic Host Configuration Protocol (DHCP), the iboot will be automatically assigned an IP Address and be ready to use. You can discover the IP Address through your Server/Router, or use Dataprobe s Device Management Utility (DMU). If your network does not use DHCP, the iboot-poe will default to IP Address Device Management Utility The DMU is available online at dataprobe.com/support-documents/iboot-poe/, provides the easiest means to find and configure your iboot-poe for use. It can: Discover all the iboots on your network, Display the current IP address of each Allow setting of an IP address Reset to Factory Defaults Upgrade the Firmware of the iboot-poe Obtain and use the DMU: 1. Download the latest version of the DMU at dataprobe.com/support-documents/iboot-poe/ Run DMUSetup.exe 2. Run the DMU DMU Discovers Dataprobe Devices on your Network Note: The IP address can only be set within the first two minutes of powering up the iboot-poe or pressing the reset button (see Section 10). The DMU will only work with iboots on the same physical subnet as the PC. Once the DMU is run, click on Device Discover to display all the iboots on your local network. The DMU will display the Location Name of the iboot, The product ID and Version Number, the current IP Address, and the MAC Address. Factory defaulted iboots will display with the name New iboot-poe and have the factory default IP address of , or as set by DHCP. Enter New IP Address for iboot-poe The IP address field also indicates the port for web access that is used by the iboot. The standard port for web browser control is factory default Port 80. iboot-poe_v160616e iboot-poe Page 7

8 Change the IP Address 1. Click on the row containing the iboot-poe to be set. The row will become highlighted. 2. From the menu select Set Network Settings 3. Select Static from the IP Mode box to manually enter the Address setings 4. Enter the new IP Address, Subnet Mask, Gateway and DNS addresses into the form. 5. Click OK when done. 6. A confirmation box is displayed. Click OK to clear the box. Once the IP Address is set, other all other operational features of the iboot-poe can be set up. Click on Discover again to refresh the display, highlight the desired iboot-poe and click on Manage Launch Browser. See Section 5 to configure the iboot. The DMU can also be used to return an iboot-poe to its Factory Default condition. This can be used to recover an iboot-poe with a lost password. Highlight an iboot-poe from the display and select Set Factory Defaults. This must be done within the first two minutes of powering up the iboot or pressing the reset button. Get all the details on the DMU at Other ways to set the IP Address 1. Web Browser via the Set-up Page See Section 5 2. Command Line Interface See Section Automatic Configuration Automatic Configuration provides the quickest and easiest way to get your iboot-poe up and running. It diagnoses the installation environment and pre-sets the Automation section based on the application. The iboot-poe will self-configure for automatic reboot under the following conditions: Factory New Install See Section 10 Factory Reset Install Manually enabling Auto Configure from the Automation web page Manually enabling Auto Configure from the CLI command The steps the iboot-poe uses for Auto Configuration are as follows 1. Establish IP credentials on the network using DHCP (if not already established) 2. Listen on the OUT connector for activity for up to 30 seconds 3. Set either the AutoPing or Traffic Monitor active o Set AutoPing if only 1 IP Address is discovered This would be typical of a camera, phone or security system installation o Set Traffic Monitor if multiple IP Addresses are discovered This would be typical of an access point application The following are the standard settings that will be used for self-configuring AutoPing and Traffic Monitor. All these settings can be changed with either the web setup or Command Line Interface. See Section 5.5 for an explanation of these settings. AutoPing Setting Address: IP Address of PD Freqency: 10 Seconds Fail Count: 3 Mode: Single Action: Cycle Restart: 10 Seconds iboot-poe_v160616e iboot-poe Page 8

9 Traffic Monitor Settings Fail Time 10 Seconds Restart Time 10 Seconds Number of Cycles 1 Minimum Traffic 0Kbps Monitoring: Uplink only Max Bandwidth Test: Disabled Daily Disable: Disabled iboot-poe_v160616e iboot-poe Page 9

10 4. Web Browser Operation 4.1. Password Protection iboot-poe uses two username/password credential sets, one for power control only (User) and one that also provides access to the setup functions (Admin). This configuration can be changed to require Administrator credentials at all times or allow unsecured User level control. See section 5.7. Default Credentials: Role Username (fixed) Password (settable) Administrator admin admin User user user Open your browser and enter the IP address of iboot-poe into the address bar. That address will either be the one assigned by your DHCP server, one that it was manually changed to or the default IP Address Enter the username and password when prompted. When the proper username/password is received the Control and Status Page is displayed. iboot-poe uses an inactivity timer for security. This timeout is user selectable from 0 to 99 minutes. Setting to zero disables the timeout feature. When there is no activity for the set time in minutes, the user is automatically logged out and the username and password will need to be entered again for access. This is to prevent accidental lockout by leaving the user logged in. As the iboot-poe allows only one Web user logged in at any time, use caution when disabling the timeout feature, as it is possible to lock out other users by forgetting to logout. Closing the browser will not log the user out and will lock out web access. If you do become locked out, access the iboot-poe via Telnet and reboot the unit, or press the reset button (see Section 10) Mobile Browser Support The standard web pages illustrated in this manual are for screen sizes 700 pixels wide and greater. For devices with screen widths below 700 pixels, the iboot-poe uses a set of mobile browser pages. The iboot-poe automatically detects the screen size and redirects automatically to the mobile pages. The mobile pages do not support the setup functions. To access the setup functions, or to view the full desktop site, click on the Full Site button. iboot-poe_v160616e iboot-poe Page 10

11 4.3. Control and Status Page Once the user is validated, the Control and Status page is displayed. (Only one person can be connected to the iboot-poe at a time.). This page provides automatic updates every 5 second. To control the power, click on the appropriate button. During power cycling, the Power Status bar will indicate the temporary status, with a blue background. Once the cycle is complete, the status bar will revert to its original condition. To abort a power cycle, click on either Power On or Power Off buttons. If the AutoPing and/or Traffic Monitor features are in use, the page will also display the current status, OK or Failed, for each, with a counter of how many times action was triggered. If connecting with the Admin credentials, reset buttons for the Trigger counter is provided. If the iboot-poe is connected to a time server (see Section 5.4), The Home page will also show the five most recent history events, including the Outlet, Action, User and Time/Date of each event. The iboot-poe holds the last 32 events in memory. The user can access a complete history webpage, download the history in a.csv file, or clear the history. Navigation Buttons: Refresh: Use the Refresh button to obtain the latest status of iboot. Using your browser's refresh button can lead to inadvertent power switching. If an NTP server is being used, the time of the last refresh will be shown in the upper right corner. Setup: To access the Setup page, the administrator credentials are required. When logged in as User, the challenge for Administrator credentials will be displayed. Logout: When you are finished with iboot, click on Logout. A Goodbye page will be displayed. This page has a URL link to re-connect with the iboot. The linkback URL is user settable. If no linkback is set, the hyperlink will be the unit s IP Address. iboot-poe_v160616e iboot-poe Page 11

12 4.4. URL Control iboot-poe can be controlled directly by sending a completely formed URL through a browser window or HTTP command. The URL syntax for control is: Where: <address> = <status> = <time> = <user> = <password> = the IP Address of the device, or DNS name that resolves to the IP Address, plus any HTTP Port if not standard 80 The status to change the outlet to: 0 = Off 1 = On 2 = Query only, no outlet change The amount of time to maintain that condition (optional). Will return to initial state if used. user or admin depending on password used password associated with user Syntax notes: The order of the variables is not significant. The user and password are not required when Auto-Login feature is enabled (see Section 5.7 for security options. Examples: Turn the outlet on for the default user. Reboot for 5 seconds with Auto-Login Return status using http port 8080 URL Command Responses iboot-poe will return an response to a URL command as follows: <location id> <status> The full http response is <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" " <html xmlns=" <head> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <title>iboot Status</title> </head> <body> <locationid>iboot-poe</locationid> <status>off</status> </body> </html> Security Note Please note that URL commands are sent in clear text and this technique will expose security credentials. Use only where this is not a concern. iboot-poe_v160616e iboot-poe Page 12

13 5. Web Setup iboot-poe setup section consists of several pages. Access any page via the buttons on the left of the page. Each time a setting is changed click on the Save button for that page to save the changes before moving to the next page. To return to the control page, use the Status / Control button Device Settings Location ID: Set a 20 Character name to be displayed on the top of the Home page. This assists in identifying which iboot-poe is being accessed. Cycle Time: 1 to 999 seconds power cycle time. This is the length of time the power will be off during a reboot, or on during a power burst. Initial State: The outlet can be set to the state it will assume when the iboot-poe is powered up or reset. The choices are: On, Off and Last, meaning the state it was in when the power was removed or reset commenced. Upgrade Enable: Check this box to allow remote firmware upgrades of the iboot-poe. When this box is unchecked, firmware upgrades will not be allowed. Auto Logout: This setting sets the automatic logout for inactivity on both the web and telnet users. It can be set from 0 to 99 minutes. 0 disables the Auto Logout feature. As the iboot-poe allows only one Web user logged in at any time, use caution when disabling the timeout feature, as it is possible to lock out other users by forgetting to logout. Closing the browser will not log the user out and will lock out web access. If you do become locked out, access the iboot-poe via Telnet and reboot the unit, or press the reset button Network Settings IP Mode: Select Static to set the IP address using the fields below, or DHCP to allow a DHCP server to set the IP Address. IP address: Enter a static IP address. This will be automatically set if using DHCP Subnet Mask: Enter the Subnet Mask. This will be automatically set if using DHCP Gateway: Enter the Gateway. This will be automatically set if using DHCP DNS: Enter the Domain Name Server address. This will be automatically set if using DHCP. iboot-poe_v160616e iboot-poe Page 13

14 5.3. Advanced Network Settings HTTP Port: This setting is used to allow access to iboot-poe on a port other than the Web standard Port 80. If the port is changed, you will need to identify the port number when you enter iboot's IP address into your browser. If the new port is 8080 then use the address Linkback URL: This setting allows control of the hotlink displayed on the Goodbye page. It allows use of the public IP address or DNS name instead of the internal IP Address of the iboot-poe, which is the default setting. If this setting is left blank, the hotlink will be the IP Address of the unit. Enter up to 128 characters. Telnet Port: This setting is used to allow access to the iboot-poe via telnet by ports other than standard 23. DxP Port: This setting is used to allow access to the iboot-poe via Dataprobe Exchange Protocol (DxP) via ports other than standard Enable Cloud Services: This setting enables the iboot for iboot Cloud Services (ibcs). ibcs allows the iboot to be monitored and controlled from a web portal from any browser. It allows multiple iboots to be managed from a single portal. For a complete description of ibcs and setup instructions, see Section 6. Note: Some of the TCP/IP Settings require a reboot of the iboot-poe, after clicking Save. A Reboot button will appear at the bottom of the page when it is necessary. The new settings will not take effect until the unit is rebooted. Reboot will not affect the power position of the iboot-poe. Upon Clicking Reboot, the Googbye page is displayed with a link to re-login Time Setup The Advanced Network Setup page also allows setup of the Time server, required for Scheduling and Logging functions. Enable: Enable or Disable the use of the Time Server with this checkbox Time Server: Enter the Time Server. The default is time.nist.gov Time Zone: Enter the Time Zone (-12 to +12) relative to GMT DST Enable: Enable or Disable the use of Daylight Savings Time with this checkbox DST Start / Stop: Enter the start and stop parameters of Daylight Savings Time here. iboot-poe_v160616e iboot-poe Page 14

15 5.5. Automation Automation settings page shows the current status of the AutoPing and Traffic Monitors that are set. It also allows Automatic Configuration of these settings. The Traffic Monitor shows the current throughput. This will update each time the Refresh button is pressed. To have the iboot-poe re-examine the network and auto-set the automation capabilities, press the Auto Config button. AutoPing Two separate Auto Ping addresses can be set with And/Or logic. Address: Enter the IP address of the device, or domain name to be pinged. To enter the second address and settings, select AND or OR for the A/B Logic. Ping Frequency: Enter 1 to 999 seconds. The ping will go out to the selected device this often. Fail Count: Enter times the ping needs to fail consecutively before the selected action is taken. When the fail count has been reached, the AutoPing action will be triggered. Mode: Select from Single, AND, OR. With AND, both AutoPings need to exceed their fail count to trigger the Action. With OR, the Action will be triggered if either AutoPing fails. Action: Select from None Power On Latch Power On Follow Power Off Latch Power Off Follow Cycle Cycle Times AutoPing is paused. No Ping tests will be performed. Upon triggering, iboot-poe will power on and remain so until changed via the web, telnet, DxP, etc. Upon triggering, iboot-poe will power on. When the ping response returns, iboot-poe will power off. Upon triggering, iboot-poe will power off and remain so until changed via the web, telnet, DxP, etc. Upon triggering, iboot-poe will power off. When the ping response returns, iboot-poe will power on. Upon triggering, iboot-poe will cycle the power. If Power Cycle does not result in the ping response the iboot-poe can cycle again. The number of times the iboot-poe will cycle is set by the Cycle Times setting. To have the iboot cycle power 3 times to get the system to respond again, set the Cycle Times to 3. Restart: This setting delays the restart of the AutoPing tests after the Action is completed. This setting allows time for the boot sequence of the failed device to complete. iboot-poe_v160616e iboot-poe Page 15

16 With AutoPing operational, the main iboot-poe page will display the current status of this feature. The status will be OK to indicate that iboot-poe is receiving responses to the ping, or that the fail counter has not yet been exceeded. If the fail count has been exceeded, the status will change to FAIL. The Trigger Counter indicates the number of times the AutoPing action has been triggered. A counter reset button is provided. Note: All of the AutoPing Settings require a reboot of the iboot-poe, after clicking Save. A Reboot button will appear at the bottom of the page. The new settings will not take effect until the unit is rebooted. Reboot will not affect the power position of the iboot-poe. Upon Clicking Reboot, the Goodbye page is displayed with a link to re-login. Traffic Monitor Traffic Monitor continuously samples the data throughput between the PD and the PSE and will provide automatic reboot when the data rate drops below a set point. It can also set a Maximum rate for reboot, plus time of day settings to temporarily disable the Traffic Monitor on a daily basis. Traffic Monitor Enable: Enable or disable the Traffic Monitor Service. Fail Time: Set the time, in seconds that the set rate must be measured before the reboot occurs. Restart Time: Set the time in seconds after reboot that the Traffic Monitor will begin again to measure traffic. Subsequent reboots will occur when the time equals the Restart Time plus the Fail Time. Number of Cycles: Set the number of reboots to attempt for a single failure event. Minimum Traffic: Sets the minimum data rate to trigger the Traffic Monitor. Can be set in Kbps or Mbps Monitoring: Set whether the Traffic Monitor looks at the Uplink (PSE to PD), Downlink (PD to PSE) or both. Each direction is independently monitored and the Minimum or Maximum setting is per direction. Maximum Bandwidth: Test Enable: Enable or disable maximum bandwidth triggering Maximum Bandwidth: Set the maximum data rate to trigger the Traffic Monitor. Can be set in Kbps or Mbps. Daily Monitor Disable: Set the start time and stop time for disabling the Traffic Monitor. Settings are in 24 hour format HH:MM Event Scheduling iboot-poe can schedule up to eight reoccurring power events. Set the starting date and time, plus the action to be taken and any repeat cycle for each. To enable the time scheduling function set the network time server in Advanced Network Setup, Section 5.3. Once the time server is active, scheduled events can occur. Up to eight independent scheduled events can be programmed. iboot-poe_v160616e iboot-poe Page 16

17 Date: Set the initial date for the event. The format for the date is mm/dd/yyyy. Time: Set the initial time for the event. The format for the time is hh:mm with hours in 24 hour format. Repeat: Set the repeat multiplier, if desired. Set the number from 0 to 999 and either Days, Hours, or Minutes. To have the schedule repeat every two days, set this number to 2. Action: Set the event Action; On, Off or Cycle. Hold/Run: Click Hold to pause the scheduled event. Click Run to re-start the scheduled event. Clear: Delete the scheduled event. Click Save to save the current settings. Click Reset to delete any unwanted changes Password Settings The iboot-poe supports three modes of user and password operation. Login Required: This mode supports both User and Admin users. Each user has a settable password. Auto Login: This mode does not require a username of password for the User level operation. No login challenge will be required for any mode of operation, until any setup function is requested. The Admin username and password is required for any admin functions. User Disabled: There is no User account. The Admin username and password will be required for operation and setup functions across all modes of operation. This is the factory default mode. Two passwords are used by iboot. In the Login Required mode, The User Password allows access to the control of iboot, but not to the Setup functions. Clicking on the Setup button allows the Administrator to log in. Passwords can be up to 20 characters long and are case sensitive. Enter the current password then the new password twice to confirm. Default Credentials Role Username (fixed) Password (user set) Administrator admin admin User user user iboot-poe_v160616e iboot-poe Page 17

18 6. iboot Cloud Service iboot Cloud Service (ibcs) allows customers with iboot to access and control multiple iboots in multiple locations from a single portal with a single sign-on. ibcs will not only make using iboots easier, by consolidating all units into one sign-on and interface, it will also enhance the number of situations where iboot can be deployed. Customers with Dynamic IP addressing will always be able to access their iboot from any location. Customers that do not allow in-bound connections can access their iboots. Service providers can manage multiple customer accounts with diverse security configurations iboot Cloud service is currently in development and is made available to our current users free of charge. Please note that as at this beta stage, service interruptions may occur or new versions of the iboot firmware may be made available and necessary to keep current with the cloud development. The full Terms of Service of the iboot Cloud Service is available here. While the Cloud Service is in Beta stage, the firmware in the iboot is fully tested and released by Dataprobe. If you do not enable the cloud capabilities of the iboot, you can expect continuous and dependable operation iboot Cloud Users Forum Dataprobe has established a special users forum for iboot Cloud Service Beta. Please use this forum to post any questions, comments and ideas about the iboot Cloud Service. Registration is required to post to the forum. Find the iboot Cloud Users Forum here ibcs Setup & Operation Use of the iboot Cloud Services requires the iboot to be configured to access the Internet. Please review the installation and configuration procedures to insure proper setup. a. Establish Account with iboot Cloud Server Visit from your browser Click on Register Complete the information Confirm Registration by clicking on the link provided in the . iboot-poe_v160616e iboot-poe Page 18

19 b. Enable Cloud Services on iboot Log into the iboot with Administrator rights Go to the Advanced Network Setup page Click on the checkbox Enable Cloud Services: Within 30 seconds, an 8 character activation code will appear. This code is also a hotlink to the Cloud Service. c. Register iboot with Cloud Account Click on the Activation code to register the iboot with the Service. You will be re-directed to the Service. Log-in with your account and the iboot will be automatically registered with your account. Alternatively, you can log in to the Service and click on Add Device and enter the activation code in the field provided. Congratulations. You are now on the cloud. d. ibcs Main Page The ibcs main web page provides a menu bar with the following options: Devices: List all registered iboot units, ordered by their Name. Click on any iboot line to manage that unit. Locations: Group all iboots by location. Click on any location to display or hide all the iboots at that location. Account: Display and edit account information and obtain account access history. Help: Links to the iboot Cloud Forum and Dataprobe support pages. iboot-poe_v160616e iboot-poe Page 19

20 e. Control Power from the Cloud The status screen will detail all the iboots registered with the cloud. You can add locations and group iboots by location. Each iboot displays the power status and AutoPing if configured. Click on the box that holds the Activation Code for the device you just entered. A modal box will appear with options to rename the device, move the device to a defined location or delete the device. Give the device a name, and Click Rename Device. The remainder of the modal is very similar to the iboot web page. Select Power ON, Power OFF or Cycle Power. f. Assign Names and Locations You can establish multiple locations and assign each iboot to a location. You can also name each iboot independently from the Device Name that is displayed on the iboot web page. To add locations, click on the Locations button on the menu bar, and then click Add Location. Name the location and click the Add Location button. iboot-poe_v160616e iboot-poe Page 20

21 7. Command Line Interface The iboot-poe Command Line Interface (CLI) provides a text based method for communicating with the iboot. The syntax of the CLI uses a basic Set (change a variable) and Get (retrieve a variable). The CLI is accessed either through the Telnet protocol, which requires a Telnet client program. Dataprobe provides a simple Telnet Client program (EZ Term) at CLI Access Open the Telnet client and connect to the IP address set for the iboot. The CLI uses the same security options as the web browser. See section 5.7 for an explanation of the options for user setup and security. When connection is successful, the User> prompt is displayed. Enter user or admin and press Enter. The prompt will change to Password>. Enter the admin or user password and press Enter. The prompt will change to iboot>. This indicates successful login. Enter commands as needed. When done, enter the logout command. Note: The telnet session will auto-disconnect if there is no activity. The maximum auto-disconnect time is 8 minutes. If the Auto-Logout setting is shorter than 8 minutes, that setting will apply. To avoid this and use a longer auto-disconnect time, use a telnet client that periodically sends a No Operation (NOP) command, like Dtelnet iboot-poe CLI Syntax Command Description Factory Default Control Commands set outlet <on off cycle> These commands are used to monitor and control the outlet. This command controls the outlet. get outlet This command returns the current status of the outlet. Device Commands These commands are available to the administrator only get location This command returns the iboot-poe s location ID. iboot-poe set location <20 char. max> This command is used to set the iboot-poe s location ID. iboot-poe_v160616e iboot-poe Page 21

22 set cycle <1-999> This command is used to set the cycle time, in seconds 10 get cycle This command returns the current cycle time set upgrade enable <yes no> Enables or disables the ability to upload new firmware to the iboot-poe. No get upgrade enable login logout reboot Network Commands get network This command displays the upload enable status. Prompts for admin credentials when logged in as user Terminates the session This command reboots the iboot-poe. All set commands require a reboot before they take effect. These commands are only available to the administrator. This command will return all the network settings as shown below: set ipmode <static dhcp> Mode: DHCP IP Address: Subnet: Gateway: DNS: HTTP Port: 80 Linkback URL: Telnet Port: 23 DxP Port: 9100 Timeout: 20 This command sets the ip address setting mode. Static mode locks the address as set, dhcp mode allows DHCP server to assign address. DHCP set ipaddress <dotted decimal> This command is used to set the iboot-poe s ip address set subnet <dotted decimal> This command is used to set the iboot-poe s subnet mask set gateway <dotted decimal> This command is used to set the Gateway set http port < > set telnet port < > set dxp port < > This command sets the port that the iboot-poe s web server listens for incoming connections on. When set to 0 the web server is disabled. This command sets the port that the iboot-poe s Telnet server listens for incoming connections on. When set to 0 the Telnet server is disabled This command sets the port that the iboot-poe s DxP protocol service listens for incoming connections on. When set to 0 the Protocol service is disabled. Note: At least one of the above MUST NOT be 0. The CLI will protect against all 3 from being set to iboot-poe_v160616e iboot-poe Page 22

23 set linkback <url> set timeout <0-99> This command sets the linkback URL displayed on the logout page. This command sets the automatic network timeout in minutes 0 = Timeout not used. 2 Automation Commands get autoping set autoping <1 2> address <dotted decimal or name> These commands require a reboot before they will take effect. These commands are available to the administrator only. This command returns all of the AutoPing settings as shown below. AutoPing 1 AutoPing 2 Address: iboot.co Frequency: Fail Count: 3 3 Status: OK OK Trig Count: Mode: Single Action: Cycle Once Wait: 2 Restart: 0 This command is used to set the address of AutoPing 1 or AutoPing 2. Use IP Address or domain name. set autoping <1 2> frequency <1-999> This command is used to set the frequency (how often the iboot-poe sends the ping) for each of the AutoPings. 10 iboot-poe_v160616e iboot-poe Page 23

24 set autoping <1 2> failcount <1-999> This command is used to set the number of consecutive failures the AutoPings must detect before the AutoPing considers the pinged device to be failed. 3 set autoping mode <single and or> Sets single AutoPing or two AutoPing relationship And or Or. Single set autoping action <none on-latch on-follow offlatch off-follow cycle> set autoping cycle <0-999> This command is used to set the action that the iboot-poe will perform when the autoping triggers. This command sets the maximum number of power cycles when the AutoPing triggers. 0 = Unlimited None 1 set autoping wait <1-999> This command sets the time, in seconds for the device to respond to a ping. 2 set autoping restart <1-999> Sets the delay in seconds to restart AutoPing tests after Action. This command sets the time, in seconds for the device to respond to a ping. 0 set traffic monitor <enable disable> Enable or disable the traffic monitor Enabled set traffic monitor failtime <1-999> Fail time 10 set traffic monitor restarttime <0-999> Restart time 10 set traffic monitor cycles <0-99> Number of cycles 0 set traffic monitor min < > <kbps mbps> set traffic monitor max < > <kbps mbps> Min band width 0 Max band width 0 set traffic monitor maxtest <enable disable> Enable/disable maximum bandwidth test Disabled set traffic monitor startdisable <hh:mm> Set the start disable time <00:00> set traffic monitor stopdisable <hh:mm> Set the stop disable time <00:00> get traffic monitor Traffic Monitor: Enabled or Disabled Fail Time: in seconds Restar Time: in seconds Number of Cycles: Minimum Bandwidth: as programmed Maximum Test: enabled/disabled Maximum Bandwidth: as programmed Monitor Disable Start Time: hh:mm Stop Time: hh:mm iboot-poe_v160616e iboot-poe Page 24

25 set autoconfig start get autoconfig Starts auto config Displays the status: Running or Found: No device, Single Ended, Multi Ended User Commands These commands are only available to the administrator. set user account <yes no> This command sets whether or not a user account is used. If <n> only the administrator account is active n set login required <yes no> This command sets whether or not a login is required for user level operation. A login is always required for admin functions. y set password <user admin> <old> <new> <repeat> This command is used to set the password of either the user or administrator. user admin Event Commands get events These commands are only available to the administrator. This command displays all scheduled events as shown below. Example: set time enable <yes no> Date Time Repeats Action 1. 01/13/ :00 every 1 Day(s) On Run 2. 01/13/ :15 every 0 Day(s) On Run 3. 01/15/ :00 every 1 Hour(s) Cycle Run 4. 02/16/ :00 every 1 Day(s) Off Run 5. 02/16/ :10 every 1 Day(s) On Run 6. 02/17/ :05 every 0 Day(s) On Run 7. 02/18/ :00 every 0 Day(s) On Run 8. 03/18/ :00 every 0 Day(s) On Run This command enables or disables the use of the time server and scheduled events. Note: When Adding new events through the CLI. Set this to no to prevent unintended power switching No set time server <dotted decimal> This command is used to set the IP Address of a network time server get time Displays the current time and time server settings: Current Time: 07/30/ :41:05 Timezone: -5 DST: Enabled Starts the 2nd Sunday of March at 2:00 Stops the 1st Sunday of November at 2:00 Server: time.nist.gov set event <1-8> <run hold> This command is used to all the event to run, or put the event on hold run iboot-poe_v160616e iboot-poe Page 25

26 set event <1-8> date <mm/dd/yyyy> This command is used to set the scheduled action s start date. set event <1-8> time <hh:mm> set event <1-8> action <on off cycle> set event <1-8> repeat <day hour minute> set event <1-8> mult <0-999> del event <1-8> This command is used to set the time the scheduled action will occur in 24 hour format. This command is used to set the scheduled action. This command is used to set how often the scheduled action will repeat. This command sets how often the event will repeat, the number of increments (as set by the command above) before the next event. This command deletes the specified event Prompts User> Password> The CLI will use the following prompts: This prompts the user to enter his user name (user or admin). This is the first prompt that the user is presented with. This prompts the user to enter his password. iboot > This is the prompt that will be displayed after the user has successfully logged in. iboot Reboot Required> This is the prompt that will be displayed whenever there have been changes made that require a reboot. This prompt will remain the active prompt until the iboot-poe has been rebooted. iboot-poe_v160616e iboot-poe Page 26

27 8. DxP Protocol iboot-poe supports the Dataprobe Exchange Protocol (DxP) for inter device communications and to allow software developers to integrate Dataprobe product into custom applications. Through the DxP protocol, the developer can: Turn on and off power to the Outlet Pulse the Power On or Off for a specified about of time. Read the status of the Outlet The DxP Protocol, as well as example code and scripts in a variety of languages are available at dataprobe.com/support-documents/iboot-poe/ iboot-poe_v160616e iboot-poe Page 27

28 9. Firmware Upgrades The iboot-poe can be field upgraded. Find the latest version or special purpose versions at dataprobe.com/support-documents/iboot-poe/ Upgrading the firmware with a minor upgrade (i.e xx to 1.01.yy) will not alter the user defined settings. Major upgrades may or may not reset the iboot-poe to factory defaults. Check the release notes for the upgrade before making changes to you iboot-poe. 1) Insure that the Upgrade Enable checkbox is checked in the Network Setup web page of the iboot-poe 2) Run the Device Management Utility, available at the link above. If the iboot-poe you would like to upgrade is not visible in the list box, either Select Device Discover from the menu to locate iboot-poe units on the local network, or Select Device Add from the menu to add the IP address of the iboot-poe. Once the device is displayed in the list, highlight it 3) Select Manage Upgrade Firmware Enter User Name admin and the Password for the Administrator. Enter the filename of the firmware, or click Browse and find the file of the firmware file to be used. iboot- PoE firmware uses the extension.g2u If you don t see any files of that type, make sure the Files of type box is set for iboot-poe or All Files. Click OK when all the details are entered. 4) The upload will begin, and a progress bar will be displayed. 5) When the firmware upload is completed, the iboot-poe will automatically reset and be ready for use. iboot-poe_v160616e iboot-poe Page 28

29 10. Troubleshooting The iboot-poe has a recessed pushbutton switch in the event the unit is not performing as expected. Use the pushbutton as follows: Action Momentary Result Soft Reset. Will not change outlet status. 5 Seconds push Reset to Factory Defaults. Hold the button in until the Outlet LED is blinking, then release. Hold in while and Power up the iboot Recovery Mode. Allows upload of new firmware to the current IP Address. Will recover to the Factory default IP Address if the database has been corrupted. Factory reset excluding basic network settings can be done using the Device Management Utility (DMU) See Section 3.2. iboot-poe_v160616e iboot-poe Page 29

30 11. Specifications Physical Height Width Depth Weight MTBF Temperature mm mm mm 3.9 oz 110g TBD TBD Power PoE 802.3af and 802.3at Compliant 25.5 Watts Maximum combined Compliance FCC CE Part 15 Class B Pending Network Dual 10/100/1000 Unshielded Twisted Pair Ethernet Jacks. IP Addressed, DHCP assigned or Static Internal HTTP Web Server Forms Processing Browser required Telnet Server User Settings Location: MAC Address: IP Address: Subnet Mask: Gateway: Record your Setup here for reference HTTP Port: Auto-Ping Address: Auto-Ping Port: Heartbeat Port: iboot-poe_v160616e iboot-poe Page 30

31 12. Technical Support and Warranty Seller warrants this product, if used in accordance with all applicable instructions, to be free from original defects in material and workmanship for a period of Three Years from the date of initial purchase. If the product should prove defective within that period, Seller will repair or replace the product, at its sole discretion. Repairs may be made with new or refurbished components and replacements may be new or refurbished at the Sellers sole discretion. Repaired or replaced units shall be warranteed for the balance of the original warranty, or 90 days, whichever is greater. If Purchased from Dataprobe Inc.; Service under this Warranty is obtained by shipping the product (with all charges prepaid) to the address below. Seller will pay return shipping charges within the United States. Call Dataprobe Technical Service to receive a Return Materials Authorization (RMA) Number prior to sending any equipment back for repair. Include all cables, power supplies, accessories and proof of purchase with shipment. If purchased from an Authorized Dataprobe Reseller; Service under this Warranty is obtained by contacting your Authorized Dataprobe Reseller. THIS WARRANTY DOES NOT APPLY TO NORMAL WEAR OR TO DAMAGE RESULTING FROM ACCIDENT, MISUSE, ABUSE OR NEGLECT. SELLER MAKES NO EXPRESS WARRANTIES OTHER THAN THE WARRANTY EXPRESSLY SET FORTH HEREIN. EXCEPT TO THE EXTENT PROHIBITED BY LAW, ALL IMPLIED WARRANTIES, INCLUDING ALL WARRANTIES OF MERCHANT ABILITY OR FITNESS FOR ANY PURPOSE ARE LIMITED TO THE WARRANTY PERIOD SET FORTH ABOVE; AND THIS WARRANTY EXPRESSLY EXCLUDES ALL INCIDENTAL AND CONSEQUENTIAL DAMAGES. Some states do not allow limitations on how long an implied warranty lasts, and some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations or exclusions may not apply to you. This warranty gives you specific legal rights, and you may have other rights which vary from jurisdictions to jurisdiction. WARNING: The individual user should take care to determine prior to use whether this device is suitable, adequate or safe for the use intended. Since individual applications are subject to great variation, the manufacturer makes no representation or warranty as to the suitability of fitness for any specific application. Dataprobe Inc. Technical Support: support@dataprobe.com