MyConnection Server (MCS) is not backward compatible with VisualRoute Server or MySpeed Server v6, a new install is required.

Upgrading to MyConnection Server v9 from MySpeed Server v7 Pro, NOC, Support Editions

MyConnection Server (MCS) 9 is backward compatible with MySpeed Server v7 with a few differences. In particular MCS is a framework architecture and the various Network Test applications (such as MyRoute, MyVoIP, MyIPTV) now store their settings separately, which may require some settings and preferences to be redefined.

If you are not concerned with keeping the old database or v7 configuration settings, a new install to a clean directory is recommended.

Server

If MCS v9 is installed over MySpeed v7, MCS will use the same ports for speed testing and VoIP testing. If you are upgrading to an MCS license with additional network tests (such as MyRoute or MyIPTV), you will need to open the corresponding ports for those tests. The ports are set under the Server Configuration option.

Database

MCS v9 has an entirely different, much more flexible database. If MCS v9 is installed over the top of MySpeed v7 it will upgrade the MySpeed database to the MCS format, but this can take a while. In our experience it converts about 100,000 records per hour. During this time the MCS server will be offline (because new records cannot be added to the database while the database is being upgraded). If you want to start afresh with a new database but still retain other MySpeed settings, then delete the DB and Detail directories from the install directory before over-installing MCS.

Recommended: If you want to keep your MySpeed v7 database and install MyConnection Server in a new directory, copy the MySpeed v7 files in the db directory to the new MyConnection Server install directory. NOTE: the database is only converted on the first MCS startup, the files need to be copied over before running MCS for the first time.

Applet Configuration, Web Pages Serving the MySpeed applet

If you have created custom web pages to serve the MySpeed v7 Java applet, you will need to modify the web pages to serve the MCS applet as noted below:

<applet MAYSCRIPT name="myspeed"
code="myspeed.class"
archive="myspeed.jar"
codebase="http://yourmyspeedserver.com/myspeed" width="600" height="400"> Java is required to view this applet </applet>

change to in MCS:

<applet mayscript name="myspeed"
code="myspeedserver/applet/myspeed.class"
archive="/myspeed/myspeed.jar,/myspeed/plugins.jar" codebase="http://yourmyspeedserver.com/myspeed" width=600 height=400> Java is required to view this applet </applet>

Most applet settings will be carried over from MySpeed v7 to MCS, however, settings such as "timeout" and "packets per second" have changed, in MCS these parameters are set in the Manage Tests option.

Remote Agents (RTAs/RSAs - MySpeed Server v7 NOC and Support Editions)

If MCS is installed over the top of MySpeed then the RTA configuration should be retained. The deployed RTAs themselves will be automatically upgraded to the latest version - this process should complete within 10-20 minutes after upgrade. If RTAs have been deployed to Unix boxes then they will need to be manually updated - the auto-upgrade machanism applies only to Windows services. In rare instances after the RTA upgrade the Windows service has trouble restarting itself, in which case the new upgraded RTA will start running on the next RTA system reboot. OnDemand RSA executables created in MySpeed are not compatible with MCS, however new RAs are easily created in MCS.

Remote Agent licensing has been signficantly improved and simplified in MCS, the RTAs and RSAs have been combined and are licensed by the maximum number of active Concurrent Remote Agent Tests (CATs). You can create and define a Remote Agent to install as a service and run in the background (for long-term testing), or as a zero-footprint agent that is active only while the agent window is open on the remote system (ideal for troubleshooting a connection problem during a support call). In either case, you can create an unlimited number of agents to support unlimited end-users, the total number of concurrent remote agent tests (CATs) determines the maximum number of active tests that may be run at a given time. If a single remote agent is defined to perform connection tests to 3 different location, it is counted as 3 tests.

Alerts

Some alert configurations will need to be redefined, so alert settings should be checked after the upgrade process is complete.

Deprecated Tags

Due to the new plugin architecture of MyConnection Server, several <param> tags for MySpeed Server are deprecated in MCS — support for them will continue for the time being, but could be removed in the future.

Old Tag	Replaced With	Purpose
downtype	speed_downtype	Speed plugin: Sets the type of download test (socket or HTTP)
uptype	speed_uptype	Speed plugin: Sets the type of upload test (socket or HTTP)
rttnumtests	speed_rttnumtests	Speed plugin: Sets the number of RTT tests
maxheadersize	speed_maxheadersize	Speed plugin: Sets the maximum header size permitted in the upload test
timeout	speed_testtime	Speed plugin: The length of the test
voipbytesperpacket	voip_bytesperpacket	VoIP plugin: Number of bytes per packet
voipsimulationseconds	voip_simulationseconds	VoIP plugin: The length of the test
voippacketspersecond	voip_packetspersecond	VoIP plugin: Number of packets to send per second
voiplines	voip_lines	VoIP plugin: Number of lines to simulate
voipdiscardms	voip_discardms	VoIP plugin: Maximum packet lateness (ms) before being discarded
voipomitpackets	voip_omitpackets	VoIP plugin: Number of packets to omit from calculations from start of stream