[nv-l] A plea for anyone who used the old Tivoli Manager for Network Connectivity product

["Van Order, Drew \(US - Hermitage\)" <dvanorder@deloitte.com>]

We are still using TFNC with NV 7.1.4. The product has been bulletproof for us; we've never needed to touch anything other than config files. Our NV environment has grown, so we decided to tweak 2 settings--number of trap applications from 2000 to 4096, and changed the ovwdb cache to 10,000 from 5000. The sm_ipfm process has suddenly started consuming considerable CPU. I changed the NV settings back, but sm_ipfm did not change. We have a failover server and a dev box--same behavior. Documentation, the list archives, and IBM's support DB have very little about TFNC. While things are running, we would like to know why sm_ipfm suddenly changed and what we can do to better understand what's going on. Our 6 CPU, 4 GB RAM AIX box went from uptime of .2 to consistently over 1.1, periodically pegging individual CPU's to where they alert us. The smaller boxes are taking a bigger beating.

We know we need to move off TFNC, but I have not seen how we can get the same results with the newer versions of NV and TEC. Any advice on that is appreciated as well. Many thanks--Drew

Drew Van Order
ESM Architect
(615) 882-7836 Office
(888) 530-1012 Pager

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.