Oracle A-Team has launched a new Oracle A-Team Chronicles web site for all A-Team generated content that cover architecture, product features, technical tips, performance tuning, troubleshooting and best practices on Oracle Middleware products.
Business application deployment and maintenance is one of the most complex projects faced by the enterprise. In many cases, these are high visibility and high risk efforts, with substantial budgets, and, if done right, will result in transformational change. Conversely, if things do not work out as planned, the results will almost certainly be disastrous.
As a system administrator, you’re asked to pull together a huge array of technologies, tools, and products into a working system while addressing performance problems, security threats and tight timelines. The last thing you need is yet another product that adds to your list of challenges.
For a customer Proof of Concept - demonstrating the benefits of Oracle Fusion Middleware on Exalogic Virtual - we decided to build a custom base template. All vServers created by using this custom base template enable some customer specific configuration settings, activation of additional services and yields flexibility for the file-system layout.
There are lots of reason for customer to create VNIC over eoib0 & eoib1 on a compute node running Solaris, two typical examples are
1) compute node needs to connect to a VLAN over the EoIB network
2) there are containers running on the compute node that require 10GbE connectivity
We talked about why Transitive Probe-based Failure Detection is required in previous blog entry, the focus was on the link between IB gateway and customer's 10GbE infrastructure.
On Exalogic, no matter which supported Operating Systems that a compute node is running, it relies on the IB gateways (NM2-GW) to provide both internal (IPoIB) and external (EoIB) network connectivity. Each compute node is physically connected to two IB gateways by copper cables, the IB gateway in turn is connected to customer's 10GbE infrastructure, typically a level 2 switch.
In a customer engagement, I found that that their bond0 and bond1 configurations look like this:
root@el01cn01:~# ipmpstat -iINTERFACE ACTIVE GROUP FLAGS LINK PROBE STATEeoib0 no bond1 is----- up disabled okeoib1 yes bond1 --mb--- up disabled okbond0_0 yes bond0 --mb--- up disabled okbond0_1 no bond0 is----- up disabled ok
notice that the active interface for bond1 is eoib1 while the active interface for bond0 is bond0_0