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

Auto remediate bonding issue #61

Open
rjsuresh opened this issue Feb 26, 2019 · 2 comments
Open

Auto remediate bonding issue #61

rjsuresh opened this issue Feb 26, 2019 · 2 comments
Assignees

Comments

@rjsuresh
Copy link

We often see issues with interface goes down in a bonding configuration which can be simply brought up/fix by ifup/ifdown (60 to 70%) of the time.

  1. validation of OS
  2. check bonding cat /proc/net/bonding/bond1 (active / passive - based on the type of bonding configuration)
  3. ifdown
  4. ifup
  5. validate.

if not up,

file a ticket to do the following.

  1. check the link on the switch port, if not green engage network team. If that is not fixing,
  2. clean the SFP/reseat it, if not fixing
  3. change the SFP, if not fixing
  4. change the fiber, if not fixing
  5. Raise a Vendor case
@cholcombe973 cholcombe973 self-assigned this Feb 27, 2019
@cholcombe973
Copy link
Collaborator

Yeah I think we can do that.

@cholcombe973
Copy link
Collaborator

So there's a few ways i can see to handle this:

  • first would be using a library like this: https://github.com/andrew-d/interfaces-rs to get the interfaces on the machine, check if they're a bond and then check the up/down status and take appropriate action.
  • the second way would be to open the /proc/net/bonding directory and open each file in there and parse the output to see if they're up/down and take appropriate action.
    I generally prefer using library calls over parsing text

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

No branches or pull requests

3 participants