This post is more than 5 years old
4 Posts
0
27344
August 27th, 2014 07:00
OMCI communication troubles
We have a single DC which is running OME 1.3, PowerEdge T710 Server 2008 R1.
I'm attempting to get OMCI communicating on a test PC, Precision T1500 Win 7. I've successfully installed OMCI ver 8.2.1.70 on the PC.
OME doesn't pick up on OMCI as a Data Source, only WMI is shown in Data Sources, so the PC has unknown health status & no hardware logs.
On the PC, I've attempted to install OMCI with SNMP enabled and disabled. I've also attempted to disable and enable SNMP in services.
On OME, I've set up discovery with WMI enabled and SNMP enabled, and WMI enabled and SNMP disabled, same result.
Using the troubleshooting tool on the DC, for WMI, both Windows NameSpace and Dell Client Agent (OMCI) NameSpace show they are present.
We have a SonicWall NSA router/firewall with McAfee/SonicWall Enforced Client AV/firewall. I've disabled the software firewall, and for the hardware firewall, there is an existing rule for LAN to LAN to pass all. I've also set a rule for port 1311 for LAN to LAN to allow all.
On the PC, using NMAP, port 1311/tcp shows open. On the DC, using the troubleshooting tool, port 1311 shows "Could not connect to 1311 port".
I should state, OME does successfully pick up on OMSA on the Servers. It also picks up successfully on our PowerConnect 2824 and network printer.
I'm not sure I'm convinced this is a firewall issue, I don't show any logs of blocking traffic and it does successfully communicate with OMSA, just not OMCI. Why would the troubleshooting tool show OMCI is present, but OME not pick up on it?
What am I missing? I'll give any more details if required.
Thanks,
Steve
calspec
4 Posts
0
September 5th, 2014 09:00
I finally figured it out, of course it's a bone-headed error.
I installed OMCI across the domain, and the only four computers that didn't respond were Precision T1500. A brief search shows they don't seem to support OMCI.
http://en.community.dell.com/techcenter/enterprise-client/f/4448/p/19415824/19977333
So, that's that. All is working as designed.
Thanks for the help,
Steve Kamego
calspec
4 Posts
0
September 5th, 2014 09:00
I installed it across the domain, and the only computers not working, including the original test PC ws30, were all Precision T1500's. Doing a brief search showed that OMCI and the T1500's don't seem to play together:
http://en.community.dell.com/techcenter/enterprise-client/f/4448/p/19415824/19977333
So, all is working as designed. Thanks for the help with this, the scripting definitely helped diagnose the issue.
Steve
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
August 27th, 2014 08:00
Hi Steve, thanks for the post. Lot's of good data there, so thanks for that.
Right, so first off, I'll point out that there is a "Client" whitepaper on www.delltechcenter.com/ome.
It looks like you have most of the info already, but just letting you know in case there are any other nuggets in there.
For sure you want to discover the Client device with OMCI and WMI (and only WMI) in your OME discovery wizard. So don't put SNMP into the picture for these devices.
As you said, your TS tool results include the name space, so that looks ok as well. It appears your OMCI is installed ok so I'm a bit at a loss.
I wonder if you can try some of the sample scripts to connect to OMCI on the web pages below. That might be useful for diagnostic purposes. I'll see if I can find out any other ideas.
Regards,
Rob
http://en.community.dell.com/techcenter/enterprise-client/f/4709.aspx
http://en.community.dell.com/techcenter/systems-management/w/wiki/1773.openmanage-client-instrumentation-omci.aspx
calspec
4 Posts
0
September 3rd, 2014 14:00
I was able to run some sample scripts and found some interesting results. Below, I am referring to the samplesystemsummary.vbs script.
The test PC in this example is ws30 running win 7. Running the script with ws30 as the system returns nothing, just a blank line.
Running this script with a PC that does not have OMCI installed returns c:\temp\samplesystemmsummary.vbs(43, 1) (null): 0x8004100E
I installed OMCI on a Win XP box, ws23 in this case, and running the script returned asset tag, service tag, and bios version, as expected.
I re-ran inventory on that PC, and health status works fine. I installed OMCI on another Win 7 box to see if it was OS specific, and it works fine.
So, I have one PC that will not respond w/ OMCI data. Coincidentally, this PC (ws30) used to host IT Assistant, so maybe some of the remnants of that are causing issues.
Thanks for the help, I'm going to keep plugging away and will post my solution when I get it.
Steve
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
September 3rd, 2014 15:00
Ok, interesting....for the XP box that the script runs correctly on...can OME discover it properly and classify it as a client device?
Rob
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
September 8th, 2014 13:00
Ah ok, great. Really appreciate the follow up post.
Regards,
Rob