|
April 2010 |
Note: This article is a follow-on from "Setting up Email Alerts from IPMI": http://www.compucon.co.nz/content/view/623/139/
Below is an example case for the purposes of illustrating what happens when email alerts from IPMI have been configured. The failure below was triggered by simulating a faulty fan. The fan was removed from the FAN4 header while the system was live (Event 1). It was later re-connected (Event 2).
The emails are in reverse chronological order. 3 emails were sent per event.
Legend:
Event Direction: Assertion = an event has happened
Event Direction: Deassertion = an event that has happened has been resolved
Event Description: LNC = Lower Non-Critical
Event Description: LC = Lower Critical
Event Description: LNR = Lower Non-Recoverable
-----Original Message-----
From:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
[mailto:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
]
Sent: Thursday, 8 April 2010 1:16 p.m.
To:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Subject: Informational Test Subject
Informational Test Message
IP : 192.168.1.53
SEL_TIME:"2010/04/08 13:13:46"
SENSOR_NUMBER:"44"
SENSOR_TYPE:"Fan "
SENSOR_ID:"FAN 4 "
EVENT_DESCRIPTION:"LNC_Going Low "
EVENT_DIRECTION:"Deassertion"
EVENT SEVERITY:"information"
-----Original Message-----
From:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
[mailto:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
]
Sent: Thursday, 8 April 2010 1:15 p.m.
To:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Subject: Informational Test Subject
Informational Test Message
IP : 192.168.1.53
SEL_TIME:"2010/04/08 13:13:46"
SENSOR_NUMBER:"44"
SENSOR_TYPE:"Fan "
SENSOR_ID:"FAN 4 "
EVENT_DESCRIPTION:"LC_Going Low "
EVENT_DIRECTION:"Deassertion"
EVENT SEVERITY:"information"
-----Original Message-----
From:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
[mailto:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
]
Sent: Thursday, 8 April 2010 1:15 p.m.
To:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Subject: Informational Test Subject
Informational Test Message
IP : 192.168.1.53
SEL_TIME:"2010/04/08 13:13:46"
SENSOR_NUMBER:"44"
SENSOR_TYPE:"Fan "
SENSOR_ID:"FAN 4 "
EVENT_DESCRIPTION:"LNR_Going Low "
EVENT_DIRECTION:"Deassertion"
EVENT SEVERITY:"information"
-----Original Message-----
From:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
[mailto:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
]
Sent: Thursday, 8 April 2010 1:13 p.m.
To:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Subject: Informational Test Subject
Informational Test Message
IP : 192.168.1.53
SEL_TIME:"2010/04/08 13:11:31"
SENSOR_NUMBER:"44"
SENSOR_TYPE:"Fan "
SENSOR_ID:"FAN 4 "
EVENT_DESCRIPTION:"LNR_Going Low "
EVENT_DIRECTION:"Assertion "
EVENT SEVERITY:"information"
-----Original Message-----
From:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
[mailto:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
]
Sent: Thursday, 8 April 2010 1:13 p.m.
To:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Subject: Informational Test Subject
Informational Test Message
IP : 192.168.1.53
SEL_TIME:"2010/04/08 13:11:31"
SENSOR_NUMBER:"44"
SENSOR_TYPE:"Fan "
SENSOR_ID:"FAN 4 "
EVENT_DESCRIPTION:"LC_Going Low "
EVENT_DIRECTION:"Assertion "
EVENT SEVERITY:"information"
-----Original Message-----
From:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
[mailto:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
]
Sent: Thursday, 8 April 2010 1:13 p.m.
To:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Subject: Informational Test Subject
Informational Test Message
IP : 192.168.1.53
SEL_TIME:"2010/04/08 13:11:30"
SENSOR_NUMBER:"44"
SENSOR_TYPE:"Fan "
SENSOR_ID:"FAN 4 "
EVENT_DESCRIPTION:"LNC_Going Low "
EVENT_DIRECTION:"Assertion "
EVENT SEVERITY:"information"
Screenshot of Event Log from IPMI Web GUI:
|
|
|
April 2010 |
The University has assigned 2 BTECH final year students to our company for training and research. The theme is on Video Surveillance.
Semester 1 is scheduled for learning the state of art
Semester 2 is scheduled for pushing the envelope
This article will be updated as more progress information is available.
|
|
|
April 2010 |
Error message about hardware-assisted virtualization for Windows XP Mode in Windows Virtual PC on a computer that is running Windows 7 has been published in a Microsoft KB article 977206.
Based on this article, Microsoft now support non HAV processors under Windows 7 Virtual PC / Windows XP Mode.
APPLIES TO
* Windows 7 Enterprise
* Windows 7 Professional
* Windows 7 Ultimate
Please see: http://support.microsoft.com/?kbid=977206
UPDATE PACKAGES can be found in the C:\Compucon\Applications\Microsoft Windows XP Mode for Windows 7 folder.
|
|
|
April 2010 |
This is a procedural guide to setting up Email Alerts via IPMI.
Step 1) Log into the IPMI Web Management GUI to configure the settings. You will need to point your web browser to the IP address of the dedicated IPMI NIC port on the server. The default setting is DHCP so check its assigned IP address by going into the motherboard BIOS setup (by pressing Del key on power-on during POST). You will find IPMI settings under Advanced (as depicted in the following screenshots).
** You should consider setting a STATIC IP address so it never changes:
The IP address, Subnet Mask and Gateway Address must be correct for IPMI to work correctly. Please leave the default MAC Address as the default address is correct.
Step 2) Once you have logged in, go to Configuration and configure SMTP settings:
Set the correct IP address and SMTP port (default is 25) for the local Email Server as shown in the screenshot above. If the SMTP outgoing mail server does NOT require a username/password, please leave these fields BLANK - otherwise it may not send emails correctly.
Step 3) Go to Configuration -> Alerts to configure Alert settings. You will be presented with a page listing of Alerts. Select to highlight Alert#1 as shown:
** And click on Modify - you will be presented with the following screen. Fill in the details - an example is shown:
Remember to click Save to save the details. The email address entered should be "
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
" for the Compucon IPMI team to receive email alerts. You can configure Alert#2 by repeating this step for Informational emails to be sent to another email address. The Destination IP can be left 000.000.000.000 or your preferred IP address if you wish to set up an SNMP Trap system.
Step 4) Select the Alert you have just configured and click on 'Send Test Alert' to test the configuration you have just set. You should receive a Dummy Test Alert email at the email address you have entered.
If you do not, please re-check all the settings covered by this guide.
Step 5) Finally, please check and set the correct Time and Date for any error messages to be logged and sent with the correct date and time stamp. You can do this by going to Configuration -> Date and Time. Enabling NTP is optional and not necessary - you can just set the correct Date and Time.
This procedure has been reviewed and tested by the Compucon team on 7 April 2010 on an X8-generation Compucon Workgroup Server. Example email alerts have been documented in a follow-on article: http://www.compucon.co.nz/content/view/626/139/
|
|
|
April 2010 |
There are currently many ways to create an iSCSI SAN Storage
Appliance/Server. Out of the freely available options, FreeNAS and
OpenFiler are popular choices. This guide introduces FreeNAS as a
solution.
First of all, one of the benefits of FreeNAS is its
small footprint; it can be installed onto a USB flash drive/dongle and
the appliance can be booted off the USB flash drive directly.
Installation
Download
the FreeNAS ISO from http://freenas.org and burn the ISO onto a CD.
Boot off this CD and you can select an option to "Install 'embedded' OS
on HDD/Flash/USB". For more info: http://freenas.org/documentation:setup_and_user_guide:installing_freenas_on_disk
A conceptual view of the appliance is shown here:
iSCSI
SAN
An iSCSI implementation simulates the presence of a
local SCSI hard drive across an IP network. There are 3 main components:
iSCSI
Target - the image of a disk stored on the Storage Server
iSCSI Disk - the virtual disk presented and simulated by the
iSCSI Target
iSCSI Initiator - an emulated SCSI controller that connects to
'iSCSI Disks' across an IP network
Implementation
An example implementation is presented below.
In this example, the FreeNAS appliance provides an iSCSI Target for the
Server to access as a D:\ Drive.The D:\ drive will appear to be a local SCSI disk even though the files are stored within an image located on the FreeNAS server. As depicted in the image, a separate GbE network is recommended for iSCSI traffic for the optimum performance.
The above scenario has been set up and tested by the Compucon team. It is designed to support multiple servers accessing their own individual iSCSI Target stored on the same FreeNAS server. The data should be treated as local to each server and so the backup plans should involve a separate architecture with the use of local tape drives or Shadow Protect etc.
|
|
|
|
<< Start < Prev 201 202 203 204 205 206 207 208 209 210 Next > End >>
|
| Results 1873 - 1881 of 2511 |
