Optivity 9.2 Unix/HP Openview - topst Process

[rmmagow]

The process topst running from /opt/lnms/bin/topst (parent topcd) is really eating up my machine, 40~60% CPU. This station is an ES450 with dual procesors so I'm inclined to think I'm not resource constrained. I used the "validate optivity DB" function in HP Openview to build my database after the Optivity install. Through the start options for Optivity I have disabled the "SuperPing" function as advised by Nortel. What exactlyis this topst trying to do that it eats up so much CPU. Can the process be tuned ? Thanks for any info.

 

[sysmanrick]

What version of Optivity are you using? I have 9.2.0 with patch(es) 9.2.0.1 & 9.2.0.2.I have a call open for Topst running away after a aborted seed discovery.No Openview is installed.

 

[rmmagow]

Just 9.2.0 out of the box. No patches installed yet. The validate optivity DB is I think the equivalent of the seeded discovery process. I too have a ticket open w/Nortel about this. I'm going to try to patch the system later this week but I'm guessing it's not gonna help a lot. How many nodes are you trying to manage ?

 

[goin2cisco]

I have never been able to get Optivity to run auto discovery. I am running it on a COMPAQ dual 750MHZ with 512MB ram. I went to class on it 14 months ago. Spent forever trying to get it to work properly. I have 5380 routers. We found it was receiving the ARP cache too...I think it is a piece of junk.

 

[Guest_imported]

Hey going2cisco. What seeds did you define? have you checked that you can get snmp request back to the nms box?

try this trick if you are on teh nms server \optivity\campus\campus\unsuppt\nman -c <read community string> -a 1.3.6.1 x.x.x.x were x.x.x.x is an ip for a peice of hardware on your network.
If you fail to get a screen dump of mib data (raw text) then its a snmp issue, or the comm string you
used does not have readd access for the host ip address (your nms server).