Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

HP Insight Mananger System Type Column

Posted on 2011-03-02
2
Medium Priority
?
917 Views
Last Modified: 2012-05-11
HP Insight Mananger System Type Column is showing "UNKNOWN" for some servers.
Can someone tell me how can I fix that. so that when automatically discovering the systems it will put under the System Type column if it's a server or a switch, etc........?

Thanks
0
Comment
Question by:jskfan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 3

Accepted Solution

by:
JanStoops earned 2000 total points
ID: 35024629
Some possible answers (from HP website) - if not ok, please specify: what os? which servers?

    * You must be able to ping the device from the server where HP Systems Insight Manager is running.
    * Community strings must match - make sure HP Systems Insight Manager & managed systems are using the same one. Note that community strings are case sensitive.
    * Under Microsoft Windows NT and Windows 2000, one community name on the device must be set to READ CREATE. Note that you do not have to use this to the community string in HP Systems Insight Manager (a community string set to READ is all that is required.) The Management Agents connect to themselves using SNMP and require one string set to READ CREATE.
    * The HP Systems Insight Manager system must be allowed to make SNMP requests to the device - make sure the SNMP security settings aren't preventing this. Under Microsoft Windows NT and Windows 2000, either the "Allow SNMP packets from any host" must be selected or the address of the Insight Manager 7 server must be in the list of allowed hosts.
    * If you are using IP-specific security (as in the second part of d above) localhost (127.0.0.1) must also be allowed to make SNMP requests to the host. The Management Agents connect to themselves using SNMP and thus need to be able to get in.
    * The Management Agents must be installed and running properly on the servers you are trying to manage. For Windows systems, check the Event Log to make absolutely sure they are running (you should see a few 'Agents started' messages and no errors.)
    * Routers/Switches in the network must pass SNMP traffic on ports 161/162 and 7.
0
 

Author Closing Comment

by:jskfan
ID: 35107543
Excellent and clear explanation
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Every server (virtual or physical) needs a console: and the console can be provided through hardware directly connected, software for remote connections, local connections, through a KVM, etc. This document explains the different types of consol…
New style of hardware planning for Microsoft Exchange server.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question