As of now (OME1.2) we don’t have specific feature to monitor the hard disk status. But we do have feature that will intimate you the hard disk status in terms of alerts.
OME has Alert Actions feature, if you configure “Alert Email Action” as per the requirement you will get notified by an email about hard disk status of specific group of servers. This may help you to get the hard disk status of specific group of servers.
While configuring Email alert action as per your specific requirement please take care of –
1)Severity Association: Warning, Critical.
2)Category and source Association : In this case select “Physical Disk”
3)Device Association: Since you want specific group of device so associate your own created device group.
Note: Email setting need to be configure with SMTP server IP to receive an email.
By the way I have configured the warranty status report to be sent automatically via my OME
1.In that ome auto generated report service tag is missing in the several devices
What would be the background of it to missing service tag in the report and how do I overcome the situation?
Note - Service tag missing devices are not recognized as servers and no service start and end date and device type model also detected in Reports->Warranty information all devises list
2.Also is it possible to classify the machines impotence in low, medium and high categories?
1. So you have a server device(s) that is not classified and missing the service tag data. Is that correct? If so, please try the Dell Troubleshooting Tool against that device. If you run the SNMP test, the result set should indicate the version of Server Administrator that is on the box. If that is detected, you should get the server classified. If it is another device or another protocol, let me know and we can go from there.
2. No real way to classify low/med, etc. You might create a custom group called "Low" and then create your alert filter against that group. But I'm not clear on your objective here.
Hi Rob, sorry for the delayed reply. 1. the issue was due to old idrac firmware and wrong password which causes the blank service tag on the warranty report and now it is fixed. by the way if we install OMSA on the dell server hardware what is the protocol we can use in ome to discover the servers ? I guess we can use the same idrac ip to discover OMSA installed servers and manage the server via ome server ? and apply the server firmware via OMSA client.? (update method) 2. I was referring to categorized the warranty report as per the priorities like low priority server under one report or under separate sheet on the same report like wise to classify in the report. thanks dnet.
If you use OMSA on the server, discover it with SNMP or WMI. But with WMI I think you will not get some of the storage data. Of course with OMSA you will discover the server IP itself. Not the Drac. For iDrac6/7 you can discover the iDrac IP via WSMan.
Interesting suggestion on warranty. Can we discuss more? So how do you think you would classify a low priority server? Would you go in and select each server to classify it H/M/L?
I passed along the request you had on H/M/L. But I'm not clear, as a user, how you would like to 'mark' a server high or low, etc. In the GUI, how would you like to do this as a user?
On the warranty, there might be some duplication if warranties expire and are extended under a new service code for the same device. Or there might be multiple warranty service codes that are assigned to a single service tag. Some of this is expected. If you open a ticket the support team can take a screen shot and forward it to the dev team to see if there are other duplicated records that are not expected and need to be fixed.
Hi Rob, Thanks for the prompt reply. What I would like to see is in the warranty report to get categorized the report H/M/L for warranty renewal ..so then we can go ahead and extend the warranty on High priority servers instead of going through the full report. In fact it is good to have a report in generation wise server list / report as well. Categorizing can be made upon the H/M/L - How critical is that particular server/service to be fully compatible in all the time. It is great if we can see the "H" priority server in GUI - High priority servers missing firmware listed in a separate column in the general pie chart (if possible) ex in the same device by status chart. I guess we can do that at least if there is a way for us to mark the servers as critical H/M/L in the system (once after the scanned) let me know if you need further clarification. thanks and regards dnet
What are the possible scenarios that the dell ome does not show up the warranty information on the Reports –> Warranty Information page? “System names, service tag, device type are already detected with the model etc.”
But , It does not show the Service level code and the days remaining, start date ,end date on the report?
Note
Ome server has internet access, with no proxy
I just check the warranty for one of the Service tag via dell troubleshooting tool and it show up the full details of warranty
Hello The issue here is I cannot receive alerts via my ome server I have installed the omsa on my servers Snmp enabled on omsa – community name public Ome server can reach omsa installed server via snmp from troubleshooting tool. However whn I test the snmp trap from omsa ..ome server does not listen. Thanks dnet
To get warranty data under warranty information report, server should be inventoried with valid service tag. If the server is only discovered then warranty data will not populate under warranty report. Please check and run the discovery and inventory of your server together and also check OME is able to connect warranty web page.
DELL-Nitin Bh
43 Posts
0
November 22nd, 2013 01:00
Hi dilipnet,
Thanks to the post.
As of now (OME1.2) we don’t have specific feature to monitor the hard disk status. But we do have feature that will intimate you the hard disk status in terms of alerts.
OME has Alert Actions feature, if you configure “Alert Email Action” as per the requirement you will get notified by an email about hard disk status of specific group of servers. This may help you to get the hard disk status of specific group of servers.
While configuring Email alert action as per your specific requirement please take care of –
1) Severity Association: Warning, Critical.
2) Category and source Association : In this case select “Physical Disk”
3) Device Association: Since you want specific group of device so associate your own created device group.
Note: Email setting need to be configure with SMTP server IP to receive an email.
Thanks,
Nitin
dilipnet
2 Intern
•
153 Posts
0
January 7th, 2014 04:00
1. In that ome auto generated report service tag is missing in the several devices
2. Also is it possible to classify the machines impotence in low, medium and high categories?
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 7th, 2014 14:00
Hi there...
1. So you have a server device(s) that is not classified and missing the service tag data. Is that correct? If so, please try the Dell Troubleshooting Tool against that device. If you run the SNMP test, the result set should indicate the version of Server Administrator that is on the box. If that is detected, you should get the server classified. If it is another device or another protocol, let me know and we can go from there.
2. No real way to classify low/med, etc. You might create a custom group called "Low" and then create your alert filter against that group. But I'm not clear on your objective here.
Thanks and regards,
Rob
dilipnet
2 Intern
•
153 Posts
0
January 10th, 2014 06:00
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 10th, 2014 09:00
Hi there,
If you use OMSA on the server, discover it with SNMP or WMI. But with WMI I think you will not get some of the storage data. Of course with OMSA you will discover the server IP itself. Not the Drac. For iDrac6/7 you can discover the iDrac IP via WSMan.
Interesting suggestion on warranty. Can we discuss more? So how do you think you would classify a low priority server? Would you go in and select each server to classify it H/M/L?
Thx
dilipnet
2 Intern
•
153 Posts
0
January 15th, 2014 20:00
Hi Rob,
Thanks for the update.
Yes what is the possibility to categorize the hardware in to H/M/L in the warranty report ?
BTW - I see the same server name and the IP is listed on the warranty report with different Service Level Code , Same serial Tag
how do I amalgamate those duplicate records in to once in order to create a perfect warranty report with single entry for each machine.
Regards
Dilip
dilipnet
2 Intern
•
153 Posts
0
January 16th, 2014 21:00
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 17th, 2014 06:00
Hi there,
I passed along the request you had on H/M/L. But I'm not clear, as a user, how you would like to 'mark' a server high or low, etc. In the GUI, how would you like to do this as a user?
On the warranty, there might be some duplication if warranties expire and are extended under a new service code for the same device. Or there might be multiple warranty service codes that are assigned to a single service tag. Some of this is expected. If you open a ticket the support team can take a screen shot and forward it to the dev team to see if there are other duplicated records that are not expected and need to be fixed.
Thanks,
Rob
dilipnet
2 Intern
•
153 Posts
0
January 19th, 2014 00:00
dilipnet
2 Intern
•
153 Posts
0
February 12th, 2014 22:00
Hi Nitin,
I have created the Alert Action in my ome and setup Critical,and Warning alerts. included memory and hard disk for action category
selected RAC as device associated with no date time restriction. action is enabled
I have selected the Normal alerts to see how it works.... however I am not receiving any alert messages.
Do I have to specifically enable any parameter on the remote host/servers and the ome server ?
What are the possible scenarios for this issue ?
Regards
Dnet
DELL-Nitin Bh
43 Posts
0
February 12th, 2014 23:00
Hi Dilipnet,
Thanks to the post.
To setup the alert actions in OME, Please refer this white paper [Configuring Alert Actions in Open Manage Essentials] that is available at below link: http://en.community.dell.com/techcenter/extras/m/white_papers/20437131.aspx
To receive alert in OME check below configuration settings:
1. OME: SNMP service is configured with valid community string (default -public)
2. OME: Firewall settings.
3. Loging to iDRAC UI and "Enable" Alerts setting and add Destination Address ip i.e. OME server ip
Thanks,
Nitin
dilipnet
2 Intern
•
153 Posts
0
February 13th, 2014 02:00
Hi Nitin
Thanks for the info:
I will try to follow the documentation
BTW :
What are the possible scenarios that the dell ome does not show up the warranty information on the Reports –> Warranty Information page? “System names, service tag, device type are already detected with the model etc.”
But , It does not show the Service level code and the days remaining, start date ,end date on the report?
Note
Ome server has internet access, with no proxy
I just check the warranty for one of the Service tag via dell troubleshooting tool and it show up the full details of warranty
Appreciate your feedback for the troubleshooting
Regards
Dnet
dilipnet
2 Intern
•
153 Posts
0
February 13th, 2014 21:00
Hi Nitin,
Currently I am using omsa with WMI authentication
Still the warranty information is not listed on the warranty page ?
SNMP does not work for some reason ...from troubleshooting tool. I have idarc5 6 and 7
Appreciate your assistance.
Regards
Dilip
dilipnet
2 Intern
•
153 Posts
0
February 14th, 2014 05:00
Hello The issue here is I cannot receive alerts via my ome server I have installed the omsa on my servers Snmp enabled on omsa – community name public Ome server can reach omsa installed server via snmp from troubleshooting tool. However whn I test the snmp trap from omsa ..ome server does not listen. Thanks dnet
DELL-Nitin Bh
43 Posts
0
February 14th, 2014 06:00
Hi Dilip,
Thanks for the post.
To get warranty data under warranty information report, server should be inventoried with valid service tag. If the server is only discovered then warranty data will not populate under warranty report. Please check and run the discovery and inventory of your server together and also check OME is able to connect warranty web page.
Thanks,
Nitin