Scott's description of the installation process where the system is staged at a service depot, shipped to a customer location, and then configured remote is one we use extensively. We change the Ethernet interfaces before we package and ship the server to the customer. It is very cost effective approach for the customer.
So whatever method you decide to implement to replace the get_def_addr script, should take into account that the interface addresses may change post installation. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Scott Lawrence Sent: Friday, February 13, 2009 11:47 AM To: Dale Worley Cc: [email protected] Subject: Re: [sipX-dev] sipx setup problem? r14720 On Fri, 2009-02-13 at 14:08 -0500, Dale Worley wrote: > On Fri, 2009-02-13 at 09:44 -0500, Scott Lawrence wrote: > > On Thu, 2009-02-12 at 14:11 -0500, Kevin Thorley wrote: > > > On Thu, 2009-02-12 at 13:28 -0500, Kathleen Eccles wrote: > > > > Has anyone seen this behavior? > > > > Revision: 14720 > > > > > > > > > > > > > > > > > > > > Failed to read configuration for │ > > > > > > > > │ /etc/sysconfig/network-scripts/ifcfg-eth0 │ > > > > > > > > │ > > > > Enter network interface settings for this system: > > > > > > Yes, I believe it is because you are using DHCP. Just enter the > > > values manually and all should be fine > > > > See > > http://list.sipfoundry.org/archive/sipx-dev/msg16146.html > > > > for why this was done. > > There are two difficulties with the present situation: > > The major one is that to the naive reader, the message seems to imply > that the script could not read /etc/.../ifcfg-eth0. This is > confusing, because the file is present and readable. It would help > greatly if the message pointed out that it could not find the IP > address and netmask in the file. fair point... I'm making some other changes in there now, I'll try to improve that > The minor one is that it seems to be an unfriendly interface to not be > able to find and read the IP address and netmask if eth0 is configured > by DHCP (which it might well be in many enterprise situations). It is > also more error-prone to have users manually enter the address than it > would be to query the system. But in fact we cannot (based on actual installation experience) assume either that the system is connected to the network at setup time, or that any network it is connected to is the one it will eventually be run on. Some installers prefer to do initial setup in a lab environment that may not even be at the customer site. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
