Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion MaxBytes like MRTG

Hello

Currently I use NPM 9.5 SP4 and am getting utilization of over 100%. I see many others on the forums with the same issue and have had tickets with SW open for my issue but noone seems to be able to explain or resolve it. What I would like to know is if there is a feature in NPM (or one that can be added) that is similar to the maxbytes line in MRTG. Which we currently use to monitor our interfaces. Below is an excerpt from MRTG's site explaining maxbytes.

MaxBytes

The maximum value either of the two variables monitored are allowed to reach. For monitoring router traffic this is normally the bytes per second this interface port can carry.

If a number higher than MaxBytes is returned, it is ignored. Also read the section on AbsMax for further info. The MaxBytes value is also used in calculating the Y range for unscaled graphs (see the section on Unscaled).

Since most links are rated in bits per second, you need to divide their maximum bandwidth (in bits) by eight (8) in order to get bytes per second. This is very important to make your unscaled graphs display realistic information. T1 = 193000, 56K = 7000, 10 MB Ethernet = 1250000, 100 MB Ethernet = 12500000. The MaxBytes value will be used by mrtg to decide whether it got a valid response from the router.

If you need two different MaxBytes values for the two monitored variables, you can use MaxBytes1 and MaxBytes2 instead of MaxBytes.

If I could do this in Orion NPM somehow my problem would be solved. Unfortunately i will not be able to use Orion if I cannot get this fixed which is a shame as I do believe it is a great product aside from this issue. If anyone has any other way they solved this issue please respond but I do believe I have tried it all.

Thanks

Mike

Network Technician

Meganet Communications

Find more posts tagged with

Accepted answers

bshopp

This enhancement was just entered recently, so unfortunantly it came in too late to include into the current release we are working on, so we will consider it for the next release potentially.

All comments

SamuelB

I also have this problem with utilization over 100%. Perhaps there could be a checkbox to enable this setting that would use the existing interface receive and transmit values and throw away any (or assume = 100%) when values that are greater are encountered.

scottshipley

The interface monitor gadget in workspace studio in the Engineers toolkit has the same issue. I see spikes on my 1GB link of 5GB, so I know it's not valid.

Meganet

SamuelB, thats exactly what I would be looking for. Hopefully there is a setting somewhere or it can be easily added by the developers.

Meganet

So there is currently no option available such as what SamuelB and I are looking for? I find that surprising if an Open Source product such as MRTG can do what I need and Orion can't? Is it maybe done some other way that I am missing? I see alot of posts of people with over 100% issues, can any of those posters please reply and let me know how your problems were resolved?

Thanks

sedmo

Does NPM show the correct speed for the interface? If not then you can set a custom bandwidth amount on the interface properties.

Another possibility is counter rollover. If you are using 32bit counters and the interface is pushing a fair amount of traffic the counters can roll over between polls and cause strange numbers to be calculated. This can be fixed by setting the "Allow 64 bit counters" property on the node details.

Meganet

Yes it does show the correct speed. I have tried setting a customer bandwidth also but that does not work either. Also I do use 32 bit counters but these are only T1 interfaces and don't push alot of traffic. Cisco only recommends using 64 bit counters on interfaces of 20Mbps or more. Nonetheless I have tried 64 bit counters just for testing. That also did not fix the issue.

Thanks