Re: Servers / Windows Cluster
For myself the patch update from 1.1.6063 to 1.1.1 the HA clusters that originally would rename to the VIP DNS name for the active node are now not being able to discovered through OME at all. The...
View ArticleRe: TCP/UDP Port Requirements for OME
So, for an ESXi host .. .Is it using SSH to the OS or 443 to the DRAC? Is patching of ESXi hosts supported? So far, have been unable to get to work
View ArticleClik here to view.
Too many devices discovered
Hi,Just installed the latest OME with patch.I entered 3 IP's which were discovered ONLY using WS-MAN discovery. All other discovery options are un-checked.Yet, upon discovery, OME return 3 known...
View ArticleRe: Non-Compliant Systems Not Showing Up
I have the same issue. Â The System Update Compliance Report pie slice shows 3 non-compliant systems. Â When I click on it, I only see two servers on the Non-Compliant Systems tab. Â The missing server...
View ArticleClik here to view.
HP Switch MIBs for OME
Wondering if anyone can help me locate a HP MIB associated with the OID: .1.3.6.1.4.1.11.2.3.7.11.50I’ve searched high/low but cannot find anything which would relate to this.Additionally, whist my HP...
View ArticleThe NIC Slot 3 Port 3 network link is down Warning alerts
Ever since I updated my iDRAC7 dracs to 1.30.30 I am getting lots of warning alerts similar to:The NIC Slot 3 Port 3 network link is down.The links are active or not in use and still the errors...
View ArticleRe: Non-Compliant Systems Not Showing Up
For the missing server under non-compliance tab, what is the protocol used for discovery+ inventory? Is the iDRAC discovered or  the in-band NIC discovered on Windows/Linux server  ?What version of...
View ArticleRe: Non-Compliant Systems Not Showing Up
- Discovery Protocols for the missing server: SNMP and WMI.- The in-band NIC is discovered as it only has a RAC 5 card that cannot be discovered using WS-MAN.- OMSA 7.1.0.1 is installed on the...
View ArticleLots of devices suddenly becomin Unknown
About a third of my devices suddenly changed from completely discoverabled and inventoried to unknown.I deleted all devices and manually ran the Discovery and Inventory range and same results.I am on...
View ArticleRe: Lots of devices suddenly becomin Unknown
All devices are discovered through dracs IPs using MSMan.
View ArticleRe: Too many devices discovered
bradje1,When 3 IPs are discovered, does the same device appear in both RAC and Unknown group (Manage -> Devices) ?Are the IP Addresses under "NIC Information" for a device under RAC and Unknown...
View ArticleUpgraded OME now need HELP
I have upgraded our OME install from 1.0.1 to 1.1, now I am unable to login to the console either locally or remotely. I also have applied the 1.1.1 patch but still the login issue persists.When...
View ArticleRe: Non-Compliant Systems Not Showing Up
In Manage->Devices, select the server (one that is missing from non-compliance report) and check if "Software Inventory" information displayed in "Details" tab. If it is displayed, what are the...
View ArticleRe: Too many devices discovered
Hi Raj,Yes and yes to the above 2 questions.I just did a further test and think that the issue lies with snmp.I tried the above with M620 and m710hd blades and R820, and it returns fine if I check SNMP...
View ArticleRe: Non-Compliant Systems Not Showing Up
Software Inventory InformationSoftware Description Software Version Software TypePCI standard PCI-to-PCI bridge Driver 5.2.3790.1830 DRVRBroadcom BCM5708C NetXtreme II GigE Driver 3.5.10.1 DRVRPCI...
View ArticleRe: Too many devices discovered
Beaver6675,Looks like during status poll or scheduled discovery, OME is losing connection to RAC device and that is probably putting RAC to Unknown group. Once the connection is restored, on the next...
View ArticleRe: Non-Compliant Systems Not Showing Up
I enabled downgrades and the server showed up as Non-Compliant.
View Article