Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1009021.1
Update Date:2010-12-29
Keywords:

Solution Type  Technical Instruction Sure

Solution  1009021.1 :   How To Configure the ALOM Notification Variables  


Related Items
  • Sun Fire V215 Server
  •  
  • Sun Fire V440 Server
  •  
  • Sun Fire V240 Server
  •  
  • Sun Fire V245 Server
  •  
  • Sun Netra 210 Server
  •  
  • Sun Fire V445 Server
  •  
  • Sun Netra 440 Server
  •  
  • Sun Fire V250 Server
  •  
  • Sun Fire V125 Server
  •  
  • Sun Fire V210 Server
  •  
  • Sun Netra 240 (AC) Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  

PreviouslyPublishedAs
212441


Applies to:

Sun Fire V210 Server
Sun Fire V440 Server
Sun Fire V240 Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Netra 240 (AC) Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Netra 210 Server - Version: Not Applicable and later    [Release: N/A and later]
All Platforms

Goal

Description
This Technical Instruction will describe how to configure ALOM notification variables to send out email to specified recipients when alerts of a desired level take place. This procedure is accurate for ALOM versions 1.0 through current which is 1.5.x

Solution

Steps to Follow
How To Configure the ALOM Notification Variables

Configuring the ALOM Notification Variables will allow varying levels of
ALOM alerts to be sent automatically to specified email addresses.

To use this functionality, ALOM requires the NET MGT port to be configured and
operational first, otherwise it has no way to send the notifications. Configuration of the
NET MGT port is described in Document 1004884.1

As in the NET MGT port configuration Article, the Notifications variable
can also be set up through a tip session to the SERIAL MGT port, or
through the use of the Solaris[TM] based "scadm" command.

We will cover the method assuming a tip connection to the ALOM serial port
is functioning in this first example.

1) Use the "showsc" command to show the current config

 sc> showsc
Advanced Lights Out Manager v1.0
 parameter                value
--------- -----
if_network true
if_modem false
if_snmp false
if_emailalerts false
sys_autorestart xir
netsc_tpelinktest false
netsc_dhcp false
netsc_ipaddr 129.148.173.27
netsc_ipnetmask 255.255.255.0
netsc_ipgateway 129.148.173.253
mgt_mailhost
mgt_mailalert
sc_customerinfo
sc_escapechars #.
sc_powerondelay false
sc_clipasswdecho true
sc_cliprompt sc
sc_clitimeout 0
sc_clieventlevel 2
sys_eventlevel 2
ser_baudrate 9600
ser_parity none
ser_stopbits 1
ser_data 8
netsc_enetaddr 00:03:ba:29:5e:34
sys_hostname abcd
sys_enetaddr 00:03:ba:29:5e:2b
 sc> setsc if_emailalerts true 

The above command enables the mail alerts to be sent

 sc> setsc mgt_mailhost 129.148.9.16 

This (above) command sets the IP address of the mail server to which ALOM delivers the mail
alerts, if two addresses are specified they must be seperated by a single space

 sc> setsc mgt_mailalert john.doe@sun.com 1  

This (above) command sets who will be sent the email with the alerts and what level alerts
will be sent. The possible settings are:
1 (critical), 2 (critical and major) and 3 (critical, major and minor)

 sc> setsc mgt_mailalert test.alom@nowhwere.com 3  

This (above) command shows the configuration of an additional email address to
receive level 3 alerts.

 sc> showsc    

This (above) command will show the configuration with the changes

 Advanced Lights Out Manager v1.0
 parameter                value
--------- -----
if_network true
if_modem false
if_snmp false
if_emailalerts true
sys_autorestart xir
netsc_tpelinktest false
netsc_dhcp false
netsc_ipaddr 129.148.173.27
netsc_ipnetmask 255.255.255.0
netsc_ipgateway 129.148.173.253
mgt_mailhost 129.148.9.16
mgt_mailalert(1) john.doe@sun.com 1
mgt_mailalert(2) test.alom@nowhwere.com 3
sc_customerinfo
sc_escapechars #.
sc_powerondelay false
sc_clipasswdecho true
sc_cliprompt sc
sc_clitimeout 0
sc_clieventlevel 2
sys_eventlevel 2
ser_baudrate 9600
ser_parity none
ser_stopbits 1
ser_data 8
netsc_enetaddr 00:03:ba:29:5e:34
sys_hostname abcd
sys_enetaddr 00:03:ba:29:5e:2b

To remove an email address from the configuration so that alerts are no
longer sent to it we use the same command as when we added it but without
the alert level number:

 sc> setsc mgt_mailalert test.alom@nowhwere.com  
 sc> showsc    - shows that test.alom@nowhwere.com is now removed
 Advanced Lights Out Manager v1.0
 parameter                value
--------- -----
if_network true
if_modem false
if_snmp false
if_emailalerts true
sys_autorestart xir
netsc_tpelinktest false
netsc_dhcp false
netsc_ipaddr 129.148.173.27
netsc_ipnetmask 255.255.255.0
netsc_ipgateway 129.148.173.253
mgt_mailhost 129.148.9.16
mgt_mailalert(1) john.doe@sun.com 1
sc_customerinfo
sc_escapechars #.
sc_powerondelay false
sc_clipasswdecho true
sc_cliprompt sc
sc_clitimeout 0
sc_clieventlevel 2
sys_eventlevel 2
ser_baudrate 9600
ser_parity none
ser_stopbits 1
ser_data 8
netsc_enetaddr 00:03:ba:29:5e:34
sys_hostname abcd
sys_enetaddr 00:03:ba:29:5e:2b

To demonstrate the event notification the system is powered down:

 sc> poweroff -y
SC Alert: Host system has shut down.

The following email was then received:

 From: abcd@sydney.East.Sun.COM
To: john.doe@sun.com
Subject: System Alert From abcd
 System Event Recorded By SC:
 HostID:         "83295e2b"
 Event:          "00040029"
 Time:           "TUE SEP 16 17:39:22 2003"
 Customer Info:  "No Entry"
 Hostname:       "abcd"
 SC IP Address:  "129.148.173.27"
 Message:        "Host system has shut down."

2) The same configuration can be done through the use of the Solaris based
scadm command:

 #scadm set if_emailalerts true
 #scadm set mgt_mailhost 129.148.9.16
 #scadm set mgt_mailalert john.doe@sun.com 1
 #scadm show
 if_network="true"
if_modem="false"
if_snmp="false"
if_emailalerts="true"
sys_autorestart="xir"
netsc_tpelinktest="true"
netsc_dhcp="false"
netsc_ipaddr="129.148.173.27"
netsc_ipnetmask="255.255.255.0"
netsc_ipgateway="129.148.173.253"
mgt_mailhost="129.148.9.16"
mgt_mailalert="john.doe@sun.com 1"
sc_customerinfo=""
sc_escapechars="#."
sc_powerondelay="false"
sc_servicemode="false"
sc_clipasswdecho="true"
sc_cliprompt="sc"
sc_clitimeout="0"
sc_clieventlevel="2"
sc_ssqamode="false"
sys_eventlevel="2"


Product
Sun Fire V210 Server
Sun Fire V440 Server

Internal Comments
Internal Link for

Technical Instruction Document 1004884.1


alom, net mgt, v210, v240, v440, sys_eventlevel, mgt_mailalert
Previously Published As
72123

Change History
Date: 2010-12-21
User Name: Ian Macdonald
Action: Updated

Change History
Date: 2007-04-04
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok
Verified still correct for audience - currently set to contract
Audience left at contract as per FvF at
http://kmo.central/howto/content/voyager-contributor-standards.html
Checked review date - added 1yr to make it 2008-03-28
Checked for TM - ok as presented
Publishing under the current publication rules of 18 Apr 2005:
Version: 10
Date: 2007-04-02
User Name: 31620
Action: Accept
Comment:
Version: 0


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback