Page 3 of 5
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Tue Oct 11, 2011 1:10 pm
by nscott
It will take a few minutes for mrtg to make the log file.
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Tue Oct 11, 2011 1:57 pm
by lntinfo
HI,
I have the details to your mail ID, Pls. check.
Thnx
SK
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Wed Oct 12, 2011 9:18 am
by lntinfo
any update???
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Wed Oct 12, 2011 11:10 am
by nscott
LntInfo, I sent a reply.
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Wed Oct 12, 2011 12:28 pm
by brian.gamble
What about me? I cannot run nano command, and cannot install nano. thx
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Wed Oct 12, 2011 1:05 pm
by nscott
I replied to your email this morning. Did it get filtered by spam?
If nano is not installed, then use vi.
vi /etc/cron.d/mrtg
then press 'i'
then go to the end of the line using the arrow keys and add
--debug=time,base,snpo,log --logging /tmp/mrtg.log
Then press escape, and then type
:wq
That should alter the cron directory, now watch the tmp folder. After five minutes you should see mrtg.log in there
cd /tmp
ls
Then send me the .log file.
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Wed Oct 12, 2011 1:10 pm
by brian.gamble
Sorry, couldn't find that email anywhere.
I'm reloading a fresh VM of XI 2011v1.7
I'll post in a few minutes if I'm still having the issue and if so, I'll try the vi command
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Wed Oct 12, 2011 1:23 pm
by brian.gamble
Same issue so I'm going to run the vi commands now and email results.
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Wed Oct 12, 2011 2:31 pm
by brian.gamble
Submitted file via email @ 2:38PM EST
Re: Unable to get bandwidth utilization data from Cisco swit
Posted: Thu Oct 13, 2011 11:00 am
by mguthrie
Just to follow up, we're still investigating this issue, and a few users appear to be having it. We consider this a high priority item so we'll post as soon as we have something