Cisco Lean Retail Oracle Siebel 8 Application Deployment Guide
Available Languages
Table Of Contents
Cisco Lean Retail Oracle Siebel 8
Application Deployment GuideSiebel Application Architecture
Application and Application Networking Design
Packet Flow Without Cisco WAAS and Cisco ACE
Packet Flow with Cisco WAAS and Cisco ACE
Implementing and Configuring the Cisco ACE Solution
What Was Not Implemented/Tested
Features, Services, and Application Design Considerations
Server Farms and Health Probes
Loadbalancing/TCP Reuse/SSL Termination
Scalability and Capacity Planning
Configuring Interface(s) and Default Gateway
Stickiness (Session Persistence)
Siebel Application Manager (AOM) Context Configuration
Management Access Configuration
Configuring Interface(s) and Default Gateway
Implementing and Configuring the Cisco WAAS Solution
Features, Services, and Application Design Considerations
Scalability and Capacity Planning
Appendix A—Cisco ACE Configuration
Siebel Application Farm (AOM) Context
Appendix B—Cisco WAE Configurations
Data Center Cisco WAE Configuration
Appendix C—Cisco ACE Appliance Configuration and Test Results
Appendix E—Cisco Advanced Services
Cisco Services Help Accelerate and Optimize ANS Deployments
Cisco Lean Retail Oracle Siebel 8
Application Deployment Guide
April 14, 2008
Introduction
The Cisco Lean Retail Oracle Siebel solution provides best practices and implementation guidance that optimizes application availability, performance, and security while lowering application ownership costs. Cisco's Lean Retail provides accelerated application performance and faster access to information. Data center-based applications and hosted managed services can have their performance accelerated to LAN-like speeds. Oracle's Siebel 8 Customer Relationship Management (CRM) enables organizations to transform the customer experience by managing sales, marketing, and customer service across all communication channels and points of customer contact.
Cisco's Lean Retail Architecture includes:
•
Reduced capital and operational costs for applications, servers, and networking
•
•
•
A key Lean Retail integrated network service is the Application Networking Service (ANS). This solution focuses on the ANS components of Cisco Application Control Engine (Cisco ACE) and Wide Area Application Services (WAAS) product families. It provides data center, retail store, and remote end user application optimization services. This collaboration between Oracle and Cisco addresses the following Siebel 8.0 deployment challenges:
•
•
•
The value of Cisco's Lean Retail is accomplished through four key benefits:
•
•
•
•
Deploying new applications and capabilities quickly and effectively are key IT metrics that improve an organization's business agility. Cisco's Lean Retail enables more applications to be deployed centrally, cutting down dramatically on the time and cost of deployment. Deploying centrally also reduces the costs of opening new stores and of integrating acquisitions. While many retailers will choose to deploy some applications in the stores, the Lean Retail Architecture improves the capabilities of a central deployment model. To learn more about Cisco's Lean Retail, see:
http://www.cisco.com/web/strategy/retail/lean-retail.html
Document Purpose
Cisco and Oracle cooperated in all phases of the Cisco Lean Retail for Siebel 8 testing, including lab set-up at Cisco offices, solution functional and performance testing, and this deployment guide. Cisco and Oracle jointly validated that the lab setup and solution testing represents best efforts in creating a realistic customer deployment and accurate documentation of such deployment.
The purpose of this document is to describe the Lean Retail Oracle Siebel 8 Solution enterprise network design, deployment, best practices, and guidance.
Prerequisites
The following prerequisites are required to deploy the Lean Retail Oracle Siebel 8 Solution:
•
•
•
•
Document Organization
The following table provides a brief description of each section.
A high-level introduction to the solution. Introduces the solution, historical aspects, potential benefits, and scope and limitations.
Describes the design of the Lean Retail Oracle Siebel 8 Solution.
Describes configuration and implementation of Cisco ACE within the Lean Retail Oracle Siebel 8 Solution.
Describes configuration and implementation of WAAS within the Lean Retail Oracle Siebel 8 Solution.
Sample Cisco ACE configuration.
Sample Cisco WAW configuration.
Appendix C—Cisco ACE Appliance Configuration and Test Results
Describes the configuration and implementation of Cisco ACE Appliance within the Lean Retail Oracle Siebel 8 Solution.
Describes the network management software used in the Lean Retail Oracle Siebel 8 Solution.
Describes the Cisco services available to accelerate deployment of the Lean Retail Oracle Siebel 8 Solution.
Solution Overview
Solution Description
The Lean Retail Oracle Siebel 8 Solution offers optimized Siebel 8.0 application availability, performance, security, and cost savings by providing application optimization services as follows:
•
Cisco ACE product family application optimization services for high Siebel 8.0 availability:
–
–
–
•
Cisco ACE and WAAS product family application optimization services for Siebel 8.0 high performance:
–
–
–
–
–
–
–
–
•
Cisco ACE product family application optimization services for optimized Siebel 8.0 data security:
–
–
•
Virtualization of application optimization services supplies such services for multiple Oracle and Siebel instances as well as other enterprise applications (see Figure 1). Specifically, a single physical Cisco ACE can be virtualized into multiple logical Cisco ACEs in which application traffic can traverse between virtualized Cisco ACEs. This virtualization of load balancing is an exclusive Cisco feature.
Figure 1 Virtualization of Application Optimization Services
The application optimization services of the Lean Retail Oracle Siebel 8 Solution reside in both the data center and the store to offer end-to-end value, from store and remote users, all the way through to the database and information storage.
•
Cisco ACE and WAAS reside in the data center and are arranged to provide virtualized application optimization services for multiple Oracle and Siebel instances as well as other enterprise applications.
Because of their unique location, these solutions can take intelligent action on end-user traffic before it is routed to the Siebel application servers, including server load balancing, server health monitoring, SSL decryption, TCP connection consolidation, and security access control.
While some of these functions could be provided natively by the Siebel application or third party server based solutions, Cisco networking provides these services cost-effectively, freeing up server processing and memory needs to focus on business logic computation.
•
Cisco WAAS also resides in the store office and is arranged to provide virtualized application optimization services for all application users in that location. Together with the data center WAAS deployment, the two offer a WAN optimization service through the use of intelligent caching, compression, and protocol optimization.
When the Siebel application servers respond to end-user requests, Cisco WAAS compresses the response and then most efficiently passes it across the WAN with minimal bandwidth usage and maximum speed. Commonly used information is cached both at the WAAS solution in the store as well as in the Cisco ACE solution in the data center, which significantly reduces the burden on the servers and the WAN (see Figure 1).
The scope of the lab engineering work pertaining to the Lean Retail Oracle Siebel 8 Solution consists of:
•
•
Note
Process Flow
Figure 2 Process Flow
Solution Design
Siebel Application Overview
Oracle Siebel 8.0 uses a multi-tiered application framework. The Siebel environment consists of client, application, and database tiers. The client tier comprises devices that access the application via the Web. The application tier can be broken down to two different functions, services that terminate client connections and application object managers (AOM) that perform the business logic. Multiple application components can reside in the application tier providing different business functions. The database tier contains the data base management system (DBMS) and shared file system. The DBMS serves as a repository for data collections. The shared file system is for attachment storage such as Adobe Acrobat files, fax quotes, and other documents.
Figure 3 Siebel Application Architecture
Siebel Application Architecture
Client Tier
There are multiple client types available on the Siebel platform. The major client types are Web client, mobile client, and dedicated Web client. Wireless and handheld clients are used in specialized applications such as retail and manufacturing.
•
•
•
Application Tier
The application tier contains two functional areas, services that terminate client connections and business logic.
The former component is called the Siebel Web Server Extension (SWSE). It is an add-on to Microsoft Internet Information Server (IIS). SWSE is responsible for handling Web requests from users. It forwards user requests to the Application Object Managers (AOM) via Siebel Internet Session API (SISNAPI) protocol. Siebel provides native server load balancing for highly-available Web servers. Third party load balancers are supported as well.
There are numerous Siebel application servers that provide different business applications. Each Siebel application component can be run on a single or multiple physical servers. Application components can be load balanced at the component level across different physical server pools. Load balancing can be configured with native Siebel load balancer or a third-party load balancer.
Database Tier
The database tier provides a repository to Siebel application data. It consist of a RDBMS and separate file system store.
•
•
Gateway Name Server
Gateway name server is a repository for configuration information for each Siebel server. It has configuration information about the Siebel Enterprise.
Application and Application Networking Design
Figure 4 Application and Application Networking Design
The Lean Retail Oracle Siebel 8 Solution uses WAAS to enhance performance and Cisco ACE to reduce the load on resources in the server farm. The WAAS and Cisco ACE each provide a unique benefit to the solution, however there are additional benefits when they are used together as the two solutions are complimentary. The Cisco ACE provides load balancing to the server farm. If the application uses SSL, then the Cisco ACE can provide SSL termination offload, thereby increasing efficiency by removing the load on the servers' resources and allowing the servers to process more transactions. Increased server efficiency also results if the Cisco ACE is used to provide TCP reuse.
The Lean Retail Oracle Siebel 8 Solution design is based on the Enterprise Branch Wide Area Application Services Design Guide (Enterprise Branch Design) and the Data Center Infrastructure Design Guide 2.1, both found at www.cisco.com/go/srnd.
In the Lean Retail Oracle Siebel 8 Solution design, the WAAS Solution is installed within the Cisco Wide Area Application Engine (WAE) Appliances.
Enterprise Store
The Enterprise Store Design shows the Cisco WAE appliance connected to the local store router, typically a Cisco Integrated Services Router (ISR). The design provides scalability and availability as compared to installing a Cisco WAAS Network Module within a Cisco ISR as the Cisco ISR must share its resources.
HP Mercury LoadRunner, running on a personal computer in the store, simulates users that would perform certain tasks in the application.
The traffic is redirected to the Cisco WAE via Web cache communications protocol (WCCP) from the store router. The Cisco WAE performs the following functions:
•
•
WAN Simulation
The WAN simulator provides simulations of the following WAN links:
1.
a.
2.
a.
Data Center
The data center (DC) follows the design guidelines found in the Data Center Infrastructure Design Guide 2.1, a Cisco Validated Design found at http://www.cisco.com/go/srnd. The design consists of a data center WAN router, core, aggregation, and access Ethernet switching, and the server farm where the application resides. In this document, the focus is on the DC WAN router, aggregation, and the server farm. The core Ethernet switching provides routing to and from the DC WAN router and the aggregation. The access Ethernet switching provides Layer 2 connectivity for the server farms to the aggregation.
The DC WAN router performs the same function as the store WAN router by redirecting traffic to the DC Cisco WAE. The DC Cisco WAE performs the following:
•
•
Included in the data center is the Cisco WAAS central manager (CM), which runs on the Cisco WAE appliance. The Cisco WAAS CM provides a centralized mechanism for configuring Cisco WAAS features and reporting and monitoring Cisco WAAS traffic. It can manage a topology containing thousands of Cisco WAE nodes and be accessed from any Web browser using SSL. The Cisco WAAS CM can be configured for high availability by deploying a pair of Cisco WAE appliances as central managers.
Within a Cisco WAAS topology, each Cisco WAE runs a process called central management system (CMS). The CMS process provides SSL-encrypted bidirectional configuration synchronization of the Cisco WAAS CM and the Cisco WAE appliances. The CMS process is also used to exchange reporting information and statistics at a configurable interval. When the administrator applies configuration or policy changes to a Cisco WAE appliance or a group of Cisco WAE appliances, the Cisco WAAS Central Manager automatically propagates the changes to each of the managed Cisco WAEs. Cisco WAEs that are not available to receive the changes will receive them the next time the appliances become available.
The aggregation segment contains Cisco ACE, which provides the following features:
•
•
•
•
•
Cisco ACE provides load balancing of the traffic to the server farm using one of the following methods: Round Robin, Weighted Round Robin, Least Connections, Hash address, Hash cookie, Hash Header, and Hash URL. In the Lean Retail Oracle Siebel 8 Solution, Least Connections was used, which selects the server with the fewest number of server connections. Cisco ACE is also used to provide SSL offload and TCP reuse.
Inter-chassis Cisco ACE redundancy was used, in which a Cisco ACE module in one Cisco Catalyst 6500 Series Switch chassis is protected by a Cisco ACE module in a peer Cisco Catalyst 6500 Series Switch chassis connected by a fault tolerant (FT) VLAN. The FT VLAN is used to transmit flow-state information, configuration synchronization information, and the redundancy heartbeat.
Server Farms
The Web server farm consisted of three Microsoft IIS Web servers with SWSE. A separate application server farm consisted of three Siebel application Servers connected to Oracle Database 10G.
The Siebel application resides on the Windows 2003 Enterprise Edition server operating system, with 3.4 GHz Intel Pentium D processors and 2 GB of RAM and 2 80 GB SATA hard drives.
Oracle Database 10G resides on the Windows 2003 Enterprise Edition server operating system with two 3.4 GHz dual core Intel Xeon processors and 3.25 GB of RAM and 2 80 GB SATA hard drives.
Packet Flow Without Cisco WAAS and Cisco ACE
Application packet flow from a remote site can be categorized into three segments, client, WAN, and server.
Figure 5 Normal Packet Flow
Client Segment
The client segment is defined as the location into which users are connected that allows them to obtain or retrieve data from the application residing on the server farm. Users have connected personal computers (PC) to a local external switch or an integrated switch/router. When a user opens a browser and provides a URL that points to the application residing on the server, the data is sent from the PC to the switch. The switch forwards the data to the router that connects to the wide area network (WAN).
WAN Segment
The WAN provides the connectivity from the client location to the data center where the server farm is located. The WAN is provided by a service provider (SP) with a given service level agreement (SLA). The WAN inherently introduces delay and packet loss to the data traffic (packets).
Server Segment
The server segment consists of a highly available and resilient core, aggregation, and access Ethernet switching. The core routes the data traffic to and from the WAN and the aggregation layer. The aggregation layer provides consolidation of multiple access layers and routes the access layer traffic into the core. The aggregation layer also takes the data traffic from the core layer and sends it to the appropriate access layer. The access layer provides connectivity to the server farm where the applications reside. The data traffic (URL, per the example) from the client segment transverses the data center until the data traffic is received by the appropriate server. The server's application responds to the request and responds back to the user by forwarding the appropriate data back the client segment.
Response Times
Transaction response time consists of server response time and WAN round trip time. Delays in the WAN or the time to process a request on a server lead to a longer wait times for data to be viewed by the end user.
Packet Flow with Cisco WAAS and Cisco ACE
Figure 6 Packet Flow with Cisco WAAS and Cisco ACE
The following sequence describes the handshake between a client and the server farm and the data transfer phase:
1.
2.
3.
4.
5.
6.
7.
8.
Implementing and Configuring the Cisco ACE Solution
Implementation
Implementation Overview
The Cisco ACE module used in this solution is deployed in a Cisco Catalyst 6509 switch in the data center aggregation layer. The Cisco ACE module is deployed in routed mode where multiple client and server side VLANs support unique IP subnets. In this deployment mode the Cisco ACE acts as the default gateway for the Web and application servers. Two Cisco ACE application contexts are used. Load balanced traffic traverses from the Web server farm to the application server farm on the same physical Cisco ACE. Cisco ACE is the only product on the market that accommodates and forwards traffic in multiple virtual contexts within the same hardware device.
What Was Implemented
Key features implemented on the Cisco ACE module to support this application are:
•
•
•
•
•
•
•
What Was Not Implemented/Tested
The following was not implemented in this solution:
•
•
•
Network Topology
Figure 7 Network Topology
Two virtual ACE contexts are used in this deployment. A logical diagram is easier to demonstrate multiple contexts in the Cisco ACE. IP addresses for this topology are shown in Table 1.
Hardware or Components
Table 2 Hardware
ACE20-MOD-K9
Must be inserted into a Cisco Catalyst 65XX chassis
N/A
Console port
957928 kB
Note
Software
Features and Functionality
Features, Services, and Application Design Considerations
The Siebel application architecture is flexible. Components within the multi-tiered framework can be on single or multiple servers. Traffic flow from the clients to the servers have clean boundaries between the different tiers. Figure 7 shows Cisco ACE can load balance Web servers and application object servers.
Cisco ACE Virtualization
•
•
Server Farms and Health Probes
Server farms are groups of hosts providing similar services in the network. There are two server farms in this deployment, Web server farm and application server farms. Server health check monitors the servers within the server farm. Cisco ACE takes the server out of rotation in the event that the server is down or services are unavailable. Numerous pre-configured health probes are available on the Cisco ACE, such as http, https, ping, etc. Http probe is used to monitor both Web server farm and application server farm.
More information on health probes is available in the Cisco ACE server load-balancing configuration guide: http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A1/configuration/slb/guide/slbgd.html.
Loadbalancing/TCP Reuse/SSL Termination
Cisco ACE supports both Layer 4 and Layer 7 load balancing. Layer 7 loadbalancing is deployed in this environment. Layer 7 load balancing must be used since cookie sticky, TCP re-use, and SSL termination are enabled. TCP reuse saves server CPU resources by re-using existing TCP connections to the server.
SSL processing can take a significant amount of CPU processing cycles. Network hardware-assisted SSL termination can reduce overall server load on the Web servers. Cisco ACE supports SSL 3.0 and TLS 1.0.
Scalability and Capacity Planning
Server farms can increase application scalability and availability by load balancing applications services with multiple servers. In the event a server is down, other servers within the server farm can assume the load. Additional servers can be added to the server farm for scalability. SSL and TCP reuse can reduce additional load on the server farms.
High Availability
Cisco ACE High Availability
The Cisco ACE has many high availability features. It is an active/active system. Multiple contexts can be active simultaneously on both devices in a HA configuration. When the Cisco ACE is deployed in an inter-chassis configuration, configuration and state information are preserved. Failover between the Cisco ACE is stateful. Client connections are preserved in Cisco ACE failovers.
Server Farm High Availability
High availability and scalability is achieved by load balancing multiple servers within the server farm. Multiple levels of availability are available on the Cisco ACE, such as ping probes, server farms, and backup server farms. Scalability and Capacity Planning describes individual server failures and recovery methods.
Configuration Task Lists
This section describes the steps necessary to configure the equipment.
MSFC Configuration
A Cisco ACE module interacts with clients and servers via VLANs that are set up in Cisco Catalyst 6500 Series/Cisco 7600 Series Supervisor Engine 720 (Sup 720). These VLANs must be configured on Sup720 to be allowed to be sent to the Cisco ACE module. Without this configuration, by default Cisco ACE does not receive any traffic from any VLAN.
The following sample configuration steps are performed on the MSFC. Refer to Appendix A—Cisco ACE Configuration for a complete configuration.
Step 1
vlan 220name ACE-CLIENT!vlan 221name ACE-SERVER!vlan 500name ACE-FT-VLAN!Step 2
For this deployment, Cisco ACE is installed in slot 4 in the Cisco Catalyst 6500 chassis. The following configuration needs to be added to allow Cisco ACE-specific VLAN traffic to be directed towards Cisco ACE:
svclc multiple-vlan-interfacessvclc module 4 vlan-group 40svclc vlan-group 40 41-43,82,100,101Step 3
The SVI (interface VLAN) configuration defines Layer 3 instance on the router MSFC. The Cisco ACE client side VLAN SVI configuration is:
WebFarminterface Vlan101description ACE-Client vlan Web Farmip address 13.1.101.2 255.255.255.0standby 1 ip 13.1.101.1standby 1 timers 1 3standby 1 priority 115standby 1 preempt delay minimum 1Application Farminterface Vlan100description DC server VLAN and AOM Farm client vlanip address 13.1.40.2 255.255.255.0standby 1 ip 13.1.40.1standby 1 timers 1 3standby 1 priority 115standby 1 preempt delay minimum 1
WebFarm Context Configuration
The following steps need to run in the WebFarm context.
Remote Management Access
To access the Cisco ACE module remotely using Telnet, SSH, SNMP, HTTP, or HTTPS or to allow ICMP access to the Cisco ACE module, a policy must be defined and applied to the interface(s) the access is entering. It is recommended that only secure protocols be used to maintain compliance requirements, e.g., PCI.
The configuration steps in this section are required for both the Admin context and the application context. The following example is for the application context. Refer to Appendix A—Cisco ACE Configuration for a complete configuration.
Step 1
class-map type management match-any REMOTE-MGMT2 match protocol ssh any3 match protocol telnet any4 match protocol icmp any5 match protocol http any6 match protocol https anyStep 2
policy-map type management first-match REMOTE-ACCESSclass REMOTE-MGMTpermitStep 3
interface vlan 41service-policy input REMOTE-ACCESSinterface vlan 101service-policy input REMOTE-ACCESS
Configuring Interface(s) and Default Gateway
Interface VLANs need to be configured for Layer 3 connectivity to Cisco ACE. Service policies for load balancing, security, and management access to Cisco ACE are also applied at the interface VLAN level.
The configuration steps in this section are required for both the Admin context and the application context. The following example is for the application context. Refer to Appendix A—Cisco ACE Configuration for a complete configuration.
Step 1
access-list ALLOW-TRAFFIC line 8 extended permit ip any anyaccess-list ALLOW-TRAFFIC line 9 extended permit icmp any anyStep 2
interface vlan 41description web farm vlanip address 13.1.41.2 255.255.255.0alias 13.1.41.1 255.255.255.0peer ip address 13.1.41.3 255.255.255.0interface vlan 101ip address 13.1.101.14 255.255.255.0alias 13.1.101.13 255.255.255.0peer ip address 13.1.101.15 255.255.255.0Step 3
interface vlan 41access-group input ALLOW-TRAFFICaccess-group output ALLOW-TRAFFICservice-policy input REMOTE-ACCESSno shutdowninterface vlan 101access-group input ALLOW-TRAFFICaccess-group output ALLOW-TRAFFICservice-policy input REMOTE-ACCESSno shutdownStep 4
ip route 0.0.0.0 0.0.0.0 10.1.220.1Step 5
Type show interface and verify the VLANs are up and assigned from the supervisor.
Here is an example of a working output:
vlan220 is upHardware type is VLANMAC address is 00:1b:d5:9b:88:edVirtual MAC address is 00:0b:fc:fe:1b:02Mode : routedIP address is 10.1.220.5 netmask is 255.255.255.0FT status is activeDescription:Client side vlanMTU: 1500 bytesLast cleared: neverAlias IP address is 10.1.220.4 netmask is 255.255.255.0Peer IP address is 10.1.220.6 Peer IP netmask is 255.255.255.0Assigned from the Supervisor, up on Supervisor53808467 unicast packets input, 17900167965 bytes7331701 multicast, 7776 broadcast0 input errors, 0 unknown, 0 ignored, 0 unicast RPF drops91028995 unicast packets output, 5455629020 bytes4 multicast, 5202 broadcast0 output errors, 0 ignoredvlan221 is upHardware type is VLANMAC address is 00:1b:d5:9b:88:edVirtual MAC address is 00:0b:fc:fe:1b:02Mode : routedIP address is 10.1.221.2 netmask is 255.255.255.0FT status is activeDescription:Server side vlanMTU: 1500 bytesLast cleared: neverAlias IP address is 10.1.221.1 netmask is 255.255.255.0Peer IP address is 10.1.221.3 Peer IP netmask is 255.255.255.0Assigned from the Supervisor, up on Supervisor83222640 unicast packets input, 95861661879 bytes1118208 multicast, 47974 broadcast0 input errors, 0 unknown, 0 ignored, 0 unicast RPF drops53089290 unicast packets output, 4304456323 bytes4 multicast, 14950 broadcast0 output errors, 0 ignored
Probes
Cisco ACE uses probe, one of the available keep-alive methods, to verify the availability of a real server. Probe is configured by defining its type and name.
There are different types of probes that can be configured on Cisco ACE:
dns Configure dns probeecho Configure echo probefinger Configure finger probeftp Configure ftp probehttp Configure http probehttps Configure https probeicmp Configure icmp probeimap Configure imap probeldap Configure ldap probepop Configure pop proberadius Configure radius probescripted Configure script probesmtp Configure smtp probetcp Configure tcp probetelnet Configure telnet probeudp Configure udp probeHTTP probe is used to check the availability of the Web farm.
probe http http-probeinterval 30expect status 200 200
Note
Real Server
Cisco ACE selects the real server and sends traffic based on certain sets of criteria. When configuring a real server, be aware that real server name is case sensitive. The minimum configuration needed for rserver configuration is IP address and making the rserver inservice. Same rserver can be used in multiple server farms (shown later in the document). If an rserver is made no inservice at the rserver level, then it is taken out of rotation from every server farm at which it is configured. This provides the flexibility to take a server completely out of rotation with a single command.
rserver host websrvr1description Siebel web serverip address 13.1.41.57inservicerserver host websrvr2description Siebel web serverip address 13.1.41.58inservicerserver host websrvr3description Siebel web serverip address 13.1.41.59inserviceServer Farm
A server farm is a logical collection of real servers (rservers) that load balancer selects based on certain sets of criteria. As with real server, serverfarm name is also case sensitive.
Basic server farm configuration includes adding rservers and probes to the server farm.
serverfarm host WEBFARMprobe http-proberserver websrvr1 80inservicerserver websrvr2 80inservicerserver websrvr3 80inserviceLayer 7 Load Balancing
Cisco ACE uses class-map, policy-map, and service-policy to classify and enforce a Layer 7 policy. Cisco ACE uses additional information, such as URL, HTTP header, or cookie to make a load balancing decision. The following example shows the configuration steps for URL-based matching:
Step 1
class-map type http loadbalance match-any L7_WEB2 match http url .*.Step 2
parameter-map type http HTTP_PARAMETERSserver-conn reusecase-insensitiveStep 3
class-map match-all L4_WEB_VIP_CLASSStep 4
policy-map type loadbalance first-match L7-WEB-MATCHclass L7_WEBsticky-serverfarm sn_cookieStep 5
policy-map multi-match L4-WEB-VIPclass L4_WEB_VIP_CLASSloadbalance vip inserviceloadbalance policy L7-WEB-MATCHloadbalance vip icmp-replyloadbalance vip advertise activeStep 6
interface vlan 101service-policy input L4-WEB-VIP
Stickiness (Session Persistence)
Session persistence or sticky configuration allows multiple connections from the same client to be sent to the same real server by Cisco ACE. Cisco ACE supports stickiness based on source/destination (or both) IP address and HTTP cookies.
Cookie Sticky
Cookie Sticky is used in this deployment.
Step 1
sticky http-cookie _sn sn_cookiereplicate stickyserverfarm WEBFARMStep 2
policy-map type loadbalance first-match L7-WEB-MATCHclass L7_WEBsticky-serverfarm sn_cookieStep 3
policy-map multi-match L4-WEB-VIPclass L4_WEB_VIP_CLASSloadbalance vip inserviceloadbalance policy L7-WEB-MATCHloadbalance vip icmp-replyloadbalance vip advertise activeStep 4
interface vlan 101service-policy input L4-WEB-VIP
SSL Termination
SSL termination configuration on Cisco ACE provides SSL traffic termination on Cisco ACE instead of on the servers. This allows the offloading of server resources and also provides HTTP request inspection for various load balancing functionality.
With SSL termination on the Cisco ACE, client to Cisco ACE traffic is SSL encrypted, but Cisco ACE to server traffic is clear-text. The configuration steps to implement front end SSL termination are:
Step 1
crypto generate key 1024 siebelweb.keyEDAL-AGG1-ACE/WebFarm# sh crypto key allFilename Bit Size Type-------- -------- ----siebelweb.key 1024 RSAStep 2
crypto csr-params testparmscountry USstate Californialocality San Joseorganization-name ESEorganization-unit ESEcommon-name www.testsiebel.comserial-number cisco123Step 3
crypto generate csr testparms siebelweb.key-----BEGIN CERTIFICATE REQUEST-----MIIBrjCCARcCAQAwbjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExETAPBgNVBAcTCFNhbiBKb3NlMQwwCgYDVQQKEwNFU0UxDDAKBgNVBAsTA0VTRTEbMBkGA1UEAxMSd3d3LnRlc3RzaWViZWwuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDE02KxO5XSi6FqwUCJ4py58NTfTiGDu/MczEt6ejVCVnLmRdakPXQovjy3ALatZe6p7IqjBDvoPSU/no6g2nAKqqObkwkmNCTep6rwNwBSlyXoh9lVvwZIFhWYmDgV5jYInPRT5qHmv5RXJK9YiMwhcQOSqJzCgF+L5RZP8aUUOQIDAQABoAAwDQYJKoZIhvcNAQEEBQADgYEARr1CUrhloKmhRtAtBeDuRmb4w6QOymrg6m8vwJ0Sywc03F4BBoFqfPmSACrSW/qyfjGYLK0dYbZV0xq+min2932zN2e6lVAdHtuFLt0/ACKOTAtGFXe849WoEghuKvICV/RZslNXgNAO4/udL6p7vQ02+sSFqLQ9OQ0fWX2nwo8=-----END CERTIFICATE REQUEST-----Step 4
An SSL certificate can be obtained from various Certificate Authority (CA) companies like VERISIGN. A local certificate server was used to generate the certificate.
Step 5
EDAL-AGG1-ACE/Siebel# crypto import ftp 13.1.40.53 anonymous siebelweb.cer siebelweb.cerPassive mode on.Hash mark printing on (1024 bytes/hash mark).#Successfully imported file from remote server.Step 6
EDAL-AGG1-ACE/WebFarm# crypto verify siebelweb.key siebelweb.cerKeypair in siebelweb.key matches certificate in siebelweb.cer.Step 7
a.
parameter-map type ssl SSL_PARAMETERScipher RSA_WITH_RC4_128_MD5version TLS1b.
ssl-proxy service SIEBELWEB_SSLkey siebelweb.keycert siebelweb.cerStep 8
class-map match-all L4_SSL_VIP_CLASS2 match virtual-address 13.1.101.41 tcp eq httpspolicy-map type loadbalance first-match L7-SSL-MATCHclass L7_WEBsticky-serverfarm sn_cookiepolicy-map multi-match L4-WEB-VIPclass L4_WEB_VIP_CLASSloadbalance vip inserviceloadbalance policy L7-WEB-MATCHloadbalance vip icmp-replyloadbalance vip advertise activeclass L4_SSL_VIP_CLASSloadbalance vip inserviceloadbalance policy L7-SSL-MATCHloadbalance vip icmp-replyloadbalance vip advertise activessl-proxy server SIEBELWEB_SSLStep 9
interface vlan 101description ACE WEBFARM client vlanip address 13.1.101.14 255.255.255.0alias 13.1.101.13 255.255.255.0peer ip address 13.1.101.15 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICaccess-group output ALLOW-TRAFFICservice-policy input REMOTE-ACCESSservice-policy input L4-WEB-VIPno shutdown
Siebel Application Manager (AOM) Context Configuration
The following steps need to run in the Siebel application context. Siebel load balancing must use rules from lbconfig.txt. Section two contains the rules for Cisco ACE.
This is a cleaned up lbconfig.txt; only the relevant AOM are defined.
#This is the load balance configuration file generated by the Siebel srvrmgr"generate lbconfig" command.#It contains two sections. Section one contains load balancing rules to be usedby Siebel session manager.#Section two is intended for 3rd party load balancers. Before modifying the conent of this file please#read the chapter on SWSE configuration in the Siebel Bookshelf.#Section one -- Session Manager Rules:VirtualServer=9:appsrvr1:2321;13:appsrvr2:2321;11:appsrvr3:2321;******************************#Section two -- 3rd Party Load Balancer Rules#Component Rules:/SBA_80/SalesCEObjMgr_enu=appsrvr3:2321;appsrvr2:2321;appsrvr1:2321;/SBA_80/SCCObjMgr_enu=appsrvr3:2321;appsrvr2:2321;appsrvr1:2321;#Server Rules:*/!9.*=appsrvr1:2321;*/!d.*=appsrvr2:2321;*/!b.*=appsrvr3:2321;#Round Robin Rules:/SBA_80/SalesCEObjMgr_enu/RR=appsrvr3:2321;appsrvr2:2321;appsrvr1:2321;/SBA_80/SCCObjMgr_enu/RR=appsrvr3:2321;appsrvr2:2321;appsrvr1:2321;Virtualization
Virtualization is a method to allocate available resources into two or more contexts for security and management purposes. Up to 250 (5 with no additional license requirements) contexts can be configured on Cisco ACE. Resources can be allocated to each context to avoid a single context consuming the entire pool of resources. This document only covers key virtualization configuration. Within each context, Domains and Role Base Access Controls (RBACs) can be further configured to provide additional security and access control to the resources.
Step 1
resource-class WebFarmlimit-resource all minimum 20.00 maximum unlimitedlimit-resource sticky minimum 40.00 maximum equal-to-minresource-class siebel-resourcelimit-resource all minimum 20.00 maximum unlimitedlimit-resource sticky minimum 40.00 maximum equal-to-minStep 2
context Siebelallocate-interface vlan 42allocate-interface vlan 100member siebel-resourcecontext WebFarmallocate-interface vlan 41allocate-interface vlan 101member WebFarm
Redundancy/High Availability
To provide high availability and redundancy, Cisco ACE can be set up and configured in a redundant mode. Cisco ACE can be configured in a typical active/backup redundancy mode or active/active (per context) redundancy mode.
! Configure FT interfaceft interface vlan 43ip address 192.168.100.1 255.255.255.0peer ip address 192.168.100.2 255.255.255.0no shutdown! Configure FT peerft peer 1heartbeat interval 200heartbeat count 20ft-interface vlan 43! Create a fault tolerant group - one for each contextft group 1peer 1priority 120associate-context Siebelinserviceft group 2peer 1priority 120associate-context WebFarminserviceBy assigning context(s) to an FT group, a network administrator can create multiple groups for multiple contexts where the ACTIVE contexts can be distributed among the two Cisco ACE modules. This setup provides active/active redundancy setup for load sharing and high availability.
Management Access Configuration
Refer to the step-by-step instructions in WebFarm Context Configuration. The access and permission list is the same. This is the interface configuration with different IP addresses:
interface vlan 42description application farm vlanip address 13.1.42.2 255.255.255.0alias 13.1.42.1 255.255.255.0peer ip address 13.1.42.3 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICservice-policy input REMOTE-ACCESSno shutdowninterface vlan 100description ACE AOM client vlanip address 13.1.40.11 255.255.255.0alias 13.1.40.10 255.255.255.0peer ip address 13.1.40.12 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICservice-policy input REMOTE-ACCESSservice-policy input L4-APPS-VIPno shutdownConfiguring Interface(s) and Default Gateway
Refer to the step-by-step instructions in WebFarm Context Configuration. This is the configuration:
ip route 0.0.0.0 0.0.0.0 13.1.40.1Probes
Refer to the step-by-step instructions in WebFarm Context Configuration.
HTTP probe is used to check the availability of the application farm. It checks port 2321 of the Siebel Servers.
probe http scbroker-probeport 2321interval 30passdetect interval 10passdetect count 1request method get url /SBA_80/scbrokerexpect status 100 200Real Server
Cisco ACE selects the real server and sends traffic based on certain sets of criteria. When configuring a real server, be aware that real server name is case sensitive. The minimum configuration needed for rserver configuration is IP address and making the rserver inservice. The same rserver can be used in multiple server farms (shown later in the document). If an rserver is made no inservice at the rserver level, then it is taken out of rotation from every server farm at which it is configured. This provides the flexibility to take a server completely out of rotation with a single command.
rserver host appsrvr1description Siebel application serverip address 13.1.42.54inservicerserver host appsrvr2description Siebel application serverip address 13.1.42.55inservicerserver host appsrvr3description Siebel application serverip address 13.1.42.56inservice inserviceServer Farms
A server farm is a logical collection of real servers (rservers) that load balancer can select based on certain sets of criteria. As with real server, serverfarm name is also case sensitive.
The Siebel application requires Layer 7 load balancing for the AOM. Each application must be defined as its own server farm. Each server must also be defined as a server farm for direct server access. The total number of server farms is two times the number of AOMs plus the number of servers. In this case, seven server farms must be defined for two applications
Step 1
serverfarm host APPS1FARMprobe scbroker-proberserver appsrvr1 2321inserviceserverfarm host APPS2FARMprobe scbroker-proberserver appsrvr2 2321inserviceserverfarm host APPS3FARMrserver appsrvr3 2321inserviceStep 2
serverfarm host SCCOBJMGR_FARMprobe scbroker-proberserver appsrvr1 2321inservicerserver appsrvr2 2321inservicerserver appsrvr3 2321inserviceserverfarm host SCCOBJMGR_FARM_RRprobe scbroker-proberserver appsrvr1 2321inservicerserver appsrvr2 2321inservicerserver appsrvr3 2321inserviceStep 3
serverfarm host SALESCEOBJMGR_FARMprobe scbroker-proberserver appsrvr2 2321inservicerserver appsrvr3 2321inserviceserverfarm host SALESCEOBJMGR_FARM_RRrserver appsrvr2 2321inservicerserver appsrvr3 2321inservice
Layer 7 Load Balancing
Cisco ACE uses class-map, policy-map, and service-policy to classify and enforce a Layer 7 policy. Cisco ACE uses additional information such as URL, HTTP header, or cookie to make a load balancing decision. The following example shows the configuration steps for URL-based matching.
The following example shows the configuration steps needed:
Step 1
class-map type http loadbalance match-any L7_APPSERVER_1_CLASS2 match http url .*/!9\. method POSTclass-map type http loadbalance match-any L7_APPSERVER_2_CLASS2 match http url .*/!d\. method POSTclass-map type http loadbalance match-any L7_APPSERVER_3_CLASS2 match http url .*/!b\. method POSTclass-map type http loadbalance match-any L7_SALESCEOBJMGR_CLASS2 match http url .*/sba_80/sseobjmgr_enu method POSTclass-map type http loadbalance match-any L7_SALESCEOBJMGR_RR_CLASS2 match http url .*/sba_80/sseobjmgr_enu/rr method POSTclass-map type http loadbalance match-any L7_SCCOBJMGR_CLASS2 match http url .*/sba_80/sccobjmgr_enu method POSTclass-map type http loadbalance match-any L7_SCCOBJMGR_RR_CLASS2 match http url .*/sba_80/sccobjmgr_enu/rr method POSTStep 2
parameter-map type connection TCP_PARAMETERset timeout inactivity 86400Step 3
class-map match-all L4_APPS_VIP_CLASS-23212 match virtual-address 13.1.40.42 tcp eq 2321Step 4
policy-map type loadbalance first-match L7-APPS-MATCHclass L7_SCCOBJMGR_CLASSserverfarm SCCOBJMGR_FARMclass L7_APPSERVER_1_CLASSserverfarm APPS1FARMclass L7_APPSERVER_2_CLASSserverfarm APPS2FARMclass L7_APPSERVER_3_CLASSserverfarm APPS3FARMclass L7_SALESCEOBJMGR_CLASSserverfarm SALESCEOBJMGR_FARMclass L7_SCCOBJMGR_RR_CLASSserverfarm SCCOBJMGR_FARM_RRclass L7_SALESCEOBJMGR_RR_CLASSserverfarm SALESCEOBJMGR_FARM_RRStep 5
policy-map multi-match L4-APPS-VIPclass L4_APPS_VIP_CLASS-2321loadbalance vip inserviceloadbalance policy L7-APPS-MATCHloadbalance vip icmp-replyloadbalance vip advertise activeconnection advanced-options TCP_PARAMETERStep 6
interface vlan 100description ACE AOM client vlanip address 13.1.40.11 255.255.255.0alias 13.1.40.10 255.255.255.0peer ip address 13.1.40.12 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICservice-policy input REMOTE-ACCESSservice-policy input L4-APPS-VIPno shutdown
Configuration and Menus
See Appendix A—Cisco ACE Configuration.
Troubleshooting Configuration
These show commands can help troubleshoot issues with the configuration:
•
•
•
•
•
•
•
•
•
•
•
•
Implementing and Configuring the Cisco WAAS Solution
Implementation
Implementation Overview
The Cisco WAAS solution requires a minimum of three Cisco Wide Area Application Engine (WAE) appliances to auto-discover and deliver applicable application optimizations. One Cisco WAE is placed in the enterprise data center and the other at the store site. The enterprise data center Cisco WAE is placed on the WAN edge connected to the WAN router. The third Cisco WAE is used for the Central Manager. The design offloads the Cisco WAE device from the local store router and leverages the available ports on a local switch. This design provides scalability and availability for the solution.
What Was Implemented
Cisco WAAS technology requires the efficient and predictable interception of application traffic to produce results. It is critical that the Cisco WAE device see the entire TCP conversation. At the WAN edge, Cisco routers support the following four methods of traffic interception:
•
•
•
•
WCCPv2 is the most common method used in the store environment; therefore, WCCPv2 has been leveraged for this solution.
Note
What Was Not Implemented
The following was not implemented in this solution:
•
Network Topology
Figure 8 Network Topology
Hardware or Components
Software
Features and Functionality
Features, Services, and Application Design Considerations
Most multi-tiered applications support Web-based clients in addition to native application clients. Web-based clients use port 80 to communicate to the Web server. Applications in this test use port 80. In the context of Cisco WAAS, port 80 is accelerated by default; no further configuration in the Cisco WAE is necessary unless the application requires ports that are not part of the default application profile. For applications that use TCP ports that are not defined in the default application profile, you must define ports to the existing application profile or create a new application profile with the associated ports. With the recommended design of Cisco WAAS at the WAN edge, client data only traverse the Cisco WAEs once, at the ingress/egress of the data center. Further application communication between the Web servers, application servers, and database servers are within the data center and are not affected by Cisco WAAS.
Transport Flow Optimization (TFO), Data Redundancy Elimination (DRE), and Lempel-Ziv (LZ)-compression, the three key technologies of Cisco WAAS, are enabled by default. Each of these features and functions are described in Features and Functionality. The net results are reduced traffic and decreased latency across the WAN. Since Cisco WAAS deployments are transparent to the network and application, applications do not need to be aware of the added functions and continue to work as-is, but with decreased response time and increased traffic throughput and transactions.
Additional information on Cisco WAAS data center and branch designs are available at:
•
•
Scalability and Capacity Planning
Cisco WAE farms can scale up to 32 devices with WCCP and up to 16000 with Cisco ACE load balancing. Cisco WAAS services scale linearly in a N+1 configuration. In addition to the Max Optimized TCP connections, the fan out ratio between the DC Cisco WAE and store Cisco WAE have to be considered. The fan out ratio is determined by a number of factors, such as the number of Cisco WAEs in the store offices, amount of network traffic, and number of TCP connections. A sizing tool is available internally that can help automate sizing decisions. NetFlow, NetQoS, and other network analysis tools can provide additional traffic flow information for increased accuracy in scalability and capacity planning.
Store devices range from the NME-WAE-302 for very small offices to the 612-4GB or even higher models for bigger store sites. WAE 7326 and up are designed for data center installations.
High Availability
Cisco WAAS deployments are transparent to the application. The application client and server do not know Cisco WAAS is optimizing traffic flows. High availability is built into the WCCP interception. When WCCP is not active or if Cisco WAAS devices are not functioning, WCCP does not forward traffic to the Cisco WAEs, resulting in un-optimized traffic flow. This is the worse case scenario; traffic flow continues but is not optimized.
Device High Availability
The Cisco WAEs have many built-in high availability features. The disk subsystem is recommended to be configured with RAID 1 protection. RAID 1 is mandatory when two or more drives are installed in the Cisco WAE. With RAID 1, failure of the physical drive does not affect normal operations. Failed disks can be replaced during planned downtime. Multiple network interfaces are available. Standby interfaces can be configured for interface failover. A standby interface group guards against network interface failure on the Cisco WAE and switch. When connected to separate switches in active/standby mode, the standby interface protects the Cisco WAE from switch failure.
N+1 Availability
Cisco WAEs and the network provide additional high availability (HA) capabilities. Routers can be configured redundantly providing HSRP or GLBP services. Cisco WAEs can configured in a N+1 configuration. N+1 configuration provides scalability and availability. This design calls for N number of Cisco WAEs for a specific workload, then add a standby Cisco WAE. Since the workload always distributes evenly among the Cisco WAEs, the standby Cisco WAE is utilized, reducing overall workload. In the event that a Cisco WAE fails, the rest of Cisco WAEs can resume normal workload.
Configuration Task Lists
The following subsections describe the information required prior to configuration of the equipment.
Central Manager
Central Manager (CM) is the management component of Cisco WAAS. CM provides a GUI for configuration, monitoring, and management of multiple store and data center Cisco WAEs. CM can scale to support thousands of Cisco WAE devices for large-scale deployments. The CM is necessary for making any configuration changes via the Web interface. In the event of CM failure, Cisco WAEs continue to function, however changes cannot be made using the Web pages on the CM until the CM comes back online.
Cisco WAEs need to connect to the CM on the initial setup. The registration process adds the Cisco WAE to the CM and initializes the local Cisco WAE data base. When disk encryption on the Cisco WAE is enabled, the CM must be available to distribute the encryption key in the event the Cisco WAE reboots.
Centralized reporting can be obtained from the CM. Individually, the Cisco WAEs provide basic statistics via the CLI and local device GUI. System-wide application statistics are available from the CM GUI. Detailed reports such as total traffic reduction, application mix, and pass-through traffic can be obtained from CM GUI.
The following example shows the configuration steps needed to configure CM.
Note
Step 1
device mode central-managerStep 2
interface GigabitEthernet 1/0ip address 13.1.40.8 255.255.255.0Step 3
ip default-gateway 13.1.40.1Step 4
primary-interface GigabitEthernet 1/0Step 5
ntp server 13.1.5.2Step 6
cms enableStep 7
Figure 9 Cisco WAAS Central Manager
Store and Data Center Router
The store and data center router provides WCCP interception points for Cisco WAAS. Without WCCP interception, Cisco WAAS does not know where to obtain and optimize traffic flow. Different methods of interception and redirection are supported by routers and switches. Redirection methods depend on the speed requirement and router/switch platform. In this deployment, Generic Router Encapsulation (GRE) redirection is used.
The loopback interface on the router is essential for identifying the router ID. While any IP address can be used to identify the router ID, the loopback interface is preferred over the physical interfaces. Loopback interfaces are always available; there are no physical ties to them. Other routing protocols also use loopback interfaces as a preferred method for naming the router ID. With the IP address tied to a specific physical interface, when the physical interface goes down, the IP address becoming unavailable, causing unexpected issues with WCCP groups.
Step 1
interface Loopback0ip address 13.1.15.3 255.255.255.255WCCP service 61 and 62 direct the router to re-route traffic from the interface to the WCCP group. Service 61 redirects ingress traffic and service 62 redirects egress traffic. Both service 61 and 62 are needed to complete redirect bi-directional traffic flow. WCCP is an open standard. Other equipment that implements the WCCP protocol can participate in the WCCP group. Passwords should be assigned to WCCP groups to prevent rogue traffic interception and redirection.
Step 2
ip wccp 61 password ciscoip wccp 62 password ciscoStep 3
interface Vlan301description WAE vlan - 301ip address 13.1.12.1 255.255.255.0Step 4
ip wccp redirect exclude inStep 5
ip flow egressStep 6
interface FastEthernet1/0description WAE portswitchport access vlan 301Step 7
interface Vlan300description client vlan - 300ip address 13.1.11.1 255.255.255.0Step 8
ip wccp 61 redirect inip wccp 62 redirect outStep 9
ip flow egressStep 10
ntp server 13.1.15.2Step 11
ip flow-export source Loopback0ip flow-export version 5ip flow-export destination 10.1.70.10 9995
WAE-612-K9, WAE-7326-K9
Step 1
device mode application-acceleratorStep 2
interface GigabitEthernet 1/0ip address 13.1.12.2 255.255.255.0Step 3
ip default-gateway 13.1.12.1Step 4
primary-interface GigabitEthernet 1/0Step 5
wccp version 2Step 6
wccp router-list 1 10.1.20.1Step 7
wccp tcp-promiscuous router-list-num 1 password ciscoStep 8
ntp server 13.1.15.2Step 9
central-manager address 13.1.40.8Step 10
cms enableStep 11
flow monitor tcpstat-v1 host 10.1.70.11flow monitor tcpstat-v1 enable
Configuration and Menus
See Appendix B—Cisco WAE Configurations.
Troubleshooting Configuration
Cisco WAE Commands
These show commands can help troubleshoot issues with the configuration:
•
•
•
•
•
The following is sample output from sh tfo connection summary. F,F,F,F means the connection is fully optimized with DRE/LZ and TCP Optimization.
Optimized Connection ListPolicy summary order: Our's, Peer's, Negotiated, AppliedF: Full optimization, D: DRE only, L: LZ Compression, T: TCP OptimizationLocal-IP:Port Remote-IP:Port ConId PeerId Policy13.1.11.3:49520 13.1.40.41:80 43357 00:14:5e:ac:3a:47 F,F,F,F13.1.11.2:9146 13.1.40.41:80 55532 00:14:5e:ac:3a:47 F,F,F,FPass-Through ConnectionsLocal-IP:Port Remote-IP:Port Conn Type13.1.42.54:445 13.1.11.2:5401 PT In ProgressRouter Commands
•
•
•
•
Testing and Results
The tests were simulations of a series of tasks performed by Siebel users during a typical working day. The were broken down into three categories.
•
•
•
In this testing scenario, the PC running the HP Mercury LoadRunner testing application was attached to the store Cisco ISR router which is connected back to the data center Cisco WAAS edge router via T1 to simulate a WAN connection using multiple speeds. The testing was performed at full T1 speed with 100 ms delay to simulate a typical intra-continental circuit and also at 512 Kbps speed with 200 ms delay to simulate a typical inter-continental circuit.
Figure 10 Testing Scenario
This network scenario included Cisco WAAS application acceleration devices at the store and the data center. At the store a Cisco WAE-612 was connected on a separate VLAN. WCCP was enabled on the router to redirect client and WAN traffic to the Cisco WAAS device. At the data center two Cisco WAAS devices were installed. The first was the Cisco WAAS Central Manager Cisco running on a Cisco WAE-612. This is connected to a VLAN to the MSFC on the Core switch.
Figure 11 Document Upload—With and Without Cisco WAAS T1 Link
Document Attachments
Document attachments in the Siebel application is for storing of data such as quotes, fax, spreadsheet, and other related information relevant to a specific opportunity or contact. A download and upload test was performed on the T1 link. Document upload is significantly faster with Cisco WAAS (see Figure 11). This is uploading attachments via http to the Siebel application. Blue/green bars are Cisco WAAS on. The initial Cisco WAAS pass is 5X faster than without Cisco WAAS; subsequent uploads are almost instantaneous at LAN-like speeds. TFO and DRE cache are accelerating the transfer.
Figure 12 Document Download—With and Without Cisco WAAS T1 Link
Document download is also faster with Cisco WAAS (see Figure 12). Siebel compresses the file before storing on the Siebel File System. The actual file download is 775 KB. Local application cache increases native file download speeds. A second send/receive with Cisco WAAS is almost three times as fast. Blue/green bars are Cisco WAAS on.
Site Navigation
Table 9 shows all data points are nearly double with Cisco WAAS enabled on a 512kbs circuit (doubling the number of transactions and throughput). The Siebel application is almost unusable with 512kbs circuit with 40 concurrent users until Cisco WAAS is enabled due to high latency. Login times (not shown) were reduced from 167 seconds down to 12 seconds. This example clearly demonstrates that using Cisco WAAS can bring immediate relief to WAN bottlenecks. Instead of increasing WAN capacity, which is a monthly recurring cost, adding Cisco WAAS can yield the same result without additional WAN capacity and recurring costs.
Figure 13 T1 Circuit with 100 msec. Delay
Figure 13 shows T1 circuit with HP Mercury LoadRunner response time for each of the actions. The average response time is reduced by 45%. The login process is three times as fast with WAAS and two times as fast for these other site navigation transactions.
Summary and Conclusions
The Cisco Lean Retail Oracle Siebel design provides best practices and implementation guidance that optimizes Siebel application availability, performance, and security while lowering application ownership costs.
All of the WAAS test results indicate significant round trip time and bandwidth savings performance improvements. Average site navigation application response time is reduced by 45%. Document attachment upload and download times are two to ten times faster. In the use case of a 512kbs line, application response time is initially well over 100 seconds for logins to the application. With WAAS, login time is reduced to an average of 12 seconds.
Cisco WAAS can drastically reduce bandwidth consumption and application response time.
The Cisco Application Networking Services, featuring the Cisco Application Control Engine and Wide Area Application Services product families, provide data center, retail store, and remote end user application optimization services.
Appendix A—Cisco ACE Configuration
Admin Context
login timeout 0hostname EDAL-AGG1-ACEboot system image:c6ace-t1k9-mz.3.0.0_A1_5a.bin! define Cisco ACE resource for each server farmresource-class WebFarmlimit-resource all minimum 20.00 maximum unlimitedlimit-resource sticky minimum 40.00 maximum equal-to-minresource-class siebel-resourcelimit-resource all minimum 20.00 maximum unlimitedlimit-resource sticky minimum 40.00 maximum equal-to-minaccess-list ALLOW-TRAFFIC line 8 extended permit ip any anyaccess-list ALLOW-TRAFFIC line 9 extended permit icmp any anyclass-map type management match-any REMOTE-MGMT2 match protocol ssh any3 match protocol telnet any4 match protocol icmp any5 match protocol http any6 match protocol https anypolicy-map type management first-match REMOTE-ACCESSclass REMOTE-MGMTpermitinterface vlan 82ip address 172.28.210.14 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICservice-policy input REMOTE-ACCESSno shutdownft interface vlan 43ip address 192.168.100.1 255.255.255.0peer ip address 192.168.100.2 255.255.255.0no shutdownft peer 1heartbeat interval 200heartbeat count 20ft-interface vlan 43ip route 0.0.0.0 0.0.0.0 172.28.210.1!define contexts within the Cisco ACEcontext Siebelallocate-interface vlan 42allocate-interface vlan 100member siebel-resourcecontext WebFarmallocate-interface vlan 41allocate-interface vlan 101member WebFarmft group 1peer 1priority 120associate-context Siebelinserviceft group 2peer 1priority 120associate-context WebFarminserviceusername admin password 5 $1$faXJEFBj$TJR1Nx7sLPTi5BZ97v08c/ role Admin domaindefault-domainusername www password 5 $1$UZIiwUk7$QMVYN1JASaycabrHkhGcS/ role Admin domain default-domainWebFarm Context
!information for generating certificatecrypto csr-params testparmscountry USstate Californialocality San Joseorganization-name ESEorganization-unit ESEcommon-name www.testsiebel.comserial-number cisco123access-list ALLOW-TRAFFIC line 8 extended permit ip any anyaccess-list ALLOW-TRAFFIC line 9 extended permit icmp any anyprobe http http-probeinterval 30expect status 200 200!configure TCP reuseparameter-map type http HTTP_PARAMETERSserver-conn reusecase-insensitiveparameter-map type ssl SSL_PARAMETERScipher RSA_WITH_RC4_128_MD5version TLS1rserver host websrvr1description Siebel web serverip address 13.1.41.57inservicerserver host websrvr2description Siebel web serverip address 13.1.41.58inservicerserver host websrvr3description Siebel web serverip address 13.1.41.59inservice! configure SSL proxy serverssl-proxy service SIEBELWEB_SSLkey siebelweb.keycert siebelweb.cerserverfarm host WEBFARMprobe http-proberserver websrvr1 80inservicerserver websrvr2 80inservicerserver websrvr3 80inservice!define cookie sticky groupsticky http-cookie _sn sn_cookiereplicate stickyserverfarm WEBFARM! match SSL server ip/portclass-map match-all L4_SSL_VIP_CLASS2 match virtual-address 13.1.101.41 tcp eq httpsclass-map match-all L4_WEB_VIP_CLASS2 match virtual-address 13.1.101.41 tcp eq wwwclass-map type http loadbalance match-any L7_WEB2 match http url .*.class-map type management match-any REMOTE-MGMT2 match protocol ssh any3 match protocol telnet any4 match protocol icmp any5 match protocol http any6 match protocol https anypolicy-map type management first-match REMOTE-ACCESSclass REMOTE-MGMTpermitpolicy-map type loadbalance first-match L7-SSL-MATCHclass L7_WEBsticky-serverfarm sn_cookiepolicy-map type loadbalance first-match L7-WEB-MATCHclass L7_WEBsticky-serverfarm sn_cookie!matching SSL and HTTPS trafficpolicy-map multi-match L4-WEB-VIPclass L4_WEB_VIP_CLASSloadbalance vip inserviceloadbalance policy L7-WEB-MATCHloadbalance vip icmp-replyloadbalance vip advertise activeclass L4_SSL_VIP_CLASSloadbalance vip inserviceloadbalance policy L7-SSL-MATCHloadbalance vip icmp-replyloadbalance vip advertise activessl-proxy server SIEBELWEB_SSLinterface vlan 41description web farm vlanip address 13.1.41.2 255.255.255.0alias 13.1.41.1 255.255.255.0peer ip address 13.1.41.3 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICaccess-group output ALLOW-TRAFFICservice-policy input REMOTE-ACCESSno shutdowninterface vlan 101description ACE WEBFARM client vlanip address 13.1.101.14 255.255.255.0alias 13.1.101.13 255.255.255.0peer ip address 13.1.101.15 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICaccess-group output ALLOW-TRAFFICservice-policy input REMOTE-ACCESSservice-policy input L4-WEB-VIPno shutdownip route 0.0.0.0 0.0.0.0 13.1.101.1Siebel Application Farm (AOM) Context
access-list ALLOW-TRAFFIC line 8 extended permit ip any anyaccess-list ALLOW-TRAFFIC line 9 extended permit icmp any anyprobe http scbroker-probeport 2321interval 30passdetect interval 10passdetect count 1request method get url /SBA_80/scbrokerexpect status 100 200parameter-map type connection TCP_PARAMETERset timeout inactivity 86400rserver host appsrvr1description Siebel application serverip address 13.1.42.54inservicerserver host appsrvr2description Siebel application serverip address 13.1.42.55inservicerserver host appsrvr3description Siebel application serverip address 13.1.42.56inservice!define server farm for each application (AOM)serverfarm host APPS1FARMprobe scbroker-proberserver appsrvr1 2321inserviceserverfarm host APPS2FARMprobe scbroker-proberserver appsrvr2 2321inserviceserverfarm host APPS3FARMrserver appsrvr3 2321inserviceserverfarm host SALESCEOBJMGR_FARMprobe scbroker-proberserver appsrvr2 2321inservicerserver appsrvr3 2321inserviceserverfarm host SALESCEOBJMGR_FARM_RRrserver appsrvr2 2321inservicerserver appsrvr3 2321inserviceserverfarm host SCCOBJMGR_FARMprobe scbroker-proberserver appsrvr1 2321inservicerserver appsrvr2 2321inservicerserver appsrvr3 2321inserviceserverfarm host SCCOBJMGR_FARM_RRprobe scbroker-proberserver appsrvr1 2321inservicerserver appsrvr2 2321inservicerserver appsrvr3 2321inservice!define L7 rules for each application component (AOM), this include individual serversclass-map match-all L4_APPS_VIP_CLASS-23212 match virtual-address 13.1.40.42 tcp eq 2321class-map type http loadbalance match-any L7_APPSERVER_1_CLASS2 match http url .*/!9\. method POSTclass-map type http loadbalance match-any L7_APPSERVER_2_CLASS2 match http url .*/!d\. method POSTclass-map type http loadbalance match-any L7_APPSERVER_3_CLASS2 match http url .*/!b\. method POSTclass-map type http loadbalance match-any L7_SALESCEOBJMGR_CLASS2 match http url .*/sba_80/sseobjmgr_enu method POSTclass-map type http loadbalance match-any L7_SALESCEOBJMGR_RR_CLASS2 match http url .*/sba_80/sseobjmgr_enu/rr method POSTclass-map type http loadbalance match-any L7_SCCOBJMGR_CLASS2 match http url .*/sba_80/sccobjmgr_enu method POSTclass-map type http loadbalance match-any L7_SCCOBJMGR_RR_CLASS2 match http url .*/sba_80/sccobjmgr_enu/rr method POSTclass-map type management match-any REMOTE-MGMT2 match protocol ssh any3 match protocol telnet any4 match protocol icmp any5 match protocol http any6 match protocol https anypolicy-map type management first-match REMOTE-ACCESSclass REMOTE-MGMTpermit! matching L7 rules with server farmspolicy-map type loadbalance first-match L7-APPS-MATCHclass L7_SCCOBJMGR_CLASSserverfarm SCCOBJMGR_FARMclass L7_APPSERVER_1_CLASSserverfarm APPS1FARMclass L7_APPSERVER_2_CLASSserverfarm APPS2FARMclass L7_APPSERVER_3_CLASSserverfarm APPS3FARMclass L7_SALESCEOBJMGR_CLASSserverfarm SALESCEOBJMGR_FARMclass L7_SCCOBJMGR_RR_CLASSserverfarm SCCOBJMGR_FARM_RRclass L7_SALESCEOBJMGR_RR_CLASSserverfarm SALESCEOBJMGR_FARM_RRpolicy-map multi-match L4-APPS-VIPclass L4_APPS_VIP_CLASS-2321loadbalance vip inserviceloadbalance policy L7-APPS-MATCHloadbalance vip icmp-replyloadbalance vip advertise activeconnection advanced-options TCP_PARAMETERinterface vlan 42description application farm vlanip address 13.1.42.2 255.255.255.0alias 13.1.42.1 255.255.255.0peer ip address 13.1.42.3 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICservice-policy input REMOTE-ACCESSno shutdowninterface vlan 100description ACE AOM client vlanip address 13.1.40.11 255.255.255.0alias 13.1.40.10 255.255.255.0peer ip address 13.1.40.12 255.255.255.0no icmp-guardaccess-group input ALLOW-TRAFFICservice-policy input REMOTE-ACCESSservice-policy input L4-APPS-VIPno shutdownip route 0.0.0.0 0.0.0.0 13.1.40.1Appendix B—Cisco WAE Configurations
Store Cisco WAE Configuration
! WAAS version 4.0.13 (build b12 Aug 9 2007)device mode application-acceleratorhostname BRANCH-WAE-EDAL! ! define the primary interface for the Cisco WAE. Primary interface is the main interface Cisco WAE uses for intercepting trafficprimary-interface GigabitEthernet 1/0!interface GigabitEthernet 1/0ip address 13.1.12.2 255.255.255.0exitinterface GigabitEthernet 2/0shutdownexitip default-gateway 13.1.12.1!no auto-register enable!! ip path-mtu-discovery is disabled in Cisco WAAS by default!ntp server 13.1.15.2!wccp router-list 1 13.1.12.1wccp tcp-promiscuous router-list-num 1 password ****wccp version 2!username admin password 1 bVmDmMMmZAPjYusername admin privilege 15username admin print-admin-password 1 29D5C31BFF3D8D25AAD3B435B51404EE 7D891AB402CAF2E89CCDD33ED54333AC!authentication login local enable primaryauthentication configuration local enable primary!central-manager address 13.1.40.8cms enable! configure the NetFlow statistics collectionflow monitor tcpstat-v1 host 10.1.70.11flow monitor tcpstat-v1 enable!tfo tcp optimized-send-buffer 2048tfo tcp optimized-receive-buffer 2048!no adapter epm enable!policy-engine applicationname Authenticationname Backup... snip ....Data Center Cisco WAE Configuration
! WAAS version 4.0.13 (build b12 Aug 9 2007)device mode application-accelerator!hostname DC-WAE-01!ip domain-name cisco! define the primary interface for the Cisco WAE. Primary interface is the main interface Cisco WAE uses for intercepting trafficprimary-interface GigabitEthernet 1/0!interface GigabitEthernet 1/0ip address 13.1.13.5 255.255.255.0exitinterface GigabitEthernet 2/0shutdownexit!ip default-gateway 13.1.13.1!no auto-register enable!! ip path-mtu-discovery is disabled in WAAS by default! designate time server for ntp protocolntp server 13.1.15.2!wccp router-list 1 13.1.13.1wccp tcp-promiscuous router-list-num 1 password ****wccp version 2!username admin password 1 bVmDmMMmZAPjYusername admin privilege 15username admin print-admin-password 1 29D5C31BFF3D8D25AAD3B435B51404EE 7D891AB40!authentication login local enable primaryauthentication configuration local enable primary!central-manager address 13.1.40.8cms enable! configure the NetFlow statistics collectionflow monitor tcpstat-v1 host 10.1.70.11flow monitor tcpstat-v1 enable!tfo tcp optimized-send-buffer 8192tfo tcp original-send-buffer 8192tfo tcp optimized-receive-buffer 8192tfo tcp original-receive-buffer 8192!!define traffic acelerationpolicy-engine applicationname Authenticationname Backup...snip...Appendix C—Cisco ACE Appliance Configuration and Test Results
Figure 14 Cisco ACE Appliance Configuration
Figure 15 Cisco ACE Appliance Logical Configuration
Enterprise Store
The enterprise store design shows the Cisco WAE Appliance connected to the local store router, typically a Cisco Integrated Services Router (ISR). The design provides scalability and availability as compared to installing a Cisco WAAS Network Module within a Cisco ISR as the Cisco ISR must share its resources.
HP Mercury LoadRunner, running on a personal computer in the store, simulates users that would perform certain routine tasks in the application.
The traffic is redirected to the Cisco WAE through the Web Cache Communications Protocol (WCCP) from the store router. The Cisco WAE performs the following functions:
•
•
WAN Simulation
The WAN simulator provide simulations of standard T1. The following simulation was used:
•
–
–
–
Data Center
For this design, the Cisco ACE Appliance is targeted for a small-to-medium data center (DC). The DC follows the design guidelines found in the Data Center Infrastructure Design Guide found at: http://www.cisco.com/go/srnd.
The design consists of a DC WAN router, a collapsed core/aggregation, access, and the server farm (where the application resides). In this appendix, the focus is on the DC WAN router, aggregation, and the server farm. The core provides routing to and from the DC WAN router and the aggregation. The access layer provides Layer 2 connectivity for the server farms to the aggregation. For larger deployments, one should consider a separate core and aggregation layer, or a one-arm deployment where the Cisco ACE Appliance connects to a Cisco 6500. For more information, refer to:
http://www.cisco.com/en/US/partner/products/ps7027/tsd_products_support_series_home.html
The DC WAN router performs the same function as the store WAN router by redirecting traffic to the DC WAE. The DC WAE performs the following:
•
•
Within a Cisco WAAS topology, each Cisco WAE runs a process called central management system (CMS). The CMS process provides SSL-encrypted bidirectional configuration synchronization of the Cisco WAAS Central Manager and the Cisco WAE devices. The CMS process is also used to exchange reporting information and statistics at a configurable interval. When the administrator applies configuration or policy changes to a Cisco WAE device or a group of Cisco WAE devices (a device group), the Cisco WAAS Central Manager automatically propagates the changes to each of the managed Cisco WAE devices. Cisco WAE devices that are not available to receive the update receive the update the next time they become available.
Note
The aggregation segment contains the Cisco ACE Appliance. The Cisco ACE Appliance provides the following:
•
•
•
•
The Cisco ACE Appliance provides load balancing of the traffic bound to the server farm using one of the following methods:
•
•
•
•
•
•
•
Round Robin was used to provide load balancing for the Siebel Web and Application Servers. Round Robin sequentially alternates the connections among available servers.
Dual VIP, Single Context
The Siebel context was configured with two VIPs. The first VIP, 16.16.80.250, was for inbound traffic from the client network. This traffic was load balanced across the Siebel Web Servers on TCP port 80 traffic. The second VIP, 16.16.81.249, was for traffic from the Siebel Web Servers destined for the Siebel Application Servers on TCP port 2321. Figure 15 details the traffic flow for both VIPs.
ACE 4710 Configuration
Admin Context
interface gigabitEthernet 1/1 <-- Connection to Client-side networkdescription CLIENT-WANswitchport access vlan 80no shutdowninterface gigabitEthernet 1/2shutdowninterface gigabitEthernet 1/3 <-- Connection to Server-side networkdescription DC-LANswitchport trunk allowed vlan 81-82no shutdowninterface gigabitEthernet 1/4shutdownresource-class STICKYlimit-resource all minimum 0.00 maximum unlimitedlimit-resource sticky minimum 10.00 maximum unlimitedboot system image:c4710ace-mz.A1_7.0.5.binlogin timeout 0class-map type management match-any MGMT-TRAFFICdescription "allowed mgmt traffic to ACE"2 match protocol http any3 match protocol https any4 match protocol icmp any5 match protocol ssh any6 match protocol telnet any7 match protocol xml-https anypolicy-map type management first-match REMOTE-MGMTclass MGMT-TRAFFICpermitinterface vlan 80 <--Management Interfacedescription "ACE mgmt interface"ip address 16.16.80.2 255.255.255.0service-policy input REMOTE-MGMTno shutdownip route 0.0.0.0 0.0.0.0 16.16.80.1context Siebelallocate-interface vlan 80-82member STICKYusername admin password 5 $1$faXJEFBj$TJR1Nx7sLPTi5BZ97v08c/ role Admin domain default-domainusername www password 5 $1$faXJEFBj$TJR1Nx7sLPTi5BZ97v08c/ role Admin domain default-domainSiebel Context
access-list APP-TIER line 16 extended permit tcp host 16.16.81.23 eq 2321 host 16.16.81.249access-list APP-TIER line 24 extended permit tcp host 16.16.81.24 eq 2321 host 16.16.81.249access-list NON-RESTRICTIVE line 8 extended permit ip any anyaccess-list STRICT line 8 extended permit tcp any eq www host 16.16.70.250access-list STRICT line 16 extended permit tcp any eq https host 16.16.70.250probe icmp L3 <--Layer 3 Health Probeinterval 10passdetect interval 10probe http SP-HTTP <--Layer 7 Health Probedescription "Test HTTP request to Portal Page"interval 20passdetect interval 10request method get url /callcenter_enu/start.swe <--URL checked on Serversexpect status 200 200parameter-map type connection WANset tcp wan-optimization rtt 0set tcp ack-delay 60set tcp mss min 0 max 1450tcp-options selective-ack allowtcp-options timestamp allowtcp-options window-scale allowrserver host APP-1 <--Assignment of Siebel Application Serversdescription "Siebel Application Server"ip address 16.16.82.23inservicerserver host APP-2description "Siebel Application Server"ip address 16.16.82.24inservicerserver host SP-1 <--Assignment of Siebel Web Serversdescription "SIEBEL Web Server"ip address 16.16.81.21inservicerserver host SP-2description "SIEBEL Web Server"ip address 16.16.81.22inserviceserverfarm host APP-FARM-1 <--Assignment of Siebel App Serverfarmprobe L3rserver APP-1 2321inservicerserver APP-2 2321inserviceserverfarm host SIEBEL <--Assignment of Siebel Web Serverfarmprobe L3probe SP-HTTPrserver SP-1 80inservicerserver SP-2 80inservicesticky http-cookie ACE ACE-COOKIE <--Cookie Insertcookie insertserverfarm SIEBELclass-map match-any APP-VIP <--VIP for App Servers used by Web Servers for TCP port 2321 traffic3 match virtual-address 16.16.81.249 tcp eq 2321class-map type management match-any REMOTE-ACCESSdescription "Define Allowed Mgmt Traffic"2 match protocol http any3 match protocol https any4 match protocol telnet any5 match protocol ssh any6 match protocol xml-https any7 match protocol snmp any8 match protocol icmp anyclass-map match-any SP-VIP-HTTP <--VIP for Web Servers for Clients2 match virtual-address 16.16.80.250 tcp eq wwwpolicy-map type management first-match REMOTE-MGMTclass REMOTE-ACCESSpermitpolicy-map type loadbalance first-match APP-TIER-SLBclass class-defaultserverfarm APP-FARM-1policy-map type loadbalance first-match SIEBELclass class-default <--Load balance with Cookie Stickinesssticky-serverfarm ACE-COOKIEpolicy-map multi-match SIEBEL-LBclass SP-VIP-HTTPloadbalance vip inserviceloadbalance policy SIEBELloadbalance vip icmp-reply activeconnection advanced-options WANclass APP-VIPloadbalance vip inserviceloadbalance policy APP-TIER-SLBloadbalance vip icmp-reply activeinterface vlan 80description CLIENT-WANip address 16.16.80.3 255.255.255.0access-group input NON-RESTRICTIVEservice-policy input REMOTE-MGMTservice-policy input SIEBEL-LBno shutdowninterface vlan 81description DC-LANip address 16.16.81.1 255.255.255.0access-group input NON-RESTRICTIVEservice-policy input REMOTE-MGMTservice-policy input SIEBEL-LBno shutdowninterface vlan 82description DC-LAN-APP-TIERip address 16.16.82.1 255.255.255.0access-group input NON-RESTRICTIVEservice-policy input REMOTE-MGMTno shutdownip route 0.0.0.0 0.0.0.0 16.16.80.1Test Results
The Siebel call center application was loaded with 40 users. The users ramped up over the five initial minutes and then they started performing four types of site navigation activities that a normal user in a Siebel environment would routinely perform.
The ACE appliance was used to load balance the Siebel application and Web servers as shown in Figure 14. WAAS was used to optimize Web traffic across the WAN connection to the Store. As shown in Figure 16, the use of WAAS in an ACE appliance environment reduced the response time for Siebel Web traffic by up to 20%.
Figure 16 Response Time
Appendix D—Network Management
This section focuses on the network management system (NMS) that was used to monitor and provide results indicating the benefits of the Cisco WAAS optimization. The NMS tool used was NetQoS SuperAgent with NetQoS Collector and Reporter. NetQoS Collector gathers the pre-optimized traffic and reports the data to the NetQoS SuperAgent. The NetQoS SuperAgent provides details on the protocols and applications traversing the network(s), including:
•
•
•
•
•
•
•
This information provides the baseline of the application under test with valid overall transaction times (end user experience).
NetQoS Reporter gathers the optimized traffic and reports the data to NetQoS Super Agent. NetQoS Super Agent uses the data from the NetQoS Collector (un-optimized) and compares it to the optimized traffic, indicating the benefits of optimization using the Cisco WAAS as shown in the generic samples in Figure 17, Figure 18, and Figure 19.
Figure 17 Benefit of Optimization Using the Cisco WAAS—Application Response Time
Figure 18 Benefit of Optimization Using the Cisco WAAS—Application Data Rate
Figure 19 Benefit of Optimization Using the Cisco WAAS—Link Utilization
NetQoS devices passively listen in by using the rspan feature of Cisco routers and switches. They do not poll servers and hence do not add to the server load. For more information about this tool, see:
http://www.netqos.com/CiscoWAASSolutions/Cisco_WAAS_overview.html
Appendix E—Cisco Advanced Services
Cisco Services Help Accelerate and Optimize ANS Deployments
Application deployments are complex projects. Cisco Services can help mitigate the risk of making changes to the environment and accelerate deployment of Cisco ANS solutions. Our product and technology expertise is constantly enhanced by hands-on experience with real-life networks and broad exposure to the latest technology and implementations. Cisco uses leading practices to help our customers define their IT and business requirements and help them deliver fast, secure and highly available application access in a scalable environment.
•
•
•
•
•
Cisco ANS Services:
http://www.cisco.com/en/US/products/ps6892/serv_group_home.html
http://www.cisco.com/en/US/products/ps6894/serv_group_home.html
Cisco Validated Design
The Cisco Validated Design Program consists of systems and solutions designed, tested, and documented to facilitate faster, more reliable, and more predictable customer deployments. For more information visit:
http://www.cisco.com/go/validateddesigns
ALL DESIGNS, SPECIFICATIONS, STATEMENTS, INFORMATION, AND RECOMMENDATIONS (COLLECTIVELY, "DESIGNS") IN THIS MANUAL ARE PRESENTED "AS IS," WITH ALL FAULTS. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THE DESIGNS, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS. THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF CISCO, ITS SUPPLIERS OR PARTNERS. USERS SHOULD CONSULT THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS. RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY CISCO.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0807R)
1 Gartner: Server consolidation can save money 12/2005.
Feedback