System Model: unknown

[Mark Chick]

I found that setting the radio button under the security tab from 'accept from these hosts' to 'accept from all hosts' is solving the issue. Apparently MS changed the default to 'only these hosts', while w2k servers were default to 'accept from all hosts'. Let me know if this helps you all.

[Larry Dutton]

Hello All,

I have had the following answer posted on a question in the Openview forum..:

---------------------------------

Stacy Rogers
Apr 13, 2005 14:59:56 GMT unassigned

The 7.20 agents changed the identification string returned for the OS name. You can edit the cpqconfig.dat file and add these entries before the end of the file. This should let the integration recognize the server.

Server : win2ksrvr : 1.3.6.1.4.1.232.11.2.2.1.0 string "Microsoft Windows 2000 Server Service Pack 4";

Server : win2k3srvr : 1.3.6.1.4.1.232.11.2.2.1.0 string "Microsoft Windows Server 2003, Enterprise Edition Service Pack 1";

Server : win2k3srvr : 1.3.6.1.4.1.232.11.2.2.1.0 string "Microsoft Windows Server 2003, Standard Edition Service Pack 1";

---------------------------------

Hopefully this will resolve the issue - I assume that HP support didnt pick this up with the various cases logged to them?

Thanks,

Larry

[Neil Thomas_2]

I had the same problem with one of my NT4 servers, and finally found the cause.

Under the registry key "hklm\system\currentcontrolset\services\snmp\parameters\extensionagents", there was an extra entry that didn't appear on my other working servers:
"319" REG_SZ "SOFTWARE\APC\InsightManagerSupport"

This was added when I installed a UPS. When I deleted this value, the management agents started reporting correctly (not sure what effect it will have on the UPS yet though).

Definitely worth checking your own registries for rogue entries.

[Larry Dutton]

Saltend,

But Stingy on the points on this thread?

We take the time to gather information and post in the event that we should all benefit from our shared investigations/knowledge...and get assigned 0 points! - can you explain the reasoning behind this?

[Saltend]

I'm sorry I must have misunderstood the points system then. I thought that you based the points on if they helped to resolve your issue. As some where other issues not related to my own then I rated them as the guide suggested with 1 being a 'thanks but it didnt help'. I have not used this points system before and shall alter this for future responses. I appear to be unable to edit the previous points.

[Larry Dutton]

Hello Saltend,

I feel I must apologise for my blunt post beforehand - I too tried to edit after the event as on reflection it appeared a bit rude..sorry as it was not meant to be!

Thanks,

Larry

[Rogier Boeken]

Dave's reply sorted this problem out for me as well

thanks Dave

[Saltend]

PSP 7.30 out for Win2k/2k3

ftp://ftp.compaq.com/pub/products/servers/supportsoftware/ZIP/psp-7.30.w2k3.i386.zip

ftp://ftp.compaq.com/pub/products/servers/supportsoftware/ZIP/psp-7.30.w2k.i386.zip

Will install tuesday probably and see what issues it resolvesd re: the above on my remaning 4 servers.

[Paul Van Goethem]

I had same problem:
- change group policy of the servers to allow the snmp queries from the HPSIM server did cure this problem.

[James D. Young]

Having same problem with mine since I upgraded the management server to 4.2 SP2. Everything was working on 4.2 before upgradeing to SP2.

For some, I found the account I use, was not listed in the Administrator group on the local machine. Others have the proper information but will not identify as the proper server. I use my own SNMP keys for Read and Create, all servers configured exactly the same. I also specify the localhost, and the management server for SNMP access.

Tried looking at Manage system types and it was not letting me even create a rule against any IP Address. Some of my unkown are supposed to be identified by this method.

Also had an issue where the Events would say the view was deleted, but I could log into the management account used for the services and see them with no problems.

So bottom line is that I have servers and other devices showing up as an Unknown system type.

[Edison Aguayo]

Recently we had a similar problem:
20 servers was reported as "unknown"
The problem was in SNMP definition and with the steps provided by Dave, it began to work after running the "identification" task over the "unknown" servers
Thanks

[Dave_419]

Hi all again

Just another thing that might be helpful, more on the Group Policy side of things to assign SNMP settings.

I found that some required settings for SNMP service could not be set in a GPO - particularly the "Send Authentication Trap" checkbox.

This was a real pain, as it appeared (in my setup at least) that this was required to make HPSIM work correctly with SNMP agents...

The solution was to make a computer startup script as part of the GPO which added the required REG entry to enable this check box. Worked great... if anyone has this issue and wants the details, just mail me: skyboy266@hotmail.com

Dave

[David Claypool]

Dave, out of curiousity, are these WS03 servers part of a NT4 domain?

[hirona hasegawa]

There are three causes of becoming "System Model=Known".

1.Connect the fiber device, and for off the check box of "Disable Fibre Tape Supoort" of "Storage" TAB of the management agent setting

2.When "Auto Select" is not chosen by the encode setting of IE connected with SMH

3.When the version control agent is effective

There is a possibility that the phenomenon is generated when applying even by
the above-mentioned and one.

The counter measure

1.The check box of "Disable Fibre Tape Supoort" is turned on.

2.The encode setting of IE is selected and "Auto Select" is selected.

3.The version control agent is invalidated.

[Dave_419]

Hi David (Claypool)

These systems are in a native W2K3 domain. We often find though that GPOs can do a lot, but some functions are missing from a particular item. For SNMP, the setting we needed to change is in another part of the registry that the GPO couldn't touch. But the startup script with reg /add command allowed us to set the SNMP parameter which seemed to directly affect our "System Model: Unknown" issue.

Dave

[Donald Kok]

Hi,
I carefully used Dave's recommendations, but this did not work.
Donald

[Matthew Maynard]

Ok I figured out what is causing this problem at least where I am. I ran live update for Symantec antivirus on several of my servers having problems and then brought up the home page and it worked now. The version of symantec that was installed on one of them is 9.x.x.x I tested a version 10 and it was not having this problem. I found out that after you run live update for symantec on the server the unknown went away. You might have to restart snmp and all the hp agents. On one of them I also had to set it to what was said in a previous post, I changed to to local host and removed anything elase restarted the snmp service and then set it back and restarted the snmp servers and all was good. Let me know if you have and questins

[t12357]

Hey guys I got more info on this one.

I have been installing several Windows Server 2003 SE + SP1 machines lately, most (if not all) of them failing with System Model: unkown.

As soon as the basic OS was installed I installed the SmartStart 7.30 tools.

Everything installed fine, except something called "Version Control Agent", that module failed.

I found an explanation saying that the module was not supported in that system because SNMP had not been found.

I am guessing that by default the OS installation does not add SNMP, you have to add it later.

I went to other of the servers I had with this problem (System Model: unknown) and I checked and it already had the SNMP service installed however I think it was not properly configured.

I checked the SNMP settings on another server that is working properly and I found a community name defined with READ/WRITE permissions and also the "Accept SNMP packets from any host" option was selected.

The system with SNMP installed and failing did not have the community defined and also the "Accept SNMP packets from these host" was selected but the list was empty.

After I added the community and changed the SNMP packets accepting settings voila! the HP management home page was complete and also the system model was no longer unknown but the one it should be (in this case ProLiant DL 380 G4).

Now I just have to configure the rest of the servers failing.

Perhaps this was explained above already but it was not clear enough for me until now that I have it working.

[David_746]

I am having the same problem but I can not modify the SNMP settings as they are greyed out on some of the servers. They are 2003 non SP1 joined to a NT4 domain, other servers built exactly the same allow me to modify the SNMP settings.

Any Ideas?

Cheers

[Edgar Guerrero Ortiz]

this helped me:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_ES050727_CW01&locale=en_US

Document ID: ES050727_CW01
HP System Management Homepage Fails to Display Agents Information

stopping the vcagent service and then loading sys homepage works fine. Maybe problems with vcagent.

[Anthony_137]

Sorry but this article, don't work for me... when i stop VCA, and I refresh SMH, i've got the same pb.
Any ideas ?

[Harry Galanos]

Hi Saltend,

The problem you are having is SNMP. THis is what you have to do.

Under SMP Service, clisck on the security tab, click on 'accept snmp packets from these hosts'
Enter in the following without the '' makes and localhost is one word.

'localhost'
'CMSname'

This will allow the agent to communicate amongst itelf, and the CMS.

Please let me knwo if this works.

[Harry Galanos]

This is to David.

David, did you work out how to enable the 'accept SNMP' feature. I read your response and it says this was disabled and did not allow you to add any hosts.

If you got it working, could you please let me know how?

Thank you.

[David_746]

Unfortuantely not, Ive reinstalled etc but the options are greyed out still so I cant configure SNMP and get the system management page working correctly.

[Harry Galanos]

Hi David, mate you are going to love me.

I had the exact same problem and only worked it out today.

The problem lies with Active Directory. This sets a group policy on your HP SIM domain. It does not allow you to make any changes.

What you need to do:

In Active Directory, right click on the domain you have used for SIM. Right click > Properties.Under 'computer configuration' select 'Administrative templates > Network > SNMP'. In the right window you will see 'permitted managers' this is where your group policy is set. You can configure this policy or simply enter in your CMS server name and also 'localhost' (without the '') to ensure SNMP works.

This should work. As mentioned, it fixed my problems. Please let me know how you go.

Best of luck.