our Network techs are seeing alot of extra overhead and they believe it is because of layer2, and 3, being checked they want to disable this 'feature' is there an easy way to do this or do we have to do it through SQL?
JWERELIN,
To disable topology calculations:
HTH,
So I have over 2000 devices in our network are you saying I need to do this 2000 times? Is there a way to globally do this?
JWERELIN,
To disable topology calculations:
- Log in as an administrator to the Orion Web Console on the SolarWinds server that is polling the object for which you want to disable topology calculations.
- Click Settings in the top right corner of the web console.
- Click Manage Nodes in the Node & Group Management grouping.
- Check the node for which you want to disable topology calculations, and then click List Resources.
- Clear all Topology checkboxes.
- Click Submit.
HTH,
If a new enhancement is to make a global change to systems, there needs to be a solution to globally remove this change.
Not all enhancements are desired by all customers and could cause havoc on client networks.
Like Car3737 I have over ... well alot of devices. to remove this wonderful addition.
is there a way to do it globally?
Hello all--
I have this marked for the PM to comment on.
Thanks,
DH
Can we please bump the priority on this?
I too have had the same request from my network team to disable this new feature globally. We've verified that this new feature caused some of our Cisco 37xx series switches that normally had very stable ~10% CPU utilization to go to >80% CPU utilization when this feature is enabled. De-selecting "Topology: Layer 2" and "Topology: Layer 3" did result in CPU going back to normal levels. However doing this on thousands of devices is not a viable option; particularly when we have many switches with hundreds of interfaces where it takes several minutes to enumerate the interfaces on a single switch. Multiply 3 minutes by 2000 devices and this equals someone's full time job for 12 and a half days.
Like RichC, we also have issues on our Cisco switches CPU usage climbing to 100% when a rediscovery of interfaces is done. This happened every 60 minutes, changing the polling settings for this rediscovery to 1440 minutes, reduces the peak CPU load to once a day.
However, the company would like to see a global way to disable the layer 2 and 3 topology instead of going over thousands devices manually.
Polling of L2 and L3 topology data might be disabled by removing topology poller assignments from Pollers table in Orion Database.
To remove all L2 and L3 topology pollers, please execute this SQL statement:
DELETE FROM Pollers WHERE PollerType LIKE 'N.Topology.SNMP.%'
To remove all L2 topology pollers only, please execute this SQL statement:
DELETE FROM Pollers WHERE PollerType LIKE 'N.Topology.SNMP.Layer2'
To remove all L3 topology pollers only, please execute this SQL statement:
DELETE FROM Pollers WHERE PollerType LIKE 'N.Topology.SNMP.Layer3'
Once pollers are removed, it should take up to 30s for Orion to notice this change and stop gathering topology data.
zizi,
SW should not depend on if their clients have SQL programmers on staff. I highly recommend that if there is a SW decision to implement something globally on any / all future deployments there be an admin setting to enable, modify, or disable a feature. It may also be recommended that the feature be initially disabled thus providing the network managers the option to enable it.
The feedback on this forum should indicate that device polling does effect device performance and the implementation global settings has had a negative impact on SW clients.
Since the people responding on this forum are generally the people on the front line in response regarding their companies' network it does make their job much more difficult.
Is there a way to globally re-enable this feature after it is removed.?
We are in the process of co-ordinating the removal. contacating the DBA group for back-up and restore support and others who may be impacted.. lets just say .. this will cost the company time and money because we have to allocate resouces accross multiple areas..
I agree. with the general concensus.. a global add/ removal is good. but also consider making it by device type, router, switch , access Point, Servers, etc...
This is a way to disable it at a poller level.
Go to the installation path, for example, C:\Program Files\SolarWinds\Orion and find the following file. SolarWinds.Orion.Core.BusinessLayer.dll.config Open the file with Notepad and set the property TopologyEnabled="False"
If you set TopologyEnabled="False" in SolarWinds.Orion.Core.BusinessLayer.dll.config, you will disable only calculations. Pollers will collect data same way as before, use ZiZi way to achieve fully disabled topology pollers.
Last but not least, create feature request, we are see your needs but feature request is best way to notice PM from customer side. Thank you
Hi Everyone, i would never suggest just delete data without checking first..
here is a little helpful script to check what nodes..
select PollerID, PollerType, substring(netobject,3,10)as NodeID, n.Caption, n.IP_Address
from Pollers p
inner join nodes n on n.nodeid = substring(netobject,3,10)
WHERE p.PollerType LIKE 'N.Topology.SNMP.Layer3'
If you then wish to just delete some of the pollers and not others, you can build your DELETE script using the node id column - just add them to the final section with a comma inbetween..
DELETE FROM Pollers WHERE PollerType LIKE 'N.Topology.SNMP.Layer3'
AND substring(netobject,3,10) IN (1,2,3,4) -- this is the NodeID (1,2,396,2000)etc
Check out our newest Script Guru :) Thanks for sharing mezdem!
DH
