robinsc wrote:It is not typical. That statement is incorrect.
During the Exadata three day training from Oracle university ( and also in the student guide) we were told that merging of the Exadata client network and management network were quite typical . On the Exadata Database Administration Workshop page 8-11 it states ' The client access network can be separate from the management network ( as in the diagram ) or both functions can be provided by the same network.Single network configurations are quite typical.
However in the Exadata User's guide and in the configuration worksheets it states that these need to be separate.You don't need to dedicate a subnet for Exadata Database Machine. The downsides that immediately come to mind are these:
Which is correct and are there any downsides to combining the functions ? We do not want to waste a large subnet on something that is unlikely to see any expansion...
So would like to eliminate the client network requirement if possible.Finally - consider that all of the testing done in-house by development, QA and all the other groups use the network layout shown in the product documentation. That is, separate management and client access networks. To get the best value from the system you're deploying, you want to leverage all that testing that Oracle does. Varying the network configuration significantly would mean that a significant portion of the testing Oracle does would not apply directly to your environment, so you'd have to invest in testing and stressing all aspects yourself. It's always a good idea to test on your own, but you'd be starting "from scratch" instead of taking advantage of the testing already done for HA, NIC failover, etc.