With this entry two items around Exadata management:
First: a pointer to My Oracle Support note 1110675.1. This is note is called "Oracle Database Machine Monitoring Best Practices" and has a lot of information on Exadata management. In this note you will read about the plugins we have to monitor the various Exadata components and how to configure them, also you will read about creating a 'Dashboard'.
The topic I like to cover here is about the steps to take to setup automated fail-over of targets. This is, because by default a target monitored using a plug-in in Enterprise Manager Grid Control is bound to the agent used during the initial installation.
So, what you basically want to do is make sure another agent (on another node) is available to take over the monitored targets when the first agents fails; providing HA for your monitoring.
For this I like to mention two items:
Once you have executed the steps above, the second agent should be able to take over the targets initially assigned to the first agent when the first fails.
You can test this by stopping the first agent; in Grid Control you will find the targets under the second agent. Making sure the monitored targets can failover to a surviving agent is recommended, but it going that route, it would make sense to also make sure Grid Control (OMS) and database are both also HA.
Second topic for this entry is the "EM 11GC Setup automatic kit" for Exadata.
With the latest Oracle Exadata Database Machine Configurator a new output file (em.param) is generated. This file can be used as input for installing Oracle Enterprise Manager Grid Control Agents on Oracle Exadata Database Machine
With this kit, Exadata customers, having an existing Oracle Enterprise Manager Grid Control environment can have setup agents rapidly by the Oracle or partner teams doing the Exadata deployment. For the sake of completeness: Oracle Enterprise Manager Grid Control is not a requirement for Exadata but a recommendation.