Database Reference
In-Depth Information
ODA Network Deployment Process
ODA networks can be deployed using the process outlined in the subsections to follow. Most of these steps are
necessary, but are fairly simple in nature. The steps are listed roughly in the order in which they should occur.
Of course, each company has their own standards and methods for getting a server deployed in their data center and
on their network. The key steps are as follows:
1.
Plan which ODA networks will be deployed.
2.
Define network security considerations.
3.
Complete work that can be accomplished before the ODA arrives.
4.
Spec and order the ODA network cabling.
5.
Request IP addresses.
6.
Build the offline configuration file.
7.
Rack the ODA.
8.
Cable the ODA, including internal cabling.
9.
Apply the ILOM IP addresses and configure the ODA public network.
10.
Run the ODA deployment process to configure the remaining networks.
Plan the ODA Networks to Be Deployed
The X3-2 ODA model supports two bonded networks. One of them will certainly be used for the public network.
The second network is generally used as the backup network. It is possible to unbond one or both networks to
take advantage of all four external network connections at the cost of network redundancy. An example would be
deploying a bonded public network and a single connection for a backup network and an additional network to
support an NFS storage mount. While it is also possible to mount NFS storage over the public network, performance
issues can arise when large volumes of data are streamed between the server and NFS storage. The need for external
storage mounts has somewhat diminished due to the very large amount of internal storage supplied with an ODA.
■
the key point in this section is that the first network deployment step is to plan out what networks are required
for your solution, and matching those requirements to the oDa network options. Understanding the workloads that need
to be supported can also be an important consideration in planning oDa networks.
Note
ODAs can now store a great deal of data. If the databases deployed have tight RTO (recovery time objective)
requirements, and they are large in size, using a 10G backup network can help drive better backup and recovery
performance. This would be in addition to deploying the standard RMAN tuning steps. If you are connected to
a backup network through an NFS mount, DNFS (Direct NFS) can be implemented to speed up the backup and
recovery throughput. There is an old adage followed by many long-term Oracle DBAs and architects: “It is better to
focus on architecting for recovery than to architect for backups.” If you want to make sure that you have all of your
recovery bases covered, your network planning plays a key role.
If your company only uses 10G fiber or other fiber network infrastructure, then additional planning, and
potentially costs, may be needed to bridge the ODA copper cabling to your fiber network. As mentioned previously,
this is subject to change when new models are released.
