I'm having an issue of the NIC not being recognized as eth0 after a system board is replaced, with the same hdd installed. eth0 is required for our setup, and this breaks dhcp and halting all accessibility for the machine. Hardware is 4800-782. OS is SLES11 (issue occurs before and after SP1).
These systems are remote, and it is cumbersome to walk a non technical end user (or technician) through the commands to manually reset it, not to mention providing the individual a password. I have a shortcut workaround in place, but I want to determine the root cause and fix the issue at the source.
Any thoughts? Please let me know what further information would be necessary to diagnose.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2011-12-01T23:09:08Z by SystemAdmin
Pinned topic NIC resetting after sys brd replacement
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-12-01T23:09:08Z at 2011-12-01T23:09:08Z by SystemAdmin