Nexio NX1010 MIOH Media Host

Transcription

1 User Guide Nexio NX1010 MIOH Media Host April Delivering the Moment

2 Publication Information 2014 Imagine Communications Corp. 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 6800+, ADC, CCS Navigator, Channel ONE, ChannelView, ClipSync, Delay, D-Series, D-Series DSX, Deliver the Moment, Delivering the Moment, FAME, Farad, G8, G-Scribe, HView, IconMaster, IconLogo, IconStation, IconKey, InfoCaster, InfoCaster Creator, InfoCaster Manager, InfoCaster Player, InstantOnline, Invenio, Live-Update, mcapture, Magellan, Magellan CCS Navigator, Magellan Q-SEE, MultiService SDN, NetPlus, NetVX, NewsForce, Nexio G8, Nexio AMP ChannelView, Nexio Channel ONE, Nexio ClipSync, Nexio Delay, Nexio Digital Turnaround Processor, Nexio Farad, Nexio G- Scribe, Nexio IconKey, Nexio IconLogo, Nexio IconMaster, Nexio IconStation, Nexio InfoCaster, Nexio InfoCaster Creator, Nexio InfoCaster Manager, Nexio InfoCaster Player, Nexio InfoCaster Traffic, Nexio InstantOnline, Nexio mcapture, Nexio NewsForce, Nexio NXIQ, Nexio Playlist, Nexio Remote, Nexio RTX Net, Nexio TitleMotion, Nexio TitleOne, Nexio Velocity ESX, Nexio Velocity PRX, Nexio Velocity XNG, Nexio Volt, OPTO+, Panacea, Platinum, Playlist, Predator II-GRF, Predator II-GX, Punctuate, Remote, RTX Net, QuiC, Q-SEE, SD-STAR, Selenio, Selenio 6800+, SelenioNext, Selenio X50, Selenio X85, Selenio X100, TitleMotion, TitleOne, Velocity ESX, Velocity PRX, Velocity XNG, Versio, Videotek SD-STAR, X50, and X85 are trademarks of Imagine Communications or its subsidiaries. Altitude Express, Connectus, Enabling PersonalizedTV, ICE Broadcast System, ICE Illustrate, ICE-Q algorithms, ICEPAC, Imagine ICE, Inscriber, Inscriber Connectus, Invenio, NEO, Nexio, Nexio AMP, PersonalizedTV, RouterWorks, Videotek, Videotek ASI-STAR, Videotek GEN-STAR, and Videotek HD- STAR are registered trademarks of Imagine Communications or its subsidiaries. Microsoft and Windows are registered trademarks of Microsoft Corporation. HD-BNC is a trademark of Amphenol Corporation. Some products are manufactured under license from Dolby Laboratories. Dolby and the double-d symbol are registered trademarks of Dolby Laboratories. DTS Neural audio products are manufactured under license from DTS Licensing Limited. DTS and the Symbol are registered trademarks & the DTS Logos are trademarks of DTS, Inc DTS, Inc. All other trademarks and trade names are the property of their respective companies. Contact Information Imagine Communications has office locations around the world. For locations and contact information see: Support Contact Information For support contact information see: Support Contacts: ecustomer Portal: Imagine Communications Corp. Proprietary and Confidential

3 iii Contents About This Guide... 1 Intended Audience... 2 Finding Specific Information in This Guide... 2 Writing Conventions... 3 Related Documentation... 3 Obtaining Documentation... 4 Purchasing Documents... 7 Unpacking/Shipping Information... 8 Technical Support... 9 Chapter 1 Media Host Configuration NX1000MIOH Media Host Failover Topology Physical Layer Interconnect Requirements Ethernet Switch Minimum Requirements Network Usage of a Media Host Failover System NXUSBTC LTC Input Module on Media Host Failover Systems Commissioning the System/Configuration System Software and Firmware Versions IP Addresses and Registry Settings Switch Settings Intel Network Interface Card (NIC) Settings NVIDIA Network Interface Card (NIC) Settings Proper Flow Control in Extreme 450 Series Switches... 46

4 iv Contents Special Registry Settings...47 Startup, Test, and Fine Tune...50 Chapter A Real Time Analysis of Network Stability...57 Real Time Analysis of Network Stability...57 Setting up Perfmon to Monitor Network Counters...57 Monitoring Segments Retransmitted...64 Glossary...67

5 1 About This Guide About This Guide provides an overview of this guide, describes guide conventions, and tells you where to look for specific information. This section also provides important information on unpacking and shipping your Harris product. This guide introduces and describes procedures for configuring, commissioning, and monitoring NEXIO NX1000MIOH Media Host. If the information in the release notes shipped with your product differs from the information in this guide, follow the instructions in the release notes.

6 2 About This Guide Intended Audience This guide is intended for users installing and operating NEXIO NX1000MIOH Media Host. Finding Specific Information in This Guide This table shows the location of specific information in this guide. If you are looking for Overview information about NX1000MIOH Media Host Configuring NX1000MIOH Media Host Commissioning NX1000MIOH Media Host Monitoring NX1000MIOH Media Host Go to NX1000MIOH Media Host Failover Topology on page 11 Commissioning the System/Configuration on page 20 Commissioning the System/Configuration on page 20 Real Time Analysis of Network Stability on page 57

7 NEXIO NX1000MIOH User Guide 3 Writing Conventions This guide uses the following writing conventions. Convention Bold Italics CAPS Code Definition Indicates dialog box, property sheet, field, button, check box, list box, combo box, menu, submenu, window, list and selection names. Indicates addresses, names of books and publications, and first instances of new terms and specialized words that need emphasis. Indicates a specific key on the keyboard, such as ENTER, TAB, CTRL, ALT, DELETE. Indicates variables or command-line entries, such as a DOS entry or something you type into a field. > Indicates the direction of navigation through a hierarchy of menus and windows. hyperlink internet address Note text Indicates a jump to another location within the electronic document or elsewhere. Indicates a jump to a website or URL. Indicates important information that helps to avoid and troubleshoot problems. text text Caution Warning Indicates important information that if not followed could cause system problems. Indicates information that if not followed could prevent system operation or cause it damage. Related Documentation NEXIO NX1000MGX Hardware Guide ( ) NEXIO NX1000MGX Installation Quick Start ( ) NEXIO Low Level Module User Guide ( ) NEXIO NXOS User Guide ( , REV A) NEXIO Safety and Compliance Manual ( )

8 4 About This Guide Obtaining Documentation Manuals, User Guides, and other documents can be viewed or downloaded from the Harris website at The Welcome to Harris BCD Support web page appears (see Figure 1). New User Figure 1 Welcome to Harris BCD Support 1 In the Customer Login area, enter your User ID and Password, and click Submit. If you do not sign in, you are redirected to Customer Login. OR Click New User to register with Harris.

9 NEXIO NX1000MIOH User Guide 5 The Harris BCD Support Home web page appears (see Figure 2). Review Documentation Figure 2 Harris BCD Support Home 2 Click Review Documentation.

10 6 About This Guide The documentation Table of Contents, and What s New - Documentation web page appears (see Figure 3). Figure 3 Documentation Table of Contents 3 In the Table of Contents list, click the category of the document to display the available documents.

11 NEXIO NX1000MIOH User Guide 7 The available documents for the selected category appear (see Figure 3). Figure 4 Available Documents 4 Click on the title of the desired document, and then click Open to view the document. OR Click Save and select a location to which to download the document. Tip: If you are having trouble finding a document, enter the title of the document or a keyword in the Search box, and then click Go. Purchasing Documents Additionally, you can purchase product documentation on our Harris E-commerce site, or contact your Harris customer service representative to request a document.

12 8 About This Guide Unpacking/ Shipping Information Unpacking a Harris Product All Harris NEXIO products have been carefully inspected, tested and calibrated before shipment to ensure stable and trouble-free service. 1 Check the equipment for any visible damage that may have occurred during transit. 2 Confirm that you have received all items listed on the packing list. 3 Contact your Harris NEXIO dealer if any item on the packing list is missing. 4 Contact the carrier if any item is damaged. 5 Remove all packaging material from the product and its associated components before you install the unit. Returning a Harris Product In the unlikely event that a Harris product fails to operate properly, contact the Harris NEXIO Customer Service Department to obtain a Return Authorization (RA) number, then send the unit back for servicing. Include the RA number on the outside of the return box. Keep at least one set of original packaging in the event that a product needs to be returned for service. If the original package is not available, you may purchase replacement packaging from Harris Corporation. Otherwise, you may supply your own packaging as long as it meets the following criteria: The packaging must be able to withstand the product s weight. The product must be held rigid within the package. There must be at least 2 inches (5 cm) of space between the product and the container. The corners of the product must be protected. If the product is still within the warranty period, Harris Corporation will return it to you by prepaid ground shipping after servicing.

13 NEXIO NX1000MIOH User Guide 9 Technical Support Technical support is available 24 hours a day, 7 days a week. You can contact technical support by phone or . Harris Broadcast Division Support: Toll Free: +1 (888) BCDService@harris.com Video Server Division LTIServiceServers@harris.com U.S., Canada, Central America, and Latin America (CALA) Video Processing, Distribution, Servers, Storage, News, Inscriber and Videotek Call: Fax: BCDService@harris.com Europe, Middle East, and Africa 24 hours a day, 7 days a week Regular Business Hours (9am to 5pm, Monday to Friday) 24/7 Support line: Fax: Infrastructure products: Service.europe@harris.com RMA s: RMArequest.europe@harris.com DAM Support: HClassDAMsupport.emea@Harris.com ADC Automation: HasHelp@Harris.com D Series Support: DALSupport@Harris.com Transmitters: SupportTX.EMEA@Harris.com

14 10 About This Guide Asia, Pacific Rim 24 hours a day, 7 days a week Regular Business Hours (9am to 5pm HKT Monday to Friday) Call: After-Hour Hotline: Fax: BCDService@harris.com

15 11 1 Media Host Configuration This chapter provides Media Host Failover topology and configuration information needed to commission a NEXIO system that uses NX1000MIOH Media Host to connect NEXIO clients (I/O nodes) to Gigabit Ethernet. This chapter includes the following sections: NX1000MIOH Media Host Failover Topology Commissioning the System/Configuration NX1000MIOH Media Host Failover Topology The NX1000MIOH Media Host Failover Topology section contains the following: Physical Layer Interconnect Requirements on page 15 Ethernet Switch Minimum Requirements on page 16 Network Usage of a Media Host Failover System on page 16 NXUSBTC LTC Input Module on Media Host Failover Systems on page 19

16 12 Chapter 1 Media Host Configuration The NX1000MIOH Media Host contains two motherboard Ethernet network ports, two Fibre Channel ports, and four peripheral card Ethernet network ports (see Figure 1-1). Motherboard Ethernet Fibre Channel Ports Network Ports Figure 1-1 NX1000MIOH Media Host Peripheral Card Ethernet Network Ports Figure 1-2 shows the NX1000MIOH Media Host Failover topology. The system is designed to support N + 1 Media Host servers streaming data from Fibre Channel shared storage over Ethernet to clients (I/O nodes) that are attached via Ethernet. This system design allows NEXIO to scale to very large channel counts, without being vulnerable to single points of failure in the connective layer. Groups of clients (I/O nodes) are not supported by single Ethernet to Fibre Channel bridge device. Instead, each client (I/O node) is able to automatically and seamlessly change to an alternate Media Host server in the event there are communication problems with their primary NX1000MIOH Media Host.

17 NEXIO NX1000MIOH User Guide 13 Figure 1-2 Media Host Failover Topology The two logical Ethernet data connections from each client (I/O node) terminate at separate Media Host frames. The failure of any one Media Host frame will not affect ongoing client (I/O node) operations. In this topology, the logical data connections are distributed among the population of Media Host frames via a distance pairing distribution algorithm. This algorithm assigns client (I/O node) connections to the Media Host frames such that failure of an Media Host frame will result in an even distribution of additional load to the remaining Media Host frames. This topology is redundant to all physical layer failures when installed in compliance with the following requirements: The physical layer connections from each device; Media Host servers and clients (I/O nodes) are split evenly between two different Ethernet infrastructures, or carried on different blades of an enterprise class switch. The logical connections are configured so that the failure of any one piece of hardware (NIC, cable, switch or blade) will not result in lost connectivity on both connections simultaneously. Figure 1-3 shows all logical connection pairs of a sample Media Host Failover topology with four MIOHs and 24 clients (I/O nodes).

18 14 Chapter 1 Media Host Configuration Primary = 0 Backup = 0 Primary = 1 Backup = 1 Primary = 2 Backup = 2 Primary = 3 Backup = 3 Clients 0, 12 Primary MIOH = 0 Backup MIOH = 1 Primary MIOH = 2 Backup MIOH = 0 Clients 6, 18 Clients 1, 13 Primary MIOH = 1 Backup MIOH = 2 Primary MIOH = 3 Backup MIOH = 1 Clients 7, 19 Clients 2, 14 Primary MIOH = 2 Backup MIOH = 3 Primary MIOH = 0 Backup MIOH = 3 Clients 8, 20 Clients 3, 15 Primary MIOH = 3 Backup MIOH = 0 Primary MIOH = 1 Backup MIOH = 0 Clients 9, 21 Clients 4, 16 Primary MIOH = 0 Backup MIOH = 2 Primary MIOH = 2 Backup MIOH = 1 Clients 10, 22 Clients 5, 17 Primary MIOH = 1 Backup MIOH = 3 Primary MIOH = 3 Backup MIOH = 2 Clients 11, 23 MIOH 1 MIOH 2 MIOH 3 MIOH 4 Figure 1-3 Sample Media Host Failover Topology

19 NEXIO NX1000MIOH User Guide 15 Physical Layer Interconnect Requirements Figure 1-4 shows the physical connection pattern to assure redundancy at the physical layer. The physical layer connections of all clients (I/O nodes) and servers are evenly split among the two network infrastructures. The two network infrastructures can be any one of the following architectures: Two separate free standing switches most cost-effective solution Two blades in an enterprise class switch Two blade sets in an enterprise class switch (large systems) One blade or blade set in each of two enterprise class switches (best redundancy solution) The choice of infrastructure is based on the number of clients (I/O nodes) and servers, as well as on customer preference. Primary MIOH S0 = 0 Clients 0, 12 Clients 0, 12 Backup MIOH S1 = 1 Primary MIOH S0 = 1 Clients 1, 13 Clients 1, 13 Backup MIOH S1 = 2 Primary MIOH S0 = 2 Clients 2, 14 Clients 2, 14 Backup MIOH S1 = 3 Primary MIOH S0 = 3 Clients 3, 15 Clients 3, 15 Backup MIOH S1 = 0 Primary MIOH S0 = 0 Clients 4, 16 Clients 4, 16 Backup MIOH S1 = 2 Switch or blade 2 Switch or blade 1 Primary MIOH S0 = 1 Clients 5, 17Clients 5, 17 Backup MIOH S1 = 3 MIOH NIC 2, B, D; Client NIC 2 S0 Primary = 2 MIOH = 2 Clients 6, 18Clients 6, 18 S1 Backup = 0 MIOH = 0 S0 Primary = 3 MIOH = 3 Clients 7, 19Clients 7, 19 S1 Backup = 1 MIOH = 1 S0 Primary = 0 MIOH = 0 Clients 8, 20Clients 8, 20 S1 Backup = 3 MIOH = 3 S0 Primary = 1 MIOH = 1 Clients 9, 21Clients 9, 21 S1 Backup = 0 MIOH = 0 S0 Primary = 2 MIOH = 2 Clients 10, 22 Clients 10, 22 S1 Backup = 1 MIOH = 1 S0 Primary = 3 MIOH = 3 Clients 11, 23 Clients 11, 23 S1 Backup = 2 MIOH = 2 MIOH NIC 1, A, C; Client NIC 1 MIOH 1 MIOH 2 MIOH 3 MIOH 4 Figure 1-4 Physical Layer Example

20 16 Chapter 1 Media Host Configuration Ethernet Switch Minimum Requirements The network environment must meet all of the following criteria: 802.3x Flow Control must be supported by the switches. The TCP retransmissions incurred due to the switch infrastructure must not exceed 2 counts/second on any server or client (I/O node). This is measured during the commissioning phase ad link aggregation must not be used on any Ethernet ports supporting the Media Host interconnections. See the NEXIO Streaming SAN, NetworkServer Service, and NetDiskServer Service sections. The packet delay between any two nodes must not exceed 4 ms. The total amount of packet delay when a message is passed in sequence from the highest node to the lowest node must not exceed one video field time. This metric is displayed in the LLM Codec window as rt time in the XOR Read Activity window. For more information on the Codec window, see the NEXIO Low Level Module User Guide, Part # Both network infrastructures must not experience simultaneous outages longer than 100 ms. Both network infrastructures must offer the same speed and duplex specifications. The available NXES45024 and NXES45048 switches meet these requirements, as does the Extreme Black Diamond series switches. The NXES400xx series switches do not meet the flow control requirement and should not be used in Media Host Failover environments. Network Usage of a Media Host Failover System There are three network services used by every Media Host server frame described in this section: NEXIO Streaming SAN NetworkServer Service NetDiskServer Service

21 NEXIO NX1000MIOH User Guide 17 NEXIO Streaming SAN This peer to peer network service is supported only on the Media Host frames and on other nodes that are directly attached to the storage system via Fibre Channel. This network service is responsible for communicating all changes made by any Media Host or client (I/O node) to all the other server frames in the domain. The communication method used is layer 2 (UDP) broadcasts with acknowledgments returned circularly through all Media Host frames. At maximum usage the SAN can manage several hundred changes per second across all nodes on the NEXIO domain, resulting in hundreds of broadcast per acknowledgment cycle. This network service does not have a large data throughput requirement. The information per transaction is small (Standard IP packets), but the need for them to arrive at their destination on-time is important to system performance. This network service is bound to two configured IP addresses on different subnets, and assigned to the two motherboard ports on each Media Host. All Media Host frames require access to this service and must use the same two subnets, and use the same ordering in the Registry. The following example uses the default addresses for Media Host 1: HKCU\Software\ASC Audio Video\LLM\Control IPADDRESS = ; Primary UDP SAN binding, motherboard port 1 IPADDRESS1 = ; Redundant UDP SAN binding, motherboard port 2 In order to maintain the SAN communications, at least one of the subnets must be operating on all connected Media Host servers at all times. Using the example above, a failure of the network on one Media Host coupled with a failure of the network on a second Media Host will result in a non-functional SAN. Up to 4 subnets may be used for this network service by adding an IPADDRESS2 and IPADDRESS3 value to the registry and selecting subnets on the 4 port peripheral card.

22 18 Chapter 1 Media Host Configuration NetworkServer Service The NetworkServer Service is used by the Media Host to extend the NEXIO Streaming SAN communications path to the attached clients (I/O nodes). This service is available on TCP port 561 on all IP addresses configured on the Media Host. In practice, the four ports on the peripheral network card are the targets used for clients (I/O nodes) to attach to the service. By convention, the clients (I/O nodes) will attach to the service either on peripheral port pair A and B, or C and D. Each port pair is configured with consecutive subnet pairing. Clients (I/O nodes) are configured to attach to the NetworkServer service via two registry entries and will always result in redundant attachment to two Media Host servers, with different physical paths selected for each. For example: HKCU\Software\ASC Audio Video\LLM\Control NetworkServer = ; Primary NetworkServer connection to Media Host 1 NetworkServer1 = ; Redundant NetworkServer connection to Media Host 2 NetDiskServer Service The NetDiskServer Service extends the Fibre Channel SCSI block-based commands for storage and retrieval from the Media Host to the clients (I/ O nodes) over the Ethernet links. This is the service that transports video and audio data through the system, and therefore large amounts of data travel over these links. This service is available on TCP port 562 on all IP addresses configured on the Media Host. In practice, the four ports on the peripheral network card are the targets used for clients (I/O nodes) to attach to the service. By convention, the clients (I/O nodes) will attach to the service either on peripheral port pair A and B, or C and D. Each port pair is configured with consecutive subnet pairing.

23 NEXIO NX1000MIOH User Guide 19 Clients (I/O nodes) are configured to attach to the NetDiskServer service via two registry entries. The two entries will be provided by Harris with your System Drawings, and will always result in redundant attachment to two Media Host servers, with different physical paths selected for each. For example: HKCU\Software\ASC Audio Video\LLM\Parameters NetDiskServer = ; Primary NetDiskServer connection to Media Host 1 NetDiskServer1 = ; Redundant NetDiskServer connection to Media Host 2 The NetworkServer and NetDiskServer connections always point to the same IP addresses. FTP Server Service FTP Server is only supported on dedicated NX1000MGX servers. FTP Server cannot be used on NX1000MIOH or any client (I/O node) that is attached to Media Host via Ethernet. NXUSBTC LTC Input Module on Media Host Failover Systems As of this release, the timecode messaging will pass between the NetworkServer and UDP Streaming SAN networks. The only supported configuration of the NXUSBTC product is to attach one, and only one, LTC input module to one client anywhere in the system. Do not attach more than one NXUSBTC per system. Do not attach the NXUSBTC to an Media Host or MGX frame.

24 20 Chapter 1 Media Host Configuration Commissioning the System/ Configuration The Commissioning the System/Configuration section contains the following: System Software and Firmware Versions on page 20 IP Addresses and Registry Settings on page 22 Switch Settings on page 22 Intel Network Interface Card (NIC) Settings on page 22 NVIDIA Network Interface Card (NIC) Settings on page 42 Proper Flow Control in Extreme 450 Series Switches on page 46 Special Registry Settings on page 47 Startup, Test, and Fine Tune on page 50 To configure and set up the system onsite 1 Confirm System Software and Firmware Versions meet requirements. 2 Configure Physical Connections, and IP Addresses and Registry Settings as provided by Harris. 3 Configure Switch Settings, Intel Network Interface Card (NIC) Settings, and NVIDIA Network Interface Card (NIC) Settings. 4 Confirm Proper Flow Control in Extreme 450 Series Switches. 5 Confirm Special Registry Settings required on clients (I/O nodes) and servers exist and are correct as provided by Harris. 6 Startup, Test, and Fine Tune the NetworkWindowSize and NetDiskWindowSize Registry settings to minimize abnormal disconnect errors on all networks. System Software and Firmware Versions The following versions of software are the minimum version numbers needed to support the Media Host architecture. Table 1-1 System Software and Firmware Versions Application Version Applies to OS WinXP 64 All LLM All Network.dll HDX Network.dll Media Host

25 NEXIO NX1000MIOH User Guide 21 Table 1-1 System Software and Firmware Versions Application Version Applies to OS WinXP 64 All DSX.dll HDX FXP.exe HDX Intel NIC All NVIDIA NIC HDX Extreme XOS x450 series switches Physical Connections Physical Ethernet infrastructures are built using one of these three methods: 1 In the case where the infrastructure is in the form of stand alone switches, separate switches are used for each of the two networks. If more than one switch must be used for either of the networks, the switches supporting that network must be connected via backplane UniStack stacking cables. 2 In the case where the infrastructure is in the form of one enterprise class switch, use multiple blades or separate blades (or blade sets) for each of the two networks. 3 In the case where the infrastructure is in the form of two enterprise class switches with multiple blades, separate each of the two networks, one on each switch. In this case, blade usage does not matter, but try to use the same blade numbers on each switch for ease of identification. In case 3 above, an additional layer of recovery can be achieved by populating each switch with enough blades to support all the networks, as though building with a single switch (case 2). Connect the networks as described in case 3, leaving enough spare connectors on the alternate switch to allow support of all cables from its partner. If one switch fails or must be taken down for maintenance, the connections can be moved to the empty jacks on the alternate switch, restoring full redundancy in a short period of time. For details on Physical Connections, see the NEXIO NX1000MGX Hardware Guide, Part #

26 22 Chapter 1 Media Host Configuration IP Addresses and Registry Settings For system specific IP addresses and registry settings, use the System Drawings provided with your system. Switch Settings The switches must be setup with appropriate VLANs assigned to the proper ports to support the six networks involved. IP Forwarding should be enabled to allow house networks to access the server system for command, control, and diagnostics. Extreme Networks switches are required to have all ports auto-negotiate settings enabled, as this is required to activate the flow control mechanism in the switch. Customer provided switches must be examined and set as necessary to activate flow control. Intel Network Interface Card (NIC) Settings Intel Network Interface Cards (NICs) are used in the Media Host frames, NX3600 frames modified for use with the Media Host architecture, and enhanced NX3601 frames. The following screens show the Intel NICs settings.

27 NEXIO NX1000MIOH User Guide 23 To set the Intel NICs 1 In the Intel PRO/1000 GT Quad Port Server Adapter Properties dialog box, click the General tab (see Figure 1-5). Figure 1-5 General Tab 2 In the Device usage list, select Use this device (enable). 3 Click the Link Speed tab (see Figure 1-6).

28 24 Chapter 1 Media Host Configuration Figure 1-6 Link Speed Tab 4 Verify that In the Link Status area, the Speed indicator is green and shows 1.0 Gbps/Full Duplex. 5 In the Speed and Duplex list, select Auto-negotiate 1000Mbps. 6 Click the Advanced tab (see Figure 1-7).

29 NEXIO NX1000MIOH User Guide 25 Figure 1-7 Advanced Tab Jumbo Frames 7 In the Settings list, click Jumbo Frames, and then in the Value list, select Disabled.

30 26 Chapter 1 Media Host Configuration Figure 1-8 Advanced Tab Locally Administered Address 8 In the Settings list, click Locally Administered Address, and leave the Value box blank.

31 NEXIO NX1000MIOH User Guide 27 Figure 1-9 Advanced Tab Log Link State Event 9 In the Settings list, click Log Link State Event, and then in the Value list, select Enabled.

32 28 Chapter 1 Media Host Configuration Figure 1-10 Advanced Tab Performance Options 10 In the Settings list, click Performance Options, and then click Properties. The Performance Options dialog box appears (see Figure 1-11).

33 NEXIO NX1000MIOH User Guide 29 Figure 1-11 Performance Options Adaptive Inter-Frame Spacing 11 In the Settings list, click Adaptive Inter-Frame Spacing, and then in the Value list, select Enabled.

34 30 Chapter 1 Media Host Configuration Figure 1-12 Performance Options Flow Control 12 In the Settings list, click Flow Control, and then in the Value list, select Generate & Respond.

35 NEXIO NX1000MIOH User Guide 31 Figure 1-13 Performance Options Interrupt Moderation Rate 13 In the Settings list, click Interrupt Moderation Rate, and then in the Value list, select Adaptive.

36 32 Chapter 1 Media Host Configuration Figure 1-14 Performance Options Receive Descriptors 14 In the Settings list, click Receive Descriptors, and then in the Value list, select Click OK.

37 NEXIO NX1000MIOH User Guide 33 Figure 1-15 Advanced Tab QoS Packet Tagging 16 In the Settings list, click QoS Packet Tagging, and then in the Value list, select Disabled.

38 34 Chapter 1 Media Host Configuration Figure 1-16 Advanced Tab TCP/IP Offloading Options 17 In the Settings list, click TCP/IP Offloading Options, and then click Properties. The TCP/IP Offloading Options dialog box appears (see Figure 1-17).

39 NEXIO NX1000MIOH User Guide 35 Figure 1-17 TCP/IP Offloading Options 18 Select all of the check boxes (i.e., Offload Receive IP Checksum, Offload Receive TCP Checksum, Offload Transmit IP Checksum, Offload Transmit TCP Checksum). 19 Click OK.

40 36 Chapter 1 Media Host Configuration Figure 1-18 Advanced Tab Wait for Link 20 In the Settings list, click Wait for Link, and then in the Value list, select Auto Detect. 21 Click the Power Management tab (see Figure 1-19).

41 NEXIO NX1000MIOH User Guide 37 Figure 1-19 Power Management Tab 22 In the Power Saver Options area, clear the Reduce link speed during standby check box. 23 In the Wake on LAN area, clear the Wake on Directed Packet and Wake on Magic Packet check boxes, and select the Wake on Magic Packet from power off state check box. 24 Click the Teaming tab (see Figure 1-20). Teaming is not supported by the Media Host topology.

42 38 Chapter 1 Media Host Configuration Figure 1-20 Teaming Tab 25 Make sure that the Team this adapter with other adapters check box is clear. 26 Click the VLANs tab (see Figure 1-21).

43 NEXIO NX1000MIOH User Guide 39 Figure 1-21 VLANs Tab 27 Make sure that there are no VLANs listed in the VLANs associated with this adapter list. If there are VLANs listed the in the VLANs associated with this adapter list, click each one, and then click Remove. 28 Click the Boot Options tab (see Figure 1-22).

44 40 Chapter 1 Media Host Configuration Figure 1-22 Boot Options Tab 29 Make sure that the information in the Boot Agent area indicates that the Boot Agent is disabled. If the Boot Agent is not disabled, call Harris Customer Support. 30 Click the Driver tab (see Figure 1-23).

45 NEXIO NX1000MIOH User Guide 41 Figure 1-23 Driver Tab 31 Verify that the Driver Version installed is or above. If the Driver version is below , download the most recent Driver from the Intel website.

46 42 Chapter 1 Media Host Configuration NVIDIA Network Interface Card (NIC) Settings NVIDIA Network Interface Cards (NICs) are used in older NX3601 frames. The driver version installed must be NVIDIA s Web based Network Access Manager (NAM) component (67.64). To configure the Ethernet Checksum Offload Advance The NVIDIA Software Version is shown in Figure Figure 1-24 NVIDIA Software Version 1 Access the NVIDIA Ethernet Checksum Offload Advance Configuration dialog box (see Figure 1-25). Figure 1-25 NVIDIA Ethernet Checksum Offload Advance Configuration 2 Select all of the check boxes (i.e., IPv4 Transmit Checksum Offload, IPv4 Receive Checksum Offload, UDP Transmit Checksum Offload,

47 NEXIO NX1000MIOH User Guide 43 UDP Receive Checksum Offload, TCP Transmit Checksum Offload, and TCP Receive Checksum Offload. 3 Click Apply. 4 Access the NVIDIA Teaming Configuration dialog box (see Figure 1-26). Figure 1-26 NVIDIA Teaming Configuration 5 In the Enable or Disable Teaming list, select Disable. 6 Click Apply. 7 Access the NVIDIA Basic Configuration dialog box (see Figure 1-27).

48 44 Chapter 1 Media Host Configuration Figure 1-27 NVIDIA Ethernet Basic Configuration 8 In the Speed/Duplex Settings list, select Full Autonegotiation (recommended). 9 In the Performance Optimization Profile list, select CPU Utilization. 10 In the Checksum Offload list, select Enable. 11 In the TCP Large Send Offload list, select Enable. 12 In the Low Power State Link Speed list, select Enable.

49 NEXIO NX1000MIOH User Guide In the Flow Control list, select Enable. 14 In the Jumbo Frame list, select Disable (size: 1500). 15 In the Receive-side Scaling list, select Enable. 16 In the Priority list, select Disable. 17 In the Wake on Magic Packet list, select Enable. 18 In the Wake on Pattern Match list, select Enable. 19 In the Wake on Magic Packet from Power Off list, select Enable. 20 Click Apply.

50 46 Chapter 1 Media Host Configuration Proper Flow Control in Extreme 450 Series Switches Flow control on an Extreme Networks x450 series switch is automatically active if auto-negotiation is turned on. This is the default setting for the switch. The NIC cards must also be set to generate and respond to flow control commands (PAUSE frames). NEXIO uses a custom auto-negotiation advertisement that prevents the switch from auto-negotiating lower speeds with the following command: #configure ports <port_range> auto on speed 1000 To confirm speed, duplex, and flow control status for a given group of ports, use the following command: #show ports <port_range> configuration Figure 1-28 shows the expected display when flow control is successfully activated. Note that all ports are set to enable auto negotiate, and the entries for all active ports in the Flow Cntrl column show SY/ASY. Figure 1-28 Extreme Networks 450 Series Switch with Flow Control Active

51 NEXIO NX1000MIOH User Guide 47 Special Registry Settings The following tables specify the Server and Client (I/O Node) registry settings required for Media Host Failover to function properly. Table 1-2 HKCU\Software\ASC Audio Video\LLM\Control Value "IPAddress" "IPAddress1" Data- Media Host " x" (Server) " x" (Server) Data - Client (I/O Node) NOTES Server: This value must match the IP Address assigned to Motherboard port 1. This is the primary binding for the NEXIO UDP Streaming SAN Client (I/O Node): Must be empty. Server: This value must match the IP Address assigned to Motherboard port 2. This is the redundant binding for the NEXIO UDP Streaming SAN Client (I/O Node): Must be empty. "IPSubnetMask" " " Server: This value must match the subnet mask assigned to Motherboard port 1. Client (I/O Node): Must be empty. "IPSubnetMask1" " " Server: This value must match the subnet mask assigned to Motherboard port 2. Client (I/O Node): Must be empty.

52 48 Chapter 1 Media Host Configuration Table 1-2 HKCU\Software\ASC Audio Video\LLM\Control Value Data- Media Host Data - Client (I/O Node) NOTES NetworkServer From Network Mapping Table provided by Harris Server: Must be empty. Client (I/O Node): Address of primary Media Host. NetworkServer1 From Network Mapping Table provided by Harris Server: Must be empty. Client (I/O Node): Address of backup Media Host. NetworkWindowSize dword: (1024) dword: (1024) May need to be fine tuned later based on test results obtained by Harris Commissioning Team. Table 1-3 HKCU\Software\ASC Audio Video\LLM\Parameters Value Data - Media Host Data - Client (I/O node) NOTES MaxIOQuota dword: (3) dword: (3) MaxIOs dword: a (10) dword: a (10) NetDiskRecovery dword: (10000) dword: (10000) NetDiskServer From Network Mapping Table provided by Harris. Server: Must be empty. Client (I/O Node): Address of primary Media Host. NetDiskServer1 From Network Mapping Table provided by Harris. Server: Must be empty. Client (I/O Node): Address of backup Media Host. NetDiskServerAgents dword: (20) dword: (16)

53 NEXIO NX1000MIOH User Guide 49 Table 1-3 HKCU\Software\ASC Audio Video\LLM\Parameters Value Data - Media Host Data - Client (I/O node) NOTES NetDiskServerBuffer dword: 00000XXX (XXX) dword: (100) For the Data - Media Host value use one of the following for this registry setting: 192, 256, 384, 512, 768, or Use the following formula to calculate which value to use: BuffSize / Number of Data Drives (then round the nearest value above). For example: 7664 / 41 = 186 and rounds up to 192. NetDiskServerClients dword: (16) dword: (0) Server: This value is calculated and provided by Harris based on the number of client (I/O node) connections for each server. NetDiskServerIOs dword: a (10) dword: a (10) NetDiskTimeout dword: 00000bb8 (3000) dword: 00000bb8 (3000) NetDiskWindowSize dword: (64) dword: (64) May need to be fine tuned later based on test results obtained by Harris Commissioning Team.

54 50 Chapter 1 Media Host Configuration Startup, Test, and Fine Tune After all physical infrastructure is connected, and all settings are made, it is time to test the system. To test the system you must: Test Basic Connectivity Verify LLM Startup Fine Tune Performance To test basic connectivity test 1 At each client (I/O node), ping the two IP addresses that are configured in the registry for NetworkServer and NetworkServer1 at each client (I/O node). 2 Troubleshoot any connection problems found. 3 At the lowest numbered Media Host frame, ping the motherboard port addresses on all other Media Host frames. 4 Troubleshoot any connection problems found. To verify LLM Startup 1 Launch the LLM on Media Host 1, and then Initialize the logical disks (for detailing on Initializing the logical disks, see the NEXIO Low Level Module User Guide, Part # ). 2 Launch remaining Media Host LLMs. Verify that the logical drives are seen as expected and verify that the node list in the LLM top pane displays one local node and as many remote nodes as remaining Media Host frames. 3 Launch the client (I/O node) LLMs one at a time. Verify that the LLM successfully loads on the client (I/O node), and that the client (I/O node) number shows up on the expected Media Host node panes as a client (I/O node). The client (I/O node) LLM will show only one local node (see Figure 1-29). This is expected and normal.

55 NEXIO NX1000MIOH User Guide 51 Figure 1-29 Typical Client (I/O Node) LLM Window 4 At the end of the process, a typical Media Host LLM node pane should show the local and remote nodes (denoting the Media Host LLMs). The number of clients (I/O nodes) shown should equal the sum of connections on that Media Host as shown in the connections table on the design tool included with your System Drawings. See Figure 1-30, Figure 1-31, and Figure 1-32.

56 52 Chapter 1 Media Host Configuration Figure 1-30 Typical Media Host Nodes Pane showing a Local Node and Remote Nodes

57 NEXIO NX1000MIOH User Guide 53 Figure 1-31 Typical Media Host Nodes Pane showing a Remote Node and Clients (I/O Nodes)

58 54 Chapter 1 Media Host Configuration Figure 1-32 Typical Media Host Nodes Pane showing Client (I/O Nodes) To fine tune performance 1 Put all configured record channels into long duration record at the end user s target bitrate. Do not use sliding or looping IDs. 2 Play out material on all playout channels. 3 After several hours, review the errlog.txt file on all Media Host frames and look for the following types of events: ( :40:54.02) NetDiskServer: ( ,1044) abnormally disconnected 4 If more than one of these events is occurring anywhere on the system more than once/hour, then adjust the NetDiskWindowSize registry entries on all Media Host and client (I/O node) frames to ½ the current value. The default value is 128d, so change it to 64d.

59 NEXIO NX1000MIOH User Guide 55 5 Close and relaunch the LLMs systemwide and start the test again beginning at Step 1. 6 Monitor the system for drift errors: they should not occur. For information on monitoring drift errors, see the NEXIO Low Level Module User Guide, Part # ). 7 If NetDiskServer abnormal disconnect events still exceed one/hour, reduce the NetDiskWindowSize one more time to 32d, but do not go below that value. 8 Retest and check for drift. If drift occurs, then there is no choice but to return to a higher NetDiskWindowSize. The abnormal disconnects are not a problem in fully redundant mode, but will cause a brief drop to black if one of them occurs during times when only one netdiskserver connection is up, either because of an infrastructure problem or failure of an Media Host. 9 Next, do the same test but this time examine the errlog.txt file on all Media Host frames for the following types of events: ( :40:50.81) NetworkServer: node 16 abnormal disconnection 10 If more than one of these events is occurring anywhere on the system more than once/hour, then adjust the NetWorkWindowSize (default 1024) up by a factor of 2 to 2048d and retest. If unsatisfactory results are seen, review the flow control settings and the switch to verify flow control is active. To verify failover capability The following procedures should be done to verify final failover capability. These procedures assume that clients working at a high load have all drift counters on and cleared to 0 with all channels operating. First, monitor the client s outputs for on-air disruptions during failure events and for drift. Playouts should not be disrupted and drift should not increment. Buffer overruns are allowed to occur as long as the overruns are not accompanied by drift.

60 56 Chapter 1 Media Host Configuration Wait 1 minute after restoring manually failed hardware to working state before completing the following procedures. 1 Stop, then restart the LLM on one MIOH. Repeat this test for each MIOH, waiting one minute between tests. 2 Power cycle one MIOH. Repeat this test for each MIOH, waiting one minute between tests. 3 Pull one Ethernet cable on a MIOH, then restore it after 30 seconds. Repeat this test for each MIOH. 4 Pull one Ethernet cable on a client, then restore it after 30 seconds. Repeat this test for each client. 5 Power cycle one Ethernet switch. Switch may take more than a minute to restart. After switch restarts, power cycle the second switch. 6 Pull one Fibre Channel cable on a MIOH, then restore it after 30 seconds. Wait one minute, then pull and replace the other Fibre Channel cable. Repeat this test for each MIOH. 7 Pull one Fibre Channel cable on a DAE, then restore it after 30 seconds. Do this on all DAEs. 8 Power cycle a Fibre Channel switch. If the system is not intrinsically mirrored, a brief pause may occur and some drift will accumulate. Monitor the system at both the turn off point and during the 5 minute switch reboot interval.

61 57 A Real Time Analysis of Network Stability Real Time Analysis of Network Stability Optimal network conditions during operations can be observed by running Perfmon to access the Performance window (see Figure A-2). This appendix includes the following sections: Setting up Perfmon to Monitor Network Counters Monitoring Segments Retransmitted Setting up Perfmon to Monitor Network Counters To setup Perfmon to monitor network counters 1 Click the Start button, and then click Run. The Run dialog box appears (see Figure A-1). Figure A-1 Run Dialog Box 2 In the Open box, type perfmon, and then click OK.

62 58 Appendix A Real Time Analysis of Network Stability The Performance window appears displaying the System Monitor with default counters (see Figure A-2). Figure A-2 Performance Window System Monitor 3 Click the first counter, and then press the Delete key three times to clear each of the default counters. 4 Click the plus(+) icon to add new counters (see Figure A-3).

63 NEXIO NX1000MIOH User Guide 59 Figure A-3 Performance Window Add New Counter Icon The Add Counters dialog box appears (see Figure A-4).

64 60 Appendix A Real Time Analysis of Network Stability Figure A-4 Add Counters Dialog Box TCPv4 5 Click the Use local computer counters option. 6 In the Performance object list, click TCPv4 (TCP on 32 bit systems). 7 Click the All counters option. 8 Click Add.

65 NEXIO NX1000MIOH User Guide 61 Figure A-5 Add Counters Dialog Box UDPv4 9 Click the Use local computer counters option. 10 In the Performance object list, click UDPv4 (UDP on 32 bit systems). 11 Click the All counters option. 12 Click Add. 13 Click Close. The added counters appear in the Performance window (see Figure A-6).

66 62 Appendix A Real Time Analysis of Network Stability Figure A-6 Performance Window Counter Menu 14 Right-click the first counter, and then click Properties. The System Monitor Properties dialog box appears (see Figure A-7).

67 NEXIO NX1000MIOH User Guide 63 Figure A-7 System Monitor Properties Dialog Box Scale Menu 15 Click the Data tab. 16 In the Counters list, click the first counter (e.g., \TCIPv4\Connection Failures). 17 In the Scale list, select Repeat these steps until all counters have been updated. 19 Click Apply, and then click OK to close the System Monitor Properties dialog box.

68 64 Appendix A Real Time Analysis of Network Stability Monitoring Segments Retransmitted The Performance window enables you to monitor the system (see Figure A-8). TCP Segments Retransmitted/sec should average around 2. Also, note the Maximum value. The Maximum value is an indication of retransmission spikes occurring within the sample period. This number should remain around 4. If retransmissions exceed this level, investigate and confirm NIC and flow control settings in the switches. Figure A-8 Performance Window Segments Retransmitted/sec In the case of user supplied switches, the end user should be made aware of the situation so that they can obtain support from their switch vendor, and the observed values should be noted on the commissioning log (see Figure A-9).

69 NEXIO NX1000MIOH User Guide 65 Figure A-9 Performance Window Commissioning Log

70 66 Appendix A Real Time Analysis of Network Stability

71 67 Glossary Node A device that is able to store and retrieve data on the NEXIO SAN. Media Host 1 RU server providing RAIDSoft file services to a group of clients redundantly. Client A video I/O chassis or editing node that is connected via Media Host to the NEXIO streaming SAN. NEXIO Streaming SAN This network service is responsible for communicating all changes made by any Media Host or client frame (node) to all the other server frames in the domain. NetworkServer Used by the Media Host to extend the NEXIO streaming SAN communications path to the attached clients. NetdiskServer The NetDiskServer Service extends the FC SCSI block-based commands for storage and retrieval from the Media Host to the clients over the Ethernet links. A large amount of data travels over these links.

72 68 Glossary

73 69 Index C commissioning 20 configuration 20 customer support 9 D documents purchasing 7 E Ethernet Switch requirements 16 Extreme Black Diamond 16 F finding information 2 fine tune 50 firmware versions 20 flow control 46 FTP Server Service 19 I intended audience 2 IP addresses 22 M manuals purchasing 7 MIOH Failover topology 11 N NetDiskServer Service 18 network monitoring 57 network stability 57 network usage 16 NetworkServer Service 18 NEXIO Streaming SAN 16, 17 NICs Intel 22 NVIDIA 22, 42 NXES NXES P Perfmon 57 physical connections 21 physical layer interconnect requirements 15 purchasing documents 7 R registry settings 22 related documentation 3 requirements Ethernet Switch 16 ethernet switch 15 physical layer interconnect 15 S segments retransmitted 64 startup 50

74 70 Index support 9 switch settings 22 switches Extreme 450 Series 46 Extreme Black Diamond 16 NXES NXES system software versions 20 T technical support 9 test 50 U user guides purchasing 7 W writing conventions 3