Data Domain: Intel E810 Interfaces May Fail to Initialize After Upgrade

One or more network interfaces do not come online correctly after a DD OS upgrade and reboot.
Network connectivity tests such as ping may fail on affected interfaces.
Interface-specific routing tables and routing rules are missing after the upgrade.
Network communication may not resume until the affected interfaces and corresponding switch ports are reset.
System logs may contain link parameter configuration errors during interface initialization.
Routing rules are automatically recreated after affected interfaces are manually disabled and re-enabled.

Example
Prior to the upgrade, interface-specific routes and routing rules are present.
For example, output similar to the following may be observed:
Before Upgrade
IPv4 Default Gateways:

Gateway 172.16.50.1 via interface address 172.16.50.40/24
Gateway 172.16.50.1 via interface address 172.16.50.41/24
Gateway 172.16.50.1 via interface address 172.16.50.42/24
Gateway 172.16.50.1 via interface address 172.16.50.48/24

Associated routing tables contain:

Default route via gateway 172.16.50.1
Connected subnet route for 172.16.50.0/24

Interface-specific routing rules tied to the source IP address and egress interface

After Upgrade and Reboot
The interfaces may appear configured, but the interface-specific routing tables and routing rules can be missing entirely for affected interfaces. As a result, network communication may fail even though IP addresses remain configured on the interfaces.
After the affected interfaces are disabled and re-enabled, the routing tables and routing rules are recreated automatically and connectivity is restored.

This issue can occur during interface initialization after a DD OS upgrade and reboot. On affected systems, the network initialization process may fail to correctly configure link parameters, causing interfaces to not fully initialize and preventing expected routing rules from being created.
The issue has been observed on systems using Intel E810 network adapters connected with Direct Attach (DA) cables. As a result, interface-specific routing entries may not be established, leading to connectivity failures on the affected interfaces.
Symptoms may coincide with interface initialization errors recorded during boot or during subsequent network configuration operations.

As an immediate recovery action, restore connectivity by reinitializing the affected network path.
This may involve:

Disabling and re-enabling the affected Data Domain interfaces.
Bouncing or resetting the connected switch ports.
Verifying physical link establishment between the Data Domain interface and the switch.
Confirming that interface link negotiation completes successfully.
Verifying the interfaces return to a RUNNING state.
Confirming that interface-specific routing tables and routing rules have been recreated.
Validating network connectivity after the interfaces have been re-established.

In the investigated case, connectivity was restored after the affected Data Domain interfaces and associated switch ports were bounced. Once the interfaces reinitialized successfully, the missing routing rules were recreated and network communication resumed.
Long-Term Resolution
Customers experiencing this behavior should upgrade to DDOS-8.3.1.40, DDOS-8.6.1.20, DDOS-8.7.0.1, DDOS-8.8.0.0 or a newer maintenance release containing the fix. Upgrading is recommended to prevent recurrence during future reboots, upgrades, or interface initialization events.