How about the MRTG code ?? that would help.
Message: 2 From: "Jon Cloud" <cloud@fsr.com> To: <usr-tc@mailman.xmission.com> Date: Thu, 10 Oct 2002 11:00:07 -0700 Subject: [USR-TC] tcs upgrade resulted problem with MRTG. Reply-To: usr-tc@mailman.xmission.com
Hello everyone one. First off I just want to say thanks. I've only posted to the group twice, but have found the list to be some of the best techsupport for TC problems and knowledge. I think something similar to my problem has been discussed before, but my computer couldn't handle the 21 MB archive file very well. So if this question has already been addressed in the list, I'm sorry I couldn't find first.
Any ways, I have a Total Control chassis with a HiPer DSP, a hyper ARC, management card, and power supply. This setup used to be in production running TCS 3.5 or 3.6 maybe even lower, sorry I can't remember the exact version any more; recently my company pulled the chassis from its service area to relocate it. During this move I thought, "Hey this would be a great time to update the TCS code since its not in use." So I did just that, I inventory the chassis and updated everything to TCS 4.0 which is the highest versions the combined hardware could support.
For the most part this went okay, the chassis is back in the field taking calls and working great. However, I swear the question is coming soon :), when we went to setup MRTG for the modem usage the results were incorrect. Instead of displaying the number of logged in users of the DSP, it displayed value of the number of successful logins, including logins from scripts telneting to the chassis. The result is a graph with an increasing slope, and prior to the updated firmware MRTG worked flawlessly with this chassis. We're using the same OID as before and have looked at the mib file to verify that the OID in use is the one we should be using. I guess my questions are, has anyone seen this kind of behavior with this version of TCS, or other versions? If so, were you able to fix them and how? If not, any suggestions? I'm currently trying to reflash ARC with the same code, as a "just in case" precaution; I have also thought about downgrading the code on the ARC to see if that improves anything.
Here is the current hardware info from the chassis inventory if this will help.
3Com 17-Slot Chassis with PB clocking
SLOT | CARD | HARDWARE VERSION | DRAM (KB) | FLASH (KB) | SOFTWARE VERSION | 1 3COM High-Density 24 Channel NAC 0.53.0 8192 2048 2.0.19 16 3COM HiPer ARC NAC 15.0.0 131072 16384 5.0.9 17 3COM NMC w/ clock 6.0 16384 8192 7.1.8
Any pointers, or solutions would be appreciated, and if I have left out any details which may help please let me know.
Thanks again for your input.
Jon Cloud -- First Step Internet.