- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- HPSIM 7.2. How to make server answer to 5989 (WBEM...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2013 05:58 AM - last edited on 09-09-2013 07:35 PM by Maiko-I
09-09-2013 05:58 AM - last edited on 09-09-2013 07:35 PM by Maiko-I
HPSIM 7.2. How to make server answer to 5989 (WBEM/WMI)
Hi!
SIM will not identify/discover server using WBEM. I get different messages, but I believe it boils down to server communication on port 5989.
I have a hard time trying to configure the client 2008 R2 servers answer to "telnet <host> 5989" from SIMserver..
Even servers on same VLAN/Subnet will not get identified by HPSIM.
I have managed to get one 2008 R2 server to be picked up by HPSIM, and that is a CommandView EVA-server. I'm not able to tell the difference of this server ant the other servers I try to identify/discover. Thought mybe the presence of Pegasus WMI Mapper Service, but I responds to the telnet command even when that service is stopped..
I try the telnet-command locally using its own IP - but no luck.
(The SIMserver answers to the telnet command from other servers.)
I have installed spp 2013020(B) + "HP Insight ManagementWBEM Providers for Windows Server x64 Editions" (cp017534.exe) in addition to all components selected automatically.
Could anybody tell me what service/program actually answers to 5989, and which component to install?
Regards
Ivar
P.S. This thread has been moved from Servers > General to ITRC HP Systems Insight Manager Forum. - Hp Forum Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2013 12:08 AM
09-19-2013 12:08 AM
Re: HPSIM 7.2. How to make server answer to 5989 (WBEM/WMI)
You are right EVA server and WMI Mapper are using same port.
Check this thread (especially last post)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2013 01:27 AM
09-26-2013 01:27 AM
Re: HPSIM 7.2. How to make server answer to 5989 (WBEM/WMI)
Hi,
first of all, WMI is not the same as WBEM (but it is alike). SIM supports WBEM, Windows supports WMI, so you need a 'translator'.
you will need to install (or verify) the (Pegasus) WMI mapper (included in SIM installation media).
it should be configured on a host which is accesible on 5989 by SIM (might be SIM server itself) and has WMI access to the monitored hosts (usually this port range is not opened in firewalls due to security).
You can install multiple "WMI mapper Proxies". You should configure each one of those in HP SIM: Options-ProtocolSettings-WMI mapper proxy.
You can configure as much proxies as you like, but keep in mind each proxy might lenghten the time needed for discovery.