Data Domain: Bonded Interface Alert Due to Member Interface Speed Mismatch

Current Alerts
--------------
Id Post Time Severity Class Object Message
------- ------------------------ -------- ------- --------------------------- --------------------------------------------
p0-1501 Wed  04:41:42 2026 CRITICAL Network Bonded Interface Name=veth0 EVT-NETM-00015: One or more interfaces in the bonded group has a speed mismatch.
------- ------------------------ -------- ------- --------------------------- --------------------------------------------
There is 1 active alert.
No recent alerts noted in logs.

Bonded interface remains operational, but a critical network alert is reported.
No related alerts may be present in recent logs.
One bond member may be running at a different negotiated speed than the other bond members.

Example of the mismatch:

eth2c = 10Gb/s
eth2d = 25Gb/s

The affected interfaces are members of the same bonded interface (veth0).

The alert is generated when member interfaces within a bonded interface are running at different link speeds.
Although a support bundle may show all interfaces operating at the same speed at a given point in time, later AutoSupport or Elysium data may indicate that one interface has negotiated a lower speed. In this case, interface eth2c was operating at 10Gb/s while eth2d was operating at 25Gb/s, causing the speed mismatch alert for bond veth0.
The alert will persist until all member interfaces within the bond are running at the same speed.
Historically, this issue has most commonly been caused by:

Faulty or degraded network cable
Optical connectivity issues
Transceiver/SFP issues
Switch port configuration mismatches
Switch-side speed negotiation problems

The issue has been observed on both copper and SFP-based connections.

Example troubleshooting steps using virtual interface zero with interfaces ethernet two c. 

Verify the speed of all member interfaces:

net show settings

net show hardware

If one interface is operating below the expected speed, attempt to statically configure the interface for the desired speed.
Remove the Interface from the Bond

net failover del veth0 interfaces eth2c

Configure the Interface for 25Gb/s

net config eth2c speed 25000

Bring the Interface Up

net config eth2c up

Verify the Interface Speed and Status

net show settings

net show hardware

If eth2c successfully comes online at 25Gb/s, add it back into the bonded interface.
Bring the Interface Down

net config eth2c down

Add the Interface Back to the Bond

net failover add veth0 interfaces eth2c

Verify Bond Configuration

net failover show

Verify Both Interfaces Are Operating at 25Gb/s

net show settings

net show hardware

If eth2c is unable to achieve a 25Gb/s link, gather the following information for further investigation:

Latest support bundle
Switch model and operating system
Switch port configuration
Switch port speed settings
Transceiver details
Cable type and connectivity details

Historically, the most common successful resolution has been replacement of the affected network cable.