How to determine M1000e CMC IP address from CLI of an installed blade

Blade servers are small, high-density, low form-factor computers, designed for maximum power in a small space.

A blade server is mounted within a chassis, and the chassis typically takes on a lot of functions and parts that were previously done by the individual host. The chassis itself will hold the power supplies (resulting in less wasted power from conversion), the fibre-channel cards, the network controllers, SCSI interfaces, and so on. The servers themselves contain only the non-unique parts – CPU, RAM, and hard drive.

The benefits are that you can pack far more computing power into a rack, you have homogenous hardware, and your management is simpler. Instead of monitoring two power supplies, NICs, etc. per server, you only have to watch one set of hardware. Because your hardware is homogenous, you can keep spare parts around without worrying about which model of power supply you need, and so on.

The downsides are the up-front costs. Because you need to buy the (very expensive) chassis, it's cost-ineffective to start with one blade and work your way up. You would typically buy blade servers if you plan on buying a large number of servers at once. Otherwise, the initial up-front cost is excessive.

To your question, I am a fan of separate interfaces for the OCFS2 Interconnect, but from your setup it looks like the best solution would be NIC Bond for two interfaces and VLAN out the virtual ip's for the ext and int (public and private) hostnames. The separation for the interconnect traffic is just for latency, not bandwidth. If you are certain there will be no latency to affect your interconnect there should be no problem in your BOND + TRUNK solution above.