SMTP: Data 421 Message Rejected

This morning we noticed some strange issues with email’s and delays in messages arriving. A quick check of the Exchange SMTP queues and the Mail Marshal queue found nothing, none of our messages were sitting on a server waiting to be delivered. I checked the queues 30min later and the Mail Marshal queue had blown out and had 80 messages from 70 domains waiting to be sent?!

MM_Mail_Queue_sml

A quick look at the mail history in Mail Marshal revealed the SMTP error, Data 421 Message rejected!

MM_Mail_History_sml

A quick search in Google found that the clever people on the Whirlpool forum had the problem solved. Dangermouze had found that the issue was with the Bigpond mail servers and their anti-spam settings. This started to make sense… a few weeks ago we added a secondary Internet connection to our Sonicwall firewall and configured the load balancing for the outgoing web requests. We had some issues with emails trying to go out on the new internet connection and failing because there was no reverse DNS and secondary MX server configured yet for that connection. Our workaround was to set the mail.bigpond.com server as our forwarding SMTP server which seemed to fix the problem, the Sonicwall would use our Telstra ADSL2 connection to send to this address and wouldn’t attempt to send mail on the Cable connection!

Word is that if too many emails are sent via the Bigpond mail server in a short period of time, they will temporarily block forwarding email from your address for 20min or so, then let you try again. This appears to be a restriction on the Bigpond Home ADSL plans, generally, BigPond Members can’t send more than 20 emails in 10 minutes and they can only be sent using the BigPond mail servers. however we’re on a Business Broadband connection, and appear to have the same limitation.

Dangermouze’s Telnet test to Bigpond SMTP

heres the a ‘telnet mail.bigpond.com 25’ session
220 oaamta03ps.mx.bigpond.com esmtp server ready wed,6 feb 2008 22:32
helo
250 oaamta03ps.mx.bigpond.com
mail from: ***@bigpond.net.au
421 message rejected

The telnet session confirms that Bigpond is the source of the 421 message rejection, not the destination server or an RBL type service.

We may have to confirm out Bigpond settings with our account manager….

iTunes -9808

I came across an interesting problem today while trying to subscribe to a podcast through iTunes where iTunes threw up an error (-9808) saying an unknown error had occurred.

9808

I’ve used iTunes on this machine (Vista SP1) a fair bit and have had no issues with downloading podcasts before, however, I was logged in as a test user and wasn’t using my normal user account. Some quick checking found that it wasn’t our Internet Content Filter causing the problem, but did find this message in our ISA firewall log:

Failed Connection Attempt
Log type:
Web Proxy (Forward)
Status: 995 The I/O operation has been aborted because of either a thread exit or an application request.
Destination: External (17.250.237.19:443)
Request: buy.itunes.apple.com:443
Filter information: Req ID: 1b5d88f0; Compression: client=No, server=No, compress rate=0% decompress rate=0%
Protocol: SSL-tunnel

Searching for status 995 and ISA in Google didn’t bring up any useful results, but a search for iTunes and 9808 bought up a a heap of results. Turns out this is a reasonably common problem and found the solution at soccerislife8 and disabled Check for server certificate revocation in Internet Explorer.

9808 IE Setting

After some more research it seems that updating to the latest version of iTunes won’t fix the problem?!

Apple_SSL

Checking Apple’s SSL Certificate in IE shows that its valid so its a still a mystery. I’m not impressed that I’ve had to disable security features in my browser for the sake of iTunes

ProCurve – Front-Panel Security & Authentication

I was looking for some ProCurve documentation on AAA security and stumbled across the Hardening ProCurve Switches White Paper and found a few nice things to add to our ProCurve config.

Password Clear Protection – Front-Panel Securitylogo_procurve_networking_by_hp
ProCurve devices utilize the Reset and Clear buttons on the front panel to help users reset the switch configuration to factory default or to reset the console password. This capability creates a security risk anywhere it’s impossible to  prevent physical access to the switch. ProCurve makes it possible to disable this functionality to protect from malicious use of these features.

There are two components to front-panel security: “password clear” and “factory reset.” Both must be disabled to fully secure the device.

In the switch’s default mode, a malicious user can utilize the front-panel clear button to reset a console password stored locally on the switch. To disable this feature, issue the command:

ProCurve Switch(config)# no front-panel-security password-clear

The other capability built into ProCurve switches is the ability to reset the switch configuration to the factory default mode:

ProCurve Switch(config)# [no] front-panel-security factory-reset

Executing this command prevents reset of the switch configuration by use of the front-panel Reset and Clear buttons.

It’s critical to understand that disabling these features severely restricts administrator options if the password is lost or forgotten. Before making these changes, users are strongly encouraged to review all considerations outlined in the Access and Security Guide for your model.
wireless_edge_services_zl_module
Authentication – Server-Supplied Privilege Level
Login privilege level instructs the switch to accept the authenticating user’s command level (manager or operator) that is supplied by the server. This allows manager-level users to skip the login context and proceed immediately to enable context, thus eliminating the need for a manager-level user to login twice.

To allow the switch to accept the privilege level provided by the server, use the following configuration command:

ProCurve Switch(config)# aaa authentication login privilege-mode

To supply a privilege level via RADIUS, specify the “Service-Type” attribute in the user’s credentials.
• Service-Type = 6 allows manager-level access
• Service-Type = 7 allows operator-level access
• A user with Service-Type not equal to 6 or 7 is denied access
• A user with no Service-Type attribute supplied is denied access when privilege mode is enabled

– The Radius Authentication for switch access sounds interesting. If our Staff are using their network credentials to access the switch config, or contractors that are working on the network, we can easily enable/disable their access to the switches without hassle and letting everyone know the Manager/Operator passwords

HP 2710p Battery issues resolved

Just over 12 months ago we purchased 55 HP 2710p Tablets with Vista Business for our Teaching Staff. The machines have generally been pretty good but we had some unsolvable battery issues that we couldn’t solve ourselves and eventually opened a support case with HP to try and rectify. We had various problems with batteries not holding much, or any charge and some machines that wouldn’t recognise their battery at all and would only work with the AC adapter connected to the power. If we swapped batteries around between machines they would start to work normally again and the battery would charge and be usable, however, it wouldn’t be long before the machine would have battery issues again.

HP Support got us to run the Battery Check and Health Check on some effected machines as well as machines that hadn’t had any battery issues and send them the .XML files that were generated for their engineers to check. We also sent them the .nfo System Info files from MSINFO32.exe for these machines.

hpbc
C:\Program Files (x86)\Hewlett-Packard\HP Battery Check\hpbc.exe

hphc
C:\Program Files (x86)\Hewlett-Packard\HP Health Check\hphc.exe

Running these two applications generates two logs files that are stored under HP Active Support
C:\Program Files (x86)\Hewlett-Packard\HP Active Support\Logs

Battery Check Results: HealthCheckBC.xml

   1: <?xml version="1.0"?>
   2: <HC_BCheck Generated="17/10/2008 11:25:39 AM">
   3:   <Battery>
   4:     <HealthStatus SerialNumber="2CE7412ZL5">Test Passed</HealthStatus>
   5:     <TestResult>0</TestResult>
   6:     <DesignCapacity>4000</DesignCapacity>
   7:     <FullChargeCapacity>3791</FullChargeCapacity>
   8:     <RemainingCapacity>1163</RemainingCapacity>
   9:     <StorageCapacity>98.9473684210526</StorageCapacity>
  10:     <MaxError>0</MaxError>
  11:     <CycleCount>1</CycleCount>
  12:     <Temperature>23</Temperature>
  13:     <TerminalVoltage>11077</TerminalVoltage>
  14:     <Current>0</Current>
  15:     <DesignVoltage>11100</DesignVoltage>
  16:     <BatteryManufactureName>HP                </BatteryManufactureName>
  17:     <Status>128</Status>
  18:     <CellVoltage1>0</CellVoltage1>
  19:     <CellVoltage2>3688</CellVoltage2>
  20:     <CellVoltage3>3700</CellVoltage3>
  21:     <CellVoltage4>3700</CellVoltage4>
  22:     <BatteryACPower>1</BatteryACPower>
  23:     <BatterySupportedCount>2</BatterySupportedCount>
  24:     <SerialNumber>00577 2008/04/10</SerialNumber>
  25:     <satId>00577</satId>
  26:     <ManufactureDate>04/10/2008</ManufactureDate>
  27:     <Source>1</Source>
  28:     <Table>0</Table>
  29:     <SubTable>0</SubTable>
  30:     <InWarranty>False</InWarranty>
  31:     <WarrantyID>12ZL5-18100-18287-2CE74-00000-01</WarrantyID>
  32:   </Battery>
  33: </HC_BCheck>

HP Health Check Results: HealthCheckAC.xml

   1: <?xml version="1.0"?>
   2: <HC_ACheck AC_Server="h20397.www2.hp.com" Generated="25/08/2008 12:13:32 PM" HealthStatus="Poor">
   3:   <ISSUE GUID="10007315-0281-0514-8344-020194660001">
   4:     <STATUS>Detected</STATUS>
   5:     <QA>True</QA>
   6:     <URLRESULT>
   7:     </URLRESULT>
   8:     <FREEINFO>
   9:       <CATEGORY>Maintenance</CATEGORY>
  10:       <PERSISTANT value="always" timestamp="" />
  11:       <ALERT>Please update HP Health Check by clicking on REPAIR and following the instructions.</ALERT>
  12:       <SYMPTOM>HP Health Check update available.</SYMPTOM>
  13:       <SEVERITY>Alert</SEVERITY>
  14:     </FREEINFO>
  15:   </ISSUE>
  16:   <ISSUE GUID="10007315-0281-0514-8344-020194660047">
  17:     <STATUS>Detected</STATUS>
  18:     <QA>True</QA>
  19:     <URLRESULT>
  20:     </URLRESULT>
  21:     <FREEINFO>
  22:       <CATEGORY>Security</CATEGORY>
  23:       <PERSISTANT value="always" timestamp="" />
  24:       <ALERT>There is a critical security update available for HP Quick Launch Button software. This update removes a security vulnerability by disabling HP Info Center.  Click the GREEN button to apply the security update.</ALERT>
  25:       <SYMPTOM>HP Quick Launch Buttons security update available.</SYMPTOM>
  26:       <SEVERITY>Alert</SEVERITY>
  27:     </FREEINFO>
  28:   </ISSUE>
  29: </HC_ACheck>

The Health Check managed to find that the machine’s were missing an update for the HP Quick Launch buttons, but didn’t find that there was an updated BIOS available for the 2710p. The HP Health check seems to be pretty good at finding updates for HP software and drivers, but not so good at finding and recommending firmware updates. The issue has been resolved by updating to the latest BIOS, which for us was F.13, F.14 is now available. All machines that had experienced battery problems have now received the BIOS update, and have not had any problems with batteries holding their charge or not being detected since then.

Mic Check // Oh Wait a minute now…

Over the last 12 months since we’ve installed our J9051A ZL Wireless Edge Services Module (WESM), we’ve had some intermittent issues with some of our wireless notebooks causing the WESM to freak out and run at 100% CPU and boot all of our wireless stations of the Wireless network. These notebooks work fine on the WLAN 99% of the time but every now and then they freak out and cause problems with the TKIP integrity check.

The notebooks that we’ve had trouble with have had either an Intel or Broadcom wireless NIC:

  • Acer 3230 with WLAN: integrated Intel® PRO/Wireless 2200ABG
  • HP 1100 Tablet with WLAN: Intel PRO/Wireless LAN 2100 3B Mini PCI
  • Motion Computing Tablet with WLAN: Broadcom Wireless

We have many other 3230’s on the WLAN and one other Motion tablet that are identical to the machines that we’ve had issues with, but no other machines have caused the TKIP failure. We’ve updated drivers for the wireless NICs and installed all Windows updates and still haven’t been able to correct the problem?

When the TKIP failure occurs the CPU on the WESM hits 100%, see below, while it tries to perform the TKIP Countermeasures. TechDuke has a great explanation of the TKIP Message Integrity Check (MIC), and explains that when a wireless station fails the MIC, or Michael, hash check twice within 60 seconds then all wireless stations are booted off the wireless network for a minute and forced to reconnect/re-authenticate. Zack de la Rocha was way ahead of his time when he wrote Mic Check, he explains the MIC failure perfectly…

Rage Against The Machine – Mic Check (The Battle of Los Angeles (1999))
Mic Check
Oh Wait a minute now
Ha ha ha
Come on
Wait a Minute Now
Check

WESM_CPU_Usage
The Diagnostic page on the WESM showing that the CPU had been running at 100%, as soon as we disabled Dial-in access in Active Directory for the offending notebook we broke the Radius authentication and the WESM went back to running as normal.

Wireless Edge Service Log

   1: Feb 06 11:27:46 2009: %CC-4-TKIPCNTRMEASSTART: TKIP countermeasures started on wlan 1
   2: Feb 06 11:28:15 2009: %MGMT-4-OTHERREQQUED: request queued in delegated requests
   3: Feb 06 11:28:46 2009: %CC-4-TKIPCNTRMEASEND: TKIP countermeasures ended on wlan 1
   4: Feb 06 11:28:47 2009: %CC-4-TKIPMICCHECKFAIL: TKIP message integrity check failed in frame on wlan 1
   5: Feb 06 11:28:47 2009: %KERN-3-ERR: mic check failure <00-13-CE-04-FB-4A>. (pkt_len 360 prio: 0) rx: <2B-2B-02-DC-00-FF> calc: <A7-CE-2B-B8-45-C6>.
   6: Feb 06 11:28:51 2009: %CC-4-TKIPMICCHECKFAIL: TKIP message integrity check failed in frame on wlan 1

Checking the message log on the WESM, we could identify which machine was failing the MIC and which WLAN they were connected to. Line 5 shows the MIC check failure and the MAC address of the offending machine.

dhcp

We traced the offending MAC address back to its owner via the DHCP console and disabled Dial-in access for the computer and on the user account of its owner. This causes WLAN Radius authentication to fail the EAP-TLS auth because a valid certificate and dial-in access are required for access to that particular WLAN.

Currently we’re still running the original firmware wt.01.03 that came with the ZL module, but will update to wt.01.15 shortly and test these machines on the WLAN to see if the updated firmware can handle integrity check failure with a little more grace than the original firmware.

HP Case Study – Ballarat Grammar

thm_ballarat_grammerHewlett Packard have just release a Case Study on the hard work that we’ve done over the last year or two with them, and our HP reseller Trident. Check it out here.

The Case Study explains some of the challenges that we had with our previous network, servers and workstations, and how HP and Trident helped us find a solution that would help us overcome these challenges.

As well as the HP Case Study, earlier this year HP ProCurve released a Case Study on our migration from Cisco/Alloy switches to ProCurve, Wireless Edge Services and 802.1x port security. The Press Release Foundersis here on CIO. With a lot of help from Lisa and Fotios we’ve been able to develop our network, provide a 10Gb fibre backbone and much improved services for Staff and Students, including our Boarders on the wireless network, using the Wireless Edge Services Module (WESM). Expect to see some How-To’s posted soon on some of the funky things that we setup with our HP gear, especially the 802.1x, the WESM and our guest wireless network.

All of the work discussed in these case studies is obviously a team effort, and wouldn’t have been possible without the hard work and planning from Des, Nathan B, Nathan H, Leon and Rian.

* Photo of Ballarat Grammar by Rob Olston

Project 2009 Rollout

Follow Nathan as he blogs our 2009 Desktop rollout here. Track our progress as we unpack, assemble and configure 187 new Rollout2009HP 7800 Ultra Slim Desktops and install around the School. To help us, we have a team of Students working with our IT Staff to take the 28 pallets of gear that arrived on two trucks on Monday, and over the next week or so, and unpack the boxes, assemble the HP machines on their desktop stands, and position around the School.

A major part of our new rollout process is using Altiris to image our machines. Previously we’ve used Ghost for all our imaging but have been disappointed with post-sysprep functionality. Altiris, which has recently been acquired by Symantec, provides all the functionality that Ghost *should* have. As we become more familiar with Altiris and the different add-ons that we purchased, like SVS, I’ll post interesting snippets and How-To’s on things we’ve discovered.

So far the only issues we’ve had with the imaging process has been re-imaging older systems around the School. We have two labs of IBM clones with MSI motherboards that have been troublesome. We’ve had issues getting them to network boot, PXE, and also a strange issue with multicasting one of the labs. Altiris’ multicast works by selecting a master machine for the imaging session, and copying the image from the Altiris server to the master machine. Then from the Master the image is sent, multicast, to the the other machines in the session. The issue we had was that after session got to around 10% the Slave machines would freeze, however the Master machine kept on Imaging. The error message on the Altiris console seemed unrelated to the actual problem, something to do with a problem with the subst command!? As always, Rian solved the problem and improvised, adapted and overcome. He set the machines to start imaging 5 minutes apart, effectively running a unicast to each machine in the lab, and after an hour or 3 the lab was successfully imaged.

Will update as we go

Scripting Switch Configuration Backup

Here’s is a short VBS script which telnet’s into your ProCurve switch and sends a config backup to your TFTP Server. The code can easily be changed to telnet into pretty much any device that supports configuration via telnet.

This code is a modified version of a snippet posted on the VBForums

Dim objShell
Dim objNetwork

Set objNetwork=CreateObject("WScript.Network")

strTitle="Telnet Demo"
strDefaultServer="Server01"
strDefaultUser=objNetwork.UserDomain & "\" & objNetwork.UserName
strDefaultPassword="P@ssw0rd"

strComputer=InputBox("What server or device do you want to connect to?",_
strTitle,strDefaultServer)
If Len(strComputer)=0 Then WScript.quit



strPassword="password"

Set objShell=CreateObject("wscript.shell")
'Start Telnet
objShell.Run "Telnet " & strComputer
'Give app a chance to get started
WScript.Sleep 5000
objShell.AppActivate "Telnet " & strComputer

'Send login credentials
objShell.SendKeys strUsername & "~"
WScript.Sleep 2000
objShell.SendKeys strPassword & "~"
WScript.Sleep 2000

'Send commands
WScript.Sleep 200
objShell.SendKeys "~"
WScript.Sleep 200
objShell.SendKeys "copy startup-config tftp 172.16.1.15 "& strComputer &"_config.txt"
WScript.Sleep 1000
objShell.SendKeys "~"

'give lengthy commands time to finish
'WScript.Sleep 10000

'make sure we get window again
objShell.AppActivate "Telnet " & strComputer
'run another command
'objShell.SendKeys "net share"
'WScript.Sleep 200
objShell.SendKeys "~"

'Close session
'make sure we get window again
objShell.AppActivate "Telnet " & strComputer
objShell.SendKeys "exit"
WScript.Sleep 200
objShell.SendKeys "~"
objShell.SendKeys "exit"
WScript.Sleep 200
objShell.SendKeys "~"
WScript.Sleep 200
objShell.SendKeys "y"
objShell.SendKeys "~"
WScript.Sleep 200
objShell.SendKeys "~"

Save this text in a .vbs file and run via “cscript switchbak.vbs“ from the command line

If your modifying the script to run on something other than a ProCurve switch ,you may have to tweak/add/remove the Sleep and SendKeys ”~” . Using the SendKeys and the tilde will send a carriage return to the telnet session

Also, if you’d like to run this script you will need a TFTP server, free download from Solawinds

To make the back script a useful tool I’ve set it to run and query an MS SQL database to get the addresses for our ProCurve switches and have scheduled it to run regularly. I will post an update with how I’ve set that up sometime soon. The Script is essentially the same but I’ve removed the prompt for the device address and added the database connection query, will post the details shortly

If you have setup the ProCurve Manager then you may find this post redundant, but, I’ve found it to be a handy script to have, and send backup config files to a server where they are easily accessible in a disaster, hopefully…

Vista bug – Deletes Inactive Profile

vista Sometime ago now, but still worth sharing, we had an issue with our Vista tablets for Staff. The issue was with Vista, pre SP1 we think, and a Group Policy setting for deleting an inactive profile after 30 days. This GPO setting was a legacy setting that we had on the network to delete Student profiles on network machines that weren’t removed when they logged off.

After successfully rolling out the notebooks to staff, we think about a 30 days after the imaging, we had 4 panicked Staff call the IT Helpdesk within minutes of each other. Their machines had fouled up and restarted and when they logged in they had a fresh profile and all of their documents and email had disappeared!

After a some quick Googling we found Dave’s post on his blog and he’d had exactly the same experience. This is straight from Dave Says:

“Seems the domain controller software has a (Y/N) parameter to delete old profiles that have not been used for 30 days or more.
If set to Y, the software screws up when a terminal logging in is running either Vista or Server 2008 OS. In these instances, it sometimes concludes the current user profile has been inactive for 30 days & deletes it!

Solution is have your admin set parameter to N – apparently there was a note floating around back in the beta days last year – thanks for publicising it guys!”

Thanks to Dave, we immediately change the GPO setting and, luckily, didn’t have any more problems. It was interesting that we only had 4 notebooks with the problem, if it was all 55 we would have been in trouble, but this is what happens when you dive into a new OS I suppose…

More info from Dave Says

DL380 – HP Insight Manager Goodness

Over the weekend I had the opportunity to experience the HP Insight Manager goodness. We were on our way to Melbourne to go shopping for they day, early Christmas shopping, and about half way there I received an email from one of our servers, “IDM”, which had detected a drive failure. The drive that failed is part of a RAID5 array so we could replace the disk and it should rebuild successfully, as long as we could replace the drive before another disk failure!

We have seen a few disk failures before on the DL380 servers and and have had no issues with replacing the disks and DL380rebuilding them, but it was only recently that we started updating all the servers with the latest firmware and configuring them to send alerts on failures. So this was the first time we’d seen the email alerts for a disk failure, which obviously meant that we could deal with it straight away instead of waiting for someone to notice the RED light on the failed disk when they were in the server room.

With the drive failure occurring  on the weekend, and as I was an hour or so away, we had to do a quick call out to our IT Staff to see who was available to perform the disk swap. As luck would have it, someone was heading in to catch up on a few hours and was only a few minutes away. This particular member of Staff is our web developer and has pretty good knowledge of hardware but hasn’t had experience with our DL380 servers before. So, over the phone, I talked him through changing the disks over and starting the rebuild process. When we had our first disk failure on a DL380 we found it hard to find documentation on what to do, and this was probably because it was so easy and that we didn’t expect the RAID controller to do so much of the work by itself.

All Jeff had to to was unpack a new drive from its box, removed the failed drive and then insert the new disk. The new disk is already boxed inside its caddy, ready to slide into the server. So there’s no need to find a screwdriver and remove the disk and insert the new one in the caddy. After inserting the new disk the raid controller detects the disk, initialises and then begins the rebuilding process. This particular RAID array wasn’t too large and took less than an hour to rebuild, and as every change in disk status occurred, the server detected the change and sent a notification message. So as Jeff was replacing the disk, I was getting the notification messages instantly on my phone.

I’ve included the emails from the Insight Manager below. At the moment we only a few of our DL380s with the current firmware and Insight Manager, this is because of a problem we found with the SCSI backplane and the newer firmware. The latest update caused a problem where the Status LED’s on the SCSI disks fail to light up, green or red, for one of the disks in the server. We held off on continuing with the firmware updates but may reconsider that for the moment when we get such comprehensive information from the Insight Manger and alert emails it seems like the gains out weigh the inconvenience of LED issues.

Initial email – detected drive failure
—————————————————————————————————————————–
From: <ProLiant@>
Date: Sat, 22 Nov 2008 09:31:01 +1100
Subject: Storage Agents: Physical Drive Status Change

The system has detected the following event:
SNMP Trap:      3046
Date time:      11/22/2008  09:31:00 AM
Computer:       IDM
Source:         Storage Agents
Type:           Error
Category:       (4)
Description:
A ‘Physical Drive Status Change’ trap signifies that the agent has detected a change in the status of a drive array physical drive.
Details:
IDA Physical Drive Status ‘FAILED’
Drive Type 2
Location  ‘SCSI Port 1 Drive 3’
Error Code 13
Bus # 1
Controller Slot # 2
Model ‘COMPAQ  BD14689BB9      ‘
Serial Number ‘DAA1P6909WNS0637’
Firmware Revision ‘HPB1’

Second Email –new disk inserted and initialised ‘OK’
—————————————————————————————————————————–
From: <ProLiant@>
Date: Sat, 22 Nov 2008 11:47:07 +1100
Subject: Storage Agents: Physical Drive Status Change

The system has detected the following event:
SNMP Trap:      3046
Date time:      11/22/2008  11:47:06 AM
Computer:       IDM
Source:         Storage Agents
Type:           Informational
Category:       (4)
Description:
A ‘Physical Drive Status Change’ trap signifies that the agent has detected a change in the status of a drive array physical drive.
Details:
IDA Physical Drive Status ‘OK’
Drive Type 2
Location  ‘SCSI Port 1 Drive 3’
Error Code 0
Bus # 1
Controller Slot # 2
Model ‘COMPAQ  BF14684970      ‘
Serial Number ‘        J4W1PB3C’
Firmware Revision ‘HPB5’

Third Email – new disk is being rebuilt in the RAID5 array
—————————————————————————————————————————–
From: <ProLiant@>
Date: Sat, 22 Nov 2008 11:47:07 +1100
Subject: Storage Agents: Logical Drive Status Change

The system has detected the following event:
SNMP Trap:      3034
Date time:      11/22/2008  11:47:06 AM
Computer:       IDM
Source:         Storage Agents
Type:           Warning
Category:       (4)
Description:
A ‘Logical Drive Status Change’ trap signifies that the agent has detected a change in the status of a drive array logical drive.
Details:
IDA Logical Drive Status ‘REBUILDING’
Logical Drive # 2
Controller Slot # 2

Fourth Email – all done, RAID rebuilding complete and disk is OK, back to normal
—————————————————————————————————————————–From: <ProLiant@>
Date: Sat, 22 Nov 2008 12:37:07 +1100

Subject: Storage Agents: Logical Drive Status Change

The system has detected the following event:
SNMP Trap:      3034
Date time:      11/22/2008  12:37:07 PM
Computer:       IDM
Source:         Storage Agents
Type:           Informational
Category:       (4)
Description:
A ‘Logical Drive Status Change’ trap signifies that the agent has detected a change in the status of a drive array logical drive.
Details:
IDA Logical Drive Status ‘OK’
Logical Drive # 2
Controller Slot # 2

After reading Mick Liubinskas’ post on ‘How I Blog’ I thought I’d try a quick and nasty, two beer post with minimal spell checking and absolutely no grammar checking or proof reading…..