Cross-posted to IBMVM and LINUX390 lists
It was a subtle but significant error when renaming the ifcfg-eth0 files. It
didn't dawn on us why the D/R copy was named DRifcfg-eth0, but the renames
proceeded thus: mv ifcfg-eth0 ifcfg-eth0OLD followed by mv DRifcfg-eth0
ifcfg-eth0. The problem is that both files now began with ifcfg-eth0, so they
"stepped on each other" (or possibly the "old" copy simply got found first at
network service startup time). Renaming the "old" copy (mv ifcfg-eth0OLD
OLDifcfg-eth0) resolved the problem.
That will be prominently highlighted in our D/R documentation for next time.
Thanks to all who offered ideas, things to check, etc.
-jc-
**********************************************************************
Information contained in this e-mail message and in any attachments thereto is
confidential. If you are not the intended recipient, please destroy this
message, delete any copies held on your systems, notify the sender immediately,
and refrain from using or disclosing all or any part of its content to any
other person.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
