Re: Refresh inventory doesn't cut it sometimes
Hi there,You may need to re-run discovery as well as inventory. The reason is discovery collects a small amount of inventory as well (just enough usually to properly classify the device). So you may...
View ArticleRe: OME Feature request
Hi cameron.Ok, I will send this along to the product team for consideration.Regards,Rob
View ArticleRe: Refresh inventory doesn't cut it sometimes
Thanks Rob!Then I would like to add a feature request :)When right clicking on a device there is currently a Refresh Inventory selection. It would be VERY nice to have a Rediscover This Device option...
View ArticleRe: Health Status is a Question Mark on a few iDRAC6
Either port 443 is not accessible in iDRAC and OME server, or the credentials may not be right. The above wsman command has to work. Otherwise OME cannot connect to the device using WSMAN. It should...
View ArticleRe: Refresh inventory doesn't cut it sometimes
Ok, I understand this request and will pass it along as well. thx
View ArticleRe: Health Status is a Question Mark on a few iDRAC6
I can access the DRAC via https so 443 is valid.Credentials are the same on all our iDRAC6 and they work fine for the other iDRAC6 in this range and when accessing any of the iDRAC6 with this issue in...
View ArticleRe: Health Status is a Question Mark on a few iDRAC6
winrm enumerate "cimv2/root/dcim/DCIM_SystemView" -r:https://$IDRACIPADDRESS/wsman -u:$USERNAME -p:$PASSWORD -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic -format:prettyMake sure $IDRACIPADDRESS,...
View ArticleRe: Health Status is a Question Mark on a few iDRAC6
BTW, launching iDRAC via https uses a different port and not 443. To communicate w/ iDRAC using WSMAN stack in secure mode, port 443 has to be enabled on both ends (OME server and iDRAC).
View ArticleRe: Health Status is a Question Mark on a few iDRAC6
<wsman:Results xmlns:wsman="schemas.dmtf.org/.../results"><n1:DCIM_SystemView xml:lang="" xmlns:n1="schemas.dell.com/.../cim-schema/2/DCIM_SystemView">...
View ArticleRe: Health Status is a Question Mark on a few iDRAC6
So as you can see it is returning the expected data from the command line code so why is it not showing correctly in OME?
View ArticleRe: OME on Windows Server 2012
Rob, I realized a date has not been announced, but is there an idea of when? Q2, Q3, Q4 ? I am having a lot of issues with my current install of OME, and was hoping to install OME on a new 2012...
View ArticleMissing something - Health status red X - System Administration
Good morning,I'm just getting into OME and have gotten it installed and patched to 1.1.1 and installed OMSA on several of my Dell servers. I have them showing in OME, but I have a red X on health...
View ArticleRe: Health Status is a Question Mark on a few iDRAC6
OK So command line retuns expected data. Troubleshooting tool returns expected good status for WS-Man, SSH, SNMP and IPMI.Why is OME not able to correctly inventory these few vs all the others that are...
View ArticleRe: Missing something - Health status red X - System Administration
Hi Damian.A few ideas.First off, when you get a red x next to SA, you should right click on that server in the device tree and launch OMSA (or do it as you indicated). The details in OMSA should...
View ArticleAPI for OME
Is there an API for OME?I would like to be able to pull the device data (SN, Proc, RAM, Disk, PCI, firmware versions etc) gathered by OME and use it in another application.
View ArticleRe: API for OME
Not really an API. But there is a CLI that we discuss in a whitepaper on www.delltechcenter.com/ome. It is used more for creating discovery ranges, etc. Nothing to pull data. But this requirement...
View ArticleRe: API for OME
Thanks Rob,We use Ubersmith for device and network oversight, ticketing, billing etc and I would love to be able to write a custom module for it that pulls live device data out of OME as that data...
View Article