Teradata AWS. User Guide

User Guide

Release 4.5 B035-5220-089A August 2009

This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.

AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.

BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc.

Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation.

IBM, CICS, RACF, Tivoli, z/OS, and z/VM are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds.

LSI and Engenio are registered trademarks of LSI Corporation.

Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries.

Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.

SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc.

Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries.

Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries.

Unicode is a collective membership mark and a service mark of Unicode, Inc.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other product and company names mentioned herein may be the trademarks of their respective owners.

THEINFORMATIONCONTAINEDINTHISDOCUMENTISPROVIDEDONAN “AS-IS” BASIS, WITHOUTWARRANTYOFANYKIND, EITHER EXPRESSORIMPLIED, INCLUDINGTHEIMPLIEDWARRANTIESOFMERCHANTABILITY, FITNESSFORAPARTICULARPURPOSE, OR NON-INFRINGEMENT. SOMEJURISDICTIONSDONOTALLOWTHEEXCLUSIONOFIMPLIEDWARRANTIES, SOTHEABOVEEXCLUSION MAYNOTAPPLYTOYOU. INNOEVENTWILL TERADATA CORPORATIONBELIABLEFORANYINDIRECT, DIRECT, SPECIAL, INCIDENTAL, ORCONSEQUENTIALDAMAGES, INCLUDINGLOSTPROFITSORLOSTSAVINGS, EVENIFEXPRESSLYADVISEDOFTHEPOSSIBILITYOF SUCHDAMAGES.

The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country.

Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice.

To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please e-mail: teradata-books@lists.teradata.com

Any comments or materials (collectively referred to as “Feedback”) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback.

Purpose

The Teradata AWS User Guide, Release 4.5 (B035-5220), provides information about starting the AWS and using AWS software to manage an MPP system.

Audience

The audience for this book includes, but is not limited to: • System Administrators

• Teradata service and support personnel

Prerequisites

You should have access to, or be familiar with, the following: • Basic computer knowledge

• Experience using keyboard and mouse

• Familiarity with Graphical User Interfaces (GUIs) • An understanding of the Windows operating system • Familiarity with MPP systems and their use

Changes to This Book

The following table provides information about the initial release and any subsequent revisions made to this document.

Date Description

August 2009 Added additional APC UPS information

February 2009 Added additional information for APC UPS and UPS adapter card firmware flash; added new Measurement Graph query

January 2009 Platform update

Additional Information

Updates and supplementary information are available online.

July 2008 Teradata AWS 4.4 release; platform release October 2007 Teradata AWS 4.3.1 release; platform release June 2007 Platform update

January 2007 Teradata AWS 4.2 release; platform update September 2006 Platform release

June 2006 Teradata AWS 4.1 release

March 2006 Platform release; corrections to the backup procedures January 2006 Linux release

August 2005 Teradata AWS 4.0.1 release

April 2005 Addition of time synchronization information; updates and or enhancements to the Battery Date Information, Firmware Version Checker, Connect, and Client Connections Window commands; and updates to the Teradata AWS upgrade/migration path

December 2004 Teradata AWS 4.0 release

Date Description

http://www.teradata.com/t/ Internet site for product, service, resource, support, and other customer information

http://www.info.teradata.com/ Internet site for published Teradata customer documentation

http://infocentral.daytonoh.teradata.com/tsd-library Intranet site for published Teradata service documentation

http://infocentral.daytonoh.teradata.com/tsd-library/isupr.cfm

Section of the intranet site for Teradata service documentation specific to software installation and upgrade information

http://tssprod.teradata.com:8080/TSFS/home.do Intranet site linking to Teradata software server

Preface

Purpose . . . .3

Audience . . . .3

Prerequisites . . . .3

Changes to This Book . . . .3

Additional Information . . . .4

Chapter 1:

Teradata AWS Overview

How the AWS Works . . . 24

Discovery . . . 24

Network Communication . . . 24

AWS Software . . . 25

Non-AWS Software . . . 25

AWS Security. . . 26

Secure Default Configuration . . . 26

File Transfers and Remote Connections . . . 26

AWS Hardware . . . 27

Key Dependencies . . . 28

AWS Platforms . . . 28

Hardware Platforms and Platform Configurations . . . 28

Internet Browser Requirements . . . 29

Client Connections Window Dependencies . . . 29

Upgrades and Migration . . . 29

What’s New in Version 4.5. . . 30

Chapter 2:

Accessing the AWS and Its Software

Accessing the AWS PC, Applications, and Application Commands . . . 33

User Groups . . . 34

Remote Access . . . .34

Access to the Primary AWS PC and the Secondary AWS PC . . . .35

Logging On to the AWS. . . .36

Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature . . . . .36

Setting Up the Remote AWS Feature . . . .37

Accessing the Teradata AWS Application with Remote AWS . . . .38

Connecting to the Teradata AWS Desktop through Remote AWS. . . .39

Working with AWS Applications . . . .40

Starting Applications on the AWS . . . .40

Exiting Applications on the AWS . . . .40

Finding the Version Number of an AWS Application . . . .41

Working with the Teradata AWS Application . . . .41

Displaying/Hiding the Teradata AWS Virus Disclaimer . . . .41

Procedures for Customer Service Representatives . . . .42

User-Defined Display Settings . . . .42

User Directories . . . .42

Redundant AWS Functionality. . . .42

Using Teradata AWS Online Help . . . .43

Running X-Windows Applications on UNIX MP-RAS Nodes . . . .45

Configuring a Connection to a Teradata Database Window. . . .45

Connecting to a Teradata Database Window . . . .46

Chapter 3:

Teradata AWS Application

Main Window . . . .48

Tree View . . . .49

System, Collective, Cabinet, and Chassis Numbering . . . .51

Component Names . . . .51

Refreshing Operational States in the Tree View . . . .58

Grouping and Ungrouping Components in the Tree View. . . .59

Locating Components in the Tree View . . . .60

Expanding and Collapsing the Tree View . . . .61

Deselecting Components in the Tree View . . . .61

Tree View Pane and Windows on the AWS Desktop . . . .62

Teradata AWS Commands. . . .64

Using Teradata AWS Menus. . . .64

Using Pop-up Menus. . . .64

Teradata AWS Menus . . . .65

Selecting Multiple Components for Input to Commands . . . 71

Chapter 4:

Monitoring and Managing Events

The Event Viewer . . . 76

Event Viewer Menus . . . 77

Event Properties . . . 78

Event Details . . . 79

Event and Event Viewer Display Options. . . 82

Creating Custom Queries for Events. . . 85

Selecting Components for Custom Queries and Displaying the Custom Query Manager . . . 86

Building or Editing a Custom Query . . . 87

Saving or Overwriting a Custom Query. . . 93

Running a Custom Query . . . 94

Renaming a Custom Query. . . 94

Deleting a Custom Query . . . 95

Closing the Custom Query Manager . . . 95

Custom Event Viewer . . . 95

Custom Event Viewer Menus . . . 98

Working with the Custom Event Viewer. . . 98

Chapter 5:

Monitoring, Managing, and Escalating Faults

with the Fault Viewer

The Fault Viewer . . . 102

Fault Viewer Menus . . . 106

Fault Properties . . . 107

Fault Details . . . 109

Fault Tracking and Management . . . 111

Tracking Fault Resolution Status . . . 112

Adding Fault Journal Comments . . . 114

Closing a Fault . . . 115

Submitting a New Fault . . . 119

Fault Resolution Recommendations . . . 121

Displaying a List of Recommendations . . . 121

Submitting New Recommendations . . . .123

Editing Recommendations . . . .125

Deleting Recommendations . . . .125

Fault Viewer Display and Filtering Options . . . .125

Chapter 6:

Creating and Managing Cabinet Windows

Creating a Cabinet Window and Setting Its Display Options . . . .130

New Cabinet Window and Cabinet Window Dialog Boxes. . . .131

Changing Cabinet Window Display Options . . . .133

Cabinet Window Menu Bar . . . .134

Working with Cabinet Icons . . . .135

Selecting Icons . . . .135

Arranging Icons . . . .136

Erasing or Replacing the Contents of a Cabinet Window . . . .136

Saving, Opening, and Closing Cabinet Windows . . . .137

Chapter 7:

Checking the Health of the System

Events and System Health . . . .139

Checking Operational States of Components . . . .140

Operational States and Their Indicators . . . .142

Analyzing Events . . . .143

Faults and System Health . . . .144

Checking Fault Severities. . . .145

Fault Severities and Their Indicators . . . .146

Receiving an Alert Notification About a Fault . . . .146

Responding to a Fault . . . .147

Alerts . . . .148

AWS Alert Notification . . . .149

Chapter 8:

Viewing and Updating Component Information

Viewing Properties of Components . . . 151

Displaying an Image of Chassis Components . . . 151

Choose a Layout View . . . 153

Chassis Layout View . . . 154

Tracking Asset Information . . . 155

Viewing Asset Information . . . 155

Viewing Asset History . . . 158

Generating a Baseline of System Assets and SHR Data . . . 165

Updating Asset Information for Components in Systems with Legacy Server Management. . . 168

Tracking Chassis Measurement Information . . . 169

Viewing Measurement Information. . . 170

Viewing Measurement History . . . 173

Generating Measurement Graphs . . . 178

Using Predefined System Queries to Generate Measurement Graphs . . . 179

Using Predefined Cabinet-Level Queries to Generate Measurement Graphs . . . 185

Using Custom Queries to Generate Graphs . . . 187

Saving Queries and Graphs . . . 197

Chapter 9:

Connecting to System Components

Connecting to a CMIC Web Page . . . 199

Connecting to Components from the Tree View. . . 201

Connecting to Components from the Client Connections Window . . . 204

Setting Options for Connecting to Components . . . 205

The Client Connections Window . . . 215

Client Connections Window Menu Bar . . . 216

Working with Terminal Windows . . . 218

Working with the Connections Manager . . . 222

Client Connections Window Display Options . . . 224

Connecting to Components from the Address Book . . . 227

Working with the Address Book . . . 229

Displaying the Address Book . . . 229

Adding Entries . . . 230

Organizing and Managing Entries . . . 234

Backing Up and Restoring the Address Book . . . .237

Chapter 10:

Servicing, Maintenance, and Troubleshooting

Enabling the Locator LED of a Node or CMIC Chassis . . . .239

Replacing Hardware Components (FRUs). . . .240

Components Replaced with the Replace FRU Command . . . .241

Replacing FRU Components . . . .242

Using the FRU Replace Procedure Window . . . .244

Updating (Flashing) Firmware . . . .245

Flashing CMIC Firmware . . . .246

Flashing Fibre Channel Switch Firmware . . . .247

Flashing Ethernet Switch Firmware in Systems with SM3G . . . .248

Flashing UPS and UPS Adapter Card Firmware in Systems with SM3G . . . .248

Flashing Management Board Firmware in Systems with Legacy Server Management. . . .249

Flashing 49xx/53xx Node Management Board Firmware in Mixed-Node Cabinets . . . .250

Checking Firmware Versions. . . .251

Checking and Updating Firmware with the Firmware Version Checker . . . .252

Running the CheckFirmwareVersion Utility. . . .256

Tracking and Setting Battery Installation and Replacement Dates . . . .257

Selecting Batteries and Setting Installation Dates . . . .257

Displaying Battery Date Information and Setting Battery Installation Dates . . . .257

Running the CheckBatteries Utility . . . .261

Dumping Node Memory . . . .262

Resetting Components . . . .262

Managing System Power . . . .263

Forcing a Command to Run after a Power Check Failure . . . .264

Powering Off a System/Cabinet/Chassis . . . .264

Powering On a System/Cabinet/Chassis . . . .265

Recovering from a Power Failure . . . .266

Performing Diagnostic Tests . . . .267

UPS Power Cabling Test . . . .267

UPS Self-Test . . . .270

UPS Input Selector Test. . . .271

MLAN Integrity Test . . . .272

Accessing the BYNET Utility . . . .272

Appendix A:

Teradata AWS Command Line Interface

Access to Teradata AWS CLI Utilities . . . 275

Using the Teradata AWS CLI. . . 276

AlertRegister . . . 277 AssetInfo . . . 281 AWSHelp . . . 282 DumpMemory . . . 282 FaultUtil . . . 283 FWConfig . . . 287 MeasurementInfo . . . 289 MLANTest . . . 289 ReadSCSI . . . 290 RemComponent . . . 291 Rescan . . . 291 Reset . . . 292 SetBatteryDate . . . 292 SetFW . . . 293 SetPower . . . 294 ShowBatteries . . . 295 ShowComponents. . . 296 ShowFirmwareVersion . . . 296 ShowProperties . . . 297 UpdateStatus . . . 298 UPSTest . . . 299 ViewAssetHistory . . . 300 ViewEvents . . . 303 ViewMeasurementHistory . . . 306

Appendix B:

Configuring the System

Configuring the CheckBatteries and CheckFirmwareVersion Utilities . . . 309

Changing System and Cabinet Numbers . . . 313

Changing a System or Cabinet Number in Systems with SM3G . . . 313

Changing a System or Cabinet Number in Systems with Legacy Server Management. . . 313

Adding Components . . . .314

Adding Components to Systems with SM3G . . . .314

Adding Components to Systems with Legacy Server Management . . . .314

Removing Components . . . .315

Removing Components from Systems with SM3G . . . .315

Removing Components from Systems with Legacy Server Management . . . .316

Configuring SCSI Adapters on 48xx/52xx and 49xx/53xx Nodes . . . .316

SCSI ID Editor . . . .316

Setting SCSI IDs . . . .318

Removing SCSI IDs . . . .318

Changing Server Management IP Addresses . . . .318

Changing IP Addresses in Systems with SM3G. . . .318

Changing IP Addresses in Systems with Legacy Server Management . . . .318

AWS IP Configuration Utility . . . .321

General Tab . . . .322

Network IDs Tab . . . .323

SM3G CMIC Addresses Tab . . . .324

AWS IP Addresses . . . .325

CMIC IP Addresses . . . .326

Configuring Permissions for Members of AWS Guests . . . .326

Displaying the User Group Config Tool . . . .327

Creating and Editing an AWS Guests Group . . . .328

Deleting an AWS Guests Group . . . .331

Configuring the System Objects Server in Systems with Legacy Server Management . . . .332

Configuring Default Values for the System Objects Server . . . .332

Configuring Default Values for the Fibre Channel Switch . . . .334

Time Synchronization in Teradata Systems . . . .336

Configuring the AWS as the Time Server for the CMICs . . . .336

Appendix C:

Configuring Alerts

Guidelines for Configuring Alerts . . . .339

Configuring and Using the Fault Notification Window . . . .340

Fault Notification Window . . . .340

Working with the Fault Notification Window . . . .341

Configuring the Alert Dispatch Service User Account . . . .342

Configuring the Alert Dispatch Service . . . .342

Customizing the AWSAlert User Account . . . .344

Using the Alert Manager Mail Tab to Configure a Mail Service . . . 346

Using the Alert Manager Page Tab to Configure a Page Service . . . 348

Registering Alert Actions . . . 354

Registering Alert Match Criteria. . . 354

Registering Alert Actions. . . 355

Example: Registering an E-mail Alert Action Based on Fault Severity . . . 355

Example: Registering an E-mail Alert Action Based on a Disk Failure . . . 355

Example: Registering an Alphanumeric Page . . . 356

Examples: Registering a Program or Script . . . 356

Monitoring the Configured Alerts . . . 357

Installing and Using Fault Log Writer. . . 357

Installing Fault Log Writer . . . 357

Testing the Fault Log Writer after Installation . . . 359

Troubleshooting the Fault Log Writer after Installation . . . 360

Stopping and Restarting the FaultLogWriter Scheduled Task. . . 361

Fault Log Format . . . 362

Appendix D:

Managing the AWS Databases

AWS Databases . . . 365

Backing Up the AWS Databases . . . 366

Performing a Full Backup . . . 366

Performing a Differential Backup. . . 367

Restoring from a Backup . . . 367

Tuning the AWS Databases . . . 368

Disk Space. . . 368

Managing the Fault Database . . . 368

Appendix E:

Configuring Hardware for Secure Remote Access to the

Teradata AWS

Appendix F:

Teradata AWS Default Security Template

(SecureAWS.inf)

AWS Software Restrictions . . . .373

About the Default Security Template (SecureAWS.inf) . . . .374

Default Security Policies and Services Settings in the Template. . . .375

Default Security Policies for the Teradata AWS . . . .375

Default Services Settings for the Teradata AWS . . . .375

Applying and Validating the Template . . . .376

Changing the Template . . . .377

Changing System Settings to Support Teradata AWS Optional Functions . . . .377

Customizing Other System Settings . . . .378

Guidelines for Changing System Settings or Modifying the Template . . . .379

Additional Information . . . .379

Appendix G:

AWS Services

Appendix H:

UNIX AWS Help

Figure 1: Applications on the Teradata AWS Menu . . . 40

Figure 2: Icon Denoting Customer Service Representative Procedure . . . 42

Figure 3: Online Help Tabs . . . 43

Figure 4: Teradata AWS Application Main Window. . . 48

Figure 5: Component Names in the Tree View: Default Names . . . 52

Figure 6: Component Names in the Tree View: Aliases . . . 52

Figure 7: Component Names in the Tree View: Component IDs . . . 53

Figure 8: Generate Aliases Dialog Box . . . 55

Figure 9: Default Aliases for Four Nodes (Example) . . . 57

Figure 10: Generating Aliases for Four Nodes (Template Example) . . . 57

Figure 11: User-Defined Aliases for Four Nodes (Example). . . 57

Figure 12: Components Grouped in the Tree View. . . 59

Figure 13: Group Tree Items Dialog Box . . . 60

Figure 14: Teradata AWS Application: Menu Bar . . . 64

Figure 15: Pop-Up Menu (Example). . . 64

Figure 16: Command Summary Dialog Box . . . 70

Figure 17: Command Summary and Command Output Windows. . . 70

Figure 18: Multi-Select Command Window . . . 72

Figure 19: Event Viewer . . . 78

Figure 20: Event Details Window . . . 80

Figure 21: View Events Dialog Box . . . 83

Figure 22: Custom Query Manager . . . 86

Figure 23: Build New Query Dialog Box: Conditions Tab . . . 88

Figure 24: Build New Query Dialog Box: Advanced Conditions Tab . . . 90

Figure 25: Build New Query Dialog Box: Display Columns Tab . . . 92

Figure 26: Build New Query Dialog Box: SQL Statement Tab . . . 93

Figure 27: Custom Event Viewer . . . 95

Figure 28: Fault Viewer. . . 107

Figure 29: View Fault Details Window . . . 109

Figure 30: Track Resolution Status Dialog Box . . . 113

Figure 31: Add To Journal Dialog Box . . . 114

Figure 32: Close Fault Dialog Box (Close > Selected Faults) . . . 116

Figure 34: Submit New Fault Dialog Box . . . .120

Figure 35: Fault Viewer Recommendations List (View > Recommendations). . . .122

Figure 36: Fault Viewer: Recommendations Window (Functions > View Details) . . . .122

Figure 37: Fault Viewer: Recommendations Dialog Box (Functions > Submit New Recommendation). . . .124

Figure 38: View Faults Dialog Box. . . .127

Figure 39: Cabinet Window . . . .129

Figure 40: New Cabinet Window Dialog Box (New > All Cabinets Command, New > Blank Command) and Cabinet Window (Edit > Options Command) Dialog Boxes . . . .131

Figure 41: Status Window (Example: 5550 Cabinet). . . .141

Figure 42: Collective Management Window . . . .150

Figure 43: Chassis Layout View: Window Series for Non-Disk Array Chassis . . . .152

Figure 44: Chassis Layout View: Choose a Layout View . . . .153

Figure 45: Chassis Layout View Window . . . .154

Figure 46: Asset Information Dialog Box . . . .156

Figure 47: Asset Information View Window . . . .157

Figure 48: View Asset History Dialog Box . . . .159

Figure 49: View Asset History Window . . . .161

Figure 50: Update Asset Information Dialog Box . . . .169

Figure 51: Measurement Information Dialog Box. . . .171

Figure 52: Measurement Information View Window . . . .172

Figure 53: View Measurement History Dialog Box . . . .174

Figure 54: View Measurement History Window . . . .175

Figure 55: Measurement Graph Manager (Predefined System Queries). . . .179

Figure 56: xy Graph of All Temperature Readings (Example) . . . .180

Figure 57: Bar Graph of Most Recent Temperature Readings (Example) . . . .181

Figure 58: xy Graph of All UPS Power Consumption Data (Example) . . . .182

Figure 59: Stacked Bar Graph of Most Recent UPS Power Consumption Data (Example) . . . .183

Figure 60: xy Graph of All UPS Power Output Data (Example) . . . .184

Figure 61: Measurement Graph Manager (Predefined Cabinet-Level Queries) . . . .185

Figure 62: xy Graph of All Temperature Readings for Selected Cabinet(s) (Example) . . . . .186

Figure 63: Measurement Graph Manager (Custom Queries). . . .187

Figure 64: Measurement Graph Dialog Box (Custom Queries): General Tab . . . .189

Figure 67: CMIC Service Web Page. . . 200

Figure 68: Client Connections Window . . . 204

Figure 69: New Connection Dialog Box: Window Tab . . . 205

Figure 70: New Connection Dialog Box: Connect Tab . . . 206

Figure 71: New Connection Dialog Box: Terminal Tab . . . 208

Figure 72: New Connection Dialog Box: Telnet Tab . . . 210

Figure 73: New Connection Dialog Box: SSH/SFTP Tab . . . 212

Figure 74: Key Generator Dialog Box . . . 214

Figure 75: Client Connections Window: Tabbed Layout, Connections Manager, Send To Toolbar (Example). . . 222

Figure 76: Client Connections Window Options Dialog Box. . . 225

Figure 77: Address Book Dialog Box. . . 230

Figure 78: FRU Replace Procedure Window . . . 244

Figure 79: Firmware Version Checker Window. . . 253

Figure 80: Battery Date Information Window . . . 258

Figure 81: Modify Battery Installation Date(s) Window. . . 260

Figure 82: Power Cable Test Dialog Box. . . 268

Figure 83: BYNET Utility Window . . . 273

Figure 84: DSSP Main Window . . . 274

Figure 85: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Task Tab . . . 310

Figure 86: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Schedule Tab . . . 311

Figure 87: SCSI ID Editor Dialog Box. . . 317

Figure 88: AWS IP Configuration Utility Dialog Box: General Tab. . . 322

Figure 89: AWS IP Configuration Utility Dialog Box: Network Tab . . . 323

Figure 90: AWS IP Configuration Utility Dialog Box: CMIC Addresses Tab . . . 324

Figure 91: AWS Group Permissions Configuration Dialog Box. . . 327

Figure 92: AWS Group Permissions Dialog Box . . . 328

Figure 93: System Objects Manager Properties Dialog Box: System Objects Manager Tab. . . 333

Figure 94: System Objects Manager Properties Dialog Box: Fibre Channel Switch Tab . . . 335

Figure 95: Fault Notification Window . . . 340

Figure 96: Alert Manager Properties Dialog Box: Alert Manager Mail Tab . . . 347

Figure 97: Alert Manager Properties Dialog Box: Alert Manager Page Tab . . . 349

Figure 98: Add/Remove Page Service ID Dialog Box. . . 350

Figure 99: Configure Page Service Dialog Box . . . 351

Table 1: Teradata AWS Security Features and Protocols . . . 26

Table 2: Changes and New Features in Teradata AWS 4.5 . . . 30

Table 3: Applications on the AWS Menu . . . 40

Table 4: Online Help Categories . . . 43

Table 5: Online Help Navigation Buttons . . . 44

Table 6: PC -XWare Connection Wizard . . . 45

Table 7: Description of Tree View Components and Example. . . 50

Table 8: Generate Aliases Dialog Box Description. . . 55

Table 9: Teradata AWS Options Dialog Box (Tools > Options): Component Tree Display Names . . . 58

Table 10: Teradata AWS: Commands on the Window Menu . . . 62

Table 11: Teradata AWS: Commands on AWS Menus . . . 65

Table 12: Teradata AWS: Access to Commands on AWS Menus . . . 68

Table 13: Teradata AWS: Access to Commands on Other Menus . . . 69

Table 14: Multi-Select Command Window Description. . . 72

Table 15: Event Viewer Commands . . . 77

Table 16: Event Viewer: Event Properties . . . 79

Table 17: Event Details Window Description . . . 80

Table 18: Teradata AWS Options Dialog Box (Tools > Options): Event Viewer Display Options . . . 82

Table 19: View Events Dialog Box: Event Viewer Display Options . . . 84

Table 20: Build New Query Dialog Box Description . . . 88

Table 21: Build New Query Dialog Box: Advanced Conditions Tab Description . . . 90

Table 22: Custom Event Viewer Description . . . 96

Table 23: Custom Event Viewer Commands . . . 98

Table 24: Fault Viewer Commands . . . 106

Table 25: Fault Viewer: Fault Properties . . . 108

Table 26: View Fault Window Description. . . 110

Table 27: Track Resolution Status Dialog Box Description . . . 113

Table 28: Add To Journal Dialog Box Description . . . 115

Table 29: Close Fault Dialog Box Description (Close > Selected Faults). . . 117

Table 30: Close Fault Dialog Box Description (Close > Similar Faults) . . . 118

Table 32: Fault Viewer Recommendations List Description

(View > Recommendations) . . . .122

Table 33: Fault Viewer: Recommendations Window Description (Functions > View Details) . . . .123

Table 34: Fault Viewer: Recommendations Dialog Box Description (Functions > Submit New Recommendation). . . .124

Table 35: Teradata AWS Options Dialog Box (Tools > Options): Fault Viewer Display Options . . . .126

Table 36: View Faults Dialog Box Description: Choose View Type . . . .127

Table 37: View Faults Dialog Box, Options Dialog Box: Filter Options . . . .128

Table 38: Cabinet Window Dialog Box (Edit > Options) and New Cabinet Window Dialog Box (New > All Cabinets and New > Blank Commands) Descriptions. . . .132

Table 39: Teradata AWS Options Dialog Box (Tools > Options): Cabinet Window. . . .134

Table 40: Cabinet Window Commands . . . .134

Table 41: Cabinet Window: Commands for Selecting Cabinet Icons . . . .135

Table 42: Cabinet Window: Commands for Manipulating Cabinet Icons . . . .136

Table 43: Cabinet Window: Commands for Saving, Opening, and Closing Cabinet Windows . . . .137

Table 44: Primary Operational States and Descriptions . . . .142

Table 45: Fault Severity Indicators and Descriptions . . . .146

Table 46: Alert Notification Descriptions . . . .149

Table 47: Collective Management Window Description. . . .150

Table 48: Asset Information Dialog Box Description . . . .156

Table 49: Asset Information View Window Description . . . .157

Table 50: Asset Information View Commands . . . .158

Table 51: View Asset History Dialog Box Description . . . .160

Table 52: View Asset History Window Description. . . .161

Table 53: View Asset History Commands . . . .163

Table 54: Update Asset Information Dialog Box Description . . . .169

Table 55: Measurement Information Dialog Box Description . . . .171

Table 56: Measurement Information View Window Description . . . .172

Table 57: Measurement Information View Commands . . . .172

Table 58: View Measurement History Dialog Box Description . . . .174

Table 59: View Measurement History Window Description . . . .176

Table 60: View Measurement History Commands . . . .176

Table 61: Measurement Graph Dialog Box (Custom Queries): General Tab Description . . . .189

Table 62: Measurement Graph Dialog Box (Custom Queries):

SQL Statement Tab Description . . . 193

Table 63: New Connection Dialog Box: Window Tab Description . . . 206

Table 64: New Connection Dialog Box: Connect Tab Description . . . 207

Table 65: New Connection Dialog Box: Terminal Tab Description . . . 208

Table 66: New Connection Dialog Box: Telnet Tab Description . . . 210

Table 67: New Connection Dialog Box: SSH/SFTP Tab Description . . . 212

Table 68: Key Generator Dialog Box Description . . . 214

Table 69: Client Connections Window Commands . . . 216

Table 70: Connections Manager Description . . . 223

Table 71: Teradata AWS Options Dialog Box (Tools > Options): Client Connections Window Options. . . 224

Table 72: Client Connections Window Display Options . . . 226

Table 73: FRU Replace Procedure Window Description . . . 245

Table 74: Firmware Version Checker Window Description . . . 253

Table 75: Firmware Version Checker Commands . . . 255

Table 76: Battery Date Information Window Description . . . 258

Table 77: Battery Date Information Window Commands . . . 259

Table 78: Set Battery Installation Date(s) Window and Set Battery Date Dialog Box Description . . . 260

Table 79: Resettable Components . . . 262

Table 80: Effects of Power Off Command on Components . . . 264

Table 81: Effects of Power On Command on Components . . . 265

Table 82: Power Cable Test Dialog Box Description . . . 268

Table 83: Teradata AWS: Access to CLI Utilities . . . 275

Table 84: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Task Tab Description . . . 310

Table 85: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Schedule Tab Description . . . 312

Table 86: SCSI ID Editor Description . . . 317

Table 87: AWS IP Configuration Utility Dialog Box: General Tab Description . . . 322

Table 88: AWS IP Configuration Utility Dialog Box: Network Tab Description . . . 323

Table 89: AWS IP Configuration Utility Dialog Box: CMIC Addresses Tab Description . . . 324

Table 90: AWS Group Permissions Dialog Box Description . . . 328

Table 91: System Objects Manager Properties Dialog Box: System Objects Manager Tab Description . . . 333

Table 92: System Objects Manager Properties Dialog Box:

Fibre Channel Switch Tab Description . . . .335 Table 93: Fault Notification Window Description . . . .340 Table 94: Alert Manager Properties Dialog Box: Alert Manager Mail Tab Description. . . . .347 Table 95: Alert Manager Properties Dialog Box: Alert Manager Page Tab Description. . . . .349 Table 96: Add/Remove Page Service ID Dialog Box Description. . . .350 Table 97: Configure Page Service Dialog Box Description . . . .351 Table 98: Fault Property Data in the Fault Log . . . .363 Table 99: Fault Manager Properties Dialog Box Description . . . .369 Table 100: Required Ports for AWS Web Services. . . .371 Table 101: AWS Services . . . .381 Table 102: UNIX MP-RAS AWS Commands/Functions and Windows (Teradata)

The Teradata Administration Workstation (AWS) provides a single operational view for monitoring and administering a Massively Parallel Processing (MPP) system. An MPP system is a group of Symmetric Multi-Processing (SMP) nodes, associated storage, and other hardware used to host an instance of the Teradata Database.

The AWS is designed for use by a customer’s on-site staff members, Teradata Services Analysts in the Global Support Center (GSC), and Teradata Customer Service Representatives.

If you are an experienced AWS user, use the topic “What’s New in Version 4.5” on page 30 to come up to speed on the newest AWS features. If you are new to the AWS, study the following topics to become familiar with its features.

Related Topics • How the AWS Works • AWS Software • Non-AWS Software • AWS Security • AWS Hardware • Key Dependencies • Upgrades and Migration • What’s New in Version 4.5

How the AWS Works

The single operational view presented by the AWS software depends upon information provided by server management. Server management consists of the server management chassis hardware and Cabinet Management Interface Controller (CMIC) software, and components that support Ethernet-based server management operation in the MPP system. Related Topics

• Discovery

• Network Communication

Discovery

During a process called discovery, the AWS discovers each CMIC. Each CMIC discovers the configuration and status information of the cabinets and chassis in its collective and sends the configuration and status information to the AWS. Discovery also occurs when the system configuration changes. For example, discovery occurs when a new cabinet or chassis is added to the MPP system.

Note: A collective is one or more cabinets having or sharing one CMIC.

After the discovery process completes, the information displays in the AWS software. AWS software can then be used to configure, monitor, administer, service, and maintain the MPP system. As the MPP system runs, the CMICs report events to the AWS and continue to report any configuration, operational state, or other changes to the AWS.

Related Topics • How the AWS Works

Network Communication

In systems with SM3G (Server Management 3rd Generation) architecture (5400 and later systems, 2500 and later systems), all communication between the AWS and server

management, between the AWS and the nodes, and between the CMICs and chassis, takes place through two dedicated, fully redundant server management networks: the primary Ethernet network and the secondary Ethernet network.

In systems with legacy server management (48xx/52xx and 49xx/ 53xx systems), all server management communication takes place through two dedicated, but not redundant, network connections: the service LAN (SLAN) for communication between the AWS and server management, and the private LAN (PvtLAN) for communication between the AWS and the nodes. In addition, a proprietary, fault-tolerant network for communication between CMICs and management boards (the management LAN, or MLAN) is responsible for monitoring the chassis in the MPP system.

In coexistence systems that have a mixture of SM3G and legacy server management, the MLAN still exists in systems with legacy server management. However, the system’s SLAN is

remapped to the primary Ethernet-based SM3G network, and the PvtLAN is remapped to the secondary Ethernet-based SM3G network.

Note: The Product Guide delivered with your platform contains additional information about server management and its operation.

Related Topics • How the AWS Works

AWS Software

AWS software includes the following applications and components for administering and managing the hardware in an MPP system.

Non-AWS Software

The AWS is staged and delivered with the applications necessary for proper operation installed. Installation of anything other than Teradata hardware management applications can seriously degrade system performance.

Teradata AWS • Tree View, Fault Viewer, and Event Viewer for checking system health.

• Interfaces for connecting to system components.

• Tools for maintaining and servicing the MPP system.

• Chapter 3: “Teradata AWS Application”

• Chapter 9: “Connecting to System Components”

• Chapter 10: “Servicing, Maintenance, and Troubleshooting”

AWS

Command-Line Interface (CLI)

Provides many of the same commands as the AWS GUI. The commands can be used in scripts and programs, and for remote operation.

Appendix A: “Teradata AWS Command Line Interface”

Additional AWS Software

• Additional interfaces for configuring the AWS.

• Tools for enabling and configuring AWS alert features, including the Alert Manager and AlertRegister CLI.

• Services for AWS, service subsystem, and SMP node communication.

• Appendix B: “Configuring the System.”

• Appendix C: “Configuring Alerts”

AWS Security

Secure Default Configuration

The Teradata AWS security template, implemented on AWSs staged with Release 4.1 and later, provides a baseline security configuration for the Teradata AWS. The template (SecureAWS.inf), which is based on Microsoft's Windows Server 2003 hardening guidelines, configures security policies and disables many Windows Server 2003 services that are not needed for Teradata AWS operation. In addition, most optional services, such as Microsoft Internet Information Server (IIS), are no longer installed during staging.

For more information about the security template, and applying the template at sites running Teradata AWS 4.0 or later on Windows Server 2003, see Appendix F.

File Transfers and Remote Connections

The Teradata AWS runs Windows 2003 Server and uses the following industry-standard protocols and techniques to provide secure file transfers and remote connections between the AWS and MPP system components:

• Secure Sockets Layer (SSL) • Secure Shell (SSH)

• Secure File Transfer Protocol (SFTP)

• Restricted Trivial File Transfer Protocol (TFTP) • Authentication, authorization, and auditing

The following table describes AWS security features and protocols for transferring data and connecting to system components in release 4.0 and later:

Table 1: Teradata AWS Security Features and Protocols Feature/Protocol Description/Usage

Private Networks MPP systems rely on dedicated and private primary and secondary Ethernet networks. When an MPP system is installed at a site, access to these networks is physically restricted. To ensure security, the AWS and server management components, including hubs and switches, must not be configured to route or forward messages between public networks and these private networks.

SSL The SSL protocol used with the TCP/IP socket provides 128-bit encryption and authentication between an SSL-enabled server and an SSL-enabled client. SSL replaces the use of FTP for fault communication between legacy Windows and UNIX MP-RAS nodes (clients) and the AWS (server); a proprietary protocol is used for event communication.

In AWS release 4.0 and later, a proprietary protocol is used for fault and event communication between system components and the AWS.

Related Topics • User Groups

• Access to Teradata AWS Commands

AWS Hardware

AWS software resides on a PC that is cabled to the MPP system’s primary and secondary Ethernet networks. The AWS PC also provides remote access, via modem, to the managed MPP system.

Note: The term AWS refers to AWS software, unless the AWS hardware is specifically mentioned.

Some sites may have two AWS PCs, one of which is redundant. A redundant AWS is an optional feature that increases the availability of the AWS to users and to Customer Services. If you have a redundant AWS, one AWS PC is the primary AWS, and the other is the

secondary AWS.

If you plan to add a redundant AWS to an existing system, consult your Customer Service Representative for information about configuring your system so that the primary and secondary AWSs both receive the same information from the system.

SSH SSH provides 128-bit encryption for console connections to Windows, UNIX MP-RAS, and Linux nodes from the AWS; SSH replaces Telnet on Windows and UNIX MP-RAS nodes.

Note: An SSH Server must be installed and configured on the nodes. For more information about configuring SSH Server host and private key authentication, see the OpenSSH documentation available online at http://www.openssh.org. Man pages are available on UNIX MP-RAS and Linux nodes, and an

OpenSSH-Help.htm file is available on Windows nodes.

Note: If a Telnet server is enabled on the nodes, the AWS can use Telnet to connect to UNIX MP-RAS and Windows nodes.

SFTP SFTP replaces FTP and provides authentication and 128-bit encryption for file transfers between nodes and the AWS; SFTP replaces FTP on Windows and UNIX MP-RAS nodes.

Note: FTP is no longer installed on the AWS.

Restricted TFTP In legacy systems, restricted TFTP is used to download firmware from a controlled directory on the AWS to the CMIC and management boards.

User Group Security

Access to Teradata AWS applications and AWS files is based on user group membership established through Windows 2003 file-level security. Members of AWS Users have full access to the AWS (as do Administrators), and AWS Guests have limited access to the applications and files on the AWS based on the AWS’s Function Lockout feature.

Table 1: Teradata AWS Security Features and Protocols (continued) Feature/Protocol Description/Usage

Related Topics

• Access to the Primary AWS PC and the Secondary AWS PC • Redundant AWS Functionality

Key Dependencies

The AWS software has the following key dependencies: • AWS Platforms

• Hardware Platforms and Platform Configurations • Internet Browser Requirements

• Client Connections Window Dependencies

The AWS has other dependencies that are not listed. The AWS software includes everything needed to monitor and manage an MPP system. Additional software does not need to be downloaded or added.

AWS Platforms

The Dell 1600, 1800, or 2900 is required for Teradata AWS 4.0 or later.

Hardware Platforms and Platform Configurations

Teradata AWS 4.5 software manages all TPA and non-TPA nodes in a cabinet and supports the following platforms:

• SM3G systems:

• 25xx systems (Linux)

• 5555 C/H systems (Windows 64-bit, MP-RAS, and Linux) • 5550H systems (Windows 64-bit, MP-RAS, and Linux)

• 5500C/5500H systems (Windows 32-bit and 64-bit, MP-RAS, and Linux) • 54xxE/54xxH systems (Windows 32-bit and 64-bit, MP-RAS, and Linux) • Pre-SM3G systems:

• 48xx/52xx and 49xx/53xx systems (Windows 32-bit and MP-RAS)

Teradata AWS 4.5 software is not compatible with the following pre-SM3G platforms: 3600, 5100M, and 4700/5150 systems, and 6256 disk arrays.

For information about available system configurations, see the Product and Site Preparation Guide for your platform.

Internet Browser Requirements

Online Help is best viewed with Internet Explorer 6.0 or later, but is compatible with Internet Explorer 5.5.

Remote AWS, which allows you to run the Teradata AWS remotely, has been tested with the following browsers:

• Internet Explorer 6.0 • Netscape 7.0

• Mozilla 1.7 under Windows XP • Mozilla 1.3 under Linux

Note: If you do not have a supported Java plug-in for the browser you are using, you are asked to install one the first time you use the Remote AWS feature to run the Teradata AWS remotely. If you are asked if you want to trust the applet signed by Teradata, click Yes.

Client Connections Window Dependencies

The Client Connections Window has a dependency on the J2SSH open source library, and the J2SSH open source library has a dependency on Apache’s Log4J open source library. The following information is provided as a condition of their use:

• This product includes software developed by SSHTools (http://www.sshtools.com). • This product includes software developed by the Apache Software Foundation (http://

www.apache.org).

Upgrades and Migration

Existing Windows Server 2003 Teradata AWS 4.x.x systems can be automatically upgraded to Teradata AWS 4.5. Teradata AWS 4.5 requires Windows Server 2003 Service Pack 2 and all fixes.

The following sites require a new installation of the AWS hardware and Teradata AWS 4.5: • New sites

• Sites converting an existing UNIX MP-RAS AWS to Teradata AWS version 4.5 • Sites that do not have a Dell 1600, 1800, or 2900 and whose Teradata AWS version is

earlier than version 3.3

Sites that have a Dell 1600, 1800, or 2900 and Teradata AWS version 3.3 can use the AWS upgrade kit to convert to Teradata AWS 4.5. For more information, see the Coexistence Guide for your platform.

Contact Customer Services for information about installing Teradata AWS 4.5 at your site. When upgrading to Teradata AWS 4.5:

• Applying the Windows Server 2003 Teradata AWS default security template is recommended.

• If user-defined aliases exist, they should be merged into the global (shared) aliases file. (Aliases are no longer user-specific.) When upgrading to 4.5 from 4.0.1 or earlier:

• Users with user-defined aliases are prompted to merge them into the global aliases file when they start the Teradata AWS application.

• If users merge their user-defined aliases, they are not be prompted again.

• If users do not merge their user-defined aliases, they are prompted to merge them each time they start the Teradata AWS application.

• If users disable the dialog box, their user-defined aliases are not merged into the global aliases file and are not used; they are not prompted again.

Customer Service Representatives can find additional information in the AWS package available on Teradata’s internal web server, Teradata Software Server.

What’s New in Version 4.5

The following table lists changes and new features for release 4.5 and shows where you can find more information.

Table 2: Changes and New Features in Teradata AWS 4.5

Feature or Change See:

SHR was added to the Tools > System Asset

Baseline command. “Generating a Baseline of System Assets and SHR Data” on page 165

The Tree View and Status window (Window > Status Window) were changed to show the physical location of the CMIC in the rack.

Table 7 on page 50

“Cabinet Status” on page 140

A Collective Management window (Window > Collective Management) was added to view and monitor the status of the collectives in the system.

“Checking Collective (CMIC) Status” on page 150

Cabinet ID and Chassis ID columns were added to the SM3G CMIC Addresses tab on the AWS IP Configuration Utility dialog box.

“SM3G CMIC Addresses Tab” on page 324

BYA32S chassis measurement information is now included for the following commands: • View > Measurement Information

• Event Mgmt > View Measurement History • Event Mgmt > View Measurement Graph

“Viewing Measurement Information” on page 170 “Viewing Measurement History” on page 173 “Generating Measurement Graphs” on page 178

A new measurement graph command was added to View Measurement Graph > Predefined Queries > System Queries. It measures UPS power output for all UPSs in the system.

“To Generate an xy Graph Showing UPS Power Output for All Cabinets” on page 184

The Power Cable Test command was added to the Functions menu.

“UPS Power Cabling Test” on page 267

FaultLogWriter (optional) can be added as a scheduled task; the task creates a daily log of new faults and faults whose status has changed to AutoSolved.

“Installing and Using Fault Log Writer” on page 357

Table 2: Changes and New Features in Teradata AWS 4.5 (continued)

This section helps you become familiar with command access privileges, how to connect to and log on to the AWS, and how to start AWS applications, including the Teradata AWS and its context-sensitive online Help.

Related Topics

• Accessing the AWS PC, Applications, and Application Commands

• Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature • Working with AWS Applications

• Working with the Teradata AWS Application

• Running X-Windows Applications on UNIX MP-RAS Nodes

Accessing the AWS PC, Applications, and

Application Commands

Access to the AWS PC(s), applications, and application commands is based on Windows Server 2003 file-level security.

By default, and as defined in the Teradata AWS default security template, only users with Administrator privileges can log on to the AWS locally at the console or remotely through Terminal Services/Remote Desktop. The ability to log on to the AWS is based on the Windows 2003 local security policy. If you want users who are members of AWS Users and AWS Guests to be able to log on to the AWS locally or through Terminal Services/Remote Desktop, you must modify the local security policy.

Related Topics • User Groups • Local Access • Remote Access

• Access to the Primary AWS PC and the Secondary AWS PC • Logging On to the AWS

• Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature • Access to Teradata AWS Commands

• Secure Default Configuration

User Groups

Access to the AWS PC, AWS applications, and AWS commands is based on membership in the following user groups:

• Users who are members of the following local user groups have full access to AWS applications and the commands in AWS applications:

• AWS Users

• Users with Administrator privileges

• Users who are members of the AWS Guests local user group have access to all AWS applications except the AWS Configuration application, limited access to the commands in AWS applications, and limited access to the commands available through the Command Line Interface (CLI).

Users with Administrator privileges and members of AWS Users can use the User Group Config Tool to give members of AWS Guests access to additional Teradata AWS commands.

• Users who are not members of Administrators, AWS Users or AWS Guests do not have access to AWS applications. If you log on as a user who does not have the appropriate privileges and attempt to start an application on the AWS, you are not notified that you do not have the appropriate privileges, but you cannot run any AWS applications.

Related Topics

• Access to the Primary AWS PC and the Secondary AWS PC • Access to Teradata AWS Commands

• Configuring Permissions for Members of AWS Guests

Local Access

Local access (logging on to the PC that contains the AWS software) requires one of the following:

• Administrator log in and password

• Membership in AWS Users or AWS Guests, and corresponding user name and password Related Topics

• User Groups

• Logging On to the AWS

Remote Access

You can access the AWS PC remotely:

• Through a network connection using Remote Desktop, Terminal Services, or Telnet. A Telnet client and Remote Desktop Client are installed on the AWS.

Remote access requires you to establish a connection to the AWS through a LAN or dial-in modem and one of the following:

• Administrator log in and password

• Membership in AWS Users or AWS Guests, and corresponding user name and password Use the following guidelines to determine which method to use:

• To perform tasks that require a GUI, use the Remote AWS feature, Remote Desktop, or Terminal Services.

• To perform tasks that require a CLI, use the Remote AWS feature, Remote Desktop, Terminal Services, or Telnet.

Related Topics

• Setting Up the AWS PC for Remote Access • User Groups

• Logging On to the AWS

• Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature • Connecting to the Teradata AWS Desktop through Remote AWS

Setting Up the AWS PC for Remote Access

The Teradata Administration Workstation (Teradata AWS) is shipped with Microsoft Windows Server 2003, which by default supports three concurrent sessions: two Remote Desktop sessions and one Remote Console. You can also enable the Remote AWS feature to provide access to the Teradata AWS Application for additional concurrent users.

If you want to enable additional Remote Desktop connections, you must install Terminal Server on the Teradata AWS and activate Terminal Server Client Access Licenses (TS CALs). You must use user-based CALs (TS User CALs), not device-based CALs (TS Device CALs), and at least two of the user-based CALs must be available to Teradata Corporation to provide remote support. Contact your System Service Representative for details.

CALs must be purchased from Microsoft. Contact Microsoft and follow Microsoft's installation and license activation instructions.

Access to the Primary AWS PC and the Secondary AWS PC

If you have a redundant AWS, one AWS is configured as the primary AWS, and the other is configured as the secondary AWS.

• The primary AWS is used to gain access to all management functions. It should always be made available to users who are members of the AWS Users group, or to users with Administrator privileges, so those users can perform system administration, management, servicing, and troubleshooting tasks. The primary AWS may also be configured so that it is available to users who are members of the AWS Guests group.

• When the primary AWS is up, the secondary AWS is always operated in “standby” mode. In standby mode, it should be made available only to users who are members of the AWS

Guests group so those users can monitor the system in “read-only” (function lockout) mode, but cannot issue commands.

• The secondary AWS should be configured to be available to members of the AWS Users group, or to users with Administrator privileges, so those users can gain access to

management functions if the primary AWS goes down. The secondary AWS should not be used as a primary AWS because some configuration data is not propagated between the primary AWS and the secondary AWS.

Related Topics

• Redundant AWS Functionality

Logging On to the AWS

Your group membership determines which applications and application commands you can access.

To Log On to the AWS

1 In the Log On to Windows dialog box, type your user name. 2 Type the password.

3 Click OK. Related Topics

• Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature • Accessing the AWS PC, Applications, and Application Commands

Accessing the Teradata AWS Application and

Desktop with the Remote AWS Feature

The Remote AWS feature allows you to use an Internet browser to access the Teradata AWS from any computer networked with the AWS (it allows you to run the Teradata AWS

remotely). After the Teradata AWS application displays, you can use the Functions > Connect command to connect to and display the AWS desktop, which gives you access to the AWS CLI and other AWS software.

Note: The following commands on the Tools menu are unavailable when you use the Remote AWS feature: BYNET DSSP, BYNET Utility, and, in systems with legacy server management, Manage CMIC.

Related Topics

• Setting Up the Remote AWS Feature

• Accessing the Teradata AWS Application with Remote AWS • Connecting to the Teradata AWS Desktop through Remote AWS

Setting Up the Remote AWS Feature

The first time you direct your browser to the Remote AWS page, you may be asked to install Java Web Start or another Java program that supports the Remote AWS feature. A series of dialog boxes prompt you through the installation and configuration of Java Web Start. If you do not install Java Web Start or have a Java plug-in that is compatible with Remote AWS, you cannot use the Remote AWS feature.

During the initial installation and configuration of Java Web Start, you can add a Remote AWS shortcut to your desktop. If you choose not to do so during the initial installation, you can add one later.

Note: For more information about Java Web Start, go to http://java.sun.com/products/ javawebstart.

Related Topics

• To Install and Configure Java Web Start for Remote AWS • To Add a Remote AWS Shortcut to Your Desktop

• Appendix E: “Configuring Hardware for Secure Remote Access to the Teradata AWS.” • To Access the Teradata AWS Application with Remote AWS

To Install and Configure Java Web Start for Remote AWS

1 Use the Remote AWS feature to access the Teradata AWS. 2 When the Security Warning dialog box displays, select Start.

3 When the Desktop Integration dialog box displays, do one of the following: • To add a Remote AWS shortcut to your desktop, click Yes.

Note: If you do not add the shortcut now, you can add it later.

• If you do not want to add a Remote AWS shortcut to your desktop, click No. • If you want to be prompted later for desktop integration options, click Ask Later. • To configure Java Web Start for use with other Java applications, click Configure. Use

the Configure Desktop Integration dialog box to specify how you want Java Web Start to integrate other Java applications on your desktop, then click OK.

To Add a Remote AWS Shortcut to Your Desktop

If you did not add a Remote AWS shortcut when you installed Java Web Start, you can add it later.

1 On your desktop, select Programs > Java Web Start > Java Web Start.

2 On the Java Web Start Application Manager dialog box, in the Applications field, select Remote AWS.

3 Select Application > Create Shortcuts. 4 Select File > Exit.

Accessing the Teradata AWS Application with Remote AWS

To Access the Teradata AWS Application with Remote AWS

Note: If this is the first time you accessed the connection page, and Java Web Start or another Java plug-in that supports the Remote AWS feature is not installed, a Security Warning dialog box displays.

1 Open a browser and type the following in the address field, substituting the appropriate AWS name and port number to be used for the connection:

http://<AWSName>:7756/index.htm

Note: The port number is always 7756. The <AWSName> must be the same value as the one entered in the Public Host or IP Address field of the AWS IP Configuration Utility. 2 Select Remote AWS.

3 In the AWS Login dialog box:

a Type your Administrator, AWSUser, or AWSGuest user name and password. b If applicable, type the Domain name.

Note: Configuring the Teradata AWS as part of a Windows Domain is not recommended.

Note: The Callback Address field contains the network address used by the AWS Panel Service to send responses to the Remote AWS.

4 Click Ok. The Teradata AWS application displays on your desktop. Related Topics

• Setting Up the Remote AWS Feature • AWS IP Configuration Utility • AWS Software Restrictions

Connecting to the Teradata AWS Desktop through Remote AWS

To Connect to the Teradata AWS Desktop through Remote AWS

1 Use the Remote AWS feature to access the Teradata AWS.

2 In the Tree View of the Remote AWS window, select AWS. The AWS name is in parentheses.

3 Select Functions > Connect.

4 When the Connect dialog box displays, select the connection type you want to use.

• Secure Shell (SSH): Displays the New Connection dialog box, which allows you to make a Secure Shell (SSH) connection. This option is available if an SSH server is enabled on the AWS. Port 22 is always used for SSH connections.

• Telnet: Displays the New Connection dialog box, which allows you to make a Telnet connection. This option is available if the AWS’s Telnet server is enabled. Port 23 is always used for Telnet connections.

• Terminal Services: Allows you to make a Terminal Services or Remote Desktop Client connection to the AWS. This option is available if a path to a Terminal Services Client is specified using the AWS’s Tools > Options dialog box.

5 Click Ok. The AWS desktop displays. Related Topics

• To Access the Teradata AWS Application with Remote AWS • To Set Display Options for the Client Connections Window

Working with AWS Applications

Starting Applications on the AWS

Your user name determines which applications and application commands you can access.

To Start an AWS Application

1 After logging on, select Start > Programs > Teradata AWS. 2 Select an application from the Teradata AWS menu.

Figure 1: Applications on the Teradata AWS Menu

Related Topics • User Groups

• Working with the Teradata AWS Application

Exiting Applications on the AWS

To Close an AWS Application

✔ Select the application’s File > Exit or File > Close command. Table 3: Applications on the AWS Menu

Item Description

AWS Command Prompt Displays the AWS command prompt from which you can run CLI programs

AWS Configuration Starts the AWS Configuration application, which contains the Fault Manager, Alert Manager, AWS IP Configuration, and User Group Config tools

Note: This application is unavailable to AWS Guests. If a user who is a member of the AWS Guests group attempts to start this application, an “access denied” message displays.

Client Connections

Window Displays the Client Connections Window from which you can connect to system components Teradata AWS Starts the Teradata AWS application

Finding the Version Number of an AWS Application

To Display the Current Version Number of an AWS Application

✔ If the application has a Help menu, select Help > About.

Working with the Teradata AWS Application

Related Topics

• Displaying/Hiding the Teradata AWS Virus Disclaimer • Procedures for Customer Service Representatives • User-Defined Display Settings

• User Directories

• Redundant AWS Functionality • Using Teradata AWS Online Help

Displaying/Hiding the Teradata AWS Virus Disclaimer

When you first start the Teradata AWS application, a message displays explaining that every effort has been made to insure that the AWS is free of viruses when it is delivered. The message explains the customer role in protecting the AWS from viruses after the AWS is installed at the customer site.

To Acknowledge the Virus Disclaimer and Keep It from Displaying the Next Time

1 When the virus disclaimer dialog box displays, select the Don’t display this dialog again check box to keep the message from displaying each time you start the Teradata AWS application.

2 Click Ok to acknowledge the virus disclaimer message.

To Change the Virus Disclaimer Display/Hide Setting

1 From the Teradata AWS application, select Help > Virus Message to display the dialog box. 2 Select or clear the Don’t display this dialog again check box.

Procedures for Customer Service Representatives

This document contains procedures for system administrators at customer sites and for Customer Service Representatives. The following icon denotes procedures that should be performed only by Customer Service Representatives:

Figure 2: Icon Denoting Customer Service Representative Procedure

User-Defined Display Settings

As you work with the Teradata AWS application, you may find that you want to customize some of its display options. For example, instead of using the default component names listed in the Tree View, you may want to define and use aliases for them.

Display options and other user options can be changed locally or remotely. When you set user preferences for the AWS and its applications, those settings are available the next time you log on.

User Directories

AWS data is saved by default to the Documents and Settings/<usergroup>/AWSUserData folder.

Redundant AWS Functionality

If you have a redundant AWS, all information that allows a user to monitor the MPP system displays in the Teradata AWS application on the primary AWS and the secondary AWS. This information includes, but is not limited to, events, faults, operational status, and status messages.

However, changing the appearance of the Teradata AWS GUI on one AWS does not change the appearance of the GUI on the other AWS. For example, if you arrange the windows on the primary AWS’s desktop, these changes are not propagated to the secondary AWS’s desktop. In addition, the following Teradata AWS changes are limited to the AWS on which these changes are made:

• Setting or changing an alias • Removing a component

• Performing fault operations. Fault operations include closing a fault, changing a resolution state, making a journal entry, and entering a recommendation.