Teradata AWS. User Guide

Teradata AWS User Guide Release 4.5 B035-5220-089A August 2009

The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You ve Never Seen Your Business Like 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. THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 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. Copyright 2001-2009 by Teradata Corporation. All Rights Reserved.

Preface 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 August 2009 February 2009 January 2009 September 2008 Description Added additional APC UPS information Added additional information for APC UPS and UPS adapter card firmware flash; added new Measurement Graph query Platform update Teradata AWS 4.5 release; platform update Teradata AWS User Guide, Release 4.5 3

Preface Additional Information Date July 2008 October 2007 June 2007 January 2007 September 2006 June 2006 March 2006 January 2006 August 2005 April 2005 December 2004 Description Teradata AWS 4.4 release; platform release Teradata AWS 4.3.1 release; platform release Platform update Teradata AWS 4.2 release; platform update Platform release Teradata AWS 4.1 release Platform release; corrections to the backup procedures Linux release Teradata AWS 4.0.1 release 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 Teradata AWS 4.0 release Additional Information Updates and supplementary information are available online. http://www.teradata.com/t/ http://www.info.teradata.com/ http://infocentral.daytonoh.teradata.com/tsd-library http://infocentral.daytonoh.teradata.com/tsdlibrary/isupr.cfm http://tssprod.teradata.com:8080/tsfs/home.do Internet site for product, service, resource, support, and other customer information Internet site for published Teradata customer documentation Intranet site for published Teradata service documentation Section of the intranet site for Teradata service documentation specific to software installation and upgrade information Intranet site linking to Teradata software server 4 Teradata AWS User Guide, Release 4.5

Table of Contents Preface.....................................................................3 Purpose.......................................................................3 Audience......................................................................3 Prerequisites...................................................................3 Changes to This Book............................................................3 Additional Information..........................................................4 Chapter 1: Teradata AWS Overview............................................. 23 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............................. 33 Accessing the AWS PC, Applications, and Application Commands.................... 33 User Groups.............................................................. 34 Local Access.............................................................. 34 Teradata AWS User Guide, Release 4.5 5

Table of Contents 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...........................................47 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 Access to Teradata AWS Commands...........................................68 Viewing Command Output..................................................70 6 Teradata AWS User Guide, Release 4.5

Table of Contents Selecting Multiple Components for Input to Commands......................... 71 Chapter 4: Monitoring and Managing Events................................. 75 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............................................... 101 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 Displaying Recommendation Details........................................ 122 Teradata AWS User Guide, Release 4.5 7

Table of Contents Submitting New Recommendations..........................................123 Editing Recommendations..................................................125 Deleting Recommendations.................................................125 Fault Viewer Display and Filtering Options.......................................125 Chapter 6: Creating and Managing Cabinet Windows.......................129 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...............................139 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 Checking Collective (CMIC) Status..............................................150 8 Teradata AWS User Guide, Release 4.5

Table of Contents Chapter 8: Viewing and Updating Component Information............... 151 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.............................. 199 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 Editing Entries........................................................... 236 Teradata AWS User Guide, Release 4.5 9

Table of Contents Backing Up and Restoring the Address Book...................................237 Chapter 10: Servicing, Maintenance, and Troubleshooting..................239 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 Accessing the BYNET Diagnostic Service Subsystem Program (DSSP).................273 10 Teradata AWS User Guide, Release 4.5

Table of Contents Appendix A: Teradata AWS Command Line Interface........................ 275 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............................................. 309 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 Teradata AWS User Guide, Release 4.5 11

Table of Contents 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.....................................................339 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 Configuring the Alert Manager..................................................345 12 Teradata AWS User Guide, Release 4.5

Table of Contents 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..................................... 365 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......................................................... 371 Teradata AWS User Guide, Release 4.5 13

Table of Contents Appendix F: Teradata AWS Default Security Template (SecureAWS.inf).......................................................373 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...........................................................381 Appendix H: UNIX AWS Help........................................................383 Index.....................................................................387 14 Teradata AWS User Guide, Release 4.5

List of Figures 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 33: Close Fault Dialog Box (Close > Similar Faults).......................... 118 Teradata AWS User Guide, Release 4.5 15

List of Figures 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 65: Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab......193 Figure 66: CMIC Web Page.....................................................200 16 Teradata AWS User Guide, Release 4.5

List of Figures 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 Figure 100: Fault Manager Properties Dialog Box.................................. 369 Teradata AWS User Guide, Release 4.5 17

List of Figures 18 Teradata AWS User Guide, Release 4.5

List of Tables 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 31: Submit New Fault Dialog Box Description............................... 120 Teradata AWS User Guide, Release 4.5 19

List of Tables 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 20 Teradata AWS User Guide, Release 4.5

List of Tables 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 Teradata AWS User Guide, Release 4.5 21

List of Tables 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) AWS Equivalents..............................................................383 22 Teradata AWS User Guide, Release 4.5

CHAPTER 1 Teradata AWS Overview 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. 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 Teradata AWS User Guide, Release 4.5 23

Chapter 1: Teradata AWS Overview How the AWS Works 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. 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. 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 24 Teradata AWS User Guide, Release 4.5

Chapter 1: Teradata AWS Overview AWS Software 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. How the AWS Works AWS Software AWS software includes the following applications and components for administering and managing the hardware in an MPP system. 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) Additional AWS Software Provides many of the same commands as the AWS GUI. The commands can be used in scripts and programs, and for remote operation. 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 A: Teradata AWS Command Line Interface Appendix B: Configuring the System. Appendix C: Configuring Alerts Appendix G: AWS Services 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 User Guide, Release 4.5 25

Chapter 1: Teradata AWS Overview AWS Security 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 Private Networks SSL Description/Usage 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. 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. 26 Teradata AWS User Guide, Release 4.5

Chapter 1: Teradata AWS Overview AWS Hardware Table 1: Teradata AWS Security Features and Protocols (continued) Feature/Protocol SSH SFTP Restricted TFTP User Group Security Description/Usage 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 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. In legacy systems, restricted TFTP is used to download firmware from a controlled directory on the AWS to the CMIC and management boards. 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. 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. Teradata AWS User Guide, Release 4.5 27

Chapter 1: Teradata AWS Overview Key Dependencies Access to the Primary AWS PC and the Secondary AWS PC Redundant AWS Functionality Key Dependencies AWS Platforms 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. 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. 28 Teradata AWS User Guide, Release 4.5

Chapter 1: Teradata AWS Overview Upgrades and Migration 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. Teradata AWS User Guide, Release 4.5 29

Chapter 1: Teradata AWS Overview What s New in Version 4.5 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 SHR was added to the Tools > System Asset Baseline command. The Tree View and Status window (Window > Status Window) were changed to show the physical location of the CMIC in the rack. A Collective Management window (Window > Collective Management) was added to view and monitor the status of the collectives in the system. Cabinet ID and Chassis ID columns were added to the SM3G CMIC Addresses tab on the AWS IP Configuration Utility dialog box. BYA32S chassis measurement information is now included for the following commands: View > Measurement Information Event Mgmt > View Measurement History Event Mgmt > View Measurement Graph 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. See: Generating a Baseline of System Assets and SHR Data on page 165 Table 7 on page 50 Cabinet Status on page 140 Checking Collective (CMIC) Status on page 150 SM3G CMIC Addresses Tab on page 324 Viewing Measurement Information on page 170 Viewing Measurement History on page 173 Generating Measurement Graphs on page 178 To Generate an xy Graph Showing UPS Power Output for All Cabinets on page 184 30 Teradata AWS User Guide, Release 4.5

Chapter 1: Teradata AWS Overview What s New in Version 4.5 Table 2: Changes and New Features in Teradata AWS 4.5 (continued) Feature or Change The Power Cable Test command was added to the Functions menu. 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. See: UPS Power Cabling Test on page 267 Installing and Using Fault Log Writer on page 357 Teradata AWS User Guide, Release 4.5 31

Chapter 1: Teradata AWS Overview What s New in Version 4.5 32 Teradata AWS User Guide, Release 4.5

CHAPTER 2 Accessing the AWS and Its Software 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. 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. 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 Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) Teradata AWS User Guide, Release 4.5 33

Chapter 2: Accessing the AWS and Its Software Accessing the AWS PC, Applications, and Application Commands 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. 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 Remote Access User Groups Logging On to the AWS 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. Through the Internet using the Remote AWS feature. 34 Teradata AWS User Guide, Release 4.5

Chapter 2: Accessing the AWS and Its Software Accessing the AWS PC, Applications, and Application Commands 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. 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 Teradata AWS User Guide, Release 4.5 35

Chapter 2: Accessing the AWS and Its Software Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature Logging On to 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. Redundant AWS Functionality 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. 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. Setting Up the Remote AWS Feature Accessing the Teradata AWS Application with Remote AWS Connecting to the Teradata AWS Desktop through Remote AWS 36 Teradata AWS User Guide, Release 4.5

Chapter 2: Accessing the AWS and Its Software Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature 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. 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. Teradata AWS User Guide, Release 4.5 37

Chapter 2: Accessing the AWS and Its Software Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature 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. Setting Up the Remote AWS Feature AWS IP Configuration Utility AWS Software Restrictions 38 Teradata AWS User Guide, Release 4.5

Chapter 2: Accessing the AWS and Its Software Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature 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. To Access the Teradata AWS Application with Remote AWS To Set Display Options for the Client Connections Window Teradata AWS User Guide, Release 4.5 39

Chapter 2: Accessing the AWS and Its Software Working with AWS Applications 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 Table 3: Applications on the AWS Menu Item AWS Command Prompt AWS Configuration Client Connections Window Teradata AWS Description Displays the AWS command prompt from which you can run CLI programs 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. Displays the Client Connections Window from which you can connect to system components Starts the Teradata AWS application 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. 40 Teradata AWS User Guide, Release 4.5

Chapter 2: Accessing the AWS and Its Software Working with 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 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. 3 Click Ok. Teradata AWS User Guide, Release 4.5 41

Chapter 2: Accessing the AWS and Its Software Working with the Teradata AWS Application 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 User Directories 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. 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. 42 Teradata AWS User Guide, Release 4.5

Chapter 2: Accessing the AWS and Its Software Working with the Teradata AWS Application Using Teradata AWS Online Help Help topics display in a Help window in your browser. Microsoft Internet Explorer, version 6.0 or later, is the recommended browser for viewing Help. After Help opens, you can navigate to other topics. The Teradata AWS provides the following types of Help: Help buttons on dialog boxes that display help about the dialog box. Help available from Help menus. The Teradata AWS Help menu provides the following types of help: Table 4: Online Help Categories Item AWS Help Field Level Help Fault Viewer Help Command Line Help UNIX AWS Help Description Displays online Help for the Teradata AWS application. Displays a cursor that you can use to select a GUI item in the Teradata AWS application s main window; when you select the item, a Help topic about that item appears in the Help window. Displays online Help topics for the Fault Viewer. Displays online Help for CLI programs. Displays online Help that UNIX AWS users can use to familiarize themselves with the Teradata AWS. To Find a Topic when the Help Window Is Open The left pane of the Help window contains tabs that you can use to search for Help topics. Figure 3: Online Help Tabs Click one of the following tabs: Contents: Finds a topic by category. Click a book icon to display more topics. Index: Uses an alphabetical list of keywords to find a topic. To display a topic, select the keyword. If a keyword is associated with more than one topic, select the topic from the list in the right pane. Search: Uses a search engine to find a topic. Type the word or phrase you want to search for, and then click Go. If the word or phrase occurs more than once, all matches display. Teradata AWS User Guide, Release 4.5 43

Chapter 2: Accessing the AWS and Its Software Working with the Teradata AWS Application To Navigate Help To browse Help topics, you can use the Contents tab in the left pane, the navigation buttons above each Help topic, and the Forward and Back navigation buttons in the browser. Table 5: Online Help Navigation Buttons Click: To: Locate the current topic in the Contents tab. Move up sequentially through the Help topics in the Contents tab. Move down sequentially through the Help topics in the Contents tab. Move back sequentially through previously viewed Help topics. Move forward sequentially through previously viewed Help topics. To Print a Help Topic Click the print button in the navigation bar above the topic. To Bookmark a Help Topic Click the bookmark button in the navigation bar above the topic. A bookmarked Help topic is added to the browser s Favorites menu. 44 Teradata AWS User Guide, Release 4.5

Chapter 2: Accessing the AWS and Its Software Running X-Windows Applications on UNIX MP-RAS Nodes Running X-Windows Applications on UNIX MP-RAS Nodes If your system contains UNIX MP-RAS nodes, PC-Xware software (ThinPATH Systems, Inc.) has been installed on your system to support all of the X-Window applications that reside on UNIX MP-RAS nodes, including the connection to Teradata s Database Window. Before you can connect to a Teradata Database Window, you must configure the connection. Consult your Customer Service Representative before using the software. For more information about PC-Xware, see PC-Xware s online Help or online documentation. Configuring a Connection to a Teradata Database Window Table 6: PC -XWare Connection Wizard The Connection Wizard in PC-Xware allows you to configure a connection to a Teradata Database Window. The following table shows a set of appropriate options to use. Only the command line (Screen 3) must be typed exactly as shown. The other set-up options may differ for your system. For more information about setting up connections, see PC-Xware s online Help or online documentation. Note: To invoke the Teradata Database Window, the rsh command must be functional on the UNIX node. This requires setting up the UNIX node s.rhosts file for rsh. For more information, see the UNIX man pages. Information Requested Response/Selection Screen 1 What do you want this connection to do? Execute application(s), command(s), or script(s) on a remote host Screen 2 Screen 3 Screen 4 Screen 5 What type of host will you be connecting to? Do you want to create a single connection or a set of predefined connections? Type in or choose the command line you want to execute on the remote host: Note: The response must be exactly as shown. What protocol do you want to use in making this connection? Automatically insert your PC s display name/address into the command line Do you want to specify a host now or when the connection is made? Do you want to specify a user name now or when the connection is made? Generic UNIX host Create a single connection Type the following: /usr/ntos/bin/xdbw Remote Shell (RSH) Select this option. Answer as appropriate. Answer as appropriate. Teradata AWS User Guide, Release 4.5 45

Chapter 2: Accessing the AWS and Its Software Running X-Windows Applications on UNIX MP-RAS Nodes Table 6: PC -XWare Connection Wizard (continued) Screen 6 Information Requested What do you want to call this connection? Response/Selection Type the name that you want to use for the Teradata Database Window connection. In the PC-Xware Connections window, the name you type appears next to the icon used to connect to the Teradata Database Window. Connecting to a Teradata Database Window To connect to a Teradata Database Window, use the following procedure: 1 Open the PC-Xware Connections window. 2 Click the icon that corresponds to the Teradata Database Window connection you created during Configuring a Connection to a Teradata Database Window on page 45. 46 Teradata AWS User Guide, Release 4.5

CHAPTER 3 Teradata AWS Application The Teradata AWS application allows you to monitor, manage, and maintain your system. Teradata AWS User Guide, Release 4.5 47

Chapter 3: Teradata AWS Application Main Window Main Window The following illustration identifies the main features of the Teradata AWS application s main window. When you start the Teradata AWS application, by default the Tree View displays on the left, and the Fault Viewer is on right (on the AWS desktop). Figure 4: Teradata AWS Application Main Window The features of the Teradata AWS application s main window are: Tree View: Lists the system components in a hierarchical, tree-based arrangement; the text to the right of each component shows its operating status. Menu Bar: Contains commands; commands are provided through the menu bar and in pop-up menus. 48 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Tree View Teradata AWS Desktop, which can contain the following: A Fault Viewer, which displays (by default) a list of open faults in the system, and the fault severity of each. One or more Cabinet Window(s), which display icons that represent cabinets and the AWS in the Tree View. A Status window, which displays the status of cabinet components in the system. A Collective Management window, which displays information about each CMIC in the system and the collective it manages. The windows on the AWS desktop can be hidden, minimized, or tiled on the desktop, or extracted from the desktop. Tree View Teradata AWS Commands Fault Severities and Their Indicators Cabinet Status Checking Collective (CMIC) Status Tree View Pane and Windows on the AWS Desktop Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer. Chapter 6: Creating and Managing Cabinet Windows. Chapter 7: Checking the Health of the System Tree View The Tree View displays system components in a hierarchical directory structure. The Tree View begins at the system level and branches downward to the subcomponent level. When you start the Teradata AWS, the AWS builds and displays the Tree View, and the mouse cursor changes to an hourglass to show that the AWS is busy updating the Tree View. Note: If the discovery process is in progress, the message Loading displays before the AWS builds and displays the Tree View. Teradata AWS User Guide, Release 4.5 49

Chapter 3: Teradata AWS Application Tree View Table 7: Description of Tree View Components and Example The Tree View contains the following components. The cabinets, chassis, and chassis components displayed in the Tree View depend on your system configuration (see the Product Guide for your platform). The name of the AWS that manages the system appears at the top level of the Tree View. System: A system is one or more collectives on the server management network, managed by a single AWS. It is the highest level of system organization in the Tree View. Collective(s): A collective is one or more cabinets having or sharing at least one CMIC. SM3G systems have one or more collectives, and each collective can contain one or more cabinets. Systems with legacy server management (49xx/53xx and 48xx/52xx systems) share only one collective, collective 0, and it contains all the legacy cabinets in the system. Cabinet: The cabinets that appear in the Tree View depend on your system configuration (see the Product Guide for your platform). Note: EMC disk arrays, if present, are not shown in the Tree View. Chassis: Each cabinet contains a specific set of chassis related to the cabinet s function in the system. Note: In some cabinet configurations, if a chassis listed in the Tree View is not present in the cabinet, the text MISSING appears to the right of the chassis. Note: In some cabinet configurations, there may be two CMICs. Components and Subcomponents: Chassis contain components and may contain subcomponents. How the AWS Works System, Collective, Cabinet, and Chassis Numbering Component Names Refreshing Operational States in the Tree View Grouping and Ungrouping Components in the Tree View Locating Components in the Tree View Expanding and Collapsing the Tree View Deselecting Components in the Tree View 50 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Tree View System, Collective, Cabinet, and Chassis Numbering Component Names Systems, collective, cabinets, and chassis are numbered in the Tree View. These numbers are assigned during initial configuration of the system. System Numbers: Systems cannot be numbered zero. Currently, only one system is supported. Collective Numbers: In systems with SM3G, cabinets are in one or more collectives, and the collective numbers can be any number from 1 through 511. In systems with legacy server management, all cabinets are in one collective, and the collective is always numbered zero. Cabinet Numbers: In systems with SM3G, cabinet numbers can be any number from 1 through 32. In systems with legacy server management, cabinet numbers can be any number from 1 through 511. Note: If a system with legacy server management is part of a coexistence system, a legacy cabinet number cannot match an SM3G collective number due to a BYNET configuration restriction. Chassis Numbers: Chassis numbers reflect the physical location of a chassis within a cabinet. However: In systems with SM3G, chassis are numbered from bottom to top. In systems with legacy server management, chassis are numbered from top to bottom. A chassis type (for example, a UPS) may have a different chassis number, depending on which cabinet type it is in. Chassis numbers cannot be changed. For chassis numbering conventions within cabinets, see the Product Guide for your platform. Node Cabinets with Fibre Channel Switches: In systems with SM3G, Fibre Channel switches, if present, are displayed and numbered according to their physical locations in a processing node cabinet. In systems with legacy server management, Fibre Channel switches display as the last chassis in the cabinet; the chassis number is the last octet of the Fibre Channel switch network address. It is possible to have a Fibre Channel switch with the same chassis number as that of another chassis, depending upon how its network address is configured. Each component name can be displayed in one of the following ways in the Tree View: Default Name Aliases Component ID During initial configuration of the system, the Default names, default Aliases, and Component IDs are established. The Default names display in the Tree View. Teradata AWS User Guide, Release 4.5 51

Chapter 3: Teradata AWS Application Tree View The Tools > Options command allows you to display either a Default name, an Alias, or a Component ID for components in the Tree View. Configuring Component Names Changing the Component Name in the Tree View Default Name During initial configuration of the system, a Default name is established for each component. You cannot change a Default name. Default names are in the following format in the Tree View: [Component Name] [Component Number] For example, the Default name for a system is System 1. Figure 5 shows default names for a system and collectives in the Tree View. Figure 5: Component Names in the Tree View: Default Names Aliases During initial configuration of the system, a default Alias is established for each component. A default Alias is a unique, alpha-numeric representation of a component. For example: The default Alias for a system whose Default name is System 1 is SYS.1. The default Alias for Node Power Supply 1 in System 1, Collective 200, Cabinet 5400HFC 1, Node 7 is PS.1.200.1.7.1. Figure 6 shows default aliases for a system and collectives in the Tree View. Figure 6: Component Names in the Tree View: Aliases Although you cannot change the default Alias of a component, you can configure a user-defined Alias for it. User-defined Aliases must be unique. A user-defined Alias can be a number, a word or combination of letters, or a combination of numbers and letters. 52 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Tree View If a user-defined Alias exists, and the Tools > Options command is set to Alias, the user-defined Alias displays instead of the default Alias. All user-defined aliases are stored in a shared (global) aliases file. Component ID The Component ID is a unique, alpha-numeric combination that identifies a component in the system. Depending on where a component is in the system hierarchy, its Component ID (its CIM or object path) can include a component type, system ID, collective ID, cabinet ID, chassis ID, and subcomponent ID. Figure 7 shows Component IDs for a system and collectives in the Tree View. Figure 7: Component Names in the Tree View: Component IDs The Component ID can be used as the display name in the Tree View, Event Viewer, and Event Viewer Detail window, in alert messages, and as an argument in CLI programs. The Component ID displays in the Fault Viewer and Fault Viewer Detail window as the Problem Source Instance. Configuring Component Names The Configuration > Set Aliases command configures aliases for component names. You can configure an alias for one or more selected components by typing it or automatically generating it. To Type a User-Defined Alias for a Component Name To Automatically Generate a User-Defined Alias for One or More Component Names To Change the Component Name Displayed in the Tree View Example: Generating Aliases To Type a User-Defined Alias for a Component Name 1 Use the Tree View or Functions > Multi-Select Command to select one or more components that you want to configure aliases for. 2 Select the Configuration > Set Aliases command. Teradata AWS User Guide, Release 4.5 53

Chapter 3: Teradata AWS Application Tree View 3 In the Set Aliases dialog box, in the User-Defined Alias column, double-click the field that corresponds to the component you want to define an alias for. 4 Type the alias. 5 Repeat step 3 and step 4 for each component in the Set Aliases dialog box. 6 Click Ok. To Automatically Generate a User-Defined Alias for One or More Component Names 1 Use the Tree View or Functions > Multi-Select Command to select one or more components that you want to automatically generate aliases for. The components should be of the same type. For example, all collectives, all CMICs, all nodes, and so forth. Note: If a user-defined alias already exists for a selected component, the new user-defined alias overwrites it. 2 Select the Configuration > Set Aliases command. The Set Aliases dialog box displays. 3 In the Set Aliases dialog box, select the components you want to generate aliases for. 4 In the Set Aliases dialog box, click Autogenerate. The Generate Aliases dialog box displays. 5 Using Table 8 as a reference, use the following procedure to create a template to automatically generate aliases for the components in the Selected Components field: a b c In the Generate Aliases dialog box, edit the Template field. Click Ok. The generated aliases display in the Set Aliases dialog box. On the Set Aliases dialog box, click Ok. 54 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Tree View Figure 8: Generate Aliases Dialog Box Table 8: Generate Aliases Dialog Box Description Option Selected Components Alias Components Description Contains the CIM path (component type and ID or IDs) of the components you selected. For example, the component type and ID for the default alias of a 5450 system is System.ID=1; the component type and ID for a 5450 collective is System.ID=1,ID=xx, where xx is the number of the collective. Template: By default, this field contains the template used to create the default alias or user-defined alias of the selected components. The template consists of text and macros. To create a template, you can delete all or part of the field or edit any part of the field, and you can delete any or all delimiters. Text, numbers, dots, dashes, and special characters are valid in templates. Preview: Uses the first entry in the Selected Components list to show what a generated alias would look like based on the text and macros in the Template field. As you change the text and macros in the Template field, the Preview field automatically updates to show the changes. Teradata AWS User Guide, Release 4.5 55

Chapter 3: Teradata AWS Application Tree View Table 8: Generate Aliases Dialog Box Description (continued) Option Macro button Description Displays the Select Macro dialog box The Select Macro dialog box allows you to specify a macro corresponding to a specific ID and the number of units in that macro. Macros: Contains macros that you can include in the template for the user-defined alias. Select Width: Allows you to select a Minimum Width for the ID selected in the Macros field. A preview of the result displays in the Preview field. To add the macro for the selected ID to the Template field on the Generate Aliases dialog box, click Ok. For example, to create a system ID macro with a minimum width of 3 for system 1: Select SystemID, then select 3 from the Minimum Width field. The following result displays in the Preview field of the Select Macros dialog box: 001. After you click Ok, the ID macro in the Template field on the Generate Aliases dialog box is {SystemID, 3}. Example: Generating Aliases In the example shown in Figure 9 below, the four nodes selected in To Automatically Generate a User-Defined Alias for One or More Component Names on page 54 display in the Selected Components field, the default alias template is in the Template field, and the default alias is in the Preview field. 56 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Tree View Figure 9: Default Aliases for Four Nodes (Example) To create a template that would generate an alias in the following format: SMPx-yyy-zzz where there is no SystemID, where x represents the default alias CollectiveID, where yyy represents a CabinetID with a minimum width of 3, and where zzz represents the ID of the node chassis, with a minimum width of 3 You would edit the Template field on the Generate Aliases dialog box so it looks like the one in Figure 10. You can use the Select Macro dialog box (accessible with the Macro button) to insert the macros for CollectiveID, CabinetID, and ID, or you can type them into the Template field if you are familiar with the format. Figure 10: Generating Aliases for Four Nodes (Template Example) 6 The resulting user-defined alias for all four nodes is shown in the User-Defined Alias column in the Set Aliases dialog box in Figure 11. Figure 11: User-Defined Aliases for Four Nodes (Example) Teradata AWS User Guide, Release 4.5 57

Chapter 3: Teradata AWS Application Tree View Changing the Component Name in the Tree View To Change the Component Name Displayed in the Tree View 1 In the Teradata AWS menu bar, select the Tools > Options command. 2 In the Component Tree section of the Options dialog box, select the display name you want to use. The options are described in Table 9. 3 Click Ok. Table 9: Teradata AWS Options Dialog Box (Tools > Options): Component Tree Display Names Options Description Label Names Default Alias Component ID Displays the Default names of components in the Tree View; a component s default name is assigned by server management. Displays the default Aliases of components in the Tree View; a component s default Alias is assigned by server management. If a user-defined Alias exists, it displays instead of the default Alias. Displays the Component IDs of components in the Tree View; the Component ID is assigned by server management. Refreshing Operational States in the Tree View The operational state of components in the Tree View is automatically updated. In rare instances, if the Tree View does not appear to reflect the current status of the system, you may need to use the View > Refresh or Legacy Support > Update Status command. Operational States and Their Indicators To Refresh the Operational States of Components To Re-Discover Components in Systems with Legacy Server Management and Update Their Operational States To Refresh the Operational States of Components 1 Do one of the following: To refresh the operational states of all the components in the Tree View, select the System component, or deselect all components. To refresh the operational states of one or more collectives, cabinets, chassis, or chassis subcomponents in the Tree View, select the target component or components. 2 Select the View > Refresh command. 58 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Tree View To Re-Discover Components in Systems with Legacy Server Management and Update Their Operational States 1 Select Collective 0, or one or more legacy cabinets and chassis in Collective 0. 2 Select the Legacy Support > Update Status command. Grouping and Ungrouping Components in the Tree View The View > Group Tree Items command allows you to form a group of collectives, or a group of cabinets in the same collective. The collectives or cabinets you select display in the Tree View under the group name you provide. Groups of collectives display below other collectives in the Tree View. Groups of cabinets display below other cabinets in the same collective. Grouping collectives and cabinets makes it easier to view them in the Tree View, especially in large systems. The View > Ungroup Tree Items command performs an undo operation on a group in the Tree View. Figure 12: Components Grouped in the Tree View To Form a Group of Collectives or Cabinets in the Tree View To Undo a Group of Collectives or Cabinets in the Tree View To Form a Group of Collectives or Cabinets in the Tree View 1 Select the collectives or cabinets you want to place in a group. Note: Cabinets must be in the same collective, and you cannot select collectives and cabinets. 2 In the Group Tree Items dialog box, the collectives or cabinets that form the group display at the top of the dialog box. Teradata AWS User Guide, Release 4.5 59

Chapter 3: Teradata AWS Application Tree View Figure 13: Group Tree Items Dialog Box 3 In the Group Name text box, type a name for the group. The name displays in the Tree View. 4 Click Ok. To Undo a Group of Collectives or Cabinets in the Tree View 1 Select the group name in the Tree View. 2 Select View > Ungroup. Locating Components in the Tree View The Teradata AWS Tools > Locate Component command allows you to use the Component ID, the default Alias, or an existing user-defined Alias to locate a component in the Tree View. You can obtain the Component ID from the Problem Source Instance of a fault, from an event ManagedElement, from an alert message, or from other sources. Component Names To Use the Component ID or Alias to Locate a Component To Use the Component ID or Alias to Locate a Component 1 Obtain the Component ID, default Alias, or an existing user-defined Alias. 2 From the Teradata AWS, select the Tools > Locate Component command. The Locate Component dialog box displays. 60 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Tree View 3 In the Locate Component dialog box, type the Component ID, default Alias, or user-defined Alias in the Component ID/Alias field. 4 Click Locate. If the name you typed is valid, the component that corresponds to it is highlighted in the Tree View. If the name you typed is not valid, an error message states that the component was not found. Expanding and Collapsing the Tree View Expansion indicators show that there are more components below the current level. The icons that appear to the left of components allow you to expand or collapse components in the Tree View: To Expand a Component Select the expand (+) icon to the left of the component. To Collapse a Component Select the collapse (-) icon to the left of the component. To Collapse the Tree View to the Cabinet Level Select the View > Collapse Tree View command. To Collapse or Expand Cabinet Subcomponents when a Cabinet Window Is Displayed Double-click a cabinet icon in the Cabinet Window to toggle between an expanded or collapsed view of the cabinet subcomponents. Deselecting Components in the Tree View To deselect all components selected in the Tree View, use the View > Deselect Tree Components command. Teradata AWS User Guide, Release 4.5 61

Chapter 3: Teradata AWS Application Tree View Pane and Windows on the AWS Desktop Tree View Pane and Windows on the AWS Desktop When you start the Teradata AWS, the Tree View and Fault Viewer display by default. The Tree View is in the left pane; the Fault Viewer is in the right. The right pane is called the Teradata AWS desktop. It may also contain one or more Cabinet Windows, and a Status window. The commands on the Window menu allow you to manipulate the Tree View pane and the windows on the Teradata AWS desktop and to create one or more Cabinet Windows. When you exit the Teradata AWS, Teradata AWS desktop settings are saved and used when you reopen the Teradata AWS. Table 10: Teradata AWS: Commands on the Window Menu Command Window > Tree View Window > Fault Viewer Window > Cabinet Window Window > Status Window Description Displays or hides the Tree View. The Tree View always displays in the left pane of the Teradata AWS main window. Displays or hides the Fault Viewer on the Teradata AWS desktop. The Fault Viewer displays faults for the entire system. When the Fault Viewer is on the AWS desktop, its title bar contains a Maximize button. When you use the Window > Extract command to extract the Fault Viewer from the Teradata AWS desktop, the Fault Viewer s title bar contains standard buttons for minimizing and maximizing the Fault Viewer on the Windows desktop. The Close button returns an extracted Fault Viewer to the AWS Console desktop. Displays a submenu of commands that allow you to create Cabinet Windows and open previously saved Cabinet Windows. Each Cabinet Window s title bar contains standard buttons for minimizing and maximizing the Cabinet Window on the Teradata AWS desktop, and for closing a Cabinet Window. Displays or hides the Status window on the Teradata AWS desktop. The Status window displays the status of the entire system. When the Status window is on the AWS desktop, its title bar contains a Maximize button. When you use the Window > Extract command to extract the Status window from the Teradata AWS desktop, the Status window s title bar contains standard buttons for minimizing and maximizing the Status window on the Windows desktop. The Close button returns an extracted Status window to the AWS Console desktop. 62 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Tree View Pane and Windows on the AWS Desktop Table 10: Teradata AWS: Commands on the Window Menu (continued) Command Window > Collective Management View Window > Tile Window > Extract Description Displays or hides the Collective Management window on the Teradata AWS desktop. The Collective Management window displays the status of the collectives (CMICs) in the system. When the Collective Management window is on the AWS desktop, its title bar contains a Maximize button. When you use the Window > Extract command to extract the Collective Management window from the Teradata AWS desktop, the Collective Management window s title bar contains standard buttons for minimizing and maximizing the Collective Management window on the Windows desktop. The Close button returns an extracted Collective Management window to the AWS Console desktop. Evenly distributes the Fault Viewer (if displayed), one or more Status windows (if displayed), and one or more Cabinet Windows (if displayed) on the Teradata AWS desktop. The item closest to the top of the Teradata AWS desktop displays at the top, the item second from the top displays next, and so forth. If the Fault Viewer, a Status window, or a Cabinet Window is minimized on the AWS desktop, it is not tiled. This command is available only if more than one window is open on the Teradata AWS desktop. Extracts the active window on the Teradata AWS desktop and places it on the Windows desktop. An extracted Fault Viewer or Status window can be returned to the Teradata AWS desktop by clicking the Close button on the title bar. An extracted Cabinet Window or Status window cannot be returned to the Teradata AWS desktop. To return a Cabinet Window to the Teradata AWS desktop, save it and reopen it with the Window > Cabinet Window > Open command. Chapter 6: Creating and Managing Cabinet Windows. Checking Collective (CMIC) Status Cabinet Status Teradata AWS User Guide, Release 4.5 63

Chapter 3: Teradata AWS Application Teradata AWS Commands Teradata AWS Commands Teradata AWS commands are available in the menus on the Teradata AWS menu bar, in pop-up menus, and as Command Line Interface (CLI) utilities. Your user group membership determines which commands are available to you. Figure 14: Teradata AWS Application: Menu Bar Using Teradata AWS Menus Using Pop-up Menus Teradata AWS Menus Access to Teradata AWS Commands Viewing Command Output Using Teradata AWS Menus Using Pop-up Menus Selecting Multiple Components for Input to Commands Appendix A: Teradata AWS Command Line Interface. When you select a component in the Tree View, the commands available for that component display in the menus on the Teradata AWS menu bar and in pop-up menus. If a command does not apply to the selected component, that command is unavailable. When you select more than one component, only the commands that apply to all the selected components display. General commands (such as exiting the Teradata AWS) do not require the selection of a component or components. Pop-up menus contain only the more frequently used commands available for the selected components. After selecting one or more components in the Tree View, one or more cabinet icons in a Cabinet Window, or one or more rows in some viewers, such as the Event Viewer, you can right-click the mouse button to display a pop-up menu. Figure 15: Pop-Up Menu (Example) 64 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Teradata AWS Commands When you select a single component or row, the pop-up menu contains the most frequently used commands for that component or row. When you select multiple components or rows, the pop-up menu contains only frequently used commands that can be performed on all selected components or rows. Access to Teradata AWS Commands Teradata AWS Menus Table 11: Teradata AWS: Commands on AWS Menus The File menu contains general commands. For more information, see Exiting Applications on the AWS on page 40. The View menu contains commands for working with components displayed in the Tree View. For more information, see: Refreshing Operational States in the Tree View on page 58 Deselecting Components in the Tree View on page 61 Expanding and Collapsing the Tree View on page 61 Grouping and Ungrouping Components in the Tree View on page 59 Displaying an Image of Chassis Components on page 151 Viewing Properties of Components on page 151 Viewing Asset Information on page 155 Viewing Measurement Information on page 170 Cabinet Status on page 140 The Extended Component Information command displays component-specific information provided by the vendor. Currently, only the UPS and UPS adapter card provide this information. See the vendor documentation for details. Teradata AWS User Guide, Release 4.5 65

Chapter 3: Teradata AWS Application Teradata AWS Commands Table 11: Teradata AWS: Commands on AWS Menus (continued) The Functions menu contains commands for administering the system and performing troubleshooting, servicing, and maintenance. For more information, see: Connecting to Components from the Tree View on page 201 Updating (Flashing) Firmware on page 245 Powering On a System/Cabinet/Chassis on page 265 Powering Off a System/Cabinet/Chassis on page 264 Resetting Components on page 262 Dumping Node Memory on page 262 Replacing Hardware Components (FRUs) on page 240 Performing Diagnostic Tests on page 267 Tracking and Setting Battery Installation and Replacement Dates on page 257 Connecting to a CMIC Web Page on page 199 Enabling the Locator LED of a Node or CMIC Chassis on page 239 Selecting Multiple Components for Input to Commands on page 71 The Legacy Support menu contains commands that pertain to systems with legacy server management (49xx/53xx and 48xx/52xx systems). The menu displays only if the system contains a legacy collective (Collective 0). For more information, see: Refreshing Operational States in the Tree View on page 58 Updating (Flashing) Firmware on page 245 Configuring SCSI Adapters on 48xx/52xx and 49xx/ 53xx Nodes on page 316 Updating Asset Information for Components in Systems with Legacy Server Management on page 168 Performing Diagnostic Tests on page 267 The Event Mgmt menu contains commands for monitoring the system and responding to events and faults. For more information, see: Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events on page 85 Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Viewing Asset History on page 158 Viewing Measurement History on page 173 Generating Measurement Graphs on page 178 66 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Teradata AWS Commands Table 11: Teradata AWS: Commands on AWS Menus (continued) The Configuration menu contains commands for configuring system components. For more information, see: To Type a User-Defined Alias for a Component Name on page 53 Removing Components on page 315 The Tools menu contains diagnostic commands, utilities, and commands for connecting to components. For more information, see: Generating a Baseline of System Assets and SHR Data on page 165 Accessing the BYNET Utility on page 272 Accessing the BYNET Diagnostic Service Subsystem Program (DSSP) on page 273 Connecting to Components from the Client Connections Window on page 204 Checking Firmware Versions on page 251 Tracking and Setting Battery Installation and Replacement Dates on page 257 Locating Components in the Tree View on page 60 Setting Tree View, Event Viewer, Fault Viewer, Cabinet Window, and Client Connections Window display options: To Change the Component Name Displayed in the Tree View on page 58 To Set AWS Options for the Event Viewer on page 82 To Set the AWS Option for Cabinet Windows on page 133 To Set the AWS Option for Cabinet Windows on page 133 To Set AWS Options for the Client Connections Window on page 224 The Window menu contains commands for manipulating the windows on the AWS Desktop. For more information, see: Tree View Pane and Windows on the AWS Desktop on page 62 Checking Collective (CMIC) Status on page 150 Chapter 6 Creating and Managing Cabinet Windows on page 129 Teradata AWS User Guide, Release 4.5 67

Chapter 3: Teradata AWS Application Teradata AWS Commands Table 11: Teradata AWS: Commands on AWS Menus (continued) The Help menu contains help commands and information about the application. For more information, see: Using Teradata AWS Online Help on page 43 Displaying/Hiding the Teradata AWS Virus Disclaimer on page 41 Finding the Version Number of an AWS Application on page 41 Access to Teradata AWS Commands Access to Teradata AWS commands is determined by your user group membership. AWS Users and users with Administrator privileges have full access to all the commands in Teradata AWS menus and pop-up menus, and to all Teradata AWS CLI utilities. AWS Guests have access to the commands and utilities shown in the following tables, and to the same command if it appears on a pop-up menu. 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. Table 12: Teradata AWS: Access to Commands on AWS Menus Teradata AWS Menu File View Functions Legacy Support Event Mgmt Configuration Tools Window Help Commands Available to AWS Guests by Default All commands All commands except the following: Group Tree Items Ungroup Tree Items Multi-Select Command Note: By default, from the Multi-Select Command window, AWS Guests can run only the commands listed in this table. Set SCSI IDs (limited access) Update Status All commands except the following: Custom Events Query No commands All commands All commands All commands 68 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Teradata AWS Commands Table 13: Teradata AWS: Access to Commands on Other Menus Teradata AWS Command Event Viewer Custom Event Viewer Fault Viewer Cabinet Window Client Connections Window Firmware Version Checker Asset Information View Asset History Measurement Information View Measurement History Battery Date Information Help Commands Available to AWS Guests by Default All commands No commands When viewing faults, all commands except the following: Functions > Track Resolution Status Functions > Add to Journal Functions > Close Functions > Submit New Fault When viewing recommendations, all commands except the following: Functions > Edit Functions > Delete Functions > Submit New Recommendation All commands All commands All commands except the following: Flash All commands All commands All commands All commands All commands except the following: Functions > Select All Functions > Modify All commands User Groups Configuring Permissions for Members of AWS Guests Teradata AWS User Guide, Release 4.5 69

Chapter 3: Teradata AWS Application Teradata AWS Commands Viewing Command Output Some commands display a Command Summary Window when you issue the command. The window lists the component or components the command was issued for in the Target column. If you issue a command for more than one component, each component displays on a separate line in the Command Summary dialog box. As the command runs, the command progress is updated in the Status column. Figure 16: Command Summary Dialog Box To View Detailed Command Output for a Component 1 In the displayed Command Summary dialog box, double-click the row containing the component you want to see detailed command results for. 2 Review the output in the displayed Command Output Window. The output is listed in chronological order, with the date/time the command started shown at the beginning of the entry, command progress at each step, and the time the command completed shown at the end of the entry. Figure 17: Command Summary and Command Output Windows 70 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Teradata AWS Commands Command output entries can also contain the following information. (Some commands do not contain all of the information shown below.) The name of the command and the date/time stamp when the command was issued Text identifying the component for which the command was issued Progress of the command and its functions while the command is running Details about all successes and errors related to the command Results of the command when the function or functions are complete To Set the Scrolling Option for the Command Output Window 1 From the Teradata AWS menu bar, select Tools > Options. 2 In the Command Output Window section of the Options dialog box, do one of the following: a To make the scroll bar automatically scroll to the most recent line of output, set the Automatically scroll output option. b To always display the first line of output, clear the Automatically scroll output option. When the command finishes, both options allow you to use the scroll bar to review all the output. 3 Click Ok. Selecting Multiple Components for Input to Commands The Functions > Multi-Select Command allows you to select multiple components and issue common commands for them instead of selecting individual components from the Tree View. The Constraints section of the command dialog box allows you to narrow your selection, which can be especially useful in large systems. For example, you can select all disk array management boards in a specific cabinet and flash their firmware, or you can select all nodes in a specific collective and view their asset information. Teradata AWS User Guide, Release 4.5 71

Chapter 3: Teradata AWS Application Teradata AWS Commands Figure 18: Multi-Select Command Window Table 14: Multi-Select Command Window Description Item Type SubType Function All Systems Systems All Collectives Collectives All Cabinets Cabinets Description Lists components that can be selected as a group. Lists component subtypes, if applicable, that can be selected. Lists the commands that can be executed on the selected components. Allows you to issue a command for the selected components in all systems. Allows you to issue a command for the selected components in one or more systems. You can enter one or more system numbers or a range of system numbers. If you enter more than one system number or range, they must be separated by commas, with no spaces. Allows you to issue a command for the selected components in all collectives in a system. Allows you to issue a command for the selected components in one or more collectives. You can enter one or more collective numbers or a range of collective numbers. If you enter more than one collective number or range, they must be separated by commas, with no spaces. Allows you to issue a command for the selected components in all cabinets in the system. Allows you to issue a command for the selected components in one or more cabinets. You can enter one or more cabinet numbers or a range of cabinet numbers. If you enter more than one cabinet number or range, they must be separated by commas, with no spaces. 72 Teradata AWS User Guide, Release 4.5

Chapter 3: Teradata AWS Application Teradata AWS Commands Table 14: Multi-Select Command Window Description (continued) Item All Chassis Chassis Description Allows you to issue a command for all chassis in the system. Allows you to issue a command for one or more selected chassis. You can enter one or more chassis numbers or a range of chassis numbers. If you enter more than one chassis number or range, they must be separated by commas, with no spaces. To Select Multiple Components and Issue a Command 1 From the AWS menu, select Functions > Multi-Select Command. 2 Use standard Windows selection methods (for example, Click, Ctrl + Click, Shift + Click) to select the components by Type and SubType (if applicable). Note: If you select only a Type, and subtypes are listed in the SubType field, the command you select is issued on all subtypes listed in the SubType field. 3 Do one or more of the following: a b c d Select All Systems, or, in the Systems field, type one or more system numbers or a range of system numbers. Select All Collectives, or, in the Collectives field, type one or more collective numbers or a range of collective numbers. Select All Cabinets, or, in the Cabinets field, type one or more cabinet numbers or a range of cabinet numbers. Select All Chassis, or, in the Chassis field, type one or more chassis numbers or a range of chassis numbers. 4 From the Functions list, select a command. 5 Click Execute. Teradata AWS User Guide, Release 4.5 73

Chapter 3: Teradata AWS Application Teradata AWS Commands 74 Teradata AWS User Guide, Release 4.5

CHAPTER 4 Monitoring and Managing Events In systems with SM3G server management, the CMIC in each collective collects events for all of the components in the collective and stores them in a database on the CMIC. In systems with legacy server management, the AWS collects events generated by the system and stores the events in a database on the AWS. The Event Viewer displays the events stored in the databases. The Event Viewer Event Viewer Menus Event Properties Event Details Event and Event Viewer Display Options Creating Custom Queries for Events Custom Event Viewer Managing the AWS Databases Checking the Health of the System Configuring Alerts Teradata AWS User Guide, Release 4.5 75

Chapter 4: Monitoring and Managing Events The Event Viewer The Event Viewer The Event Viewer shows events reported by server management, event logs collected from the nodes, and command actions. You can view all of the events in the system, or events for components and their subcomponents. You can open more than one Event Viewer. Event and Event Viewer Display Options To Display a Specific Number of Events (One Component Only) 1 In the Tree View, select one component. 2 Select the Event Mgmt > View Events command. 3 When the View Events dialog box displays, select Most recent. Note: The View Events dialog box does not display if the Tools > Options command has been used to clear the Prompt for Event Viewer settings option, or if you previously selected the Keep this setting and don t prompt again option on the View Events dialog box. Note: If you selected more than one component in the Tree View, the Most recent option is not available. 4 Select the number of events you want to display (25, 50, 100, 500, 1000, or 5000). 5 Click Ok to display the Event Viewer. To Display Events by Time Frame (One or More Components) 1 In the Tree View, select one or more components. 2 Select the Event Mgmt > View Events command. 3 When the View Events dialog box displays, select Events for the last. Note: The View Events dialog box does not display if the Tools > Options command has been used to clear the Prompt for Event Viewer settings option, or if you previously selected the Keep this setting and don t prompt again option on the View Events dialog box. 4 Specify the time frame. 5 Click Ok to display the Event Viewer. To Sort Events by Property To sort events by property, click the appropriate column header. To toggle between ascending and descending order, click the column heading. 76 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Event Viewer Menus To Search for Events 1 Display the Event Viewer. 2 Select the Event Viewer s Search > Find command. 3 Use the Find dialog box to search for text strings. To Locate a Component in the Tree View 1 In the Event Viewer, select an event. 2 Select the Functions > Locate Component command. To Save the Contents of the Event Viewer 1 Do one of the following: To save files in text (.txt) format, select File > Save Table > Text. Files saved in plain text format can be viewed in Notepad or a similar text editor. To save files in comma separated value (.csv) format, select File > Save Table > CSV. Files saved in this format contain individual entries, separated by commas, that can be viewed in Microsoft Excel or a similar spreadsheet application. 2 In the Save dialog box, specify a name and location for the file. To Close the Event Viewer Select the Event Viewer s File > Close command. Event Viewer Menus The following table describes the commands available from each menu in the Event Viewer menu bar. Before you can select a command, you must select the event for which you want to use the command. Table 15: Event Viewer Commands Contains general commands Allows you to search for text strings See: To Save the Contents of the Event Viewer on page 77 To Close the Event Viewer on page 77 To Search for Events on page 77 Teradata AWS User Guide, Release 4.5 77

Chapter 4: Monitoring and Managing Events Event Properties Table 15: Event Viewer Commands (continued) Contains commands to work with events displayed in the Event Viewer Note: The Next and Previous commands are available when you select Most recent on the View Events dialog box. Contains a command to locate components Event Details on page 79 To Display Events by Time Frame (One or More Components) on page 76 To Locate a Component in the Tree View on page 77. Contains commands for displaying Event Viewer help Using Teradata AWS Online Help on page 43. Access to Teradata AWS Commands Event Properties By default, the Event Viewer displays events based on the time stamp, with the most recent time stamp first. The title bar indicates which component s events are displayed. The display is updated as new events occur for the selected component or components. Each event entry contains properties associated with the event. Each column in the Event Viewer represents a specific event property. Note: In the Event Viewer shown below, Previous and Next buttons display, and, in the lower right corner, the number of events in the Event Viewer displays. The display of these items depends on which display options were set. Figure 19: Event Viewer 78 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Event Details Table 16: Event Viewer: Event Properties Column Alias Time Severity Description Definition The default Alias or CIM path for the component name. If a user-defined Alias exists, it displays instead of the default Alias. Time the event occurred. When the Event Viewer is first displayed, an arrowshaped icon appears in the Time column to indicate that the events are sorted by time, with the most recent event at the top of the list. Severity of the event being reported for the component. An event can have the following severity levels: OK: No action required; the component is operating normally. Warning: Monitor the condition; the component or subsystem is reporting a condition that does not threaten system operation, but if not remedied could worsen over time. Degraded: Investigate and correct the condition; the component or subsystem is not operating normally. Critical: Take immediate action; the component or subsystem will not continue to operate in this state. Critical conditions are often handled internally by components or subsystems, causing them to shut down Fatal: Take immediate action to return the system to its normal operating state; the component or subsystem has failed Information: The event has changed some characteristic of the subsystem, but the subsystem is operating at the same level. It can also mean that the event may have restored a previously diminished subsystem. Message describing what occurred. Event Details Event and Event Viewer Display Options Component Names Event Details When the Event Viewer displays, you can view additional details about a specific event. To View Event Details 1 Select the event in the Event Viewer. 2 Select View > Detail from the Event Viewer menu bar. An Event Details window, similar to the one shown below, displays. Some fields are displayed for all event types and others are unique to components and event types. Teradata AWS User Guide, Release 4.5 79

Chapter 4: Monitoring and Managing Events Event Details Note: You can also double-click the event in the Event Viewer to display the Event Details window. Figure 20: Event Details Window Table 17: Event Details Window Description Data Field ID TimeStamp TimeReceived Sequence Definition A unique global identifier assigned to the event record. Time and date the event occurred; for a node, the time and date the event was detected on the node. Time and date the event was received by server management. Sequence in which the event was logged. 80 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Event Details Table 17: Event Details Window Description (continued) Data Field ReporterType SubType ManagedElement ManagedElementAlias Domain MessageID Severity Description Details RequestID Data Definition The category the event belongs to: MPP_StatusEvent: an event reported for environmental conditions and significant state changes MPP_ConfigChangeEvent: an event reported for asset and setting changes MPP_CommandEvent: an event reported for commands users perform on the MPP system MPP_SnmpTrap: a trap event reported from the Fibre Channel switch and UPS MPP_BynetDPEvent: an event sent by the BYNET DP MPP_ApplicationEvent: an event reported to server management from an application MPP_Alert: an event indicating an alert condition; these events are processed by the Fault Manager MPP_WinLog: an event from the application and system logs of Windows nodes MPP_UNIXLog: an event from the ConsoleLog and StreamsError log of MP-RAS nodes or from the Syslog of Linux nodes. MPP_DeviceLog: an event from a log resident on a device; for example, a disk array MEL event An optional event type; depends on the ReporterType or the type of managed object. Examples: PostError, AssetChange, SettingChange, StreamsError, and ConsoleLog (UNIX MP-RAS nodes); Syslog (Linux nodes), Application (Windows nodes); and SLAN (legacy systems) The component for which the event occurred; this is the Component ID (the unique name assigned to the component). The default Alias of the component. The source the event originated from. In conjunction with MessageID, it uniquely identifies the type of event. An event name or message key or number unique within the Domain for a specific type of event, for example, a Windows Event ID or MP-RAS E-tag. Severity level of the event being reported for the component. The severity levels are OK, Information, Warning, Degraded, Critical, and Fatal. The severity of event indicates the level of impact to the component. Message describing the event that occurred Contains properties specific to the kind of event reported Groups a sequence of events, such as command results Hex representation of the binary data, if any Component Names Teradata AWS User Guide, Release 4.5 81

Chapter 4: Monitoring and Managing Events Event and Event Viewer Display Options Event and Event Viewer Display Options The following commands allow you to set display options for events and the Event Viewer: The Tools > Options command displays the Options dialog box for: Displaying or hiding the View Events dialog box when the Event Mgmt > View Events command is selected Changing the interval that specifies when new events are displayed in the Event Viewer Changing the maximum number of events displayed in the Event Viewer. The Event Mgmt > View Events command displays the View Events dialog box for: Specifying which events you want to display in the Event Viewer Specifying whether you want to keep the options you set each time the Event Viewer displays To Set AWS Options for the Event Viewer To Set Display Options for Events in the Event Viewer The Event Viewer To Set AWS Options for the Event Viewer 1 From the Teradata AWS menu bar, select the Tools > Options command. 2 In Event Viewer, select the options you want to use. 3 Click Ok. Table 18: Teradata AWS Options Dialog Box (Tools > Options): Event Viewer Display Options Option Prompt for Event Viewer settings Check for new events every Description This check box allows you to specify whether you want the Teradata AWS to display a dialog box that prompts you for Event Viewer settings when you select the Event Mgmt > View Events command. If the dialog box does not display, you must use the Prompt for Event Viewer settings option to redisplay it. After you set this option, the dialog box used to set Event Viewer settings displays the next time you use the Event Mgmt > View Events command. The default is checked. This list box allows you to set the time span (in seconds) elapsed before the AWS checks for and displays new events. The options are 10 (default), 15, 20, 30, 45, or 60 seconds. The default is considered to be the optimum level for system performance, and changing it may affect system performance. 82 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Event and Event Viewer Display Options Table 18: Teradata AWS Options Dialog Box (Tools > Options): Event Viewer Display Options (continued) Option Maximum Table Size Description This list box allows you to set the maximum number of events displayed in the Event Viewer. When the maximum table size is reached, a dialog box displays that contains the message Maximum table size exceeded. Oldest events have been removed from this viewer. Approximately one-third of the events are removed from the table. The options are 2,000 events (default), 5,000 events, 10,000 events, or 20,000 events. The default is considered to be the optimum level for system performance, and changing it may affect system performance. To Set Display Options for Events in the Event Viewer 1 From the Teradata AWS menu bar, select the Event Mgmt > View Events command. 2 In the View Events dialog box, set the display options you want to use. 3 Click Ok to display the Event Viewer. Figure 21: View Events Dialog Box Teradata AWS User Guide, Release 4.5 83

Chapter 4: Monitoring and Managing Events Event and Event Viewer Display Options Table 19: View Events Dialog Box: Event Viewer Display Options Options Description Events for the last Displays events for one or more components by time frame. Values from 1-60 are available from the list box on the left. The following time increments are available from the list box on the right: Second(s), Minute(s), Hour(s), Day(s). When this option is used, the Events Since field displays below the Event Viewer s menu bar: If more than one component is selected in the Tree View, the Events for field and the Events Since field display below the Event Viewer s menu bar. Next and Previous buttons are available on the Event Viewer. These buttons display the events in increasing or decreasing increments, based on the time selected in the Events for the last field. The number of events displayed also appears in the lower right corner of the Event Viewer. Note: The Events for the last option and the Most recent option operate as a toggle only one option can be selected at a time. Most recent Displays a specific number of events for one component selected in the Tree View: 25 events 50 events 100 events 500 events 1,000 events 5,000 events Next and Previous buttons are available on the Event Viewer. These buttons display the events in increasing or decreasing increments, based on the number of events selected in the Most recent field. The number of events displayed also appears in the lower right corner of the Event Viewer. Note: The Events for the last option and the Most recent option operate as a toggle only one option can be selected at a time. 84 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Table 19: View Events Dialog Box: Event Viewer Display Options (continued) Options Enable Event Type Filtering Keep this setting and don t prompt again Description When you select this option, you can select one or more of the following event types and display them in the Event Viewer: Bynet DP Commands Configuration Changes SNMP Traps Device Log Status UNIX Log (MP-RAS nodes or Linux nodes) Windows Log (Windows nodes only) Alerts The event types correspond to the ReporterType that appears in the Event Details window. For more information, see ReporterType in Table 17 on page 80. When you select this option, the next time you select the Event Mgmt > View Events command, the View Events dialog box is not displayed, and the Event Viewer is displayed using the previous options set for it. To redisplay the View Events dialog box: 1 Select the Tools > Options command. 2 In the Event Viewer section of the Options dialog box, select the Prompt for Event Viewer settings option. 3 Click Ok, then reselect the Event Mgmt > View Events command. Creating Custom Queries for Events The Event Mgmt > Custom Events Query command allows you to create and save custom queries that you can use to search the events database. This command extends the Event Viewer by allowing you to fine tune an event time and to display event database column definitions not usually shown by default. When you create custom queries, the command automatically generates appropriate SQL statements. In general, building a custom query does not require SQL knowledge. However, you can manually edit the SQL statements generated with this command; to do so, you must be familiar with SQL syntax and the event database column definitions. Selecting Components for Custom Queries and Displaying the Custom Query Manager Custom Event Viewer Teradata AWS User Guide, Release 4.5 85

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Selecting Components for Custom Queries and Displaying the Custom Query Manager To Select Components for Custom Queries and Display the Custom Query Manager 1 Select one or more components in the Tree View. 2 Select Event Mgmt > Custom Events Query. 3 When the Custom Query Manager displays, it contains a list of existing queries. You can create a new query, or modify or delete the existing queries. Figure 22: Custom Query Manager Creating Custom Queries for Events Building or Editing a Custom Query Saving or Overwriting a Custom Query Running a Custom Query Renaming a Custom Query Deleting a Custom Query Closing the Custom Query Manager 86 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Building or Editing a Custom Query When you select New from the Custom Query Manager, the Build New Query dialog box displays. Use it to create a custom query and edit the custom query or SQL statement as you build it. When you select an existing custom query from the Custom Query Manager, then select Edit, the Edit Saved Query dialog box displays. You can use the dialog box to edit the custom query or SQL statement of the existing query. The Build New Query and Edit Saved Query dialog boxes contain the same options. You must save all new or edited custom queries before you can run them. To Build or Edit a Custom Query 1 Select a component or components and display the Custom Query Manager. 2 From the Custom Query Manager, do one of the following: To build a new query, click New. To edit an existing query, select the query from the list in the Custom Query Manager, then click Edit. 3 Use the tabs to set the options you want to use for the custom query. 4 Click Ok to save the custom query. The Conditions Tab When building a new query or editing an existing query, the Conditions tab allows you to set the options described in Table 20 on page 88. After setting the options: If you are finished building or editing the query, continue with step 4 in To Build or Edit a Custom Query on page 87. If you would like to set options on the next tab, go to The Advanced Conditions Tab on page 89. Teradata AWS User Guide, Release 4.5 87

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Figure 23: Build New Query Dialog Box: Conditions Tab Table 20: Build New Query Dialog Box Description Option Description Time Selection Do not limit time Events before this time Events after this time Events between this time Events for the last Displays the most recent event first Displays events recorded before the date and time you specify in the text box Displays events recorded after the date and time you specify in the text box Displays events recorded between the two dates and times you specify in the text boxes Displays events recorded within the time frame you specify in the list (1-60 seconds, minutes, hours, or days) Number of Records Returned Limit number of records returned Specifies the total number of records to display in the Custom Event Viewer. In the text box, type the number of records you want to see. 88 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Table 20: Build New Query Dialog Box Description (continued) Option Description Event Reporter Types When you select this option, you can select one or more of the following event types and display them in the Custom Event Viewer: Bynet DP Commands Configuration Changes SNMP Traps Device Log Status UNIX Log (MP-RAS nodes or Linux nodes) Windows Log (Windows nodes only) Alerts The event types correspond to the ReporterType that appears in the Event Details window. The Advanced Conditions Tab When building a new query or editing an existing query, use the Advanced Conditions tab to specify values for event database column names. For example, to search for events that have a severity of 3 (Warning), type Severity=3 in the Custom Conditions text box. To specify more than one condition, separate the conditions with an OR or AND clause. After setting the options, you can do either of the following: If you are finished building or editing the query, continue with step 4 in To Build or Edit a Custom Query on page 87. If you would like to set options on the next tab, go to The Display Columns Tab on page 91. Teradata AWS User Guide, Release 4.5 89

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Figure 24: Build New Query Dialog Box: Advanced Conditions Tab Table 21: Build New Query Dialog Box: Advanced Conditions Tab Description Event Database Column Name Possible Values Description/Notes Example Syntax Domain Node Domain= Node ManagedElement root/ cmic:cmic_powersupply.syste mid=1,collectiveid=50,cabine tid=1,chassisid=6,id=1 ManagedElement= root/ cmic:cmic_powersupply.systemid=1,coll ectiveid=50,cabinetid=1,chassisid=6,id =1 MessageID 40000200 MessageID= 40000200 ObjectClass MPPSS_ChassisNode ObjectClass='MPPSS_ChassisNode' ReporterType MPP_BynetDPEvent ReporterType= MPP_BynetDPEvent MPP_CommandEvent MPP_ConfigChangeEvent MPP_SnmpTrap MPP_DeviceLog MPP_StatusEvent MPP_UNIXLog MPP_WinLog MPP_Alert ReporterType= MPP_CommandEvent ReporterType= MPP_ConfigChangeEvent ReporterType= MPP_SnmpTrap ReporterType= MPP_DeviceLog ReporterType= MPP_StatusEvent ReporterType= MPP_UNIXLog ReporterType= MPP_WinLog ReporterType= MPP_Alert 90 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Table 21: Build New Query Dialog Box: Advanced Conditions Tab Description (continued) Event Database Column Name Possible Values Description/Notes Example Syntax RequestID {1AA4D12F-AF27-E919-9EE1-014E1D68317B} RequestID={1AA4D12F-AF27-E919-9EE1-014E1D68317B} Sequence 1294050 Sequence=1294050 Severity 0 Unknown Severity=0 1 Ok Severity=1 2 Information Severity=2 3 Warning Severity=3 4 Degraded Severity=4 5 Critical Severity=5 6 Fatal Severity=6 SubType StreamsError SubType= StreamsError ConsoleLog TimeReceived 2006-04-25 17:44:54.0 Time stored in database is GMT TimeStamp 2006-04-25 17:44:54.0 Time stored in database is GMT SubType= ConsoleLog TimeReceived > 2006-04-25 17:44:54.0 TimeStamp > 2006-04-25 17:44:54.0 The Display Columns Tab The Description, TimeStamp, Severity, and Sequence columns are displayed in the Custom Event Viewer by default. You can use the Display Columns tab to specify additional columns by moving their names from the Column names field to the Display columns field. For a description of the database column names, see Table 22 on page 96 in the Custom Event Viewer topic. After setting the options, you can do either of the following: If you are finished building or editing the query, continue with step 4 in To Build or Edit a Custom Query on page 87. If you would like to view or edit the SQL statement, go to The SQL Statement Tab on page 92. Teradata AWS User Guide, Release 4.5 91

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Figure 25: Build New Query Dialog Box: Display Columns Tab The SQL Statement Tab The SQL Statement tab displays the SQL statement you built or edited using the Conditions, Advanced Conditions, and Display Columns tabs. After reviewing the SQL statement, you can do either of the following: If you are finished building or editing the query, continue with step 4 in To Build or Edit a Custom Query on page 87. If you would like to edit the SQL statement, select the Enable SQL statement editing checkbox. To edit SQL statements, you must be familiar with SQL syntax and the event database column definitions. When you are finished editing the SQL statement, continue with step 4 in To Build or Edit a Custom Query on page 87. 92 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events Figure 26: Build New Query Dialog Box: SQL Statement Tab Saving or Overwriting a Custom Query After you build a new query or edit an existing query, save it as a new query or by overwriting an existing query. To Save a New Query 1 When the Save Query dialog box displays, type a name for the custom query at Save as. 2 Click Save. Teradata AWS User Guide, Release 4.5 93

Chapter 4: Monitoring and Managing Events Creating Custom Queries for Events To Overwrite an Existing Query 1 When the Save Query dialog box displays, select the existing custom query you want to overwrite. 2 Click Save. 3 Click Yes to confirm. Running a Custom Query To Run a Query from the Custom Query Manager Note: The Custom Query Manager runs new or existing custom queries on the currently selected components. To run a custom query on different components, you must close the Custom Query Manager, select the components you want to use, then select the Event Mgmt > Custom Events Query command before you begin this procedure. 1 From the Custom Query Manager, select the custom query you want to run. 2 Click Execute. 3 When the Custom Event Viewer displays, use it to view the events returned by the query. Custom Event Viewer Renaming a Custom Query To Rename a Custom Query 1 From the Custom Query Manager, select the name of the query you want to rename. 2 Select Rename. 3 When the Rename Query dialog box displays, type a new name in the Enter new query name text box. 4 Click Save to rename the query and return to the Custom Query Manager. 94 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Custom Event Viewer Deleting a Custom Query To Delete a Custom Query 1 From the Custom Query Manager, select the name of the query you want to delete. 2 Select Delete. 3 When the confirmation dialog box displays, click Yes to delete the query and return to the Custom Query Manager. Closing the Custom Query Manager To Close the Custom Query Manager From the Custom Query Manager, click Close. Custom Event Viewer When you use the Custom Query Manager to run a custom query on the events database, the results are displayed in the Custom Event Viewer. The arrow indicates which column the information is sorted by, and whether the information is sorted in ascending (up arrow) or descending (down arrow) order. Note: The columns displayed in the Custom Event Viewer depend on the settings used in the Display Columns tab of the Build New Query or Edit Saved Query dialog box. Figure 27: Custom Event Viewer Teradata AWS User Guide, Release 4.5 95

Chapter 4: Monitoring and Managing Events Custom Event Viewer Table 22: Custom Event Viewer Description Event Database Column Definition Events for Most recent x events Time Severity Description SystemID CollectiveID CabinetID ChassisID ManagedElement ObjectClass TimeReceived Domain MessageID Description Contains the path, default alias, or component ID of the chassis, depending on the option set for the Tree View: Default option: the path follows the hierarchy displayed in the Tree View. Alias option: the default alias displays. If a user-defined alias exists, it displays instead of the default alias. Component ID option: the CIM path displays. If one component is selected, this field is not displayed. Indicates the number of records entered in the Conditions tab of the Build New Query or Edit Saved Query dialog box. Time and date the event occurred; for a node, the time and date the event was detected on the node. Severity level of the event being reported for the component. The severity levels are OK, Information, Warning, Degraded, Critical, and Fatal. The severity of event indicates the level of impact to the component. Message describing what occurred Numerical value in the default alias of the selected system Numerical value in the default alias of the selected collective Numerical value in the default alias of the selected cabinet Numerical value in the default alias of the selected chassis The component for which the event occurred; this is the unique name assigned to the component. Object class name of the component (usually the first part of the component ID). For example, if the component ID is CMIC_5400J.SystemID=1,CollectiveID=400,CabinetID=1,ID=6, the class name is CMIC_5400J. Time and date the event was received by server management. The source the event originated from. With MessageID, it uniquely identifies the type of event. An event name or message key or number unique within the Domain for a specific type of event, for example, a Windows Event ID or MP-RAS E-tag. 96 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Custom Event Viewer Table 22: Custom Event Viewer Description (continued) Event Database Column Definition ReporterType SubType RequestID Sequence Description The category the event belongs to: MPP_StatusEvent: an event reported for environmental conditions and significant state changes MPP_ConfigChangeEvent: an event reported for asset and setting changes MPP_CommandEvent: an event reported for commands users perform on the MPP system MPP_SnmpTrap: a trap event reported from the Fibre Channel switch and UPS MPP_BynetDPEvent: an event sent by the BYNET DP MPP_ApplicationEvent: an event reported to server management from an application MPP_Alert: an event indicating an alert condition; these events are processed by the Fault Manager MPP_WinLog: an event from the application and system logs of Windows nodes MPP_UNIXLog: an event from the ConsoleLog and StreamsError log of MP-RAS nodes or from the Syslog of Linux nodes. MPP_DeviceLog: an event from a log resident on a device; for example, a disk array MEL event An optional event type; depends on the ReporterType or the type of managed object. Examples: PostError, AssetChange, SettingChange, StreamsError, and ConsoleLog (UNIX MP-RAS nodes); Syslog (Linux nodes), Application (Windows nodes); and SLAN (legacy systems) Groups a sequence of events, such as command results Sequence in which the event was logged. The Display Columns Tab The Conditions Tab Creating Custom Queries for Events Component Names Teradata AWS User Guide, Release 4.5 97

Chapter 4: Monitoring and Managing Events Custom Event Viewer Custom Event Viewer Menus The following table describes the commands available from each menu in the Custom Event Viewer menu bar. Table 23: Custom Event Viewer Commands Contains commands for saving the results of the custom query to a file and closing the Custom Event Viewer Allows you to search for text string See: To Save the Results of a Custom Query to a File on page 99 To Close the Custom Event Viewer on page 100 See: To Search for an Event Record on page 99. Display the Event Details window. See: To View Event Details on page 99. Allows you to find a component in the Tree View See: To Locate a Component in the Tree View on page 99. Displays help for the Custom Event Viewer See: Using Teradata AWS Online Help on page 43. Access to Teradata AWS Commands Working with the Custom Event Viewer Note: For a description of the columns in the Custom Event Viewer, see Table 22 on page 96. To Sort Event Records by Column Click the appropriate column header. To toggle between ascending and descending order, click the column header. 98 Teradata AWS User Guide, Release 4.5

Chapter 4: Monitoring and Managing Events Custom Event Viewer To Display or Hide a Column The Custom Event Viewer contains one or more of the columns described in Table 22 on page 96. To display or hide one or more columns: 1 Right-click any column header. The displayed pop-up menu contains the names of all the available columns. Check-marks beside column names indicate which columns are currently displayed. 2 On the pop-up menu, select a column header to display it, or clear a column header to hide it. To Save the Results of a Custom Query to a File 1 From the Custom Event Viewer, do one of the following: a To save the information in plain text format (.txt) that can be viewed with Notepad or a similar text editor, select File > Text. b To save the information in comma separated value format (.csv) that can be viewed with Microsoft Excel or a similar spreadsheet application, select File > CSV. 2 When the Save dialog box displays, enter a file name and location, then click Save. To Search for an Event Record 1 Select the Search > Find command. 2 Use the Find dialog box to search for text strings. To View Event Details 1 Select the event in the Custom Event Viewer. 2 Select View > Detail from the Custom Event Viewer menu bar. A separate Event Details window displays. Some fields are displayed for all event types and others are unique to components and event types. The Event Details window is the same as the one accessible with the View > Detail command on the Event Viewer. For a description of the window, see Table 17 on page 80. To Locate a Component in the Tree View 1 In the Custom Event Viewer, select an event. 2 Select the Functions > Locate Component command. The component associated with the event is highlighted in the Tree View. Teradata AWS User Guide, Release 4.5 99

Chapter 4: Monitoring and Managing Events Custom Event Viewer To Close the Custom Event Viewer From the Custom Event Viewer, click File > Close. 100 Teradata AWS User Guide, Release 4.5

CHAPTER 5 Monitoring, Managing, and Escalating Faults with the Fault Viewer The AWS Fault Viewer is used to view and track problem conditions. As server management and the AWS collect events, fault detection agents filter each event to detect problem conditions. During the filtering process, each event is compared to a set of predefined criteria. When a match occurs, a fault is reported to the AWS Fault Manager and displays in the Fault Viewer. The Fault Viewer Fault Viewer Menus Fault Properties Fault Details Fault Tracking and Management Fault Resolution Recommendations Fault Viewer Display and Filtering Options Checking the Health of the System Configuring Alerts Teradata AWS User Guide, Release 4.5 101

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer The Fault Viewer The Fault Viewer The Fault Viewer provides a centralized view of the faults that have been generated in the system. The Fault Viewer allows you to: View the history of open or closed faults Filter the fault history by date or other fault properties Track the resolution of a fault Keep a journal of actions taken to investigate or resolve a fault Save recommendations for resolving future faults Add new faults that you want to track By default, all open faults are displayed in the Fault Viewer in the right pane of the Teradata AWS. The Event Mgmt > View Faults command allows you to display one or more separate (additional) instances of the Fault Viewer. You can display open faults, closed faults, or both open and closed faults in the Fault Viewer. Fault Severities and Their Indicators To Set Filtering Options for the Fault Viewer To Set the AWS Option for the Fault Viewer Fault Properties Tree View Pane and Windows on the AWS Desktop To Display Open Faults Open faults are faults that currently impact the system and those that are in some state of resolution but have not yet been closed. By default, the Fault Viewer displays open faults. The open faults are sorted by time stamp, in descending order; the fault with the most recent time stamp display first. The open fault list displayed in the Fault Viewer dynamically updates as new faults occur, resolution status changes, or faults are closed. To display open faults in another instance of the Fault Viewer, do one of the following: In the Fault Viewer, select View > Open Faults. From the Teradata AWS, select Event Mgmt > View Faults. When the View Faults dialog box displays, select Open Faults. Note: When the View Faults dialog box displays, use it to set additional filtering options. When you filter faults in a Fault Viewer, the faults displayed in that Fault Viewer are not updated or removed, and no new faults are added. Note: The View Faults dialog box does not display if the Tools > Options command has been used to clear the Prompt for Fault Viewer settings option. 102 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer The Fault Viewer To Display Closed Faults Closed faults are faults that have been archived with the Fault Viewer s Functions > Close > Similar Faults or Functions > Close > Selected Faults commands, or faults that have been closed automatically when the open list maximum size limit has been exceeded. The Fault Viewer displays closed faults sorted by time stamp, in descending order; the fault with the most recent time stamp displays first. The closed fault list dynamically updates. To display closed faults, do one of the following: In the Fault Viewer, select View > Closed Faults. From the Teradata AWS, select Event Mgmt > View Faults. When the View Faults dialog box displays, select Closed Faults. This opens a new Fault Viewer. Note: When the View Faults dialog box displays, use it to set additional filtering options. When you filter faults in a Fault Viewer, the faults displayed in that Fault Viewer are not updated or removed, and no new faults are added. Note: The View Faults dialog box does not display if the Tools > Options command has been used to clear the Prompt for Fault Viewer settings option. To Display All Faults The Fault Viewer displays all faults, open and closed, with the most recent time stamp displayed first, regardless of whether the fault is an open or closed fault. To display all faults, do one of the following: In the Fault Viewer, select View > All Faults. From the Teradata AWS, select Event Mgmt > View Faults. When the View Faults dialog box displays, select All Faults. This opens a new Fault Viewer. Note: When the View Faults dialog box displays, use it to set additional filtering options. When you filter faults in a Fault Viewer, the faults displayed in that Fault Viewer are not updated or removed, and no new faults are added. Note: The View Faults dialog box does not display if the Tools > Options command has been used to clear the Prompt for Fault Viewer settings option. To Hide One or More Fault Types in the Fault Viewer The Fault Viewer Functions > Hide Selected Fault Type(s) command allows you to reduce the number of faults you see in the Fault Viewer. You can hide faults that have the same Problem Domain and Problem Code, and redisplay them with the Fault Viewer Functions > Hide Selected Fault Type(s). When you hide faults in the Fault Viewer, the faults are not removed from the system, and their Resolution status continues to be updated. 1 If the Problem Domain property is not displayed as a column in the Fault Viewer, display it. 2 Select a fault that has a Problem Domain matching the fault you want to hide. 3 Click the Fault Viewer Functions > Hide Selected Fault Type(s) command. Teradata AWS User Guide, Release 4.5 103

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer The Fault Viewer 4 When the confirmation dialog box containing the fault s Problem Domain and Problem Code displays, click Yes. All faults with the same Problem Domain and Problem Code are hidden in the Fault Viewer. To Redisplay Hidden Fault Types in the Fault Viewer The following procedure redisplays fault types hidden with the Fault Viewer Functions > Hide Selected Fault Type(s) command. 1 Click the Fault Viewer Functions > Redisplay Hidden Faults command. Note: If the Fault Viewer Functions > Redisplay Hidden Faults command is not active, there are no hidden faults. 2 Select one or more fault types in the list. 3 Click Ok. 4 When the confirmation dialog box displays, click Yes. All faults matching the fault type or types you selected are redisplayed in the Fault Viewer. To Open a New Fault Viewer More than one instance of the Fault Viewer can be open at the same time. You can set different filtering options for each Fault Viewer you open. When you filter faults in a Fault Viewer, the faults displayed in that Fault Viewer are not updated or removed, and no new faults are added. 1 Do one of the following: In the Fault Viewer, select the View > Options command. From the Teradata AWS, select Event Mgmt > View Faults. Note: The View Faults dialog box does not display if the Tools > Options command has been used to clear the Prompt for Fault Viewer settings option. 2 Use the View Faults dialog box to set additional filtering options. 3 Click Ok to display another instance of the Fault Viewer with the faults you specified. 104 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer The Fault Viewer To Sort Faults by Property Click the appropriate column header. To toggle between ascending and descending order, click the column header. To Search for Text Strings in the Fault Viewer 1 Display the Fault Viewer. 2 Select the Fault Viewer s Search > Find command. 3 Use the Find dialog box to search for text strings. To Locate a Component in the Tree View 1 In the Fault Viewer, select a fault. 2 Select the Functions > Locate Component command. The component associated with the fault is highlighted in the Tree View. To Hide or Display the Fault Viewer on the Teradata AWS Desktop From the Teradata AWS, select or clear Window > Fault Viewer. To Save the Contents of a Fault Viewer 1 Do one of the following: To save files in text (.txt) format, select File > Save Table > Text. Files saved in plain text format can be viewed in Notepad or a similar text editor. To save files in comma separated value (.csv) format, select File > Save Table > CSV. Files saved in this format contain individual entries, separated by commas, that can be viewed in Microsoft Excel or a similar spreadsheet application. 2 In the Save dialog box, specify a name and location for the file. To Close the Fault Viewer To close a Fault Viewer that was opened using the Teradata AWS Event Mgmt > View Faults command, select the Fault Viewer s File > Exit command. Note: To close or manipulate the Fault Viewer displayed in the right pane of the Teradata AWS, use the commands in the Teradata AWS Window menu. Teradata AWS User Guide, Release 4.5 105

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Viewer Menus Fault Viewer Menus The following table describes the commands available from each menu in the Fault Viewer menu bar. When you select a fault, the commands available for that fault display in the menus on the Fault Viewer menu bar and in pop-up menus. Table 24: Fault Viewer Commands Contains commands for saving and closing the Fault Viewer. Allows you to search for text strings. Contains commands for displaying and filtering faults in the Fault Viewer. Contains commands for working with faults displayed in the Fault Viewer. Contains commands for working with recommendations. See: To Save the Contents of a Fault Viewer on page 105 To Close the Fault Viewer on page 105 See: To Search for Text Strings in the Fault Viewer on page 105. See: To Display Open Faults on page 102 To Display Closed Faults on page 103 To Display All Faults on page 103 Fault Resolution Recommendations on page 121 To Open a New Fault Viewer on page 104 See: Fault Details on page 109 Tracking Fault Resolution Status on page 112 Adding Fault Journal Comments on page 114 To Locate a Component in the Tree View on page 105 To Hide One or More Fault Types in the Fault Viewer on page 103 Closing a Fault on page 115 Submitting a New Fault on page 119 To Redisplay Hidden Fault Types in the Fault Viewer on page 104 See: Fault Resolution Recommendations on page 121. 106 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Properties Table 24: Fault Viewer Commands (continued) Allows you to monitor faults. Displays Fault Viewer help. See: Configuring and Using the Fault Notification Window on page 340. See: Using Teradata AWS Online Help on page 43. Access to Teradata AWS Commands Fault Properties The Fault Viewer displays open faults, closed faults, or all faults, depending upon the display options you set. The title bar indicates which faults are displayed. Faults are sorted according to time stamp, in descending order, with the most recent fault displayed first. If the Fault Viewer contains only open faults (the default), the Fault Viewer is dynamically updated as new faults are added, faults are closed, and resolution states change. To rearrange the columns in the Fault Viewer, drag each column header to its new location. To hide or display columns in the Fault Viewer, right-click any column header. On the pop-up menu, select a column header to display it, or clear a column header to hide it. Each fault entry contains properties associated with the fault. Each column in the Fault Viewer represents a specific fault property. The table that follows describes these fault properties. Figure 28: Fault Viewer Teradata AWS User Guide, Release 4.5 107

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Properties Table 25: Fault Viewer: Fault Properties Column ID List Time Severity Resolution Alias Problem Source Problem Domain Description Definition A unique Fault ID assigned to the fault. Fault IDs are assigned in sequence, as they occur. The icon to the left of the ID represents the fault severity level. Indicates whether the fault is open or closed; this column displays by default when all faults are displayed. The date and time that the fault was detected. When the Fault Viewer is first displayed, an arrow-shaped icon appears in the Time column to indicate that the faults are sorted by time, in descending order, with the most recent fault at the top of the list. Severity level of the fault: Unknown, OK, Information, Warning, Degraded, Critical, Fatal. The fault s resolution status. Auto Solved denotes a problem that has been automatically solved the status of the component associated with this fault is OK. The default Alias or CIM path for the component name. If a user-defined Alias exists, it displays instead of the default Alias. Internal identifier for the managed object or source of the problem; for example, the CIM identifier of the object that generated the fault. The problem area, which is typically a short name for the agent reporting the fault. Representative categories or examples of possible Problem Domains are listed below. Not all domains are listed. Faults reported by SM3G server management, including Node, CMIC, NCRChassisAgent, CMICCore, BYNET, BYNETDP, ChassisMonitor, UPS_PWDEB, FCSW_SB2, and Disk_Array faults ADEPT: A disk predictive warning or fault CheckBatteries: Fault reported by the CheckBatteries utility CSF domains: NODECSF faults reported for legacy MP-RAS nodes, including Teradata software (CSF-PDE), BYNET software (CSF-BYNET), MP-RAS kernel (CSF-KERNEL), and user error log (CSF-Misc) faults Linux domains: faults reported for Linux node software LSI Array Controller: Fault reported by MEL MPPFM: Fault reported by the AWS Fault Manager; for example, the AWS low disk-space fault MPPSS domains: faults reported for legacy systems by server management, including BYNET (MPPSS-BY, MPPSS-BYDP), disk array (MPPSS-DA, MPPSS- EMC), Fibre Channel switch (MPPSS-FCSW), node (MPPSS-NOD), server management (MPPSS-SM), and UPS (MPPSS-UPS) faults MPRAS domains: faults reported for MP-RAS node software WinLog domains: faults reported for Windows node software Text message giving a brief synopsis of the problem. The text message is the first non-blank line of the fault problem description, up to 80 characters. 108 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Details Fault Severities and Their Indicators Fault Details Tracking Fault Resolution Status Component Names Fault Details The Fault Viewer s Functions > View Details command displays a detail window containing all available information about the fault. You must select the fault from the Fault Viewer before you select the command. Figure 29: View Fault Details Window Teradata AWS User Guide, Release 4.5 109

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Details Table 26: View Fault Window Description Field Id List Time Severity Resolution Alias Problem Source Instance Problem Domain Problem Code Problem Description Additional Data Description A unique Fault ID assigned to the fault. Fault IDs are assigned in sequence, as they occur. Indicates whether the fault is in the Open or Closed list. The date and time the fault was generated by the fault detection agent. Severity level of the fault. The following list describes the possible severity levels: Unknown: The severity level of the problem is unknown. OK: Indicates that a component s status has returned to normal. Faults generated by the system do not have a severity level of OK, but an event indication with a severity level of OK can be used to Auto Solve existing faults. Faults that you submit may have a severity level of OK. Information: An informational message that draws attention to an event that changes some characteristic of the subsystem but leaves all aspects of its operation at the same level, or draws attention to an event that signifies the restoration of a previously diminished subsystem. No further degradation is anticipated. Warning: A warning message that draws attention to a condition that, if not addressed, could become a more serious problem. The subsystem is still fully functional at the same level of performance. Degraded: The subsystem is degraded; an event has left the subsystem fully functional but at a lesser performance level. Critical: The subsystem is down; the event is a certain forerunner to a more fatal event. Fatal: The subsystem is down; the event has caused the subsystem to stop. The fault's resolution status. The default Alias for the component name. If a user-defined Alias exists, it displays instead of the default Alias. Internal identifier for the managed object or source of the problem; for example, the CIM identifier of the object that generated the fault. The problem area, which is typically a short name for the agent reporting the fault.representative categories or examples of possible Problem Domains are listed in Problem Domain in Table 25 on page 108. Not all domains are listed. A value, text string, or number that, in combination with the Problem Domain, represents a unique problem type within the MPP environment. Contains Customer Service recommendations for Alert Register faults at the time of product release. The Problem Description consists of a text message that describes the problem comprehensively, including a one-line short synopsis, meaning, probable cause, recommended action for further diagnosis and corrective measures, and event message that triggered the fault. Contains any additional information available to document the problem, such as the event message from which the fault was generated, NODECSF SFR script output, and additional details. 110 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Table 26: View Fault Window Description (continued) Field Journal Close button Previous button Next button Save button Update button Description The Journal area is a log of information entered to resolve the fault. Each Journal entry contains a time stamp and user name. A Journal entry can be composed of one or more of the following: User-saved recommendations that match the Problem Domain and Problem Code you entered appear here. Entries display here when comments are entered with the Functions > Add To Journal, Functions > Track Resolution, or Functions > Close Fault commands State and status change messages display here when the Fault Manager performs a function on the fault, such as when the Fault Manager changes the fault s resolution status to Auto Solved. Closes the window. Displays fault details of the previous fault in the Fault Viewer. Displays fault details of the next fault in the Fault Viewer. Saves the fault details to a text file. Adds updated recommendations to the detail window. Tracking Fault Resolution Status Component Names Fault Properties Fault Tracking and Management The Fault Viewer contains a set of fault tracking and management commands that allow you to track a fault s resolution status, add journal entries to the fault, add site-specific recommendations to a fault, submit a problem as a fault, escalate a fault to Customer Services through Teradata Vital Infrastructure (TVI), and close a fault. These tracking and management commands help you track problem conditions that occur on your system and what you did to resolve them. This information helps you effect a quick recovery if the same problem occurs again. Each fault s Problem Description contains the Customer Services recommendation at the time of product release. You or Customer Services can add additional recommendations for your site. Each time a fault is generated with the same Problem Domain and Problem Code, the Customer Services recommendations and user-defined recommendations can be displayed with the Fault Viewer s Functions > View Details command. Tracking Fault Resolution Status Adding Fault Journal Comments Teradata AWS User Guide, Release 4.5 111

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Closing a Fault Submitting a New Fault Tracking Fault Resolution Status The Functions > Track Resolution Status command allows you to change a fault s resolution status and add an annotation to the fault Journal. The annotation can optionally be stored as a recommendation. Moving a fault through various states of resolution is optional. However, it can help a system administrator monitor a problem through various stages of resolution until an acceptable solution is found. The following list shows a typical fault resolution scenario for entering information into the Resolution State field of the Track Resolution Status dialog box: 1 When a new fault occurs, the Resolution State is None. 2 If there is no readily apparent corrective action, the administrator may notify Teradata for assistance and enter Under Investigation. 3 When a recommended action is taken, the administrator may enter Action Taken, describe what was done, and enter the name of the user who performed the action. 4 If the problem disappears and you want to monitor it or determine its cause, enter Unsolved. 5 When the problem is considered resolved, enter Solved. 6 Use the Functions > Close Fault command to close the fault. To use the Functions > Track Resolution Status command, select a fault or faults, then select the command to display the Track Resolution Status dialog box. If you select more than one fault (for example, all the faults that pertain to one problem condition), the resolution status you enter is applied to all the selected faults. The following table describes the fields on the Track Resolution Status dialog box. After you enter changes, click Ok to save the changes. 112 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Figure 30: Track Resolution Status Dialog Box Table 27: Track Resolution Status Dialog Box Description Field Resolution State User Comment Description This list box allows you to change the resolution status of the fault to one of the following. Unchanged: Select this option if a previously entered Resolution State is set appropriately and you want to enter a comment. This is the default. Under Investigation: Select this option if the problem is currently being investigated. Action Taken: Select this option if an action has been performed to resolve the fault. Solved: Select this option if the problem has been corrected. Unsolved: Select this option if the problem is no longer impacting the component; however, the problem is not considered solved (for example, if the problem disappeared but its cause is unknown). In addition, a fault can have a resolution state of Auto Solved. The Fault Manager assigns this state to a component that was not operating normally, but has returned to normal (OK) operation. Auto Solved is not a user-selectable state. This field allows you to type the name or user name of the person who is investigating the problem, who performed an action to resolve the problem, or who is now indicating that the problem is resolved. The name does not have to correspond to a user account login name. This field is optional. The default is the current user; for example, Administrator. This field allows you to enter a text annotation that is stored with the fault Journal. You can use this field to add notes to the fault concerning the status of problem investigations, actions performed, and how the fault was resolved. Teradata AWS User Guide, Release 4.5 113

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Table 27: Track Resolution Status Dialog Box Description (continued) Field Save this comment as a recommendation for this Fault Problem Code Description When the comment you entered in the Comment field is a recommendation on how to resolve future problems, you can check this box to store the comment as a recommendation. The next time a fault with the same Problem Domain and Problem Code occurs, the recommendation displays in the fault Journal. This user-specified recommendation is stored in addition to the Customer Services recommendation included in the Problem Description. The default is unchecked. Adding Fault Journal Comments The Functions > Add To Journal command allows you to add comments to the fault Journal. The comments can be optionally stored as recommendations. The Journal comments you enter are available for display in the Fault Viewer s Functions > View Details detail window. Note: If you need to change the Resolution State, you should use the Functions > Track Resolution Status command to add comments to the Journal. To use the Functions > Add To Journal command, select a fault or faults, then select the command to display the Add To Journal dialog box. If you select more than one fault, the same comment is applied to all the selected faults. The following table describes the fields on the Add To Journal dialog box. After you enter changes, click Ok to save the changes. Figure 31: Add To Journal Dialog Box 114 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Table 28: Add To Journal Dialog Box Description Field User Comment Save this comment as a recommendation for this Fault Problem Code Description This field allows you to type the name or user name of the person who is investigating the problem. The name does not have to correspond to a user account login name. This field is optional. The default is the current user; for example, Administrator. Use this field to type comments that you want to store with the fault Journal. You can use this field to add notes about the problem condition, such as impacts to the system, the status of problem investigations, or actions performed. When the text in the Comment field is a recommendation on how to resolve future problems, you can check this box to store the comment as a recommendation. The next time a fault with the same Problem Domain and Problem Code occurs, the recommendation text displays in the fault Journal. This user-specified recommendation is stored in addition to the Customer Services recommendation included in the Problem Description. The default is unchecked. Closing a Fault The Functions > Close > Selected Faults and Functions > Close > Similar Faults commands archive faults. Archiving a fault moves it from the open fault list to the closed fault list. When faults are resolved, they should be closed to remove them from the list of open faults currently being monitored. The Close Selected Faults command archives faults selected in the Fault Viewer. When you close a selected fault, you can optionally change the resolution state, add a Journal comment to the fault, and save the comment as a recommendation. If you select more than one fault, the same resolution state and comments are applied to all the selected faults. The Close Similar Faults command archives faults similar to a selected fault. You can archive faults that have the same Problem Source, Resolution State (None, Auto Solved, Unchanged, Under Investigation, Action Taken, Solved, Unsolved), or fault type (Problem Domain, Problem Code). When you close a fault similar to a selected fault, you can optionally add a Journal comment to the fault. If you do not close faults, they remain open until the Open Fault List Max Faults limit is exceeded; when the limit is exceeded, the resolved faults are automatically closed, then the oldest faults are automatically closed. To Close Selected Faults To Close Faults Similar to a Selected Fault Managing the Fault Database Teradata AWS User Guide, Release 4.5 115

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management To Close Selected Faults 1 Select one or more faults. 2 Select Functions > Close > Selected Faults. 3 When the Close Fault dialog box displays, use the information in Table 29 to make changes. 4 Click Ok. Figure 32: Close Fault Dialog Box (Close > Selected Faults) 116 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Table 29: Close Fault Dialog Box Description (Close > Selected Faults) Field Resolution State User Comment Save this comment as a recommendation for this Fault Problem Code Description Use this list box to change the resolution status of the fault to: Unchanged: Select this if the Resolution State is set appropriately. Under Investigation: Select this if the problem is currently being investigated. Action Taken: Select this if an action has been performed to resolve the fault. Solved: Select this if the problem has been corrected. Unsolved: Select this if the problem is no longer impacting the component; however, the problem is not considered solved (for example, if the problem disappeared but its cause is unknown). A fault can also have one of the following resolution states. These states appear in the Fault Viewer, but are not available when using the Fault Viewer s Functions > Close > Selected Faults command to close selected faults. Auto Solved. The Fault Manager assigns this state to a component that was not operating normally, but has returned to normal (OK) operation. Auto Solved is not a user-selectable state. None: The Fault Manager assigns this state to new faults. This field allows you to type the name or user name of the person closing the fault. The name does not have to correspond to a user account login name. This field is optional. The default is the current user; for example, Administrator. Use this field to type comments to store with the fault Journal. You can use this field to add notes to the fault concerning the results of problem investigations, actions performed, and how the fault was resolved. When the text in the Comment field is a recommendation on how to resolve future problems, check this box to store the comment as a recommendation. The next time a fault with the same Problem Domain and Problem Code occurs, the recommendation text displays in the fault Journal. This userspecified recommendation is stored in addition to the Customer Services recommendation included in the Problem Description. The default is unchecked. To Close Faults Similar to a Selected Fault 1 Select a fault. 2 Select Functions > Close > Similar Faults. 3 When the Close Fault dialog box displays, use the information in Table 30 to make changes. 4 Click Ok. Teradata AWS User Guide, Release 4.5 117

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Figure 33: Close Fault Dialog Box (Close > Similar Faults) Table 30: Close Fault Dialog Box Description (Close > Similar Faults) Field By Problem Source By Resolution Type Description When you select this checkbox, you can close faults that have the same Problem Source Instance as the selected fault. The Problem Source Instance of the selected fault is automatically added to the Problem Source Instance field in the Close Fault dialog box. For more information about Problem Source Instance, see the description in Table 26 on page 110. Note: When closing similar faults, one, two, or all of the checkboxes can be selected. When you select this checkbox, you can close faults that have the same Resolution State as the selected fault. The following resolution states are available: None: New faults. Under Investigation: Faults currently being investigated. Action Taken: Faults for which an action has been performed to resolve the fault. Auto Solved. Faults for components that were not operating normally, but have returned to normal (OK) operation. Solved: Faults that have been corrected. Unsolved: Faults no longer impacting the component; however, the problem is not considered solved. Note: When closing similar faults, one, two, or all of the checkboxes can be selected. 118 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Table 30: Close Fault Dialog Box Description (Close > Similar Faults) (continued) Field By Fault Type User Comment Description When you select this checkbox, you can close faults that have the same Problem Domain and Problem Code as the selected fault. The Problem Domain and Problem Code of the selected fault are automatically added to the Problem Domain and Problem Code fields in the Close Fault dialog box. For more information about Problem Domain and Problem Code, see their descriptions in Table 26 on page 110. Note: When closing similar faults, one, two, or all of the checkboxes can be selected. This field allows you to type the name or user name of the person closing the fault. The name does not have to correspond to a user account login name. This field is optional. The default is the current user; for example, Administrator. Use this field to type comments that you want to store with the fault Journal. You can use this field to add notes to the fault concerning the results of problem investigations, actions performed, and how the fault was resolved. Submitting a New Fault The Functions > Submit New Fault command allows you to add a new fault for tracking by the AWS Fault Manager. Once submitted, the fault displays in the Fault Viewer s open list. When you submit the fault, you can select the Escalate check box. This identifies all faults with the same Problem Code as User-Escalate. Customer Services can then review all faults with the same Problem Code. You can use the Functions > Submit New Fault command when a problem is observed on your system that was not automatically detected by the Fault Detection subsystem. You may also want to use this command to escalate an event you see in the Event Viewer that did not generate an associated fault in the Fault Viewer, or to track problems in customer applications. The following table describes the Submit New Fault dialog box. The Problem Source Instance field, Problem Domain field, and the Problem Code field are automatically set to User. At the minimum, you should enter the Severity and Description for the new fault, then click Ok to submit the fault. Teradata AWS User Guide, Release 4.5 119

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Tracking and Management Figure 34: Submit New Fault Dialog Box Table 31: Submit New Fault Dialog Box Description Field Severity Problem Source Instance Problem Domain Problem Code Description Use this list box to enter the level of impact this problem is causing to your system: Unknown, OK, Information, Warning, Degraded, Critical, Fatal. If you know the internal object identifier that should be associated with this problem, select Advanced to enable this field and enter the AWS Component ID of the MPP component that is having a problem. You can find the Component ID by selecting the component in the Tree View, then selecting View > Properties in the Teradata AWS menu bar, or from other faults or events you see for the same component. If this problem is not associated with a particular component, you may also enter the name of a system entity that is impacted or a suspected root cause. The default is User. If Escalate is selected, this field is set to User. Optionally, if you wish to categorize the problem for your own tracking purposes, enter a name for the problem area, for example, Program XYZ. If you want to separately identify and track problem types within a domain by number or error name (for example, Install Error-abc), select Advanced to enable this field. The default is User. If Escalate is selected, this value is set to User-Escalate. 120 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Resolution Recommendations Table 31: Submit New Fault Dialog Box Description (continued) Field Escalate Advanced Description Description This option allows you to escalate the new fault to Customer Services through TVI. When this check box is selected, you can select the Severity and enter text in the Description field. The Problem Domain and Problem Code fields contain the text required for escalation through TVI and cannot be modified. To enter a Component ID in the Problem Source Instance field, select Advanced. This option allows you to enter text in the Problem Source Instance and Problem Code fields. The default is unchecked.the Severity and Problem Domain fields are already enabled. This field allows you to enter a description of the problem you are observing. If you are escalating this problem, enter enough detail about the condition to allow Customer Services to diagnose the problem. Fault Details Fault Resolution Recommendations The Fault Viewer s View > Recommendations command displays a list of user-entered recommendations in the Fault Viewer. The user-entered recommendations are additional solutions or corrective actions you have used to resolve a particular problem. The recommendations are displayed in the Journal area in subsequent faults. (Customer Service-supplied recommendations are displayed in the fault s Problem Description area). Displaying a List of Recommendations Displaying Recommendation Details Submitting New Recommendations Editing Recommendations Deleting Recommendations Fault Tracking and Management Displaying a List of Recommendations When you select the Fault Viewer s View > Recommendations command, a list of recommendations displays. Display details by double-clicking one of the recommendations. The table that follows describes the columns on the recommendations list. Teradata AWS User Guide, Release 4.5 121

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Resolution Recommendations Figure 35: Fault Viewer Recommendations List (View > Recommendations) Table 32: Fault Viewer Recommendations List Description (View > Recommendations) Column Problem Domain Problem Code Recommendation Description The key used to store the recommendation by problem type. See the description for Problem Domain in Table 25 on page 108. The key used to store the recommendation by problem type. It is a value, text string, or number that, in combination with the Problem Domain, represents a unique problem type within the MPP environment. This field contains the user-entered corrective actions or solutions to be performed to resolve subsequent faults with the same Problem Domain and Problem Code. Displaying Recommendation Details When you select the Fault Viewer s View > Recommendations command, you can do one of the following to display a Recommendations window containing detailed recommendations: Double-click one of the recommendations in the list Select the Fault Viewer s Functions > View Details command The table that follows describes the fields on the Recommendations window. Figure 36: Fault Viewer: Recommendations Window (Functions > View Details) 122 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Resolution Recommendations Table 33: Fault Viewer: Recommendations Window Description (Functions > View Details) Field Problem Domain Problem Code Recommendations Close button Previous button Next button Save button Description The key used to store the recommendation by problem type. The key used to store the recommendation by problem type. It is a value, text string, or number that, in combination with the Problem Domain, represents a unique problem type within the MPP environment. This field contains the user-entered corrective actions or solutions to be performed to resolve subsequent faults with the same Problem Domain and Problem Code. Closes the window. Displays fault details of the previous fault in the Fault Viewer. Displays fault details of the next fault in the Fault Viewer. Saves the fault details to a text file. Fault Details Submitting New Recommendations If you submit a new recommendation and a recommendation already exists for the same Problem Domain and Problem Code, the existing recommendation is overwritten with the new one. To add a recommendation, use the following procedure: 1 Display the recommendation list using the Fault Viewer's View > Recommendations command. 2 Select Functions > Submit New Recommendation. 3 When the Recommendations window displays, use the information in the following table to add a recommendation. The Problem Domain and Problem Code fields must pertain to a fault known to be generated by the system. You can find these values displayed as fault properties in the Fault Viewer s View > Details window. Recommendations can also be added by entering text in the Comment field and selecting the check box Save this comment as a recommendation for this fault Problem Code in the following dialog boxes: Add To Journal, Track Resolution, or Close. Recommendations added using these commands are appended to existing recommendations with the same Problem Domain and Problem Code. Teradata AWS User Guide, Release 4.5 123

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Resolution Recommendations Figure 37: Fault Viewer: Recommendations Dialog Box (Functions > Submit New Recommendation) Table 34: Fault Viewer: Recommendations Dialog Box Description (Functions > Submit New Recommendation) Field Problem Domain Problem Code Description Ok Cancel Description The key used to store the recommendation by problem type. The key used to store the recommendation by problem type. It is a value, text string, or number that, in combination with the Problem Domain, represents a unique problem type within the MPP environment. Use this field to enter corrective actions or solutions to be performed when future faults of this same type occur. This text is added to the Journal of subsequent faults with the same Problem Domain and Problem Code. Closes the window and stores the recommendation. Closes the window without storing the recommendation Fault Details Fault Tracking and Management 124 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Viewer Display and Filtering Options Editing Recommendations To Edit a Recommendation 1 Display the recommendation list using the Fault Viewer's View > Recommendations command. 2 Select a recommendation in the list. Deleting Recommendations 3 Select Functions > Edit Recommendation. 4 When the Recommendations window displays, use the text box to edit the recommendation pertaining to the Problem Domain and Problem Code. 5 Select OK to save the recommendation changes. 6 Select Save to save the recommendation to a text file. To Delete a Recommendation 1 Display the recommendation list using the Fault Viewer's View > Recommendations command. 2 Select one or more recommendations in the list. 3 Select Functions > Delete Recommendation. The recommendations you selected are removed from the recommendation list and are no longer appended to subsequent faults with the indicated Problem Domain and Problem Code. Fault Viewer Display and Filtering Options The following commands allow you to set display and filtering options for the Fault Viewer: The Tools > Options command displays the Options dialog box, which contains an option for displaying or hiding the View Faults dialog box when the Event Mgmt > View Faults command is selected. The Event Mgmt > View Faults command and the Fault Viewer s View > Options command display the View Faults dialog box, which contains options for: Specifying which faults you want to display in the Fault Viewer Specifying additional filtering options To Set the AWS Option for the Fault Viewer To Set Filtering Options for the Fault Viewer Fault Details Teradata AWS User Guide, Release 4.5 125

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Viewer Display and Filtering Options To Set the AWS Option for the Fault Viewer 1 From the Teradata AWS menu bar, select the Tools > Options command. 2 In the Fault Viewer section of the Options dialog box, select or clear the option described in Table 35. 3 Click Ok. Table 35: Teradata AWS Options Dialog Box (Tools > Options): Fault Viewer Display Options Option Prompt for Fault Viewer settings Description This check box allows you to specify whether you want the Teradata AWS to display a dialog box that prompts you for Fault Viewer settings when you select the Event Mgmt > View Faults command. If the dialog box does not display, you must use the Prompt for Fault Viewer settings option to redisplay. After you set this option, the dialog box that prompts you for Fault Viewer settings displays the next time you use the Event Mgmt > View Faults command. The default is checked. To Set Filtering Options for the Fault Viewer 1 Do one of the following: In the Fault Viewer, select View > Options. From the Teradata AWS menu bar, select the Event Mgmt > View Faults command. Note: The View Faults dialog box does not display if the Tools > Options command has been used to clear the Prompt for Fault Viewer settings option. 2 When the View Faults dialog box displays, use the information in Table 36 to set the filtering options you want to use. 126 Teradata AWS User Guide, Release 4.5

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Viewer Display and Filtering Options 3 Click Ok to display the Fault Viewer. Figure 38: View Faults Dialog Box Table 36: View Faults Dialog Box Description: Choose View Type Options Open Faults Closed Faults All Faults Recommendations Description This radio button allows you to display open faults. Open faults are faults that are currently impacting the system, are in some state of resolution, or have been resolved but have not yet been closed. The default is selected. This radio button allows you to display closed faults. Closed faults are faults that have been closed with the Fault Viewer s Functions > Close Fault command, or the faults that have automatically been closed when the open list limit was exceeded (only the oldest resolved faults, then the oldest faults, are automatically closed). The default is unselected. By default, open (active) faults are displayed in the Fault Viewer. This radio button allows you to display both open and closed faults. The default is unselected. This radio button allows you to display recommendations that are entered and saved by a user. These recommendations are included with Customer Service-supplied recommendations when a fault of the same problem type occurs in the future. Teradata AWS User Guide, Release 4.5 127

Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Fault Viewer Display and Filtering Options Table 37: View Faults Dialog Box, Options Dialog Box: Filter Options Options Start Date End Date Problem Source Instance Problem Domain Severity Resolution Description This set of list boxes is used in conjunction with the End Date list boxes to display faults within a range of start and end dates. Select the month, date, and year of the start date. The default is January 1, 2000. This set of list boxes is used in conjunction with the Start Date list boxes to display faults within a range of start and end dates. Select the month, date, and year of the end date. The default is the current date. This field allows you to type a Component ID and display faults associated with the component based on the Component ID. You can find and copy a Component ID from a fault Problem Source Instance. This field allows you to display faults based on the Problem Domain property. For example, the Problem Domain of Disk_Array (5400 or later systems) or MPPSS-DA (legacy systems) displays all disk array faults reported from the MPP service subsystem. The check boxes allow you to display faults with specific severity levels. You can select one or more of the following options: Unknown, OK, Information, Warning, Degraded, Critical, Fatal. All severity levels are selected by default. The check boxes allow you to display faults based on resolution states. You can select one or more of the following resolution states. All resolution states are selected by default. None: This denotes a problem that does not yet have a resolution. New faults are assigned this value initially. Under Investigation: This denotes a problem that is currently being investigated. Action Taken: This denotes that an action has been taken to resolve the fault. Auto Solved: This denotes a problem that has been automatically solved the status of the component associated with this fault is OK. Solved: This denotes that the problem has been solved. 128 Teradata AWS User Guide, Release 4.5

CHAPTER 6 Creating and Managing Cabinet Windows The commands in the Window > Cabinet Window submenu create separate Cabinet Windows that show different views of your system. A Cabinet Window contains icons that represent the cabinets and the AWS in the Tree View. The color of each cabinet or AWS icon matches severity of the highest fault in the cabinet. The color of the AWS icon also matches its fault severity. Figure 39: Cabinet Window Each cabinet icon has a letter that identifies its cabinet type. N: Processing node cabinet (SMP) B: BYNET cabinet D: Disk array cabinet Creating a Cabinet Window and Setting Its Display Options Cabinet Window Menu Bar Working with Cabinet Icons Saving, Opening, and Closing Cabinet Windows Tree View Pane and Windows on the AWS Desktop Fault Severities and Their Indicators Teradata AWS User Guide, Release 4.5 129

Chapter 6: Creating and Managing Cabinet Windows Creating a Cabinet Window and Setting Its Display Options Creating a Cabinet Window and Setting Its Display Options The commands in the Window > Cabinet Window submenu create separate Cabinet Windows that show different views of your system. For example, you can create a geographic view by arranging icons to represent how your system is physically arranged, or logical views by arranging icons in cliques and collectives. When you create a Cabinet Window, you set its display options, which include: The display name of the icons in the Cabinet Window The size of the icons The maximum size of the Cabinet Window The initial positions of the grid rows and columns Hiding or displaying a grid and specifying whether the icons snap to the grid. You can also change a Cabinet Window s display options after you create the Cabinet Window. Each new Cabinet Window displays on the AWS desktop. You can create and display more than one Cabinet Window at a time. Each Cabinet Window is labeled Cabinet Window, followed by a number, in the title bar. The number represents the order in which a Cabinet Window was created (Cabinet Window 1, for example). When you save a Cabinet Window, the file name replaces the default label in the title bar. Each Cabinet Window contains menus for working with Cabinet Windows or creating additional Cabinet Windows. New Cabinet Window and Cabinet Window Dialog Boxes Changing Cabinet Window Display Options Cabinet Window Menu Bar Working with Cabinet Icons Saving, Opening, and Closing Cabinet Windows To Create a Cabinet Window and Set Its Display Options 1 Do one of the following: To create a Cabinet Window containing icons of the AWS and all the cabinets displayed in the Tree View, do one of the following: Select Window > Cabinet Window > New > All Cabinets from the Teradata AWS menu bar. Select File > New > All Cabinets from the Cabinet Window menu bar. To create a blank Cabinet Window that you can populate later by dragging cabinets from the Tree View into the window, do one of the following: 130 Teradata AWS User Guide, Release 4.5

Chapter 6: Creating and Managing Cabinet Windows Creating a Cabinet Window and Setting Its Display Options Select Window > Cabinet Window > New > Blank from the Teradata AWS menu bar. Select File > New > Blank from the Cabinet Window menu bar.. 2 When the New Cabinet Window dialog box displays, use the information in Table 38 on page 132 to set the display options you want to use. Note: The New Cabinet Window dialog boxes do not display if the Tools > Options command has been used to clear the Prompt for Cabinet Window settings option. Note: You cannot specify a value of zero for any of the fields on the New Cabinet Window dialog box. 3 Click Ok. New Cabinet Window and Cabinet Window Dialog Boxes Figure 40: New Cabinet Window Dialog Box (New > All Cabinets Command, New > Blank Command) and Cabinet Window (Edit > Options Command) Dialog Boxes Teradata AWS User Guide, Release 4.5 131

Chapter 6: Creating and Managing Cabinet Windows Creating a Cabinet Window and Setting Its Display Options Table 38: Cabinet Window Dialog Box (Edit > Options) and New Cabinet Window Dialog Box (New > All Cabinets and New > Blank Commands) Descriptions Option Display Name Type Icon Size Max Width Max Height Column Width, or Horizontal Spacing Row Height, or Vertical Spacing Initial x-axis position Description Sets the name displayed beneath the icons in the Cabinet Window. The following options are available: Default: Displays the word Cabinet followed by the system, collective, and cabinet numbers, separated by dashes. Alias: Displays the cabinet s default Alias. If a user-defined Alias exists, it displays instead of the default Alias. Cabinet Numbers: Displays the system, collective, and cabinet numbers, separated by dashes. Component ID: Displays the cabinet s Component ID. Note: The AWS is always labeled as shown in the Tree View. Sets the size of the icons in the Cabinet Window to Small, Medium, or Large. Sets the maximum width of the Cabinet Window in pixels. If you specify a maximum width that is less than the space the icons currently occupy, a message displays asking you whether you would like to change the maximum width to a value that would include all of the icons in the Cabinet Window. Click Yes to include all of the icons. Note: If you click No, another message warns you that if you continue, the icons outside of the specified width will be deleted from the Cabinet Window. Sets the maximum height of the Cabinet Window in pixels. If you specify a maximum height that is less than the space the icons currently occupy, a message displays asking you whether you would like to change the maximum height to a value that would include all of the icons in the Cabinet Window. Click Yes to include all of the icons. Note: If you click No, another message warns you that if you continue, the icons outside of the specified height will be deleted from the Cabinet Window. Column Width sets the width between the grid columns in pixels. When the New > Blank command or the Cabinet Window s Edit > Options command is used, Column Width displays on the New Cabinet Window or Cabinet Window # dialog box, respectively. Horizontal Spacing sets the number of pixels placed between the center of an icon in one column to the center of an icon in the next column. When the New > All Cabinets command is used, Horizontal Spacing displays on the New Cabinet Window dialog box. Row Height sets the height between the grid rows in pixels. When the New > Blank command or the Cabinet Window s Edit > Options command is used, Row Height displays on the New Cabinet Window or Cabinet Window # dialog box, respectively. Vertical Spacing sets the number of pixels placed between the center of an icon in one row to the center of an icon in the next row. When the New > All Cabinets command is used, Vertical Spacing displays on the New Cabinet Window dialog box. Specifies how close the initial vertical grid line is, in pixels, from the left side of the Cabinet Window. The value of this option must be positive. The intersection of the Initial x-axis position and Initial y-axis position represent the location of the first icon added to the Cabinet Window. 132 Teradata AWS User Guide, Release 4.5

Chapter 6: Creating and Managing Cabinet Windows Creating a Cabinet Window and Setting Its Display Options Table 38: Cabinet Window Dialog Box (Edit > Options) and New Cabinet Window Dialog Box (New > All Cabinets and New > Blank Commands) Descriptions (continued) Option Initial y-axis position Show Grid Snap Cabinets to Grid Wrap icons around visible contents of window Description Specifies how close the initial horizontal grid line is, in pixels, from the top of the Cabinet Window. The value of this option must be positive. The intersection of the Initial x-axis position and Initial y-axis position represent the location of the first icon added to the Cabinet Window. Determines whether the grid displays. To display the grid, select the checkbox. The default is unchecked. Determines whether the icons should snap to the column and row intersections of the grid. To make the cabinet icons snap to the nearest intersections of the grid, select the checkbox. The default is unchecked. Note: If two or more cabinet icons are close to an intersection, the icons may overlap. Cabinets that overlap are marked with an x. You can use the Cabinet Window s Edit > Move command to move one of the icons to another location. This option is available when the New > All Cabinets command is used. If this option is checked, the Cabinet Window is populated with icons from left to right until the next icon is unable to fit within the visible contents of the Cabinet Window. When this occurs, a new row is started below the last row. If this option is unchecked, the Cabinet Window is populated with icons from left to right until the value within the Max Width field is reached. Note: If all the icons cannot fit within the area designated with the Max Width and Max Height fields, an error message displays. Changing Cabinet Window Display Options To Change Display Options for the Active Cabinet Window 1 Select or open a Cabinet Window. 2 Select the Cabinet Window s Edit > Options command. The Cabinet Window Options dialog box displays. It contains options for the active Cabinet Window. 3 Use the information in Table 38 on page 132 to set the options you want to use. Note: You cannot specify a value of zero for any of the fields on the Cabinet Window Options dialog box. 4 Click Ok. To Set the AWS Option for Cabinet Windows You can display or hide the New Cabinet Window dialog box when you select Cabinet Window commands from the Teradata AWS Window menu. Teradata AWS User Guide, Release 4.5 133

Chapter 6: Creating and Managing Cabinet Windows Cabinet Window Menu Bar 1 From the Teradata AWS menu bar, select the Tools > Options command. 2 In the Cabinet Window section of the Options dialog box, select or clear the option described in Table 39 on page 134. 3 Click Ok. Table 39: Teradata AWS Options Dialog Box (Tools > Options): Cabinet Window Option Prompt for Cabinet Window settings Description This check box allows you to specify whether you want the Teradata AWS to display a dialog box that prompts you for Cabinet Window settings when you select the Window > Cabinet Window > New > All Cabinets command or the Window > Cabinet Window > New > Blank command. If the dialog box does not display, you must use the Prompt for Cabinet Window settings option to redisplay. After you set this option, the dialog box that prompts you for Cabinet Window settings displays the next time you use the Blank or All Cabinets commands. The default is checked. Cabinet Window Menu Bar The following table describes the commands available from each menu in a Cabinet Window menu bar. Table 40: Cabinet Window Commands Contains commands for creating additional Cabinet Windows, and saving, opening, and closing Cabinet Windows. See: Creating a Cabinet Window and Setting Its Display Options on page 130 Saving, Opening, and Closing Cabinet Windows on page 137 Contains commands for working with the cabinet icons displayed in the Cabinet Window. See: Working with Cabinet Icons on page 135 Displays Cabinet Window help. See Using Teradata AWS Online Help on page 43. Access to Teradata AWS Commands 134 Teradata AWS User Guide, Release 4.5

Chapter 6: Creating and Managing Cabinet Windows Working with Cabinet Icons Working with Cabinet Icons Selecting Icons The Tree View and Cabinet Windows are designed to work together. Cabinet Windows complement the Tree View and allow you to create alternate views of your system. Severity levels correspond to the severity levels in the Fault Viewer. Selecting a cabinet or the AWS in the Tree View highlights the corresponding icon in a Cabinet Window. Selecting an icon in a Cabinet Window highlights the corresponding cabinet or AWS in the Tree View. Double-clicking a cabinet icon in a Cabinet Window expands or collapses the corresponding cabinet in the Tree View. Right-clicking a cabinet icon in a Cabinet Window displays a pop-up menu containing Teradata AWS commands relevant to cabinets. Deleting an icon from a Cabinet Window deletes the cabinet or AWS from the active Cabinet Window it does not delete the cabinet or AWS from the Tree View. You must use the Configuration > Remove Component command to delete a cabinet from the Tree View. Selecting Icons Arranging Icons Erasing or Replacing the Contents of a Cabinet Window Use the following methods to select and deselect the icons you want to move: Table 41: Cabinet Window: Commands for Selecting Cabinet Icons Method Cabinet Window s Edit > Select All command CTRL + Click Cabinet Window s Edit > Deselect All command Cursor Description Selects all of the icons in the Cabinet Window Selects and deselects one or more icons in the Cabinet Window Deselects all of the icons in the Cabinet Window Allows you to select a group of icons by dragging the cursor diagonally from one corner of the group to the other corner; the icons within the rectangle become selected Teradata AWS User Guide, Release 4.5 135

Chapter 6: Creating and Managing Cabinet Windows Working with Cabinet Icons Arranging Icons When icons are first placed in a Cabinet Window, the icons are locked and cannot be moved. You must select icons and use the Cabinet Window s Edit > Move command to unlock the icons and arrange them in the Cabinet Window, or to move icons if they overlap. Note: You can drag and drop the AWS and the cabinets from the Tree View into any Cabinet Window. After you select one or more cabinets in a Cabinet Window, you can use the following commands in the Cabinet Window s Edit menu and the keyboard to arrange the icons. Table 42: Cabinet Window: Commands for Manipulating Cabinet Icons Edit Menu Command or Keyboard Key Undo Redo Move Delete Options Description Removes the previous action Reinstates the previous action Unlocks icons in a Cabinet Window; you can select one or more icons and use the cursor to drag them into position or use the arrow keys to move them. Removes selected icons from a Cabinet Window. You can also use the Delete key. Note: Deleting an icon from a Cabinet Window does not delete it from the Tree View. To delete a cabinet from the Tree View, use the Configuration > Remove Component command. Allows you to set options for the Cabinet Window. Arrow Keys If the Edit > Move command is active, you can use the arrow keys to move a selected icon in the Cabinet Window. If the Snap Cabinets to Grid check box on the Options dialog box is selected, the icon moves to the next grid intersection in the specified direction. If the Snap Cabinet to Grid check box is not selected, the icon moves one pixel at a time. If the Edit > Move command is not active, you can use the arrow keys to select one icon and move the selection to the next icon in the specified direction. Tab Key Delete Key Shifts the active window among the Tree View, the Results Panel, and one or more Cabinet Windows. Removes selected icons from a Cabinet Window. Erasing or Replacing the Contents of a Cabinet Window After you create a Cabinet Window, you can use the commands on the Cabinet Window s menu bar to erase or replace its contents: The File > New > Blank command erases the contents of the active Cabinet Window. The File > New > All Cabinets command replaces the contents of the active Cabinet Window with cabinet icons that represent all the cabinets displayed in the Tree View. 136 Teradata AWS User Guide, Release 4.5

Chapter 6: Creating and Managing Cabinet Windows Saving, Opening, and Closing Cabinet Windows If you have made changes to a Cabinet Window, and then click File > New > Blank or File > New > All Cabinets, you are prompted to save the current Cabinet Window. Saving, Opening, and Closing Cabinet Windows You can use the following commands to save, open, and close Cabinet Windows on the AWS desktop. More than one Cabinet Window can be displayed at a time on the AWS desktop. Table 43: Cabinet Window: Commands for Saving, Opening, and Closing Cabinet Windows Command AWS menu bar: Window>Cabinet Window> >Open Cabinet Window menu bar: File > Open Cabinet Window menu bar: File > Save Cabinet Window menu bar: File>Save As Cabinet Window menu bar: File > Close Description Opens a previously saved Cabinet Window and places it on the AWS desktop Replaces the contents of the active Cabinet Window on the AWS desktop with a previously saved Cabinet Window Saves the active Cabinet Window on the AWS desktop and replaces the text in the title bar with the name of the file Renames and saves the active Cabinet Window on the AWS desktop and replaces the text in the title bar with the name of the file Closes the active Cabinet Window on the AWS desktop Teradata AWS User Guide, Release 4.5 137

Chapter 6: Creating and Managing Cabinet Windows Saving, Opening, and Closing Cabinet Windows 138 Teradata AWS User Guide, Release 4.5

CHAPTER 7 Checking the Health of the System The Teradata AWS application provides access to commands that allow you to check system and component health. Two main indicators of system health are: The operational states of components The severity of faults (if present) You can use Teradata AWS commands to view operational states, faults, fault severities, events, system messages, and methods for diagnosing and correcting faults. You can also configure the Teradata AWS so you receive alerts about problem conditions that require action. Events and System Health Faults and System Health Alerts Checking Collective (CMIC) Status Events and System Health The Event Consolidator collects operational events, problem events, and changes in system and component status and stores them in a database as events. In systems with SM3G server management, each CMIC contains an events database for the components in its collective. In systems with legacy server management, the AWS contains an events database for the components in the system. An event indicates a change in condition that may or may not require intervention. The change may be good, bad, or insignificant to the ongoing operation of the system. For example, events include changes due to operations performed on the system, such as power off, and problem events detected by the MPP server management system or reported to node event logs by node software. Checking Operational States of Components Operational States and Their Indicators Analyzing Events Teradata AWS User Guide, Release 4.5 139

Chapter 7: Checking the Health of the System Events and System Health Checking Operational States of Components Events and commands can change the operational states of components. Event Viewer Tree View Chassis Layout View Cabinet Status ShowComponents (Teradata AWS CLI Utility) Operational States and Their Indicators Event Viewer Events reported by server management (hardware events) or from a node s error logs (software events) are displayed in the Event Viewer (Event Mgmt > View Events). An event s severity reflects its impact at the component level or how urgent it is to fix the component. Events reported about status changes may include the operational status in the Event Viewer s Severity column. Note: Events that are determined to be serious enough to affect the ongoing operation of the system generate faults. Tree View In the Tree View, primary operational states are displayed in text to the right of each chassis or chassis component. One or more secondary operational states, if applicable or available, may appear to the right of the primary operational state. The text of the secondary operational state provides additional status information about the component. Operational state text is updated when an event or command changes a component s operational state. Chassis Layout View The View > Chassis Layout View command displays icons for the primary operational states of components in the selected chassis. If an event or command changes a component s operational state, the color icons are not updated until you use the command again. Cabinet Status The following commands display a Status window that allows you to check the operational states of cabinet components: The Window > Status Window command displays a Status window on the Teradata AWS desktop. The Status window contains the status of all the components in each cabinet in the system. Only one status window can be open at a time on the Teradata AWS desktop. The View > Status command displays a Status window that is separate from the Teradata AWS desktop. The Status window contains the status of the collectives and cabinets you 140 Teradata AWS User Guide, Release 4.5

Chapter 7: Checking the Health of the System Events and System Health selected. You can select one, more than one, or all collectives or cabinets. When you select a collective, the status of all of the cabinets in it displays. You can have more than one Status window open at a time. When an event or command changes a component s operational state, the component s color icon is automatically updated in the Status window. Figure 41: Status Window (Example: 5550 Cabinet) Each entry in the Status window is organized as follows: The system and collective number are displayed on the first line of the entry. Individual cabinet entries are displayed next. In each cabinet entry, icons representing the operational state of each chassis in the cabinet, including the CMIC, are displayed in a grid. To Check the Status of All the Components in the System Select Window > Status Window. To Check the Status of Components in Specific Collectives and Cabinets 1 In the Tree View, select one or more cabinets or one or more collectives, or a mixture of cabinets and collectives. 2 Select View > Status. To Hide or Display Components with Normal Operational States In the Status window, select or clear the Hide components that have normal operational states option. Teradata AWS User Guide, Release 4.5 141

Chapter 7: Checking the Health of the System Events and System Health To Display a Pop-up Menu for a Component in the Status Window In the Status window, right-click the component. The pop-up menu contains the same set of commands as the pop-up menu for the same component in the Tree View. To Display a Tool Tip Containing the Component Name and Operational State In the Status window, roll the cursor over the component. ShowComponents (Teradata AWS CLI Utility) The ShowComponents CLI utility displays system components and their operational status. : ShowComponents Operational States and Their Indicators Operational States and Their Indicators A component s operational state is represented by either text or color icons in an AWS GUI or CLI utility. A component s operational state does not reflect the operational state of the entire system. Table 44: Primary Operational States and Descriptions Tree View Text Status Window Icons Chassis Layout View Primary Operational State Description OK No action required; the component is operating normally. Warning The condition should be monitored; the component or subsystem is reporting a condition that does not threaten system operation, but if not remedied could worsen over time. Critical Immediate action should be taken; the component or subsystem will not continue to operate in this state Note: Critical conditions are often handled internally by components or subsystems, causing them to shut down. Fatal Immediate action must be taken to return the system to its normal operating state; the component or subsystem has failed. Unknown The component s severity level is unknown. 142 Teradata AWS User Guide, Release 4.5

Chapter 7: Checking the Health of the System Events and System Health Table 44: Primary Operational States and Descriptions (continued) Tree View Text Status Window Icons Chassis Layout View Primary Operational State Description Missing The component is expected to be present in the system, but is either not present (MISSING) or has not been detected. Powered Off The component is powered off. Analyzing Events This topic describes appropriate methods for analyzing events. To Use the Tree View and Event Viewer to Analyze a Problem To Use the ViewEvents CLI to Analyze Events Expanding and Collapsing the Tree View Tree View Operational States and Their Indicators To Use the Tree View and Event Viewer to Analyze a Problem 1 In the Tree View, expand the collectives and cabinets to show the rolled-up operational status of each CMIC and chassis. 2 Look for a CMIC or chassis with an abnormal operational state and expand it to view its components and their operational states. 3 Select the component with the abnormal status and display the Event Viewer (Event Mgmt > View Events). 4 Review the event history for the component and find the event that caused the operational status change. Note the time of the status change. 5 Review other events that occurred within that timeframe. 6 Select the cabinet that contains the component, then display the Fault Viewer (Event Mgmt > View Faults). 7 Use the time you noted earlier to find fault reports that may be associated with the event that caused the operational status change. Teradata AWS User Guide, Release 4.5 143

Chapter 7: Checking the Health of the System Faults and System Health To Use the ViewEvents CLI to Analyze Events 1 Log on to the AWS. 2 Select Start > Programs > Teradata AWS > AWS Command Prompt. 3 Obtain an event history for the time frame by including the time the event occurred. Redirect the output to a text file and use Notepad to view the text output. For example: viewevents -start mm/dd/yy hh:mm:ss -end mm/dd/yy hh:mm:ss -detail > c:\temp\events.txt Faults and System Health Events that are serious enough to affect the ongoing operation of the system generate faults. A fault is a report of a problem condition that requires attention to protect system availability. The Teradata AWS consolidates faults and stores them in the AWS fault database. A fault s severity reflects its impact at the system level, or how urgent it is to correct the problem condition. The MPP system and Teradata software include fault detection agents that report problem conditions. The fault detection agents in the MPP system are pre-configured to detect problem conditions for the following: Teradata Database BYNET SCSI adapters Fibre Channel adapters Disk arrays Node operating systems MPP platform hardware The problem conditions reflect known problem scenarios, such as configuration issues or potential hardware or software failures. The fault detection agents may also report indications of improving conditions. For example, if an event with an operational state of OK is available (the component is now operating normally), the resolution status of previously reported faults for the component can be changed to Auto Solved, indicating that the problem condition is resolved. Checking Fault Severities Receiving an Alert Notification About a Fault Responding to a Fault 144 Teradata AWS User Guide, Release 4.5

Chapter 7: Checking the Health of the System Faults and System Health Checking Fault Severities Fault Viewer Cabinet Window Fault Notification Window FaultUtil (Teradata AWS CLI Utility) Fault Severities and Their Indicators Fault Viewer System and component faults are displayed in the Fault Viewer (Window > Fault Viewer, Event Mgmt > View Faults). Fault properties include a comprehensive description of the problem, its probable causes, and recommended actions to take to resolve the problem. The Fault Viewer shows the severity of each fault that affects the system and provides commands to track and manage the progress of fault resolution. By default, the Fault Viewer displays the open list of faults in the right pane of the Teradata AWS. The icon to the left of a fault indicates the fault s severity. When the fault is closed and removed from the open list of faults, the color of the icon is not updated. The Fault Viewer integrates with remote support through Teradata Vital Infrastructure (TVI). Significant events or faults can be escalated through TVI. Cabinet Window The color of each cabinet or AWS icon in the Cabinet Window reflects the highest fault severity for a component in a cabinet or AWS. For example, if a disk array cabinet icon is red, it signifies that the cabinet contains a component with a fatal fault severity. When the fault is closed and removed from the open list of faults, the color of the icon is updated to indicate the severity of the next highest fault in the cabinet. Fault Notification Window The color of the background of the Fault Notification window indicates the highest fault severity since the window was last reset. FaultUtil (Teradata AWS CLI Utility) The FaultUtil CLI provides a command line interface to view and manage faults. The -severity option allows you to display fault severities. Teradata AWS User Guide, Release 4.5 145

Chapter 7: Checking the Health of the System Faults and System Health Fault Severities and Their Indicators A component s fault severity is represented by either text or color icons in an AWS GUI or CLI utility. The following Teradata AWS commands and features show fault severities: Table 45: Fault Severity Indicators and Descriptions Severity Level Fault Viewer Icon Color of Cabinet Window Icon Color of Fault Notification Window Icon Description Unknown Gray Gray The severity level of the problem is unknown. OK Green Green Indicates that a component s status has returned to normal. Faults generated by the system do not have a severity level of OK, but an event indication with a severity level of OK can be used to Auto Solve existing faults. Faults that you submit may have a severity level of OK. Information Blue Blue An informational message that draws attention to an event that changes some characteristic of the subsystem but leaves all aspects of its operation at the same level, or draws attention to an event that signifies the restoration of a previously diminished subsystem. No further degradation is anticipated. Warning Yellow Yellow A warning message that draws attention to a condition that, if not addressed, could become a more serious problem. The subsystem is still fully functional at the same level of performance. Degraded Orange Orange The subsystem is degraded; an event has left the subsystem fully functional but at a lesser performance level. Critical Magenta Magenta The subsystem is down; the event is a certain forerunner to a more fatal event. Fatal Red Red The subsystem is down; the event has caused the subsystem to stop. Faults and System Health Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer. Chapter 6: Creating and Managing Cabinet Windows. Configuring and Using the Fault Notification Window Receiving an Alert Notification About a Fault After staging, the AWS is configured to ensure that faults appear in the Fault Viewer in the event of any device failure or Teradata-supplied software failure. You should configure alerts to ensure that the appropriate personnel at your site receive alert notifications. After receiving an alert notification, system administrators and Customer Services personnel use the Fault Viewer to investigate and resolve faults, and the Event Viewer to view events that may have led up to the problem condition. 146 Teradata AWS User Guide, Release 4.5

Chapter 7: Checking the Health of the System Faults and System Health When you receive an alert notification, such as the display of the Fault Notification window on the AWS, or an alert message sent through e-mail, a page, or a customized program or script, it indicates that a fault requires your attention. The alert message typically contains the name of the AWS, a Fault ID, and the time the fault occurred. Faults and System Health Responding to a Fault AWS Alert Notification Appendix C: Configuring Alerts. Responding to a Fault Although this topic focuses on responding to an alert notification, it also describes an appropriate fault resolution strategy to use when resolving faults. To Use the Fault Viewer to Respond to and Resolve a Fault To Use the FaultUtil CLI to Analyze a Fault To Use the Fault Viewer to Respond to and Resolve a Fault 1 Log on to the AWS. 2 Open the AWS Fault Viewer. 3 Find the fault in the Fault Viewer. 4 Select the fault and review the fault report using the Fault Viewer s Functions > View Details command. 5 Examine other faults that occurred that may be associated with the same problem. 6 Review the recommended actions for the faults by selecting the Fault Viewer s Functions > View Details command and doing one or both of the following: a Use the Problem Description field in the detail window to review Customer Service-supplied recommendations. b Use the Journal field in the detail window to review user-defined recommendations. 7 If further diagnosis is needed, do one or both of the following: a b Use the AWS Event Viewer to look for events that occurred in the same time frame. You can limit the events displayed in the Event Viewer by selecting the chassis the fault was reported in. Look for a past history of the same problem or problems by displaying the Fault Viewer s Closed faults and filtering them using the same Problem Domain and Problem Teradata AWS User Guide, Release 4.5 147

Chapter 7: Checking the Health of the System Alerts Code as the fault you are trying to resolve. Look at the previous fault s Journal for tips on how to resolve the current fault. 8 Resolving a fault includes the following optional steps: a b c Performing actions given in the recommendations. Writing comments in the fault Journal concerning investigations and actions taken. Changing the fault s Resolution State as the fault progresses through the stages of investigation, action taken, and solved. 9 Use the Fault Viewer s Functions > Close Fault command to close the fault when it is solved or when it is no longer necessary to track it as an open problem. The fault and the entries you made to track its resolution is then archived in the closed fault list. To Use the FaultUtil CLI to Analyze a Fault The FaultUtil CLI can be used as an alternative when analyzing faults. If you received an Alert message containing a Fault ID, use the following procedure: 1 Log on to the AWS. 2 Select Start > Programs > Teradata AWS > AWS Command Prompt. 3 Use the Fault ID in the following command line to display all the fault information stored in the fault database about this occurrence: faultutil -id {faultid} -detail 4 Obtain a fault or event history for the time frame by including the time the fault occurred, and redirect the output to a text file. For example: faultutil -open -start mm/dd/yyyy hh:mm -end mm/dd/yyyy hh:mm -detail > faults_out.txt viewevents -start mm/dd/yy hh:mm:ss -end mm/dd/yy hh:mm>:ss -detail > events_out.txt 5 Use Notepad or another text editor to view the text output files. Alerts An alert is a notification mechanism or message that indicates that a fault or significant event requires attention. AWS alert mechanisms offer various methods for alerting you to problem conditions, including e-mail messages and pages. You must configure or customize some of these alert mechanisms to set up your preferences for receiving alerts. Note: You can also run a specified program or script in response to a fault. 148 Teradata AWS User Guide, Release 4.5

Chapter 7: Checking the Health of the System Alerts AWS Alert Notification The AWS provides a set of alert mechanisms. AWS alert mechanisms are either visible on the AWS workstation or result in an alert action, such as the sending of an e-mail. You can configure the AWS s alert mechanisms so that you are notified about a problem condition requiring your attention. You can receive one or more of the following types of alert notifications listed in the table. All are configurable. Table 46: Alert Notification Descriptions Alert Notification Cabinet Window icons Fault Notification window Alert e-mail message Alert page message Alert run program Description When an event changes the fault severity level of a component, the color of the cabinet icon changes to indicate the severity of the highest-level open fault in the cabinet. You can activate a Fault Notification window that alerts you to new faults. Each time a new fault is reported to the Fault Manager, the Fault Notification window opens on the AWS. You can use the AWS Configuration application to configure the e-mail service, then the AlertRegister CLI program to specify when you will be notified of faults by e-mail. You can use the AWS Configuration application to configure the paging service, then the AlertRegister CLI program to specify when you will be notified of faults by being paged. You can use the AlertRegister CLI program to specify a custom action, such as running a command line (for example, to send a net send message) or running a program or script that sends a message to an enterprise manager. Configuring and Using the Fault Notification Window Using the Alert Manager Mail Tab to Configure a Mail Service Registering Alert Actions Using the Alert Manager Page Tab to Configure a Page Service Configuring the Alert Dispatch Service User Account Appendix C: Configuring Alerts. Teradata AWS User Guide, Release 4.5 149

Chapter 7: Checking the Health of the System Checking Collective (CMIC) Status Checking Collective (CMIC) Status The Window > Collective Management View command displays the Collective Management window (Figure 42) on the AWS desktop. The window shows each CMIC in the system (identified by its system, collective, cabinet, and chassis ID) and displays information about the CMIC and the collective it manages. Figure 42: Collective Management Window Table 47: Collective Management Window Description Item CMIC ID Primary Network Secondary Network Availability Primary Availability Secondary Availability Collectives Hosted CMIC Nodes Hosted Version Description Shows the system, collective, cabinet, and chassis ID numbers of the CMIC Shows the IP address of the CMIC s primary network connection Shows the IP address of the CMIC s secondary network connection Shows the overall status of the CMIC, indicating whether the CMIC is up, resetting, or unavailable Shows the status of the CMIC s primary network, indicating whether the CMIC is up, resetting, or unavailable Shows the status of the CMIC s secondary network, indicating whether the CMIC is up, resetting, or unavailable Shows the collective ID numbers of all collectives managed by the CMIC Shows the collective ID numbers of the other CMICs the CMIC is monitoring. For more information, see the Platform Hardware Installation and Service Guide. Displays the CMIC Image version installed on the CMIC. To install the latest available version, see the Platform Hardware Installation and Service Guide. 150 Teradata AWS User Guide, Release 4.5

CHAPTER 8 Viewing and Updating Component Information This section discusses viewing and updating information about components. Viewing Properties of Components You can select and view the properties of only one system, collective, cabinet, component, or sub-component at a time. To View Component Properties 1 In the Tree View, select a component. 2 Select the View > Properties command. To Display Property Descriptions In the Properties dialog box, select the Description button. To Hide or Display Properties with Empty Values In the Properties dialog box, select or clear Do not display empty property values. Displaying an Image of Chassis Components The View > Chassis Layout View command displays a printable, digital image of a chassis and its components. A series of windows are used to select the view containing the chassis or chassis component. The windows also display a color icon indicating the operating state of chassis components. The series of windows differs depending on the type of component you select. Each window s title bar contains the following information: the window name (Chassis Layout View), and the path to the chassis you selected in the Tree View. The following example shows the series that displays for a UPS. Teradata AWS User Guide, Release 4.5 151

Chapter 8: Viewing and Updating Component Information Displaying an Image of Chassis Components Figure 43: Chassis Layout View: Window Series for Non-Disk Array Chassis Note: The same series of windows displays when you use the Functions > Replace FRU command. However, the window name in the title bar is Replace FRU instead of Chassis Layout View. To Display an Image of a Chassis, Its Components, and Component Operational States Choose a Layout View Chassis Layout View To Display an Image of a Chassis, Its Components, and Component Operational States 1 In the Tree View, select a chassis. 2 Select the View > Chassis Layout View command. If you selected one of the following chassis, a Choose a Layout View window displays. CMIC SMC (systems with legacy server management) Node SMP (systems with legacy server management) BYNET chassis (except 1 U) UPS Fibre channel switch 152 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Displaying an Image of Chassis Components Choose a Layout View If you selected a 1U BYNET chassis, a digital image of the chassis displays. If you selected a disk array (MDA in systems with legacy server management, Disk Array in systems with SM3G), a window containing a digital image of the disk array controller and its disks displays. Do one of the following: In the Key list, select a component or circle. The Choose a Layout View window displays. To print the digital image, select the Print button. To discontinue the procedure and close the window, click the Close button. After you select and chassis in the Tree View, then select the View > Chassis Layout View command, the Choose a Layout View window displays. The window contains a list of the components in the selected chassis. The components are sorted into columns based on their location in the chassis (front, internal, rear). The operational state of each component displays next to the component. The UPS chassis shown below is an example of a Choose a Layout View window. Figure 44: Chassis Layout View: Choose a Layout View Item Front View, Internal View, Rear View Temperature Close button Description To display a digital image of chassis components, find the component in the list, then select the button at the top of the list. Chassis temperature sensor; the color of the rectangle corresponds to the chassis operational state displayed in the Tree View. A chassis can have one or more temperature sensors. Discontinues the procedure and closes the window. Teradata AWS User Guide, Release 4.5 153

Chapter 8: Viewing and Updating Component Information Displaying an Image of Chassis Components Chassis Layout View After you select a chassis in the Tree View, then select the View > Chassis Layout View command, then select the appropriate View button from the Choose a Layout View window, the Chassis Layout View window displays. It contains a digital image of the view you selected. The UPS chassis shown below is an example of a Chassis Layout View window. Figure 45: Chassis Layout View Window Item Circled numbers Key Close button Print button Description Correspond to the items listed in the Key. The color in the numbered circle corresponds to a component s operational state in the Tree View. Note: When you use the Functions > Replace FRU command, replaceable components are represented by numbers in rectangles. Lists the components represented in the digital image. The components correspond to the components displayed in the Tree View. Discontinues the procedure and closes the window. To print the image, click the Print button. If you have a color printer, the numbered circles are printed in color. You can use the printout as a visual reference if you need to locate the component in the chassis. 154 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Asset Information Tracking Asset Information Viewing Asset Information When CMIC and node data collection agents (DCAs) detect changes to the hardware, software, and firmware information of components, they store the changes as asset records in the Asset Database. Types of asset records include inventory information (such as model numbers, serial numbers, and part numbers), battery installation dates, and revision levels for components. You can track asset information for a system or one or more collectives, cabinets, or chassis. For example, you can visually verify correct firmware versions across all UPS chassis in the system, or that a particular BYNET board part number is present in the system. Customer Services personnel use the following commands to track asset information: The View > Asset Information command displays current asset records. The Event Mgmt > View Asset History command displays a history of changes to asset records. In systems with legacy server management, the Legacy Support > Update Asset Information command is typically used to update information when a FRU is replaced. The information is stored as asset information and is usually changed only by Customer Services personnel. Viewing Asset Information Viewing Asset History Generating a Baseline of System Assets and SHR Data Updating Asset Information for Components in Systems with Legacy Server Management The View > Asset Information command provides a consolidated view of the current asset records stored in the Asset Database. You can save the information in.txt or.csv file format for later reference. Selecting Chassis and Displaying Asset Information If you select more than one chassis, the following applies: If you select components of the same type, for example, all CMICs, the Common Identification Fields displays all available asset records for that type. If you select components of different types, the Common Identification Fields displays only the asset records that are common to all the components. Teradata AWS User Guide, Release 4.5 155

Chapter 8: Viewing and Updating Component Information Tracking Asset Information To Select Chassis and Display Asset Information 1 In the Tree View, select the system or one or more collectives, cabinets, or chassis. Note: You can also use the Functions > Multi-Select Command to make selections and run the Asset Information command. 2 Select the View > Asset Information command. The Asset Information dialog box displays. See Table 48 for a description of the dialog box. Figure 46: Asset Information Dialog Box Table 48: Asset Information Dialog Box Description Option Selected Components Common Identification Fields Description Displays the components you selected in the Tree View. Displays fields common to chassis of the same type. To select one or more fields, use CTRL+click or SHIFT+click. If no fields are selected, all fields are included in the output. 3 To display the Asset Information View window, click Ok. 156 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Asset Information The Asset Information View Window The Asset Information View window contains asset records for the chassis you selected with the View > Asset Information command or Functions > Multi-Select Command. The arrow indicates which column the information is sorted by, and whether the information is sorted in ascending (up arrow) or descending (down arrow) order. Figure 47: Asset Information View Window Table 49: Asset Information View Window Description Label Chassis Unit Asset Name Property Name Property Value Description Path, default alias, or component ID of the chassis, depending on the option set for the Tree View: If the Default option is set, the path follows the hierarchy displayed in the Tree View. If the Alias option is set, the default alias displays. If a user-defined alias exists, it is displayed instead of the default alias. If the Component ID option is set, the CIM path displays. Chassis component whose asset record displays Name of the chassis component asset whose asset record displays Type of asset record displayed (type of hardware, software, or firmware asset information) Asset information Teradata AWS User Guide, Release 4.5 157

Chapter 8: Viewing and Updating Component Information Tracking Asset Information The Asset Information View Menu Bar The following table describes the commands available from the menu in the Asset Information View menu bar. Table 50: Asset Information View Commands The File menu contains commands for saving asset records to a file and closing the Asset Information View window. See: To Save Displayed Asset Information to a File on page 158 To Close the Asset Information View Window on page 158 Working with the Asset Information View Window Note: For a description of the Asset Information View window, see Table 49 on page 157. To Sort Asset Records by Column Click the appropriate column header. To toggle between ascending and descending order, click the column header. To Save Displayed Asset Information to a File 1 From the Asset Information View window, do one of the following: a To save the information in plain text format (.txt) that can be viewed with Notepad or a similar text editor, select File > Text. b To save the information in comma separated value format (.csv) that can be viewed with Microsoft Excel or a similar spreadsheet application, select File > CSV. 2 When the Save dialog box displays, enter a file name and location, then click Save. To Close the Asset Information View Window From the Asset Information View window, click File > Close. Viewing Asset History The Event Mgmt > View Asset History command displays a history of chassis asset change records stored in the Asset Database. You can save the displayed information in.txt or.csv file format for later reference. The command options allow you to specify a time frame and the number of records to display. For example, if you want to see all changes to the BIOS version for a specific CMIC over the last week, select the CMIC, specify the number of records you want to display, specify a time interval of seven days, and sort the columns by Asset Name to find the BIOS records. Note: If one week s worth of records exceeds the number of records displayed, you can use the Next button in the View Asset History window to display the remaining records. 158 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Asset Information Selecting Components and Displaying Their Asset Record History The View Asset History Window The View Asset History Menus Working with the View Asset History Window Selecting Components and Displaying Their Asset Record History To Select Components and Display Asset Record History by Number of Records and Time Span 1 In the Tree View, select the system or one or more collectives, cabinets, or chassis. Note: You can also use the Functions > Multi-Select Command to make selections and run the View Asset History command. 2 Select the Event Mgmt > View Asset History command. 3 From the View Asset History options dialog box, use the information in Table 51 to specify what you want to see. Figure 48: View Asset History Dialog Box Teradata AWS User Guide, Release 4.5 159

Chapter 8: Viewing and Updating Component Information Tracking Asset Information Table 51: View Asset History Dialog Box Description Option Description Number of Records Returned Number of records to display Specifies the maximum number of records to display in the View Asset History window: 50 records 100 records 200 records 300 records 400 records 500 records 1,000 records 2,000 records Time Selection Do not limit time Records before this time Records after this time Records between this time Records for the last Displays the most recent record first Displays records recorded before the date and time you specify in the text box Displays records recorded after the date and time you specify in the text box Displays records recorded between the two dates and times you specify in the text boxes Displays records recorded within the time frame you specify in the list (1-60 seconds, minutes, hours, or days) 4 To display the View Asset History window, click Ok. 160 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Asset Information The View Asset History Window The View Asset History window contains the asset records of each chassis you selected with the Event Mgmt > View Asset History command. The arrow indicates which column the information is sorted by, and whether the information is sorted in ascending (up arrow) or descending (down arrow) order. Figure 49: View Asset History Window Table 52: View Asset History Window Description Options Records for Previous/Next buttons Description Contains the path, default alias, or component ID of the chassis, depending on the option set for the Tree View: If the Default option is set, the path follows the hierarchy displayed in the Tree View. If the Alias option is set, the default alias displays. If a user-defined alias exists, it displays instead of the default alias. If the Component ID option is set, the CIM path displays. If one chassis is selected, this field is not displayed. If the number of records retrieved (based on the Time Selection option) exceeds the Number of records to display, the Next and Previous buttons allow you to display more records. Chassis Unit Contains the path, default alias, or component ID of the chassis, depending on the option set for the Tree View. Chassis component whose asset record is displayed Teradata AWS User Guide, Release 4.5 161

Chapter 8: Viewing and Updating Component Information Tracking Asset Information Table 52: View Asset History Window Description (continued) Options Asset Name Modification Date Change Status Property Name Property Value Type Model Last Seen Date Managed Element ID GUID Description Name of the chassis component asset whose asset record is displayed Date the asset was modified Type of change the CMIC detected: New: CMIC has no previous knowledge of this asset Missing: CMIC expects the asset to be there, but the asset is absent Replaced: CMIC detected that the asset was missing, but the asset now exists Changed: CMIC detected a new value for an existing asset Same: Indicates the asset monitors (CMICs and node DCAs) have not detected a change in the asset. Not all asset monitors use Same. When Same is reported, only the LastSeenDate of the asset property is updated. Type of asset record displayed (type of hardware, software, or firmware asset information) Asset information Chassis type (node, UPS, and so forth) Chassis model Date the component was detected during the last CMIC or node reboot; this date is usually more current than the Modification Date and is used to track the component s life cycle changes CIM path of the component whose measurement information is displayed; this is the unique name assigned to the component. A unique global identifier for an event; when the CMIC detects a change in a component s asset record, it is logged as an event and assigned a GUID in the Event Viewer 162 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Asset Information The View Asset History Menus The following table describes the commands available from each menu in the View Asset History menu bar. Table 53: View Asset History Commands Contains commands for saving asset history and closing the View Asset History window. See: To Save Displayed Asset History to a File on page 164 To Close the View Asset History Window on page 164 Allows you to search for text string. See: To Search Asset History Records on page 164. Allows you to update the information in the View Asset History window. Allows you to find a component in the Tree View. See: To Update the View Asset History Window on page 164. See: To Locate a Component in the Tree View on page 164. Displays help for the View Asset History window. See: Using Teradata AWS Online Help on page 43. Working with the View Asset History Window Note: For a description of the columns in the View Asset History window, see Table 52 on page 161. To Sort Asset History Records by Column Click the appropriate column header. To toggle between ascending and descending order, click the column header. To Display or Hide a Column The View Asset History window contains all the columns described in Table 52. To display or hide one or more columns: 1 Right-click any column header. The displayed pop-up menu contains the names of all the available columns. Check-marks beside column names indicate which columns are currently displayed. 2 On the pop-up menu, select a column header to display it, or clear a column header to hide it. Teradata AWS User Guide, Release 4.5 163

Chapter 8: Viewing and Updating Component Information Tracking Asset Information To Save Displayed Asset History to a File 1 From the View Asset History window, do one of the following: a b To save the information in plain text format (.txt) that can be viewed with Notepad or a similar text editor, select File > Text. To save the information in comma separated value format (.csv) that can be viewed with Microsoft Excel or a similar spreadsheet application, select File > CSV. 2 When the Save dialog box displays, enter a file name and location, then click Save. To Search Asset History Records 1 Select the Search > Find command. 2 Use the Find dialog box to search for text strings. To Update the View Asset History Window When the window displays, the table does not automatically update if measurement information changes. To update the window, select the View > Refresh command. To Locate a Component in the Tree View 1 In the View Asset History window, select an asset record in the table. 2 Select the Functions > Locate Component command. The component for which the measurement was performed is highlighted in the Tree View. To Close the View Asset History Window From the View Asset History window, click File > Close. 164 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Asset Information Generating a Baseline of System Assets and SHR Data The Tools > System Asset Baseline command takes a snapshot of a system s asset information and System Health Report (SHR) data. The asset information is collected into one report (AssetBaseline.xml) and the SHR data is collected into another report (SHR.xml). The asset information and SHR data files are saved locally and are also sent to Customer Services for inclusion in the Customer System Information (CSI) database. It is recommended that the System Asset Baseline command be used at initial configuration and after changes to a configuration. To generate a complete SHR report, the shr_collect.pl script and shrdca.pl script must be installed on all Linux and MP-RAS nodes and the AWS. If the scripts are not installed, the command creates and sends the SHR report, but there is no data for the nodes or AWS that do not have the scripts. Note: If the System Asset Baseline command does not complete, asset information and SHR data is not collected and saved. Note: The command does not log on to the customer s Teradata Database or save any customer network configuration data. Asset Baseline Data SHR Data System Asset Baseline Error Messages Asset Baseline Data Asset data consists of information about cabinet hardware, such as firmware versions, serial numbers, product IDs, and so forth. The System Asset Baseline command collects, saves, and sends asset information as follows: If there is a pre-sm3g system, the AWS communicates with TAS (TVI Administration System) to retrieve data collection agent (DCA) asset reports for legacy nodes Removes and updates stale or orphaned asset information Updates SM3G DCA-generated asset information Gathers all available, current asset information for each chassis in the system Formats the asset data in XML and saves the output to the <drive:>\program Files\Teradata\SM3G AWS\Data\AssetBaseline.xml file Adds the system s Site ID to the asset file, zips the file, and sends it to the TAS outbox for transmission to Teradata Customer Services; the asset file is fragmented and reassembled when necessary Teradata AWS User Guide, Release 4.5 165

Chapter 8: Viewing and Updating Component Information Tracking Asset Information SHR Data SHR data includes information about operating system and Teradata Database configuration. After the asset baseline data is sent, the command collects, saves, and sends SHR data as follows: Gathers system level, node level, and array level System Health Report (SHR) data from Linux and MP-RAS nodes Formats the SHR data in XML and saves the output to the <drive:>\program Files\Teradata\SM3G AWS\Data\SHR.xml file Adds the system s Site ID to the SHR file, zips the file, and sends it to the TAS outbox for transmission to Teradata Customer Services To Generate a Baseline of System Assets and SHR Data Caution: For a successful completion of an asset baseline and SHR, the System Asset Baseline command must be able to communicate with all the chassis it is updating or getting asset information from. The TAS service must also be running on the AWS, and the appropriate levels of TAS and TVI software must be running on the AWS and all of the nodes. Before running the command, check the status of the system to make sure the components are in an OK state. Note: Depending on the size of the system, the command may take awhile to complete. 1 Select Tools > System Asset Baseline. 2 When the System Asset Baseline dialog box displays, click Ok. Generating a baseline consists of several steps. A progress indicator displays for each step. The following figure shows the System Asset Baseline dialog box for an SM3G system. For pre-sm3g systems and coexistence systems, an additional step, Retrieve Legacy Node DCA Assets, is performed. 166 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Asset Information Note: If an error message displays, see System Asset Baseline Error Messages on page 167. 3 To view the output, open the following files: Asset information: <drive:>\program Files\Teradata\SM3G AWS\Data\AssetBaseline.xml SHR data: <drive:>\program Files\Teradata\SM3G AWS\Data\SHR.xml System Asset Baseline Error Messages If one of the following TAS error messages displays, the System Asset Baseline command does not complete the baseline. TAS command timed out TAS was not able to contact node TAS failed to send command TAS was not able to locate node Internal TAS exception TAS has stopped Unknown TAS error Other errors may also occur that prevent the command from completing successfully. Once the problems have been corrected, you can select the command again. Teradata AWS User Guide, Release 4.5 167

Chapter 8: Viewing and Updating Component Information Tracking Asset Information Updating Asset Information for Components in Systems with Legacy Server Management In systems with legacy server management, asset information is typically updated by Customer Services personnel on the following chassis: SMC chassis BYNET chassis SMP chassis Disk Array chassis UPS chassis Note: Asset information is automatically updated in systems with SM3G server management. Depending on the node type, UPS type, and other system variables, the information displayed differs. For example, the UPS contains the date the battery was installed so battery aging can be tracked. Additional information is automatically recorded when the component is installed. Although it displays on the Update Asset Information dialog box, it cannot be edited. All asset information recorded for a component can be displayed with the View > Asset Information command. To Update Asset Information for Components in Systems with Legacy Server Management Viewing Asset Information To Update Asset Information for Components in Systems with Legacy Server Management 1 In the Tree View, select one or more chassis whose asset information you want to update. 2 Select the Legacy Support > Update Asset Information command. If you select more than one chassis, a separate Asset Information window displays for each chassis. The title bar contains the path to the chassis you selected in the Tree View. If an SMP cabinet is selected, a window like the one in the following figure displays. 3 To update the asset information, edit the fields and click Ok. The table shows some of the fields that can be edited for each chassis type: 168 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Figure 50: Update Asset Information Dialog Box Table 54: Update Asset Information Dialog Box Description The following field: Chassis Model No. Chassis Serial No. MB Serial No. MB Assembly No. CMIC Part No. Appears on the Update Asset Information dialog boxes for the following components: SMC chassis, BYNET chassis, disk array chassis SMC chassis, BYNET chassis, disk array chassis SMC chassis, BYNET chassis, SMP nodes, UPSs, disk array chassis SMC chassis, BYNET chassis, SMP nodes, UPSs, disk array chassis SMC chassis (if a CMIC is present in the SMC chassis) Tracking Chassis Measurement Information CMICs record measurement information from collectives and store the information in the CMIC Measurement Database. Measurement information includes data from node, CMIC, UPS, BYA32S, and Fibre Channel switch chassis hardware sensors (for example, power, temperature, and cooling) and CMIC software performance monitors. The measurement data is recorded and stored in the database at eight-hour intervals, and when a CMIC boots. Customer Services personnel use the following commands to access measurement information for debugging and trend analysis. The View > Measurement Information command displays current chassis measurement data. The Event Mgmt > View Measurement History command displays a history of chassis measurement data based on a time interval and number of records. Teradata AWS User Guide, Release 4.5 169

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Note: The Measurement Information and View Measurement History commands are not available for chassis in systems with legacy server management (chassis in Collective 0). Viewing Measurement Information Viewing Measurement History Viewing Measurement Information The View > Measurement Information command displays current measurement information stored in the CMIC Measurement Database. You can save the information in.txt or.csv file format for later reference. Note: Measurement information is available for node, CMIC, UPS, BYA32S, and Fibre Channel switch chassis; it is not available for disk array and other BYNET chassis. Note: The Measurement Information command is not available for legacy chassis (chassis in Collective 0). Selecting Chassis and Displaying Measurement Information The Measurement Information View Window The Measurement Information View Menu Bar Working with the Measurement Information View Window Selecting Chassis and Displaying Measurement Information When you select chassis of the same type, you can select and display measurement information for specific fields common to that chassis type. For example, if you select one or more CMIC chassis, you can select and display measurement information for all system baseboard fans in each CMIC chassis. When you select a system or one or more collectives, cabinets, or chassis that are not of the same type, there are no common information fields to display. To Select Chassis and Display Chassis Measurement Information 1 In the Tree View, select the system or one or more collectives, cabinets, node chassis, CMIC chassis, UPS chassis, BYA32S chassis, and Fibre Channel switch chassis. Note: You can also use the Functions > Multi-Select Command to make selections and run the Measurement Information command. 2 Select the View > Measurement Information command. The Measurement Information dialog box displays. 170 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Figure 51: Measurement Information Dialog Box Table 55: Measurement Information Dialog Box Description Option Selected Components Common Identification Fields Description Displays the components you selected in the Tree View. Displays fields common to chassis of the same type. To select one or more fields, use CTRL+click or SHIFT+click. If no fields are selected, all fields are included in the output. 3 To display the Measurement Information View window, click Ok. The Measurement Information View Window The Measurement Information View window contains measurement information for the chassis you selected with the View > Measurement Information command or the Functions > Multi-Select Command. The arrow indicates which column the information is sorted by, and whether the information is sorted in ascending (up arrow) or descending (down arrow) order. Teradata AWS User Guide, Release 4.5 171

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Figure 52: Measurement Information View Window Table 56: Measurement Information View Window Description Option Chassis Location Property Name Property Unit Property Value Description Path, default alias, or component ID of the chassis, depending on the option set for the Tree View: If the Default option is set, the path follows the hierarchy displayed in the Tree View. If the Alias option is set, the default alias displays. If a user-defined alias exists, it is displayed instead of the default alias. If the Component ID option is set, the CIM path displays. Chassis component whose measurement information is displayed Type of measurement information displayed for the chassis component Units the measurement information is recorded in Measurement The Measurement Information View Menu Bar The following table describes the commands available from the menu in the Measurement Information View menu bar. Table 57: Measurement Information View Commands The File menu contains commands for saving measurement information to a file and closing the Measurement Information View window. See: To Save Displayed Measurement Information to a File on page 173 To Close the Measurement Information View Window on page 173 172 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Working with the Measurement Information View Window Note: For a description of the Measurement Information View window, see Table 56 on page 172. To Sort Measurement Information by Column Click the appropriate column header. To toggle between ascending and descending order, click the column header. To Save Displayed Measurement Information to a File 1 From the Measurement Information View window, do one of the following: a To save the information in plain text format (.txt) that can be viewed with Notepad or a similar text editor, select File > Text. b To save the information in comma separated value format (.csv) that can be viewed with Microsoft Excel or a similar spreadsheet application, select File > CSV. 2 When the Save dialog box displays, enter a file name and location, then click Save. To Close the Measurement Information View Window From the Measurement Information View window, click File > Close. Viewing Measurement History The Event Mgmt > View Measurement History command displays a history of chassis measurement information stored in the CMIC Measurement Database. You can save the displayed information in.txt or.csv file format for later reference. The command options allow you to specify a time frame and the number of records to display. For example, if you want to see all temperature measurements for a specific node chassis over the last week, select the node chassis, specify the number of records you want to display, and specify a time interval of seven days. Note: If one week s worth of records exceeds the number of records displayed, you can use the Next button in the View Measurement History window to display the remaining records. Note: Measurement information is available for node, CMIC, UPS, BYA32S, and Fibre Channel switch chassis; it is not available for disk array and other BYNET chassis. Note: The View Measurement History command is not available for chassis in systems with legacy server management (chassis in Collective 0). Selecting Chassis and Displaying Their Measurement History Records The View Measurement History Window The View Measurement History Menus Working with the View Measurement History Window Teradata AWS User Guide, Release 4.5 173

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Selecting Chassis and Displaying Their Measurement History Records To Select Chassis and Display Measurement History by Number of Records and Time Span 1 In the Tree View, select the system or one or more collectives, cabinets, node chassis, CMIC chassis, UPS chassis, BYA32S chassis, or Fibre Channel switch chassis. Note: You can also use the Multi-Select Command to make selections and run the View Measurement History command. 2 Select the Event Mgmt > View Measurement History command. 3 From the View Measurement History options dialog box, use the information in Table 58 to specify what you want to see. Figure 53: View Measurement History Dialog Box Table 58: View Measurement History Dialog Box Description Option Description Number of Records Returned Number of records to display Specifies the maximum number of records to display in the View Measurement History window: 50 records 100 records 200 records 300 records 400 records 500 records 1,000 records 2,000 records 174 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Table 58: View Measurement History Dialog Box Description (continued) Option Description Time Selection Do not limit time Records before this time Records after this time Records between this time Records for the last Displays the most recent record first Displays records recorded before the date and time you specify in the text box Displays records recorded after the date and time you specify in the text box Displays records recorded between the two dates and times you specify in the text boxes Displays records recorded within the time frame you specify in the lists (1-60 seconds, minutes, hours, or days) 4 To display the View Measurement History window, click Ok. The View Measurement History Window The View Measurement History window contains the measurement history of each chassis you selected with the Event Mgmt > View Measurement History command. The arrow indicates which column the information is sorted by, and whether the information is sorted in ascending (up arrow) or descending (down arrow) order. The columns are described in Table 56. Component Names Changing the Component Name in the Tree View Figure 54: View Measurement History Window Teradata AWS User Guide, Release 4.5 175

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Table 59: View Measurement History Window Description Label Records for Previous/Next buttons Description Contains the path, default alias, or component ID of the chassis, depending on the option set for the Tree View: If the Default option is set, the path follows the hierarchy displayed in the Tree View. If the Alias option is set, the default alias displays. If a user-defined alias exists, it displays instead of the default alias. If the Component ID option is set, the CIM path displays. If one chassis is selected, this field is not displayed. If the number of records retrieved (based on the Time Selection option) exceeds the Number of records to display, the Next and Previous buttons allow you to display more records. Chassis Type Time Stamp Location Property Name Unit Property Value Managed Element ID Contains the path, default alias, or component ID of the chassis, depending on the option set for the Tree View. Type of chassis: node, CMIC, UPS, or Fibre Channel switch Date and time the measurement was performed Location of the component performing the measurement Chassis component whose measurement information is displayed Units the measurement is recorded in Measurement CIM path of the component whose measurement information is displayed; this is the unique name assigned to the component. The View Measurement History Menus The following table describes the commands available from each menu in the View Measurement History menu bar. Table 60: View Measurement History Commands Contains commands for saving measurement history and closing the View Measurement History window. Allows you to search for text strings. See: To Save Displayed Measurement Information to a File on page 173 To Close the Measurement Information View Window on page 173 See: To Search for Chassis Measurement History on page 178. 176 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Tracking Chassis Measurement Information Table 60: View Measurement History Commands (continued) Allows you to update the information in the View Measurement History window. Allows you to find a component in the Tree View. Displays help for the View Measurement History window. See To Update the View Measurement History Window on page 178. See: To Locate a Component in the Tree View on page 178. See: Using Teradata AWS Online Help on page 43. Working with the View Measurement History Window Note: For a description of the View Measurement History window, see Table 56 on page 172. To Sort Measurement History by Column Click the appropriate column header. To toggle between ascending and descending order, click the column header. To Display or Hide a Column The View Measurement History window contains all the columns described in Table 56 on page 172. To display or hide one or more columns: 1 Right-click any column header. The displayed pop-up menu contains the names of all the available columns. Check-marks beside column names indicate which columns are currently displayed. 2 On the pop-up menu, select a column header to display it, or clear a column header to hide it. To Save Displayed Measurement History to a File 1 From the View Measurement History window, do one of the following: a To save the information in plain text format (.txt) that can be viewed with Notepad or a similar text editor, select File > Text. b To save the information in comma separated value format (.csv) that can be viewed with Microsoft Excel or a similar spreadsheet application, select File > CSV. 2 When the Save dialog box displays, enter a file name and location, then click Save. Teradata AWS User Guide, Release 4.5 177

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs To Search for Chassis Measurement History 1 Select the Search > Find command. 2 Use the Find dialog box to search for text strings. To Update the View Measurement History Window When the window displays, the table does not automatically update if measurement information changes. To update the window, select the View > Refresh command. To Locate a Component in the Tree View 1 In the View Measurement History window, select a measurement in the table. 2 Select the Functions > Locate Component command. The component for which the measurement was performed is highlighted in the Tree View. To Close the View Measurement History Window From the View Measurement History window, click File > Close. Generating Measurement Graphs The Event Mgmt > View Measurement Graph commands allow you to display, in graph form, environmental, power, and operational information for components. The graphs are based on information gathered from hardware sensors and recorded and stored in the CMIC Measurement Database. Note: The View Measurement Graph commands are not available for components in Collective 0. Customer Service Representatives can use the following commands to generate graphs and save them in HTML format for later reference: The View Measurement Graph > Predefined Queries > System Queries command allows you to use predefined queries to generate the following: Temperature graphs for all nodes and CMICs Power consumption and output graphs for all UPSs The View Measurement Graph > Predefined Queries > Cabinet-Level Queries command allows you to use a predefined query to generate temperature graphs for nodes and CMICs in one or more selected cabinets. The View Measurement Graph > Custom Queries command allows you to use a dialog box to construct a custom query for selected nodes, CMICs, UPSs, BYA32S chassis, or Fibre 178 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs Channel switches and generate a graph based on your choice of hardware sensor(s). You can save, edit, or delete a custom query. Using Predefined System Queries to Generate Measurement Graphs Using Predefined Cabinet-Level Queries to Generate Measurement Graphs Using Custom Queries to Generate Graphs Saving Queries and Graphs Using Predefined System Queries to Generate Measurement Graphs The Event Mgmt > View Measurement Graph > Predefined Queries > System Queries command displays a Measurement Graph Manager dialog box (Figure 55). Figure 55: Measurement Graph Manager (Predefined System Queries) The dialog box contains a list of predefined queries that retrieve information from the CMIC Measurement Database and generate graphs for components in the system. To Generate an xy Graph Showing All Temperature Readings for All Nodes and CMICs. To Generate a Bar Graph Showing the Most Recent Temperature Readings for All Nodes and CMICs. To Generate an xy Graph Showing All UPS Power Consumption for All Cabinets. To Generate a Stacked Bar Graph Showing the Most Recent UPS Power Consumption for All Cabinets. To Generate an xy Graph Showing UPS Power Output for All Cabinets Teradata AWS User Guide, Release 4.5 179

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs To Generate an xy Graph Showing All Temperature Readings for All Nodes and CMICs 1 Select Event Mgmt > View Measurement Graph > Predefined Queries > System Queries. 2 From the Measurement Graph Manager, select Front Panel Temperature: All Readings. 3 Click Create Graph. The query retrieves all front panel and ambient temperature data for all nodes and CMICs in the system. The query generates an xy graph that plots the temperature change, in Celsius, as measured over time. An example of a graph is shown in Figure 56. Figure 56: xy Graph of All Temperature Readings (Example) 180 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs To Generate a Bar Graph Showing the Most Recent Temperature Readings for All Nodes and CMICs 1 Select Event Mgmt > View Measurement Graph > Predefined Queries > System Queries. 2 From the Measurement Graph Manager, select Front Panel Temperature: Recent. 3 Click Create Graph. The query retrieves the most recent front panel or ambient temperature data of each node and CMIC in the system. The query generates a bar graph that shows the temperature reading of each sensor, in Celsius, for each component. Figure 57: Bar Graph of Most Recent Temperature Readings (Example) Teradata AWS User Guide, Release 4.5 181

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs To Generate an xy Graph Showing All UPS Power Consumption for All Cabinets 1 Select Event Mgmt > View Measurement Graph > Predefined Queries > System Queries. 2 From the Measurement Graph Manager, select UPS Input Watts: Grouped by Cabinet. 3 Click Create Graph. The query retrieves data for all UPSs in the system, grouped by cabinet, and uses the data in the following formula to calculate UPS power consumption: average input watts = average input current (A RMS) multiplied by average input voltage (V RMS) Note: RMS is Root Mean Square, the method used to average the volts. The resulting xy graph plots the power consumption (UPS Input Watts RMS) for the UPSs in each cabinet, as measured over time. Figure 58: xy Graph of All UPS Power Consumption Data (Example) To Generate a Stacked Bar Graph Showing the Most Recent UPS Power Consumption for All Cabinets 1 Select Event Mgmt > View Measurement Graph > Predefined Queries > System Queries. 2 From the Measurement Graph Manager, select UPS Input Watts: Recent. 182 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs 3 Click Create Graph. The query retrieves the most recent data for all UPSs in the system, grouped by cabinet, and uses the data in the following formula to calculate UPS power consumption: average input watts = average input current (A RMS) multiplied by average input voltage (V RMS) Note: RMS is Root Mean Square, the method used to average the volts. The resulting stacked bar graph plots the power consumption (UPS Input Watts RMS) for the UPSs in each cabinet, as measured over time. An example of a stacked bar graph is shown in Figure 59: Each bar represents one cabinet. The height of the bar represents the sum of the average input watts of all the UPSs in the cabinet. Each band of color in the bar represents one UPS in the cabinet. To find the average input watts of each individual UPS, take the value from the top of the band and subtract the value of the bottom of the band. For example (Figure 59): In cabinet 70, the blue band represents UPS 2. (~625 watts to 1500 watts). So, for this measurement, UPS 2 in cabinet 1 in collective 70 received 875 input watts (1500-625 = 875). Figure 59: Stacked Bar Graph of Most Recent UPS Power Consumption Data (Example) Teradata AWS User Guide, Release 4.5 183

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs To Generate an xy Graph Showing UPS Power Output for All Cabinets 1 Select Event Mgmt > View Measurement Graph > Predefined Queries > System Queries. 2 From the Measurement Graph Manager, select UPS Output Watts: Grouped by Cabinet. 3 Click Create Graph. The query adds the output watts of each UPS in a cabinet and displays an xy graph of the output power of each cabinet, in watts, as measured over time. An example of an xy graph is shown in Figure 60: Figure 60: xy Graph of All UPS Power Output Data (Example) 184 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs Using Predefined Cabinet-Level Queries to Generate Measurement Graphs When you select one or more cabinets that contain nodes and CMICs, the Event Mgmt > View Measurement Graph > Predefined Queries > Cabinet-Level Queries command displays a Measurement Graph Manager dialog box (Figure 61). Figure 61: Measurement Graph Manager (Predefined Cabinet-Level Queries) The dialog box contains a predefined query that retrieves information from the CMIC Measurement Database and generates a temperature graph for the nodes and CMICs in one or more selected cabinets. To Generate an xy Graph Showing All Temperature Readings for Nodes and CMICs in Selected Cabinets To Save a System or Cabinet-Level Measurement Graph in HTML Format To Generate an xy Graph Showing All Temperature Readings for Nodes and CMICs in Selected Cabinets 1 From the Tree View, select one or more processing node cabinets. 2 Select Event Mgmt > View Measurement Graph > Predefined Queries > Cabinet-Level Queries. 3 From the Measurement Graph Manager, select Front Panel Temperature: Selected Cabinet(s). Teradata AWS User Guide, Release 4.5 185

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs 4 Click Create Graph. The query retrieves all front panel and ambient temperature data for all nodes and CMICs in the selected cabinet(s). The query generates an xy graph that plots the temperature change, in Celsius, as measured over time. An example of a graph is shown in Figure 56. Figure 62: xy Graph of All Temperature Readings for Selected Cabinet(s) (Example) 186 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs Using Custom Queries to Generate Graphs When you select one or more components of the same or similar type (nodes or CMICs, UPSs, BYA32S chassis, or Fibre Channel switches), the Event Mgmt > View Measurement Graph >Custom Queries command displays a Measurement Graph Manager dialog box (Figure 63). The components must have at least one sensor in common. Figure 63: Measurement Graph Manager (Custom Queries) The dialog box contains a set of commands that allow you to create and work with custom queries. The custom queries retrieve information from the CMIC Measurement Database for the selected nodes, CMICs, UPSs, BYA32S chassis, or Fibre Channel switches and generate graphs based on the queries. You can also modify and delete the custom queries, and save the custom query and graph. Creating a New Custom Query The Measurement Graph Dialog Box (Custom Queries): General Tab Editing the SQL Statement Generated from a Custom Query The Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab Running an Existing Custom Query Editing an Existing Custom Query Renaming an Existing Custom Query Deleting an Existing Custom Query Saving Queries and Graphs Teradata AWS User Guide, Release 4.5 187

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs Creating a New Custom Query To Create a New Custom Query 1 In one or more processing node cabinets, select: One or more nodes One or more CMICs One or more nodes and CMICs One or more UPSs One or more BYA32S chassis One or more Fibre Channel switches Note: If you select components that do not have sensors in common, an error message displays. 2 Select Event Mgmt > View Measurement Graph > Custom Queries. 3 From the Measurement Graph Manager dialog box, click New. 4 From the Measurement Graph dialog box, choose the sensor, graph, and time criteria options you want to use. Note: You can select only one unit of measurement from the Sensors list (Amps, for example). However, you can expand the unit of measurement and select one or more individual sensors (node or CMIC Power Supply : PS1 +12V Current, for example). 5 To edit the resulting SQL query and generate a graph, see Editing the SQL Statement Generated from a Custom Query on page 191. 6 Click Create Graph. 7 Do one of the following: a b c d To save the custom query or graph, see To Save a Custom Query or Graph on page 197. To close the graph without saving the custom query or the graph, click Close. To continue creating new graphs for the same component or set of components, return to step 3 on page 188. To work with a different component or set of components, click Cancel and start with step 1 on page 188. The Measurement Graph Dialog Box (Custom Queries): General Tab The General tab allows you to create a custom query and generate a graph based on your choice of hardware sensors. When you select more than one component, the General tab contains only the units of measurement and hardware sensors that the selected components have in common. For example, two 5400 nodes have more sensors in common than one 5400 node and one 5550 node. 188 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs Although you can select only one unit of measurement from the list in the Sensors section, you can expand each unit of measurement and select one or more hardware sensors. The units of measurement and hardware sensors are described in the following table. Figure 64: Measurement Graph Dialog Box (Custom Queries): General Tab Table 61: Measurement Graph Dialog Box (Custom Queries): General Tab Description Item Description # Component(s) Selected (Components) Lists the default Alias or CIM path for the selected component(s). If a user-defined Alias exists, it is displayed instead of the default Alias. Sensors (listed alphabetically) Amps Amps RMS (Root Mean Square) Celsius Count Unit of measurement for the current of node or CMIC power supplies. Selecting Amps chooses all available power supply sensors. Expanding Amps displays allows you to select one or more power supply sensors from a list. Unit of measurement for UPS input current. Selecting Amps RMS chooses all available input current sensors. Expanding Amps RMS allows you to select one or more input current sensors from a list. Unit of measurement for node, CMIC, UPS, BYA32S port, or Fibre Channel Switch temperature. Selecting Celsius chooses all available temperature sensors. Expanding Celsius allows you to select one or more temperature sensors from a list. A count of operating system processes, operating system threads, and operating system handles running on a CMIC. Selecting Count chooses all operating system items. Expanding Count allows you to select one or more operating system items from a list. Teradata AWS User Guide, Release 4.5 189

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs Table 61: Measurement Graph Dialog Box (Custom Queries): General Tab Description (continued) Item MB Milliamps Milliwatts Description A count of the megabytes of memory used on a CMIC. Selecting MB chooses all measurements. Expanding MB allows you to select one or more types of memory measurements from a list. A measure of the current transmitted by a port on the BYA32S chassis A measure of the power used to transmit a message through a port on the BYA32S chassis Percent Nodes: Percent of thermal control on processors. Selecting Percent chooses all processors. Expanding Percent allows you to select one or more processors from a list. CMICs: Percent of space available on CMIC hard drives. Selecting Percent chooses all drives. Expanding Percent allows you to select one or more drives from a list. RPM Revolutions per minute of baseboard fans on nodes or CMICs. Selecting RPM chooses all available fans. Expanding RPM allows you to select one or more fans from a list. Volts Nodes or CMICs: Unit of measurement for a variety of system baseboard and processor power sensors on nodes or CMICs. Selecting Volts chooses all available power sensors. Expanding Volts allows you to select one or more power sensors from a list. UPSs: Unit of measurement for UPS battery voltage. To select the battery, select Volts, or expand Volts and select Battery: Battery Voltage. BYA32S chassis: Unit of measurement for the volts received by a port Volts RMS (Root Mean Square) Unit of measurement for UPS input or output voltage. Selecting Volts RMS chooses all available voltage sensors. Expanding Volts RMS allows you to select one or more voltage sensors from a list. Watts Nodes and CMICs: Unit of measurement for node or CMIC power supply gauges. Selecting Watts chooses both gauges. Expanding Watts allows you to select one or more gauges from a list. UPSs: UPS output watts. To select UPS output watts, select Watts, or expand Watts and select Output: Output Watts. Graph Options Graph Title Time Series Bar Graph The name you want to use for the graph; the title appears at the top of the generated graph Retrieves the data for the sensor(s) selected in Sensors and generates an xy graph that plots the change, as measured in the relevant unit of measurement, over the time specified in Time Options. Retrieves the data for the node, CMIC, or UPS sensor(s) selected in Sensors and generates a bar graph that shows the latest measurement(s) for each of the selected sensors within the time specified in Time Options. 190 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs Table 61: Measurement Graph Dialog Box (Custom Queries): General Tab Description (continued) Item Periodic Groups Description Retrieves the data for the sensor(s) selected in Sensors and uses the setting in Group values into intervals of to cluster the data into groups. The query calculates the average value of each group, then plots the average value, instead of all values that made up the group, over the time specified in Time Options. Overlay standard deviation lines: Selecting this option calculates the standard deviation of each group, then draws a vertical line through the point, where the bottom of the line indicates the average - the standard deviation and the top of the line indicates the average + the standard deviation. Group values into intervals of: Determines the size of the group: automatic: Calculates how many days of data are available in the CMIC Measurement Database. If it is less than 30 days, the query groups the data by 3-day intervals. If it is more than 30 days, but less than 60, the query groups the data in 1-week intervals. Between 60 and 120 days groups the data into 2-week intervals, and anything more than 120 days is grouped into monthly intervals. 3 days: Groups the data by 3-day intervals 1 week: Groups the data by 1-week intervals 2 weeks: Groups the data by 2-week intervals 1 month: Groups the data by monthly intervals Note: If the time specified in Time Options is less than the interval, the query clusters all the data into one point. Time Options Do not restrict time Before this time After this time Between these times Retrieves all measurements stored in the CMIC Measurement Database Retrieves measurements stored before the time specified in Start date Retrieves measurements stored after the time specified in Start date Retrieves measurements stored between the times specified in Start date and End date Within the last Retrieves measurements for one of the following intervals: Day, Week, Month, 2 Months, 3 Months, 6 Months Editing the SQL Statement Generated from a Custom Query Note: You cannot edit predefined system and cabinet-level queries. To Edit the SQL Statement Generated from a Custom Query The following procedure assumes you have created a custom query using step 1through step 4 on page 188. 1 On the Measurement Graph dialog box, click the SQL Statement tab. 2 Select Edit SQL. Teradata AWS User Guide, Release 4.5 191

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs 3 When the confirmation dialog box displays, click Yes. 4 Using the information in The Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab as a guideline, edit the SQL statement. 5 Click Create Graph. 6 Do one of the following: a To save the custom query or graph, see Saving Queries and Graphs on page 197. b c d e To close the graph without saving the custom query or the graph, click Close. To continue creating new graphs for the same component or set of components, return to step 3 on page 188. To work with a different component or set of components, click Cancel and start with step 1 on page 188. To work with previously saved custom queries displayed in the Measurement Graph Manager, see one of the following: Running an Existing Custom Query on page 193 Editing an Existing Custom Query on page 194 Renaming an Existing Custom Query on page 195 Deleting an Existing Custom Query on page 196 The Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab The SQL Statement tab allows you to edit the SQL statement generated from the options selected on the General tab. When you edit the SQL statement, the Sensors and Time Options on the General tab are unavailable. To edit SQL statements, you must be familiar with SQL syntax and the components and units of measurement stored in the CMIC Measurement database. Use the following information to edit the SQL statement: Do not edit or remove the following line (it shows the program where to find the database): FROM [$IPS$\x3gsma].[3gsmm].dbo.Measurements1 The custom query can only retrieve data from selected cabinets. To edit the statement so that the SQL retrieves data for all components in all cabinets, you must select at least one node, CMIC, BYA32S, or UPS in each cabinet before you select the Event Mgmt > View Measurement Graph > Custom Queries command. After you click Create Graph, the program automatically adds an ORDER BY clause to the SQL statement. This ensures that the program can create a graph from the query. If you add an ORDER BY clause before you click Create Graph, there are two ORDER BY clauses, which will return an error. 192 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs The program uses the selected nodes, CMICs, BYA32S chassis, and or UPSs to determine where the CMIC Measurement database resides. When the database resides in more than one location (across multiple IP addresses), the program automatically changes the query to: query to ip address1 UNION ALL query to ip address 2 UNION ALL query to ip address 3 In these cases, when the program adds UNION ALL, a valid SQL statement may return an error. Figure 65: Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab Table 62: Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab Description Item Edit SQL Description When selected, this checkbox allows you to edit the SQL statement on the tab. Running an Existing Custom Query To Run an Existing Custom Query 1 Select the node(s), CMIC(s), BYA32S chassis, or UPS(s) that you want to run an existing custom query on. Note: You can run an existing custom query on components that are of the same type as the component(s) used to create the query. For example, you can use CMIC 70 to create a query, then run the same query on CMIC 500. However, you cannot run queries on components in Collective 0. 2 Select Event Mgmt > View Measurement Graph > Custom Queries. Teradata AWS User Guide, Release 4.5 193

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs 3 From the Measurement Graph Manager, select the query you want to run. 4 Click Create Graph. 5 Do one of the following: a To save the graph, see Saving Queries and Graphs on page 197. b c To close the graph without saving it, click Close. To work with other previously saved custom queries displayed in the Measurement Graph Manager, see one of the following: Editing an Existing Custom Query on page 194 Renaming an Existing Custom Query on page 195 Deleting an Existing Custom Query on page 196 Editing an Existing Custom Query You can edit previously created custom queries. You cannot edit predefined queries. To Edit an Existing Custom Query 1 Select any node, CMIC, BYA32S, or UPS that is not in Collective 0. Note: You can edit the options used to create an existing custom query, but you cannot change the component(s) originally used to create the query. 2 Select Event Mgmt > View Measurement Graph > Custom Queries. 194 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs 3 From the Measurement Graph Manager, select the query you want to edit. 4 Click Edit. 5 When the Measurement Graph dialog box displays, use the information in The Measurement Graph Dialog Box (Custom Queries): General Tab on page 188 or The Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab on page 192 to edit the query. 6 Click Create Graph. 7 Do one of the following: a To save the custom query or graph, see Saving Queries and Graphs on page 197. b c To close the graph without saving the custom query or the graph, click Close. To work with other previously saved custom queries displayed in the Measurement Graph Manager, see one of the following: Running an Existing Custom Query on page 193 Renaming an Existing Custom Query on page 195 Deleting an Existing Custom Query on page 196 Renaming an Existing Custom Query To Rename an Existing Custom Query 1 Select any node, CMIC, BYA32S, or UPS that is not in Collective 0. 2 Select Event Mgmt > View Measurement Graph > Custom Queries. Teradata AWS User Guide, Release 4.5 195

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs 3 From the Measurement Graph Manager, select the query you want to rename. 4 When the Rename Query dialog box displays, type the new name in the Enter new name for query field. 5 Click Save. The renamed query appears on the Measurement Graph Manager dialog box. Deleting an Existing Custom Query To Delete an Existing Custom Query 1 Select any node, CMIC, BYA32S, or UPS that is not in Collective 0. 2 Select Event Mgmt > View Measurement Graph > Custom Queries. 3 From the Measurement Graph Manager, select the query you want to delete. 4 Click Delete. 196 Teradata AWS User Guide, Release 4.5

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs Saving Queries and Graphs To Save a System or Cabinet-Level Measurement Graph in HTML Format 1 After you create a graph, on the Graph window, click Save. 2 When the Save Graph Window dialog box displays, type the file name in the File Name field. Note: Do not use a file extension. 3 Click Save. The file is saved, in HTML format, to the location indicated on the dialog box. To Save a Custom Query or Graph 1 Create the graph. 2 On the Graph window, click Save. 3 When the Save Graph Window dialog box displays, the graph title is automatically entered in the File Name and Save query as fields. To change the file name or query name, do one of the following: Note: Do not use a file extension. To save only the graph, in the File Name field, type the file name. To save only the custom query, in the Save query as field, type a name for the query. To save both the graph and the custom query, type a file name in the File Name field, and a query name in the Save query as field. 4 Click Save. If there is a file name in the File Name field, the graph is saved, in HTML format, to the location indicated on the dialog box. If there is a name in the Save query as field, the query is saved and appears on the Measurement Graph Manager dialog box. Teradata AWS User Guide, Release 4.5 197

Chapter 8: Viewing and Updating Component Information Generating Measurement Graphs 198 Teradata AWS User Guide, Release 4.5

CHAPTER 9 Connecting to System Components The AWS provides interfaces and connection options that allow you to make LAN, console, and browser-based connections to the AWS and to system components. Connecting to a CMIC Web Page The Functions > Manage CMIC command allows you to connect to a CMIC s web page. The web page opens in the default Internet browser and provides a primary server management network connection to the CMIC. Field and development personnel use this diagnostic interface to perform CMIC, server management, and cabinet administration functions. You can also use this command to access a legacy SMC s (CMIC s) BCL menu. Note: When you use the Remote AWS feature, the Manage CMIC command is unavailable. To Access a CMIC Web Page 1 In the Tree View, select the CMIC whose web page you want to access. Note: If the CMIC resides in a legacy server management chassis (SMC), the Functions > Manage CMIC command is available only for 10-slot and 11-slot SMCs (those with CMIC3s) in 4851/5251 through 4980/5380 platforms. 2 From the AWS main window, select Functions > Manage CMIC. For SM3G CMICs, the following web page displays. For more information, see the Hardware Service Guide delivered with your system. Teradata AWS User Guide, Release 4.5 199

Chapter 9: Connecting to System Components Connecting to a CMIC Web Page Figure 66: CMIC Web Page For legacy CMIC3s, the following web page displays: Figure 67: CMIC Service Web Page 200 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Connecting to Components from the Tree View Connecting to Components from the Tree View From the Teradata AWS application, you can select components in the Tree View and use the Functions > Connect command to connect to the components. When the New Connection dialog box displays, you can use the tabs to set connection options. Note: If the New Connection dialog box does not display, use the Client Connection Window s Window > Options command and select the option Prompt for connection options. Client Connections Window Display Options To Set Display Options for the Client Connections Window To Connect to a CMIC or a Legacy SMC 1 In the Tree View, select the CMIC or legacy SMC you want to connect to. 2 From the AWS main window, select Functions > Connect. 3 If you selected a CMIC, the Connect dialog box displays. Select the connection type you want to use: Console: Displays the New Connection dialog box, which allows you to make a Telnet connection to a CMIC s console; this option is used mainly to display a CMIC s messages during the BIOS booting process or to access the CMIC s BIOS setup. Telnet: Displays the New Connection dialog box, which allows you to make a Telnet connection. Port 23 is always used for Telnet connections. 4 If you selected a legacy SMC, the New Connection dialog box displays. Note: After you connect to a legacy SMC, you can access its BCL menu. Teradata AWS User Guide, Release 4.5 201

Chapter 9: Connecting to System Components Connecting to Components from the Tree View To Connect to a Node Only the types of connections compatible with the selected node are available. For example, if the node is running the UNIX MP-RAS or Linux operating system, the Terminal Services connection is unavailable. Note: If the Telnet server is not enabled on the selected UNIX MP-RAS or Windows node, you cannot make a Telnet connection to the node. 1 In the Tree View, select the node you want to connect to. 2 From the AWS main window, select Functions > Connect. 3 When the Connect dialog box displays, select the connection type you want to use. Console: Displays the New Connection dialog box, which allows you to make a Telnet connection to a UNIX MP-RAS or Windows node s console over the primary server management network; this option is used mainly to display a node s messages during the BIOS booting process or to access the node s BIOS setup. 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 node. Port 22 is always used for SSH connections. Telnet: Displays the New Connection dialog box, which allows you to make a Telnet connection to a UNIX MP-RAS or Windows node. This option is available if the node 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 Windows nodes over the secondary server management network. This option is available if a path to a Terminal Services Client is specified using the AWS s Tools > Options dialog box. 202 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Connecting to Components from the Tree View To Connect to BYNET Utilities or a BYNET Switch Console Note: When you use the Remote AWS feature, the BYNET utilities are unavailable. Note: The Tools > BYNET Utility and Tools > BYNET DSSP commands are the preferred methods for connecting to the BYNET utilities. For more information about BYNET utilities, see the Service Guide appropriate for your system. 1 In the Tree View, select the BYNET switch you want to connect to. 2 From the AWS main window, select Functions > Connect. 3 A dialog box similar to the following displays after you select the Connect: command. Console: Displays the New Connection dialog box, which allows you to make a Telnet connection to a BYNET chassis console through the CMIC. LAN: This option connects you to the BYNET DSSP Main utility over the primary or secondary server management network, depending on your configuration. Utility: This option connects you to the BYNET Utility. To Connect to a UPS, Disk Array Controller, Ethernet Switch, or Fibre Channel Switch 1 In the Tree View, select the UPS (SM3G only), disk array controller, Ethernet switch, or Fibre Channel switch you want to connect to. 2 From the Teradata AWS main window, select Functions > Connect. Teradata AWS User Guide, Release 4.5 203

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Connecting to Components from the Client Connections Window The Client Connections Window provides the following connections to system components. Secure Shell (SSH) and SFTP for secure connections and file transfers between UNIX MP- RAS, Linux, and Windows nodes; to connect to a node, an SSH server must be installed and configured on the node. SFTP replaces FTP on UNIX MP-RAS and Windows nodes. Telnet for connecting to the consoles of UNIX MP-RAS and Windows nodes, and CMICs, disk array controllers, and Fibre Channel switches; to connect to a UNIX MP-RAS or Windows node, a Telnet server must be enabled on the node. Figure 68: Client Connections Window To Connect to One or More Components with the Client Connections Window Setting Options for Connecting to Components To Connect to One or More Components with the Client Connections Window 1 From the AWS, do one of the following: a Select Start > Programs > Teradata AWS > Client Connections Window. b Select Tools > Client Connections Window. 2 From the Client Connection Window, select Connection > New. 3 When the New Connection dialog box displays, set the connection options. 4 Click Ok. 5 To make additional connections, one at a time, from the Client Connections Window, use the Connection > New command. 204 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Setting Options for Connecting to Components The tabs on the New Connection dialog box allow you to set options for connecting to components. The dialog box displays when you select the following commands: Teradata AWS Functions > Connect Note: If the New Connection dialog box does not display, use the Client Connection Window s Window > Options command and select the option Prompt for connection options. Client Connections Window Connect > New The New Entry command on the New Address Book Entry dialog box (Client Connections Window Tools > Manage Address Book command) The New Connection dialog box contains tabs for setting connection options. Client Connections Window Display Options Connecting to Components from the Tree View Hiding and Displaying Terminal Windows Generating SSH Keys for Use with the SSH Protocol The Window Tab The Window tab on the New Connection dialog box allows you to specify display options for the Client Connections Window. The Window tab appears only when you use the Teradata AWS Functions > Connect command. The default port number is used for the connection. Figure 69: New Connection Dialog Box: Window Tab Teradata AWS User Guide, Release 4.5 205

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Table 63: New Connection Dialog Box: Window Tab Description Option Display Connections Manager Hide terminals until requested Open connection(s) in separate Client Connections Window Window Options Description When selected, this option displays the Connections Manager in the Client Connections Window. This option opens the Client Connections Window with all terminal windows hidden. When making multiple connections, this option displays each connection in a separate Client Connections Window. The settings in the Window tab are used for all the windows. When you select this button, the Client Connections Window s Options dialog box displays. The options you set are used for the connection. For a description of the options, see Table 72 on page 226. The Connect Tab The Connect tab on the New Connection and New Address Book Entry dialog boxes allows you to specify generic connection options, such as information about the remote host you want to connect to. For example, you can provide the port number and domain name or IP address of the component to which you want to connect. The port number and other connection information are retained for future connections. Note: When you use the Teradata AWS Functions > Connect command, the Window tab replaces the Connect tab, and the default port number is used. Figure 70: New Connection Dialog Box: Connect Tab 206 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Table 64: New Connection Dialog Box: Connect Tab Description Option Host Protocol Port Name Capture data or text to file Mode File Browse Description The domain name or the IP Address of the host to connect to. This field is required. If no host is specified, an error message displays. The protocol used to establish the connection. The available options are: SSH (Secure Shell), SFTP (Secure File Transfer Protocol), and Telnet. The port to connect to on the remote host. This field is required. The default for Telnet is 23. The default for SSH and SFTP is 22. If no port is specified, an error message displays. If the value of this field is greater than 65,535, an error message displays. The name (alias) of the component or the path to the component; the path follows the hierarchy displayed in the Tree View. If no name is specified, then the host and port number (<host name> (<port number>)) are used. This value is used as the title of the terminal frame or tab in the Client Connections Window, and to refer to the connection in the Connection Manager. When checked, this option allows you to capture data or text sent from the server and save it to a file. When Capture data or text to file is selected, the options allow you to specify one of the following capture modes: Data mode saves the data interpreted by the terminal, and the text, to a file. Text mode saves only the text to a file. When Capture data or text to file is selected, this field contains the path and file name for the file where you want to save the text or data. The default is capture.txt, located in the user s home directory (\Documents and Settings\<username>\capture.txt). If the file already exists or the path is invalid, an error message displays. To change the path and file name, use the Browse button. When Capture data or text to file is selected, this button displays the Open dialog box, which allows you to specify the name and path of the file where you want to save text or data. Teradata AWS User Guide, Release 4.5 207

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window The Terminal Tab The Terminal tab on the New Connection and New Address Book Entry dialog boxes allows you to specify options related to the terminal type and display. Figure 71: New Connection Dialog Box: Terminal Tab Table 65: New Connection Dialog Box: Terminal Tab Description Options Terminal Type Restore Defaults Button Encoding Description The type of terminal to emulate; the following options are available when using the Teradata AWS Functions > Connect command or the Client Connections Window Connection > New command: ansi-bbs, pc-ansi, vt100, vt100+, vt-utf8. In addition, a Preferred option is available for the Teradata AWS Functions > Connect command. This option allows the Connect command to obtain the selected component s default terminal type from a CMIC and use the default to connect to the selected component. Returns the values on the Terminal tab to their default settings. The type of encoding used to display data in the terminal. The default is ASCII. 208 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Table 65: New Connection Dialog Box: Terminal Tab Description (continued) Options Description Display Rows: The number of rows to display in the terminal. The number of Rows in Display cannot be greater than the number of Rows in Buffer. Columns: The number of columns to display in the terminal. The number of Columns in Display cannot be greater than the number of Columns in Buffer. Foreground Color: The font color to use in the terminal. Background Color: The background color to use in the terminal. Adjust the number of rows and columns to fit the display area: Allows the number of rows and columns to change dynamically as the width and the height of the terminal window changes. Font Allows you to edit the font, font style, and font size used in the terminal. Name: Displays the name of the current font and, in parentheses, the font style. Size: Displays the size of the current font..button: Displays the Select Font dialog box. To change the current font, style, and size of the text displayed in a terminal, select the options you want to use, then click Ok. Note: If a font is not displayed correctly in the Select Font dialog box, select a font that does display correctly. Buffer Displays options for changing the size of the buffer. Rows: Sets the number of rows in the buffer. The number of Rows in Buffer cannot be less than the number of Rows in Display. Columns: Sets the number of columns contained within the buffer. The number of Columns in Buffer cannot be less than the number of Columns in Display. Teradata AWS User Guide, Release 4.5 209

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Table 65: New Connection Dialog Box: Terminal Tab Description (continued) Options Options Description The following terminal display options are also available: Cursor Size: Changes the size of the cursor in the terminal. Small: Causes the cursor to fill part of the lower half of a character cell. Medium: Causes the cursor to fill the lower half of a character cell. Large: Causes the cursor to fill a character cell. Tab Size: Changes the number of character cells that a tab character spans. The default value is 4 character cells. Line Wrap: Causes text to line wrap if the number of columns a line of text spans is greater than the number of columns in the buffer. Scroll Screen: Causes the terminal to scroll to the active cursor position when either the server or the user enters text into the terminal. The Telnet Tab The Telnet tab on the New Connection and New Address Book Entry dialog boxes allows you to specify Telnet options. If you are connecting to an SMP node, the node s Telnet server must be enabled before you can make a Telnet connection. Figure 72: New Connection Dialog Box: Telnet Tab Table 66: New Connection Dialog Box: Telnet Tab Description Option Local Echo Description When you enter text, this option causes the client, and not the server, to echo user input. 210 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Table 66: New Connection Dialog Box: Telnet Tab Description (continued) Option Send CR as telnet <CR> <NULL> Receive data in binary mode Send data in binary mode Escape Character Restore Defaults Description When the Enter key is pressed, this option causes the Carriage Return/ NULL (0) sequence to be sent to the server instead of the Carriage Return/ Line Feed sequence. Causes the server to send data in binary mode. Causes data to be sent to the server in binary mode. Specifies the character used to escape from the current interactive session. When you enter the escape character, a command prompt displays at the terminal. The command prompt allows you to send specific Telnet commands or enter commands that change options. For more information, type help at the command prompt. When you finish, you can use the escape character to return to the interactive session. Resets the values in the Telnet tab to their default values. The SSH/SFTP Tab The SSH/SFTP tab on the New Connection and New Address Book Entry dialog boxes allows you to specify options for SSH and SFTP connections. If you are connecting to a node, SSH server must be enabled on the node before you can make an SSH connection or use SFTP. The options you set on the SSH/SFTP tab depend on how the SSH server is configured on the nodes. There are four types of client authentication that can be configured on the SSH server on the nodes: Host-based authentication (by host) Public key authentication (by user) Password authentication (default) Keyboard interactive authentication (allows for any authentication method that only requires keyboard input) Note: For more information about configuring SSH Server host and private key authentication on UNIX MP-RAS, Linux, or Windows nodes, see the OpenSSH documentation available online at http://www.openssh.org. Man pages are available on UNIX MP-RAS nodes and Linux nodes, and an OpenSSH-Help.htm file is available on Windows nodes. Password authentication is used as the default until you use the Set Key dialog box to specify the necessary keys for using host-based and public key authentication. If a host key is specified, and the SSH server allows host-based authentication, then host-based authentication is attempted. If no host key is specified, or if host-based authentication fails, and a user key is specified, and the SSH server allows public key authentication, then public key authentication is attempted. Teradata AWS User Guide, Release 4.5 211

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Note: The Client Connections Window can be used to generate the host and user keys to be used with host-based and public key authentication. If no user key is specified, or if public key authentication fails, and the SSH server allows password authentication, then password authentication is attempted. If password authentication fails, and the SSH server allows keyboard interactive authentication, then keyboard interactive authentication is attempted. If keyboard interactive authentication fails, an Authentication Failed message displays and the connection is closed. When connecting to an SSH Server the following occurs during host-based authentication: 1 The hosts file is checked to see if the server is trusted. 2 If the server is not trusted a message states that the host is unknown. 3 The user is asked if they would like to trust the host. a b c If the user enters No the connection is closed. If the user enters Yes the connection proceeds as usual. If the user enters Always then the unknown host is added to the hosts file and the user is no longer prompted about trust on subsequent connections to the same server. Figure 73: New Connection Dialog Box: SSH/SFTP Tab Table 67: New Connection Dialog Box: SSH/SFTP Tab Description Option Client Authentication Description The Default Username is the user name used to log on to the AWS. 212 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Table 67: New Connection Dialog Box: SSH/SFTP Tab Description (continued) Option Set Keys Description Displays the Set Keys dialog box, which can be used to specify the host and user keys to be used with host-based and public key authentication. You can use the Client Connection Window s Tools > Generate Key command to generate host and user keys. Host Private Key File: Contains the location and name of the host private key file; to specify a host key for host-based authentication, click the Browse button and select the appropriate file. User Private Key File: Contains the location and name of the user private key file; to specify a user key for public key authentication, click the Browse button and select the appropriate file. User Key Passphrase: The password/string used to decrypt the user s private key. Host Key Verification Algorithms SFTP Restore Defaults Button The hosts file contains the Name or IP address and public key of SSH Servers that are trusted by the user. To specify the location of the Hosts File, select the Browse button and use the Open dialog box. The default is.ssh in the user s home directory (\Documents and Settings\<username>). The Message Authentication and Encryption options are for advanced users. For more information about these options, see the SSH server documentation. SFTP is a protocol that uses the SSH communication protocol to transfer files securely across a network. The Client Authentication, Host Key Verification, and Algorithms section apply to SFTP and SSH. The SFTP section only applies to SFTP. Select the Browse button and use the Open dialog box to set a local directory as the Local Home Directory. The default is the local working directory (\Documents and Settings\<username>). Note: For a list of SFTP commands create an SFTP session and type help at the prompt. The * and? wild cards can be used in all path-related command arguments. The * wildcard substitutes for more than one character. The? wildcard substitutes for one character. Resets the values in the SSH/SFTP tab to their default values. Teradata AWS User Guide, Release 4.5 213

Chapter 9: Connecting to System Components Connecting to Components from the Client Connections Window Table 67: New Connection Dialog Box: SSH/SFTP Tab Description (continued) Option SSH Escape Character Description Specifies the character used to escape from the current interactive session. When you enter the escape character, a command prompt displays at the terminal. The command prompt allows you to enter commands that you can use to change the terminal emulation type. For more information, type help at the command prompt. When you finish, you can use the escape character to return to the interactive session. Generating SSH Keys for Use with the SSH Protocol The Client Connection Window Tools > Generate Keys command allows you to generate keys for use with the SSH protocol s host-based and public key authentication. After the keys are generated, you must place the public key file on the nodes. The location of the private key file is specified using the Set Key dialog box on the SSH/SFTP tab. Figure 74: Key Generator Dialog Box Table 68: Key Generator Dialog Box Description Option Key Location Browse Password Algorithm Verify Password Description The location where the public and private keys are stored. For example, if you enter c:\temp\key, the private key is stored in c:\temp\key and the public key is stored in c:\temp\key.pub. An error message displays if the file already exists or if the path is invalid. Displays the Open dialog box that allows you to browse the file system for the location where you want to store the key files. The password that should be used to protect the private key file. If no password is specified, a message allows you to confirm that you want the private key stored in clear text. Note: Host-based keys should not be password protected. Specifies whether you want to use the RSA or DSA key algorithm. Verifies that you entered the correct password in the Password field. If the content in this field does not match the content in the Password field, an error message displays. 214 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components The Client Connections Window Table 68: Key Generator Dialog Box Description (continued) Option Key Size Public Key Format Description The size of the key in bits. An error message displays if the key size is not in the range of 512 to 2048. The format of the public key. The available options are IETF (Internet Engineering Task Force) standard or OpenSSH format. The Client Connections Window The Client Connections Window provides an interface for connecting to components and managing component connections. All connections are displayed in the Client Connections Window. Client Connections Window Menu Bar Working with Terminal Windows Working with the Connections Manager Client Connections Window Display Options Connecting to Components from the Client Connections Window Working with the Connections Manager Teradata AWS User Guide, Release 4.5 215

Chapter 9: Connecting to System Components The Client Connections Window To Display the Client Connections Window From the AWS, do one of the following: a b c Select Start > Programs > Teradata AWS > Client Connections Window. Select Tools > Client Connections Window. Follow one of the procedures in Connecting to Components from the Tree View on page 201 To Hide or Display the Connections Manager Click Window > Connections Manager to toggle between hiding and displaying the Connections Manager. To Hide or Display the Status Bar When displayed, the Status bar is at the bottom of the Connections Manager window. The Status bar contains the name of the active connection, its terminal type, its status, and the number of active connections in the Client Connections Window. Click Window > Status Bar to toggle between hiding and displaying the Status bar. To Close the Client Connections Window When you close the Client Connections Window, all open connections are terminated. Click the Client Connections Window s Connection > Exit command. Client Connections Window Menu Bar The following table describes the commands available from each menu in the Client Connections Window menu bar. Table 69: Client Connections Window Commands When no connections exist in the Client Connections Window, the Connection menu contains only the New, Open, and Exit commands See: Connecting to Components from the Client Connections Window on page 204 To Open Connections from the Client Connections Window on page 227 To Close the Client Connections Window on page 216 216 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components The Client Connections Window Table 69: Client Connections Window Commands (continued) When connections exist in the Client Connections Window, the Connection menu contains commands for performing tasks. Contains commands for manipulating text in the active terminal window or the Connections Manager. See: Connecting to Components from the Client Connections Window on page 204 To Open Connections from the Client Connections Window on page 227 Closing an Existing Connection on page 221 To Save Open Connections from the Client Connections Window to the Address Book on page 232 Reconnecting to a Terminal Window on page 221 Viewing the Properties of Existing Connections on page 220 To Close the Client Connections Window on page 216 See: Working with Text in an Active Terminal Window or the Connections Manager on page 219. When connections exist in the Client Connections Window, contains commands for hiding and displaying terminal windows See: Hiding and Displaying Terminal Windows on page 218. Contains a command for generating keys to be used with the SSH protocol and for creating and managing connections. Manipulates the contents of the Client Connections Window See: Generating SSH Keys for Use with the SSH Protocol on page 214 Working with the Address Book on page 229 See: Working with the Connections Manager on page 222 Modifying the Display of Terminal Windows and Terminal Icons on page 219 Client Connections Window Display Options on page 224 Teradata AWS User Guide, Release 4.5 217

Chapter 9: Connecting to System Components The Client Connections Window Table 69: Client Connections Window Commands (continued) Displays Help for the Client Connections Window. See: Using Teradata AWS Online Help on page 43. Access to Teradata AWS Commands Working with Terminal Windows Opening Terminal Windows Hiding and Displaying Terminal Windows Modifying the Display of Terminal Windows and Terminal Icons Working with Text in an Active Terminal Window or the Connections Manager Viewing the Properties of Existing Connections Reconnecting to a Terminal Window Opening Terminal Windows The File > Open command in the Client Connections Window allows you to open connections whose addresses are stored in the Address Book. Hiding and Displaying Terminal Windows The following commands on the Client Connections Window View menu hide and display terminal windows. If there are no open terminal windows, the commands are unavailable. Command View > Hide <terminal> View > Hide Selected View > Hide All View > Display Selected View > Display All Description Hides the active terminal window. The name of the connection is in quotation marks. If you used the Tree View to connect to the component, the component name set with the Teradata AWS Tools > Options command displays in quotation marks. If you did not use the Tree View to connect to the component, <hostname> (<port number>) displays in quotation marks. Hides the terminal connections selected in the Connections Manage. This displays only if the Connections Manager is open. Hides all open terminal windows. Displays only if the Connections Manager is open. It displays the terminal connections selected in the Connections Manager. Displays all terminal windows. 218 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components The Client Connections Window Modifying the Display of Terminal Windows and Terminal Icons When you collapse a terminal window, you can use the following commands in the Client Connections Window s Window menu to modify how the window icon displays. If there is no active terminal in the Client Connections Window, or if the Tabbed layout is used, the commands in the Window menu are unavailable. Command Window > Arrange Icons Window > Cascade Window > Tile Description Arranges window icons in the lower portion of the Client Connections Window. Displays each terminal window below and to the right of the window behind it in the Client Connections Window; this command does not display terminal windows outside the boundary of the Client Connections Window. Tiles terminal frames within the Connection Desktop Pane. Working with Text in an Active Terminal Window or the Connections Manager You can use the following commands in the Edit menu to manipulate text in an active terminal or the Connections Manager. However, the Clear Terminal command is unavailable with the Connections Manager. If there is no active terminal displayed in the Client Connections Window, or the Connections Manager is not displayed, the commands on the Edit menu are unavailable. Command Edit > Clear Terminal Edit > Copy Edit > Paste Edit > Select All Edit > Deselect All Description Clears the buffer of the active terminal. If no terminal is selected, this command is unavailable. Copies the selected text from an active terminal or Connections Manager to the system clipboard. If no text is selected, this command is unavailable. Pastes text from the system clipboard into the active terminal or Connections Manager. (You can also click the right mouse button.) If no text is available for pasting, the command is unavailable. Selects all the text in the active terminal or the Connections Manager. Deselects all selected text in the active terminal or the Connections Manager. Teradata AWS User Guide, Release 4.5 219

Chapter 9: Connecting to System Components The Client Connections Window Viewing the Properties of Existing Connections The Client Connections Window s Connection > Properties commands display the properties of a selected terminal in the Client Connections Window or a selected connection in the Connections Manager. If there are no open terminal windows, the commands are unavailable. Command Connections > Properties <terminal> Connections > Properties for Selected Description Displays the properties of the connection whose name is specified in quotation marks. If you used the Tree View to connect to the component, the component name set with the Teradata AWS Tools > Options command displays in quotation marks. If you did not use the Tree View to connect to the component, <hostname> (<port number>) displays in quotation marks. Displays the properties of the connection selected in the Connections Manager. This command displays only if the Connections Manager is open and is active when only one connection is selected. The properties are displayed in a Properties dialog box, which contains a Connect tab, a Terminal Tab, and either a Telnet tab or SSH/SFTP tab (depending upon the type of connection). The options on the tab match those on the New Connection dialog box, but some options are unavailable because they cannot be changed. To Set AWS Options for the Client Connections Window To View the Properties of Existing Connections 1 Do one of the following: If Tabbed layout is used, select the connection tab. If Desktop layout is used, select the connection s terminal window or icon. If the Client Connections Manager displays, select the connection row. 2 In the Client Connections Window, select Connection > Properties <terminal>, or Connection > Properties for Selected. 220 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components The Client Connections Window Reconnecting to a Terminal Window If a connection in a terminal window is lost, you can use one of the following Client Connections Window Connection > Reconnect commands to re-establish the connection. If there are no open terminal windows, the commands are unavailable. Command Connections > Reconnect <terminal> Connections > Reconnect Selected Description Re-establishes the connection whose name is specified in quotation marks. If you used the Tree View to connect to the component, the component name set with the Teradata AWS Tools > Options command displays in quotation marks. If you did not use the Tree View to connect to the component, <hostname> (<port number>) displays in quotation marks. Displays only if the Connections Manager is open. It reestablishes the connections selected in the Connections Manager. Saving Open Connections to the Address Book Closing an Existing Connection To Set AWS Options for the Client Connections Window Saving Open Connections to the Address Book The File > Save commands in the Client Connections Window allows you to store one or more open connections in the Address Book. Closing an Existing Connection The Client Connections Window Connection > Close commands close open terminal windows. If there are no open terminal windows, the commands are unavailable. Note: The Connection > Close commands do not close the Client Connection Window. Command Connections > Close <terminal> Description Terminates the connection in the active terminal window and closes the terminal window. The name of the connection is in quotation marks. If you used the Tree View to connect to the component, the component name set with the Teradata AWS Tools > Options command displays in quotation marks. If you did not use the Tree View to connect to the component, <hostname> (<port number>) displays in quotation marks. Teradata AWS User Guide, Release 4.5 221

Chapter 9: Connecting to System Components The Client Connections Window Command Connections > Close Selected Connections > Close All Description Terminates the connections selected in the Connections Manager and closes its terminal window. This command displays only if the Connections Manager is open. Terminates all active connections and closes all open terminal windows. Working with the Connections Manager The Client Connections Window s Window > Connections Manager command displays and hides the Connections Manager. The Connections Manager: Lists each open connection and displays information about the connection in table format. Has an optional Send To toolbar that allows you to send commands to multiple hosts at the same time. When working with the Connections Manager, you can Move and resize the columns in a table Sort the columns Select one or more rows Use the commands in the Client Connections Window Edit menu Choose commands from pop-up menus Note: You can also choose commands from pop-up menus in terminal window title bars. The active terminal window and the Connections Manager are not dependent on one another. Figure 75: Client Connections Window: Tabbed Layout, Connections Manager, Send To Toolbar (Example) 222 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components The Client Connections Window Table 70: Connections Manager Description Column Send toolbar Description Allows you to send commands to multiple hosts at the same time: 1 If you want input to be sent only to selected terminals, in the Client Connections Manager, select the terminals. 2 Specify whether the command should be sent to All terminals or Selected terminals. 3 In the Mode list, select one of the following options: a b To send input one command at a time in the Send text box, select Command. To hide the input as you type it in the Send text box, and send the input one command at a time, select Password. c To send input as you type it in the Send text box, select Keyboard; the input displays in the open terminal windows, and all keyboard keys, such as function keys, can be used for input. 4 Type or copy and paste the text in the Send text box. 5 Click the Send button. Name Status Last Line IP Address Port Protocol Type Terminal Type Time Established Time Elapsed The component name or connection: If you used the Tree View to connect to the component, the component name set with the Teradata AWS Tools > Options command displays. If you did not use the Tree View to connect to the component, <hostname> (<port number>) displays. The connection status. The last line displayed in the terminal window. The IP address of the component you are connected to. The port number for the connection. The connection protocol (SSH, SFTP, or Telnet). The type of terminal emulation used for the connection (ansi-bbs, pc-ansi, vt100, vt100+, vt-utf8). The terminal type is specified on the Terminal tab of the New Connection dialog box. The date and time the connection was established. The time that has passed since Time Established. To Set Display Options for the Client Connections Window Working with Text in an Active Terminal Window or the Connections Manager Teradata AWS User Guide, Release 4.5 223

Chapter 9: Connecting to System Components The Client Connections Window Client Connections Window Display Options To Set AWS Options for the Client Connections Window Client Connections Window Display Options The following commands allow you to set display options for the Client Connections Window: The Tools > Options command displays the Options dialog box, which contains options for the following: Selecting the display name for the component names displayed in the Client Connections Window Displaying or hiding the New Connection dialog box when the following commands are selected: Functions > Connect, Tools > Client Connections Window, or Start > Programs > Teradata AWS > Client Connections Window Configuring the program the Functions > Connect command uses to make connections The Client Connection Window Window > Options command displays the Options dialog box, which allows you to set display options for the Client Connections Window: To Set AWS Options for the Client Connections Window To Set Display Options for the Client Connections Window To Type a User-Defined Alias for a Component Name To Connect to One or More Components with the Client Connections Window To Set AWS Options for the Client Connections Window 1 From the Teradata AWS menu bar, select the Tools > Options command. 2 In the Client Connections section of the Options dialog box, select the options you want to use. The options are described in Table 71. 3 Click Ok. Table 71: Teradata AWS Options Dialog Box (Tools > Options): Client Connections Window Options Option Description Connection Names Default: Displays the Default names of components in the Tree View; the path reflects the position the component occupies in the hierarchy. Alias: Displays the default Aliases of components in the Tree View. If a user-defined Alias exists, it displays instead of the default Alias. Component ID: Displays the Component IDs of components in the Tree View. Prompt for connection settings Specifies whether you want the Teradata AWS to display the New Connection dialog box. The default is checked. 224 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components The Client Connections Window Table 71: Teradata AWS Options Dialog Box (Tools > Options): Client Connections Window Options (continued) Option Terminal Services Client Location Description Before the Connect command can be used to make a remote Terminal Services Connection to an SMP node, you must specify the path to a local Terminal Services Client or a URL to a Terminal Services Client. To Set Display Options for the Client Connections Window 1 From the Client Connections Window menu bar, select the Window > Options command. 2 When the Options dialog box displays, use the information in Table 72 to set the display options you want to use. 3 Click Ok. Figure 76: Client Connections Window Options Dialog Box Teradata AWS User Guide, Release 4.5 225

Chapter 9: Connecting to System Components The Client Connections Window Table 72: Client Connections Window Display Options Option Layout Options Key Stroke Options Connections Manager Options Description Specifies the type of layout you want to use in the Client Connections Window. Connections Layout: Allows you to specify whether you want to use a Desktop, Extracted, or Tabbed layout for displaying connections. The Desktop option displays each connection in its own frame (window) on the Client Connections Window s desktop. The Extracted option displays each connection in its own frame outside of the Client Connections Window. Note: When you use this option, if the Connections Manager is not already displayed, it displays, and all frames (windows) are automatically hidden. To display the terminal windows, use the Client Connection Window View > Display Selected or View > Display All command. In addition, each extracted window contains Connection, Edit, and Help menus. The Tabbed option displays each connection on a separate tab in the Client Connections Window. Tile Layout: Allows you to specify whether you want to use a Vertical, Horizontal, or Grid layout when you use the Client Connections Window s Window >Tile command. Specifies the options you want to use for key stroke shortcuts. Enable Ctrl+C/Ctrl+V for Copy/Paste: This option allows you to use Ctrl+C for the copy command and Ctrl+V for the paste command. If this option is unchecked, Ctrl+C and Ctrl+V are sent to the server. Enable Ctrl+Tab for Terminal Traversal: This option allows you to use Ctrl+Tab to activate the next terminal in the stack. If this option is unchecked, Ctrl+Tab is sent to the server. Specifies display options you want to use for the Connections Manager. Display Send To toolbar: Displays the Send To toolbar at the top of the Connections Manager. For a description of how to use the toolbar, see Table 70 on page 223. Location: This option allows you to specify whether the Connections Manager is located at the Top, Bottom, Left, or Right in the Client Connections Window. Number of connections to display per line: Connections are usually displayed in one table. Use this option to split the table into two or more tables. All open connections are distributed among the number of tables you specify. (This option is useful in large systems.) Columns Displayed: This option allows you to specify which columns are displayed in the Connections Manager. The options are Name, Status, Last Line, IP Address, Port, Protocol, Terminal Type, Time Established, Time Elapsed. For a description of these columns, see Table 70 on page 223. 226 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Connecting to Components from the Address Book Connecting to Components from the Address Book Connections stored in the Address Book with the Tools > Manage Address Book command allow you use the following commands to connect to components: The Client Connection Window Connection > Open command The Open command on the Address Book dialog box (accessible with the Client Connection Window Tools > Manage Address Book command) When you add connection entries to the Address Book, the tabs for setting connection options are the same as the tabs on the New Connection dialog box. To Use the Address Book to Open One or More Connections To Open Connections from the Client Connections Window Working with the Address Book To Use the Address Book to Open One or More Connections 1 From the Client Connections Window, click Tools > Manage Address Book. 2 In the Address Book dialog box, on the Content tab, select one or more connection entries or group entries. 3 To hide the terminals when you open the connection, on the Options tab, select the Hide terminals when opening connections text box. 4 Select Open. The selected connections open in the Client Connections Window. 5 To close the Address Book dialog box, click Ok. To Open Connections from the Client Connections Window 1 From the Client Connections Window, select Connection > Open. 2 When the Open dialog box displays, do the following: a b Select one or more connection entries or group entries. Click Open. Teradata AWS User Guide, Release 4.5 227

Chapter 9: Connecting to System Components Connecting to Components from the Address Book The following table describes the options in the Open dialog box. Option or Icon Save in Description Identifies the Address Book as the location where the connections are stored; the file list shows all existing connections and groups in the Address Book: : Indicates an individual connection entry : Indicates a group If groups exist in the Address Book, the arrow allows you to navigate one level up in the Address Book; the Address Book is the highest level in the hierarchy Allows you to create a group; the selected connections are saved to that group in the Address Book. The path names are used for the individual connection entries. Lists the group and connection entries in the Address Book Lists the following details for the group and connection entries in the Address Book: Name, Size, Type, and Modified. File name Files of type Contains the connection entries or group entries you selected All files are of the type Saved Connections 228 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Working with the Address Book Working with the Address Book The Client Connections Window s Tools > Manage Address Book command and group of File > Save commands allow you to store connections to components as entries in an Address Book. You can open the connections stored in the Address Book with the File > Open command in the Client Connections Window, and the Open command provided through the Tools > Manage Address Book command. The Manage Address Book command also provides commands for editing, managing and organizing the entries in the Address Book. Connecting to Components from the Address Book Displaying the Address Book Adding Entries Organizing and Managing Entries Editing Entries Backing Up and Restoring the Address Book Displaying the Address Book To Display the Address Book From the Client Connections Window, click Tools > Manage Address Book. Note: When you finish making changes with the commands on the Address Book dialog box, you must click Ok on the Address Book dialog box to save the changes and close the Address Book. Teradata AWS User Guide, Release 4.5 229

Chapter 9: Connecting to System Components Working with the Address Book Figure 77: Address Book Dialog Box Adding Entries Organizing and Managing Entries Editing Entries Connecting to Components from the Address Book Backing Up and Restoring the Address Book Adding Entries To Add a Connection to the Address Book To Save Open Connections from the Client Connections Window to the Address Book Setting Options for Connecting to Components To Rename an Entry or Group Component Names To Add a Connection to the Address Book 1 From the Client Connections Window, click Tools > Manage Address Book. 2 In the Address Book dialog box, on the Content tab, select New Entry. The New Address Book Entry dialog box displays. 230 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Working with the Address Book 3 On the New Address Book Entry dialog box, on the Connect tab, specify the host you want to connect to in the Host field. 4 Use the name in the Name field on the Connect tab to store the connection in the Address Book. If the Name field is empty, type a name for the connection in the Name field, or provide a name after you save the connection to the Address Book. 5 Use the tabs on the New Address Book Entry dialog box to set the rest of the options you want. The tabs are the same as the tabs on the New Connection dialog box. 6 On the New Address Book Entry dialog box, click Ok. The Address Book dialog box displays and contains the connection entry. If a name for the connection was not provided, the entry is named New Connection. a b Click Rename. Type a name for the group. Teradata AWS User Guide, Release 4.5 231

Chapter 9: Connecting to System Components Working with the Address Book 7 To add additional connections, repeat step 2 through step 6. 8 To save the connection or connections to the Address Book, and close the Address Book dialog box, click Ok. To Save Open Connections from the Client Connections Window to the Address Book The connection name used for the entry is the component s path, alias, or component ID, depending on the option set for the Tree View. 1 From the Client Connections Window: To save the active connection, select File > Save <connection name>. To save more than one connection, but not all connections: i ii Display the Connections Manager (Window > Connections Manager). Select the connections from the list. iii Select File > Save Selected. To save all connections, select File > Save All. 2 When the Save dialog box displays, do one of the following: If you selected the Save <connection name> command, type a new name for the connection, or leave the default displayed, then click Save. In the Address Book, the new name, or the <connection name>, respectively, is used for the entry. If you selected the Save Selected or Save All commands, do one of the following: To store the selected connections in a group (the default), type the group name in the File name text box, then click Save. In the Address Book, the entries are stored under the group name. The <connection name> is used for the individual entries. To save the connections as individual entries in the Address Book, verify that / 232 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Working with the Address Book AddressBook is displayed in the File name text box, then click Save. In the Address Book, the <connection name> is used for the entries. Option or Icon Save in Description Identifies the Address Book as the location the connections are saved to; the file list shows all existing connections and groups in the Address Book: : Indicates an individual connection entry : Indicates a group If groups exist in the Address Book, the arrow allows you to navigate one level up in the Address Book; the Address Book is the highest level in the hierarchy Allows you to create a group; the selected connections are saved to that group in the Address Book. The path names are used for the individual connection entries. Lists the group and connection entries in the Address Book Lists the following details for the group and connection entries in the Address Book: Name, Size, Type, and Modified. File name Files of type If you selected the Save <connection name> command, this text box contains the path of the active terminal window. If you selected the Save Selected or Save All commands, this text box contains / Address Book by default. If you selected the Save <connection name> command, this text box contains the text Saved Connections. If you selected the Save Selected or Save All commands, this text box contains the text Connection Groups. Teradata AWS User Guide, Release 4.5 233

Chapter 9: Connecting to System Components Working with the Address Book Organizing and Managing Entries Organizing and managing entries in the Address Book is similar to organizing and managing folders in a Windows directory. Connection entries can be grouped into folders and subfolders, and a connection entry can be included in more than one folder. When you open a group with the File > Open command or the Open command in the Address Book dialog box, terminal windows for all connections in the group open in the Client Connections Window. To Create a Group in the Address Book To Copy or Move Existing Entries in the Address Book To Rename an Entry or Group To Remove an Entry or Group To Add a Connection to the Address Book To Create a Group in the Address Book The following procedure shows you how to use the Address Book dialog box to create groups. You can also create subfolders within a group. 1 From the Client Connections Window, click Tools > Manage Address Book. 2 In the Address Book dialog box, select the Address Book folder or an existing group. 234 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Working with the Address Book 3 Click New Group. A new folder with the name New Connection Group displays. 4 Click Rename. 5 Type a name for the group. 6 To create additional groups, repeat step 2 through step 5. 7 Add connections to groups. 8 To save the connection or connections to the Address Book, and close the Address Book dialog box, click Ok. To Copy or Move Existing Entries in the Address Book 1 In the Address Book dialog box, select one or more individual entries or group entries. 2 Do one of the following: To copy the entries to another location, in the Address Book dialog box, click Copy, select a group folder or the Address Book folder, then click Paste. To move the entries to another location, drag the entries to the group folder or the Address Book folder and drop them in. 3 To save the changes to the Address Book, and close the Address Book dialog box, click Ok. Teradata AWS User Guide, Release 4.5 235

Chapter 9: Connecting to System Components Working with the Address Book To Rename an Entry or Group 1 From the Client Connections Window, click Tools > Manage Address Book. 2 In the Address Book dialog box, on the Content tab, select the entry or group you want to rename. 3 Click Rename. 4 Type the new name for the entry or group. 5 To save the change to the Address Book, and close the Address Book dialog box, click Ok. Editing Entries To Remove an Entry or Group 1 From the Client Connections Window, click Tools > Manage Address Book. 2 In the Address Book dialog box, on the Content tab, select the entry or group you want to remove. 3 Click Remove. 4 To save the change to the Address Book, and close the Address Book dialog box, click Ok. To Edit the Connection Options of an Entry 1 From the Client Connections Window, click Tools > Manage Address Book. 2 In the Address Book dialog box, on the Content tab, select the connection whose options you want to edit. 3 Select Edit.The New Address Book Entry dialog box displays. 236 Teradata AWS User Guide, Release 4.5

Chapter 9: Connecting to System Components Working with the Address Book 4 Use the tabs on the New Address Book Entry dialog box to edit the rest of the options. The tabs are the same as the tabs on the New Connection dialog box. 5 On the New Address Book Entry dialog box, click Ok. The Address Book dialog box displays. 6 To edit additional connections, repeat step 2 through step 5. 7 To save the changes to the Address Book, and close the Address Book dialog box, click Ok. Setting Options for Connecting to Components Backing Up and Restoring the Address Book To Back Up the Address Book 1 From the Client Connections Window, click Tools > Manage Address Book. 2 In the Address Book dialog box, on the Content tab, do one of the following: To back up an individual entry, select the entry. To back up the entire Address Book, select Address Book. 3 Click Export. 4 When the Save dialog box displays, it is set to the MyDocuments directory. If you want to save the backup file to a different directory, select the directory from the Save in list. 5 In the File name field, type a name for the backup file. 6 Select Save. Teradata AWS User Guide, Release 4.5 237

Chapter 9: Connecting to System Components Working with the Address Book 7 To close the Address Book dialog box, click Ok. To Restore the Address Book 1 From the Client Connections Window, click Tools > Manage Address Book. 2 In the Address Book dialog box, on the Content tab, click Import. 3 When the Open dialog box displays, it is set to the MyDocuments directory. If the backup file is stored in a different directory, select the directory from the Save in list. 4 Select Open. 5 To close the Address Book dialog box, click Ok. 238 Teradata AWS User Guide, Release 4.5

CHAPTER 10 Servicing, Maintenance, and Troubleshooting This section describes servicing, maintenance, and troubleshooting procedures. Enabling the Locator LED of a Node or CMIC Chassis Replacing Hardware Components (FRUs) Updating (Flashing) Firmware Checking Firmware Versions Tracking and Setting Battery Installation and Replacement Dates Dumping Node Memory Resetting Components Managing System Power Performing Diagnostic Tests Accessing the BYNET Utility Accessing the BYNET Diagnostic Service Subsystem Program (DSSP) Enabling the Locator LED of a Node or CMIC Chassis The Functions > Enable Locator LED command illuminates the locator LED on a node or CMIC chassis in an SM3G system. The LED remains illuminated until you turn it off. To Enable the Locator LED of a Node or CMIC Chassis 1 In the Tree View, select a node or CMIC. 2 Select Functions > Enable Locator LED. The locator LED on the node or CMIC chassis is illuminated, and the Locator LED Enabled dialog box displays. Teradata AWS User Guide, Release 4.5 239

Chapter 10: Servicing, Maintenance, and Troubleshooting Replacing Hardware Components (FRUs) Note: To enable locator LEDs on additional nodes or CMICs, repeat step 1 and step 2 for each node and CMIC. 3 When you finish servicing or maintenance on the node or CMIC, click Disable to turn off its locator LED. Replacing Hardware Components (FRUs) Customers should not attempt to replace failed hardware components. The components within the MPP system must be replaced by Teradata Service personnel only. If a Teradata Service agreement is in place, notification or prediction of a failed component is made directly to Teradata Services through TVI software, and Teradata Services responds per the agreement. The following commands are used to replace components in an MPP system: The Functions > Replace FRU command Some Field-Replaceable Units (FRUs) can be replaced with this command, which uses an interactive script to step Teradata Customer Service Representatives through an often complex replacement process. Only one FRU Replace command for a chassis or its components can be active at one time. The Functions > Power Off and Functions > Power On commands Some FRUs that are not replaceable with the Functions > Replace FRU command are replaced by powering off the chassis with the Functions > Power Off command, replacing the component, and powering on the chassis with the Functions > Power On command. Some FRUs do not need to be powered off to replace them. For more information, see the service guide for the chassis. The appropriate hardware replacement procedures for FRUs can be found in the chassis hardware service guide. Components Replaced with the Replace FRU Command 240 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Replacing Hardware Components (FRUs) Replacing FRU Components Using the FRU Replace Procedure Window To Replace a Chassis To Replace a Chassis Component Components Replaced with the Replace FRU Command The Functions > Replace FRU command can be used with the following chassis and components. For detailed information about replacing hardware, see the chassis hardware service guide. Chassis CMIC (systems with SM3G only) SMC (systems with legacy server management only) Chassis or Component Replaced with the Replace FRU Command CMIC chassis System baseboard SMC CMIC (if present) Power supplies Management boards * Pass-through boards Pass-through board extenders BYNET BYA16G chassis (systems with legacy server management only) BYA32 and BYA32S chassis (systems with SM3G only) BYA32S power supply/fan module (systems with SM3G only) BYA32S SFP transceivers BYA64GX chassis BYB64G chassis (systems with legacy server management only) BYC64 chassis (systems with SM3G only) Diagnostic Processor (DPT) board BYCLK chassis (systems with SM3G only) Node/SMP Node chassis (systems with SM3G only) SMP chassis (systems with legacy server management) System baseboard (systems with SM3G only) Note: To replace a system baseboard, select the node the system baseboard is located in, then select the Replace FRU command. Power supplies Chassis voltage battery (49xx/53xx nodes only) 2U Powerware UPS UPS chassis Battery Dual Ethernet UPS interface card (systems with SM3G only) Teradata AWS User Guide, Release 4.5 241

Chapter 10: Servicing, Maintenance, and Troubleshooting Replacing Hardware Components (FRUs) Chassis Chassis or Component Replaced with the Replace FRU Command 3U Powerware UPS UPS chassis Battery UPS input selector chassis 2U APC UPS (systems with SM3G only) Battery Electronics (includes charger, fan, inverter, fuse, power switch) UPS adapter cards Fibre channel switch (16-port) Fibre channel switch Power supplies Fans Fibre channel switch (20-port) Fibre channel switch Power supply and fan assembly Ethernet switch (48-port) Ethernet switch (systems with SM3G only) Disk Array Disk array chassis Disk array controller Disk drives ESM boards Minihubs (if applicable) Fans Power supplies Note: * For 4950/5350 platforms, you must determine the SMP node s board type if you are replacing its management board. For more information, see the Service Subsystem Service Guide for your platform. Replacing FRU Components The Functions > Replace FRU command steps Customer Service personnel through the FRU replacement process. To Replace a Chassis To Replace a Chassis Component Using the FRU Replace Procedure Window Choose a Layout View Chassis Layout View To Replace a Chassis 1 In the Tree View, select the chassis to be replaced. 2 Select Functions > Replace FRU. 242 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Replacing Hardware Components (FRUs) 3 When the Replace FRU dialog box displays, select Entire chassis. 4 Click Ok. When the FRU Replace Procedure window displays, use it to replace the chassis. To Replace a Chassis Component Note: The Replace FRU series of windows is the same as the series of windows displayed when you use the View > Chassis Layout View command. 1 In the Tree View, select the chassis whose component is to be replaced. 2 Select Functions > Replace FRU. 3 When the Replace FRU dialog box displays, select Chassis component. 4 Click Ok. 5 If a FRU Replace Procedure window displays, use it to replace the component. 6 If you are replacing a disk array component, in the Key list, select the component you want to replace. When the Choose a Layout View window displays, go to step 8. 7 For all other components, the Choose a Layout View window displays. Go to step 8. 8 In the Choose a Layout View window, select the button corresponding to the view that contains the component you want to replace. 9 In the Chassis Layout View window, the components with numbered squares denote components that you can replace. Click the square associated with the component you want to replace. 10 When the FRU Replace Procedure window displays, use it to replace the component. Teradata AWS User Guide, Release 4.5 243

Chapter 10: Servicing, Maintenance, and Troubleshooting Replacing Hardware Components (FRUs) Using the FRU Replace Procedure Window The FRU Replace Procedure window guides a Customer Service Representative through the recommended procedure for replacing components in an MPP system. Each procedure is an ordered list of steps, descriptions, and actions that are performed manually by the operator or automatically by running a command step. Steps are then run (or skipped) contingent upon user confirmation. To Replace a FRU with the FRU Replace Procedure Window Replacing FRU Components To Replace a FRU with the FRU Replace Procedure Window Note: Table 73 on page 245 describes the items on the FRU Replace Procedure window. In Figure 78 on page 244, a FRU Replace Procedure window for a UPS chassis is shown as an example. 1 For the step highlighted in the left panel, do one of the following: Follow the process outlined in the Step Description on the right panel, and then click Ok. Click Skip, if appropriate. For more information, see the chassis hardware service guide for the component you are replacing. 2 Repeat step 1 for each step until the procedure is complete. Note: If you are replacing an SMP node s management board in 4950/5350 or 4980/5380 platforms, choose the firmware image you want to download to the replacement board. To determine which firmware to download, you must determine the node s board type. For more information, see the Service Subsystem Service Guide for your platform. Figure 78: FRU Replace Procedure Window 244 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Updating (Flashing) Firmware Table 73: FRU Replace Procedure Window Description Item Title Bar Session ID Steps panel Step Description panel Ok Skip Cancel Description Contains the path of the component you selected in the Tree View, and the Session ID number. Each replacement procedure has its own Session ID that prevents running simultaneous, conflicting FRU replace procedures. (For example, a conflict occurs if you try to replace two different components in the same chassis at the same time.) If you do attempt simultaneous FRU replace procedures, a warning message informs you that a conflicting FRU replace session is active. The warning message displays the Session ID of the active session. Clicking No in answer to the question Do you wish to override the active session? allows you to continue with the session that is already in progress. Clicking Yes in answer to the question Do you wish to override the active session? aborts the session that is in progress and displays a new FRU replace window. The original FRU replace window remains open until you either close that window, or issue a command from that window. Note: Aborting active FRU replace procedures is not recommended. However, if the AWS application is closed before an active session is complete, the AWS assumes that the session is still active. When you restart the AWS and attempt to initiate another session that is in conflict with the previously active session, you should click Yes to abort the previously active session. Lists all the steps that need to be completed to replace the selected component or chassis. Describes the highlighted step in the Steps panel and provides additional information you may need to run the step. To complete the step and proceed to the next step, click the Ok button. If a step is optional (such as updating the asset information), the Skip button is enabled, allowing you to bypass the step. The Cancel button allows you to prematurely end the procedure. However, it is your responsibility to ensure that the system is not left in a volatile state. Updating (Flashing) Firmware The Functions > Flash Firmware command downloads new firmware to the following components: CMICs (legacy server management only) Management boards (legacy server management only) UPS and UPS adapter cards (SM3G only) Fibre channel switches Ethernet switches (48-port, SM3G only) Teradata AWS User Guide, Release 4.5 245

Chapter 10: Servicing, Maintenance, and Troubleshooting Updating (Flashing) Firmware Use the Flash and Flash CoProcessor Firmware commands when notified by Customer Services personnel that a new version of firmware has been released. When a new version is available: On systems with SM3G, you must use the CMIC Monitor to install the currently supported CMIC image on the CMICs before you use the Functions > Flash command to update UPS, UPS adapter, Fibre Channel switch, or Ethernet switch firmware. For more information, see the appropriate Hardware Service Guide for your platform. On systems with legacy server management, you must install the currently supported SM3G Legacy SLAN firmware package on the AWS before you use the Functions > Flash command to update CMIC, management board, or Fibre Channel switch firmware. The firmware image is automatically downloaded from a controlled directory on the AWS. You can also use the features in the Tools > Firmware Version Checker command to flash firmware. Flashing CMIC Firmware Flashing Fibre Channel Switch Firmware Flashing Ethernet Switch Firmware in Systems with SM3G Flashing UPS and UPS Adapter Card Firmware in Systems with SM3G Flashing Management Board Firmware in Systems with Legacy Server Management Flashing 49xx/53xx Node Management Board Firmware in Mixed-Node Cabinets Checking Firmware Versions Firmware Images for Systems with Legacy Server Management Flashing CMIC Firmware In systems with SM3G, CMIC firmware is included with the CMIC image. For more information about installing a new CMIC image, see the appropriate Hardware Service Guide for your platform. In systems with legacy server management, use the following procedure to flash the CMIC. To Flash the Firmware on One or More CMICs in Systems with Legacy Server Management Note: During the flash procedure, the CMIC reboots causing a Lost Heartbeat event. At this point, the CMIC operating state displayed in the Tree View is Critical. After the CMIC successfully reboots, the operational state returns to OK (normal). 1 In the Tree View, select one or more CMICs. Note: If you select more than one CMIC, the firmware of each CMIC is flashed in parallel. 2 Select Functions > Flash Firmware. 3 When the confirmation dialog box displays, click Yes. 246 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Updating (Flashing) Firmware Flashing Fibre Channel Switch Firmware In systems with SM3G, Fibre Channel switch firmware is included with the CMIC image. For more information about installing a new CMIC image, see the appropriate Hardware Service Guide for your platform. To Flash the Firmware on One or More Fibre Channel Switches Note: If you select a Fibre Channel switch and any other component, the Flash Firmware command is unavailable. Note: If you select more than one Fibre Channel switch, the firmware of each Fibre Channel switch is flashed one switch at a time (serially). 1 In the Tree View, select the Fibre Channel switch or switches to be flashed. 2 Select Functions > Flash Firmware. 3 When a confirmation dialog box displays, click Yes. (The dialog box also reminds you to reset the Fibre Channel switch after the firmware flash completes. Resetting the switch activates the firmware.) 4 When the firmware flash completes, and the command complete dialog box displays, click Yes. 5 When the command status window displays, verify whether the flash completed successfully. 6 If the flash is successful, do the following to activate the firmware: a b c d e Select the same Fibre Channel switch or switches. Select Functions > Reset. When a confirmation dialog box displays, click Yes. (The dialog box also informs you that the switch or switches are temporarily out of service.) When the reset completes, and the command complete dialog box displays, click Yes. Verify the results of the reset by checking the output in the command status window. Configuring Default Values for the Fibre Channel Switch Viewing Command Output Teradata AWS User Guide, Release 4.5 247

Chapter 10: Servicing, Maintenance, and Troubleshooting Updating (Flashing) Firmware Flashing Ethernet Switch Firmware in Systems with SM3G In systems with SM3G, Ethernet switch firmware is included with the CMIC image. For more information about installing a new CMIC image, see the appropriate Hardware Service Guide for your platform. To Flash the Firmware on One or More Ethernet Switches 1 In the Tree View, select one or more Ethernet switches. 2 Select Functions > Flash Firmware. When the confirmation dialog box displays, click Yes. 3 When the firmware flash and switch reset completes, and the command complete dialog box displays, click Yes. 4 In the command status window, verify that the flash completed successfully and that the switch was reset. Viewing Command Output Flashing UPS and UPS Adapter Card Firmware in Systems with SM3G Caution: When flashing the firmware of UPSs and UPSs adapter cards, a power check is performed. If the power check fails, a dialog box displays that allows you to force the command to run. Do not force a command to run until you review the warning in Forcing a Command to Run after a Power Check Failure on page 264. In systems with SM3G, the firmware for both the UPS and UPS adapter cards is included with the CMIC image. For more information about installing a new CMIC image, see the appropriate Hardware Service Guide for your platform. To Flash the Firmware on One or More APC UPSs and UPS Adapter Cards Caution: Firmware on the UPS adapters and UPS cannot be flashed at the same time. Flash the firmware on the UPS adapters first, then the firmware on the UPS. (APC UPS firmware is extracted from APC UPS adapter 1.) 1 Download the current version of the CMIC image. The firmware for both the UPS and UPS adapters is included with the CMIC image. For more information, see the appropriate Hardware Service Guide for your platform. 2 In the Tree View, select both UPS adapters of each UPS you want to flash. Note: If you select more than one pair of UPS adapters in a cabinet, they are flashed one at a time (serially). 3 Select Functions > Flash Firmware. 4 At the confirmation dialog box, click Yes. 5 In the Tree View, select one or more UPSs whose adapter firmware has been flashed. 248 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Updating (Flashing) Firmware Note: If you select more than one UPS in a cabinet, they are flashed one at a time (serially). 6 Select Functions > Flash Firmware. 7 At the confirmation dialog box, click Yes. To Flash the Firmware on One or More Powerware UPSs or UPS Adapter Cards Caution: Caution: Firmware on the UPS adapter and UPS cannot be flashed at the same time. Flash the firmware on the UPS adapter first, then the firmware on the UPS. 1 Download the current version of the CMIC image. The firmware for both the UPS and UPS adapters is included with the CMIC image. For more information, see the appropriate Hardware Service Guide for your platform. 2 In the Tree View, select the UPS adapter of each UPS you want to flash. Note: If you select more than one UPS adapter in a cabinet, they are flashed one at a time (serially). 3 Select Functions > Flash Firmware. 4 At the confirmation dialog box, click Yes. 5 In the Tree View, select one or more UPSs whose adapter firmware has been flashed. Note: If you select more than one UPS in a cabinet, they are flashed one at a time (serially). 6 At the confirmation dialog box, click Yes. When flashing the firmware on the bottom two UPSs in the cabinet (UPS1 and/or UPS2), a short-term primary or secondary network outage may occur. Flashing Management Board Firmware in Systems with Legacy Server Management You can use the Functions > Flash Firmware in the Teradata AWS menu bar or in the Multi- Select Command to select and flash more than one management board. If multiple management boards controlled by a single CMIC are selected, the flash operation progresses sequentially in the order selected. If the management boards are in different collectives, the flash operation is processed in parallel, one flash at a time per collective. When the command status window displays for each flash operation, you can verify which flashes completed successfully. Caution: If you are flashing a UPS management board or universal management board, the cabinet power subsystem is checked for conditions that could cause a cabinet power off. If such a condition is discovered, a dialog box displays that allows you to force the command to run. Do not force the command to run until you review the warning in Forcing a Command to Run after a Power Check Failure on page 264. Teradata AWS User Guide, Release 4.5 249

Chapter 10: Servicing, Maintenance, and Troubleshooting Updating (Flashing) Firmware The Legacy Support > Flash CoProcessor Firmware command downloads new Communications Processor (CoProcessor) firmware to Universal Management Boards (UMBs). To Flash Management Board Firmware 1 Do one of the following: In the Tree View, management boards are listed with the chassis they manage. Expand the chassis containing the management board you want to flash and select the management board. Select Functions > Multi-Select Command and use the displayed window to select the management board or boards to be flashed. 2 In the AWS menu bar or the Multi-Select Command menu bar, do one of the following: Select Functions > Flash Firmware to flash the management board firmware. Select Legacy Support > Flash CoProcessor Firmware to flash the management board coprocessor firmware. 3 When the confirmation dialog box displays, click Yes. 4 If you selected a UPS management board, the cabinet power subsystem is checked for conditions that could cause a cabinet power off. If such a condition is discovered, a warning message displays. Click Yes to flash the UPS UMB, or No to cancel. 5 When the firmware flash completes and the confirmation dialog box displays, click Yes. 6 The results of the command display in the command status window. If a confirmation screen displays, click Ok. Viewing Command Output Flashing 49xx/53xx Node Management Board Firmware in Mixed-Node Cabinets Mixed-node cabinets contain 4900 and 4950 nodes, or 5300 and 5350 nodes. In these cabinets, you may have to use the SetFW command to flash the node management boards with the correct firmware. To Determine When to Use the SetFW Command on a Node Management Board To Flash a Node Management Board with the SetFW Command To Display Open Faults 250 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Checking Firmware Versions To Determine When to Use the SetFW Command on a Node Management Board The following procedure helps you determine if you need to use the SetFW command on a 49xx/53xx node management board, and which node management board to use it on. 1 Use the Event Mgmt > View Faults command to display open faults in the Fault Viewer. 2 In the Description column, check for the following fault: Wrong MB FW. If this fault is not displayed, you do not need to use the SetFW command. If this fault displays, you must use the SetFW command. Continue with the next step. 3 In the Fault Viewer, select the Wrong MB FW fault. 4 Click Functions > View Details. 5 In the Problem Description field, note the cabinet number and chassis number of the node associated with the management board. 6 Close the Fault Viewer. To Flash a Node Management Board with the SetFW Command 1 In the Tree View, expand the cabinet and chassis containing the node management board you want to flash. 2 Select the node management board and click View > Properties. 3 Write down the management board s Component ID, or copy it from the Properties dialog box, and click Ok. 4 From the AWS Start menu, click Programs > AWS > AWS Command Prompt. 5 At the prompt, do one of the following: If the node is a 4900 or 5300 node, type: setfw -f DOD2_MB.rom <mgmt board ComponentID> If the node is a 4950 or 5350 node, type one of the following, as appropriate: setfw -f HOD2_MB.rom <mgmt board ComponentID> setfw -f HLG2_MB.rom <mgmt board ComponentID> Checking Firmware Versions The Tools > Firmware Version Checker command highlights out-of-date firmware in the Firmware Version Checker and displays the following: Each component that has firmware All firmware instances for each component (some components have more than one firmware instance) The firmware version installed on each component The firmware version supported for each component Teradata AWS User Guide, Release 4.5 251

Chapter 10: Servicing, Maintenance, and Troubleshooting Checking Firmware Versions For components in systems with SM3G, the firmware version installed on the CMICs You can also use the Firmware Version Checker to flash firmware. The CheckFirmwareVersion utility is a scheduled program that discovers out-of-date firmware and displays the results as a fault in the Fault Viewer. Checking and Updating Firmware with the Firmware Version Checker Running the CheckFirmwareVersion Utility Checking and Updating Firmware with the Firmware Version Checker The Tools > Firmware Version Checker command compares the versions of firmware as follows: In systems with SM3G: For the CMIC Image, the command compares the CMIC Image versions installed on the CMICs with the version available in the SM3G CMIC Support package on the AWS. For all other components, the command compares the firmware versions installed on the components with the versions available on the CMICs and the SM3G CMIC Support package on the AWS. In systems with legacy server management (48xx/52xx and 49xx/53xx systems): The command compares the firmware versions installed on the components with the versions available in the SM3G Legacy SLAN support package on the AWS. The results display in the Firmware Version Checker window. To Check Firmware Versions and Display the Results The Firmware Version Checker Window The Firmware Version Checker Menu Bar Working with the Firmware Version Checker To Check Firmware Versions and Display the Results 1 Click Tools > Firmware Version Checker. 2 A Firmware Version Checker confirmation dialog box displays. It states that it may take a while to complete the task. Click Yes to continue. Note: A dialog box tracks the command s progress. 3 The Firmware Version Checker window displays. 252 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Checking Firmware Versions The Firmware Version Checker Window The Firmware Version Checker contains a row for each firmware instance in the system. The arrow indicates which column the information is sorted by, and whether the information is sorted in ascending (up arrow) or descending (down arrow) order. The columns are described in Table 74. Note: Highlighted rows (red, yellow, or gray rows) are described in the Status column. Note: Some components have more than one firmware instance. For example, in systems with legacy server management, a universal management board (UMB) has two firmware instances in the Firmware Version Checker one for co-processor firmware and one for management board (MB) firmware. Figure 79: Firmware Version Checker Window Table 74: Firmware Version Checker Window Description Column Component Definition Path, default alias, or component ID of the component, depending on the option set in the View menu of the Firmware Version Checker. A dot to the left of the command in the View menu identifies the current option. If View > Alias is set, the default alias displays. If a user-defined alias exists, it displays instead of the default alias. If View > Name is set, the path follows the hierarchy displayed in the Tree View. If View > ID is set, the CIM path displays. Teradata AWS User Guide, Release 4.5 253

Chapter 10: Servicing, Maintenance, and Troubleshooting Checking Firmware Versions Table 74: Firmware Version Checker Window Description (continued) Column Type Definition Type of firmware: Adapter Card Firmware (UPSs in systems with SM3G) Alert Knowledge (CMICs in systems with SM3G) CMIC Firmware (systems with legacy SMCs) CMIC Image (CMICs in systems with SM3G) Coprocessor Firmware (systems with legacy server management boards) Ethernet Switch Firmware (48-port Ethernet switches in systems with SM3G) FCSW (Fibre Channel switch) Firmware MB Firmware (systems with legacy management boards) UPS firmware (UPSs in systems with SM3G) Note: Firmware on UPS adapters and the UPS cannot be flashed at the same time. For an APC UPS, flash both adapters first, then the UPS. For a Powerware UPS, flash the adapter first, then the UPS. Available Version Systems with SM3G: Indicates the currently supported firmware version available from the SM3G CMIC Support package on the AWS Systems with legacy server management (48xx/52xx and 49xx/53xx): Indicates the currently supported firmware versions available from the SM3G Legacy SLAN package on the AWS Pending Version Systems with SM3G: Indicates the firmware version available from the SM3G CMICs; this is the version used by the Flash command Note: The CMIC image contains the firmware for UPSs, UPS adapters, Fibre Channel switches, and Ethernet switches. Use the CMIC Monitor to download the currently supported CMIC image from the SM3G CMIC Support package on the AWS to the SM3G CMICs. For more information, see the appropriate Hardware Service Guide for your platform. Systems with legacy server management (48xx/52xx and 49xx/53xx): Indicates the currently supported firmware versions available from the SM3G Legacy SLAN package on the AWS; this is the version used by the Flash command Active Version Status Firmware version installed on the component Indicates whether the Available Version, Pending Version, and Active Version columns: Match (OK): The firmware version installed is the currently supported version. Are a Mismatch (Mismatch): The firmware version installed is not the currently supported version. Do not contain version information (Unknown): The firmware version information is missing or unavailable. When there is a match, the row is not highlighted. When there is a mismatch, or missing information, one of the following colors is used to highlight the corresponding row: Red: Red indicates that a more current version of the CMIC Image (SM3G only) is available on the AWS. Yellow: For all components except the CMIC Image (SM3G only), yellow indicates that a more current version of firmware is available on the CMICs or AWS, as appropriate. Gray: Gray indicates that firmware version information is missing. 254 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Checking Firmware Versions The Firmware Version Checker Menu Bar The following table describes the commands available from each menu in the Firmware Version Checker menu bar. Table 75: Firmware Version Checker Commands Contains commands for rediscovering all firmware versions, changing the display name of components, and closing the window. See: To Rediscover the Firmware Version Information of All Components on page 256 To Change the Component Name Displayed in the Firmware Version Checker on page 255 To Close the Firmware Version Checker Window on page 256 Contains commands for flashing firmware and refreshing the firmware versions of selected components. Displays Firmware Version Checker help. See: To Use the Firmware Version Checker to Flash Out-of-Date Firmware on page 255 To Refresh the Firmware Version Information of Selected Components on page 256 See: Using Teradata AWS Online Help on page 43. Working with the Firmware Version Checker Note: For a description of the columns in the Firmware Version Checker window, see Table 74 on page 253. To Change the Component Name Displayed in the Firmware Version Checker In the View menu of the Firmware Version Checker, select Alias, Name, or ID. Note: A dot to the left of the command in the View menu identifies the current setting (Alias, Name, or ID) for the Component column in the Firmware Version Checker. To Use the Firmware Version Checker to Flash Out-of-Date Firmware 1 From the Firmware Version Checker window, select one or more components whose firmware you want to flash. Note: Firmware on UPS adapters and UPSs cannot be flashed at the same time. Flash the firmware on the UPS adapters first, then the firmware on the UPSs. The Powerware UPS has one UPS adapter (ADPCARD.x.x.x.1 in the Firmware Version Checker), the APC UPS has two UPS adapters (ADPCARD.x.x.x.x.1 and ADPCARD.x.x.x.x.2). Note: When flashing APC UPS adapter cards, select both adapter cards in the same UPS. For example, to flash the first APC UPS adapter cards shown in Figure 79 on page 253, you would select ADPCARD 1.1.1.1.1 and ADPCARD 1.1.1.1.2. Teradata AWS User Guide, Release 4.5 255

Chapter 10: Servicing, Maintenance, and Troubleshooting Checking Firmware Versions 2 Select Functions > Flash. 3 To update the firmware information in the Firmware Version Checker window, use one of the following procedures: To Rediscover the Firmware Version Information of All Components To Refresh the Firmware Version Information of Selected Components To Rediscover the Firmware Version Information of All Components The View > Reload command reruns the Tools > Firmware Version Checker command. In the Firmware Version Checker, select View > Reload. Note: A dialog box tracks the command s progress. To Refresh the Firmware Version Information of Selected Components The Functions > Update command updates the firmware information of selected components in the Firmware Version Checker window. 1 In the Firmware Version Checker, select one or more components. 2 Select Functions > Update. Note: A dialog box tracks the command s progress. To Close the Firmware Version Checker Window In the Firmware Version Checker, select View > Close. Running the CheckFirmwareVersion Utility If the CheckFirmwareVersion utility is enabled and run as a regularly scheduled program, it discovers out-of-date firmware and, in the Fault Viewer, displays a Degraded fault. The fault contains a list of components that have out-of-date firmware or whose firmware versions are unavailable. To view faults, use the Fault Viewer. To flash out-of-date firmware, use the Functions > Flash Firmware command or Legacy Support > Flash CoProcessor Firmware in the AWS main window. Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer. Updating (Flashing) Firmware Configuring the CheckBatteries and CheckFirmwareVersion Utilities 256 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Tracking and Setting Battery Installation and Replacement Dates Tracking and Setting Battery Installation and Replacement Dates The life of a UPS battery is expected to be three years. UPS batteries must be replaced before they expire. The following commands allow you to set and track battery installation and replacement dates: The Functions > Set Battery Date command allows you to change the battery installation date for one or more batteries in a system with SM3G. The Tools > Battery Date Information command allows you to do the following: View information about UPS battery installation and expiration dates for all the UPS batteries in the system, including batteries in systems with legacy server management. Change the battery installation date of one or more batteries in a system with SM3G. The CheckBatteries utility, if enabled, uses the battery installation date to determine when UPS batteries are ready to expire. UPSs that have batteries that are close to their expiration date display as faults in the Fault Viewer. Selecting Batteries and Setting Installation Dates Displaying Battery Date Information and Setting Battery Installation Dates Running the CheckBatteries Utility Selecting Batteries and Setting Installation Dates To Use the Set Battery Date Command to Change Battery Installation Dates Note: You can change the battery installation date of one or more batteries in a system with SM3G. 1 In the Tree View, select one or more UPS batteries. 2 Select Functions > Set Battery Date. 3 When the Set Battery Date dialog box displays, in the Battery Installation Date field, enter the new battery date for the selected batteries. Use the format YYYYMMDD. For a description of the fields in the dialog box, see Table 78 on page 260. 4 Click Ok. Displaying Battery Date Information and Setting Battery Installation Dates To Display Battery Date Information for All UPSs in a System 1 Select Tools > Battery Date Information. 2 The Battery Date Information window displays. Teradata AWS User Guide, Release 4.5 257

Chapter 10: Servicing, Maintenance, and Troubleshooting Tracking and Setting Battery Installation and Replacement Dates Battery Date Information Window Battery Date Information Menus Working with the Battery Date Information Window Configuring the CheckBatteries and CheckFirmwareVersion Utilities SetBatteryDate Battery Date Information Window When you select the Tools > Battery Date Information command, the Battery Date Information window displays. The window contains a list of all batteries in the system, and their installation and replacement dates. The arrow indicates which column the information is sorted by, and whether the information is sorted in ascending (up arrow) or descending (down arrow) order. Figure 80: Battery Date Information Window Table 76: Battery Date Information Window Description Column Chassis Definition Path to the UPS that houses the battery; the path follows the hierarchy displayed in the Tree View. A green (OK) severity indicator displays if the battery installation date is newer than 2.5 years. An orange (degraded) severity indicator displays for any battery older than 2.5 years. A magenta (critical) severity indicator displays for any battery older than 3.0 years. Note: The CheckBatteries utility checks UPSs for batteries that have expired and for batteries that are within 6 months of expiring. 258 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Tracking and Setting Battery Installation and Replacement Dates Table 76: Battery Date Information Window Description (continued) Column Installation Date Replacement Date Definition Date the battery was installed; if information about the installation date of the battery is unavailable, this column is blank. Note: The CheckBatteries utility ignores batteries that do not have installation dates. If a battery does not have an installation date, you can add one. To add an installation date for UPSs in systems with legacy server management, select the UPS in the Tree View, and then use the Legacy Support > Update Asset Information command to add the installation date to the UPS Battery Date field. Date the battery must be replaced; if information about the installation date of the battery is unavailable, this column is blank. Battery Date Information Menus The following table describes the commands available from each menu in the Battery Date Information window menu bar. Table 77: Battery Date Information Window Commands Closes the Battery Date Information window. Contains commands for selecting batteries and changing battery installation dates. See: To Close the Battery Date Information Window on page 261. See: To Set Battery Installation Dates on page 260. Displays Battery Date Information help. See: Using Teradata AWS Online Help on page 43. Working with the Battery Date Information Window Note: For a description of the Battery Date Information window, see Table 76: Battery Date Information Window Description on page 258. To Sort Battery Information by Column Click the appropriate column header. To toggle between ascending and descending order, click the column header. Teradata AWS User Guide, Release 4.5 259

Chapter 10: Servicing, Maintenance, and Troubleshooting Tracking and Setting Battery Installation and Replacement Dates To Set Battery Installation Dates Note: You can change the battery installation date for one or more batteries in a system with SM3G. 1 Select Tools > Battery Date Information. 2 When the Battery Date Information window displays, do one of the following: a b c To change the installation dates of specific batteries, select those batteries in the Battery Date Information window. To change the installation date of all the batteries in the Battery Date Information window, select Functions > Select All. If the system is a coexistence system that contains cabinets with legacy server management and cabinets with SM3G, the Select All and Set Battery Date commands in the Functions menu are inactive. To set battery dates for batteries in cabinets with SM3G, you must manually select only the batteries in those cabinets. You cannot set battery dates for batteries in cabinets with legacy server management. 3 Select Functions > Set Battery Date. 4 When the Set Battery Installation Date(s) dialog box displays, in the Battery Installation Date field, enter the new battery date for the selected batteries. Use the format YYYYMMDD. For a description of the fields in the dialog box, see Table 78 on page 260. Figure 81: Modify Battery Installation Date(s) Window Table 78: Set Battery Installation Date(s) Window and Set Battery Date Dialog Box Description Item Selected Batteries Set Battery Date Description Contains a list of the batteries previously selected from the Battery Date Information window. Contains the current date by default; you can enter a new date in the Battery Installation Date field. The date must be entered in the format YYYYMMDD. For example, 20050323. When you click Ok, the selected batteries all have the same date. 5 Click Ok. 260 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Tracking and Setting Battery Installation and Replacement Dates To Close the Battery Date Information Window Select one of the following from the Battery Date Information window: a b File > Exit. The Close button. Running the CheckBatteries Utility If the CheckBatteries utility is enabled and run as a regularly scheduled program, it uses the battery installation date to determine when UPS batteries are ready to expire, and display a fault for the UPS in the Fault Viewer. The life of a UPS battery is expected to be three years. When a battery is older than 2.5 years, the CheckBatteries utility generates a fault showing that the battery is operating in a degraded state and needs to be replaced. When a battery is older than 3 years, it has expired. The CheckBatteries utility generates a critical fault showing that the battery has expired and needs to be replaced. If the CheckBatteries utility finds more than one battery in a degraded or critical state, it generates one fault for batteries in a degraded state, and one fault for batteries in a critical state. To view faults, use the Fault Viewer. To determine which batteries need to be replaced, select the fault, and then use the Fault Viewer s View > Fault Details command to get a list of the batteries that need to be replaced. To get a list of the operational state of all the batteries in the system, use the Tools > Battery Date Information command. Note: The CheckBatteries utility ignores batteries that do not have installation dates. To add an installation date for a UPS in a system with legacy server management, select the UPS in the Tree View, and then use the Legacy Support > Update Asset Information command to add the installation date to the UPS Battery Date field. Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer. Fault Details To Display Battery Date Information for All UPSs in a System Configuring the CheckBatteries and CheckFirmwareVersion Utilities Tracking and Setting Battery Installation and Replacement Dates Updating Asset Information for Components in Systems with Legacy Server Management Teradata AWS User Guide, Release 4.5 261

Chapter 10: Servicing, Maintenance, and Troubleshooting Dumping Node Memory Dumping Node Memory Caution: Typically, you would select this item only when instructed to do so by Teradata technical support personnel. It is used when the node is unresponsive. To start the Memory Dump process, select an SMP node from the Tree View, then select the Functions > Dump Memory command. This operation does not perform a graceful shutdown. Resetting Components The Functions > Reset command lets you reset components. Table 79 lists the components you can reset from the Tree View. Table 79: Resettable Components Component System Node Cabinet CMIC (SM3G) or SMC (legacy server management) Node Chassis BYNET Chassis Ethernet Switch (48-port) Fibre Channel Switch Result A graceful shutdown and reboot of all the node (SMP) chassis in the system will be attempted. * A graceful shutdown and reboot of the node (SMP) chassis in the cabinet will be attempted. * During a reset of an SM3G CMIC, the CMIC will reboot. During a CMIC reset of a legacy SMC, the operational status may change to Lost Heartbeat before returning to normal. A graceful shutdown and reboot of the node (SMP) chassis will be attempted. * Resets the BYNET chassis. Note: This does not reset the BYNET network. If the system contains a BYB64G chassis in the BYNET network, it may be necessary to use the BYNET Utility to reset the BYNET network after resetting a BYNET chassis. After the Reset command completes, the AWS displays a dialog box asking the user if the BYNET Utility should be invoked. For information about when it is appropriate to use the BYNET Utility, see the Service Guide appropriate for your system. Resets the Ethernet switch; the ports on the attached devices will go to link down and be unavailable during the reset. Resets the Fibre Channel switch; the ports on the attached devices will go to link down and be unavailable during the reset. You must also use the Reset command to activate Fibre Channel switch firmware after a firmware flash. 262 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Managing System Power Table 79: Resettable Components (continued) Component Management Boards (systems with legacy server management) UPS Adapter Card Result During a management board reset, the operational status may change to Lost Heartbeat before returning to normal. Resets the adapter card(s) in the UPS in systems that have one. Note: When resetting adapter cards for an APC UPS, it is recommended that you select both APC UPS adapter cards. * Note: If a graceful shutdown fails, the node chassis is issued a hardware reset after approximately 11 minutes. This causes the SMP chassis to reset and then reboot. To Reset One or More Components Caution: Caution: Before starting a system reset, a node (SMP) chassis reset, or a processing node cabinet reset, shut down appropriate applications to ensure data integrity. 1 In the Tree View, select one or more components. Note: If you select one or more Fibre Channel switches and any other component, the Reset command is unavailable. 2 Select Functions > Reset. If a power check fails during the reset of a UPS adapter card or Fibre Channel switch, a dialog box displays that allows you to force the command to run. Do not force any command to run until you review the warning in Forcing a Command to Run after a Power Check Failure on page 264. Managing System Power The Functions > Power Off command and the Functions > Power On command power systems, cabinets, and chassis off and on, respectively. Forcing a Command to Run after a Power Check Failure Powering Off a System/Cabinet/Chassis Powering On a System/Cabinet/Chassis Recovering from a Power Failure Teradata AWS User Guide, Release 4.5 263

Chapter 10: Servicing, Maintenance, and Troubleshooting Managing System Power Forcing a Command to Run after a Power Check Failure A dialog box displays if a power check fails during the performance of one of the following commands: Command Component Reset UPS adapter cards (systems with SM3G) Power On System Fibre channel switch Cabinet Flash Firmware UPS and UPS adapter cards (systems with SM3G) UPS management board or universal management board (systems with legacy server management) UPS Self Test UPS UPS adapter card (systems with SM3G) UPS Input Selector Test UPS UPS adapter card (systems with SM3G) To Force a Command to Run Warning: Forcing a command to run should only be done as a last resort, and only under the direction of a Customer Service Representative. When the Force dialog box displays, click Yes. Powering Off a System/Cabinet/Chassis You can use the Functions > Power Off command to power off the following components. Table 80: Effects of Power Off Command on Components Component System Effect of the Functions > Power Off command: The command powers off all the cabinets in the system, in the following order: 1 Processing node (SMP) cabinets after an orderly shutdown of the nodes; if a node does not power off successfully, none of the subsequent cabinets are powered off * 2 Disk array cabinets 3 BYNET cabinets, if present, in systems with legacy server management 264 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Managing System Power Table 80: Effects of Power Off Command on Components (continued) Component Node Cabinet Disk Cabinet BYNET Cabinet Effect of the Functions > Power Off command: The command powers off the following chassis, in the following order: 1 SMP nodes (after an orderly shutdown) * 2 BYNET chassis, if present, in systems with legacy server management The command powers off the disk array chassis. The command powers off BYNET chassis in systems with legacy server management Node Chassis Only the selected nodes (after an orderly shutdown) * BYNET Chassis Only the selected BYNET chassis in systems with legacy server management * Warning: If an orderly shutdown is unsuccessful, the node remains on until the battery is drained, then it shuts down. To Power Off a System, Cabinet, or Chassis Caution: Caution: Before removing power from a system, cabinet, or chassis, notify users and determine if any applications are running on the SMP node. If applications are running, terminate them. Data integrity cannot be ensured unless you shut down all applications before starting a power off. 1 In the Tree View, select the component or components you want to power off. 2 Select Functions > Power Off. 3 A confirmation dialog box displays, asking you to confirm the power off. Click Yes. If you selected one or more nodes, or if a node is present, the operating system performs an orderly shutdown and the component or components are powered off. Powering On a System/Cabinet/Chassis You can use the Functions > Power On command to power on the following components in the system: Table 81: Effects of Power On Command on Components Component System Node Cabinet Effect of the Functions > Power On command The command powers on all the cabinets in the system, in the following order: 1 BYNET cabinets, if present, in systems with legacy server management 2 Disk array cabinets 3 Processing node (SMP) cabinets The command powers on the following chassis, in the following order: 1 BYNET chassis, if present, in systems with legacy server management 2 SMP nodes Teradata AWS User Guide, Release 4.5 265

Chapter 10: Servicing, Maintenance, and Troubleshooting Managing System Power Table 81: Effects of Power On Command on Components (continued) Component Disk Cabinet BYNET Cabinet Node Chassis BYNET Chassis Effect of the Functions > Power On command The command powers on the disk array chassis. The command powers on BYNET chassis in systems with legacy server management. Only the selected nodes Only the selected BYNET chassis in systems with legacy server management To Power On a System, Cabinet, or Chassis 1 In the Tree View, select the component or components you want to power on. 2 Select Functions > Power On. 3 A confirmation dialog box displays, asking you to confirm the power on. Click Yes to power on the component or components. The AWS displays the results in the Results Panel and updates the Tree View. Caution: If a power check fails when a system or cabinet is being powered on, a dialog box displays that allows you to force the command to run. Do not force any command to run until you review the warning in Forcing a Command to Run after a Power Check Failure on page 264. Note: If a legacy system contains a BYB64G chassis in the BYNET network, it may be necessary to use the BYNET Utility to reset the BYNET network when a BYNET chassis is powered on. After the Power On command completes, the AWS displays a dialog box asking the user if the BYNET Utility should be invoked. For information about when it is appropriate to use the BYNET Utility, see the Service Guide appropriate for your system. Recovering from a Power Failure A power failure occurs when AC power has been lost to one or more cabinets within the system. AC power can be lost for up to 15 seconds without harm. After 15 seconds, an orderly shutdown of the nodes occurs. To Recover from a Power Failure to All Cabinets in the System Note: To recover from an EPO activation in systems with SM3G server management, follow the procedure Restoring Power After an EPO Event in the Hardware Service Guide for your platform. 1 After AC power has been restored, if the AWS lost power due to the AC-FAIL, wait for the AWS PC to boot. 2 Log on to the AWS and start the Teradata AWS. 3 When the CMICs are operational, select the system in the Tree View. 266 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Performing Diagnostic Tests 4 Select Functions > Power On. Note: Disk array cabinets automatically power on when recovering from a power failure. 5 Verify that system components are operating normally. 6 When all SMP nodes have booted, the system is ready to begin recovery of any application that was disrupted when power was lost. Starting Applications on the AWS Performing Diagnostic Tests UPS Power Cabling Test UPS Self-Test UPS Input Selector Test MLAN Integrity Test UPS Power Cabling Test The Functions > Power Cable Test command verifies whether the chassis in a cabinet are correctly cabled to the UPSs in the cabinet. The command allows you to troubleshoot cabinet power failure problems. It is recommended that you run the test after system installation, or if new components are added to the cabinet. How the Power Cable Test Command Works Power Cable Test Dialog Box To Test UPS Power Cabling for a Cabinet Component Names How the Power Cable Test Command Works The Power Cable Test command first checks the status of each UPS and chassis power supply to see if there are problems. If there are no problems, the command runs. If there are problems, the UPSs and power supplies with problems display. You can continue with the test, or cancel. Next, the CMIC powers off and on each of the load groups on every UPS in the cabinet, one at a time. As each load group powers off, the CMIC detects and logs the following: Any chassis power supply that lost power when it should not have Any chassis power supply that did not lose power when it should have Teradata AWS User Guide, Release 4.5 267

Chapter 10: Servicing, Maintenance, and Troubleshooting Performing Diagnostic Tests When the test is completed, one of the following messages displays: Power Cable Test complete with no errors! Power Cable Test complete with errors A list displays stating how the incorrectly cabled UPS load groups and chassis power supplies should be cabled. Power Cable Test Dialog Box The Power Cable Test dialog box (Figure 82) displays test status. As the test runs, you can use the Details/No Details button to display or hide test details for each load group and associated chassis power supplies. Load groups that have passed the test display in green, those that have failed the test display in red, and those that have not yet been tested are in black. See Table 82 for a description of the test details and dialog box buttons. Figure 82: Power Cable Test Dialog Box Table 82: Power Cable Test Dialog Box Description Item Status Overall Progress Load Group Description Shows command status as each UPS load group and chassis power supply is tested; lists UPS load group and chassis power supplies that are incorrectly cabled Shows the progress of each UPS load group and power supply tested as the command runs The default Alias or CIM path for the UPS load group being tested. If a user-defined Alias exists, it displays instead of the default Alias. 268 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Performing Diagnostic Tests Table 82: Power Cable Test Dialog Box Description (continued) Item Expected Unexpected Result Details/No Details button Continue button Restart button Cancel button Description The default Alias or CIM path for the power supply the UPS load group should be cabled to. Correctly cabled power supplies are in green. If a user-defined Alias exists, it displays instead of the default Alias. The default Alias or CIM path for the power supply the UPS load group is incorrectly cabled to. Incorrectly cabled power supplies are in red. If a user-defined Alias exists, it displays instead of the default Alias. Shows the results of the power cabling test for each UPS load group and power supply: OK (green): Power supply is correctly cabled. ERROR (red): Power supply is incorrectly cabled. Toggles between hiding and displaying test details for the UPS load groups and chassis power supplies being tested Allows you to continue the test if the command discovers problems with the UPSs and power supplies whose cabling is about to be tested Allows you to restart the test; you can use the button before or after fixing incorrect power cabling Cancels the command To Test UPS Power Cabling for a Cabinet 1 Stop the Teradata Database. 2 In the Tree View, select the cabinet whose UPS power cabling you want to test. 3 Select Functions > Power Cable Test. The Power Cable Test dialog box displays. If there are no UPS or power supply problems, the power cable test continues. If there are UPS or power supply problems, as shown below, do one of the following: Teradata AWS User Guide, Release 4.5 269

Chapter 10: Servicing, Maintenance, and Troubleshooting Performing Diagnostic Tests UPS Self-Test Click Continue to resume the test without fixing the components. Fix the components, then click Continue to run the command without re-checking the components. Click Cancel, fix the components, then restart the command to re-check the components. 4 To display test details, click the Details button. 5 If the command finds a cabling error, the fix for the incorrectly cabled UPS load group and power supply displays in the Status field. Do one of the following: To wait until after the test to fix the cabling error(s), click Continue each time a cabling error is found. To fix each cabling error one-at-a-time during the test, fix the cabling as described in the Status field, then click Restart. 6 When the test completes, the Status window displays one of the following messages: a b If no cabling errors were found during the test, the message states that the test is complete with no errors. If cabling errors were found, the message states that the test is complete, with errors. A list of the fixes for the incorrectly cabled UPS load groups and power supplies displays in the Status field. (The list is provided even if you fixed the cabling errors during the test.) The Functions > UPS Self Test command checks the functionality of the UPS to determine whether the UPS s internal components are working properly. The command runs only if all other power-related components in the cabinet have an operating status of OK. It should be run on only one UPS at a time in a cabinet. 270 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Performing Diagnostic Tests To Run a UPS Self-Test Caution: If a power check fails during the UPS self-test, a dialog box displays that allows you to force the command to run. Do not force any command to run until you review the warning in Forcing a Command to Run after a Power Check Failure on page 264. 1 In the Tree View, select a UPS. 2 Select Functions > UPS Self Test. Command results, whether the test completed successfully or not, are available in the Command Summary window. Details about test errors, if any, appear in the Event Viewer and Fault Viewer. UPS Input Selector Test The Functions > UPS Input Selector Test command checks the functionality of the UPS Input Selector to determine whether it is working properly. The UPS Input Selector Test forces a switch from the default power source to the alternate power source to verify that the switchover capability is functional. When the UPS switches to the alternate power source, a transient AC fail displays in the Event Viewer. When the test is complete, the system switches power back to the default power source. The system does not switch to the alternate power source if the alternate power source is not operating normally. When you run this test, all other power-related components in the cabinet have an operating status of OK. The test should be run on only one UPS at a time in a cabinet. Caution: If a power check fails during UPS input selector test, a dialog box displays that allows you to force the command to run. Do not force any command to run until you review the warning in Forcing a Command to Run after a Power Check Failure on page 264. To Run a UPS Input Selector Test 1 In the Tree View, check the status of the UPS containing the UIS you want to run the test on to make sure it is operating normally. 2 Select the UPS. 3 Select Functions > UPS Input Selector Test. Command results, whether the test completed successfully or not, are available in the Command Summary window. Details about the test, including test errors, if any, appear in the Event Viewer and Fault Viewer. Teradata AWS User Guide, Release 4.5 271

Chapter 10: Servicing, Maintenance, and Troubleshooting Accessing the BYNET Utility MLAN Integrity Test In systems with legacy server management, the Legacy Support > MLAN Integrity Test command tests the functionality of the service subsystem MLAN connections. The Rack Chassis Management Boards automatically initiate the MLAN Integrity Test diagnostic once per day (approximately every 18 hours). The Legacy Support > MLAN Integrity Test command allows you to run the diagnostic as needed. It is typically used if there are MLAN problems or if new components appear to have configuration problems. Test results are reported as events that are stored in the AWS events database. To Run an MLAN Integrity Test 1 In the Tree View, select a legacy SMC that contains a CMIC. 2 Select Legacy Support > MLAN Integrity Test. Command results, whether the test completed successfully or not, are available in the Command Summary window. Details about test errors, if any, appear in the Event Viewer and Fault Viewer. Accessing the BYNET Utility The primary function of the BYNET Utility is to determine BYNET groupings and service the BYNET chassis as collections rather than as individual chassis. It is also a useful troubleshooting tool. For more information about the BYNET Utility, see the Service Guide appropriate for your system. Note: When you use the Remote AWS feature, the BYNET Utility command is unavailable. 272 Teradata AWS User Guide, Release 4.5

Chapter 10: Servicing, Maintenance, and Troubleshooting Accessing the BYNET Diagnostic Service Subsystem Program (DSSP) To Launch the BYNET Utility Select Tools > BYNET Utility. The utility has its own Help system. Figure 83: BYNET Utility Window Accessing the BYNET Diagnostic Service Subsystem Program (DSSP) The BYNET DSSP utility is used for diagnostic purposes only and should be run only when instructed to do so by customer service personnel. The utility has its own Help system. For more information about the BYNET DSSP utility, see the Service Guide appropriate for your system. Note: When you use the Remote AWS feature, the DSSP Main command is unavailable. Teradata AWS User Guide, Release 4.5 273

Chapter 10: Servicing, Maintenance, and Troubleshooting Accessing the BYNET Diagnostic Service Subsystem Program (DSSP) To Launch the BYNET DSSP Select Tools > DSSP Main. Figure 84: DSSP Main Window 274 Teradata AWS User Guide, Release 4.5

APPENDIX A Teradata AWS Command Line Interface The 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 through Telnet when the remote connection is too slow to adequately support GUI operation. You can also run the commands through the Remote AWS feature. Access to Teradata AWS CLI Utilities Using the Teradata AWS CLI Access to Teradata AWS CLI Utilities Command access is determined by your user group membership. AWS Users and users with Administrator privileges have full access to all the Teradata AWS CLI utilities. The CLI utilities are listed in Table 83; AWS Guests do not have access to the CLI utilities marked with an asterisk (*). 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 CLI utilities. Table 83: Teradata AWS: Access to CLI Utilities CLI Utilities (Utilities Accessible by AWS Guests Are Marked with an Asterisk) AlertRegister * AssetInfo AWSHelp DumpMemory * FaultUtil * FWConfig * MeasurementInfo MLANTest * ReadSCSI Teradata AWS User Guide, Release 4.5 275

Appendix A: Teradata AWS Command Line Interface Using the Teradata AWS CLI Table 83: Teradata AWS: Access to CLI Utilities (continued) CLI Utilities (Utilities Accessible by AWS Guests Are Marked with an Asterisk) RemComponent * Rescan Reset * SetBatteryDate * SetFW * SetPower * ShowBatteries ShowComponents ShowFirmwareVersion ShowProperties UpdateStatus UPSTest * ViewAssetHistory ViewEvents ViewMeasurementHistory User Groups Configuring Permissions for Members of AWS Guests Using the Teradata AWS CLI Using the Teradata AWS CLI The CLI is accessible from a DOS Command Prompt window (Start > Programs > Teradata AWS > AWS Command Prompt). The AWS command prompt is automatically set to the AWS bin directory where the AWS command line executables are located. To access the AWS command prompt, on the desktop, select Start > Programs > Teradata AWS > AWS Command Prompt. Caution: When you use a CLI command, the command is executed when you press return. You are not asked to confirm whether you want to run the command. CLI programs generally rely on a Component ID or alias to identify the component that is being operated upon. The ShowComponents command allows you to find Component IDs or 276 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface AlertRegister aliases, or you can get them from the Properties dialog box in the GUI by using the View > Properties command. The following general rules apply to all CLI commands: Command names are shown mixed-case for readability (for example, SetFW). They are not case-sensitive under Windows. All commands, except where noted, accept more than one Component ID or alias, separated by commas or spaces, so you can, for example, power on two cabinets with one command. All options start with either - or /. Anything else is interpreted as a Component ID or alias. Partial words for options may be typed, as long as enough letters are typed to identify the option. For example, -r and -rec and -recursive all mean the same thing. AlertRegister This command configures alert actions that occur when a fault matches the filter criteria. Alert actions include running a command line, sending e-mail, and sending a page. This command allows you to customize the AWS to send alert messages to specified personnel when a fault requiring their attention occurs. This command has three forms: Register an alert definition Display alert definitions Unregister an alert definition The three forms of this command are entered in the following format: alertregister -H[elp] alertregister -R action_name [-p priority] [match_criteria] [action_options] alertregister -D action_name alertregister -U [action_name] AlertRegister Options AlertRegister Match Criteria Options AlertRegister Action Options AlertRegister Alert Data Parameters Appendix C: Configuring Alerts Teradata AWS User Guide, Release 4.5 277

Appendix A: Teradata AWS Command Line Interface AlertRegister AlertRegister Options Option Name Description -Help Help Display help for the alertregister command. -R Register Register the alert action definition. -U Unregister Remove the alert action definition. -D Display Display the alert action definition. Default is all alert actions. action_name Action name Logical name given to an alert definition. -p <priority> Priority Register in the specified order. Enter a digit <priority> indicating the position at which this action should be run. Default is registered last. match_criteria Match criteria Specifies conditions that must be met to trigger the alert action. action_options Action options Specifies how to run the action. AlertRegister Match Criteria Options The following options are used to register an alert. When a fault matching the criteria occurs, the specified alert action is triggered. Option Name Description [-fault] Fault Apply match criteria to new faults. This is the default. [-c=componentid] ComponentID Specify the fault SourceInstance (the default alias for the component). The format is: TYPE.Sys.Col.Cab.Chas.ID with a wild card (*) in any ID position. For example, in systems with SM3G server management, -c=node*.* specifies any node chassis faults; in systems with legacy server management, -c=smp*.* specifies any node chassis faults. [-sev={ok, Info, Warning, Degraded, Critical, Fatal} x-y] Severity Specify a set of severity names separated by comma, or specify a severity level range, by number, x to y; Ok=1, Info=2, Warning=3, Degraded=4, Critical=5, Fatal=6, respectively. [-time=hh:mm-hh:mm] Time Specify range of time, where hh is the hour(0-23) and mm is the minutes (0-59). [-days={sun, Mon, Tue, Wed, Thu, Fri, Sat}] Days Specify a set of days separated by comma. [-o=objecttype] ComponentName Specify the ComponentName portion of the component s ComponentID. For example, Disk_XBB is the objecttype for the ComponentID Disk_XBB.SystemID=1,CollectiveID=1,CabinetID=1, ID=10. 278 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface AlertRegister Option Name Description [-source=sourcename] Fault Problem Domain Specify fault problem domain name. Use wild-card * for partial matching. For example: -source=winlog-teradata or -source=mpras-pde. [-prob="problemcode[;.]"] Problem Code Specify a set of fault problem codes separated by semi-colon. Use double quotation marks to enclose special characters and spaces. For example: -prob= 1234;34001001. Use this in conjunction with -source (the source filter) to uniquely identify the fault type. Registering Alert Match Criteria AlertRegister Action Options The following options allow you to specify an alert action type and any relevant options. Option Name Description [-abey=mmm] Abeyance Specify abeyance time period, where mmm is minutes, to suppress this alert action following last time triggered. The default is 0 (no abeyance). -run="action_command" [run_options] Run Create a process and run the command line. Include the full path of the application to run and its arguments enclosed in double-quotation marks. Startup Options alter the default behavior of run action process. Action processes are created by default as non-interactive. The following Run options are available: [-env] Specifies that environment variables for Alert Data Parameters are to be passed to the action process. [-show] Specifies that this action interacts with desktop and requires a console window for input/output. [-hide] Specifies that this action interacts with desktop and does not require a console window. Teradata AWS User Guide, Release 4.5 279

Appendix A: Teradata AWS Command Line Interface AlertRegister Option Name Description -email="destaddress" -subject="short text" -message="email body text" -page=pageserviceid -subject="short text" E-mail Page Send an alert message via email to specified recipients. The mail server must first be configured using the AWS Configuration application s Alert Manager Mail dialog box tab. [-email= destaddress ]: One or more SMTP addresses (for example, john @smith.com) separated by a comma. [-subj= short text ]: The subject is a short text line and may contain Alert Data Parameters. [-mess="long_message_text"]: The e-mail body text, which may contain multiple lines (indicated by $_) and Alert Data Parameters. For example: -email="joeadmin@myco.com" -subj="fault $SeverityName" -mess="connect to $AWSName and use AWS Fault Viewer to analyze problem $ID occurring for $ObjectPath $Description" Send a page message. The page service must first be configured using the AWS Configuration application s Alert Manager Page dialog box tab. [-page=pageserviceid]: The name of the page service. [-subj= short text ]: The subject is a short text line and may contain Alert Data Parameters. For example: -page=skytel -subject="fault on $AWSName" Registering Alert Actions AlertRegister Alert Data Parameters The following parameters can be specified as run command line arguments or in subject/ message for email or page. They are expanded from the fault data when the action is dispatched. With -run and -env they are available as environment variables. Parameter Description $$ Use $$ to specify single $ character. $_ $AWSName $CreateTime $SeverityName $Source $ProblemCode $ObjectPath $ID Use $_ or control+a to specify newline character. Computer name of AWS to connect to for problem analysis. Time the fault was detected. Severity level of fault. For example: Warning, Degraded, Critical or Fatal. Fault's problem domain. An error code within fault domain. Identifier of the managed object that reported the fault. Unique reference to the fault record in the AWS fault database. 280 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface AssetInfo Parameter $Description $Data $ComponentID Description Fault description and recommendation, when available. The fault's AdditionalData property. The default Alias name for a component that reported or is impacted. AssetInfo AssetInfo Options This command allows you to display, or output to a file, asset information for specific chassis or for all chassis contained in a system, collective, or cabinet. The command is entered in the following format: assetinfo [-h[elp]] [-f [ile] outputfile -c[sv]] <components> AssetInfo Options Option Name Description -h [elp] Help Displays help for this command. -f [ile] outputfile Filename Specifies the name of the file to which the chassis asset information will be output. If the full path is not specified, the file is stored in the \Documents and Settings\<username>\AWS\UserData directory. If this option is not used, the information is output to the screen. -c[sv] CSV Saves the asset information in CSV (comma separated value) format to the specified outputfile. The information can then be viewed with spreadsheet software. If this option is not used, the asset information is saved to a text file that can be viewed with an ASCII text editor. components Component ID or Alias Unique ID of the system, collective, cabinet, or chassis whose chassis asset information you want to see or save to a file. The unique ID can be a Component ID, default alias, or user-defined alias. ShowComponents Teradata AWS User Guide, Release 4.5 281

Appendix A: Teradata AWS Command Line Interface AWSHelp AWSHelp This command displays a list of the available AWS CLI commands and a brief description of them. You can display more information about each command, including command format, usage, and options, by typing awshelp and the command name. Detailed help for each command can be displayed by typing the command name and the -h[elp] argument. Any CLI command name can be used as input to the command. This command is entered in one of the following formats: awshelp awshelp [-h[elp]] <command> awshelp <command> <command> -h[elp] DumpMemory This command invokes a memory dump on one or more nodes. Typically, you would perform this action only when instructed to do so by Teradata technical support personnel. A dump partition must be set up before performing this action. Command progress displays on the screen. Caution: This operation does not perform a graceful shutdown. There is a potential for data loss or corruption when performing this action. This command is entered in the following format: dumpmemory -h[elp] <components> DumpMemory Options The following table lists the options available for this command: Option Name Description -h [elp] Help Displays help for this command. components Component ID or Alias Unique Component ID, default alias, or user-defined alias of one or more nodes or SMPs. ShowComponents 282 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface FaultUtil FaultUtil This command provides a command line interface to view and manage faults. This command has the following functions, entered in the following formats: Displays help for the command at the command line. faultutil [-h -? -H] Lists faults with optional details and filters. faultutil -open -closed -all [-detail] [-severity x] [-instance x] [-probinstance] [-domain x] [-code x] [-start datetime -end datetime ] Lists fault details. faultutil -id <faultid> Performs operations on faults. faultutil -close <faultid> faultutil -closeall <comment text> faultutil -closeautosolved <comment text> faultutil -closeinstance instancename faultutil -closetype -domain problemdomain -code problemcode faultutil -closequery query faultutil -trackstatus <faultid> [-state x] [-user name] [-saveasrec] <comment text> faultutil -addtojournal <faultid> [-user name] [-saveasrec] <comment text> faultutil -addfault [-severity x] [-instance x] [-probinstance] [-domain x] [-code x] [-escalate] <description text> Performs operations on saved recommendations. faultutil -recadd -domain x -code x <recommendation text> faultutil -recs [-detail] [-domain x] [-code x] faultutil -recapp -domain x -code x <recommendation text> faultutil -recdel -domain x -code x faultutil -recdelall Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer FaultUtil Help Options FaultUtil Display Options FaultUtil Fault Detail Options FaultUtil Fault Operation Options FaultUtil Saved Recommendation Options Teradata AWS User Guide, Release 4.5 283

Appendix A: Teradata AWS Command Line Interface FaultUtil FaultUtil Help Options Option Name Description -h, -? Help Displays command usage. -H Help Displays detailed command syntax and help information. FaultUtil Display Options Option Name Description -open -closed -all Open, Closed, All Select open, closed, or all faults -detail Detail Displays complete fault details -severity x Severity Fault severity, where x can be: Unknown, OK, Information, Warning, Degraded, Critical or Fatal. -instance x SourceInstance The fault s SourceInstance property. -probinstance x ProblemSourceInstance The fault s ProblemSourceInstance property. -domain x ProblemDomain The fault s ProblemDomain property. -code x ProblemCode The fault s ProblemCode property. -start [mm/dd/[yy]yy] [hh:mm:ss] -end [mm/dd/[yy]yy] [hh:mm:ss] Start End -start is optional; when the -start option is used, a time or a date must be specified. Specifying a date displays faults from the specified date to the current date. If no date is specified, faults for the current date are returned. Specifying a time displays faults after that time on the current day. If you use -start without the -end option, all faults from the specified time or date to the current time or date display. -end is optional; when the -end option is used, a time or a date must be specified. Specifying a date displays faults preceding the specified date. If no date is specified, faults preceding the current date are returned. Specifying a time displays faults preceding that time. If you use -end without the -start option, all faults preceding the specified time or date display. Fault Properties 284 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface FaultUtil FaultUtil Fault Detail Options The following table lists options for retrieving fault details for this command when a Fault ID is specified: Option Name Description -id Details Lists all the fault details of the specified fault ID. FaultUtil Fault Operation Options The following table lists options for fault operations; some require a Fault ID: Option Name Description -close Close Closes the specified fault and moves the fault from the Open Fault List to the Closed Fault List. -closeall Close All CloseAll moves all open faults to the Closed Fault List. -closeautosolved Close Autosolved Closes all faults in the Open Fault List whose Resolution is AutoSolved. -closeinstance Close Instance Closes all faults in the Open Fault List with the specified ProblemSourceInstance or ProblemInstance name. -closetype Close Type Closes all faults in the Open Fault List with the specified ProblemDomain and ProblemCode -closequery Close Query Closes all faults in the Open Faul List that match the specified query <comment text> Comments Enter comments to be applied to each fault journal. -trackstatus Status Track the status of the specified fault. Either -state or <comment text> must be specified. -state x Resolution State The new ResolutionState, where x is UnderInvestigation ActionTaken Solved Unsolved -user name User Name The user name to log. -saveasrec Recommendation Save the comment as a recommendation for the fault s ProblemCode. -addtojournal Add to Journal Adds the comment to the fault s Journal. -addfault Add Fault Creates a new fault in the Open fault list. -severity x Severity The fault s severity, where x can be Unknown OK Information Warning Degraded Critical Fatal -instance x Source Instance The fault s SourceInstance property. In systems with legacy server management, the AWS ComponentID is stored here; for faults generated for the AWS, this contains the AWS name Teradata AWS User Guide, Release 4.5 285

Appendix A: Teradata AWS Command Line Interface FaultUtil Option Name Description -probinstance x Problem Instance The fault s ProblemSourceInstance (its object path to the managed element); for node log alerts, this is the node s object path; for node faults in systems with legacy server management, this contains the node Name and domain; for faults generated for the AWS, this contains the AWS name and domain. -domain x Problem Domain The fault s ProblemDomain property. -code x Problem Code The fault s ProblemCode property. -escalate Escalate When specified, -code is ignored and is set to User-Escalate. Fault Properties FaultUtil Saved Recommendation Options The following table lists options for saved recommendations operations: Option Name Description -recadd Add Recommended Solution Add recommended solution to be saved for inclusion in subsequent same faults by problem domain and problem code. -recs Recommendations Display saved recommendations. -detail Details Display details of saved recommendations. -domain x ProblemDomain Save or filter recommendations by fault ProblemDomain property.. -code x ProblemCode Save or filter recommendations by fault ProblemCode property. -recapp Append Append recommendation text to existing saved recommendation for the problem domain and problem code. <recommendation text> Recommendation Recommendation text. -recdel Delete Delete saved recommendations for a ProblemDomain and ProblemCode. -recdelall Delete All Delete all saved recommendations. Fault Properties 286 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface FWConfig FWConfig FWConfig Help Options This command configures the Windows Firewall to allow SSH, Remote AWS, and Remote Desktop (Terminal Services) access to the AWS. The AWS must be running Windows Server 2003 (SP1 or SP2), AWS 4.3.1 or later, with the Windows Firewall enabled. Note: If the site has both primary and secondary AWSs, and you want the Windows Firewall to allow access to both AWSs, you must run the command on both AWSs. You can use different options to configure each AWS. This command has the following functions that are entered in the following formats: Displays help for the command at the command line. FWConfig [-h -? -H] Configures the Windows Firewall. FWConfig [-allow -block][-ip -scopeall -local] x.x.x.x [- mask{optional} x.x.x.x -[ssh, rdp, remote, all] Utilities for listing open ports and applications, gathering information about installed adapters, and verifying a range of addresses. FWConfig -list FWConfig -showadptrs FWConfig -calcnetid -ip x.x.x.x -mask x.x.x.x FWConfig Help Options FWConfig Firewall Configuration Options FWConfig Utilities Option Name Description -h, -? help Displays command usage -H Help Displays detailed command usage, including configuration examples FWConfig Firewall Configuration Options The following table lists options for configuring to allow ports and applications access through the Windows Firewall when the firewall is enabled on the Teradata AWS: Option Name Description -allow Allow Configures the Windows Firewall to allow a remote IP address or a range of IP addresses to use one or more connection methods (SSH, Remote Desktop, the Remote AWS feature) to access the AWS Teradata AWS User Guide, Release 4.5 287

Appendix A: Teradata AWS Command Line Interface FWConfig Option Name Description -block Block Configures the Windows Firewall to block a remote IP address or a range of IP addresses from using one or more connection methods (SSH, Remote Desktop, the Remote AWS feature) to access the AWS -ip IP Address Specifies the target machine or range of machines that you want to give access to: To specify a target machine, use -ip and the machine s IP address (for example, -ip 10.1.0.12) To specify a range of machines, use -ip and -mask (for example, -ip 10.1.0.12 -mask 255.255.255.254. Note: You can use -calcnetid to verify that the range is correct. -scopeall Scope (all) Opens the specified ports or applications (SSH, Remote Desktop, Remote AWS feature) for the managed (Teradata AWS) IP address in the Windows Firewall to any IP address from anywhere -local Local subnet Cpens ports or applications (SSH, Remote Desktop, Remote AWS feature) for the managed (Teradata AWS) IP address in the Windows Firewall to any IP address from local subnets -mask Subnet Mask Allows you to specify a subnet mask for a range of machines; required only with the network ID (-ip x.x.x.x -mask x.x.x.x), optional in other cases -ssh Secure Shell Allows or blocks access to Secure Shell (SSH) -rdp Remote Desktop Allows or blocks access to the Remote Desktop service (Terminal Services) -remote Remote AWS Allows or blocks access to the AWS s Remote AWS feature -all SSH, Remote Desktop, Remote AWS Allows or blocks access to Secure Shell (SSH), Remote Desktop (Terminal Services), and the AWS s Remote AWS feature FWConfig Utilities Option Name Description -list List Lists all ports and applications open in the Windows Firewall that have been configured with FWConfig, the Windows Firewall in the Control Panel, and Microsoft COM APIs -showadptrs Show Adapters Displays all the LAN adapters (excluding modem) installed on the Teradata AWS; displays basic information for each adapter, including its name, a description, its IP address, its subnet mask, and whether Windows Firewall is enabled or disabled -calcnetid Calculate Network ID Uses the IP address and subnet mask to calculate the network ID; verifies that the range of IP addresses that you plan to configure is valid; if the range is invalid, the correct range displays. 288 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface MeasurementInfo MeasurementInfo This command allows you to display, or output to a file, measurement information for specific chassis or for all chassis contained in a system, collective, or cabinet. The command is entered in the following format: measurementinfo [-h[elp]] [-f[ile] outputfile -c[sv]] <components> MeasurementInfo Options MeasurementInfo Options Option Name Description -h [elp] Help Displays help for this command. -f [ile] outputfile Filename Specifies the name of the file to ouput the chassis measurement information. If the full path is not specified, the file is stored in the \Documents and Settings\<username>\AWS\UserData directory. If this option is not used, the information is output to the screen. -c[sv] CSV Saves the measurement information in CSV (comma separated value) format to the specified outputfile. The information can then be viewed with spreadsheet software. If this option is not used, the measurement information is saved to a text file that can be viewed with an ASCII text editor. components Component ID or Alias Unique ID of the system, collective, cabinet, or chassis whose measurement information you want to see or save to a file. The unique ID can be a Component ID, default alias, or user-defined alias. ShowComponents MLANTest In systems with legacy server management, this command tests the functionality of the server management MLAN connections. The command is entered in the following format: mlantest -h[elp] <components> MLANTest Options Teradata AWS User Guide, Release 4.5 289

Appendix A: Teradata AWS Command Line Interface ReadSCSI MLANTest Options Option Name Description -h [elp] Help Displays help for this command. components Component ID or Alias Unique Component ID, default alias, or user-defined alias of a legacy SMC that contains a CMIC. ShowComponents ReadSCSI ReadSCSI Options This command allows you to display, or output to a file, SCSI information for specific legacy nodes or for all legacy nodes in a system, collective, or cabinet. The syntax for the command is: readscsi -h[elp] [-f[ile] outputfile] <components> Option Name Description -h [elp] Help Displays help for this command. -f [ile] outputfile Filename Specifies the name of the file to which the SCSI information will be output. If the full path is not specified, the file is stored in the \Documents and Settings\<username>\AWS\UserData directory. If this option is not used, the information is output to the screen. components Component ID or Alias Unique ID of legacy nodes, or the system, collectives, or cabinets containing legacy nodes, whose SCSI information you want to see or save to a file. ShowComponents 290 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface RemComponent RemComponent In systems with legacy server management, this command removes a legacy component from the internal AWS database of managed legacy components. It is used to remove components that no longer exist in the system. Removal of components that still exist and are communicating with the AWS is not allowed. Note: This is a rarely performed operation and usually is not permitted. This command is entered in the following format: remcomponent -h[elp] <components> RemComponent Options RemComponent Options Option Name Description -h [elp] Help Displays help for this command. components Component ID or Alias Unique ID of the component or components you want to remove. The unique ID can be a Component ID, default alias, or user-defined alias. ShowComponents Rescan In systems with legacy server management, this command forces a rediscovery of components in the legacy collective (Collective 0). It can be used when the GUI does not accurately reflect the hardware configuration. If changes have occurred, all running instances of the AWS GUI are notified. There is no direct effect unless a GUI is running and the AWS database is out of synchronization with the actual configuration. Note: It is rarely necessary to perform this operation because new hardware is discovered automatically. This command in entered in the following format: rescan -h[elp] There are no other options available for this command. Teradata AWS User Guide, Release 4.5 291

Appendix A: Teradata AWS Command Line Interface Reset Reset Reset Options This command resets one or more components. This command is entered in the following format: reset -h[elp] <components> Reset Options Option Name Description -h [elp] Help Displays help for this command. components Component ID or Alias Unique ID of the component or components you want to reset. The unique ID can be a Component ID, default alias, or user-defined alias. ShowComponents SetBatteryDate This command sets the battery installation date for all batteries in the system, or for one or more batteries specified by the components option. This command in entered in the following formats: setbatterydate -h[elp] setbatterydate -d[ate] <installdate> <components> setbatterydate -d[ate] <installdate> -a[ll] SetBatteryDate Options SetBatteryDate Options Option Name Description -h [elp] Help Displays help for this command. 292 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface SetFW Option Name Description -d [ate] <MM/dd/yyyy> Installation Date The date the battery was installed. Entering one or more components after the installation date applies the date to the specified components. The components option specifies the unique ID of the battery. The unique ID can be a Component ID, default alias, or user-defined alias. Entering -all after the installation date applies the date to all batteries in the system. ShowComponents SetFW This command downloads firmware for managed components that support this function (for example, CMIC and management boards). For systems with SM3G, this command is entered in the following format: setfw -h[elp] -b[ypass]] <components> In systems with legacy server management, this command in entered in the following format: setfw -h[elp] [-c[oproc] -f[ile] <ImageFile> -b[ypass]] <components> Firmware Images for Systems with Legacy Server Management SetFW Options Firmware Images for Systems with Legacy Server Management The SM3G Legacy SLAN package installs the legacy firmware image files in the following directory on the AWS: Program Files\SM3G Legacy SLAN\AWSFirmware The SetFW CLI program and the Functions > Flash Firmware and Legacy Support > Flash CoProcessor Firmware GUI commands automatically download the latest firmware image from the AWSFirmware directory. The AWSFirmware directory and all its subdirectories are controlled directories. If you need to download a firmware image from a different directory, you must download it to a controlled directory and use the -f option with SetFW. Note: The Service Subsystem Service Guide for your system lists the file names of the firmware images for each management board. Teradata AWS User Guide, Release 4.5 293

Appendix A: Teradata AWS Command Line Interface SetPower SetFW Options Option Name Description -h [elp] Help Displays help for this command. -f [ile] <ImageFile> Image file name Allows a firmware image file to be specified for components in systems with legacy server management. The filename is any valid firmware image file name. The firmware must be downloaded from a controlled directory that contains firmware image files. Note: This option is not valid for components in systems with SM3G server management. -c[oproc] Co-processor For components that have a co-processor, flashes the co-processor firmware rather than the main firmware. -b[ypass] components Bypass power check Component ID or Alias When flashing a UPS management board (MB) or adapter card, the cabinet s power subsystem is checked. If a problem is found, a warning message displays. To bypass the power check and flash the UPS management board or adapter card anyway, you must run the SetFW command again using the -b option. Note: It is recommended that you correct the condition before flashing the UPS MB or adapter card. Unique ID of the component or components you want to flash. The unique ID can be a Component ID, default alias, or user-defined alias. Note: Before flashing the firmware of an APC UPS, you must first flash the firmware of both APC UPS adapter cards. Firmware Images for Systems with Legacy Server Management ShowComponents SetPower This command powers one or more components on (the default) or off, for managed components that support this. This command is entered in the following format: setpower [-h[elp]] -on -off -1-0 [-b[ypass]] <components> SetPower Options Managing System Power 294 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface ShowBatteries SetPower Options Option Name Description -h [elp] Help Displays help for this command. -on or -1 Power on Powers on the managed component. -off or-0 Power off Powers off the managed component. -b[ypass] components Bypass power check Component ID or Alias When powering on a cabinet or a system, the cabinet s power subsystem is checked. If a problem is found, a warning message displays. To bypass the power check and power on the cabinet or system, you must run the SetPower command again using the -b option. Note: This option does not apply to (legacy) cabinets in Collective 0. Unique ID of the component or components you want to power on or off. The unique ID can be a Component ID, default alias, or user-defined alias. ShowComponents ShowBatteries This command displays battery installation and battery replacement dates or outputs them to a file. This command is entered in the following format: showbatteries [-h[elp]] [-f [ile] outputfile [-c[sv]]] ShowBatteries Options ShowBatteries Options Option Name Description -h [elp] Help Displays help for this command. -f [ile] outputfile Filename Specifies the name of the file to which the battery information will be output. If the full path is not specified, the file is stored in the \Documents and Settings\<username>\AWS\UserData directory. If this option is not used, the information is output to the screen. -c[sv] CSV Using this option saves the battery information in a CSV (comma separated values) file format that can be viewed with spreadsheet software. If this option is not used, the battery information is saved to a text file that can be viewed with an ASCII text editor. Teradata AWS User Guide, Release 4.5 295

Appendix A: Teradata AWS Command Line Interface ShowComponents ShowComponents This command displays the managed components and their operational status. This command is entered in the following format: showcomponents [-h[elp]] -r[ecursive] -c[hildren] -n[ame] -i[d] -a[lias] [-f[ile] outputfile] [components] ShowComponents Options ShowComponents Options Option Name Description -h [elp] Help Displays help for this command -r[ecursive] Recursive Shows the operational status of all components contained under the component -c[hildren] Children Shows the operational status of the component and only its immediate subcomponents -n[ame] Element Name Displays the components by the default name displayed in the Tree View -i[d] Component ID Displays the components by their Component IDs; this is the default display option if neither -n, -i, or -a is specified -a[alias] Alias Displays the components by their aliases; if a user-defined alias exists, it displays instead of the default alias -f[ile] outputfile File Specifies the name of the file to which the component information will be output. If the full path is not specified, the file is stored in the \Documents and Settings\<username>\AWS\UserData directory. If this option is not used, the information is output to the screen. components Component ID or Alias Unique ID of the component or components. The unique ID can be a Component ID, default alias, or user-defined alias. If no Component IDs or aliases are specified, the system components are the default. ShowProperties ShowFirmwareVersion This command displays or outputs to a file all firmware instances in the system, the installed firmware version for each component, the supported firmware version for each component, and reports whether there is a mismatch between the installed firmware version and the supported firmware version: OK: The firmware version installed is the currently supported version. 296 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface ShowProperties Mismatch: The firmware version installed is not the currently supported version. Unknown: The firmware version information is missing or unavailable. This command is entered in the following format: showfirmwareversion [-h[elp]] [-a[lias]] [-f[ile] <outputfile> [-c[sv]] Checking Firmware Versions ShowFirmwareVersion Options ShowFirmwareVersion Options Option -h[elp] Output Displays detailed help for this command. -a [lias] Displays or saves output using the component alias instead of the Component ID -f[ile] outputfile -c[sv] Specifies the name of the file to which the firmware version information will be output. If the full path is not specified, the file is stored in the \Documents and Settings\<username>\AWS\UserData directory. If this option is not used, the information is output to the screen. Saves the firmware version details in a CSV (comma separated values) file format that can be viewed with spreadsheet software. If this option is not used, the information is saved to a text file that can be viewed with an ASCII text editor. ShowProperties This command displays component properties. This command is entered in the following format: showproperties [-h[elp]] [-f [ile] outputfile] <components> ShowProperties Options ShowProperties Options Option Name Description -h [elp] Help Displays help for this command. -f[ile] outputfile File Specifies the name of the file to which the property information will be output. If the full path is not specified, the file is stored in the \Documents and Settings\<username>\AWS\UserData directory. If this option is not used, the information is output to the screen. Teradata AWS User Guide, Release 4.5 297

Appendix A: Teradata AWS Command Line Interface UpdateStatus Option Name Description components Component ID or Alias The unique Component IDs, default aliases, or user-defined aliases of the components. ShowComponents UpdateStatus This command updates the operational status of components in a system with legacy server management. Use this command when the operational status of a component does not seem correct. You can run the command on a system, collective, cabinet, or chassis the command updates the operational status of the selected components, and all the components beneath them. This command is entered in the following format: updatestatus -h[elp] <components> UpdateStatus Options UpdateStatus Options The following table lists the options available for this command: Option Name Description -h [elp] Help Displays help for this command. components Component ID or Alias Unique ID of the system, collective, cabinet, or chassis. The unique ID can be a Component ID, default alias, or user-defined alias. ShowComponents 298 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface UPSTest UPSTest This command tests the functionality of either the UPS s internal components or the UPS Input Selector. The command is entered in the following format: upstest [-h[elp]] -s[elf] -i[nput] <components> UPSTest Options UPSTest Options The following table lists the options available for this command. Only one option can be used at a time. Option Name Description -h [elp] Help Displays help for this command. -i [nput] UPS Input Selector Test Runs the UPS Input Selector Test and outputs the results to the screen; the test forces a switch from the default power source to the alternate power source to verify that the switch-over capability is functional. When the test is complete, the system switches power back to the default power source. The system does not switch to the alternate power source if the alternate power source is not operating normally. The command runs only if all other power related components in the cabinet appear OK. -s [elf] UPS Self Test Runs the UPS Self-Test and outputs results to the screen. If no option is specified, the UPS Self-Test is run. components Component ID or Alias Unique ID of the UPS you want to test. The unique ID can be a Component ID, default alias, or user-defined alias. ShowComponents Teradata AWS User Guide, Release 4.5 299

Appendix A: Teradata AWS Command Line Interface ViewAssetHistory ViewAssetHistory ViewAssetHistory Options This command displays asset records retrieved from the Asset Database. This command can be entered in the following format. viewassethistory -h[elp] [components] [timeoptions] [displayoptions] [filteroptions] ViewAssetHistory Options ViewAssetHistory Time Options ViewAssetHistory Display Options ViewAssetHistory Filter Options ViewAssetHistory Examples Option Name Description -h[elp] Help Displays help for this command. components Component ID or Alias Unique ID of the component or components whose records you want to display. The unique ID can be a Component ID, default alias, or userdefined alias. If no Component IDs or aliases are specified, records for the system display. ShowComponents ViewAssetHistory Time Options Option Name Description -start [mm/dd/yyyy] [hh:mm:ss] Start Select start date or time. Default is current date or time 0. -end [mm/dd/yyyy] [hh:mm:ss] End Select end date or time. Default is current date or time 23:59:59. 300 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface ViewAssetHistory Option Name Description -sec -min -hrs -days x Time Select events x seconds, minutes, hours, or days since the start time or before the end time; if -start or -end is not specified, the default is since current time. For example: -start 10/02/2001 -days 2 Means display 2 days of events, starting Oct 2 00:00:00 and ending 2 days later, on Oct 3 23:59:59. -end 10/15/2001 -days 4 Means display 4 days of events, starting on 10/11/2001 00:00:00 and ending on 10/15/2001 23:59:59. -days 4 Means display events starting 4 days earlier up to current time. -desc -asc Sort order Specify sort order. Default is descending create time (newest first). Use ascending to sort by create time (oldest first). -all All Display all records in the system. Caution: Operation could be lengthy depending on the size of the system. Note: If -all or -max is not specified, the default is 1000 records. -max x Maximum Specify maximum number of records to retrieve. Note: If -all or -max is not specified, the default is 1000 records. ViewAssetHistory Display Options Option Name Description -nohdr No header Suppress display of format header. -formnamevalue Name Display in AttributeName=Value format. -perform Statistics Display statistics such as elapsed time and number of records. -byalias -csv Display output using the component alias instead of the ObjectPath. If a user-defined alias has been configured, it displays. Display asset information in CSV (comma separated values) format enabling users to view this information in their spreadsheet software. ViewAssetHistory Filter Options Option -type=chassistype[,...] -model=modelname[,...] Description Select records with the specified chassis type(s). Select records with the specified model name(s). Teradata AWS User Guide, Release 4.5 301

Appendix A: Teradata AWS Command Line Interface ViewAssetHistory Option -assetnames=assetname[,...] -propunit=propertyunit[,...] -propname=propertyname[,...] -propvalue=propertyvalue[,...] -objectclass=objectclassname[,...] -systemid=systemidnumber[,...] -collectiveid=collectiveidnumber[,...] -cabinetid=cabinetidnumber[,...] -chassisid=chassisidnumber[,...] Description Select records with the specified asset name(s). Select records with matching property unit(s). Select records with matching property name(s) Select records with matching property value(s) Select records associated with the object class name(s). To determine the class name, look at the first part of the component ID. Example: If the component ID is CMIC_5400J.SystemID=1,CollectiveID=400,CabinetID=1,ID=6, the class name is CMIC_5400J. Select records associated with the system ID number(s). If you identify multiple system ID numbers, you cannot specify collective ID(s), cabinet ID(s), or chassis ID(s). Select records associated with the collective ID number(s). If you identify multiple collective ID numbers, you cannot specify cabinet ID(s) or chassis ID(s). Select records associated with the cabinet ID number(s). If you identify multiple cabinet ID numbers, you cannot specify chassis ID(s). Select events associated with the chassis ID number(s). ViewAssetHistory Examples To list all asset records in the system: viewassethistory -all To list asset records for all records logged on 8/19/2000: viewassethistory -start 8/19/2000 -days 1 To list asset records where property unit value is volts and chassis type is cmic: viewassethistory -propunit=volts -type=cmic To list asset records where system ID is 1, cabinet ID is 300, and chassis ID type is either 203 or 204: viewassethistory -sys=1 -cab=300 -chas=203,204 302 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface ViewEvents ViewEvents ViewEvents Options This command captures a particular time frame of events, retrieves them from the Consolidated Event Log, and displays them to the screen. To redirect the command output to a text file, type the following after the command: > myout.txt. The output file can then be viewed, searched, or printed using the Windows Notepad or other text editor. System problem events can be captured and then forwarded to Customer Services for further analysis. This command can be entered in the following formats: viewevents -h[elp] [components] [timeoptions] [displayoptions] [filteroptions] viewevents -monitor [components] [monitoroptions] [filteroptions] viewevents -id {eventguid} [-timesequence sequencenumber] ViewEvents Options ViewEvents Time Options ViewEvents Display Options ViewEvents Filter Options ViewEvents Monitor Options ViewEvents Examples Option Name Description -h[elp] Help Displays help for this command. -id {eventguid} components Component ID or Alias Displays event details for the event specified by {eventguid}; using the timesequence option speeds up event retrieval Unique ID that identifies an event Unique ID of the component or components whose events you want to display. The unique ID can be a Component ID, default alias, or userdefined alias. If no Component IDs or aliases are specified, events for the system display. ShowComponents Teradata AWS User Guide, Release 4.5 303

Appendix A: Teradata AWS Command Line Interface ViewEvents ViewEvents Time Options Option Name Description -start [mm/dd/yyyy] [hh:mm:ss] Start Select start date or time. Default is current date or time 0. -end [mm/dd/yyyy] [hh:mm:ss] End Select end date or time. Default is current date or time 23:59:59. -sec -min -hrs -days x Time Select events x seconds, minutes, hours, or days since the start time or before the end time; if -start or -end is not specified, the default is since current time. For example: -start 10/02/2001 -days 2 Means display 2 days of events, starting Oct 2 00:00:00 and ending 2 days later, on Oct 3 23:59:59. -end 10/15/2001 -days 4 Means display 4 days of events, starting on 10/11/2001 00:00:00 and ending on 10/15/2001 23:59:59. -days 4 Means display events starting 4 days earlier up to current time. -desc -asc Sort order Specify sort order. Default is descending time (newest first). Ascending time is oldest first. -all All Display all events in the system. Caution: Operation could be lengthy depending on the size of the system. Note: If -all or -max is not specified, the default is 1000 events. -max x Maximum Specify maximum number of events to retrieve. Note: If -all or -max is not specified, the default is 1000 events. -timesequence <sequencenumber> Sequence Adding the time sequence number speeds up event retrieval ViewEvents Display Options Option Name Description -detail Detail Display detailed event data. -nohdr No header Suppress display of format header. -formnamevalue Name Display in AttributeName=Value format. -perform Statistics Display statistics such as elapsed time and number of records. -byalias Alias Display output using the component alias instead of the ObjectPath. If a user-defined alias has been configured, it displays. -csv CSV Display measurement information in CSV (comma separated values) format enabling users to view this information in their spreadsheet software. 304 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface ViewEvents ViewEvents Filter Options Option Name Description -reportertype={mpp_statusevent MPP_ConfigChangeEvent MPP_CommandEvent MPP_SnmpTrap MPP_BynetDPEvent MPP_UNIXLog MPP_WinLog MPP_ApplicationEvent MPP_Alert} [,.] Reporter type Select reporter event types. -subtype=subtypename[,...] Subtype Select events with the specified subtype name(s). -domain=domainname Domain name Select events associated with domain names. -severity={unknown OK Info Warning Degraded Critical Fatal x-y} [,.] Severity name or range Select the first letter of one or more severity names or a range, x to y, between 0 and 6. -msgid=msgid[,.] Message ID Select one or more events with matching MessageIDs. -objectclass=objectclassname [,.] Object Class Select one or more events associated with objectclassname(s). -systemid=systemidname [,.] System ID Select one or more events associated with systemidname(s). * -collectiveid=collectiveidname [,.] Collective ID Select one or more events associated with collectiveid(s). * -cabinetid=cabinetidname [,.] Cabinet ID Select one or more events associated with cabinetidname(s). * -chassisid=chassisidname Chassis ID Select events associated with chassisidname(s). * * Note: If a system, collective, cabinet, or chassis has more than one component, you cannot specify any further granularity. For example, ViewEvents -sys=1 -coll=200 -cab=1,2,3 is valid, ViewEvents -sys=1 -coll=200, 300 is valid, but ViewEvents -sys=1 - coll=200,300 -cab=1 is not valid. ViewEvents Monitor Options Option -monitor -refreshrate x Description Monitors the database for new events and displays them. The following options are not supported: -start, -end, -sec, -min, -hrs, -days, -active, -desc, -asc, -seq, -detail, -perform, and -id. To exit the command, enter ctrl+c. Refresh rate in seconds; use with -monitor; the default is 10 seconds; the minimum is 5 seconds. ViewEvents Examples To list all events in a system: viewevents To show event details for all events logged on 8/19/2000: viewevents -start 8/19/2000 -days 1 -detail Teradata AWS User Guide, Release 4.5 305

Appendix A: Teradata AWS Command Line Interface ViewMeasurementHistory To show event details for a specific event with a matching event ID: viewevents -id {175CC646-8CC3-11d3-84FD-00E029103BC7} To list any Windows log from NCRBYNET with a severity of Warning or Degraded: viewevents -rep=mpp_winlog -dom=ncrbynet -sev=w,d To list events where systetmid=1 or systemid=2, cabinetid=300, and chassisid=203 or chassisid=204: viewevents -sys=1 -cab=300 -chas=203,204 ViewMeasurementHistory This command displays measurement records retrieved from the CMIC Measurement Database. This command can be entered in the following format. viewmeasurementhistory -h[elp] [components][timeoptions][displayoptions][filteroptions] ViewMeasurementHistory Options ViewMeasurementHistory Time Options ViewMeasurementHistory Display Options ViewMeasurementHistory Filter Options ViewMeasurementHistory Examples ViewMeasurementHistory Options Option Name Description -h[elp] Help Displays help for this command. components Component ID or Alias Unique ID of the component or components whose history records you want to display. The unique ID can be a Component ID, default alias, or user-defined alias. If no Component IDs or aliases are specified, records for the system display. ShowComponents ViewMeasurementHistory Time Options Option Name Description -start [mm/dd/yyyy] [hh:mm:ss] Start Select start date or time. Default is current date or time 0. -end [mm/dd/yyyy] [hh:mm:ss] End Select end date or time. Default is current date or time 23:59:59. 306 Teradata AWS User Guide, Release 4.5

Appendix A: Teradata AWS Command Line Interface ViewMeasurementHistory Option Name Description -sec -min -hrs -days x Time Select events x seconds, minutes, hours, or days since the start time or before the end time; if -start or -end is not specified, the default is since current time. For example: -start 10/02/2001 -days 2 Means display 2 days of events, starting Oct 2 00:00:00 and ending 2 days later, on Oct 3 23:59:59. -end 10/15/2001 -days 4 Means display 4 days of events, starting on 10/11/2001 00:00:00 and ending on 10/15/2001 23:59:59. -days 4 Means display events starting 4 days earlier up to current time. -desc -asc Sort order Specify sort order. Default is descending create time (newest first). Use ascending to sort by create time (oldest first). -all All Display all events in the system. Caution: Operation could be lengthy depending on the size of the system. Note: If -all or -max is not specified, the default is 1000 records. -max x Maximum Specify maximum number of events to retrieve. Note: If -all or -max is not specified, the default is 1000 records. ViewMeasurementHistory Display Options Option Name Description -nohdr No header Suppress display of format header. -formnamevalue Name Display in AttributeName=Value format. -perform Statistics Display statistics such as elapsed time and number of records. -byalias Alias Display output using the component alias instead of the ObjectPath. If a user-defined alias has been configured, it displays. -csv CSV Display measurement information in CSV (comma separated values) format enabling users to view this information in their spreadsheet software. ViewMeasurementHistory Filter Options Option -type=chassistype[,...] -propunit=propertyunit[,...] Description Select records with the specified chassis type(s). Select records with matching property unit(s). Teradata AWS User Guide, Release 4.5 307

Appendix A: Teradata AWS Command Line Interface ViewMeasurementHistory Option -propname=propertyname[,...] -propvalue=propertyvalue[,...] -objectclass=objectclassname[,...] -systemid=systemidnumber[,...] -collectiveid=collectiveidnumber[,...] -cabinetid=cabinetidnumber[,...] -chassisid=chassisidnumber[,...] Description Select records with matching property name(s) Select records with matching property value(s) Select records associated with the object class name(s). To determine the class name, look at the first part of the component ID. Example: If the component ID is CMIC_5400J.SystemID=1,CollectiveID=400,CabinetID=1,ID=6, the class name is CMIC_5400J. Select records associated with the system ID number(s). If you identify multiple system ID numbers, you cannot specify collective ID(s), cabinet ID(s), or chassis ID(s). Select records associated with the collective ID number(s). If you identify multiple collective ID numbers, you cannot specify cabinet ID(s) or chassis ID(s). Select records associated with the cabinet ID number(s). If you identify multiple cabinet ID numbers, you cannot specify chassis ID(s). Select events associated with the chassis ID number(s). ViewMeasurementHistory Examples To list all measurement records in the system: viewmeasurementhistory -all To list measurement records for all records logged on 8/19/2000: viewmeasurementhistory -start 8/19/2000 -days 1 To list measurement records where property unit value is volts and chassis type is cmic: viewmeasurementhistory -propunit=volts -type=cmic To list measurement records where system ID is 1, cabinet ID is 300, and chassis ID type is either 203 or 204: viewmeasurementhistory -sys=1 -cab=300 -chas=203,204 308 Teradata AWS User Guide, Release 4.5

APPENDIX B Configuring the System You may need to update system information as your system configuration changes. Configuring the CheckBatteries and CheckFirmwareVersion Utilities Changing System and Cabinet Numbers Adding Components Removing Components Configuring SCSI Adapters on 48xx/52xx and 49xx/53xx Nodes Changing Server Management IP Addresses AWS IP Configuration Utility Configuring Permissions for Members of AWS Guests Configuring the System Objects Server in Systems with Legacy Server Management Time Synchronization in Teradata Systems Configuring Alerts Managing the AWS Databases Configuring the CheckBatteries and CheckFirmwareVersion Utilities During the installation, a CheckBatteries utility and a CheckFirmwareVersion utility are added to the AWS s Start > Settings > Control Panel > Scheduled Tasks menu. Each utility must be enabled before it can be run. If enabled, each utility is scheduled to run by default once a week on Monday at 8 am, starting from the day the utility is enabled. AWS Users or Administrators can change or remove the scheduling of each utility. Access privileges are determined at log on. User Groups Teradata AWS User Guide, Release 4.5 309

Appendix B: Configuring the System Configuring the CheckBatteries and CheckFirmwareVersion Utilities To Enable or Disable the CheckBatteries or CheckFirmware Version Utility 1 On the AWS desktop, do one of the following: Select Start > Settings > Control Panel, select Scheduled Tasks, then select CheckBatteries. The CheckBatteries dialog box displays. Select Start > Settings > Control Panel, select Scheduled Tasks, then select CheckFirmwareVersion. The CheckFirmwareVersion dialog box displays. 2 To enable the utility, on the Task tab, click Enabled (scheduled task runs at specified time). Note: Click Apply or OK. Figure 85: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Task Tab Table 84: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Task Tab Description Option Run Start in Comments Description This field displays the name of the executable for the utility and the directory the executable is located in. This field displays the start directory of the utility. This field contains the default description of the utility. 310 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Configuring the CheckBatteries and CheckFirmwareVersion Utilities Table 84: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Task Tab Description (continued) Option Run as Enabled (scheduled task runs at specified time) Description This field runs the utility under a specific user s account; the user must be an AWS User or Administrator. To set a password for running the utility under that user s account, click the Set Password button and use the Set Password dialog box. When this option is checked, the utility runs at the time specified on the Task tab; when unchecked, the utility does not run. To Change the Time Interval for the CheckBatteries or CheckFirmwareVersion Utility 1 On the AWS desktop, do one of the following: Select Start > Settings > Control Panel, select Scheduled Tasks, then select CheckBatteries. The CheckBatteries dialog box displays. Select Start > Settings > Control Panel, select Scheduled Tasks, then select CheckFirmwareVersion. The CheckFirmwareVersion dialog box displays. 2 On the displayed dialog box, use the Schedule tab to change the utility s time interval, day, and start time. Note: Click Apply or OK. Figure 86: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Schedule Tab Teradata AWS User Guide, Release 4.5 311

Appendix B: Configuring the System Configuring the CheckBatteries and CheckFirmwareVersion Utilities Table 85: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Schedule Tab Description Option Schedule Task Start Time Advanced button Schedule Task <option> Show multiple schedules Description This option sets the time interval at which the utility runs. The information in the Schedule Task area changes depending upon the option you select. The options are: Daily specifies the run interval by number of days. Weekly specifies the run interval by number weeks and day of week. Monthly specifies the run interval by the calendar day of a month or by the first, second, third, fourth or last day of a month; use the Select Month button to set which months you want the utility to run. Once displays a calendar to select the month and day to run the utility. At System Startup runs the utility when the AWS boots. At Logon runs the utility when someone logs on to the AWS. When Idle specifies the run interval by the number of minutes the AWS is idle. This option sets the time the utility runs. This button displays the Advanced Schedule Options dialog box to set a Start Date and End Date for the specified interval, and to set options for repeating the task for a specific interval. The options displayed in this area schedule the specific number of times the utility runs at the interval specified in the Schedule Task list box. This field changes depending upon the option you select from the Schedule Task list. This option sets multiple schedules for running the utility. When you select this option, the following field and buttons display at the top of the Schedule tab. The run interval that is currently set displays in the list box. To set up several run intervals, do the following: 1 Select another option from the Schedule Task list box and set the run interval. 2 Click New. 3 Repeat steps 1 and 2 for each run interval you want to use. To delete a run interval, select the run interval from the list, then click Delete. 312 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Changing System and Cabinet Numbers Changing System and Cabinet Numbers System and cabinet numbers are assigned at the factory during the staging process. As your MPP system configuration changes (for example, if you join two systems, or add or remove cabinets), Customer Services personnel may need to change a system number or cabinet number. Changing a System or Cabinet Number in Systems with SM3G Changing a system or cabinet number in systems with SM3G is covered in the platform Hardware Service Guide. Changing a System or Cabinet Number in Systems with Legacy Server Management In a system with legacy server management, the system number must be changed for each cabinet in the system, one cabinet at a time. A system number must always be unique, and only one system is currently supported. A cabinet number must be a unique number, and cabinets must be renumbered one cabinet at a time. System, Collective, Cabinet, and Chassis Numbering To Change a System or Cabinet Number in a System with Legacy Server Management The procedure for changing system and cabinet numbers cannot be performed remotely the Bootp dialog box displays locally on the AWS. Note: The following procedure does not include changing primary server management network IP addresses for CMICs, BYNET chassis, disk array controllers, or SMP nodes. 1 Label and unplug the power cables from the cabinet s SMC chassis. Note: At the Teradata AWS, highlight the cabinet and select Configuration > Remove Component. The cabinet s configuration data is deleted, and the cabinet is deleted from the Tree View. 2 Plug the power cables back into the SMC chassis outlets from which you removed them. 3 When the CMIC in the SMC chassis boots, use the displayed CMIC Bootp Request dialog box to configure the cabinet with the new system or cabinet number, then click OK. The fields should be completed as follows: CMIC Name: The host name of the CMIC. IP Address: The SLAN IP address for the CMIC. Teradata AWS User Guide, Release 4.5 313

Appendix B: Configuring the System Adding Components Hardware Address: The CMIC s unique MAC hardware address. System Number: The system number of the CMIC. Cabinet Number: The cabinet number of the CMIC. 4 Reboot the CMIC by doing the following: a b c Unplug the power cables from the SMC chassis again. Wait 5 seconds for the power to cycle. Plug the power cables back into the SMC chassis. When the CMIC reboots, you are not prompted for new values (the CMIC Bootp Request dialog box does not display). The Tree View is updated with the new cabinet configuration. Adding Components Adding Components to Systems with SM3G Adding components to systems with SM3G is covered in the platform Hardware Service Guide for your system. Adding Components to Systems with Legacy Server Management Accessing the BYNET Utility Configuring SCSI Adapters on 48xx/52xx and 49xx/53xx Nodes To Add a Processing Node Cabinet to a System with Legacy Server Management 1 Physically connect all the cables, including power cables. 2 Connect the cabinet to site power. 3 At the Teradata AWS, complete the CMIC Bootp Request dialog box, filling in the configuration fields for the CMIC IP address, the cabinet number, and the system number. 4 Click OK to add the cabinet to the legacy configuration database. The cabinet then displays in the Tree View. To Add a Teradata Disk Array Cabinet to a System with Legacy Server Management 1 Physically connect all the cables, including power cables. 2 Connect the cabinet to site power. 314 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Removing Components 3 At the Teradata AWS, the SMC Bootp Request dialog box displays. It already contains the IP address of the controlling CMIC. Fill in the configuration fields for the cabinet number, and the system number. 4 Click OK to add the cabinet to the legacy configuration database. The cabinet then displays in the Tree View. To Add a BYNET Cabinet to a System with Legacy Server Management 1 Make sure the power cables are unplugged from the BYNET chassis. 2 Physically connect all the other cables, including power cables. 3 Connect the cabinet to site power. 4 At the Teradata AWS, complete the CMIC Bootp Request dialog box, filling in the configuration fields for the CMIC IP address, the cabinet number, and the system number. 5 Click OK to add the cabinet to the legacy configuration database. The cabinet then displays in the Tree View. 6 Plug the power cords into the BYNET chassis. 7 The BYNET Bootp Request dialog box displays. Configure the BYNET IP address. 8 Use the BYNET Utility to reset and reconfigure the BYNET network. To Add Chassis to Cabinets in System with Legacy Server Management 1 Add the chassis according to the Hardware Service Guide for your system. The CMIC and AWS automatically discover the chassis when they are cabled to the primary server management network and powered on. 2 If you are adding an SMP node, configure it and restart the Teradata database. Removing Components The AWS does not allow you to delete components that are communicating with the AWS over the server management network. If you attempt to remove a component that is still communicating with the AWS over the server management network, an error message displays. Removing Components from Systems with SM3G In systems with SM3G, the Configuration > Remove Component command deletes the component from the Tree View. To delete the component from the system configuration, you must use the CMIC Configuration Utility. For details, see the platform Hardware Service Guide for your system. Teradata AWS User Guide, Release 4.5 315

Appendix B: Configuring the System Configuring SCSI Adapters on 48xx/52xx and 49xx/53xx Nodes Removing Components from Systems with Legacy Server Management In systems with legacy server management, the Configuration > Remove Component command deletes the component configuration data and deletes the component from the Tree View. To Delete or Remove a Component from a System with Legacy Server Management 1 Remove the cabinet or chassis from the server management network by unplugging its communication cables. 2 Select the component in the Tree View. 3 Select Configuration > Remove Component. A dialog box asks you to confirm the deletion. Note: Click Yes to delete the component. After the command finishes, the AWS updates the Tree View and displays a dialog box confirming the command completion. Configuring SCSI Adapters on 48xx/52xx and 49xx/53xx Nodes Although shared SCSI buses are configured during the initial set up of the system, you may need to set SCSI IDs if nodes or adapters are added to your system. The Legacy Support > Set SCSI IDs command allows you to configure the shared SCSI buses for one or more SCSI adapters on 48xx/52xx and 49xx/53xx nodes. After you install a SCSI adapter and complete the SCSI adapter s configuration, you must reboot the node for the changes to take effect. You can also use the Legacy Support > Set SCSI IDs command to edit the configuration of one or more SCSI adapters installed in SMP nodes, or remove SCSI adapters. Note: If your MPP system has Fibre Channel adapters, there are no SCSI adapters to configure. SCSI ID Editor Setting SCSI IDs Removing SCSI IDs SCSI ID Editor When you select the Legacy Support > Set SCSI IDs command, a SCSI ID Editor dialog box, similar to the one shown below, displays. Each row in the dialog box represents a physical SCSI adapter installed in a slot on the SMP node. Caution: The SCSI ID Editor used to set SCSI IDs cannot determine what other devices are connected to a particular bus, so you must be careful to never assign the same ID to more than one device on a SCSI bus. 316 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Configuring SCSI Adapters on 48xx/52xx and 49xx/53xx Nodes Only AWS Users or users with Administrator privileges can edit SCSI information. AWS Guests can view SCSI information, but they do not have access to the Apply button on the SCSI ID Editor. Figure 87: SCSI ID Editor Dialog Box Table 86: SCSI ID Editor Description Field Board Type Physical Slot SCSI ID Description Determines how many bus IDs must be configured for a particular adapter. PQS (PCI Quad SCSI) adapters have four ports, therefore they have four SCSI IDs to configure. The default adapter type is PQS. PDS (PCI Dual SCSI) have two ports, therefore they have two SCSI IDs to configure. Note: You must know which board type you are configuring. Represents the physical slot the adapter is installed in; slots start at the first available PCI slot appropriate for a SCSI adapter. Each adapter in an SMP node has its own slot; the number of slots available on an SMP node depends on the system platform (for example, the number of slots on a 4800 node differs from the number of slots on a 4855 node). The slot number starts at 1; the numbering scheme on a node chassis is from top to bottom or left to right; recommended slot configurations are described in the Processing Node Service Guide for the platform. Represents the SCSI host identification of the bus on the specified port on the board. SCSI IDs are shown as hexadecimal values ranging from 0-F. For PQS adapters, Port 0, Port 1, Port 2, and Port 3 must be set. For PDS adapters, Port 0 and Port 1 must be set (the other ports are unavailable). Note: Use the highest available unique identifier for the bus being configured. Access to Teradata AWS Commands Teradata AWS User Guide, Release 4.5 317

Appendix B: Configuring the System Changing Server Management IP Addresses Setting SCSI IDs Removing SCSI IDs To Set SCSI IDs for Adapters Installed on 48xx/52xx and 49xx/53xx Nodes 1 In the Tree View, select the SMP node. 2 Select Legacy Support > Set SCSI IDs. 3 If no adapters are listed, click the Add button. 4 Configure the Board Type, Physical Slot, and SCSI ID for the adapters displayed in the SCSI ID Editor. 5 To implement the changes, click Ok and reboot the node at the AWS. SCSI ID Editor To Remove SCSI IDs for Adapters Installed on 48xx/52xx and 49xx/53xx Nodes 1 In the Tree View, select the SMP node. 2 Select Legacy Support > Set SCSI IDs. 3 When the SCSI ID Editor displays, find the board you want to remove, then click inside the area to highlight the board. 4 On the SCSI ID Editor, click the Delete button. The selected board is removed from the configuration. 5 To implement the changes, click Ok and reboot the node at the AWS. Changing Server Management IP Addresses Changing IP Addresses in Systems with SM3G Changing the server management IP addresses of components in systems with SM3G is covered in the Hardware Service Guide for your platform. If you have a coexistence system, see the appropriate Coexistence Guide for your platform. Changing IP Addresses in Systems with Legacy Server Management In systems with legacy server management, use the following procedures to change the SLAN IP addresses of a CMIC, BYNET, Fibre Channel switch, or disk array controller. Always make sure the AWS hosts file contains the new SLAN IP address and the existing SLAN network name 318 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Changing Server Management IP Addresses To Change a CMIC IP Address in Systems with Legacy Server Management 1 Label and unplug the power cables from the cabinet s SMC chassis. Note: When the CMIC reports a Lost Heartbeat status, highlight the cabinet and select Configuration > Remove Component. The cabinet is removed from the Tree View. 2 Plug the power cables back into the SMC chassis outlets you removed them from. 3 When the CMIC in the SMC chassis boots, use the displayed CMIC Bootp Request dialog box to configure the cabinet with the new IP address, then click OK. The fields should be completed as follows: CMIC Name: The host name of the CMIC. IP Address: The SLAN IP address for the CMIC. Hardware Address: The CMIC s unique MAC hardware address. System Number: The system number of the CMIC. Cabinet Number: The cabinet number of the CMIC. 4 Reboot the CMIC by doing the following: a b Unplug the power cables from the SMC chassis again. Wait 5 seconds for the power to cycle. c Plug the power cables back into the SMC chassis. When the CMIC reboots, the SMC chassis is configured with the new IP address. To Change a BYNET IP Address in Systems with Legacy Server Management Note: When you change the IP address of a BYNET chassis, it is the IP address of the BYNET chassis Diagnostic Processor (DP) that is being changed. 1 Label and unplug the power cables from the cabinet s SMC chassis. Note: Label and unplug the power cables from the cabinet s BYNET chassis. When the CMIC reports a Lost Heartbeat status, highlight the BYNET chassis in the Tree View and select Configuration > Remove Component. 2 Plug the power cables back into the BYNET chassis outlets you removed them from. 3 Plug the power cables back into the SMC chassis outlets you removed them from. Teradata AWS User Guide, Release 4.5 319

Appendix B: Configuring the System Changing Server Management IP Addresses To Change a Disk Array (MDA) IP Address in Systems with Legacy Server Management During staging, the disk array controller (MDA) is assigned the server management IP address that is stored in the disk array, and the AWS's bootp request feature is typically disabled. If you need to change the SLAN IP address of a disk array controller, contact your Customer Service Representative. To Change a Fibre Channel Switch IP Address in Systems with Legacy Server Management 1 Power off the Fibre Channel switch. 2 Highlight the Fibre Channel switch in the Tree View and select Configuration > Remove Component. 3 Power on the Fibre Channel switch. 4 Use the displayed Fibre Channel Switch Bootp Request dialog box to configure the Fibre Channel switch chassis with the new IP address, then click OK. The fields should be completed as follows: IP Address: The SLAN IP address for the Fibre Channel switch. The first three octets are typically set to match the first 3 octets of the CMIC in the same cabinet. Subnet Mask: The subnet mask for the SLAN network. This is typically 255.255.255.0. Gateway Address: The default gateway for the SLAN. The SLAN is a closed network, so this address is typically configured to match the AWS s SLAN IP address. Hardware Address: The Fibre Channel switch s unique MAC hardware address. System Number: The system number of the CMIC in the same cabinet. Cabinet Number: The cabinet number of the CMIC in the same cabinet. 5 Use the on/off button to power cycle the Fibre Channel switch. When the Fibre Channel switch powers on, it is configured with the new IP address. 6 Reboot the AWS or do the following: a b c On the AWS desktop, select Start > Programs > Teradata AWS > AWS Configuration to display the AWS dialog box. In the Tree tab, right-click System Objects Manager to display a pop-up menu. Click Properties. 320 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System AWS IP Configuration Utility d e When the System Objects Manager Properties dialog box displays, on the System Objects Manager tab, select Snmp Discovery from the drop-down list. Click Perform Action, then OK. AWS IP Configuration Utility The AWS IP Configuration Utility allows you to: Configure the AWS software with the primary and secondary SM3G server management network IP addresses used by the AWS and the CMICs. Identify the network ID (IP addressing scheme) used by the server management networks. Enable the Remote AWS feature, which gives users remote access to the Teradata AWS and its commands. Enable support for coexistence systems that have both SM3G and legacy server management. In systems with redundant AWSs, each AWS has its own AWS IP Configuration Utility. General Tab Network IDs Tab SM3G CMIC Addresses Tab AWS IP Addresses CMIC IP Addresses To Display the AWS IP Configuration Utility 1 Select Start > Programs > Teradata AWS > AWS Configuration to display the AWS Configuration dialog box. 2 Right-click the IP Configuration icon to display a pop-up menu. 3 Select the IP Configuration Tool command from the pop-up menu. 4 The AWS IP Configuration Utility displays. The following tabs are available: Teradata AWS User Guide, Release 4.5 321

Appendix B: Configuring the System AWS IP Configuration Utility General Tab The General tab on the AWS IP Configuration Utility configures the server management network IP addresses used by the AWS, enables the Remote AWS feature, and enables support for coexistence systems with both SM3G and legacy server management. Note: The Primary IP, Secondary IP, and System ID fields are blank until you click the AutoDiscover button or use the Add button to enter information. Figure 88: AWS IP Configuration Utility Dialog Box: General Tab Table 87: AWS IP Configuration Utility Dialog Box: General Tab Description Item Primary IP Secondary IP System ID Add button Remove button Auto Discover button Enable remote access to AWS services Public Host Name or IP Address Description The AWS IP address of a server management primary network (formerly known as the SLAN) The AWS IP address of a server management secondary network (formerly known as the PLAN, or PvtLAN) The system whose primary and secondary AWS IP addresses display Adds an AWS primary or secondary IP address to the AWS software configuration. Removes the selected primary and secondary AWS IP addresses from the AWS software configuration. Automatically discovers the primary and secondary AWS IP addresses. Allows client machines to use the Remote AWS feature to establish a remote connection to the AWS Panel service, which then displays the Teradata AWS. The host name or IP address of the AWS; to access the Remote AWS feature, the host name or IP address must be accessible by client machines 322 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System AWS IP Configuration Utility Table 87: AWS IP Configuration Utility Dialog Box: General Tab Description (continued) Item Enable Legacy Support Legacy Support Host Legacy System ID Description If a system with legacy server management is connected to the AWS, this option enables the AWS to provide support for that system, including the display of legacy components in the Teradata AWS. The name of the host running the software packages for the system with legacy server management; in most cases, this is the localhost The number assigned to the system with legacy server management. Network IDs Tab The Network IDs tab on the AWS IP Configuration Utility allows you to identify the network ID used by the server management network. Figure 89: AWS IP Configuration Utility Dialog Box: Network Tab Table 88: AWS IP Configuration Utility Dialog Box: Network Tab Description Item Class A Network ID Description For sites that use a Class A IP addressing scheme, this field informs AWS software about the network ID used by the server management networks. The default is 10.0.0.0. If the server management networks use a different Class A network ID, that network ID must be entered in this field, or the AWS software cannot function properly. If your site uses a Class B IP addressing scheme, this value is not used. Teradata AWS User Guide, Release 4.5 323

Appendix B: Configuring the System AWS IP Configuration Utility Table 88: AWS IP Configuration Utility Dialog Box: Network Tab Description (continued) Item Class B Network ID Description For sites that use a Class B IP addressing scheme, this field informs AWS software about the network ID used by the server management networks. The default is 172.16.0.0. If the server management networks use a different Class B network ID, that network ID must be entered in this field, or the AWS software cannot function properly. If your site uses a Class A IP addressing scheme, this value is not used. SM3G CMIC Addresses Tab The SM3G CMIC Addresses tab on the AWS IP Configuration Utility allows you to configure the server management network IP addresses used by the CMIC. Note: Only SM3G CMIC IP addresses need to be added to this tab. Note: All rows in this dialog box are blank until you click the AutoDiscover button or use the Add button to enter information. Figure 90: AWS IP Configuration Utility Dialog Box: CMIC Addresses Tab Table 89: AWS IP Configuration Utility Dialog Box: CMIC Addresses Tab Description Item Display CMIC IP addresses for Primary IP Secondary IP Description Displays the CMIC IP addresses for the system selected in the list box For the system specified by the System ID, this field contains the IP address of a CMIC connected to the primary server management network For the system specified by the System ID, this field contains the IP address of a CMIC connected to the secondary server management network 324 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System AWS IP Configuration Utility Table 89: AWS IP Configuration Utility Dialog Box: CMIC Addresses Tab Description (continued) Item System ID Collective ID Cabinet ID Chassis ID Add button Remove button Auto Discover button Description The system whose primary and secondary CMIC IP addresses are displayed The collective whose primary and secondary CMIC IP addresses are displayed The cabinet whose primary and secondary CMIC IP addresses are displayed The CMIC chassis whose primary and secondary CMIC IP addresses are displayed Allows you to add a CMIC primary or secondary IP address to the AWS software configuration for the specified system. Removes the selected primary and secondary CMIC IP addresses from the AWS software configuration for the specified system. Automatically discovers the primary and secondary CMIC IP addresses for the specified system; if there are no CMIC IP address entries in the table, you must add one before you can use the Auto Discover button to discover the remaining CMIC IP addresses. AWS IP Addresses The Add AWS Address dialog box adds a primary or secondary AWS IP address to the AWS IP Configuration Utility, or update this information if the AWS IP configuration changes. You only need to specify one IP address; the other IP addresses are configured automatically. To Add a Primary or Secondary AWS IP Address 1 Display the AWS IP Configuration Utility. 2 On the General tab, in the AWS IP Addresses section, select Primary IP or Secondary IP. 3 If an IP address already exists, click Remove. 4 Click Add. 5 In the Primary or Secondary Network Address field, type a primary or secondary IP address. 6 Click OK. To Display the AWS IP Configuration Utility Teradata AWS User Guide, Release 4.5 325

Appendix B: Configuring the System Configuring Permissions for Members of AWS Guests CMIC IP Addresses The Add CMIC Address dialog box allows you to add a primary or secondary CMIC IP address to the AWS IP Configuration Utility, or update this information if the CMIC IP configuration changes. You only need to specify one IP address; the other IP addresses are configured automatically. To Add a Primary or Secondary CMIC IP Address 1 Display the AWS IP Configuration Utility. 2 On the SM3G CMIC Addresses tab, in the CMIC IP Addresses section, select Primary IP or Secondary IP. 3 If an IP address already exists, click Remove. 4 Click Add. 5 In the Primary or Secondary Network Address field, type the primary or secondary IP address. 6 Click OK. To Display the AWS IP Configuration Utility Configuring Permissions for Members of AWS Guests The User Group Config Tool allows users with Administrator privileges, or members of AWS Users, to create groups. The groups give members of AWS Guests access to additional Teradata AWS commands. The additional commands are those that Administrators and AWS Users have access to by default. Different sets of commands can be specified for each group. Each group is automatically added to the Groups folder in Local Users and Groups. After you create a group, you must use Computer Management to add members of AWS Guests to the group. For more information about adding users to groups, see Microsoft Help. Table 90 on page 328 lists the additional commands that members of the AWS Guests group can be given access to. Displaying the User Group Config Tool 326 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Configuring Permissions for Members of AWS Guests Creating and Editing an AWS Guests Group Deleting an AWS Guests Group Displaying the User Group Config Tool To Display the User Group Config Tool 1 Select Start > Programs > Teradata AWS > AWS Configuration to display the AWS Configuration dialog box. 2 Right-click the User Group Config icon to display a pop-up menu. 3 Select the User Group Config Tool command from the pop-up menu. 4 The AWS Group Permissions Configuration dialog box displays. Figure 91: AWS Group Permissions Configuration Dialog Box Creating and Editing an AWS Guests Group Deleting an AWS Guests Group Teradata AWS User Guide, Release 4.5 327

Appendix B: Configuring the System Configuring Permissions for Members of AWS Guests Creating and Editing an AWS Guests Group To Create an AWS Guests Group and Configure Permissions 1 From the AWS Group Permissions Configuration dialog box, click New. 2 When the AWS Group Permissions dialog box displays, in the Group Name text box, type a name for the group. 3 To specify which commands you want this group of AWS Guests to have access to, select the appropriate check boxes. Figure 92: AWS Group Permissions Dialog Box Table 90: AWS Group Permissions Dialog Box Description Option Gives Permission to Access See: AWS Functions Connect Functions > Connect. Connecting to Components from the Tree View on page 201. 328 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Configuring Permissions for Members of AWS Guests Table 90: AWS Group Permissions Dialog Box Description (continued) Option Gives Permission to Access See: Flash Firmware Functions > Flash Firmware Updating (Flashing) Firmware on page 245 Legacy Support > Flash CoProcessor Firmware Firmware Version Checker Functions > Flash Flashing Management Board Firmware in Systems with Legacy Server Management on page 249 Checking Firmware Versions on page 251 SetFW SetFW on page 293 Power On Functions > Power On Powering On a System/Cabinet/Chassis on page 265 SetPower SetPower on page 294 Power Off Functions > Power Off Powering Off a System/Cabinet/Chassis on page 264 SetPower SetPower on page 294 Reset Functions > Reset Resetting Components on page 262 Reset Reset on page 292 Dump Memory Functions > Dump Memory Dumping Node Memory on page 262 DumpMemory DumpMemory on page 282 Replace FRU Functions > Replace FRU Replacing Hardware Components (FRUs) on page 240. Set Battery Date Functions > Set Battery Date Battery Date Information Functions > Select All Functions > Modify Tracking and Setting Battery Installation and Replacement Dates on page 257 SetBatteryDate SetBatteryDate on page 292 Diagnostics Functions > UPS Self-Test UPS Self-Test on page 270 Functions > UPS Input Selector Test UPS Input Selector Test on page 271 Functions > MLAN Integrity Test; MLAN Integrity Test on page 272 UPSTest UPSTest on page 299 MLANTest MLANTest on page 289 Manage CMIC Functions > Manage CMIC Connecting to a CMIC Web Page on page 199. Event/Fault Functions Custom Events Query Event Mgmt > Custom Events Query Creating Custom Queries for Events on page 85. Teradata AWS User Guide, Release 4.5 329

Appendix B: Configuring the System Configuring Permissions for Members of AWS Guests Table 90: AWS Group Permissions Dialog Box Description (continued) Option Gives Permission to Access See: Track Fault Resolution Status Add to Fault Journal Close Fault Submit New Fault Edit Fault Recommendation Delete Fault Recommendation Submit New Fault Recommendation Functions > Track Resolution Status (when viewing faults) Functions > Add to Journal (when viewing faults) Functions > Close (when viewing faults) Functions > Submit New Fault (when viewing faults) Functions > Edit (when viewing recommendations) Functions > Delete (when viewing recommendations) unctions > Submit New Recommendation (when viewing recommendations) Tracking Fault Resolution Status on page 112. Adding Fault Journal Comments on page 114. Closing a Fault on page 115. Submitting a New Fault on page 119. Editing Recommendations on page 125. Deleting Recommendations on page 125. Submitting New Recommendations on page 123. Legacy AWS Functions Set SCSI IDs Legacy Support > Set SCSI IDs Configuring SCSI Adapters on 48xx/52xx and 49xx/53xx Nodes on page 316. Update Asset Information Legacy Support > Update Asset Information Updating Asset Information for Components in Systems with Legacy Server Management on page 168. Configuration Functions Remove Component Functions > Remove Component Removing Components on page 315 RemComponent RemComponent on page 291 Set Aliases Configuration > Set Aliases Configuring Component Names on page 53. Group/Ungroup Tree Items View > Group Tree Items View > Ungroup Tree Items Grouping and Ungrouping Components in the Tree View on page 59 4 Click Save. The new group appears in the AWS Group Permissions Configuration dialog box. 5 Click Close. 6 To add members of AWS Guests to the new group, do the following: a Select Start > Settings > Control Panel > Administrative Tools. 330 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Configuring Permissions for Members of AWS Guests b c d e f Double-click Computer Management. Double-click Local Users and Groups. When you created the new group, it was automatically added to Groups. Double-click Groups. Find the name of the group you created and double-click it. Use the displayed dialog box to add members of AWS Guests to the group. After users are added to the group, they have immediate access to the commands specified in the AWS Group Permissions dialog box. To Edit Permissions in an Existing AWS Guests Group 1 From the AWS Group Permissions Configuration dialog box, click Edit. 2 When the AWS Group Permissions dialog box displays, select the appropriate check boxes to specify which commands you want users of AWS Guests in this group to have access to. For command descriptions, see the references in Table 90. 3 To update the permissions, click Save. The changes take effect immediately. 4 Click Close. Deleting an AWS Guests Group To Delete an AWS Guests Group 1 From the AWS Group Permissions Configuration dialog box, select the group you want to delete. 2 Click Delete. 3 To delete the group from the AWS, do the following: a b c d e f Select Start > Settings > Control Panel > Administrative Tools. Double-click Computer Management. In the Computer Management dialog box, double-click Local Users and Groups. Double-click Groups. Find the name of the group you want to delete and select it. Click Yes to delete the group. Teradata AWS User Guide, Release 4.5 331

Appendix B: Configuring the System Configuring the System Objects Server in Systems with Legacy Server Management Configuring the System Objects Server in Systems with Legacy Server Management The Start > Programs > Legacy SLAN > Legacy SLAN Configuration application configures values used by the System Objects server (legacy server management only). To Display the Legacy SLAN Configuration Application 1 On the AWS desktop, select Start > Programs > Legacy SLAN > Legacy SLAN Configuration to display the Legacy SLAN dialog box. 2 In the right panel, right-click System Objects Manager to display a pop-up menu. 3 Click Properties. Configuring Default Values for the System Objects Server Configuring Default Values for the Fibre Channel Switch Configuring Default Values for the System Objects Server In systems with legacy server management, the System Objects Manager tab configures the default values used by the System Objects server. You can use this tab to force the server to perform various actions that are usually performed automatically. Warning: Caution: The options on this tab are tuning parameters and do not normally need to be adjusted. Changing the values of these options may adversely affect the AWS s performance. By default, the options on the System Objects Manager Properties dialog box are set to the optimum values during AWS installation. 332 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Configuring the System Objects Server in Systems with Legacy Server Management Figure 93: System Objects Manager Properties Dialog Box: System Objects Manager Tab Table 91: System Objects Manager Properties Dialog Box: System Objects Manager Tab Description Option Compact Period (in seconds) Check Schedule Period (in seconds) Cmd Timeout (in mili-seconds) Cmd Retry Count (SLAN) Discovery Period (in seconds) Event Handler Max Events (SNMP) Discovery Period (in seconds) Heart Beat Period (in seconds) Polling Period (in seconds) Description Period of time in between SLAN internal state compacts. In seconds, 0 means disabled. Period of time in between SLAN internal state checks. In seconds, 0 means disabled. Timeout on SLAN commands in milliseconds. The number of attempts to re-try failed SLAN commands. Period of time in between SLAN discovery attempts. In seconds, 0 means disabled. Maximum number of internal SLAN events queued for processing. 0 to disable processing. -1 for no limit. Period of time in between SNMP discovery attempts. In seconds, 0 means disabled. Period of time in between SNMP heart beat attempts. In seconds, 0 means disabled. Period of time in between SNMP polling attempts. In seconds, 0 means disabled. Teradata AWS User Guide, Release 4.5 333

Appendix B: Configuring the System Configuring the System Objects Server in Systems with Legacy Server Management Table 91: System Objects Manager Properties Dialog Box: System Objects Manager Tab Description (continued) Option Perform Action. list box and button Defaults button OK button Cancel button Apply button Description The button forces the server to execute the action specified in the list box. The following actions can be performed: Discover Elements: Attempts to discover managed elements (both SLAN and SNMP). Re-load Knowledge: Reloads of all fault detection knowledge used by this service. Compact: Performs any possible cleanup operations, for example, system resources and memory. Check Schedule: Performs flushes to the PDS, the configuration database that stores system information on the AWS, and performs other periodic checks. Slan Discovery: Attempts to discover all managed SLAN elements. Snmp Discovery: Attempts to discover all managed SNMP elements, such as Fibre Channel switches. Snmp Heart Beat: Issues a heart beat attempt to all known SNMP devices, such as Fibre Channel switches. Snmp Polling: Polls all known SNMP devices, such as Fibre Channel switches, for current operational statuses. Restores the fields to their default values. Saves the configured data and closes the dialog box. Closes the dialog box without saving the configured data. Saves the configured data without closing the dialog box. Configuring Default Values for the Fibre Channel Switch The Fibre Channel switch firmware flash and reset operations use the ftp and Telnet accounts built into the Fibre Channel switch. The ftp and Telnet user/password accounts and the image name on the Fibre Channel Switch tab are set appropriately and do not normally need to be changed. The default values in these fields are used by the AWS during Fibre Channel switch firmware flash and reset operations. The SetFW and Reset programs provide command line arguments to override these default values. Warning: Caution: Do not change the user name/password values on the Fibre Channel switch. Changing these values could hinder the AWS s ability to perform Fibre Channel switch firmware flash and reset operations. However, should the user name/password values of the switches change, matching values must be entered in the Fibre Channel Switch tab. By default, the options on the System Objects Manager Properties dialog box are set to the optimum values during AWS installation. 334 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Configuring the System Objects Server in Systems with Legacy Server Management Figure 94: System Objects Manager Properties Dialog Box: Fibre Channel Switch Tab Table 92: System Objects Manager Properties Dialog Box: Fibre Channel Switch Tab Description Item Ftp User Name Ftp Password Telnet User Name Telnet Password Image Name Description The ftp user name used to log on to the Fibre Channel switch. The password for the Ftp User Name field. The Telnet user name used to log on to the Fibre Channel switch. The password for the Telnet User Name field. The path and filename of the firmware image used to flash Fibre Channel switches. Note: The firmware image is stored in a controlled directory.. button Launches the Select Image dialog box, which allows you to select the default firmware image used to flash Fibre Channel switches. After you select the file from the Select Image dialog box and click Open, the image s path and file name display in the Image Name field on the Fibre Channel Switch tab. Defaults button OK button Cancel button Apply button Restores the fields to their default values. Saves the configured data and closes the dialog box. Closes the dialog box without saving the configured data. Saves the configured data without closing the dialog box. SetFW Reset Firmware Images for Systems with Legacy Server Management Teradata AWS User Guide, Release 4.5 335

Appendix B: Configuring the System Time Synchronization in Teradata Systems Time Synchronization in Teradata Systems Network Time Protocol (NTP) is used to synchronize time on the following nodes in Teradata Database systems: Server management nodes (SM3G), which run Windows XP UNIX MP-RAS and Linux TPA and non-tpa nodes Windows Server 2003 TPA and non-tpa nodes Simple Network Time Protocol (SNTP) is used to synchronize time on nodes running Windows 2000 Advanced Server. Teradata AWS 4.0 or later (Windows Server 2003) is the time server for all the nodes in Teradata Database systems. When PUT is used to install or upgrade software on a Teradata system, PUT configures the overall system time synchronization, including the time synchronization the AWS uses. The way time is synchronized on the AWS depends on whether your site is configured to use DNS or a manually configured server to synchronize time. The recommended configuration for time synchronization in Teradata Database systems is as follows: Configure one node in each Teradata Database clique as a time service server/client, with the rest of the nodes in the clique configured as its time service clients. Configure the AWS (Windows Server 2003) as the time service server for the Teradata Database system. Configure the AWS (Windows Server 2003) as the time server for the CMICs. Configuring the AWS as the Time Server for the CMICs You must configure the AWS as the time server for the CMICs. If you have a redundant AWS, the primary AWS should be configured as the time server for the CMICs and the Teradata Database system. To Configure the AWS as Time Server for the CMICs 1 If you have a redundant AWS, go to the AWS that is not acting as the time server. a b c d Select Start > Programs > Teradata AWS > AWS Configuration. Select AWS. Right-click AWS. Select Properties from the pop-up menu. e On the AWS Properties dialog box, clear the Configure this AWS as the Time Server for the CMICs option. 2 Go to the AWS that is acting as the time server. 336 Teradata AWS User Guide, Release 4.5

Appendix B: Configuring the System Time Synchronization in Teradata Systems a b c d e Select Start > Programs > Teradata AWS > AWS Configuration. Select AWS. Right-click AWS. Select Properties from the pop-up menu. On the AWS Properties dialog box, select the Configure this AWS as the Time Server for the CMICs option. Teradata AWS User Guide, Release 4.5 337

Appendix B: Configuring the System Time Synchronization in Teradata Systems 338 Teradata AWS User Guide, Release 4.5

APPENDIX C Configuring Alerts Alerting is crucial to system availability. You can configure the AWS to send alerts by e-mail or page, or to run a script or program, when a problem condition requires attention. Guidelines for Configuring Alerts Configuring and Using the Fault Notification Window Configuring the Alert Dispatch Service User Account Configuring the Alert Manager Registering Alert Actions Installing and Using Fault Log Writer Guidelines for Configuring Alerts To Configure the AWS Alert Manager to Send a Page or E-mail to Alert You to Problem Conditions 1 Configure the Alert Dispatch service user account, if necessary. 2 Use the AWS Configuration application to configure the page and e-mail services to be used. The Alert Manager Page tab configures the page service or services. This method requires an external modem connected to the AWS. The Alert Manager Mail tab configures the e-mail service. This method required an Internet connection to an SMTP server. Note: Integration with an Enterprise Manager can be accomplished by running a program using the AlertRegister command or the Fault Manager WMI script interface. 3 Use the AlertRegister CLI to register alert criteria and alert actions. Configuring the Alert Dispatch Service User Account Configuring the Alert Manager Registering a Program or Script to Run Registering Alert Actions Teradata AWS User Guide, Release 4.5 339

Appendix C: Configuring Alerts Configuring and Using the Fault Notification Window To Configure the AWS to Display a Window to Alert You to Problem Conditions Activate the Fault Notification window. Configuring and Using the Fault Notification Window Configuring and Using the Fault Notification Window The Fault Viewer s Tools > Fault Notification command activates the Fault Notification window. The window displays information about open faults in the system. You can configure the window to blink when faults of a specific severity level are reported. Fault Notification Window Working with the Fault Notification Window Fault Notification Window The background color of the Fault Notification window indicates the highest fault severity level reported since the Fault Notification window was reset. The window can be minimized in the AWS PC s taskbar. If minimized, it automatically opens each time a new fault is reported to the Fault Manager. Figure 95: Fault Notification Window Table 93: Fault Notification Window Description Item Open fault count Description The number of open faults in the system. The open fault count is automatically updated each time a new fault is reported. 340 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Configuring and Using the Fault Notification Window Table 93: Fault Notification Window Description Item Last reset Fault count since reset Highest fault severity since reset Description The date and time since the Reset button was used. The number of faults reported since the Reset button was used. The fault count is automatically updated. The highest fault severity level reported since the Reset button was used. The highest fault severity is automatically updated. Working with the Fault Notification Window Fault Notification Window To Enable the Fault Notification Window In the Fault Viewer, select Tools > Fault Notification. To Configure the Fault Notification Window to Blink By default, the background color of the open Fault Notification window matches the highest fault severity level reported since the Fault Notification window was reset. To configure the Fault Notification Window to blink when a new fault is reported: 1 Select the option Enable blink notification for faults at or above severity level. 2 From the dropdown list, select one of the following fault severity levels: Unknown OK Information Warning Degraded Critical Fatal For more information about fault severity levels, see Table 45 on page 146. To Minimize the Fault Notification Window When the Fault Notification window is open, click the Minimize button on the title bar. The Fault Notification window icon is minimized in the AWS PC s taskbar. Note: When minimized, the Fault Notification window automatically opens each time a new fault is reported to the Fault Manager. Teradata AWS User Guide, Release 4.5 341

Appendix C: Configuring Alerts Configuring the Alert Dispatch Service User Account To Display a Minimized Fault Notification Window In the AWS PC s taskbar, select the Fault Notification window icon. To Reset the Fault Notification Window When the Fault Notification window is open, click Reset. Resetting the Fault Notification window does the following: Updates the Last reset field with the current date and time Sets the Fault count since reset field to zero Sets the Highest fault severity since reset field to None. To Disable the Fault Notification Window When the Fault Notification window is open, click Close. Configuring the Alert Dispatch Service User Account You must configure the Alert Dispatch Service user account before you configure the Alert Manager to send e-mails and pages to users. By default, the Alert Dispatch service is set up to run under the local system account, but it may be modified based on site-specific security needs. If the type of alert action you are triggering runs a program, script, or command at the command line, you may want these types of actions to run under a specific user s account instead of the local system account. Running as a user account protects the AWS from improper access and from problems that could be caused by alert programs run as systemprivileged processes. Any special configuration needs required by the alert action programs, scripts, or commands, such as privileges, need to be applied to the user account configured for the Alert Dispatch service. Configuring the Alert Dispatch Service Customizing the AWSAlert User Account Configuring the Alert Dispatch Service To Configure the Alert Dispatch Service to Run as a User Account This procedure is optional, but if you do Step 1, make sure you also do Step 2. 342 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Configuring the Alert Dispatch Service User Account 1 To create a new user, do the following: a b c d e f g h i Select Start > Settings > Control Panel. Select Administrative Tools, then Computer Management. In the left pane, select Local Users and Groups, then Users. Right click in the right pane and select New User from the pop-up menu. In the New User dialog box, create a user account by entering a name, such as AWSAlert, in the User name field. Specify a password. (The same password is used later in the procedure.) Select Password Never Expires. Click Create. Click Close. 2 To add the user account to the following groups, in the detail pane of Computer Manager, select the user account you created, such as AWSAlert, then do the following: a b Right click to display the pop-up menu for the user account (AWSAlert), then click Properties. On the Properties dialog box, select the Member Of tab. c Use the Add button to add the user to the following groups: AWS Users: Adding the user account to this group allows the service to start up. Administrators: Adding the user account to this group prevents the service from failing while running alert actions with DLL Initialization of Kernel32 or User32. 3 Optional: To define a local home directory, on the Properties dialog box, select the Profile tab, then select Local Path and specify the path to the home directory. Defining a home directory allows you to put your alert programs and output files in the home directory and use relative paths in your alert programs or scripts. If you do not define a home directory, use full path names when you register your programs or scripts with the AlertRegister CLI command. If a home directory is not specified, the Alert Dispatch service's current directory defaults to the Windows system installation location. When you specify a home directory, the environment variables HOMEDRIVE and HOMEPATH are available to your alert action programs, and the current directory of the alert process is initially set to the home directory you specified. If you specify a home directory in your alert action programs, and the home directory does not exist, the creation of an alert action process fails and the error is indicated in the AlertLog.txt file as Result: Failed to run; The directory name is invalid. 4 Click OK to save the changes and exit the Properties dialog box. 5 In the left pane of the Computer Management window, select Services and Applications, then Services. 6 In the right pane, select the entry for the Teradata AWS Alert Dispatch service. Teradata AWS User Guide, Release 4.5 343

Appendix C: Configuring Alerts Configuring the Alert Dispatch Service User Account 7 On the Teradata AWS Alert Dispatch Properties dialog box, select the Log On tab. This tab allows you to configure the user account. 8 Select This account and use the Browse button to find and select the user name you set up above. 9 In the Password and Confirm Password fields, enter the same password you used to create the user account. 10 Enter Apply and OK. 11 Return to the Computer Management window and make sure Services is still selected. 12 In the detail pane, select Teradata AWS Alert Dispatch service. 13 Right-click, then select Restart to restart the Alert Dispatch service. 14 Verify that the service starts up successfully. If the service does not start up successfully, you may have entered the wrong password, not given the account proper group permissions, or possibly defined other aspects of the user account incorrectly (for example, the home directory path may be invalid). Customizing the AWSAlert User Account As you create alert programs and register them as alert actions, you may need to customize the AWSAlert user account further to grant special privileges or configure specific environment settings required by your programs. These privileges or settings depend on the system resources your alert programs or scripts access. 344 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Configuring the Alert Manager To Make and Apply Changes to the User Account 1 Use the Computer Management applet to make the following changes to the AWSAlert user account: Add group privileges. Add special User Rights. Add specific file/directory permissions for AWSAlert user or its groups. Add environment settings. 2 To make password changes to the user account, reenter the password in the Alert Dispatch Service Log On tab. 3 To apply changes to the user account, such as changes to permissions and environment, restart the Alert Dispatch service. 4 To propagate system environment variable changes to the Alert Dispatch service, reboot the AWS. Configuring the Alert Manager The Start > Programs > Teradata AWS > AWS Configuration application allows you to configure the e-mail and page services used for e-mail and page alert actions. Once configured, these services should only need to be changed if the page or mail server s configuration changes, if you are configuring a new PIN for a paging service, or if you change the e-mail or paging service provider. After you configure the Alert Manager, you must register the alerts you want to send. To Display the Alert Manager Properties Dialog Box 1 On the AWS desktop, select Start > Programs > Teradata AWS > AWS Configuration to display the AWS dialog box. 2 Right-click the Alert Manager icon to display a pop-up menu. 3 Select the Properties command from the pop-up menu. If a page service is configured, the Alert Manager Properties dialog box displays. Teradata AWS User Guide, Release 4.5 345

Appendix C: Configuring Alerts Configuring the Alert Manager If a page service is not configured, a dialog box displays. Click OK to display the Alert Manager Properties dialog box. 4 When the Alert Manager Properties dialog box displays, select the Alert Manager Mail or Alert Manager Page tab. Using the Alert Manager Mail Tab to Configure a Mail Service Using the Alert Manager Page Tab to Configure a Page Service Using the Alert Manager Mail Tab to Configure a Mail Service The Alert Manager Mail tab configures the parameters for an SMTP mail server. SMTP is a TCP/IP protocol for sending messages from one computer to another on a network. This protocol is the standard method used on the Internet to send e-mail. The Alert Dispatch service uses the data you entered in the Alert Manager Mail tab when triggering an e-mail alert. To Display the Alert Manager Properties Dialog Box To Configure the Mail Service 1 Display the Alert Manager Properties dialog box. 2 Set the options on the Alert Manager Mail tab. 3 Click OK. 346 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Configuring the Alert Manager Figure 96: Alert Manager Properties Dialog Box: Alert Manager Mail Tab Table 94: Alert Manager Properties Dialog Box: Alert Manager Mail Tab Description Item SMTP Server Description Specifies the SMTP server s name or IP address; for example, mail.sandiegoca.teradata.com. SMTP Port Specifies the SMTP server s port number. SMTP servers typically use port 25. Server Timeout This server requires a secure connection (SSL) Reply Address Logon using User Name Indicates the number of seconds to wait for a valid socket to be established with the SMTP service before timing out. This time out field should be set based on the speed of the network path to the SMTP service. The field should be set as low as possible to report an error, in a reasonable length of time, when the SMTP server/service is unavailable. Specifies whether to use the SSL (Secure Sockets Layer) security protocol when connecting to the server. SSL is a security protocol that provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The reply e-mail address. This may be a valid or invalid account name under a domain address depending on whether the SMTP server accepts reply mail to e- mail triggered actions. If the specified SMTP server requires basic (clear text) authentication, enabling this field allows you to specify the user name and password. The account name to log on to the SMTP server. Typically this is the first part of an e-mail address left of the at (@) symbol. Teradata AWS User Guide, Release 4.5 347

Appendix C: Configuring Alerts Configuring the Alert Manager Table 94: Alert Manager Properties Dialog Box: Alert Manager Mail Tab Description (continued) Item Password Logon using NTLM Test Recipient Defaults Test OK Cancel Apply Description The password for the user name field. If enabled, the security context of the Alert Dispatch service is used to authenticate with the server using Microsoft's NT LAN Manager (NTLM) authentication protocol. NTLM is used on networks and on stand-alone systems and is a more advanced challenge/response-based protocol than its predecessor, LAN Manager (LM). Note: Test messages invoked from this tab with the Test button authenticate using the security context of the locally logged in user. The test recipient s e-mail address. This field is not saved when you select OK. Restores fields to predefined settings. Use this button to send an e-mail test message to the address specified in the Test Recipient field using the configuration specified in the Alert Manager Mail tab. Saves the changes and exits the Alert Manager Properties dialog box. Note: The Test Recipient field entry is not saved. Exits the Alert Manager Properties dialog box without saving the configured data. Saves the changes without exiting the Alert Manager Properties dialog box. Using the Alert Manager Page Tab to Configure a Page Service The Alert Manager Page tab allows you to configure, add, or remove Page Service IDs. You may also select a serial device to use. The Teradata Alert Dispatch service uses the selected Page Service ID and Serial Device when triggering a dial-up page alert. Some paging companies offer an e-mail method for sending a page (for example, sending e- mail to <pin>@<pagingservice>.com.). The e-mail paging alternative requires Internet access and e-mail service. It should be used when dialup access to a paging service is not available or when you want faster processing of paging actions. The dial-up page method configured with the Alert Manager Page tab provides a general paging method and does not require Internet access or a mail service but does require an external modem connected to the AWS. The predominant industry standard method of sending alphanumeric pages is through a protocol known as TAP (Telocator Alphanumeric Protocol). You can use the Configure Page Service dialog box to send pages using the automatic mode of the TAP protocol or specify a manual send/expect string that communicates with a central paging terminal. The TAP protocol also supports a manual mode and the Send/Expect string field of the Configure Page Service dialog box is initialized with the appropriate text for the predefined Page Service IDs. To Configure, Add, or Remove a Page Service 1 Display the Alert Manager Properties dialog box. 2 Set the options on the Alert Manager Page tab. 348 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Configuring the Alert Manager 3 Click OK. Figure 97: Alert Manager Properties Dialog Box: Alert Manager Page Tab Table 95: Alert Manager Properties Dialog Box: Alert Manager Page Tab Description Item Page Service ID Description Allows you to select a predefined Page Service Identifier such as Default, SkyTel, or PageNet. If your page service provider is not listed in the predefined Page Service IDs list box, or if you want to add a new Page Service ID (for example, SkyTel2) when you introduce another PIN for a paging service, you can select the button and use the displayed dialog box to add your provider s Page Service Identifier to the Page Service ID list box. After you select a Page Service Identifier from the list box, you can use the Configure button to configure the page service.. This button allows you to add user-defined Page Service Identifiers to, or remove them from, the Page Service ID list box or to add another PIN for an existing page service. Configure Serial Device OK Cancel This button displays the Configure Page Service dialog box. Use the dialog box to configure the page service shown in the Page Service ID list box. This list box contains the Windows Telephony devices available for the page operation. Note: The Phone and Modem Options control panel applet is used to configure Windows Telephony devices and site-specific information such as dialing rules and calling card information. If the control panel applet is used to add or remove serial devices while the AWS Configuration application or Alert Dispatch Service is running, the AWS Configuration application and Alert Dispatch Service must be restarted to reflect the changes. Describing the use of the Phone and Modem Options control panel applet is outside the scope of this document, and its use is outside the boundary of AWS control. Saves the selected serial device data on the Alert Manager Page tab and exits the Alert Manager Properties dialog box. Exits the Alert Manager Properties dialog box without saving the serial device data on the Alert Manager Page tab. Teradata AWS User Guide, Release 4.5 349

Appendix C: Configuring Alerts Configuring the Alert Manager Table 95: Alert Manager Properties Dialog Box: Alert Manager Page Tab Description (continued) Item Apply Description Saves the changes without exiting the Alert Manager Properties dialog box. To Add or Remove a Page Service or PIN 1 Display the Alert Manager Properties dialog box. 2 On the Alert Manager Page tab, select the... button. 3 Use the Add/Remove Page Service ID Dialog to: Add a page service or a new PIN for an existing page service to the Alert Manager Page tab s Page Service ID field. Remove a page service and pin from the Alert Manager Page tab s Page Service ID field. 4 Click Ok. Figure 98: Add/Remove Page Service ID Dialog Box Table 96: Add/Remove Page Service ID Dialog Box Description Item Page Service ID Description Enter the alphanumeric name of the Page Service Identifier you want to add. >> Select this button, next to the Page Service ID field, to insert the Page Service ID into the Page Service ID list on the Alert Manager Page tab of the Alert Manager Properties dialog box. Page Service ID(s) to be removed This field contains a list of Page Service IDs to remove. >> Moves the selected Page Service ID out of the remove list. << Moves the selected Page Service ID into the remove list. Page Service ID(s) This field contains a list of user-defined Page Service IDs. 350 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Configuring the Alert Manager Table 96: Add/Remove Page Service ID Dialog Box Description (continued) Item OK Cancel Description Removes the Page Service IDs that are in the remove list, adds the Page Service Identifiers that are in the Page Service ID list, and exits the dialog box. Exits the dialog box without removing or adding any Page Service IDs. To Configure a Page Service 1 Display the Alert Manager Properties dialog box. 2 On the Alert Manager Page tab, in the Page Service ID list, select the page service you want to configure. 3 Select the Configure button. 4 Use the Configure Page Service dialog box to configure the page service. 5 Click OK. Figure 99: Configure Page Service Dialog Box Table 97: Configure Page Service Dialog Box Description Item Retry on dial error Use TAP protocol Description When enabled, the dial is reattempted under busy or line-in-use conditions. When this check box is selected, the automatic entry mode of TAP is used to send the page. When the check box is cleared, the Manual send/expect string is used to send the page. Teradata AWS User Guide, Release 4.5 351

Appendix C: Configuring Alerts Configuring the Alert Manager Table 97: Configure Page Service Dialog Box Description (continued) Item Dial Max Message Size Limit Manual send/ expect string Field separator Use Country Code and Area Code Country Code Area Code Phone No PIN Description Enter the maximum number of times to dial under busy or line-in-use conditions. Enter the message size limit (or a lesser value) imposed by the paging service. Messages are truncated at this limit minus space needed for checksum data. Enter the manual send/expect protocol with the paging service. Most paging services support the manual entry mode of TAP. For the predefined Page Service IDs, this field is initialized with a sample send/expect string which may or may not require user modification. A send/expect string consists of the <send> and <expect> sequences used to communicate with a paging service central paging terminal. Escape characters may be used within the <send> strings to send carriage returns, line feeds, set time-outs, delays, and so forth. The format of a send/expect string consists of send and expect sequences listed on a single line (string) beginning with a send sequence, as follows: <send> <expect> <send> <expect>.. The <send> and <expect> sequences are separated by the character configured in the dialog box's Field Separator field. The send/expect string may end with either a send or an expect sequence. Send sequences The <send> sequences are sent to the paging terminal one character at a time. Only the <send> sequences may contain escape characters. These escape characters themselves are not sent to the paging terminal, but are translated internally before being sent. If the paging terminal expects a carriage return or a line feed, you must specify that, using escape characters, at the end of the <send> sequence. Expect sequences Characters in the <expect> sequences are used for matching data that the paging terminal returns. No escape characters are allowed in the <expect> sequence. The next <send> sequence is processed after the <expect> string has been found. Example The following send/expect string supports the SkyTel Paging terminal as implemented at the time of this writing. The exclamation point (!) is the field separator value in the example below. \13N\1d!ID=!M\r\1d!Pager ID?!\1$\r\2d!Message:!\2$\r\2d!Message accepted. Enter the separator character used in the Manual send/expect string to separate what is sent and what is expected in response. The field separator cannot be a backslash or space. When enabled, the country code and area code are used when dialing the page service. Select the Windows Telephony country code to use for dialing. Enter the area code of the paging service. Enter the phone number of the paging service. Enter the paging service PIN number. 352 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Configuring the Alert Manager Table 97: Configure Page Service Dialog Box Description (continued) Item Data Bits Stop Bits Parity Defaults Test Description Select the paging service data bit format to use. Select the paging service stop bits to use. Select the paging service parity to use. Fills the fields with predetermined defaults. Offers the ability to send a test page using the configuration specified in the dialog. Manual Mode Escape Characters The following table shows the escape characters that can be used in the <send> sequences of the Manual send/expect string field of the Configure Page Service dialog box. For example, \27N would send an escape character, \d would provide a one-second delay, and \1$ and \2$ would send the PIN and alert message, respectively. Escape Character Description \f Ignore linefeeds in the next expect sequence. \[n]m \[n]d \[n]w \[n]n Pause n number of milliseconds. When n is omitted, the delay is 1 second. Pause n number of seconds. When n is omitted, the delay is 1 second. Wait n number of seconds for the next expect sequence to be found. Send decimal value n (n must be in 0-255 range). \c Do not send a linefeed after the send sequence is sent. \n Send a linefeed. \r Send a carriage return. \[n] \[n]b Send a carriage return and don't send a BREAK signal after a received line during the expect search and set the number of expect search line retries to n. Do not send a carriage return and do send a BREAK signal after a received line during the expect search and set the number of expect search line retries to n. \s Search for the expect string but ignore if not found and continue. \n$ Place substitution parameter (n) into the string at the point where this escape sequence occurs. The following two substitution parameters are supported: \1$ represents the PIN and \2$ represents the message that is being sent. Teradata AWS User Guide, Release 4.5 353

Appendix C: Configuring Alerts Registering Alert Actions TAP Automatic Entry Mode The automatic entry mode of the TAP protocol defines a specific protocol for data to be exchanged between an application and a TAP-based central paging terminal. Messages are broken up into blocks, verified with checksum values, and retried if the server indicates the block should be re-sent. It should be noted that many alphanumeric pagers cannot handle more than 180-240 characters, so breaking the message into multiple blocks, as offered through the automatic mode, is not supported by the Teradata Alert Dispatch service. Registering Alert Actions The AlertRegister command is used to register the alert criteria and the action to be performed when the criteria match. The alert criteria determine when you want to be notified or about which faults you want to be notified. New faults are evaluated against the alert criteria to trigger the specified alert action. The AlertReadme.doc provides tips on how to configure alerts to run user-defined programs or scripts. The AlertReadme.doc and alert sample programs are available on the AWS installation media in the \SM3GAWS\AlertSamples directory. Registering Alert Match Criteria Registering Alert Actions Example: Registering an E-mail Alert Action Based on Fault Severity Example: Registering an E-mail Alert Action Based on a Disk Failure Example: Registering an Alphanumeric Page Examples: Registering a Program or Script Monitoring the Configured Alerts AlertRegister Configuring the Alert Manager AlertRegister Alert Data Parameters Registering Alert Match Criteria To be notified of problem conditions that require your attention, use the AlertRegister CLI to register the following match criteria for faults: severity, problem domain, problem code, component ID, time-of-day-range, days-of week. At least one of the following alert criteria options must be registered: The severity criteria is commonly used to limit alerts to only the most severe problem conditions, for example: [-sev=degraded,critical,fatal] Criteria for [-source] and [-problem] are optional and are used to identify specific sources of or types of faults you want to be notified about. 354 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Registering Alert Actions Registering Alert Actions The time-of-day-range and days-of-week criteria can be used to specify who is to be notified by the alert action. For example, you can set up a filter to specify that Joe be paged during the day shift or weekend, and another alert filter to specify that Kathy be paged during the night shift. You can use the AlertRegister command to set action options that allow you to trigger the following types of alert actions and set the following alert action parameters: Send a page or e-mail, or run a user-defined program or script. Before you can specify an e-mail or page alert action, you must first configure page and e-mail services through the Alert Manager. Specify a command line to execute in a separate process, including the selection of various run-time options. Use Alert Data Parameters to configure the page, e-mail, or command line actions so they contain appropriate expanded data, at run-time, to identify the triggering fault or event. Set an abeyance period, in minutes, that controls how soon after an action is triggered the action may be triggered again. You can register up to 10 alert actions. If you need to register more than 10 alert actions, increase the registry tunable value AlertActionMax at the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\SM3G AWS\Apps\AlertMgr\ Example: Registering an E-mail Alert Action Based on Fault Severity The following AlertRegister command line registers an e-mail alert action that is triggered when any fault with a severity of degraded, critical, or fatal occurs. For example, an e-mail message could be sent to John Doe with a subject line similar to Critical Fault 12345 on AWS1 and a message body that includes all other information concerning the fault. AlertRegister -r EmailAlert -sev=d,c,f -email=john.doe@teradata.com -subj= $SeverityName fault $ID on $AWSName -message= Component: $ObjectPath $_ Source: $Source ProblemCode: $ProblemCode $_$Description $_$Data Example: Registering an E-mail Alert Action Based on a Disk Failure The following AlertRegister command line registers an e-mail alert action that is triggered when a drive fails and needs to be replaced. For example, an e-mail message could be sent to John Doe with a subject line similar to Drive needs to be replaced and a message body that includes what to do about the fault. AlertRegister -r emaildiskfail -sour= Disk_Array -prob= Drive- State:FAILED -email=john.doe@company.com -subj= Drive needs to be replaced -mess= $Description $_Connect to Teradata AWS $AWSName, locate the faulted drive known as $ComponentID and run the FRU Replace procedure to replace it. Teradata AWS User Guide, Release 4.5 355

Appendix C: Configuring Alerts Registering Alert Actions Example: Registering an Alphanumeric Page The following AlertRegister command lines register a page alert action that is triggered when a critical or fatal fault occurs after hours or on weekends. When the severity, time-of-day, and days-of-week criteria match, a page message such as Critical Fault on AWS1 is sent using the SkyTel page service configuration. SkyTel is the name of one of the predefined page service IDs configured through the AWS Configuration application s Alert Manager Page tab. The - subj section shows an example of a minimal message that includes the urgency and AWS name to connect to for further diagnosis of the problem. AlertRegister -r PageAlertWeekend -sev=c,f -days=sat,sun -page=skytel -subj= $SeverityName fault on $AWSName AlertRegister -r PageAlertAfterHours -sev=c,f -days=mon,tues,wed,thu,fri -time=17:00-8:00 -page=skytel -subj= $SeverityName fault on $AWSName Examples: Registering a Program or Script The following examples show the command syntax for registering a program and a Net Send message using the AlertRegister CLI s -run option. Registering a Program or Script to Run The following AlertRegister command line registers a run alert action that is triggered when faults with a warning severity level or higher occur. All of the alert data parameters are available to MYAlert.exe as environment variables for forming the custom alert notification action or message specified in the MyAlert.exe program. In the following example for registering a program to run, MyAlert.exe does not interact with the desktop. AlertRegister -r RunMyAlertProgram -sev=w,d,c,f -faults -env -run= c:\myfolder\myalert.exe For more information and sample programs, see the following documents on the AWS installation media in the \SM3G\AWS\AlertSamples directory: AlertReadme.doc: Provides tips on how to configure alerts to run user-defined programs or scripts WAWS_Fault_Traps.doc: Discusses how to send traps for AWS faults (a common Enterprise Management option) How to Use MPPFM_Fault.doc: Discusses how to write Fault Manager WMI scripts to meet more specific needs. You can modify the sample programs to create your own custom actions, or contact Teradata Professional Services for assistance if needed. Registering a Net Send Message The following AlertRegister command line registers a net message alert action that results in a pop-up window on the PC you identify. The alert action is triggered when a fault is received at the AWS with a severity of critical or fatal. The alert message shown in the example include can include the computer name of another user s PC (for example, the computer name of the system administrator s PC), the fault severity, the Component ID identifying the MPP component that has a problem, and the fault description. The message in the pop-up window 356 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Installing and Using Fault Log Writer is specified with the -run option and can include any alert text and alert data parameters that you need. AlertRegister -R AlertNetSend -sev=c,f -run= net send <ComputerName> $SeverityName $ComponentID $Description Note: The Windows Net Send command allows you to send messages to other users, computers, or messaging names on the network. The Messenger service must be running to receive messages. Read the Microsoft Windows Help Command Reference on Net Send. Monitoring the Configured Alerts After alerts are configured, you can use the AlertRegister CLI display option AlertRegister -d to review alerts that have been triggered. This option shows the configured alerts and the last time the alert was performed. The Alert Log file, C:\Program Files\Teradata\SM3g AWS\Data\AlertLog.txt, can be viewed in Notepad or a similar text editor. The log file contains entries for each alert action that was started. Errors during the alert action process startup, such as file not found, are logged, and so are e-mail or page errors. The results of the alert action process termination are not logged; your alert action program should do its own error logging. Installing and Using Fault Log Writer Installing Fault Log Writer Fault Log Writer can be used to track faults or can be processed for viewing in Enterprise Management System (EMS) consoles. The Fault Log Writer is a scheduled task that creates a log entry in a text file: Each time a fault is created Each time a fault is changed to AutoSolved A daily Fault Log is added to and stored in C:\Program Files\Teradata\SM3G AWS\Data in the format FaultLog_mmddyyyy.txt. At the start of each new day, a new file is created when the first fault is created or a change occurs. The file that is two days old is deleted. Installing Fault Log Writer Testing the Fault Log Writer after Installation Troubleshooting the Fault Log Writer after Installation Stopping and Restarting the FaultLogWriter Scheduled Task Fault Log Format To Install Fault Log Writer 1 At the AWS, log in as Administrator. 2 Select Start > Programs > Teradata AWS > AWS Command Prompt. Teradata AWS User Guide, Release 4.5 357

Appendix C: Configuring Alerts Installing and Using Fault Log Writer 3 At the prompt, type: cd C:\Program Files\Teradata\SM3G AWS\Setup 4 At the prompt, type: FaultLog_setup.bat 5 Click Start > Settings > Control Panel. 6 Double-click Scheduled Tasks. 7 In the Scheduled Tasks window, double-click FaultLogWriter. 8 On the Settings tab of the FaultLogWriter dialog box, clear all check boxes. The dialog box should look like the following: 9 Click Apply, then OK. 358 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Installing and Using Fault Log Writer 10 In the Scheduled Tasks window, right-click FaultLogWriter and select Run. Verify that the status changes to Running. The FaultLogWriter entry should look like the following: 11 Test the Fault Log Writer. Testing the Fault Log Writer after Installation Troubleshooting the Fault Log Writer after Installation Testing the Fault Log Writer after Installation To Test the Fault Log Writer after Installation 1 Do one of the following: Open the Teradata AWS Fault Viewer (Event Mgmt > View Faults) and wait for faults to be created and displayed in the Fault Viewer. In the Tree View, select a node, select the Connect command, log into the node, and use one of the following to create test faults: For an MP-RAS node, type /opt/sm3g/bin/faulttest For a Windows node, type cd C:\Program Files\Teradata\sm3g Node\, then type mcfdtest -fault For a Linux node, type /opt/teradata/sm3g/bin/faulttest For the AWS, type cd C:\Program Files\Teradata\FaultDetector\bin\, then type mcfdtest -fault 2 At the AWS, navigate to C:\Program Files\Teradata\SM3G AWS\Data and look for the Fault Log file, which is in the format FaultLog_mmddyyyy.txt. The file should look similar to the following: Teradata AWS User Guide, Release 4.5 359

Appendix C: Configuring Alerts Installing and Using Fault Log Writer Installing Fault Log Writer Troubleshooting the Fault Log Writer after Installation Troubleshooting the Fault Log Writer after Installation If Fault Log Writer is running, you should expect to see a message similar to the following in the in C:\Program Files\Teradata\SM3G AWS\Trace\FaultLog_error.log file: Miscrosoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved 12/08/08 07:38:56 FaultLog.vbs starting up! showmode is detail SM3g AWS DataDir is C:\Program Files\Teradata\SM3G AWS\Data\ 12/08/08 07:40:12 LogFolder is c:\program Files\Teradata\SM3G AWS\Data\ 12/08/08 07:40:16 Waiting for faults... Fault Log Writer Error File Fault Log Writer and WMI Stopping and Restarting the FaultLogWriter Scheduled Task 360 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Installing and Using Fault Log Writer Fault Log Writer Error File If there is no FaultLog_mmddyyyy.txt file in C:\Program Files\Teradata\SM3G AWS\Data, faults are missing from the log file, or other problems are suspected, check for error messages in C:\Program Files\Teradata\SM3G AWS\Trace\FaultLog_error.log. If you are unable to fix the problem, contact Teradata Customer Services. Note: After a reboot, the older file is renamed FaultLog_errors.bak. Fault Log Writer and WMI The FaultLog.vbs script requires a WMI connection. Although the FaultLogWriter task automatically starts up when the AWS is rebooted, there may be a delay of approximately 1.5 minutes (and infrequently a delay of up to ten minutes) before the FaultLog.vbs script is allowed to connect to WMI. During this period the faults detected before the script connects to WMI are missed and not written to FaultLog_mmddyyyy.txt. The FaultLog_errors.log will show gaps in time stamps during this period. If a package is installed that restarts WMI, you must restart the FaultLogWriter task by doing one of the following: Rebooting the AWS Stopping and restarting the FaultLogWriter task Stopping and Restarting the FaultLogWriter Scheduled Task The FaultLogWriter scheduled task is automatically started on installation and on boot of the AWS. If the task was disconnected from WMI, you should stop the task before you restart the task. To Stop the FaultLogWriter Scheduled Task 1 Select Start > Settings > Control Panel. 2 Double-click Scheduled Tasks. 3 In the Scheduled Tasks window, select FaultLogWriter. 4 Right-click and select End Task. 5 Press Ctrl-Alt-Delete. 6 From the Windows Security dialog box, click Task Manager. 7 In the Windows Task Manager dialog box, click the Processes tab. 8 Select the appropriate cscript.exe task, then right-click and click End Task. An example of the Windows Task Manager is shown below. Caution: The process id from the FaultLog.vbs script is not recorded in the FaultLog_ddmmyyyy.txt file. If there are multiple cscript.exe tasks running, look at the User Name column and verify that the task is running under the user name SYSTEM. Teradata AWS User Guide, Release 4.5 361

Appendix C: Configuring Alerts Installing and Using Fault Log Writer Fault Log Format To Restart the FaultLogWriter Scheduled Task Although the FaultLogWriter scheduled task is automatically started on boot of the AWS, if the task was disconnected from WMI, you should stop the task, then restart it. 1 Stop the FaultLogWriter scheduled task. 2 Select Start > Settings > Control Panel. 3 Double-click Scheduled Tasks. 4 In the Scheduled Tasks window, double-click FaultLogWriter. 5 In the Scheduled Tasks window, right-click FaultLogWriter and click Run. Each fault instance in the Fault Log has a unique ID. Each ID has a Created entry, and there may be a subsequent Modified entry for each ID when its resolution state has changed to AutoSolved. The TimeDetected line is written in local time in the format mm/dd/yy hh:mm:ss. Fault Properties are written in Name = Value format and are covered separately. There are multiple lines for the ProblemDescription, AdditionalData, and other properties. The end of each log entry is denoted by the ending line END***. Example: Created Fault in the Fault Log Example: Modified Fault in the Fault Log Fault Properties in the Fault Log Fault Details on page 109, Table 26 on page 110 Closing a Fault on page 115, Table 29 on page 117 362 Teradata AWS User Guide, Release 4.5

Appendix C: Configuring Alerts Installing and Using Fault Log Writer Example: Created Fault in the Fault Log The following example shows an entry for a fault created in the fault log. However, some of the information is descriptive and does not represent an actual entry. Created ID = 74918 TimeDetected = 10/31/08 15:53:53 Severity = Warning SourceInstance = TEMP.1.60.1.18.11.0 ProblemSourceInstance = root/cmic:bynet_v4_temperature.systemid=1, Coll... ProblemDomain = Bynet ProblemCode = Temp-Warning Problem Description = <synopsis> Meaning: <multi-line description about what this fault means (optional)> Probably Cause: <multi-line description of the cause of the problem (optional)> Recommended Action: <multi-line recommendation about what to do about the problem (if known)> AdditionalData: <multi-line details about how the fault was detected> END*** Example: Modified Fault in the Fault Log The following example shows an entry for a fault modified in the fault log. Modified ID = 74916 TimeDetected = 10/31/08 15:53:53 ResolutionState = AutoSolved END*** Fault Properties in the Fault Log Fault properties are described elsewhere. Additional information about these properties as they appear in the Fault Log are described in Table 98. Table 98: Fault Property Data in the Fault Log Column Type Description ID uint32 A unique Fault ID assigned to the fault; ranges from 1 to 4294967295 TimeDetected datetime The date and time that the fault was detected; maximum 25 characters. GMT is given to the WMI script in the format yyyymmddhhmmss.mmmmmmsuuu and converted to local time for display as mm/dd/yy hh:mm:ss Teradata AWS User Guide, Release 4.5 363

Appendix C: Configuring Alerts Installing and Using Fault Log Writer Table 98: Fault Property Data in the Fault Log (continued) Column Type Description Severity uint16 Indicates the level of problem urgency and impact; can be one of the following values: Unknown (0), OK (1), Information (2), Warning (3), Degraded (4), Critical (5), or Fatal (6). The value is converted to severity text strings that are, at most, 11 characters. ResolutionState uint16 A fault s resolution status; although there is more than one resolution status, only the AutoSolved resolution status appears in the FaultLog_ddmmyyyy.txt file, and only in Modified fault entries SourceInstance string Alias (CIM path) for the component reporting the fault; maximum 25 characters ProblemSourceInstance string Internal identifier for the managed object or source of the problem (the component s Component ID); maximum 256 characters ProblemDomain string The problem area, which is typically a short name for the agent reporting the fault; maximum 32 characters ProblemCode string A value, text string, or number that, in combination with the Problem Domain, represents a unique problem type within the MPP environment; maximum 64 characters ProblemDescription string A description of the fault, including synopsis, optional meaning, probable cause, and recommendation; maximum 3200 characters; variable size and multiple lines AdditionalData string Any additional information available to describe the fault, including the event message that triggered the fault; variable size; multiple lines; some xml encoding 364 Teradata AWS User Guide, Release 4.5

APPENDIX D Managing the AWS Databases All AWS databases are maintained by the AWS. The AWS interprets the database data and represents it in a way that allows you to manage the MPP system. Note: The Events Database, Asset Database, and CMIC Measurement Database are small-capacity databases that reside on SM3G CMICs. AWS Databases Backing Up the AWS Databases Tuning the AWS Databases AWS Databases There are four small-capacity databases on the AWS in the following directory: <AWSInstallDir>\Teradata\SM3G PDS\Data Warning: Warning: Do not modify the database files directly. The AWS GUIs and CLIs are the appropriate interfaces for accessing the data. Do not use Microsoft Access or other tools to open the database tables for browsing. These tools establish and hold locks that conflict with the AWS software. Database ncrmppcfgdb.mdf x3gsm_data.mdf x3gsma_data.mdf AwsFaultSQL.mdf Description In systems with legacy server management, this database contains configuration information about the system that is being controlled by the AWS. AWS services uses this database. This database contains links to the event database that resides on SM3G CMICs and stores event records for systems with legacy server management. These events display in the Event Viewer. This database contains links to the asset database that resides on SM3G CMICs and stores asset history records for chassis in systems with legacy server management. This database stores system fault records collected by AWS service for display in the Fault Viewer. This fault database consists of an open fault table, a closed fault table, and a recommendations table. The open fault table stores a maximum number of open faults for efficient display by the Fault Viewer. As the number of fault records grows, first the oldest resolved faults, then the oldest open faults, are moved from the open fault table to the closed fault table based on the OpenFaultListMax tunable value. This value is set on the AWS Configuration application s Fault Manager tab. Teradata AWS User Guide, Release 4.5 365

Appendix D: Managing the AWS Databases Backing Up the AWS Databases Managing the Fault Database Backing Up the AWS Databases In systems with legacy server management, a backup of the AWS legacy configuration database is necessary to maintain information about the System Objects (components) in the Tree View in the unlikely event of an AWS hardware failure. Teradata recommends that you back up the AWS configuration database after successfully completing major hardware changes that would affect the components in the Tree View. The event database, asset history database, and fault database do not require backups, but if you want to maintain an event or fault history for offline review, you can use the backup procedures described below. Note: The procedures below describe a basic SQL Server technique for backing up and restoring databases. If you need more advanced backup and restore strategies, consult an SQL Server reference manual or an SQL Server expert. Performing a Full Backup Performing a Differential Backup Restoring from a Backup Performing a Full Backup You can run a full backup of each of the four databases while the AWS is operational. The time and space required depends on the amount of data you want to back up. To Perform a Simple Backup to a Disk File 1 From the list below, choose the command line for the database you want to back up. osql -E -S %computername% -Q " backup database [ncrmppcfgdb] to disk='<full path to backup file1>' " osql -E -S %computername% -Q " backup database [awsfaultsql] to disk='<full path to backup file2>' " osql -E -S %computername%\x3gsm -Q " backup database [3gsm] to disk='<full path to backup file3>' " osql -E -S %computername%\x3gsma -Q " backup database [3gsma] to disk='<full path to backup file4>' " 2 Type the line at the command line prompt. 366 Teradata AWS User Guide, Release 4.5

Appendix D: Managing the AWS Databases Backing Up the AWS Databases Performing a Differential Backup You can run a differential backup of each of the four databases while the AWS is operational. A differential backup is cumulative to the last full backup. To Perform a Differential Backup to a Disk File 1 From the list below, choose the command line for the database you want to back up. osql -E -S %computername% -Q " backup database [ncrmppcfgdb] to disk='<full path to backup file1d>' with differential " osql -E -S %computername% -Q " backup database [awsfaultsql] to disk='<full path to backup file2d>' with differential " osql -E -S %computername%\x3gsm -Q " backup database [3gsm] to disk='<full path to backup file3d>' with differential " osql -E -S %computername%\x3gsma -Q " backup database [3gsma] to disk='<full path to backup file4d>' with differential " 2 Type the line at the command line prompt. Restoring from a Backup The following procedures describe how to restore the legacy configuration database (ncrmppcfgdb.mdf) from a full backup, and from a full backup plus a differential backup. You can restore only one full backup plus one differential backup. Note: Restoring the event, asset, and fault databases is not recommended. Doing so overwrites the data recorded since the backup date. To Restore a Full Backup Type the following line at the command prompt: osql -E -S %computername% -Q " restore database [ncrmppcfgdb] from disk='<full path to backup file1>' " To Restore a Full Backup Plus a Differential Backup 1 Type the following line at the command prompt: osql -E -S %computername% -Q " restore database [ncrmppcfgdb] from disk='<full path to backup file1>' with no recovery " 2 Type the following line at the command prompt: osql -E -S %computername% -Q " restore database [ncrmppcfgdb] from disk='<full path to backup file1d>' " Teradata AWS User Guide, Release 4.5 367

Appendix D: Managing the AWS Databases Tuning the AWS Databases Tuning the AWS Databases The AWS database files should not require tuning except in the most demanding environments. Tunables include moving the database files to another location to improve system performance or balance the performance of the AWS disk drives, and tuning the size and automatic maintenance features of the events database and the fault database. Disk Space Managing the Fault Database Disk Space You are strongly urged to provide ample free space for work space and for the database files to grow to their maximum size. A new AWS has have sufficient disk space for the databases to expand. You should not use up this free space. The AWS services produce an AWS fault in the Fault Viewer if the free disk space for the database directory falls below the number of megabytes specified by the Fault Manager dialog box option AWSLowOnDiskSpaceThreshold. You can use the AWS Configuration application to access the Fault Manager dialog box. Managing the Fault Database Managing the Fault Database The AWS Configuration application s Fault Manager settings are used to automatically manage the size of the open and closed fault tables in the fault database. You can configure the maximum number of Open faults in the open fault table and the maximum number of Closed faults in the closed fault table. By default, the settings are set to the optimum values during AWS installation. The Fault Manager uses these maximums to perform maintenance tasks at a specified maintenance time period. If there are too many open faults, resolved faults are moved to the closed table. If there are still too many open faults, the oldest faults are moved to the closed table. If the closed fault table contains too many records, the oldest faults are deleted permanently. You can also use the Fault Manager to specify that a fault be generated when the amount of free disk space available in the <AWSInstallDir>\Teradata\SM3G PDS database folder or the <AWSInstallDir>\Teradata\SM3G AWS\data folder falls below a specific limit. 368 Teradata AWS User Guide, Release 4.5

Appendix D: Managing the AWS Databases Tuning the AWS Databases To Configure the Fault Manager 1 On the AWS desktop, select Start > Programs > Teradata AWS > AWS Configuration to display the AWS Configuration dialog box. 2 Right-click the Fault Manager icon to display a pop-up menu. 3 Select the Properties command from the pop-up menu. 4 When the Fault Manager Properties dialog box displays, use the information in the following table to set the options you want to use, then click Apply or Ok. Figure 100: Fault Manager Properties Dialog Box Table 99: Fault Manager Properties Dialog Box Description Option Open fault list max faults: Closed fault list max faults: Description This field allows you to set the maximum number of faults allowed in the Open Fault List. Faults are automatically closed only when the value is exceeded. Faults are moved to the Closed Fault List in the following order: resolved faults (those with a Resolution of Solved or Unsolved), then oldest faults. A value of zero means unlimited. The default is 1000. This field allows you to set the maximum number of faults in the Closed Fault List. Closed faults are automatically deleted only when the value is exceeded. Oldest faults are deleted first. A value of zero means unlimited. The default is 10,000. Teradata AWS User Guide, Release 4.5 369

Appendix D: Managing the AWS Databases Tuning the AWS Databases Table 99: Fault Manager Properties Dialog Box Description (continued) Option Maintenance time period (in seconds): AWS Low Disk Space Threshold: Perform Action. list box and button Defaults button OK button Cancel button Apply button Description This field allows you to specify the periodic length of time before the Fault Manager performs maintenance tasks. The default is 3600 seconds. This field allows you to set the minimum allowable amount of free disk space in the AWS database folders (<AWSInstallDir>\Teradata\SM3G PDS or <AWSInstallDir>\Teradata\SM3G AWS\data) in megabytes. A fault is created when the AWS database folder s disk space falls below this value. A value of zero disables checking. The default is 1024 MB. The button forces the Fault Manager to execute the action specified in the list box. The following actions can be performed: Close All Faults: Closes all open faults. Force a Maintenance Check: Forces the Fault Manager to perform maintenance tasks. Re-load Knowledge: Reloads fault knowledge. Restores the fields to their default values. Saves the configured data and closes the dialog box. Closes the dialog box without saving the configured data. Saves the configured data without closing the dialog box. 370 Teradata AWS User Guide, Release 4.5

APPENDIX E Configuring Hardware for Secure Remote Access to the Teradata AWS To restrict access to the Teradata AWS from a corporate LAN, and restrict access to the corporate LAN from the Teradata AWS, placing a hardware router/firewall between the corporate network and the AWS is recommended. Individual services on the AWS should not be disabled by any user unless a feature or component is identified as optional in the AWS User Guide or online help, and the user follows the documented steps for disabling the optional feature or component. The use of a separate hardware router/firewall is also recommended in cases where the required ports opened on the Teradata AWS, or the services running on the Teradata AWS, cause security concerns. If the configuration described above is planned, the following table documents which ports and protocols must be opened across the router/firewall to allow the Remote AWS feature to function. Note that the AWS Web Server is optional, and this feature must be installed/enabled at the customer s discretion. Table 100: Required Ports for AWS Web Services Port Number/Range Protocol Initiator Description/Service 1433 TCP Client AWS private instance of SQL Server (MSDE) 1434 UDP Client AWS private instance of SQL Server (MSDE) 7744-7754 RMI/SSL/TCP Server Exported Remote Interfaces (Remote AWS) 7756 HTTP/TCP Client AWS Private Web Server (Panel Service) 7757 RMI/SSL/TCP Client RMI Registry Service (Panel Service) 7758-7759 RMI/SSL/TCP Client Connection Tunnel Service (Panel Service) 7760-7769 RMI/SSL/TCP Client Exported Remote Interfaces (Panel Service) 8998 Private/TCP Client AWS private instance of SQL Server (MSDE) 8999 Private/TCP Client AWS private instance of SQL Server (MSDE) Teradata AWS User Guide, Release 4.5 371

Appendix E: Configuring Hardware for Secure Remote Access to the Teradata AWS 372 Teradata AWS User Guide, Release 4.5

APPENDIX F Teradata AWS Default Security Template (SecureAWS.inf) This section describes the Teradata AWS default security template. AWS Software Restrictions About the Default Security Template (SecureAWS.inf) Default Security Policies and Services Settings in the Template Applying and Validating the Template Changing the Template Additional Information AWS Security AWS Software Restrictions The Teradata AWS is a dedicated machine for managing a Teradata MPP system. Use of the AWS as a server or host for other applications could negatively impact the ability to service and maintain the MPP system. No other use of the Teradata AWS is supported. For example, the Teradata AWS should not be used: As a web server, file server, mail server, or print server As a domain controller For Teradata Manager As a server or host for any other applications not staged on the AWS at the factory Note: The AWS should not be configured as a member of a Windows Domain, particularly where group policy may override local security policy. Overriding local security policy defeats the purpose of the template and may cause the AWS software not to function. Teradata AWS User Guide, Release 4.5 373

Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) About the Default Security Template (SecureAWS.inf) About the Default Security Template (SecureAWS.inf) Not all security risk can be eliminated, but the intention of the Windows Server 2003 Teradata AWS default baseline security template (SecureAWS.inf) is to reduce exposure and maintain the core operation of the AWS. The template is supported on any Windows Server 2003 Teradata AWSs, Releases 4.x and later, with or without Service Pack 1. To get the latest security template, contact your Customer Service Representative. The template defines security policies and Microsoft Windows services settings for the Teradata AWS. To display security policy settings, select Control Panel > Administrative Tools > Local Security Policy. The folders Account Policies and Local Policies contain local security policy settings. To display services settings, select Control Panel > Administrative Tools > Component Services. The Component Services folder contains default settings, including startup settings for common Windows system services. Be aware that not all security settings may be defined in a template, and not all settings defined in a template apply to every system. For example, there are differences between Windows Server 2003, and Windows Server 2003 with Service Pack 1. In addition, specific optional features of the Teradata AWS may require the baseline security template settings to be changed or services to be enabled in order to function. Caution: Although modifications to policies and settings defined in the template can be made to accommodate Teradata AWS optional features, all other changes are at the customer s risk. Before making any other changes, consult Customer Services. The following MMC snap-ins can be used to view, apply, and verify the Teradata AWS default security template: The Security Templates snap-in allows you to define and customize templates The Security Configuration and Analysis, snap-in allows you to: Apply security policies through templates Compare system settings and policies to security template definitions Changing System Settings to Support Teradata AWS Optional Functions 374 Teradata AWS User Guide, Release 4.5

Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) Default Security Policies and Services Settings in the Template Default Security Policies and Services Settings in the Template The following sections provide an overview of the default security policies and services settings in the template. For a detailed comparison between the default settings for a Windows system and the settings defined for the Windows Server 2003 Teradata AWS in the default security template (SecureAWS.inf), consult your Customer Service Representative. Teradata-provided software is configured appropriately during installation. Default Security Policies for the Teradata AWS Default Services Settings for the Teradata AWS Default Security Policies for the Teradata AWS The template defines the following default security policies for the Teradata AWS: Account Policies and Local Policies: Password, account lockout, audit, user rights assignment, and security option policies are based on the Microsoft Windows Server 2003 Hardening Guidelines, which are more strict than the default Windows security settings. Event Log: The maximum sizes of the application, security, and system logs are configured for optimal AWS operation. Default Services Settings for the Teradata AWS As a general rule, the template services are set as follows: Disabled: These services are not needed for Teradata AWS operation; they may be enabled, but at the customer s risk. Manual: These services are needed for optional AWS functions or are services that do not negatively impact AWS functions; they can be enabled or disabled based on customer needs. Services configured for manual startup may be started on demand by other services and applications that depend on them. Automatic: These services are required for Teradata AWS operation; they must be left running. Not Defined: These services are not defined in the template. The template modifies default run states and default user information the template does not change underlying ACLs. Teradata AWS User Guide, Release 4.5 375

Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) Applying and Validating the Template Applying and Validating the Template You must log on to the Teradata AWS as a user with Administrative privileges to apply, re-apply, or validate the template. You can use one of the following tools to apply the template and validate system settings against it: Security Configuration Engine Command Line Utility (secedit.exe) MMC Security Configuration and Analysis Snap-in Note: In the following procedures, secedit.exe is used to apply and validate the template. To Apply the Baseline Teradata AWS Security Template 1 Log in as a user with Administrator privileges. 2 Find the security template file. The SM3G AWS package installs the file in the following location: %programfiles%\aws\config\secureaws.inf 3 Copy the file to the Windows security template directory by typing the following at the prompts shown below: a C:\> cd %systemroot%\security b C:\WINDOWS\security> copy C:\Program Files\Teradata\SM3G AWS\Setup\SecureAWS.inf templates 4 Validate the syntax of the new template by typing the following at the prompt: C:\WINDOWS\security> secedit /validate templates\secureaws.inf 5 Import the Teradata AWS default security template into a security database and apply it to the system by typing the following at the prompt: C:\WINDOWS\security> secedit /configure /db database\secureaws.sdb /cfg templates\secureaws.inf /overwrite /log logs\secureaws.log To Validate System Settings against the Baseline Security Template 1 Run secedit again from the security directory (%systemroot%\security) by typing the following: Secedit /analyze /db database\secureaws.sdb /log logs\chk.log 2 Use Notepad to open the Chk.log file and examine it. Not available and Not configured messages do not usually mean there is a problem. Mismatches do not necessarily mean there is a problem, but should be examined. The following list describes common or known mismatches between the baseline security template and the system settings: Security policies: 376 Teradata AWS User Guide, Release 4.5

Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) Changing the Template NullSessionPipes (Network Access: Named pipes that can be accessed anonymously): If Terminal Services Licensing is in use, there is a mismatch. SeInteractiveLogonRight (Allow Logon Locally): If AWS Users and AWS Guests are allowed, there is a mismatch. SeRemoteInteractiveLogonRight (Allow Logon through Terminal Services): If Terminal Services Licensing is in use, and Remote Desktop Users are allowed, there is a mismatch; if AWS Users and AWS Guests are allowed, there is a mismatch. Services settings: When optional AWS features are in use, there is Service Startup Type mismatches. Changing the Template Caution: Caution: Always use care when considering deviating from the default baseline settings defined in the Teradata AWS default security template. Modifying the template should only be attempted by users with a detailed knowledge of the Windows operating system. Deviation from the baseline setting may cause the AWS software to stop functioning or to function incorrectly, or may expose your AWS to additional security risks. Before attempting to change system settings, review the information in this appendix thoroughly. For additional information on the requirements for securing a Teradata AWS on Windows 2003, contact your Customer Service Representative. Changing System Settings to Support Teradata AWS Optional Functions Customizing Other System Settings Guidelines for Changing System Settings or Modifying the Template Changing System Settings to Support Teradata AWS Optional Functions The following optional functions of the AWS require services settings that differ from the baseline established by the Teradata AWS default security template. AWS e-mail alerting with an SMTP server If the customer wants to use the AWS as an SMTP server for e-mail alerts, Simple Mail Transfer Protocol (SMTP) must be installed and enabled. Otherwise, the SMTP service is not required for e-mail alerting. Cryptographic Services must be installed and enabled. In systems with legacy server management, the management of large cliques using Fibre Channel switches SNMP Service is required SNMP Trap Service is required Remote support through Microsoft VPN or modem If TVI uses VPN for the remote support connection, Remote Access Connection Manager must be enabled. Teradata AWS User Guide, Release 4.5 377

Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) Changing the Template If TVI uses a modem for the remote support connection: The following must be enabled: Remote Access Connection Manager and Telephony. The following should be enabled to allow inbound service connections through a modem connection: Routing and Remote Access. Terminal Server Licensing It is recommended that the customer use the Remote AWS feature to establish remote desktop connections to the AWS. However, Terminal Licensing can be enabled and used instead of, or in addition to, Remote AWS. Remote Access Guidelines for Changing System Settings or Modifying the Template Customizing Other System Settings Caution: Customers who change the local security policy of the AWS from the default security template settings do so at their own risk. The following guidelines apply if you must modify the settings in the Teradata AWS baseline security template: Security Policy Changes: Use care when changing a security policy to a different setting than the one defined in the template. Less secure settings could potentially compromise security. More secure settings may cause the AWS to become non-functional. Do not allow Group Policy to override Local Security Policy. (Again, the AWS should not be configured as part of a domain.) Service Settings Changes: Services defined in the template: Leave Automatic services enabled. They are required for AWS operation. Enable Manual services as needed. Do not enable Disabled services; if you do, you do so at your own risk (enabling them is not recommended) Services not defined in the template: It is recommended that you leave them at their defaults (they are present and enabled for a reason) All Teradata services must remain enabled Guidelines for Changing System Settings or Modifying the Template 378 Teradata AWS User Guide, Release 4.5

Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) Additional Information Guidelines for Changing System Settings or Modifying the Template If you determine that you need to change settings or modify the baseline security template, do not edit the SecureAWS.inf and SecureAWS.sdb files. Change system settings directly by using the Local Security Policy editor or the Service Control Manager. Develop a new template, using SecureAWS.inf as a starting point. Do not edit the.inf files directly. Use the MMC Security Templates Snap-in. Additional Information For more information about the requirements for securing a Windows Server 2003 Teradata AWS, contact your Customer Service Representative. For general information about system security, see the following Microsoft Support articles: HOW TO: Analyze System Security in Windows Server 2003 (KB816580) HOW TO: Define Security Templates by Using the Security Templates Snap-In in Windows Server 2003 (KB816297) You can find them at Microsoft s web site by searching for their knowledge base numbers listed next to the titles, above, or by using the following keyword: kbsecurityservices Teradata AWS User Guide, Release 4.5 379

Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) Additional Information 380 Teradata AWS User Guide, Release 4.5

APPENDIX G AWS Services The following services are automatically started when the AWS boots. Table 101: AWS Services Service Started Teradata AWS Alert Dispatch Teradata AWS Fault Manager Teradata AWS Panel Service Teradata CMIC CIM Server Teradata CMIC Core Teradata CMIC Event Consolidator Teradata Fault Detector Teradata Legacy SLAN CSF Fault Provider Teradata Legacy SLAN SFR Service Description Responsible for running alert action programs that have been configured with the AlertRegister CLI. This service requires the Teradata AWS Fault Manager service to be running. Consolidates faults, which are reports of problem conditions, and stores them persistently in a common format suitable for presentation in the Fault Viewer and in alerts. This service also includes the Alert Manager, which filters events and faults against alert criteria and forwards alert messages to the AWS Alert Dispatch service. Provides Java based panels/clients a simple interface for accessing data and performing operations related to the MPP systems attached to the AWS. It enables remote administration of MPP systems by providing remote clients with the same functionality that would normally be available on the AWS. Included in this service is a connections tunnel so that connections to nodes, disk array controllers, and so forth can be established by clients not directly attached to the private primary and secondary server management networks. Also included is a web server so that panels/clients can be accessed remotely using a web browser. Provides access to management data via the WBEM/CIM standards. Provides the main framework for the CMIC managed element plug-ins. On systems with legacy server management, responsible for logging events received over the SLAN, including events detected by the service subsystem and events forwarded from the SMP node s event logs. A service that detects faults from Windows Application and System event logs that reside on the AWS. In the Fault Viewer, the ProblemSourceInstance for these faults is the same as the AWS's computername. On systems with legacy server management, responsible for reporting faults forwarded from the NODECSF package on UNIX MP-RAS nodes to the AWS Fault Manager. NODECSF is responsible for monitoring streams events and thresholding, and for gathering information that is included in fault reports for PDE/Teradata, BYNET Driver, UNIX MP-RAS kernel, and other miscellaneous significant MPP software sources running on UNIX MP-RAS nodes. On systems with legacy server management, provides a secure method (SSL) to transfer System Fault Record (SFR) files from UNIX MP-RAS nodes to the Teradata AWS. Teradata AWS User Guide, Release 4.5 381

Appendix G: AWS Services Table 101: AWS Services (continued) Service Started Teradata Legacy SLAN System Objects Legacy SLAN/COMM Services Description On systems with legacy server management, the central AWS management framework. This service is a collection of software objects that represent all system components that are managed by the AWS. These objects provide the software interfaces for system management and monitoring. The System Objects service manages the MPP system through the service subsystem over the SLAN connection. This service uses a socket protocol to pass commands, events, and notifications between the System Objects service and the Java-based AWS application and CLIs. Low level services that provide communication capabilities on the SLAN of systems with legacy server management, including: Teradata SLAN BOOTP Server Teradata SLAN Command Teradata SLAN Event Teradata SLAN Heartbeat Receive Teradata SLAN Heartbeat Send Teradata SLAN TFTP Server 382 Teradata AWS User Guide, Release 4.5

APPENDIX H UNIX AWS Help The Teradata AWS (Windows OS) provides a single operational view of an MPP system that has UNIX MP-RAS nodes and provides functionality comparable to the UNIX MP-RAS AWS. The following table can help UNIX MP-RAS AWS users quickly become familiar with Teradata AWS functionality. The following table shows UNIX MP-RAS AWS commands and functions and their corresponding Teradata AWS equivalent. Table 102: UNIX MP-RAS AWS Commands/Functions and Windows (Teradata) AWS Equivalents UNIX MP-RAS AWS Command/Function Automatic cabinet and chassis recognition and configuration Windows AWS Command/ Function Automatic cabinet and chassis recognition and configuration See: How the AWS Works on page 24 Icon Label Alias To Type a User-Defined Alias for a Component Name on page 53 Cabinet Status Status command Operational states Cabinet Window Chassis Layout View Cabinet Status on page 140 Tree View on page 49 Operational States and Their Indicators on page 142 Chapter 6: Creating and Managing Cabinet Windows Displaying an Image of Chassis Components on page 151 Customer Service Facility (CSF) Fault Viewer Fault Manager Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer Managing the Fault Database on page 368 Revision Level Management (RLM) Asset Information Viewing Asset Information on page 155 SEEPROM Rev Update Update Asset Information Updating Asset Information for Components in Systems with Legacy Server Management on page 168 Revision Level Management (RLM) constraint records CheckBattery utility Configuring the CheckBatteries and CheckFirmwareVersion Utilities on page 309 Teradata AWS User Guide, Release 4.5 383

Appendix H: UNIX AWS Help Table 102: UNIX MP-RAS AWS Commands/Functions and Windows (Teradata) AWS Equivalents (continued) UNIX MP-RAS AWS Command/Function Windows AWS Command/ Function See: FRU Replace Replace FRU Replacing Hardware Components (FRUs) on page 240 MLAN Integrity Test MLAN Integrity Test MLAN Integrity Test on page 272 UPS Self-test UPS Self Test UPS Self-Test on page 270 UPS Input Selector Test UPS Input Selector Test UPS Input Selector Test on page 271 EEPROM FW Flash Flash Firmware Flash CoProcessor Firmware Flashing Management Board Firmware in Systems with Legacy Server Management on page 249 To Flash the Firmware on One or More CMICs in Systems with Legacy Server Management on page 246 System/Subsystem Reset Reset Resetting Components on page 262 Memory Dump Memory Dump Dumping Node Memory on page 262 Power Off/On Power Off/On Managing System Power on page 263 Event Log Event Viewer The Event Viewer on page 76 Online Help Online Help Using Teradata AWS Online Help on page 43 Processor (SMP) Connect Console VGA Console (Intel BIOS/Diagnostic Partition Output) LAN Disk Array Controller Connect Connect Remote AWS Client Connections Window Connect Remote AWS Client Connections Window Chapter 9 Connecting to System Components on page 199 Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature on page 36 Chapter 9: Connecting to System Components Chapter 9 Connecting to System Components on page 199 Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature on page 36 Chapter 9: Connecting to System Components CMIC Connect Connect: CMIC Service Chapter 9 Connecting to System Components on page 199 Connecting to a CMIC Web Page on page 199 Accessing the Teradata AWS Application and Desktop with the Remote AWS Feature on page 36 384 Teradata AWS User Guide, Release 4.5

Appendix H: UNIX AWS Help Table 102: UNIX MP-RAS AWS Commands/Functions and Windows (Teradata) AWS Equivalents (continued) UNIX MP-RAS AWS Command/Function BYNET Connect (Utility/ LAN) Connect to the Database (Connect > Database Console Window command) Windows AWS Command/ Function Connect: LAN Utility PC-Xware software See: Chapter 9 Connecting to System Components on page 199 Running X-Windows Applications on UNIX MP-RAS Nodes on page 45 System/Cabinet Level Rescan Rescan (CLI) Rescan on page 291 Set SCSI IDs Set SCSI IDs Configuring SCSI Adapters on 48xx/ 52xx and 49xx/53xx Nodes on page 316 Mark/Unmark Icons Multi-Select Command Deselect All Tree Components Selecting Multiple Components for Input to Commands on page 71 Deselecting Components in the Tree View on page 61 X-Remote Connectivity Terminal Services Connectivity Accessing the AWS PC, Applications, and Application Commands on page 33 Chapter 9: Connecting to System Components BYNET Utility BYNET Utility/DSSP Main Accessing the BYNET Utility on page 272 Accessing the BYNET Diagnostic Service Subsystem Program (DSSP) on page 273 Teradata AWS User Guide, Release 4.5 385

Appendix H: UNIX AWS Help 386 Teradata AWS User Guide, Release 4.5

Index A accessing AWS, applications, and commands 287 BYNET DSSP Utility 273 BYNET Utility 272 Add To Journal command 114 Address Book adding entries 230 backing up and restoring 237 connecting to components 227 description 229 displaying 229 editing entries 236 organizing and managing entries 234 saving connections to 232 Alert Dispatch service configuring 342 description 381 Alert Log file 357 Alert Manager adding a page service 350 configuring e-mail and page services 345 AlertRegister command 277, 354 alerts configuring 339 definition 148 examples of 355 monitoring 357 registering alert actions 354, 355 registering match criteria 354 types of notifications 149 aliases autogenerating 54 configuring 53 for component names 51 typing 53 All Cabinets command 130 applications exiting 40 starting 40 Asset Database 155, 169 asset history description 155 displaying 158 View Asset History window 161 asset information Asset Information View window 157 description 155 displaying 155 generating baseline, SHR data 165 Asset Information command 155 Asset Information View menus 158 window 157 working with 158 AssetInfo command 281 authentication 211 AWS checking system health 139 connecting to 199 description 23 desktop 62 exiting applications 40 file transfers 26 hardware 27 main window 47, 129, 239 menus, description 64 menus, function lockout 68 migration 29 operation overview 24 redundant 42 required ports, remote access 371 security template 26 services 381 software 25 starting applications 40 Status window 129, 239 Tree View 49, 129, 239 upgrades 29 version number 41 viewing command results 70 Virus Message 41 AWS Configuration application 332, 345 AWS databases backing up 366 configuration database 365 database files 365 fault database 365 managing 365 tuning 368 types of 365 AWSAlert User account, customizing 344 AWSHelp command 282 Teradata AWS User Guide, Release 4.5 387

Index B bar graphs 181 bar graphs, stacked 182 baseline of system assets, SHR data 165 batteries CheckBatteries utility 261 expiration date 261 setting installation date 292 tracking replacement date 257 Battery Date Information menus 259 window 258 Blank command 131 Bootp Request dialog boxes, legacy systems 314 browser requirement 29 BYNET cabinets in Tree View 50 BYNET DSSP command 274 BYNET Utility command 273 C Cabinet Window commands 62 Cabinet Window menu 129 Cabinet Windows arranging icons 136 AWS desktop 62 closing 137 creating 130 description 129 extracting 63 hiding, displaying 62 icons 129 menus 134 opening 137 saving views 137 selecting icons 135 setting display options 131, 134 setting up 136 tiling 63 uses 130 working with cabinet icons 135 cabinets changing number of 313 in Tree View 50 names 51 numbering 51 power cabling 267 changing BYNET IP addresses 319 cabinet number 313 CMIC IP addresses 319 disk array controller IP addresses 320 Fibre Channel switch IP addresses 320 system number 313 chassis in Tree View 50 names 51 numbering 51 Chassis Layout View command 151 CheckBatteries utility changing time interval 311 description 309 enabling, disabling 310 CheckFirmwareVersion utility changing time interval 311 description 256, 309 enabling, disabling 310 Client Connections Window closing 216 command description 204 Connect tab 206 connecting to components 204 description 215 display options 224 hiding/displaying Connections Manager 216 hiding/displaying status bar 216 menus 216 saving connections to Address Book 232 setting display options 224 Telnet tab 210 Terminal tab 208 terminal windows 218 Window tab 205 Close Selected Faults command 115 Close Similar Faults command 115 closing faults 115 CMIC Event Consolidation service 381 CMIC Measurement Database 169, 178 CMIC status 150 CMIC, flashing firmware 246, 253 Collapse Tree View command 61 Collective Management View command 150 Collective Management window 150 collectives in Tree View 50 names 51 numbering 51 collectives (CMICs) status 150 commands selecting multiple components 71, 73 viewing results 70 Component IDs 53 component IDs 51 component names 51 component numbers 51 components adding 314 388 Teradata AWS User Guide, Release 4.5

Index asset information and history 155 configuring aliases 53 connecting to 199, 201, 204, 227 deselecting 61 measurement information and history 169 operational states 142 powering off 264 powering on 265 properties 151 removing 315 replacing using FRU Replace Procedure window 244 with Replace FRU command 240, 241, 242 resetting 262 selecting 71, 73 tracking 155, 169 viewing chassis layout 151 configuration database 365 configuring adapters for SMP nodes 316 Alert Dispatch service 342 e-mail and page services 345 ports for remote access 371 SCSI adapters, one node 318 SCSI IDs 316 configuring Windows Firewall 287 Connect command BYNET utilities 203 CMIC web page connections 199 connecting to a CMIC web page 199 to BYNET utilities 203 to components 199, 204 to the AWS 199 connecting to components Address Book 227 Client Connections Window 204 properties of connections 220 Tree View 201 connection options 206 Connections Manager description 222 hiding/displaying 216 sending commands to multiple hosts 223 working with text 219 controlled directory (MB firmware) 293 CSF Fault Provider service, legacy SLAN 381 Custom Event Viewer description 95 menus 98 working with 98 Custom Events Query command 85 Custom Queries commands 187 customizing AWSAlert User account 344 D databases Asset Database 155, 169 AWS types 365 backing up 366 CMIC Measurement Database 169 Fault Database 365 default aliases 52 default names for components 51 dependencies 28 Deselect All command 135 Deselect Tree Components command 61 Detail command 79, 99 diagnostic tests 267 discovery 24 disk array cabinets in Tree View 50 dual AWS 27 Dump Memory command 262 DumpMemory command 282 E e-mail, configuring services 346 error messages System Asset Baseline command 167 escape characters, page service manual mode 353 Event Viewer closing 77 description 76 displaying events 76 event properties 78 saving contents 77 setting display options 82 sorting events 76 viewing details 79 events analyzing 143 creating custom queries 85 definition 139 displaying for one component 76 displaying for one or more components 76 properties of 78 searching for 77 setting display options 82 sorting 76 viewing details 79 Exit command AWS 40 Firmware Version Checker 256 exiting applications 40 Extended Component Information command 65 Extract command 62, 63 Teradata AWS User Guide, Release 4.5 389

Index F fault database description 365 managing 368 fault details 109 Fault Detector service 381 fault journal, adding comments to 114 Fault Manager service 381 settings 368 Fault Notification window 149 fault properties 107 Fault Viewer adding journal comments 114 AWS desktop 62 battery faults 261 choosing view type 127 closing 105 closing a fault 115 deleting recommendations 125 description 102 displaying all faults 103 closed faults 103 faults in separate window 104 hidden fault types 104 list of recommendations 121 open faults 102 recommendation details 122 editing recommendations 125 escalating a fault 119 extracting 63 fault properties 107 filter options 128 filtering faults 125 filtering faults in active window 104 hiding fault types 103 hiding, displaying 62 hiding,displaying 105 Journal 111 managing faults 111 menus 106 Problem Code 110 Problem Domain 108, 110 saving contents 105 setting display options 126 setting filtering options 126 severity indicators 146 sorting faults 105 submitting a new fault 119 submitting new recommendations 123 tiling 63 tracking faults 111 tracking resolution status 112 viewing details 109 Fault Viewer command 62 faults analyzing 147 definition 144 responding to 147 searching for 105 FaultUtil command 148, 283 Fibre Channel Switches in Tree View 50 Fibre Channel switches chassis numbering 50 default values 334 flashing firmware 247 file transfers 26 Find command Event Viewer 77 Fault Viewer 105 firmware checking versions of 251, 252 flashing CMIC 246 flashing Fibre Channel Switch 247 flashing management board 249 flashing management board, mixed-node cabinets 250 firmware image files 293 Firmware Version Checker checking and updating firmware 252 command description 251, 252 description 251 menus 255 window 253 working with 255 firmware versions, checking 251, 256 Flash CoProcessor Firmware command 250 Flash Firmware command 245 flashing CMIC firmware 246 Fibre Channel switch firmware 247 management board firmware 249 management board firmware, mixed-node cabinets 250 flashing firmware 245, 251, 252 FRU Replace Procedure window 244 function lockout 68 FWConfig command 287 G graphs bar 181 saving 197 stacked bar 182 xy 180, 182, 184, 185 Group Tree Items command 59 390 Teradata AWS User Guide, Release 4.5

Index H Help, about 43 I IP addresses BYNET 315 changing for BYNET 319 changing for CMIC 319 changing for disk array controllers 320 changing for Fibre Channel switches 320 CMIC 314, 315 L legacy server management 24 Legacy SLAN services 381 locator LED, enabling 239 M management board, flashing firmware 249, 250 managing AWS databases 365 fault database 368 faults 111 measurement graphs, generating 178 measurement history description 169 displaying 173 measurement information description 169 displaying 170 Measurement Information View window 171 Measurement Information command 170 Measurement Information View menus 172 window 171 working with 173 MeasurementInfo command 289 menus AWS 64, 68 Battery Date Information 259 Cabinet Window 134 Client Connections Window 216 Fault Viewer 106 pop-up 64 migration 29 MLAN Integrity Test command 272 MLANIntegrity command 289 monitoring configured alerts 357 Move command 136 Multi-Select Command description 71 N node cabinets in Tree View 50 node memory, dumping 262 nodes configuring SCSI adapters 316 enabling locator LED 239 non-tpa nodes 28 O Options command Cabinet Windows 133 changing display names 58 Client Connections Window 225 Fault Viewer 104 P page services adding 350 configuring 348, 351 manual mode escape characters 353 removing 350 platforms, supported 28 pop-up menus 64 Power Cable Test command 267 power cabling, cabinets 267 power consumption graphs all in system 182 custom 188 most recent in system 182 power failure, recovering from 266 Power Off command 263 Power On command 263 power output graphs 184 powering off systems, cabinets, chassis 265 powering on systems, cabinets, chassis 265 Predefined Queries commands cabinet level 185 system level 179 Q queries, saving 197 R ReadSCSI command 290 recommendations deleting 125 displaying details 122 displaying list of 121 editing 125 submitting 123 Recommendations command 121 Teradata AWS User Guide, Release 4.5 391

Index recovering from a power failure 266 redundant AWS description 27 differences, primary and secondary 42 Refresh command 58 registering alert actions 354, 355 alert match criteria 354 RemComponent command 291 remote access, configuring ports 371 Remote AWS browser requirements 29 configuring hardware for access 371 description 36 Remove Component command 315 removing components 315 SCSI IDs 318 Replace FRU command 240, 241 replacing components chassis 242 description 240 FRU Replace Procedure window 244 Rescan command 291 Reset command 262, 263, 292 resetting components 262 S saving graphs 197 queries 197 SCSI ID Editor 316 SCSI IDs, removing 318 SecureAWS.inf 26, 373 security 26, 373 security template 26, 373 Select All command 135 selecting components and commands 73 services started during boot 381 Set SCSI IDs command 316 SetBatteryDate command 292 SetFW command 293 SetPower command 294 setting display options Cabinet Windows 134 Client Connections Window 224, 225 Event Viewer 82 Fault Viewer 126 severity indicators, faults 146 SFR service, legacy SLAN 381 ShowBatteries command 295 ShowComponents command 276, 296 ShowFirmwareVersion command 296 ShowProperties command 297 SHR 165 SLAN/COMM services, legacy 382 SM3G 24 SMP nodes, configuring adapters 316 SQL statement, editing 191 SSH keys, generating 214 starting applications 40 status cabinet components 140 collectives (CMICs) 150 operational 142 Status column 70 Status window AWS desktop 62 description 140 extracting 63 hiding, displaying 62 tiling 63 Status Window command 62, 140 Submit New Fault command 119 system changing number of 313 in Tree View 50 System Asset Baseline command description 165 error messages 167 System Health Report 165 System Objects configuring Fibre Channel switches 334 configuring server 332 server default values 332 System Objects service, legacy SLAN 382 systems names 51 numbering 51 T TAP (Telocator Alphanumeric Protocol) 348 Target column 70 Telnet options 210 temperature graphs all in system 180 all selected cabinets 185 custom 188 most recent in system 181 Teradata AWS Panel Service 381 Teradata CMIC CIM Server 381 Teradata CMIC Core 381 terminal options 208 Terminal Services 35 terminal windows closing 221 392 Teradata AWS User Guide, Release 4.5

Index connection properties 220 hiding/displaying 218 modifying display 219 opening 218 reconnecting to 221 working with text 219 Tile command 63 TPA nodes 28 Track Resolution Status command 112 tracking components 155, 169 tracking faults 111 Tree View AWS desktop 62 changing component display name 58 component names 51 component numbering 51 components 50 configuring aliases 53 connecting to components 201 description 49 expanding, collapsing 61 grouping cabinets or collectives 59 hiding, displaying 62 operational states 142 refreshing 58 ungrouping cabinets or collectives 59 Tree View command 62 menus 176 window 175, 177 View Measurement History command 173 View System Faults command 102 ViewAssetHistory command 300 ViewEvents command 144, 303 viewing asset history 158 asset information 155 event details 79 fault details 109 measurement history 173 measurement information 170 ViewMeasurementHistory command 306 virus message 41 W Windows Firewall configuration 287 X xy graphs 180, 182, 184, 185 U Ungroup Tree Items command 59 UNIX AWS commands, Windows AWS equivalents 383 Update Asset Information command 168 UpdateStatus command 298 updating asset information (legacy systems) 168 upgrading 29 UPS Input Selector Test command 271 UPS power cabling 267 UPS Self-Test command 270 UPSTest command 299 user-defined aliases 52 V version 4.5 30 version number 41 View Asset History menus 163 window 161 working with 163 View Asset History command 158 View Details command 122 View Events command 76 View Measurement Graph commands 178 View Measurement History Teradata AWS User Guide, Release 4.5 393

Index 394 Teradata AWS User Guide, Release 4.5