This post is more than 5 years old
1 Rookie
•
33 Posts
0
39057
May 6th, 2015 17:00
OME 2.0.1.2222 - Newer Catalog version available
I'd like to know why when my OME console tells me there is a Newer Catalog version available, and after I download it, I have no new updates. Been like this for about the last 3 months. I know for a fact there are newer updates available, so I have to get them manually from Dell's Support site.
No Events found!
Dell-Ranveer
96 Posts
0
May 7th, 2015 00:00
Hi,
Thanks for your post!
1. What was the Release ID for the catalog? Before and After download?
2. Did you see any "Import Catalog" task getting created under Task Execution History?
3. After the catalog download, were there no devices listed under Non-Compliant, is this what you are seeing?
And just to bring the feature which OME has within the console which actually keeps you posted whenever there is any new (ftp) catalog is available.
Just browse to System Update > View Active Catalog, there it will show you if there is any new catalog available, if it says "Yes" you can go ahead and select "Update" or select "Get the Latest" button under Summary tab. Make sure you have proxy settings configured under Preferences tab.
So once you click on any of these it will download the latest catalog automatically and will list out the newer updates available for the discovered target, if there are any.
Note: There is a new catalog released 2nd Friday of every month.
Hope this helps!
Thanks
Ranveer
NOCTech
1 Rookie
•
33 Posts
0
May 7th, 2015 14:00
Hi, I don’t remember what the Release ID was, but I noticed today there was a Newer Catalog version available, and after I downloaded it, I finally saw all the available updates that I knew existed, and more, and the Release ID is now TFNG9. I went from having 92 servers in Compliance to 9, but that’s good news, now I can go to work on getting them in to Compliance.
Also, thanks for the tip on the 2nd Friday of the month release.
On another note, the R720/R720xd, 09.2B.80 Power FW that came out a while back, I actually had a PS go bad after this update, so my question is, will there be a newer update available for this that works and that I can trust, and if not, what is the best way to install this update. I usually just double-click the package from the server I’m doing the update on.
Thanks
Dell-Ranveer
96 Posts
0
May 8th, 2015 08:00
Hi,
Glad to know that it worked!
And for the PSU update, the method you tried is correct. But there is an issue (http://en.community.dell.com/techcenter/systems-management/f/4494/p/19599861/20721183#20721183) which we are aware of, so once there are any updates we will keep you posted.
Thanks
Ranveer
NOCTech
1 Rookie
•
33 Posts
0
May 8th, 2015 12:00
I don't think my copy/paste came thru on the last post, so here it is:
Alert message ID: 2238, Controller information. The controller debug log has been exported., system, Controller 0 (PERC H710 Mini) [Event Code:2238]
This is what I'm referring to in the previous post. Thanks
NOCTech
1 Rookie
•
33 Posts
0
May 8th, 2015 12:00
That would be great to be notified when a newer update becomes available.
I have 1 last question for now. Since I updated to OME 2.0.1.2222, I see a ton of these Alerts by Severity on the Home Portal of OME, but not sure why they are happening.
It used to be that you had to manually do this in OMSA, either by myself or a Dell Technician.
Is there any reason this is happening??
Dell-Ranveer
96 Posts
0
May 12th, 2015 06:00
Hi,
From the OME point of view, I can recommend you to create an ignore alert action created for this specific alert since this is just an informational alert which brings no harm. You can browse to Manage > Alerts > New Alert Ignore Action to achieve that.
Here, we mostly look for problems\issues specifically to OME ;)
But still for the specific alert which you have mentioned, i.e. Alert message ID: 2238, Controller information. The controller debug log has been exported., system, Controller 0 (PERC H710 Mini) [Event Code:2238]
This alert is generally received when user has attempted to export the controller debug log, though this is for informational purpose with appropriate severity. So, by any chance is there any tool (third party tool) which is triggering this export for debug log which is running in background?
If not, and you want to know more about Event: 2238 I would recommend you to cross post this query in general management or hardware forum, as that's where most of omsa/hardware guys hang out.
Hope this helps!
Thanks
Ranveer