Beruflich Dokumente
Kultur Dokumente
Document Version: 1.0 Document Status: Approved Document Release Date: June 2002
2002 by CMG Wireless Data Solutions All rights reserved. This document may not be copied in whole or in part without the
prior written consent of CMG Wireless Data Solutions. The information in this document is subject to change without notice and should not be construed as a commitment by CMG Wireless Data Solutions. CMG Wireless Data Solutions assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of such license. Products mentioned in this document are identified by the trademarks or service marks of their respective companies or organisations.
Table of Contents
Getting Started.................................................................................................. 14
2.1 2.2 2.3 2.4 2.5 2.6 Setup the passwords .............................................................Error! Bookmark not defined. Setup the Management port ................................................................................................ 14 Change the hostname.......................................................................................................... 15 The IOS................................................................................................................................ 15 Shutting Down the CSS ....................................................................................................... 15 Save the configuration ......................................................................................................... 15
Troubleshooting ............................................................................................... 22
4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 Troubleshoot the Content Service Switch 11052 ................................................................ 22 Show the interfaces ............................................................................................................. 23 Show the content rules for the onwer wds........................................................................... 23 Check the software version and license .............................................................................. 23 Check the time and date ...................................................................................................... 23 Show the configured Vlan .................................................................................................... 23 Check the service ................................................................................................................ 24 Show owner setting.............................................................................................................. 25 Check the group................................................................................................................... 25
iv
List of Figures
List of Tables
vii
Preface
Purpose
This manual guides you to make changes in the auto generated configuration file of the CSS 11052 used in the MMSC environment.
Audience
This manual is first of all intended for CMG personnel when installing and configuring the Cisco load balancer for the MMSC system.
Scope
This manual only describes the installation & configuration process of the Cisco CSS 11052.
Other related documents are: [Cisco CSS 11052] Content Service Switch Quick Configuration. Doc. Nr: 78-114260-01, Rel: Augustus 2000
Organisation
This document is organised in 4 chapters. The first chapter describes the load-balancing functionality. The second chapter will explain the setup Cisco Content Service Switch 11052. The third chapter will explain the configuration of the CSS switch. When there are troubles with the 11052 look to chapter 4, a few handsets are given to trouble shoot the CSS 11052.
Typographic conventions
In this document, the typographic conventions listed in Table P-1 are used.
ix
<courier>
[]
[ETSI 03.38]
Italic
% ls
# ls
$ \ (Unix) or (OpenVMS)
$ dir
% grep searchforthis \ data/*.dat $ search [.data]*.dat searchforthis If Ctrl-C does not work, use CtrlAlt-Del. Note that the system is usually...
1.1 Introduction
This document will guide you through the load-balancer configuration for the MMSC solution and explain the functions of each configuration element. Describing in detail all the features of this load-balancer configuration is beyond the scope of this document. More information about the load balancer is available on the Cisco Internet site. The following configuration will define a fail-over load-balancing environment. There will be used virtual interface and VIP redundancy (VRRP). The incoming traffic will be load balanced over the internal servers, depending of the content rules. All the servers will link to a service with its physical IP address. These services will link to an owner with content rules, the content contains the services and is reachable from the Operator LAN (or internal MMCS network) by a Virtual IP Address. The content loadbalance the services. When one of the services is down, depending on the used loadbalance algorithm, this service will not be used by the content rule. In the figure below you see this set-up of the configuration file. In the appendici you see the complete example of a configuration file.
configure !************** GLOBAL *************************** Networking settings !************* INTERFACE ************************* Interface settings !************** CIRCUIT ************************** Circuit settings; virtual routers, redundant interfaces and redundant VIP !**************
SERVICE **************************
service <Name_1> ip address <real IP address> active service <Name_2> ip address <real IP address> active service etc !**************** OWNER *************************** owner <Owner_Name_1> content <Content_Name_1>
11
add service Name_1 add service Name_2 vip address <IP address> protocol tcp redundancy-l4-stateless balance srcip port <port number> active <other content rules>
owner <other owners> content etc !***************** GROUP *************************** group LB vip address <same IP address as in one of the content rules> add service Name_1 add service Name_2 active group etc
Figure 1-1: Short explanation of the configuration file Figure 1-1: Schema of a load balanced environment From the load balancing point off view, the MMSC environment looks principle the same as the schema below.
Operator switch VLAN2 192.1.1.1 CSS02 BACKUP VLAN1 10.1.1.1 2950
Redundant Interface
Operator switch
Start on the top, the operator cloud with its gateway connected to the CSS. The CSS is connected by an optical fiber with the 2950 switch. Both 2950 switches have an optical interconnection. All the systems (front-ends, back-end and MM-store) are connected to 2950 switch. The servers will be load-balanced by both CSS 11052.
2950
12
13
Getting Started
Log into the CSS using the default administrative username admin and password system or the username and password you assigned during the boot process. Access config mode. # config (config)# Access boot mode to configure an IP address for the Ethernet Management port. This IP address must be on a different subnet than any other CSS VLAN circuit IP subnet or you will not be able to access the port. You must reboot the CSS for the new IP address to take effect. (config)# boot (config-boot)# ip address 172.3.6.58 Configure the subnetmask (config-boot)# subnet mask 255.255.255.0
14
This is the only way to power off the system, do not direct a power off!
15
16
To get a running configuration on the CSS some standard settings are necessary. Depending on the configuration of the STP settings must be changed. The minimal settings for a running configuration default gateway; connecting Ethernet ports to a Vlan; circuits, redundant interfaces, VIPs and Vlans; create a services; for the real servers; create an owner with content; create a group; to become a connection form the inside network to the operator side; enable the DNS service and the domain suffix.
In the next paragraph the configuration of the CSS 11052 will be explained. The examples have no relation with the IP addresses and system settings of the MMSC system.
17
(config)# Enter the interface mode for the interface you wish to configure. This interface command applies to the CS150. On the CSS 11052 is Ethernet port 1; ethernet-1 and the is the Gigabit Ethernet port; ethernet-9 CS150(config)# interface ethernet-1 CS150(config-if[ethernet-1])# CS150(config-if[ethernet-1])# bridge vlan 2 CS150(config-if[ethernet-1])# description "Int. netwrk. GW:10.20.30.254" CS150(config-if[ethernet-1])# exit
Create the virtual route with a virtual router identifier VRID (e.g. 1) chose for another virtual router another VRID but for the related peer backup system the same VRID. Give also a priority to the virtual router, give the master the highest number (0255) but dont use 255. CS150(config-circuit-ip[VLAN20-10.20.30.40])# ip virtual-router 1 priority 240
Create the redundant interface, only on the internal site, this will be the default gateway for the servers The typical use for virtual interface redundancy is in a configuration where servers are positioned behind a Layer 2 switch and CSSs with the redundant virtual interface are positioned in front of the Layer 2 switch. The servers would be configured with a default route pointing to the redundant virtual interface IP address. CS150(config-circuit-ip[VLAN20-10.20.30.40])# ip redundant-interface 1 10.20.30.254 Create the redundant VIPaddress.
18
Before you use this command, the VIP must be configured in a minimum of one content rule. Additionally, if you defined the content rule VIP using the range option, you must configure an identical range for the redundant VIP.
Enter config mode by typing config. (config)# When you create a service. To create additional services, re-enter the service command. (config)# service fe1 (config-service[fe1])# string FrontEnd1 (config-service[fe1])# # keepalive port 23 (config-service[fe1])# ip address 10.20.30.80 (config-service[fe1])# active When you need to change a service go to this service, stop the service, do the changes and dont forget to start the service again. Enter config mode by typing config. (config)# (config)# service fe1 (config-service[serv1])# suspend (config-service[serv1])# <change the setting> (config-service[serv1])# active
19
(config)# Create an owner. (config)# owner wds Add to these owner the content (services).
Create the content rule for the owner. CS150(config-owner[wds])# content L4-wds_25 The CSS enters into the owner-content rule mode.
Configure a Virtual IP address (VIP) or domain name for the owner content. CS150(config-owner-content[wds-L4-wds_25])# ip address 10.20.30.75
Set the protocol and the port. The service is only accessible by the defined port.
During a failover situation the service shall stay connected to the client
20
CS150(config-owner-content[wds-L4-wds_25])# redundancy-l4-stateless Configure a load-balancing algorithm for the content rule. CS150(config-owner-content[wds-L4-wds_25])# balance srcip
Activate the content rule. CS150(config-owner-content[wds-L4-wds_25])# act To make changes into a content rule, first stop (suspend) the content rule, make the changes and start (active) the content rule.
21
Troubleshooting
22
---- ----Up
Licensed Cmd Set(s): Standard Feature Set Enhanced Feature Set CS50#
23
Redirect Domain: Redirect String: Keepalive: (ICMP 5 3 5 ) Mtu: Connections: 1500 0 State Transitions: 2 Max Connections: 0
CSS01# show service summary Service Name State Conn Weight Avg State Load Transitions FE_1 FE_2 FE_3 FE_4 NAT_1 NAT_2 NAT_20 NAT_21 Alive Down Alive Alive Alive Alive Suspended Suspended 0 0 0 0 1 0 0 0 1 2 8 5 0 0 8 8 0 1
1 255 1 1 1 1 2 2 2 2
1 255 1 255
24
1 255 1 2
------
----- ------ ---------- ----Alive Alive Alive Down Alive Alive Alive 2 2 2 2 2 2 56 28 52 255 24 12 24 25 ICMP ICMP ICMP ICMP ICMP ICMP ICMP 0 0 0 0 0 0 0
25
svc1fe42
303
Alive
12
ICMP
26
configure
!************************* INTERFACE ************************* interface e1 phy 100Mbits-FD description "Connection to Internal SVCC-network."
27
ip address 10.253.200.99 255.255.255.0 ip virtual-router 1 priority 240 ip redundant-interface 1 10.253.200.254 ip redundant-vip 1 10.253.200.240
ip address 10.226.178.126 255.255.255.0 ip virtual-router 2 priority 240 ip redundant-vip 2 10.226.178.121 ip redundant-vip 2 10.226.178.120 ip redundant-vip 2 10.226.178.125 ip redundant-vip 2 10.226.178.130 ip redundant-vip 2 10.226.178.134 ip redundant-vip 2 10.226.178.135
28
weight 2 active
service svc1fe11 ip address 10.253.200.101 weight 2 string FE1a keepalive port 25 active
service svc1fe12 ip address 10.253.200.1 weight 5 string FE1b keepalive port 25 active
service svc1fe21
29
service svc1fe22 ip address 10.253.200.2 weight 5 string FE2b keepalive port 25 active
service svc1fe31 ip address 10.253.200.103 weight 2 string FE3a keepalive port 25 active
service svc1fe32 ip address 10.253.200.3 weight 5 string FE3b keepalive port 25 active
service svc1fe41 ip address 10.253.200.104 weight 2 string FE4a keepalive port 25 active
30
service svc1fe42 ip address 10.253.200.4 weight 5 string FE4b keepalive port 25 active
content BE1 add service NAT_BE1a vip address 10.226.178.134 add service NAT_BE1b active
content BE2
31
add service NAT_BE2a vip address 10.226.178.135 add service NAT_BE2b active
owner maint_svc_mmsc
content l3_svc1ms1 vip address 10.226.178.121 add service svc1ms1b add service svc1ms1a active
owner svc_mmcs
content l4_SMTP_ext add service svc1fe12 add service svc1fe22 add service svc1fe32 add service svc1fe42 add service svc1fe11 add service svc1fe21 add service svc1fe31 add service svc1fe41 vip address 10.226.178.125 protocol tcp port 25 redundancy-l4-stateless
32
content l4_SMTP_int add service svc1fe41 add service svc1fe31 add service svc1fe21 add service svc1fe11 add service svc1fe42 add service svc1fe32 add service svc1fe22 add service svc1fe12 vip address 10.253.200.240 protocol tcp redundancy-l4-stateless balance srcip port 25 active
!*************************** GROUP *************************** group NAT_BE1a add service NAT_BE1a vip address 10.226.178.134 add service NAT_BE1b active
group NAT_BE2a add service NAT_BE2a vip address 10.226.178.135 add service NAT_BE2b active
group SMTP
33
vip address 10.226.178.125 add service svc1fe41 add service svc1fe42 add service svc1fe11 add service svc1fe12 add service svc1fe21 add service svc1fe22 add service svc1fe31 add service svc1fe32 active
group svc1ms1 vip address 10.226.178.121 add service svc1ms1a add service svc1ms1b active
34
configure
!************************* INTERFACE ************************* interface e1 phy 100Mbits-FD description "Connection to Internal SVCC-network."
35
ip address 10.253.200.199 255.255.255.0 ip virtual-router 1 priority 230 ip redundant-interface 1 10.253.200.254 ip redundant-vip 1 10.253.200.240
ip address 10.226.178.127 255.255.255.0 ip virtual-router 2 priority 230 ip redundant-vip 2 10.226.178.120 ip redundant-vip 2 10.226.178.121 ip redundant-vip 2 10.226.178.125 ip redundant-vip 2 10.226.178.130 ip redundant-vip 2 10.226.178.134 ip redundant-vip 2 10.226.178.135
36
weight 2 active
service svc1fe11 ip address 10.253.200.101 weight 2 string FE1a keepalive port 25 active
service svc1fe12 ip address 10.253.200.1 weight 8 string FE1b keepalive port 25 active
service svc1fe21
37
service svc1fe22 ip address 10.253.200.2 weight 8 string FE2b keepalive port 25 active
service svc1fe31 ip address 10.253.200.103 weight 2 string FE3a keepalive port 25 active
service svc1fe32 ip address 10.253.200.3 weight 8 string FE3b keepalive port 25 active
service svc1fe41 ip address 10.253.200.104 weight 2 string FE4a keepalive port 25 active
38
service svc1fe42 ip address 10.253.200.4 weight 8 string FE4b keepalive port 25 active
content BE1 add service NAT_BE1a vip address 10.226.178.134 add service NAT_BE1b active
content BE2
39
add service NAT_BE2a vip address 10.226.178.135 add service NAT_BE2b active
owner maint_svc_mmsc
content l3_svc1ms1 vip address 10.226.178.121 add service svc1ms1b add service svc1ms1a active
owner svc_mmcs
content l4_SMTP_ext add service svc1fe12 add service svc1fe22 add service svc1fe32 add service svc1fe42 add service svc1fe11 add service svc1fe21 add service svc1fe31 add service svc1fe41 vip address 10.226.178.125 protocol tcp port 25 redundancy-l4-stateless
40
content l4_SMTP_int add service svc1fe41 add service svc1fe31 add service svc1fe21 add service svc1fe11 add service svc1fe42 add service svc1fe32 add service svc1fe22 add service svc1fe12 vip address 10.253.200.240 protocol tcp port 25 redundancy-l4-stateless balance srcip active
!*************************** GROUP *************************** group NAT_BE1a add service NAT_BE1a vip address 10.226.178.134 add service NAT_BE1b active
group NAT_BE2a add service NAT_BE2a vip address 10.226.178.135 add service NAT_BE2b active
group SMTP
41
vip address 10.226.178.125 add service svc1fe41 add service svc1fe42 add service svc1fe11 add service svc1fe12 add service svc1fe21 add service svc1fe22 add service svc1fe31 add service svc1fe32 active
group svc1ms1 vip address 10.226.178.121 add service svc1ms1a add service svc1ms1b active
42
References
Version History
Version 1.0 1.1 1.2 Status DRAFT DRAFT DRAFT Date 26 June 02 10 july 02 19 juli 02 Details of Changes Initial version Initial version Initial version Author(s) Roger Heijnen Roger Heijnen Roger Heijnen
Approval
Version 1.0 Date October 2002 Approved by Rob Mertz Signature