Expert Oracle Exadata - Parent Directory

CHAPTER 8 CONFIGURING EXADATANetwork SettingPDU-B IP addressDescriptionExadata is equipped with a redundant PDU that can also beconfigured on the network by assigning it an IP address. Thisfield defines the network for the PDU.The domain name, DNS server, and NTP server settings are all standard network settings.These should be specified as you would for any other Oracle database server on yournetwork. The remaining network settings are described as follows:Management Network (NET0): The management network is used foradministrative access to the database servers and storage cells. You can think ofthis network as your SSH entry point for logging into the compute nodes,storage cells, and IB switches. The management network is serviced by theinternal Cisco network switch. Only one network drop is required to uplink theCisco management switch to your company network. The managementnetwork also includes the ILOM interfaces on the compute nodes and storagecells.Client Access Network (NET1): The client access network provides SQL*Netaccess to the database. This is the network used by the SCAN Listeners toestablish client connections to the database. Only the database servers use thisnetwork; storage cells are not assigned an IP address on this network. And eventhough the database servers have an IP on this network, you cannot connect tothese IP addresses using SSH, because SSH is not configured to listen on thisnetwork. One network drop (minimum) is required for each database server toprovide access through your company network. If channel bonding is used toprovide hardware redundancy, you will need two drops per database server.The cable pairs from the database servers should be connected to redundantnetwork switches to provide full network redundancy. If channel bonding isconfigured for the client access network, OneCommand configures thesedevices in the ifcfg-eth1 and ifcfg-eth2 configuration files in the/etc/sysconfig/network-scripts directory. They are bonded to the bondeth0device defined in the ifcfg-bondeth0 file. For example, the following listingshows how the master bond device is referenced by the eth1 and eth2 slavedevices.# egrep 'DEVICE|MASTER|SLAVE' ifcfg-bondeth0 ifcfg-eth1 ifcfg-eth2ifcfg-bondeth0:DEVICE=bondeth0ifcfg-eth1:DEVICE=eth1ifcfg-eth1:MASTER=bondeth0ifcfg-eth1:SLAVE=yesifcfg-eth2:DEVICE=eth2ifcfg-eth2:MASTER=bondeth0ifcfg-eth2:SLAVE=yesChannel Bonding (NET1): Oracle recommends that you configure NIC bondingfor the client access network to provide network redundancy. If you choose tobond the client access network, OneCommand will use NET2 as the secondarynetwork device.251