BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

enclosure name is "Unknown"

Menno S.
Occasional Visitor

enclosure name is "Unknown"

Hello all,

We have here a strange problem, let me explain.
We have a lot of HP bl20p G3 blades. In one rack with name "Rack6", we have enclosure with the name "Enclosure4". Every blade in this enclosure sees the correct rack and enclosure names.
Except the blade in bay 2. This blade thinks he is at bay 2 in enclosure "Unknown" in rack "HP".

The problem is located in the enclosure, when we insert an other blade at bay 2 the problem stays.

Has someone any idea how to fix this?

Thanks,
Menno
1 REPLY
James ~ Happy Dude
Honored Contributor

Re: enclosure name is "Unknown"

Hello Menno,
Unknown In HP SIM, a status indicating that none of the built-in or System Type Manager (STM) based tasks could identify the system. However, some management protocol was detected on the system. Servers might be listed as Unknown for the following reasons:
* You must be able to ping the system from the server where HP SIM is running. You can issue the ping command from a command or terminal window, or you can ping from HP SIM by selecting the unknown server, selecting the Diagnose and Ping options, and following the on-screen instructions.
* Try running the Configure or Repair Agent settings tool located under the Configure menu.
* If the system supports SNMP, it might be that the type is new or a third-party system that is not identified by default. See â Global protocolsâ and â System tabâ for more information. You can use the System Type Manager (STM) tool to add a new type. See â Creating STM rulesâ for more information.
* Community strings in HP SIM must match the ones used for the remote device. Ensure HP SIM and the systems are using the same community string. Note that community strings are case sensitive. From HP SIM, select Optionsâ Protocol Settings and select Global Protocol Settings, or System Protocol Settings to make the changes.
* In Windows NT and Windows 2000, one community name on the system must be set to Read Create. You are not required to use this community string in HP SIM (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 SIM system must be allowed to make SNMP requests to the managed systems. Ensure the SNMP security settings are not preventing this. In Windows NT and Windows 2000, ensure the Allow SNMP packets from any host is selected or that the address of the HP SIM server is in the list of allowed hosts.
* If you are using IP-specific security, localhost (127.0.0.1) must also be allowed to make SNMP requests to the host. The localhost entry enables the Management Agents to connect to themselves using SNMP.
* The ProLiant Management Agents must be installed and running properly on the ProLiant servers you are trying to manage. For Windows systems, look at the Event Log to verify that they are running (you should see a few Agents started messages and no errors).
* Routers and switches in the network must allow SNMP traffic to pass on UDP ports 161 or 162.

Regards,
James.