IPMI interface: dedicate, share, failover

Chris Wahl said it short and best:

Dedicate – the IPMI port is used exclusively for out of band access
Share – the on-board NIC’s first port is used exclusively for out of band access
Failover – try to use the IPMI port, and if it is not connected, fail over to the on-board NIC port

From Supermicro:

* The default setting is Failover, which will allow IPMI to be connected from either
the shared LAN port (LAN1/0) or the dedicated IPMI LAN port. Precedence is
given to the Dedicated LAN port over the shared LAN port.
* Select Dedicate for IPMI to connect through the IPMI Dedicated LAN port
at all time.
* Select Share for IPMI to connect through the LAN port on the board

Longer with more detail.

Check the current mode:

ipmitool raw 0x30 0x70 0x0c 0

The output will be one of these:

0x00 = Dedicated
0x01 = Onboard / Shared
0x02 = Failover

To set the mode to

  1. Dedicated
    ipmitool raw 0x30 0x70 0xc 1 1 0
    
  2. Shared
    ipmitool raw 0x30 0x70 0xc 1 1 1
    
  3. Failover
    ipmitool raw 0x30 0x70 0xc 1 0 0 
    

Via http://www.supermicro.com/support/faqs/faq.cfm?faq=9848

Advertisements

Cannot manually run rules in Outlook for mac to existing mails

After years of using Lotus Notes at work, I am back to Outlook. This time Outlook for Mac with Office 365 Exchange server. I cannot apply rules to already existing emails on my inbox. For a while I thought I had the rules wrong or just don’t know how to use Outlook. If found the reason today:

Manually applying rules works only for On My Computer rules. You cannot use Outlook for Mac to manually apply server-based rules

My rules are server based. Therefore, I cannot apply them manually.

What is NVMe?

Flash and SSD storage devices are faster than spinning disks because they have no moving parts. They can be even faster. They are still accessed using SCSI protocol that sends one command at a time. With NVMe (Non-Volatile Memory Express), a protocol that will be used to access SSDs via PCIe interface.

This is an excellent introduction to NVMe: NVMe for Absolute Beginners.

Emulex 10G OneConnect NIC doesn’t work after ESXi upgrade

After upgrading to ESXi 5.5 or 6, Emulex 10G nic does not work. If you run esxcfg-nics -l, the NICs still have link. If you check the module, it is loaded but it won’t work. It won’t pass traffic.

For 5.5, we found a workaround in the community forum by way of disabling elxnet and enabling be2net driver followed by a reboot. Prior to upgrade, in 5.1, be2net was the driver but upon upgrading to 5.5 or 6, the driver changes to elxnet.
Continue reading