Database Reference
In-Depth Information
Here are some of the additional things that you can learn from reviewing these notes:
•
The network configuration files are stored in
/etc/sysconfig/networking
and
/etc/sysconfig/network-scripts
.
The DNS server entries are stored in the
•
/etc/resolve.conf
file.
•
The
ifconfig
command can be used to display your ODA network settings.
Your ODA deployment settings are stored in
•
/opt/oracle/oak/onecmd/onecommand.params
.
After updating your ODA, you may need to generate new files or changes to files using the
Oracle Appliance Manager configuration utility. The appliance manager version has to match
the ODA version of the machine. This file is only readable by the root account.
•
You can use the
GridInst.pl
script, which is run by the deployment process, to modify the
existing ODA configurations, including changing the networks.
•
Running the
GridInst.pl
script with the
-l
option—as in
GridInst.pl -l
—displays a
current list of the individual deployment steps run by the script. The
-l
option is used to make
sure you rerun the correct step when making changes to an ODA configuration.
ipmitool
command can change the ILOM IPs by providing a wrapper to generate
/SP/
Network
commands.
Finally, if you have any questions regarding what version of the ODA software you are running on, you can run
the following command as root:
/opt/oracle/oak/bin/oakcli show version
.
•
The
Virtualization Considerations
If you are virtualizing your ODA, you need an additional IP address for each virtual machine that will be created on
the ODA. Support for multiple VLANs on an ODA was released in version 2.8, which was a week old at the time this
chapter was written. Currently, all of the documentation for ODA virtualization support is published in the Getting
Started Guide. Currently, this documentation details the following:
•
How to create a VLAN
•
How to delete a VLAN
•
How to list the VLANs deployed on an ODA
Since multiple VLAN support on a virtualized ODA was just released, it will take some time for the
documentation to cover all of the details needed to fully understand multiple VLAN support. Until the ODA
virtualization documentation catches up, there are a couple of ways to try to fill the gap. First, you have to start with
understanding why you might want to use multiple VLANs on a virtualized ODA. Second, you have to understand
the background of virtualization on an ODA. VLANs, or virtualized local area networks, segment a physical network
into multiple logical networks. This can be done to create multiple networks to share a single physical network, which
will increase the number of available networks on an ODA. VLANs can also be created to provide multiple networks
on an ODA to support network segmentation for security reasons, or to create VMs on specific networks to match
the networks deployed for other components of the application. VLANs can be configured to control which network
segment traffic can be routed between addresses to enhance network security.
Examples of virtualized networks that may be deployed on an ODA include a database network, multiple
application networks, the management (ILOM) network, and backup or other special purpose networks. ODAs have a
lot of capacity, and customers might only license part of the database cores on the appliance for database processing.
This leaves capacity for other purposes, including running applications on ODAs.
