Database Reference
In-Depth Information
ifup: Enslaving eth24 to bond2
kernel: eth24: link up.
kernel: eth24: Setting full-duplex based on negotiated link capability.
kernel: bonding: bond2: enslaving eth as an active interface with an up link.
network: Bringing up interface bond2: succeeded
kernel: ip_tables: (C) 2000-2002 Netfilter core team
kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
kernel: bonding: bond0: link status definitely up for interface eth1.
network: Bringing up interface eth0: succeeded
sshd(pam_unix)[5066]: session opened for user root by (uid=0)
[root@prddb3 root]#
2.
Verify the new active networks using the ifconfig command.
[root@prddb3 root]# ifconfig -a
bond2 Link encap:Ethernet HWaddr 00:D0:B7:6A:39:85
inet addr: 192.30.0.96 Bcast:192.30.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:3162 errors:0 dropped:0 overruns:0 frame:0
TX packets:1312 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:275327 (268.8 Kb) TX bytes:142369 (139.0 Kb)
eth24 Link encap:Ethernet HWaddr 00:D0:B7:6A:39:85
inet addr:192.30.0.96 Bcast:192.30.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:804 errors:0 dropped:0 overruns:0 frame:0
TX packets:1156 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:83807 (81.8 Kb) TX bytes:120774 (117.9 Kb)
Interrupt:11 Base address:0x2800 Memory:41500000-41500038
eth25 Link encap:Ethernet HWaddr 00:D0:B7:6A:39:85
inet addr:192.30.0.96 Bcast:192.30.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:2358 errors:0 dropped:0 overruns:0 frame:0
TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:191520 (187.0 Kb) TX bytes:21933 (21.4 Kb)
Interrupt:11 Base address:0x9000
eth2 Link encap:Ethernet HWaddr 00:09:5B:E0:45:94
.... .......... .........
the ifconfig output in the preceding displays all interfaces available on the node; however, once bonding has
been configured, only the new logical ip address assigned to bond2 will be accessible.
Note
High Available IP (HAIP)
Starting with Oracle Database 11g Release 2 (11.2.0.2), there is a new paradigm shift to this entire configuration option
implementation with the new HAIP feature. Using the HAIP feature, multiple NICs can be configured as private
networks without any bonding or without the use of the CLUSTER_INTERCONNECTS parameter. Apart from providing
continuous availability should an NIC in the configuration fail, Oracle load balances traffic across all the available NICs.
 
Search WWH ::




Custom Search