- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- ESX Host not detecting properties in SIM
Server Management - Systems Insight Manager
1753738
Members
4298
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО08-12-2009 11:48 AM
тАО08-12-2009 11:48 AM
ESX Host not detecting properties in SIM
I have about 40 ESX hosts and all of them are detected by SIM just fine. They are all built from an image and seem to be identical. I have two of them that I can't get SIM to detect any of the details like model and OS. It comes up as Unknown. I pulled out a mirrored harddrive and I did get the alert in SIM. I've ran the Options > Identify and it said the following:
Checking for SNMP support on system.
The system did not respond to SNMP, verify security settings and community strin
gs.
.
.
.
Running HP ProLiant management agent identification
The system does not support SNMP.
Not sure where to take this. If the other boxes are working fine with the same settings what could be different about these two systems?
Checking for SNMP support on system.
The system did not respond to SNMP, verify security settings and community strin
gs.
.
.
.
Running HP ProLiant management agent identification
The system does not support SNMP.
Not sure where to take this. If the other boxes are working fine with the same settings what could be different about these two systems?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2009 01:42 PM
тАО08-12-2009 01:42 PM
Re: ESX Host not detecting properties in SIM
SNMP is used to ID the server, from the above the trapsink setting is correct. You should also have a setting like:
rocommunity OurROCommunity HPSIM.ourco.com
This is what should allow HPSIM access.
You should also check that SNMP has been allowed access through the ESX Firewall. Typically the HP Agent install checks and enables that if required.
rocommunity OurROCommunity HPSIM.ourco.com
This is what should allow HPSIM access.
You should also check that SNMP has been allowed access through the ESX Firewall. Typically the HP Agent install checks and enables that if required.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2009 10:56 AM
тАО08-13-2009 10:56 AM
Re: ESX Host not detecting properties in SIM
I made the fatal mistake of "assuming" that since the servers were all built from an image that the settings were identical. We all know the dangers of assuming.
The firewall settings on a working server look like this:
Opened ports:
NaviCLI : port 6390 tcp.in
hp-sim : port 2301 tcp.in
hpim : port 2381 tcp.in
sim-cert : port 280 tcp.out
NaviCLI : port 6391 tcp.in
NaviCLI : port 6389 tcp.in tcp.out
NaviCLI : port 6392 tcp.in
On the non-working machines it was:
Opened ports:
NaviCLI : port 6390 tcp.in
hp-sim : port 2301 tcp.in
NaviCLI : port 443 tcp.out
sim-cert : port 280 tcp.out
NaviCLI : port 6391 tcp.in
hpim : port 2381 tcp.in
NaviCLI : port 6389 tcp.in tcp.out
NaviCLI : port 2163 tcp.out
NaviCLI : port 6392 tcp.in
I ran the "esxcfg-firewall -allowincoming & -allowoutgoing command. I deleted the entries from SIM and rediscovered them. Now they are responding just fine.
The firewall settings on a working server look like this:
Opened ports:
NaviCLI : port 6390 tcp.in
hp-sim : port 2301 tcp.in
hpim : port 2381 tcp.in
sim-cert : port 280 tcp.out
NaviCLI : port 6391 tcp.in
NaviCLI : port 6389 tcp.in tcp.out
NaviCLI : port 6392 tcp.in
On the non-working machines it was:
Opened ports:
NaviCLI : port 6390 tcp.in
hp-sim : port 2301 tcp.in
NaviCLI : port 443 tcp.out
sim-cert : port 280 tcp.out
NaviCLI : port 6391 tcp.in
hpim : port 2381 tcp.in
NaviCLI : port 6389 tcp.in tcp.out
NaviCLI : port 2163 tcp.out
NaviCLI : port 6392 tcp.in
I ran the "esxcfg-firewall -allowincoming & -allowoutgoing command. I deleted the entries from SIM and rediscovered them. Now they are responding just fine.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP