Re: [OpenIndiana-discuss] Problem with Dell iDRAC
On 22 April 2013 20:25, Rich wrote: > What NIC does the machine have? > > My solution on Rx10 with the BCM NICs was to grab the bnx driver blob from > Joyent [ > https://github.com/joyent/smartos-live/tree/master/overlay/generic/kernel/drv/amd64/bnx] > and throw that in /kernel/drv/amd64/bnx, bootadm update-archive, and > reboot. The BMC works great with that driver loaded and not the stock one. > > [I have a ticket about this for Dell R815s - > https://www.illumos.org/issues/1552 ] Thanks for posting this. I also have a T610, and I've just been leaving the bnx interface unplumbed. Not having tested with any other OSes, I wasn't sure if it was even supposed to work. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem with Dell iDRAC
> From: Kris Henriksson [mailto:kt...@cornell.edu] > > I've been having a long-standing issue with using the iDRAC on my > server with OpenIndiana, and I thought before giving up completely, I > could try asking the mailing list. The problem is that the iDRAC is > completely inaccessible while OpenIndiana is running. > > The system is a Dell PowerEdge T610, with Dell iDRAC 6 Express. If I > run Linux on it, the iDRAC can be accessed just fine, and before > OpenIndiana has started booting, I can access it, but with OI running > it is inaccessible. The DRAC shares a physical network port with the > OS, but has a separate MAC address and independent network traffic. I've seen that before. Got over it... I forget precisely how ... I think I had to go into BIOS, and "disable" the first NIC. This makes it inaccessible to the OS, but not inaccessible to the iDRAC. Then, obviously, connect two separate ethernet cables. One for the management interface, and one for the OS. Also, if you ping monitor the OS and the iDRAC... It is normal to see the iDRAC disappear at certain moments during the boot process. So don't assume it's failed the moment ping begins to fail. Wait for the OS to come up completely, and perhaps a minute longer. Oh yeah ... This might be separate, but the built-in broadcom NIC was never stable in solaris 10 / opensolaris. Symptom was a weird sort of black-screen lockup while still responding to ping, which occurred approx once a week. We made this problem go away by buying an add-on Intel server NIC. So it's distinctly possible, that the actual iDRAC solution is to "disable" both the broadcom ethernets in BIOS (use only by iDRAC) and only use the Intel NIC in the OS. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem with Dell iDRAC
Oh. I see now, Rich's solution about updated driver. That sounds better. ;-) > -Original Message- > From: Edward Ned Harvey (openindiana) > Sent: Tuesday, April 23, 2013 8:34 AM > To: openindiana-discuss@openindiana.org > Subject: RE: [OpenIndiana-discuss] Problem with Dell iDRAC > > > From: Kris Henriksson [mailto:kt...@cornell.edu] > > > > I've been having a long-standing issue with using the iDRAC on my > > server with OpenIndiana, and I thought before giving up completely, I > > could try asking the mailing list. The problem is that the iDRAC is > > completely inaccessible while OpenIndiana is running. > > > > The system is a Dell PowerEdge T610, with Dell iDRAC 6 Express. If I > > run Linux on it, the iDRAC can be accessed just fine, and before > > OpenIndiana has started booting, I can access it, but with OI running > > it is inaccessible. The DRAC shares a physical network port with the > > OS, but has a separate MAC address and independent network traffic. > > I've seen that before. > > Got over it... I forget precisely how ... I think I had to go into BIOS, and > "disable" the first NIC. This makes it inaccessible to the OS, but not > inaccessible to the iDRAC. Then, obviously, connect two separate ethernet > cables. One for the management interface, and one for the OS. > > Also, if you ping monitor the OS and the iDRAC... It is normal to see the > iDRAC disappear at certain moments during the boot process. So don't > assume it's failed the moment ping begins to fail. Wait for the OS to come up > completely, and perhaps a minute longer. > > Oh yeah ... > > This might be separate, but the built-in broadcom NIC was never stable in > solaris 10 / opensolaris. Symptom was a weird sort of black-screen lockup > while still responding to ping, which occurred approx once a week. We made > this problem go away by buying an add-on Intel server NIC. So it's distinctly > possible, that the actual iDRAC solution is to "disable" both the broadcom > ethernets in BIOS (use only by iDRAC) and only use the Intel NIC in the OS. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem with Dell iDRAC
On 2013-04-22 22:01, Kris Henriksson wrote: Outstanding! I do have the BCM NIC, and trying the driver you mentioned works like a charm. I've updated the bug you referenced to say that it also affects my system. Hmmm... I think I should try that sometime. For historic sake: we have a Sun Fire X2100M2 in our office zoo, which also has a bge port shared with its remote-management card, another bge port, and a couple of lousy nge ports which can behave strangely even by themselves. Basically, this leaves the system with one reliable port out of four preinstalled - the other bge ;) Sometimes we did have connections lost to the RSC in cases of heavy IO on the port from the OS, losses of link to RSC during server reset, etc. Some reconfiguration of port usage and switch port to try and avoid resets did help - but there are just that, workarounds that need to be remembered to keep in place ;) Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Logwatch equivalent...
Hi, is there a logwatch equivalent under openindiana? Or, what do people usually setup to get daily server status by mail? Thx, JD ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Pounding on well trod ground..
"Edward Ned Harvey (openindiana)" writes: >> Once I have a running install, is the syntax for the packages still >> something like REPONAME/dev? > > sudo pkg search subversion > sudo pkg install subversion > (or whatever) I probably phrased poorly. What I'm asking there is once the OS is installed and working. If I want a software package using the gui software management tool, and I want to keep up with the development version ... we used to have the name of the repo and the dev directory after plugged into the software tool. Something like: REPONAME/dev So I'm asking for the address to use with the gui software tool? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Logwatch equivalent...
Can you explain further? Did logwatch work for you previously on OpenIndiana, then stop? Logwatch is written in Perl, and should run on any Unix, or Unix clone with Perl installed. Jerry On 04/23/13 09:01 AM, John Doe wrote: Hi, is there a logwatch equivalent under openindiana? Or, what do people usually setup to get daily server status by mail? Thx, JD ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NFS exported dataset crashes the system
Hi. We have almost the same hardware as yours and we had the same issue. We have exported a ZFS pool to three Xen VMs Debian 6.0 mounted using NFSv3. When one of these boxes launches a highio PHP process to create a backup, it creates, copies and deletes a large amount of files. The box just crashed the same way as yours, during the deletion process, no ping, no log, no response at all. We had to do a cold restart unplugging system power cords... We have changed to NFSv4 hoping to fix this issue. Can please comment your results regarding this issues? Any help would be kindly appreciated. Best Regards, I've asked the ZFS discussion list for help on this but now I have more information and it looks like a bug in the drivers or something. I have number of Dell PE R710 and PE 2950 servers running OpenSolaris, OI 151a and OI 151a.7. All these systems are used as storage servers, clean OS install, no extra services running. The systems are NFS exporting a lot of ZFS datasets that are mounted on about ten CentOS-5.9 systems. The above setup has been working for 2+ years with no problem. Recently we bought two Supermicro systems: Supermicro X9DRH-iF Xeon E5-2620 @ 2.0 GHz 6-Core 128GB RAM LSI SAS9211-8i HBA 32x 3TB Hitachi HUS723030ALS640, SAS, 7.2K I installed OI151.a.7 on them and started migrating data from the old Dell servers (zfs send/receive). Things have been working great for about two months until I migrated one particular directory to one of the new Supermicro systems and after about two days the system crashed. No network connectivity, black console, no response to keyboard keys, no activity lights (no error lights either) on the chassis. The only way out is to hit the reset button. Nothing in the logs as far as I can tell. Log entries just stop when the system crashes. In the following two months I did a lot of testing and a lot of trips to the colo in the middle of the night and the observation is that regardless of the OS everything works on the Dell servers. As soon as I move that directory to any of the Supermicro servers with OI151.a.7 it will crash them within 2 hours up to 5 days. The Supermicro servers can be idle, exporting nothing, or can be exporting 15+ other directories with high IOPS and working for months with no problems but as soon as I have them export that directory they'll crash in 5 days the most. There is only one difference between that directory an all others exported directories. One of the client systems that mounts it and writes to it is an old Debian 5.0 system. No idea why that would crash a Supermicro system but not a Dell system. We worked directly with LSI developers and upgraded the firmware to some unpublished, prerelease development version to no avail. We disabled all power saving features and CPU C states in the BIOS and nothing changed. Any idea?I had a similar kind of problem where a VirtualBox Freebsd 9.1 VM could hang the server. It had /usr/src and /usr/obj NFS mounted from the OI a7 box it was running on. The are separate NFS shared datasets in on of my 3 pools. When I ran a make buildworld in that VM it consistently locked up the OI host, no console access, no network access ( not even ping ). As a test I switched to NFSv4 instead of NFSv3 and I have not seen a hang since. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
