Re: IPMI SOL setup on FreeBSD 9.1 amd64 supermicro X9SCM-F/X9CL-F
At 09:07 AM 1/23/2013, Anton Yuzhaninov wrote: On Mon, 21 Jan 2013 22:52:17, Derek Ragona wrote: DR I have a couple servers that are built using the supermicro X9SCM-F/X9CL-F DR motherboards, and I can't quite get IPMI SOL working right. DR DR These motherboards have 3 NIC's. One NIC is for a dedicated IPMI interface. DR DR I have both servers configured to use the dedicated IPMI NIC and these DR NIC's are plugged into a separate unmanaged switch. DR DR Both systems boards are set to redirect com1. I changed /etc/ttys to run a DR getty on /dev/ttyu0. I have com1 configured to 115,200 baud, 8, n, 1, no DR flowcontrol in the BIOS. I in have /etc/ttys: DR ttyu0 /usr/libexec/getty std.115200 vt100 on secure /etc/ttys: ttyu1 /usr/libexec/getty std.115200 vt100 on secure /boot/loader.conf: hint.uart.0.flags=0 hint.uart.1.flags=0x10 boot_serial=YES boot_multicons=YES comconsole_speed=115200 console=comconsole vidconsole Anton, Thanks for answering. I thought: /etc/ttys: ttyu1 /usr/libexec/getty std.115200 vt100 on secure is for com2? I also thought: hint.uart.1.flags=0x10 Is for com2? you said: hint.uart.1.flags=0x10 Is that for for a serial only console? I read in some posts, to use: hint.uart.1.flags=0x30 for both a local console with a serial console. I could not find much documentation on the uart or sio flags. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IPMI SOL setup on FreeBSD 9.1 amd64 supermicro X9SCM-F/X9CL-F
On Mon, 21 Jan 2013 22:52:17, Derek Ragona wrote: DR I have a couple servers that are built using the supermicro X9SCM-F/X9CL-F DR motherboards, and I can't quite get IPMI SOL working right. DR DR These motherboards have 3 NIC's. One NIC is for a dedicated IPMI interface. DR DR I have both servers configured to use the dedicated IPMI NIC and these DR NIC's are plugged into a separate unmanaged switch. DR DR Both systems boards are set to redirect com1. I changed /etc/ttys to run a DR getty on /dev/ttyu0. I have com1 configured to 115,200 baud, 8, n, 1, no DR flowcontrol in the BIOS. I in have /etc/ttys: DR ttyu0 /usr/libexec/getty std.115200 vt100 on secure /etc/ttys: ttyu1 /usr/libexec/getty std.115200 vt100 on secure /boot/loader.conf: hint.uart.0.flags=0 hint.uart.1.flags=0x10 boot_serial=YES boot_multicons=YES comconsole_speed=115200 console=comconsole vidconsole -- Anton Yuzhaninov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IPMI SoL oddity on 9.0
I've managed to get SoL to work. Turned out the IPMI is utilizing uart2 on my box so modified loader.conf so uart2 is configured to be the serial console port. hint.uart.0.flags=0x0 hint.uart.2.at=isa hint.uart.2.port=0x3E8 hint.uart.2.irq=10 hint.uart.2.flags=0x10 The handbook does not seem to indicate this very clearly but well, now that it's working, I'm a happy man. ihsan On Jun 13, 2012, at 5:53 AM, Ihsan Junaidi Ibrahim wrote: Folks, I'm hitting a roadblock on getting IPMI SoL up and running on my Supermicro box. It's a X9SCL-F with a dedicated IPMI LAN. I've installed ipmitool and set the necessary console redirects (COM1, COM2 and SoL) in the BIOS. The new AMI BIOS does not seem to indicate the SoL is sharing resources with either one of the two COM ports. All 3 redirect speed is 9600. Serial console works, as far as COM ports are concerned. The BIOS, the boot, loader, kernel messages and TTY are all redirected to the COMs. However SoL only works with the BIOS, boot and reading loader defaults. It will get stuck once it enters the spinning kernel boot and it will stay there. I've tried playing with 0x10 uart flags in device.hints alternating between uart0 and uart1 also to no available in hoping that the SoL port is sharing with either one of the two COMs. Regardless SoL simply will not work entering the kernel onwards. Attached are what I believe the configs relevant to my problem. inf02-kul# cat /boot.config -P inf02-kul# cat /boot/loader.conf autoboot_delay=1 console=comconsole boot_serial= boot_multicons= inf02-kul# grep uart /var/run/dmesg.boot uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (9600,n,8,1) uart1: 16550 or compatible port 0x2f8-0x2ff irq 3 on acpi0 uart2: 16550 or compatible port 0x3e8-0x3ef irq 10 on acpi0 inf02-kul# grep ttyu /etc/ttys ttyu0 /usr/libexec/getty std.9600 vt100 on secure ttyu1 /usr/libexec/getty std.9600 vt100 on secure ttyu2 /usr/libexec/getty std.9600 vt100 on secure ttyu3 /usr/libexec/getty std.9600 dialup off secure inf02-kul# ipmitool sol info Set in progress : set-complete Enabled : true Force Encryption: false Force Authentication: false Privilege Level : USER Character Accumulate Level (ms) : 5 Character Send Threshold: 1 Retry Count : 0 Retry Interval (ms) : 0 Volatile Bit Rate (kbps): 9.6 Non-Volatile Bit Rate (kbps): 9.6 Payload Channel : 1 (0x01) Payload Port: 623 inf02-kul# cat /var/run/dmesg.boot Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz (3292.59-MHz K8-class CPU) Origin = GenuineIntel Id = 0x306a9 Family = 6 Model = 3a Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x77bae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,AVX,F16C,b30 AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8219156480 (7838 MB) Event timer LAPIC quality 600 ACPI APIC Table: SUPERM SMCI--MB FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: SUPERM SMCI--MB on motherboard acpi0: Power Button (fixed) acpi0: reservation of 67, 1 (4) failed Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 cpu4: ACPI CPU on acpi0 cpu5: ACPI CPU on acpi0 cpu6: ACPI CPU on acpi0 cpu7: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 1.1 on pci0 pci2: ACPI PCI bus on pcib2 igb0: Intel(R) PRO/1000 Network Connection version - 2.2.5 port 0xe020-0xe03f mem
Re: ipmi is broken? (ppc0: cannot reserve I/O port range)
Actually IPMI was working until yesterday (on Linux rhel 5) and stopped working when I installed FreeBSD 8.2 amd64 (same result with FreeBSD 8.2 i386) On Linux : # dmidecode Handle 0x0029, DMI type 38, 16 bytes IPMI Device Information Interface Type: KCS (Keyboard Control Style) Specification Version: 1.5 I2C Slave Address: 0x10 NV Storage Device: Not Present Base Address: 0x0CA2 (I/O) # ipmitool mc info Device ID : 0 Device Revision : 1 Firmware Revision : 1.48 IPMI Version : 1.5 Manufacturer ID : 2 Manufacturer Name : Unknown (0x02) Product ID: 34869 (0x8835) Product Name : Unknown (0x8835) Device Available : yes Provides Device SDRs : no Additional Device Support : Sensor Device SDR Repository Device SEL Device FRU Inventory Device IPMB Event Receiver Bridge Chassis Device Aux Firmware Rev Info : 0x88 0x00 0x00 0x00 #lspci 02:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) 02:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) As my google searches pointed to me, the problem on FreeBSD seems to be related to the bge driver. I tried to configure hw.bge.allow_asf=0|1 and hw.pci.enable_msi=0 in loader.conf, which didn't fix the problem. Should I try to compile an older bge driver or fix the new one ? -- View this message in context: http://freebsd.1045724.n5.nabble.com/ipmi-is-broken-ppc0-cannot-reserve-I-O-port-range-tp4266087p4670031.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipmi is broken? (ppc0: cannot reserve I/O port range)
Do you really know that your server have IPMI? As I can see via google, IBM eserver 325 doesn't have IPMI devices out of the box. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ipmi-is-broken-ppc0-cannot-reserve-I-O-port-range-tp4266087p4667459.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipmi is broken? (ppc0: cannot reserve I/O port range)
Got the same problem on an IBM eserver 325. FreeBSD 8.2 amd64 Generic seems to crash the BMC ... -- View this message in context: http://freebsd.1045724.n5.nabble.com/ipmi-is-broken-ppc0-cannot-reserve-I-O-port-range-tp4266087p4667421.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipmi is broken? (ppc0: cannot reserve I/O port range)
May be you haven`t IPMI device on your motherboard. Which MB model do you use? -- View this message in context: http://freebsd.1045724.n5.nabble.com/ipmi-is-broken-ppc0-cannot-reserve-I-O-port-range-tp4266087p4267472.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: IPMI kernel object i/o error
On Monday 03 September 2007 17:10:05 Grant Peel wrote: Hi all, I am trying to get ipmitool working on a Dell 1850. When I kldload the ipmi.ko, it seems to load fine but the dev device is not being created. I can see this in the dmesg any time I try. If anyone can interprate this I wouold be greatful The ACPI driver cannot be loaded after boot. ipmi0: IPMI System Interface on isa0 ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa ipmi0: couldn't configure I/O resource device_attach: ipmi0 attach returned 6 ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled I'd start by: cat EOF /boot/loader.conf acpi_load=YES ipmi_load=YES EOF and reboot. -- Mel People using reply to all on lists, must think I need 2 copies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI A Question to all Dell Users.
Grant Peel wrote: Hi all, I have been reading a bit about IPMI. I am running 6.2 on all my servers. Does any Dell (PowerEdge) users have the IPMI port installed? Is it safe? Easy to use? Any problems with installation? I am mostly interested in viewing sensor info and extracting SELs. TIA, Have been using IPMI on PE2850 without problems. Although i have not performed any extensive testing on the functionality, it appears correct and i have had no trouble with it. I have used /usr/ports/sysutils/ipmitool on 6.1. /usr/ports/sysutils/ipmi-kmod is either available as ports module or in base system on some versions of FreeBSD. -- Sten Daniel Soersdal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipmi
Yes, I tried that. Still same error message. I am thinking its saysing there is no device node. I am adding it the loader.conf and rebooting ... see what happes. Oddly enough, there is a ipmi1 in the dev dir. crw-rw 1 root operator0, 91 Aug 25 07:15 ipmi1 -Grant - Original Message - From: Riemer Palstra To: Grant Peel Cc: freebsd-questions@freebsd.org Sent: Sunday, August 26, 2007 9:08 AM Subject: Re: ipmi On Sun, Aug 26, 2007 at 08:44:51AM -0400, Grant Peel wrote: Can anyone take my blinders off and show me what I am missing? excelsior# ipmitool sensor Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory Is the ipmi module loaded or compiled into the kernel? Usually a 'kldload ipmi' should be enough. -- Riemer Palstra [EMAIL PROTECTED] -- Total Control Panel Login To: [EMAIL PROTECTED] Message Score: 50 High (60): Pass From: [EMAIL PROTECTED] My Spam Blocking Level: High Medium (75): Pass Low (90): Pass Block messages from this sender (blacklist) This message was delivered because the content filter score did not exceed your filter level. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipmi
On Sun, Aug 26, 2007 at 08:44:51AM -0400, Grant Peel wrote: Can anyone take my blinders off and show me what I am missing? excelsior# ipmitool sensor Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory Is the ipmi module loaded or compiled into the kernel? Usually a 'kldload ipmi' should be enough. -- Riemer Palstra [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipmi
Added a sym link from /dev/ipmi1 to ipmi0 and all is well. -Grant - Original Message - From: Grant Peel To: Riemer Palstra Cc: freebsd-questions@freebsd.org Sent: Sunday, August 26, 2007 9:16 AM Subject: Re: ipmi Yes, I tried that. Still same error message. I am thinking its saysing there is no device node. I am adding it the loader.conf and rebooting ... see what happes. Oddly enough, there is a ipmi1 in the dev dir. crw-rw 1 root operator 0, 91 Aug 25 07:15 ipmi1 -Grant - Original Message - From: Riemer Palstra To: Grant Peel Cc: freebsd-questions@freebsd.org Sent: Sunday, August 26, 2007 9:08 AM Subject: Re: ipmi On Sun, Aug 26, 2007 at 08:44:51AM -0400, Grant Peel wrote: Can anyone take my blinders off and show me what I am missing? excelsior# ipmitool sensor Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory Is the ipmi module loaded or compiled into the kernel? Usually a 'kldload ipmi' should be enough. -- Riemer Palstra [EMAIL PROTECTED] -- Total Control Panel Login To: [EMAIL PROTECTED] Message Score: 50 High (60): Pass From: [EMAIL PROTECTED] My Spam Blocking Level: High Medium (75): Pass Low (90): Pass Block messages from this sender (blacklist) This message was delivered because the content filter score did not exceed your filter level. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Total Control Panel Login To: [EMAIL PROTECTED] Block messages from this sender (blacklist) From: [EMAIL PROTECTED] Remove this sender from my whitelist You received this message because the sender is on your whitelist. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipmi drivers
Dhananjaya hiremath wrote: Hello sir, Hello, Here we did the following command to build the ipmi. # cd /usr/src/sys/modules/i2c/smbus make make install # cd /usr/src/sys/modules/ipmi make make install # kldload smbus # kldload ipmi Then how we come to know that the driver is installed.And how to ensure that driver runs successfully. And pls specfiy the steps for building on the freebsd. Take a look at your console (ttyv0) and/or at the tail of /var/log/messages. You should see whether your hardware has been attached by the ipmi driver. Unfortunately I don't own such a hardware, so I cannot provide an example. -- Pietro Cerutti PGP Public Key ID: http://gahr.ch/pgp signature.asc Description: OpenPGP digital signature
Re: IPMI on SuperMicro PDSMi+ Motherboard
Philipp Wuensche wrote: Hi, I lately aquired an SuperMicro PDSMi+ motherboard and the IPMI AOC-IPMI20-E daughterboard. I can report that the ipmi driver in 6.2 is working just fine and I can use ipmitool to access the module from the hostsystem. The only problem is that the IPMI module loses its network connection and is not reachable via IP some times, this espacially happens after a SOL session. If the server is up I can issue a cold reset for the module and I can reach it again, I'm not sure if this has anything todo with freebsd and problems with the em driver or if it is just the firmware of the module but if anyone has experience with this stuff maybe he can give me a hint what could causing this problems at all. Currently it is configured with a different MAC and a different IP than the host system, haven't tried same MAC and IP yet. Shouldn't make a difference, should it? It makes a difference! If I use the same MAC as the hostsystem, access to the IPMI module is unavailable when booting single-user or until the first ifconfig em0 up, this could be either be a problem with the em driver or maybe the eeprom issue Jack Vogel described on freebsd-stable, but I haven't had the chance yet to test the update tool he mentions. Using the same IP as the hostsystem makes no difference of course. I now have it mostly running okay but again running with a different MAC and IP as the system. I now did _not_ use the MAC address from the sticker on the IPMI socket and instead just took one random. This is of course not good and one should use the MAC address from the IPMI socket, maybe I will give it another try. Just to document my findings so other don't have to get to the same pain again, some of my experience: 1. There are basically three modes of MAC/IP configuration for IPMI 1.1 same MAC and same IP as hostsystem 1.2 same MAC as hostsystem but different IP 1.3 different MAC and different IP as hostsystem 2. Get console access working 2.1 The IPMI module connects to the onboard com2 port via a straigt cable with 10pin connectors on both sides. You have to enable bios-redirection in the BIOS and use port B. 2.2 To make the second serial port the console port (default is the first), you have to set hint.sio.1.flags=0x10 in /boot/device.hints, maybe setting BOOT_COMCONSOLE_PORT=0x2f8 in /etc/make.conf and rebuilding/installing the boot-loader will do the same. 2.3 To change the speed of the serial port you have to set BOOT_COMCONSOLE_SPEED=115200 in /etc/make.conf and rebuild/install your boot-loader. One advise if you want to use a different baudrate for the serial console than 19200.. stay away from the IPMIView tool, it resets the baudrate of the IPMI module back to the default 19200 every time you try to establish a SOL session. Use the ipmitool from the ports. (has some issues too but works for access from the hostsystem and most of the remote stuff.) 3. Local IPMI access via OpenIPMI (needs FreeBSD 6.2) 3.1 To get access to the IPMI module via the hostsystem you need device ipmi in your kernel configuration. 3.2 Accessing the IPMI module is done by using ipmitool -I open, you have to compile ipmitool from ports on at least FreeBSD 6.2 (needs some headerfiles to enable OpenIPMI support) Maybe a section in the Handbook would be helpful, should write that up once I get it working reliable. greetings, philipp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI doesn't work...
How are you attempting to manage the server.. via a command line or terminal emulation software directly to the BMC? What amangement software ships with the IBM? Once the kernel loads, you need to perform SOL (serial redirection over LAN), or use management software the speaks directly with the BMC.. Just curious a little bit more about your setup T - Original Message - From: Jeff Behl [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Monday, March 14, 2005 11:25 AM Subject: IPMI doesn't work... on a 5.3 amd64 system. anyone have any luck or know anything about this? i can query variables right up until the point where the kernel loads, then nothing. ibm is saying this can be caused by the actual net driver (the Baseboard Management Controller (BMC) shares the network interface); we're using a Broadcom BCM5704C Dual gig adapter: bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003 mem 0xfe00-0xfe00,0xfe01-0xfe01 irq 24 at device 1.0 on pci2 anyone have any idea why this may be the case? unfortunately for me and others, the inability to remotely manage boxes (console/power cycle/detect drive failures/etc) via will be a deal breaker in our push for FBSD in our fleet (couple hundred) of dual proc amd64 IBM e325 servers. SuSe here we come (unwillingly)... thx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPMI doesn't work...
Thomas Foster wrote: How are you attempting to manage the server.. via a command line or terminal emulation software directly to the BMC? What amangement software ships with the IBM? Once the kernel loads, you need to perform SOL (serial redirection over LAN), or use management software the speaks directly with the BMC.. Just curious a little bit more about your setup T We've only used command line tools which speak directly to the BMC. The strange thing with these boxes is the network card is also used by the BMC. You configure (via the bios) a BMC IP address which is different from what the NIC is assigned via the OS. Like I said earlier, we're able to query/control the chassis just fine when the box is powered off or when it's booting, but as soon as the kernel loads, we lose control and simply no longer get any response from the BMC. This is not he case with the linux distros we've tried, so I'm guessing it's somehow to do with the NIC driver that BSD is loading... jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
