Databases Reference
In-Depth Information
Chapter 10
Network Administration
Exadata's compute nodes consist of a management network, a client access network, an InfiniBand network used for
both the storage and Oracle RAC cluster interconnect, and an optional additional network. Exadata's storage cells are
deployed with a similar management network as well as the InfiniBand storage network.
In this chapter, you will learn how to confidently manage and administer the various network components in the
Exadata Database Machine.
10-1. Configuring the Management Network on the
Compute Nodes
Problem
You wish to validate and modify the administrative network on the Exadata Compute Nodes.
Solution
In this recipe, you will learn how to validate your current administrative network configuration on the Exadata
Compute Nodes and modify the administration network configuration.
The administration or management network is called the
NET0
network and is used to provide shell access via
SSH to the Exadata DMA. The
NET0
network is enabled on interface
eth0
. To display the configuration, log in to a
compute node and run the following
ifconfig
command:
[root@cm01dbm01 ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:21:28:B2:17:02
inet addr:172.16.1.10 Bcast:172.16.1.255 Mask:255.255.255.0
... Output omitted for brevity
[root@cm01dbm01 ~]#
This
NET0
/admin network is comprised of a single network interface and is not typically deployed with channel
bonding, although in some rare cases clients choose to bond the
eth0
interface with the
NET3
/
eth3
interface to
provide additional network interface redundancy.
When configuring DNS for your Exadata Database Machine, the host name of each compute node is registered
with the IP address of the
NET0
/admin interface. Validate this by using
nslookup
from any host on your network and
compare the IP address returned from the DNS query with that of the previous
ifconfig
output:
Macintosh-8:~ jclarke$ nslookup cm01dbm01
Server: 11.11.1.250
Address: 11.11.1.250#53
Search WWH ::
Custom Search