Teradata AWS. User Guide

Transcription

1 Teradata AWS User Guide Release 4.5 B A August 2009

2 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 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 by Teradata Corporation. All Rights Reserved.

3 Preface Purpose The Teradata AWS User Guide, Release 4.5 (B ), 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

4 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 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 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 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

5 Table of Contents Preface Purpose Audience Prerequisites Changes to This Book Additional Information Chapter 1: Teradata AWS Overview How the AWS Works Discovery Network Communication AWS Software Non-AWS Software AWS Security Secure Default Configuration File Transfers and Remote Connections AWS Hardware Key Dependencies AWS Platforms Hardware Platforms and Platform Configurations Internet Browser Requirements Client Connections Window Dependencies Upgrades and Migration What s New in Version Chapter 2: Accessing the AWS and Its Software Accessing the AWS PC, Applications, and Application Commands User Groups Local Access Teradata AWS User Guide, Release 4.5 5

6 Table of Contents 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 Setting Up the Remote AWS Feature Accessing the Teradata AWS Application with Remote AWS Connecting to the Teradata AWS Desktop through Remote AWS Working with AWS Applications Starting Applications on the AWS Exiting Applications on the AWS Finding the Version Number of an AWS Application 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 Running X-Windows Applications on UNIX MP-RAS Nodes Configuring a Connection to a Teradata Database Window Connecting to a Teradata Database Window Chapter 3: Teradata AWS Application Main Window Tree View 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 Tree View Pane and Windows on the AWS Desktop Teradata AWS Commands Using Teradata AWS Menus Using Pop-up Menus Teradata AWS Menus Access to Teradata AWS Commands Viewing Command Output Teradata AWS User Guide, Release 4.5

7 Table of Contents Selecting Multiple Components for Input to Commands Chapter 4: Monitoring and Managing Events The Event Viewer Event Viewer Menus Event Properties Event Details Event and Event Viewer Display Options Creating Custom Queries for Events Selecting Components for Custom Queries and Displaying the Custom Query Manager 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 Custom Event Viewer Custom Event Viewer Menus Working with the Custom Event Viewer Chapter 5: Monitoring, Managing, and Escalating Faults with the Fault Viewer The Fault Viewer Fault Viewer Menus Fault Properties Fault Details Fault Tracking and Management Tracking Fault Resolution Status Adding Fault Journal Comments Closing a Fault Submitting a New Fault Fault Resolution Recommendations Displaying a List of Recommendations Displaying Recommendation Details Teradata AWS User Guide, Release 4.5 7

8 Table of Contents Submitting New Recommendations Editing Recommendations Deleting Recommendations Fault Viewer Display and Filtering Options Chapter 6: Creating and Managing Cabinet Windows Creating a Cabinet Window and Setting Its Display Options New Cabinet Window and Cabinet Window Dialog Boxes Changing Cabinet Window Display Options Cabinet Window Menu Bar Working with Cabinet Icons Selecting Icons Arranging Icons Erasing or Replacing the Contents of a Cabinet Window Saving, Opening, and Closing Cabinet Windows Chapter 7: Checking the Health of the System Events and System Health Checking Operational States of Components Operational States and Their Indicators Analyzing Events Faults and System Health Checking Fault Severities Fault Severities and Their Indicators Receiving an Alert Notification About a Fault Responding to a Fault Alerts AWS Alert Notification Checking Collective (CMIC) Status Teradata AWS User Guide, Release 4.5

9 Table of Contents Chapter 8: Viewing and Updating Component Information Viewing Properties of Components Displaying an Image of Chassis Components Choose a Layout View Chassis Layout View Tracking Asset Information 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 Tracking Chassis Measurement Information Viewing Measurement Information Viewing Measurement History Generating Measurement Graphs 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 Chapter 9: Connecting to System Components Connecting to a CMIC Web Page Connecting to Components from the Tree View Connecting to Components from the Client Connections Window Setting Options for Connecting to Components 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 Address Book Working with the Address Book Displaying the Address Book Adding Entries Organizing and Managing Entries Editing Entries Teradata AWS User Guide, Release 4.5 9

10 Table of Contents Backing Up and Restoring the Address Book Chapter 10: Servicing, Maintenance, and Troubleshooting Enabling the Locator LED of a Node or CMIC Chassis Replacing Hardware Components (FRUs) Components Replaced with the Replace FRU Command Replacing FRU Components Using the FRU Replace Procedure Window Updating (Flashing) 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 Checking and Updating Firmware with the Firmware Version Checker Running the CheckFirmwareVersion Utility Tracking and Setting Battery Installation and Replacement Dates Selecting Batteries and Setting Installation Dates Displaying Battery Date Information and Setting Battery Installation Dates Running the CheckBatteries Utility Dumping Node Memory Resetting Components Managing System Power 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 Performing Diagnostic Tests UPS Power Cabling Test UPS Self-Test UPS Input Selector Test MLAN Integrity Test Accessing the BYNET Utility Accessing the BYNET Diagnostic Service Subsystem Program (DSSP) Teradata AWS User Guide, Release 4.5

11 Table of Contents Appendix A: Teradata AWS Command Line Interface Access to Teradata AWS CLI Utilities Using the Teradata AWS CLI AlertRegister AssetInfo AWSHelp DumpMemory FaultUtil FWConfig MeasurementInfo MLANTest ReadSCSI RemComponent Rescan Reset SetBatteryDate SetFW SetPower ShowBatteries ShowComponents ShowFirmwareVersion ShowProperties UpdateStatus UPSTest ViewAssetHistory ViewEvents ViewMeasurementHistory Appendix B: Configuring the System Configuring the CheckBatteries and CheckFirmwareVersion Utilities Changing System and Cabinet Numbers Changing a System or Cabinet Number in Systems with SM3G Changing a System or Cabinet Number in Systems with Legacy Server Management Teradata AWS User Guide, Release

12 Table of Contents Adding Components Adding Components to Systems with SM3G Adding Components to Systems with Legacy Server Management Removing Components Removing Components from Systems with SM3G Removing Components from Systems with Legacy Server Management Configuring SCSI Adapters on 48xx/52xx and 49xx/53xx Nodes SCSI ID Editor Setting SCSI IDs Removing SCSI IDs Changing Server Management IP Addresses Changing IP Addresses in Systems with SM3G Changing IP Addresses in Systems with Legacy Server Management AWS IP Configuration Utility General Tab Network IDs Tab SM3G CMIC Addresses Tab AWS IP Addresses CMIC IP Addresses Configuring Permissions for Members of AWS Guests Displaying the User Group Config Tool Creating and Editing an AWS Guests Group Deleting an AWS Guests Group Configuring the System Objects Server in Systems with Legacy Server Management Configuring Default Values for the System Objects Server Configuring Default Values for the Fibre Channel Switch Time Synchronization in Teradata Systems Configuring the AWS as the Time Server for the CMICs Appendix C: Configuring Alerts Guidelines for Configuring Alerts Configuring and Using the Fault Notification Window Fault Notification Window Working with the Fault Notification Window Configuring the Alert Dispatch Service User Account Configuring the Alert Dispatch Service Customizing the AWSAlert User Account Configuring the Alert Manager Teradata AWS User Guide, Release 4.5

13 Table of Contents Using the Alert Manager Mail Tab to Configure a Mail Service Using the Alert Manager Page Tab to Configure a Page Service Registering Alert Actions Registering Alert Match Criteria Registering Alert Actions Example: Registering an Alert Action Based on Fault Severity Example: Registering an Alert Action Based on a Disk Failure Example: Registering an Alphanumeric Page Examples: Registering a Program or Script Monitoring the Configured Alerts Installing and Using Fault Log Writer 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 Appendix D: Managing the AWS Databases AWS Databases Backing Up the AWS Databases Performing a Full Backup Performing a Differential Backup Restoring from a Backup Tuning the AWS Databases Disk Space Managing the Fault Database Appendix E: Configuring Hardware for Secure Remote Access to the Teradata AWS Teradata AWS User Guide, Release

14 Table of Contents Appendix F: Teradata AWS Default Security Template (SecureAWS.inf) AWS Software Restrictions About the Default Security Template (SecureAWS.inf) Default Security Policies and Services Settings in the Template Default Security Policies for the Teradata AWS Default Services Settings for the Teradata AWS Applying and Validating the Template Changing the Template Changing System Settings to Support Teradata AWS Optional Functions Customizing Other System Settings Guidelines for Changing System Settings or Modifying the Template Additional Information Appendix G: AWS Services Appendix H: UNIX AWS Help Index Teradata AWS User Guide, Release 4.5

15 List of Figures Figure 1: Applications on the Teradata AWS Menu Figure 2: Icon Denoting Customer Service Representative Procedure Figure 3: Online Help Tabs Figure 4: Teradata AWS Application Main Window Figure 5: Component Names in the Tree View: Default Names Figure 6: Component Names in the Tree View: Aliases Figure 7: Component Names in the Tree View: Component IDs Figure 8: Generate Aliases Dialog Box Figure 9: Default Aliases for Four Nodes (Example) Figure 10: Generating Aliases for Four Nodes (Template Example) Figure 11: User-Defined Aliases for Four Nodes (Example) Figure 12: Components Grouped in the Tree View Figure 13: Group Tree Items Dialog Box Figure 14: Teradata AWS Application: Menu Bar Figure 15: Pop-Up Menu (Example) Figure 16: Command Summary Dialog Box Figure 17: Command Summary and Command Output Windows Figure 18: Multi-Select Command Window Figure 19: Event Viewer Figure 20: Event Details Window Figure 21: View Events Dialog Box Figure 22: Custom Query Manager Figure 23: Build New Query Dialog Box: Conditions Tab Figure 24: Build New Query Dialog Box: Advanced Conditions Tab Figure 25: Build New Query Dialog Box: Display Columns Tab Figure 26: Build New Query Dialog Box: SQL Statement Tab Figure 27: Custom Event Viewer Figure 28: Fault Viewer Figure 29: View Fault Details Window Figure 30: Track Resolution Status Dialog Box Figure 31: Add To Journal Dialog Box Figure 32: Close Fault Dialog Box (Close > Selected Faults) Figure 33: Close Fault Dialog Box (Close > Similar Faults) Teradata AWS User Guide, Release

16 List of Figures Figure 34: Submit New Fault Dialog Box Figure 35: Fault Viewer Recommendations List (View > Recommendations) Figure 36: Fault Viewer: Recommendations Window (Functions > View Details) Figure 37: Fault Viewer: Recommendations Dialog Box (Functions > Submit New Recommendation) Figure 38: View Faults Dialog Box Figure 39: Cabinet Window Figure 40: New Cabinet Window Dialog Box (New > All Cabinets Command, New > Blank Command) and Cabinet Window (Edit > Options Command) Dialog Boxes Figure 41: Status Window (Example: 5550 Cabinet) Figure 42: Collective Management Window Figure 43: Chassis Layout View: Window Series for Non-Disk Array Chassis Figure 44: Chassis Layout View: Choose a Layout View Figure 45: Chassis Layout View Window Figure 46: Asset Information Dialog Box Figure 47: Asset Information View Window Figure 48: View Asset History Dialog Box Figure 49: View Asset History Window Figure 50: Update Asset Information Dialog Box Figure 51: Measurement Information Dialog Box Figure 52: Measurement Information View Window Figure 53: View Measurement History Dialog Box Figure 54: View Measurement History Window Figure 55: Measurement Graph Manager (Predefined System Queries) Figure 56: xy Graph of All Temperature Readings (Example) Figure 57: Bar Graph of Most Recent Temperature Readings (Example) Figure 58: xy Graph of All UPS Power Consumption Data (Example) Figure 59: Stacked Bar Graph of Most Recent UPS Power Consumption Data (Example) Figure 60: xy Graph of All UPS Power Output Data (Example) Figure 61: Measurement Graph Manager (Predefined Cabinet-Level Queries) Figure 62: xy Graph of All Temperature Readings for Selected Cabinet(s) (Example) Figure 63: Measurement Graph Manager (Custom Queries) Figure 64: Measurement Graph Dialog Box (Custom Queries): General Tab Figure 65: Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab Figure 66: CMIC Web Page Teradata AWS User Guide, Release 4.5

17 List of Figures Figure 67: CMIC Service Web Page Figure 68: Client Connections Window Figure 69: New Connection Dialog Box: Window Tab Figure 70: New Connection Dialog Box: Connect Tab Figure 71: New Connection Dialog Box: Terminal Tab Figure 72: New Connection Dialog Box: Telnet Tab Figure 73: New Connection Dialog Box: SSH/SFTP Tab Figure 74: Key Generator Dialog Box Figure 75: Client Connections Window: Tabbed Layout, Connections Manager, Send To Toolbar (Example) Figure 76: Client Connections Window Options Dialog Box Figure 77: Address Book Dialog Box Figure 78: FRU Replace Procedure Window Figure 79: Firmware Version Checker Window Figure 80: Battery Date Information Window Figure 81: Modify Battery Installation Date(s) Window Figure 82: Power Cable Test Dialog Box Figure 83: BYNET Utility Window Figure 84: DSSP Main Window Figure 85: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Task Tab Figure 86: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Schedule Tab Figure 87: SCSI ID Editor Dialog Box Figure 88: AWS IP Configuration Utility Dialog Box: General Tab Figure 89: AWS IP Configuration Utility Dialog Box: Network Tab Figure 90: AWS IP Configuration Utility Dialog Box: CMIC Addresses Tab Figure 91: AWS Group Permissions Configuration Dialog Box Figure 92: AWS Group Permissions Dialog Box Figure 93: System Objects Manager Properties Dialog Box: System Objects Manager Tab Figure 94: System Objects Manager Properties Dialog Box: Fibre Channel Switch Tab Figure 95: Fault Notification Window Figure 96: Alert Manager Properties Dialog Box: Alert Manager Mail Tab Figure 97: Alert Manager Properties Dialog Box: Alert Manager Page Tab Figure 98: Add/Remove Page Service ID Dialog Box Figure 99: Configure Page Service Dialog Box Figure 100: Fault Manager Properties Dialog Box Teradata AWS User Guide, Release

18 List of Figures 18 Teradata AWS User Guide, Release 4.5

19 List of Tables Table 1: Teradata AWS Security Features and Protocols Table 2: Changes and New Features in Teradata AWS Table 3: Applications on the AWS Menu Table 4: Online Help Categories Table 5: Online Help Navigation Buttons Table 6: PC -XWare Connection Wizard Table 7: Description of Tree View Components and Example Table 8: Generate Aliases Dialog Box Description Table 9: Teradata AWS Options Dialog Box (Tools > Options): Component Tree Display Names Table 10: Teradata AWS: Commands on the Window Menu Table 11: Teradata AWS: Commands on AWS Menus Table 12: Teradata AWS: Access to Commands on AWS Menus Table 13: Teradata AWS: Access to Commands on Other Menus Table 14: Multi-Select Command Window Description Table 15: Event Viewer Commands Table 16: Event Viewer: Event Properties Table 17: Event Details Window Description Table 18: Teradata AWS Options Dialog Box (Tools > Options): Event Viewer Display Options Table 19: View Events Dialog Box: Event Viewer Display Options Table 20: Build New Query Dialog Box Description Table 21: Build New Query Dialog Box: Advanced Conditions Tab Description Table 22: Custom Event Viewer Description Table 23: Custom Event Viewer Commands Table 24: Fault Viewer Commands Table 25: Fault Viewer: Fault Properties Table 26: View Fault Window Description Table 27: Track Resolution Status Dialog Box Description Table 28: Add To Journal Dialog Box Description Table 29: Close Fault Dialog Box Description (Close > Selected Faults) Table 30: Close Fault Dialog Box Description (Close > Similar Faults) Table 31: Submit New Fault Dialog Box Description Teradata AWS User Guide, Release

20 List of Tables Table 32: Fault Viewer Recommendations List Description (View > Recommendations) Table 33: Fault Viewer: Recommendations Window Description (Functions > View Details) Table 34: Fault Viewer: Recommendations Dialog Box Description (Functions > Submit New Recommendation) Table 35: Teradata AWS Options Dialog Box (Tools > Options): Fault Viewer Display Options Table 36: View Faults Dialog Box Description: Choose View Type Table 37: View Faults Dialog Box, Options Dialog Box: Filter Options Table 38: Cabinet Window Dialog Box (Edit > Options) and New Cabinet Window Dialog Box (New > All Cabinets and New > Blank Commands) Descriptions Table 39: Teradata AWS Options Dialog Box (Tools > Options): Cabinet Window Table 40: Cabinet Window Commands Table 41: Cabinet Window: Commands for Selecting Cabinet Icons Table 42: Cabinet Window: Commands for Manipulating Cabinet Icons Table 43: Cabinet Window: Commands for Saving, Opening, and Closing Cabinet Windows Table 44: Primary Operational States and Descriptions Table 45: Fault Severity Indicators and Descriptions Table 46: Alert Notification Descriptions Table 47: Collective Management Window Description Table 48: Asset Information Dialog Box Description Table 49: Asset Information View Window Description Table 50: Asset Information View Commands Table 51: View Asset History Dialog Box Description Table 52: View Asset History Window Description Table 53: View Asset History Commands Table 54: Update Asset Information Dialog Box Description Table 55: Measurement Information Dialog Box Description Table 56: Measurement Information View Window Description Table 57: Measurement Information View Commands Table 58: View Measurement History Dialog Box Description Table 59: View Measurement History Window Description Table 60: View Measurement History Commands Table 61: Measurement Graph Dialog Box (Custom Queries): General Tab Description Teradata AWS User Guide, Release 4.5

21 List of Tables Table 62: Measurement Graph Dialog Box (Custom Queries): SQL Statement Tab Description Table 63: New Connection Dialog Box: Window Tab Description Table 64: New Connection Dialog Box: Connect Tab Description Table 65: New Connection Dialog Box: Terminal Tab Description Table 66: New Connection Dialog Box: Telnet Tab Description Table 67: New Connection Dialog Box: SSH/SFTP Tab Description Table 68: Key Generator Dialog Box Description Table 69: Client Connections Window Commands Table 70: Connections Manager Description Table 71: Teradata AWS Options Dialog Box (Tools > Options): Client Connections Window Options Table 72: Client Connections Window Display Options Table 73: FRU Replace Procedure Window Description Table 74: Firmware Version Checker Window Description Table 75: Firmware Version Checker Commands Table 76: Battery Date Information Window Description Table 77: Battery Date Information Window Commands Table 78: Set Battery Installation Date(s) Window and Set Battery Date Dialog Box Description Table 79: Resettable Components Table 80: Effects of Power Off Command on Components Table 81: Effects of Power On Command on Components Table 82: Power Cable Test Dialog Box Description Table 83: Teradata AWS: Access to CLI Utilities Table 84: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Task Tab Description Table 85: CheckBatteries and CheckFirmwareVersion Dialog Boxes: Schedule Tab Description Table 86: SCSI ID Editor Description Table 87: AWS IP Configuration Utility Dialog Box: General Tab Description Table 88: AWS IP Configuration Utility Dialog Box: Network Tab Description Table 89: AWS IP Configuration Utility Dialog Box: CMIC Addresses Tab Description Table 90: AWS Group Permissions Dialog Box Description Table 91: System Objects Manager Properties Dialog Box: System Objects Manager Tab Description Teradata AWS User Guide, Release

22 List of Tables Table 92: System Objects Manager Properties Dialog Box: Fibre Channel Switch Tab Description Table 93: Fault Notification Window Description Table 94: Alert Manager Properties Dialog Box: Alert Manager Mail Tab Description Table 95: Alert Manager Properties Dialog Box: Alert Manager Page Tab Description Table 96: Add/Remove Page Service ID Dialog Box Description Table 97: Configure Page Service Dialog Box Description Table 98: Fault Property Data in the Fault Log Table 99: Fault Manager Properties Dialog Box Description Table 100: Required Ports for AWS Web Services Table 101: AWS Services Table 102: UNIX MP-RAS AWS Commands/Functions and Windows (Teradata) AWS Equivalents Teradata AWS User Guide, Release 4.5

23 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

24 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

25 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

26 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

27 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 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

28 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

29 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 ( This product includes software developed by the Apache Software Foundation ( 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

30 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 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 Teradata AWS User Guide, Release 4.5

31 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

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

33 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

34 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

35 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

36 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

37 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 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

38 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: Note: The port number is always 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

39 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

40 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

41 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

42 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

43 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

44 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

45 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

46 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 Teradata AWS User Guide, Release 4.5

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

48 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

49 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

50 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

51 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

52 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 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

53 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

54 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

55 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

56 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

57 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

58 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

59 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

60 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

61 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

62 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

63 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

64 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

65 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

66 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 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 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

68 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

69 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

70 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

71 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

72 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

73 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

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

75 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

76 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

77 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

78 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

79 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

80 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

81 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

82 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

83 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

84 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

85 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

86 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

87 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

88 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

89 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

90 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 MessageID= 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

91 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 Sequence= 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 :44:54.0 Time stored in database is GMT TimeStamp :44:54.0 Time stored in database is GMT SubType= ConsoleLog TimeReceived > :44:54.0 TimeStamp > :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

92 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 Teradata AWS User Guide, Release 4.5

93 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

94 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

95 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

96 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

97 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

98 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

99 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

100 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

101 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

102 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

103 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

104 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

105 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

106 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 Teradata AWS User Guide, Release 4.5

107 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

108 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

109 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

110 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

111 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

112 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

113 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

114 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

115 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

116 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

117 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

118 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

119 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

120 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

121 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

122 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

123 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

124 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

125 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

126 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 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

127 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

128 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, 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

129 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

130 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

131 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

132 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

133 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

134 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 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

135 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

136 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

137 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

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

139 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

140 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

141 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

142 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

143 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

144 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

145 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

146 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

147 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 , 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

148 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 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

149 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 . 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 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 service, then the AlertRegister CLI program to specify when you will be notified of faults by . 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

150 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

151 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

152 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

153 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

154 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