ADC Automation v11 & v12 Networking v1.11

Transcription

1 ADC Automation v11 & v12 Networking v March-2015 Revision: Release

2 Publication Information 2015 Imagine Communications Proprietary and Confidential. Imagine Communications considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of Imagine Communications. All others uses are illegal. This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product. Trademarks Product names and other brands (such as ADC, D-Series, Nexio, Nexio Insight, Nexio Motion, PowerSmart, Versio ) are trademarks or trade names of Imagine Communications or its subsidiaries. Microsoft and Windows are registered trademarks of Microsoft Corporation. All other trademarks and trade names are the property of their respective companies. Contact Information Imagine Communications has office locations around the world. For domestic and international location and contact information see: Support Contact Information For domestic and international support contact information see: Support Contacts: ecustomer Portal: Imagine Communications Proprietary and Confidential 17-March-2015 Page 2 of 32

3 Contents Contents About this Document... 5 Scope... 5 Important Service Pack and Update Note... 5 Important Note about Automation Environment... 5 Bandwidth Requirements... 5 Network Stability... 6 Alternative to Remote API Connections... 7 Important Note about CHP Onboard NICs... 7 Important Note about Windows OS Component Configuration... 8 Network Adapter Settings... 9 Protocols... 9 Link Speed and Duplex... 9 Receiving Buffer Disable Delay Ack Enter the new registry entry Windows AutoTuning Level To disable AutoTuningLevel To check status of AutoTuningLevel Configuring Network Discovery Enabling Network Discovery (Windows 7 Client) Network Redundancy for ADC Fault-Tolerant networks Adapter Fault Tolerance (AFT) Switch Fault Tolerance (SFT) Imagine Communications Proprietary and Confidential 17-March-2015 Page 3 of 32

4 Contents Mixing AFT/SFT technologies Intel Advanced Network Services Setting up Adapter Fault Tolerance IP Schemes Configuring IPv4 Addresses Configuring IPv6 Addresses Additional Changes Required for Version 11 environments Set LANA Priority Install LanaConfig Run LanaConfig Enable NetBIOS Implementing IPv6 on Cisco Networks Windows 7 Specific Recommended Settings Introduction Device Server Network Location Set User Account Control settings to the lowest option To verify, go to: Set Network List Manager Policies Local Security Policy settings Select the High performance profile Power Options settings Disable power management for all NICs Power Management Network settings Imagine Communications Proprietary and Confidential 17-March-2015 Page 4 of 32

5 About this Document About this Document Scope This document presents the procedures and processes necessary to configure the network for an ADC environment utilizing Windows Server 2008 and Windows 7 Device Servers and client computers. This document does not cover all fire wall settings or anti-virus recommendations. For those requirements please see the appropriate Operating System Installation Guide and the ADC Safe Networking Guide. Important Service Pack and Update Note It is important that all Service Packs and Updates be applied to all computers on the network. To maximize performance of the network, the latest network interface drivers should be installed for all network interface cards as well. Intel NIC driver version is needed for proper network communication. You can use this link to download new versions for Intel NIC drivers: Important Note about Automation Environment It is important that the Automation Network remain as isolated as possible and no systems not approved for Automation be connected. A dedicated switch or vlan for automation is recommended. Please contact Automation Technical Support for further information. Bandwidth Requirements When deployed on a single, physical gigabit network, essentially no bandwidth issues will be encountered- aggregate systems with literally hundreds of lists and devices have been run. However, in cases where bandwidth limitation occurs, it is critical that the ADC system be provided with sufficient bandwidth. There are two primary types of connections- SQL connections, between the clients and the fileserver; and API connections between the device servers and the clients. The bandwidth required for the SQL database connections is relatively small, is used only 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 5 of 32

6 About this Document intermittently, and can be throttled with relatively little or no effect on the operation of the automation. However, the ADC API connection, in addition to handling control transactions, also contains a real time broadcast of the status of status of each device server s lists and controlled devices, as well as general clocking and status- this data is sent by the device server every video frame and the clients depend on this real time data stream for their display. The bandwidth required to make and maintain this data stream is dependent on the scope of a device server s configuration- and the number of lists and devices increases, the bandwidth does as well. In addition to the real time stream, additional data is also sent from the device server to the clients- the contents of the list, storage collections of devices, and other system data. These items are relatively static, in comparison to the dynamic status, and are therefore not repeated and represent a relatively small amount of data in comparison to the real time stream. However under certain operational conditions, the amount of this data will increase- such as loading or appending lists, reinitializing devices (particularly with large storage collections), or editing and manipulating the system. These increases do not have to be handled in the same real time manner as the status, but do affect the overall bandwidth available on the network. Finally, there is an interconnection between the device servers- but this is used only intermittently, with extremely low data dates. Because the status data is multicast, it does not have to be repeated when multiple clients utilize it. This means that the largest portion of the bandwidth requirements will remain constant, even when the same list is displayed on multiple clients. However, all of the device servers API streams are potentially available to all clients- it is the client application that determines which device servers data will be displayed. Each device server s bandwidth requirements are essentially independent, and therefore the total bandwidth will be the sum of the individual device servers As an example of the data throughput, a system with two device servers, each running 16 lists and with a total of 74 device heads was measured as generating a constant data stream of approximately 750 Kb/S, with a peak (on an unthrottled gigabit network) of approximately 1.5 Mb/S.. It is also critical that the network environment on which ADC is deployed have a low intrinsic latency, and a low rate of out of order packet delivery. In the case on a local physical network, this is not an issue, and even geographically dispersed WANs can be provisioned accordingly. However, connections across public networks, even those using VPNs, or using varied topographies, are likely to be unacceptable. In addition, an ideal network should also have a low rate of dropped and/or retransmitted packets. Network Stability When the network is unable to continuously support ADC s requirements, various impacts may be observed. In general, these will not affect the actual real time playout of lists that are already resident in the Device Server- although control of network connected devices is of course of potential concern. In general, the most likely and immediate effect is a slowdown in the display and response of the client applications. In some cases operations that depend on immediate feedback may become unusable. Furthermore, because of the mix is frame rate and session data, actions such as repetitive database access might be slowed to a degree not directly proportional to the network deficit Imagine Communications Proprietary and Confidential 17-March-2015 Page 6 of 32

7 About this Document Equally important, the characteristics of the network are expected to remain relatively constant. Changes to the available bandwidth or latency while the system is operational can have a significant negative impact on system operation and stability. ADC depends on the interconnection of the various components of the system- the Device Server(s), the various client applications, the file server, and any interconnected systems. Thus should the connection between any of these components become negatively affected, the stability of the system as a whole can be impacted. Even intermittent disruptions in connectivity can affect aspects of the system. In some cases, a disconnection of a portion of the system will require the restarting of other applications or services to restore full functionality. Furthermore, some data, such as logging of As-Runs and error may be lost. Alternative to Remote API Connections In cases where it is necessary to have an operating control point distant from the Device Server, it may be possible to remotely connect a client through a WAN connection. However, it many cases, use of Remote Desktop or a similar application may be preferable. This eliminates the need for the ADC API to be transported across the WAN. In general, all of a client s functionality is available when controlled via Remote Desktop. The most significant limitation is the inability to utilize a hardware control panel. In addition, a client has the ability to connect to multiple Device Servers when the Device Servers are also remote. Important Note about CHP Onboard NICs The CHP chassis used for the ADC Device Server, in both 4RU and 2RU configurations, has two NICs onboard the SBC (Single Board Computer). One of these NICs is dedicated for the ADC automation network providing the connection between the Device Server and the clients, and the other is used to provide an IP control connection. These NICs are supported by all OSs deployed with ADC, up through and including Windows Server 2008 and Windows Server However, a serious issue has been identified with these NICs that can affect the operation of ADC in certain network environments. Symptoms of this issue vary in presentation and severity, but are typified by intermittent client disconnects, list stoppages, and errors in list timing as indicated by anomalous LONG events in asruns. While these symptoms may be due to a variety of factors, in multiple cases it has been determined to be related to the onboard NICs. Furthermore, these issues are related to the capabilities and characteristics of the chipset itself and therefore cannot be addressed with a driver update. All of the conditions that may affect the NICs has not been determined, but one factor that has been identified is the presence of jumbo frames on a network connected to either of the CHP NICs. ADC does not utilize jumbo frames and it is not necessary for the jumbo frame traffic to be directed to a connection on the Device Server /CHP chassis. The presence of jumbo frames on the network can be sufficient to cause anomalous behavior. In cases where anomalous behavior is present, replacing the onboard NICs may be necessary to correct the issue(s). The Intel Pro 1000 GT NIC has been identified and tested, both internally and in the field, and found to be both compatible and effective in this regard Imagine Communications Proprietary and Confidential 17-March-2015 Page 7 of 32

8 About this Document Note that while jumbo frames have been identified as an issue, there have been cases where jumbo frames are not found to be present, but anomalous behavior is present, and in some cases the replacement of the onboard NICs has been effective. Note: Effective troubleshooting is critical to determine the cause of failures. This section is not intended to imply that replacing the onboard NICs is necessary or beneficial in all cases. If it is determined that the onboard NICs should be replaced, both onboard NICs should be replaced if in use, and the onboard NICs disconnected and disabled. All network connections should be via the replacement Intel Pro 1000 GT NICs. Note: Contact Automation Technical Support for assistance. Important Note about Windows OS Component Configuration When ADC computer hardware is supplied by Imagine Communications, the Windows installation will be tuned and configured specifically for this use. In cases where customer supplied computers, either in the form of physical computers or virtual machines, are utilized, it is critical to realize that a standard Windows installation will enable various features and services which can dramatically impact the availability of the computer and the network. Furthermore, many hardware vendors include additional applications and services. Examples of features and applications that have been demonstrated to impact system stability include: Windows Update (Automatic updates should never be enabled) Firewalls Anti-Virus and Anti-Malware software Messaging applications Download Managers It is recommended that a clean Windows installation be performed on computers to be used in an ADC installation. In addition to applications that directly affect the network, certain user interface configurations can have a dramatic impact on the responsiveness of the user interface. Note: Installation guides for each supported OS are available. Contact Automation Technical Support for assistance Imagine Communications Proprietary and Confidential 17-March-2015 Page 8 of 32

9 Network Adapter Settings Network Adapter Settings Protocols Communication between ADC clients and device servers use IPv6. Communication between clients and file servers use IPv4. It is important to note that while IPv6 addressing occurs automatically, the IPv4 addressing schemes must be set up correctly for the device servers to talk to the client computers. Due to the implementation of IPv6 unicasting, ADC has completely eliminated its dependency on NetBIOS, allowing a pure IP based platform. IPv6 is more efficient than the NetBIOS over IP option used in v11. If the computer has multiple Network Interface Cards, it is highly recommended to disable IPv6 on the NICs not on the automation LAN, even if the NIC itself is disabled. Link Speed and Duplex If the automation environment includes a managed router, link speed and duplex may be set there. ADC requires a Gigabit Ethernet network. Other settings may be required to enable IPv6 as well Imagine Communications Proprietary and Confidential 17-March-2015 Page 9 of 32

10 Network Adapter Settings If a unmanaged switch or standalone switch is used, link speed and duplex may need to be set in the network adapter of each computer on the network. One Gigabit and full duplex should be selected. Receiving Buffer Increasing the Receive Buffer value can help prevent networking timeout issues in case of dropped packets Imagine Communications Proprietary and Confidential 17-March-2015 Page 10 of 32

11 Network Adapter Settings Power Management Disable Allow the computer to turn off this device to save power. Disable Delay Ack TcpAckFrequency is a registry setting that determines the number of TCP acknowledgments (ACKs) that will be outstanding before the Delay ACK timer is ignored. Setting the Registry value TcpAckFrequency to 1 will disable Delay ACK. This will prevent the resend processing time from going to 5 frame/sec when a packet is dropped. Using this method will not prevent packets from being dropped, but even if they are dropped the resend processing delay will be improved, so that time outs should not occur. Enter the new registry entry 1. Click Start, Run, type regedit in the Open: field of the Run window, and click OK. 2. Double click on HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, Tcpip, Parameters, and then Interfaces. 3. Highlight, (one at a time), an item in the Interfaces sub tree. 4. Look on the right side of the screen for the IP Address of the NIC that you wish to change. 5. With the correct item in the Interfaces sub tree highlighted, right click on the right side of the screen, and pop-up named New will appear Imagine Communications Proprietary and Confidential 17-March-2015 Page 11 of 32

12 Network Adapter Settings 6. Place the cursor on New, select DWORD Value, and type in TcpAckFrequency. 7. Double click on TcpAckFrequency, enter 1 into the Value data: window, and click OK. 8. Close the Registry Editor, disable and then re-enable this NIC, or reboot the computer. Windows AutoTuning Level The TCP receive window size (RWIN) is the amount of data that a TCP receiver allows a TCP sender to send before having to wait for an acknowledgment. After the connection is established, the receive window size is advertised in each TCP segment. Advertising that maximum amount of data that the sender can send is a receiver-side flow control mechanism that prevents the sender from sending data that the receiver cannot handle. A sending host can only send - at a maximum - the amount of data advertised by the receiver before waiting for an acknowledgment and a receive window size update. Auto Tuning adjusts the receive windows size continually based upon the changing network conditions. Disabling AutoTuningLevel will prevent the window from expanding. As a result, there will be a great reduction in the receiving rate, making it more difficult to drop packets. By default, Windows Server 2008 in normal auto tuning level will use RWIN size of 256 bytes with a scale factor of 8. This value is not suitable for all routers and servers which may not support TCP scale factor. Windows XP x64 (NEXIO Server) does not support the TCP receive window auto tuning feature. To disable AutoTuningLevel 1. Open a command prompt as administrator 2. Type: netsh interface tcp set global autotuninglevel=disabled To check status of AutoTuningLevel 3. Open a command prompt as administrator 4. Type: netsh interface tcp show global 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 12 of 32

13 Configuring Network Discovery Configuring Network Discovery Enabling Network Discovery (Windows 7 Client) Network discovery should be enabled on all Clients. 5. Right click on the Network icon on the desktop and select Properties. 6. In the left column of the Network and Sharing Center, click on Change advanced sharing settings. 7. From here you can turn on Network Discovery. Network Discovery must be enabled for Windows 7 Client computers to be seen on the network Imagine Communications Proprietary and Confidential 17-March-2015 Page 13 of 32

14 Network Redundancy for ADC Network Redundancy for ADC Fault-Tolerant networks Network redundancy is a set of techniques which are intended for providing continuity of business in case of some technical failures. These failures may be: cable failure (such as physical rupture, which is important for campus-area networks), switching equipment/port failure, or NIC failure. Fault tolerance for networks is provided through redundancy of critical network components. Intel Advanced Network Services provide two main methods of redundancy for ADC network: Adapter Fault Tolerance (AFT) Example: AFT combines a group of physical NICs into one logical interface (team). One physical NIC within such team remains as active and all other are remain as standby. Redundancy is provided through automatic failovers from an active adapter to a standby adapter in the case of switch port, cable, or adapter failure. Characteristics of AFT are: AFT supports two to eight adapter ports per team. Team members do not have to run at the same speed or duplex. No switch configuration is required for this team type. This teaming type works with any switch or hub. An example of AFT with two NICs in the DS is show below: NIC 1 NIC 2 AFT Team Active link Standby link Device Server Network Switch Switch Fault Tolerance (SFT) Like an AFT, this method combines a group of physical NICs into one logical interface (team). The difference is that SFT provides redundancy across switches. An adapter connected to one switch 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 14 of 32

15 Network Redundancy for ADC Example: will automatically failover to a standby adapter connected to a different switch in the event of a switch, switch port, cable, or adapter failure. Characteristics of SFT are: SFT supports only two adapter ports per team. Each port is connected to a separate switch. Team members do not have to run at the same speed or duplex. No switch configuration is required. This team type is supported by any switch, but is not supported on hubs. The main benefit of SFT is a switch fault tolerance. An example of SFT is shown below: Network Switch #2 Network Switch #1 NIC 1 NIC 2 SFT Team Active link Standby link Device Server Note: Inter-switch connections must be redundant too. Such connections are built by meaning of link aggregation protocols (such as LACP/PAGP), stacking or loop prevention protocols (STP). These protocols are outside the scope of this guide. Mixing AFT/SFT technologies AFT/SFT technologies may be mixed among the ADC network: 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 15 of 32

16 Network Redundancy for ADC Workstation NIC 1 NIC 2 AFT Team Active and standby link Network Switch #2 Inter-switch redundant link Network Switch #1 NIC 1 NIC 2 SFT Team Active link Standby link Active link Stanby link NIC 1 NIC 2 SFT Team Device Server#1 Device Server#2 Intel Advanced Network Services Intel Advanced Network Services provide some other techniques of redundancy: EtherChannel, Link Aggregation, Load-balancing and so on. They are not recommended for use, since they give no significant advantages and are much more complicated to configure. Setting up Adapter Fault Tolerance Use this procedure to set up Adapter Fault Tolerance. 8. From Windows Device Manager, right click on a Network Adapter and select Properties. Select the Teaming tab. (If the Teaming Tab is not available you need to update the NIC driver.) 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 16 of 32

17 Network Redundancy for ADC 9. Click the Team this adapter with other adapters check box. 10. This brings up the New Team Wizard that lets you configure the Team. Specify a Name for the Team Imagine Communications Proprietary and Confidential 17-March-2015 Page 17 of 32

18 Network Redundancy for ADC 11. Select the adapters that will be teamed together. 12. Select Adapter Fault Tolerance for the Team Type Imagine Communications Proprietary and Confidential 17-March-2015 Page 18 of 32

19 Network Redundancy for ADC 13. Click on the Finish button. 14. The New Team Wizard will then configure the team. This will take a few seconds. 15. The new Team will now appear in the Team drop down selection Imagine Communications Proprietary and Confidential 17-March-2015 Page 19 of 32

20 Network Redundancy for ADC 16. Click on the Properties Button to ensure the team is working correctly. 17. This is how the Team will look in the Device Manager window Imagine Communications Proprietary and Confidential 17-March-2015 Page 20 of 32

21 Network Redundancy for ADC 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 21 of 32

22 IP Schemes IP Schemes Configuring IPv4 Addresses It is recommended that a Class C IP scheme be used with the supplied network switch. If automation is being installed in a VLAN environment, Class A or B networks may be used. Class C network addresses begin at and end at The default subnet mask is Configuring IPv6 Addresses The IPv6 configuration should be set to Obtain an IPv6 address automatically and Obtain DNS server address automatically Imagine Communications Proprietary and Confidential 17-March-2015 Page 22 of 32

23 Additional Changes Required for Version 11 environments Additional Changes Required for Version 11 environments Set LANA Priority Use the following procedure for configuring Windows Server 2008 Device Servers and Windows 7 Clients to use Lana number 0. IMPORTANT: The differences between running LanaConfig for a 32-bit system and a 64-bit system are indicated below. Install LanaConfig 32-Bit System 64-Bit System 18. Locate Lanacfg.exe, highlight it, right click, and select Copy. 19. Browse to C:\Windows\System32, right click, and select Paste. 20. Close the Windows Explorer. 21. Locate Lanacfg.exe, highlight it, right click, and select Copy. 22. Browse to C:\Windows\SysWOW64, right click, and select Paste. 23. Close the Windows Explorer. Run LanaConfig 24. Select Start\All Programs\Accessories, hover over Command Prompt, right click, and select Run as administrator: 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 23 of 32

24 Additional Changes Required for Version 11 environments 25. Run Lana Config: For 32-bit Systems ensure the Command Prompt is set to c:\windows\system32, enter lanacfg showlanapaths, and then press Enter on the keyboard. For 64-bit Systems set the Command Prompt to c:\windows\syswow64 (i.e. at the prompt type "cd\windows\syswow64"), enter lanacfg showlanapaths, and then press Enter on the keyboard. 26. Identify which Adapter is currently bound to lana 0, and which one needs to be changed to it. 27. In the following example lana 0 is currently bound to the Internet Protocol Version 4 <TCP/IPv4>-->Intel <R> PRO/1000 PL Network Connection #2, and the Internet Protocol Version 4 <TCP/IPv4>--> Intel <R> PRO/1000 PL Network Connection, (currently bound to lana 6), is the one that needs to be configured to lana 0: 28. To make lana 0 available enter lanacfg setlananumber 0 5, (the second number can be any number that is not currently displayed), and press Enter on the keyboard: 29. Enter lanacfg setlananumber 6 0 and press Enter on the keyboard: 30. Enter lanacfg rewritelanainfo and press Enter on the keyboard: 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 24 of 32

25 Additional Changes Required for Version 11 environments 31. To confirm the changes enter lanacfg showlanapaths and press Enter on the keyboard. The Internet Protocol Version 4 <TCP/IPv4>-->Broadcom NetExtreme Gigabit Adapter is now bound to lana 0: 32. Close the Command Prompt by entering exit and pressing Enter on the keyboard, or by using the X in the upper right corner of the window: 33. Restart the computer. Enable NetBIOS Version 11 device servers utilize NetBIOS for communication. As such it is needed to enable NetBIOS over TCP/IP. To Configure Network Communications 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 25 of 32

26 Additional Changes Required for Version 11 environments 34. Select the NIC that was configured to Lana 0, right click, and select Properties. 35. Select Internet Protocol Version 4 (TCP/IPv4) and then click Properties. 36. Select Use the following IP address, enter the given IP address, Subnet mask (and DNS address(es) if applicable), and then select Advanced. 37. Select the WINS tab, in the NetBIOS setting area select Enable NetBIOS over TCI/IP, and click OK: Implementing IPv6 on Cisco Networks The following link contains information for implementing Cisco IPv6 Networks: Imagine Communications Proprietary and Confidential 17-March-2015 Page 26 of 32

27 Windows 7 Specific Recommended Settings Windows 7 Specific Recommended Settings Introduction The following section describes specific settings to verify when running NEXIO software with Windows 7. Device Server Network Location Change the Win7 Network location from Public to Private on all Device Servers Set User Account Control settings to the lowest option Requires that the User Account Control settings to be set to the lowest option. To verify, go to: 1. Control Panel > All Control Panel Items > User Accounts 2. Change User Account Control settings 3. Set to the lowest option (Never Notify) Set Network List Manager Policies By default, Windows 7 considers all new networks public and inhibits traffic flow. For machines with multiple adapters, where all adapters are connected to a trusted network, it is necessary to set Network List Manager Policies to allow the connection(s) to be trusted, overriding the default behavior. Local Security Policy settings To verify this setting, there are two ways to access the Local Security Policy console: 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 27 of 32

28 Windows 7 Specific Recommended Settings 1. Start > All Programs > Administrative Tools > Local Security Policy 2. Press the Windows key, and then click Run to open the Run dialog. Type: secpol.msc, and then click OK. The Local Security Policy dialog appears. 3. Click Network List Manager Policies. 4. Right-click Unidentified Networks, and click Properties. The Unidentified Networks Properties dialog appears. 5. In the Location type area, select Private. 6. Click Apply. 7. Click OK Imagine Communications Proprietary and Confidential 17-March-2015 Page 28 of 32

29 Windows 7 Specific Recommended Settings 8. Right-click Identifying Networks, and click Properties. The Identifying Networks Properties dialog appears. 9. In the Location type area, select Private. 10. Click Apply. 11. Click OK. Select the High performance profile By default, Windows 7 selects a Balanced power plan which inhibits power management for various devices, Display, HDD, USB..etc. For optimal performance, select the High performance profile which requires navigation of the plan settings to configure additional options. Power Options settings To verify this setting, navigate to: 1. Start > Control Panel > Power Options NOTE: It may be necessary to change the Control panel view from Category to Small icons Imagine Communications Proprietary and Confidential 17-March-2015 Page 29 of 32

30 Windows 7 Specific Recommended Settings 2. Select: High performance > Change plan settings 3. Set: Turn off the display = Never 4. Set: Put the computer to sleep = Never 5. Select: Change advanced power settings 6. Set the following options: Hard disk Sleep after Link State Power Management 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 30 of 32

31 Windows 7 Specific Recommended Settings Turn off display after JavaScript Timer Frequency 2015 Imagine Communications Proprietary and Confidential 17-March-2015 Page 31 of 32

32 Windows 7 Specific Recommended Settings Disable power management for all NICs By default, the Network Interface Card (NIC) sets the power management. For optimal performance, disable power management for all NICs. NOTE: The NIC power management is separate from the Windows 7 Power Options and must be checked separately. Power Management Network settings To verify this setting, navigate to: 1. Start > Control Panel > Network and Sharing Center 2. From the left window pane, select: Change adapter settings 3. Right-click Ethernet 1 and select: Properties 4. From the Properties window, select: Configure 5. From the Network Connection Properties window, select: Power Management 6. Un-check any option stating, turn off this device to save power 7. Once set, click: OK and repeat for remaining NICs. Once completed, proceed to install and/or launch NEXIO applications Imagine Communications Proprietary and Confidential 17-March-2015 Page 32 of 32