NIC teaming configuration is not restored after restoring backup to a dissimilar hardware using Veritas System Recovery.
Article ID: 100033795
Updated On:
Resolution
NIC teaming/bonding combines multiple physical interfaces into a single virtual interface. The process of creating the teamed or bonded interface will create internal configuration information that describes the teamed or bonded virtual interface by the physical adapter ports that makes up the virtual interface.
The physical ports in use are identified by the MAC address associated with it. When a server boots up, the network teaming driver is loaded into kernel space and attempts to acquire the needed physical ports (as noted in its configuration section) , replacing the physical port hardware paths with the teamed/bonded virtual device path.
When the recovered client reboots to its restored state, the NIC teaming will attempt to perform the teaming function. If the interface ports that were configured for teaming are not present on that server, the teaming function will fail.
Hence after restoring backup to dissimilar hardware, NIC team may fail and would require manual intervention. This behavior by design.
The physical ports in use are identified by the MAC address associated with it. When a server boots up, the network teaming driver is loaded into kernel space and attempts to acquire the needed physical ports (as noted in its configuration section) , replacing the physical port hardware paths with the teamed/bonded virtual device path.
When the recovered client reboots to its restored state, the NIC teaming will attempt to perform the teaming function. If the interface ports that were configured for teaming are not present on that server, the teaming function will fail.
Hence after restoring backup to dissimilar hardware, NIC team may fail and would require manual intervention. This behavior by design.
Issue/Introduction
NIC teaming/bonding combines multiple physical interfaces into a single virtual interface. The process of creating the teamed or bonded interface will create internal configuration information that describes the teamed or bonded virtual interface by the physical adapter ports that makes up the virtual interface.
The physical ports in use are identified by the MAC address associated with it. When a server boots up, the network teaming driver is loaded into kernel space and attempts to acquire the needed physical ports (as noted in its configuration section) , replacing the physical port hardware paths with the teamed/bonded virtual device path.
When the recovered client reboots to its restored state, the NIC teaming will attempt to perform the teaming function. If the interface ports that were configured for teaming are not present on that server, the teaming function will fail.
Hence after restoring backup to dissimilar hardware, NIC team may fail and would require manual intervention. This behavior by design.
The physical ports in use are identified by the MAC address associated with it. When a server boots up, the network teaming driver is loaded into kernel space and attempts to acquire the needed physical ports (as noted in its configuration section) , replacing the physical port hardware paths with the teamed/bonded virtual device path.
When the recovered client reboots to its restored state, the NIC teaming will attempt to perform the teaming function. If the interface ports that were configured for teaming are not present on that server, the teaming function will fail.
Hence after restoring backup to dissimilar hardware, NIC team may fail and would require manual intervention. This behavior by design.
Was this article helpful?
Yes
No
Powered by
