Inaccessible

[Joern]

Hi folks,

we´ve got lots of Compaq servers and most of them are always accessible via CIM 4.90/5.10. Server´s got SNMP installed incl. agents... but sometimes some servers could not be accessed. We´re using WinNT 4.0/SP6a and only the IP-protocol. No SNMP-traps.
-> The indicator light in CIM is coloured black, which means the device is not accessible via CIM. We´ve checked the services on the servers and couldn´t find an error...
After re-installing the agents nothing changed.
Do we have to delete CIM on the Workstation? What is wrong? Agents, SNMP, IP, CIM???
We would appreciate any comments...

Bye,
Joern

 

[DevilDog]

When you say that "sometimes some servers could not be accessed", are you saying that the same servers sometimes ARE accessible and sometimes NOT? On the one hand I would suggest that it's the network (no doubt you checked that) and on the other make sure that your SNMP public names match. I have installed servers where the name defaulted to either "Public" or "public". To the best of my knowledge the name is case sensitive. -- Devil Dog --

 

[Guest_imported]

I've had the same thing happen with some of my servers. The one thing that I have noticed is restarting the compaq insight manager will sometimes resolve this. I have been hunting what the cause is but no luck so far. I also have devices that are setup exactly the same yet I can not do sets on a couple of them.

 

[Guest_imported]

A word of caution to those who are using "public" or some variation of it as their SNMP Community String... That's one of the oldest and easiest ways to hack at or into a box. Using a default like "public" or "private" as your Community String is like using a password of "password" for your NT domain administrator account.

Does your SNMP/CIM Agent config allow Sets on your servers? If so, anyone on your network can reboot your servers (or worse) at will simply by supplying the "public" community string. That probably wasn't your intention.

My suggestion? Change "public" to something that only your administrative staff will know like "w0lf359z" or something even more obscure. You'll have to change the Default Community String in your CIM Console to match your new string, or all of your servers in CIM will revert to black icons.

 

[Guest_imported]

Has anyone solved this???

 

[lilasplace]

I am having the same issue with one of my Compaq Servers. It has been inaccessible for a period of time. I am running version 5.3.

I also have alot of problems with the batteries on the insight board on two other systems. They are always sending alarms regarding the battery/battery interface at least one or twice a month). The status changes for a short period of time (sometimes) without changing the batteries after reboot, but not always.

 

[jkallen]

The battery issues are on what kind of insight boards (EISA/PCI?) If EISA, upgrade the firmware to address the issue. If its PCI, unlug the battery from the card for a few minutes and then re-attch it to reset the card's battery settings.

As far as server showing as black, this means the console is having some SNMP-related issue with the server. First the console has to see that the server is running SNMP and then has to see the Compaq agents on the server.

1) Check SNMP secuirty settings. The "community string" needs to match the community string in the console and it is Case-sensitive. The easiest thing is to set it to "public" as this is the common default. Once you get it all working, change it to somethign else.
2) Check to see that the agents are running properly (there are no community strings for the agents as they ride on top of SNMP.
3) Microsoft has addressed SNMP issues in almost every Svc Pack for every OS - update the service packs.
4) There is a reskit util called snmputil. Run it with these parameters:
snmputil walk <servername> <communitstring> .1.3.6.1.4.1.232

Put all of the above on one line. If you get anything back (besides an error) it means all is working and your console should work. Since the syntax says &quot;walk&quot; it will return pages and pages of info, so you can just kill it if ti works. If it doesn't work, start checking the above suggestions again. This line test not only SNMP, but the compaq agents as well. You can test to see that just SNMP is working by running
snmputil walk <servername> <communitstring> 1.3.6.1.2.1.1.1
This should return the basic system description.


Good luck

 

[nu2ibm]

Sometimes CIM will not pick up a server because the agents are not hooked on to snmp. The best way to insure that the agents get installed correct is to uninstall the agents, uninstall snmp. Reinstall snmp, then sp6 then the CIM agents and of course setup the correct community strings and every thing will work OK

 

[novak]

I have the same issue with inaccesible servers, as NU21BM says, remvoing the agents and SNMP, reinstalling SNMP and agents resolved the issue..