Edit Interface - Custom Bandwidth

Hi,

NPM v10.1.3

When changing the Custom Bandwidth from say 10 to 100 or 100 to 1000 Mb/s on an interface, submitting and running a manual poll on the interface and or the node, the Bandwidth gets reset back to the value it had before setting a "Custom Bandwidth".

My question is when can we expect to see this working and or when will the Custom Bandwidth setting be removed to avoid confusion?

Cheers

Find more posts tagged with

edit_interface

custom_bandwidth

Accepted answers

fcaron

What David describes is the known issue (60988).

So we are back to the initial suggestion.

Tks David.

Deltona, can you post here the result of the test that David suggests? Tks

Also, we are taking your suggestion into account (gray-out)

All comments

Deltona

bump

fcaron

This is a known issue, that happens sometimes, usually triggered by a high number of elements being polled and short polling period (i.e. general load). How many elements do you have on teh same polling engine and what is the polling frequency?

There are possible workarounds that you might want to look at:

#1. Stop Netperfmon service before doing the adjustments (i.e. setting the bandwidth) and re-start it after the config change. With this sequence, your change should stick and be permanent.

#2 Reduce the load by off-loading some elements elsewhere if possible and/or reduce polling frequency.

We are tentativelly looking at a fix in the next version of NPM. (60988).

If you try one of these workarounds, would report result here?

Tks Deltona.

Deltona

Hi Francois,

This particular setup is currently polling around 20 some nodes and 400 odd interfaces, all SNMP.
Setting a custom bandwidth does work but only when done through Manage Nodes > check interface > Edit Properties. When done through Manage Nodes the changes stick even after repeated polls :-)

However, changes made under Edit Interface and Custom Bandwidth in particular does not work if you start from the Interface Details - <interface name> page/view.

Strange!

/Orion/NPM/InterfaceProperties.aspx?Interfaces=412&ResourceID=159&ReturnTo=aHR0cDovL21haWwuZHJhd2FyZS5kay9Pcmlvbi9OUE0vSW50ZXJmYWNlRGV0YWlscy5hc3B4P05ldE9iamVjdD1JOjQxMiZ2aWV3PUludGVyZmFjZURldGFpbHM=

The above url is displayed after clicking on Edit Interface, coming from an Interface Details page/view. If i remove the following string: ?Interfaces=412&ResourceID=159&ReturnTo=aHR0cDovL21haWwuZHJhd2FyZS5kay9Pcmlvbi9OUE0vSW50ZXJmYWNlRGV0YWlscy5hc3B4P05ldE9iamVjdD1JOjQxMiZ2aWV3PUludGVyZmFjZURldGFpbHM=

... hit return and make changes to the reloaded page then it works. The changes for Custom Bandwidth stick!

I can confirm that this is not a caching issue from the client side.

Sincerely,
Deltona

fcaron

Interesting.

Does not look like the one we had already, even though the symptoms match. Let me ask internally.

Halef

Hello,

When changing the Custom Bandwidth from say 10 to 100 or 100 to 1000 Mb/s on an interface, submitting and running a manual poll

please don't do the poll. This is indeed a known issue. Heavy load is one way to reproduce it, and a manual Poll Now right after the change is second.

Try setting the bandwidth and NOT trigger Poll Now for a minute or two. After that, the bandwidth should be stored properly.

DaP

Deltona

Hey David,

Could we include a function that greys out the Poll Now and or Rediscovery buttons for a minute or two after changes have been made to if/node properties?
This would be more of a patch than a fix but one that would work non the less...

Thanks for your input guys!

Deltona

fcaron

What David describes is the known issue (60988).

So we are back to the initial suggestion.

Tks David.

Deltona, can you post here the result of the test that David suggests? Tks

Also, we are taking your suggestion into account (gray-out)

Deltona

Sorry been AWOL for a week.

I can confirm that the test as David suggested works.