|
Steps to Follow
Please review the following
information.
Data Gathering Process
Gathering data at the time of
an incident reduces the chance that failure data
will be lost,
and increases the efficiency and accuracy of the repair process.
When the failure data is forwarded to Sun's Customer
Control Center at case
opening, troubleshooting will begin almost
immediately, and the appropriate
part may be ordered so that it
can arrive with the Field engineer. Conversely,
although
there may be times when data gathering is impossible, delays
should be expected as the Field engineer will have to go onsite
and gather
data in order to troubleshoot the problem.
An
additional delay may occur while waiting for ordered parts to
arrive.
The process of data collection
is fairly simple. What's needed:
This section explains
how to log in and out of the WebGUI.
Notes:
The ILOM boots automatically
when the Sun server is cabled appropriately
and plugged in to an
AC supply, usually within one minute. However, if the
management
Ethernet is not connected, or if the ILOM's Dynamic Host
Configuration Protocol(DHCP) process fails due to the absence of a
DHCP
server on the management network, the ILOM might take a few
minutes to
boot. Disabling the use of the browser proxy server (if
one is used) for access
to the management network might make the
WebGUI response time faster.
Do not use the Refresh or Log
Out buttons in your Internet web browser when
using the WebGUI.
Instead, only use the Refresh and Log Out buttons
provided at the
top right of the WebGUI window.
You need the IP address of the
ILOM. The ILOM's IP address is provided in the BIOS Setup
screen.
You can also observe the DHCP server which issues the IP address
when the ILOM boots, or look up the ILOM's MAC address-to-IP
address
mapping in the DHCP server logs or lease file.
To log in to the
WebGUI
Type the IP address of the
ILOM into your web browser - being used in secure
https format,
i.e.: https://xxx.xxx.xxx.xxx
The login screen appears.
Please see named
200000070000679E00004B5F4FE7F05A.svm below.
2. Type your user name
and password.
When you first try to access
the WebGUI, it prompts you to type the default
user name and
password. The default user name and password are:
Default user name
root
Default password
changeme
The default user name and
password are in lowercase characters.
One local user ID is
predefined with the user name root with the role
Administrator.
You cannot delete this user ID or change its role attributes.
The
initial password changeme also is provided. This password is
required for
log in on the serial port, Secure Shell (SSH), and
the WebGUI. To increase
secure access to the ILOM, change
the default password to a new,
unique password.
3. Click Log In
.
The WebGUI user interface
appears.
4: Gather Data:
Select System Monitoring => Event Logs.
The System Event Logs
page appears.
Please see named
2000000700007F9000003B8AAB6F9A6A.svm below.
5: Copy and paste the
data from the screen into a text file and forward
to the SUN
engineer who handles the case.
It should be a file of the format :
----------------------------------------------------------------------------------------------------
1225 Audit Log minor Tue Aug 28 04:06:53 2007 root : Open Session : object = /session/type : value = www : success
1224 Audit Log minor Tue Aug 28 04:06:38 2007 14416 : Open Session : object = /session/type : value = www : error
1223 IPMI Log critical Tue Aug 28 01:32:55 2007 ID = 163 : 08/28/2007 : 01:32:55 : System Firmware Progress : BIOS : System boot initiated
1222 Audit Log minor Tue Aug 28 01:32:54 2007 KCS Command : Set System Boot Options : parameter = boot flags : data1 = 0x0 : data2 = 0x0 :
data3 = 0x0 : data4 = 0x0 : data5 = 0x0 : success
1221 Audit Log minor Tue Aug 28 01:32:44 2007 KCS Command : Set ACPI Power State : system power state = 0x0 : device power state = no change : success
1220 IPMI Log critical Tue Aug 28 01:32:05 2007 ID = 162 : 08/28/2007 : 01:32:05 : System Firmware Progress : BIOS : User-initiated system setup
1219 IPMI Log critical Tue Aug 28 01:31:22 2007 ID = 161 : 08/28/2007 : 01:31:22 : System Firmware Progress : BIOS : Option ROM initialization
1220 Audit Log critical Tue Aug 28 01:31:19 2007 Uncorrected Error Node 0 DIM_Pair 0 : Master Write Read : channel number = 0 : bus ID = 0 :
bus type = public : slave address = 0x29 : read count = 14 : write data = 0x2 0x10 : failure
The data can be analyzed to help resolve most hardware issues.
Using Simple Network
Management Protocol (SNMP)
This section has been directly
pulled from the system admin manual .
More information
about data collection and the associated MIB's can be found
at:
http://download.oracle.com/docs/cd/E19203-01/819-1160-13/index.html
About SNMP:
The Sun server supports the
Simple Network Management Protocol (SNMP)
interface, versions 1,
2c, and 3. SNMP is an open technology that enables the
management
of networks and devices, or nodes, connected to the network.
SNMP
messages are sent over IP using the User Datagram Protocol (UDP).
Any management application that supports SNMP can manage your
server.
1.1 How SNMP
Works:
Utilizing SNMP requires two
components, a network management station and
a managed node (in
this case, the ILOM). Network management stations
host management
applications, which monitor and control managed nodes.
Managed nodes are any number
of devices, including servers, routers, and
hubs, which host SNMP
management agents responsible for carrying out the
requests from
management stations. The management station monitors nodes
by
polling management agents for the appropriate information using
queries.
Managed nodes can also provide
unsolicited status information to a
management station in the form
of a trap. SNMP is the protocol used to
communicate management
information between the management stations
and agents.
The SNMP agent is preinstalled
and runs on the ILOM, so all SNMP
management of the server should
occur through the ILOM. To utilize this
feature, your operating
system must have an SNMP client application.
See your operating
system vendor for more information.
The SNMP agent on your ILOM
provides the following capabilities: inventory management, and
sensor and system state monitoring.
1.2: SNMP
Management Information Base (MIB) Files:
The base component of an SNMP
solution is the Management Information
Base (MIB). A MIB is a text
file that describes a managed node s available
information
and where it is stored. When a management station requests
information from a managed node, the agent receives the request
and retrieve
s the appropriate information from the MIBs. The Sun
server supports the
following SNMP classes of Management
Information Base (MIB) files.
Download and install the product
specific MIB
files from your Resource CD or Tools and Drivers CD
for your platform.
The system group and
SNMP group from RFC1213 MIB
SNMP-FRAMEWORK-MIB
SNMP-USER-BASED-MIB
SNMP-MPD-MIB
SUN-PLATFORM-MIB
ENTITY-MIB
SUN-PLATFORM-MIB
1.3: MIB's
Integration:
Use the MIBs to integrate the
management and monitoring of the server into
SNMP management
consoles. The MIB branch is a private enterprise MIB,
located at
MIB object iso(1).org (3). dod (6). internet (1). private (4).
enterprises (1).
sun (42). products (2). The standard SNMP port
(161) is used by the SNMP
agent on the ILOM.
1.4: About SNMP
Messages:
SNMP is a protocol, not an
operating system so you need some type of
application to use SNMP
messages. Your SNMP management software may
provide this
functionality, or you can use an open source tool like net-SNMP,
which is available at SourceForge.
Both management stations and
agents use SNMP messages to communicate.
Management stations can
send and receive information. Agents can respond
to requests and
send unsolicited messages in the form of a trap. There are
five
functions that management stations and agent use:
Get
GetNext
GetResponse
Set
Trap
By default, port 161 is used
for SNMP messages and port 162 is used to
listen for SNMP traps.
1.5: About ILOM
and SNMP:
The ILOM has a preinstalled
SNMP agent that supports trap delivery to an
SNMP management
application. To use this feature, you must:
1) integrate the
platform-specific MIBs into your SNMPenvironment,
2) tell your
management station about your server, then
3) configure the
specific traps.
1.5.1 Integrating
the MIB's:
Use a third party SNMP
management application to load the SUN-PLATFORM-MIB.
1.6 Managing SNMP User
Accounts:
You can add, delete, or
configure SNMP user accounts from the CLI.
By default, SNMP v3 is
enabled, and SNMP v1 and v2c are disabled.
To do this on the
WebGUI,
1.6.1 Adding a User
Account:
To add an SNMP v3 read-only
user account, type the following command:
create
/SP/services/snmp/users/username authenticationpassword=password
To add an SNMP v1/v2c user
account, type this command:
create
/SP/services/snmp/communities/communityname
1.6.2 Deleting a User
Account:
To delete an SNMP v3 user
account, type this command :
delete
/SP/services/snmp/users/username
To delete an SNMP v1/v2c user
account, type this command:
delete
/SP/services/snmp/communities/communityname
1.6.3 Configuring User
Accounts:
To configure SNMP user
accounts, use the set command.
set target
[propertyname=value]
These targets, properties, and
values are valid for SNMP user accounts.
When changing the
parameters of SNMP users, you must set values for all of
the
properties, even if you are not changing all of the values. For
example,
to change
user al's privacy protocol to
DES you must type:
-> set
/SP/services/snmp/users/al privacyprotocol=DES
privacypassword=password
authenticationprotocol=SHA
authenticationpassword=password
Your changes would be invalid
if you only typed:
-> set
/SP/services/snmp/users/al privacyprotocol=DES
Note: You can change SNMP user
permissions without resetting the privacy and authentication
properties.
TABLE 11-1 SNMP User Account
Targets, Properties and Values
Target Property Value Default
/SP/services/snmp/communities/
communityname
permissions ro|rw ro
/SP/services/snmp/users/username
authenticationprotocol
authenticationpassword
permissions
privacyprotocol
privacypassword
MD5|SHA
ro|rw
none|DES
MD5
(null string)
ro
none*
(null string)
/SP/services/snmp engineid =
none
port = 161
sets = enabled
v1 = disabled
v2c = disabled
v3 = disabled
string
integer
enabled|disabled
enabled|
|
