MVO-SP 5.0 Administrators Guide - Home | Circadence 5.0 Administrator... · MINIMUM HARDWARE REQUIREMENTS ... About This Guide While the technologies incorporated into MVO are complex,

Doc No: CUD-MVO-1010

MVO-SP 5.0 Administrator Guide

Copyright © 2012 Circadence Corporation. All rights reserved.

Information in this document is subject to change without notice. This document is the property of Circadence Corporation and may contain information that is privileged, confidential, or otherwise protected from disclosure. Other than printing one copy for use by the intended recipient, no part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Circadence Corporation.

MVO™ and Web Assured Response Protocol™ are trademarks of Circadence Corporation.

TMP® and Transport Morphing Protocol® are registered trademarks of Circadence Corporation in the United States and other countries.

Trademark Acknowledgements

Microsoft, MS-DOS, Windows, Win32, and Internet Explorer are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Pentium is a registered trademark of Intel Corporation in the United States and other countries.

All other trademarks and registered trademarks are the property of their owners.

CHAPTER 1 – INTRODUCTION........................................................................................................................ 4

ABOUT THIS GUIDE ........................................................................................................................................................ 4 CIRCADENCE CUSTOMER SUPPORT .................................................................................................................................... 4

CHAPTER 2 – INSTALLING MVO SHAREPOINT REMOTE APPLICATION .............................................. 5

WINDOWS BACKGROUND NOTES ...................................................................................................................................... 5 MINIMUM HARDWARE REQUIREMENTS ............................................................................................................................. 5 WINDOWS PREPARATION ................................................................................................................................................ 5 INSTALLATION/CONFIGURATION CHECKLIST ......................................................................................................................... 6 STEP 1 – INSTALL MVO-SP REMOTE FOR SHAREPOINT ......................................................................................................... 7 STEP 2 – USING THE MVO-SP CONTROL PANEL TO CONFIGURE THE MVO-SP REMOTE ........................................................... 13

CHAPTER 3 – INSTALLING MVO SHAREPOINT SERVER ........................................................................ 15

WINDOWS BACKGROUND NOTES .................................................................................................................................... 15 MINIMUM HARDWARE REQUIREMENTS ........................................................................................................................... 15 WINDOWS PREPARATION .............................................................................................................................................. 15 INSTALLATION/CONFIGURATION CHECKLIST ....................................................................................................................... 15 STEP 1 – INSTALL MVO-SP SERVER FOR SHAREPOINT ........................................................................................................ 16 STEP 2 – LICENSING MVO-SP SERVER ............................................................................................................................. 21 STEP 4 – CONFIGURE THE MVO-SP SERVER ..................................................................................................................... 24

CHAPTER 4 – MONITORING MVO-SP WITH THE CLIENT UI ................................................................... 27

TABS: ......................................................................................................................................................................... 27 Home Screen .................................................................................................................................................... 27 Hub ..................................................................................................................................................................... 28

CHAPTER 5 – ADVANCED MVO FEATURES AND CONFIGURATION .................................................... 30

SECTION 1 - CHANGING THE LISTENING PORT FOR THE MVO SERVER ..................................................................................... 30 The MVO Default Listening Port .................................................................................................................... 30 Changing the Default Listening Port on the MVO Hub ............................................................................... 30 Changing the Port Number to Use for the MVO Channel on a MVO Remote ........................................ 30

SECTION 2 - ADJUSTING TIMEOUT VALUES FOR MTDS ........................................................................................................ 31 MTD Timeout Explanation .............................................................................................................................. 31 Adjusting the Timeout Value for MTDs ......................................................................................................... 31

SECTION 3 - CONFIGURING IP REDIRECTION ...................................................................................................................... 32 Configuring IP Redirection on a Hub ............................................................................................................. 32

SECTION 4 - WINDOWS FIREWALL/ANTIVIRUS ................................................................................................................... 33

APPENDIX A – GLOSSARY ............................................................................................................................ 34

APPENDIX B – PRODUCT END USER LICENSE AGREEMENT ............................................................... 37

Chapter 1 – Introduction Page 4

Chapter 1 – Introduction

Congratulations on purchasing the Circadence MVO™ Product. MVO delivers superior WAN Optimization with the industry’s most flexible deployment options. With its patented TMP® technology, MVO tunnels through network congestion, loss, and latency to deliver performance boosts across-WAN-links. Better performance translates to lower WAN costs and more productive computing.

MVO-SP is the SharePoint Edition of the Circadence MVO Product. It is preconfigured during installation to provide optimization for a single SharePoint server. For network optimization on multiple servers and beyond SharePoint, contact Circadence Sales at (303)413-8800. Sales can also be reached by email at [email protected].

About This Guide

While the technologies incorporated into MVO are complex, this guide is intended to provide sufficient information to use MVO effectively, including details for basic installation, configuration, and operation. Basic networking concepts will not be covered.

Circadence Customer Support

For problems, questions, or suggestions concerning the Circadence MVO™ Product contact Customer Support from 8 a.m. to 5 p.m., Monday through Friday-CST, by dialing 1-866-876-9967. After those hours, leave a message and the support staff will respond as quickly as possible. Customer Support can also be reached by email at [email protected].

mailto:[email protected]

mailto:[email protected]

Chapter 2 – Installing MVO SharePoint Remote Application Page 5

Chapter 2 – Installing MVO SharePoint Remote Application

This chapter provides instructions for installing the MVO SharePoint Remote Application in a Windows environment. Steps for initial configuration are also included.

Windows Background Notes

The Windows version of the MVO-SP product can be installed on Windows XP/Vista/7/8, or Windows Server 2003/2008 operating systems. The Windows-based version of MVO-SP can be used in both 32 and 64 bit version of the operating systems. Windows-based MVO-SP runs as multiple services, controlled through the MVO-SP Control Panel.

Minimum Hardware Requirements

For non-server installations on Windows XP, Windows Vista and Windows 7, refer to the recommended system requirements for the given operating system as defined by Microsoft in their support articles, plus 1GB of RAM and 5GB of free hard-drive space.

For Windows Server 2003 and 2008, refer to the recommended the system requirements for the given server, plus 2GB of RAM and 5GB of free hard-drive space.

Windows Preparation

The Windows MVO-SP application allows the user to select the install location. The default location for the 32 bit version of Windows would be C:\Program Files\Circadence\ Circadence MVO-SP SharePoint Acceleration and the default location for the 64bit version of Windows would be C:\Program Files (x86)\Circadence\ Circadence MVO-SP SharePoint Acceleration.

If the MVO-SP Remote application has been installed on the target computer previously, the configuration files will be overwritten by the installation process. If updating the version of the MVO-SP Remote, document the configuration settings before installation to aid in the configuration of the new version. Do not use backups of the configuration files as direct replacements in this folder as they may not be compatible with the new version.

The MVO-SP Remote application should be installed on client computers requiring WAN optimization of SharePoint. The remote component requires no special licensing. The licensing and allowed number of concurrent connections are handled by the MVO-SP Server component.

Important: If an earlier version of the MVO product has previously been installed on this computer, it must first be uninstalled before the MVO-SP Remote can be installed. These products cannot co-exist on the same computer.


Installation/Configuration Checklist

The table below outlines the steps that will be taken in installing MVO-SP Remote. This table can be used as a Windows installation and configuration checklist.

Step # Description Completed?

Step 1 Install MVO-SP Remote for SharePoint

Step 2 (optional) Using the MVO-SP Control Panel to configure the MVO-SP Remote

Table 1: MVO-SP Remote configuration checklist.


Step 1 – Install MVO-SP Remote for SharePoint

Installing the MVO-SP Remote on a Windows Machine 1. Download the installation executable from the Circadence Customer Download site and then

launch the Installer by double clicking the MVO SharePoint Remote Setup Executable icon from the download location.

2. After reading the information on the first screen, click Next. Refer to Fig. 1.

Figure 1: The Next button will present the EULA.


3. After reading the License Agreement and the terms and conditions are agreeable then, select "I accept the terms of the License Agreement" and click Next.

4. (Optional) Refer to Fig 2. click Browse… to select a different installation folder or click Next to continue.

Figure 2: Optional path selection for files during installation.


5. Enter the IP or hostname of the SharePoint server for which to provide optimization (assuming that the MVO-SP Server is installed on the same machine as the SharePoint server). See Figure 3 below. Note: If the MVO-SP Server is installed on a different machine, enter the address where the MVO-SP Server is installed. For best performance the SharePoint Server should be hosting the MVO-SP instance. The installer will attempt to resolve the server address/hostname to an IP address. If no valid server address/hostname is entered, the user will be issued a warning that this will need to be completed later. The IP/hostname can be configured later using the MVO-SP Control Panel.

Figure 3: Setting the IP/hostname of the SharePoint server.


6. Select which shortcuts to the MVO-SP Control Panel to install

Figure 4: Select which shortcuts to install


7. The Confirm Installation screen will now appear and prompt the user to click Install. The Installation screen will then provide the status of the installation of the product.

Figure 5: Click Install to start the installation.


8. Click Finish, as seen in Figure 6 below, to complete the installation process. Check the ‘Start MVO SharePoint Client’ box to launch the MVO-SP Control Panel if you were unable to configure the server address during the installation.

Figure 6: This completes the installation for the remote application.


Step 2 – Using the MVO-SP Control Panel to configure the MVO-SP Remote

If a valid server was specified during the installation, no additional configuration is necessary. The service will be running and pointing to a MVO-SP Server instance. However, if a server was not specified during installation or the server address has changed, use the MVO-SP Control Panel to configure the server location.

Launch the MVO-SP Control Panel using either the Desktop or Start Menu Circadence MVO SharePoint Acceleration shortcut if selected during install. Figure 7 below shows the control panel interface.

Figure 7: MVO-SP Control Panel

If a valid IP address/hostname was entered during the installation, an entry will exist for the Remote and the service will be started. The ‘Start’ and ‘Stop’ buttons can be used to enable and disable the MVO-SP Remote service respectively.


To edit the link, right click on the entry and select Edit. Modify the IP address to point to server instance of the MVO-SP Server, or enter a valid hostname and select the red checkmark.

Figure 8: Add/Edit the MVO link.

Click OK to save the changes. The service must be restarted before changes will be applied.

Chapter 3 – Installing MVO SharePoint Server 15

Chapter 3 – Installing MVO SharePoint Server

This chapter provides instructions for installing MVO SharePoint Server in a Windows environment. Steps for initial configuration are also included.

Windows Background Notes

The Windows version of the MVO-SP product can be installed on Windows XP/Vista/7, or Windows Server 2003/2008 operating systems. The Windows-based version of MVO-SP can be used in both 32 and 64 bit version of the operating systems. Windows-based MVO-SP runs as multiple services, controlled through the MVO-SP SharePoint Acceleration Client.

Minimum Hardware Requirements

For non-server installations on Windows XP, Windows Vista and Windows 7, refer to the recommended system requirements for the given operating system as defined by Microsoft in their support articles, plus 1GB of RAM and 5GB of free hard-drive space.

For Windows Server 2003 and 2008, refer to the recommended the system requirements for the given server, plus 2GB of RAM and 5GB of free hard-drive space.

Windows Preparation

The Windows MVO-SP application allows the user to select the install location. The default location for the 32 bit version of Windows would be C:\Program Files\Circadence\ Circadence MVO-SP SharePoint Acceleration and the default location for the 64bit version of Windows would be C:\Program Files (x86)\Circadence\ Circadence MVO-SP SharePoint Acceleration.

If Windows-based MVO-SP has been installed on the target computer previously, the configuration files will be overwritten by the installation process. If updating the version of Windows-based MVO-SP, document the configuration settings before installation to aid in the configuration of the new version. Do not use backups of the configuration files as direct replacements in this folder as they may not be compatible with the new version.

Important: If an earlier version of the MVO product has previously been installed on this computer, it must first be uninstalled before the MVO-SP Server can be installed. These products cannot co-exist on the same computer.

Installation/Configuration Checklist

The table below outlines the steps that will be taken in installing MVO. This table can be used as a Windows installation and configuration checklist.

Step # Description Completed?

Step 1 Install MVO-SP Server for SharePoint

Step 2 Licensing MVO-SP Server

Step 3 (optional) Configure the MVO-SP Server

Table 2: MVO-SP Server configuration checklist.


Step 1 – Install MVO-SP Server for SharePoint

1. Download the installation executable from the Circadence Customer Download site and then launch the Windows Installer by double clicking the MVO SharePoint Server Setup Executable icon on the desktop.

2. After reading the information on the first screen, click Next.

Figure 9: MVO-SP Server product installation screen.

3. After reading the License Agreement and the terms are agreeable, select I accept the terms of the License Agreement and click Next.


4. (Optional) Click Browse… to select a different installation folder

Figure 10: Optional installation directory location during installation.


5. Enter the SharePoint server address. The dialog is initially populated with the current computer’s IP address. However, an alternate hostname/IP Address may be entered if the MVO-SP application is hosted on a different machine. The installer will attempt to resolve the hostname to an IP address. If the address can’t be resolved or is not known during the time of installation, it can be specified later using SharePoint Acceleration Client application.

Figure 11: Enter SharePoint server address


6. Click Install. Then the Installation screen will provide the status of the installation of the product.

Figure 12: MVO-SP installation details confirmation.


7. Click Finish. A directory is placed in the start menu under as Start > All Programs > Circadence MVO-SP SharePoint Acceleration. If you weren’t able to configure the location of the SharePoint server during the installation, check the ‘Start MVO Client’ box to run the SharePoint Acceleration Client application for further configuration. A link to this application is also created on the desktop and in the Start menu.

Figure 13: Installation completion screen for MVO-SP application


Step 2 – Licensing MVO-SP Server

MVO-SP Server is installed with a fully functional 45-day evaluation license so that the product can be used immediately after installation. To purchase a license key, visit the Circadence web site at www.circadence.com.

After the 45 day evaluation period a full license must be purchased for the server.

Note: If internet access is not available at the time of registration please contact Circadence Customer Support. A License will be generated by the Support team and further instructions will be provided at that time.

1. Double-Click on the Circadence MVO Network Acceleration Client icon on the desktop of the client that will be used for the management of the MVO appliances.

2. At the login, enter the values to reflect those that are assigned to the Windows machine that the MVO application resides on. When accessing the application residing on the local machine, specify localhost as the address of the machine to monitor/configure. Upon the first login, you’ll be prompted to read and accept the license agreement.

Figure 14: MVO Client UI log in screen.


3. On the home screen, the current status for the MVO-SP Server will be displayed.

Figure 15: MVO-SP client UI home screen.


To enter a production license key, click on the License tab (see figure 15).

4. After purchasing a license from Circadence (visit the Circadence web site to purchase a license key), enter the supplied license key and a unique name to identify the machine and click Register.

n

Figure 16: Licensing screen.


Step 4 – Configure the MVO-SP Server

If a valid SharePoint IP Address/hostname was specified during the installation, no additional configuration is necessary unless this installation's port configuration is atypical for SharePoint. Follow the instructions below to configure the server for a different port configuration.

1. After installing the MVO-SP Server product on the appliance that will be the Hub, login to the MVO Hub using the client User Interface as completed in Step 2.

2. By configuring Managed Traffic Definitions (MTD) on the MVO-SP Hub the types of data streams placed on the MVO channel by the Remote can be managed. These MTD’s are passed to the Remote after a successful connection to the Hub.

3. The MVO-SP Server installer preconfigures MVO with ports related to SharePoint. In most installations, there is no need to change these ports. However, for SharePoint sites that are hosted on non-typical ports (i.e. not port 80), the definition will need to be modified.

4. Click the Hub tab to view status on the Hub. If the Hub is currently running, the indicator

on the left of the screen will appear in green. Use the buttons below the indicator to stop and start the Hub as needed.

Figure 17: Hub status tab.


5. Clicking the Details button in the lower right-hand corner of the screen will display the traffic definition for SharePoint. Click the edit icon in the SharePoint title bar to edit the traffic definition for SharePoint.

Figure 18: Hub traffic definitions.


6. Figure 19 shows the list of ports being optimized by MVO. This list is the full list of ports typically used by SharePoint. This particular installation may use different or additional ports. Use this form to customize the ports to be optimized. To add a port, click the (+) button and modify the port settings and priority. To remove a port, highlight the port to remove and click the (-) button. Click OK to save the changes. Any changes to the definition, requires a restart of the Hub for the changes to be applied.

Figure 19: Editing SharePoint traffic definition.

Chapter 4 – Monitoring MVO-SP with the Client UI 27

Chapter 4 – Monitoring MVO-SP with the Client UI

This chapter describes methods for monitoring the MVO product and status of the appliances.

The first elements of the Client UI are the tabs that display the information for each feature that is registered and accessible from the UI.

Clicking any tab navigates to that screen to manage settings and controls.

Tabs:

Home Screen

Within the Home tab screen is the Hub status screen.

Figure 20: Home screen of the Client UI

On the header of the viewing pane will be the name of the SharePoint feature and an indicator bulb on the far left to show if the Hub service has been started. If the bulb glows green then the appliance has been started. A yellow or amber bulb shows that the Hub service is in a transition state, usually stopping. An empty or grey bulb shows that the Hub service is in a stopped state.

The next element to the home screen is the data graph for that Hub. The traffic is color coded for data being sent and data being received by the Hub. The graph is a representation of Bytes transferred for the time shown.

Tabs

Indicator Bulb

Advanced Options


The next section is the Status and Actions of the Hub. The status gives the name of the Hub that was given when registered, or can be assigned through the Advanced Options feature of the Client UI. Also, the description can be defined from the Advanced Options Side Bar feature as well. Both the name and description are optional.

The state is a direct written reflection of the indicator bulb from the header. If the bulb is green then the state of the Hub service is Active. Otherwise the state should show that the appliance is Offline.

The connected Remotes field for the Hub shows the number of connected Remotes that have been configured with that Hub as a link and the connection has been started from both the Remote and Hub.

The actions sections of the Hub pane are tasks that can be performed from the home screen. You can start and stop the Hub from the home screen as well as view certain log files.

The view logs task will allow you to view the Hub, UI Service, Hub TMP and the System log files.

The last feature of the home page is the Advanced Options side bar button. The button will expand the Advanced Option side bar to expose the advanced options used for the Hub and the MVO application.

Hub

This screen is broken into four primary functions or sections. The status of the Hub is represented at the far left. The Details button for editing Traffic Definitions. The Advanced Options side bar button which is the same location as on the Home Screen. Then the listing of all connected Remotes.

Figure 21: MVO Client UI, Hub feature main screen.


The first section is the status of the Hub and has an icon that will glow green when the Hub service is started. Below that is the Name and description of the Hub as discussed on the Home Tab. The same Action button from the Home Tab is last in the Status section and functions just the same.

The next feature is the Details button. The Details button displays a page with the currently configured definition and a method of editing the current definition.

The Connected Remotes section will show individual sections for all Connected Remotes that have that this Hub as a TMP Link. Each section will contain an indicator bulb, which is the same as the Home screen, in the header that shows the IP Address for the Connected Remote. Then a traffic graph for that specific connection.

The Traffic Details button will provide a more detailed graph showing each of the configured MTDs for that Hub. Also all the MTDs will be listed below the graph with all corresponding details.

The More Information button will expand the Configured TMP Link section to allow additional details about the Remote to be viewed. This will also create a Less Information button to be used to hide those details again.

The View History Button will give you a more extensive view of data in graphical form for 5 time frames: The last 15 minutes, Last Hour, Last Day(24hrs), Last Week(Sun-Sat calendar Week), Last Month

Chapter 5 – Advanced MVO Features and Configuration 30

Chapter 5 – Advanced MVO Features and Configuration

This chapter provides configuration examples of supported advanced MVO functions and features. These options are advanced configuration options and should only be done under the guidance or direction of Circadence Customer Support.

Section 1 - Changing the Listening Port for the MVO Server

The MVO Default Listening Port

An MVO Hub, by default, listens on port 16000 for messages from a MVO Remote. Changing the listening port requires configuration changes on both the Remote server and Hub server. The port number must be between 1024 and 65535. If multiple Remotes connect to the Hub, the port number must be changed on all the Remotes.

Note: When the MVO Hub is restarted with a new Listening Port, the MVO channel will not resume passing traffic until the MVO Remote is restarted with the new port number and the link is established. Users will experience an outage during this process.

Changing the Default Listening Port on the MVO Hub

1. Log into the MVO Hub using the Client UI and click the MVO Hub Tab.

2. Click the arrow on the right side to expand the side bar.

3. Select the Advanced Connection Settings

4. In the Advanced Connection Settings option, enter a new port number in the TMP/UDP Binding Port field.

5. Click Ok to Save the changes

6. Click the Stop button if your Hub is running and then click the Start button to apply changes. After the application restarts, the MVO Hub server will now be listening on the new port number. The port number on the MVO Remote(s) that are to be connected to the MVO Hub must also be changed.

Changing the Port Number to Use for the MVO Channel on a MVO Remote

The configuration on all MVO Remotes connected to the MVO Hub must be changed to reflect the new port number.

1. Log into the MVO-SP Control Panel UI application on the remote computer.

2. Edit the link by right clicking on the link and selecting Edit.


Figure 22: Choosing the Edit button for the TMP link.

3. Enter the new port number in the Port field.

4. Click OK to save the changes.

5. Click Stop if the Remote is already running and then click Start to apply changes. After the application restarts, the MVO Remote server will now be attempting to connect on a new port number. This change requires that the bind port be changed on the Hub as well to match this new port number entered on the Remote.

Section 2 - Adjusting Timeout Values for MTDs

MTD Timeout Explanation

An MTD timeout setting defines how long the session in an MTD will remain in an open state without traffic. The default setting is 60 seconds, but it is possible that certain applications in an environment may not function properly if they need a longer timeout value.

Note: While there is not a defined upper limit to the number of seconds that can be entered for a timeout value, it is not recommend that you use values greater than 120 seconds. Also, the value of “0” represents “never timeout” and the value of “-1” represents “use system default value”. Consult Circadence customer support before using the value “0”, or values greater than 120 seconds.

Adjusting the Timeout Value for MTDs

1. Log into the MVO Hub and click the MVO Hub Tab.

2. Click the Details button

3. Click the Edit button for the MTD element you want to change.

4. Enter a new timeout value in the Timeout field. The default setting is "Default" which as stated earlier is 60 seconds.


Figure 23: Selecting the Timeout value for a Traffic Definition.

5. Click Ok to save the changes.

6. Click Stop if your Hub is running and then click Start to apply changes.

Section 3 - Configuring IP Redirection

The IP Redirect feature in the MVO product is intended for the situation where the address the MVO Remote receives does not match the actual address of the intended destination. One situation where this occurs is when the intended destination is behind a firewall.

Configuring IP Redirection on a Hub

To configure IP Redirection:

1. Log into the MVO Hub and click the MVO Hub Tab.

2. Click on the Details button

3. Click the Edit button.

4. When entering the IP Redirect information in the Redirect IP data field the format should be

<IP Address:Port> If no port is entered then the same port in the Port/Range field will be

used.


Figure 24: Setting the IP address for Redirection.

5. Click the OK button to save the data. The IP Redirection will be reflected in the MTD details

list.

6. If the Hub is running then it will need to be restarted for the change to be applied.

Section 4 - Windows Firewall/Antivirus

When an Antivirus (AV) software is present on Client machines, it needs to be configured properly in order for MVO to work properly.

First Full Access must be given any/all MVO executables; FEService.exe, BEServervice.exe, SMBService.exe, FTPProxyClass.exe, and FTPProxyTrans.exe, UIServices.exe when prompted by the AV software. After access is given to each executable, two methods are available to complete the process: Recommended Method: Under the firewall Advanced configuration, add a Trusted UDP Port tunnel System Service for Circadence MVO for port 16000 and save. Alternative Method: Under the firewall Advanced configuration, add a Trusted Network with a single IP address for the Hub and save.

34

Appendix A – Glossary

bandwidth — A networking term referring to the data transfer rate supported by a network.

Bandwidth rates can be measured in kilobits per second, kilobytes per second, or megabytes per second.

BIOS — An acronym for Basic Input/Output System, the first program a computer runs when

powered on. The BIOS can be used to configure such things as the order that devices are checked for the operating system to be loaded next.

broadcast address — A network address that allows information to be sent to all

machines on a given subnet rather than to one specific machine.

caching — A common performance strategy of staging common files close to the end user.

CIDR — An acronym for Classless Inter-Domain Routing, a technique that summarizes a

block of Internet addresses in a routing table as an address in dotted decimal notation followed by a forward slash and a two-digit decimal number giving the number of leading one bits in the subnet mask. For example, 123.123.123.0/24 implying the block of addresses 123.123.123.0 through 123.123.123.255.

compression — The strategy of making files smaller through various methods to reduce

the consumption of resources (bandwidth, RAM, and disk space) and increase performance.

crossover cable — A network cable that allows two electronic devices to perform full-

duplex communication without the use of a switch or hub. This term commonly refers to the Ethernet crossover cable, but other cables can follow the same principle.

DNS — An acronym for the Domain Name System, a hierarchical naming protocol for

computers, services, or any other resource connected to a network. DNS servers return an IP address when queried with a domain name. See also: Reverse DNS.

DSL — An acronym for Digital Subscriber Line, refers to a family of technologies that provides

digital data transmission over the wires of a local telephone network.

firewall — A system designed to prevent unauthorized access to or from a private network.

Remote — Also known as an MVO Remote, the MVO component that connects to an MVO

Hub to form an MVO channel. Host machines using the MVO channel use the MVO Remote as a gateway for packet routing. MVO Remotes examine traffic streams for matching characteristics to the set of Managed Traffic Definitions passed to them from the MVO Hub. Any matching traffic is placed on the MVO channel by the MVO Remote. MVO Remotes can exist on a Windows-based host machine or as a separate network device.

FTP — An acronym for File Transfer Protocol, a protocol used to effectively manage the

transfer of files from one computer to another through a network, often between systems that have different operating systems

GUI — An acronym for Graphical User Interface, a program interface that takes advantage of

the computer's graphics capabilities to make the program easier to use.

Hub — Also known as a MVO Hub, a MVO appliance that typically resides near the

destination servers and communicates with one or more MVO Remotes. It is one of the two required components of a simple MVO channel.

http://dictionary.reference.com/browse/Internet%20addresses

http://dictionary.reference.com/browse/routing%20table

http://dictionary.reference.com/browse/dotted%20decimal%20notation

http://dictionary.reference.com/browse/forward%20slash

Appendix A – Glossary 35

IP — An acronym for Internet Protocol, a protocol used for communicating data across a

packet-switched network.

IP address — The 32-bit number uniquely identifying a node on a network using Internet

Protocol, as defined in STD 5, RFC 791. An IP address is normally displayed in dotted decimal notation, e.g. 128.121.4.5.

kilobit vs. kilobyte — The measurements of kilobits and kilobytes are often confused with

each other, causing the actual transfer rate to be misrepresented by a factor of 1/8th or 8x, since a kilobit is 1/8th the size of a kilobyte.

link resiliency — A term used to describe a characteristic of a network connection where

all packets are to be delivered after an interruption of service without restarting as a new connection.

listening port — A configurable characteristic of the MVO Hub that defines which port

number the MVO Hub listens on for communications from the MVO Remote.

MD5 — An acronym for Message-Digest 5, an algorithm used to create a digital signature of a

file or file system.

MD5 hash — Created by the MD5 algorithm, a 32 digit hexadecimal number representing

the digital signature assigned to files or file systems, often to verify integrity.

MTD — An acronym for Managed Traffic Definition, a rule or set of rules used for determining

which types of network traffic are optimized and managed by a MVO channel.

MTU — An acronym for Maximum Transmission Unit, the maximum size of a data packet that

can traverse a network without being fragmented. The legal values for MTU on an Ethernet network are between 576 bytes and 1500 bytes. There are two types of MTU associated with the MVO product, interface MTU and MVO channel MTU.

out-of-band — A technical term referring to communications which occur outside of a

previously established communications method or channel. Out-of-band networks typically are separated from the established corporate network used for security and management of network devices.

port — Referring to TCP/IP and UDP networks, an endpoint to a logical connection. The port

number usually identifies what type of service is listening. For example, port 80 is used for HTTP traffic.

port range — As referenced in MVO, a range of sequential values representing port

numbers that will be part of a Managed Traffic Definition (MTD). Specify a port range by using the minimum and maximum values of the sequence with a “-“ character between them. Always specify the range with the minimum value first and the maximum value last. An example is 6000-6015.

port timeout — A specified time period of no activity before the connection using that port is

terminated by MVO.

prioritization — The method of assigning throughput levels of High, Medium-high, Medium,

Low-Medium, or Low to different types of traffic in a MVO channel through the use of the priority setting in a Managed Traffic Definition.

http://dictionary.reference.com/browse/node

http://dictionary.reference.com/browse/Internet%20Protocol

http://dictionary.reference.com/browse/Internet%20Protocol

http://dictionary.reference.com/browse/STD

http://dictionary.reference.com/browse/RFC



Appendix A – Glossary 36

routing — In internetworking, the process of moving a packet of data from source to

destination.

SCP — An abbreviation for the Secure Copy application or protocol, a method of securely

transferring files between hosts on a network.

SSH — An acronym for the Secure Shell application or protocol, a network protocol that allows

data to be exchanged using a secure channel between two networked devices. Used primarily on Linux and Unix based systems to access shell accounts. The encryption used by SSH provides confidentiality and integrity of data over an insecure network, such as the Internet.

switch — A hardware device that connects other devices or segments on a network.

TCP — An acronym for Transmission Control Protocol, a primary method of transferring data

across networks. It is connection-oriented, meaning that the two endpoints communicate with each other in a send-and-acknowledge format. Almost all data that traverses a network is sent with either TCP or UDP.

TCP handshaking — The negotiation of communication rules and protocol details at the

beginning of connection-oriented sessions. TCP sessions begin with electronic handshaking.

TMP® — An acronym for Transport Morphing Protocol, the network data transfer method

implemented by the MVO product.

UDP — An acronym for Universal Datagram Protocol, a primary method of transferring data

across networks. It is connectionless, meaning that the two endpoints communicate with each other in a send-and-forget format. Almost all data that traverses a network is sent with either UDP or TCP.

VPN — An acronym for Virtual Private Network, a network that uses a public

telecommunication infrastructure, such as the Internet, to provide remote offices or individual users with secure access to their organization's network. A VPN works by using the shared public infrastructure while maintaining privacy through security procedures and tunneling protocols such as the Layer Two Tunneling Protocol (L2TP). The protocols, by encrypting data at the sending end and decrypting it at the receiving end, send the data through a "tunnel" that cannot be "entered" by data that is not properly encrypted.

WAN — An acronym for Wide Area Network, a network with links that cross metropolitan,

regional or national boundaries.

WAN optimization — A process used to increase the efficiency of bandwidth usage or

perceived user experience in a wide area network.

MVO™ — The Circadence-developed software that implements the TMP network data

transfer method.

MVO appliance — A device where the MVO software is installed; part of a MVO network.

MVO channel — The connection between a MVO Remote and a MVO Hub.

MVO channel MTU — The maximum size of the data packet transmitted across a MVO

channel. See also MTU.

Windows — The most widely used operating system for desktop and laptop computers.

http://en.wikipedia.org/wiki/Network_protocol

http://en.wikipedia.org/wiki/Secure_channel

http://en.wikipedia.org/wiki/Linux

http://en.wikipedia.org/wiki/Unix

http://en.wikipedia.org/wiki/Shell_account

http://en.wikipedia.org/wiki/Encryption

http://en.wikipedia.org/wiki/Internet

Appendix B – Product End User License Agreement 37

Appendix B – Product End User License Agreement

These Circadence Terms and Conditions of Sale and Service govern Circadence's sale of Products and Support and Circadence's license of Software.

1. DEFINITIONS

a) "Delivery" means standard Circadence shipping to and arrival at the receiving area at the "Ship To" address specified in Customer's order.

b) "Exhibits" means attachments that describe or otherwise apply to the sale or license of Products or Support.

c) "License Fee" means the fee or fees designated by Circadence for Use of Software.

d) "Products" means hardware, Software, documentation, accessories, supplies, parts and upgrades that are determined by Circadence to be available from Circadence upon receipt of Customer's order. "Custom Products" means Products modified, designed or manufactured to meet Customer requirements.

e) "Software" means one or more programs capable of operating on a controller, processor or other hardware Product ("Device") and related documentation. Software is either a separate Product, included with another Product ("Bundled Software"), or fixed in a Device and not removable in normal operation ("Firmware").

f) "Software License" means the Software license grant and general license terms set forth herein.

g) "Specifications" means specific technical information about Circadence Products that has been delivered by Circadence to the Customer with Customer's order.

h) "Support" means hardware maintenance and repair; Software updates and maintenance; training; and other standard support services provided by Circadence. "Custom Support" means any agreed non-standard Support, including consulting and custom project services.

i) "Use" means storing, loading, installing, executing or displaying Software on a Device.

2. PRICES

a) Prices are valid for the period quoted by Circadence or for the applicable purchase agreement ordering period, whichever expires first. Product prices for an order remain valid for 30 days from the original order date unless otherwise quoted by Circadence. Change orders that extend Delivery beyond those validity periods become new orders at prices in effect when Circadence receives the change orders. Circadence may change support prices, except for Custom and prepaid Support, upon 60 days written notice.

b) Prices are exclusive of, and Customer will pay, applicable sales, use, consumption, goods and service, value added or like taxes, unless Customer has provided Circadence with an appropriate exemption certificate for the Delivery jurisdiction.

3. ORDERS

All orders are subject to acceptance by Circadence. Product orders must specify Delivery within 90 days from order date at the Ship To address specified by Customer, unless otherwise agreed or quoted by Circadence. Customer may cancel orders for Products (except Custom Products) prior to shipment at no charge.

4. DELIVERY


Circadence will make reasonable efforts to meet Customer's Delivery requirements. If Circadence is unable to meet Customer's Delivery requirements, alternative arrangements may be agreed. In the absence of such agreement, Customer's sole remedy is to cancel the order.

5. SHIPMENT, RISK OF LOSS OR DAMAGE, AND TITLE

Circadence will ship according to Circadence's standard commercial practice, and risk of loss or damage and title will pass from Circadence to Customer at the Ship To address. Shipping and handling charges will be listed separately on Circadence's invoice when not included in the Product's purchase price. If Circadence has agreed to Customer requested special packing or shipping instructions, charges will be billed separately to Customer, and risk of loss or damage and title will pass to Customer on delivery to Customer's carrier or designate.

6. INSTALLATION AND ACCEPTANCE

a) Product installation information is available with Products, on quotations or upon request. Installation by Circadence, when included in the purchase price, is complete when the Product passes Circadence's standard installation and test procedures.

b) For Products without installation included in the purchase price, acceptance by Customer occurs upon Delivery. For Products with installation included in the purchase price, acceptance by Customer occurs upon completion of installation by Circadence. If Customer schedules or delays installation by Circadence more than 30 days after Delivery, Customer acceptance of the Product(s) will occur on the 31st day after Delivery.

7. PAYMENT

a) Payment terms are subject to Circadence credit approval. Payment is due 30 days from Circadence's invoice date. Invoices for contractual support services and maintenance will be issued in advance of the Support period. Circadence may change credit or payment terms at any time when, in Circadence's opinion, Customer's financial condition, previous payment record, or the nature of Customer's relationship with Circadence so warrants.

b) Circadence may discontinue performance if Customer fails to pay any sum due, or fails to perform under this or any other Circadence agreement if, after ten days written notice, the failure has not been cured.

8. LIMITED WARRANTY

a) Circadence warrants Circadence hardware Products against defects in materials and workmanship for a period of ninety days from the original purchase date by Customer as reflected on Customer's purchase order. Circadence warrants the Software for a period of ninety days from the original purchase date by Customer as reflected on Customer's purchase order. During this warranty period, Circadence will promptly repair any properly documented errors in the software at no charge. Errors must be reported by Fax or e-mail. This warranty applies to custom development and Circadence's pre-built applications. The warranty period commences on the original purchase date by Customer as reflected on Customer's purchase order, not from the date of acceptance by Customer. CIRCADENCE'S SOLE RESPONSIBILITY IS TO REPAIR ERRORS IN OUR SOFTWARE. CIRCADENCE EXPECTS THE CUSTOMER TO THOROUGHLY TEST THE SOFTWARE BEFORE USE. Circadence does not warrant that Software will operate in hardware and software combinations selected by Customer, or meet requirements specified by Customer.


c) Circadence does not warrant that the operation of Products will be uninterrupted or error free.

d) If Circadence receives notice of defects, Circadence will, at its option, repair or replace the affected Products. If Circadence is unable, within a reasonable time, to repair, replace or correct a defect or non-conformance in a Product to a condition as warranted, Customer will be entitled to a prorated refund of the purchase price upon prompt return of the Product to Circadence. Such refunded amount will be based on a four-year straight line depreciation schedule and shall be the prorated unused portion of such schedule. Customer will pay expenses for return of such Products to Circadence. Circadence will pay expenses for shipment of repaired or replacement Products.

e) Circadence warrants that Circadence Support will be provided in a professional and workmanlike manner. Some newly manufactured Circadence Products may contain and Circadence Support may use remanufactured parts that are equivalent to new in performance.

f) The warranties provided herein will apply only to those Products and Support that are branded by Circadence with a Circadence trademark ("Circadence Branded"). Circadence does not warrant any third party Products or Support even if included with other Circadence Branded Products or Support. Furthermore, Circadence provides all such third party Products and Support AS IS. However, the original manufacturers or suppliers may provide their own warranties as specified in the documentation accompanying such third party Products and Support.

g) The above warranties do not apply to defects resulting from:

1) improper or inadequate maintenance by Customer;

2) Customer or third party supplied software, interfacing or supplies;

3) unauthorized modification;

4) improper use or operation outside of the Specifications for the Product;

5) abuse, negligence, accident, loss or damage in transit;

6) improper site preparation; or

7) unauthorized maintenance or repair.

h) THE ABOVE WARRANTIES ARE EXCLUSIVE AND NO OTHER WARRANTY, WHETHER WRITTEN OR ORAL, IS EXPRESSED OR IMPLIED. TO THE EXTENT PERMITTED BY LAW, CIRCADENCE SPECIFICALLY DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NONINFRINGEMENT.

9. SUPPORT

a) Customer may order Support from Circadence's then current Support offering. Orders for Support are subject to the terms of the quotation in effect on the date of order.

b) Circadence may, at no additional charge, modify Products to improve operation, supportability and reliability, or to meet legal requirements.

c) Relocation of Products is Customer's responsibility. Relocation may result in additional Support charges and modified service response times. Support of Products moved to another country is subject to availability.


d) Circadence will provide Support for Circadence Products when Customer allows Circadence to perform modifications if requested by Circadence under Section 9.b) above. Customer is responsible for removing any products not eligible for Support to allow Circadence to perform Support services. If Support services are made more difficult because of such product(s), Circadence will charge Customer for the extra work at Circadence's standard rates.

e) Support does not cover any damage or failure caused by:

1) use of non-Circadence media, supplies and other products; or

2) site conditions that do not conform to Circadence's site specifications; or

3) neglect, improper use, fire or water damage, electrical disturbances, transportation by Customer, modification by people other than Circadence employees or subcontractors, or other causes beyond Circadence's control.

f) Customer is responsible for maintaining a procedure external to the Products to reconstruct lost or altered Customer files, data or programs. Customer will have a representative present when Circadence provides Support services at Customer's site. Customer will notify Circadence if Products are being used in an environment that poses a potential health or safety hazard to Circadence employees or subcontractors; Circadence may require Customer to maintain such Products under Circadence supervision and may postpone service until such hazard is remedied.

g) Customer may delete Products under Support or cancel Support orders upon 30 days written notice unless otherwise agreed in a Support agreement. Circadence may cancel Support orders or delete Products no longer included in Circadence's Support offering upon 60 days written notice unless otherwise agreed in a Support agreement.

10. LICENSES

a) In return for the License Fee, Circadence grants Customer a non-exclusive license to Use the object code version of the Software listed in Customer's order in conformance with:

1) the terms set forth herein; and

2) Use restrictions and authorizations for the Software specified by Circadence in its quotation, invoice or terms that accompany the Software; and

3) Circadence's third party suppliers' terms that accompany the Software.

In the event of a conflict, the third party suppliers' terms that accompany the Software will take precedence over the Use restrictions and authorizations specified by Circadence and the terms set forth herein, and the Use restrictions and authorizations specified by Circadence will take precedence over the terms set forth herein.

b) Unless otherwise specified, in return for the applicable License Fee, Circadence grants Customer a license to Use one copy of the Software on one Device at any one time.

c) Unless otherwise specified, all Software Licenses will be perpetual unless terminated or transferred in accordance with Section 10. k).

d) Customer may not sublicense the Software unless otherwise agreed to by Circadence in writing

e) Software is owned and copyrighted by Circadence or by third parties. Customer's Software License confers no title or ownership and is not a sale of any rights in the


Software. Third parties may protect their rights in the Software in the event of any infringement.

f) Unless otherwise permitted by Circadence, Customer may only make copies or adaptations of the Software for archival purposes or when copying or adaptation is an essential step in the authorized Use of the Software on a backup Device, provided that copies and adaptations are used in no other manner and provided further that the Use on the backup Device is discontinued when the original or replacement Device becomes operable.

g) Customer must reproduce all copyright notices in or on the original Software on all permitted copies or adaptations. Customer may not copy the Software onto any public or distributed network.

h) Bundled Software or Firmware provided to Customer may only be used when operating the associated Device in configurations as sold or subsequently upgraded by Circadence. Customer may transfer Firmware only upon transfer of the associated Device.

i) Updates, upgrades or other enhancements are available under Circadence Support agreements. Circadence reserves the right to require additional licenses and fees for Use of the Software on upgraded Devices.

j) Customer will not modify, disassemble or decompile the Software without Circadence's prior written consent. Where Customer has other rights under statute, Customer will provide Circadence with reasonably detailed information regarding any intended disassembly or decompilation. Customer will not decrypt the Software unless necessary for legitimate use of the Software.

k) Customer's Software License is transferable subject to Circadence's prior written authorization and payment to Circadence of any applicable fee(s). Upon transfer of the Software License, Customer will immediately deliver all copies of the Software to the transferee. The transferee must agree in writing to the terms of Customer's Software License. All Software License terms will be binding on involuntary transferees, notice of which is hereby given. Customer's Software License will automatically terminate upon transfer.

l) Circadence may terminate Customer's or any transferee's or sublicensee's Software License upon notice for failure to comply with any applicable Software License terms. Immediately upon termination, the Software and all copies of the Software will be destroyed or returned to Circadence. Copies of the Software that are merged into adaptations, except for individual pieces of data in Customer's or transferee's or sublicensee's database, will be removed and destroyed or returned to Circadence. With Circadence's written consent, one copy of the Software may be retained subsequent to termination for archival purposes.

11. INTELLECTUAL PROPERTY RIGHTS

a) Circadence will defend or settle any claim against Customer that Circadence Branded Products or Support (excluding Custom Products and Custom Support), delivered under these Circadence Terms and Conditions of Sale and Service infringe a patent, utility model, industrial design, copyright, trade secret, mask work or trademark in the country where Products are used, sold or receive Support, provided Customer:

1) promptly notifies Circadence in writing; and


2) cooperates with Circadence in, and grants Circadence sole control of the defense or settlement

b) Circadence will pay infringement claim defense costs, settlement amounts and court-awarded damages. If such a claim appears likely, Circadence may modify the Product, procure any necessary license, or replace it. If Circadence determines that none of these alternatives is reasonably available, Circadence will refund Customer's purchase price upon return of the Product if within one year of Delivery, or the Product's net book value thereafter.

c) Circadence has no obligation for any claim of infringement arising from:

1) Circadence's compliance with Customer's designs, specifications or instructions;

2) Circadence's use of technical information or technology provided by Customer;

3) Product modifications by Customer or a third party;

4) Product use prohibited by Specifications or related application notes; or

5) Product use with products that are not Circadence Branded.

d) These terms state Circadence's entire liability for claims of intellectual property infringement.

12. LIMITATION OF LIABILITY AND REMEDIES

a) To the extent Circadence is held legally liable to Customer, Circadence's total liability is limited to: payments described in Sections 8. d) and 11. b) above; other direct damages for any claim based on a material breach of Support services, up to a maximum of six months of the related Support charges paid by Customer during the period of material breach; and other direct damages for any claim based on a material breach of any other term of these Circadence Terms and Conditions of Sale and Service, up to the amount paid to Circadence for the associated Product.

b) Notwithstanding Section 12. a) above, in no event will Circadence or its affiliates, subcontractors or suppliers be liable for any of the following: incidental, special or consequential damages (including downtime costs or lost profits, but excluding payments described in Section 11 above and damages for bodily injury); damages relating to Customer's procurement of substitute products or services (i.e., "cost of cover"); or damages for loss of data, or software restoration.

c) THE REMEDIES IN THESE CIRCADENCE TERMS AND CONDITIONS OF SALE AND SERVICE ARE CUSTOMER'S SOLE AND EXCLUSIVE REMEDIES.

13. GENERAL

a) The Parties hereby agree that they may do business electronically, including contract formation, order placement and acceptance. Any orders placed by Customer electronically will create fully enforceable obligations that will be subject to the terms hereof. Such orders and acceptances will be deemed for all purposes to be

1) business records originated and maintained in documentary form,

2) a "writing" or "in writing," and "signed,"

3) an "original" when printed from electronic files or records established and maintained in the normal course of business.


The Parties further agree not to contest the validity or enforceability of such transactions under the provisions of any applicable law relating to whether certain agreements are to be in writing or signed by the Party to be bound thereby and will be admissible if introduced as evidence on paper in any judicial, arbitration, mediation, or administrative proceeding to the same extent and under the same conditions as other business records originated and maintained in documentary form.

b) Circadence will not be liable for performance delays or for non-performance, due to causes beyond its reasonable control.

c) If either party becomes insolvent, is unable to pay its debts when due, files for bankruptcy, is the subject of involuntary bankruptcy, has a receiver appointed, or has its assets assigned, the other party may cancel any unfulfilled obligations.

d) Customer may not assign any rights or obligations hereunder without prior written consent from Circadence.

e) A Customer who exports, re-exports or imports Products, technology or technical data purchased hereunder, assumes responsibility for complying with applicable laws and regulations, and for obtaining required export and import authorizations. Circadence may suspend performance if Customer is in violation of applicable regulations.

f) Disputes arising in connection with these Circadence Terms and Conditions of Sale and Service will be governed by the laws of State of Colorado.

g) Provisions herein that, by their nature, extend beyond the termination of any sale or license of Products or Support will remain in effect until fulfilled.

h) If any term or provision herein is determined to be illegal or unenforceable, the validity or enforceability of the remainder of the terms or provisions herein will remain in full force and effect.

i) The Commercial Sales Contract to which these Circadence Terms and Conditions of Sale and Service are attached, together with any other Exhibits that may be attached, constitute the entire agreement between Circadence and Customer, and supersede any previous communications, representations or agreements between the parties, whether oral or written, regarding transactions hereunder. Customer's additional or different terms and conditions will not apply. Customer's purchase or license of Products and Support will constitute Customer's acceptance of these Circadence Terms and Conditions of Sale and Service, which may not be changed except by an amendment signed by an authorized representative of each party.

* * * * *

MVO-SP 5.0 Administrators Guide - Home | Circadence 5.0 Administrator... · MINIMUM HARDWARE REQUIREMENTS ... About This Guide While the technologies incorporated into MVO are complex,

Documents