If you work with Exadata, you inevitably have already faced these interrogations:
- What is the IP of my database server ILOM ? (when you need to reboot a server from its ILOM for example or take an ILOM snapshot for Oracle support)
- What is the Cisco switch IP ? (when patching it for example)
- How many IB Switches do I have in my Rack ?
- What are the Cells IP ?
- . . .
Let's have a look at few screenshots
- A Full Rack
- A Quarter Rack
It looks cool, isnt't it ?
Note that the storage servers use 2 U, this is why 2 lines are colored in Red for each Storage Server.
A short view
As those who have non Full Racks may ended with an output full of empty U slots, I have implemented a -s option to show only the used U slots:
How it works ?
I didn't want to go in root commands to find the information so exa-racklayout.sh just parses the /opt/oracle.SupportTools/onecommand/databasemachine.xml file and creates this nice output. The advantage of /opt/oracle.SupportTools/onecommand/databasemachine.xml is that you can access it as non-root user, is usually up to date and if it is not as you have extended your Exadata, it is a good opportunity to update it.
Use a non default databasemachine.xml
The script can also generate the Rack Layout from a non default databasemachine.xml file like one coming from another Exadata:
[oracle@exadata ~] ./exa-racklayout.sh -f /tmp/mydatabasemachine.xmlI must confess that the goal of this feature is more to allow anyone with an admin server or even a laptop with SSH keys deployed to the Exadatas to have a quick look at this information on many Exadatas in a glimpse with this many-exa-racklayout.sh script ! And you'll quickly have this kind of output:
Download the script
Let me know if you like it !
Very cool. I'll try it soon.
ReplyDeleteAmazing .Time saving .Really nice script... Thanks Very much Fred.
ReplyDeleteAwesome !! thanks
ReplyDeleteHappy you like it !
DeleteIs there a reason it doesn't show the client network endpoints and only the admin network endpoints?
ReplyDeleteIt is based on databasemachine.xml so it shows the admin interfaces which is of interest for DBAs.
DeleteHi Fred, any chance you could also populate the rack serial numbers and individual component serial numbers?
ReplyDeleteHi Rich,
DeleteSounds like a good idea, I'll have a look and see what I can do.
exa-raclayout.sh script not available
ReplyDeletePlease share it again or send to my email "zodiacsom@gmail.com"
extremely good article ..thanks
Cannot you access https://raw.githubusercontent.com/freddenis/oracle-scripts/master/exa-racklayout.sh ?
DeleteHi. Thankks for your scripts. Very helpful. Please, this one, can not be found - https://raw.githubusercontent.com/freddenis/oracle-scripts/master/many-exa-racklayout.sh
ReplyDeleteKindly share with me. projbayo@gmail.com
Many Thanks
Hi, the many- script suppose to run the script on many target hosts has been replaced by a real generic alternative yal.sh;please have a look at https://unknowndba.blogspot.com/2019/09/yal-yet-another-launcher.html?m=1
DeleteHave a good day
databasemachine.xml file is not available at /opt/oracle.SupportTools/onecommand/ location , Is it possible to generate by manually
ReplyDeleteI dont think so; try locate databasemachine.xml to see if it is not somewhere else on your system
Delete