Browsed by
Category: OVM exadata

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

Compute node disk expansion resulted in mount.ocfs2: Bad magic number in superblock while opening device /dev/sda3

Compute node disk expansion resulted in mount.ocfs2: Bad magic number in superblock while opening device /dev/sda3

Before Christmas 2017 I had the honour to expand the compute node storage for a virtualised exadata. Better said, OVM on exadata. This can be done for several reasons. The most logic one, also the reason why this customer bought the disk expansion, is that you want to create more virtual machines and you have ran out of space on /EXAVMIMAGES. The preparation is actually pretty simple. It is documented completely in the Exadata Database Machine Maintenance Guide. And look,…

Read More Read More

%d bloggers like this: