Browsed by
Tag: oeda

Building bridges: “Bridge must not have discovery mode for LACP interface; Interface file: bondeth0;”

Building bridges: “Bridge must not have discovery mode for LACP interface; Interface file: bondeth0;”

Some days start as an exatastic day and end up grasping your hair. This post is about such a day. A brand new shiny X7 Quarter Rack exadata was being installed for a customer. This setup was a fairly straightforward one. Quarter rack, full ovm and 2 virtual clusters. Not too fancy. LACP is being used for the public network on the fibers and vlan tagging is done on the switch. Given that, my customer created a OEDA configuration using…

Read More Read More

A heads up for my bad memory

A heads up for my bad memory

Gotcha! This post is not about memory settings at all, but a quick heads up. If you are dealing with several generations of exadata’s and you like ironhugging them as much as I do, sometimes things can get confusing. The X7 exadata has changed a bit so when you use them, it’s nice to do things right. Only way to do it right is check it, double check it and verify. One of the things which is always in my…

Read More Read More

OEDA has properties too

OEDA has properties too

Some customers ask for help to fill in the Exadata Deployment assistant (OEDA for short). This is the case in my current project. They bought a shiny brand new X7 and requested assistance for the OEDA as they faced an issue with the admin network. It reproduces very easily so I will show this using a demo example. A small introduction is maybe needed for this. Most of us know the 10.x.x.x/8 or the 172.16.x.x and 192.168.1.x/24 ranges that are…

Read More Read More

OEDA does more than you would expect: januari 2018 update

OEDA does more than you would expect: januari 2018 update

Today I was at one of my Exadata customers for a (PL/)SQL performance tuning assignment. In the meantime there is a parallel project running for a new Exadata. So as you might know, the configuration for an Exadata starts with running the OEDA-tool. The latest version can always be found on My Oracle Support note 888828.1. At the moment of writing this blog, the latest one was January 2018 with patch number 27370068. One of the things which caught our attention,…

Read More Read More

OEDA does more than you would expect

OEDA does more than you would expect

The title summaries this complete blogpost, the OEDA (oracle exadata deployment assistant) does a lot more than you would expect. Therefor it is pretty important that you should use a recent version every time when fiddling around with virtual machines on the exadata. A simple example I just discovered and did not know about. In my previous blogpost about the bond_eth issue (find it here: http://vanpupi.stepi.net/index.php/2017/06/09/exadata-ovm-creation-second-argument-is-not-defined-bondeth_mode/ ) you could read that there was a problem while I invoked domU maker manually…

Read More Read More

%d bloggers like this: