Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oxidized is in a loop with a device? #3242

Open
MLyszyk opened this issue Aug 9, 2024 · 1 comment
Open

Oxidized is in a loop with a device? #3242

MLyszyk opened this issue Aug 9, 2024 · 1 comment

Comments

@MLyszyk
Copy link

MLyszyk commented Aug 9, 2024

Hey all,

I believe something weird is going on with this device(s) that Oxidized is pulling. We are getting numerous emails of config changes for a device that seems to be in a loop. For instance, one email for the switch will say this -->

interface eth-0-7
  flowcontrol receive on
- switchport access vlan 3438
+ switchport access vlan 2094
 !
 interface eth-0-8
  flowcontrol receive on
- switchport access vlan 2482
+ switchport access vlan 2095

Then, the next email will say this -->

interface eth-0-7
  flowcontrol receive on
- switchport access vlan 2094
+ switchport access vlan 3438
 !
 interface eth-0-8
  flowcontrol receive on
- switchport access vlan 2095
+ switchport access vlan 2482

Then, after those 2 being sent, it'll send another email that says this -->

interface eth-0-7
  flowcontrol receive on
- switchport access vlan 3438
+ switchport access vlan 2094
 !
 interface eth-0-8
  flowcontrol receive on
- switchport access vlan 2482
+ switchport access vlan 2095

And then it just keeps on going, and it's not just that interface it does this with but the overall switch config. Is there a database that Oxidized is using to hold the pulled configurations of a device that gets used for comparison against newly pulled configs for that device? Maybe if I remove the existing file, the next time it'll pull will be that device's "first time"? But I assume that means I'll lose all configuration iterations that have occurred which can be seen on our Oxidized-Web.

Any ideas or tips?

Thanks!

@robertcheramy
Copy link
Collaborator

Please give more context:

  • which version of oxidized are you running?
  • give your oxidized configuration (with everything you don't want to share like passwords remove/modified)
  • which model are you using?

It seems like a configuration flapping to me, oxidized just informs you that the configuration changed.
Check on the device that the configuration did not change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants