Sut851 Install

7/28/2019 Sut851 Install

1/288

Lotus Sametime

Version 8.5.1

Lotus Sametime Unified TelephonyInstallation Guide


2/288


3/288

Lotus Sametime

Version 8.5.1

Lotus Sametime Unified TelephonyInstallation Guide


4/288

NoteBefore using this information and the product it supports, read the information in "Notices."

Edition notice

This edition applies to version 8.5.1 of IBM Lotus Sametime Unified Telephony (program number 5724-U79) and toall subsequent releases and modifications until otherwise indicated in new editions.

Copyright IBM Corporation 2010.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/288

Contents

Chapter 1. Sametime Unified Telephonyoverview . . . . . . . . . . . . . . 1

Sametime Unified Telephony PDF library. . . . . 1Solution overview . . . . . . . . . . . . 1

Features and functions . . . . . . . . . . 2Supported interfaces, protocols, PBXs, andgateways . . . . . . . . . . . . . . 4

Component overview . . . . . . . . . . . 5Telephony Application Server. . . . . . . . 6Media Server overview . . . . . . . . . . 8Telephony Control Server . . . . . . . . . 10

Deployment scenarios . . . . . . . . . . . 12Minimal server deployment . . . . . . . . 12Multiple TAS server deployment with StandbyTAS . . . . . . . . . . . . . . . . 12Deployment with IP PBX environment . . . . 13

Deployment with non-IP PBX environment . . . 14

Chapter 2. Installing . . . . . . . . . 15Hardware installation . . . . . . . . . . . 15

Setting up hardware for a Telephony ControlServer . . . . . . . . . . . . . . . 15Setting up hardware for a Telephony ApplicationServer . . . . . . . . . . . . . . . 19SAN deployment . . . . . . . . . . . 25

Software installation . . . . . . . . . . . 39Installing Telephony Control Server . . . . . 39Installing Telephony Application Servers . . . 60Starting and stopping services. . . . . . . 122

Verifying the installation . . . . . . . . 124

Chapter 3. Upgrading from LotusSametime Unified Telephony 8.0 CF1 . 127Planning the upgrade to Lotus Sametime UnifiedTelephony 8.5.1 . . . . . . . . . . . . . 127Understanding directory conventions . . . . . 128Upgrading a Telephony Control Server. . . . . 129Updating the list of supported clients for Sametime 129Upgrading a Telephony Application Server . . . 130

Backing up the Telephony Application Serverconfiguration . . . . . . . . . . . . 130Performing the Telephony Application Serverupgrade . . . . . . . . . . . . . . 132

Chapter 4. Configuring . . . . . . . 145Configuring the Telephony Control Server. . . . 145

Command-line interface tasks . . . . . . . 145Common Management Portal (CMP)

configuration tasks . . . . . . . . . . 158Configuring Telephony Application Servers . . . 180Initializing the persistent cache on a TelephonyApplication Server . . . . . . . . . . 180Establishing trust between TelephonyApplication Servers and Lotus Sametime servers 184

Configuring the dial plan . . . . . . . . . 186Example dial plan . . . . . . . . . . . 187Creating office codes . . . . . . . . . . 188Creating Home DNs . . . . . . . . . . 189Different numbering plans available . . . . . 193Configuring business groups . . . . . . . 194Creating numbering plans . . . . . . . . 195Creating default unified number feature profiles 198

Creating a queue device . . . . . . . . . 198Overview of number plan components . . . . 206Create conferencing endpoint profile . . . . 210Creating a route . . . . . . . . . . . 218

Adding subscribers for testing. . . . . . . . 220Conducting simple call tests . . . . . . . . 221Configuring conferencing . . . . . . . . . 222

Enabling conferencing on the Media Server . . 223Updating the dial plan . . . . . . . . . 227Configuring conferencing resources on TAS . . 240Modifying endpoint in CLI . . . . . . . . 245Testing conference features . . . . . . . . 250

Configuring security . . . . . . . . . . . 253Enabling TLS encryption for the deployment 253

Configuring SUT SIP proxy/registrar security 257Configuring TLS trunks . . . . . . . . . 260

Configuring advanced features . . . . . . . 261Localizing announcements . . . . . . . . 261Configuring CDR and call records . . . . . 271Setting up 911 . . . . . . . . . . . . 271Communications Assistance for LawEnforcement Act . . . . . . . . . . . 272Setting up speed dial lists . . . . . . . . 273Setting up voice mail . . . . . . . . . . 273

Chapter 5. Preparing the Sametimeclient . . . . . . . . . . . . . . . 275

Notices . . . . . . . . . . . . . . 277Trademarks . . . . . . . . . . . . . . 279

Copyright IBM Corp. 2010 iii


6/288

iv Lotus Sametime Unified Telephony: Installation Guide


7/288

Chapter 1. Sametime Unified Telephony overview

IBM Lotus Sametime Unified Telephony provides the integration of telephonyacross multivendor Private Branch Exchange (PBX) systems resulting in a unified

end-user experience, including integrated softphones; phone and IM presenceawareness; call control and rules-based call management.

Sametime Unified Telephony PDF library

Help for IBM Lotus Sametime Unified Telephony is available in PDF format.

Guide Description

Lotus Sametime Unified Telephony8.5.1 Quick Start Guide

The Quick Start Guide provides an overview of theinstallation requirements and process for deployingLotus Sametime Unified Telephony.

Lotus Sametime Unified Telephony

8.5.1 Functional Specification

The Functional Specification includes a description of

Lotus Sametime Unified Telephony softwarecapabilities and benefits, as well as a summary of userand administrator features. The specification describessupported languages and product architecture,including detailed server specifications for theTelephony Control Server, the Telephony ApplicationServer, and the Media Server. The functionalspecification also describes the storage area networkand IP network connections. The specification alsoincludes information on interoperability and testing.

Lotus Sametime Unified Telephony8.5.1 Installation Guide

The Installation Guide provides detailed informationon installing and configuring Lotus Sametime UnifiedTelephony 8.5.1, including: hardware, operatingsystems, primary servers, and failover servers.

Lotus Sametime Unified Telephony8.5.1 Administration Guide

The Administration Guide explains how to monitorand maintain a Lotus Sametime Unified Telephony8.5.1 deployment, and includes sections ontroubleshooting and security.

Solution overview

Enterprises need to deliver products and services faster to enhance customerservice and speed decision making. Companies are finding that a key to improvingproductivity and business responsiveness is delivering communication andcollaboration tools in a consistent and meaningful context. By integrating

telephony into the company's greater communications platform, decision makingand handling business processes are accelerated. The telephony integration allowsperson-to-person as well as multi-person interaction.

IBM Lotus SametimeUnified Telephony software offers the immediacy of instantmessaging with telephone capabilities on users' desktops, so that users can find,reach, and collaborate with one another more effectively. Telephony features withintegrated presence awareness, softphones, call control, and rules-based callmanagement can be used with a wide variety of telephone systems. Themiddleware layer of Unified Telephony software provides connectivity to multipletelephone systems both IP private branch exchange (PBX) and legacy

Copyright IBM Corp. 2010 1
http://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_qsg_en.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_qsg_en.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_qsg_en.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_func_spec.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_func_spec.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_func_spec.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_install.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_install.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_install.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_admin.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_admin.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_admin.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_admin.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_admin.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_install.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_install.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_func_spec.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_func_spec.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_qsg_en.pdfhttp://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v851.sut_install.doc/sut851_qsg_en.pdf


8/288

time-division multiplexing (TDM) systems independent of the enterprise'stelephony infrastructure or migration to IP telephony.

Features and functionsThis section describes the benefits and features contained in IBM Lotus SametimeUnified Telephony.

Benefits

v Helps users access telephony functionality from within real-time collaborationsoftware. The front-end user capabilities in IBM Lotus Sametime UnifiedTelephony software are designed to be intuitive and ease access to telephonyfunctionality from within the Lotus Sametime client.

v Provides users a simple, consistent user communications experience includingtelephony presence, incoming call management and call control, click to call andsoftphones. Within a single client, users have the same functions and userexperience independent of the phone system to which they are connected. Userscan see if colleagues are available and then reach them more reliably andeffectively without having to find different numbers for different locations.

v

Fosters communication and collaboration within applications to help speedbusiness processes for users. Lotus Sametime and IBM Lotus Sametime UnifiedTelephony software allow communication and collaboration in a meaningfulcontext that accommodates work-style preferences. Users can access and managetheir communications from a Lotus Sametime or IBM Lotus Notes client; aMicrosoft Outlook, Microsoft Exchange, or Microsoft Office application; or anenterprise application.

v Helps optimize the value from existing enterprise applications and telephonysystems - independent of the telephony infrastructure or migration to IPtelephony. The software integrates both IP PBX and legacy TDM systems.

v Helps reduce calling costs with softphone, call management, and aggregatedpresence awareness. Calls made through the softphone feature avoid PBXtelephone charges. Call management capabilities can direct calls to a user'spreferred device so that colleagues do not have to call various devices to findthe user. The aggregation of presence information - a user's availability forinstant messaging or a telephone call - helps colleagues avoid makingunnecessary calls or calls that cannot be accepted by a user. Theclick-to-conference feature can reduce cost of expensive audio-conferencingservices for improvised conferences

Features

v Presence awareness - including telephony status. At a glance, users can seetelephone status (for example, on the phone, off the phone) along with onlinepresence status (for example, available, away, in a meeting, do not disturb),making it easy to know whether it is appropriate to initiate a real-time

conversation through instant messaging or a phone/conference call.v Telephony and voice The front-end user capabilities in Lotus Sametime

Unified Telephony software are designed to be intuitive and ease users' access totelephony functionality from within the Lotus Sametime client. The softwarecombines the immediacy of instant messaging with telephone capabilities, righton users' desktops. Users can see if colleagues are available and then reach themmore reliably and effectively without having to look up their numbers even ifthey are on the move.

2 Lotus Sametime Unified Telephony: Installation Guide


9/288

Softphone users can initiate and manage phone calls through their PCmicrophone and speakers using the Lotus Sametime Unified Telephonyembedded softphone.

Click to Call and Click to Conference Users can initiate a call or audioconference through a PBX telephone system by selecting one or multiplenames from the contact list. Users who are collaborating through an instantmessage can escalate from instant messaging to a call or audio conference byusing the click-to-call, click-to-conference capability.

Incoming call management With Lotus Sametime Unified Telephonysoftware, users focus on the people they need to reach not where they areor what device they are using. Users can have a single unified phone numberthat allows calls to be routed automatically to their current location and thedevice they are currently using. Users can easily set rules and preferences todirect their calls such as redirecting a call to a mobile phone. BecauseLotus Sametime software has presence and location awareness, LotusSametime Unified Telephony software can automatically set the preferredcontact device based on availability and location status.

Call control The software includes call control capabilities for participantsand moderators.

- Participant call controls

v Click to Call

v Click to Conference

v accept, reject, or redirect incoming call

v transfer/forward call

v raise/lower volume

v mute/unmute

v move call to another device

v Call Merge

v hold/resume

v disconnect- Moderator call controls

v mute one or all participants

v lock call

v invite others

v end call for everyone

A simple, consistent user communications experience on the desktop client.Sametime Unified Telephony software provides the same set of functionalityand user experiences to supported users, independent of the phone system towhich they are connected. And, it provides these capabilities from within asingle client. Other offerings provide a softphone that only works with a PBX

from a specific vendor and that require a full migration to IP telephony beforedelivering a common set of unified communications collaboration capabilitiesto users.

v A platform for unified communications and collaboration

The back-end middleware layer of Lotus Sametime Unified Telephonysoftware masks the complexity of back-end integration by providingconnectivity to multiple telephone systems.

The software connects through Session Initiation Protocol (SIP) toSIP-compliant PBXs from multiple vendors using SIP, and it connects tolegacy TDM phone systems through SIP gateways.

Chapter 1. Sametime Unified Telephony overview 3


10/288

Technology and telecommunications managers can extend their existingtelephone systems rather than replacing them to provide the same set ofunified communications functionality to supported users regardless of thephone systems they access.

The middleware approach can help enterprises deliver the value of unifiedcommunications to virtually all users even if they have not yet completeda migration to VoIP telephony.

Lotus Sametime Unified Telephony software is designed for reliability andscalability from hundreds of users to hundreds of thousands.

The call control elements are designed to provide high availability, helping toassure that calls can be completed. Other elements of the system supportredundancy, clustering, and load balancing to help optimize performance andcontinue to provide service to users in the event of component failure.Theincluded IBM Tivoli System Automation for Multiplatforms (SAMP) softwareprovides advanced policy-based automation for applications and servicesacross heterogeneous environments to help provide high levels of availabilityand reduce the frequency and duration of service disruptions.

Lotus Sametime Unified Telephony software provides tools for configuring,monitoring, and managing your deployment. A browser-based configurationinterface aids the configuration of the telephony control, application andMedia servers, as well as the definition of business groups, number plans andfeature profiles. Administration consoles can be used to check server status; tomonitor call volume, user call activity and license usage; and to view and editSIP proxy properties.

Supported interfaces, protocols, PBXs, and gatewaysThis section lists the supported interfaces, protocols, PBXs, and gateways fortheIBM Lotus Sametime Unified Telephony product.

The list of interfaces and PBXs that are supported by Sametime Unified Telephonyare included in the Sametime Unified Telephony system requirements.

Protocols

v Proprietary protocol

Virtual Places (VP) - A proprietary protocol used in Sametime forcommunication between clients and server applications and the Sametimeserver.

v Standard protocols:

Hypertext Transfer Protocol (HTTP) - A communications protocol for thetransfer of information about the Internet.

Session Initiation Protocol (SIP) - A signaling protocol used for setting up andtearing down multimedia communication sessions.

Media Gateway Control Protocol (MGCP) - A signaling and call controlprotocol used within a distributed Voice over IP system.

Simple Object Access Protocol (SOAP) - A simple XML-based protocol to letapplications exchange information over HTTP.

Computer-Supported Telecommunications Applications (CSTA) - Anabstraction layer for telecommunications applications.

SIMPLE

T.120

XMPP

http://www-01.ibm.com/support/docview.wss?uid=swg27019317http://www-01.ibm.com/support/docview.wss?uid=swg27019317


11/288

H.323

PBX

v IP PBX Voice over a data network and interacts with the normal publicswitched telephone network (PSTN)

v Telephony Gateway Telecommunications network node that can interface with

another network that uses different protocols, as follows: PSTN Network of the world's public circuit-switched telephone networks.

TDM PBX Time-Division Multiplexing used for circuit mode communicationwith a fixed number of channels and constant bandwidth per channel.

Gateways

v Siemens Gateway

SIP gateways for Non-IP PBX sites

Gateway RG8702 - two E1/T1 ports - 60 or 46 IP channels

Gateway RG8708 - eight E1/T1 ports - 240 or 184 IP channels

Gateway RG8716 - 16 x E1/T1 ports - 480 or 368 IP channels

Software RG7800v Dialogic Gateway

DMG2030DTI - one E1/T1 port - 30 IP channels

DMG2060DTI - two E1/T1 ports - 60 IP channels

DMG2120DTI - four E1/T1 ports - 120 IP channels

Component overview

This section describes the components that make up the IBM Lotus SametimeUnified Telephony product including servers, clients, and external telephonyequipment.

The following graphic shows the various components and how they work together.



12/288

The major components are discussed in separate topics:

v Telephony Application Server

v The Media Server

v Telephony Control Server

Lotus Sametime Standard Server

IBM Lotus Sametime Standard server lets a community of users to collaborate in

real-time activities such as online meetings, presence, chat, and VoIP over andintranet or the Internet.

Lotus Sametime Connect Client

The Lotus Sametime Connect client is the end-user client for letting communityusers collaborate in real-time activities: presence, chat, and VoIP over an intranet orthe Internet.

External Telephony Equipment

v IP PBX The business telephone system that delivers voice over a data networkand interacts with the normal public switched telephone networks (PSTN).

v PSTN The network of the world's public circuit switched telephone networks.

v Telephony Gateway A telecommunications network node that can interfacewith another network that uses different protocols.

Telephony Application ServerThe Telephony Application Server provides telephony services to the SametimeUnified Telephony users through the Sametime Connect client. The TelephonyApplication Server interfaces with Sametime Community server, enterprisedirectory, and Telephony Control Servers.



13/288

Telephony Application Server

The Telephony Application Server (TAS) executes the workflow for handling thecalls of the users. The Telephony Application Server (TAS) executes the workflowfor handling the calls of the users. Users must be provisioned to a specificTelephony Application Server before they can use IBM Lotus Sametime UnifiedTelephony. The Telephony Application Server is notified when a user logs on to the

Lotus Sametime Connect and a channel opens to the user and notifies the user thatthe telephony service is available.

There can be up to eight Telephony Application Servers on each SUT installation.

Each Telephony Application Server monitors up to 15,000 users. User affinity isestablished when a person logs on to the Sametime server with a SametimeUnified Telephony client. Once the Sametime server notifies the TelephonyApplication Server of the event, the Telephony Application Server opens a channelto the Sametime Connect client that enables the Sametime Unified Telephonyfeatures.

Users can provision as many preferred devices and phone numbers for themselvesas they like. The Telephony Application Server can ring any of these devices basedon rich presence and user rules that allow the user to determine what device theywant to ring according to any combination of time, location, and presence status.Telephony Application Servers are deployed with at least one warm standby serverto provide redundancy for server failure. One warm standby server can be used toprovide redundancy for one or all eight Telephony Application Servers. If higherredundancy is required, the number of warm standby servers can be increased tomatch the number of Telephony Application Servers.

Components

SIP Proxy/RegistrarThe Session Initiation Protocol (SIP) is a protocol for creating, modifying,

and terminating sessions with one or more Lotus Same Unified Telephonyusers. SIP uses elements called proxy servers to help route requests to theuser's computer, to authenticate and to authorize users. SIP also provides aregistration function that lets users send their current locations for use bythe proxy servers.

Presence AdapterThis component publishes telephony presence to the Lotus Sametimecommunity.

Communications AdapterThis component starts and manages two-party and conference calls. Thecommunication adapter keeps the Lotus Sametime Connect client informedof the IP address of the SIP registrar.

Media ServerThis component provides tones and announcements for teleconferencemessages.

AdministrationThis component displays the status of the main components and providesreal-time monitoring of user sessions and registered devices.

REST APIThe Representational State Transfer Convention (REST) is the standard for



14/288

building web services. The REST interface allows for Click-To-Call andconference integration with third-party applications.

Functions

Telephony Application Server performs the following functions:

v Runs all application logic that manages the workflow associated with routingincoming calls so that they are always routed to the preferred device.

v Initiates all call-related events to the client. If the Sametime Connect client isonline, the Telephony Application Server initiates a popup window that lets theuser answer an incoming call with the current preferred device or deflect the callto another device.

v Provides personal call history records of all calls that user makes and receives.

v Handles all call and flow control for audio conferences.

v Manages all user and configuration data.

v Some data is provisioned into the system as part of the initial configuration,while other data is managed by the user.

v Together with Media Server component provides limited audio conferencing

capability. Primary use case is for small ad-hoc meetings. This capacity isconfigurable.

v Provides ability to provision remote administrative features.

v Provides SIP Registrar and Proxy service for the embedded softphones.

Media Server overviewThe Media Server is an application that is installed on to the TelephonyApplication Server and integrates into the Telephone Control Server Framework.The Media Server can be installed on its own hardware. The more dedicated thehardware, the better the Media Server performance.

The Media Server hosts and executes the following services:

v Provides announcement services for the Telephony Control Server in differentlanguages.

v Supports the following audio-codecs, and can transcode between different codes:

G.711 A-Law (Europe and the rest of the world)

G.711 -Law (North American and Japan)

G.729 AB

Every Media Server node can handle up to a certain number of media channels. Amedia channel is an active call with an active RTP-based media steam.

Media Server Scalability

The following table shows media server scalability according to the server profile.It displays required hardware, RAM, and the maximum rate of calls per hour atthe busiest time of the day.



15/288

Table 1. Media Server Scalability by server profile

ServerProfile CPU RAM (GB)

Max. G.711Channel

Max. G.729Channel BHCA rate

Small server Dual-Coresystem, forexample, IntelXeon 3060 or5030 (>= 2.33GHz)

4 150 50 3,000

MidrangeServer

Quad-coresystem, forexample, IntelXeon 5345(>= 2.33GHz)

4 300 100 6,000

High-EndServer

Octo-Coresystem, forexample, 2Intel Xeon5345 (>=2.33GHz)

8 500 160 10,000

Each Telephony Application Server is provided with a single-accompanying MediaServer to handle the media server needs of that Telephony Application Server.

When scaling up to multiple Telephony Application Servers with theircorresponding Media Server, the Telephony Control Server must be configured touse the Media Server used for the tones and announcements of the usersconfigured on a specific TAS.

The following graphic shows a typical Lotus Sametime Unified Telephony

environment that can support up to 100,000 users. This support requires the use ofseven Telephony Application Servers, each supporting up to 15,000 users and atthe center is a Duplex Telephony Control Server system.

Note: One TAS server is used as a failover server in this diagram but it is notactive until required.

The Sametime server supports 30,000 - 50,000 users depending on the operationalprofile. The Sametime cluster support can be scaled as needed.

A Telephony Application Server can be connected to one Sametime server or acluster community.



16/288

Media Server Conferences:

Media Servers support ad-hoc conferencing. Users can initiate conference calls andthe conference bridge in the Media Server dials out to participants. Once thead-hoc conference has been started by the user, the conference bridge in the MediaServer can accept inward dialing into the conference bridge. The Media Serverconferences feature has its own set of specifications:

v There is no fixed limit to the number of simultaneous ad-hoc conferences. Thelimit is based on the maximum number of total conference participants allowed.

v The Media Server transcodes between different codecs if needed.

v The number of conference participants in a single conference can be configured.The default number of users is 6.

vAn onboard Media Server can handle 400 concurrent conference legs. For

example, there can be 100 conferences with 4 people each, or 80 conferenceswith five people each, and so on.

Media Server: Offboard

A Sametime Unified Telephony cluster supports up to eight external or offboardMedia Servers. The ratio of TAS to Media Servers is always one-to-one. There is alimit of eight Telephony Application Servers to one Telephony Control Server.

Note: You can configure the Telephony Control Server itself to use a separateMedia Server for tones and announcements. However, this Media Server cannot beused for conferences.

For failover purposes, the TAS and Media Server must be on the same subnet.

Telephony Control ServerThe Telephony Control Server is responsible for receiving incoming requests. TheTelephony Control Server also provides the unified number service and handles allincoming call routing for the unified number. The Telephony Control Servercontainer is a back-to-back user agent (B2BUA) with a PBX abstraction layer thatallows it to work with Telephony Application Server.



17/288

Specifications

The Telephony Control Server (TCS) handles the VoIP connections. This server ispart of a duplex configuration that serves as a failover system. The TelephonyControl Server is always deployed in a duplex configuration with RAID hard diskdrives to provide high availability.

The Telephony Control Server provides the unified number facility that informs theTelephony Application Server about receiving a call from the unified number of auser. It also uses that number for any calls the user makes through Lotus SametimeConnect client. The unified number is the single telephone number for routing callsto the telephony devices of the user.

The Telephony Control Server uses the Computer Supported TelecommunicationsApplication (CSTA) to communicate with the TAS, where call-related events aretriggered and handled. When a call comes in to TCS and is a unified number, TCSnotifies the TAS through CSTA. The TCS also expects the TAS to return thenumber where the call is routed. All this communication happens through CSTA.

The Telephony Control Server has the following functional components:

v SIP B2BUA The SIP back-to-back user agent (B2BUA) is the user agent to bothend points of a SIP call. B2BUA handles all SIP signaling between the end point,from call initiation to call termination.

v CSTA The abstraction layer of Lotus Sametime Telephony allows interactionson a telephone and a computer to be integrated.

v Hardware: IBM System x3650T with specific part number: 79805CX. It is theonly part number that can be used as a TCS server.

The IBM Lotus Sametime Unified Telephony Connect software cannot beinstalled to any other server.

This part number comes with a pre-defined set of adapters and aconfiguration, including two 146 GB SCSI hard disks configured into RAID

and with two redundant power supplies. Use of this specified part number ensures that all the correct components are

shipped with the server and that the configuration matches what has beentested by IBM software development and performance test teams.

v Operating System: SUSE Linux Enterprise Server version 9 is included in theIBM Sametime Unified Telephony software bundle.

v Software: IBM Lotus Sametime Unified Telephony Connect component ofSametime Unified Telephony.

v Telephony Control Servers have eight Gigabit Ethernet ports and require twosets of physical Ethernet switches with three Virtual LANs (Billing, Managementand Signaling). They also require two direct server-to-server interconnect cablesto assure high availability.

v Two Telephony Control Servers must be on the same layer two subnet with thefollowing requirements:

The network links used for interconnects must have low latency and lowerror rates.

The interconnects must not be used on any network that might experiencenetwork outages of 5 seconds or more.

v Telephony Control Server can handle up to 100,000 users. Telephony ControlServer can handle up to 15,000 SIP trunks.



18/288

v Telephony Control Server acts as SIP B2BUA between PBXs (IP PBXs and Non IPPBXs through SIP gateways).

v Telephony Control Server can connect to the PSTN through SIP gateways. TheTCS is connected to IP PBXs, non-IP PBXs, and gateways through SIP trunks.

v Telephony Control Server can support up to eight active Telephony ApplicationServers and eight warm standby servers. The number of users cannot exceed

100,000 users.

Deployment scenarios

The following sections describe the supported deployment scenarios for theSametime Unified Telephony system.

The supported deployment scenarios are as follows:

Minimal server deploymentThis section describes the minimal IBM Lotus Sametime Unified Telephonydeployment. IT consists of two Telephony Application Servers for failover, a singleMedia Server, and a standard duplex Telephony Control Server cluster.

The Sametime clients are connected to a Domino Sametime server, a TelephonyApplication Server configured for failover, and a Media Server which can behosted on the Telephony Application Server or on a separate server.

The Telephony Application Server is connected to the Telephony Control Serverwhich in turn is connected to the normal array of PBX equipment: desk phones,time-division multiplexing phones, and VoIP phones made up of IP and cellphones that are connected to the IP-PBX system.

This minimal deployment is sufficient for up to 15,000 users.

Multiple TAS server deployment with Standby TASThis section describes a multiple Telephony Application Server IBM LotusSametime Unified Telephony deployment with a standby TAS. This failover



19/288

solution employs a standby Telephony Application Server that comes online whenanother TAS fails. The failover solution is implemented using IBM Tivoli SystemAutomation for Multiplatforms (SAMP).

The basis for this system is the storing of all the individual TAS applicationconfiguration details on separate partitions on a storage area network (SAN).When a particular Telephony Application Server fails, the standby TelephonyApplication Server is pointed to a location on the SAN from which it loads therequired configuration settings and applications.

The time IT takes for the Telephony Application Server system to restore itself isdirectly proportional to the user base that it needs to reload.

Deployment with IP PBX environmentLotus Sametime Unified Telephony software supports connectivity to multiple,mixed PBX environments. Lotus Sametime Unified Telephony software is designedto support connections to SIP-compliant PBX, using the following SIP RFCs: 3261,3264, 4566, and to PBXs supporting Primary Rate Interface (PRI) and Basic RateInterface (BRI) using gateways.

All calls routed to the desk-phones must be intercepted by the Sametime UnifiedTelephony system. Based on Sametime Unified Telephony Subscriber rules, the callis then routed. There is a gateway between the PBX and the phones.

Calls made to the PBX system are now routed through the Sametime UnifiedTelephony system and then routed to the desk top. The customer can choose tokeep the current telephone numbers or get a new set of numbers for the SametimeUnified Telephony installation. Most customers elect to keep their current numbersto avoid disruption in their communications environment. The telephone numbersare converted into Sametime Unified Telephony format, which can include aspecial prefix. The call gets directed to the preferred client device.



20/288

v Calls routed from the PBX to the desk phones no longer reach the desk phonesdirectly, but instead are routed to Sametime Unified Telephony.

v Calls from Sametime Unified Telephony destined for desk phones are routed tothe phones directly.

v Calls from Sametime Unified Telephony to anywhere else are routed to the PBX(and then to the PSTN if needed).

v

Calls from desk phones can be routed directly back to the PBX which route toSametime Unified Telephony if needed.

Deployment with non-IP PBX environmentSametime Unified Telephony deployment on a non-IP PBX is the simplestSametime Unified Telephony installation. It requires that calls are intercepted

between the PBX and the desk phone.

Calls placed on the phones are routed through the non-IP PBX to other phones orto the Public Switched Telephone Network (PSTN).

All calls out to the desk-phones must be intercepted and the calls redirected to the

Sametime Unified Telephony system. Sametime Unified Telephony then decides,based on subscriber rules, where the call is routed. There are several options.

v If the non-IP PBX has a SIP interface, it could act like a gateway between the IPand the Time Division Multiplexing (TDM) world, as the integration point.

v If there is no SIP interface available on the PBX, the use of a SIP Gateway ispossible. The proposed gateway must be compatible with the existing TDMtraffic and there can be no known interoperability issues between the gatewayand the non-IP PBX.



21/288

Chapter 2. Installing

This section provides an overview of the installation prerequisites, a checklist, andthe installation tasks for the Lotus Sametime Telephony product.

Hardware installation

Hardware technical information relating to the Telephony Control Server and theTelephony Application Server.

Setting up hardware for a Telephony Control ServerSet up the hardware needed for a Telephony Control Server in an IBM LotusSametime Unified Telephony deployment.

Telephony Control Server

The Telephony Control Server runs on an IBM xSeries 3650T, using SuSEEnterprise Linux Server version 9. Install Telephony Control Server in pairs toprovide backup and failover services; each server can be cabled in aswitchover/failover style or directly to the network. For technical specifications,see the Sametime Unified Telephony system requirements.

TCS hardware installation checklistThis section lists all the hardware requirements for the TCS.

Hardware checklist

The Telephony Control Server hardware checklist:v Inventory and inspect the hardware.

v Locate the IBM xSeries server printed documentation and digital media.

v Perform a power on test.

v Attach the slides to the rack and place the servers onto the slides.

v Connect all cables.

v Modify the SCSI RAID configuration

v Modify the server BIOS settings.

v Update firmware.

Copyright IBM Corp. 2010 15
http://www-01.ibm.com/support/docview.wss?uid=swg27018591http://www-01.ibm.com/support/docview.wss?uid=swg27018591


22/288

v Power-Supply AC or DC (Hot swappable)

The basic system sometimes come with the memory and additional NIC cards.These cards are packaged separately and need to be inserted into the server. Thedual port and Quad port Gigabyte Ethernet cards must be placed in specific PCIslots.

Telephony Control Server cablingThis section describes the Telephony Control Server cabling for simplex and duplexsystems.

v 2 x Power-Supply AC or DC (Hot swappable)

v Remote Management with Intel BMC

v 2U rack-optimized 20" deep chassis

The dimensions of the server are:

v Height (imperial/metric) 3.5 in/87.6 mm

v Width (imperial/metric) 17.14 in/ 435.0 mm

v Depth (imperial/metric 20.0 in/508.0 mm

There are at least eight cables used in connecting a single 3650T server. Six cablesare connected to the network and two cables serve as cross-over cables to beconnected to the second 3650T server.

BIOS SettingsDuring the installation of the TCS hardware, you must also perform BIOS settings.

Before you begin

Determine that all the hardware works as expected.

About this task

You can enter the BIOS by pressing the F2 key during the Startup process.



23/288

Procedure

1. Change the Startup Sequence to the following order from Boot SettingsPriority:

a. DVD ROM

b. RAID LUN

c. Disabled

2. From Boot Settings Configuration, disable Quick Boot and Quit Boot.

3. From Advanced Settings, select Processor Configuration.

4. Enable Processor Retest.

RAID unit setupDuring the installation of the TCS hardware, you must configure the SCSI RAIDand create a disk mirror.

Before you begin

You must have setup the BIOS.

About this task

A new server is accompanied by an IBM ServerGuide (TM) software. It contains allthe necessary drivers for the server type and model. You can boot the server usingthe CD and it takes you through the setting up the date and time, and the RAIDcontroller. It also primes the server with the correct hard disk drivers (SCSI) for therequired operating system.

You can download the software from the IBM Web site: http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5079561&brandind=5000008

If you do not have the IBM ServerGuide (TM) software available, you can set up

the SCSI RAID unit and create a disk mirror as follows:

Procedure

1. Turn on the server. A number of screens display the system information untiland LSI banner displays and indicates that the LSI controller is initializing.

LSI Logic Corp. MPT IME BIOSCopyright 1995-2005 LSI Logic Corp.MPTBIOS-IME-5.10.06Initializing ............

2. After initialization is complete, the system displays the following message:

LSI Logic Corp. MPT IME BIOSCopyright 1995-2005 LSI Logic Corp.MPTBIOS-IME-5.10.06Press Ctrl-C to start LSI Logic Configuration Utility...

3. Press CTRL+C. The LSI Logic MPT SCSI Utility Screen displays.

4. Press the Down Arrow Key to select the second controller (where the internaldisks are attached.

5. Press Enter to scan the controller.

6. After the scan is complete, the setup utility displays the Adapter Propertiesscreen. Select Device Properties and press Enter.

7. On the RAID Properties array configuration screen, Make sure that the ArrayDisk? entry for the first disk is selected and press the + (plus sign) key.

Chapter 2. Installing 17
http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5079561&brandind=5000008http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5079561&brandind=5000008http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5079561&brandind=5000008http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5079561&brandind=5000008http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5079561&brandind=5000008http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5079561&brandind=5000008


24/288

8. The setup utility displays the following question.

F3 Keep Data (Create 2 disk array)Delete Erase Disk (Create 2 to 6 disk array)

9. Press F3 to keep the data that is already on the disk and create a two-diskarray. The RAID Properties screen is displayed again. The first drive nowshows Yes in the Array Disk? field and Primary in the Status field.

10. On the RAID Properties screen, select the second drive and press the + (plussign) key. The setup utility displays the following:

WARNING: Data on drive will be LOST!Press DELETE if data loss OK or any other key to cancel

This indicates that all the data on the second drive is replaced with the datafrom the primary drive.

11. Press the Delete key to replace the data on the second drive. The RAIDProperties screen is displayed again. The second drive now shows Yes in theArray Disk? field.

12. Press Esc key to exit the RAID Properties screen. The setup utility displays thefollowing:

RAID Properties changedExit the Configuration Utility.

13. On the RAID Properties changed menu, select the option and press enter.

14. The setup utility displays a screen that indicates the disks are Resyncing. Itcan take up to 12 hours on a 146 GB disk, so it is recommended that you exitthe utility. When finished, the RAID Status changes from Resyncing toOptimal indicating a good mirror.

15. Press Esc to return to the top-level menu and then press Esc again to exit thesetup utility. The setup utility displays the following:

Are you sure you want to exit?Save changes then exit this menuDiscard changes then exit this menu

16. On the Exit menu, select the Exit the Configuration Utility option and pressEnter. The system continues to boot. Each time the system is restarted theresynchronizing continues until the disks are fully synchronized.

Update the firmwareThe Firmware Update is executed automatically with the CD-ROM providedthrough SWS.

Before you begin

You have configured the SCSI RAID unit and created a disk mirror.

About this task

To update the firmware for the X3650T, use the firmware update CD-ROM. It isimportant that you do not interrupt the update process.



25/288

Procedure

1. Insert the x3650T firmware update CD-ROM into the DVD drive and reboot themachine to load the CD. The system displays the following information duringstartup:

X3650T firmware and configuration CD0123456Starting ROM-DOS ...

2. Select option 1 from the following menu to update the firmware:

] eServer x3650T Type 7980 System Update Package Disk c1.02 10/05/2005] --------------------------------------------------------------------]] A system Reboot is required after the selected option is complete:]] Choose an option.] 1) Full update of the BMC, FRUSDR and BIOS] Order of install:] BMC to version 0.53] FRU/SDR to version ES-6.6.3] BIOS to version P11.00.0089] 2) Exit to DOS] --------------------------------------------------------------------]

Choose an option:[1,2]?3. About halfway through the update, the system asks you to specify the type of

power supply installed in the machine. Enter 1 or 2 as appropriate for yourtype of power supply.

4. After the firmware update is complete, the system prompts you to remove theCD and cycle the power. Execute this step to complete the Update.

Setting up hardware for a Telephony Application ServerSet up the hardware needed for a Telephony Application Server in an IBM LotusSametime Unified Telephony deployment.

Telephony Application Server

The Telephony Application Server runs on an IBM x3550M2 using the SuSE Linux10 SP2 operating system. For technical specifications, see the Sametime UnifiedTelephony system requirements.

TAS hardware installation checklistThis section lists all the hardware requirements for the TAS.

Hardware checklist

The Telephony Application Server hardware checklist:

v Inventory and inspect the hardware.

v Locate the printed documentation and digital media for the server.

http://www-01.ibm.com/support/docview.wss?uid=swg27018591http://www-01.ibm.com/support/docview.wss?uid=swg27018591http://www-01.ibm.com/support/docview.wss?uid=swg27018591http://www-01.ibm.com/support/docview.wss?uid=swg27018591


26/288

v Perform a power on test.

v Attach the slides to the rack and place the servers onto the slides.

v Connect all six cables. Modify the SCSI RAID configuration

v Modify the server BIOS settings.

v Remote Console Startup through a Web Browser.

v Check to see if a RAID card is installed in the top full-height PCI slot of the IBMx3550M2. Refer MOP located in KMOSS how to remove the RAID controllercard.

Telephony Application Server cablingThis section describes the Telephony Application Server cabling.

v 2 x Power-Supply AC or DC (Hot swappable)

v Remote Management with Intel BMC

v Rack-optimized 1U

BIOS SettingsDuring the installation of the TAS hardware, you must also perform BIOS settings.

Before you begin

Determine that all the hardware works as expected. The Remote ManagementController (iRMC) must be configured.

About this task

You can enter the BIOS by pressing the F2 key during the Startup process.

Procedure

1. Change the Startup Sequence to the following order Boot Settings Priority:

a. IDE - DVD ROM

b. SCSI - RAID LUNc. Legacy Only

d. Remove all other boot items (such asUSB, Floppy, PSX, network) in order toavoid other possible delays or hangs during boot.

2. From Advanced IPMI LAN Settings, press enter.

3. Configure the iRMC card.

a. Disable DHCP.

b. Set the LAN port to separate.

c. Enter the IP data for the iRMC card.

4. On the Advanced screen, select Power On/Off, press Enter.

5. Check that the values are as follows:a. Software: Enabled

b. Power Button: Enabled

c. Power-On Source: Bios controlled.

d. Remote: Enabled

e. LAN: Enabled

f. Wake up Timer: Disabled

g. Wake up Mode: Daily



27/288

Supported network topologiesPlan the network interfaces that will be used by the Telephony Application Serversand the IBM WebSphere Application Servers within an IBM Lotus SametimeUnified Telephony deployment.

If the Telephony Application Server/WebSphere Application Server nodes will beused for purposes other than providing telephony services (for example, network

security or device management), you may need to use an additional networkinterface on some or all nodes in the cluster. The additional adapters will not bedefined in the Lotus Sametime Unified Telephony automation policy, so they will

be completely outside the control of SAMP. However, this additional networkinterface must be on a different subnet from the subnet used by TelephonyApplication Server and WebSphere Application Server signaling interfaces.

Example 1

v Signaling for Telephony Application Server/WebSphere Application Servernodes will be on the bond0 interface. The bond0 interface is assigned to subnetA.

v A management LAN will be on the bond1 interface. The bond1 interface is

assigned to subnet B, to keep it separate from the bond0 interface.

Example 2

v Signaling for the Telephony Application Server nodes will be on the bond0interface. The bond0 interface assigned to subnet A.

v Signaling for the WebSphere Application Server nodes will be on the bond1interface. The bond1 interface is also assigned to subnet A. Because bond0 and

bond1 are both used for signaling, they can reside on the same subnet.

v A management LAN will be on the bond2 interface. The bond2 interface isassigned to subnet B, because it must be hosted on a separate subnet from thesignaling interfaces.

The reason for this requirement is that it is not possible to have static configurednetwork interfaces in the same IP subnet as the Telephony ApplicationServer/WebSphere Application Server signaling subnet. Each IP address willrequire an entry in the kernel routing table. In the case of an interface in the samesubnet as the TAS/WAS signaling subnet, there will be 2 routes for the samesubnet. If the interface that created the second entry (in our examples, for themanagement LAN) fails, the communication for this subnet will break down even if there is another interface that still is able to communicate. As a resultSAMP will incorrectly recognize the Telephony Application Server/WebSphereApplication Server interface as broken and initiate a failover to the standby node.Keeping the signaling interfaces on a separate subnet prevents this problem.

Network considerations

When setting up a SAMP cluster, it is important to understand that all peer nodesmust have the same network interface configuration; in particular:

v If Telephony Application Server/WebSphere Application Server signaling will beon bond0, then all nodes in the cluster must have a bond0 interface.

v If Telephony Application Server signaling will be on bond0 and WebSphereApplication Server signaling on bond1, then all nodes in the cluster must have a

bond0 interface and a bond1 interface.



28/288

v If an extra interface is required (for example, for network security purposes), thisinterface must be on a separate subnet from the subnet used by TelephonyApplication Server and WebSphere Application Server.

Bonding adaptorsThe SUT cluster of TAS and Media Server systems are intended to be highlyavailable. The cluster is installed on top of cluster-failover software, called Tivoli

System Automation for Multiplatforms which is covered in detail in the Installationof TAS Software section. With reliability in mind, it is necessary to add redundancyto network ports in a TAS machine. In a failover configuration, a bond interface(bond0) using two ethernet interfaces (eth0 and eth1) must be created.

About this task

In a failover configuration a TAS machine must have:

v Two ethernet interfaces if TAS and WebSphere Application Server reside on thesame NIC

v Four ethernet interfaces if TAS and WebSphere Application Server reside onseparate NICs

v All ethernet interfaces must be on the same subnet

To decrease the likelihood of a failover condition due to a network switch, adapter,or cable failure, bonding adapters can be used to team two or more adapters.

Procedure

1. To configure bonding adapters for SUT on SLES 10 SP1/SP2, modify the ifcfgscripts in the /etc/sysconfig/network directory. By default, there is at least onefile in the form of ifcfg-eth-id-mac_address format. Example:

Default Network Configuration File Namestasnode1:/etc/sysconfig/network # ls -al ifcfg-eth*-rw-r--r-- 1 root root 211 May 17 09:00 ifcfg-eth-id-00:1a:64:62:47:d2-rw-r--r-- 1 root root 211 May 17 09:00 ifcfg-eth-id-00:1a:64:62:47:d3

2. To simplify the configuration, rename the ifcfg-eth-id- file to aformat that matches the interface name. To determine the appropriate name:execute ifconfig -a use the output to correlate the interface name to the macaddress (HWaddr). Example output from ifconfig -a. Renameifcfg-eth-id-00:1a:64:62:47:d2 to ifcfg-eth0, and ifcfg-eth-id-00:1a:64:62:47:d3 to ifcfg-eth1.

Network Interface Listtasnode1:/etc/sysconfig/network # ifconfig -a | moreeth0 Link encap:Ethernet HWaddr 00:1F:34:12:57:E2

inet addr:19.142.227.17 Bcast:19.142.227.255 Mask:255.255.252.0inet6 addr: fe80::21a:64ff:fe62:47d2/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:14532939 errors:0 dropped:0 overruns:0 frame:0

TX packets:127637196 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:2175565080 (2074.7 Mb) TX bytes:655615846 (625.2 Mb)Interrupt:90

eth1 Link encap:Ethernet HWaddr 00:1A:64:62:47:D3BROADCAST MULTICAST MTU:1500 Metric:1RX packets:0 errors:0 dropped:0 overruns:0 frame:0TX packets:0 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)Interrupt:98



29/288

3. Modify the ifcfg-eth files as appropriate for bonding. The originalconfiguration of ifcfg-eth0 looks like this example:

Default ifcfg File (ifcfg-eth0)BROADCAST=ETHTOOL_OPTIONS=MTU=NAME=NETWORK=STARTMODE=onbootUNIQUE=rBUF.OxfKyHLVUp6USERCONTROL=no_nm_name=bus-pci-0000:02:01.0BOOTPROTO=staticIPADDR=19.142.227.17NETMASK=255.255.252.0

4. For an adapter to function as a bonding slave, the configuration file must bemodified. Specifically, the STARTMODE, BOOTPROTO, IPADDR, NETMASK,MASTER, and SLAVE properties. Make the following changes to bothifcfg-eth0 and ifcfg-eth1:

a. Set STARTMODE to Off.

b. Set BOOTPROTO to None.

c. Remove IPADDR.

d. Remove NETMASK.

e. Add MASTER='bond0'.

f. Add SLAVE='yes'.

5. Create the bonding interface and associating the physical adapters as slaves.Create a file called ifcfg-bond0. The example which follows can be copied as is,with the following exceptions:

a. Update IPADDR and NETMASK as appropriate.

b. Include BONDING_SLAVEx for each physical adapter to be included in thebond pair.

c. Execute service network restart to activate the configuration. With the stepscompleted, network connectivity is not interrupted if either of the networksindependently fail.

Bonding Adapter (ifcfg-bond0)BONDING_MASTER=yesBONDING_MODULE_OPTS=mode=1 miimon=100 primary=eth0BOOTPROTO=staticBROADCAST=ETHTOOL_OPTIONS=IPADDR=19.142.227.17MTU=NAME=NETMASK=255.255.252.0NETWORK=REMOTE_IPADDR=

STARTMODE=autoUSERCONTROL=noBONDING_SLAVE0=eth0BONDING_SLAVE1=eth1

RAID unit setupDuring the installation of the TAS hardware, you must configure the SCSI RAIDand create a disk mirror.



30/288

Before you begin

You must have setup the BIOS.

About this task

You must configure the SCSI RAID unit and create a disk mirror as follows:

Procedure

1. Turn on the server. A number of screens display the system information untilan LSI banner displays and indicates that the LSI controller is initializing.

LSI Logic Corp. MPT SAS BIOSMPTBIOS-6.12.00.00 (2006.10.31)Copyright 2000-2006 LSI Logic Corp.Initializing ............

2. After initialization is complete, the system displays the following message:

LSI Logic Corp. MPT SAS BIOSMPTBIOS-6.12.00.00 (2006.10.31)Copyright 2000-2006 LSI Logic Corp.Press Ctrl-C to start LSI Logic Configuration Utility...

3. Press CTRL+C. The LSI Logic Utility Screen displays.

4. Press Enter to select the internal controller (SAS1068)

5. Press the Down Arrow Key to select RAID properties. Press Enter.

6. Select Create IM Volume and press Enter to create the array.

7. Use the Right Arrow Key to select the RAID Disk in the Slot Num 0.

8. Press the + (plus sign) key to select the drive to be placed in the array.

9. Press the D key to overwrite all existing data and create an IM array. The firstdrive is now selected.

10. Use the Down Arrow Key to select the RAID Disk in Slot Num 1.

11. Press the + (plus key) to select the second drive of the array and press the C

key to create the array.12. Create and save the new array at the system prompt.

13. Use the Down Arrow Key to select the Save changes option then exit thismenu and press enter.

14. The system processes the request which can take up to a minute.

15. Press the Esc key to exit the Adapter Properties menu. The Adapter ListGlobal Properties is displayed. Press the Esc key to exit this screen.

16. Select the Exit the Configuration Utility and Reboot option and press Enterto finish the RAID configuration. After the system reboots, the system displaysa screen that indicates the single logical volume has been created.

Start up the remote console

You can start up the remote console through a web Browser.

Before you begin

Set up the BIOS and RAID array for the TAS.

About this task

Using the web browser, log on to the Remote Console. Test the console using theVideo Redirection.



31/288

Procedure

1. Log on to the Remote Console through a web browser using the IP addressyou entered within the BIOS for the LAN settings.

2. Accept any certificate warnings that appear, enter the user name, and passwordas follows: USERID/PASSW0RD (the 0 is a zero.)

3. The Server Management Information screen appears. Select Server

Management, then Video Redirection in the navigation list on the left side.4. Start the Video Redirection using the button.

5. Accept all the certificate warnings that appear and all other messages byclicking OK.

6. At the end, a similar screen appears that reflect the console messages.

7. To finish, select Exit from the Extra drop down menu and click Ok.

SAN deploymentThe following document focuses on the setup of a SAN (Storage Area Network)system IBM DS3400. The document also describes an example environment ofmultiple TAS systems with a single standby/failover server. A SAN is a hard

requirement for this environment.

Acronyms/Terminology:

v FC: Fiber Channel: A gigabit speed network technology used to access storagenetworking. Can be either twisted pair or fiber-optic

v SAN: Storage Area Network. A disk array that is accessed with an FC

v HBA: Host Bus Adapter. The PCI card installed in the host to access the SAN orSAN switch with an FC

v Array: Set of disk drives logically grouped and associated to a RAID level

v Logical Drive: Virtual component created for the host to access an allocatedportion of the disk array

v LUN: Logical Unit Number. The logical drive identifier as it is known to theaccessing host

Hardware:

The hardware components relevant to this setup focus on the TAS and SANportion of the topology, with no details of the Sametime Server or TCS. Thesecomponents remain unchanged and are independent of a TAS and SAN. Thefollowing table includes the hardware components and reference host names forexamples used through the document.

Component Type/Model Type/Model

TAS 1 IBM xSeries 3455 stx3455d

TAS 2 IBM xSeries 3455 stx3455e

TAS 3 IBM xSeries 3455 stx3455f

TAS 4 IBM xSeries 3455 stx3455g

TAS 5 IBM xSeries 3455 stx3455h

SAN Disk System IBM DS3400 N/A

24 Port SAN Switch IBM SAN 24B-4 N/A

Architecture Overview



32/288

Logical Mappings

The following diagram details the overall architecture of Sametime UnifiedTelephony in a failover environment. HBA cards are installed on all TAS systems,including the standby systems. The TAS systems are then in a position to connectto the SAN with a SAN switch.

Note: The cluster software, SAMP, is not included in this diagram. Fulldeployment descriptions, including how the cluster software interacts with thetopology, are provided in subsequent sections. The main purpose of this section isto explain how the SAN is used.

Configuring SAN LUNs:

The following diagram provides an example logical mapping of hosts/partitionstoSAN LUNs. The SAN is broken up into logical disk arrays which the HBA (host

bus adapter) cards on the TAS servers access with standard SATA drive mappings,for example, sda and sdb. The table provides an example host-to-LUN mapping,along with their associated array allocations. For example, the TAS residing onstx3455b mounts the /enterprise directory with the SATA drive sdb, which mapsto LUN 0 on the SAN.



33/288

The active and standby TAS systems interact with the SAN LUNs in the followingmanner:

By providing the logical mappings to each system, the standby can take over fromany system in the cluster.

Note: All systems maintain all logical mappings. If the standby takes over from afailed system, once the failed system has been repaired, for example with an OSpatch, the original active node becomes the acting standby node.



34/288

The SAN is configured using a utility called Storage Manager a simple interfacefor configuring arrays and logical drives. Use the Storage Manager utility to createnew logical drives, name logical drives, and view the logical drive name to LUNmapping. For simplicity, the SAN can be configured with a host group thatcontains all TAS servers enabling all TAS servers access to all LUNs. With thisconfiguration, mount the appropriate LUN from the appropriate machine. Thediagram provides an example array allocation, including the relevant Host Group:

Installing the QLogic HBA (Host Bus Adapter)

These instructions cover installing the Qlogic 4 Gb FC single-port PCIe HBA forSystemX adapters

Procedure

1. Install the HBA card into an empty PCI slot on the TAS.

2. Update the system to the latest RPMs.

3. Ensure that the active kernel is a valid non-debug kernel and that the driverinstallation hangs. SLES 10 SP1 kernel used: 2.6.16.54-0.2.8-bigsmp. Validateusing the uname -a command. Switch the kernel by updating the "default"integer in /boot/grub/menu.lst (second line) and reboot.

4. Download the latest QLogic driver:

a. Browse to http://www.qlogic.com.

b. Click the Downloads tab.

c. Under "QLogic Models" click operating system in the search box.

http://www.qlogic.com/http://www.qlogic.com/


35/288

d. Select Fibre Channel Adapters Linux Linux Novell SLES (32-bit).

e. Click the Go button to run the search.

f. On the results page, look in the "Drivers" table, then locate the section forthe "2.6 Kernel Drivers" and click the link for SANsurfer Linux Driver

Installer (x86/x64/IA64) to begin the download.

The SANsurfer installer includes the scli for performing operations with a CLI.It also automates all the steps necessary to install, configure, and load the HBAdrivers upon reboot.

5. Extract qlafc-linux-8.02.*-install.tgz.

6. Change to the extract qlafc-linux-8.02.*-install directory.

7. Install the drivers using ./qlinstall.

8. Reboot the system.

Updating the QLogic HBA (Host Bus Adapter)The level of the Qlogic HBA BIOS that is shipped with some systems does notsupport UEFI (such as V1.28). Update the HBA BIOS to support UEFI, and shortenstart-up time.

About this task

Download both the SANSurfer application and the Multi-boot image, and then useSANSurfer to install the image.



36/288

In this task, you will update the HBA BIOS to the following versions:

v 4GB BIOS version: 2.02

v 4GB FCode version: 2.00

v 4GB EFI version: 2.00

v Firmware version: 4.03.01

Procedure1. Download the Qlogic Multi-boot Image for 4GB FC adapters:

a. Browse to http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=25334&Contentid=69579&docid=21253.

b. Click the Agree button at the bottom of the page.

c. In the "File Download" dialog box, click Save.

d. In the "Save As" box, select a directory for storing the file, and click Save.

e. Extract the Multi-boot Image.

This step extracts several files, so you may want to extract them to asubdirectory.

2. Download the Qlogic SANSurfer Management Application for Linux:

a. Browse to http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=24816&Contentid=67882&docid=19583.

b. Click the Agree button at the bottom of the page.

c. In the "File Download" dialog box, click Save.

d. In the "Save As" box, select a directory for storing the file, and click Save.

e. Extract the SANSurfer Management Application.

f. Run the extracted file to install the SANSurfer Management Application.

g. On the "Choose a product" screen, click FC HBA GUI and ALL Agent.

3. After the SANSurfer application has installed, start it.

http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=25334&Contentid=69579&docid=21253http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=25334&Contentid=69579&docid=21253http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=25334&Contentid=69579&docid=21253http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=24816&Contentid=67882&docid=19583http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=24816&Contentid=67882&docid=19583http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=24816&Contentid=67882&docid=19583http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=24816&Contentid=67882&docid=19583http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=24816&Contentid=67882&docid=19583http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=24816&Contentid=67882&docid=19583http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=25334&Contentid=69579&docid=21253http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=25334&Contentid=69579&docid=21253http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ShowEula.aspx?resourceid=25334&Contentid=69579&docid=21253


37/288

4. In the "Enter Hostname or IP Address" box, select Local Host from the list,and then click the Connect button.

5. When prompted to start a General Configuration Wizard, click No.

6. On the left side of the SANSurfer screen, wait for the "FC HBA" tab topopulate, and then select your one of your HBA ports.

7. Click the Utilities tab, and then click Update Entire Image.



38/288

8. In the "Open" box, browse to the directory where you extracted the Multi-bootimage (Step 1), select the Q24AF169.BIN, and then click Open.

9. When prompted, type the security password for the HBA Adapter Bios, clickOK to continue, and wait for the update to complete.

The default password is "config" (contact your technical support if thepassword has been changed).



39/288

10. When the "Flash Update Complete" message appears, click OK.

Configuring the QLogic HBAThese instructions cover configuring the Qlogic 4 Gb FC single-port PCIe HBA forSystemX adapters

Procedure

1. Start SuSE Linux from the system's internal RAID.



40/288

When using X3550 M2 servers that are connected to a SAN via Qlogic adapters,you may not be able to start SuSE Linux from the system's internal RAID. Ifthis happens, enable "Legacy only" under boot manager in UEFI using thefollowing boot priority:

v CD/DVD Legacy only

v Hard disk 0

v

Hard disk 1Now you can start SuSE Linux from the RAID.

2. View the SCSI configuration and browse the SAN LUNs available using cat/proc/scsi/scsi. In this example, the SAN LUNs are accessible with scsi5.

SCSI Devicestasnode1:~ # cat /proc/scsi/scsiAttached devices:Host: scsi4 Channel: 00 Id: 00 Lun: 00

Vendor: IBM-ESXS Model: ST373455SS Rev: BA26Type: Direct-Access ANSI SCSI revision: 05

Host: scsi4 Channel: 00 Id: 01 Lun: 00Vendor: IBM-ESXS Model: ST373455SS Rev: BA26Type: Direct-Access ANSI SCSI revision: 05

Host: scsi4 Channel: 01 Id: 00 Lun: 00Vendor: LSILOGIC Model: Logical Volume Rev: 3000Type: Direct-Access ANSI SCSI revision: 02

Host: scsi5 Channel: 00 Id: 00 Lun: 00Vendor: IBM Model: 1722-600 Rev: 0914Type: Direct-Access ANSI SCSI revision: 05




Host: scsi5 Channel: 00 Id: 00 Lun: 04

Vendor: IBM Model: 1722-600 Rev: 0914Type: Direct-Access ANSI SCSI revision: 05


Host: scsi5 Channel: 00 Id: 00 Lun: 31Vendor: IBM Model: Universal Xport Rev: 0914Type: Direct-Access ANSI SCSI revision: 05

Host: scsi6 Channel: 00 Id: 00 Lun: 00Vendor: AVOCENT Model: vmDisk-CD Rev: 0.01Type: CD-ROM ANSI SCSI revision: 02

Host: scsi7 Channel: 00 Id: 00 Lun: 00Vendor: AVOCENT Model: vmDisk Rev: 0.01Type: Direct-Access ANSI SCSI revision: 02

tasnode1:~ #

3. Determine the SATA drive ID by browsing the /sys/bus/scsi/devices directoryand look for the block identifier block:sdX. In the example, the SAN is scsi5, sothe device identifiers that begin with 5 were browsed. The last integer in eachdevice directory is the LUN identifier that corresponds to the SANconfiguration. If 5:0:0:0 (LUN 0), the SATA drive is /dev/sdb block:sdb. Usethis information to determine how to mount the SAN drives on a given system.

Determine SD Identifierstasnode1:~ # cd /sys/bus/scsi/devices/tasnode1:/sys/bus/scsi/devices # ls4:0:0:0 4:0:1:0 4:1:0:0 5:0:0:0 5:0:0:1 5:0:0:2 5:0:0:35:0:0:31 5:0:0:4 5:0:0:5 6:0:0:0 7:0:0:0



41/288

tasnode1:/sys/bus/scsi/devices # ls 5\:0\:0\:0block:sdb delete driver iocounterbits ioerr_cntmodel queue_depth rescan rev scsi_disk:5:0:0:0scsi_level timeout ueventbus device_blocked generic iodone_cnt iorequest_cntpower queue_type retries scsi_device:5:0:0:0 scsi_generic:sg3state type vendortasnode1:/sys/bus/scsi/devices # ls 5\:0\:0\:1

block:sdc delete driver iocounterbits ioerr_cntmodel queue_depth rescan rev scsi_disk:5:0:0:1scsi_level timeout ueventbus device_blocked generic iodone_cnt iorequest_cntpower queue_type retries scsi_device:5:0:0:1 scsi_generic:sg4state type vendortasnode1:/sys/bus/scsi/devices # ls 5\:0\:0\:2block:sdd delete driver iocounterbits ioerr_cntmodel queue_depth rescan rev scsi_disk:5:0:0:2scsi_level timeout ueventbus device_blocked generic iodone_cnt iorequest_cntpower queue_type retries scsi_device:5:0:0:2 scsi_generic:sg5state type vendortasnode1:/sys/bus/scsi/devices # ls 5\:0\:0\:3block:sde delete driver iocounterbits ioerr_cntmodel queue_depth rescan rev scsi_disk:5:0:0:3scsi_level timeout ueventbus device_blocked generic iodone_cnt iorequest_cntpower queue_type retries scsi_device:5:0:0:3 scsi_generic:sg6state type vendortasnode1:/sys/bus/scsi/devices # ls 5\:0\:0\:4block:sdf delete driver iocounterbits ioerr_cntmodel queue_depth rescan rev scsi_disk:5:0:0:4scsi_level timeout ueventbus device_blocked generic iodone_cnt iorequest_cntpower queue_type retries scsi_device:5:0:0:4 scsi_generic:sg7state type vendortasnode1:/sys/bus/scsi/devices # ls 5\:0\:0\:5block:sdg delete driver iocounterbits ioerr_cntmodel queue_depth rescan rev scsi_disk:5:0:0:5scsi_level timeout uevent

bus device_blocked generic iodone_cnt iorequest_cntpower queue_type retries scsi_device:5:0:0:5 scsi_generic:sg8state type vendortasnode1:/sys/bus/scsi/devices #

4. Create an ext3 file system for each SATA drive using mke2fs -j /dev/sdb.Substitute /dev/sdb with the information determined from step 2. Repeat foreach drive.

5. Determine the disk identifier to use in the /etc/fstab file for mounting bybrowsing /dev/disk/by-id. In the example, scsi-3600a0b80000f14a900000368489ae610 is the disk identifier for /dev/sdb.

tasnode1:~ # cd /dev/disk/by-id/tasnode1:/dev/disk/by-id # ls -altotal 0

drwxr-xr-x 2 root root 320 Aug 7 15:03 .drwxr-xr-x 5 root root 100 Aug 7 11:03 ..lrwxrwxrwx 1 root root 9 Aug 7 11:03 edd-int13_dev80 -> ../../sdalrwxrwxrwx 1 root root 10 Aug 7 11:03 edd-int13_dev80-part1 -> ../../sda1lrwxrwxrwx 1 root root 10 Aug 7 11:03 edd-int13_dev80-part2 -> ../../sda2lrwxrwxrwx 1 root root 9 Aug 7 11:03scsi-3600508e00000000046b9ebfdf84b9a0a -> ../../sdalrwxrwxrwx 1 root root 10 Aug 7 11:03scsi-3600508e00000000046b9ebfdf84b9a0a-part1 -> ../../sda1lrwxrwxrwx 1 root root 10 Aug 7 11:03scsi-3600508e00000000046b9ebfdf84b9a0a-part2 -> ../../sda2lrwxrwxrwx 1 root root 9 Aug 7 11:03scsi-3600a0b80000f14a900000368489ae610 -> ../../sdb



42/288

lrwxrwxrwx 1 root root 9 Aug 7 11:03scsi-3600a0b80000f14a900000373489ae660 -> ../../sddlrwxrwxrwx 1 root root 9 Aug 7 11:03scsi-3600a0b80000f14a90000037e489ae6a6 -> ../../sdflrwxrwxrwx 1 root root 9 Aug 7 11:03scsi-3600a0b80000f4d2e0000019d489ad2f1 -> ../../sdclrwxrwxrwx 1 root root 9 Aug 7 11:03scsi-3600a0b80000f4d2e000001a3489ad333 -> ../../sde

lrwxrwxrwx 1 root root 9 Aug 7 11:03scsi-3600a0b80000f4d2e000001a9489ad387 -> ../../sdglrwxrwxrwx 1 root root 9 Aug 7 15:03usb-AVOCENT_vmDisk-CD_00430009CB6 -> ../../sr0lrwxrwxrwx 1 root root 9 Aug 7 15:03usb-AVOCENT_vmDisk_00430009CB6 -> ../../sdhtasnode1:/dev/disk/by-id #Disk Identifiers

6. Create fstab entries for each mount point on the file system using the diskidentifier from step 4. Specifically, create entries for /enterprise and/opt/IBM/WebSphere.

/etc/fstab Configurationtasnode1:~ # cat /etc/fstab/dev/disk/by-id/scsi-3600508e00000000046b9ebfdf84b9a0a-part2 /

ext3 acl,user_xattr 1 1proc /proc proc defaults0 0sysfs /sys sysfs noauto0 0debugfs /sys/kernel/debug debugfs noauto0 0usbfs /proc/bus/usb usbfs noauto0 0devpts /dev/pts devpts mode=0620,gid=50 0/dev/sda1 swap swap defaults 0 0/dev/disk/by-id/scsi-3600a0b80000f14a900000368489ae610 /enterpriseext3 noauto,acl,user_xattr 1 0/dev/disk/by-id/scsi-3600a0b80000f4d2e0000019d489ad2f1 /opt/IBMext3 noauto,acl,user_xattr 1 0tasnode1:~ #

7. Test the mounts by executing mount /enterprise

Configuring for MPIO (Multipath IO)Configure Linux to support Multipath IO connectivity with the SAN in an IBMLotus Sametime Unified Telephony deployment.

About this task

The example used in this topic is a 3550 M2 with a dual port Qlogic card. Bothports are connected to two different Dell EMC SAN switches. Two LUNs areconfigured on the SAN and assigned to the Qlogic WWNs.

Procedure

1. Log in to the server as root.

2. Show SCSI devices:

geatas1node2:~ # lsscsi[0:0:0:0] cd/dvd TSSTcorp CDDVDW TS-L633B IB03 /dev/sr0[4:0:0:0] disk IBM-ESXS ST9146803SS B536 -[4:0:1:0] disk IBM-ESXS ST9146803SS B536 -[4:1:1:0] disk LSILOGIC Logical Volume 3000 /dev/sda[5:0:0:0] disk DGC RAID 5 0428 /dev/sdb[5:0:0:1] disk DGC RAID 5 0428 /dev/sdc[5:0:1:0] disk DGC RAID 5 0428 /dev/sdd



43/288

[5:0:1:1] disk DGC RAID 5 0428 /dev/sde[6:0:0:0] disk DGC RAID 5 0428 /dev/sdf[6:0:0:1] disk DGC RAID 5 0428 /dev/sdg[6:0:1:0] disk DGC RAID 5 0428 /dev/sdh[6:0:1:1] disk DGC RAID 5 0428 /dev/sdi

Two LUNs are created and visible. LUN 0 is indicated by "0" as the last digit:

[5:0:0:0]

[5:0:1:0][6:0:0:0][6:0:1:0]

while LUN 1 is indicated by "1" as the last digit:

[5:0:0:1][5:0:1:1][6:0:0:1][6:0:1:1]

3. Add the multipath package using yast.

4. Insert the multipath drivers into the boot sequence:

geatas1node2:~ # insserv multipathdgeatas1node2:~ # insserv boot.multipath

5. Start the drivers:

geatas1node2:~ # /etc/init.d/boot.multipath start

Creating multipath targets donegeatas1node2:~ multipathd startStarting multipathd done

6. Start the Multipath daemon in command mode:

geatas1node2:~ # multipathd k

7. Show available commands:

multipathd> helpmultipath-tools v0.4.8 (08/02, 2007)CLI commands reference:

list|show pathslist|show maps|multipathslist|show maps|multipaths status

list|show maps|multipaths statslist|show maps|multipaths topologylist|show topologylist|show map|multipath $map topologylist|show configlist|show blacklistlist|show devicesadd path $pathremove|del path $pathadd map|multipath $mapremove|del map|multipath $mapswitch|switchgroup map|multipath $map group $groupreconfiguresuspend map|multipath $mapresume map|multipath $map

reinstate path $pathfail path $path

8. Display the generated multipath topology:

multipathd> show top36006016001802200b593f40ae042df11 dm-0 DGC,RAID 5[size=30G][features=1 queue_if_no_path][hwhandler=1 emc]\_ round-robin 0 [prio=2][active]

\_ 6:0:0:1 sdg 8:96 [active][ready]\_ 5:0:0:1 sdc 8:32 [active][ready]

\_ round-robin 0 [prio=0][enabled]\_ 6:0:1:1 sdi 8:128 [active][ready]\_ 5:0:1:1 sde 8:64 [active][ready]



44/288

36006016001802200b493f40ae042df11 dm-1 DGC,RAID 5[size=30G][features=1 queue_if_no_path][hwhandler=1 emc]\_ round-robin 0 [prio=2][active]

\_ 6:0:0:0 sdf 8:80 [active][ready]\_ 5:0:0:0 sdb 8:16 [active][ready]

\_ round-robin 0 [prio=0][enabled]\_ 6:0:1:0 sdh 8:112 [active][ready]\_ 5:0:1:0 sdd 8:48 [active][ready]

multipathd> geatas1node2:~ #geatas1node2:~ #

9. Display disks:

geatas1node2:~ # cd /dev/disk/by-idgeatas1node2:/dev/disk # ls

edd-int13_dev80edd-int13_dev80-part1edd-int13_dev80-part2scsi-3600508e000000000a8648159e62e3106scsi-3600508e000000000a8648159e62e3106-part1scsi-3600508e000000000a8648159e62e3106-part2scsi-36006016001802200b493f40ae042df11scsi-36006016001802200b593f40ae042df11

10. Create File systems:geatas1node2:/dev/disk # mkfs -j /dev/disk/by-id/scsi-6006016001802200b493f40ae0

mke2fs 1.38 (30-Jun-2005)Filesystem label=OS type: LinuxBlock size=4096 (log=2)Fragment size=4096 (log=2)3932160 inodes, 7864320 blocks393216 blocks (5.00%) reserved for the super userFirst data block=0Maximum filesystem blocks=8388608240 block groups32768 blocks per group, 32768 fragments per group16384 inodes per group

Superblock backups stored on blocks:32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,4096000

Writing inode tables doneCreating journal (32768 blocks): doneWriting superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or180 days, whichever comes first. Use tune2fs -c or -i to override.

geatas1node2:/dev/disk # mkfs -j /dev/disk/by-id/scsi-6006016001802200b593f40ae0

mke2fs 1.38 (30-Jun-2005)Filesystem label=OS type: LinuxBlock size=4096 (log=2)Fragment size=4096 (log=2)3932160 inodes, 7864320 blocks393216 blocks (5.00%) reserved for the super userFirst data block=0Maximum filesystem blocks=8388608240 block groups32768 blocks per group, 32768 fragments per group16384 inodes per groupSuperblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,4096000



45/288

Writing inode tables: doneCreating journal (32768 blocks): doneWriting superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 31 mounts or180 days, whichever comes first. Use tune2fs -c or -i to override.geatas1node2:/dev/disk #

11. Create Libraries:geatas1node2:/dev/disk # cd /geatas1node2:/ # mkdir /enterprise

geatas1node2:/ # cd /opt/[mgeatas1node2:/opt # mkdir IBMgeatas1node2:/opt # cd IBM/geatas1node2:/opt/IBM # mkdir WebSphere

12. Display disks for mounting:

geatas1node2:~ # mount /dev/disk/by-id/edd-int13_dev80edd-int13_dev80-part1edd-int13_dev80-part2scsi-3600508e000000000a8648159e62e3106

scsi-3600508e000000000a8648159e62e3106-part1scsi-3600508e000000000a8648159e62e3106-part2scsi-36006016001802200b493f40ae042df11scsi-36006016001802200b593f40ae042df11

13. Mount disks

geatas1node2:~ # mount /dev/disk/by-id/scsi-36006016001802200b493f40ae042df11 /enter

geatas1node2:~ # mount /dev/disk/by-id/scsi-36006016001802200b593f40ae042df11 /opt/I

14. Display mounted disks:

geatas1node2:~ # mount/dev/sda2 on / type reiserfs (rw,acl,user_xattr)proc on /proc type proc (rw)sysfs on /sys type sysfs (rw)

debugfs on /sys/kernel/debug type debugfs (rw)udev on /dev type tmpfs (rw)devpts on /dev/pts type devpts (rw,mode=0620,gid=5)securityfs on /sys/kernel/security type securityfs (rw)/dev/dm-1 on /enterprise type ext3 (rw)/dev/dm-0 on /opt/IBM/WebSphere type ext3 (rw)

The mounts are displayed with their new virtual names: dm-0 and dm-1

15. Display the files ystems:

geatas1node2:~ # d fFilesystem 1K-blocks Used Available Use% Mounted on/dev/sda2 140468028 13868796 126599232 10% /udev 3103544 180 3103364 1% /dev/dev/dm-1 30963708 176288 29214556 1% /enterprise/dev/dm-0 30963708 176288 29214556 1% /opt/IBM/WebSphere

geatas1node2:~ #16. Revert to normal Failover configuration for further configuration.

Software installation

Review the installation checklist, and then install TCS and TAS.

Installing Te

Date post:	03-Apr-2018
Category:	Documents
Upload:	k4lonk
View:	218 times
Download:	0 times

Sut851 Install

Documents