pt-summary should give better info about bonding interfaces

Bug #1177037 reported by Jay Janssen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Invalid
Undecided
Unassigned

Bug Description

For example:

# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: b4:b5:2f:5d:34:94
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: b4:b5:2f:5d:34:95
Slave queue ID: 0

However, all that pt-summary outputs is:

# Network Devices ############################################
  Device Speed Duplex
  ========= ========= =========
  bond0
  eth0 1000Mb/s Full
  eth1 1000Mb/s Full

Would like info in the summary on:
- bonding type (fault-tolerant in this case)
- slave status (eth0 and eth1's status in the bonding), which is active, etc.

Tags: pt-stalk
Revision history for this message
Daniel Nichter (daniel-nichter) wrote :

Thanks for the sample output. Since this isn't a bug, I've created https://blueprints.launchpad.net/percona-toolkit/+spec/pt-summary-better-bonding-if-info

tags: added: pt-stalk
Changed in percona-toolkit:
status: New → Invalid
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1109

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.