Sun Microsystems Sun Management Center User Manual

Download

Sun™ Management Center

2.1 Supplement for Starfire Servers

Sun Microsystems, Inc.

901 San Antonio Road Palo Alto, CA 94303-4900 USA 650 960-1300 Fax 650 969-9131

Part No.: 806-1581-10 Revision A, November 1999

Send comments about this document to: docfeedback@sun.com

Copyright 2000 Sun Microsystems,Inc.,901SanAntonioRoad,PaloAlto,California94303-4900U.S.A.Allrightsreserved. This productordocumentisprotectedbycopyrightanddistributedunderlicensesrestrictingitsuse,copying,distribution,anddecompilation.

No part of this productordocumentmaybereproducedinanyformbyanymeanswithoutpriorwrittenauthorizationofSunanditslicensors, if any. Third-partysoftware,includingfonttechnology,iscopyrightedandlicensedfromSunsuppliers.

Parts of the productmaybederivedfromBerkeleyBSDsystems,licensedfromtheUniversityofCalifornia.UNIXisaregisteredtrademarkin the U.S. and other countries, exclusively licensed throughX/OpenCompany,Ltd.

Sun, Sun Microsystems,theSunlogo,AnswerBook2,docs.sun.com,Java,SunEnterprise,SunStorEdgeA5000,Ultra,Starﬁre,andSolarisare trademarks, registeredtrademarks,orservicemarksofSunMicrosystems,Inc.intheU.S.andothercountries.AllSPARCtrademarksareused under license and aretrademarksorregisteredtrademarksofSPARCInternational,Inc.intheU.S.andothercountries.Productsbearing SPARC trademarks are based upon an architecturedevelopedbySunMicrosystems,Inc.

The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems,Inc.foritsusersandlicensees.Sunacknowledges the pioneering effortsofXeroxinresearchinganddevelopingtheconceptofvisualorgraphicaluserinterfacesforthecomputerindustry.Sun holds a non-exclusive license fromXeroxtotheXeroxGraphicalUserInterface,whichlicensealsocoversSun’slicenseeswhoimplementOPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.

RESTRICTEDRIGHTS:Use, duplication, or disclosurebytheU.S.GovernmentissubjecttorestrictionsofFAR 52.227-14(g)(2)(6/87) and FAR

52.227-19(6/87), or DFAR252.227-7015(b)(6/95)andDFAR227.7202-3(a). DOCUMENTATIONISPROVIDED“ASIS”ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONSANDWARRANTIES,

INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,FITNESSFORAPARTICULARPURPOSEORNON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TOTHEEXTENTTHAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLYINVALID.

Copyright 2000 Sun Microsystems,Inc.,901SanAntonioRoad,PaloAlto,Californie94303-4900U.S.A.Tous droits réservés. Ce produitoudocumentestprotégéparun copyright etdistribuéavecdeslicencesquienrestreignentl’utilisation,lacopie,ladistribution,etla

décompilation. Aucune partie de ce produitou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a. Le logiciel détenu par des tiers, et qui comprendla technologie relativeaux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Des parties de ce produitpourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems,le logo Sun, AnswerBook2, docs.sun.com, Java, Sun Enterprise, Sun StorEdge A5000, Ultra, Starﬁre, et Solaris sont des marquesde fabrique ou des marques déposées, ou marques de service, de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marquesSPARCsont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux EtatsUnis et dans d’autres pays. Les produits portant les marques SPARCsont basés sur une architecturedéveloppée par Sun Microsystems, Inc.

L’interfaced’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaîtles efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive de Xeroxsur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

CETTE PUBLICATIONEST FOURNIE "EN L’ETAT"ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, N’EST ACCORDEE, Y COMPRIS DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L’APTITUDEDE LA PUBLICATIONA REPONDRE A UNE UTILISATION PARTICULIERE,OU LE FAIT QU’ELLE NE SOIT PASCONTREFAISANTEDE PRODUIT DE TIERS. CE DENI DE GARANTIE NE S’APPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU.

Please

Recycle

Preface xv

Before You Read This Book xv How This Book Is Organized xv Using UNIX Commands xvi Typographic Conventions xvii Shell Prompts xvii Related Documentation xviii Ordering Sun Documentation xviii Accessing Sun Documentation Online xviii Sun Welcomes Your Comments xix

1. Introduction to Sun Management Center 2.1 Supplement for Starfire Servers 1

Known Limitations 2

Starfire Config Reader and Storage Enclosures 2

▼ To Determine Disk-to-Enclosure Mapping 2

Known Bugs 3

2. Installing Sun Management Center 2.1 Software for Starfire Systems 7

Starfire System Add-On Component Packages 8 Preparing to Install Sun Management Center Software for Starfire Systems 8

iii

Where to Install Sun Management Center Software for Starfire Systems 8 Choosing Your Sun Management Center Server Host 9 Required Sun Management Center Version 10 System Requirements 10 Supported Operating Environments 10 Supported SSP Releases 11 Required SSP Memory Configuration 11 Required Patches 11 Required Network Port Configuration 12 SSP Config Reader Support 13

Sun Management Center Installation Files 13 Considerations When Installing Sun Management Center 2.1 Software on Starfire

Systems 14

▼ To Mount a Remote CD-ROM Drive 14

Sun Management Center Software Licensing 15

Installing the Sun Management Center 2.1 Software 16

Starfire Software Installation Sequence 17 Proceeding With the Installation 17

3. Setting Up Sun Management Center 2.1 Components for Starfire Systems 19

Setting Up Add-On Sun Management Center Components for StarfireServers 19

▼ To Set Up a Starfire Domain Add-On Component 20 ▼ To Set Up a Starfire Platform (SSP) Add-On Component 21

Setting Up the Sun Management Center Server License 27

▼ To Set Up the Server License 28

Restarting the SSP snmpd Process 28

Restarting snmpd During Starfire Platform Package Setup 29 Restarting snmpd After Starfire Platform Package Removal 29

iv Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Risks in Restarting snmpd 29 How to Restart snmpd 29

▼ To Kill snmpd 30

Reconfiguring Starfire Setup Parameters 30

▼ To Run the Setup Script 31

Starting Sun Management Center Software 31

▼ To Start Sun Management Center Software on Starfire Systems 32

Uninstalling the Add-On Starfire Components 33

4. Starfire Topology Objects 35

Starfire Platform Composites 35

▼ To Create a Starfire Composite Object 37 ▼ To Discover a Starfire Composite 37

Updating a Starfire Platform Composite 38

▼ To Update a Starfire Composite Created by Create Topology Object 39 ▼ To Update a Starfire Composite Created by Discovery 39 ▼ To Troubleshoot a Composite Creation Failure 40

Starfire Platform Objects 41

▼ To Create a Starfire Platform Object 42

5. Starfire System Details Windows 43

Starfire Domain Details Window 44

Starfire Domain Configuration Resources 44 Interaction With Starfire Domain Devices 45

Starfire Platform Details Window 46

Determining the Complete Platform Configuration 47 Starfire Platform Configuration Resources 48

Starfire Physical and Logical Views 49 SSP Details Window 51

6. Starfire Agent Modules 53

Module Properties 53 Starfire Domain Config Reader Module 54

Module Refresh Intervals 54

▼ To Refresh Starfire Domain Config Reader Data 54 ▼ To Change the Starfire Domain Config Reader Refresh Interval 55

Starfire Domain Config Reader Properties 55

System 55 Starfire Platform 56 System Boards 57 System Board ASIC POST Status 57 Processor Modules 58 Memory Modules 59 Memory Groups 59 DIMM Table 60 I/O Modules 60 I/O Controllers 61 I/O Adaptors 61 I/O Device Drivers 62 Tape Devices 62 Network Devices 63 Disk Devices 64

Starfire Platform Config Reader Module 64

Module Refresh 64 Starfire Platform Config Reader Properties 65

System 65 System Boards 66 System Board ASIC POST Status 68

vi Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Processor Modules 68 Memory Modules 68 Memory Groups 69 DIMM Table 69 I/O Modules 69 I/O Controllers 70 I/O Adaptors 70 Centerplane Boards 71 Centerplane Support Boards 71 Control Boards 72 Fan Trays 73 Fans 73 48V Power Supplies 74 AC Power Input Modules 74 I/O Cabinet Table 75 SSP Information 75 Starfire Domains 76 Agent Status 77 Discovery Object Information 78

Refresh Model 79 SSP Status Module 80 Discovery Table Module 80 Starfire Config Reader Rules 81

POST Status Rule (e10kpost)81 Processor Status Rule (e10kproc)82 Tape Warnings Rule (e10ktwrn)82 Disk Warnings Rule (e10kdwrn)82 Memory ECC Errors Rule (e10kmerr)83

vii

Starfire Domain Trap Rule (e10kdtrp)84 Temperature Rule (e10ktemp)84 Power Rule (e10kpowr)85 Voltage Rule (e10kvolt)85 Comparison Rule (rCompare)86

Changing Config Reader Rule Limits 86

▼ To Edit Rule Parameters 87

Changing Default Rule Limits 87

Starfire Domain Config Reader Module alarmlimit Variables 88 Starfire Platform Config Reader Module alarmlimit Variables 88

▼ To Change Default Rule Limits 89

Reading Sun Management Center Log Files 91

viii Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Figures

FIGURE 4-1 Starfire Composite and Objects It Contains 36 FIGURE 4-2 Main and Spare Starfire Platform and SSP Icons 41 FIGURE 5-1 Resource Information for a Starfire Domain 45 FIGURE 5-2 Resource Information for a Starfire Platform 48 FIGURE 5-3 Physical Views of a Starfire Domain and a Starfire Platform 50 FIGURE 5-4 Unknown Module With Question Mark Indicator 50

x Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Tables

TABLE P-1 Typographic Conventions xvii TABLE P-2 Shell Prompts xvii TABLE P-3 Related Documentation xviii TABLE 2-1 Add-On Sun Management Center Packages for Starfire Servers 8

TABLE 2-2 Additional Minimum Disk Space Required to Install Add-On Sun Management Center

Components for Starfire Servers 10

TABLE 2-3 Solaris Software Patches for Starfire Domains 11 TABLE 2-4 Default Sun Management Center Port Addresses 12 TABLE 2-5 Starfire Platform Hosts and Their Installed Layers 16 TABLE 3-1 Starfire Components and the Commands Used to Stop Them 31 TABLE 5-1 Sun Management Center Agent Modules 43 TABLE 5-2 Starfire Domain Information 45 TABLE 5-3 Starfire Platform Information 49 TABLE 6-1 Starfire Domain Config Reader System 55 TABLE 6-2 Starfire Domain Config Reader Platform 56 TABLE 6-3 Starfire Domain Config Reader System Boards 57 TABLE 6-4 Starfire Domain Config Reader System Board ASIC POST Status 57 TABLE 6-5 Starfire Domain Config Reader Processor Modules 58 TABLE 6-6 Starfire Domain Config Reader Memory Modules 59 TABLE 6-7 Starfire Domain Config Reader Memory Groups 59

TABLE 6-8 Starfire Domain Config Reader DIMM Table 60 TABLE 6-9 Starfire Domain Config Reader I/O Modules 60 TABLE 6-10 Starfire Domain Config Reader I/O Controllers 61 TABLE 6-11 Starfire Domain Config Reader I/O Adaptors 61 TABLE 6-12 Starfire Domain Config Reader I/O Device Drivers 62 TABLE 6-13 Starfire Domain Config Reader Tape Devices 62 TABLE 6-14 Starfire Domain Config Reader Network Devices 63 TABLE 6-15 Starfire Domain Config Reader Disk Devices 64 TABLE 6-16 Starfire Platform Config Reader System 65 TABLE 6-17 Starfire Platform Config Reader System Boards 66 TABLE 6-18 Starfire Platform Config Reader Processor Modules 68 TABLE 6-19 Starfire Platform Config Reader Memory Modules 69 TABLE 6-20 Starfire Platform Config Reader I/O Modules 70 TABLE 6-21 Starfire Platform Config Reader Centerplane Boards 71 TABLE 6-22 Starfire Platform Config Reader Centerplane Support Boards 71 TABLE 6-23 Starfire Platform Config Reader Control Boards 72 TABLE 6-24 Starfire Platform Config Reader Fan Trays 73 TABLE 6-25 Starfire Platform Config Reader Fans 73 TABLE 6-26 Starfire Platform Config Reader Power Supplies 74 TABLE 6-27 Starfire Platform Config Reader AC Power Input Modules 74 TABLE 6-28 Starfire Platform Config Reader I/O Cabinet Table 75 TABLE 6-29 Starfire Platform Config Reader SSP Information 75 TABLE 6-30 Starfire Platform Config Reader Starfire Domains 76 TABLE 6-31 Starfire Platform Config Reader Starfire Domain Ports 77 TABLE 6-32 Agent Status Table 77 TABLE 6-33 Status Property Values 78 TABLE 6-34 Starfire Platform Config Reader Discovery Object Table 79 TABLE 6-35 Starfire Platform Config Reader Refresh Model 79

xii Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

TABLE 6-36 SSP Status Module 80 TABLE 6-37 Discovery Table 80 TABLE 6-38 POST Status Rule 81 TABLE 6-39 Tape Warnings Rule Limits 82 TABLE 6-40 Disk Warnings Rule Limits 83 TABLE 6-41 Memory ECC Error Rule Limits 83 TABLE 6-42 Temperature Rule Levels (Degrees Celsius) 84 TABLE 6-43 Power Rule Levels 85 TABLE 6-44 Voltage Rule Levels for System Boards 85 TABLE 6-45 Voltage Rule Levels for Control Boards 85 TABLE 6-46 Voltage Rule Levels for Centerplane Support Boards 86 TABLE 6-47 Starfire Domain Config Reader alarmlimit Variables 88 TABLE 6-48 Starfire Platform Config Reader alarmlimit Variables 88 TABLE 6-49 Starfire Platform Config Reader rCompare alarmlimits 89 TABLE 6-50 Commands to Stop and Restart Sun Management Center Agents 90 TABLE 6-51 Sun Management Center Log Files 91

xiii

xiv Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Preface

This Sun Management Center 2.1 Supplement for Starfire Servers document provides instructions on how to install, configure, and use Sun™ Management Center software on the Sun Enterprise™ 10000 (Starfire™) computer. It does not provide detailed information about using Sun Management Center software.

This book is intended for Starfire system administrators who install and use the Sun Management Center software components.

Before You Read This Book

This book must be read in conjunction with the Sun Management Center 2.1 Software User’s Guide, which provides instructions for installing and configuring Sun Management Center software, as well as detailed information about how to use the Sun Management Center system management solution. The Sun Management Center

2.1 Software User’s Guide is available from the Sun Management Center web site at http://www.sun.com/sunmanagementcenter.

How This Book Is Organized

Chapter 1 provides an overview of Sun Management Center software on the Starfire platform.

Chapter 2 shows you how to install Sun Management Center software on Starfire servers. Use this chapter in conjunction with the Sun Management Center 2.1 Software User’s Guide.

Chapter 3 shows you how to set up the add-on Starfire system software components. Use this chapter in conjunction with the Sun Management Center 2.1 Software User’s Guide.

Chapter 4 shows you how to create, modify, and discover Starfire system topology objects.

Chapter 5 helps you understand domain and platform data specific to Starfire systems that is shown in Details windows.

Chapter 6 contains brief descriptions of each property in the Sun Management Center software modules in the Starfire server add-on components. It also provides information about how to change rule limits for the Starfire domain Config Reader and Starfire platform Config Reader.

Using UNIX Commands

This document may not contain information on basic UNIX™ commands and procedures such as shutting down the system, booting the system, and configuring devices.

See one or more of the following for this information:

■ Solaris Handbook for Sun Peripherals

■ AnswerBook2™ online documentation for the Solaris™ software environment

■ Other software documentation that you received with your system

xvi Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Typographic Conventions

TABLEP-1 Typographic Conventions

Typeface or Symbol Meaning Examples

AaBbCc123 The names of commands, files,

and directories; on-screen computer output.

AaBbCc123 What you type, when

contrasted with on-screen computer output.

AaBbCc123 Book titles, new words or

terms, words to be emphasized

Command-line variable; replace with a real name or value

Edit your .login file.

ls -a to list all files.

Use

% You have mail. % su

Password:

Read Chapter 6 in the User’s Guide. These are called class options. You must be superuser to do this.

To delete a file, type

Shell Prompts

TABLEP-2 Shell Prompts

Shell Prompt

C shell machine_name% C shell superuser machine_name# Bourne shell and Korn shell $ Bourne shell and Korn shell superuser #

rm filename

xvii

Ordering Sun Documentation

Fatbrain.com, an Internet professional bookstore, stocks select product documentation from Sun Microsystems, Inc.

For a list of documents and how to order them, visit the Sun Documentation Center on Fatbrain.com at:

http://www1.fatbrain.com/documentation/sun

Accessing Sun Documentation Online

The docs.sun.comSMweb site enables you to access Sun technical documentation on the Web. You can browse the docs.sun.com archive or search for a specific book title or subject at:

xviii Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

http://docs.sun.com

Sun Welcomes Your Comments

We are interested in improving our documentation and welcome your comments and suggestions. You can email your comments to us at:

docfeedback@sun.com

Please include the part number (806-1581-10) of your document in the subject line of your email.

xix

xx Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

CHAPTER

Introduction to Sun Management Center 2.1 Supplement for Starfire Servers

Sun Management Center software is a client-server application that uses Java™ software and Simple Network Management Protocol (SNMP) to effectively monitor the activity of agents running on many of your network’s components.

Sun Management Center software provides generic services to Sun Solaris™ operating environment hosts, including monitoring processes such as Solaris software performance and health, MIB-2, and some remote print monitors. Sun Starfire domain hosts can take advantage of these generic Sun Management Center services, since a Starfire host operates in the same manner as any other Solaris operating environment host.

Hardware configuration information is provided by architecture-specific Sun Management Center agent Config Reader modules. The information provided by these Config Reader modules is displayed in the physical view and logical view of the Sun Management Center Details window. The add-on Starfire components provide this Config Reader support for Starfire domains and platforms.

Chapter 1 of the Sun Management Center 2.1 Software User’s Guide includes definitions, explanations, and diagrams that clarify the Sun Management Center architecture. See this chapter whenever you have questions about how consoles, servers, agents, domains, and modules interact.

In other server architectures supported by Sun Management Center software, all hardware configuration information is accessible from the running Solaris operating environment host. The Starfire platform differs because hardware configuration information resides on both the System Service Processor (SSP) and on each of the individual Starfire platform domains.

Note – Sun Management Center 2.1 software for Starfire servers is not intended to

replace hostview. Its primary purpose is to monitor your system components rather than manage them.

Note – Starfire Dynamic Reconfiguration (DR) is not supported in this Sun

Management Center software release.

Known Limitations

This section refers to limitations that were known at the time of release. Software limitations are frequently fixed by software patches that you can download and install.

Refer to the documentation page of the Sun Management Center web site located at http://www.sun.com/sunmanagementcenter for links to information about software patches that are available, and for other current information.

Refer to the SunSolve web site located at http://sunsolve.sun.com to download patches that solve software limitations or fix known bugs.

Starfire Config Reader and Storage Enclosures

The Starfire domain Config Reader (Config-Reader4u1D) module does not support any storage enclosure devices. If the storage enclosure disks are recognized as discrete devices, such as sd or ssd disks, these disks will appear in the Starfire domain Config Reader Disk Devices table.

Storage enclosures that present pseudo-disk devices to the system will not be represented in the Config Reader module, and disks they contain will not appear in the Disk Devices table.

Disks within Sun StorEdge A5x00 storage enclosures will appear as ssd devices in the Disk Devices table.

▼ To Determine Disk-to-Enclosure Mapping

1. Display the Starfire domain Host Details window

2 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

2. Use the browser to display the Config Reader Disk Devices table

3. Find the entry that corresponds to the disk you want to map to an enclosure.

4. Look for the disk name, which resembles cntndn, where n is an integer.

5. Type the luxadm(1M) command in a shell window to determine the enclosure of which that disk is a part, specifying the disk name and slice specifier. For example:

% luxadm display /dev/rdsk/c3t0d0s0 DEVICE PROPERTIES for disk: 2000002037078d52 Status(Port B): O.K. Vendor: SEAGATE Product ID: ST19171FCSUN9.0G WWN(Node): 200002037078d52 WWN(Port_B): 220002037078d52 Revision: 1378 Serial Num: 9735J32664 Unformatted Capacity: 8637.338 MByte Location: In the enclosure named: XF3-B12 Path(s): /dev/rdsk/c3t0d0s0 /devices/sbus@79,0/SUNW,socal@1,0/sf@0,0/ssd@w220002037078d52,0:a,raw

Known Bugs

This section describes software bugs that were known at the time of release. Software bugs are frequently fixed by software patches that you can download and install. For example, workarounds shown for bugs in this section may no longer be necessary if a patch is available.

Refer to the SunSolve web site located at http://sunsolve.sun.com to download software patches.

The following bugs can affect the operation of Sun Management Center software on Starfire systems:

============================================================= Bug Id 4264022 Bug/Rfe: Bug Public Summary: Starfire domains using the Solaris 2.5.1 operating environment and

the Sun Management Center Starfire domain Config Reader module may encounter hung Dynamic Reconfiguration (DR) operations. This hung DR operation is due to a deadlock situation in the DR subsystem.

Workaround: Refer to the documentation page of the Sun Management Center web site located at http://www.sun.com/sunmanagementcenter for links to information about software patches. If no patch for this bug is available, do not perform Dynamic Reconfiguration (DR) operations while the Sun Management Center Starfire domain Config Reader module is running on your Starfire domain. This Sun Management Center module may be disabled and then re-enabled as follows:

Prior to starting your DR operation, use the Sun Manager Center console to display a Host Details window for your Starfire domain. Using the browser, select the Config Reader (Starfire Domain) module and then select Module -> Disable Module. This will disable the Config Reader module while your DR operation takes place.

After the DR operation is complete, enable the module by selecting the Config Reader (Starfire Domain) module and then Module -> Enable Module. After it is reenabled, the Config Reader module detects the current hardware configuration.

============================================================= Bug Id 4265862 Bug/Rfe: Bug Public Summary: Starfire domains using the Solaris 2.6 operating environment and

the Sun Management Center Starfire domain Config Reader module may encounter system hangs while doing Dynamic Reconfiguration (DR) operations. These system hangs are actually hung panics related to device opens occurring during DR detach operations.

4 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Prior to starting your DR operation, use the Sun Manager Center console to display a Host Details window for your Starfire domain. Using the browser, select the Config Reader (Starfire Domain) module and then Module -> Disable Module. This will disable the Config Reader module while your DR operation takes place.

After the DR operation is complete, enable the module by selecting the Config Reader (Starfire Domain) module and then select Module -> Enable Module. After it is re-enabled, the Config Reader module detects the current hardware configuration.

============================================================= Bug Id 4252532 Bug/Rfe: Bug Public Summary: In Starfire systems running SSP software version 3.1.1, CBE

sometimes truncates the values of temperature readings or reports no reading at all for a given value. This results in false temperature reports that can lead to 911 temperature traps.

Workaround: Install SSP software patch 108230-01. ============================================================= Bug Id 4261146 Bug/Rfe: Bug Public Summary: System-board voltages reported in the SSP MIB are inconsistent.

When a system-board is powered on, the voltages reported in the SSP MIB sometimes are sometimes too low. When a system-board is powered-off, the voltages are sometimes not updated.

Workaround: None available at this time.

6 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

CHAPTER

Installing Sun Management Center

2.1 Software for Starfire Systems

This chapter, used in conjunction with the Sun Management Center 2.1 Software User’s Guide, shows you how to install the Sun Management Center software on Starfire servers.

The Sun Management Center software is divided into core packages that provide the Sun Management Center infrastructure and basic support, and add-on components that add support for particular hardware platforms or other options.

Starfire support requires core packages and add-on Starfire packages that are installed during the Sun Management Center software installation described in this chapter. Once this software is installed, set up the Sun Management Center software using the instructions in Chapter 3.

Starfire System Add-On Component Packages

The add-on Starfire component includes the following packages for Sun Management Center software support of Starfire platforms (

TABLE2-1 Add-On Sun Management Center Packages for Starfire Servers

Package Description

SUNWessfd

SUNWessfp

SUNWessfs

Sun Management Center software Domain Agent Support for Starfire servers. This package provides libraries and configuration files needed to monitor the hardware configuration of Starfire domains.

Sun Management Center software SSP Agent Support for Starfire servers. This package provides libraries and configuration files needed to monitor the hardware configuration of the entire Starfire platform.

Sun Enterprise Starfire Server Support for Starfire systems. This package provides files needed by the Sun Management Center server to display the physical view of the Starfire platform.

TABLE 2-1):

Preparing to Install Sun Management Center Software for Starfire Systems

Your Starfire system must meet certain requirements before you install Sun Management Center 2.1 software for Starfire servers. These requirements are explained below.

Where to Install Sun Management Center Software for Starfire Systems

The Sun Management Center software must be installed on a number of hosts for Starfire support to be available. Sun Management Center components must be installed on:

■ Sun Management Center server host

■ SSP for the Starfire platform

8 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

■ Spare SSP (if configured)

■ Each Starfire domain you would like to monitor

See “Starfire Platform Objects” on page 41 for more information about Main and Spare SSPs.

In addition, the Sun Management Center console software must be installed on a host in your network. There are no add-on Starfire components for the console layer.

Sun Management Center online help can be installed on a Sun Management Center help server and viewed by web browsers on the network. There are no add-on Starfire components for the help server, but you do need to decide where to install the online Sun Management Center help server. Refer to “Sun Management Center Online Help” in the Sun Management Center 2.1 Software User’s Guide for more information.

Caution – Only the Sun Management Center agent layer should be installed on the

SSP. Do not install the Sun Management Center console or server layer on a Starfire SSP. SSP resources are dedicated to managing the Starfire platform; running additional functions on the SSP can result in the SSP software not running correctly.

Note – (Optional) Install Sun Management Center software on each Starfire domain

if you want full monitoring capabilities.

Choosing Your Sun Management Center Server Host

Before installing the Sun Management Center software, determine which host will be the Sun Management Center server host. The host chosen to be the Sun Management Center server for your network should be a system with high availability; when the Sun Management Center server is down, you will be unable to use Sun Management Center software to manage your systems. Refer to the Sun Management Center 2.1 Configuration and Deployment Guide for more information about server host requirements.

You can place any of the Sun Management Center layers (console, server, agent) on a Starfire domain. But if you want to be able to manage a Starfire platform when all domains are down, you should not place the Sun Management Center server layer on one of the Starfire platform domains.

For more timely platform monitoring of the Starfire domain hardware configuration, configure the SSP and the Starfire domain Sun Management Center agents to use the same Sun Management Center server.

Required Sun Management Center Version

Sun Management Center 2.1 must be running on all of the following Starfire components:

■ Starfire domains

■ Starfire SSP

■ Sun Management Center server host

■ All consoles

System Requirements

The Sun Management Center 2.1 Configuration and Deployment Guide provides information about general Sun Management Center prerequisites, including minimum disk space requirements. space required for the add-on Sun Management Center components for Starfire servers.

TABLE 2-2 on page 10 shows the additional disk

TABLE2-2 Additional Minimum Disk Space Required to Install Add-On Sun

Layer

Starfire Domain Agent 0.5 Starfire Platform (SSP) Agent 0.7 Sun Management Center Server Starfire

Support

Management Center Components for Starfire Servers

Minimum Disk Space Required (Mbytes) for Add-On Starfire Components

0.4

Note – Sun Management Center support for Starfire servers is only available

beginning with the Sun Management Center 2.1 release. The Sun Management Center console, server, and agent components for the Starfire SSP and Starfire domains must be running Sun Management Center 2.1 software or subsequent compatible versions.

Supported Operating Environments

For supported Sun Management Center 2.1 operating environments, refer to the Sun Management Center Software Release Notes.

10 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Supported SSP Releases

The Sun Management Center software add-on component for Starfire servers requires SSP version 3.1.1 or later software. Any of the supported operating environments may be used on the SSP.

Required SSP Memory Configuration

The SSP must have a minimum of 128 Mbytes of memory.

Required Patches

Starfire domains running the Solaris 2.5.1 or Solaris 2.6 operating environment require Solaris software patches to run correctly with Sun Management Center software. These patches enable the Solaris operating environment to detect DR hardware configuration changes. that support Sun Management Center software.

TABLE2-3 Solaris Software Patches for Starfire Domains

Solaris Operating Environment Version Solaris Software Patch

2.5.1 Patch 105174-08

2.6 Patch 106284-04

TABLE 2-3 shows the first versions of these patches

Note – If these patches are not installed, Sun Management Center software will not

detect DR hardware configuration changes.

Note – Refer to any README files associated with these patches for information

about any dependencies or prerequisites the patches may have.

Required Network Port Configuration

Sun Management Center software requires the use of network ports to communicate with various components of the system. The default port addresses for these components are shown in

TABLE2-4 Default Sun Management Center Port Addresses

Layer Component Default Port Number

Agent Agent 161 Server Trap handler 162 Server Event manager 163 Server Topology manager 164 Server Configuration manager 165 Server Server 2099 Agent Platform agent 166

In some cases, this default port configuration conflicts with software already running on your system. The Starfire SSP always has a port 161 conflict, since the SSP snmpd agent or Solaris software snmpdx agent uses this port. Some Starfire domains may also have port 161 conflicts due to the presence of legacy SMNP agents. During the Sun Management Center software setup, specify a different network port to avoid this conflict. Refer to Appendix B of the Sun Management Center 2.1 Software User ’s Guide for information about how to determine what ports are in use.

TABLE 2-4:

To create and access topology objects, Sun Management Center software uses port 161 by default. If you configure an agent to use an alternate port, you must specify that port when the topology object is created or discovered. To simplify your Sun Management Center network configuration and management and enable more efficient discovery of Sun Management Center agents, select an alternate port number and use that number for all agent installations that cannot use the default port configuration.

The Starfire SSP has two Sun Management Center agents: the agent and the platform agent. The agent provides information about the SSP and the platform agent provides information about the Starfire platform. Usually there are no port conflicts with the default port configuration for the platform agent. When a platform topology object is created or discovered, the correct default port is provided and does not need to be specified.

12 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

SSP Config Reader Support

You can add Config Reader support for some SSP Sun Ultra™ workstation architectures by installing and setting up the workstation add-on component of the Sun Management Center software. Refer to the Sun Management Center 2.1 Supplement for Workstations for a complete list of supported workstations.

Note – Sun SPARCstation™ workstation architectures are not supported by the

workstation add-on component. Sun Management Center software can be installed on a SPARCstation workstation, but no SSP hardware configuration information will be available.

If you wish, you can install this add-on component during the installation and setup of the Sun Management Center 2.1 software. If you install the core software from a CD-ROM, the workstation add-on packages will be installed during the core installation. If you install from the Web, you must download and install the required workstation images.

Sun Management Center Installation Files

The Sun Management Center 2.1 CD-ROM contains all files necessary to install Sun Management Center software on Starfire servers. This software is also available from the Sun Management Center web site at http://www.sun.com/sunmanagementcenter. If you obtain this software from the web site, be sure that you download:

■ Sun Management Center Core packages

■ Add-on Starfire component

■ (optional) Desktop add-on component for SSP

When downloading Sun Management Center software from the Web, you must choose which Solaris operating environment releases you need to support. Each operating environment release has a separate set of downloadable images. If more than one release is running anywhere in your Starfire configuration, you need to download multiple versions for each software component.

For example, you will need to download three Solaris operating environment versions of the Sun Management Center 2.1 release and the Sun Management Center packages for Starfire servers to perform a Sun Management Center software installation if your configuration includes:

■ Sun Management Center server host running the Solaris 7 operating environment

■ Starfire domain running the Solaris 2.6 operating environment

■ SSP running the Solaris 2.5.1 operating environment

Once you have downloaded all the required components, extract these files into a single directory. This will build an installation directory containing all the Sun Management Center software components you need, and will allow you to install with one command the Sun Management Center core software, the add-on Starfire component and, optionally, the add-on Desktop component.

For detailed instructions on downloading and extracting these files, refer to the README file accompanying each downloadable installation package available on the Sun Management Center web site at http://www.sun.com/sunmanagementcenter.

Considerations When Installing Sun Management Center 2.1 Software on Starfire Systems

Detailed directions for installing and setting up Sun Management Center 2.1 software are provided in the Sun Management Center 2.1 Software User’s Guide. For Starfire configurations, you should be aware of these additional considerations:

■ If you are installing the Sun Management Center software from a CD-ROM onto a

Starfire domain, you must mount a remote CD-ROM drive since the Starfire host does not have a local CD-ROM drive. See “To Mount a Remote CD-ROM Drive” on page 14 for instructions.

■ Sun Management Center software management of Solaris software hosts for a

single Starfire platform does not require a license. See “Sun Management Center Software Licensing” on page 15 for more information.

▼ To Mount a Remote CD-ROM Drive

If you are installing from a CD-ROM, you will first need to mount a remote CDROM drive from the SSP since the Starfire domain does not have a local CD-ROM drive and the SSP does.

1. Log in to the SSP as superuser.

2. Insert the Sun Management Center 2.1 CD into the CD-ROM drive on the SSP.

14 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

3. Type the share(1M) command on the SSP to make the CD-ROM usable across the network.

ssp# share -o ro,anon=0 -F nfs /cdrom/sun_management_center_2_1

4. Log in to a Starfire domain as superuser.

5. Make a local directory, if it does not already exist, on which to mount the CDROM:

# mkdir /cdrom

6. Mount the SSP /cdrom directory on /cdrom:

# mount ssp_hostname:/cdrom/sun_management_center_2_1 /cdrom

7. Change to the Sun Management Center software installation directory:

# cd /cdrom/sun_management_center_2_1

Sun Management Center Software Licensing

Sun Management Center software is freely available to manage or monitor an individual Starfire platform. The Starfire platform includes the Starfire Dynamic System Domains, the SSP (System Service Processor), and the spare SSP, if one is configured.

During the setup of the core Sun Management Center server layer, the following message will be displayed:

Sun Management Center requires a license in order to run in a multiple host/agent configuration. If not licensed, Sun Management Center will only allow you to have a default domain with just your local host.

Do you have a license token you would like to install now? [y|n|q]

If you are only monitoring the hosts for a single Starfire platform, answer n (for No).

A Sun Management Center software right-to-use license is required if you want to create more than one Sun Management Center domain or to monitor more than one Starfire platform. If you do not purchase a license, you will be operating in violation of your license agreement. For information on purchasing a license, visit the Sun Management Center web site at http://www.sun.com/sunmanagementcenter.

See “Setting Up the Sun Management Center Server License” on page 27 for instructions on how to set up the license server.

Installing the Sun Management Center

2.1 Software

For Starfire support, install the following Sun Management Center software on these Starfire platform hosts:

TABLE2-5 Starfire Platform Hosts and Their Installed Layers

Host Layer Software Installed

Sun Management Center Server Host

Starfire Domain Agent Core Sun Management Center Agent layer and add-

Main SSP Agent Core Sun Management Center Agent layer and

Spare SSP (if configured) Agent Core Sun Management Center Agent layer and

Server Core Sun Management Center Server layer and Sun

Management Center server add-on component for Starfire servers

on Starfire Domain component

Starfire Platform add-on component. No other Sun Management Center layers should be installed here.

Note – In addition to the Sun Management Center agent layer, any of the Sun

Management Center layers can be installed on Starfire domain hosts. Refer to “Choosing Your Sun Management Center Server Host” on page 9 for more information.

You must also install the Sun Management Center console and online help somewhere on your network, as described in the Sun Management Center 2.1 Software User’s Guide.

16 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Starfire Software Installation Sequence

For best results, install the Sun Management Center software on the hosts in the following order:

1. Sun Management Center server host

2. Starfire Domains

3. Main SSP

4. Spare SSP (if configured)

5. Sun Management Center console host

6. Sun Management Center Online Help (if not installed on the Sun Management

Center console host)

Proceeding With the Installation

You are now ready to install the core Sun Management Center software. Follow the instructions in the Sun Management Center 2.1 Software User’s Guide carefully. After selecting the Sun Management Center components to install, the required Sun Management Center software and the add-on Starfire components will be installed on your host.

Remember to:

■ Install the Sun Management Center software on the hosts in the sequence shown

above.

■ For each host, install the Sun Management Center layers as described in TABLE 2-5.

Once the Starfire add-on components are installed, a setup confirmation message is displayed:

Would you like to proceed with setup now? [y|n|q]

To set up the Sun Management Center software, see “Setting Up Sun Management Center 2.1 Components for Starfire Systems” on page 19.

18 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

CHAPTER

Setting Up Sun Management Center

2.1 Components for Starfire Systems

Now that you have installed the Sun Management Center software, as described in the previous chapter, you are ready to set up the add-on components.

Setting Up Add-On Sun Management Center Components for Starfire Servers

For information about configuring the core components, refer to the Sun Management Center 2.1 Software User ’s Guide.

For information about where these components are located, refer to page 16.

TABLE 2-5 on

The setup script detects which core Sun Management Center components are currently installed and asks you whether you wish to set up these core components. If you already have set up the core components, answer n (for No) so that you do not have to go through the core setup procedure again. For example:

You have the following Sun Management Center components installed

Sun Management Center Server Sun Management Center Agent Sun Management Center Console

This script will perform the setup for each of these components

Would you like to setup the Core Sun Management Center Server Component now? [y|n|q] n Would you like to setup the Core Sun Management Center Agent Component now? [y|n|q] n Would you like to setup the Core Sun Management Center Console Component now? [y|n|q] n

Core Sun Management Center setup complete.

After you are asked to set up the core components, the setup script prompts you for any other installed add-on components needing setup. Instructions for setting up each of the Starfire components are provided in the next sections.

Note – Be sure the core components are set up prior to setting up the Starfire

components.

▼ To Set Up a Starfire Domain Add-On Component

You are prompted to confirm that you wish to set up the Starfire domain add-on component:

----------------------------------------------------Starting Sun Management Center Starfire Domain Setup

----------------------------------------------------Would you like to setup this Sun Management Center package? [y|n|q]

20 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

1. Type y (for Yes).

The setup script queries the platform SSP SNMP agent in an effort to get the platform name for this Starfire domain and supply it without your intervention. For example:

Query the SSP for the Starfire platform name... The Starfire platform name is allsdsim3.

2. If the query is unable to determine the SSP name, type the SSP name when prompted.

3. If the query is unable to determine the platform name from the SSP, type the platform name when prompted.

A reminder that the Sun Management Center agent port number for this domain must be correctly configured during the Starfire platform setup is displayed:

Added module Config-Reader4u1D to /var/opt/SUNWsymon/cfg/base-modules-d.dat.

Remember, when setting up the Sun Management Center Starfire SSP platform package (SUNWessfp) to add port 1161 to the list of Starfire domain ports.

▼ To Set Up a Starfire Platform (SSP) Add-On

Component

You are prompted to confirm that you wish to set up the Starfire platform (SSP) add-on component:

----------------------------------------------------Starting Sun Management Center Starfire Platform Setup

-----------------------------------------------------

Would you like to setup this Sun Management Center package? [y|n|q]

1. Type y (for Yes).

Forwarding SSP snmpd traps to the Sun Management Center software requires stopping and then restarting the SNMP daemon. The setup script identifies this process for you and enables you to restart it automatically by answering y (for Yes) when prompted. For example:

Added SSP Sun Management Center trap forwarding. Sun Management Center trap server sdsim1-b7, trap server port 162.

------------------------ IMPORTANT ------------------------In order to complete SSP trap forwarding setup, the SSP snmpd process must be restarted. The interruption to SSP services due to restarting snmpd is brief. However, restarting the SSP snmpd process may delay or cause to fail SSP operations which require snmpd. Commands affected include hpost(1m) and bringup(1m).

No bringup or hpost processes are currently running.

If you choose to not restart snmpd now, you must restart snmpd before you start the Sun Management Center agents.

Would you like to restart the SSP snmpd process now? [y|n|q]

22 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

If bringup or hpost processes are running, the message displays the process numbers. For example:

Added SSP Sun Management Center trap forwarding, Sun Management Center trap server sdsim1-b7, trap server port 162.

bringup or hpost processes are currently running: UID PID PPID C STIME TTY TIME CMD ssp 10511 21978 0 15:13:35 pts/26 0:00 /usr/bin/sh /opt/SUNWssp/bin/bringup -A off ssp 10619 10511 6 15:15:00 pts/26 0:00 hpost

If you choose to not restart snmpd now, you must restart snmpd before you start the Sun Management Center agents.

Would you like to restart the SSP snmpd process now? [y|n|q]

If you refuse to restart the SSP snmpd process when prompted, you must manually restart the SSP snmpd process before you start the Sun Management Center agents on this host. See “Restarting the SSP snmpd Process” on page 28 for more information.

2. Type y (for Yes) when prompted to restart the SSP snmpd process.

The setup script will stop the snmpd process, wait for it to be restarted, and display the new snmpd process number. The setup script usually determines the platform name automatically from SSP configuration files. For example:

Would you like to restart the SSP snmpd process now? [y|n|q] y Waiting for SSP snmpd process to restart... SSP snmpd restarted, process id 10644.

SSP snmpd SNMP port 5050

platform name is: allxf2

3. If the setup script is unable to determine the platform name from the SSP, type the platform name when prompted.

Note – Be sure to enter the correct platform name. This name is used during Sun

Management Center operations to access SSP information and identify the Starfire platform.

The setup script automatically determines which SNMP port is configured to be used by the Sun Management Center agent and displays it. For example:

Checking Sun Management Center Agent configuration. Sun Management Center Agent port: 161

4. If the Sun Management Center agent is configured to use port 161, type an alternate network port when prompted to do so.

See “Required Network Port Configuration” on page 12 for more information. The setup script automatically determines if the platform agent port was properly

configured by the core Sun Management Center setup file, and ensures that the configured port is not currently in use. For example:

Checking Sun Management Center Platform agent configuration. Verifying port number: 166 Sun Management Center Platform Agent port: 166

5. If the platform agent port is in use, select a different network port when prompted to do so.

Warning, port 166 is currently in use. You need to either pick a different port, or insure that port 166 is available when you next start Sun Management Center. Do you still wish to use port 166? [y|n|q] n Enter new Sun Management Center Agent port: 1166

See “Required Network Port Configuration” on page 12 for more information. If you modify the SNMP port for either the Sun Management Center agent or

platform agent, the setup script prompts you to regenerate the Sun Management Center security keys. The Sun Management Center security keys must be regenerated before you start the Sun Management Center agents on this host if the SNMP port numbers are modified.

24 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

6. Type y (for Yes) to regenerate the security keys when prompted to do so:

The Sun Management Center agent and platform agent security keys must be regenerated because the agent port numbers used have been changed.

Do you want to regenerate the security keys now? [y|n|q] y

Set up the security keys as described in the “Security Seeds” section of Chapter 3 in the Sun Management Center 2.1 Software User’s Guide . If you refuse to regenerate the Sun Management Center security keys when prompted, you are warned that you must manually regenerate them before starting Sun Management Center software.

The setup script asks you if your Starfire platform is configured with a spare SSP:

Is this Starfire platform configured with a spare SSP? [y|n|q]

7. Type y (for Yes) if this platform has a spare SSP. Type n (for No) if this platform does not have a spare SSP.

Note – The Sun Management Center agent and the add-on Starfire components

should be installed on both the main and spare SSP when a spare SSP is configured. The same installation and setup instructions apply to both the main and spare SSP. Answer y (for Yes) to this question when configuring both the main and the spare SSP. In addition, both the main and spare SSP must use the same network port configuration.

The spare SSP configuration information is used to create Starfire topology objects. See “Starfire Topology Objects” on page 35 for more information.

8. (Optional) If you have a spare SSP, type the name of the alternate SSP when prompted. When setting up Sun Management Center software on the main SSP, the alternate SSP is the spare SSP. When setting up the spare SSP, the alternate SSP is the main SSP.

The script describes which ports to specify when configuring the Sun Management Center agent and platform agent on the alternate SSP:

Please enter the alternate SSP hostname (not xf2-ssp) for this platform. Alternate SSP hostname: xf2-ssp2 Remember on SSP xf2-ssp2 the Agent must be configured to use port

1161. Remember on SSP xf2-ssp2 the Platform Agent must be configured to use port 166.

The Starfire platform obtains information from each of its Starfire domains by checking the SNMP ports associated with them. This information is used to create Starfire topology objects and is required to access hardware configuration information gathered by the Starfire domain add-on component. See “Starfire Topology Objects” on page 35 for more information.

The setup script displays the current default ports and prompts you to change the list of ports:

This Platform Config Reader will optionally acquire data from the Sun Management Center Config-Reader modules loaded on Starfire domains.

The default ports to be checked for Starfire Domains are: 161

Do you want to change the ports that will be checked? [y|n|q]

By default, Sun Management Center agents are installed on port 161. But due to port 161 conflicts, you may have configured the Starfire domain agents to use a different port or ports.

26 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

9. If all Starfire domain agents use the default port 161, type n for No. If you configured one or more other ports, type y (for Yes) and type the Starfire domain agent network port (or ports, separated by spaces) when prompted. For example:

Do you want to change the ports that will be checked? [y|n|q] y Use space to separate multiple port numbers, just press <Enter> to check no ports. Enter port numbers: 161 1161

Be sure that this list contains all the ports on which Starfire domain Sun Management Center agents are configured.

The setup script displays the added modules and completes the setup. For example:

Updating alarm limits with SSP information. Updating temperature alarm limits. Updating voltage alarm limits.

Added module Config-Reader4u1P to /var/opt/SUNWsymon/cfg/platform-modules-d.dat. Added module sspStatus to /var/opt/SUNWsymon/cfg/base-modules-d.dat. Added module dtable to /var/opt/SUNWsymon/cfg/base-modules-d.dat. Updated symon.conf information. Updated Discovery Table information.

Setting Up the Sun Management Center Server License

Once you have installed the Starfire Server package on the Sun Management Center server, you must manually set up the server license. You must also manually set up the server license any time you reinstall core Sun Management Center components or add-on Starfire components.

Note – You can safely run the script that sets up the server license more than once.

▼ To Set Up the Server License

1. Log in as superuser on the Sun Management Center server.

2. Type this command:

# /opt/SUNWsymon/sbin/es-run /opt/SUNWsymon/sbin/e10ksrv

Note – If you installed the Sun Management Center software in a different directory

than /opt, use that directory instead.

This message is displayed:

--------------------------------------------------------------Starting Sun Management Center Starfire Server Setup

--------------------------------------------------------------Would you like to setup this Sun Management Center package? [y|n|q]

3. Type y (for Yes).

The Starfire license for the Sun Management Center software is installed automatically:

Installed Sun Management Center Starfire license.

Note – The Starfire Sun Management Center license is removed automatically from

the Sun Management Center license file when the Starfire Server package is removed.

Restarting the SSP snmpd Process

To make changes to SSP snmpd trap forwarding, the SSP snmpd process must be restarted after the SSP snmpd configuration file is changed. Changes are required to the SSP snmpd configuration file when the Sun Management Center package setup script for the Starfire Platform is run, and when the Sun Management Center package is removed.

28 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Restarting snmpd During Starfire Platform Package Setup

The Sun Management Center package setup script for the Starfire Platform prompts you to automatically restart the SSP snmpd process. If you do not want the script to restart the SSP snmpd process, you must manually restart the SSP snmpd process before starting the Sun Management Center agents.

Restarting snmpd After Starfire Platform Package Removal

When the Sun Management Center Starfire Platform package is removed, the trap forwarding entry is removed from the SSP snmpd configuration file. However, you must restart the SSP snmpd process before the changes in the configuration file are effective. The package remove script does not restart the SSP snmpd process. SSP snmpd traps will continue to be forwarded until the SSP snmpd process is restarted.

Risks in Restarting snmpd

The SSP snmpd process is essential to SSP functionality, and SSP software will automatically restart the SSP snmpd process if it detects that the process has died on a main SSP.

Restarting the SSP snmpd process causes a slight delay in SSP services. Do not kill the SSP snmpd process while either hpost(1M) or bringup(1M) are running, as it can cause those commands to fail.

Note – Once the SSP snmpd process has been killed and restarted, subsequent

hpost(1M) and bringup(1M) commands are not affected.

How to Restart snmpd

There are two ways to restart snmpd:

■ Reboot the SSP

■ Kill the SSP snmpd process

In both cases, the SSP software automatically restarts the SSP snmpd process.

▼ To Kill snmpd

1. Log in to the main SSP as superuser.

2. Find the snmpd process number by typing:

# ps -ef | grep snmpd

A message similar to this is displayed:

root process_id 1 0 Jun 17 11:31 snmpd

3. If snmpd is running, kill the snmpd process by typing:

# kill process_id

where process_id is the process identification (pid) number shown in the results of Step 2.

Caution – Make sure you type the process_id number correctly.

Reconfiguring Starfire Setup Parameters

You can reconfigure the Starfire setup parameters at any time by running the setup script again. You must reconfigure the appropriate Starfire setup parameters if certain changes occur:

■ Reconfigure the Starfire domain and platform (SSP) component if the Starfire

platform name is changed.

■ Reconfigure the Starfire platform (SSP) component if the Sun Management Center

agent port configuration for the Starfire domains changes.

■ Reconfigure the Starfire platform (SSP) component if a spare SSP is added or

removed from the platform configuration.

■ Reconfigure the Starfire platform (SSP) component if the Sun Management Center

server host or trap agent port configuration changes.

■ Reconfigure the Starfire platform (SSP) component if the SSP software is

reinstalled or the default voltage or temperature alarm limits contained in the SSP’s ssp_resource file are modified.

30 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

For information about where these components are located, refer to TABLE 2-5 on page 16.

▼ To Run the Setup Script

1. Log in as superuser and stop the components you will be reconfiguring.

The command you use to stop the component depends on which component you are reconfiguring. to stop them.

TABLE3-1 Starfire Components and the Commands Used to Stop Them

Component Command Used to Stop Operation of the Component

Starfire domain agent /opt/SUNWsymon/sbin/es-stop -a Starfire SSP agents /opt/SUNWsymon/sbin/es-stop -al Sun Enterprise SyMON server /opt/SUNWsymon/sbin/es-stop -s

TABLE 3-1 shows a list of Starfire components and the commands used

2. Type the appropriate command from

3. Run the setup script to set up the component layers:

# /opt/SUNWsymon/sbin/es-setup

TABLE 3-1.

Note – If you installed the Sun Management Center software in a different directory

than /opt, use that directory instead.

4. Follow the instructions in “Setting Up Add-On Sun Management Center Components for Starfire Servers” on page 19.

5. Restart the components that you stopped.

Starting Sun Management Center Software

The es-start command requires different command arguments, depending on which component you are starting.

▼ To Start Sun Management Center Software on

Starfire Systems

1. On the SSP, start the Sun Management Center agents:

# /opt/SUNWsymon/sbin/es-start -al

This starts both the regular and platform agents. The platform agent provides all the Starfire platform information to Sun Management Center software.

Note – If you installed the Sun Management Center software in a different directory

than /opt, use that directory instead.

2. For the Starfire domain with only the Sun Management Center agent layer installed, start the Sun Management Center agent:

# /opt/SUNWsymon/sbin/es-start -a

Note – If you installed the Sun Management Center software in a different directory

than /opt, use that directory instead.

3. For the Sun Management Center server host that has all layers installed, start all the Sun Management Center components:

# /opt/SUNWsymon/sbin/es-start -A

Note – If you installed the Sun Management Center software in a different directory

than /opt, use that directory instead.

Note – After the Sun Management Center components are started, it may take a few

minutes to initialize. If you encounter problems using Sun Management Center software immediately after a component is started, wait a few minutes and try again.

Note – Upon rebooting, all Sun Management Center agents will start automatically.

32 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

4. To start the console:

# /opt/SUNWsymon/sbin/es-start -c

Note – If you installed the Sun Management Center software in a different directory

than /opt, use that directory instead.

Refer to “Starting the Sun Management Center Software” in the Sun Management Center 2.1 Software User ’s Guide for more detailed information about startup procedures.

Uninstalling the Add-On Starfire Components

The add-on Starfire components are uninstalled with the rest of the Sun Management Center software as described in Chapter 2 of the Sun Management Center 2.1 Software User ’s Guide. If you are permanently removing Sun Management Center software from your SSP, rather than upgrading to a new release, be sure to restart the SSP snmpd process as described in “Restarting the SSP snmpd Process” on page 28.

34 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

CHAPTER

Starfire Topology Objects

This chapter shows you how to create, modify, and discover Starfire topology objects. Refer to Chapter 5 of the Sun Management Center 2.1 Software User’s Guide for general information about creating and monitoring Sun Management Center objects.

Starfire Platform Composites

A Starfire composite is a Sun Management Center group object that contains all the hosts associated with a Starfire platform. This composite includes the SSP, spare SSP if one is configured, and the Starfire domains. Additionally, a Sun Management Center object represents the Starfire platform information gathered from the SSP. The Starfire composite groups all these objects together to enable easier management of all components of the Starfire platform (

FIGURE 4-1).

Platform icon

SSP icon

Domain icon

(Sun Management

Center agent host)

Center agent)

FIGURE 4-1 Starfire Composite and Objects It Contains

Note – Icons for hosts monitored by Sun Management Center agents include a

machine model badge, such as the 10000 badge shown for the lower domain icon in the illustration. The icon for a host that is not monitored by a Sun Management Center agent host, such as the first domain icon in the illustration, displays no badge.

The SSP provides information to the Sun Management Center software about which objects to include in the Starfire platform composite. When creating a Starfire composite, you must supply the SSP hostname and agent port number.

SSP and Starfire domain hosts in a Starfire platform composite can be included in multiple groupings in the Sun Management Center topology so that you can view the hosts by their Starfire platform association as well as by their network grouping. When Starfire hosts are found by a discovery request, they are placed in the topology according to their network groupings. In addition, when the main SSP is found by a discovery request, the Starfire domain and SSP hosts are also placed into the Starfire platform composite grouping.

36 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

To monitor Starfire domains and platforms, create a Sun Management Center Starfire composite from the Create Topology Object window, or use a Sun Management Center discovery request.

▼ To Create a Starfire Composite Object

1. In the hierarchy view of the main console window, change levels to the level in the Sun Management Center domain topology where you want to create the new composite object.

2. In the main console window, select Create an Object from the Edit menu.

3. Click the Composite tab in the Create Topology Object window.

4. Type a label (usually the Starfire platform name with which the SSP software was configured), the SSP hostname, and the port number on which the SSP Sun Management Center agent is configured.

5. Select OK.

This message is displayed:

Creating composite object... Please Wait.

The amount of time this operation requires depends upon how many Starfire domains are configured and whether those domains are running.

You will see the Starfire folder added to the current location in the Sun Management Center domain topology. If the Starfire composite is not created, follow the steps in “To Troubleshoot a Composite Creation Failure” on page 40.

6. Open this folder to see all the objects associated with the Starfire platform.

▼ To Discover a Starfire Composite

1. Create a Sun Management Center discovery request that includes the Starfire SSP IP address. Be sure to include the Sun Management Center agent port in the list of network ports.

2. Run this discovery request.

The Starfire composite is added to the root level of the Sun Management Center domain topology. In addition, the SSP is added to the Sun Management Center topology network grouping.

3. If the Starfire composite is not created, follow the steps in “To Troubleshoot a Composite Creation Failure” on page 40.

Note – If the SSP was busy at the time the discovery request was made, run the

discovery request again or increase the discovery request SNMP timeout value.

You can use the following Discovery Request filter options to customize your Starfire composite discovery request:

■ The Platform Type filter criteria enable you to include or exclude Starfire domain,

Starfire platform, and Starfire composite object types.

■ Starfire domain hosts and the SSP within the composite can be filtered by the host

names and operating system filter criteria. The host names and operating system filter criteria do not filter Starfire platform objects.

■ If the SSP is excluded by a filter criterion, the Starfire composite objects will still

be examined by the Discovery Manager for inclusion in the Sun Management Center domain.

Updating a Starfire Platform Composite

Once you have created the Starfire platform composite, the contents and type of the composite Sun Management Center topology objects do not change. The composite objects must be updated if:

■ Starfire domains are added to or deleted from the platform configuration.

■ A spare SSP is added to or deleted from the platform configuration.

■ Sun Management Center monitoring for an object no longer shows the correct

monitor type. For example, if the Sun Management Center agent or the Starfire domain is not running at the time the composite was created, an ICMP Ping monitoring type host object is created for the Starfire domain. Once the host and Sun Management Center agent are running again, the Starfire domain host object needs to be updated so that it can be monitored as a Sun Management Center Agent - Host type.

Note – If Starfire domain hosts running the Sun Management Center agent are

monitored as any type other than a Sun Management Center Agent - Host, verify that you have specified the correct Starfire domain ports during SSP platform setup. This configuration can be examined from the Starfire platform Details window in the Starfire Agent Status object of the Config Reader (Starfire Platform) module.

38 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

▼ To Update a Starfire Composite Created by Create

Topology Object

1. If the Starfire platform composite was created using the Create Topology Object window, you must perform all updates to the composite manually.

■ If Starfire composite objects have been added or deleted, delete or create the

objects as described in Chapter 5 of the Sun Management Center 2.1 Software User’s Guide.

■ If the monitoring type has changed, modify the topology object as described in

the “Modifying Objects” section of Chapter 5 in the Sun Management Center 2.1 Software User’s Guide.

2. If the changes are numerous, it may be easier to delete the current Starfire composite object from the topology and recreate it. See “To Create a Starfire Composite Object” on page 37 for instructions.

▼ To Update a Starfire Composite Created by

Discovery

1. If the Starfire platform composite was created by the Discovery Manager, many of the updates can be made by running a discovery request for the main SSP. This discovery request can either be started manually or scheduled for periodic running.

Running the discovery request makes these changes:

■ New Starfire objects such as Starfire domains and a spare SSP are added to the

platform composite.

■ If an object monitoring type has changed to a level of higher monitoring

capability, the monitoring type is updated. Monitoring capability increases from the ICMP Ping monitoring type to the SNMP Ping monitoring type to the Sun Management Center Agent - Host monitoring type.

Running a discovery request does not make certain other changes:

■ Topology objects are not deleted from the platform composite.

■ If any of the topology objects have been modified from the Sun Management

Center console window, the object monitoring type is not updated.

2. If you prefer, you can create an updated platform composite by deleting the Starfire platform composite from the topology and running a discovery request.

▼ To Troubleshoot a Composite Creation Failure

If you are unable to create a Starfire platform composite, check for the following problems:

1. Verify that the correct SSP hostname and Sun Management Center agent port number were specified in the Create Topology Object procedure or discovery request.

Note – The SSP must be the main SSP for the platform, not the spare SSP.

2. Log in to the SSP and verify that the two Sun Management Center agents are running:

ssp# ps -ef | grep esd root 21020 1 2 Mar 10 ? 84:03 esd - init agent -dir /var/opt/ SUNWsymon root 21858 1 3 Mar 10 ? 103:07 esd - init platform -dir /var/opt/ SUNWsymon

■ If a running agent has terminated, examine the Sun Management Center log files

to determine the reason:

ssp# /opt/SUNWsymon/sbin/es-run ccat /var/opt/SUNWsymon/log/ agent.log ssp# /opt/SUNWsymon/sbin/es-run ccat /var/opt/SUNWsymon/log/ platform.log

■ If a discovery request failed, try rerunning the discovery request or increasing the

discovery request SNMP timeout value.

3. Examine the SSP Details window and use the browser to confirm that the Discovery Table module is loaded under Local Applications, and that it is not empty. If the Discovery Table module is not loaded, run platform setup again. See “To Run the Setup Script” on page 31 for more information.

4. Create the Starfire platform object as described in “To Create a Starfire Platform Object” on page 42.

5. Examine the Browser tab of the platform Details window to confirm that the Config Reader (Starfire Platform) module is loaded under Hardware and that the module is not disabled. The Discovery Object Table provided by this module defines the objects that will be included in the Starfire platform composite.

40 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Starfire Platform Objects

Starfire platform information is provided by a Sun Management Center platform agent running on the main SSP. When a spare SSP is configured, two Starfire platform objects are present in the Starfire platform composite. One provides information from the main SSP and the other provides information from the spare SSP.

Starfire platform information is only available from the platform object associated with the main SSP. When a platform object is created as part of a composite, the platform object name includes the associated SSP name in square brackets. The spare SSP object and its associated Starfire platform topology objects are marked with a Disabled alarm icon to distinguish the spare and main topology objects (

Main Platform Object and SSP

Spare Platform Object and SSP

FIGURE 4-2):

FIGURE 4-2 Main and Spare Starfire Platform and SSP Icons

Note – If a higher severity alarm exists for the spare SSP or Starfire platform, the

higher severity alarm is displayed on the object instead of the Disabled alarm icon.

Once Sun Management Center has been installed and set up on the main and spare SSPs and the Starfire platform objects have been created, no Sun Management Center configuration changes are required when the spare SSP becomes the acting main SSP.

When this switch from spare to acting main SSP occurs, the platform agent on the acting main SSP becomes active and collects current information about the Starfire platform.

Not all the information that was available prior to this switch will be available from the newly active platform agent. For example, the Starfire domain information must be gathered again and if a Starfire domain Sun Management Center agent is no longer accessible, that domain configuration information is now unknown.

The counts maintained for SNMP communications errors or the number of arbstops encountered are also reset to zero. Current errors such as a high temperature will be reported if the condition still persists.

The Sun Management Center agents on the spare and main SSP are not automatically synchronized. If you modify any of the default limits, attributes, or loaded modules of the Sun Management Center agents on either the main or spare SSP, you should also make those changes to the agents operating on the other SSP.

▼ To Create a Starfire Platform Object

Starfire platform objects are created as part of the Starfire composite. You can also create the platform objects directly.

1. Follow the instructions in “Creating a Node” in Chapter 5 of the Sun Management Center 2.1 Software User ’s Guide instructions to create a Starfire platform object.

2. In Step 3, select the Agent - Platform monitoring type from the Monitor Via pulldown menu.

3. In Step 4, type the name or IP address of the SSP.

Note – The default platform agent port number is port 166. Do not change this port

number unless the platform agent was configured on a different port during Sun Management Center setup.

42 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

CHAPTER

Starfire System Details Windows

The add-on Starfire components consist of the following Sun Management Center agent modules that are viewable from the Starfire System Details windows:

TABLE5-1 Sun Management Center Agent Modules

Module Name Details Window

Config Reader (Starfire Domain) Starfire Domain Config Reader (Starfire Platform) Starfire Platform SSP Status SSP Discovery Table SSP

These modules provide Starfire hardware monitoring capability and provide information about the Starfire composite configuration. See “Starfire Agent Modules” on page 53 for detailed information about the objects and properties provided by these modules.

This chapter provides details about the Starfire domain and platform information shown in the Details window. Three related chapters in the Sun Management Center

2.1 Software User’s Guide provide general information about using the Sun Management Center Details window:

■ Chapter 7, “Sun Management Center Software Main Console Window,” shows

you how to use the main Sun Management Center console window.

■ Chapter 8, “Browser,” shows you how to display the Details window from the

main Sun Management Center console window.

■ Chapter 14, “Details,” shows you how to use the Details window.

Starfire Domain Details Window

The Starfire domain Details window resembles the host Details window described in the Sun Management Center 2.1 Software User’s Guide , except that additional information is shown by the Hardware tab.

Note – If your Starfire domain Details window does not include a Hardware tab,

Starfire support has not been installed correctly on your Sun Management Center server host. Confirm that the add-on Starfire components have been installed and set up, and that the Sun Management Center server process has been restarted following installation.

The Hardware tab displays information provided by the Starfire domain Config Reader module. This module provides up-to-date information about the system boards and the components that reside on those boards including:

■ Processors

■ Memory

■ Attached I/O devices

Only the system boards allocated to the Starfire domain are included in this information. Information about the hardware configuration of the entire platform can be viewed from the Starfire platform Details window. See “Starfire Platform Details Window” on page 46 for more information.

Starfire Domain Configuration Resources

The Resources view of the Starfire domain Hardware tab provides information about the platform components of which this Starfire domain is a part, as well as summary information about domain hardware resources (

44 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

FIGURE 5-1).

FIGURE 5-1 Resource Information for a Starfire Domain

The Starfire Domain Information shown above includes these properties (TABLE 5-2):

TABLE5-2 Starfire Domain Information

Property Description

Starfire Platform Name Name given to the platform during SSP software configuration. SSP Hostname Hostname of the main SSP. SSP IP Address SSP IP address. Total System Boards Number of systems boards assigned to this Starfire domain. System Board List List of the system boards assigned to this Starfire domain.

Interaction With Starfire Domain Devices

The Starfire domain Config Reader module periodically opens and immediately closes Starfire domain disk and tape devices to determine the physical presence of these devices. These actions may cause the following behavior:

■ When devices have been configured into the system but are no longer physically

attached or are turned off, the Starfire domain Config Reader module operation may be delayed while the device open call attempts to contact the missing device.

This may lead to sluggish refreshing of the hardware configuration information or displaying the black star or “splat” icon on the Starfire domain Config Reader module. Resolve this problem by removing the entries for the missing devices in

/dev/rdsk and /dev/rmt or reconfiguring the system devices; see drvconfig(1M).

■ Dynamic Reconfiguration detach operations may occasionally fail, due to board

devices being momentarily busy due to this Config Reader activity. In the rare event that a DR detach operation fails, retrying the detach operation is usually successful.

Starfire Platform Details Window

The Sun Management Center Details window for a Starfire platform displays information about the entire platform hardware. This window includes the following tab buttons, which are explained in the Sun Management Center 2.1 Software User’s Guide:

■ Info

■ Browser

■ Alarms

■ Hardware

Note – If your Starfire platform Details window does not include each of these tab

buttons, Starfire support has not been correctly installed on your Sun Management Center server host. Confirm that the add-on Starfire components have been installed and set up, and that the Sun Management Center server process has been restarted following installation.

The Starfire platform is monitored by a Sun Management Center platform agent on the SSP. The platform agent is dedicated to this task, so you cannot load or unload agent modules from the Starfire platform Details window.

The Hardware tab displays information provided by the Starfire platform Config Reader module. This module provides up-to-date information about platform hardware, including:

■ Voltage and temperature

■ All boards

■ Power supplies

■ Fan trays

■ Hardware errors encountered, such as recordstop, arbstop, and watchdog.

46 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Both the Starfire platform and Starfire domain Config Reader modules provide information about the system board configuration. This duplicated information may cause the Starfire domain and platform Details window to report duplicate alarms for a single condition. This enables you to see alarms quickly, regardless of which Details window you are watching.

The Starfire platform Config Reader module does not provide configuration information for the I/O devices attached to the platform. To see this information, open a Starfire domain Details window for each domain whose I/O devices you want to check.

Determining the Complete Platform Configuration

The complete Starfire platform hardware configuration cannot be determined from the SSP alone. The Starfire platform Config Reader module queries the Starfire domain Config Reader module for the following system board information:

■ Memory configuration

■ I/O configuration

■ Processor details

■ Components which failed POST

If the platform Config Reader cannot access the Starfire domain Config Reader information, the detailed configuration for a system board assigned to that Starfire domain is unknown.

Caution – The Starfire platform Config Reader accesses Starfire domain information

using SNMP. If you use the Attribute Editor to change the security attributes of the Starfire domain Config Reader module and exclude access by the “public” SNMP community, the platform Config Reader module will be unable to access any Starfire domain configuration information.

Once the detailed system board configuration is determined, this information is available from the Starfire platform Details window even if the Starfire domain Config Reader is inaccessible. All hardware components whose configuration is unknown are clearly marked.

The system board configuration information gathered from the Starfire domain is cached and time-stamped so you can determine how current it is. This information is periodically checked and updated when it has changed. It is discarded whenever either of these events occurs:

■ The system board is physically removed from the Starfire platform.

■ The Starfire platform agent is stopped.

Note – There may be a delay of a few minutes before the Starfire platform Config

Reader module is updated with the most current Starfire domain information.

Starfire Platform Configuration Resources

The Resources view of the Starfire platform Hardware tab provides information about the hosts associated with this Starfire platform and a summary of the platform’s hardware configuration (

FIGURE 5-2).

FIGURE 5-2 Resource Information for a Starfire Platform

48 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

The Starfire Platform Information table shown in FIGURE 5-2 includes these properties (

TABLE5-3 Starfire Platform Information

Property Description

Platform Name Name given to the platform during SSP software configuration SSP Status Status, either Main or Spare, of the SSP associated with this

SSP Hostname Hostname of the SSP associated with this platform topology

Alternate SSP Hostname of the alternate SSP for this platform, if one is

Total Starfire Domains Number of Starfire domains configured for this platform Starfire Domain Names List of the domains configured on this Starfire platform

TABLE 5-3):

platform topology object

object

configured

Starfire Physical and Logical Views

In the Starfire domain physical view, the chassis picture has some grayed-out areas rather than the photo-realistic image shown in the Starfire platform physical view (

FIGURE 5-3). This difference reminds you that only Starfire domain system board

information is available from the Starfire domain.

Domain

FIGURE 5-3 Physical Views of a Starfire Domain and a Starfire Platform

Platform

Note – Display the Starfire platform physical view if you want more information

about the entire platform.

The Starfire platform physical view “watermarks” the system board memory and I/O modules whose presence is unknown with a question mark indicator (

FIGURE 5-4).

FIGURE 5-4 Unknown Module With Question Mark Indicator

The physical and logical view highlight components that have open alarms but, when displayed, the physical and logical view property detail information does not identify which property is currently in an alarm state. Many Starfire components are characterized by multiple properties that have rules and potential alarms. To determine which component properties have open alarms, examine the Alarm or Browser tab of the Details window.

50 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

The physical view shows only components that are visible in the platform chassis. For example, centerplane boards and I/O devices are not shown in the physical view. To view information on these devices, examine the logical view or Browser displays.

SSP Details Window

No changes specific to Starfire servers have been made to the SSP Details window. Two additional local application modules, SSP Status and Discovery Table, are configured for loading into the SSP agent during Starfire platform setup. These modules display the main or spare status of the SSP and provide Starfire composite information.

Note – If the SSP status module and Discovery Table are not loaded, perform

Starfire platform setup again.

52 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

CHAPTER

Starfire Agent Modules

This chapter provides specific information about the agent modules contained in the Starfire add-on components:

■ Starfire Domain Config Reader (Config-Reader4u1D)

■ Starfire Platform Config Reader (Config-Reader4u1P)

■ SSP Status module (sspStatus)

■ Discovery Table module (dtable)

This chapter also provides specific information about how to change rule limits for the Starfire domain Config Reader and Starfire platform Config Reader.

Appendix C and D of the Sun Management Center 2.1 Software User’s Guide describe the core Sun Management Center modules that monitor various components of your system, including your hardware, operating environment, local applications, and remote systems.

Chapter 10, “Attribute Editor” in the Sun Management Center 2.1 Software User’s Guide provides general information about how to use the Attribute Editor to set alarm limits.

Module Properties

The tables in this chapter provide brief descriptions of each property in a module. If a property is monitored by a Sun Management Center rule, the name of that rule is shown in the table. For descriptions of these rules, see “Starfire Config Reader Rules” on page 81.

A field-replaceable property means that the component can be replaced on-site. A hot-plug property means that the component can be removed from the platform

without shutting the system down.

Properties that can be graphed are noted in the property description. See Chapter 9 of the Sun Management Center 2.1 Software User’s Guide for more information about graphing properties.

Note – It is not always possible for Sun Management Center software to determine

the value for a particular property. When the value is unknown, the property value displayed is --.

Starfire Domain Config Reader Module

The Starfire Domain Config Reader module provides the hardware configuration for Starfire domains. During Starfire domain add-on setup, this module is configured for automatic loading into the Starfire domain agent and is displayed under the Browser hardware icon.

Module Refresh Intervals

Sun Management Center agent modules refresh their data at periodic intervals and the Browser periodically retrieves the current value of agent data. This combination of periodic refreshes and updates provides a current view of module information from the Details window.

The Starfire domain Config Reader module is refreshed every minute, and the refresh of all module data is driven by the refresh of the System folder. When viewing the module data from the Browser, you can request an immediate refresh of the module data. See “To Refresh Starfire Domain Config Reader Data” on page 54 fore more information.

You can also change the periodic interval at which the module refreshes its data. This periodic interval balances getting timely notification of changes to your system configuration with using system resources to accomplish this periodic refresh. See “To Change the Starfire Domain Config Reader Refresh Interval” on page 55 for more information.

▼ To Refresh Starfire Domain Config Reader Data

1. Open the Starfire domain Details window and select the Browser tab.

54 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

2. Select any property within the System folder and refresh that data.

This will cause the Starfire domain Config Reader module to refresh all its data.

3. If you wish to view information not contained in the System folder, select that property in the Browser and refresh the data.

This will update the Browser with the latest value of that property.

▼ To Change the Starfire Domain Config Reader

Refresh Interval

1. Open the Starfire domain Details window and select the Browser tab.

2. Select any property within the System folder and invoke the Attribute Editor.

Caution – Do not change the refresh interval to a value less than its default value.

3. Select the Refresh tab and change the refresh interval.

Starfire Domain Config Reader Properties

The tables in this section describe each of the visible properties for each Starfire Domain Config Reader object.

System

The following table provides a brief description of the properties for the Starfire Domain Config Reader System (

TABLE6-1 Starfire Domain Config Reader System

Property Rule (if any) Description

Name “system” Hostname Starfire domain hostname Host ID Host identification number Operating System Operating system running in the Starfire domain OS Version Version of the operating system running System Clock (MHz) Clock frequency in megahertz

TABLE 6-1):

TABLE6-1 Starfire Domain Config Reader System (Continued)

Property Rule (if any) Description

Architecture Machine architecture (SPARC) Machine Type Machine type (sun4u) Platform Type Platform type (SUNW, Ultra Enterprise 10000) Last Update Time the configuration information was last updated Total Disk Number of disks present in the system Total Memory

Total memory, in megabytes

(Mbytes) Total Processors Number of processors. This includes all processors

allocated to the domain, including processors not configured by POST.

Total Tape Devices Number of tape devices present in the system

Starfire Platform

The following table provides a brief description of the properties for the Starfire Domain Config Reader Platform (

TABLE6-2 Starfire Domain Config Reader Platform

TABLE 6-2):

Property Rule (if any) Description

Name “starfire_platform” Starfire Platform

Name

Name of the Starfire platform of which this Starfire

domain is a part SSP Hostname Name of the main SSP for the Starfire platform SSP IP address IP address of the main SSP for the Starfire platform Total System Boards Number of the system boards allocated to this Starfire

domain System Board List A list of all system boards allocated to this Starfire

domain

56 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

System Boards

The following table provides a brief description of the properties for Starfire Domain Config Reader System Boards (

TABLE6-3 Starfire Domain Config Reader System Boards

Property Rule (if any) Description

Name system-board(n) where n is the system board number System Board System board number POST Status e10kpost POST status for the entire system board Memory (Mbytes) System board memory size in megabytes Processors Number of processors on this system board I/O Adaptors Number of I/O adaptors on this system board Field Replaceable “yes” Hot Plug “yes”

TABLE 6-3):

System Board ASIC POST Status

The following table provides a brief description of the properties for Starfire Domain Config Reader System Board ASIC POST Status (

TABLE 6-4):

TABLE6-4 Starfire Domain Config Reader System Board ASIC POST Status

Property Rule (if any) Description

Name ASIC(n) where n is the system board number System Board System board number CIC0 e10kpost POST status for the coherency interface controller 0

ASIC and, more generally, this system board’s ability to operate with global address bus 0.

CIC1 e10kpost POST status for the coherency interface controller 1

ASIC and, more generally, this system board’s ability to operate with global address bus 1.

CIC2 e10kpost POST status for the coherency interface controller 2

ASIC and, more generally, this system board’s ability to operate with global address bus 2.

CIC3 e10kpost POST status for the coherency interface controller 3

ASIC and, more generally, this system board’s ability to operate with global address bus 3.

TABLE6-4 Starfire Domain Config Reader System Board ASIC POST Status (Continued)

Property Rule (if any) Description

LDPATH0 e10kpost POST status for the local data router lower 72 bits

ASIC and, more generally, this system board’s ability

to operate with global data bus 0. LDPATH1 e10kpost POST status for the local data router upper 72 bits

ASIC and, more generally, this system board’s ability

to operate with global data bus 1. PC0 e10kpost POST status for the port controller 0 ASIC PC1 e10kpost POST status for the port controller 1 ASIC PC2 e10kpost POST status for the port controller 2 ASIC XDB0 e10kpost POST status for the data buffer 0 ASIC XDB1 e10kpost POST status for the data buffer 1 ASIC XDB2 e10kpost POST status for the data buffer 2 ASIC XDB3 e10kpost POST status for the data buffer 3 ASIC

Processor Modules

The following table provides a brief description of the properties for Starfire Domain Config Reader Processor Modules (

TABLE 6-5):

TABLE6-5 Starfire Domain Config Reader Processor Modules

Property Rule (if any) Description

Name cpu-unit(n), where n is the Processor ID Processor Module n.m where n is the system board number and m is the

system board processor module number (0-3) Processor ID Processor identifier POST Status e10kpost POST status for this processor Status e10kproc Processor on-line/off-line status Clock (MHz) Processor clock frequency in megahertz Ecache Size

External cache size in megabytes (Mbytes)

Dcache Size (KB) Data cache size in kilobytes Icache Size (KB) Instruction cache size in kilobytes

58 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

TABLE6-5 Starfire Domain Config Reader Processor Modules (Continued)

Property Rule (if any) Description

Processor Type Processor type Model Processor model type Field Replaceable “yes”

Memory Modules

The following table provides a brief description of the properties for Starfire Domain Config Reader Memory Modules (

TABLE6-6 Starfire Domain Config Reader Memory Modules

Property Rule (if any) Description

Name mem-unit(n), where n is the memory module number Memory Module System board number this memory module is on POST Status e10kpost POST status of this memory module Size (Mbytes) Memory module size in megabytes Field Replaceable “yes”

TABLE 6-6):

Memory Groups

The following table provides a brief description of the properties for Starfire Domain Config Reader Memory Groups (

TABLE6-7 Starfire Domain Config Reader Memory Groups

Property Rule (if any) Description

Name mem-group(n.m), where n.m is the memory group

Memory Group n.m where n is the memory module number and m is

POST Status e10kpost POST status of this memory group Size (Mbytes) Memory group size in megabytes

TABLE 6-7):

number

the memory group number (0-3)

DIMM Table

The following table provides a brief description of the properties for Starfire Domain Config Reader DIMM Table (

TABLE6-8 Starfire Domain Config Reader DIMM Table

Property Rule (if any) Description

Name dimm(i.j.k), where i.j.k is the DIMM number DIMM i.j.k where i is the memory module number, j is the

ECC Errors e10kmerr (graphable) Number of ECC errors detected in

Size (Mbytes) DIMM size in megabytes Board Reference Part location silk-screened on the memory module

Field Replaceable “yes”

TABLE 6-8):

memory group number, and k is the DIMM number

(0-7)

/var/adm/messages for this DIMM.

mezzanine board

I/O Modules

The following table provides a brief description of the properties for Starfire Domain Config Reader I/O Modules (

TABLE 6-9).

TABLE6-9 Starfire Domain Config Reader I/O Modules

Property Rule (if any) Description

Name io-unit(n), where n is the I/O module number I/O Module System board number this I/O module is on I/O Module Type I/O module type is either SBus or PCI. The type is

displayed as unknown (--) if no board I/O adaptors or

controllers were configured by POST. I/O Adaptors Number of I/O adaptors on this I/O module Field Replaceable “yes”

60 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

I/O Controllers

The following table provides a brief description of the properties for Starfire Domain Config Reader I/O Controllers (

TABLE6-10 Starfire Domain Config Reader I/O Controllers

Property Rule (if any) Description

Name When the I/O controller is configured by POST, the

I/O Controller n.m where n is the I/O module number and m is the

POST Status e10kpost POST status for this I/O controller UPA Portid UPA portid for this I/O controller displayed in

Clock (MHz) I/O controller clock frequency in megahertz Model Model name Version Number Version number

TABLE 6-10):

name is either sbus(n) or pci(n) where n is the kernel assigned instance number for the controller. If not configured by POST, the name is io-controller(n.m) where n.m is the I/O controller number

host bus controller number (0-1)

hexadecimal

Note – I/O controllers for empty I/O adaptor slots are not included in the I/O

Controllers table.

I/O Adaptors

The following table provides a brief description of the properties for Starfire Domain Config Reader I/O Adaptors (

TABLE6-11 Starfire Domain Config Reader I/O Adaptors

Property Rule (if any) Description

Name io-adaptor(i.j.k), where i.j.k is the I/O adaptor number I/O Adaptor i.j.k where i is the I/O module number, j is the I/O

POST Status e10kpost POST status for this I/O adaptor

TABLE 6-11):

controller number, and k is the adaptor slot number (0-1)

TABLE6-11 Starfire Domain Config Reader I/O Adaptors (Continued)

Property Rule (if any) Description

Model If known, the model name for this I/O adaptor Device Summary Summary of I/O device drivers and devices supported

by this I/O adaptor Disk Count Number of disks supported by this I/O adaptor Network Count Number of configured network interfaces supported

by this I/O adaptor Tape Count Number of tape devices support by this I/O adaptor

I/O Device Drivers

The following table provides a brief description of the properties for Starfire Domain Config Reader I/O Device Drivers (

TABLE6-12 Starfire Domain Config Reader I/O Device Drivers

Property Rule (if any) Description

Name Device driver name and kernel assigned instance

I/O Adaptor I/O adaptor number for this device Device Type Device type, if known, such as SCSI or network.

TABLE 6-12):

number, such as isp(2). If an instance number has

not been assigned, the device name and register

properties are used instead.

Tape Devices

The following table provides a brief description of the properties for Starfire Domain Config Reader Tape Devices (

TABLE6-13 Starfire Domain Config Reader Tape Devices

Property Rule (if any) Description

Name Device name and kernel assigned instance number,

Tape Name /dev name for this tape device I/O Adaptor I/O adaptor number for this device

62 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

TABLE 6-13):

such as st(0)

TABLE6-13 Starfire Domain Config Reader Tape Devices (Continued)

Property Rule (if any) Description

Status Current status, such as “ok” or “drive present, but

busy”

Tape Warnings e10ktwrn (graphable) Number of tape warnings detected in

/var/adm/messages for this tape. Model Model name for this tape device, if known Target Number Tape target number Field Replaceable “yes”

Network Devices

The following table provides a brief description of the properties for Starfire Domain Config Reader Network Devices (

TABLE6-14 Starfire Domain Config Reader Network Devices

Property Rule (if any) Description

Name Device name and kernel assigned instance number

Interface Name Network interface name I/O Adaptor I/O adaptor number for this device Symbolic Name Hostname associated with this network interface Internet Address IP address for the network interface Ethernet Address Ethernet address for the network interface

TABLE 6-14):

such as le(0). If an instance number has not been

assigned, the device name and register properties are

used instead.

Disk Devices

The following table provides a brief description of the properties for Starfire Domain Config Reader disk devices (

TABLE6-15 Starfire Domain Config Reader Disk Devices

Property Rule (if any) Description

Name Device name and kernel assigned instance number,

Disk Name /dev name for this disk I/O Adaptor I/O adaptor number for this device Disk Warnings e10kdwrn (graphable) Number of disk warnings detected in

Target Number Disk target number Field Replaceable “yes”

TABLE 6-15):

such as sd(0)

/var/adm/messages for this disk.

Starfire Platform Config Reader Module

The Starfire Platform Config Reader module provides information about the hardware configuration for the entire Starfire platform. During Starfire platform add-on setup, this module is configured for automatic loading into the SSP platform agent and is displayed under the browser Hardware icon.

This module is automatically disabled when the SSP becomes the spare SSP, and is enabled when the SSP becomes the main SSP. When the module is disabled, no platform information is available.

Module Refresh

The Starfire Platform Config Reader module gathers its data from two primary sources: the SSP snmpd agent and the Starfire domain Config Reader modules. SNMP traps are monitored by the module to get prompt notification of system configuration changes. In addition, the configuration information is updated at periodic intervals in case an SNMP trap is missed.

Gathering so much data at one time consumes too many system resources, so the platform agent does not gather it all at once. A complete refresh of the module data requires a span of 3–12 minutes, depending on the system configuration.

64 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Using the browser from the platform Details window, you can refresh any module property, but doing so only retrieves the current value of the property from the platform agent. It does not force a recalculation of the data.

The Refresh Model properties described in “Refresh Model” on page 79 enable you to start a refresh of the SSP or Starfire domain model data.

Starfire Platform Config Reader Properties

Platform Config Reader information gathered from the Starfire domain Config Reader is identified in the property description. Tables that have information gathered from the Starfire domain Config Reader have a Cache Updated property that is a time stamp of when this information was gathered from the Starfire domain.

Note – Since the Starfire domain configuration information is updated only when it

changes and Starfire domain data changes infrequently, the Cache Updated time stamp may appear old even though the data is current.

If the Cache Updated property has a value of --, Starfire domain information for that table row is unavailable.

Note – A °C notation refers to temperatures measured in degrees Celsius.

System

The following table provides a brief description of the properties for the Starfire Platform Config Reader System (

TABLE6-16 Starfire Platform Config Reader System

Property Rule (if any) Description

Name “system” Platform Name Name assigned to this Starfire platform

Ambient Temp (°C) e10ktemp (graphable) Ambient temperature as

Total Starfire Domains Number of Starfire domains configured Total System Boards Number of system boards

TABLE 6-16):

during SSP software configuration

measured by a sensor on the master control board

TABLE6-16 Starfire Platform Config Reader System (Continued)

Property Rule (if any) Description

Total Processors Number of processors Total Control Boards Number of control boards Total Centerplane Boards Number of centerplane boards Total Centerplane Support

Number of centerplane support boards

Boards Total I/O Cabinets Number of I/O cabinets Total Fan Trays Number of fan trays Total 48V Power Supplies Number of power supplies Master Control Board Master control board number SysClk Control Board System clock is provided by this control

board System Clock Frequency (MHz) Clock frequency in megahertz Last Update Last time the configuration information for

the System object was updated

System Boards

The following table provides a brief description of the properties for Starfire Platform Config Reader System Boards (

TABLE6-17 Starfire Platform Config Reader System Boards

Property Rule (if any) Description

Name system-board(n) where n is the system board

System Board System board number Power Status e10kpowr Indicates whether the board power is on or off. Starfire Domain Name of the Starfire domain this board is

POST Status e10kpost (Starfire domain) POST status for the entire

Memory (Mbytes) (Starfire domain) System board memory size in

Processors Number of processors on this system board

66 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

TABLE 6-17):

number

assigned to. A ’--’ is displayed if the board is not assigned to any Starfire domain.

system board

megabytes

TABLE6-17 Starfire Platform Config Reader System Boards (Continued)

Property Rule (if any) Description

I/O Adaptors (Starfire domain) Number of I/O adaptors on this

system board

CIC0 Temp (°C) e10ktemp (graphable) Temperature of the CIC0 ASIC CIC1 Temp (°C) e10ktemp (graphable) Temperature of the CIC1 ASIC MC Temp (°C) e10ktemp (graphable) Temperature of the MC ASIC XDB2 Temp (°C) e10ktemp (graphable) Temperature of the XDB2 ASIC XDB3 Temp (°C) e10ktemp (graphable) Temperature of the XCB3 ASIC Proc0 Temp (°C) e10ktemp (graphable) Temperature of the processor unit 0 Proc1 Temp (°C) e10ktemp (graphable) Temperature of the processor unit 1 Proc2 Temp (°C) e10ktemp (graphable) Temperature of the processor unit 2 Proc3 Temp (°C) e10ktemp (graphable) Temperature of the processor unit 3

3.3 VDC Temp (°C) e10ktemp (graphable) Temperature of the board 3.3 VDC

power supply

VDC Core Temp (°C) e10ktemp (graphable) Temperature of the board VDC core

power supply

5 VDC Temp (°C) e10ktemp (graphable) Temperature of the system board

5 VDC power supply

3.3 VDC Voltage (V) e10kvolt (graphable) Voltage level for the board 3.3 VDC power

5 VDC/HK Voltage (V) e10kvolt (graphable) Voltage level for the board 5 VDC

housekeeping power

5 VDC Voltage (V) e10kvolt (graphable) Voltage level for the board 5 VDC

power

VDC Core Voltage (V) e10kvolt (graphable) Voltage level for the board VDC core

power

3.3 VDC/HK Voltage (V) e10kvolt (graphable) Voltage level for the board 3.3 VDC housekeeping power

Serial Number System board serial number. Due to the manner

in which this information is collected, a -- is displayed if the system board has not been thermally calibrated

Cache Updated Time the Starfire domain data was last updated Field Replaceable “yes” Hot Plug “yes”

System Board ASIC POST Status

The values in this table are retrieved from the corresponding Starfire domain Config Reader module. These properties are described in

TABLE 6-4. An additional Cache

Updated property in this table displays the time that the information was gathered from the Starfire domain.

Processor Modules

The following table provides a brief description of the properties for Starfire Platform Config Reader Processor Modules (

TABLE6-18 Starfire Platform Config Reader Processor Modules

Property Rule (if any) Description

Name cpu-unit(n), where n is the Processor ID Processor Module n.m where n is the system board number and m is the

system board processor module number (0-3) Processor ID Processor identifier POST Status e10kpost (Starfire domain) POST status for this processor Status e10kproc (Starfire domain) Processor on-line/off-line status Clock (MHz) (Starfire domain) Processor clock frequency in

megahertz Ecache Size

(Mbytes) Dcache Size (KB) (Starfire domain) Data cache size in kilobytes Icache Size (KB) (Starfire domain) Instruction cache size in kilobytes Processor Type (Starfire domain) Processor type Model (Starfire domain) Processor model type Cache Updated Time Starfire domain data was last updated Field Replaceable “yes”

(Starfire domain) External cache size in megabytes

TABLE 6-18):

Memory Modules

When system board configuration information from a Starfire domain is unavailable, it is unknown whether the board has a memory module configured and a table entry is created for the memory module. The memory module properties have a value of

-- to indicate that the information is unavailable.

68 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

When this Starfire domain information becomes available, the table is updated. If the memory module is not present, the table entry for the memory module is removed.

The following table provides a brief description of the properties for Starfire Platform Config Reader Memory Modules (

TABLE6-19 Starfire Platform Config Reader Memory Modules

Property Rule (if any) Description

Name mem-unit(n), where n is the memory module number Memory Module System board number this memory module is on POST Status e10kpost (Starfire domain) The POST status of this memory

module Size (Mbytes) (Starfire domain) Memory module size in megabytes Cache Updated Time Starfire domain data was last updated Field Replaceable “yes”

TABLE 6-19):

Memory Groups

The values in this table are retrieved from the corresponding Starfire domain Config Reader module. These properties are described in Updated property in this table displays the time the information was gathered from the Starfire domain.

TABLE 6-7. An additional Cache

DIMM Table

The values in this table are retrieved from the corresponding Starfire domain Config Reader module. These properties are described in

TABLE 6-8. An additional Cache

Updated property in this table displays the time the information was gathered from the Starfire domain.

I/O Modules

When system board configuration information from a Starfire domain is unavailable, it is unknown whether the board has an I/O module configured and a table entry is created for the I/O module. The I/O module properties have a value of -- to indicate that the information is unavailable.

When this Starfire domain information becomes available, the table is updated. If the I/O module is not present, the table entry for the I/O module is removed.

The following table provides a brief description of the properties for Starfire Platform Config Reader I/O Modules (

TABLE6-20 Starfire Platform Config Reader I/O Modules

Property Rule (if any) Description

Name io-unit(n), where n is the I/O module number I/O Module System board number this I/O module is on I/O Module Type (Starfire domain) I/O module type is either SBus or

I/O Adaptors (Starfire domain) Number of I/O adaptors on this I/O

Cache Updated Time Starfire domain data was last updated Field Replaceable “yes”

TABLE 6-20):

PCI. Type is displayed as unknown (--) if no board I/O adaptors or controllers were configured by POST.

module

I/O Controllers

TABLE 6-10. An additional Cache

I/O Adaptors

70 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

TABLE 6-11. An additional Cache

Centerplane Boards

The following table provides a brief description of the properties for Starfire Platform Config Reader Centerplane Boards (

TABLE6-21 Starfire Platform Config Reader Centerplane Boards

Property Rule (if any) Description

Name centerplane(n), where n is the centerplane board

number Centerplane Board Centerplane board number (0-1) Temp 0 (°C) e10ktemp (graphable) Temperature at sensor 0 on the centerplane Temp 1 (°C) e10ktemp (graphable) Temperature at sensor 1 on the centerplane Temp 2 (°C) e10ktemp (graphable) Temperature at sensor 2 on the centerplane Temp 3 (°C) e10ktemp (graphable) Temperature at sensor 3 on the centerplane Temp 4 (°C) e10ktemp (graphable) Temperature at sensor 4 on the centerplane Temp 5 (°C) e10ktemp (graphable) Temperature at sensor 5 on the centerplane Temp 6 (°C) e10ktemp (graphable) Temperature at sensor 6 on the centerplane Temp 7 (°C) e10ktemp (graphable) Temperature at sensor 7 on the centerplane Temp 8 (°C) e10ktemp (graphable) Temperature at sensor 8 on the centerplane Temp 9 (°C) e10ktemp (graphable) Temperature at sensor 9 on the centerplane Field Replaceable “yes”

TABLE 6-21):

Centerplane Support Boards

The following table provides a brief description of the properties for the Starfire Platform Config Reader Centerplane Support Boards (

TABLE6-22 Starfire Platform Config Reader Centerplane Support Boards

Property Rule (if any) Description

Name centerplane-support-board(n), where n is the

centerplane support board number

Centerplane Support Board

Power Status e10kpowr Indicates whether the board power is on or off

Centerplane support board number (0-1)

TABLE 6-22):

TABLE6-22 Starfire Platform Config Reader Centerplane Support Boards (Continued)

Property Rule (if any) Description

3.3 VDC1 Temp (°C) e10ktemp (graphable) Temperature of the 3.3 VDC power

supply (sensor 1)

3.3 VDC 2 Temp (°C) e10ktemp (graphable) Temperature of the 3.3 VDC power

supply (sensor 2)

5 VDC/HK Voltage (V) e10kvolt (graphable) Voltage level for the board 5 VDC

housekeeping power

3.3 VDC/HK Voltage (V) e10kvolt (graphable) Voltage level for the board 3.3 VDC housekeeping power

3.3 VDC Voltage (V) e10kvolt (graphable) Voltage level for the board 3.3 VDC power

Field Replaceable “yes”

Control Boards

The following table provides a brief description of the properties for the Starfire Platform Config Reader Control Boards (

TABLE6-23 Starfire Platform Config Reader Control Boards

TABLE 6-23):

Property Rule (if any) Description

Name control-board(n), where n is the control board

number Control Board Control board number (0-1) Power Status e10kpowr Indicates whether the board power is on or off Control Board

Hostname

Hostname associated with the IP address of the

control board 5 VDC Temp (°C) e10ktemp (graphable) Temperature of the board 5 VDC power

supply 5 VDC Peripheral

Temp (°C)

e10ktemp (graphable) Temperature of the board 5 VDC

peripheral power supply 5 VDC Fan Temp (°C) e10ktemp (graphable) Temperature of the board 5 VDC fan

power supply Sensor 0 Temp (°C) e10ktemp (graphable) Ambient temperature at sensor 0 Sensor 1 Temp (°C) e10ktemp (graphable) Ambient temperature at sensor 1 Sensor 2 Temp (°C) e10ktemp (graphable) Ambient temperature at sensor 2

5 VDC Voltage (V) e10kvolt (graphable) Voltage level for the board 5 VDC power

72 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

TABLE6-23 Starfire Platform Config Reader Control Boards (Continued)

Property Rule (if any) Description

5 VDC/HK Voltage

(V)

3.3 VDC/HK Voltage

(V) 5 VDC Peripheral

Voltage (V) 5 VDC Fan Voltage (V) e10kvolt (graphable) Voltage level for the board 5V fan power Field Replaceable “yes”

e10kvolt (graphable) Voltage level for the board 5 VDC

housekeeping power

e10kvolt (graphable) Voltage level for the board 3.3 VDC

housekeeping power

e10kvolt (graphable) Voltage level for the board 5 VDC

peripheral power

Fan Trays

The following table provides a brief description of the properties for the Starfire Platform Config Reader Fan Trays (

TABLE6-24 Starfire Platform Config Reader Fan Trays

Property Rule (if any) Description

Name fantray(n), where n is the fan tray number Fan Tray Fan tray number Power Status e10kpowr Indicates whether the fan power is on or off Field Replaceable “yes” Hot Plug “yes”

TABLE 6-24):

Fans

The following table provides a brief description of the properties for Starfire Platform Config Reader Fans (

TABLE6-25 Starfire Platform Config Reader Fans

Property Rule (if any) Description

Name fanunit(n), where n is the fan unit number Fan Tray Fan tray number (0-15)

TABLE 6-25):

TABLE6-25 Starfire Platform Config Reader Fans (Continued)

Property Rule (if any) Description

Fan Fan number (0-1) Power Status e10kpowr Indicates whether the fan power is on, off, or failed Speed Fan speed. Either Nominal (low speed) or Fast (high

speed)

48V Power Supplies

The following table provides a brief description of the properties for Starfire Platform Config Reader 48V Power Supplies (

TABLE6-26 Starfire Platform Config Reader Power Supplies

Property Rule (if any) Description

Name bulkpower(n), where n is the power supply number Power Supply Power supply number (0-15) Status e10kpowr Power status is either Ok or Failed Field Replaceable “yes” Hot Plug “yes”

TABLE 6-26):

AC Power Input Modules

The following table provides a brief description of the properties for Starfire Platform Config Reader AC Power Input Modules (

TABLE6-27 Starfire Platform Config Reader AC Power Input Modules

Property Rule (if any) Description

Name acpower(n), where n is the AC power input module

number

AC Power Input Module

74 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

AC power input module number (0-7)

TABLE 6-27):

I/O Cabinet Table

The following table provides a brief description of the properties for the Starfire Platform Config Reader I/O Cabinet (

TABLE6-28 Starfire Platform Config Reader I/O Cabinet Table

Property Rule (if any) Description

Name io(n), where n is the I/O cabinet number I/O Cabinet I/O cabinet number Power Status e10kpowr Power status is either on or off Field Replaceable “yes”

TABLE 6-28):

SSP Information

The SSP Information table is only viewable from the Browser tab in the Starfire platform Details window. It is not part of the hardware tree displayed in the physical and logical views.

The following table provides a brief description of the properties for Starfire Platform Config Reader SSP Information (

TABLE 6-29):

TABLE6-29 Starfire Platform Config Reader SSP Information

Property Rule (if any) Description

SSP Hostname Hostname of the SSP associated with this platform

object

SSP Status Status, Main or Spare, of the SSP associated with this

platform object. Platform information is not available from this platform object when its SSP status is Spare; use the platform object associated with the Main SSP.

snmpd Last Updated Last time SNMP operations with the SSP snmpd

process were successfully completed

snmpd Communication Errors

rCompare (graphable) Number of consecutive SNMP

communication errors which have occurred when accessing the SSP snmpd platform data. This error count may reflect a transient problem, such as increased SSP activity causing SNMP timeouts, or a more persistent problem with snmpd SNMP communications.

TABLE6-29 Starfire Platform Config Reader SSP Information (Continued)

Property Rule (if any) Description

snmpd Traps Received “yes” if SSP snmpd traps have been received, or -- if

no traps have been received yet. A value of -- does not necessarily indicate an error in the SSP snmpd trap

forwarding configuration. Alternate SSP Hostname of the alternate SSP for this platform SSP Software Version SSP software version

Starfire Domains

The Starfire Domains table is only viewable from the Browser tab in the Starfire platform Details window. It is not part of the hardware tree displayed in the physical and logical views.

The following table provides a brief description of the properties for Starfire Platform Config Reader Starfire Domains (

TABLE6-30 Starfire Platform Config Reader Starfire Domains

Property Rule (if any) Description

Domain Name Starfire domain hostname Arbstop Count e10kdtrp (graphable) Number of arbstops detected for this

domain

Recordstop Count e10kdtrp (graphable) Number of recordstop events detected

for this domain

Watchdog Count e10kdtrp (graphable) Number of watchdog events detected for

this domain

Total System Boards Number of system boards allocated to this Starfire

domain

System Board List List of the system boards allocated to this Starfire

domain

Configured System Board List

Boot Processor Boot processor number for the Starfire domain. If the

List of the system boards configured by POST for this Starfire domain

value is -1, the Starfire domain is not configured or booted.

TABLE 6-30):

76 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

Agent Status

The Agent Status information is only viewable from the Browser tab in the Starfire platform Details window. It is not part of the hardware hierarchy displayed in the physical and logical views.

The Starfire platform Config Reader module communicates with the Starfire domain Sun Management Center agent to determine the Starfire composite topology object type (Agent Host or ICMP Ping) for the Starfire domain and to gather the Starfire domain-resident system board configuration information. This agent status information is presented largely for diagnostic purposes and consists of the Starfire Domain Ports property and the Agent Status Table.

The following table provides a brief description of the properties for the Starfire Platform Config Reader Starfire Domain Ports (

TABLE6-31 Starfire Platform Config Reader Starfire Domain Ports

Property Rule (if any) Description

Starfire Domain Ports

List of Sun Management Center Agent network ports for the platform’s Starfire domains. This list is supplied during the setup of the Starfire platform add-on component.

The following table provides a brief description of the properties for the Agent Status Table (

TABLE 6-32):

TABLE 6-31):

TABLE6-32 Agent Status Table

Property Rule (if any) Description

Hostname Hostname of the Starfire domain Agent Port Network port on which the Starfire domain Sun

Management Center agent is configured. This port is determined by sending the agent a message and receiving a response. If this value is --, communication with the agent has not been established.

TABLE6-32 Agent Status Table (Continued)

Property Rule (if any) Description

SNMP Communication Errors

Status If agent communication has been established,

Last Update Time Last time successful communications with the

rCompare (graphable) The number of consecutive SNMP

communication errors which have occurred when accessing the Starfire domain Config Reader data. This error count may reflect a transient problem, such as increased system activity causing SNMP timeouts, or a more persistent problem with SNMP communications.

indicates the current status of communications.

Starfire domain agent occurred

Values for the Status property are shown in TABLE 6-33:

TABLE6-33 Status Property Values

Value Description

-- Communication with the agent is not established Ok Sun Management Center agent is present; no errors Host Not

Responding Agent Not

Responding Module Not

Responding

Starfire domain is down or not responding

Starfire domain is up; the agent is not present or not responding

Starfire domain is up and the agent is up; the requested module is not loaded or is not responding

Discovery Object Information

The Discovery Object Information table is only viewable from the Browser tab in the Starfire platform Details window. It is not part of the hardware hierarchy displayed in the physical and logical views.

The Discovery Object Table provides information used by the Discovery Manager and the Create Topology Object GUI to create Starfire composites. This information is presented largely for diagnostics purposes and contains information not directly relevant to the Sun Management Center software user. This information consists of a table identifier (the Magic Number), followed by a table containing information for each topology object created as part of the Starfire composite. A Magic Number value of 53444f54 identifies the following table as a valid Discovery Object Table.

78 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

The following table provides a brief description of the properties for the Starfire Platform Config Reader Discovery Object Table (

TABLE6-34 Starfire Platform Config Reader Discovery Object Table

Property Rule (if any) Description

Topology ID Encoded topology identification Topology Parent Topology identification of the parent of this object Discovery Type Encoded discovery type IP Address IP address for this topology object Agent Port Network port number for this topology object Family Type Topology object family type Label Object label displayed in the Sun Management Center

topology

Description Optional description of the object

TABLE 6-34):

Note – A -1 value for the Agent Port indicates that the object is a Platform Group

object.

Refresh Model

The two properties in this table describe the way the Starfire platform Config Reader module is refreshed. Using the Browser, you can select a property and refresh it. This will start a refresh cycle for the selected information.

The following table provides a brief description of the properties for the Starfire Platform Config Reader Refresh Model (

TABLE6-35 Starfire Platform Config Reader Refresh Model

Property Rule (if any) Description

Refresh SSP Model Number displayed is a count of SSP model refresh

Refresh Starfire Domain Model

TABLE 6-35):

operations Number displayed is a count of Starfire Domain model

refresh operations

SSP Status Module

The SSP Status module monitors the main or spare status of the SSP. During Starfire platform add-on setup, this module is configured for automatic loading in the SSP agent and is displayed under the Browser local applications icon.

The following table provides a brief description of the properties for the SSP Status Module (

TABLE6-36 SSP Status Module

Property Rule (if any) Description

SSP Status rSspStatus Status, either Main or Spare, of the SSP SSP Hostname Hostname of the SSP

The rSspStatus rule raises a disabled alarm if the status is Spare SSP.

TABLE 6-36):

Discovery Table Module

The Discovery Table module provides information to the Discovery Manager and Create Topology Object GUI necessary to create composite objects. During Starfire platform add-on setup, this module is configured for automatic loading in the SSP agent and is displayed under the Browser local applications icon.

This information is presented largely for diagnostic purposes and contains information not directly relevant to the Sun Management Center software user. This information consists of a table identifier (the Magic Number), which is 534454, followed by a table containing information for each composite object hosted by this system (

TABLE6-37 Discovery Table

Property Rule (if any) Description

IP Address IP address where the composite information table is

Port Network port used with the IP address OID SNMP OID used with the IP address

80 Sun Management Center 2.1 Supplement for Starfire Servers • November 1999

TABLE 6-36):

located

Sun Microsystems Sun Management Center User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Sun Microsystems, Inc.

Contents

Figures

Tables

Preface

Before You Read This Book

How This Book Is Organized

Using UNIX Commands

Typographic Conventions

Shell Prompts

Related Documentation

Ordering Sun Documentation

Accessing Sun Documentation Online

Sun Welcomes Your Comments

Introduction to Sun Management Center 2.1 Supplement for Starfire Servers

Known Limitations

Starfire Config Reader and Storage Enclosures

▼ To Determine Disk-to-Enclosure Mapping

1. Display the Starfire domain Host Details window

2. Use the browser to display the Config Reader Disk Devices table

3. Find the entry that corresponds to the disk you want to map to an enclosure.

4. Look for the disk name, which resembles cntndn, where n is an integer.

Known Bugs

Starfire System Add-On Component Packages

Preparing to Install Sun Management Center Software for Starfire Systems

Where to Install Sun Management Center Software for Starfire Systems

Choosing Your Sun Management Center Server Host

Required Sun Management Center Version

System Requirements

Supported Operating Environments

Supported SSP Releases

Required SSP Memory Configuration

Required Patches

Required Network Port Configuration

SSP Config Reader Support

Sun Management Center Installation Files

Considerations When Installing Sun Management Center 2.1 Software on Starfire Systems

▼ To Mount a Remote CD-ROM Drive

1. Log in to the SSP as superuser.

2. Insert the Sun Management Center 2.1 CD into the CD-ROM drive on the SSP.

3. Type the share(1M) command on the SSP to make the CD-ROM usable across the network.

4. Log in to a Starfire domain as superuser.

6. Mount the SSP /cdrom directory on /cdrom:

7. Change to the Sun Management Center software installation directory:

Sun Management Center Software Licensing

Starfire Software Installation Sequence

1. Sun Management Center server host

2. Starfire Domains

3. Main SSP

4. Spare SSP (if configured)

5. Sun Management Center console host

Proceeding With the Installation

Setting Up Add-On Sun Management Center Components for Starfire Servers

▼ To Set Up a Starfire Domain Add-On Component

1. Type y (for Yes).

2. If the query is unable to determine the SSP name, type the SSP name when prompted.

1. Type y (for Yes).

2. Type y (for Yes) when prompted to restart the SSP snmpd process.

5. If the platform agent port is in use, select a different network port when prompted to do so.

6. Type y (for Yes) to regenerate the security keys when prompted to do so:

Setting Up the Sun Management Center Server License

▼ To Set Up the Server License

1. Log in as superuser on the Sun Management Center server.

2. Type this command:

3. Type y (for Yes).

Restarting the SSP snmpd Process

Restarting snmpd During Starfire Platform Package Setup

Restarting snmpd After Starfire Platform Package Removal

Risks in Restarting snmpd

How to Restart snmpd

1. Log in to the main SSP as superuser.

2. Find the snmpd process number by typing:

3. If snmpd is running, kill the snmpd process by typing:

Reconfiguring Starfire Setup Parameters

▼ To Run the Setup Script

1. Log in as superuser and stop the components you will be reconfiguring.