In my experience LC and iDRAC NIC setting and/or config issues are best solved by updating the Firmware on the iDRAC, LC and NIC, then resetting the LC with the 'Repurpose' function and checkboxing a) Reset LC to Defaults and delete Logs and Config Data b) iDRAC Reset to Defaults
http://delltalk.dell.com/latest_poweredge-13g.html#R230%20Network http://delltalk.dell.com/latest_poweredge-13g.html#R230%20iDRAC%20with%20Lifecycle%20Controller If the server firmware hasn't been updated for a while (lets say 1 or 2 years) avoid using the LC and instead use this bootable ISO: https://dell.app.box.com/bootableR230 On Tue, Mar 21, 2017 at 11:59 AM, Kuzmin, Evgeniy <[email protected]> wrote: > Hi, > > > > We have observed an intermittent issue with networking while installing > our Dell R230 server. Please see the details below. > > > > After the target OS installation the network was not accessible. Looking > at the ifconfig output we saw that there were some TX packets sent but no > RX received. We have tried various settings in the server configuration to > resolve the issue and found 2 ways that worked for us: > > > > 1) Configure the NIC IP address in R230 settings with the same IP we > wanted to use on our system. Hovewer, when we switched the IP on the OS > side, server had become unavailable again. > > 2) Configure the iDRAC IP in the same subnet with the IP address supposed > to be used by OS and set "OS to iDRAC Passtrough" option to "LOM". It looks > like this setting doesn't have any direct influence on the host networking, > but we have suggested that it can change some internal routing in the R230. > Anyway, it made the system working. > > > > On the other hand we have the second server that has same hardware with > the problem one (according to the hardware diagnostic dump). On this server > the problem has not been reproduced - we just powered it on, installed our > OS from CD and set the IP address on the OS side. The second server works > fine without any additional configurations. > > > > The main problem is that after resetting iDRAC and NIC configuration > parameters of the problem server to default, the problem has disappeared. > It is not reproducible now - we can use the server with no NIC IP config > and no iDRAC. So, unfortunately we are not able to catch logs or traces for > now. > > > > The operating system we have installed is the old customized Debian 4.0 > (x32), however the same OS was installed without any issues on the second > server. So it doesn't seem this is related. > > > > Could you please take a look at this and provide some explanation of that? > Is there any existing problem that can cause such a behavior? > > > > Thanks in advance! > > > > Thanks, > > Evgeniy Kuzmin > > > > _______________________________________________ > Linux-PowerEdge mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > -- Tech III * AppControl * Endpoint Protection * Server Maintenance Buncombe County Schools Technology Department Network Group ComicSans Awareness Campaign <http://comicsanscriminal.com>
_______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
