Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

System Model: unknown

SOLVED
Go to solution
Saltend
Advisor

System Model: unknown

I am having some problems with about half our servers.

we've been using the psp's for a while but only just started looking at Manager side. Using HP SIM4.2 and PSP7.20 - half the servers come up as "unknown" and logging into the servers individual management site shows none of the expected boxes for integrated log, etc.
also the VCA fails to pull up data.

 

 

P.S. This thread has been moved from ITRC server mgmt (Insight Manager 7) Forum to ITRC HP Systems Insight Manager Forum - HP Forums Moderator

69 REPLIES
OlivierV
Trusted Contributor

Re: System Model: unknown

Check that all the agents are running (service control panel) and the SNMP service is started.
Saltend
Advisor

Re: System Model: unknown

All services are running, inc SNMP except the event notifier service which is set to disabled.

that service is disabled on servers that work however.
SteveBxxx
Frequent Advisor

Re: System Model: unknown

Probably need to check the config on the snmp service from control panel. Compare the Agents / traps / security tabs between working / non working servers.
Larry Dutton
Frequent Advisor

Re: System Model: unknown

I am having a similair issue using the Insight agent version 7.20 and Insight intergration for NNM,

I have logged this in the Openview section but this is the same, Insight agent 7.20 comes up as cpqmodel=unknown after upgrading the agent, the manufacturer is picked up as HP via SNMP and I now am looking at ways of manually setting the cpqmodel number within Openview,

Incidently this is on a Proliant DL380 G4 and at the moment looks like an issue with the later insight agents - which now seem to be called 'system management homepage' bizzare!

Any update on this would be appreciated but I would say that it is a bug in the 7.20 agents at the moment??

Thanks,

Larry
Dave_419
Advisor

Re: System Model: unknown

I have the same problem, but no wisdom to add. Installing PSP7.20 gives the System Model: Unknown on the page. Quite annoying, as I haven't found any obvious doco about this needing any extra config after installing.

My SNMP settings are set for Public, dest localhost, which I am guessing is ok...?

So I am also waiting for a solution...

Thanks
Dave
Saltend
Advisor

Re: System Model: unknown

starting to look more like a bug/default config issue.

it appears to only affect window2003 servers here.
Larry Dutton
Frequent Advisor

Re: System Model: unknown

I am also thinking bug - this was on a Windows 2000 server with 7.20 applied,

I have since changed this back to 7.10 and the server is identified correctly again,

Could this be related to changing from the old Compaq insight to indentify as HP insight - all the SNMP fields are "isCPQ = e.t.c." yet the manaufacturer on 7.10 is "CPQsrver" yet on 7.20 shows as a HP server....

No notes found on this either - thinking of logging this with HP to see what the response would be, just really want to know if they are aware of the problem but would have thought testing of the new agent would have identified this?
Dave_419
Advisor

Re: System Model: unknown

I've just logged the call with HP's online tech support. I'll let you know what I find out.
Saltend
Advisor

Re: System Model: unknown

Thanks. I've had no success here so far.
Larry Dutton
Frequent Advisor

Re: System Model: unknown

Thats good news Dave, I like the look of the later version but it's a shame it's not compatable!

I look forward to the resolution! (7.21 perhaps..)

Larry
Saltend
Advisor

Re: System Model: unknown

I removed our group policy configuration for SNMP and that got most servers working, some still appear to be fubar but only a handful.
Christopher_64
Occasional Visitor

Re: System Model: unknown

Thanks for posting, misery loves company.

I've seen this on 28+ of my Windows 2003 Ent HP DL580G2 servers. This occurs only on servers that have been upgraded or have previously had another version of the PSP installed. New (clean) installs appear to work fine.

I've forced the uninstall of the previous diagnostics using "sc delete hpdiags" and tried to force the correct install of PSP 7.20 w2k3 using "setupc /use-latest /force". Nothing appears to resolve the System Model: unknown.

In addition to this, the foundation, server, and storage agents appear to be running successfully, but cannot be accessed from the management homepage. The mamangement processor (iLO) is also listed as "none".

There are no errors in any system or application log to identify failures of services or applications. It would seem to be a SNMP or WMI based issue. I've tested the setting as READ/CREATE and READ/WRITE with no results.

I've also opened a case with HP Insight Manager software support to resolve this issue. I will report back if I receive more insight or a resolution.
Russ_50
Advisor

Re: System Model: unknown

I am having the same problem on my 2003 server. However, I was having this issue before I upgraded to 7.20. I was running 7.10 and was experiencing this issue. I upgraded to 7.20 hoping the issue would be resolved thinking maybe something was corrupt. My main issue is the 2003 server is my version control repository, so all the rest of my machines will not connect to it to update their VCA's. Pleas post here if anyone finds a resolution. Thanks!
Russ_50
Advisor

Re: System Model: unknown

Ok, I fixed the issue of the System Model: Unknown. I looked at my SNMP settings and found a public community string in the security tab with read-write. I removed the public item and left only the standard community strings we use normally. However, I am still unable to get my VCA to find the repository, even on the machine that actually contains the repository. I tried both using the old administrator password (which it said it does not do anymore) and i have tried several domain admin accounts in our domain.
Dave_419
Advisor

Re: System Model: unknown

Thanks Russ for the info. Can you advise what SNMP strings you used to have to have it working?

I also have little progress with my HP call - they've said it's been routed to another department and I will be contacted shortly. We'll see!
Russ_50
Advisor

Re: System Model: unknown

We do one community string with read-only and another one with read-write as the accepted community strings. We also set it to accept snmp packets from any host. good luck with HP :)
Martin_73
Occasional Contributor

Re: System Model: unknown

We have the same issue with 7.20.
But only when we install the agents with the "Local Access" enabled. If we install without that option it works fine.
Dave_419
Advisor
Solution

Re: System Model: unknown

Hi all

I have it working now, and can consistently make it not work at will :) That's after using the guidance of others on this forum, thanx!

For me, it's completely related to SNMP settings. For previous versions I haven't touched SNMP, it just worked... But when I went back to 7.1 agent it also didn't work (though it did before, but maybe it was earlier version, not sure now).

Anyway, I had to do the following steps (also screenshots are attached which show the same as written below):

1. Set the SNMP Service properties, TRAPS page, give it the chosen community name and destination to localhost

2. Set the SNMP Service properties, SECURITY page, and ADD the chosen community name with READ ONLY access. This is the setting that seems to make a difference - remove it and you have the "system model unknown" problem.

3. Also on the SNMP service SECURITY page, I have set the trap destination for localhost.

Hope it also works for you. Thanx for the help everyone.

Dave
Saltend
Advisor

Re: System Model: unknown

I just noticed that on some of my non working servers the settings tab is not there in the system homepage.
Gary J
Occasional Visitor

Re: System Model: unknown

I'm gonna throw a spanner in the works and say that this error is not solely related to the SNMP settings on the server..

You need to check that your server is pointed at your Version Control Manager Server (VCMS) and that it has a PSP baseline configured to suit your server..

You can configure your server to point to the VCMS in the Systems Management Homepage under Version Control Agent - Change Agent Settings..

Type in the name of the VCMS and enter the account details of the administrative account on the VCMS server.. On the next page select the Baseline setup for your server then click finish.. Hey Presto you should now be able to see all your lovely Hardware Component Statuses and the System Model Type..

It seems like with the 7.20 agent you require a VCMS to be configured where as previos versions couldn't give a stuff about them..

Hope you can all close your calls with HP as I'm about to do.. Seeeee ya.

Re: System Model: unknown

Well. Our organization supports about 1000 servers spread out on sites around the world.

We have the same experience as several of you describes: System Model is set to unknown.

Sometimes it helps just to do a refresh from Your browser.

It seems like the further the server is from the sentral HPSIM 4.2 server the more problems You get.

This leads me to beleive that the problem is caused by some kind of timeout generated by the Insight Agents on the servers.
Jeg er her
Saltend
Advisor

Re: System Model: unknown

Dave's reply sorted it for me.

I will now look at making our SNMP settings consistent throught the domain using Group Policy i think.
Fab_3
Frequent Advisor

Re: System Model: unknown

All,
thanks for yours suggestions.
But i've a big trouble about SNMP configuration. In security and traps tab all box are grayed...All my servers with 2003 in NT4 domains are in this state. Servers Stand-alone or join to AD seems don't have this trouble.
However i tried to move one server from domain to workgroup without success. In few words: I cannot modify SNMP parameters.
Any ideas ?

Simon Blears
Frequent Advisor

Re: System Model: unknown

Just to add a "me too" to this thread. I have upgraded 7.10a to 7.20a on all of them.

The 2003 servers seem to have the most issues, but the 2000 servers also have issues. I am keenly watching this thread for a resolution.