Unable to register device

[Jerame]

Hi,
I have 2 new Compellent Windows Storage Server NAS devices. They run Windows 2008 Storage Server. I installed SNMP, and configured them to trap to my SIM 5.3 server. One is registered, and the other will not.

Firewall is disabled on both, and I have the same snmp settings. I uninstalled/reinstalled SNMP on the Node 1, which isn't registering, and still no luck.

Any ideas what I need to do to get this sucker registered?

Here is the results from the discovery task:
Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
The System Management Homepage is not supported on this system.
Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
This system doesn't have a server CIMOM installed locally, or cannot connect to it using all credentials specified
Running WBEM rules based identification.
Got ComputerSystem WBEM/WMI data from the system
Running VM Identification.
The system is not a VM Host, or WBEM credentials may not be specified, skipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system responded to a SNMP request, it supports SNMP.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
System does not have the SNMP ProLiant Server (foundation) agents installed.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System does not have the HPUX SNMP agents installed.
Running SNMP System Type Manager identification.
No matching SNMP System Type Manager rule was found.
Checking for DMI protocol support.
The system does not have Windows DMI support.
Running DMI System Type Manager identification.
The system does not have Windows DMI support.
Running HP-UX DMI identification.
The system does not have HP-UX DMI support.
Running HP/Compaq Desktop identification.
The system does not have Windows DMI support.
Running HP DMI Desktop identification.
The system does not have HP DMI Desktop support.
Running Generic DMI identification.
The system does not have Generic DMI support.
Running SSH Protocol identification.
The SSH protocol is not supported on this system
Running SSH Identification.
SSH Protocol is not detected; skipped SSH Identification
Running Storage identification.
Storage identification completed.
Running HP Service Guard Identification.
The system is not part of HP Service Guard cluster
Running SNMP Subtypes identification
No additional subtypes found from SNMP
Create bare-metal device nodes if OA is discovered with "Automatic Device discovery" option enabled.
Create bare-metal server node if ILO is discovered with "Automatic Server discovery" option enabled.
Running VM identification.
VMM Integration is not enabled, skipping VM Identification
Building system relationships.
Running limited data collection for common attribute.
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.

TIA,
Jerame

[BPE]

Try to access the system management home page of the two server and check if you can see the the same entries. Your log looks like the system was accessible by snmp. I guess the problem is something with sub agents.

Because you use SIM 5.3 you do not get error message if you have a name resolution problem.
Check forward and reverse lookup of your systems. HP SIM 6.x would tell you more about possible configuration errors.

[DMorgan]

I have the same problem!! All our new X3800's will not connect to HP SIM 6.2. :( If I disable the discovery filter or tick Unknown in the systems type then it will be detected when a trap is received but it will be listed as Unknown in the console. Everything seems to work but its classed as Unknown which isnt ideal....

Maybe something in the NAS build??

[Jerame]

Hi,
Since these are not HP servers, I don't have the SMH or other HP agents installed.

I'm just hoping to get a little extra notification such as cold boots, link up/down and that sort of thing.

It's just frustrating that these are two identical computers, and one works, and the other doesn't. :(

[Rob Buxton]

For a bit of additional troubleshooting go to Options ->Manage System Types.
Use the "New" icon and then just go through and try and get info from the device using the SNMP communicty string you believe should be used.
This may help troubleshoot.
In essence, "Unknown" means it has detected SNMP but hasn't been able to identify the device. "UnManaged" means it hasn't detected any protocol it can use to ID the device.
Manage SystemTypes can be used to manually add new device types based on criteria you specify.

You may want to recheck global credentials etc. and then the SNMP on the target device. Note community names are case sensitive and the HP SIM Server may need to be added as an allowed host.

[BPE]

An other idea is to compare the system credential for the two systems. You should see at least SNMP in the list of credential.

If you do not see SNMP on one of the system you should check on the storage server if his SNMP agent blocks the management server access.

SNMP Agent or sub agent no longer running. I just had this error with a HP P4300 lefthand storage. 3 nodes worked one had the SNMP agent/daemon in not running state.

[Jerame]

Sorry for the long delay, had some big issues going on the last week.

I found an old thread where someone had a simialr problem (Don't know why I didn't see this before), and he fixedd the problem with a reboot.

Tried this myself, and everything is working correctly.

Thanks everyone for your efforts!!!!

Cheers,
Jerame

[Jerame]

Sorry for the long delay, had some big issues going on the last week.

I found an old thread where someone had a simialr problem (Don't know why I didn't see this before), and he fixedd the problem with a reboot.

Tried this myself, and everything is working correctly.

Thanks everyone for your efforts!!!!

Cheers,
Jerame