03 | Cluster Networking Elden Christensen | Principal Program Manager Lead | Microsoft Symon Perriman | Vice President | 5nine Software.

Module Overview Cluster Network Infrastructure fundamentals
Cluster Network Design Planning Cluster Network Configuration Options

Cluster Network Infrastructure

Health Monitoring of Nodes in the Cluster
Failover Clustering conducts health monitoring between nodes to detect when servers are no longer available When servers are unresponsive clustering takes recovery action Unicast in nature and uses a Request-Reply type process for reliability and security Not just a basic ping You there? Yes You there? Yes

Network Health Detection
Clustering does full mesh monitoring between all network interfaces between all nodes Health monitoring: Nodes exchange heartbeats every 1 second (configurable) Nodes are considered down if they do not respond to 5 heartbeats (configurable) Nodes are removed from cluster membership if they exceed thresholds Communication over port 3343

Failover Cluster Virtual Adapter (NetFT)
TechReady13 5/13/2019 Failover Cluster Virtual Adapter (NetFT) Failover Cluster Virtual Adapter (NetFT) is a virtual network adapter that builds fault- tolerant TCP connections across all available interfaces between nodes in the cluster NetFT is the mechanism by which clusters use multiple cluster-enabled adapters to communicate Similar to an internal NIC teaming for clustering Route prioritization and routing across dissimilar subnets Provides resiliency to the loss of a network path between nodes Compatible with NIC Teaming Seamless internode communication NetFT will dynamically and seamlessly switch cluster communication to a different network (based on priority) when a network fails © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Viewing NetFT Virtual Adapter
NetFT is a virtual network adapter Visible in Device Manager and with IPConfig /all Completely self configuring Media Access Control (MAC) address is self-generated based on a hash of MAC address of the first enumerated (by NDIS) physical NIC in the cluster node NetFT self-configures an APIPA (Automatic Private Internet Protocol Addressing) address No manual user configuration required

NetFT Architecture NDIS 6.2 miniport virtual adapter
Supports Receive Side Scaling (RSS) Network fault tolerance for TCP and UDP across routed network connections Each link independently monitored Supports IPv4 and IPv6 Built in route failure detection IP over UDP/IP Tunneling Virtual adapter tunnels over physical adapters Clustering leverages port 3343 NetFT uses UDP 3343 ClusSvc uses TCP 3343 ClusSvc TCP UDP UDP IP NDIS NetFT NIC1 NIC2

Cluster Network Topology Manager
Discovers multiple communication paths between nodes Identifies available network adapters, IP addresses, subnets Determines list of same-subnet, cross-subnet, public/private Cluster Networks Enables NetFt routing of cluster networks Plumbs cluster networks on NetFt NetFt starts sending heartbeats on the enabled cluster network routes cluster network routes Maintains cluster network route health Receives notifications from NetFt about route health Determines the need of using cross-subnet routes Part of Cluster Service Loaded upon the start of Cluster Service

Cluster Network Discovery
Cluster uses exactly one IP per Subnet per NIC Cluster ignores other IPs from the same subnet configured on the NIC Cluster ignores other NICs & associated IPs from the same subnet Each NIC per Node will be part of exactly one Cluster Network Cluster will use prefix matching to determine the set of Cluster Networks Cluster has built-in resilience to use IPv4 or IPv6 per NIC (prefix must match) Cluster will use an IP from different Subnet from another NIC Cluster will ignore other IPs configured on that NIC for subnets already discovered

Cluster Network Discovery: Example
Same Subnet NIC 2 NIC 2 Ignored By Cluster 1 2 Cluster Network 1 Same Subnet NIC 1

NetFT Virtual Adapter Performance Filter
Improves cluster network performance Delivers packet directly to NetFT driver for increased performance Inspects traffic inbound on the physical NIC Reroutes traffic addressed to NetFT directly to NetFT Bypasses the physical NIC UDP / IP stack Disabled by default Enable for non-Hyper-V clusters

Cluster Communication
TechReady13 5/13/2019 Cluster Communication Clusters exchange three types of communication: Network Health Monitoring Heartbeats are sent to monitor health status of network interfaces Are sent over all cluster enabled networks Intra-cluster Communication Database updates and state synchronization that are sent between the nodes in the cluster Example: When creating a new resource the cluster database must be updated on all nodes Are over a single interface CSV I/O Redirection Metadata updates to files All I/O in failure scenarios Over same network as intra-cluster communication Over a single interface Can leverage SMB multi-channel to stream over multiple interfaces © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Manage Cluster Networking

Cluster Network Design Planning

Network Bandwidth Planning
Lightweight (only 134 bytes) Sensitive to latency If cluster heartbeats become blocked by a saturated NIC, this could cause nodes to be removed from cluster membership Bandwidth not important, but quality of service is Heartbeats Lightweight Traffic varies by workload, in general infrequent on running stable File / Hyper-V clusters. Heavier on SQL / Exchange clusters Clustering is a distributed synchronous system, latency will slow down cluster state changes (such as failover) Intra-Cluster Communication Metadata updates Lightweight and Infrequent Latency will slow down I/O performance Yes, network performance will impact storage I/O performance! Quality of service most important Failure scenarios / asymmetric storage configurations All I/O is forwarded via SMB over the network Network bandwidth is most important CSV I/O Redirection Key Take-away: Primary design consideration for cluster communication is ensuring quality of service

Traditional Network Configuration Guidance
TechReady13 5/13/2019 Traditional Network Configuration Guidance What we have recommended for the last decade… At least 2 independent networks Public / Client Network IPv4 - Static or DHCP assigned address APIPA (aka. autonet) x.x addresses not supported IPv6 Stateless address autoconfiguration (SLAAC) Note: DHCPv6 not supported for cluster IP Address resources Default gateway (routable) Intra-Node Communication IPv6 (preferred) or IPv4 IPv6 Linklocal (fe80) works great No default gateway (non-routable) Separate physical network 1 2 This still applies, but we also support converged networking © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

May I need even more than two Networks?
TechReady13 5/13/2019 May I need even more than two Networks? Guidance in the past: Yes, this gets a little unrealistic… Especially when you start adding NIC Teaming 1 Isolated network for the host partition Increased security isolation (could use VLAN’s to isolate from Client network) Host Management Public network for client access to VMs Virtual Machines Short duration heavy burst traffic Live Migration Intra-cluster communication is lightweight, but sensitive to latency Metadata updates are infrequent and light, but failure conditions could be heavy Intra-cluster communication / CSV Dedicated storage network Disable for cluster use iSCSI 2 3 4 Cluster Traffic and CSV traffic are inseparable Live Migration will default to the second lowest metric if you have 3 or more networks Live Migration network looks like it is a resource property in the UI – it isn’t, it is a cluster wide setting iSCSI networks should be disabled, you don’t want cluster traffic creating storage latency Host VMs – they can share the public network, or you can give them their own separate network. 5 Key Takeaway: It is really about providing quality of service guarantees!! © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Are Separate Networks Really Needed?
Required? No – It is not required to have 2 separate networks Clustering does support a converged networking model Validate will generate a Warning to alert you of a potential single point of failure Validate is not NIC Teaming aware Recommended? Yes – It is recommended to have redundant network communication between nodes Sort of… let’s talk about what really matters and converged networking (next slide)

Converged Network Considerations
Resiliency Quality of Service In a highly available system you want to avoid any single points of failure Many ways to accomplish network redundancy Multiple independent networks NIC Teaming Cluster heartbeats are lightweight, but sensitive to latency If cluster heartbeats can’t get through… this can be falsely interpreted that nodes are down Many ways to accomplish network quality of service Multiple network cards QoS Create VLANs

CSV Networking Planning
I/O Redirected via SMB Cluster Shared Volumes routes I/O over the network between nodes over SMB Planning a CSV deployment involves network considerations in addition to storage Network path leveraged when… Metadata updates to files Very infrequent for VM workload (such as starting a VM or live migration) No storage connectivity Failure recovery Asymmetric storage configurations where nodes run over SMB If an asymmetric configuration or Mirrored Space, you will need more bandwidth VM running on Node 2 is unaffected SAN SAN Connectivity Failure

CSV Networking Considerations
TechReady13 5/13/2019 CSV Networking Considerations CSV Requirements: SMB Server and Workstation Services NTLM Tuning CSV performance: CSV traffic will take advantage of SMB multi-channel and RDMA Disabling NetBIOS has shown increased performance CSV testing has seen little advantage with Jumbo Frames However, not discouraged © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Reducing Single Points of Failure
Use multiple physical NIC’s Single multi-port NIC introduces it as a single point of failure Connect NIC’s to different switches Carving up VLAN’s all to the same switch is a single point of failure Use NIC Teaming for network resiliency Most important for non-redundant networks, such as for client connectivity Intra-cluster communication, CSV, and Live Migration will already failover to another network Using different types of NIC’s removes common drivers Eliminate a driver bug from affecting connectivity across all NIC’s Ensure upstream network resiliency Eliminate a single point of failure between multiple networks

Cluster Network Configuration Options

Firewall Exceptions Inbound Rules
TechReady13 5/13/2019 Firewall Exceptions Inbound Rules Failover Clustering requires that exceptions be defined to allow clusters to communicate Failover Clustering primarily uses port 3343 When you install the Failover Clustering feature it will automatically enable all the necessary Windows Firewall exceptions Security Configuration Wizard is cluster aware and will detect and enable appropriate exceptions Consideration: Need to manually enable if using a 3rd party firewall solution Common support call generator Symantec Endpoint Protection Blades & Clustering: The point of clusters is to have redundant systems, but Blades introduce shared hardware. Especially problematic with shared network hardware. CSV: Make sure to check what your networks were doing when you have a CSV problem, if no failures were logged was there perhaps a very high amount of CSV traffic right then. Or are you using the same network for LM and CSV and a LM was in progress? Clustering has a group of firewall rules, but if they get disabled by accident there can be problems. “Yanking cables testing” often hits the restart limit. Outbound Rules © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Tuning Network Thresholds
TechReady 16 5/13/2019 Tuning Network Thresholds Failover clustering by default is configured to deliver the highest levels of availability Which means quickly detecting and reacting to failures This can sometimes result in premature failovers Some customers may wish to have reduced sensitivity Enables greater tolerance for unreliable networks Results in greater downtime when things do go wrong Highest Availability Tolerance of Transient Failures See this blog for more: Clustering is fully configurable to achieve either © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Configuring Cluster Heartbeating
Cluster intra-node heartbeating is fully configurable Configurable via a cluster common property Thresholds for heartbeats across subnets independently configurable PowerShell: (Get-Cluster). SameSubnetThreshold = 10 Property Default Maximum Description SameSubnetDelay 1 second 2 seconds Frequency heartbeats are sent SameSubnetThreshold 5 heartbeats 120 heartbeats Missed heartbeats before an interface is considered down CrossSubnetDelay 4 seconds Frequency heartbeats are sent to nodes on dissimilar subnets CrossSubnetThreshold Missed heartbeats before an interface is considered down to nodes on dissimilar subnets Increasing heartbeat thresholds does not fix network problems, it only masks them!

Win2012 R2 Heartbeat Changes
For a Hyper-V deployment slightly more relaxed settings may make sense Traditionally the definition of down, is when clients cannot connect to an app in the VM In general, TCP defines recoverable network errors for applications Recommended for cluster heartbeats not to exceed 20 seconds Greater resiliency to transient network failures with Windows Server 2012 R2 Heartbeat thresholds increased by default for Hyper-V Clusters Defaults changed when the first VM is clustered Cluster heartbeating improved for increased resiliency to packet loss Cluster Property Default Hyper-V Default SameSubnetThreshold 5 10 CrossSubnetThreshold 20

Achieving Network Redundancy
Clustering only recognizes 1 network interface per logical subnet Do not assign more than 1 NIC per subnet This includes IPv6 linklocal Achieving Network Redundancy on Clusters: Use NIC Teaming to aggregate multiple NIC’s into a single logical Recommended configuration to achieve network resiliency on client network Clustering fully supports in-box NIC Teaming as well as 3rd party solutions Multiple NIC’s on different subnets: SMB multi-channel on clusters requires NIC’s on different networks NetFT will build fault-tolerant routes and cluster networking will failover across multiple networks Live migration will use cluster networking to determine network routes and switch if networks go down

Network Binding Order Cluster nodes are multi-homed systems
TechReady13 5/13/2019 Network Binding Order Cluster nodes are multi-homed systems Network priority affects DNS client for outbound network connectivity Client connecting adapter should be first bound Non-routed networks lower priority Configuring Binding Order GUI: Control Panel -> Network Connections Press “Alt” to get the menu bar Advanced->Advanced Settings Command Line: nvspbind.exe (web download) NetFT automatically placed at bottom of binding order during install © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

TechReady13 5/13/2019 Cluster Network Roles Cluster networks are created for all logical subnets connected to all nodes in the cluster Each NIC connected to that common subnet will be listed Cluster networks can be configured for different cluster use: Name Value Description Disabled for Cluster Communication No cluster communication of any kind sent over this network Enabled for Cluster Communication only 1 Internal cluster communication and CSV traffic can be sent over this network Enabled for client and cluster communication 3 Cluster IP Address resources can be created on this network for clients to connect to. Internal and CSV traffic can be sent over this network Role value of 2 was deprecated in Windows Server 2008 © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Configuring Cluster Network Roles
TechReady13 5/13/2019 Configuring Cluster Network Roles Automatic Configuration Manual Configuration Network role is automatically configured during cluster creation Logic for role assignment: Failover Cluster Manager PowerShell (Get-ClusterNetwork “Cluster Network 1").Role=3 If enabled for iSCSI Software Initiator New Windows Server 2012 logic Disabled for Cluster Communication If no default gateway is present Enabled for Cluster Communication only If a default gateway is present Enabled for client and cluster communication © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Cluster Network Prioritization Assignment
Determines priority for NetFT traffic (effects both CSV & intra-cluster traffic) Networks are given a “cost” (Metric) to define priority Lower metric value = higher priority (private) Higher metric value = lower priority (public) Automatically configured based on cluster network role setting Cluster Network Role of 1 = 40,000 starting value Cluster Network Role of 3 = 80,000 starting value Link speed, RDMA, and RSS capabilities will reduce metric value NetFT will load balance across networks that are <16 metric values apart Load balancing is cluster wide All communication between a pair of nodes will be on the same interface A node may communicate with different nodes on different networks if they are of similar metric weight Metric Algorithm: (40000 if Role 1 or if Role 3) – (19200 if RDMA capable) – (9600 if RSS capable [does not stack with RDMA bonus]) – ((16 for NetFT’s load balancing logic group size) * (link speed [NIC’s slower than 1 GB will be 0])) = Metric Value

Configuring Cluster Network Prioritization
Clustering has intelligence to automatically detect and set preference on which network to use Metric’s can be manually configured as well Cluster automatically assigned mode (default) (Get-ClusterNetwork “Cluster Network 1").AutoMetric = $true Manually set (Get-ClusterNetwork “Cluster Network 2").Metric = 40000 Consideration: NetFT load balancing and SMB multi-channel will send cluster communication over multiple paths Recommended to leave as default cluster controlled Restricting traffic different in Win2012

Configuring Live Migration Network Priority
Intra-cluster communication / CSV traffic will prefer the highest priority network Live migration will prefer the 2nd highest network Live migration uses cluster network topology to discover available networks and establish priority Priority will automatically be configured Cluster priority can be manually configured (see previous slide) Live migration preference can also be manually configured in Failover Cluster Manager Will take preference over cluster settings Also configurable via PowerShell in-a-hyper-v-cluster.aspx

CSV with SMB Multi-channel
TechReady13 5/13/2019 CSV with SMB Multi-channel CSV is integrated with SMB multi-channel Allows streaming CSV traffic across multiple networks Delivers improved I/O performance for I/O redirection CSV traffic will default to SMB multi-channel CSV traffic will failover to NetFT if SMB multi-channel is not available Configuring Cluster Network Prioritization affects only NetFT Disabling SMB multi-channel: Set-SmbServerConfiguration -EnableMultiChannel $false X X CSV Streaming I/O Across Multiple Networks © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

SMB Multi-Channel Selection on a Cluster
Understanding which network CSV will use: SMB Multi-Channel: Only select networks which are: Enabled for cluster use Set to a cluster role of 1 (internal cluster communication) Logic can be overridden with UseClientAccessNetworksForSharedVolumes cluster property Select the NIC’s with the best features Select RDMA-capable NICs If none select RSS-capable and/or teamed NIC If none select all others If multiple NIC’s are selected, pick NIC with highest speed If multiple NIC’s are equal on above criteria, then stream over multiple NIC’s NetFT If no SMB multi-channel enabled network found, CSV uses NetFT logic for network selection

Configuring Quality of Service Policies
QoS policy features Prioritization Recommendation: Configure on all cluster deployments Heartbeats and Intra-cluster communication are sensitive to latency and configuring a QoS Priority Flow Control policy will ensure they are sent first Bandwidth Allocation Recommendation: Configure on CSV deployments CSV may send large amounts of data, need to ensure it has sufficient bandwidth Relative Minimum Bandwidth SMB policy recommended

iSCSI Cluster Planning
Recommended that iSCSI Storage fabric have a dedicated and isolated network Disable iSCSI networks for cluster use Prevents intra-cluster communication as well as CSV traffic from flowing over same network Cluster will automatically disable iSCSI interfaces for cluster use in Win2012 Set to be lowest in binding order Configure iSCSI network redundancy with MPIO NIC Teaming is now supported in Win2012 with iSCSI

Multi-Subnet Clusters
Failover Clustering supports having nodes reside in different IP subnets Most commonly used for multi-site clusters that are stretched across datacenters Longer distance traditionally means greater network latency CSV now supports nodes in different IP subnets in Windows Server 2012 SQL Server 2012 now supports multi-subnet clusters More on this in the Multi-Site Clustering module Site A Site B

In Review: Session Objectives and Takeaways
TechReady13 5/13/2019 In Review: Session Objectives and Takeaways Design your network on clusters to provide: Resiliency With multiple networks or through NIC Teaming Quality of service Dedicated cluster networks is old-school… use QoS policies in Win2012 CSV brings bandwidth considerations In general clustering will ‘just work’ out of the box IT Generalists: No need to worry IT Specialists: Highly flexible and configurable © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

03 | Cluster Networking Elden Christensen | Principal Program Manager Lead | Microsoft Symon Perriman | Vice President | 5nine Software.

Similar presentations

Presentation on theme: "03 | Cluster Networking Elden Christensen | Principal Program Manager Lead | Microsoft Symon Perriman | Vice President | 5nine Software."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

03 | Cluster Networking Elden Christensen | Principal Program Manager Lead | Microsoft Symon Perriman | Vice President | 5nine Software.

Similar presentations

Presentation on theme: "03 | Cluster Networking Elden Christensen | Principal Program Manager Lead | Microsoft Symon Perriman | Vice President | 5nine Software."— Presentation transcript:

Similar presentations

About project

Feedback