The motherboard was replaced by an HP Technician due to a network connection not working. After he left and I turned on the system I get 'Invalid Chassis.

Chris, I have had a few of these situations with some BL460c-GEN8 blades. Each time the system board was replaced due to iLO issues, the technician did in fact update the serial number and product ID in the RBSU. When the server reboots, the product ID field is not being updated to the OA. HP Proactive Support informed me that there was an HP Advisory issued, and the fix is a firmware update that is in the 2015.060 version of the SPP. The alternate solution, as this is what corrected all three of my issues, was to power cycle the server a second time. (removed it from the enclosure and reseated it) That corrected the missing Part number field in the OA, and therefore OneView was happy once again.

(I did try the Server Reset 'bay#' command from the OA CLI, and that resulted in a worse condition with one of the blade servers, as I lost several iLO settings, including the Advanced license key) after issuing that command.

Hi guys, I recently decided that my lacking knowledge of networks and what makes them tick is no longer admissible and therefore chose the practical/exciting approach to get started: kismet. After reading /usr/share/doc/kismet/README.gz I tried to set up /etc/kismet/kismet.conf properly but eventually failed because I don't know which interface to use (nor do I *really* know what an interface actually is). I tried to determine the correct interface with iwconfig, but it says that there're no wireless extensions available for any of the interfaces. I can't test wlan right know since there's no public access available but NetworkManager shows two ap's in the my vicinity and therefore I assume that wlan generally works.

I took a wild guess and specified the interface as eth0, but kismet failed setting up monitor mode. My broadcom bcm4312 internal wnic is supported by kismet (according to README.gz). Out of curiosity I installed the proprietary driver but quickly changed back to what I assume to be bcm43xx. I really don't know how to pick the right interface, if missing info from iwconfig is indacating a problem or not and if so what to do to solve it, so please forgive me for simply dumping some data and begging for help *beg*. System: HP 6735s notebook, Ubuntu 8.10 recently installed w/o aimlessly changed system settings (yet). Code: dominik@auntlizzy:~/.nautilus/metafiles$ sudo iwconfig [.] eth1 IEEE 802.11bg ESSID:' Nickname:' Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Tx-Power:32 dBm Retry min limit:7 RTS thr:off Fragment thr:off Power Managementmode:All packets received Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0Kismet however was still not willing to work and so I changed the driver once more.

The new interface is still there (propably because I did not restart the networking system?) and kismet is still pis. Here is what it says. Code: dominik@auntlizzy:~/.nautilus/metafiles$ sudo kismet Launching kismet_server: //usr/bin/kismet_server Suid priv-dropping disabled. This may not be secure. No specific sources given to be enabled, all will be enabled. Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng) Enabling channel hopping.

Enabling channel splitting. NOTICE: Disabling channel hopping, no enabled sources are able to change channel. Source 0 (BCM4312): Enabling monitor mode for bcm43xx source interface eth1 channel 6.

FATAL: Failed to set monitor mode: Invalid argument. This usually means your drivers either do not support monitor mode, or use a different mechanism for getting to it. Make sure you have a version of your drivers that support monitor mode, and consult the troubleshooting section of the README. Done.Does that simply mean that my wnic does not support monitor mode or is there a less final explanation?

Last edited by lostbuthappy; April 1st, 2009 at 06:05 AM. I am having a similar problem. I use a rtl8187b network adapter in my laptop and can't get Kismet to work. I think the problem is that most drivers that the companies who make these adapters write don't have monitor mode enabled for legal reasons. You would therefor need to get a cracked driver instead. That's my theory anyway.