Compaq MIBs not seen in snmp?

[Ayman Altounji]

We have installed Insight Manager 7 on a central console with static ip address and are now in the process of rolling out agents to servers across the division. However, 2 servers in particular are giving me a real headache. I installed snmp, reinstalled SP6a and then Compaq NT supportpaq 1.10a with 5.3 agents. We have configured a snmp community which is the same as all the other servers but for some reason the console does not pick up all the snmp information.

For example, if I connect to the server http://server:2301 and look at system info I get the following info:

General Information
Product: N/A
Operating System: NULL NULL
N/A
Machine ID (System Board): N/A
Expansion Bus: ISA

Description
System Name: RUGNT01
Description: Hardware: x86 Family 6 Model 1 Stepping 9 AT/AT COMPATIBLE - Software: Windows NT Version 4.0 (Build Number: 1381 Uniprocessor Free )
Network Management Up Time: Days: 0, Hours: 0, Minutes: 20
Contact Information: Network Services
Location: 01788 535329
IP Address: 172.16.2.10

It therefore looks to me as though CIM is only picking up some of the snmp mibs (such as system description and uptime) but not the compaq mibs. This is backed up by the fact that via http I can only see standard mibs (i.e there is no integrated management log view). Because this is only happening on these two servers does that mean that it is a failed snmp or agent install on these particular boxes? I've looked at the compaq support website but to no avail. I'd be really grateful for a resolution to this one as I'm now reluctant to carry on with the roll out of CIM agents until I find out if I'm doing something wrong. I've removed and reinstalled the cim 5.3 agents but it hasn't fixed it.

Cheers

Neil Binnie
DSSmith Packaging

[Ayman Altounji]

Check the NT Event Log - this information is provided by the agents so if they aren't running you'll see this. My guess is you'll see an entry indicating that one of the agents isn't starting right.

[Ayman Altounji]

Sadly the event log shows no problems, we haved removed snmp, reinstalled it, ran SP6a and the NT support paq 1.10a but all to no avail. If I compare serverA (OK) and ServerB (not OK) I've looked at the snmp settings and they are exactly the same on both servers. The compaq services are exactly the same on both servers with one exception serverB is running the compaq vcagent - could this be the problem? All compaq services are running as local service and snmp is running on both servers.
I'll remove the vcagent from serverB and see if its causing a conflict. Other than that the servers are as identical as I can make them (hardware, firmware, OS and software)

Thanks in advance for any help you can offer.

[Ayman Altounji]

We have a dispersed fleet over 35 sites all running Proliant 2500 and 1600 servers as the backbone of NT and exchange.

The current update methodology is to:

Update bios to latest release
Update array controller (mainly smart array 2DH) to latest firmware
Update system partition using Smart Start 5.2 CD
Run Compaq Support Paq for NT 1.10a we usually just accept the default and let the programme decide what components to install (we run the config programme first which I'll discuss below)

The snmp is configured as:

All services checked
Community name 'compaq' is given read_create rights (We usually delete all references to public and private communities)
Accept packets from any host
Traps are configured to send traps to a static IP address (CIM server)
Data collection interval is 2 minutes
SNMP sets enabled
Remote reboot disabled

If I send a test trap from the agents applet in control panel its seen on the server, but as I've mentioned earlier the compaq portion of the snmp config doesn't seem to be recognised ie if I open up the server homepage on http://server:2301 (and then to the ssl link) the problem servers do not show the existence of the Integrated Log option and a lot of the snmp info is left blank (e.g product id).

One thing that we've just noticed is that some of the working servers are using the snmp community 'private' for their control community and dsspit for their monitor community. Does snmp require separate distinct community names for monitor and control either woithin snmp or within CIM?

Neil

[Ayman Altounji]

CIM7 does not require distinct community strings. However, there must be one community string set to READ CREATE for the agents to work right. Also, localhost must be allowed to make SNMP requests if you are using IP-based security.

Take a look at the FAQ for the question of Q: Why are my servers listed as Unknown devices? One of these answers might be relevant for your situation.

You can find the FAQ on the CIM7 page off of www.compaq.com/manage or directly at ftp://ftp.compaq.com/pub/products/servers/management/cim7/cim7-FAQs.doc

Scott

[Ayman Altounji]

Hi, If you are getting NULL Values showing, I have traced this back to a systemBoards being replaced and the person who did it used the backup.chl file instead of a re-discover, the Info that is populated in the F10 Partition is missing, you could-With a good back up, Pull your drives and do a system erase, re -smartstart the server, add any info like serial Number, system Name, location, etc, This is usually the issue, You might want to have a Compaq or HPAQ Tech onsite to asist you,

[Ayman Altounji]

Thanks for all the advice. We managed to get a compaq techie on site who was also stumped (always a relief when they don't click one button and say its the first thing in the manual!)

The only resolution we have found is to:
remove snmp
remove insight agents
reboot
install snmp
reboot
install SP6a
reboot
install insight agents
reboot

this seems to do the trick although as can be seen it takes a while.