Network Management
Polling stops after manual rediscover/poll now on unmanaged entities
Solarwinds stops polling managed entities when any of the unmanaged entities in the polled job group is forced to do poll now or rediscovery now.
First published date
6/24/2023 12:22 PM
Last published date
6/24/2023 12:22 PM
Overview
By default Solarwinds stops polling any entities (nodes/volumes/interfaces) that are unmanaged
However, if you unknowingly did poll now or discover now for an unmanaged Interfaces / Volumes that are part of the polling job (by default 10 entities are poll per job), then you will run into this bug, which will cause polling to stop on managed Interfaces and volumes as well.
And the managed interfaces Next poll and next discovery value is not updated which indicates polling stopped.
Other symptom is you will see a message like below on Interface utilization charts
This was reproduced on entities which are polled in groups and Issue is verified for both volumes and interfaces. E.g. polling stops for group of interfaces of which unmanaged interface was member.
Note, these troup of interfaces are not Orion groups. They are automatically picket i the polling job.
However, if you unknowingly did poll now or discover now for an unmanaged Interfaces / Volumes that are part of the polling job (by default 10 entities are poll per job), then you will run into this bug, which will cause polling to stop on managed Interfaces and volumes as well.
And the managed interfaces Next poll and next discovery value is not updated which indicates polling stopped.
Other symptom is you will see a message like below on Interface utilization charts
This was reproduced on entities which are polled in groups and Issue is verified for both volumes and interfaces. E.g. polling stops for group of interfaces of which unmanaged interface was member.
Note, these troup of interfaces are not Orion groups. They are automatically picket i the polling job.
Product section
Network Performance Monitor
Cause
Bug in product which is triggered when a Unmanaged Interface/Volume is polled or Discovered manually.
Resolution
Bug in product (as of 2023.3), it will be fixed in future version. If you run into this issue, please open a ticket with support.
Workaround:
- Avoid manually polling of interfaces or volumes that are unmanaged.
Workaround:
- Avoid manually polling of interfaces or volumes that are unmanaged.