Sun Fire™ V20z and Sun Fire V40z Servers Server Management Guide Sun Microsystems, Inc. www.sun.com Part No. 817-5249-11 May, 2004, Revision A Submit comments about this document at: http://www.sun.
Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
Contents Preface xix How This Book Is Organized Related Documentation xx Accessing Sun Documentation Third-Party Web Sites xix xxi xxi Contacting Sun Technical Support Sun Welcomes Your Comments 1.
Assigning Static SP Network Settings Part II: Securing the Service Processor 13 Creating the Initial Manager Account Enabling IPMI Access on the Server 11 13 14 Enabling IPMI Access on a Linux-Based Server (In-Band) 14 Enabling IPMI Access on a Solaris-Based x86 Server (In-Band) Enabling IPMI LAN Access 16 17 Enabling IPMI LAN Access on a Linux-Based Server (In-Band) 17 Enabling IPMI LAN Access on a Solaris-Based x86 Server (In-Band) Alternate Method for Enabling IPMI LAN Access (Out-of-Band) U
IPMI Linux Kernel Device Driver LAN Interface for the BMC Files 36 37 Viewing the IPMI System Event Log 38 Clearing the IPMI System Event Log 38 IPMI Troubleshooting 3.
Remote Scripting Using SSH 56 Configuring Multiple Systems for Scripting Generating Host Keys 57 Creating Trusted Host Relationships Adding Public Keys 57 58 58 Generating a Host Key Pair 59 Enabling SSH Access Using Trusted Hosts Enabling SSH Access Using Public Keys 59 60 Guidelines for Writing Server Management Command Scripts Command Output 61 Other Tips For Best Results 62 Console Redirection Over Serial on a Linux-based Server 63 grub 64 LILO 65 getty 66 securetty 66 Enabling a
Commands 75 Return Codes B.
Format 89 Return Codes 90 Access Trust Subcommands 91 Access Add Trust Subcommand Format 91 91 Generating Host Keys Return Codes 92 93 Access Delete Trust Subcommand Format 93 Return Codes 94 Access Get Trusts Subcommand Format 93 94 94 Return Codes 95 Access Public Key Subcommands 96 Access Add Public Key Subcommand Format 96 96 Return Codes 97 Access Get Public Key Users Subcommand Format 97 Return Codes 98 Access Delete Public Key Subcommand Format 99 Access User Subcom
Format 101 Return Codes 102 Access Get Users Subcommand Format 103 103 Return Codes 103 Access Update Password Subcommand Format 104 Return Codes 104 Access Update User Subcommand Format 106 Diagnostics Commands 107 Diags Cancel Tests Subcommand Format 109 Diags Get State Subcommand 110 Diags Get Tests Subcommand 111 Diags Run Tests Subcommand 112 112 Return Codes 113 Diags Start Subcommand Format 111 111 Return Codes Format 110 110 Return Codes Format 108 108 Return C
Format 116 Return Codes D. Inventory Commands 116 117 Inventory Compare Versions Subcommand Format 118 Return Codes 119 Inventory Get Hardware Subcommand Format 119 119 Return Codes 120 Inventory Get Software Subcommand Format 121 Inventory Get All Subcommand E.
Return Codes 127 IPMI Enable PEF Subcommand Format 128 128 Return Codes 128 IPMI Get Global Enables Subcommand Format 129 Return Codes 129 IPMI Set Global Enable Subcommand Format 131 IPMI Reset Subcommand 132 132 Return Codes F.
Platform Set OS State Subcommand Format 144 144 Return Codes 145 Platform Set OS State Boot Subcommand Format 145 Return Codes 146 Platform Power State Subcommands 147 Platform Get Power State Subcommand Format 148 Platform Set Power State Subcommand 149 Platform Get Hostname Subcommand 150 Platform Get Product ID Subcommand Sensor Commands 151 153 Sensor Get Subcommand Format 156 Sensor Set Subcommand xii 158 158 Return Codes H.
SP Date Subcommands 162 SP Get Date Subcommand Format 162 162 Return Codes 163 SP Set Date Subcommand Format 163 163 Return Codes 164 SP DNS Subcommands 165 SP Disable DNS Subcommand Return Codes 165 165 SP Enable DNS Subcommand Format 166 Return Codes 166 SP Get DNS Subcommand Format 166 167 167 Return Codes 167 SP Events Subcommands 168 SP Delete Event Subcommand Format 168 Return Codes 169 SP Get Events Subcommand Format 168 169 169 Return Codes 170 SP Hostname Subc
Format 172 Return Codes SP IP Subcommands 173 174 SP Get IP Subcommand Format 174 Return Codes 175 SP Set IP Subcommand Format 174 175 175 Return Codes 176 SP JNET Address Subcommands SP Get JNET Subcommand Format 177 177 Return Codes 178 SP Set JNET Subcommand Format 177 178 178 Return Codes 179 SP Locate Light Subcommands 180 SP Get Locatelight Subcommand Format 180 Return Codes 180 SP Set Locatelight Subcommand Format 181 SP Logfile Subcommands 182 SP Get Logfile Subcom
Format 183 Return Codes 184 SP Miscellaneous Subcommands 185 SP Create Test Events Subcommand Format 185 Return Codes 186 SP Get Port 80 Subcommand Format 186 186 Return Codes 187 BIOS POST Codes 187 Boot Block Codes for Flash ROM SP Load Settings Subcommand Format 194 194 Return Codes 195 SP Get TDULog Subcommand 197 SP Reboot Subcommand 197 197 Return Codes 198 SP Reset Subcommand Format 195 195 Return Codes Format 193 194 SP Get Status Subcommand Format 192 193 Ret
Format 201 Return Codes SP Delete Mount Format 202 203 203 Return Codes 203 SP Get Mount Subcommand Format 204 204 Return Codes 204 SP SMTP Subcommands 205 SP Get SMTP Server Subcommand Format 205 Return Codes 206 SP Set SMTP Server Subcommand Format 205 207 207 Return Codes 207 SP Get SMTP Subscribers Subcommand Format 208 208 Return Codes 209 SP Update SMTP Subscriber Subcommand Format 209 Return Codes 211 SP SNMP Subcommands 212 SP Add SNMP Destination Subcommand Format
SP Get SNMP Destinations Subcommand Format 215 215 Return Codes 215 SP Get SNMP Proxy Community Subcommand Format 216 Return Codes 216 SP Set SNMP Proxy Community Subcommand Format SP SSL Subcommands 217 218 SP Disable SSL-Required Subcommand 218 SP Enable SSL-Required Subcommand 219 SP Get SSL Subcommand 220 220 Return Codes 220 SP Set SSL Subcommand Format 221 221 Return Codes 221 SP Update Subcommands 222 SP Update Flash All Subcommand Format 219 219 Return Codes Format 2
Return Codes 224 SP Update Flash PIC Subcommand Format 225 Return Codes 225 SP Update Diags Subcommand Format 226 226 Return Codes xviii 225 226 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
Preface This guide explains how to manage the Sun Fire™ V20z and Sun Fire V40z servers. How This Book Is Organized Chapter 1 provides an overview of the ways in which a user can manage the servers. See “Introduction” on page 1. Chapter 2 describes how to manage the servers through the Intelligent Platform Management Interface (IPMI). See “IPMI Server Management” on page 27. Chapter 3 describes how to manage the servers through the Simple Network Management Protocol (SNMP).
Appendix E contains detailed descriptions of IPMI commands. See “IPMI Commands” on page 123. Appendix F contains detailed descriptions of Platform commands. See “Platform Commands” on page 133. Appendix G contains detailed descriptions of Sensor commands. See “Sensor Commands” on page 153. Appendix H contains detailed descriptions of service processor (sp) commands. See “Service Processor Commands” on page 161.
Accessing Sun Documentation You can view, print, or purchase a broad selection of Sun documentation, including localized versions, at: http://www.sun.com/documentation Third-Party Web Sites Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products or other materials that are available on or through such sites or resources.
xxii Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
CHAPTER 1 Introduction Overview Strong server-management capabilities are crucial to maintaining mission-critical servers. Advance notification of problems and rapid diagnosis and correction are critical functions to an environment in which a few servers bear the bulk of the workload. The Sun Fire™ V20z and Sun Fire V40z servers and their extensive server-management capabilities lower costs by reducing failure and by potentially eliminating hands-on management.
Acronyms TABLE 1-1 defines the acronyms found in this document.
Server Management There are several options for remotely managing a Sun Fire V20z or Sun Fire V40z server: ■ ■ Lights Out Management (LOM) through IPMItool Simple Network Management Protocol (SNMP) Service Processor The Sun Fire V20z and Sun Fire V40z servers include a dedicated chipset for complete operating-system independence and maximum availability of server-management functions.
Command Line Interface Server-management capabilities are available from the command line. See Appendix B for a list of server-management commands that you can use with these servers, as well as a description, the command format, a list of arguments and a list of return codes for each command. SSH and Scripting Capabilities A system administrator can log in to the Service Processor using SSH and issue commands, or more commonly, write a shell script that remotely invokes these operations.
Sun Control Station IPMItool Third-Party Management MODULES: Health Monitoring, Lights Out Management, Software Management, AllStart and others CLI LOM SNMP-based solutions (HP Open View, CA UniCenter, etc.
Operator Panel You can use the operator panel to configure network settings for the SP. See FIGURE 1-2 or FIGURE 1-3 for the operator panel location on your server. Note – The SP defaults to Dynamic Host Configuration Protocol (DHCP) networking if the operator panel is not interactively engaged on the first power-up.
The operator panel displays information on the LCD display in two lines, and you respond to prompts or initiate actions using the following buttons: TABLE 1-2 Buttons Operator Panel Buttons Function Back/No Select Forward/Yes Enter Cancel If a menu or data-entry screen displays for more than 30 seconds with no action taken, the menu or data entry is cancelled and the display returns to the idle/background state.
User Groups Administrators can define several different user groups, or types, on the server. Capabilities of the different user types are defined in TABLE 1-3. For example, when you log in to the system the first time using the setup account, the first thing you must do is set up the initial manager account so that other user accounts can be managed.
Initial Setup of the Service Processor This procedure describes the steps for the initial setup of the SP. Part I: Assigning Network Settings to the SP This section contains two alternate methods you can use to define SP network settings: ■ ■ “Assigning SP Network Settings Using DHCP” on page 9 “Assigning Static SP Network Settings” on page 11 Note – As an alternative, if no DHCP server or physical access is available, you can configure the SP using IPMItool in conjunction with an IPMI kernel driver.
Back Select Press both for Cancel FIGURE 1-4 Forward Press both for Enter Operator Panel Buttons 2. Press the Forward button until you reach the SP menu: Menu: SP menu 3. Press the Select button to display the SP menu options. SP Menu: Set SP IP info? 4. Press the Select button. The following prompt appears with the default response: SP use DHCP? No 5. Press the Forward button to change to Yes, then press the Select button. 6. Press the Select button at the confirmation prompt.
Assigning Static SP Network Settings Follow these steps to set the SP network settings using a static IP address. You must specify a subnet mask and default gateway. This example uses the following sample settings: IP Address: 192.168.1.2 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.1.254 1. Press any operator panel button on the server front panel (see FIGURE 1-4). The LCD panel displays the first menu option: Menu: Server Menu 2.
Note – The Back and Forward operator panel buttons automatically scroll, repeating the action as long as the button is held down. 8. Repeat Step 6 and Step 7 for each field until the desired IP address is displayed, then use the Enter button combination to save the IP Address. The process continues to the next network setting, the Subnet Mask. The LCD displays as follows: SP netmask: 255.255.255.0 9. Edit the subnet mask setting in the same manner as you did for the IP address.
Part II: Securing the Service Processor After you install the server and configure the SP, you must create the initial manager account to secure and access the server. You can then perform initial configuration of the server and create additional user accounts. Creating the Initial Manager Account A setup account is included with each server. This setup account has no password.
Enabling IPMI Access on the Server This section contains two alternate procedures; one for a Linux-based server and one for a Solaris-based x86 server. Use the procedure that corresponds to your OS: ■ ■ “Enabling IPMI Access on a Linux-Based Server (In-Band)” on page 14 “Enabling IPMI Access on a Solaris-Based x86 Server (In-Band)” on page 16 Enabling IPMI Access on a Linux-Based Server (In-Band) 1. Log in to the server and authenticate as the user root. 2.
b. Install the openIPMI RPM file by running the command: # rpm -ivh openipmi*.rpm Note – The kernel driver will be compiled using the kernel-source code during installation. 5. Install IPMItool. IPMItool is the command-line-interface (CLI) server-management client. ■ If the installed Linux distribution uses the 32-bit “i386” architecture, run the following command: # rpm -ivh ipmitool*.i386.
Enabling IPMI Access on a Solaris-Based x86 Server (In-Band) 1. Log in to the server and authenticate as the user root. 2. Run the following command to install the LIPMI Solaris x86 kernel driver and the IPMItool management control application. These files are located on the Documentation and Support Files CD in the /support/sysmgmt/solaris9 directory. # pkgadd -d ./ Confirm installation of all packages when prompted. 3. Reboot the server.
Enabling IPMI LAN Access This section contains three alternate procedures; two in-band procedures, and one out-of-band procedure. Use the procedure that corresponds to your OS: ■ ■ ■ “Enabling IPMI LAN Access on a Linux-Based Server (In-Band)” on page 17 “Enabling IPMI LAN Access on a Solaris-Based x86 Server (In-Band)” on page 18 “Alternate Method for Enabling IPMI LAN Access (Out-of-Band)” on page 18 Enabling IPMI LAN Access on a Linux-Based Server (In-Band) 1.
Enabling IPMI LAN Access on a Solaris-Based x86 Server (In-Band) 1. If the server is powered off, boot the local OS. 2. Log in to the server and authenticate as the user root. 3. Using IPMItool, configure the network setting for the SP by using the following commands. Note – For more information on the syntax for IPMItool commands, refer to “Syntax” on page 30.
Upgrading the Linux Kernel Upgrading the installed Linux kernel to a newer version requires you to recompile the upgraded IPMI kernel device driver. 1. Install the kernel-source RPM that matches the version of the upgraded kernel binary RPM package. 2. Log in to the server and authenticate as the user root. 3. Change to the following directory: # cd /usr/src/kernel-modules/openipmi 4. Recompile the module by running the following commands: # make clean # make # make install 5.
Daisy-Chaining the Servers You can interconnect multiple servers in a daisy chain configuration by using the SP connectors to form a management LAN as shown in FIGURE 1-5. This figure also shows how the servers are connected to external LANs using the platform gigabit connectors.
Site Integration When deploying your server, ensure that you determine the best integration strategy for your environment. These servers include network connections for the service processor (SP) that are separate from network connections for the platform. This allows you to configure the server so that the SP is connected to an isolated, management network and is not accessible from the production network.
2. Press the Forward button until you reach the SP menu. Menu: SP menu 3. Press Select or Enter to display the SP menu’s options. SP Menu: Set SP IP info? 4. Press the Forward button until you reach the Update SP Flash menu option. SP Menu: Update SP Flash? 5. Press Select or Enter. 6. A string of 0s displays with the cursor at the left digit. Use the Forward and Back buttons to increment or decrement a digit. Note – You are prompted for an IP address.
Updating the Service Processor Base Component To update the SP base component: 1. Start the spupdate server on a machine with a Java Runtime Environment (JRE) by running the following command: # java -jar spupdate.jar -f filename [ -p port ] The spupdate.jar file is located in the spupdate folder of the Network Share Volume (NSV). In this command, filename is an SP .image file located in sw_images/sp/spbase/version. This sw_images directory contains an SP base .image file for each version available.
Autoconfiguring the SP (Optional Method) Autoconfiguration replicates the majority of configuration files from an SP that has already been configured to another SP, so that the two servers have identical configurations, except for the host name and IP address. For example, after you configure a single SP (set up users, hosts, certificates, mounts and so on), you then run autoconfiguration on each additional SP so that the settings are identical.
■ If the SP does not locate an IP address, the following message appears: Unable to get SP IP address In this case, you must manually enter an IP address before you press the Select operator panel button to start autoconfiguration. 3. Wait until the autoconfiguration is complete, at which point the SP automatically reboots. The following message displays when autoconfiguration is running. SP AutoConfigure in progress Note – If the autoconfiguration is unsuccessful, a failure message displays.
26 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
CHAPTER 2 IPMI Server Management Server manufacturers today have to re-invent how each new server manages itself. The hardware and software design for one server does not necessarily work with another. Every server supplier provides basic monitoring and data collection functions but no two do it exactly the same. These proprietary implementations for manageability only complicate the problem.
Baseboard Management Controller In order to perform autonomous platform-management functions, the processor runs embedded software or firmware. Together, the processor and its controlling firmware are referred to as the Baseboard Management Controller (BMC), which is the core of the IPMI structure. Tightly integrating an IPMI BMC and management software with platform firmware facilitates a total management solution.
IPMI Compliance and LAN Channel Access The server supports IPMI through the SP software version 2.0 and later. These servers meet compliance standards for IPMI version 1.5. The IPMI implementation on these servers also support LAN channel access. (Refer to the IPMI specification version 1.5 for details.) The LAN channel access is disabled by default. To enable it, use the ipmi enable channel command and specify the ID of the channel to enable for the LAN Interface, as follows.
Lights Out Management (LOM) On these servers, Lights Out Management is performed through IPMItool, a utility for controlling IPMI-enabled devices. Description IPMItool is a simple command-line interface (CLI) to servers that support the Intelligent Platform Management Interface (IPMI) v1.5 specification.
Options TABLE 2-1 lists the options available for IPMItool. TABLE 2-1 Options for IPMItool Option Description -h Provides help on basic usage from the command line. -c Makes the output suitable for parsing, where possible, by separating fields with commas instead of spaces. -g Attempts to make IPMI-over-LAN communications more robust. -V Displays the version information. -v Increases the amount of text output. This option may be specified more than once to increase the level of debug output.
Expressions TABLE 2-2 lists the expressions and parameters available for IPMItool. Note – For each of these expressions, the beginning command is always ipmitool, followed by the expression and parameter(s). Note – The sol command is not supported in these servers, but you can enable a Serial-over-LAN feature. See “Serial Over LAN” on page 70.
TABLE 2-2 Expression chaninfo Expressions and Parameters for IPMItool (2 of 4) Parameter Sub-parameter channel Description and examples Displays information about the selected channel. If no channel is specified, the command displays information about the channel currently being used.
TABLE 2-2 Expression Expressions and Parameters for IPMItool (3 of 4) Parameter Sub-parameter power lan Performs a chassis control command to view and change the power state. status Shows the current status of the chassis power. on Powers on the chassis. off Powers off chassis into the soft off state (S4/S5 state). NOTE: This command does not initiate a clean shutdown of the operating system prior to powering off the server. cycle Provides a power-off interval of at least 1 second.
TABLE 2-2 Expression Expressions and Parameters for IPMItool (4 of 4) Parameter Sub-parameter Description and examples arp respond [on|off] Sets the BMC-generated ARP responses. arp generate [on|off] Sets the BMC-generated gratuitous ARPs. arp interval [seconds] s Sets the interval for the BMC-generated gratuitous ARPs. auth level,... type,... This command sets the valid authtypes for a given auth level.
IPMI Linux Kernel Device Driver The IPMItool application utilizes a modified MontaVista OpenIPMI kernel device driver found on the Sun Fire V20z and Sun Fire V40z Servers Documentation and Support Files CD. The driver has been modified to use an alternate base hardware address and modified device IO registration. This driver must be compiled and installed from the Documentation and Support Files CD. The following kernel modules must be loaded in order for IPMItool to work: 1.
Remote Management Control Protocol is a request-response protocol delivered using UDP datagrams to port 623. IPMI-over-LAN uses version 1 of the RMCP to support management both before installing the OS on the server, or if the server will not have an OS installed. The LAN interface is an authenticated, multi-session connection; messages delivered to the BMC can (and should) be authenticated with a challenge/response protocol with either a straight password/key or an MD5 message-digest algorithm.
Viewing the IPMI System Event Log To view the System Event Log (SEL), use IPMItool.
IPMI Troubleshooting TABLE 2-3 describes some potential issues with IPMI and provides solutions. TABLE 2-3 IPMI Troubleshooting Issue Solution You cannot connect to the management controller using IPMItool over LAN. Verify the network connection to the management controller and its IP address and verify the channel is enabled using the ipmi get channels command. You cannot authenticate to the management controller using IPMItool over LAN.
40 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
CHAPTER 3 SNMP Server Management You can manage your server using the Simple Network Management Protocol (SNMP). Simple Network Management Protocol Simple Network Management Protocol (SNMP) is a network-management protocol used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices, and to manage configurations, statistics collection, performance and security on a network. SNMP-based management allows for third-party solutions to be used.
SNMP Integration SNMP is an open network-management technology that enables the management of networks and entities connected to the network. Within the SNMP architecture is a collection of network-management stations and managed nodes. Network-management stations execute management applications, which monitor and control managed nodes.
Sun Fire V20z and Sun Fire V40z Servers MIB Tree FIGURE 3-1 illustrates the MIB tree: FIGURE 3-1 MIB Tree Integrating MIBs with Third-Party Consoles You use the server’s MIBs to integrate the management and monitoring of the server into SNMP management consoles. The MIB branch is a private enterprise MIB, located at object identifier (OID) 1.3.6.1.2.1.9237. The standard SNMP port 161 is used by the SNMP agent on the SP.
Configuring SNMP on Your Server Note – There are several services that are supplied by the SNMP agent on the server. Depending on your business needs and the configuration of your current office network and management environment, you might want to take advantage of these services.
SNMP Agent on the Service Processor The SNMP agent running on the SP facilitates the management and monitoring of the server. The SNMP agent can be used to query various types of SP information. Refer to FIGURE 3-1 for a list of the MIBs; refer to TABLE 3-3 for a detailed description of the MIBs. There is no configuration required to use this functionality other than integrating the server MIBs with your desired management station.
Setting the Community Name The SNMP agent on the SP acts as a proxy for the SNMP agent running on the platform. (Refer to “Configuring SNMP on Your Server” on page 44.) To properly proxy, you must use the community string. The community string needed to do so is the value defined when you configured the platform for SNMP. If you find that your SNMP queries are not being proxied to the platform SNMP agents, validate that the community string on the SP matches that on the platform.
Using a Third-Party MIB Browser The following example demonstrates integrating the server MIBs into an SNMP node manager. 1. From the Manager Preferences menu, choose Load/Unload MIBS: SNMP. 2. Locate and select the SP-MasterAgent-MIB.mib. 3. Click Load. 4. Specify the directory in which the server MIBs are placed and click Open. 5. Repeat steps 2 through 4 to load other MIBS (for example, SP-SST-MIB.mib, SP-INVENTORY-MIB.mib, SP-EVENT-MIB.mib, SP-PLATFORM-MIB.mib, SP-GROUP-MIB.mib and so on). 6.
SNMP Traps SNMP traps are network-management notifications of an event occurring at a managed network node. These events can identify problems in the network, machines up or down, and so on. These servers use traps to signal conditions related to the server’s health, including critical conditions related to physical components, the return to a normal state for these components, and other situations related to the state of the software running on the SP (for example, network settings being reconfigured).
Configuring SNMP Trap Destinations Although SNMP traps are generated for events that occur on the SP, you must configure where these traps are to be sent. There is no default destination for traps. You can use the server-management subcommands (see TABLE 3-2) on the SP to configure SNMP destinations. For more information on these subcommands, refer to Appendix B.
Server MIB Details SNMP uses object identifiers (OIDs) to provide name variables by which objects are grouped together for easier reference. These servers provide agents for the MIBs shown in TABLE 3-3: TABLE 3-3 50 SNMP MIBs MIB OID Description SP-MasterAgent-MIB .mib .1.3.6.1.4.1.9237 Creates the main trunk of the server MIB tree. All other MIBs of the SP branch from this tree. To be loaded first while integrating with any third-party framework. SP-INVENTORY-MIB .mib .1.3.6.1.4.1.9237.2.1. 1.1 .
The events listed in TABLE 3-4 are sent to the SNMP destination by SP-EVENT-MIB.mib.
TABLE 3-4 52 SP Events (2 of 2) Enterprise Trap ID Event 29 spVoltageEventWarning 30 spVoltageEventCritical 31 spFanEventInformational 32 spFanEventWarning 33 spFanEventCritical 37 spPlatformStateChangeEventInformational 38 spPlatformStateChangeEventWarning 39 spPlatformStateChangeEventCritical 40 spPlatformBIOSEventInformational 41 spPlatformBIOSEventWarning 42 spPlatformBIOSEventCritical Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
SNMP Troubleshooting TABLE 3-5 describes a potential issue with SNMP and provides a solution. TABLE 3-5 SNMP Troubleshooting Issue Solution SNMP queries to the SP time out. The platform OS requires both the NPS driver suite RPM and an active SNMP daemon sharing the SP’s community string.
54 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
CHAPTER 4 Further Management Information Configuring Scripting Capabilities A system administrator can log in to the Service Processor (SP) using secure shell (SSH) and issue commands, or more commonly, write a shell script that remotely invokes these operations. Note – You must create a valid initial manager account before using SSH. The SP includes a setup account that can be used to set up an initial manager account. This initial manager user can create additional users.
Using Shell Scripts An administrator can make configuration changes for a single SP by using SSH to log in and run commands. For a multi-system environment in which configurations for all SPs must be synchronized, you can automate configuration changes. As a Unix/Linux administrator, you can use SSH, trusted host relationships or public key authentication, and Unix/Linux shell scripting to automate tasks that need to be performed on multiple SPs. 1. Set up your system for scripting.
If using trusted host relationships for passwordless access, the SP must have a local user of the same name as the remote user (or the remote user should be a member of a directory service group that is mapped to a local SP administrative group). You can also add your public key file instead of creating a trusted host relationship to be authenticated via SSH. Refer to “Adding Public Keys” on page 58. When configured for passwordless access, the ssh daemon on the SP allows the remote user access to sp.
Note – Use scp to copy the files to either /tmp or to your home directory. The sp commands will then install the file specified on the command line. Creating Trusted Host Relationships Adding a trusted host relationship is one way to allow for passwordless access and thus is a means for one-to-many scripting.
# access add public key -l PUBLIC_KEY_FILE [-u user] The public key file is your RSA or DSA key. Up to 10 users can install public keys; only one key per user is allowed. Admin-level users can only add their own public key. Manager-level users can add a public key for any local user. If the user is not specified in the command, the current user is the default. Note – The maximum supported key length is 4096 bits.
b. Authenticate yourself for the scp command by entering the password for your manager-level user. c. Add the client key to the set of trusted hosts for this SP. # ssh sp.test.com access add trust -c client.test.com -k \ /tmp/ssh_host_dsa_key.pub d. Authenticate yourself for the ssh command. From this point, any user with the same login on both sp.test.com and client.test.com has access without requiring a password to the like-named account on sp.test.com. 4.
Guidelines for Writing Server Management Command Scripts This section describes some basic guidelines for managing your systems by writing scripts for remote execution on one or more SPs. ■ Shell Scripts: You should be familiar with standard shell scripting. Refer to “Using Shell Scripts” on page 56. ■ SSH: You must currently use an SSH (Secure Shell) client to execute automated command scripts. Refer to “Remote Scripting Using SSH” on page 56.
■ Data for each column is left-aligned with at least one space between columns. Numeric data might be right-aligned. ■ The -D argument allows you to specify a delimiter character when scripting. This is very useful in parsing fields with white space. ■ If all lines have the same number and type of data values, each row is printed to a separate line so variable data can be parsed easily. For example, executing access get users -g monitor returns a list of monitor users each on a separate line.
Console Redirection Over Serial on a Linux-based Server Caution – Redirecting the console over serial is a procedure intended for advanced users of Linux only. You can seriously disrupt the proper functioning of the server or render the server unbootable if you introduce a problem in the configuration files. Note – Instructions for console redirection on a Solaris-based server are not yet available.
grub If you use grub, there are three steps to enable console redirection over serial; these steps all involve editing the grub configuration file: ■ ■ If you are using Red Hat Linux, the grub file is /etc/grub.conf. If you are using SUSE Linux, the grub file is /boot/grub/menu.1st. Note – On Red Hat Linux systems, the file /etc/grub.conf might be a symbolic link to the file /boot/grub/grub.conf. 1. Pass the proper console parameters to the kernel. 2.
A working-image section in your grub configuration file should have an entry for the kernel image to boot. The stock kernel entry looks like: kernel /vmlinuz-kernel_revision ro root=/dev/sda5 where kernel_revision is simply the kernel version that you are using. 1.
getty You can run a service called getty to enable login on the serial interface. To enable getty, append the following line to the list of gettys in the /etc/inittab file: 7:12345:respawn:/sbin/agetty 9600 ttyS0 Note – It does not matter where you append this line in the list. Note – Make certain that the first number is unique within the inittab file.
Enabling and Configuring BIOS Console Redirection Note – Console redirection is enabled by default in the BIOS. If the default settings have been changed in the BIOS, the following procedure explains how to change the console-redirection settings. 1. Boot or reboot the server. 2. When prompted, press to enter BIOS setup. 3. Select the Advanced menu from the category selections along the top. 4. Select Console Redirection.
Network Share Volume (NSV) CD-ROM A network share volume (NSV) structure is included with the server on the Sun Fire V20z and Sun Fire V40z Servers Network Share Volume CD. Although the SP functions normally without access to an external file system, a file system is required to enable several features, including event log files, software updates, diagnostics, and the troubleshooting dump utility. You can configure the NSV to be shared among multiple SPs.
When extracted, the compressed packages in TABLE 4-1 populate the following files on the NSV: /mnt/nsv/ diags logs scripts snmp spupdate sw_images (this folder appears after you extract one of the OS-specific Zip files) TABLE 4-2 Extracted Files on the Network Share Volume File Name Description diags Offline location of the server diagnostics. logs Offline location of the log files for the SP. scripts Sample scripts that can be used for scripting commands. snmp SNMP MIBS.
Serial Over LAN The Serial Over LAN (SOL) feature lets servers transparently redirect the serial character stream from the baseboard Universal Asynchronous Receiver/Transmitter (UART) to and from the remote-client system over LAN. Serial over LAN has the following benefits compared to a serial interface: ■ ■ ■ Eliminates the need for a serial concentrator. Reduces the amount of cabling. Allows remote management of servers without video, mouse, or keyboard (headless servers).
Note – Ensure that the baud rate value passed to the -S argument matches the speed that was specified for the serial redirection feature of the BIOS and the speed used for your boot loader and OS configuration.
72 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
APPENDIX A Server Management Commands Summary The service processor (SP) includes a suite of commands that enables management and monitoring of the server; this suite of commands is referred to as the server management commands. Note – This appendix provides an overview of the server management command types that are available on the SP. For a detailed description of the subcommands, arguments and return codes for each command type, refer to the appendixes in this guide, as described in TABLE A-1.
Using the ssh Protocol You must use ssh to execute these commands on the service processor (SP). There are two ways to do this: ■ Use the interactive shell on the SP. ■ Preface each command with a set piece of text.
Commands The server management commands take arguments, perform one or more actions, and display the result or text to the standard output device. Commands are grouped by similar function; each command has numerous subcommands supporting functions within that grouping. Note – Every command (except help) returns a return code upon completion. See “Return Codes” on page 76 for a summary.
TABLE A-1 Server Management Commands Command Description sensor Reports or sets the value of an environmental sensor or control. See Appendix G, “Sensor Commands.” sp Allows the authorized user to manage and monitor the SP configurations, such as networking, external file system, SNMP, SMTP, SSL, event logs and so on. See Appendix H, “Service Processor Commands.” help Returns the following text: Available Commands: platform, access, sp, sensor, inventory, ipmi.
TABLE A-2 Return Codes (2 of 2) Return Code ID Description NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_MissingArgument 7 Missing argument(s). NWSE_NoMemory 8 Insufficient memory. NWSE_Busy 9 Device or resource is busy. NWSE_NotImplemented 10 Function not implemented. NWSE_RPCConnected 11 RPC client already connected. NWSE_RPCConnRefused 12 RPC connection refused. NWSE_NoRouteToHost 13 No route to host (network down). NWSE_HostDown 14 Host is down.
78 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
APPENDIX B Access Commands The access command validates a user’s authority or controls authorization services. Using the access command, you can retrieve information about user groups, add a user to or delete a user from a group, and specify a mapping between site-defined administrative groups and the administrative groups that are used to authorize actions on the Service Processor. TABLE B-1 lists the groups of access subcommands.
Access Groups Subcommands The subcommands in TABLE B-2 return the authorization group for a specific user or a list of defined groups. TABLE B-2 Access Group Subcommands Subcommand Description access get group Returns the authorization group for the specified user. access get groups Returns a list of the groups defined, including the standard groups. Access Get Group Subcommand Description: Returns the authorization group for the specified user.
Access Get Groups Subcommand Description: Returns a list of the groups defined, including the standard groups. Format Command format: access get groups Return Codes TABLE B-4 lists the return codes for this subcommand. TABLE B-4 Return Codes for Subcommand access get groups Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified.
Access Map Subcommands The subcommands in TABLE B-5 manage mappings between existing site-specified groups and one of the standard administrative groups. TABLE B-5 Access Map Subcommands Subcommand Description access get map Returns the names of all the site-specified groups mapped to a specific administrative group. access map Maps an existing site-specified group name (the directory-service group) to one of the standard administrative groups.
Return Codes TABLE B-7 lists the return codes for this subcommand. TABLE B-7 Return Codes for Subcommand access get map Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Return Codes TABLE B-9 lists the return codes for this subcommand. TABLE B-9 Return Codes for Subcommand access map Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Return Codes TABLE B-11 lists the return codes for this subcommand. TABLE B-11 Return Codes for Subcommand access unmap Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Access Directory Services Subcommands Services defines a directory-services mechanism that determines the group memberships for a user. Remote users gain access to the Service Processor features only through these group mappings that relate a directory-services group to a local Service-Processor administrative group.
Return Codes TABLE B-14 lists the return codes for this subcommand. TABLE B-14 Return Codes for Subcommand access disable service Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
TABLE B-15 lists the arguments for this subcommand. TABLE B-15 Arguments for Subcommand access enable service Argument Description {-d | --domain} Specifies the domain name. {-s | --server} Specifies the server. {-k | --keytab} For ADS only: Specifies the ADS keytab file name. {-o | --ou} For ADS only: Specifies the organizational unit under which the name-service library looks for group data. {-l | --logon} For ADS only: Specifies the logon ID for the active directory account.
TABLE B-16 Return Codes for Subcommand access enable service Return Code ID Description NWSE_RPCNotConnected 3 Unable to connect to the RPC server. NWSE_InvalidArgument 4 One or more arguments were incorrect or invalid. NWSE_NotFound 5 Entity (user, service, file, path, etc.) was not found. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_FileError 18 File open, file missing, or a read or write error occurred.
TABLE B-17 Arguments for Subcommand access get services Argument Description {-l | --ID} For ADS only: Returns the ADS logon ID. Only one of the parameters -o and -l are permitted at a time. {-o | --ou} For ADS only: Returns the organization unit information. Only one of the parameters -o and -l are permitted at a time. [-H | --noheader] Suppresses header output. {-D | --delim } Delimits columns with the specified delimiter. Headings are also delimited unless suppressed.
Access Trust Subcommands Adding host-based trusts provides many-to-one scripting solutions. Once a host equivalence relationship has been created with a client, users on that client can remotely execute commands on the SP without being prompted for a password. TABLE B-19 lists the commands related to trusted host relationships. TABLE B-19 Access Trust Subcommands Subcommand Description access add trust Creates a host-based trust relationship for the specified host.
If the login is authorized through a mapping of a directory-service group, the ssh command is executed as the proxy user on the SP, either rmonitor, radmin or rmanager. Support is available for SSH protocol version 2 key types (RSA or DSA) only. If DNS is enabled on the SP, the client machine must be specified with its DNS name, (and not the IP address). Generating Host Keys The host’s ssh install should generate the host keys. If it does not, follow these steps to manually generate the key pair: 1.
Return Codes TABLE B-21 lists the return codes for this subcommand. TABLE B-21 Return Codes for Subcommand access add trust Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Return Codes TABLE B-23 lists the return codes for this subcommand. TABLE B-23 Return Codes for Subcommand access delete trust Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Return Codes TABLE B-24 lists the return codes for this subcommand. TABLE B-24 Return Codes for Subcommand access get trusts Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Access Public Key Subcommands The subcommands listed in TABLE B-25 allow you to manage public keys and public-key users. TABLE B-25 Access Public Key Subcommands Subcommand Description access add public key Installs a public key for SSH authentication. access get public key users Determines which users have public keys installed. access delete public key Removes a user’s public key.
Return Codes TABLE B-27 lists the return codes for this subcommand. TABLE B-27 Return Codes for Subcommand access add public key Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Return Codes TABLE B-28 lists the return codes for this subcommand. TABLE B-28 Return Codes for Subcommand access get public key users Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Return Codes TABLE B-30 lists the return codes for this subcommand. TABLE B-30 Return Codes for Subcommand access delete public key Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Access User Subcommands The subcommands listed in TABLE B-31 allow you to manage a single user or group of users. TABLE B-31 Access User Subcommands Subcommand Description access add user Adds the specified local user to the specified group. access delete user Deletes the specified user. access get users Retrieves all the users in an administrative group or all users in all groups. access update password Updates the password of the specified user.
Return Codes TABLE B-33 lists the return codes for this subcommand. TABLE B-33 Return Codes for Subcommand access add user Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
TABLE B-34 lists the arguments for this subcommand. TABLE B-34 Arguments for Subcommand access delete user Argument Description USERNAME Specifies the name of the user to remove. This argument is repeatable to remove multiple users at one time. [-a | --all] Removes all user accounts. The manager-level user executing the command is not removed. [-q | --quiet] If the user to delete is not found, this argument specifies that no error be returned.
Access Get Users Subcommand Description: Retrieves all the local users in an administrative group. Format Command format: access get users {-g | --group} [{-H | noheader}][{-D | --delim }] TABLE B-36 lists the arguments for this subcommand. TABLE B-36 Arguments for Subcommand access get users Argument Description {-g | --group} Specifies that group from which to retrieve all users. { -H | --noheader } Specifies that column headings should be suppressed.
Access Update Password Subcommand Note – This command is for managers to change other users’ passwords; all users can change their own passwords. Description: Changes the password of an existing user. Format Command format: access update password {-p | --password} PASSWORD {u | --user} USER TABLE B-38 lists the arguments for this subcommand. TABLE B-38 Arguments for Subcommand access update password Argument Description {-u | --user} The name of the user whose password you wish to update.
TABLE B-39 Return Codes for Subcommand access update password Return Code ID Description NWSE_InvalidArgument 4 One or more arguments were incorrect or invalid. NWSE_NotFound 5 Entity (user, service, file, path or other) was not found. NWSE_NoPermission 6 Not authorized to perform this operation. Access Update User Subcommand Description: Updates the login information (password or group) for the user.
Return Codes TABLE B-40 lists the return codes for this subcommand. TABLE B-41 106 Return Codes for Subcommand access update user Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
APPENDIX C Diagnostics Commands The diags commands allow you to manage the diagnostics tests. TABLE C-1 lists the groups of diags subcommands. Note – The diagnostics commands are also provided in the Sun Fire V20z Server User Guide, 817-5248. TABLE C-1 Diagnostics Subcommand Groups Subcommand Description diags cancel tests Cancels one or more diagnostic tests, resulting in the deletion of the results data. diags get state Returns the state of the platform-diagnostics control server.
Diags Cancel Tests Subcommand Description: Cancels one or more diagnostic tests, resulting in the deletion of results data. Format Command format: diags cancel tests [[{ -t | --test} TEST HANDLE] [{-a|--all}] [{-H | --noheader}]] TABLE C-2 lists the arguments for this subcommand. Note – Specifying no arguments cancels all tests for each device in the server. TABLE C-2 108 Arguments for Subcommand diags cancel tests Arguments Description { -t | --test} Specifies the test to cancel.
Return Codes TABLE C-3 lists the return codes for this subcommand. TABLE C-3 Return Codes for Subcommand diags cancel tests Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Diags Get State Subcommand Description: Returns the state of the platform-diagnostics control server. Format Command format: diags get state If the result returned from the command is that the platform is up and ready for diagnostics, then you can submit platform diagnostic tests for execution. Success Text message – The Platform Diagnostics are up and are available to receive test requests. Error Text Message – The Platform Diagnostics are not up.
Diags Get Tests Subcommand Description: Returns data describing the diagnostic tests that are available. This data includes the specific test name and the module to which the test applies. Format Command format: diags get tests [{ -a | --all}] [{-H | --noheader}]] [{-D | --delim }] TABLE C-5 lists the arguments for this subcommand. TABLE C-5 Arguments for Subcommand diags get tests Arguments Description {-a | --all} Specifies to return information for all tests in the server.
TABLE C-6 Return Codes for Subcommand diags get tests Return Code ID Description NWSE_InvalidArgument 4 One or more arguments were incorrect or invalid. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_MissingArgument 7 Missing argument(s). Diags Run Tests Subcommand Description: Submits one or more diagnostic tests for execution.
■ ■ Test Result (for example: Passed, Failed) Details. If you specify the -v option, the Test Details are displayed, indicating detailed information about the test, such as high, low and nominal values, actual values, and so on. Upon failure, the Failure Details are displayed with a text message indicating the cause of failure. Return Codes TABLE C-8 lists the return codes for this subcommand.
Diags Start Subcommand Description: Starts the SP and platform-diagnostics framework. You must execute this command before running any tests. After running this command, you can immediately run Service Processor tests or wait for the subcommand diags get state to return the result platform diags available, at which point you can run platform tests. The platform state must be either off or OS Communicating. Refer to the subcommand platform get os state for details about these states.
TABLE C-9 Return Codes for Subcommand diags start Return Code ID Description NWSE_InvalidArgument 4 One or more arguments were incorrect or invalid. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_InvalidOpForState 22 Invalid operation for current state.
Diags Terminate Subcommand Description: Terminates all diagnostics tests and the diagnostics session. Format Command format: diags terminate Return Codes TABLE C-10 lists the return codes for this subcommand. TABLE C-10 116 Return Codes for Subcommand diags terminate Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified.
APPENDIX D Inventory Commands The inventory command reports on the inventory of hardware and software for a Sun Fire V20z server. TABLE D-1 lists the groups of inventory subcommands that you can use to retrieve specific information about hardware or software. TABLE D-1 Inventory Subcommands Groups Subcommand Description inventory compare versions Returns a list of all installed software packages and the version differences with those listed in a release manifest.
Inventory Compare Versions Subcommand Description: Returns a list of all installed software packages and the version differences with those listed in a release manifest. You can use this command to verify that your installation is consistent with a supported release and to determine the packages that have been updated in a new release. Format Command format: inventory compare versions {-f | -–file} RELEASE_MANIFEST_FILE {-v | -–verbose} TABLE D-2 lists the arguments for this subcommand.
Return Codes TABLE D-3 lists the return codes for this subcommand. TABLE D-3 Return Codes for Subcommand inventory compare versions Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
To obtain the board revision, product ID and PRS revision, you can run the following commands: inventory get hardware -D '|' | awk -F '|' '/PRS/{print $8}' inventory get hardware -D '|' | awk -F '|' '/PRS/{print $7}' | awk '{print $4}' inventory get hardware -D '|' | awk -F '|' '/PRS/{print $6}' You can also obtain this information by running the sensor get command. Return Codes TABLE D-5 lists the return codes for this subcommand.
Inventory Get Software Subcommand Description: Returns the inventory information for all installed or uninstalled software (located on the optional external file system). Format Command format: inventory get software [{-a | --all}][{-H | --noheader}] [{-D | --delim }] TABLE D-6 lists the arguments for this subcommand.
Inventory Get All Subcommand Description: Returns detailed information for all field-replaceable hardware components and all installed or uninstalled software. Format Command format: inventory get all {-a | --all} {-v | --verbose} [{-H | --noheader}] [{-D | --delim }] TABLE D-8 lists the arguments for this subcommand.
APPENDIX E IPMI Commands The ipmi command manages the Intelligent Platform Management Interface (IPMI) functions. TABLE E-1 lists the groups of ipmi subcommands. TABLE E-1 IPMI Subommands Groups Subcommand Description ipmi disable channel Disables one of two IPMI channels. ipmi enable channel Enables one of two IPMI channels. ipmi get channels Displays the list of IPMI channels and whether they are enabled or disabled. ipmi enable pef Enables platform-event filtering.
IPMI Disable Channel Subcommand Description: Allows you to disable one of two IPMI channels. Format Command format: ipmi disable channel {sms | lan} TABLE E-2 lists the arguments for this subcommand. TABLE E-2 Arguments for Subcommand ipmi disable channel Arguments Description sms The ID of the channel to disable for the System Interface; not case-sensitive. lan The ID of the channel to disable for the LAN Interface; not case-sensitive.
IPMI Enable Channel Subcommand Description: Allows you to enable one of two IPMI channels. Format Command format: ipmi enable channel {sms | lan} TABLE E-4 lists the arguments for this subcommand. TABLE E-4 Arguments for Subcommand ipmi enable channel Arguments Description sms The ID of the channel to enable for the System Interface; not case-sensitive. lan The ID of the channel to enable for the LAN Interface; not case-sensitive.
IPMI Get Channels Subcommand Description: Displays the list of IPMI channels and whether they are enabled or disabled. Format Command format: ipmi get channels Return Codes TABLE E-6 lists the return codes for this subcommand. TABLE E-6 126 Return Codes for Subcommand ipmi get channels Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified.
IPMI Disable PEF Subcommand Description: Allows you to disable platform-event filtering (PEF). Format Command format: ipmi disable pef Return Codes TABLE E-7 lists the return codes for this subcommand. TABLE E-7 Return Codes for Subcommand ipmi disable pef Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_NoPermission 6 Not authorized to perform this operation.
IPMI Enable PEF Subcommand Description: Allows you to enable platform-event filtering (PEF). Format Command format: ipmi enable pef Return Codes TABLE E-8 lists the return codes for this subcommand. TABLE E-8 128 Return Codes for Subcommand ipmi enable pef Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_NoPermission 6 Not authorized to perform this operation.
IPMI Get Global Enables Subcommand Description: Displays the list of IPMI global enables and their current value. Format Command format: ipmi get global enables Return Codes TABLE E-9 lists the return codes for this subcommand. TABLE E-9 Return Codes for Subcommand ipmi get global enables Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified.
IPMI Set Global Enable Subcommand Description: Allows you to set the value of several IPMI global-enable variables. Format Command format: ipmi set global enable {-n |--name} GLOBAL_NAME {{-e|--enabled} | {-d|--disabled}} TABLE E-10 lists the arguments for this subcommand. TABLE E-11 provides information about the aliases. TABLE E-10 Arguments Description {-n |--name} The name of one of the IPMI global enable variables; see TABLE E-11.
TABLE E-11 Information about the aliases Alias Name String Values msg_buf Enable Event Message Buffer Enabled/ Disabled msg_buf_interrupt Enable the Event Message Buffer Full Enabled/ Disabled msg_queue_interrupt Enable Receive Message Queue Interrupt Enabled/ Disabled Default Enabled Return Codes TABLE E-12 lists the return codes for this subcommand. TABLE E-12 Return Codes for Subcommand ipmi set global enable Return Code ID Description NWSE_Success 0 Command successfully completed.
IPMI Reset Subcommand Description: Resets IPMI information back to default factory settings. Format Command format: ipmi reset {-s | –-sdrr} {-c | –-config} {-p | –-password} {-a | –-all} TABLE E-13 lists the arguments for this subcommand. TABLE E-13 Arguments for Subcommand ipmi reset Arguments Description {-s | –-sdrr} Copies the original database file to pstore. {-c | –-config} Deletes the configuration file and global enables. {-p | –-password} Deletes the password file.
APPENDIX F Platform Commands The platform command reports or changes some aspect of the state of the platform. TABLE F-1 lists the groups of platform subcommands. TABLE F-1 Platform Subcommand Groups Subcommand Group Description platform console Manages access to the platform serial console. platform os state Manages the current state of the operating system (OS). platform power state Manages the state of the platform power.
Platform Console Subcommands The subcommands listed in TABLE F-2 allow you to manage access to the platform serial console. TABLE F-2 Platform Console Subcommands Subcommand Description platform console Provides access to the platform serial console. platform get console Retrieves the configuration of the Service Processor (SP) access to the platform serial console. platform set console Configures the SP access to the platform serial console.
TABLE F-3 lists common COM1 values. TABLE F-4 lists common values for console redirection. TABLE F-3 Common COM1 Values I/O Device Configuration Serial port A Enabled Base I/O address 3F8 Interrupt IRQ 4 TABLE F-4 Common Values for Console Redirection Console Redirection Com Port Address On-board COM A Console connection Direct Baud Rate 19.
TABLE F-5 Serial-Console Values Character Function f Forces an attach read/write. g Groups information. i Information dump. L Toggles logging on/off. l? Breaks the sequence list. l0 Sends a break per configuration file. l1-9 Sends a specific break sequence. o Re-opens the tty and log file. p Replays the last 60 lines. r Replays the last 20 lines. s Spy read only. u Shows the host status. v Shows the version information. w Shows who is logged on to this console.
Example The following example lists the steps you would perform to enable and run the platform console: 1. Check or set the BIOS settings. 2. Run the command: platform set console -s sp -S 19200 -e 3. Run the command: platform set console Return Codes TABLE F-6 lists the return codes for this subcommand. TABLE F-6 Return Codes for Subcommand platform console Return Code ID Description NWSE_Success 0 Command successfully completed.
Platform Get Console Subcommand Description: Retrieves the configuration information regarding the Service Processor (SP) access to the platform serial console. Format Command format: platform get console [{-H|--noheader}] [{-D | --delim }] TABLE F-7 lists the arguments for this subcommand. TABLE F-7 Arguments for Subcommand platform get console Arguments Description {-H |--noheader} Suppresses column headers. { -D | --delim } Delimits columns with the specified delimiter.
TABLE F-8 Supplementary Output Column Description Speed Indicates the communications speed of the link. Prune Indicates whether ANSI escape code and duplicate information pruning is enabled. Log Trigger Indicates the approximate size at which log rotation occurs (for example, when the file console.0 is removed, the current log is moved to console.0 and a new log file is opened). Pruning of log-file contents happens only when rotation occurs.
Platform Set Console Description: Enables the configuration of SP access to the platform serial console, sets the speed of the connection and limits the size of the log files created. Format Command format: platform set console {--serial|-s} platform This option configures the external serial port so that it is connected to the platform serial console. This is the default setting.
TABLE F-10 Arguments for Subcommand platform set console Arguments Description {-n | --noprune} Indicates that the platform console log should be the raw console data. Cannot be used with: -p. {-p | --prune} Indicates that the platform console log is to be cleaned of ANSI sequences and pruned of duplicated information. Cannot be used with: -n. {-s | --serial} {sp|platform} Specify whether the serial port is connected to the platform COMA port, or the SP serial console.
Platform OS State Subcommands The subcommands listed in TABLE F-12 allow you to manage the operating system (OS). TABLE F-12 Platform OS State Subcommands Subcommand Description platform get os state Retrieves the current state of the platform OS (for example, running, booting, off and so on). platform set os state Reboots the platform into the default OS, BIOS setup or BIOS update, or shuts down the platform.
■ OS shutting down When the platform is in the Communicating state (in which the OS is communicating with the SP), if the platform drivers are uninstalled, the SP remains in the Communicating state even though it can no longer communicate with the platform. Refer to “Platform Set OS State Subcommand” on page 144 for more information about setting the state. Return Codes TABLE F-13 lists the return codes for this subcommand.
Platform Set OS State Subcommand Description: Provides the ability to reboot the platform into the default OS, BIOS setup or BIOS update, or to shut down the platform. Rebooting to BIOS setup allows you to configure the BIOS parameters while BIOS update allows you to reflash the BIOS image.
When the platform is in the Communicating state (in which the OS is communicating with the SP), if the platform drivers are uninstalled, the SP remains in the Communicating state even though it can no longer communicate with the platform. Refer to “Platform Get OS State Subcommand” on page 142 for a list of possible states. Return Codes TABLE F-15 lists the return codes for this subcommand.
TABLE F-16 lists the arguments for this subcommand. TABLE F-16 Arguments for Subcommand platform set os state boot Arguments Description {-f | --forced} Results in a hard power off. This option is ignored. [-b | --bios] Allows you to reflash the BIOS image. [-q | --quiet] Suppresses interative warning messages. No error messages are blocked. [-W | --nowait] If specified, the command returns immediately instead of waiting for the operation to complete.
Platform Power State Subcommands The subcommands listed in TABLE F-18 allow you to manage the platform power. TABLE F-18 Platform Power State Subcommands Subcommand Description platform get power state Provides the ability to determine the platform power state (for example, whether it is on or off). platform set power state Provides the ability to turn the platform power on or off.
Return Codes TABLE F-19 lists the return codes for this subcommand. TABLE F-19 Return codes for Subcommand platform get power state Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
TABLE F-20 lists the arguments for this subcommand. TABLE F-20 Arguments for Subcommand platform set power state Arguments Description {-W |--nowait} If specified, the command returns immediately instead of waiting for the operation to complete. {-f | --forced} Results in a hard power off. {-t |--timeout} Specifies the maximum time to wait for the operation to complete (in seconds). {off | on | cycle} Specifies whether to turn the platform power on or off or to cycle.
Platform Get Hostname Subcommand Description: Displays the host name of the current primary platform. The data is refreshed only when the platform is rebooted. Format Command format: platform get hostname [{-H|--noheader}] TABLE F-22 lists the argument for this subcommand. TABLE F-22 Argument for Subcommand platform get hostname Arguments Description {-H | --noheader} Suppresses column headers. Return Codes TABLE F-23 lists the return codes for this subcommand.
Platform Get Product ID Subcommand Description: Displays the product ID for the current system. Format Command format: platform get product-id Note – You can also retrieve the product ID, board revision number and PRS revision number by running the subcommands sensor get and inventory get hardware. Return Codes TABLE F-24 lists the return codes for this subcommand.
152 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
APPENDIX G Sensor Commands The sensor command reports or sets the value of an environmental sensor or control. TABLE G-1 lists the groups of sensor subcommands. TABLE G-1 Sensor Subcommand Groups Subcommand Group Description sensor get Returns all data associated with a sensor. sensor set Sets some of the data associated with a specific sensor or a class of sensors. Note – Every command returns a return code upon completion.
Sensor Get Subcommand Description: Returns all data associated with a sensor. By default, only the sensor ID and its current value are displayed. You can specify on the command line the order of the data output. Note – The identifier field is always displayed first, unless you suppress it with the -I option.
TABLE G-2 lists the arguments for this subcommand. TABLE G-2 Arguments for Subcommand sensor get Arguments Description {-i | --id} SENSOR_ID, PRODUCT-ID, BOARD-REVISION, PRS-REVISION Specifies the sensor for which the data is desired. You can specify this argument multiple times, in which case the sensor data is reported in the order specified. You can also retrieve the product ID, board-revision number and PRS revision number using this flag.
TABLE G-2 Arguments for Subcommand sensor get Arguments Description {-I | --noid} Suppresses the display of the sensor ID column. By default, this column always displays when more than one sensor is selected. [-H | --noheader] Suppresses the column headings. { -D | --delim } Delimits columns with the specified delimiter. Headings are also delimited unless suppressed. The delimiter can be any character or string. Return Codes TABLE G-3 lists the arguments for this subcommand.
Note – There are some sensors whose value does not change, some that are there to provide information in the event of a problem, and others to facilitate the proper operation of the software. Many of these sensors do not have a related component (parent) associated with them.
Sensor Set Subcommand Description: Allows you to set some of the data associated with a specific sensor or a class of sensors.
TABLE G-4 Arguments for Subcommand sensor set Arguments Description {-v | --value} Sets the value of the sensor. {-r | --reset} Resets all thresholds for the specified sensor(s) to the factory defaults. {-R | --resetall} Resets all thresholds for all sensors to the factory defaults. Return Codes TABLE G-5 lists the arguments for this subcommand. TABLE G-5 Return Codes for Subcommand sensor set Return Code ID Description NWSE_Success 0 Command successfully completed.
160 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
APPENDIX H Service Processor Commands The sp command gets or sets the configuration values for the Service Processor (SP), generates or manages events and notices; or adds or modifies subscribers, event routes and email-notification groups for the SP event manager. TABLE H-1 lists the groups of sp subcommands. Note – Every command returns a return code upon completion. TABLE H-1 Service Processor Subcommand Groups Subcommand Description Date Sets or retrieves the date and time on the SP RTC.
TABLE H-1 Service Processor Subcommand Groups Subcommand Description SNMP Manages SNMP functions. SSL Manages SSL capabilities. Update Flash Sets the update flag to start the full flash update or copies the Value-Add file to the Value-Add component of the SP flash. SP Date Subcommands The subcommands in TABLE H-2 manage the date and time on the SP. TABLE H-2 SP Date Subcommands Subcommand Description sp get date Retrieves the date and time from the SP RTC.
Return Codes TABLE H-3 lists the return codes for this subcommand. TABLE H-3 Return Codes for Subcommand sp get date Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_NoMemory 8 Insufficient memory. SP Set Date Subcommand Description: Sets the date and time on the SP RTC.
Return Codes TABLE H-5 lists the return codes for this command. TABLE H-5 164 Return Codes for Subcommand sp set date Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_InvalidArgument 4 One or more arguments were incorrect or invalid. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_NoMemory 8 Insufficient memory.
SP DNS Subcommands The subcommands in TABLE H-6 manage the DNS configuration on the SP. TABLE H-6 SP DNS Subcommands Subcommand Description sp disable dns Disables the DNS configuration on the SP. sp enable dns Configures the DNS configuration on the SP. sp get dns Displays the current DNS configuration on the SP. SP Disable DNS Subcommand Description: Disables the DNS configuration on the SP.
SP Enable DNS Subcommand Description: Configures the DNS configuration on the SP. Because applications do not see updated DNS resolver configurations (in /etc/resolv.conf) until they are restarted, this command restarts server processes that depend on DNS. This currently includes the sshd daemon and the Security Manager. Format Command format: sp enable dns { -n | --nameserver} NAMESERVER IP… {-s | --searchdomain } SEARCH DOMAIN… TABLE H-8 lists the arguments for this subcommand.
SP Get DNS Subcommand Description: Displays the current DNS configuration on the SP. Format Command format: sp get dns [{-n | --nameserver } | -s | --searchdomain } | {-H | --noheader }] [{-D | --delim }] TABLE H-10 lists the arguments for this subcommand. TABLE H-10 Arguments for Subcommand sp get dns Argument Description { -n | --nameserver } Displays the name server(s). If there is more than one nameserver, they print on separate lines.
SP Events Subcommands The subcommands in TABLE H-12 manage events on the SP. TABLE H-12 SP Events Subcommands Subcommand Description sp delete event Clears an existing event using the event ID. sp get events Returns detailed information about all active SP events. SP Delete Event Subcommand Description: Clears an existing event using the event ID. Format Command format: sp delete event { EVENT ID | {-a | --all}} [-q | --quiet] TABLE H-13 lists the arguments for this subcommand.
Return Codes TABLE H-14 lists the return codes for this subcommand. TABLE H-14 Return Codes for Subcommand sp delete event Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
TABLE H-15 lists the arguments for this subcommand. TABLE H-15 Arguments for Subcommand sp get events Argument Description {-i | --id} Specifies to display only information about this event; otherwise information for all existing events returns. {-d | --detail} Specifies to display the history of either one or all events. { -v| --verbose} Specifies to display all columns. { -H | --noheader } Suppresses column headings. { -D | --delim } Specifies to delimit columns with the specified delimiter.
SP Hostname Subcommands The subcommands in TABLE H-17 manage the SP host and domain. TABLE H-17 SP Hostname Subcommands Subcommand Description sp get hostname Displays the current host name and optionally the domain name of the SP. sp set hostname Resets the host name or domain name of the SP to the specified name. SP Get Hostname Subcommand Description: Displays the current host name and optionally the domain name of the SP.
Return Codes TABLE H-19 lists the return codes for this subcommand. TABLE H-19 Return Codes for Subcommand sp get hostname Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_NoMemory 8 Insufficient memory. NWSE_Busy 9 Device or resource is busy. NWSE_RPCConnected 11 RPC client already connected. NWSE_RPCConnRefused 12 RPC connection refused.
Return Codes TABLE H-21 lists the return codes for this subcommand. TABLE H-21 Return Codes for Subcommand sp set hostname Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_InvalidArgument 4 One or more arguments were incorrect or invalid. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_NoMemory 8 Insufficient memory.
SP IP Subcommands The subcommands in TABLE H-22 manage the SP network configuration. TABLE H-22 SP IP Subcommands Subcommand Description sp get ip Retrieves the ethernet-based network configuration information for the SP. sp set ip Sets or modifies the SP network configuration. SP Get IP Subcommand Description: Retrieves the ethernet-based network-configuration information for the SP, including IP address, network mask and gateway.
Return Codes TABLE H-24 lists the arguments for this subcommand. TABLE H-24 Return Codes for Subcommand sp get ip Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_NoMemory 8 Insufficient memory. NWSE_Busy 9 Device or resource is busy. NWSE_RPCConnected 11 RPC client already connected. NWSE_RPCConnRefused 12 RPC connection refused.
TABLE H-25 lists the arguments for this subcommand. TABLE H-25 Arguments for Subcommand sp set ip Argument Description {-i | --ipaddress} Specifies the IP address you wish to set. {-n | --netmask} Specifies the netmask; the default value is 255.255.255.0. {-g | --gateway} Specifies the gateway; the default value is the existing gateway. {-w | --nowait} If you specify the -nowait option, loss of connectivity will occur some time after the command returns.
SP JNET Address Subcommands The JNET address is used for communications between the SP and the platform. The subcommands in TABLE H-27 manage the SP JNET address. TABLE H-27 SP JNET Subcommands Subcommand Description sp get jnet Retrieves the JNET address. sp set jnet Sets the JNET address. SP Get JNET Subcommand Description: Retrieves the IP address of the platform JNET driver.
Return Codes TABLE H-29 lists the return codes for this subcommand. TABLE H-29 Return Codes for Subcommand sp get jnet Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_NoMemory 8 Insufficient memory. NWSE_Busy 9 Device or resource is busy. NWSE_HostDown 14 Host is down. SP Set JNET Subcommand Description: Sets or modifies the SP and platform network addresses for JNET.
TABLE H-30 lists the arguments for this subcommand. TABLE H-30 Arguments for Subcommand sp set jnet Argument Description {-p | --platform} Specifies the IP address for the platform. {-s | --sp} Specifies the IP address for the SP. Note – If you change the default addresses of JNET using this command and then re-install the platform operating system or reset the SP through the subcommand sp reset to default-settings , you must re-issue the subcommand sp set jnet to re-establish the JNET connection.
SP Locate Light Subcommands The subcommands in TABLE H-32 manage the locatelight switch. TABLE H-32 SP Locatelight Subcommands Subcommand Description sp get locatelight Reads the value of the locatelight switch (which represents the state of the front and rear panel identification lights). sp set locatelight Sets the state of the locatelight switch.
SP Set Locatelight Subcommand Description: Sets the state of the locatelight switch (which describes the state of the front and rear panel identification lights). Format Command format: sp set locatelight {blink | off} Return Codes TABLE H-34 lists the return codes for this subcommand. TABLE H-34 Return Codes for Subcommand sp set locatelight Return Code ID Description NWSE_Success 0 Command successfully completed.
SP Logfile Subcommands The subcommands in TABLE H-35 manage the SP log files. TABLE H-35 SP Logfile Subcommands Subcommand Description sp get logfile Retrieves the event-log file configuration. sp set logfile Configures the event log file that is the destination of all Event Manager events and notices. SP Get Logfile Subcommand Description: Retrieves the event log file configuration.
Return Codes TABLE H-37 lists the return codes for this subcommand. TABLE H-37 Return Codes for Subcommand sp get logfile Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Return Codes TABLE H-39 lists the arguments for this subcommand. TABLE H-39 184 Return Codes for Subcommand sp set logfile Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
SP Miscellaneous Subcommands The subcommands in TABLE H-40 manage miscellaneous SP functions. TABLE H-40 Miscellaneous SP Subcommands Subcommand Description sp create test events Tests and validates different types of configurations you may be considering for the SP. sp get port 80 Retrieves the last port 80 postcode from the PRS Port80 register. sp get status Returns the status of the overall system. sp get tdulog Captures data and stores it on the SP in compressed format.
Return Codes TABLE H-41 lists the return codes for this command. TABLE H-41 Return Codes for Subcommand sp create test events Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server. NWSE_NoMemory 8 Insufficient memory.
Return Codes TABLE H-43 lists the return codes for this subcommand. TABLE H-43 Return Codes for Subcommand sp get port80 Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_NoMemory 8 Insufficient memory. NWSE_ServiceNotAvailable 24 Requested service is not available.
TABLE H-44 BIOS POST Codes POST Code Description 13 Initialize PCI bus mastering devices 14 Initialize keyboard controller 16 BIOS ROM checksum 17 Initialize cache before memory autosize 18 8254 programmable interrupt timer initialization 1A 8237 DMA controller initialization 1C Reset programmable interrupt controller 20 Test DRAM refresh 22 Test 8742 keyboard controller 24 188 Set ES segment register to 4GB 26 Enable gate A20 line 28 Autosize DRAM 29 Initialize POST memory man
TABLE H-44 BIOS POST Codes POST Code Description 48 Check video configuration against CMOS 49 Initialize PCI bus and devices 4A Initialize all video adapters in system 4B QuietBoot start (optional) 4C Shadow video BIOS ROM 4E Display BIOS copyright notice 4F Initialize MultiBoot 50 Display CPU type and speed 51 Initialize EISA board 52 Test keyboard 54 Set key click if enabled 55 Enable USB devices 58 Test for unexpected interrupts 59 Initialize POST display service 5A Displ
190 TABLE H-44 BIOS POST Codes POST Code Description 76 Check for keyboard errors 7C Set up hardware interrupt vectors 7D Initialize Intelligent System Monitoring 7E Initialize coprocessor if present 80 Disable onboard super I/O ports and IRQs 81 Late POST device initialization 82 Detect and install external RS232 ports 83 Configure non-MCD IDE controllers 84 Detect and install external parallel ports 85 Initialize PC compatible PnP ISA devices 86 Reinitialize onboard I/O ports 87
TABLE H-44 BIOS POST Codes POST Code Description 9E Enable hardware interrupts 9F Determine number of ATA and SCSI drives A0 Set time of day A2 Check key lock A4 Initialize typematic rate A8 Erase F2 prompt AA Scan for F2 key stroke AC Enter setup AE Clear boot flag B0 Check for errors B1 Inform RomPilot about the end of POST B2 POST done - prepare to boot operating system B4 One short beep B5 Terminate QuietBoot (optional) B6 Check password B7 Initialize ACPI BIOS B9 Pr
TABLE H-44 BIOS POST Codes POST Code Description C7 Initialize notebook docking late C8 Force check (optional) C9 Extended checksum (optional) CA Redirect Int 15h to enable remote keyboard CB Redirect Int 13 to Memory Technologies Devices such as ROM, RAM, PCMCIA, and serial disk CC Redirect Int 10h to enable remote serial video CD Re-map I/O and memory for PCMCIA CE Initialize digitizer and display message D2 Unknown interrupt Boot Block Codes for Flash ROM TABLE H-45 lists the boot b
TABLE H-45 Boot Block Codes in Flash ROM Post Code Description EE Shadow Boot Block EF System memory test F0 Initialize interrupt vectors F1 Initialize Run Time Clock F2 Initialize video F3 Initialize System Management Manager F4 Output one beep F5 Clear Huge Segment F6 Boot to mini DOS F7 Boot to Full DOS SP Load Settings Subcommand Description: Configures an SP with the same configuration as that of another SP.
Return Codes TABLE H-47 lists the return codes for this subcommand. TABLE H-47 Return Codes for Subcommand sp load settings Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_InvalidArgument 4 One or more arguments were incorrect or invalid. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_NoMemory 8 Insufficient memory. NWSE_HostDown 14 Host is down.
Return Codes TABLE H-49 lists the return codes for this subcommand. TABLE H-49 Return Codes for Subcommand sp get status Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
TABLE H-50 lists the arguments for this subcommand. TABLE H-50 Arguments for Subcommand sp get tdulog Argument Description {-f | --filename} Optional. The name of the output file to which the log files are copied, or the fully qualified path name. File names cannot contain the backward relative path reference (..) or the less than symbol (<).
Return Codes TABLE H-52 lists the return codes for this subcommand. TABLE H-52 Return Codes for Subcommand sp get tdulog Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_NotFound 5 Entity (user, service, file, path or other) was not found. NWSE_NoPermission 6 Not authorized to perform this operation. NWSE_MissingArgument 7 Missing argument(s).
Return Codes TABLE H-54 lists the return codes for this command. TABLE H-54 Return Codes for Subcommand sp reboot Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
TABLE H-55 lists the arguments for this command. TABLE H-55 Arguments for Subcommand sp reset Argument Description {-a | --all} Resets all SP settings to their default configuration. When the SP reboots, the settings are reset to their default values. {-c | --config} Resets other system configuration settings to their default configuration. When the SP reboots, the system settings are reset to their default values. {-n | --network} Resets network settings to their default configuration.
Return Codes TABLE H-56 list the return codes for this command. TABLE H-56 200 Return Codes for Subcommand sp reset Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
SP Mount Subcommands The subcommands in TABLE H-57 manage the SP mount points. TABLE H-57 SP Mount Subcommands Subcommand Description sp add mount Creates or resets a mount point. sp delete mount Deletes the specified mount point. sp get mounts Displays the current mount points on the SP. SP Add Mount Subcommand Description: Creates or resets a mount point.
Note – Several error messages may appear when executing an smb mount while mounting windows partitions. Check that the mount succeeded after the call by running the subcommand sp get mount. The required formats for remote NFS and SMB mounts are as follows: ■ ■ For NFS: server_name:server_exported_mountpoint For SMB: //server_name/windows_share_name Return Codes TABLE H-59 lists the return codes for this subcommand.
SP Delete Mount Description: Deletes a mount point. Format Command format: sp delete mount LOCAL_MOUNT_POINT [-q | --quiet] TABLE H-60 lists the arguments for this subcommand. TABLE H-60 Arguments for Subcommand sp delete mount Argument Description LOCAL MOUNT POINT Specifies the mount point to remove. If you do not specify the local mount point, /mnt is implicit as the default value. [-q | --quiet] If the mount point to delete is not found, this argument specifies that no error be returned.
SP Get Mount Subcommand Description: Displays the current mount points on the SP. Format Command format: sp get mounts [{-l | --local} MOUNTPOINT] [-H | --noheader] [{-D | --delim }] TABLE H-62 lists the arguments for this subcommand. TABLE H-62 Arguments for Subcommand sp get mount Arguments Description {-l | --local} Specifies the local mount point. If you do not specify -l, /mnt is implicit as the local mount point. { -H | --noheader } Suppresses column headings.
TABLE H-63 Return Codes for Subcommand sp get mount Return Code ID Description NWSE_NoRouteToHost 13 No route to host (network down). NWSE_HostDown 14 Host is down. NWSE_NotMounted 21 File system is not mounted. SP SMTP Subcommands The subcommands in TABLE H-64 manage SMTP communications. TABLE H-64 SP SMTP Subcommands Subcommand Description sp get smtp server Retrieves the SMTP server information. sp get smtp subscribers Returns detailed information about one or all SMTP subscribers.
TABLE H-65 lists the arguments for this subcommand. TABLE H-65 Arguments for Subcommand sp get smtp server Argument Description { -H | --noheader } Suppresses column headings. { -D | --delim } Delimits columns with the specified delimiter. Headings are also delimited unless suppressed. The delimiter can be any character or string. Return Codes TABLE H-66 lists the return codes for this subcommand.
SP Set SMTP Server Subcommand Description: Configures the SP SMTP client with the information for the remote SMTP server, including the address and optional port number. Format Command format: sp set smtp server [{-f | --from} FROM FIELD ] IP OR HOSTNAME OF SMTP SERVER TABLE H-67 lists the arguments for this subcommand. TABLE H-67 Arguments for Subcommand sp set smtp server Arguments Description {-f | --from} Specifies the from field for the SMTP server.
SP Get SMTP Subscribers Subcommand Description: Returns detailed information about one or all SMTP subscribers. Format Command format: sp get smtp subscribers [{-n | --name} ] [-H | noheader] [{-D | --delim }] TABLE H-69 lists the arguments for this subcommand. TABLE H-70 lists the default SMTP subscribers. TABLE H-69 Arguments for Subcommand sp get smtp sebscribers Arguments Description { -n | --namserver } Specifies the name of the SMTP subscriber for which to retrieve information.
Return Codes TABLE H-71 lists the return codes for this subcommand. TABLE H-71 Return Codes for Subcommand sp get smtp subscribers Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
Note – All options replace the existing values with the new value. Unspecified options leave existing settings as they are. For example, if you only specify the -r option for an existing subscriber, the existing email address list is replaced with the new list specified in the command. TABLE H-72 Arguments for Subcommand sp update smtp subscriber Arguments Description {-n | --name} Specifies the name of the SMTP subscriber to update.
Return Codes TABLE H-74 lists the return codes for this command. TABLE H-74 Return Codes for Subcommand sp update smtp subscriber Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified. NWSE_RPCTimeout 2 Request was issued, but was not serviced by the server. RPC procedure timed out and the request may or may not have been serviced by the server.
SP SNMP Subcommands The subcommands in TABLE H-75 manage SNMP communications. TABLE H-75 SP SNMP Subcommands Subcommand Description sp add snmp destination Adds an SNMP destination. sp delete snmp destination Deletes the SNMP destination. sp get snmp destinations Displays the available SNMP destinations (IP address or hostname) to which the Service Processor is configured to send.
TABLE H-76 lists the argument for this subcommand. TABLE H-76 Argument for Subcommand sp add snmp-destination Arguments Description IP ADDRESS/HOSTNAME Specifies the IP address or name of the host for the destination you wish to add. This argument is repeatable to add multiple destinations at one time; however, the number of destinations you can create is limited due to memory constraints. Return Codes TABLE H-77 lists the return codes for this subcommand.
SP Delete SNMP Destination Subcommand Description: Deletes a single SNMP destination (either IP address or host name). Format Command format: sp delete snmp-destination { IP_ADDRESS/HOSTNAME | {-a | --all} [-q | --quiet] TABLE H-78 lists the arguments for this subcommand. TABLE H-78 Arguments for Subcommand sp delete snmp-destination Arguments Description IP ADDRESS/HOSTNAME Specifies the IP address or hostname of the destination to remove.
TABLE H-79 Return Codes for Subcommand sp delete snmp-destination Return Code ID Description NWSE_RPCConnRefused 12 RPC connection refused. NWSE_UnknownError 15 Miscellaneous error not captured by other errors. NWSE_FileError 18 File open, file missing, or a read or write error occurred. SP Get SNMP Destinations Subcommand Description: Displays the available SNMP destinations (IP address or host name) to which the SP is configured to send.
SP Get SNMP Proxy Community Subcommand Description: Returns the community name the SP is currently using to proxy the platform SNMP agent. Format Command format: sp get snmp proxy community Return Codes TABLE H-81 lists the return codes for this subcommand. TABLE H-81 Return Codes for Subcommand sp get snmp proxy community Return Code ID Description NWSE_Success 0 Command successfully completed. NWSE_InvalidUsage 1 Invalid usage: bad parameter usage, conflicting options specified.
TABLE H-82 lists the argument for this subcommand. TABLE H-82 Argument for Subcommand sp set snmp proxy community Argument Description COMMUNITY STRING Specifies the name of the community to configure. There are no restrictions on the length of the community strings; common names are private and public. The default name of the community string is private. If you run the subcommand sp get snmp proxy community without setting it, the return valule is private. Otherwise, you can set it to any string.
SP SSL Subcommands The subcommands in TABLE H-84 manage SSL capabilities. TABLE H-84 SP SSL Subcommands Subcommand Description sp disable ssl-required Disables forced use of the secure HTTP (https) protocol. sp enable ssl-required Enables forced use of the secure HTTP (https) protocol. sp get ssl Determines if the Apache Web server is using factory-supplied files or user-supplied files. sp set ssl Allows you to use site SSL certificates in the SP environment.
TABLE H-85 Return Codes for Subcommand sp disable ssl-required Return Code ID Description NWSE_NoMemory 8 Insufficient memory. NWSE_FileError 18 File open, file missing, or a read or write error occurred. NWSE_ServiceNotAvailable 24 Requested service is not available. SP Enable SSL-Required Subcommand Description: Enables automatic redirect to secure HTTP URLs. With SSL enabled, HTTP requests are automatically redirected to equivalent HTTPS requests to maintain site security. SSL version 0.9.
SP Get SSL Subcommand Description: Determines if automatic redirect to secure HTTP is required or optional, and whether Apache Web Server is using factory or user-supplied SSL certificate files. Format Command format: sp get ssl [{-H | noheader}] [{-D | --delim }] TABLE H-87 lists the arguments for this subcommand. TABLE H-87 Arguments for Subcommand sp get ssl Arguments Description { -H | --noheader } Suppresses column headings.
SP Set SSL Subcommand Description: Allows you to use site SSL certificates in the Service Processor environment. This command allows you to replace the Server Certificate in the SP Value-Add image with your own internally-generated certificate and to restore the factory settings. Format Command format: sp set ssl [-f] sp set ssl {-c | --certfile} {-k | --keyfile} TABLE H-89 lists the arguments for this subcommand.
SP Update Subcommands The subcommands in TABLE H-91 manage the SP flash. TABLE H-91 SP Flash Subcommands Subcommand Description sp update flash all Sets the update flag to start the full flash update on the next reset of the SP. sp update flash applications Copies the file Value-Add to the Value-Add component of the SP flash. sp update flash pic Updates the PIC firmware to a newer version. sp update diags Updates the diagnostics to a newer version.
TABLE H-92 lists the arguments for this subcommand. TABLE H-92 Arguments for Subcommand sp update flash all Argument Description {-i | --serverip} The IP address of the remote server on which the Java spUpdate program is running. {-p | --port} Optional: The port number on the remote server on which the Java spUpdate program is listening for SP flash update requests. If the port number is not provided, the command tries to connect to the default port. The default port number is 52708.
SP Update Flash Applications Subcommand Description: The SP file system is divided into two componenets: Base and Value-Add. The Base component includes the repository and the Value-Add component includes the application software. This command copies the file Value-Add to the Value-Add component of the SP flash. The new Value-Add image takes effect after you reset the SP. Format Command format: sp update flash applications {-f | --filename} TABLE H-94 lists the arguments for this subcommand.
SP Update Flash PIC Subcommand Description: This command updates the PIC firmware to a newer version. An input PIC-update image file is provided. Format Command format: sp update flash pic {-f | --filename} FULL PATH OF THE FILE | [{-v | --version}] TABLE H-96 lists the arguments for this subcommand. TABLE H-96 Arguments for Subcommand sp update flash pic Argument Description {-f | --filename} Specifies the full path of the file. {-v | --version} Outputs the current version of the firmware.
SP Update Diags Subcommand Description: Updates the current version of diagnostics available. While the SP functions normally without access to an external file system, a file system is required to enable several features, including diagnostics. The SP software uses a default version of diagnostics. However, if a new version is released and stored on the Network Share Volume, you must explicitly point to that new version to use it.
Index A B access commands add public key 96 add trust 91 add user 100 delete public keys 98 delete trust 93 delete user 101 directory services subcommands 86 disable service 86 enable service 87 get group 80 get groups 81 get map 82 get public key users 97 get services 89 get trusts 94 get users 103 groups subcommands 80 map 83 map subcommands 82 public key subcommands 96 subcommand groups summary 79 trust subcommands 91 unmap 84 update password 104 update user 105 user subcommands 100 Agent X for SNMP 4
diagram of server management options 5 diags commands cancel tests 108 get state 110 get tests 111 run tests 112 start 114 subcommands summary table 107 terminate 116 documentation, related xx E enabling IPMI access 14 enabling IPMI LAN access 17 F flash ROM boot block codes 192 G getty, using for console redirection 66 grub, using for console redirection 64 H host key pairs for scripting 59 host keys, scripting 57 I initial manager account, creating 13 integration of SNMP protocol 42 intelligent platf
LILO, using for console redirection 65 logging in with setup account 13 LOM, see lights out management POST codes table 187 propagating SP settings 24 public keys for scripting 58 M R MAC addresses, determining 25 management information base (MIB) for SNMP 42 MIB browser 47 MIB tree diagram 42 related documentation xx return codes summary table 76 S N network share volume extracted content 68 structure 68 O operator panel buttons functions defined 7 illustration 6 organization of this book xix overvi
updating SP software 21 service processor commands, see sp commands setup account, logging in 13 shell scripts, using 55 simple network management protocol, see SNMP interface SNMP interface agent on the SP 45 Agent X 46 architecture diagram 44 community name, setting 46 configuring 44 integration overview 42 logging options, setting 47 management information base (MIB) 42 MIB details 50 overview 41 prerequisites 44 proxy agent 45 server event trap destinations 49 server event traps 48 SP events table 51 th
T traps, server events with SNMP 48 troubleshooting dump utility (TDU) 195 troubleshooting IPMI 39 troubleshooting SNMP 53 trusted host relationship, scripting 58 types of users, defined 8 U updating service processor software 21 updating SP base component 23 user groups, defined 8 user types, defined 8 Index 231
232 Sun Fire V20z and Sun Fire V40z Servers, Server Management Guide • May, 2004
