Configuring the Brocade ServerIron to Enable Peak Performance of Siemens ComAssistant



Similar documents
Transparent Cache Switching Using Brocade ServerIron and Blue Coat ProxySG

Configuring Highly Available OracleAS Infrastructure with Brocade ServerIron Application Delivery Controllers

CAMPUS NETWORK Enhancing the Performance of Microsoft Office SharePoint Server Using Brocade ServerIron and Blue Coat ProxySG

DATA CENTER. Best Practices for High Availability Deployment for the Brocade ADX Switch

WHITE PAPER MICROSOFT LIVE COMMUNICATIONS SERVER 2005 LOAD BALANCING WITH FOUNDRY NETWORKS SERVERIRON PLATFORM

Deploying SAP NetWeaver Infrastructure with Foundry Networks ServerIron Deployment Guide

CLE202 Introduction to ServerIron ADX Application Switching and Load Balancing

Solution Guide: Load Balancing with the Brocade ServerIron Platform

Deploying the Brocade ServerIron ADX with Microsoft Exchange Server 2010

ServerIron TrafficWorks Firewall Load Balancing Guide

APPLICATION NOTES High-Availability Load Balancing with the Brocade ServerIron ADX and McAfee Firewall Enterprise (Sidewinder)

Server Iron Hands-on Training

APPLICATION NOTES Seamless Integration of LAN and WLAN through Brocade mobility products and

Brocade Certified Layer 4-7 Professional Version: Demo. Page <<1/8>>

Deployment Guide Oracle Siebel CRM

Deploying Brocade ServerIron ADX to Increase Availability, Scalability, and Security of Microsoft Lync Server 2010 Infrastructure

Deployment Guide AX Series with Active Directory Federation Services 2.0 and Office 365

Deployment Guide AX Series with Citrix XenApp 6.5

QUICK START GUIDE. Cisco C170 Security Appliance

Deployment Guide. AX Series for Microsoft Lync Server 2010

Deployment Guide Microsoft IIS 7.0

Load Balancing. Outlook Web Access. Web Mail Using Equalizer

QUICK START GUIDE. Cisco S170 Web Security Appliance. Web Security Appliance

login timeout 30 access list ALL line 20 extended permit ip any any port 9053 interval 15 passdetect interval 30

Cisco S380 and Cisco S680 Web Security Appliance

Introduction to ServerIron ADX Application Switching and Load Balancing. Module 5: Server Load Balancing (SLB) Revision 0310

DEPLOYMENT GUIDE CONFIGURING THE BIG-IP LTM SYSTEM WITH FIREPASS CONTROLLERS FOR LOAD BALANCING AND SSL OFFLOAD

SAML 2.0 SSO Deployment with Okta

QUICK START GUIDE Cisco M380 and Cisco M680 Content Security Management Appliance

Exam Name: Foundry Networks Certified Layer4-7 Professional Exam Type: Foundry Exam Code: FN0-240 Total Questions: 267

Advanced SLB High Availability and Stateless SLB

Connect the Host to attach to Fast Ethernet switch port Fa0/2. Configure the host as shown in the topology diagram above.

High Availability. PAN-OS Administrator s Guide. Version 7.0

Deployment Guide AX Series for Palo Alto Networks SSL Intercept and Firewall Load Balancing

Brocade SIP-Intelligent Application Switching for IP Communication Services

Deployment Guide MobileIron Sentry

Configuring SSL VPN on the Cisco ISA500 Security Appliance

Deployment Guide AX Series for Palo Alto Networks Firewall Load Balancing

F-SECURE MESSAGING SECURITY GATEWAY

Deploying the BIG-IP System with Oracle E-Business Suite 11i

Lab 3.5.1: Basic VLAN Configuration (Instructor Version)

eprism Security Suite

High Availability. Palo Alto Networks. PAN-OS Administrator s Guide Version 6.0. Copyright Palo Alto Networks

Multi-Chassis Trunking for Resilient and High-Performance Network Architectures

How to configure MAC authentication on a ProCurve switch

Apache CloudStack 4.x (incubating) Network Setup: excerpt from Installation Guide. Revised February 28, :32 pm Pacific

Skills Assessment Student Training Exam

Configuring VIP and Virtual IP Interface Redundancy

Smart Tips. Enabling WAN Load Balancing. Key Features. Network Diagram. Overview. Featured Products. WAN Failover. Enabling WAN Load Balancing Page 1

Deployment Guide Microsoft Exchange 2013

Starting a Management Session

Guideline for setting up a functional VPN

Deploying the Barracuda Load Balancer with Office Communications Server 2007 R2. Office Communications Server Overview.

Comodo MyDLP Software Version 2.0. Installation Guide Guide Version Comodo Security Solutions 1255 Broad Street Clifton, NJ 07013

TotalCloud Phone System

Radware AppDirector and Juniper Networks Secure Access SSL VPN Solution Implementation Guide

Load Balancing Microsoft Sharepoint 2010 Load Balancing Microsoft Sharepoint Deployment Guide

Set Up Panorama. Palo Alto Networks. Panorama Administrator s Guide Version 6.0. Copyright Palo Alto Networks

Dominion KX II-101-V2

iboss Enterprise Deployment Guide iboss Web Filters

Installation of the On Site Server (OSS)

How to Configure Web Authentication on a ProCurve Switch

Solution Guide: Brocade Server Application Optimization for a Scalable Oracle Environment

Overview of WebMux Load Balancer and Live Communications Server 2005

Using the NetVanta 7100 Series

Thunder Series for SAP BusinessObjects (BOE)

LifeSize Video Communications Systems Administrator Guide

Configuring the Edgewater 4550 for use with the Bluestone Hosted PBX

Deploying F5 with Microsoft Active Directory Federation Services

CT5760 Controller and Catalyst 3850 Switch Configuration Example

DEPLOYMENT GUIDE. This document gives a brief overview of deployment preparation, installation and configuration of a Vectra X-series platform.

Trouble Shooting SiteManager to GateManager access

Introducing the BIG-IP and SharePoint Portal Server 2003 configuration

Exam : EE : F5 BIG-IP V9 Local traffic Management. Title. Ver :

VMware Identity Manager Connector Installation and Configuration

Savvius Insight Initial Configuration

F5 BIG-IP V9 Local Traffic Management EE Demo Version. ITCertKeys.com

Note: This case study utilizes Packet Tracer. Please see the Chapter 5 Packet Tracer file located in Supplemental Materials.

Command Line Interface User s Guide

F-Secure Messaging Security Gateway. Deployment Guide

Thunder ADC for Epic Systems

USING BROCADE ADX LOAD BALANCER WITH EMC ATMOS

PT Activity: Configure Cisco Routers for Syslog, NTP, and SSH Operations

Management Software. User s Guide AT-S84. For the AT-9000/24 Layer 2 Gigabit Ethernet Switch. Version Rev. B

BCLP in a Nutshell Study Guide for Exam Exam Preparation Materials

Resonate Central Dispatch

Load Balancing Trend Micro InterScan Web Gateway

emerge 50P emerge 5000P

Brocade and EMC Solution for Microsoft Hyper-V and SharePoint Clusters

December ServerIron ADX. Firewall Load Balancing Guide. Supporting Brocade ServerIron ADX version

CounterACT 7.0 Single CounterACT Appliance

Firewall Load Balancing

How to Configure the Cisco UC500 for use with Integra Telecom SIP Solutions

Lab Configure Basic AP Security through IOS CLI

Cisco Application Networking Manager Version 2.0

Managing Virtual Servers

SANGFOR SSL VPN. Quick Start Guide

Quick Start Guide. Sendio System Protection Appliance. Sendio 5.0

FortiOS Handbook - Load Balancing VERSION 5.2.2

3.1 RS-232/422/485 Pinout:PORT1-4(RJ-45) RJ-45 RS-232 RS-422 RS-485 PIN1 TXD PIN2 RXD PIN3 GND PIN4 PIN5 T PIN6 T PIN7 R+ PIN8 R-

Transcription:

Configuring the Brocade ServerIron to Enable Peak Performance of Siemens ComAssistant Using a Web-based user interface, Siemens OpenScape ComAssistant serves up a suite of PBX and call control features to support enterprise communications. This brief provides guidance for ServerIron configuration in ComAssistant deployments.

CONTENTS Introduction...3 Brocade ServerIron...3 Siemens OpenScape ComAssistant...3 Basic Terminology...4 Real Server...4 Virtual Server...4 Virtual Server Port...4 Real Server Port...4 Health Checks...4 Putting It All Together...4 The Basic Topology...5 The Load Balancer...5 Configuration Prerequisites...6 Building the Configuration...7 1. Configure Basic Network Connectivity and High Availability...8 Load Balancer #1...8 Load Balancer #2...9 2. Configure Global Parameters...10 3. Configure Real Servers and Real Server Ports...13 4. Configure Virtual Server and Virtual Server Ports with Bindings...15 5. Verify functionality...16 Completing the Configuration...18 For Load Balancer #1...18 For Load Balancer #2...21 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 2 of 24

INTRODUCTION Brocade ServerIron The Brocade ServerIron family of Application Delivery Controllers (ADCs) intelligently balance enduser traffic across server farms to provide high availability, acceleration, security, and scalability for business-critical IP, Web, and Voice over IP (VoIP) applications, ensuring a better end-user experience with IP-based applications. The Brocade ServerIron provides a total solution for server load balancing, application (Layer 7) switching, server farm and application security, SSL acceleration, compression, and multisite redundancy. It offers enterprisesn service providers, and e-commerce data centers, a highly resilient application switch in both stackable and high-port-density, chassis-based configurations to optimize application delivery while decreasing the Total Cost of Ownership (TCO). ServerIron switches are deployed in more than 3,000 of the world s most demanding customer networks, where they support business-critical applications, including financial trading, e-mail, DNS, VoIP, Web, CDN, e-commerce, and ERP. The ServerIron family offers the broadest portfolio of Layer 4 7 products and meets a range of needs in the enterprise, service provider, and content provider markets. Siemens OpenScape ComAssistant Modern enterprise communications solutions such as Siemens HiPath are becoming increasingly popular. Siemens OpenScape ComAssistant provides an easy way to enhance the user experience. ComAssistant is a desktop call control interface that provides feature access via a Web browser. Users can initiate and log incoming and outgoing calls, transfer calls, conference calls, and access many other OpenScape telephony features. Additionally, OpenScape ComAssistant offers: One-number-service Journal entries, a speed-dial list, and LDAP search functionality Hotkey functionality enables users to dial numbers directly from Microsoft Office applications Team members can view one another s availability and support each other by handling incoming communications LDAP integration of corporate directories and personal address lists Support for multiple business groups enables large corporations to treat in-house companies separately by providing separate directory access or managed service bill-back models Integrates into business productivity applications such as mysap Portal, IBM WebSphere, and IBM Sametime Support for up to 50,000 users The ComAssistant WebGUI is provided through a Web server and a single server cannot simultaneously support thousands of users. However, ServerIron can distribute the connection load across multiple Web servers, increasing the performance of the solution dramatically by intelligently sharing the load between multiple instances of ComAssistant. This document explains how to load balance multiple ComAssistant front-end servers using the Brocade ServerIron. For configuration information for Siemens ComAssistant, see the product documentation. Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 3 of 24

BASIC TERMINOLOGY Real Server One of the functions of an ServerIron ADC is traffic distribution. A real server is a node/host or a physical server/network device that receives traffic from the ServerIron ADC after a load balancing decision has taken place. The server is represented by the IP address to which the ADC directs traffic. In this document the term real server is used to describe the physical ComAssistant front-end Web servers that receive traffic after the load balancing decision at the ADC. Virtual Server A virtual server is a single ADC-owned IP address to which clients connect and from which they are forwarded by the ADC to one of many physical or real servers. A virtual server IP address is commonly referred to as a VIP (Virtual server IP). Virtual Server Port Virtual servers offer services to their clients, such as HTTP, DNS, and others. A virtual server port is a TCP or UDP port that is open for clients to talk to the VIP. The virtual server port for HTTP is usually TCP port 80, and for DNS is typically UDP port 53. This solution uses ports 8443, 7778, 7788, and 7780. Real Server Port The Brocade ADC receives traffic on one of its VIPs, and that traffic arrives via a virtual server port (that is, ). A load balancing decision is then made, and after the ADC has selected a real server, the traffic is forwarded to the TCP/UDP port of that real server. That port does not have to be it is possible to forward traffic to port 8080 of a real server even if the client is talking on of the VIP. The destination port of the real server is called the real server port. Health Checks The ADC needs to ensure back-end resources (the ComAssistant front-end servers) are available to receive forwarded traffic. Using health checks the ADC verifies that back-end resources are available. An HTTP health check is basically an HTTP request from the ADC to the real server port, on which the ADC waits to receive an HTTP reply from the HTTP service. The real server port is declared ACTIVE (available) when the real server sends an HTTP response indicating SUCCESS (so called HTTP 2xx OK). Putting It All Together Putting all these things together results in a basic load balancing configuration. The Brocade ADC presents virtual servers to the outside world, and then distributes traffic to its real servers. Clients access the virtual server via defined services (virtual server ports) and the traffic is forwarded to configured real server ports. The Brocade ADC runs health checks to maintain availability of its back end server resources. Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 4 of 24

THE BASIC TOPOLOGY Cluster-ID Back-end server PBX CAP HBR CA - MGMT CA Cluster-ID Port X Port Y Admin client (browser) Front-end servers with Web engines ADC 1 ADC 2 Users Port 8443 (SSL) or Port 7789 (HTTP) 1 50,000 Figure 1. The basic topology NOTE: The solution is set up with HTTPS access to the ComAssistant WebGUI only (via ). The HTTP port 7789 is not used, but if it were, it would be configured in the same way as is configured. The Load Balancer For this setup, a Brocade ServerIron 4G (non-ssl and without PREM license) is used and it has the following specifications: Dedicated management processor Dedicated traffic processor Dedicated acceleration ASIC 4 x Gigabit combo-ports (copper or fiber (via SFP)) Up to 1.5 Gigabits per second (Gbps) application level throughput Up to 5,000,000 concurrent sessions Up to 40,000 Layer 4 connections per second Up to 15,000 Layer 7connections per second Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 5 of 24

Configuration Prerequisites Before beginning the setup you need to record the following information: ComAssistant real server names ComAssistant real server ports (8443, 7778, 7788, and 7780) ComAssistant real server IP addresses Virtual Server IP address (VIP) Virtual Server ports (8443, 7778, 7788, and 7780) Content to use for health checks Table 1. Example of a setup with eight real servers Real Server Name Real Server IP Address Real Server Ports sg016101 192.168.100.101 8443,7778,7780,7788 sg016102 192.168.100.102 8443,7778,7780,7788 sg016103 192.168.100.103 8443,7778,7780,7788 sg016104 192.168.100.104 8443,7778,7780,7788 sg016105 192.168.100.105 8443,7778,7780,7788 sg016106 192.168.100.106 8443,7778,7780,7788 sg016107 192.168.100.107 8443,7778,7780,7788 sg016108 192.168.100.108 8443,7778,7780,7788 The health check for each of the real servers needs to ask for the URL: /tweb/public/req?ping&returntype=text via The reply to this request needs to contain the content : PortalGUI is alive which asserts that the front-end server is up and running. The virtual server IP should be 192.168.100.137 and the virtual server should offer the following virtual server ports: 8443,7778,7780, and 7788. ADC #1 will use IP address 192.168.100.135 ADC #2 will use IP address 192.168.100.136 The ADC default gateway is 192.168.100.134 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 6 of 24

The solution uses a single multi-link trunk only. Traffic from the client to the virtual server and traffic from the load balancer to the real servers crosses the same link, which requires source-nat to force the traffic from the real servers back to the load balancer. Otherwise the real servers would reply via the router, which would result in communication problems. The load balancer needs to see all replies to keep its session table entries up-to-date and to do the reverse address translations. The IP addresses which are getting used for source-nat are 192.168.100.138 and 192.168.100.139. Port #1 of the load balancer is the client facing port and port #2 is a special port used for synchronization between the load balancer pair. ADC 1 ADC 2 Physical IP: 192.168.100.135 Port 4 Physical IP: 192.168.100.136 Source NAT IPs : 192.168.100.138/139 Gateway: 192.168.100.134 VIRTUAL SERVER IP: 192.168.100.137 Source NAT IPs : 192.168.100.138/139 Gateway: 192.168.100.134 Sync VIRTUAL SERVER IP: 192.168.100.137 Port 1 Port 1 192.168.100.x / 2 Back-end subnet ComAssistant back-end server IP: 192.168.100.134 Intranet IN TRANET ComAssistant front-end servers IP addresses: 192.168.100.101-108 Default gateway s: 192.168.100.134 Various client subnets Users 1-50,000 Figure 2. Front-end and back-end servers, clients, and the load balancer BUILDING THE CONFIGURATION The following high-level tasks are required: 1. Configure basic network connectivity and High Availability (HA) 2. Configure global parameters 3. Configure real servers and real server ports 4. Configure a virtual server and virtual server ports with bindings 5. Verify functionality Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 7 of 24

1. Configure Basic Network Connectivity and High Availability The load balancers must be configured. Connect a laptop to load balancer #1 using a serial straight-through cable (an EIA/TIA DB-9 serial cable (M/F) is shipped with the device). Use the following terminal settings: Baud: 9600 bps Data bits: 8 Parity: None Stop bits: 1 Flow control: None The following prompt appears: ServerIron> Establish physical connectivity (ensure load balancer #2 is still powered off). Connect port #1 of both load balancers to the router/client facing the subnet. Load Balancer #1 Get the load balancer s MAC address and configure the IP address and default gateway using the Command-Line Interface (CLI). Verify IP connectivity using PING. Save the configuration. ServerIron 4G>ena No password has been assigned yet... ServerIron 4G#show chassis power supply 1 failed power supply 2 failed power supply 1 to 2 from left to right fan 1 ok fan 2 ok fan speed set to high Current temperature : 39.0 C degrees Warning level : 65 C degrees, shutdown level : 75 C degrees Boot Prom MAC: 0012.f288.4a41 ServerIron 4G#conf t ServerIron 4G(config)#ip address 192.168.100.135 255.255.255.0 ServerIron 4G(config)#ip default-gateway 192.168.100.134 ServerIron 4G(config)#exit ServerIron 4G#ping 192.168.100.134 Sending 1, 16-byte ICMP Echo to 192.168.100.134, timeout 5000 msec, TTL 64 Type Control-c to abort Reply from 192.168.100.134 : bytes=16 time=4ms TTL=255 Success rate is 100 percent (1/1), round-trip min/avg/max=4/4/4 ms. ServerIron4G#write memory.write startup-config in progress..write startup-config done. ServerIron 4G# Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 8 of 24

Create a special sync VLAN (here VLAN #99) using port 4, disable spanning tree globally, activate HA, (using the MAC address from above), and set the pointer to the router/client facing port: ServerIron 4G#conf t ServerIron 4G(config)#vlan 99 ServerIron 4G(config-vlan-99)#untagged eth 4 ServerIron 4G(config-vlan-99)#exit ServerIron 4G(config)#no spanning-tree ServerIron 4G(config)#server backup ethe 4 0012.f288.4a41 vlan-id 99 ServerIron 4G(config)#server router-ports ethernet 1 Configure source-nat IPs and enable source-nat, and save the configuration: (config)#server source-nat-ip 192.168.100.138 255.255.255.0 0.0.0.0 port-range 2 (config)#server source-nat-ip 192.168.100.139 255.255.255.0 0.0.0.0 port-range 2 (config)#server source-nat (config)#write memory.write startup-config in progress..write startup-config done. (config) Load Balancer #2 Power on load balancer #2. Its configuration is very similar to load balancer #1, however the physical IP is different and the port range is 1 instead of 2. The MAC address stays the same as well as the other parameters. Establish a serial connection to load balancer #2 and follow these configuration instructions: ServerIron 4G>ena No password has been assigned yet... ServerIron 4G#conf t ServerIron 4G(config)#ip address 192.168.100.136 255.255.255.0 ServerIron 4G(config)#ip default-gateway 192.168.100.134 ServerIron 4G(config)#exit ServerIron 4G#ping 192.168.100.134 Sending 1, 16-byte ICMP Echo to 192.168.100.134, timeout 5000 msec, TTL 64 Type Control-c to abort Reply from 192.168.100.134 : bytes=16 time=4ms TTL=255 Success rate is 100 percent (1/1), round-trip min/avg/max=4/4/4 ms. ServerIron4G#write memory.write startup-config in progress..write startup-config done. ServerIron 4G#conf t ServerIron 4G(config)#vlan 99 ServerIron 4G(config-vlan-99)#untagged eth 4 ServerIron 4G(config-vlan-99)#exit ServerIron 4G(config)#no spanning-tree ServerIron 4G(config)#server backup ethe 4 0012.f288.4a41 vlan-id 99 ServerIron 4G(config)#server router-ports ethernet 1 (config)#server source-nat-ip 192.168.100.138 255.255.255.0 0.0.0.0 port-range 1 (config)#server source-nat-ip 192.168.100.139 255.255.255.0 0.0.0.0 port-range 1 (config)#server source-nat (config)#write memory.write startup-config in progress..write startup-config done. (config) Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 9 of 24

Connect the load balancers using port #4. Ensure HA (High Availability) comes up between them using the command show server backup on BOTH load balancers: (config)#show server backup Server Backup port = 4 Backup group id = 0 Switch state = Standby SLB state = 0 Peer sync state = 0 SLB Partner MAC valid= 1 SLB Partner MAC = 0012.f27c.a580 SLB Partner VLAN ID = 99 SLB Partner port cnt = 64 SLB Backup preference = 0 minutes SLB Backup timer = 1000 milliseconds [ ] Routers ports = 1, Partner Router ports= 1 Server ports = 0, Partner Server ports= 0 The switch state of one of the ServerIrons should be Standby and the other Active. The SLB state of both ServerIrons should be 0. Both ServerIrons should show the MAC address of the partner behind SLB Partner MAC (check via show chassis ) at both ServerIrons. The VLAN ID used for HA is 99. 2. Configure Global Parameters Begin to configure some global parameters on load balancer #1. A few settings must be changed, and the most important are the port profiles for all real server ports being used. The port profiles define: Protocol type (UDP/TCP) Health check interval (health check every x seconds) and regularity of health checks Number of unsuccessful health checks before declaring a real server port is down Number of successful health checks before declaring a real server port is up Four virtual server/real server ports are used in this example: 8443, 7778, 7780,and 7788. Therefore a port profile needs to be defined for each of these ports. All traffic is TCP traffic The load balancer should check the server status every 10 seconds A real server port will be declared as down as soon as the health check goes wrong twice in a row; and the session timeout from the load balancer point of view should be 60 minutes Three successful health checks in a row will result in the real server being declared up again Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 10 of 24

Table 2. Health check settings server no-fast-bringup Ensures that health checks are successful up to Layer 7 before declaring a server as available no server use-simple-ssl-health-check SSL health checks are based on content as well and not only the SSL handshake server Profile for port 80 tcp 60 tcp keepalive 10 2 bringup-retries 3 Timeout of 60 minutes It is TCP and the health check is every 10 seconds 2 failed means that the server is down 3 successful health checks in a row to declare the server up The configuration instructions to do this for all virtual/real server ports are as follows: (config)#server no-fast-bringup (config)#no server use-simple-ssl-health-check (config)#server (config-port-8443)#tcp 60 (config-port-8443)#tcp keepalive 10 2 (config-port-8443)#bringup-retries 3 (config-port-8443)#server (config-port-7778)#tcp 60 (config-port-7778)#tcp keepalive 10 2 (config-port-7778)#bringup-retries 3 (config-)#server (config-port-7780)#tcp 60 (config-port-7780)#tcp keepalive 10 2 (config-port-7780)#bringup-retries 3 (config-port-7780)#server (config-port-7788)#tcp 60 (config-port-7788)#tcp keepalive 10 2 (config-port-7788)#bringup-retries 3 (config-port-7788)#exit (config)# You can also configure other global settings: Users with passwords Authentication using these users Host name for the load balancer Domain name for the load balancer SNTP server Syslog server Time zone Health check for the ComAssistant front-end Web servers Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 11 of 24

The examples above are covered here, but there are additional settings you might use. For more information, contact your Brocade Systems Engineer. Table 3. Global setting commands with explanations username XYZ password MYPASS Creates a new user with the username XYZ and password MYPASS aaa authentication web-server default local hostname NAME Log in via ssh and WebGui will use the local user DB Changes host name to NAME ip dns domain-name domain.com Changes domain to domain.com sntp server a.b.c.d Sets SNTP server to a.b.c.d logging q.w.e.r Sets syslog server to q.w.e.r clock timezone gmt GMT-08 clock summertime http match-list Alive GMT-08, summertime Content match rule with the name Alive default down Real server is down by default up simple "PortalGUI is alive" server port-policy HTTPS-HC protocol ssl protocol ssl url "GET /tweb/public/req?ping&returntype=t ext HTTP/1.1\r\nHost: 192.168.100.137\r\n\r\n" protocol ssl content-match Alive Real server is declared as up when the health check answer contains the string in double quotes A port-policy with the name HTTPS-HC is declared to use the SSL protocol and will send an HTTP request as specified Expected answer (see above) The health check will send the virtual server IP as host-header, and this is necessary so that it looks like it is coming from a request to the virtual server. NOTE: Be careful with the question mark (?) inside the URL string in the second-to-last (config-portpolicy-https-hc) statement. You need to escape it using a backslash as shown. (config)#username test password test123 (config)#aaa authentication web-server default local (config)#aaa authentication login default local (config)#hostname myhost (config)#ip dns domain-name domain.com (config)#sntp server 10.234.12.100 (config)#logging 10.234.12.100 (config)#clock timezone gmt GMT+01 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 12 of 24

(config)#clock summertime (config)#http match-list Alive (config-http-ml-alive)#default down (config-http-ml-alive)#up simple PortalGUI is alive (config-http-ml-alive)#server port-policy HTTPS-HC (config-port-policy-https-hc)#protocol ssl (config-port-policy-https-hc)#protocol ssl url GET /tweb/public/req\?ping&returntype=test HTTP/1.1\r\nHost: 192.168.100.137\r\n\r\n (config-port-policy-https-hc)#protocol ssl content-match Alive 3. Configure Real Servers and Real Server Ports Begin to create the real servers with the real server port at load balancer #1. They all look the same except for their IP addresses and the real server name. The real server IP addresses are 192.168.100.101 through 108. The ports needed are 8443, 7780, 7788, and 7778. Table 4. Creating real server ports server real sg016101 192.168.100.101 Creates a real server with the name sg016101 and the IP address 192.168.100.101 Real server will be used later and is getting a health check using the port policy with the name HTTPS-HC These three additional ports which will be used later These four ports are part of the same health check group, so the load balancer will take them all down as soon as one of them has a problem This needs to be repeated for all the real servers: (config)#server real sg016101 192.168.100.101 (config-rs-sg016101)# (config-rs-sg016101)# (config-rs-sg016101)# (config-rs-sg016101)# (config-rs-sg016101)# (config-rs-sg016101)# (config-rs-sg016101)#server real sg016102 192.168.100.102 (config-rs-sg016102)# (config-rs-sg016102)# (config-rs-sg016102)# (config-rs-sg016102)# (config-rs-sg016102)# (config-rs-sg016102)# (config-rs-sg016102)#server real sg016103 192.168.100.103 (config-rs-sg016103)# (config-rs-sg016103)# (config-rs-sg016103)# (config-rs-sg016103)# (config-rs-sg016103)# (config-real-sg016103)# Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 13 of 24

(config-real-sg016103#server real sg016104 192.168.100.104 (config-real-sg016104)# (config-real-sg016104)# (config-real-sg016104)# (config-real-sg016104)# (config-real-sg016104)# (config-real-sg016104)# (config-real-sg016104)#server real sg016105 192.168.100.105 (config-real-sg016105)# (config-rs-sg016105)# (config-rs-sg016105)# (config-rs-sg016105)# (config-rs-sg016105)# (config-rs-sg016105)# (config-rs-sg016105)#server real sg016106 192.168.100.106 (config-rs-sg016106)# (config-rs-sg016106)# (config-rs-sg016106)# (config-rs-sg016106)# (config-rs-sg016106)# (config-rs-sg016106)# (config-rs-sg016106)#server real sg016107 192.168.100.107 (config-rs-sg016107)# (config-rs-sg016107)# (config-rs-sg016107)# (config-rs-sg016107)# (config-rs-sg016107)# (config-rs-sg016107)# (config-rs-sg016107)#server real sg016108 192.168.100.108 (config-rs-sg016108)# (config-rs-sg016108)# (config-rs-sg016108)# (config-rs-sg016108)# (config-rs-sg016108)# (config-rs-sg016108)# (config-rs-sg016108)# exit (config)# Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 14 of 24

4. Configure Virtual Server and Virtual Server Ports with Bindings Begin by creating a virtual server with the IP address 192.168.100.137. The ports accessible from the client (virtual server ports) are 8443, 7780, 7788, and 7778. All ports need to be sticky, because ServerIron needs to remember the server assigned to a client during the first request so that subsequent requests will be sent to the same real server. This needs to happen independently from the port. Table 5. Creating Virtual Server Ports server virtual sg016137 192.168.100.137 sticky-age 60 sticky-age-multiplier 96 sticky sticky sticky sticky track-group 8843 7780 7788 7778 bind 8443 sg016101 8443 sg016102 8443 sg016103 8443 sg016104 8443 bind 8443 sg016105 8443 sg016106 8443 sg016107 8443 sg016108 8443 bind 7780 sg016101 7780 sg016102 7780 sg016103 7780 sg016104 7780 bind 7780 sg016105 7780 sg016106 7780 sg016107 7780 sg016108 7780 bind 7788 sg016101 7788 sg016102 7788 sg016103 7788 sg016104 7788 bind 7788 sg016105 7788 sg016106 7788 sg016107 7788 sg016108 7788 bind 7778 sg016101 7778 sg016102 7778 sg016103 7778 sg016104 7778 bind 7778 sg016105 7778 sg016106 7778 sg016107 7778 sg016108 7778 Creates a virtual server with the name sg016137 and the IP address 192.168.100.137 Clients need to stick to the server selected for them and this needs to be the case over a period of days, such as the weekend, in this example, 96 * 60 minutes = 4 days. Stickiness is important for all ports Stickiness across different ports Binds the real server ports together with the virtual server ports (config)#server virtual sg016137 192.168.100.137 (config-vs-sg016137)#sticky-age 60 (config-vs-sg016137)#sticky-age-multiplier 96 (config-vs-sg016137)# sticky (config-vs-sg016137)# sticky (config-vs-sg016137)# sticky (config-vs-sg016137)# sticky (config-vs-sg016137)#track-group 8843 7780 7788 7778 (config-vs-sg016137)#bind 8443 sg016101 8443 sg016102 8443 sg016103 8443 sg016104 8443 (config-vs-sg016137)#bind 8443 sg016105 8443 sg016106 8443 sg016107 8443 sg016108 8443 (config-vs-sg016137)#bind 7780 sg016101 7780 sg016102 7780 sg016103 7780 sg016104 7780 (config-vs-sg016137)#bind 7780 sg016105 7780 sg016106 7780 sg016107 7780 sg016108 7780 (config-vs-sg016137)#bind 7788 sg016101 7788 sg016102 7788 sg016103 7788 sg016104 7788 (config-vs-sg016137)#bind 7788 sg016105 7788 sg016106 7788 sg016107 7788 sg016108 7788 (config-vs-sg016137)#bind 7778 sg016101 7778 sg016102 7778 sg016103 7778 sg016104 7778 (config-vs-sg016137)#bind 7778 sg016105 7778 sg016106 7778 sg016107 7778 sg016108 7778 Now return to Step 2 and repeat Steps 2, 3 and 4 for load balancer #2. Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 15 of 24

5. Verify functionality Verify again that the master and backup status of the ServerIrons is correct, using the command show server backup at both ServerIrons. One ServerIron needs to be Active and the other Standby. The Server Backup Port should be 4 and the SLB Partner VLAN ID should be 99. The number of router ports and partner router ports should be 1, whereas the number of server ports and partner server ports should be 0. SLB-ServerIron 4G#show server backup Server Backup port = 4 Backup group id = 0 Switch state = Active SLB state = 0 Peer sync state = 0 SLB Partner MAC valid = 1 SLB Partner MAC = 0012.f27c.3f60 SLB Partner VLAN ID = 99 SLB Partner port cnt = 64 SLB Backup preference = 0 minutes [ ] Router ports = 1, Partner Router ports = 1 Server ports = 0, Partner Server ports = 0 Verify that all real servers are up and running by using the command show server bind at both ServerIrons. ServerIron 4G(config)#show server bind Bind info Virtual server: sg016137 Status: enabled IP: 192.168.100.137 8443 -------> sg016101: 192.168.100.101, 8443 (Active) sg016102: 192.168.100.102, 8443 (Active) sg016103: 192.168.100.103, 8443 (Active) sg016104: 192.168.100.104, 8443 (Active) sg016105: 192.168.100.105, 8443 (Active) sg016106: 192.168.100.106, 8443 (Active) sg016107: 192.168.100.107, 8443 (Active) sg016108: 192.168.100.108, 8443 (Active) 7780 -------> sg016101: 192.168.100.101, 7780 (Active) sg016102: 192.168.100.102, 7780 (Active) sg016103: 192.168.100.103, 7780 (Active) sg016104: 192.168.100.104, 7780 (Active) sg016105: 192.168.100.105, 7780 (Active) sg016106: 192.168.100.106, 7780 (Active) sg016107: 192.168.100.107, 7780 (Active) sg016108: 192.168.100.108, 7780 (Active) 7788 -------> sg016101: 192.168.100.101, 7788 (Active) sg016102: 192.168.100.102, 7788 (Active) sg016103: 192.168.100.103, 7788 (Active) sg016104: 192.168.100.104, 7788 (Active) sg016105: 192.168.100.105, 7788 (Active) sg016106: 192.168.100.106, 7788 (Active) sg016107: 192.168.100.107, 7788 (Active) sg016108: 192.168.100.108, 7788 (Active) Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 16 of 24

7778 -------> sg016101: 192.168.100.101, 7778 (Active) sg016102: 192.168.100.102, 7778 (Active) sg016103: 192.168.100.103, 7778 (Active) sg016104: 192.168.100.104, 7778 (Active) sg016105: 192.168.100.105, 7778 (Active) sg016106: 192.168.100.106, 7778 (Active) sg016107: 192.168.100.107, 7778 (Active) sg016108: 192.168.100.108, 7778 (Active) SLB-telnet@ServerIron 4G(config)# Check the virtual server statistics all counters should be 0 (no testing done so far): ServerIron 4G(config)#show server virtual Virtual Servers Info Name: sg016137 State: Enabled IP:192.168.100.137: 1 Pred: least-conn ACL-Id: 0 TotalConn: 0 VIP state: healthy Port State Sticky Concur Proxy DSR CurConn TotConn PeakConn ---- ----- ------ ------ ----- --- ------- ------- -------- default enabled NO NO NO NO 0 0 0 8443 enabled YES NO NO NO 0 0 0 7780 enabled YES NO NO NO 0 0 0 7788 enabled YES NO NO NO 0 0 0 7778 enabled YES NO NO NO 0 0 0 ServerIron 4G(config)# Establish connections to the ComAssistant WebGUI using some clients (connecting to 192.168.100.137:8443 ). Counters should begin to increase: ServerIron 4G(config)#show server virtual Virtual Servers Info Name: sg016137 State: Enabled IP:192.168.100.137: 1 Pred: least-conn ACL-Id: 0 TotalConn: 0 VIP state: healthy Port State Sticky Concur Proxy DSR CurConn TotConn PeakConn ---- ----- ------ ------ ----- --- ------- ------- -------- default enabled NO NO NO NO 0 0 0 8443 enabled YES NO NO NO 2 7 3 7780 enabled YES NO NO NO 0 0 0 7788 enabled YES NO NO NO 0 0 0 7778 enabled YES NO NO NO 0 0 0 ServerIron 4G(config)# Failover test: Get the output of show server backup at both ServerIrons. Unplug the cable connected to port 1 at the ServerIron showing Active. The active box should move to Standby status and the old Standby ServerIron to Active status. Ensure that it is still possible to connect to the virtual sever 192.168.100.137 using the virtual service. Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 17 of 24

COMPLETING THE CONFIGURATION For Load Balancer #1 Building configuration... Current configuration : 6093 bytes ver 10.2.01eTI2 server backup ethe 4 0012.f27c.0983 vlan-id 99 server no-fast-bringup no server use-simple-ssl-health-check server tcp 60 tcp keepalive 10 2 bringup-retries 3 server tcp 60 tcp keepalive 10 2 bringup-retries 3 server tcp 60 tcp keepalive 10 2 bringup-retries 3 server tcp 60 tcp keepalive 10 2 bringup-retries 3 server source-nat server source-nat-ip 192.168.100.138 255.255.255.0 0.0.0.0 port-range 2 server source-nat-ip 192.168.100.139 255.255.255.0 0.0.0.0 port-range 2 server router-ports ethernet 1 context default server port-policy HTTPS-HC protocol ssl protocol ssl url "GET /tweb/public/req?ping&returntype=text HTTP/1.1\r\nHost: 192.168.100.137\r\n\r\n" protocol ssl content-match Alive server real sg016101 192.168.100.101 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 18 of 24

server real sg016102 192.168.100.102 server real sg016103 192.168.100.103 server real sg016104 192.168.100.104 server real sg016105 192.168.100.105 server real sg016106 192.168.100.106 server real sg016107 192.168.100.107 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 19 of 24

server real sg016108 192.168.100.108 server virtual sg016137 192.168.100.137 sticky-age 60 sticky-age-multiplier 96 sticky sticky sticky sticky track-group 8443 7780 7788 7778 bind 8443 sg016101 8443 sg016102 8443 sg016103 8443 sg016104 8443 bind 8443 sg016105 8443 sg016106 8443 sg016107 8443 sg016108 8443 bind 7780 sg016101 7780 sg016102 7780 sg016103 7780 sg016104 7780 bind 7780 sg016105 7780 sg016106 7780 sg016107 7780 sg016108 7780 bind 7788 sg016101 7788 sg016102 7788 sg016103 7788 sg016104 7788 bind 7788 sg016105 7788 sg016106 7788 sg016107 7788 sg016108 7788 bind 7778 sg016101 7778 sg016102 7778 sg016103 7778 sg016104 7778 bind 7778 sg016105 7778 sg016106 7778 sg016107 7778 sg016108 7778 vlan 1 name DEFAULT-VLAN by port no spanning-tree vlan 99 by port untagged ethe 4 no spanning-tree http match-list Alive default down up simple "PortalGUI is alive" aaa authentication web-server default local aaa authentication login default local enable telnet password... no enable aaa console hostname myhost ip address 192.168.100.135 255.255.255.0 ip default-gateway 192.168.100.134 ip dns domain-name domain.com logging 10.234.12.100 telnet server username test password... clock summer-time clock timezone gmt GMT+01 sntp server 10.234.12.100 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 20 of 24

For Load Balancer #2 Building configuration... Current configuration : 6093 bytes ver 10.2.01eTI2 server backup ethe 4 0012.f27c.0983 vlan-id 99 server no-fast-bringup no server use-simple-ssl-health-check server tcp 60 tcp keepalive 10 2 bringup-retries 3 server tcp 60 tcp keepalive 10 2 bringup-retries 3 server tcp 60 tcp keepalive 10 2 bringup-retries 3 server tcp 60 tcp keepalive 10 2 bringup-retries 3 server source-nat server source-nat-ip 192.168.100.138 255.255.255.0 0.0.0.0 port-range 1 server source-nat-ip 192.168.100.139 255.255.255.0 0.0.0.0 port-range 1 server router-ports ethernet 1 context default server port-policy HTTPS-HC protocol ssl protocol ssl url "GET /tweb/public/req?ping&returntype=text HTTP/1.1\r\nHost: 192.168.100.137\r\n\r\n" protocol ssl content-match Alive server real sg016101 192.168.100.101 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 21 of 24

server real sg016102 192.168.100.102 server real sg016103 192.168.100.103 server real sg016104 192.168.100.104 server real sg016105 192.168.100.105 server real sg016106 192.168.100.106 server real sg016107 192.168.100.107 server real sg016108 192.168.100.108 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 22 of 24

server virtual sg016137 192.168.100.137 sticky-age 60 sticky-age-multiplier 96 sticky sticky sticky sticky track-group 8443 7780 7788 7778 bind 8443 sg016101 8443 sg016102 8443 sg016103 8443 sg016104 8443 bind 8443 sg016105 8443 sg016106 8443 sg016107 8443 sg016108 8443 bind 7780 sg016101 7780 sg016102 7780 sg016103 7780 sg016104 7780 bind 7780 sg016105 7780 sg016106 7780 sg016107 7780 sg016108 7780 bind 7788 sg016101 7788 sg016102 7788 sg016103 7788 sg016104 7788 bind 7788 sg016105 7788 sg016106 7788 sg016107 7788 sg016108 7788 bind 7778 sg016101 7778 sg016102 7778 sg016103 7778 sg016104 7778 bind 7778 sg016105 7778 sg016106 7778 sg016107 7778 sg016108 7778 vlan 1 name DEFAULT-VLAN by port no spanning-tree vlan 99 by port untagged ethe 4 no spanning-tree http match-list Alive default down up simple "PortalGUI is alive" aaa authentication web-server default local aaa authentication login default local enable telnet password... no enable aaa console hostname myhost ip address 192.168.100.136 255.255.255.0 ip default-gateway 192.168.100.134 ip dns domain-name domain.com logging 10.234.12.100 telnet server username test password... clock summer-time clock timezone gmt GMT+01 sntp server 10.234.12.100 Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 23 of 24

2009 Brocade Communications Systems, Inc. All Rights Reserved. 07/09 GA-SG-197-00 Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government. Configuring the Brocade ServerIron to Enable Peak Performance of the Siemens ComAssistant 24 of 24