tip Looking for a virtual machine version of InSite? Check out Private Node Server.

InSite Private Monitoring

InSite is your own personal monitoring location. InSite monitors websites and transactions, collecting web application metrics from a private location within your local network. This provides crucial insight into service delivery levels and a common platform of metrics for managing Service Level Agreements.

InSite adds an internal perspective to external web performance monitoring, giving you the means to evaluate website performance and availability from inside as well as outside your network.

InSite can also provide monitoring for back-office, CRM, and other internal applications that have no external accessibility. InSite is completely integrated into AlertSite's monitoring service and console, and brings all of your critical web monitoring together in one view.

1. Overview

This document is a comprehensive tutorial on installation, configuration, and troubleshooting. Setting up InSite requires knowledge of your network and some rudimentary hardware and software skills. Once the system is configured and monitoring, it needs little care other than occasional software upgrades.

See 9. Release Notes below for the list of software upgrades.

2. Installation

Installation is quick and easy:

  • Install the hardware
  • Purchase the InSite by AlertSite plan for your AlertSite account
  • Configure the InSite Location in the account
  • Configure Site/Server devices to be monitored with the InSite plan
  • Register the InSite Location through the InSite Control Panel
  • Change the admin password to access the InSite Control Panel to your own custom password, to ensure that the system is secure.

Each of these steps is described in detail below.

The InSite appliance must always be powered on, otherwise, monitoring from your InSite location will stop.

Please read through these notes before continuing in order to familiarize yourself with the procedure. Note that screenshots are provided for illustration purposes only and may not reflect actual devices.

2.1 InSite-to-AlertSite Communication Configuration

As a prerequisite, the remote InSite appliance needs to communicate, either directly or through a proxy, to the hosts and outbound ports of any external servers you wish to monitor, as well as to the following servers/services:

Port Protocol URL/Server Function
22 SSH insiterepair.alertsite.com (209.156.160.90) For AlertSite Remote Support on InSite appliance.
25 SMTP Mail servers of alert recipients For outgoing e-mail notifications (if you do not set an internal mail relay host).
80 HTTP N/A For access to the web portal interface on the InSite appliance.
443 HTTPS (SSL) privateagent.alertsite.com
privateagent.jupiter.alertsite.com
To register the InSite appliance and ServerAgent, send monitoring data to AlertSite and collect configuration updates from the AlertSite.
Note: privateagent endpoints have dynamic IP addresses, so you need to whitelist the host names and not their current IP addresses.
4892 Encrypted XML AlertSite monitoring locations For outbound performance data and status of InSite's ServerAgent.

NOTE: If you use InSite v.2.0.2, you can test the connection to AlertSite servers by using the DiagnosticsConnection Tests page in the InSite Control Panel.

For proxy server, you need to know the HTTP, SSL (HTTPS), and/or SOCKS proxy IP addresses (not hostnames) and port numbers, as well as SOCKS version if using SOCKS proxy. If your proxy server requires authentication, you must provide the Userid and Password for the server. Note that if the Userid includes a domain name, such as DOMAIN\user, you need to use a double backslash: DOMAIN\\user.

In addition, the IP addresses of the monitoring location used by the ServerAgent configured to monitor InSite must be allowed. To find out what monitoring location you are using:

  • Click on the ServerAgent name in the Configuration: ServerAgents page.
  • In the Manage Servers page, click on the Locations button in the upper right.
  • Note the top-most location highlighted in the list (it will be marked as Primary).
  • On the Monitoring Location IP Addresses page, find this location and note its IP addresses.

All IPs listed for that location must be allowed, as load balancing is used to select the specific server.

If you change the location that is monitoring InSite, you will need to allow connection to those IP addresses. Note that changing to a location outside of United States, Canada, and the UK will consume additional usage credits for Usage-Based customers. Click here for more information about configuring ServerAgent on InSite.

2.2 Install the InSite Appliance Hardware

  • Unpack the appliance
  • Install server rails (optional)
  • Install a monitor on the video interface
  • Plug in the network connector to the Ethernet port
  • Plug in the power cord and press the power button on the front panel
  • Note the IP address of the InSite appliance in the monitor screen after boot-up is complete

NOTE: If you are not using DHCP, see 4.3.1 Network Configuration.

2.3 Purchasing InSite by AlertSite

Log in to your AlertSite Console and navigate to SupportAlertSite Contact for your AlertSite Sales Manager's contact information. Call your sales rep for assistance in choosing the right InSite appliance for your needs.

2.4 InSite Monitoring Capacity

Please consider carefully the number of devices you expect to monitor prior to purchasing your InSite appliance to allow for future expansion. The load capacity of the InSite unit is a function of several factors:

  • The maximum number of devices
  • The number of transaction steps (actions)
  • The monitoring interval

The maximum number of devices refers to the number of devices for which monitoring data history is maintained, regardless of monitoring status. For example, if you have an InSite-25 appliance, you cannot add more than 25 devices even if the existing devices are disabled as they are still using device "slots".

Appliance capacity guidelines are also based on 5-step transactions running at 5-minute intervals. If you have an InSite-50 and running, say, 45 10-step transactions at 5-minute intervals, you may find this exceeds the unit's workload capacity; however, you should be fine with 50 3-step transactions at 3-minute intervals.

If you are exceeding the capacity of your unit, you can:

Please note that deleting devices also deletes the data history for those devices.

Back to top

3. Configuration

This section describes modifications needed within your AlertSite Account.

3.1 Configure the InSite Monitoring Location in the AlertSite Console

  • From the Configuration drop-down in the Control Menu, click on InSite Locations
  • In Configuration: InSite Locations, click on the button labeled Add a new location in the upper right
  • Enter in a Description and select the Location Plan, then click Submit
  • A 32-character Location ID will be created as illustrated below:

New_Manage_InSite_Log.PNG


NOTE: The 32-character Location ID is needed to register the monitoring location. This is described later in 4.2.1 Register Location.

3.2 Configure Device with InSite Monitoring Location

  • In the Configuration drop-down menu, click on Sites
  • In the Configuration: Sites screen, click on the Add a new site button in the upper right
  • Fill in the form fields:
    • Enter a “report-friendly” site name the Site Name field
    • In the Site Plan field drop-down, select the InSite plan purchased earlier
    • Select Global Notify from the Monitoring Type drop-down list. (Global Notify is the Monitoring Type supported for devices monitored with InSite by AlertSite; Round Robin and SLA (MultiPOP) are not supported because InSite by AlertSite cannot coordinate among monitoring locations when it is behind the firewall.)
    • Enter the URL to monitor
    • Select a Site Type from the drop-down list
    • Select the monitoring interval from the Check Every drop-down
    • If not resolving DNS, enter the IP address and change the Resolve DNS field to No
    • Click Submit in the upper right to save
  • Repeat for as many monitors as needed and as allowed by the InSite plan selected (in this example, up to 25).

After registering the InSite Monitoring Location (described in 4.2.1 Register Location below), you may also select it as a monitoring station for other devices. To accomplish this:

  • From the Manage Site configuration screen of your existing device, click the Locations button to display the Monitoring Locations table
  • Click the checkbox in the Active column for the registered InSite Monitoring Location, and click Submit

This counts towards the number of monitors allowed by the purchased InSite plan.

Note: Devices monitored with SLA (MultiPOP2) monitoring type or rotated locations cannot be monitored by InSite.

3.3 Notifier Configuration

To receive alerts when InSite detects an error on a monitored device, configure notifiers through the Configure Notifiers interface:

  • Click Notifier in the Control Menu
  • Click the Add Notifer button in the upper right and fill in the form with the necessary information

The following Notifier Methods for receiving alerts are supported by InSite by AlertSite:

  • E-mail (HTML or text),
  • E-mail to wireless device (text message)
  • SMS
  • SNMP trap (snmpv1/snmpv2c)
  • VoIP

See the Console Help screen Manage Notifiers - Description of fields for notifier format information. At the current time, the following notifier methods are not supported by InSite:

  • Pager types
  • AOL Instant Message (AIM)

3.4 ServerAgent Configuration

AlertSite's ServerAgent is included with each InSite appliance to monitor the health of your InSite system. Verify that you have an available (no-charge) plan by going to AccountAccount Summary in the AlertSite Console. You should see the following entry in the Plan Summary section:

InSite_SA_Plan.png

If you do not see this information in the Account Summary, please contact Customer Support or your sales rep (shown in SupportAlertSite Contact in your Console) immediately.

Once the ServerAgent for InSite plan is in place, you must configure the ServerAgent device in the Console:

  • Go to ConfigurationServerAgents
  • Click Add a New ServerAgent
  • Enter a Name for the ServerAgent
  • Select Server Agent 5 w/ InSite from the Site Plan dropdown
  • Click Submit

The AlertSite monitoring location used to monitor your InSite appliance is automatically configured.

As described in 2.1 InSite-to-AlertSite Communication Configuration above, you can change the monitoring location. In that case, click on the Locations button in the upper right of the Manage Servers page and click the radio button for the desired location. Remember to allow connection to the IP addresses of the new location.

NOTE: If you are a usage-based monitoring customer and you select a location outside of United States, Canada or the United Kingdom, you will consume additional measurement credits for each ServerAgent check.

To use ServerAgent to monitor the InSite box, there are a few more steps:

  • The ServerAgent must be registered with InSite using the 32-character Device ID generated after adding the ServerAgent. This step is described in 4.4.1 Register ServerAgent.
  • After the ServerAgent has been registered, it must be enabled on the InSite appliance as described in 4.4.2 Start/Stop ServerAgent Monitoring
  • The User Script, a heartbeat check called lastsend.sh that provides the feedback on the InSite appliance, must be added to the ServerAgent; see 5. InSite ServerAgent Monitoring.

    NOTE: The lastsend.sh User Script is the only ServerAgent functionality supported for the InSite location.

Reboot is not required when registering or starting ServerAgent in InSite, and there is no loss of monitoring.

The ServerAgent client runs on the InSite, gathering metrics on CPU, memory and disk usage, and results of the heartbeat check. The client sends the health-check information from the InSite appliance to the AlertSite monitoring location, which is then displayed on your Console.

For more information about ServerAgent, go to ServerAgent Systems Monitor.

Back to top

4. InSite Control Panel

To access the InSite Control Panel, bring up a new browser window or tab, then:

  • Enter http://<IP Address>, where <IP Address> is either:
    • the IP address of the InSite appliance noted during the installation of the hardware, OR
    • the static IP address configured in the Network Configuration screen (see 4.3.1 Network Configuration)

  • Provide the following credentials:
    • User Name: admin
    • Password: password

      NOTE: Once you are logged in, be sure to change the default password to something more secure. You first need to register your InSite, then you can set the new password in Manage InSite Location > Change Web Password. The password can be up to 10 characters long.

The InSite Control Panel will be displayed with:

  • Control Panel - Displays the current monitoring status and network configuration settings
  • Manage InSite Location – Perform administrative functions such as software upgrades, network configuration, and remote support access
  • Configure Settings - Customize your network configuration and time settings
  • ServerAgent - Manage the InSite ServerAgent
  • Diagnostics – Run verification and networking tests, send logs to AlertSite, and test notifications

All InSite management functions are accessed through the dropdown menus, To access any of these functions, hover on the link in the menu bar. Each function is described in more detail below.

4.1 Control Panel

This is the main page shown when first logging in to the InSite Control Panel. Displayed are:

  • A table that confirms the InSite monitoring location is functioning properly and monitoring devices
  • A link to the Device Status Report for devices monitored by InSite
  • Network configuration settings with links to each configuration page
  • ServerAgent status

New_Control_Panel.png


The Activity and Program fields in the monitoring status tables are defined as follows:

Activity Definition
Last Monitor Last time monitoring test was performed
Results Send to AlertSite Last time monitoring results were sent back to AlertSite
Database Update Last time your AlertSite data were sent to InSite
Notification Attempt Last time notification process checked for outgoing alerts
Note: Activity timestamps are in the time zone selected in your AlertSite account settings,
whereas InSite system time displayed in the top right of the Control Panel is GMT-based.
   
Program Definition
Monitor Main AlertSite monitoring program for scheduled tests
Diagnostic Monitor Monitoring program for ad-hoc diagnostic tests
Monitoring Controller Scheduler for timed tests
Notifier Program which sends notifications to users

Back to top

4.2 Manage InSite Location

This screen enables you to perform the following administrative tasks:

  • Register Location
  • Change Web Password*
  • Start/Stop Remote Access*
  • Upgrade Software*
  • Reboot InSite Device
  • Reset To Factory Defaults

* Requires InSite registration.

The following sections describes each task:

4.2.1 Register Location

The first function to perform is to register your InSite Monitoring Location through the InSite Control Panel. To register the InSite Monitoring Location:

  • From the Control Panel top menu, select Manage InSite Location > Register Location.
  • Enter your AlertSite Account Login ID and Password.
  • If you are not logged in to the AlertSite Console:
    • Open a new browser tab and window.
    • Log in to the console and navigate to ConfigurationInSite Locations.
    • Click on the InSite Location Name of the InSite device you want to configure.
    • Copy the 32-character ID (configured in 3.1 Configure the InSite Monitor).
  • Paste the 32-character ID into the Location ID field in the Register InSite Location screen. The page should look like:

Register_Location.png
  • Click Register, and at the confirmation page, click to continue. Your InSite monitoring location is now available as a monitoring station for any of your monitored sites.

In the AlertSite Console Configuration: InSite Locations screen, verify that the device is displayed as Active.

NOTE: If you delete an InSite Monitoring Location, devices monitored exclusively by that location will not be visible in the Console Dashboard or Status screens, but will remain in the Configuration: InSite Locations screen and can be restored when the InSite appliance is re-registered. If you need to stop monitoring with the InSite appliance temporarily, you can change the Monitoring Status to Inactive in the Manage InSite Locations screen.

4.2.2 Change Web Server Password

This page gives you the opportunity to change the login ID and password used to log in to InSite by AlertSite. Enter the current Login ID and password, then enter a new password and confirm it. The password can be up to 10 characters long.

4.2.3 Start/Stop Remote Access

If you need assistance from AlertSite for your InSite system, click on this link to allow remote access for up to 12 hours. Contact Customer Support with information that will assist with troubleshooting.

4.2.4 Upgrade Software

If a new release of the InSite by AlertSite application software is available, click on this link to upgrade. If the software is up to date, the resulting page will display this information, otherwise, it will display the list of available upgrades, with the radio button for the next revision automatically selected. Click the Upgrade button to start the upgrade process. Log messages will appear as the software is updated. If there are interim releases, click the radio button for the next major revision (e.g., 1.5.0).

If upgrading from V1.2.X to V1.3.X or later, a refresh of the browser is required after the upgrade completes in order to get the new interface. If the new interface doesn't appear after refresh, change status.cgi in the URL to upgrade.cgi. The settings previously made to the InSite host file, DNS (resolv.conf), mail configuration, etc., will be preserved through the upgrade.

Note: if you have custom security certificates installed, the certs will be overwritten by the upgrade and will need to be reinstalled.

4.2.5 Reboot InSite Device

This link will reboot your InSite monitoring location. This pauses monitoring of any device configured with this location during this time. To check the location to see when it's back up, go to Diagnostic Tests and run Ping on the IP address of your InSite box.

4.2.6 Reset to Factory Defaults

This will cause a complete reset of your InSite system. It will be set up as it was right out of the box, reverting to the original installed InSite software version. Any modifications you made, e.g., IP address, network settings, Proxy Server settings, etc., and any log data collected will be cleared. Re-registration is required.

Back to top

4.3 Configure Settings

This screen enables you to configure several network settings:

  • Network Configuration*
  • Proxy Connection Settings*
  • E-mail Configuration*
  • NTP Configuration*
  • Set System Time

* Requires InSite registration.

The following sections describes each task:

4.3.1 Network Configuration

This screen allows you to switch to DHCP for dynamic IP address assignment and modify network settings such as the static IP address, network mask, name server, and gateway host. An Advanced DNS Configuration screen accessed through a button on this page provides the ability to add multiple name servers if your environment requires it. Removing an added DNS IP address is accomplished by simply clearing the Name Server IP address fields.

4.3.2 Proxy Connection Settings

If you require proxy access to the Internet from behind your firewall, use this screen to set the HTTP, SSL, or Socks proxy host.

  • Select Manual Proxy Configuration.
  • Fill in the IP address for the proxy server type. Note: You must use the IP address in the HTTP, SSL, and SOCKS proxy fields, not a hostname.
  • Enter the Userid and Password for the server, if needed. If the Userid includes a domain name, such as DOMAIN\user, you need to use a double backslash: DOMAIN\\user.
  • Click OK.

Note: Every DéjàClick transaction monitored from that InSite box must be configured to have the matching proxy server settings. For details on how to set that up, go to Browser Preferences in the DéjàClick Knowledge Base.

4.3.3 Mail Configuration

InSite sends email alerts on port 25. If your local network does not allow outgoing connections through the firewall on port 25, you need to specify a mail relay host on your local network to send alerts through.

  • Relay Host – The name or IP address of the host to pass all outbound email to.
  • Relay Port – The port to connect to the mail relay host (specify only if different from the default 25).
  • Masquerading host - Not used. Reserved for future use.

Note: If your mail relay host requires authentication or works over SSL (like Gmail), please contact Customer Care for assistance.

InSite does not retry alerts if it cannot reach the mail relay host.

4.3.4 NTP Configuration

The InSite appliance accesses an NTP Time Server daemon in the AlertSite domain by default. Use this screen to configure up to two different NTP servers.

4.3.5 Set System Time

This page allows you to set the system time on the appliance (in GMT). Use of the NTP daemon is recommended for accuracy.

The current system time is displayed in the top right corner of InSite Control Panel.

Back to top

4.4 ServerAgent

The InSite ServerAgent will monitor the health of your InSite location and alert any selected notifiers if an outage or missed monitor is detected.

The firewall setting for TCP OUTBOUND Port 4892 needs to be open. This is the port used by the ServerAgent Manager (Windows) or commgr (Linux) to report InSite's monitored metrics.

The dropdown provides two functions:

  • Register ServerAgent
  • Start/Stop ServerAgent

Note: if you need to delete and reconfigure your InSite ServerAgent, you must disable it first in order to register a new ServerAgent.

4.4.1 Register ServerAgent

Select this menu item and paste into the Device ID field the Device ID copied from the AlertSite Console Manage Servers page for the device you have configured as the InSite ServerAgent.

4.4.2 Start/Stop ServerAgent

In order for the ServerAgent to begin monitoring your InSite appliance, it must be enabled through this screen. Click the Start button (the Stop button is deactivated).

To stop monitoring the InSite appliance, return to the Start/Stop ServerAgent page and click the Stop button, then confirm the action in the dialog box that's presented. You must also disable ServerAgent prior to reconfiguring and/or registering a new InSite ServerAgent.

Back to top

4.5 Diagnostics

This screen enables you to perform the following diagnostic tasks:

  • Connection Tests
  • Diagnostic Tests
  • Retrieve System Logs
  • Send Test Notification

4.5.1 Connection Tests (InSite v. 2.0.2)

This page allows you to test the connectivity to AlertSite hosts and ports required for proper functioning of InSite (see 2.1 InSite-to-AlertSite Communication Configuration above). Tests are performed using the network parameters configured for this InSite appliance, including the proxy server, DNS server, and so on.

The results are displayed after some time (about a minute). Please do not refresh the page during this time.

4.5.2 Diagnostic Tests

You can run several network or device tests from this screen:

Hostname Lookup Determine a specific IP number from a domain name and vice-versa
Traceroute See the exact path a packet takes to get to a remote location.
Ping Determine whether a specific internet address is accessible.
AlertSite Web Test Test a web page or CGI by retrieving the actual page.*

* Requires InSite registration

4.5.3 Retrieve System Logs

This page allows you to send available error log files to AlertSite Support for assistance with troubleshooting as needed. InSite registration is required for this function.

NOTE: The log files may be large, so please send one at a time and not all at once.

4.5.4 Send Test Notification

To verify that alert notifications will be received by the notifiers configured in your AlertSite Console, click on any of the notifiers in the Description column of the table displayed in this screen to send a test message to the recipient shown. Only VoIP, E-mail, or text message are applicable.

Back to top

5. InSite ServerAgent Monitoring

Every 10 minutes, InSite checks for new monitoring data. If there are new results, the data are sent back to AlertSite and an InSite log file is updated, changing the log file's date. How often the data are sent depends on the monitoring interval for devices monitored with InSite. Results are sent to AlertSite at the shortest interval configured in the console, but no shorter than 10 minutes. In other words, if the shortest monitoring interval for all your InSite monitored devices is 15 minutes, then data will be sent every 20 minutes. If the shortest interval is 5 minutes, the data will be sent every 10 minutes.

In order to monitor the health of your InSite box using ServerAgent, a special script, lastsend.sh, has been included in InSite V1.2.1 and later. The script returns the number of minutes since the last time data was sent from InSite to AlertSite, based on the log file date. At least one device must be monitored by InSite for this script to function as it was intended.

Configure ServerAgent to run lastsend.sh as a User Script. Since the date of the log file should not be older than 10 minutes longer than your shortest monitoring interval, it will report a warning if the return value is, say, >(interval+5) minutes and an error if the return value is >(interval+10) minutes. The ServerAgent User Script thresholds can be populated during ServerAgent configuration, following ServerAgent registration as described in 4.4.1 Register ServerAgent and after it is enabled as described in 4.4.2 Start/Stop ServerAgent Monitoring.

Configuring the User Script is a simple process:

  1. Go to the Manage Server screen for the InSite ServerAgent device
  2. Click the User Scripts tab
  3. Click the Enable User Scripts Monitor check box
  4. Make the following changes in the first (blank) line
    • Click the Enabled and Notify check boxes
    • Enter lastsend.sh in the Name Box if it is not present
    • Change the Compare conditional operator to > or >=
    • Change Warning Value to your shortest monitoring interval + 5
    • Change Threshold Value to your shortest monitoring interval + 10
  5. Click Submit in the upper right of the Manager Server screen

User_script_line.png


You may adjust the Warning and Threshold values, but don't make them lower than your shortest monitoring interval + 20 minutes. Also note that if your shortest monitoring interval is 10 minutes, the data may not be sent until the next 10-minute check.

The lastsend.sh user script is the only functionality supported for the InSite location.

NOTE: You may receive one or two alerts initially while the system syncs up the connection to ServerAgent and/or the lastsend.sh user process. Allow some time for communications to settle in.

6. Troubleshooting

If the response time metrics are not being updated or notifications are not being sent/received, please refer to the list below for tips on troubleshooting.

  • Verify that InSite appliance hardware is up and running.
  • Make sure your firewall allows traffic from the InSite appliance to the hosts and ports specified in 2.1 InSite-to-AlertSite Communication Configuration.
    NOTE: If you use InSite v. 2.0.2, you can test the connection using the DiagnosticsConnection Tests in the InSite Control Panel.
  • Ensure the network cabling is installed correctly. See 2.2 Install the InSite Appliance Hardware.
  • Bring up the InSite Control Panel as referenced in 4. InSite Control Panel and verify that the Control Panel is functioning and the time stamp in the Time field is updating.
  • If the Monitoring Status shows that the monitor is functioning, re-register the location as described in 4.2.1 Register Location.
  • Check that the monitoring status in the Manage InSite Locations screen in the AlertSite console is Active.
  • In the InSite Control Panel, select DiagnosticsDiagnostic Tests and run a traceroute to privateagent.alertsite.com and privateagent.jupiter.alertsite.com. To use a different port, put a space after .com followed by the port number, e.g., privateagent.alertsite.com 443.
  • Make sure that your device has the InSite Monitoring Location selected in the Locations list.
  • If you do not receive notifications, send the logs from your SMTP server to AlertSite support.
  • If your SMTP logs do not provide enough information for you to determine the problem, you can send a subset of log files from the InSite appliance to AlertSite Support. In the InSite Control Panel, select DiagnosticsRetrieve System Logs and send the following logs one at a time:

    IPD Logs
    Notification Logs
    Watch Logs
    System Log
    Mail Log

    To send a log, select the check box next to it, then click Send Logs in the top right. Repeat for other logs.
  • If the InSite appliance goes down or crashes, reinitialize the box by cycling power.

If you're still having problems after following these troubleshooting tips, contact Customer Support. Remote Access to your InSite box may be required. In the event of a Linux security update, a new InSite appliance will be shipped to you.

Back to top

7. InSite Appliance Specifications and Replacement Information

Specifications for InSite by AlertSite Appliance *

insite-server.jpg Enterprise Data Center Appliance
Up to 100 monitors

Height: 1.68” (1U)
Width:18.99” (incl. rack latches)
Depth: 30.39” (incl. PSU handles and bezel)
Weight (max. config): 39 lbs.
Power (max. config): 1004W
  Standard Data Center Appliance
Up to 25 or 50 monitors

Height: 1.68” (1U)
Width:17.10" (incl. rack latches)
Depth: 24.00” (incl. PSU handles and bezel)
Weight (max. config): 33 lbs
Power (max. config): 350W

* Specifications may change on an as-needed basis.

Replacement

Note: Before swapping out your InSite unit with a replacement or cold spare, please contact Customer Support.

Replacing your InSite appliance with another InSite unit supplied by AlertSite is simple and straightforward:

  • Before powering down your existing appliance, make note of any hard-coded network addresses and port information in the currently configured InSite Control Panel
  • Move the Ethernet and power cables from the existing InSite appliance to the replacement and attach a monitor
  • After the replacement appliance boots up, note the new IP address displayed in the monitor
  • In your browser, open a new tab and enter http://<IP Address>, where <IP Address> is the IP address of the InSite appliance noted in the monitor
    • If your InSite unit is running SSL3 3.0, then you need to use https://<IP Address>
  • Provide the following credentials to display the InSite Control Panel for the replacement appliance:

User Name = admin
Password = password

  • Hover over Manage InSite Location in the menu bar and select Register Location from the dropdown
  • Enter your AlertSite Console Login ID and Password
  • Copy-and-paste into the Location ID field the InSite location's 32-character ID displayed in the AlertSite Console Manage InSite Locations screen
  • Click Register, and at the confirmation page, click to continue.
    • If you are using a static IP address, or have configured a DNS Server or Mail Relay Host, reference 4.2 Manage InSite Location for instructions on configuring that information in the replacement
  • Your new InSite appliance is now functioning as the monitoring station.

Back to top

8. Frequently Asked Questions

8.1   What port is the InSite appliance using to send data back to AlertSite?

It uses port 443 to check in to privateagent.alertsite.com or privateagent.jupiter.alertsite.com. This is also the route used when registering the appliance.

8.2   What port does the InSite appliance use for Enable Remote Support ?

It uses port 22 through to insiterepair.alertsite.com.

8.3   How often is the data being sent out from the appliance to AlertSite - immediately, at the exact monitoring interval used, or is it sent later in a batch?

Data is sent as a batch. There are a couple of different schedules, but for reporting, it's every 10 minutes. Notifications are done locally on the box, and are immediate.

8.4   Is the data from the InSite appliance being sent out to AlertSite as clear text or is it being encrypted?

The data is encrypted (SSL).

8.5   How is a DejaClick transaction being distributed to the InSite appliance once a transaction is uploaded to the AlertSite console?

It's distributed in the same manner as that data is sent up as a batch; we hand any updates that have occurred to devices and/or notifiers back to the InSite appliance.

8.6   What is the patch process for InSite, and is it the same process as the upgrade software option found on the InSite Control Panel?

The patch process is the same as the upgrade software option. In some cases, major revisions may require new hardware to be delivered, in which case AlertSite will ship a replacement.

8.7   Please describe the security features for the InSite appliance.

A firewall is used to prevent access within the member firm. The InSite appliance can not be administered remotely without access through the firewall, and authentication is required to administer the appliance. The InSite Operating System, Debian Linux, undergoes an AlertSite internal customer build process. All unnecessary services are disabled. Email will not accept inbound connections. Web server access is restricted by a settable username/password. All conversations with AlertSite are encrypted.

8.8   How is the InSite appliance administered? Can AlertSite gain access to my appliance?

The appliance is administered by customer-defined administrators who are required to authenticate to the appliance's Control Panel or AlertSite Console. AlertSite cannot administer remotely without access through the customer's firewall and authentication on the appliance. The customer's administrator can enable a service which lasts for 12 hours (V1.2.0 and later, 1 hour for V0.9.4 and earlier) for remote access for AlertSite support troubleshooting. Access can also be manually disabled.

8.9  Is this remote access process done through HTTP, and can this be compromised?

No. Remote access is accomplished with ssh (Secure Shell), requires authentication, and cannot be compromised.

8.10  Can the customer remotely access the InSite Monitoring Appliance boot-up configuration screen?

Remote access to the InSite boot-up configuration screen is not available/provided.

8.11 It appears the InSite appliances have multiple NICs. Does InSite support multihoming?

The InSite appliance does not support two NICs, despite the hardware being present. The interfaces cannot be teamed; this is something we do not support and the customers cannot do this themselves.

9. Release Notes

This section describes the bug fixes and enhancement of new InSite releases.

InSite V1.5:

  • InSite Site Plans can be selected for SoapUI devices.
    • SoapUI devices with Usage-Based Monitoring Site Plans can select InSite locations for monitoring along with AlertSite locations.
    • SoapUI monitors with an InSite Plan do not require Test On Demand run in order to be enabled.
  • InSite Site Plans can be selected for transactions with ContentViews.
    • Transactions with ContentViews using Usage-Based Monitoring Site Plans can select InSite locations for monitoring along with AlertSite locations.
  • InSite Site Plans can be selected for transactions recorded as a simulated Mobile Device.
    • Mobile-Device transactions using Usage-Based Monitoring Site Plans can select InSite locations for monitoring along with AlertSite locations.

InSite V1.4.1:

  • Maintenance release.
  • NOTE: Duplicate column name errors displayed during upgrade are expected and can be ignored. These messages will occur if the current version already contains the database table being added in the upgrade.

InSite V1.4:

  • Remote Support Access status corrected in Control Panel (stale PID file removed).
  • Allow unregistered InSite to request Remote Support.
  • ServerAgent registration Exit Code 2 fixed.
  • Out of memory condition caused by Java plugin fixed.
  • Recovery of ServerAgent from unknown state.
  • Correct handling of alerts from inactive InSite location.
  • Database added to support subaccount visibility in Configuration: InSite Locations screen.
  • Fixed error messages displayed during mail relay host configuration update.

InSite V1.3.1:

  • Database glitch caused an interruption of notifications. Quick patch V1.3.1 fixed this issue. V1.3.0 must be installed first, then V1.3.1.

InSite V1.3.0:

  • InSite Control Panel provides an overview of monitoring activity and configuration settings.
  • Improved navigation though the Control Panel with menus linking to all functions.
  • Improved configuration through the Control Panel Network Configuration menu - replaces text based script in separately attached monitor.
    • Network Configuration
    • Proxy Settings
    • Email Configuration
    • NTP Configuration
    • Network Search Directives supported in Advanced Network Configuration menu
    • Multiple Nameservers supported in Advanced Network Configuration menu
  • Enhanced ability to maintain the InSite appliance.
    • InSite Control Panel:
      • Additional information given while handling Reboot InSite Device and Reset to Factory Defaults.
      • Better verification that the InSite location is active and working successfully.
      • Additional information given while registering and enabling ServerAgent devices.
    • AlertSite Console:
      • Configuration: InSite Locations screen includes the number of used and available devices for each InSite location.
      • Easier selection of specific InSite locations for assigning monitored devices when multiple InSite locations are available.
  • Customer Testing - enable standard AlertSite testing features on the InSite appliance.
    • Send test notifications from the InSite mail/notification system.

10. Customer Support

For questions or technical support, contact:

Email: CustomerCare@alertsite.com Phone: 954-312-0188 Fax: 954-312-0186

Go to Customer Support for more information.

Back to top

APPENDIX: InSite Appliance Console

This section describes some of the functions that are available through the InSite Appliance Console. To display the InSite Appliance Console, attach a monitor and keyboard to the appropriate ports on the back of the appliance. The monitor will display the InSite Appliance Console.

A.1 Configure Static IP Address

By default, InSite by AlertSite obtains its IP address through Dynamic Host Configuration Protocol (DHCP). If you require a static IP address, attach a monitor and keyboard to the appropriate ports on the back of the appliance. The monitor will display the InSite Appliance Console:

Hit 'C' to select ConfigurationManual IP Address Config:

Manual_IP.JPG


Hit <ENTER>, then follow the prompts to enter the following information:

  • IP address
  • netmask
  • gateway
  • nameserver

Back to top

A.2 Configure DNS Server

To assign a different Domain Name Server, go to the InSite Appliance Console, accessed from a terminal attached to the InSite box. Choose Configuration from the main menu. On the next screen, choose the option Manual IP Address Config:

InSite_Manual_IP_Address_Config.JPG


This prompts for new IP settings:

InSite_Detail_Manual_IP_Address_Config.JPG


Hit <ENTER> to step through the default settings until New Nameserver is displayed. Enter the Nameserver IP address.

Back to top

A.3 Configure Mail Relay Host

When you're working behind the firewall, if you choose to keep Port 25 closed, you must configure a mail relay host to have the notifications sent to your mail server from InSite.

To configure a mail relay host, go to the InSite Appliance Console, accessed from a terminal attached to the InSite box. Under the main menu choose Configuration, then select MailConfig from the menu:

Mail_ConfigurationPanel.JPG


Next, cursor to Set RelayHost in the Mail Config menu.

SetMailConfigPanel.JPG


Hit <ENTER> to display the input field:

SetRelayHostPanel.JPG


Enter the IP address or your company email server name. This will redirect email notification from InSite through your mail server.

Back to top

© 2016 SmartBear Software --
Syndicate this site RSSATOM