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 meant for your own use. The network admins know more and there exist also other predefined ranges. You can find those ranges here: https://en.wikipedia.org/wiki/Reserved_IP_addresses or the official one here: http://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml#iana-ipv4-special-registry-1

You feel where this is heading to aren’t you?

My customer wanted to use one of these ranges. In order not to reveal the customer I took another range to demo it, but the point is the same.

As you can see, the OEDA complains on using the ICAN ranges. I used the range which is originally intended for a 6to4 Relay Anycast (but it’s deprecated). I think this is a good thing that OEDA protects you from using these.

In some (rare) cases, it might be necessary to derive from these recommendations. The OEDA tool has, just like many others, a properties file. This one is located in the properties directory.

There we find the es.properties file

First create a copy of this file as a precaution. The mandatory disclaimer is needed. Do not mess with these files unless you are very aware of what are the consequences of this.

So the entry we are interested in is:

Look who is there. All the ICAN ranges which should not be used. The demo used 192.88.99.x/24 so when I remove this entry and change the IANA_IPV4 from


and rerun the OEDA using the same input:

There we go! OEDA accepts the input and the next button does not result anymore in an error.

The thing is. This properties file is a very powerful file which contains all the correct information which is needed to get a stable exadata. I would not recommend to tamper with it, but at least this shows how it works and why the error was thrown.

As always, questions, remarks? find me on twitter @vanpupi

Leave a Reply

Your email address will not be published. Required fields are marked *

fifteen − five =

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: