Auto Service Request (ASR) v2.

7
Installation and Operations Guide

Oracle, Inc. www.oracle.com July 2010

Copyrights
Oracle Auto Service Request (ASR) Installation and Operations Guide Copyright © 2010, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services. This product includes software developed by the JDOM Project. Copyright © 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution. 3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact . 4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management. THIS SOFTWARE IS PROVIDED “AS IS”' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter and Brett McLaughlin . For more information on the JDOM Project, please see http://www.jdom.org.

ASR Table of Contents
1.0 Overview of the Auto Service Request (ASR) Software................................................................. 1
1.1 ASR Feature Summary.................................................................................................................................................... 1 1.2 ASR Architectural Summary........................................................................................................................................... 2 1.2.1 Close-Up of the ASR Manager............................................................................................................................... 3 1.3 ASR Installation Overview.............................................................................................................................................. 4 1.3.1 ASR Installation Guidelines....................................................................................................................................4 1.3.2 General Installation Considerations........................................................................................................................ 4 1.3.3 ASR Installation Milestones Summary................................................................................................................... 5

2.0 Designate ASR Systems..................................................................................................................... 7
2.1 Designate an ASR Manager System................................................................................................................................ 7 2.1.1 Size the ASR Manager System............................................................................................................................... 8 2.2 Designate ASR Asset System(s)...................................................................................................................................... 9

3.0 Validate ASR Systems...................................................................................................................... 10
3.1 Create a Sun Online Account.........................................................................................................................................10 3.2 Register/Validate Systems in the Sun Member Support Center (MSC)........................................................................ 11 3.2.1 Register for Access to the Sun Member Support Center.......................................................................................11 3.2.2 Log In to the Sun Member Support Center...........................................................................................................12 3.2.3 Validate Information in the Sun Member Support Center.................................................................................... 13

4.0 Assess ASR Systems......................................................................................................................... 15
4.1 Verify: Hardware, Solaris, Java, Network..................................................................................................................... 16 4.2 Telemetry Sources: Overview and Check......................................................................................................................17 4.2.1 Confirm Existing Telemetry Sources.................................................................................................................... 17 4.2.2 Initially Set-Up and Configure Telemetry Sources...............................................................................................17 4.2.3 ILOM General Procedures.................................................................................................................................... 18 4.2.3.1 ILOM Sideband Management Set-Up..........................................................................................................19 4.2.3.2 Set Up the Sun Server Hardware Management Pack (SHMP).................................................................... 19

5.0 Install the ASR Manager................................................................................................................. 20
5.1 Prerequisite Tasks.......................................................................................................................................................... 20 5.2 Install Sun Management Center (SunMC) Agent..........................................................................................................20 5.2.1 Download SunMC v4.0.........................................................................................................................................21 5.2.2 Install the SunMC Agent.......................................................................................................................................22 5.2.3 Install the SunMC 4.0 Add On Software.............................................................................................................. 23 5.3 Install Service Tools Bundle (STB)............................................................................................................................... 24 5.4 Check the Existence of SASM and Version.................................................................................................................. 26 5.5 Download the SASM and ASR Packages......................................................................................................................26 5.6 Install the SASM Package............................................................................................................................................. 27 5.7 Install the ASR Package.................................................................................................................................................27 5.8 Register the ASR Manager............................................................................................................................................ 28 5.9 Verify System and Activate the ASR Manager..............................................................................................................29 5.10 Crontab Set-Up............................................................................................................................................................ 30 5.11 What to Do Next.......................................................................................................................................................... 31

6.0 Configure ASR Asset(s)....................................................................................................................32
6.1 Install SunMC Agent and Service Tools Bundle........................................................................................................... 32 6.2 Obtain the ASR Asset Bundle........................................................................................................................................32 6.3 Set-Up Telemetry Sources to ASR.................................................................................................................................33 ASR Installation and Operations Guide – July 2010 iii

6.3.1 Enable SunMC Agent and/or FMA Telemetry......................................................................................................33 6.3.1.1 Command Line Options for Setting Solaris FMA and SunMC Trap Destinations...................................... 34 6.3.2 Enable ILOM Telemetry....................................................................................................................................... 34 6.3.2.1 Enable ILOM: GUI Interface....................................................................................................................... 35 6.3.2.2 Enable ILOM: Command Line Interface..................................................................................................... 36 6.3.3 Enable M-Series XSCF Telemetry........................................................................................................................38 6.3.4 Activate ASR Assets..............................................................................................................................................39 6.3.4.1 Activate Blade Assets................................................................................................................................... 40

7.0 Manage the ASR Environment....................................................................................................... 43
7.1 ASR Asset Management................................................................................................................................................ 43 7.1.1 View Status of ASR Asset(s).................................................................................................................................44 7.1.2 Generate Status Reports........................................................................................................................................ 44 7.1.3 Generate Periodic Status Reports..........................................................................................................................45 7.1.4 Create Test Alert....................................................................................................................................................45 7.1.5 Enable/Disable ASR Assets.................................................................................................................................. 46 7.1.5.1 Disable ASR Assets...................................................................................................................................... 46 7.1.5.2 Enable ASR Asset(s).................................................................................................................................... 46 7.1.6 Deactivate/Activate ASR Assets........................................................................................................................... 47 7.1.7 Add/Remove Telemetry Traps from ASR Asset(s)............................................................................................... 48 7.1.7.1 Add/Remove Telemetry Traps from SunMC and FMA Systems................................................................. 48 7.1.7.2 Add/Remove Telemetry Traps from ILOM Systems....................................................................................49 7.1.7.3 Add/Remove Telemetry Traps from M-Series Systems (XSCF)................................................................. 50 7.2 ASR Environment Management.................................................................................................................................... 50 7.2.1 Register/Unregister ASR.......................................................................................................................................50 7.2.2 Starting and Stopping ASR and SASM.................................................................................................................50 7.2.2.1 Stopping SASM and ASR............................................................................................................................ 50 7.2.2.2 Starting SASM and ASR.............................................................................................................................. 51 7.2.3 ASR Emails........................................................................................................................................................... 51 7.2.3.1 Example Heartbeat Failure Notification Email............................................................................................ 52 7.2.3.2 Example Successful ASR Test Email........................................................................................................... 53 7.2.3.3 Example Failed ASR Test Email.................................................................................................................. 54 7.2.3.4 Successful ASR Service Request Email.......................................................................................................55 7.2.3.5 Successful ASR Service Request Email: Blade Server Module...................................................................56 7.2.3.6 Failed ASR Service Request Email.............................................................................................................. 57 7.2.3.7 Fault Rules Update Email.............................................................................................................................58 7.2.3.8 ASR Successful Registration Status Email.................................................................................................. 59 7.2.3.9 ASR Incomplete Registration Status Email..................................................................................................60 7.3 ASR Network Parameters Management........................................................................................................................ 61 7.3.1 ASR Port Usage.................................................................................................................................................... 61 7.3.2 Changing the Default SNMP Port for ASR...........................................................................................................61 7.3.3 Configure ASR to Send HTTPS Traffic Through a Proxy Server........................................................................ 61 7.3.4 Confirm SASM Network Settings........................................................................................................................ 62 7.3.5 Test Connectivity from the ASR Manager to Sun.................................................................................................62 7.4 ASR Integration with Enterprise Monitoring Systems.................................................................................................. 63 7.4.1Configuring Trap Files........................................................................................................................................... 64 7.4.2MIB Location and Data Elements..........................................................................................................................64 7.5 ASR Diagnostic Utility.................................................................................................................................................. 65 7.5.1 Delivery Model..................................................................................................................................................... 65 7.5.2 Configure the ASR Diagnostic Utility.................................................................................................................. 66

8.0 ASR General Troubleshooting........................................................................................................ 67
8.1 Service Tools Bundle Troubleshooting (STB)...............................................................................................................67 8.1.1 Check the STB Agent............................................................................................................................................68 8.1.2 Check the Service Tags Version............................................................................................................................ 68 8.1.3 Check Service Tags Probe.....................................................................................................................................68 ASR Installation and Operations Guide – July 2010 iv

........................................................................................................................................................................ 76 8.................73 8...2 ASR Systems Tracking Form......................... 73 8....................................1..................................1........................................................................5 Unable to Contact Service Tags on Asset..............................................4 Check Service Tags Listener...................1 Installation Parameters Form.......6 Uninstall ASR.................................................................... Move Assets to a New ASR Manager..........8.......................................2 Set Log File Counts.......................................................4 ASR Log Files...........................................5 Error Messages and Resolutions....................................75 8.............. 75 8...... 71 8................................................................1 Error Messages and Resolutions......8 stdiscover or stlisten Services are Disabled........1.............................................................................................78 9...................................................................................................................... 72 8.......................................................................................1..................................................... 70 8...............................................4.....................................................................................71 8..........................................................................................................................................3 Check the State of ASR Bundles..............................................................9 ASR Manager Crashed.................................................................70 8..........72 8..................................................................................................................................................................2 Check the State of the SMA Service...................2 Only One Client Can Access Console at a Time..5.......... 74 8................................................................ 79 ASR Installation and Operations Guide – July 2010 v .............................................73 8........................................................................................................8 ASR Fault Rules Updates...........7 Upgrade ASR.....77 9.............1............6 Service Tags on Asset Reports Unknown or Empty Serial Number/Product Name................................................69 8.............................. 78 9..................................................7 Activation Failed for Asset <asset name> Due to Data Error.................................................5.....1 Set Log level....................................................................................................................................................0 Installation Aids – Forms...........................................4......................... 69 8...... 76 8.................................................................................................................

and other internal Sun hardware components. Sun systems filter the data again to confirm the reality of the fault and then automatically generates a Service Request (SR). scalable.3 ASR Installation Overview 1. The fault telemetry sent to Sun includes specific hardware faults. Once created.1 ASR Feature Summary ASR provides the following features: • Telemetry Collection and Forwarding—ASR collects specific hardware telemetry data from all ASRenabled Sun systems. http://www.2 ASR Architectural Summary 1.0 Overview of the Auto Service Request (ASR) Software Welcome to the Auto Service Request (ASR) software from Oracle. CPUs. If your qualified Sun system is under warranty or covered by a service plan. ASR filters this telemetry data and forwards what it determines to be potential hardware faults directly to Sun. you are entitled to ASR at no charge. Before beginning the installation. reducing both the number of phone calls needed and overall phone time required. To see which Sun systems are qualified for ASR. ASR is designed to enable faster problem resolution by eliminating the need to initiate contact with Oracle for hardware failures. disks. review the following topics in this section: • • • 1. Support Response—Service Requests are actively reviewed by Oracle and service response is provided in accordance with your Oracle Premier Support or Oracle/Sun Limited Warranty contract. This document provides complete instructions to install the ASR software. SRs are sent to Oracle and also communicated.CHAPTER 1 1. memory. to the support contact of record for the Sun system reporting the fault.com/service/asr Note – ASR is not a monitoring solution and is not a substitute for the normal monitoring processes/services that customers have. ASR also simplifies support operations by utilizing electronic diagnostic data. called ASR Assets. go to the URL below and click on the “Sun Systems Qualified for ASR” link. • • ASR Installation and Operations Guide – July 2010 1 .1 ASR Feature Summary 1. Automatic Creation of Service Requests—Once fault telemetry is sent to Oracle's ASR infrastructure. The ASR fault coverage is different for each qualified Sun system type. ASR is a secure. Hardware faults can range from fans. but also includes the conditions that may later result in a component failure. to power supplies. customerinstallable software feature of Oracle Premier Support for Systems and Oracle/Sun Limited Warranty support that provides auto-case generation when specific hardware faults occur.sun. via e-mail.

The reasons to do this may be to support a large amount of ASR Assets and/or for organizational reasons. The ASR Manager filters the incoming data and forwards potential fault telemetry to Sun/ASR Backend systems. or if you already have some familiarity with the ASR software. ASR Manager—The ASR Manager is a qualified Sun system that centrally ingests hardware telemetry data sent from a group of ASR Assets.2 ASR Architectural Summary Whether this is a new installation of ASR. ASR Assets—ASR Assets are qualified Sun systems that are configured to report its hardware telemetry to an ASR Manager. The following diagram shows the end-state environment once ASR is installed. 2. it is highly recommended that you review the ASR architecture discussed below. This way.1. Customers have the option to install more than one instance of an ASR Manager. as does an ASR Asset. such as grouping ASR Assets by data center. • ASR Installation and Operations Guide – July 2010 2 . The ASR Manager system is installed as an ASR Asset. the ASR Manager system can report its hardware telemetry. Use the numbered indicators in the diagram to review it in sequential order and for corresponding explanations in the text that follows. An ASR Asset communicates its telemetry to one ASR Manager only. Understanding the architecture and the nomenclature of ASR is key to a successful installation. 1. subnet. support group. or other grouping scheme as desired by the customer. Additional features of the ASR Manager include the following: • • The ASR Manager is always installed first. followed by ASR Assets.

• The telemetry data that is sent from the ASR Manager to the Sun/ASR Backend Systems is encrypted. From there. Oracle Support Interaction—Once a Support Engineer begins working on the Service Request. For more information on this topic. Order and ship a replacement part to the customer site to be installed by a Sun Field Engineer.sun. • 3. In addition to ASR. Sun/ASR Backend Systems—The ASR backend infrastructure at Sun collects all telemetry data forwarded to it from the ASR Manager. At the same time. SASM is an applications environment that manages various plug-in applications used mainly for systems level management. an email notification of the Service Request is sent to the customer’s support contact of record associated with the system reporting a fault. SASM simplifies different Sun Network Service deployments and provides a secure transport mechanism for telemetry data. also called a case. The Service Request is handled in accordance with the asset’s SunSpectrum or Warranty contract.2. • 4. and other plug-ins on a Sun system. examples of other SASM plug-in applications include SFT (Sun Secure File Transport) and others. the following actions occur: • A Service Request. 1. the engineer may collect additional information from the customer to better determine resolution to the hardware issue. or ASR Managers if multiple instances are installed. The diagram below shows the relationship between ASR. The fault rule technology on these backend systems ascertain the reality of the fault telemetry. and forwards recognized faults to Sun’s Service Request system. refer to the ASR White Paper at: http://www.com/service/asr Refer to Close-Up of the ASR Manager for more information on the ASR Manager system. These are called Customer Replaceable Units (CRUs). ASR Installation and Operations Guide – July 2010 3 . SASM. Resolution to the issue may involve system configuration or the following possibilities: • • Order and ship a replacement part with installation instructions to the customer.1 Close-Up of the ASR Manager The ASR Manager software runs as a plug-in application to the Sun Automated Service Manager (SASM) software. is created and sent to Oracle where it is assigned to a Support Engineer. These are called Field Replaceable Units (FRUs).

This document makes every attempt to accommodate these differences.com/service/asr • • Operating System Version—The operating system version may impact the ASR installation. ASR Installation and Operations Guide – July 2010 4 .2 General Installation Considerations The ASR installation process may vary given the differences across computing environments. refer to 1. on page 78 to keep track of various credentials and parameters used throughout the installation. For more on the roles of these ASR components.3. go to the URL below and click on the “Sun Systems Qualified for ASR” link.3. To view the supported platforms now.1 • ASR Installation Guidelines Keep the following guidelines in mind when installing ASR: Installing ASR consists of installing an ASR Manager followed by ASR Assets. 1. • • 1. http://www. Existing Hardware Telemetry Sources—The existing telemetry sources on Sun systems may impact the installation of ASR. This document provides the platform criteria for ASR installation. but it is helpful to be aware of the following considerations that may alter the process: • Hardware Platform—Some Sun hardware may not support the installation of ASR.sun.1 Installation Parameters Form.3 ASR Installation Overview This section summarizes the ASR installation process so that customers are better prepared to install ASR.2 ASR Architectural Summary. In some cases. ASR Assets can be added or removed as needed. telemetry software must be installed and/or upgraded.1. on page 2. Once the ASR Manager is installed. Installers are highly recommended to use the 9. The ASR Manager system is always installed first. as some platforms may require a Solaris update and/or a patch upgrade. Installers of ASR should have systems administration experience and some measure of support responsibility for the Sun systems where ASR is to be installed.

to ensure the proper routing of Service Requests. and support contacts in the Sun Member Support Center database. ASR relies on the accuracy of this data to verify service entitlement. installers will have to correct it. • 2. 1. • 1. they can contact Sun Support Services or their Sun account team for assistance. they will have to obtain access to these systems. Designate ASR Systems and Validate ASR Systems. 5 ASR Installation and Operations Guide – July 2010 . If this data is inaccurate. If installers do not have access to these systems. on page 7. This milestone determines which host system will have the ASR Manager installed. Accuracy of Data in the Sun Member Support Center Database—A key task to installing ASR involves validating Sun hardware serial numbers. This milestone also consists of determining which systems will be installed as ASR Assets and ensures that they too are qualified for ASR.3 ASR Installation Milestones Summary Review the diagram below and the text that follows to better understand the ASR installation process: The explanations below correspond to the numbered items in the diagram.3.• Access to Sun Online Systems—If installers do not have access to a Sun Online Account and to the Sun Member Support Center. contract levels. It includes sizing the system and ensuring it is qualified for ASR.0 Designate ASR Systems. and to ensure the correct support personnel are contacted when specific Sun systems send fault telemetry. These instructions explain this process.

This information includes Sun hardware serial numbers. on page 15. for example. The last milestone to installing the ASR environment is to configure ASR Assets and validate the installation. This milestone. ASR Installation and Operations Guide – July 2010 6 . on page 20. This may include the Service Tools Bundle (STB).0 Assess ASR Systems. are the quickest parts to the overall installation. and support contacts. • • 3. Proceed to section 2. 2. Items reviewed include an OS version check. JDK version check. the ASR Manager can be installed. JDK updates.0 Designate ASR Systems to begin the ASR installation. This milestone includes installing supporting software that may be required for ASR. contract levels.0 Validate ASR Systems. along with installing ASR Assets. 6. 4. and network configurations if required. This milestone involves accessing the Sun Member Support Center and validating/updating key information in its database. Configuring ASR Assets may involve installing supporting software.0 Install the ASR Manager. This milestone involves assessing the state of the systems designated for ASR installation. such as the Service Tools Bundle (STB) and Sun Management Center (SunMC).• 3. depending upon your Sun platform. on page 10. • • 4. and to confirm the specific hardware telemetry sources installed on the systems. on page 32. this milestone involves installing OS patches. a check of proper network connectivity. Depending on the results of the systems assessment. Once the above milestones are complete. 5.0 Configure ASR Asset(s).

go to section 2. repeat the instructions on section 2. it is important to understand the difference between an ASR Manager and an ASR Asset system. From the Qualified Systems List.1 Designate an ASR Manager System Use the following procedure to designate an ASR Manager system.sun. Go to 2.1 Designate an ASR Manager System. select another system that is on the list to be your ASR Manager. If you have already installed an ASR Manager and are now installing ASR Assets.com/service/asr 3. 4. If the system you selected to be an ASR Manager is under-sized. or upgrade the current system. depending on how many ASR Asset(s) will report their telemetry to the ASR Manager. Size the system using the following steps: • • • Establish roughly how many ASR Assets will report their hardware telemetry to the ASR Manager system now and in the future. and are installing another ASR Manager for another group of ASR Assets. http://www.1 Designate an ASR Manager System.1. If you have not installed an ASR Manager. 2. This process involves sizing the systems and making sure all the systems are qualified for ASR. ASR Installation and Operations Guide – July 2010 7 . If you have already installed an ASR Manager and a group of ASR Assets. on page 8 to confirm the system requirements. Go to the URL below and click on the “Sun Systems Qualified for ASR” link.1 Size the ASR Manager System. on page 2. This system does not need to be a dedicated server and can co-reside with other applications and services. consider the following options: ◦ Select another system that is better sized. 2. Proceed to one of the following options.2 ASR Architectural Summary. Choose a Sun system that you intend to install as the ASR Manager.CHAPTER 2 2. if needed. To use these instructions. Refer to 1. depending upon your circumstance: • • • The ASR Manager is installed first before ASR Assets. 1. If not.0 Designate ASR Systems This section explains how to initially designate which system will have the ASR Manager installed and which systems will be installed as ASR Assets. Qualify the system. go to section 2.2 Designate ASR Asset System(s). confirm that your Sun system is on the list.

2. you will have to consider installing an additional instance(s) of the ASR Manager to accommodate the remaining ASR Assets. more if extra capacity is required. on page 79. 3 PCIe Number of CPUs: 2 T2 Units for the first 500 assets.6 GHz Up to 128 GB memory. Once the ASR Manager is qualified and sized. Return to the following steps once the above tasks are complete. 2. depending upon how many ASR Assets will be installed. more if a customized database is required Network components: Minimum of 110/100/1000 Ethernet ports. 4 MB Level 2 Cache Up to four 32-GB 2.◦ Reduce the number of ASR Assets that you will associate to this ASR Manager system. DDR2 667 memory 6 MB L3 Cache per processor 4 x 146 GB 10000 RPM SATA disks 4 x 10/100/1000 Ethernet ports. Use your own mechanism for tracking this information or use the section 9.5” SATA solid-state drives.5” SATA solid-state drives. 1 T2 Unit for each additional 500 assets Memory size: 1 GB minimum for each 200 requests/minute or a minimum of 2 GB Storage requirements: Minimum of 180 GB disk. Sun SPARC Enterprise T5120 server Sun Fire X4140 server Class 3: Large (Greater than 2000 assets) For this class. • ASR Installation and Operations Guide – July 2010 8 . up to 1.1 Size the ASR Manager System The following hardware requirements are suggested for the ASR Manager. Then proceed to section 3. 4 MB Level 2 Cache Up to four 32-GB 2.2 ASR Systems Tracking Form. record the hostname and hardware type. up to 1. If you choose this option.1.2 GHz 8 GB (4 x 2 GB DIMMs). Class Class 1: Smaller (Less than 500 ASR assets) Class 2: Medium (500 to 2000 ASR assets) Server Recommendation Sun SPARC Enterprise T5120 server • • • • • • • • • • • • • • • Specifications One UltraSPARC T2 multicore processor.6 GHz Up to 128 GB memory. on page 10. careful professional sizing is recommended. • 5.0 Validate ASR Systems. 4 x 10/100/1000 Ethernet ports 1 six-core AMD Opteron – Model 2427. 4 x 10/100/1000 Ethernet ports One UltraSPARC T2 multicore processor. Focus on the first ASR Manager and its associated ASR Assets before installing additional ASR Manager instances.

go to 1. 1. E12K. it is important to understand the difference between an ASR Manager and ASR Asset systems. If you have not completed the installation of the ASR Manager. Qualify the system.sun. on page 2. Sun SPARC Enterprise T5120. Note: The ASR Manager system is always installed first. Sun Blade X6240. SunFire V490.com/service/asr 3. Once the ASR Asset system(s) are qualified.2 ASR Systems Tracking Form on page 79.0 Validate ASR Systems. 5.2. http://www. etc. 4. From the Qualified Systems List. To use these instructions. confirm that your Sun system is on the list. Proceed to section 3. ASR Installation and Operations Guide – July 2010 9 .2 Designate ASR Asset System(s) Use the following procedure to designate ASR Asset system(s).2 ASR Architectural Summary. Refer to 1. Go to the URL below and click on the “Sun Systems Qualified for ASR” link.).3 ASR Installation Overview. if needed. Use your own mechanism for tracking this information or use the 9. on page 4. record the hostname(s) and hardware type of each. If not. the system is not yet qualified to run ASR. 2. Choose the Sun systems that you intend to install as ASR Assets and make note of the hardware type of each (for example. on page 10.

on page 7. 3. make sure you are logged into the Sun Online web site. ASR Installation and Operations Guide – July 2010 10 .0 Validate ASR Systems To install ASR. on page 10. Note: If your organization does not have access to the Sun Member Support Center. installers must access Sun Online systems and validate key information about the systems targeted for ASR installation (for example. on page 11. if the registration details are not submitted completely. Select the Log In link at the top of the page. the systems targeted for ASR installation must already be qualified and sized as described in the previous section 2. (Note: You will receive a “Registration Incomplete’ status email notification. If the login does not work. serial numbers).com 2.) Once registered. Installers must access the Sun Member Support Center in order to validate Sun serial numbers.CHAPTER 3 3.sun. go to same URL above and follow the links to register.1 Create a Sun Online Account Use the following instructions to create a Sun Online account. https://reg. 3. contract levels. 3. and support contacts for the systems targeted for ASR installation. This account is required to register and access the Sun Member Support Center. The instructions in this section involve completing the following two tasks: • • 3. and support contacts for the systems targeted for ASR installation. See step 1 above. This account is required to register and access the Sun Member Support Center. If you already have a Sun Online account.1 Create a Sun Online Account. 1. Before continuing. please contact your Sun account team or Sun Support Services for assistance in providing the information needed to validate Sun serial numbers. or if you do not have a Sun Online account.2 Register/Validate Systems in the Sun Member Support Center (MSC). go to the URL below and log in.0 Designate ASR Systems. contract levels.

If not logged in already to your Sun Online account.1 Register for Access to the Sun Member Support Center Use the following procedure to register for access to the Sun Member Support Center. go to section 3. Before continuing. Keep track of your login credentials for future use. Once you have established the Sun Online account. 6. • • If you have an established Sun Member Support Center login for yourself or your organization. Once logged in. on page 12. if needed. Click on the drop-down menu at the Welcome [customer_name] link and select Manage My Account to change any information.2. or Sun Support Services to obtain this information.4. contract levels. Select the Log In link at the top of the page. Sun Account Manager. https://reg.2 Log In to the Sun Member Support Center. confirm that the information listed below is valid.sun. select Member Support Center from the Support Resources section of the page.2 Register/Validate Systems in the Sun Member Support Center (MSC). proceed to Register for Access to the Sun Member Support Center. as discussed in section 3. While logged into the Sun Online web site.2. ◦ ◦ ◦ ◦ ◦ ◦ Company name Street address City Province/Postal code Country Contact telephone number 5. and support contacts for the systems targeted for ASR installation. 3. go directly to section 3. For all other circumstances. go to the following URL to log in. ASR Installation and Operations Guide – July 2010 11 . If needed. consult your local System Administrator.com 2.2 Register/Validate Systems in the Sun Member Support Center (MSC) Use the instructions in this section to access the Sun Member Support Center in order to validate Sun serial numbers.1 Create a Sun Online Account. 1. This information is typically sent with your Sun welcome kit. on page 10. Obtain the Contract ID and/or the Party ID under which your Sun hardware is registered. review the following prerequisites: • • You must have a login to a Sun Online account before continuing. 3. This information is used by ASR.

1 Create a Sun Online Account. 5. on page 10 for more information.2 Log In to the Sun Member Support Center Use the following procedure to log in to the Sun Member Support Center. Log in using an established Sun Member Support Center login for yourself or your organization. go to the following URL: http://sun. Do not continue with the installation until you have approved access to the Sun Member Support Center. 12 ASR Installation and Operations Guide – July 2010 . Once you complete and submit the registration.2.com/support 2. You will log in using one of these two methods: • • 1. continue to Log In to the Sun Member Support Center. Once obtained. 4. From the Support menu at the top of the screen. Log in using your Sun Online account that has been registered and approved to access the Sun Member Support Center. In a browser window. Contact your Sun Account Manager for assistance. From the top of the page.3. Contact Sun Support Services for assistance. select the Member Support Center. you may have to wait for a period of time for Sun Support to respond and approve your registration. select Register and complete the following information. if needed. See section 3. Ways to accelerate this process include the following options in order: • • • Consult a local System Administrator who may have approval authority for the Sun Member Support Center. 3.

select the Global Search tab. If the serial number is found. • Contact your Sun Account Manager. Note: If the serial number is not found. If you are installing ASR Asset(s). Then. which is installed first. select the Log In link. From the Sun Member Support Center. It is possible that the serial numbers have not been entered or were entered incorrectly into Sun’s database. If such mechanisms are unavailable. you need to acquire the serial numbers for each. the Sun system is displayed as shown below. on page 79 to track your ASR systems. enter the serial number of the system targeted for ASR installation and click Search. a primary MSC user for your organization will need to approve your request.3 Validate Information in the Sun Member Support Center Use this section to access the Sun Member Support Center in order to validate Sun serial numbers. and support contacts for the systems targeted for ASR installation.2. 4. For convenience. you can use the 9. contact Sun Support Services or your Sun account team for assistance before proceeding. contract levels. you need to provide an Organization ID. and to ensure that the correct support personnel are contacted when specific Sun systems are sending fault telemetry. Review the following information: • If you are installing the ASR Manager. 6. you must physically obtain the serial number for the Sun system(s) targeted for ASR installation by finding it on the system chassis. or if you discover that multiple serial numbers are not found. it is recommended that you acquire the mechanism used to track your Sun systems and their serial numbers. After logging in. Be sure that you are logged in to the Sun Member Support Center. you will have to correct it. If this data is inaccurate.3. you need to acquire the serial number for this system only. 2. From the Member Support Center. From the Install Base portion of the screen. as described in the previous instructions. continue to Validate Information in the Sun Member Support Center. This could be a spreadsheet or other internal inventory tool. 4.2 ASR Systems Tracking Form. At this time. If this is the first time you are accessing the Member Support Center. • 3. 3. 1. 5. If you do not know your Organization ID or primary MSC user. 5. contact the following resources to resolve the issue. Log in using your known credentials or use your Sun Online account credentials. ASR relies on the accuracy of this data to verify service entitlement. or: • Contact Sun Support Services ASR Installation and Operations Guide – July 2010 13 . to ensure the proper routing of Service Requests.

10. In the Classification column. ASR Installation and Operations Guide – July 2010 14 . enter a partial name and use the wildcard (%) to substitute for the rest. 12. 3. From the Contracts screen.0 Assess ASR Systems. 15. A customer with a Sun Online Account registers with the MSC using the Party ID for their organization. This classification is essential as Service Requests created from ASR will get sent to the Primary and Preferred contact associated with this Sun system. contact your Sun Account Manager or Sun Support Services for assistance. 7. Click the Update button. If not. 8. The typical approach to add contacts is as follows: 1. choose the appropriate one. In the Contact Name column. select Contracts. Note: Once the initial contact is updated as the Primary and Preferred. The new user can then be selected as a Contact. on page 15. confirm that an active Sun warranty or Sun Spectrum support contract is associated with the Sun system. click on the Contacts option from the left-side menu. Click on the system listed in the Description column. ASR requires that the system has an active Sun warranty or Sun Spectrum support contract. After validating the contract information. go to chapter 4. Note: If you are having issues setting contacts. Click Go. choose Primary and Preferred in the drop-down list. all Sun systems under the same Contract ID will be updated with this contact. choose Technical in the drop-down list. contact Sun Support Services or your Sun Account team for assistance. If more than one name is displayed. 11. 9. enter the name of the person in your organization that should be the contact for Service Requests created by ASR. 2. After successful completion of searching serial numbers and verifying contracts and contacts. 13. Alternatively. A primary user for the organization approves the new user in the MSC.6. From the left-side menu. In the Contact Type column. 14.

and ASR Manager and Asset(s) network configurations. An assessment of your operating system version. Java. Continue with the following procedures in order: • • 4. Note: The instructions in this section apply to both the ASR Manager and ASR Assets. and available telemetry sources is necessary to determine if any of these items need upgrading or other configuration to support the ASR installation.. network setup.CHAPTER 4 4. ASR Installation and Operations Guide – July 2010 15 . 4.0 Assess ASR Systems Use the procedures in this section to assess the state of your Sun systems’ environment for the ASR installation. Solaris.1 Verify/Check your hardware. on page 17.2 Telemetry Sources: Overview and Check.

Africa) Or you can test your connection in a terminal window: • telnet transport. using port 6481. Network Check/Verify Hardware Parameters Only the hardware listed on the Sun Systems Qualified for ASR page is supported. Solaris Solaris 10.sun.3.com If you receive a “connected” message. go to: • https://transport. Check and make note of the ASR Manager IP address: ifconfig -a Test the connection to Sun. Middle East. supported version of Java.0_xx Warning! Do not use JDK 1.sun.0_17. See section 3. 2. ASR Manager Network Connection The ASR Manager System must have an internet connection – either a direct connection or through a proxy.5. Action Visit the Sun ASR product page and click the “Sun Systems Qualified for ASR” link to see the list.5.x Manager systems require at least JDK 1.5.2 Register/Validate Systems in the Sun Member Support Center (MSC) on page 11. via http. Solaris. check with your network administrator to collect information needed to configure the ASR Manager system.com:443 (North/South America. Qualified hardware must be registered with the Sun Member Support Center.6.0_14 • JDK 1. ASR Installation and Operations Guide – July 2010 16 .5. such as Blade systems and some T and X-series systems. These will be required for ASR installation ASR Asset Network Connection Contact your network administrator to confirm or enable the following: 1.sun.sun. visit SunSolve Online (login required). Java.co.2. In a browser.0_04 or later (see JDK 6 on the Java SE Downloads page).0_16 • JDK 1. refer to section 7. on page 61. or later is supported for ASR.5.1 Verify: Hardware. Java ASR 2. Ensure that ASR Assets can send SNMP telemetry data out on port 162 to the ASR Manager. verify your patch level: patchadd -p|grep patch number To download any required patches. 3.4.6. Check your Java version: java -version Visit the Java SE Downloads page to get the latest.uk:443 (Europe.0_15 • JDK 1. Previous versions of the ASR Manager systems required specific versions of Java: • JDK 1.com 443 • /usr/sfw/bin/wget https://transport. the connectivity is successful. obtain the service processor and/or the chassis IP address. Ensure that the ASR Manager can communicate with ASR Assets. Check and make note of the ASR Asset IP address: ifconfig -a If working with a system that has a service processor. This version of Java is required for SASM 1.1 ASR Port Usage. Update 6 (10u6). Asia) • https://transport. Set-up firewall rules to allow bi-directional SNMP/UDP traffic to traverse between ASR Assets and the ASR Manager. Check your Solaris version: cat /etc/release If the “Sun Systems Qualified for ASR” list indicates a particular patch version. You will need to know: • Proxy server name • Proxy port number • Proxy user name • Proxy password • NTLM Domain Name (if applicable) • NTLM Host Name (if applicable) • SASM Host Information (if applicable) For an explanation of the network ports used by ASR. If you access the internet through a proxy.

ILOM. and others reside on the host itself.1 Confirm Existing Telemetry Sources Use this section to determine the existing telemetry sources on your Sun system. 17 ASR Installation and Operations Guide – July 2010 .. For example. 1. the telemetry source requires a dedicated network connection (for example.). continue to chapter 5. the Sun SPARC Enterprise T5000 series requires that either ILOM or SunMC be used as the telemetry source. make a note of the telemetry sources and requirements.0 Install the ASR Manager. If you have ILOM telemetry. Initially Set-Up and Configure Telemetry Sources.2 Telemetry Sources: Overview and Check An integral component to ASR functionality is the hardware telemetry sources resident on your ASR Assets.2 Initially Set-Up and Configure Telemetry Sources This section defines all possible telemetry sources that could exist on your system. In the columns titled Telemetry Source on: SERVICE PROCESSOR and Telemetry Source on: HOST.2. the telemetry software must be upgraded for ASR. If the telemetry sources have a Note indicator. If ILOM is not applicable to you. you will see the telemetry sources that are on your system. Refer to the Solaris Version Check table. Your specific telemetry sources should already be known. as explained in the previous section 4. FMA. some telemetry sources reside on a service processor (dedicated hardware). In some cases. XSCF. if necessary. and then continue to Initially Set-Up and Configure Telemetry Sources. Find your hardware platform in the tables.1 Confirm Existing Telemetry Sources. 4.2. on page 20. 4.com/service/asr 2. Make a note of the telemetry sources on your system for later use in the installation process (for example. Use this procedure to determine what telemetry sources exist on your hardware.sun. on page 16. go to the ILOM section in the list below and follow the specific ILOM instructions. ILOM-enabled systems). some configuration or updates may be required.4. As stated previously. not both. In some cases. Proceed with the installation by continuing to the following sections in order: • • Confirm Existing Telemetry Sources. 6. etc. Depending upon your Sun hardware type. you will have one or more hardware telemetry sources resident on your system. In other cases. As indicated. Sun Management Center Agent (SunMC): SunMC provides power and environmental fault information from the host for some servers and from the system controllers of some high-end servers. or you have completed the ILOM instructions. collects potential fault data. It is also common for some systems to have multiple telemetry sources. and forwards it to Sun for the automatic creation of Service Requests. on page 17. 4. Go to the URL below and click on the “Sun Systems Qualified for ASR” link: http://www. review the note at the bottom of the table and make note of the requirements for that telemetry source. ASR connects to these telemetry sources. 1. Keep the following in mind: • • • Any Solaris operating system or patch requirements should have been completed. 3. multiple telemetry sources cannot run together on the same system.2. 5. Based on what telemetry sources exist on your system.

X4270. Use ssh to the IP address of the ILOM network interface and log in as root. ILOM is the recommended option.com/documentation 1.1 ILOM Sideband Management Set-Up. As a result. For X2270.2.2. When complete. thus eliminating the need for the physical connection to the ILOM Net Management ports. The instructions provided here are summarized for your convenience.3 ILOM General Procedures If you have determined that the ILOM telemetry source is required for ASR. isolates. on page 19. you cannot run both SunMC and ILOM as your telemetry sources. go to chapter 5. but it is routed through one of the Gigabit Ethernet ports (NET 0-3). return and continue with the following instructions. ILOM can be connected using Sideband Management. Make note of the telemetry source you select for this system for later use in the ASR installation. • ASR Installation and Operations Guide – July 2010 18 . ssh IP_Address_of_ILOM_Interface • Run the following command: show /SP or version 2. it must be upgraded to 2. on page 18 and return to these instructions. and X4275 systems.3 ILOM General Procedures. ILOM reports power and environmental problems as well as CPU and memory faults on certain servers.0 Install the ASR Manager.sun.0. memory. go to 4. Confirm the ILOM version. 4.2. You must choose one. For complete details on configuring ILOM. If you know that ILOM is already set-up and connected to the network. and recovers from many hardware and application faults. configuration.3. business-critical applications and essential system services can continue uninterrupted in the event of software failures. XSCF regularly monitors server components including CPU. X4170. disks. and telemetry reporting. • • • A network connection must be made from the Net Management port on the system’s service processor (SP) to the network. go to 4. An IP address must be assigned to the Net Management port. Otherwise. refer to your ILOM documentation or the following URL: http://www. If you want to configure your ILOM system for Sideband Management. and even software misconfiguration problems. Solaris 10 Fault Management Architecture (FMA): FMA is a capability in Solaris 10 that automatically diagnoses. continue to the next step. Obtain and make note of this IP address for later use in the installation. fan rotation and device temperatures. If the version is 1. 3. use the following procedure to set-up and/or confirm your ILOM configuration.0. ILOM Sideband Management allows the same ILOM IP address to be used. Integrated Lights Out Manager (ILOM): ILOM is embedded into some Sun platforms and comes with dedicated network and serial ports to provide remote management. major hardware component failures. When complete. ILOM requires a network connection/route to the ASR Manager system. continue with the tasks below. • • 4.2. M-Series Extended System Control Facility (XSCF): XSCF incorporates a service processor separate from all other processors. • If your system is a T5xxx series. To confirm your ILOM set-up.

1.2. The SP Network Management Port /SYS/SP/NET0 is the default setting. 3. but it is routed through one of the Gigabit Ethernet ports (NET 0-3). and X4275 systems.com/documentation 4. and the dropdown list allows the user to change to any of the four Gigabit Ethernet ports /SYS/MB/NETx.3. Note: The SHMP for ASR is only available for certain systems using Solaris 10. Before you begin: Make sure to set the port to a connected and configured Gigabit Ethernet port. 1. X4270. Refer to this document and its companion documents (Sun Server Management Agents User's Guide and Sun Server CLI Tools and IPMItool User's Guide) for more information.0. X4170.2. 4. Included with the software bundle. upgrade it now to 2. The host must be activated for ASR and trap destinations configured. Download the Sun Service Hardware Management Pack from the Download Center.0 using your ILOM documentation.3. Click Save for the changes to take effect. thus eliminating the need for the physical connection to the ILOM Net Management ports. 2.0 Install the ASR Manager. Note: Connection to the SP using ssh or the web interface may be lost during configuration of Sideband Management. Select the ILOM Sideband Management Port by using the drop-down list to activate the desired management port.3. If the product version is 1. When you have confirmed that ILOM is enabled and properly networked. ASR Installation and Operations Guide – July 2010 19 .sun. Select the Configuration tab and then the Network tab. Refer also to the following URL: http://www. continue to chapter 5. For more information about specific systems check the Sun Products Qualified for ASR page. . the Sun Server Hardware Management Pack User's Guide contains the latest instructions for setting up SHMP on your Solaris 10 system. 4.2 Set Up the Sun Server Hardware Management Pack (SHMP) The Sun Server Hardware Management Pack (SHMP) allows ILOM events to be ported through the network connection of the host.xx. where x is 0 to 3. ILOM Sideband Management allows the same ILOM IP address to be used.1 ILOM Sideband Management Set-Up If desired. Log into ILOM using the web interface. ILOM is typically configured using its own IP address and network connection. 2. This can only be done on X2270. use the following instructions to set-up an ILOM system for a Sideband Management connection. 4. You can verify the mac address by running ifconfig -a on the host and matching it to the correct Gigabit Ethernet port.

Only the SunMC agent is required. 6. The system serial number must be in the MSC database. 8.1 Confirm Existing Telemetry Sources. Install Service Tools Bundle (STB). the following tasks should already be complete before the ASR Manager is installed: • • • Create a Sun Online Account. on page 15 (OS version check. To begin. you should have already determined if SunMC is a telemetry source on your specific hardware platform. Register/Validate Systems in the Sun Member Support Center (MSC). 1. 4. and an assigned technical contact. skip this section and go to chapter 6. Download the SASM and ASR Packages. As discussed in section 4. on page 17. continue with the following steps to determine if installing SunMC is required. 2. 5. on page 24. on page 10. ASR Installation and Operations Guide – July 2010 20 . Install the SASM Package. network validation. 5. Note: If you have ILOM telemetry on the system. If you plan to use ILOM telemetry.1 Prerequisite Tasks If you have followed these instructions from the beginning. Keep in mind that the ASR Manager must be installed first before ASR Assets. 1. on page 11.2. Crontab Set-Up. 7.CHAPTER 5 5. Installing the ASR Manager consists of the following tasks. Note: The SunMC server is not required for ASR. Verify System and Activate the ASR Manager. Register the ASR Manager. Install the ASR Package. go to section 5. verify existing telemetry sources). you are highly recommended to use that telemetry source instead of SunMC.3 Install Service Tools Bundle (STB). 5.2 Install Sun Management Center (SunMC) Agent Use this section to install the Sun Management Center (SunMC) agent. If installing ASR Assets. 9. Check the Existence of SASM and Version. Assess ASR Systems.0 Configure ASR Asset(s). 3. on page 32.0 Install the ASR Manager This chapter explains how to install the ASR Manager. Install Sun Management Center (SunMC) Agent. have an active contract. JDK version check.

If SunMC is not a telemetry source for your hardware platform. 3. go to section 5. Go to http://sun. pkginfo -l SUNWescom 4. on page 22. 2. 2. skip this section and proceed directly to section 5. select on the link to download the patch.2. on page 22.com/sunmanagementcenter From the Get It tab.0 installed. If you do not have SunMC installed. If you have version 3. 2. Use your Sun Online Account. go to Download SunMC v4. download the file to another machine and copy it to the machine where ASR is to be installed. Install the patch as directed using the displayed patch information page. 4.0 installed. 4. Select the Patch Finder link from the Patches and Updates portion of the screen. select the SunSolve Knowledge Base link.0. use your Sun Online Account. and log in if required. This system type requires SunMC version 4. 3. Log in to the system and install patch 123923-02 using your patch update policies.2 Install the SunMC Agent. If you do have SunMC v4.6.0. 5. on page 24.0.0 in order to use ASR. Search for patch number 123923-02.6.3 Install Service Tools Bundle (STB). From the patch information page. • 1. go to Download SunMC v4.2. the next step is to determine what version of SunMC you have. 5. • • • If you do not have SunMC v4. 3. Select the platform and language. select the Download button for Sun Management Center. Once completed go to 5. 5. ASR Installation and Operations Guide – July 2010 21 . If prompted to log in. use one of the bulleted instructions below: • If you have a Txxxx system: 1. log in as root and go to: http://sun. 6. From the machine where ASR is to be installed.2.2 Install the SunMC Agent. Run the following command to determine the SunMC version. This is necessary to determine if an upgrade is required.2. below.0.1: If you have a version that is not 3.0 Use the following instructions to download SunMC v4.1 1.0. go to 5. If you have version 4. Depending whether you have SunMC installed and which version of SunMC you have. If SunMC is a telemetry source for your hardware platform.2.zip file to begin the download. Download SunMC v4.com/sunmanagementcenter From the Patch Information portion of the screen.2 Install the SunMC Agent. Open a terminal window and log in to the system targeted for ASR installation as root. Note: If a browser is not available. go to Download SunMC v4. on page 22. Click on the Sun Management Center . Place the patch file in an install directory of your choosing on the system targeted for ASR installation.1 or 4.0. agree to the license agreement.

Do you want to proceed./es-inst -a As the installation progresses. all T-series) ◦ Workgroup Server config-reader (for V480 --> V890) ◦ Sun Fire High-End Systems Monitoring (for SunFire12K --> E25K) • • • • If prompted: “Do you want to select all the products. Once the file is downloaded. unzip sun_mc_zip_file 6. ◦ ELP Config-Reader Monitoring (for V210 --> V445. If you already have SunMC installed. 5. enter localhost or the loopback address 127.xml Note: If you are installing ASR Assets. If you select all. go to SunMC’s default scripts directory: cd /opt/SUNWsymon/sbin To begin the agent installation. Select one of the following three add-ons depending upon your platform type.” select Y.sun. you can use the SunMC Installation Guide for the Jump Start method of installing SunMC.0.com/sunmanagementcenter/support. run the following command: .zip file.” select Y. If prompted for the Server Host Name. The agent is used to report hardware telemetry to ASR.0.2.zip file: cd download_directory then cd disk1/sbin • 3. If prompted: “The Following Add-On Products have been selected for installation. Be certain that the file is copied to an installation directory on the system where ASR is to be installed before unzipping it.5. 2. open a terminal window and log in as root.1.0. Depending upon your circumstance. If prompted: “No Add-On Products have been selected for installation. and wish to install SunMC across several ASR Assets at once. For complete SunMC documentation. go to the following URL and select Sun Management Center under the Documentation section of the page: http://www. Do you want to proceed. go to the directory where you unzipped the SunMC . ASR Installation and Operations Guide – July 2010 22 . and unzip the file. below. 4. that is also acceptable. Proceed to the next step. go to the download directory. Install the SunMC Agent.” select Y. This section provides abbreviated instructions to install the SunMC Agent only. use one of the following instructions: • If you downloaded SunMC 4.2 Install the SunMC Agent Use the following procedure to install the SunMC Agent. Use the list below to determine how to respond to the SunMC installation prompts: • • Respond with Y to install all components. you are prompted to make several selections. or other directory where you copied the . 1. On the system where ASR is to be installed.

log in to another machine to complete the download and copy the file to the system targeted for ASR installation. Select Downloads A-Z. log in using your Sun Online Account. please reconfigure SunMC to use a different port number (for example. on page 33.0. depending upon your circumstance: • • If you are working with a SunMC version that precedes SunMC 4. 5. go to 5.3 Install Service Tools Bundle (STB). agree to the license agreement. you will use the script asrassetmenu. When prompted to set-up.3 Install Service Tools Bundle (STB). Once the SunMC installation is successfully complete.3 Set-Up Telemetry Sources to ASR. select your platform and the language. • • • • Note: The SunMC agent uses the default port 161. If you are working with SunMC 4. 7. Use the SunMC documentation for complete details. Download the SunMC 4. 3. Sun Blade. 3.3 Install the SunMC 4. unzip Sun_MC_Addon-4_0_V5-GA. 1161).3 Install Service Tools Bundle (STB).zip to download. use the following procedure to install the SunMC 4. go to one of the following sections. select Y. The displayed page provides links to both the software and documentation. In the section 6.0 add-on for x86_64.0 V5 Add On software.0. these prompts can be ignored.0 Add On Software. 8.sh to set the SunMC agent trap destinations. and Netra Systems Note: For x86_64 platforms. Sun Ultra.0 V5 Add-on Software for SPARC Enterprise. Click on Sun_MC_Addon-4_0_V5-GA. and click Continue. If needed. it is not necessary to download or install the Sun Management Center 4. 5. 4. Go to the following URL: http://www. If you are installing to an x86_64 system. open the documentation link in its own window and continue with the installation.0. 5. go to Install the SunMC 4. open a terminal window and log in as root.2. on page 24.• If prompted for SNMP trap destination information. If there is a port conflict with using 161 during the installation.zip ASR Installation and Operations Guide – July 2010 23 .0 only.com/download/index. go to 5. Scroll to the S list and select: Sun Management Center 4. 6. If prompted for SNMP trap destination information. At the bottom of the page. Go to the directory where you downloaded the installation file and unzip it.jsp Note: If needed. go to 5. Traps are set later from ASR itself.0 V5 Add On software. If prompted to disable features. on page 24. 4. select N. select Y. When prompted to start the agent. ignore this prompt.0 Add On Software For users of SunMC 4.sun. If you are working with a SunMC version that precedes SunMC 4. If required. On the system where ASR is to be installed. below.

Download the Service Tool Bundle software. 1. 3. log in to another machine to complete the download and then copy the file to the system targeted for ASR installation. tar -xvf Sun_MC_Addon-4_0_V5-GA.” enter Y. open a terminal window and log in as root. on page 20. or make note of this directory for use below. 4.tar 10. Note: If your system is using only a service processor-based telemetry source (ILOM.0 Configure ASR Asset(s). Go to http://sun. On the system where ASR is to be installed. on page 32. STB does not need to be installed. there will be a /disk1/image directory. When prompted: “Do you want to run set-up now. open the documentation link in it’s own window and continue with the installation. Go to SunMC’s default scripts directory. For example: cd download_directory/disk1/image pwd 11. such as obtaining the system’s serial number from firmware. When prompted for the path to the installation image. Go to this directory and run a pwd command. If needed.” enter Y. Use the instructions below to install the Service Tools Bundle (STB) v5. Highlight the results of the pwd command and copy it into your system’s clipboard. If installing ASR Assets. For example: download_directory/disk1/image 15.9. When prompted: “Do you want to start Sun Management Center agent now. 2. go to 6. log in using your Sun Online Account. paste or enter the full path of the image and press [Return]. The displayed page provides links to both the software and documentation. To begin the installation.0 Install the ASR Manager. Click on the Download Now link from the web page. Do you want to Proceed. run the following command: . cd /opt/SUNWsymon/sbin 13. As the installation progresses. select your platform and the language. you are prompted to make several selections.” enter Y. Use the list below to determine how to respond to the installation prompts: • • • • When prompted: “Do you want to select all the products. 12. When prompted: “The following Add-On Products will be installed: ELP Config-Reader Monitoring. below. 5./es-inst 14. agree to the license agreement.” enter Y.com/service/stb Note: If needed. Within the directory where you untarred the file. ASR Installation and Operations Guide – July 2010 24 . go to 5.2 or later.3 Install Service Tools Bundle (STB) STB is a tool set that helps ASR obtain required information from each ASR system before you can activate them. or XSCF on M-Series). If this is your situation. go to Install Service Tools Bundle (STB). and click Continue. At the bottom of the page. 16. Upon successful installation. If required. Untar the resulting tar file.

When prompted: “Do you want to replace the existing SNEEP packages. When prompted: “Would you like to (I)nstall. (X)tract component selections. When prompted: “Do you want to replace the existing Solaris Crash Analysis Tool packages. you may have to set execute permissions on the file. <product_name> must be Solaris Operating System. Keep in mind that the definitive source for the actual serial number is on the chassis of your system. Click on the following file to download it: install_stb. <platform> must be your platform type. To confirm that STB is installed correctly. 9. <container>global <source> must be SUNWstosreg. (M)odify.” enter Y. on page 13. Be sure that the following attributes are reporting as indicated: • • • • • • <agent_version> must be 5. <system> must be SunOS./install_stb.sh 8. 25 ASR Installation and Operations Guide – July 2010 . (M)odify.sh. 7.2 or above.” enter Y. as described in 3. (X)tract component selections.” enter I. sneep -s <serial_number> 11. tar -xvf install_stb.3 Validate Information in the Sun Member Support Center.: enter Y.” enter M. you are prompted to make several selections. Also.” enter Y or N depending on your preference. When prompted: “Do you want to replace the existing Explorer packages. When prompted: “Do you want to replace the existing Light Weight Availability Collection Tool packages. <serial_number> must be the serial number of your system.tar Execute the resulting file.sh. run the following command: sneep -a 10. Untar the file from the download directory. run the command below to set the serial number. As the installation progresses.2. the option to install Sun Secure File Transport is also provided. Run the following command to be sure that STB is reporting your system attributes correctly: stclient -E 12.5.sh . If the serial number for your system is not displayed. You may have to change shells to sh if the file does not execute. Note: the above list is valid for STB 5. When prompted: “Do you want to replace the existing Service Tags packages. Use the list below to determine how to respond to the installation prompts: • • • • • • • When prompted: “Would you like to (I)nstall.tar 6. It should also be the same in the Sun Member Support Center. as shown below: sh chmod +x install_stb. and that it is reporting your system’s serial number correctly.0. while for older versions.” enter Y or N depending on your preference.

If you do have SASM installed at version 1. Once the file(s) are downloaded. go to one of the following options depending upon whether you are installing an ASR Manager or ASR Asset. Keep in mind that a completely installed and active ASR Manager must be in place before installing ASR Assets. Click Continue.1 or higher. • • If installing the ASR Manager. and unzip the file(s). 6. 4. 1. 10. 5. download the files to another machine and copy them to the machine where the ASR Manager is to be installed. 2. 14. From the machine where the ASR Manager is to be installed. Select the platform and language. Click on the ASR Software Download link.0 Install the ASR Manager.pkg. go to the download directory. Click on the SUNWswasr. Run the following command to determine the existence and version of SASM: pkginfo -l SUNWsasm 3.5 Download the SASM and ASR Packages If you do not have SASM installed.sun. Click on the ASR Software Download link. on page 3. on page 32. return to the following URL: http://www.com/service/asr Note: If a browser is not available. 13.4 Check the Existence of SASM and Version Use the following procedure to determine if you already have SASM. 2. go to 6. agree to the license agreement. ASR Installation and Operations Guide – July 2010 26 . To download the ASR package. Select the platform and language. 5.2.1 Close-Up of the ASR Manager. use the following procedure to download both the SASM and ASR packages.0 Configure ASR Asset(s). Make note of the results and continue to the next section. Open a terminal window to the system where the ASR Manager is to be installed and log in as root. 9. refer to 1.• <container>global <source> must be SUNWsthwreg. 8. on page 20. and log in if required using your Sun Online Account.gz link to complete the download.version_num. or other directory where you copied the .gz link to complete the download.version_num. Click Continue.pkg.com/service/asr 7. If installing an ASR Asset. 5. go to step 6 in this procedure. open a terminal window and make sure you are logged in as root. agree to the license agreement. For more information on the relationship between SASM and ASR. go to 5.gz file(s). Be certain that the file(s) are copied to an installation directory on the system where the ASR Manager is to be installed before unzipping them. re-install STB. 3. Click on the Sun Automated Service Manager link. If you are not getting the correct data. 1. and log in if required using your Sun Online Account. Go to the following URL: http://www. Upon successful installation.sun. Click on the SUNWsasm.

1. When prompted: “. As the installation progresses. . install conflicting files. you are prompted to make several selections. go to 7. scripts will be executed with super-user permission during the process of installing this package.version_num. continue to the next procedure Install the ASR Package. continue to the following procedure. From the directory where you unzipped the SASM package. 5. . 2.version_num. you are prompted to make several selections. Otherwise. Open a terminal window and make sure you are logged in to the ASR Manager system as root. .cshrc. . scripts will be executed with super-user permission during the process of installing this package. Add the asr command to the PATH (update to the root's .” enter Y. . install the ASR package using the following command: pkgadd -d SUNWswasr. on page 27.kshrc. Use the list below to determine how to respond to the installation prompts: • • • 4.gz (if downloaded) gunzip SUNWswasr.version_num. Open a terminal window and make sure you are logged in to the ASR Manager system as root.” press [Return] to select all packages. .5 Test Connectivity from the ASR Manager to Sun. . 2.pkg 3.gz 11. install conflicting files. install all packages. When complete. .pkg. .7 Install the ASR Package.” enter Y.3. PATH=$PATH:/opt/SUNWswasr/bin export PATH 5.7 Install the ASR Package Use the following procedure to install the ASR package on the ASR Manager system. When prompted: “.” press [Return].” enter Y. . When prompted: “. 5. skip the following procedure and go to 5. As the installation progresses. If you do not need to install SASM. Once the installation completes successfully. When prompted: “. install the SASM package using the following command: pkgadd -d SUNWsasm. From the directory where you unzipped the ASR package. or . Keep in mind that SASM is installed on the ASR Manager system only.profile. not ASR Assets. . .” enter Y. .6 Install the SASM Package Use the following procedure to install SASM. When prompted: “.version_num. select all packages to process.pkg. continue to the next procedure Register the ASR Manager. When prompted: “. on page 62.pkg 3.gunzip SUNWsasm. To confirm proper network connectivity between the ASR Manager and Sun. 1. . Use the list below to determine how to respond to the installation prompts: • • • 4.bashrc as needed): ASR Installation and Operations Guide – July 2010 27 .

If you are not using a proxy server. enter -. refer to 7. 8. Upon successful results of the above commands. run the following command: asr test_connection This command sends a test message (ping) to the transport server. the registration is complete. enter the proxy server information as you determined in 4. 6. Network. Usually this is the hostname of the SASM server. 5. on page 16.samba. enter . Use the following command to register the ASR Manager: asr register 2. if authentication is not required. Proxy server name: ? <proxy server name> Proxy port number: ? <proxy port number> Proxy authentication. Once validated. pay close attention to the requirements as shown in the installation prompts (shown below).(hyphen).sun.3. Solaris. or Africa regions) 3. Java.jar file 3) Enter full path to this file below jCIFS jar file: [?] <full path of jCIFS jar file> Note: These properties are stored in the/var/opt/SUNWsasm/configuration/config.ini file with your SOCKS proxy server information. You may have to contact a network administrator for assistance. on page 61.3 Configure ASR to Send HTTPS Traffic Through a Proxy Server. 1) transport.uk (Europe.sun. If you are using a proxy server for access to the internet.for no proxy.8 Register the ASR Manager Use the following procedure to register the ASR Manager. To be sure that ASR can send information to the transport server.5.co.com (Americas or Asia Pacific regions) 2) transport. Enter the username and password of your Sun Online account when prompted. Enter 1 or 2 depending on your geographic location. manually edit the SASM config. For instructions. Middle East. Upon entry of the Sun Online account credentials. enter the hyphen . enter the information below. ASR will validate the login. Proxy user: <proxy user name> Proxy password: <proxy password> If this is an NTLM type proxy. the registration of the ASR Manager is complete.ini file. You can update these properties if needed and then restart the SASM. Check the registration status of ASR by running the following command: asr show_reg_status A message is displayed on the screen indicating whether ASR is registered with the transport server.org/ 2) Extract contents and locate the jcifs-*. 4. When completed with the steps in this procedure. 1) Download jCIFS from http://jcifs. NTLM Host: [?] <NTLM host name> NTLM support is not bundled with SASM but may be added now. Otherwise. If you are using an NTLM proxy. enter NTLM Domain: [?] <NTLM domain name> Enter the host the NTLM authentication request is originating from.1 Verify: Hardware. Make sure you are logged in to the ASR Manager system as root. ASR Installation and Operations Guide – July 2010 28 . Note: If you are using a SOCKS proxy. 7. 1.

ASR Installation and Operations Guide – July 2010 29 . Unzip and untar the ASRAssetBundle file using the following commands: gunzip ASRAssetBundle. Go to the ASRAssetBundle directory and launch the ASR Asset Menu using the following commands: cd /opt/SUNWswasr/asrassetbundle .version_num. Check the system for ASR qualifications by typing 1. continue to the next procedure Verify System and Activate the ASR Manager." then run the following activate command. 5. on page 16. While logged in as root on the ASR Manager system. This command checks that the system has all the necessary requirements for ASR.Sun-Fire-V215 SPARC --------------------------------------------------------------------------------- 6. Network. go to the following directory: cd /opt/SUNWswasr 2. If you receive a list of missing patches.version_num./asrassetmenu. If you are installing the ASR Manager. 5. enter 9 to close the ASR Asset Menu. To ensure that the ASR Manager has been activated. run one of the following commands. Be sure to use the IP or hostname of the ASR Manager system.9 Verify System and Activate the ASR Manager Use the following procedure to verify that the system is fully qualified for ASR and to activate the ASR Manager. install these patches following your internal processes and/or using the steps described in 4.sh Welcome to the ASR asset menu ---------------------------------------------1) Check system for ASR qualifications 2) Add a trap-destination to SunMC agent 3) Add a trap-destination to FMA agent 4) Remove a trap-destination from SunMC agent 5) Remove a trap-destination from FMA agent 6) List SunMC agent trap-destinations 7) List FMA agent trap-destinations 8) Test event to verify ASR connectivity (Generates test event to ensure connectivity between the asset and ASR) 9) Exit 4. Auto-activation of the ASR Manager is attempted during registration.tar.gz tar -xvf ASRAssetBundle.tar 3. Solaris.168.9. asr list_asset -i <IP address> or asr list_asset -h <hostname> Information similar to the following is displayed: --------------------------------------------------------------------------------IP_ADDRESS HOST_NAME SERIAL_NUMBER ASR PRODUCT_NAME 192.78. Note: When complete. Be sure to use the IP or hostname of the ASR Manager system. 1.193s4u-v215b-xyz 0715FL3999 Enabled SUNW.1 Verify: Hardware. If the output is "No asset found to list. Java.

• • Note: If the asr heartbeat is disabled in crontab. To confirm end-to-end ASR functionality. The crontab entries are set-up as follows and can be changed by the ASR installer as needed: asr heartbeat: 0 0. on page 52 for more information. you can run the asr update_rules command from the ASR Manager system.1 Example Heartbeat Failure Notification Email. When there are new rules.4.2.m.sh Note: If working with an ASR version previous to ASR 2. 5.4 and above. If the Sun/ASR back-end systems do not receive the heartbeat in 48 hours. The update rules option is not available in versions previous to 2. asr report: This task schedules an automatic Status Report emailed every Sunday at 6 a. To be sure your fault rules are current. an email is sent to the Sun Online account used to install and register ASR. Continue to the following procedures. you will not be notified. ASR Installation and Operations Guide – July 2010 30 .10 Crontab Set-Up For ASR version 2. These fault rules can change as ASR improves its filtering and as new platforms and telemetry sources are supported by ASR. the asr heartbeat and asr report crontab entries need to be manually added using crontab -e. These crontab entries perform the following tasks: • asr heartbeat: This task sends a message to the Sun backend server every 12 hours.3. via email.4. If the cron job is not set to download the fault rules automatically. if your ASR fault rules are out of date with the most current release. crontab entries are automatically created when the ASR Manager is installed. Refer to 7. on page Error: Reference source not found.” The filtering process also ensures that telemetry that contains faults is reported. For more information on fault rules. they send an email to the Sun Online Account used to install/register the ASR Manager. run the following command: asr report A status report will be emailed to you. the ASR Manager automatically downloads and installs the latest rules bundle. asr update_rules: ASR uses fault rules to filter the telemetry data sent from ASR Assets. This filtering is done to remove telemetry that contains no real fault data and general telemetry “noise. 8. refer to Error: Reference source not found.asr activate_asset -i <IP address> or asr activate_asset -h <hostname> 7.12 * * * /opt/SUNWswasr/bin/asr heartbeat asr report: 0 6 * * 0 /opt/SUNWswasr/bin/asr report update rules: 0 <random number between 1-59> 0 <random number between 1-23> * * * /opt/SUNWswasr/bin/update_rules. ASR installs a cron job on the ASR Manager system to periodically check Sun’s autoupdate server for any new rules updates.

ASR Installation and Operations Guide – July 2010 31 .0 Configure ASR Asset(s). 6.3 Set-Up Telemetry Sources to ASR. Once the ASR Manager is installed. Now that the ASR Manager is installed. ASR Assets can be configured. 2.11 What to Do Next Continue to the following tasks in order: 1. on page 33.5. 6. telemetry sources must be set-up so that this system can report its fault telemetry to ASR and Sun.

CHAPTER

6

6.0 Configure ASR Asset(s)
Use this chapter to configure ASR Assets. Keep in mind that an active ASR Manager must be installed before configuring ASR Assets. Before continuing, the following prerequisites must be complete for the system(s) targeted for ASR configuration: • • • 3.1 Create a Sun Online Account, on page 10. This needs to be done once and should have been done during the installation of the ASR Manager. 3.2 Register/Validate Systems in the Sun Member Support Center (MSC), on page 11. The system serial number must be in the MSC database, have an active contract, and an assigned technical contact. 4.0 Assess ASR Systems, on page 15 (OS version check, network validation, verify existing telemetry sources).

Note: If you have completed installing the ASR Manager and need to set-up telemetry reporting on the ASR Manager, go to 6.3 Set-Up Telemetry Sources to ASR,on page 33.

6.1 Install SunMC Agent and Service Tools Bundle
You may need to install the SunMC Agent and the Service Tools Bundle software on your ASR Asset system. Proceed to the following instructions in order. When complete, return to these instructions. • • 5.2 Install Sun Management Center (SunMC) Agent, on page 20. 5.3 Install Service Tools Bundle (STB), on page 24.

6.2 Obtain the ASR Asset Bundle
If you are configuring an M-series system, skip this procedure and go to 6.3.3 Enable M-Series XSCF Telemetry, on page 38. In all other cases, use the following procedure to obtain the ASR Asset Bundle. 1. 2. Open a terminal window and log in as root on the system where the ASR Manager is installed. Go to the following directory: cd /opt/SUNWswasr 3. Copy the ASRAssetBundle.version_num.tar.gz file to one or multiple systems that will be ASR Assets. You can copy the file to an NFS location or use a provisioning tool to distribute the file to a group of assets. Copy the ASR Asset Bundle file to any directory on the system, such as /opt or /tmp. Open a terminal window and log in as root on the ASR Asset system. Go to the directory where you copied the ASR Asset Bundle file. Unzip and untar the ASRAssetBundle file using the following commands:

4. 5. 6.

ASR Installation and Operations Guide – July 2010

32

gunzip ASRAssetBundle.version_num.tar.gz tar -xvf ASRAssetBundle.version_num.tar 7. Continue to the following procedure Set-Up Telemetry Sources to ASR.

6.3 Set-Up Telemetry Sources to ASR
Use the following procedures to enable telemetry sources on your system(s) to send telemetry to Sun. These steps are the same for both the ASR Manager and ASR Assets. Before continuing, you should have already verified what telemetry sources reside on the system, as explained in 4.2.1 Confirm Existing Telemetry Sources, on page 17. Depending upon what telemetry sources reside on your system, complete one or more of the following procedures: • • • Enable SunMC Agent and/or FMA Telemetry. Enable ILOM Telemetry. Enable M-Series XSCF Telemetry.

6.3.1
1. 2.

Enable SunMC Agent and/or FMA Telemetry

Use the following procedure to enable SunMC and/or FMA telemetry sources. Make sure you are logged in as root on the system whose telemetry you wish to enable. This could be either an ASR Manager or an ASR Asset system. Go to the directory where you untarred the Asset Bundle file, and then go to the specific ASR Asset Bundle directory. For example: If on an ASR Asset: cd /file_copy_location/asrassetbundle If on the ASR Manager system: cd /opt/SUNWswasr/asrassetbundle 3. Launch the ASR Asset Menu: ./asrassetmenu.sh Welcome to the ASR asset menu ---------------------------------------------1) Check system for ASR qualifications 2) Add a trap-destination to SunMC agent 3) Add a trap-destination to FMA agent 4) Remove a trap-destination from SunMC agent 5) Remove a trap-destination from FMA agent 6) List SunMC agent trap-destinations 7) List FMA agent trap-destinations 8) Test event to verify ASR connectivity 9) Exit 4. Select 2 to enable SunMC telemetry, or select 3 to enable FMA telemetry, if applicable. Respond to the script’s prompts as follows: • When prompted, “Please enter Hostname or IP address of SASM ASR plugin,” enter the information for the ASR Manager. Whether you are enabling telemetry on the ASR Manager system or on ASR Asset systems, the hostname or IP entered must be for the installed ASR Manager.

ASR Installation and Operations Guide – July 2010

33

• • 5. 6. 7. 8.

When prompted, “Please enter SNMP port of SASM ASR plugin (q to quit) [162],” press [Return] or enter another port if you have changed your port settings for ASR. When prompted, “Do you want to set trap-destination [y,n,q],” confirm the displayed information, enter Y, and press [Return].

The ASR Asset Menu then enables the telemetry and displays where the telemetry from this system will be sent (IP or hostname of the ASR Manager). If you are also enabling FMA telemetry, repeat the steps in this procedure but select option 3 from the ASR Asset Menu. When complete, enable any other telemetry sources that may reside on the system (for example, ILOM). Refer to 6.3 Set-Up Telemetry Sources to ASR, on page 33, if required, and return to these instructions. Go to one of the following procedures depending upon your circumstance: • If you have enabled all telemetry sources on the ASR Manager system, the installation of the ASR Manager is complete. Continue to one of the following sections: ◦ 6.0 Configure ASR Asset(s), on page 32. Once an ASR Manager system is installed, ASR Assets can be installed/enabled. ◦ 7.0 Manage the ASR Environment, on page 43. This section provides information on sending test faults and other tasks to manage the ASR environment. • If you have enabled all telemetry sources on an ASR Asset system, go to 6.3.4 Activate ASR Assets, on page 39.

6.3.1.1 Command Line Options for Setting Solaris FMA and SunMC Trap Destinations
With ASR 2.5, you can incorporate ASR asset configuration into your automated provisioning process. The asrassetmenu.sh script now includes command line options for setting Solaris and SunMC trap destinations. To set a Solaris FMA or SunMC trap destination from the command line: asrassetmenu.sh -sunmc <destination_IP_address> <port_number> asrassetmenu.sh -solaris <destination_IP_address> <port_number> The asrassetmenu.sh script will exit with an error status value for any of these conditions: • • • <destination_IP_address> not provided <port_number> not provided Trap destination unable to be set

6.3.2

Enable ILOM Telemetry

Use the following procedure to enable ILOM telemetry. It is assumed that a network connection to the platform’s dedicated service processor (SP) is connected and configured, as discussed in 4.2.3 ILOM General Procedures, on page 18. Do not continue with the installation unless you have confirmed the initial ILOM setup. Additionally, you will need the ILOM service processor IP address to complete the following procedure. Note: For more information on ILOM, refer to the ILOM documentation for your platform. Refer to: http://www.sun.com/documentation

ASR Installation and Operations Guide – July 2010

34

6.3.2.1 Enable ILOM: GUI Interface
Installers of ASR have the choice of using a web-based GUI or a command-line interface to enable ILOM telemetry. Use the procedure below for the GUI method. If command-line is desired, go to 6.3.2.2 Enable ILOM: Command Line Interface. 1. 2. 3. From a web browser, use https to access the IP address of the ILOM interface. https://IP_Address_of_ILOM_Interface Log in as root. From the menu, select Configuration, then select Alert Management. Note: If using ILOM on a Sun Blade 6000 series, select CMM from the left navigation pane, then select Configuration, and Alert Management.

4.

The Alert Setting screen lists 15 possible Alert IDs that can be configured to send ILOM telemetry. Alert ID slots that are occupied by existing alert settings are shown along with their alert parameters. Choose an Alert ID that is not used by selecting the radio button next to the Alert ID number. For example, Alert ID 7 is selected in the above example.

Note: Unused Alert IDs are mainly indicated by the disable setting in the Level column and by all zeros in the Destination Summary column. 5. Select Edit from the Actions pull-down menu.

Note: If using ILOM on a Sun Blade 6000 series, select the Edit button from the top of the screen.

ASR Installation and Operations Guide – July 2010

35

• If you have enabled all telemetry sources on an ASR Asset system. 10.0 Configure ASR Asset(s). and return to these instructions. on page 32. as described in the previous procedure. you do not need to complete these steps.2 Enable ILOM: Command Line Interface Use the ILOM command line procedures below to enable ILOM telemetry. Continue to one of the following sections: ◦ 6. meaning that the port is assigned to the default for SNMP (162). IP Address: Enter the IP Address of the ASR Manager system.6. Once an ASR Manager system is installed. the port cannot be changed from the default. This section provides information on sending test faults and other tasks to manage the ASR environment.4 Activate ASR Assets. Refer to 6. Generate test alerts. on page 39. ◦ 7. Type: Select SNMP Trap from the pull-down menu. Community Name: Enter public in the text entry field. Go to one of the following procedures depending upon your circumstance: 6.0.3 Set-Up Telemetry Sources to ASR. on page 43. go to 6. ASR Installation and Operations Guide – July 2010 36 .3. • • 7. When complete. on page 33. For ILOM versions 2.2. enable any other telemetry sources that may reside on the system (for example. If you used the GUI method. In the Alert Settings page. Enter data in this screen as follows: • • • • Level: Select Minor from the pull-down menu. the installation of the ASR Manager is complete. select Disable. if required. ASR Assets can be installed/enabled.0 Manage the ASR Environment. FMA).4.3. 8. ILOM generates test alerts to each of the alert rule configurations enabled on the Alert Settings page. Destination Port: The default of 0 is automatically set. click the Send Test Alert button. • If you have enabled all telemetry sources on the ASR Manager system. SNMP Version: Select v2c from the pull-down menu. Click the Save button.2 or lower. 9. If removing an ILOM trap.

2 or lower. Note: If you are removing a trap. it is important to understand that ILOM supports up to 15 userconfigurable alert rules.0. Open a terminal window and ssh to the IP address of the ILOM network interface: ssh IP_address_of_ILOM_interface 2. Before choosing. add the destination_port=xxx parameter into the command following the destination parameter. You can use the web-based GUI method to determine this quickly. depending upon which alert rule slot you have determined is unoccupied using the previous step. you must determine that the rule you select is not currently being used. If you wish to change the port. type: cd /SP/alertmgmt/rules For a blade server SP.4. however.1 Enable ILOM: GUI Interface. • For Rack Mount Servers and Blades: -> set /SP/alertmgmt/rules/x type=snmptrap level=minor destination=IP_of_ASR Manager snmp_version=2c community_or_username=public • For the Sun Blade 6000 Chassis: -> set /CMM/SP/alertmgmt/rules/x type=snmptrap level=minor destination=IP_of_ASR Manager snmp_version=2c community_or_username=public 5.2. 3.) until you find an available alert rule slot.0. 2. Before enabling ILOM telemetry. • • For Rack Mount Servers and Blades: -> show /SP/alertmgmt/rules/x For Sun Blade 6000 Chassis: -> show /CMM/alertmgmt/rules/x Important: Substitute x for a rule number (1 to 15). Type one of the following command paths to set the working directory: • • • For a rack-mounted server SP. enter a number from 1 to 15. It is one of these rules you must set to enable ILOM telemetry. destination: Enter the IP address of the ASR Manager. If you see that a rule level is set to anything else but disabled. the destination port can be changed if needed. Log in as root. For ILOM versions higher than 2. on page 35. Rerun the command above and substitute the rule number with the next number in sequence (for example.2.1. as discussed in 6. you must first choose one of these rules (1 to 15) to set. etc. Therefore. type: cd /CMM/alertmgmt/CMM/rules Type the following command to generate a test alert for each enabled alert rule configuration: ->set testalert=true ASR Installation and Operations Guide – July 2010 37 . run the following command to determine an available alert rule slot. then 3. Once an alert rule slot is determined. Pay close attention to the following data entry points before running the command: rules/x: For x. For ILOM versions 2. run one of the following commands. the alert rule slot is occupied.3. set the level parameter to disable. destination_port: The port is assigned to the default for SNMP (162). 4.4. the port cannot be changed from the default. Otherwise. Generate test alerts. type: cd /CH/BLn/SP/alertmgmt/rules For a chassis CMM.

on page 43. Note: This procedure can also be used to remove XSCF trap destinations. run the following command to stop XSCF from sending telemetry to the ASR Manager system: XSCF>setsnmp remtraphost -t v2 xxx. XSCF> setsnmp disable 4. ASR Assets can be installed/enabled. Open a terminal window and initiate an ssh connection to the IP address of the XSCF network interface: ssh IP_address_of_XSCF_interface 2. Log in to the XSCF console.xxx. Once an ASR Manager system is installed. It is assumed that a network connection to the platform’s dedicated service processor (SP) is connected and configured.0 Configure ASR Asset(s). and return to these instructions. on page 39.xxx.0 Manage the ASR Environment. Continue to one of the following sections: ◦ 6.3. 6. 3.xxx.xxx.xxx xxx. For more information on XSCF. enable any other telemetry sources that may reside on the system (for example.com 1. When complete.xxx. the installation of the ASR Manager is complete. • If you have enabled all telemetry sources on an ASR Asset system. You can run showuser -p for a list of users with this privilege. see further below in this step: XSCF>setsnmp addtraphost -t v2 -s public -p 162 xxx. on page 33.xxx=ASR Manager IP address If Removing a Trap: If you wish to remove an XSCF trap destination. Do not continue with the installation unless you have confirmed the initial XSCF set-up. on page 32.3 Set-Up Telemetry Sources to ASR. FMA). Make sure you have platadm privileges. if required. Enable the SNMP agent: XSCF> setsnmp enable 6. If using these procedures to remove a trap.6. (showuser -p <login name>). Documents are available at: http://docs.3 Enable M-Series XSCF Telemetry Use the following procedure to enable M-Series XSCF telemetry.4 Activate ASR Assets.xxx = ASR Manager IP address 5.xxx -s=community string (default value is public) -p=SNMP listener port (default value is 162) xxx. 7. Add the ASR Manager system as the trap destination. Refer to 6. Disable the SNMP agent. go to 6. This section provides information on sending test faults and other tasks to manage the ASR environment.xxx.sun. ◦ 7.xxx. Enable SNMP v1v2: XSCF> setsnmp enablev1v2c public ASR Installation and Operations Guide – July 2010 38 . Go to one of the following procedures depending upon your circumstance: • If you have enabled all telemetry sources on the ASR Manager system. refer to the XSCF User Guide for SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers.xxx.3.

3. Important: Activating ASR Assets is not done on the assets themselves but on the ASR Manager system only. on page 43. All assets to be activated should already have telemetry trap destinations set. Once an ASR Manager system is installed. Be sure to use the IP or hostname of the ASR Asset system. 7. Additional FMA diagnostic data cannot be retrieved without setting the community string as public. Proceed to one of the following options.3. Run the following activate command for each ASR Asset. For all other systems.xxx. use the procedure below. This section provides information on sending test faults and other tasks to manage the ASR environment. go to 6. Go to one of the following procedures depending upon your circumstance: • If you have enabled all telemetry sources on the ASR Manager system. XSCF> showsnmp Agent Status: Enabled Agent Port: 161 System Location: Unknown System Contact: Unknown System Description: Unknown Trap Hosts: Hostname Port Type Community String Username Auth Protocol xxx. Verify SNMP settings to make sure the trap destination is set and SNMP is enabled. the configuration of the ASR Assets is complete. ASR Installation and Operations Guide – July 2010 39 . as described in 6. asr activate_asset -i <IP address> or asr activate_asset -h <hostname> 3.0 Manage the ASR Environment. Run the following command to receive an email listing all activated assets. ASR Assets can be installed/enabled. 2. Continue to one of the following sections: ◦ 6. ◦ 7. on page 32.xxx 162 v2 public n/a n/a SNMP V1/V2c: Status: Enabled Community String: public Enabled MIB Modules: SP MIB FM MIB 8. on page 40 to activate the system.4 Activate ASR Assets Use the following procedure to activate ASR Assets. depending upon your circumstance: • • 1. on page 33.xxx. go to Activate ASR Assets. If you are activating a Sun Blade system.0 Configure ASR Asset(s).The value of the community string should always be public. Open a terminal window and log in as root on the ASR Manager system.3 Set-Up Telemetry Sources to ASR. Once ASR Assets are activated. If this has not been done. the installation of the ASR Manager is complete. 6.1 Activate Blade Assets. complete that task first before continuing. • If you have enabled all telemetry sources on an ASR Asset.4.

Run the following command to receive an email listing all activated assets. Therefore. and blade telemetry reports faults specific to the blade’s subsystems.0 Configure ASR Asset(s). the configuration of the ASR Asset(s) is complete. You have the following options: • • 6. 7. Keep in mind that Blade systems also include the chassis within which the Blade systems are installed. Run the following commands. Keep in mind that the Blade systems must be qualified for ASR.0 Manage the ASR Environment. You have the following options: • 6. Important: Activating ASR Assets is not done on the assets themselves but on the ASR Manager system only. Open a terminal window and log in as root on the ASR Manager system.1 Activate Blade Assets Use the following procedure to activate a Sun Blade system. This section provides information on sending test faults and performing other tasks to manage the ASR environment. Repeat the asr activate_blade command for each Blade within the chassis that you desire to have under ASR management. Configure additional ASR Assets as needed. • • If you are working with Blade systems whose chassis has not been activated with ASR.asr report 4. Note – Auto Activation: If the ASR Manager receives fault telemetry from an asset that has not been previously activated. Once the ASR Asset(s) are activated. If activating an X6270 or X6275 system. on page 32.sun. ASR Installation and Operations Guide – July 2010 40 .3. Once the ASR Asset is activated. go to Previously ASR Activated Blade Systems. 6.com/service/asr Note: For the X6270 . It is issued once where Blade IP is the IP of the blade’s service processor. as specified in the “Sun Systems Qualified for ASR” link at: http://www. ASR automatically attempts to activate the asset as if the asr activate_asset command is executed. when activating. go to New ASR Activation on Blade Systems and Chassis. the asr activate_blade command is issued twice. Configure additional ASR Assets as needed. 2. on page 32. New ASR Activation on Blade Systems and Chassis 1. the installation of the ASR Asset is complete.4. You will need the IP addresses of the Blade chassis and the Blade systems in order to complete this procedure.0 Configure ASR Asset(s). and once where Blade IP is the IP of the blade’s host. If you are working with systems whose chassis has previously been activated with ASR. asr activate_asset -i Chassis_ILOM_IP asr activate_blade -i Blade_IP -c Chassis_ILOM_IP 3. The ILOM on the service processor for an X6270 must be configured. It is acceptable to only activate the service processor of the blade in this case. The host of an X6270 or X6275 can only be activated if it is running Solaris. asr report 5. the Blade and the chassis must be activated. Chassis telemetry reports power and environmental faults. on page 43. 4. see the note further below.

0 Manage the ASR Environment. Sun Blade X6275 Service Processors Activate each Sun Blade X6275 Service Processor with the command: activate_blade -i <SP_IP_address> -c <CMM_IP_address> When activated both X6275 Service Processors located on a single X6275 Blade Server will report ASR events independently. Important: Activating ASR Assets is not done on the assets themselves but on the ASR Manager system only.0 Manage the ASR Environment. If activating an X6270 or X6275 system. Configure additional ASR Assets as needed.• 7. This section provides information on sending test faults and performing other tasks to manage the ASR environment.0 Configure ASR Asset(s). 7. 2. Repeat the asr activate_blade command for each Blade within the chassis. Sun Blade X6275 Hosts To use this telemetry each Host will need to be activated using the command: activate_blade -i <Host_IP_address> -c <CMM_IP_address> ASR Installation and Operations Guide – July 2010 41 . use the following instructions to activate Blade systems. Open a terminal window and log in as root on the ASR Manager system. each X6275 has two Hosts than can be configured as a secondary telemetry source. The host of an X6270 or X6275 can only be activated if it is running Solaris. asr report 5. Each activated Service Processor on a single blade will be displayed in ASR as having the same serial number and a different IP address. the asr activate_blade command is issued twice. on page 43. It is issued once where Blade IP is the IP of the blade’s service processor. asr activate_blade -i Blade_IP -c Chassis_ILOM_IP 3. 4. Sun Blade X6275 Configuration A Sun Blade X6275 server has two Service Processors that should be configured and activated for ASR using the steps described above. Keep in mind that the Blade systems must be qualified for ASR. It is acceptable to only activate the service processor of the blade in this case. and once where Blade IP is the IP of the blade’s host.com/service/asr Note: For the X6270. Run the following command. the configuration of the ASR Asset(s) is complete. The ILOM on the service processor for an X6270 must be configured. on page 32. as specified in the “Sun Systems Qualified for ASR” link at: http://www. on page 43. Once the ASR Asset(s) are activated. Also. see the note further below. This section provides information on sending test faults and performing other tasks to manage the ASR environment. Previously ASR Activated Blade Systems If you have previously activated a Blade chassis. Run the following command to receive an email listing all activated assets. You have the following options: • • 6.sun. 1.

When activated both X6275 Hosts located on a single X6275 Blade Server will report ASR events independently. Each activated Host on a single blade will be displayed in ASR as having the same serial number and a different IP address. ASR Installation and Operations Guide – July 2010 42 .

7.1 View Status of ASR Asset(s).0 Manage the ASR Environment This chapter contains all procedures and other information required to manage and troubleshoot the ASR environment.5 Enable/Disable ASR Assets.5 ASR Diagnostic Utility. 7. 7. ASR Installation and Operations Guide – July 2010 43 .4 Create Test Alert.1.1. 7.2 ASR Environment Management.4 ASR Integration with Enterprise Monitoring Systems.1. 7.1. 7.1 ASR Asset Management This section provides a variety of commands and procedures for managing ASR Assets.7 Add/Remove Telemetry Traps from ASR Asset(s). 7.1.2 Generate Status Reports.3 ASR Network Parameters Management.CHAPTER 7 7. 7.1.1. 7.6 Deactivate/Activate ASR Assets. 7. Listed below are the available topics: • • • • • • • 7.3 Generate Periodic Status Reports. 7. Listed below are the available topics for this chapter: • • • • • 7.1 ASR Asset Management.

name. The results will be similar to the following example: IP_ADDRESS 123.1.2 Generate Status Reports A status report of all ASR Asset(s) can be obtained by running the following command from the ASR Manager system. asr report Example: ASR Installation and Operations Guide – July 2010 44 .7. a Service Request is created.54.67. subnets.76.1.1 View Status of ASR Asset(s) The status of any ASR Asset can be obtained by running one of the following command options from the ASR Manager system: asr list_asset (lists all assets associated with this ASR Manager) or asr list_asset -i IP_Address_of_ASR Asset or asr list_asset -h Hostname_of_ASR Asset or asr list_asset -s Subnet_IP_Address_of_ASR Asset(s) Note: The asr list_asset command accepts a comma delimited list of IP addresses.45.890 198.321 HOST_NAME abcd. or hostnames.com sasm-123-21 SERIAL_NUMBER 1234ABCD A11BAC ASR Enabled Enabled PRODUCT_NAME| Sun-Fire-V240 SPARC Sun-Fire-V210 SPARC 7. The status report is sent to the email address of the Sun Online Account associated with the ASR installation. The status report enables you to identify any issues with your ASR Asset(s) to ensure that if hardware faults occur.

To automatically generate periodic status reports./asrassetmenu.sh Note: If you have issues finding the asrassetbundle directory. the automatic scheduling of periodic status reports should have been complete. ASR Installation and Operations Guide – July 2010 45 .3 Generate Periodic Status Reports During ASR installation. Note: Setting up periodic status reports from ASR is performed on the ASR Manager system. on page 30. The status report is sent to the email address of the Sun Online Account associated with the ASR installation. 1.1.2 Obtain the ASR Asset Bundle. Execute the asrassetbundle shell script: • If on an ASR Asset: cd /untar_location_of_assetbundle/asrassetbundle .4 Create Test Alert The following command allows you to test the end-to-end functionality of ASR by simulating a hardware fault. 7. The end result is an email sent to the email address of the Sun Online Account associated with the ASR installation. on page 32 for more information.10 Crontab SetUp.1. a Service Request is created.7. The status report enables you to identify any issues with your ASR Asset(s) to ensure that if hardware faults occur. go to 5. go to 6.

Note: Test Alerts can only be generated from a host.1. All enabled ASR Asset(s) that send telemetry to this ASR Manager will continue.1. When the test alert is sent. After you have disabled an ASR asset. Regardless of which asset you wish to enable or disable. Test Alerts are not supported on service processors. asr disable_asset -i IP_address or asr disable_asset -h hostname or asr disable_asset -s subnet (used to disable a group of assets within the subnet) 7. Whether you are on an ASR Asset or the ASR Manager. Use the IP address or the hostname of the asset you wish to disable. Open a terminal window and log in to the ASR Manager system as root. you can re-enable it when you are ready for ASR to begin transmitting telemetry data.sh 2. Run one of the following commands depending on your circumstance. and the ASR Manager will continue to forward fault telemetry to Sun’s backend systems. only its telemetry will be stopped.1 Disable ASR Assets Use the following procedure to disable an ASR Asset. 7. Note: If this test fails on Solaris 10. Open a terminal window and log in to the ASR Manager system as root. 2. From the ASR Asset Menu./asrassetmenu. 5. 7. The default port is 162. Disabling an ASR Asset stops it from sending hardware telemetry. type 8. ASR Installation and Operations Guide – July 2010 46 . this action is always performed on the ASR Manager system.5. 1. 4. 3.2 Enable ASR Asset(s) Use the following procedure to enable an ASR Asset. enter the IP address of the ASR Manager.5 Enable/Disable ASR Assets Use the following procedures to enable or disable ASR Asset(s).5.1. If you disable the ASR Manager itself.• If on the ASR Manager system: cd /opt/SUNWswasr/asrassetbundle . check the email account of the Sun Online account associated with the ASR installation. Enter the SNMP port used to send hardware telemetry to the ASR Manager. be sure that the /usr/sfw/bin/snmptrap exists and Solaris netsnmp library is installed on the asset. The most common reasons to disable ASR Asset(s) are for system maintenance or if an asset is “noisy” in terms of sending an excess of telemetry data. 1.

ASR Installation and Operations Guide – July 2010 47 . on page 48 for more information. 3. Once enabled.6 Deactivate/Activate ASR Assets Deactivating an ASR Asset is done when you are replacing the asset or removing it entirely from the ASR system. When you deactivate an ASR Asset. ASR can no longer transmit telemetry data from this asset to Sun.3. you must re-activate it. If you want to enable it again for ASR. Refer to 7.1. on page 39. a successfully enabled message is displayed. 1. Open a terminal window and log in to the ASR Manager system as root. 4. Run one of the following commands depending on your circumstance. Once an asset is deactivated. asr enable_asset -i IP_address or asr enable_asset -h hostname or asr enable_asset -s subnet (used to enable a group of assets within the subnet) 3.2.1. To confirm the asset is enabled.7 Add/Remove Telemetry Traps from ASR Asset(s). Use the IP address or the hostname of the asset you wish to enable. 2. you should also stop the hardware telemetry from being sent from the asset (even though the telemetry data is ignored by ASR once sent). you cannot re-enable it. Run one of the following commands depending on your circumstance. asr deactivate_asset -i IP_address or asr deactivate_asset -h hostname or asr deactivate_asset -s subnet (used to enable a group of assets within the subnet) Note: When you deactivate an ASR Asset. Once complete. The status of the test event is sent to the email address of the Sun Online Account associated with the ASR installation.4 Activate ASR Assets. Refer to 6. Use the IP address or the hostname of the asset you wish to deactivate. you can generate a test event using one of the following command options: asr send_test -i IP_address or asr send_test -h hostname 5. 7. the asset will send hardware telemetry data to the ASR Manager and faults will be sent to Sun’s backend systems.

An active ASR Manager should already be fully installed.1 Add/Remove Telemetry Traps from SunMC and FMA Systems.7. its trap destination must be this same ASR Manager. on page 20.7. It does not remove the telemetry software itself nor disables its operation (for example. Keep in mind that this process stops telemetry from being sent to the ASR Manager. Refer to 5. depending upon the telemetry types you are working with on your system: • • • 7. on page 17.3. 7. then re-enable the traps with the new IP information.1 Confirm Existing Telemetry Sources. but not required.0 Configure ASR Asset(s). SunMC or FMA). go to 6. A trap destination is where the telemetry data is sent.2 Add/Remove Telemetry Traps from ILOM Systems.7 Add/Remove Telemetry Traps from ASR Asset(s) The procedures in this section explain how to enable or disable telemetry trap destinations on ASR Asset(s).1 Enable SunMC Agent and/or FMA Telemetry. During ASR installation. on page 33. 7. Reasons for enabling traps include: • • Traps were not enabled during installation. To add a SunMC and/or an FMA telemetry trap.3 Add/Remove Telemetry Traps from M-Series Systems (XSCF).1. Even if the ASR Manager itself is configured to send telemetry data.7.1.1. Ideally.2. 2. Refer to 6.1 Add/Remove Telemetry Traps from SunMC and FMA Systems Use the following procedure to add or remove a trap destination for systems using SunMC and/or FMA telemetry. For example: 3. at least one ASR Asset should already be fully installed. If this situation occurs. 7. if needed.1. and then go to the specific ASR Asset Bundle directory. Go to the directory where you previously untarred the ASR Asset Bundle file. which centrally collects the telemetry data sent from ASR Asset(s). Before continuing. ASR Installation and Operations Guide – July 2010 48 . 1. This could be either an ASR Manager or an ASR Asset system. Reasons for disabling traps include: • • IP address of ASR Manager changed.1. the trap destination specified is the ASR Manager system. each asset is configured by setting trap destinations from the asset system. on page 32. In all cases. Refer to 4. Traps need to be enabled as part of troubleshooting tasks.7. To remove a trap destination.7. be mindful of the following: • • • You should know what telemetry sources exist on any particular ASR system. Go to one or more of the following sections. make sure you are logged in as root on the system whose telemetry trap you wish to remove. you need to disable the traps.0 Install the ASR Manager. Stopping the use of ASR and/or you want to minimize telemetry traffic.

sh script (below). use the following parameters: • • If using the ILOM GUI interface.2 Add/Remove Telemetry Traps from ILOM Systems. ASR Installation and Operations Guide – July 2010 49 . Also. enter the listed IP address with the port number (for example. 4. . 6.3. or select 5 to remove the FMA trap destination. The trap is then removed from the system and all telemetry sent from SunMC and/or FMA to the ASR Manager is stopped. either remove the entire alert rule destination or set the Level parameter to Disable.3 Add/Remove Telemetry Traps from M-Series Systems (XSCF).7.2 Add/Remove Telemetry Traps from ILOM Systems To add or remove an ILOM trap.1.20.7. set the Level parameter to Disable. SunMC).192:162). If other telemetry sources exist on the system and you wish to remove them also (for example. refer to 6.77. Important: If you are removing an FMA trap. Launch the ASR Asset Menu: .2 Obtain the ASR Asset Bundle. on page 32 if you have issues locating the asrassetbundle directory and/or asrassetmenu. repeat the steps in this procedure to remove traps for FMA. When prompted. If removing a trap. be sure to specify the correct alert rule (1 to 15) to disable. on page 34. 192. ILOM). 7.1. 8.2 Enable ILOM Telemetry. If only one trap type is removed (for example. 7. go to one or more of the following sections: • • 7.If on an ASR Asset: cd /file_copy_location/asrassetbundle If on the ASR Manager system: cd /opt/SUNWswasr/asrassetbundle Note: Refer to 6. if applicable. enter the number of the trap-destination to remove.7.1. This referenced procedure can be used to add or remove traps.sh Welcome to the ASR asset menu ---------------------------------------------1) Check system for ASR qualifications 2) Add a trap-destination to SunMC agent 3) Add a trap-destination to FMA agent 4) Remove a trap-destination from SunMC agent 5) Remove a trap-destination from FMA agent 6) List SunMC agent trap-destinations 7) List FMA agent trap-destinations 8) Test event to verify ASR connectivity 9) Exit 5. if applicable. . Select 4 to remove the SunMC trap destination. If using the command line interface. 7./asrassetmenu.” enter the list number of the IP address of the ASR Manager. “.

7.3 Enable M-Series XSCF Telemetry. • To unregister ASR: 1.1 Stopping SASM and ASR Use the following procedure to stop SASM and ASR. The registration is performed on the ASR Manager system.3.7.3 Add/Remove Telemetry Traps from M-Series Systems (XSCF) To add or remove telemetry traps on systems that have XSCF telemetry (Sun M-Series).1 Register/Unregister ASR. 7.8 Register the ASR Manager.1 Register/Unregister ASR When you installed ASR.ini file (/var/opt/SUNWsasm/configuration/config. refer to 5. If the Sun server and ASR handshake becomes corrupted.2.3 ASR Emails. To register ASR. There are several reasons why you may want to do this. run the following command: /opt/SUNWswasr/bin/asr unregister 2. 7. This referenced procedure can be used to add or remove traps. If you need to perform system maintenance to the ASR Manager or to ASR Asset(s).1. ASR should be unregistered and then re-registered with the new Sun Online account information. In this case. you registered it with the transport server (transport. as in a case when the email contact is no longer associated with the company. The following procedures are provided in this section: • • • 7.2. 7. as is an unregister if required. 7.7.2. refer to 6. ASR Installation and Operations Guide – July 2010 50 .2 ASR Environment Management This section provides a variety of procedures that can be used to manage the ASR environment as a whole.2. ASR cannot send hardware fault telemetry to Sun’s backend systems. such as status reports.2 Starting and Stopping ASR and SASM. you would stop SASM and ASR to avoid any fault telemetry being sent to Sun and the creation of unnecessary Service Requests. The email address associated with the Sun Online account is used by ASR to send a variety of ASR notifications.2 Starting and Stopping ASR and SASM This section explains how to stop and start your complete ASR environment. 7. If you change network and port settings used by ASR. as listed below: • • • Telemetry rules or other image upgrade to ASR.sun.2. From the ASR Manager system. on page 28 for instructions. In this case. Once unregistered.ini). Reasons for unregistering ASR can include the following: • If your current Sun Online Account is no longer valid. These changes are typically made in the SASM config.com) using your Sun Online Account. on page 38.2.2.

continue to the next section to restart ASR.3 Example Failed ASR Test Email. and started when ASR is started. 1.2. 7. Once complete. Error: Reference source not found.8 ASR Successful Registration Status Email. If changes are made to the SASM config.1 Example Heartbeat Failure Notification Email. 2. SASM should be stopped whenever ASR is stopped.2.3. and ASR Heartbeat emails.3 ASR Emails This section provides example emails that are generated by ASR.3.3.3. 7. 1.3.9 ASR Incomplete Registration Status Email ASR Installation and Operations Guide – July 2010 51 .5 Successful ASR Service Request Email: Blade Server Module.2.2.Note: Stopping SASM is optional. Run the following commands: svcadm enable sasm (starts SASM) /opt/SUNWasr/bin/asr start (starts ASR) 3.3. 7. Once ASR is stopped. These include test emails.2.4 Successful ASR Service Request Email. 7. 7. Service Requests. Be sure that ASR can send information to the Sun transport servers by running the following command: asr test_connection 7. depending upon what your purpose is. you must stop and restart SASM.2.3. Open a terminal window and log in as root on the ASR Manager system. Run the following commands: svcadm disable sasm (stops SASM) /opt/SUNWasr/bin/asr stop (stops ASR) 3. 2.3. 7. 7.2.2.2. for example. Open a terminal window and log in as root on the ASR Manager system.ini file.2 Example Successful ASR Test Email. you can perform the desired maintenance tasks.2 Starting SASM and ASR Use the following procedure to start SASM and ASR. In conformance with best practices. Examples of these ASR emails are listed below: • • • • • • • • • 7.6 Failed ASR Service Request Email. 7.2.2.

com> ASR backend has not received any communication from the SASM ASR Plugin on <Host name> during the last 50 hours. From: do-not-reply@sun. See [http://www. ASR Installation and Operations Guide – July 2010 52 .2. If the ASR Heartbeat detects a communications error to Sun.sun.com/support].1 Example Heartbeat Failure Notification Email This section provides an example email of a failed ASR Heartbeat notification.com> Subject: WARNING: Sun Microsystems ASR connectivity failure on: <Host name> ASR SASM hostname: <Host name> ASR registration ID: <Registration ID> ASR registration username: <customer@email. Is SASM ASR Plugin registered with Sun? 'asr show_reg_status' command shows the registration status. please request support via the Sun Member Support Center [http://www. Is SASM ASR Plugin running? 'asr diag' command provides a short status listing of SASM ASR Plugin bundles. The ASR Heartbeat should have been setup in a cron job during ASR installation. If a fault event on any of the ASR-enabled assets were to occur.10 Crontab Set-Up. please check: • • • • Is SASM ASR Plugin heartbeat enabled in cron? 'crontab -l | grep heartbeat' command shows the heartbeat cron entry. on page 30.3. as discussed in 5. To resolve this problem. Is SASM ASR Plugin able to communicate with Sun? 'asr test_connection' command performs a Sun transport test.com/service/asr] for more information about Auto Service Request.com Date: November 19. If you are unable to resolve this issue. 2009 10:06:57 AM MST To: <customer@email.sun. an email is sent to the Sun Online account used to register/install ASR. ASR would be unable to create a Sun Service Request.7.

asr-test@sun.sun.2. Contact Information: Name: ASR Test3 Telephone: 1-Testing-Please CANCEL SR.7. 2010 10:20:52 PM MST To: <customer@email.com> Subject: Sun Microsystems *Test* Service Request for host: <Host name> Service Request: N/A Severity: N/A Hostname: <Host name> Serial#: <Host serial number> Platform type: SUNW.comEmail: asrtest3@gmail.2 Example Successful ASR Test Email Below is an example of a successful test email sent from ASR when you run the asr send_test command from the ASR Manager system.SUN-FIRE-V215 SPARC SYSTEM Fault Information: Test Rule Matched: N/A This Service Request test-create was successful. ASR Installation and Operations Guide – July 2010 53 .3.com If the above contact information is incorrect.com/support] to make corrections. please access the Sun Member Support Center [http://www.com Date: January 11. From: do-not-reply@sun.

7. please access the Sun Member Support Center [http://www.com/service/asr] for more information about Auto Service Request.2.3 Example Failed ASR Test Email Below is an example of a failed test email sent from ASR when you run the asr send_test command from the ASR Manager system.com> If the above contact information is incorrect. See [http://www.3.sun. 2010 11:06:43 AM MST To: <customer@email.com Date: January 8. From: do-not-reply@sun. Contact Information: Name: <Customer technical contact name> Telephone: <Customer telephone number> Email: <customer@email. ASR was unable to create Service Request because: The asset cannot be activated because it is not qualified for ASR.sun. ASR Installation and Operations Guide – July 2010 54 .com> Subject: WARNING: unable to create Sun Microsystems *Test* Service Request for host: <Host name> Hostname: <Host name> Serial#: <serial #> Platform type: SUN FIRE X4640 This Service Request test-create failed.com/support] to make corrections. Please contact Sun Support Services or your Sun account team to correct this problem.

Service Request emails are sent to the Primary and Preferred Technical Contact associated with the system reporting a potential fault.x Probable Fan failure. If you need to change the severity or provide additional information regarding this issue.SUN-FIRE-V215 SPARC SYSTEM Fault Information: SUNMC event: ASR2.2.sun. please access the Sun Member Support Center [http://www.com> If the above contact information is incorrect. For more on how this contact is established or changed.2.SUNMC Contact Information: Name: <Customer technical contact name> Telephone: <Customer telephone number> Email: <customer@email.sun. fan-unit: MB/FIOB/FCB0/FT1 Rule matched:000214 .com/support] to make corrections. please access the Sun Member Support Center [http://www.com/support].3.v240_v440_v445_v245_v210_v215 .7. on page 13. A Sun Support Engineer will soon contact you to follow up on this Service Request.3 Validate Information in the Sun Member Support Center.com> Subject: Sun Microsystems Service Request <service request #> created for host: <Host name> Service Request: <service request #> Severity: 2 Hostname: <Host name> Serial#: <serial #> Platform type: SUNW. refer to 3. 2010 5:15:33 PM MST To: <customer@email.4 Successful ASR Service Request Email Service Request emails are generated whenever a Service Request is created at Sun that results from a hardware fault detection on any of your ASR-enabled systems. ASR Installation and Operations Guide – July 2010 55 .com Date: January 8. The following is an example of a typical Service Request email: From: do-not-reply@sun.

sun. ASR Installation and Operations Guide – July 2010 56 .5 Successful ASR Service Request Email: Blade Server Module Service Request emails are generated whenever a Service Request is created at Sun that results from a hardware fault detection on any of your ASR enabled systems.com/msg/SPX86-8001-7E Rule matched:1029_X2270_X4170_X4270_X4275_X6270_X6275 Contact Information: Name: <Customer technical contact name> Telephone: <Customer telephone number> Email: <customer@email.7.com Date: November 18. please access the Sun Member Support Center [http://www.com> Subject: Sun Microsystems Service Request <service request #> created for host: <Host name> Service Request: <service request #> Severity: 2 Chassis Host Name: <chassis host name> Chassis Serial#: <chassis serial #> Chassis Product type: SUN BLADE 6240 MODULAR SYSTEM Blade Host Name: <blade host name> Blade Serial#: <blade serial #> Blade Product type: SUN BLADE X6275 SERVER MODULE Fault Information: ILOM event: ASR2. 2009 12:06:02 PM MST To: <customer@email. on page 13.com/support].2.3 Validate Information in the Sun Member Support Center. refer to 3.com> If the above contact information is incorrect.2. If you need to change the severity or provide additional information regarding this issue. please access the Sun Member Support Center [http://www.sun. For more on how this contact is established or changed. A Sun Support Engineer will soon contact you to follow up on this Service Request. The following is an example of a Service Request email resulting from a potential fault on a Blade server: From: do-not-reply@sun.x http://www. Service Request emails are sent to the Primary and Preferred Technical Contact associated with the system reporting a potential fault.3.sun.com/support] to make corrections.

7. Contact Information: Name: <Customer technical contact name> Telephone: <Customer telephone number> Email: <customer@email. For more on how this contact is established or changed. please access the Sun Member Support Center [http://www. ASR Installation and Operations Guide – July 2010 57 . 2010 12:27:38 AM MST To: <customer@email.com/support] to make corrections. These emails indicate what issues may have prevented a Service Request from being created upon receipt of a hardware fault from ASR.com> If the above contact information is incorrect. From: do-not-reply@sun. on page 13.3.3 Validate Information in the Sun Member Support Center.2.x Probable fan failure ASR was unable to create Service Request because: Sun's customer relationship management system is experiencing delays in creating the Service Request.6 Failed ASR Service Request Email The following is an example of a failed Service Request email. Failed Service Request emails are sent to the Primary and Preferred Technical Contact associated with the system reporting a potential fault. refer to 3. Please contact Sun Support Services to request service.com/service/asr] for more information about Auto Service Request.com Date: January 5.sun.2.sun.com> Subject: WARNING: unable to create Sun Microsystems Service Request for host: <Host name> Hostname: <Host name> Serial#: <Serial #> Platform type: SUN FIRE X4100 M2 Fault Information: ILOM event: ASR2. See [http://www.

10 Crontab Set-Up. please run the following command: asr update_rules This will download the latest fault rules version and update the ASR rules. Note: If the asr heartbeat is disabled in crontab.7 Fault Rules Update Email The following email is sent to the Sun Online account associated with the ASR installation if ASR detects that its fault rules are out of date.2.7. you will not be notified. 2009 12:54:22 AM MDT To: <customer@email. See [http://www. To be sure your fault rules are current.com Date: October 8. The latest version is 2.3. on page 30 for more information on fault rules. via email. 5.sun.com> Subject: ASR fault rules are out of date on: <Host name> ASR SASM hostname: <Host name> ASR registration ID: <Registration ID> ASR registration username: <customer@email.com/support].com> The ASR fault rules are out of date on this system.com/service/asr] for more information on the rules bundle and its contents. ASR Installation and Operations Guide – July 2010 58 . please request support via the Sun Member Support Center [http://www. if your ASR fault rules are out of date with the most current release. you can run the asr update_rules command from the ASR Manager system. From: do-not-reply@sun. If you are unable to resolve this issue.5 On the SASM/ASR host <Host name>.sun.

com> Sun Online Account company: <Customer company name> Registration Status: Successful.com> <Customer Address> • To resolve problems with Serial# or Platform. • ASR Installation and Operations Guide – July 2010 59 .com Date: January 8.3.com/service/asr]. See ASR documentation [http://sun.sun.8 ASR Successful Registration Status Email The following email is sent to the Sun Online account associated with the ASR installation to show a summary of a successful registration and ASR Assets: From: do-not-reply@sun.com> Subject: Sun Microsystems ASR Status . To resolve problems with contracts or Technical Contacts. Yes Serial# 0000000000000 Contract Type Warranty category 3: Next Business Day Warranty category 3: Next Business Day Contract # <Contract #> Contract Expiration 14 Jun 2010 ASR Activation Request Date 04 Jan 2010 18:32:46 MST Technical Installation Contact Address Unknown Unknown x ✔ <Serial #> <Host name> <Contract #> 27 July 2010 04 Jan 2010 18:32:46 MST <customer@e mail. please use the Sun Member Support Center [http://www.2.com/support] to make any needed changes. please check your ASR Manager configuration and serial number information on the asset. Activation Status Summary: Non-activated Assets : 25 Activated Assets : 11 Total : 36 Device Hostname and Platform <Host name> SUN BLADE 6000 MODULAR SYSTEM SUN FIRE X4600 ASR Activated? No Serial number is not valid. 2010 6:00:39 AM MST To: <customer@email.7. You may also contact your Sun account team or Sun Support Services.Hostname: <Host name> on 08 Jan 2010 06:00:34 MST ASR hostname: <Host name> ASR registration ID: <Host registration ID> Sun Online Account username: <customer@email.

Sun Online Account <customer@email. 2010 6:00:39 AM MST To: <customer@email. Sun Online Account <customer@email.sun. Sun Online Account <customer@email.com/service/asr]. To resolve problems with contracts or Technical Contacts.com Activation Status Summary: Non-activated Assets : 25 Activated Assets : 0 Total : 25 Device Hostname and Platform <Host name> SUN BLADE 6000 MODULAR SYSTEM ASR Activated? No Serial number is not valid.9 ASR Incomplete Registration Status Email The following email is sent to the Sun Online account associated with the ASR installation to show a summary of an incomplete registration of ASR Assets: From: do-not-reply@sun.2. See ASR documentation [http://sun.3.com> does not have City set. • ASR Installation and Operations Guide – July 2010 60 . You may also contact your Sun account team or Sun Support Services. Please correct this problem via http://reg.com/support] to make any needed changes.com Date: January 8. please check your ASR Manager configuration and serial number information on the asset. Sun Online Account <customer@email.com> Sun Online Account company: <not set> Registration Status: Incomplete Data.7.sun. please use the Sun Member Support Center [http://www. Serial# 0000000000000 Contract Type Warranty category 3: Next Business Day Contract # <Contract #> Contract Expiration 14 Jun 2010 ASR Activation Request Date 04 Jan 2010 18:32:46 MST Technical Installation Contact Address Unknown Unknown x • To resolve problems with Serial# or Platform.com> Subject: Sun Microsystems ASR Status .Hostname: <Host name> on 08 Jan 2010 06:00:34 MST ASR hostname: <Host name> ASR registration ID: <Host registration ID> Sun Online Account username: <customer@email.com> does not have Zip/Postal Code set.com> does not have a telephone number set. Sun Online Account <customer@email.com> does not have Company set.com> does not have Address set.

4 Confirm SASM Network Settings. This command will return the new port value that you entered. as discussed in 5. Verify the change /opt/SUNWsasm/bin/sasm getprop | grep com.1 ASR Port Usage.3. FMA enrichment for getting additional diagnostics information.7.snmp.port=162 to listen on whatever port is appropriate. 7. 7.3 Configure ASR to Send HTTPS Traffic Through a Proxy Server This procedure should be used to enable network communications in cases where you have a SOCKS proxy server mediating network traffic between the ASR Manager and the internet.3.svc. For sending telemetry messages to the ASR Manager.ini file as follows: 1.3.3.3.svc. 1.5 Test Connectivity from the ASR Manager to Sun.3. 7.3.container.sun.1 Source ASR Port Usage Destination ASR Backend (Sun) ASR Asset ASR Manager ASR Asset Protocol https http snmp udp snmp (get) udp Port 443 6481 162 161 Description For sending telemetry messages to the ASR backend systems at Sun. Restart SASM: svcadm restart sasm 3.container. ASR Manager ASR Manager ASR Asset ASR Manager 7.3 Configure ASR to Send HTTPS Traffic Through a Proxy Server.3. Change com.2 Changing the Default SNMP Port for ASR You can change the default SNMP port on the ASR Manager by editing the /var/opt/SUNWsasm/configuration/config.sun.8 Register the ASR Manager. 162 is the default. Open a terminal window and log in as root to the ASR Manager system.port 4.snmp.3 ASR Network Parameters Management The following topics are provided in this section for networking related tasks for ASR operations: • • • • • 7. 7. 7. 2. on page 28. The following table explains the network ports used by ASR. For other proxy server types. Service Tags listener for Asset activation. you need to re-register ASR to set-up the proxy server information. 7. ASR Installation and Operations Guide – July 2010 61 .2 Changing the Default SNMP Port for ASR.

socks.com 443 If you have a web browser.transport. If the results of the above commands do not indicate the Data Transport Service is operating.root= https://transport.sun. or you might need to add transport. socksProxyHost= socksProxyPort= java.ini | grep socks 7.sun.net.sun.com. Restart ASR using the following command: svcadm restart sasm To verify the changes.root /var/opt/SUNWsasm/configuration/config. If a web browser is unavailable.3.com or.uk 2.4 Confirm SASM Network Settings The following command can be used to confirm that the network parameters used by SASM to connect to Sun’s ASR backend systems are properly set.sun. or Africa regions. or Africa Regions: wget https://transport.sun. Contact a Network Administrator if needed. ASR Installation and Operations Guide – July 2010 62 .username= java. grep transport. or you are in Europe. Listed below are possible resolutions: • The issue could be a DNS problem.sun.container. run the following command: cat /var/opt/SUNWsasm/configuration/config. Complete one of the following steps from the ASR Manager to verify connectivity to Sun’s ASR backend systems: • • • telnet transport.ini 3.com 7. the Middle East. 1.socks.com to the /etc/hosts file.net. go to https://transport. edit the following file by changing the SOCKS proxy information as needed: /var/opt/SUNWsasm/configuration/config. for Europe.ini The ASR transport hostname is displayed and will be similar to the results shown below: com.3.co.5 Test Connectivity from the ASR Manager to Sun The following procedure can be used to confirm proper communication between the ASR Manager and Sun’s ASR backend systems. Using an editor of your choice (such as vi).svc.sun. The following entries must be made within the file. 5.2. The web page should indicate that the Data Transport Service is operating. Middle East. run one the following commands from a terminal window: wget https://transport.password= 4. you must resolve your network connection issue.

on page 16 for the specific ASR network requirements. Refer to 4. Network.4 ASR Integration with Enterprise Monitoring Systems Other environments are set up to use different enterprise monitoring systems (e.. Once installed and properly configured.g. the issue could be that the proxy information has not yet been configured to ASR and SASM. Once the service request/test alert information is available to the SASM ASR Plugin. The SASM ASR Plugin polls the ASR backend whenever a fault event or test alert occurred and updates its local database with service request or test alert information. the Sun Support Services coverage and response times are delivered in accordance with your Sun Warranty or the SunSpectrum Support Contract. the ASR software is capable of sending ASR service-request information to these systems.5.) Beginning with version 2. Java. During installation of the ASR software package. ASR provides the following integration features with enterprise monitoring systems: • • • Ability to configure SNMP trap destination from SASM ASR to enterprise monitoring systems Send case creation and test alert messages to enterprise monitoring systems New ASR MIB that provides the data model of ASR case creation notification Examples of enterprise-monitoring systems include: • • • • • • IBM Tivoli HP OpenView BMC Patrol Unicenter xVM Ops Center Any monitoring tool that can receive an SNMP v2c trap. etc. ASR is designed to generate a service request after specific faults are detected. HP OpenView. Once the service request is opened.• • You may need to contact your network administrator for assistance. 7. the SNMP trap destination can be configured from the SASM host to monitoring systems. as discussed in the following procedure. Solaris.1 Verify: Hardware. it sends an SNMP v2c trap to the enterprise monitoring systems and include the following service request/test alert data defined in the ASR MIB: • • • • • • • Hostname IP address Serial# Platform type Fault information (one line description) Fault information knowledge link Service Request number • • • • • • Link to Service Request number Service Request status information (for "unable to create SR" problems) Severity of Service Request SR creation time Fault detection time Customer Contact information ASR Installation and Operations Guide – July 2010 63 . If you use a proxy server. This is done by registering ASR. IBM Tivoli. Once the ASR-capable assets are activated.

Example: Created Additional information associated with the fault can be added as name/value pairs. Notification traps from older ASR manager versions will not have any sample values for SR information. Configuring Trap Files Set ASR notification trap destination: asr set_notification_trap -i <ip_address> -p <portNumber> -c <community string> example: asr set_notification_trap -i 127.4. chassis serial number is used.2 MIB Location and Data Elements The “SUN-ASR-NOTIFICATION-MIB” file is located at: /var/opt/SUNWsasm/configuration/SUN-ASR-NOTIFICATION-MIB.3.Note: For the test SR.12. Date and time when the Service Request was created. Product Type of the system for which the Service Request was created.1.0. Status indicating the processing of Service Request creation. IP address of the system for which the Service Request was created. Show ASR notification trap destination: asr show_notification_trap Delete ASR notification trap destination asr delete_notification_trap 7. For chassis and blade systems.5.0.4. 7.mib Data Element sunAsrSrHostname sunAsrSrIpAddress sunAsrSrSerialNumber sunAsrSrPlatformType sunAsrSrCreationDateTime sunAsrSrFaultDetectionDateTime sunAsrSrCreationStatus sunAsrSrAdditionalInfo Description Hostname of the system for which the Service Request was created.1.42.7 Test SR notification trap will have sample values for SR number.1.4.1 1.1) will show "Test Service Request was successful" for a successful test SR. For example: <additional-information name=chassis_host_name>chassisHostName</additional-information> <additional-information name=chassis_serial_number>chassisSerial</additional-information> ASR Installation and Operations Guide – July 2010 64 .232. 3. Date and time when the fault was generated. and also when the test SR (test SNMP alert from the ASR asset menu) is successful 2. a notification trap "fault summary"(.1 -p 162 -c public Note: Port “162” in the example is the destination port on your monitoring system. No traps will be sent in other scenarios . The notification trap will be sent only when a new service request (SR) is created successfully. ASR 2.especially when either the SR or test SR has failed to be created. SR link and SR severity.1. Product serial number of the system for which the Service Request was created.2.6.

Link to a knowledge article for the fault that was reported.pkg 2.<timestamp>.5 or later package and extract the . you can still obtain the ASR Diagnostic Utility by extracting the necessary files from the bundle. Email address of Customer Contact associated with the Serial Number of the Device for which the Service Request was created. Verify the ASR Diagnostic Utility files are present in: SUNWswasr/reloc/opt/SUNWswasr/util/diag 5.4 and Earlier 1. Copy the files (see below) to another directory. run: pkgtrans SUNWswasr. 4.asr./asrDiagUtil. • • Customer contact information associated with the device reporting the fault.zip file. will need to be sent to Sun manually.Java method for collecting diagnostic data README – a “readme” text file describing the utility At command prompt.sh and follow the on-screen instructions on where the diagnostic data file is being generated.shell script for invoking the utility method com. For users of ASR 2. Run the utility.properties . ASR Installation and Operations Guide – July 2010 65 . configurable location for later retrieval/delivery and analysis. Verify the ASR Diagnostic Utility files are located under /opt/SUNWswasr/util/diag 3. 7.5. Name of Customer Contact associated with the Serial Number of the Device for which the Service Request was created. Severity of the Service Request opened for the reported fault. Verify a SUNWswasr subdirectory is created.5. sunAsrSrTelephone sunAsrSrEmail Telephone number of Customer Contact associated with the Serial Number of the Device for which the Service Request was created. 6.Data Element sunAsrSrFaultSummary sunAsrSrKnowledgeLink sunAsrSrNumber sunAsrSrLink sunAsrSrSeverity sunAsrSrName Description Brief summary of the fault for which the Service Request was created. After you download the latest ASR software bundle.diag. run .sun.jar .5 ASR Diagnostic Utility As part of ASR v2. Download the ASR 2.<timestamp>. This utility packages the data collected and stores it in a consistent.svc.pkg .1 Delivery Model The ASR Diagnostic Utility is available as part of the ASR 2. The . 2.util. Run the utility.5 software bundle.4 or earlier.<version>. The ASR Diagnostic Utility consists of the following files: • • • • diag-config. which is created. Retrieved from the Sun Case Management System.gz file.<version>.property file for customizing the diagnostic utility configuration asrDiagUtil. access and run the utility: ASR 2. Service request number URL for accessing the Service Request information. At a command prompt. a ASR Diagnostic Utility is included to provide analysis support of any installation problems. Install SUNWswasr. 3.sh .x. ASR 2. 7.5 and Later 1.

com.zip.svc.asr.2 Configure the ASR Diagnostic Utility The diag-config.util.7.asr.util.util.properties file consists a list of properties for specifying location of the configuration and log directories.diag.directory – The property for specifying where the diagnostic data .sun. It also contains "toggle switches" for enabling and disabling a particular data set to be collected: • • • com.prefix – The property for configuring the diagnostic data .5.zip. com.diag.sun.sun.home.file.diag.recursive property – The property for enabling traversing into subdirectories of any configuration or log directories.svc.svc. Default is current directory where the ASR Diagnostic Utility is located.zip bundle will be generated.asr. ASR Installation and Operations Guide – July 2010 66 .zip file's name.

Error: Reference source not found. 8.1.3 Check Service Tags Probe.1. The following topics are provided: • • • • • • • • 8.1.6 Uninstall ASR.1. 8.1 Check the STB Agent. This section contains the following topics: • • • • • • • • • 8. If issues arise during the installation and operation of ASR.5 Error Messages and Resolutions. 8.1.1. 8. 8. 8. 8. STB may be part of the issue.6 Service Tags on Asset Reports Unknown or Empty Serial Number/Product Name.3 Check the State of ASR Bundles.1. 8.1 Service Tools Bundle Troubleshooting (STB) This section provides a variety of steps to check on the state of the Service Tools Bundle (STB) that must installed on most ASR systems.4 ASR Log Files. 8.4 Check Service Tags Listener.2 Check the State of the SMA Service.1 Service Tools Bundle Troubleshooting (STB). 8. 8.0 ASR General Troubleshooting This section provides a variety of troubleshooting procedures for the ASR software.1.7 Activation Failed for Asset <asset name> Due to Data Error.CHAPTER 8 8.8 stdiscover or stlisten Services are Disabled ASR Installation and Operations Guide – July 2010 67 .7 Upgrade ASR. 8.2 Check the Service Tags Version. Move Assets to a New ASR Manager 8. 8.5 Unable to Contact Service Tags on Asset.9 ASR Manager Crashed. 8.

1. Inc. http://asr_system_hostname:6481/stv1/agent/ 2. run the following command: svcs -l svc:/network/stdiscover 3.1 1.4.</cpu_manufacturer> <serial_number>0707FL2015</serial_number> <hostid>846ffcc4</hostid> </system_info> </agent> </st1:response> 3.4</agent_version> <registry_version>1.stlisten man stclient 8. To determine that the Service Tag discovery probe is running.</manufacturer> <cpu_manufacturer>Sun Microsystems.1. If you do not get a response from the Service Tags agent. Check the Service Tags Version Use the following procedure to check the Service Tags version. A response similar to the following will be displayed: <st1:response> <agent> <agent_urn>urn:st:234ebb6b-8a7f-6563-a57e8bf14c7d258d</agent_urn> <agent_version>1.8.10</release> <architecture>sparc</architecture> <platform>SUNW. 2.Sun-Fire-V215::Generic_137111-06</platform> <manufacturer>Sun Microsystems.1. 8. Inc.4</registry_version> <system_info> <system>SunOS</system> <host>s4u-v215c-brm03</host> <release>5. Open a terminal window and log in as root to the ASR system you wish to check.1. 2. If the probe is running correctly.3 1.1. consult the Service Tags man pages: man in.1.2 1. Run the following command to get the Service Tags version: stclient -v Note: ASR requires Service Tags version 1. Be sure to include the / after agent. Open a terminal window and log in as root to the ASR system you wish to check. Check the STB Agent Open a browser window to the system you wish to check using the following command. Check Service Tags Probe Use the following procedure to determine that the Service Tag discovery probe is running. the following information is displayed: fmri svc:/network/stdiscover:default name Service Tag discovery probe enabled true ASR Installation and Operations Guide – July 2010 68 .

it means Service Tags is not installed on the ASR asset. Also the issue can be network connectivity between ASR Manager and the ASR Asset. Check if the Service Tags services are installed and online using the following command: svcs | grep reg 4.stlisten:<SASM host name> 69 ASR Installation and Operations Guide – July 2010 . Open a terminal window and log in as root to the ASR system you wish to check.1. To determine if the Service Tags listener is running. Check if Service Tags is installed and running on an ASR asset. Complete the following checks: 1.4 1.state online next_state none state_time Wed Sep 03 21:07:28 2008 restarter svc:/network/inetd:default 8. The results should be similar to the following example: online Sep_09 svc:/application/psncollector:default Make sure that there are no TCP Wrappers installed on the ASR asset to prevent any service tags discovery issues. If you cannot run this command. use the following command: stclient -x 2. use the following command: svcs | grep psncollector 7. If there are TCP wrappers installed on the ASR asset. the following information is displayed: fmri svc:/network/stlisten:default name Service Tag Discovery Listener enabled true state online next_state none state_time Wed Sep 03 21:07:28 2008 restarter svc:/network/inetd:default xibreXR_US root@s4u-v215c-abc12 8. edit /etc/hosts.1. Check Service Tags Listener Use the following procedure to determine that the Service Tags Listener is running. 6. 2. If the Service Tags services are online.5 Unable to Contact Service Tags on Asset This message indicates that the activation failed during Service Tags discovery. 3. 8. The results should be similar to the following example: online Aug_23 svc:/application/stosreg:default online Aug_23 svc:/application/sthwreg:default 5. If you cannot find these services. If the listener is running correctly. The issue can be either Service Tags is not installed on the ASR Asset or is installed but not running.allow on the asset by adding: in. either Service Tags is not installed or not online. run the following command: svcs -l svc:/network/stlisten 3. check if psncollector is online. Run the following command from the ASR Manager system: wget http://<<assetHostNameOrIPaddress>>:6481/stv1/agent/ 9.

run the following command: svcadm restart psncollector Note: If you are using SNEEP version 2. on page 24. Input the correct serial number using the SNEEP command: /opt/SUNWsneep/bin/sneep -s <serial number> Note: SNEEP is part of the Services Tools Bundle that is a prerequisite of ASR (for more information. For versions of SNEEP older than 2. 4. it is not necessary to manually restart the psncollector after inputting the serial number. it means Hardware Service Tags is not installed on the ASR asset.8. To resolve this message. on page 24. see 5. enter the following command: svcadm restart psncollector Note: If you are using SNEEP version 2.1.7 Activation Failed for Asset <asset name> Due to Data Error This message indicates that the message creation failed because of bad or missing data. 2. this error is the result of a bad serial number or product name.6. 8.6. 3. Most of the time.3 Install Service Tools Bundle (STB).3 Install Service Tools Bundle (STB).6. it is not necessary to manually restart the psncollector after inputting the serial number. ASR Installation and Operations Guide – July 2010 70 . see 5. If serial number is not correct then input the correct serial number using the following SNEEP command: /opt/SUNWsneep/bin/setcsn -c <serial number> Note: SNEEP is part of the Services Tools Bundle that is a prerequisite of ASR (for more information. The results should be similar to the following example: online Aug_23 svc:/application/sthwreg:default If you cannot find this service. 3. For versions of SNEEP older than 2.6. complete the following steps: 1.1.6 Service Tags on Asset Reports Unknown or Empty Serial Number/Product Name If serial number is empty or "unknown" complete the following steps: 1. Verify the serial number using the SNEEP command: sneep 2. You can view the serial number using the following URL: http://<AgentipAddress>:6481/stv1/agent/ If product name is empty or "unknown" check if the Hardware Service Tags are installed and online using the following command: svcs | grep sthwreg 5. 6.

8 1. 8. 4.2 Check the State of the SMA Service The SMA service needs to be online in order to support FMA enrichment data properly.1. Check to determine if the stdiscover or stlisten services are disabled. 3. You can view the serial number using the following URL: http://<AgentipAddress>:6481/stv1/agent/ Check if the Hardware Service Tags are installed and online using the following command: svcs | grep sthwreg 6. the state should indicate online.4. ASR Installation and Operations Guide – July 2010 71 . If SMA is online. it means Hardware Service Tags is not installed on the ASR asset. The results should be similar to the following example: online Aug_23 svc:/application/sthwreg:default If you cannot find this service. Prior to configuring FMA. run the following command: svcs sma 2. To check that the state of the SMA service is online. run the following command: svcadm enable stlisten stdiscover Verify the services are online: svcs stlisten stdiscover Once the services have been enabled. 7. If SMA is not online. STIME 12:20:14 12:20:14 FMRI svc:/network/stdiscover:default svc:/network/stlisten:default To enable the stdiscover and stlisten services. as in the following example: STATE STIME FMRI online 15:40:31 svc:/application/management/sma:default 3. stdiscover or stlisten Services are Disabled Service tag processes (stlisten and stdiscover) must be online in order to activate assets successfully. Run the following command: svcs stlisten stdiscover If the services have been disabled. 5. the output would look like this: STATE online online STIME 0:28:31 0:28:31 FMRI svc:/network/stlisten:default svc:/network/stdiscover:default 8. run the following command to enable it: svcadm enable sma Repeat these steps to confirm SMA is online. complete the following steps: 1. the output would look like this: STATE disabled disabled 2.

svc.svc.asr. enter the following commands: asr stop asr start 5. it may be necessary to check the state of various application bundles installed on the ASR Manager system using the following procedure.0.0. Enter the following command: asr diag 3. It contains not only informational data.4 ASR Log Files When you are troubleshooting ASR.sun.sun.sun.6 and later: /var/opt/SUNWsasm/log For ASR 2.svc. Log files are located on the ASR Manager system at: For ASR 2. but both warnings.sw-frag_1.8.0. run the following commands: asr test_connection asr send_test 8.sun.sw-frag should be RESOLVED com. Open a terminal window and log in as root to the ASR Manager.0 /fragnebts=264. The logs are written to the swasr.ServiceActivation_1.sw-rulesdefinitions_1. 1. If you are gathering as much ASR Installation and Operations Guide – July 2010 72 .sun. ASR begins overwriting the oldest file. Repeat steps 1 to 3.0 Master=263 266 ACTIVE com. Review the results of this command below along with the settings you should see.0 The state of each bundle should be as follows: com.asr.sun.asr. This is the default setting. 2.sun.5 and earlier: /var/opt/SUNWsasm/configuration There are three levels of logs: 1. you can change the level of information displayed in the logs. Once that number is reached.sw bundle should be ACTIVE com.asr.asr. 3.svc.svc.svc.3 Check the State of ASR Bundles For diagnostic purposes.log files.svc. 2. The default number of logs collected and saved is 5. and increase or decrease the number of logs that are saved before being overwritten. If any of these states are incorrect.0. severe messages only.0 Master=263 265 RESOLVED com. Warning: Displays warnings and severe messages. 6.asr. 265 264 RESOLVED com. id State Bundle 263 ACTIVE com.sun.sw-rulesdefinitions should be RESOLVED com.Service Activation should be ACTIVE 4. You have the option to change the number of logs collected and saved. Info: Displays the highest level of information.svc. and severe messages. Severe: Displays the least amount of information. To ensure everything is working properly.sw_1.

Warning. Open a terminal window and log in as root on the ASR Manager system.5. or Severe 8.4. 2. ASR Installation and Operations Guide – July 2010 73 .2 Only One Client Can Access Console at a Time. enter the following command: asr set_logfilecount number 8.1 Error Messages and Resolutions. 8.5 Error Messages and Resolutions This section provides a variety of error conditions and resolution steps. enter the following command: asr get_logfilecount 3. enter the following command: asr get_loglevel 3. The following topics are provided: • • 8.2 1. 8.4. 2.5. To change the logging level. enter the following command: asr set_loglevel level The choices for level are: Info. Set Log File Counts Use the procedure below to set log file counts.information as possible in a short time. To view the current level of information being gathered. Open a terminal window and log in as root on the ASR Manager system. you might want to limit the number of logs saved to accommodate the larger files. To change the number of logs being saved. Set Log level Use the procedure below to set logging levels.1 1. To view the current number of logs being saved.

168. When a failure error is encountered. WARNING: This trap is rejected because the asset is disabled Enable the ASR asset using one of the following commands: asr enable_asset -i ip (where ip is the IP address of the ASR asset) or asr enable_asset -h host (where host is the hostname of the ASR asset) Activate the ASR Manager using one of the following commands: asr activate_asset -i ip (where ip is the IP address of the ASR Manager) or asr activate_asset -h host (where host is the hostname of the ASR Manager) WARNING: this trap is rejected because SASM ASR Plugin is not activated WARNING: this trap is rejected because the Activate the ASR asset using one of the following commands: asset is not found asr activate_asset -i ip (where ip is the IP address of the ASR Asset) or asr activate_asset -h host (where host is the hostname of the ASR Asset) SEVERE: Cannot attach snmp trap to snmp service! Failure to Register Errors This indicates that there could be another process using the port 162.5.3.sun.ini file is incorrect or missing.8. Kill that process and then run the following command: svcadm restart sasm The sasm.com/display/ASRSO/Sun+Products+Qualified+f or+ASR/. The socks configuration in the config.sun. This usually means that you need to add an entry of transport.3 Enable M-Series XSCF Telemetry on page 38 for more details) Review the FMA trap destination configuration file.log This error indicates that the host running ASR and the SASM ASR Plugin cannot resolve the name transport. This error indicates that the communication between transport server and Sun is down or busy.sun. ASR Manager requires public as the value of the community string in order to retrieve FMA enrichment and additional fault details. No Such Host Exception Not Authorized. 2. Review the community string properties on the asset. and restart sma and fmd SMF services.232.1 Error Messages and Resolutions Resolution 1. This error indicates one of the following: 1. This can also indicate that the queue set-up is wrong or that the user does not have permissions to the queue. Error Message WARNING: Unable to retrieve fault details. See the ASR General Troubleshooting Section.com. Action: This usually indicates that you need to supply a user/password for the socks settings. For additional information and some insights into how to correct. (See 6.com/198.com/service/asr.156 in the /etc/hosts file (or the name_service file you are using). please see the ASR Installation and Operations Guide located at www.sun. 3.log has more detailed information and a java stacktrace on what failed during registration. additional details can be found in: /var/opt/SUNWsasm/configuration/sasm. Verify that the asset has got the right Solaris minimum required version and patch level as per the ASR qualified systems web page (https://wikis. The Sun Online Account provided could not be verified by the transport server Socket Exception: Malformed reply from SOCKS server ASR Installation and Operations Guide – July 2010 74 .

If SASM is running.sun. 8. on page 47. on page 50.svc. Important: If you wish to remove ASR for the long term.container.3 Configure ASR to Send HTTPS Traffic Through a Proxy Server. on page 17. If uncertain. Refer to 7. 2. on page 48. Each command has a max handle on the connection for 60 seconds before SASM console kills the connection. Deactivate the ASR Manager. kill the process using the following command: kill -9 Process_ID (for example.2 Telemetry Sources: Overview and Check. 5.6 Deactivate/Activate ASR Assets. or partially for the purpose of an upgrade.6 Deactivate/Activate ASR Assets. Deactivate all ASR Asset(s). remove telemetry traps that send hardware telemetry to the ASR Manager. Refer to 7. do the following: 1. 4.7 Add/Remove Telemetry Traps from ASR Asset(s). the SASM transport service used by these plug-ins will be unregistered as part of this process. Resolution The socks is not able to route to the transport server endpoint.1. refer to 4.jar:/var/opt 2. Consult your plug-in documentation to reregister the SASM transport service. Remove the telemetry traps. if needed.ManagementTier. If you still get same message. Action: Add the correct http proxy information or socks settings.1. From all ASR Asset systems. or for an ASR upgrade. Try executing the command after 60 seconds.5. Check if SASM is running: ps -ef | grep SUNWsasm Results: root 16817 1 0 16:09:49 ? 4:24 java -cp /var/opt/SUNWsasm/lib/com. Refer to 7. Refer to 7. Refer to 7.3.1. Restart the SASM using the following command: svcadm restart sasm 8. Unregister ASR. it indicates that only one command can go into the SASM admin port at a time. 6.Error Message 2.2 Only One Client Can Access Console at a Time If you get this error message running an ASR command on the ASR Manager system.1 Register/Unregister ASR.2. Use the following steps: Identify what telemetry sources reside on the systems. 16817) 3. pkgrm SUNWswasr ASR Installation and Operations Guide – July 2010 75 . on page 61 to correct the information. • • 3. start with the procedures below. start at step 6.6 Uninstall ASR The following procedure explains how to remove ASR completely. be sure to remove those traps as well. on page 47. If you are collecting telemetry from the ASR Manager itself. Important: If you are using other SASM plug-ins (for example SFT). Remove the ASR package from the ASR Manager system. 1. If you are removing ASR for a short time.

Note: If the asr heartbeat is disabled in crontab. Refer to 5. 8. on page 27. you will not be notified. on page 26.5 Download the SASM and ASR Packages.3.8 ASR Fault Rules Updates ASR uses fault rules to filter the telemetry data sent from ASR Assets. do not remove it. Obtain the new ASR and SASM packages. the ASR Manager automatically downloads and installs the latest rules bundle. To be sure your fault rules are current. on page 26 for more information on SASM.).7 Install the ASR Package.7 Fault Rules Update Email. Install ASR.10 Crontab Set-Up. rm -r /var/opt/sunwsasm After completing the steps above. Refer to 5. ASR asset database. For more information on fault rules. on page 30. refer to: • • 5. Install SASM. 3. 8. • • Uninstall ASR. run the following command to remove leftover artifacts (SASM log files.” The filtering process also ensures that telemetry that contains faults is reported. 2. Remove the SASM package from the ASR Manager system. on page 27. This filtering is done to remove telemetry that contains no real fault data and general telemetry “noise. as explained in the referenced instructions.7.2.7 Upgrade ASR Use the following procedure to upgrade ASR.6 Install the SASM Package. If you did not remove SASM during the uninstall of ASR. When there are new rules. 9. via email. Otherwise. the uninstall of ASR is complete. Be sure to register and activate the ASR Manager.6 Uninstall ASR. pkgrm SUNWsasm If you never intend to use ASR and SASM again. configuration files. Refer to 8. ASR installs a cron job on the ASR Manager system to periodically check Sun’s auto-update server for any new rules updates. Refer to 5.4 Check the Existence of SASM and Version. etc. if your ASR fault rules are out of date with the most current release. skip this step. 7. on page 58. ASR Installation and Operations Guide – July 2010 76 . an email is sent to the Sun Online account used to install and register ASR. If the cron job is not set to download the fault rules automatically. you can run the asr update_rules command from the ASR Manager system. 8. Refer to 5. you can still install the new SASM package. 1. Removing this package is optional and is often done to reduce system overhead. If you have other applications running under SASM. Install the new SASM and ASR packages. These fault rules can change as ASR improves its filtering and as new platforms and telemetry sources are supported by ASR.

g. An ASR Manager is set up (e.10.g. 4. 3. All ASR assets are now activated on ASRHOST02 ASR Installation and Operations Guide – July 2010 77 .. and the trap destination is changed to report failures to ASRHOST02. A critical failure occurs in the cabinet of ASRHOST01 (for example: a fire destroys the system and its data). This ASR host is registered and activated to itself. and all ASR assets are activated on the host. All ASR assets are now re-configured to report failures to the new ASR Manager host ASRHOST02. 5. The assets need to be attached to a different ASR Manager host (e.10. The following steps describe a sample scenario: 1.g.1) and configured on the network. IP address: 10. All ASR assets are configured to report failures to the ASR Manager host (ASRHOST01). IP address: 10. hostname: ASRHOST02). A new ASR Manager is set up (e. hostname: ASRHOST02.2) and configured on the network. Move Assets to a New ASR Manager In cases where an ASR Manager experiences a critical failure..9 ASR Manager Crashed.8. 6. you can set up a new ASR Manager and reconfigure ASR Assets to report to the new host.10..10. 2. The new ASR host is registered and activated to itself. hostname: ASRHOST01.

Parameter Sun Online Account Organizational ID Contract ID Sun Account Manager Name/Phone Proxy Server Information (if applicable) Hostname: IP: Details Username: Password: ASR Installation and Operations Guide – July 2010 78 .0 Installation Aids – Forms This section provides a sample Installation Parameters form and an ASR Systems Tracking form.1 Installation Parameters Form Use this form to capture key information used for the ASR installation.CHAPTER 9 9. 9.

2 ASR Systems Tracking Form Use this form to track all ASR systems that are to be installed.9. Host Name and IP SP Name annd IP Platform Type Location Serial Number Validated in MSC MSC Tech Contact and Email Telemetry Sources Port Changes from Defaults ASR Manager Systems ASR Asset Systems ASR Installation and Operations Guide – July 2010 79 .

Host Name and IP SP Name annd IP Platform Type Location Serial Number Validated in MSC MSC Tech Contact and Email Telemetry Sources Port Changes from Defaults ASR Installation and Operations Guide – July 2010 80 .

Sign up to vote on this title
UsefulNot useful