HP StorageWorks Enterprise File Services WAN Accelerator 3.0.
Legal and notice information © Copyright 2007 Hewlett-Packard Development Company, L.P. © Copyright 2003–2007 Riverbed Technology, Inc. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Introduction CONTENTS Contents ........................................................................................................... 7 About This Guide.................................................................................. Types of Users ................................................................................ Organization of This Guide ............................................................ Document Conventions ................................................................
Chapter 2 In-Path Deployments ................................................................ 23 Introduction to Physical In-Path Deployments ................................... 24 In-Path, Failover Support Deployment ............................................... 24 Basic Steps (Client-Side).............................................................. 25 Basic Steps (Server-Side) ............................................................. 26 In-Path, Two Routing Points Deployment ..................
Chapter 6 Policy-Based Routing Deployments ........................................ 51 Introduction to PBR ............................................................................ 52 Overview of CDP................................................................................ 52 How PBR works on a Cisco 6500 Platform, Version 12.2(17d) SXB1 53 Asymmetric HP EFS WAN Accelerator Deployments with PBR ...... 55 Configuring PBR Using the CLI ..................................................
Troubleshooting .................................................................................. 88 Chapter 8 Serial Cluster and Cascade Deployments ............................... 89 Serial Cluster Deployment.................................................................. 89 A Basic Serial Cluster Deployment.............................................. 90 Cascade Deployment .......................................................................... 93 Peering Rules...................................
Configuring TACACS+ Authentication in the HP EFS WAN Accelerator....................................................................................... 117 Basic Steps.................................................................................. 118 Chapter 13 Troubleshooting Deployment Problems ................................ 119 Problem: Inability to Access Files During WAN Disruption............ 121 Solution: Use Proxy File Service ...............................................
6 CONTENTS
INTRODUCTION Introduction In This Introduction Welcome to the HP StorageWorks Enterprise File Services WAN Accelerator Deployment Guide. Read this introduction for an overview of the information provided in this guide and for an understanding of the documentation conventions used throughout.
Chapter 2, “In-Path Deployments,” describes physical in-path deployments. Chapter 3, “Virtual In-Path Network Deployments,” describes virtual in-path deployments. Chapter 4, “Out-of-Path Network Deployments,” describes out-of-path deployments. Chapter 5, “Connection Forwarding,” describes how to configure the HP EFS WAN Accelerator to forward connections in asymmetric networks.
Document Conventions This manual uses the following standard set of typographical conventions to introduce new terms, illustrate screen displays, describe command syntax, and so forth. Meaning italics Within text, new terms and emphasized words appear in italic typeface.
Hardware and Software Dependencies The following table summarizes the hardware and software requirements for the HP EFS WAN Accelerator. HP Component Hardware and Software Requirements HP EFS WAN Accelerator • 19 inch (483 mm) two or four-post rack. HP EFS WAN Accelerator Management Console, HP StorageWorks Enterprise File Services WAN Accelerator Manager • Any computer that supports a Web browser with a color image display. • The Management Console has been tested with Mozilla Firefox, version 1.0.
Network Associates (McAfee) VirusScan 7.0.0 Enterprise on the server Network Associates (McAfee) VirusScan 7.1.0 Enterprise on the server Network Associates (McAfee) VirusScan 7.1.0 Enterprise on the client Symantec (Norton) AntiVirus Corporate Edition 8.1 on the server F-Secure Anti-Virus 5.43 on the client F-Secure Anti-Virus 5.5 on the server Network Associates (McAfee) NetShield 4.5 on the server Network Associates VirusScan 4.
HP StorageWorks Enterprise File Services WAN Accelerator Bypass NIC Installation Guide describes how to install the bypass cards in the HP EFS WAN Accelerator. Online Documentation The HP EFS WAN Accelerator documentation set is periodically updated with new information. To access the most current version of the HP EFS WAN Accelerator documentation and other technical information, consult the HP Technical Support site located at http://www.hp.com/support.
HP Storage Web Site HP STORAGEWORKS ENTERPRISE FILE SERVICES WAN ACCELERATOR DEPLOYMENT GUIDE 13 INTRODUCTION The HP web site has the latest information on this product, as well as the latest drivers. Access the storage site at: http://www.hp.com/country/us/eng/prodserv/storage.html. From this web site, select the appropriate product or solution.
14 INTRODUCTION
In This Chapter Designing an HP EFS WAN Accelerator Deployment This chapter describes how the HP EFS WAN Accelerator works and how to design an HP EFS WAN Accelerator deployment.
Transaction Acceleration Transaction Acceleration (TA) is composed of the following optimization mechanisms: A connection bandwidth-reducing mechanism called Scalable Data Referencing (SDR). A Virtual TCP Window Expansion (VWE) mechanism that repacks TCP payloads with references that represent arbitrary amounts of data. A latency reduction and avoidance mechanism called Transaction Prediction (TP).
Transaction Prediction Latency optimization is delivered through Transaction Prediction (TP). TP involves an intimate understanding of protocol semantics to reduce the chattiness that would normally occur over the WAN. By acting on foreknowledge of specific protocol request-response mechanisms, HP EFS WAN Accelerators streamline the delivery of data that would normally be delivered in small increments through large numbers of handshakes and interactions between the client and server over the WAN.
Users and Servers. A site that has users and servers that are accessed remotely. Typically, users and servers are in a regional office with branch offices at remote sites that accesses data from remote sites and a data center. 2. Determine what kind of WAN routing infrastructure you have. For example, do you have one or two WAN routers? 3.
Definition of Terms Optimization. The process of increasing data throughput and network performance over the WAN using the HP EFS WAN Accelerator. An optimized connection exhibits bandwidth reduction as it traverses the WAN. Scalable Data Referencing (SDR). The proprietary algorithms that allow an arbitrarily large amount of data to be represented by a small number of references to the HP EFS WAN Accelerator data store.
For detailed information about bypass card status lights, see the HP StorageWorks Enterprise File Services WAN Accelerator Bypass NIC Installation Guide. If there is a serious problem with the HP EFS WAN Accelerator or it is not powered on, it goes into bypass mode to prevent a single point of failure. If the HP EFS WAN Accelerator is in bypass mode, you are notified in the following ways: The Intercept/Bypass status light is active.
optimization is lost on the current connections on the master HP EFS WAN Accelerator. the backup HP EFS WAN Accelerator takes over and all new connections are optimized. when the master HP EFS WAN Accelerator comes back up, the backup HP EFS WAN Accelerator stops optimizing connections.
22 1 - DESIGNING AN HP EFS WAN ACCELERATOR DEPLOYMENT
In This Chapter 2 - IN-PATH DEPLOYMENTS CHAPTER 2 In-Path Deployments This chapter describes physical in-path network deployments and summarizes the basic steps for configuring them.
Introduction to Physical In-Path Deployments The following section describes physical in-path network configurations where the HP EFS WAN Accelerator is physically in the direct path between clients and servers. The clients and servers continue to see client and server Internet Protocol (IP) addresses. Physical in-path configurations are suitable for locations where the total bandwidth is within the limits of the installed HP EFS WAN Accelerator. Figure 2-1.
Basic Steps (Client-Side) Perform the following steps for each client-side HP EFS WAN Accelerator. 2. Connect to the Management Console. For detailed information, see the HP Enterprise File Services WAN Accelerator Management Console User Guide. 3. Navigate to the Setup: Advanced Networking - Failover Settings page in the Management Console. 4. Enable failover support.
Type the number of seconds in the Reconnection interval text box. The default value is 30. 6. Type the backup HP EFS WAN Accelerator’s IP address in the Other Appliance’s IP Address text box. 7. Apply and save the new configuration in the Management Console. 8. Begin optimization. 9. View performance reports and system logs in the Management Console. Basic Steps (Server-Side) The server-side HP EFS WAN Accelerator is configured as an in-path device.
Figure 2-4. In-Path, Two Routing Points Deployment 2 - IN-PATH DEPLOYMENTS Basic Steps (Client-Side) Perform the following steps on each client-side HP EFS WAN Accelerator. 1. Configure the HP EFS WAN Accelerator as an in-path device. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide. 2. Connect to the Management Console to verify your configuration.
This deployment is useful in environments where most of the server-side traffic is outof-path but there are applications that originate on the server-side that require optimization (for example, backup software, software distribution suites, or other similar applications). The following figure illustrates a server-side subnet where the HP EFS WAN Accelerator is deployed to provide data center clients with optimized data. Figure 2-5.
The following figure illustrates the server-side of the network. Figure 2-6. In-Path, Server-Side, One-to-One Deployment 2 - IN-PATH DEPLOYMENTS Basic Steps (Client-Side) The client-side HP EFS WAN Accelerator is configured as an in-path device. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide. Basic Steps (Server-Side) Perform the following steps for each of the server-side HP EFS WAN Accelerators. 1.
On HP EFS WAN Accelerator B, specify HP EFS WAN Accelerator B as the backup (other) and specify the in-path IP address of HP EFS WAN Accelerator A as the master IP address. Figure 2-7. Setup: Advanced Networking - Failover Settings Page 5. Under Automated Online Datastore Settings, click Enable Automated Online Datastore Synchronization. Select Master or Backup from the Current Appliance is the drop-down list. Type a port number in the Synchronization Port text box. The default value is 7744.
In This Chapter 3 - VIRTUAL IN-PATH NETWORK DEPLOYMENTS CHAPTER 3 Virtual In-Path Network Deployments This chapter describes virtual in-path deployments and summarizes the basic steps for configuring them. This chapter includes the following sections: “Introduction to Virtual In-Path Deployments,” next “In-Path, Load Balanced, Layer-4 Switch” on page 32 This chapter assumes you are familiar with the HP EFS WAN Accelerator Management Console (Management Console).
Layer-4 Switch. You enable Layer-4 switch (or server load-balancers) support when you have multiple HP EFS WAN Accelerators in your network to manage large bandwidth requirements. Hybrid. A hybrid deployment is a deployment in which the HP EFS WAN Accelerator is both in-path and out-of-path.
The following figure illustrates the server-side of the network where load balancing is required. Figure 3-1. In-Path, Load-Balanced, Layer-4 Switch Deployment 3 - VIRTUAL IN-PATH NETWORK DEPLOYMENTS Basic Steps (Client-Side) The client-side HP EFS WAN Accelerator is configured as an in-path device. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide.
On HP EFS WAN Accelerator B, plug the straight-through cable into the WAN port of the HP EFS WAN Accelerator and the Layer-4 switch. 5. Connect to the Management Console. For details see the HP Enterprise File Services WAN Accelerator Management Console User Guide. 6. Navigate to the Setup: Optimization Service - General Settings page in the Management Console. 7. Enable Layer-4 switch support. For example: Click Enable In-Path Support and Enable L4/PBR/WCCP Support on Interface wan0_0. Figure 3-2.
In This Chapter 4 - OUT-OF-PATH NETWORK DEPLOYMENTS CHAPTER 4 Out-of-Path Network Deployments This chapter describes out-of-path deployments and summarizes the basic steps for configuring them.
Typically, in an out-of-path deployment, the client-side HP EFS WAN Accelerator is configured as an in-path device, and the server-side HP EFS WAN Accelerator is configured as an out-of-path device. Figure 4-1. Physical Out-of-Path Deployment Out-of-Path, Failover Deployment An out-of-path, failover deployment serves networks where an in-path deployment is not an option. This deployment is cost effective, simple to manage, and provides redundancy.
The following figure illustrates the server-side of the network where two HP EFS WAN Accelerators are deployed in an out-of-path configuration to ensure that data continues to be optimized if there is an error in the system. Basic Steps (Client-Side) 4 - OUT-OF-PATH NETWORK DEPLOYMENTS Figure 4-2.
3. Navigate to the Setup: Optimization Service - In-Path Rules page in the Management Console. Figure 4-3. Setup: Optimization Service - In-Path Rules Page 4. To enable failover support for the out-of-path HP EFS WAN Accelerators, define a fixed-target rule that points to the main and backup targets. For example: Type the out-of-path, server-side HP EFS WAN Accelerator IP address and port in the Target Appliance IP and Port text boxes.
Out-of-Path, Static Cluster Deployment The following figure illustrates a deployment where two HP EFS WAN Accelerators are configured as out-of-path devices on the server-side of the network and there are static clusters with in-path HP EFS WAN Accelerators on the client-side of the network. Figure 4-4. Static Cluster Deployment Basic Steps (Client-Side) Perform the following steps for each HP EFS WAN Accelerator on the client-side of the network. 1.
In the Southern region, for all HP EFS WAN Accelerators in the set, define HP EFS WAN Accelerator 2 as the fixed target for servers in Subnet S. Figure 4-5. Setup: Optimization Service - In-Path Rules, Fixed Target Page 5. Apply and save the new configuration in the Management Console. 6. Begin optimization. 7. View performance reports and system logs in the Management Console.
The following figure illustrates the client-side of the network where the HP EFS WAN Accelerator is configured as both an in-path and out-of-path device. Figure 4-6. Hybrid: In-Path and Out-of-Path Deployment 4 - OUT-OF-PATH NETWORK DEPLOYMENTS Basic Steps (Client-Side) Perform the following steps for the HP EFS WAN Accelerator. 1. Configure the HP EFS WAN Accelerator as an in-path and out-of-path device.
Figure 4-7. Setup: Optimization Service - In-Path Rules Page 4. Define in-path, fixed-target rules for traffic you want to optimize. For example: 42 Select start, end, or a rule number from the Insert Rule At drop-down list to insert a rule in the Rules list. When you specify a particular rule number, the rule is placed after the rule number you specified and before the default autodiscover rule. Type the IP address for the source subnet in the Source Subnet text box. Use the following format: 0.
Type the IP address and port for the destination subnet, in the Destination Subnet and Port text boxes. To specify all ports, type all in the Port text box. Under Targets, type the IP address and port number for the HP EFS WAN Accelerator that is the peer in the Target Appliance IP and Port text boxes. The IP address must be the Primary Port IP address on the target HP EFS WAN Accelerator. The default port is 7810.
44 4 - OUT-OF-PATH NETWORK DEPLOYMENTS
In This Chapter 5 - CONNECTION FORWARDING CHAPTER 5 Connection Forwarding This chapter describes the HP EFS WAN Accelerator connection forwarding feature and how to deploy the HP EFS WAN Accelerator in asymmetric networks using connection forwarding. You can configure HP EFS WAN Accelerator connection forwarding on the client-side or server-side of a network. The examples in this chapter describe configuring server-side connection forwarding.
If you have one path (through HP EFS WAN Accelerator-2) from the client to the server and a different path (through HP EFS WAN Accelerator-3) from the server to the client, you need to enable in-path connection forwarding and configure the HP EFS WAN Accelerators to communicate with each other. These HP EFS WAN Accelerators are called neighbors and exchange connection information to redirect packets to each other. Figure 5-1.
If one of the neighbor HP EFS WAN Accelerators reaches its optimization capacity limit, that HP EFS WAN Accelerator will not accept new connections, but it redirects packets to other neighbors for optimization. To ensure optimization in the event of a failure, a backup HP EFS WAN Accelerator can be added to each neighbor HP EFS WAN Accelerator in a one-to-one failover configuration.
Connection forwarding can be configured for client-side and server-side asymmetric networks. The following sections describe configuring server-side connection forwarding for the network shown in Figure 5-3 on page 48. Configuring Connection Forwarding Using the Management Console You can configure connection forwarding on the client-side and server-side of the network. This section describes the basic steps for enabling and configuring serverside connection forwarding using the Management Console.
Basic Steps (Server-Side) Perform the following steps on each of the server-side HP EFS WAN Accelerators. 2. Connect to the Management Console. For detailed information, see the HP Enterprise File Services WAN Accelerator Management Console User Guide. 3. Navigate to the Setup: Advanced Networking - Connection Forwarding page in the Management Console. 4. Configure each of the neighbors by specifying the in-path IP address for the neighbor HP EFS WAN Accelerator. Figure 5-4.
Optionally, you can configure global keep-alive intervals and count for the neighbor HP EFS WAN Accelerators. Click Apply. 5. Save the new configuration in the Setup: Configuration Manager page. 6. Restart the HP EFS WAN Accelerator service in the Setup: Start/Stop Services page. 7. Begin optimization. 8. View performance reports and system logs in the Management Console.
In This Chapter 6 - POLICY-BASED ROUTING DEPLOYMENTS CHAPTER 6 Policy-Based Routing Deployments This chapter describes how to configure Policy-Based Routing (PBR) to redirect traffic to an HP EFS WAN Accelerator or group of HP EFS WAN Accelerators. It includes the following sections: “Introduction to PBR,” next “Overview of CDP” on page 52 “How PBR works on a Cisco 6500 Platform, Version 12.
For detailed information about the factors you must consider before you design and deploy the HP EFS WAN Accelerator in a network environment, see “Design and Deployment Overview” on page 17. Introduction to PBR PBR is a router configuration that allows you to define policies to route packets instead of relying on routing protocols. It is enabled on an interface basis and packets coming into a PBR-enabled interface are checked to see if they match the defined policies.
IMPORTANT: HP recommends that you DO NOT use hybrid mode with WCCP in production environments. WCCP is designed to redirect traffic to a group of HP EFS WAN Accelerators so it is often better in clustering solutions. With PBR, any clustering must be done manually by configuring a set of redirect rules. The following table summarizes the advantages and disadvantages of PBR and WCCP.
PBR checks availability in the following manner: 1. When PBR first attempts to send to a PBR next hop, it checks the CDP neighbor table to see if the IP address of the next hop appears to be available. If so, it sends an Address Resolution Protocol (ARP) request for the address, resolves it, and begins redirecting traffic to the next hop (that is, the HP EFS WAN Accelerator). 2.
Asymmetric HP EFS WAN Accelerator Deployments with PBR If the client-side HP EFS WAN Accelerator is on a different Layer-2 interface than the clients on the router where PBR is configured, PBR can be enabled on a Layer-2 interface basis and redirect TCP traffic going to the server. IMPORTANT: HP recommends you define a policy based on the source or destination IP and not on the TCP source or destination ports because certain protocols use dynamic ports instead of fixed ones.
In this example, the HP EFS WAN Accelerator is configured as a client-side HP EFS WAN Accelerator in an in-path configuration with PBR support. It must reach the remote network through the router from the in-path interface and a fixed-target in-path rule is defined for the remote out-of-path HP EFS WAN Accelerator. Basic Steps (Client-Side) To configure the client-side HP EFS WAN Accelerator Perform the following basic steps for the client-side HP EFS WAN Accelerator. 1. Connect to the client-side CLI.
TIP: Enter configuration commands, one per line. End with CRTL-Z. For detailed information about configuring Cisco routers for PBR, see http:// www.cisco.com/en/US/products/sw/iosswrel/ps1831/ products_configuration_guide_chapter09186a00800c60d2.html#23550. Basic Steps (Server-Side) In this example, the server-side HP EFS WAN Accelerator is configured as an out-of-path device. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide.
1. Configure the HP EFS WAN Accelerator as an in-path device. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide. 2. Connect to the Management Console. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide. 3. Navigate to the Setup: Optimization Service - General Settings page in the Management Console. 4.
5. Navigate to the Setup: Optimization Service - In-Path Rules page. 6. Define fixed-target, in-path rules to reach the remote network through the remote out-of-path HP EFS WAN Accelerator. 6 - POLICY-BASED ROUTING DEPLOYMENTS Figure 6-3. Setup: Optimization Service - In-Path Rules Page 7. Apply and save the new configuration in the Setup: Configuration Manager page. 8. Restart the HP EFS WAN Accelerator service in the Setup: Start/Stop Services page. 9. Begin optimization. 10.
Client-Side HP EFS WAN Accelerator Attached to a Router through a Switch In this deployment, PBR is enabled on the interface of the client-side router connected to the Layer-2 switch that redirects traffic to the HP EFS WAN Accelerator. Communication between the client-side HP EFS WAN Accelerator and the clients must be through the client-side router. Figure 6-4.
Client-Side HP EFS WAN Accelerator Attached to an Inside Router Figure 6-5. Client-Side HP EFS WAN Accelerator Attached to an Inside Router Basic Steps (Client-Side) Perform the steps for “Basic Steps (Client-Side)” on page 56. Make sure that you configure different PBR rules for the second router. Basic Steps (Server-Side) Perform the steps for “Basic Steps (Server-Side)” on page 57.
In this configuration, the HP EFS WAN Accelerator is attached to any Layer-2 switch that the router can reach (even the same switch as the clients). VLAN trunking is enabled between the Layer-2 switch and the PBR router (not on the link between the HP EFS WAN Accelerator and the switch). In this configuration you use the IP addresses in a single subnet and the router has 2 VLAN interfaces on fastEthernet0/0.
Symmetric HP EFS WAN Accelerator Deployments with PBR and Auto-Discovery Figure 6-7. Symmetric HP EFS WAN Accelerator Deployments with PBR For this example, assume that clients, servers, and HP EFS WAN Accelerators are all on a separate VLANs and the Layer-2 switch is attached to the router fastEthernet0/ 0 interface. This example uses the following IP addresses: Left-side. Clients=10.0.1.0/24, Servers=10.0.2.0/24, HP EFS WAN Accelerator=10.0.3.0/24 Right-side. Clients=10.1.1.0/24, Servers=10.1.2.
Right-SH Right-SH Right-SH Right-SH Right-SH Right-SH Right-SH Right-SH > enable # configure terminal (config) # in-path enable (config) # in-path oop enable (config) # interface in-path ip address 10.1.3.2 /24 (config) # ip in-path-gateway inpath0_0 10.1.3.1 (config) # write memory (config) # restart IMPORTANT: You must save your changes to memory and restart the HP EFS WAN Accelerator service for your changes to take effect. To configure the Cisco router 1.
2. On the right router, at the system prompt, enter the following set of commands: HP STORAGEWORKS ENTERPRISE FILE SERVICES WAN ACCELERATOR DEPLOYMENT GUIDE 65 6 - POLICY-BASED ROUTING DEPLOYMENTS Router#configure terminal Router(config)#interface fastEthernet 0/0.1 Router(config-subif)#encapsulation dot1Q 1 Router(config-subif)#ip address 10.1.1.1 255.255.0.0 Router(config-subif)#ip policy route-map TrafficToLeftS Router(config-subif)#exit Router(config)#interface fastEthernet 0/0.
Symmetric Deployments with PBR, Auto-Discovery, and CDP In the case where clients and servers are on both sides of the WAN, PBR can be configured on both sides of the network where each router has the reversed rules of the other router. Figure 6-8. Symmetric HP EFS WAN Accelerator Deployments with PBR For this example, assume that clients, servers, and HP EFS WAN Accelerators are all on a separate VLANs and the Layer-2 switch is attached to the router fastEthernet0/ 0 interface.
2. On the right HP EFS WAN Accelerator, at the system prompt, enter the following set of commands: > enable # configure terminal (config) # in-path enable (config) # in-path oop enable (config) # in-path cdp enable (config) # interface in-path ip address 10.1.3.2 /24 (config) # ip in-path-gateway inpath0_0 10.1.3.1 (config) # write memory (config) # restart IMPORTANT: You must save your changes to memory and restart the HP EFS WAN Accelerator service for your changes to take effect.
2. On the right router, at the system prompt, enter the following set of commands: Router#configure terminal Router(config)#interface fastEthernet 0/0.1 Router(config-subif)#encapsulation dot1Q 1 Router(config-subif)#ip address 10.1.1.1 255.255.0.0 Router(config-subif)#ip policy route-map TrafficToLeftS Router(config-subif)#exit Router(config)#interface fastEthernet 0/0.2 Router(config-subif)#encapsulation dot1Q 2 Router(config-subif)#ip address 10.1.2.1 255.255.0.
A route exists in the Routing Information Base (RIB) (for example, policy route only if 10.2.2.0/24 is in the RIB). Interface state (for example, packets received on E0 should be the policy routed out of E1 only if E2 is down).
70 6 - POLICY-BASED ROUTING DEPLOYMENTS
In This Chapter 7 - WCCP DEPLOYMENTS CHAPTER 7 WCCP Deployments This chapter describes how to configure the Web Cache Communication Protocol (WCCP) to redirect traffic to an HP EFS WAN Accelerator or group of HP EFS WAN Accelerators.
Introduction to WCCP WCCP was originally implemented on Cisco routers, multi-layer switches, and Web caches to redirect HTTP requests to local Web caches (Version 1). Version 2, which is implemented on HP EFS WAN Accelerators, can redirect any type of connection from multiple routers to multiple Web caches.
The following steps describe how WCCP works with the HP EFS WAN Accelerator: 1. Routers and HP EFS WAN Accelerators are added to the same service group. 3. Routers send back the state of the service group. 4. One HP EFS WAN Accelerator takes a leadership role and tells the routers how to redirect traffic among the HP EFS WAN Accelerators in the service group. The HP EFS WAN Accelerators use the following methods to communicate with routers: Unicast (User Datagram Protocol Packets).
You can also provide failover support using WCCP. In a failover configuration, the HP EFS WAN Accelerators periodically announce themselves to the routers. If an HP EFS WAN Accelerator fails, traffic is redirected to the working HP EFS WAN Accelerators. To configure failover support where the passive HP EFS WAN Accelerator takes over if there is a failure in the active HP EFS WAN Accelerator, you simply configure the weight for the backup HP EFS WAN Accelerator to be 0.
Specifies the service group identification number (ID) (from 0 to 255). The service group ID is the number that is set on the router. A value of 0 specifies the standard http service group which redirects only HTTP traffic. router The router IP is a multicast group IP address or a unicast router IP address. A total of 32 routers can be specified.
Connecting the HP EFS WAN Accelerator to Your Network in WCCP Deployments There are two Ethernet cables attached to the HP EFS WAN Accelerator in WCCP deployments: A straight-through cable to the Primary interface. You use this connection to manage the HP EFS WAN Accelerator, reaching it through HTTPS or SSH. A straight-through cable to the WAN interface. You assign an IP address to the In-Path interface; this is the IP address that you redirect traffic to.
IMPORTANT: When you connect to the WAN port on the HP EFS WAN Accelerator for WCCP, the LAN port no longer passes traffic. You cannot run the HP EFS WAN Accelerator in both in-path and client, out-of-path mode. Before you configure the HP EFS WAN Accelerator, you enable your router for WCCP. You create a service group and attach it to the interface where you want packets to be redirected.
In this example, the client-side, in-path HP EFS WAN Accelerator IP address is 10.1.0.2, its WAN router is 10.1.0.1, and the server-side HP EFS WAN Accelerator primary IP address is 10.2.0.2. To configure the HP EFS WAN Accelerator 1. Connect to the HP EFS WAN Accelerator (CLI). For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Command-Line Interface Reference Manual. 2.
Configuring WCCP Using the Management Console This section does not describe how you enable your router for WCCP and create a service group for the HP EFS WAN Accelerator. For detailed information about configuring your router, see “Configuring the WCCP Router or Multi-Layer Switch” on page 77. In this example, the client-side HP EFS WAN Accelerator IP address 10.1.0.2, its WAN router is 10.1.0.1, and the server-side HP EFS WAN Accelerator IP address is 10.2.0.2.
4. To enable external traffic redirection click Enable In-Path Support, Enable L4/ PBR/WCCP Support on Interface wan0_0, and Enable Optimization on Interface inpath0_0. Figure 7-3. Setup: Optimization Service - General Settings Page 5. Enable WCCP on your router.
6. Navigate to the Setup: Advanced Networking - WCCP Groups page. Figure 7-4.
7. Define the service group: Specify the service group identification number, the router IP address, password, priority, weight, and encapsulation scheme, and optionally, global settings. 8. Click Add Group to display your new group in the Service Group list. 9. Under General, click Enable WCCP v2 Support. 10. Click Apply to enable WCCP v2 support. 11. Double-click the new service group name to display the Setup: Service, WCCP Groups, Service Group page. 12.
13. Save and apply the new configuration in the Management Console. 14. Restart the HP EFS WAN Accelerator service in the Setup: Start/Stop Service page. To define in-path rules to reach the server-side appliance 15. Navigate to the Setup: Optimization Service - In-Path Rules page in the Management Console. 16. Define a fixed-target rule to optimize traffic on the server-side HP EFS WAN Accelerator with port 135. 17. Repeat Step 16 for ports 139, 445, and 80. 18.
Dual WCCP Deployment The following section describes how to deploy two HP EFS WAN Accelerators that are physically out-of-path but virtually in-path so that traffic is directed to them using WCCP. Figure 7-6. Dual WCCP Deployment Traffic between client and server passes through the two routers.
To configure router 2 7 - WCCP DEPLOYMENTS !Client Interface interface FastEthernet0/0 ip address 10.11.21.100 255.255.255.0 ip wccp 90 redirect in ! !HP EFS WAN Accelerator Interface interface FastEthernet0/1 ip address 10.11.22.17 255.255.255.0 • At the system prompt, enter the following set of commands: ip wccp 91 !Server Interface interface FastEthernet0/0 ip address 10.11.25.250 255.255.255.0 ip wccp 91 redirect in ! !HP EFS WAN Accelerator Interface interface FastEthernet0/1 ip address 10.11.24.
Additional WCCP Features This section describes the additional features for WCCP. Security To set the password for WCCP WCCP protocol messages can be authenticated between the router and the HP EFS WAN Accelerator using a password. The maximum password length is eight characters. 1. On the router, at the system prompt, enter the following command: Router(config)# ip wccp 90 password 2.
To configure multicast groups on the HP EFS WAN Accelerator client-SH client-SH client-SH client-SH client-SH client-SH client-SH > enable # configure terminal (config) # wccp enable (config) # wccp mcast-ttl 10 (config) # wccp service-group 90 routers 224.0.0.3 (config) # write memory (config) # exit By default, all TCP ports are redirected, but the HP EFS WAN Accelerator can be configured to tell the router to redirect only certain TCP source or destination ports.
For example, to configure load balancing, you change the hashing scheme to hash on a destination IP and port and specify a weight on the HP EFS WAN Accelerator. (You do not need to configure the router.) To change the hashing scheme and assign a weight 1. On the client-side HP EFS WAN Accelerator, enter the following command: client-SH (config) # wccp service-group 90 routers 10.1.0.1 flags dst-ip-hash,dst-port-hash 2.
In This Chapter Serial Cluster and Cascade Deployments This chapter describes serial cluster and cascade deployments and summarizes the basic steps for configuring them. This chapter includes the following sections: “Serial Cluster Deployment,” next “Cascade Deployment” on page 93 This chapter assumes that you are familiar with the HP EFS WAN Accelerator Management Console (Management Console).
Appliances in a cluster process the peering rules you specify in a spill-over fashion. When the maximum number of TCP connections for an HP EFS WAN Accelerator is reached, that appliance stops intercepting new connections and passes them on to the next HP EFS WAN Accelerator in the cluster (as defined by the peer rule that you set). This process continues until there are no more HP EFS WAN Accelerators available in the cluster. Figure 8-1.
HP EFS WAN Accelerator1 IP address is 10.0.1.1 on a /16 HP EFS WAN Accelerator2 IP address is 10.0.1.2 on a /16 HP EFS WAN Accelerator3 IP address is 10.0.1.3 on a /16 To configure HP EFS WAN Accelerator1 1. On HP EFS WAN Accelerator1, connect to the CLI. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Command-Line Interface Reference Manual. 2.
Rule Port ----1 2 def To configure HP EFS WAN Accelerator3 Type Source Addr ---pass pass auto Dest Addr Port Target Addr ------------------ ------------------ ----- --------------10.0.1.3/32 * * --10.0.1.1/32 * * --* * * --- 1. On HP EFS WAN Accelerator3, connect to the CLI. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Command-Line Interface Reference Manual. 2.
Cascade Deployment Figure 8-3. Cascade Deployment When the Client connects to a server in Site B, HP EFS WAN Accelerator1 and HP EFS WAN Accelerator2 are optimizing the connection. When the Client connects to a server in Site C, HP EFS WAN Accelerator1 and HP EFS WAN Accelerator3 are optimizing the connection. The following rules apply to cascade deployments: Peering Rules A cascade deployment can be created on either the client side or on the server side.
SH2 SH2 SH2 SH2 SH2 SH2 Server1 IP address is 10.0.2.0 on a /24 > enable # configure terminal (config) # in-path peering rule pass rulenum 1 (config) # in-path peering rule auto dest 10.0.2.0/24 rulenum 1 (config) # in-path rule pass-though dstport 7800 rulenum 1 (config) # wr mem SH2 (config) # show in-path peering rules Rule Type Source Network Dest Network Port Peer Addr ----- ---- - - ---- ------------------ ------------------ ------------1 auto * 10.0.2.
In This Chapter Proxy File Service Deployments This chapter describes Proxy File Service (PFS) and provides the basic steps for configuring it. This chapter includes the following sections: “Introduction to PFS,” next “Configuring PFS Using the Management Console” on page 101 This chapter assumes you are familiar with the installation and configuration process for the HP EFS WAN Accelerator.
PFS allows you to store copies of files on the HP EFS WAN Accelerator with Windows file access, creating several options for transmitting data between remote offices and centralized locations with improved performance. Data is configured into file shares and the shares are periodically synchronized (updated) transparently in the background, over the optimized connection of the HP EFS WAN Accelerator.
PFS Terms The following terms are used to describe processes and devices in PFS. Description Proxy File Server A virtual file server resident on the HP EFS WAN Accelerator, providing Windows file access (with ACLs) capability at a branch office on the LAN network, populated over an optimized WAN connection with data from the origin server. Origin File Server The server located in the data center which hosts the origin data volumes.
NOTE: For Broadcast mode: if you are performing directory moves regularly (for example, mv ./dir1/dir2 ./dir3/dir2), incremental synchronization will not reflect these directory changes. You must perform a full synchronization more frequently to keep the PFS shares in synchronization with the remote site. NOTE: While performing an incremental synchronization for a Broadcast mode share, if files are deleted on the server, they are not deleted on the HP EFS WAN Accelerator. Local Mode.
The HP EFS WAN Accelerator is configured as a Domain Member Server or a Local Workgroup. Figure 9-1. PFS Deployment Domain Mode In Domain mode, you join the Windows domain for which the HP EFS WAN Accelerator will be a member. Typically, this is the same domain as your company’s domain. Use Domain mode if you want the HP EFS WAN Accelerator to be more integrated in terms of permissions.
Before you enable Domain mode in PFS make sure you: Local Workgroup Mode configure the HP EFS WAN Accelerator to use Network Time Protocol (NTP) to synchronize the time. For detailed information about setting the date and time in the HP EFS WAN Accelerator, see the HP Enterprise File Services WAN Accelerator Management Console User Guide. configure the DNS server correctly. The configured DNS server must be the same DNS server to which all the Windows client machines point.
Local Mode. For environments that need to efficiently and transparently copy data created at a remote site to a central data center, perhaps where tape archival resources are available to backup the data. Local Mode enables read-write access at remote offices to update files on the origin file server. Stand-Alone Mode. For network environments where it is more effective to maintain a separate copy of files that are accessed locally by the clients at the remote site.
Basic Steps 1. Enable PFS and configure the operating mode (either domain or local workgroup) in the Management Console Proxy File Service (PFS) - Configuration page. 2. Create and manage PFS shares in the Management Console Proxy File Service Shares page. 3. Enable and synchronize shares in the Management Console Proxy File Services (PFS) - Shares Details page. 4. If you have v2.x PFS shares, upgrade them to v3.x shares in the Management Console Proxy File Service (PFS) - Shares Details page. 5.
In This Chapter 10 - QUALITY OF SERVICE CHAPTER 10 Quality of Service This chapter describes the HP EFS WAN Accelerator Quality of Service (QoS) feature and the basic steps for implementing it: “Introduction to Quality of Service for HP EFS WAN Accelerators,” next “Implementing QoS” on page 105 This chapter assumes you are familiar with the HP EFS WAN Accelerator Management Console (Management Console) and the HP EFS WAN Accelerator Command Line Interface (CLI).
HP EFS WAN Accelerators use Hierarchical Fair Service Curve (HFSC) QoS operations to simultaneously control bandwidth and latency for each QoS class. For each class, you can set a: Priority level. There are five QoS class priorities, as described in “About QoS Class Priorities” on page 104. Minimum guaranteed bandwidth level, which specifies the minimum amount of bandwidth a QoS class is guaranteed to receive when there is bandwidth contention.
Maximum Allowable QoS Classes Maximum Allowable QoS Rules 5x0, 1xx0 60 180 2xx0 80 240 3xx0 120 360 5xx0 200 600 10 - QUALITY OF SERVICE HP EFS WAN Accelerator Model Implementing QoS This section describes the basic steps for using the HP EFS WAN Accelerator Management Console (Management Console) to enable and configure QoS for a single HP EFS WAN Accelerator. For more information and detailed procedures, see the HP Enterprise File Services WAN Accelerator Management Console User Guide.
4. Create QoS rules for QoS classes in the Management Console Setup: Advanced Networking: QoS Classification - QoS Classes page. Each rule maps a type of network traffic to a QoS class. You can create more than one QoS rule for a QoS class. When more than one QoS rule is created for a QoS class, the rules are followed in the order in which they are shown under QoS Rules in the Management Console Setup: Advanced Networking - QoS Classification page and only the first matching rule is applied to the class.
In This Chapter 11 - NETWORK FILE SYSTEM OPTIMIZATION CHAPTER 11 Network File System Optimization This chapter describes the HP EFS WAN Accelerator Network File System (NFS) optimization feature and basic steps for implementing it: “Introduction to Network File System Optimization,” next “About NFS Prefetch Policies” on page 108 “Implementing NFS” on page 108 This chapter assumes you are familiar with NFS and the HP EFS WAN Accelerator Management Console (Management Console).
About NFS Prefetch Policies For each HP EFS WAN Accelerator, you can specify the policy it follows when prefetching data from NFS servers and volumes. You can choose from the following policies for all or specific NFS servers or volumes: Global read/write. (Default.) Choose this policy when the data on the NFS server or volume can be accessed from any client, including LAN clients and clients using other file protocols.
Basic Steps 1. Enable NFS in the Management Console Setup: Optimization Service - Protocol: NFS page. Enable NFS on all desired client and server HP EFS WAN Accelerators. Configure these settings on all desired client HP EFS WAN Accelerators. These settings are ignored on server HP EFS WAN Accelerators.
4. If you have configured IP aliasing for an NFS server, specify all of the server’s IP addresses in the HP EFS WAN Accelerator NFS protocol settings, as described in “Configuring IP Aliasing” on page 110. 5. View and monitor QoS statistics in the Management Console Reports: Performance: NFS Statistics page. For detailed information, see the HP Enterprise File Services WAN Accelerator Management Console User Guide.
In This Chapter 12 - RADIUS AND TACACS+ AUTHENTICATION CHAPTER 12 RADIUS and TACACS+ Authentication This chapter describes how to configure Remote Authentication Dial-In User Service (RADIUS) or Terminal Access Controller Access Control System (TACACS+) authentication for the HP EFS WAN Accelerator.
The HP EFS WAN Accelerator does not have the ability to set a per interface authentication policy. The same authentication method list is used for all interfaces (that is, default). You cannot configure authentication methods with subsets of the RADIUS or TACACS+ servers specified (that is, there are no server groups).
The contents of the dictionary. file define a vendor identifier (which ought to be the Structure of Management Information (SMI) Network Management Private Enterprise Code of the Vendor), and the definitions for any vendor specific attributes. These instructions assume you are running FreeRADIUS, v.1.0, which is available from http://www.freeradius.org. To install FreeRADIUS on a Linux computer 1. Download FreeRadius from http://www.freeradius.org. 2.
6. Add users to the Radius server by editing the /usr/local/etc/raddb/users file. For example: "admin" "monitor" "raduser" Auth-Type := Local, User-Password == "radadmin" Reply-Message = "Hello, %u" Auth-Type := Local, User-Password == "radmonitor" Reply-Message = "Hello, %u" Auth-Type := Local, User-Password == "radpass" Local-User = "monitor", Reply-Message = "Hello, %u" 7. Start the server using /usr/local/sbin/radiusd. Use the -X option if you want to debug the server.
6. As the root user, enter the following command: >make install key = testtacacs user = admin { pap = cleartext "tacadmin" user = monitor { pap = cleartext "tacmonitor" user = tacuser { pap = cleartext "tacpass" service = rbt-exec { local-user-name = "monitor" } The secret you specify here must also be specified in the HP EFS WAN Accelerator when you set up TACACS+ server support. For detailed information, see the HP Enterprise File Services WAN Accelerator Management Console User Guide.
To configure TACACS+ with Cisco Secure ACS 1. Log in to Cisco Secure ACS. 2. Click Interface Configuration. 3. Click TACACS+(CiscoIOS). 4. Under New Services: Check the User box. Under Service, type rbt-exec. Under Protocol, type unknown. 5. Click Submit. 6. Click User Setup and locate the name of the user you want to grant administrative access to the HP EFS WAN Accelerator. 7. At the bottom of the window, locate the TACACS+ Settings box. 8.
Basic Steps 1. Configure the HP EFS WAN Accelerator. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide. 3. In the Management Console Setup: Authentication - General Settings page, define the default login and the authentication methods. Make sure you put the authentication methods in the order in which you want them to occur.
Basic Steps 1. Configure the HP EFS WAN Accelerator. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide. 2. Connect to the Management Console. For detailed information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide. 3. In the Management Console Setup: Authentication - General Settings page, define the authentication methods.
In This Chapter Troubleshooting Deployment Problems This chapter describes common deployment problems and solutions.
Problem: Duplex Mismatch This section describes common problems that can occur in networks in which duplex settings do not match. Duplex mismatch, which can cause performance degradation and lost packets, is a condition that occurs when two devices that communicate over a network have different duplex settings. If all of your applications are slower after you have installed in-path HP EFS WAN Accelerators, it might be due to network duplex mismatch.
For more information, see the HP StorageWorks Enterprise File Services WAN Accelerator Command-Line Interface Reference Manual. If you have tried ensuring that speed and duplex settings match as well as manually setting speed and duplex settings, as described in previous sections, and duplex mismatch still causes slow performance and lost packets after you deploy in-path HP EFS WAN Accelerators, introduce an intermediary hub or switch that is more compatible with both existing network interfaces.
If synchronization (SYN) packets that traverse from one side of the network are optimized, but SYN packets that traverse from the opposite side of the network are passed-through unoptimized, it is a symptom of network asymmetry. The following figure shows an asymmetric server-side network in which a server response can traverse a path (the bottom path) in which an HP EFS WAN Accelerator is not installed. Figure 13-1.
page 47 and in the HP Enterprise File Services WAN Accelerator Management Console User Guide. For more information and examples, see Chapter 5, “Connection Forwarding.” Because a connection cannot be optimized unless packets traveling in both network directions pass through the same client-side HP EFS WAN Accelerator and the same server-side HP EFS WAN Accelerator, you can use a virtual in-path deployment to solve network asymmetry.
For more information on two- and four-port HP EFS WAN Accelerators, see the Bypass Card Installation Guide. Problem: Old Anti-Virus Software If, after installing HP EFS WAN Accelerators, application access over the network does not speed up or certain operations on files (such as dragging and dropping files) speed up greatly but application access does not, it could be due to old anti-virus software installed on a network client.
Solution: Use Simplified Routing You can also use simplified routing to prevent packet ricochet. To configure simplified routing, use the CLI command in-path simplified routing or the Management Console. Problem: Router CPU Spike After WCCP Configuration If a router’s central processing unit (CPU) usage spikes after WCCP configuration, it could be because you are not using a WCCP-compatible Cisco Internetwork Operating System (IOS) release, or because you need to use inbound redirection.
Solution: Use Inbound Redirection with Fixed-Target Rules If inbound redirection, described in “Solution: Use Inbound Redirection” on page 125, does not solve router CPU spike after WCCP is configured, try using inbound redirection with a fixed-target rule between HP EFS WAN Accelerators. The fixed-target rule can eliminate one redirection interface. Fixed-target rules directly specify server-side HP EFS WAN Accelerators near the target server that you want to optimize.
Symptoms of SMB signing are: Access to some Windows file servers in a WAN is slower than access to other Windows file servers in the WAN. Connections are shown as optimized in the Management Console. The results of a tcpdump show low WAN utilization for files where their contents do not match existing segments in the segment store. Copying files via File Transfer Protocol (FTP) from the slow server is much faster than copying the same files via mapped network drives (CIFS).
The following sections describe possible solutions to SMB-signed sessions: “Solution: Enable Secure-CIFS” on page 128 “Solution: Disable SMB Signing with Active Directory” on page 128 For more information, see the HP StorageWorks Enterprise File Services WAN Accelerator Installation and Configuration Guide. Solution: Enable Secure-CIFS Enable Secure-CIFS using the CLI command protocol cifs secure-sig-opt enable.
Problem: Unavailable Opportunistic Locks Without opportunistic locks (oplocks), SDR and compression are performed on file contents, but the HP EFS WAN Accelerator cannot perform latency optimization because data integrity cannot be ensured without exclusive access to file data. The following are symptoms of unavailable oplocks: Within a WAN: A client, PC1, in a remote office across the WAN can open a file it previously opened in just a few seconds.
Problem: Underutilized Fat Pipe A fat pipe is a network that can carry large amounts of data without significantly degrading transmission speed. If you have a fat pipe that is not being fully utilized and you are experiencing WAN congestion, latency, and packet loss as a result of the limitations of regular TCP, consider the solutions outlined in this section.
GLOSSARY Glossary ARP. Address Resolution Protocol. An IP protocol used to obtain a node's physical address. Bandwidth. The upper limit on the amount of data, typically in kilobits per second (kbps), that can pass through a network connection. Greater bandwidth indicates faster data transfer capability. Bit. A Binary digit. The smallest unit of information handled by a computer; either 1 or 0 in the binary number system. Blade.
FDDI. Fiber Distributed Data Interface. A set of American National Standards Institute (ANSI) protocols for sending digital data over fiber optic cable. FDDI networks are token-passing networks, and support data rates of up to 100 Mbps (100 million bits) per second. FDDI networks are typically used as backbones for WideArea Networks (WANs). Filer. An appliance that attaches to a computer network and is used for data storage. Gateway.
Internet. The collection of networks tied together to provide a global network that use the TCP/IP suite of protocols. IP. Internet protocol. Network layer protocol in the TCP/IP stack that enables a connectionless internetwork service. IPsec. Internet Protocol Security Protocol. A set of protocols to support secure exchange of packets at the IP layer. IPsec has been deployed widely to implement Virtual Private Networks (VPNs). IPsec supports two encryption modes: Transport and Tunnel.
WAN Accelerator only optimizes access to data to which exclusive access is available (in other words, when locks are granted). When an oplock is not available the HP EFS WAN Accelerator does not perform application-level latency optimizations but still performs Scalable Data Referencing and compression on the data as well as TCP optimizations.
that the total amount of bytes sent is received correctly at the other end. TCP/IP is a routable protocol, and the IP part of TCP/IP provides this capability.
136 GLOSSARY
A Antivirus compatibility 11 Anti-virus software 124 Application slowdown 120, 124 Architecture, overview of 15 Asymmetric network 122 asymmetric routing auto-detection of 122 Authentication, overview of 111 auto-detection of asymmetric routes 122 Auto-discovery configuring with CDP 66 PBR 63 rules, overview of 19 B Bypass mode, overview of 19, 20 C Cascade clusters, overview of 93 CDP, overview of 52 Client request 122 Connection forwarding as solution to network asymmetry 123 configuring using the CLI 50
hub 121 switch 121 IOS compatibility, as solution to router CPU spike after WCCP configuration 126 IP aliasing 110 L Layer-2 73 Layer-4 switch, configuring 32 Load balancing, configuring 32 Logical in-path deployment load balanced, Layer-4 switch deployment, configuring 32 PBR, overview of 32 WCCP, overview of 32 long fat pipe 130 M Multicast in WCCP 73 N Neighbors, overview of 46 Network asymmetry 122 connection failure 125 connections 122 path 122 Network File System (NFS) deployments 107 NFS prefetch pol
Router CPU spike 125 INDEX S Scalable Data Referencing, overview of 16, 19 Serial cluster, configuring 90 Server response 122 Settings duplex 120, 121 speed 120, 121 Share settings, PFS 102 Share synchronization, definition of 97 Share, definition of 97 Simplified routing, as solution to packet ricochet 125 SMB signing disabling 128 overview of 127 symptoms of 127 Software dependencies 10 Speed, settings 120 Static cluster deployment, configuring 39 Synchronization of data 121 of file shares 121 CLI comm
140 INDEX
