System Model: unknown

[David_746]

Hi there
Unfortunately the servers reside in an NT 4.0 domain, I can see the policy setting in the Local GPO but it only allows read only access.

Cheers

[Mike Elliott_3]

I had this problem with HP dl580 and dl380 after applying the w2k security rollup Windows2000-KB891861-x86-ENU.EXE with HP System Management Homepage version 2.02.106.
Went down the path of adding SNMP localhost settings but no joy -- what actually fixed it was the HP CUSTOMER ADVISORY
Document ID: ES050727_CW01 that Edgar Ortiz pointed out to me .I am currently using both the SNMP trap configuration of localhost and disabling the version control service and these have sorted out my problems

[Rollin Derks]

Edgar's Reply worked as stated above. Just as an FYI: PSP 7.40 DOES NOT FIX THIS ISSUE. HP Promises future release will resolve this but obviously not. I just tried it.

Here are the steps just as a reminder...

As a workaround, to prevent the SMH data collection timeout from continuing to occur, perform the following:

Stop the Version Control Agent from the Service Applet and restart SMH.


Once the SMH the web-based interface is loaded properly, restart the Version Control Agent.
A future release of HP System Management Homepage will prevent the timeout from occurring. This advisory will be updated when more information is available.

[Rich Purvis]

If stopping the VC Agent fixes your problem then you have a VCA configuration or access problem. If you use Version Control then you need to make sure that the VC Agent is properly configured to point to a VC Repository Manager. If you still have an issue and you have a proper VCA configuration then you may have an issue with the VCA being able to access the VCRM - slow network or firewall interferring with access. If you have SS7.40 SMH installed then you will get a popup message when a timeout occurs - if you get the popup then you can go to the System Management Homepage log and you should see an entry that lists the time it took for each application to respond in seconds. This is there to help people identify the application causing the timeout.
-Rich

[Russ_50]

It looks like the newest version of the HP System Homepage for Windows, version 2.1.3.132 fixes this problem. I consistantly got this issue when I installed the 7.40 support pack, but it goes away when I install the 2.1.3.132 System Homepage which does not come with the 7.40 support pack.

Wow, it has been a long time since I started having this issue. Nice to see HP finally came through.

[Kjetil_4]

I can confirm what Ross says. I upgraded the Systems Management Homepage v2.1.2.127 which is included in Proliant Support Pack 7.40b to version v2.1.4.143

link:
http://h18013.www1.hp.com/support/files/server/us/download/23388.html

This took care of the "uknknown system type" problem on all my recently installed windows 2003 servers immediately.

[Sebastian Tempo]

Hi, I've 2 servers with W2K and the same problem, but in my case installing Insight Agents the System Model appears.

Saludos
Sebastian

[Onanimity]

Hello.

I've just applied PSP 7.51A to our servers, and I'm suffering from the dreaded "unknown" system type on a number of our servers - generally the older ones such as all of our Proliant ML530G2 servers.

I've checked the SNMP settings, and all looks fine. I have the SIM server in the trap destination, and I accept SNMP packets from localhost as well as the SIM server.

What should I do I wonder? Regress the version of the management agents?

I wouldn't have thought that updating the HP System Management Homepage would help as I would have thought that the latest PSP would have the latest HP System Managment Homepage in it?

I am using HP SIM 4.2 SP2.

By the way, when I updated our servers to PSP 7.51A, I had a problem installing the Insight Managment agents, where the HP Insight Server NIC agent wouldn't start, and I found the fix to be to uninstall the managment agents and reinstall from scratch. This problem happened on about 5 of our 30 servers.

[Jeff Fong]

I also recently upgraded to 7.51 agents and afterwards the server came up as unknown. It correctly displayed the system model before the upgrade from 7.50. I had upgraded the agents on a number of servers, but this was the first one that gave an unknown status after the upgrade. I looked and the server was not running the most current system BIOS version. Upgraded the BIOS, restarted the server and everything is OK now.

HTH

[Michael H. Yost]

We found the reason the HP System Management Homepage only partially displays and the system name is "Unknown" is because the SNMP service did not have a community name added and the name had no security rights. In the properties page of the SNMP service select the Trap tab. Add a community name. In the Security tab add the name again and give it READ CREATE rights. Allow trap to come in from any location. You can also unselect the encrypt button if you wish. Stop and restart the snmp service. Hope this helps.

[mdking]

Three (that I know of) of my 400 servers are having the same problem. The servers are DL380's & two are G4's and one is a G3. They were originally using the 7.40 PSP and after identifying the problem, I did an in place upgrade to PSP 7.70. This did not resolve the issue so I proceeded to remove all the agents and do a clean install of the PSP forcing them to update current versions. This produced no change. I then engaged HP's support. He recommended downgrading to 7.60. I was very doubtful that would produce any desirable effect and that doubt proved to be well founded. Afterward I began searching on the forums and found the following.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=805954
This thread contained some good information and using it I removed & reinstalled SNMP, updated the systems firmware, verified the SNMP settings are correct which are distributed via GPO to all the servers, and found another article.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_ES050727_CW01&locale=en_US
None of these steps helped although the last article made the timeout error message disappear.

Any suggestion would be greatly appreciated.
MDK

[Donmac]

Hi

I downloaded installed the following

HP Insight Management Agent for servers (Windows 2003 latest version) CP007179.exe

and this stopped the system model = unknown message. All works fine now.

Paul

[imasood]

Heres what did it for me:

In SNMP service settings, on the security tab, choose the "Accept SNMP packets from these hosts" radio button. In addition to your SIM server add localhost to that list. That made everything work for me....EVERYTHING!!!

[starchaser]

Please make sure that the HP Insight management agents and HP system management homepage is correctly configured under the HP remote deployment utility.

[Jreynolds]

I was having the same issue and followed the advice of this thread.

To resolve my issue I did the following

1) Set SNMP to accept from any host.
2) configure a community string to have read only.

This then showed the information I required.

Thanks all

[Patraulescu]

the 'localhost' in permitted managers for snmp communities seems to do the job (the anyhost is working too because 'localhost' is a host as 'any')

[Mark Sifflett]

Had problem and fixed, thanks you guys. Mine was snmp. I'd also like to point out that version repositry needs populating and pointing a the correct folder for it all to work well.

[Brandi Holcomb]

I had a similar problem, only it's about 3 years later and it was with PSP 8.0 on a new server setup. Just thought I'd put it out there for any others who run into it.

On the local System Management Homepage (SMH) of the new Server 2003 std box, the system model was "unknown" and there were no boxes showing the status of the different modules (network, System, storage). However, Version Control agent worked fine (and showed up in the SMH, and the system status summary was OK. (But it was OK because it wasn't monitoring anything!) This was after I had struggled to get the SMH to show up at all after doing a firmware update (it's not clear if the firmware update blitzed it, but it was after that point that I could no longer get to SMH).

Once I reinstalled all PSP components using the "force" option, SMH showed up, but in this useless state described above. Reinstalling the WBEM option, using the "force" option caused my proliant model to become known again and Network, System, and Storage boxes reappeared.

[Prasad12]

I have faced the same issues on a HP Proliant DL380 G5 server.

But after changing the SNMP settings under services its working fine.

Here what I did :

Go to Services and select SNMP services.

Right click on it and select properties.

Select security tab. Click on add and enter

a community name.

localhost should be added under

"Accept SNMP packets from these hosts"

Click on OK.

Now go to HP system management icon on the

desktop of the server or go to HP mangement

agents under programs.

Everything should be populated about the

server and System model : should have model

name here.

[Prasad12]

Thanks Dave. I have tried multiple things.

But your suggestions helped me to solve the

issue.