翻译HAIP相关问答

Highly Available IP (HAIP) FAQ for Release 11.2 (文档 ID 1664291.1)


In this Document
Purpose
Questions and Answers
  1. What does HAIP stand for?
  2. What clusterware version was HAIP introduced in?
  3. What is the purpose of HAIP?  
  4. How does HAIP create a layer of transparency between the cluster interconnect NICs on a given node and the RDBMS/ASM instances?
  5. How does HAIP obtain an IP address for use in the virtual link?
  6. How can I check if the HAIP is in use?
  7. Which Oracle clusterware log shows the failover or failback of a HAIP?
  8. What happens to the HAIP if a physical NIC fails or is disabled?
  9. What happens to the HAIP if the failed or disabled physical NIC is brought back up?
  10. Does HAIP require NIC bonding or teaming?
  11. Can OS bonding or teaming still be used with HAIP?
  12 . Is the HAIP active even if there is only one NIC per node for the cluster interconnect?
  13. Is there any limit to how many redundant interconnect NICs that can be used by clusterware?
  14. With HAIP, are all the interconnect NICs active concurrently?
  15. Can I manually failover or failback HAIP?
  16. Is HAIP supported with pre-11.2.0.2 databases?
  17. What is the recommendation regarding using OS level NIC virtualization with HAIP?
  18. Can HAIP feature be disabled manually?
  19. Can RDS be used with HAIP?
References
APPLIES TO:


Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Information in this document applies to any platform.
Covers release 11.2
支持11.2.0.2之后的企业版的任何平台并且包含11.2版本
PURPOSE


The purpose of this note is to supplement the HAIP information available in Grid Infrastructure
 Redundant Interconnect and ora.cluster_interconnect.haip Note 1210883.1
对于grid软件私网冗余的增强机制
 


 


QUESTIONS AND ANSWERS


1. What does HAIP stand for?


Highly Available IP (address)
HAIP 是什么的简写，Highly Available IP (address)
2. What clusterware version was HAIP introduced in?


Oracle Grid Infrastructure 11.2.0.2
哪个版本引入HAIP  11.2.0.2
3. What is the purpose of HAIP?  


Haip has two primary functions:


HAIP allows for redundant cluster interconnect NICs on cluster nodes without requiring any OS level bonding, teaming or aggregating of the NICs.
HAIP provides a layer of transparency between multiple Network Interface Cards (NICs) on a given  node that are used for the cluster_interconnect which is used by RDBMS and ASM instances. However，it is not used for the Clusterware network heartbeat.
引入HAIP的目的：1）节点间私有网络的冗余，不需要再os层级的绑定分组等
                2）HAIP为节点在使用cluster_interconnect连接rdbms和asm instance的多网卡环境提供了透明的层级，然而它不是用于集群的心跳网络


4. How does HAIP create a layer of transparency between the cluster interconnect NICs on a given node and the RDBMS/ASM instances?


When clusterware on a given node is started, a virtual ip address (HAIP)  is dynamically allocated and linked (link-local) to each NIC configured for use as a cluster interconnect.  Each NIC defined as an interconnect (using oifcfg setif) will be assigned a unique HAIP during clusterware startup.  The HAIP from each interconnect NIC is then used by the the ASM 
 and RDBMS instances and ACFS.  The static ip address associated with the physical NIC is not used by the ASM and RDBMS instances. The NIC name is not used by the ASM or RDBMS instance but is used by other clusterware components.
 
 Each NIC defined as a cluster interconnect (using oifcfg setif) on a given node will have a static ip address assigned to it and each cluster interconnect NIC on a given node must be on a unique subnet. Clusterware requires that each subnet 
 used by the cluster interconnect have a functioning NIC on each active cluster node. If any one of the cluster interconnect NICs is down on a node, then the subnet associated with the down NIC is considered not usable by any node of the cluster.


HAIP 如何在给定节点的网卡上创建数据库和asm实例的透明层级
当节点的集群启动，一个虚拟ip动态分配和连接到每个配置集群内部网络的网卡上。每个配置了作为私网通信的网卡在集群启动时被定义一个
唯一的HAIP 这时每个私网网卡上的HAIP用来服务于asm实例和数据库以及acfs文件系统。网卡上配置的静态ip不被asm实例和数据库使用，但是
它被集群中的其他功能部件使用。
配置为私网的网卡节点有一个静态ip，它也必须有一个唯一的子网。集群要求集群内网使用的每个子网在每个活动的节点上存在一个有效的
网卡配置，如果集群内网中的一个节点的任何一个网卡down，down掉的子网相关的子网将不能被集群中的其他节点使用




5. How does HAIP obtain an IP address for use in the virtual link?


HAIP takes advantage of linked-local ip addresses as defined in the Internet Engineering Task Force RFC-3927 .  
This RFC reserves the IPv4 prefix 169.254/16 specifically for linked local use.


HAIP如何获得虚拟连接的ip地址
HAIP将使用RFC-3927定义的ipv4的地址，使用一个169.254/16网段的ip
6. How can I check if the HAIP is in use?


Use the OS command "ifconfig -a". Look in the ASM and RDBMS instance alert logs. During instance startup the interfaces and associated HAIP will be shown.


Alert log example showing two NICs
Starting ORACLE instance (normal)
...
Private Interface 'eth1:1' configured from GPnP for use as a private interconnect.
  [name='eth1:1', type=1, ip=169.254.89.182, mac=08-00-27-06-a4-37, net=169.254.0.0/17, mask=255.255.128.0, use=haip:cluster_interconnect/62]
Private Interface 'eth1:2' configured from GPnP for use as a private interconnect.
  [name='eth1:2', type=1, ip=169.254.224.204, mac=08-00-27-06-a4-37, net=169.254.128.0/17, mask=255.255.128.0, use=haip:cluster_interconnect/62]
...
 Cluster communication is configured to use the following interface(s) for this instance
  169.254.89.182
  169.254.224.204
  
 如何确认HAIP被使用。
 使用os命令 ifconfig -a 查看asm和database的alert日志
 
 
7. Which Oracle clusterware log shows the failover or failback of a HAIP?


The ohasd orarootagent_root logs under <GRID_HOME>/log/<node>/agent/ohasd/orarootagent_root/orarootagent_root.log.
哪个集群日志能够展示HAIP的故障转移和故障恢复
<GRID_HOME>/log/<node>/agent/ohasd/orarootagent_root/orarootagent_root.log.
8. What happens to the HAIP if a physical NIC fails or is disabled?


The HAIP associated with the failed NIC will failover and be linked-local to one of the remaining working physical NICs designated for the cluster interconnect. So the HAIP will now be on a different subnet, one that is working on all nodes.
An ARP broadcast will be made using the new MAC address for the NIC that the HAIP has attached to.  Since the ASM and RDBMS instances are using the HAIP, they transparently continue to work using the NIC that HAIP failed over to.An important point to note is that that HAIP will perform the same failover on EVERY active cluster node. The reason this is done is to ensure that the HAIP is attached to an NIC on the same subnet across all nodes. 


 如果物理的网卡fail或者disable HAIP会怎么样。
 HAIP将故障转移到另一个还在正常工作的网卡上，这样就在另一个私网段上。当然这个私网段也是在所有节点有配置的


9. What happens to the HAIP if the failed or disabled physical NIC is brought back up?


The HAIP will failback to the physical NIC it was linked to before the failover. The HAIP will be unlinked from  the redundant NIC it was temporarily on, and locally-linked to the interconnect NIC that was brought back online. 
As with a failover this also will happen on all nodes of the cluster to ensure the HAIP is on the same subnet on all nodes. An ARP broadcast is made to publish the changed MAC address of the NIC that each HAIP that failed back to.
当故障的物理网卡复活后HAIP会怎样
HAIP将回到最先坏掉现在正常的那个私网子网段的网卡上，他认为冗余的网卡只是一个临时的所在。一个arp广播通知mac地址转换会原来的网卡
10. Does HAIP require NIC bonding or teaming?


No. HAIP allows you to provide redundant NICS for the cluster interconnect without using OS level NIC bonding or teaming or aggregation. Each physical interface is presented to the clusterware and registered with the clusterware via the 
 Oracle clusterware command "oifcfg setif".
HAIP需要网卡绑定或者分组么
不需要，HAIP提供集群层级的冗余机制，每个为集群配置的物理网卡都是通过oifcfg setif 注册到集群中的
11. Can OS bonding or teaming still be used with HAIP?


Yes, however Oracle's best practice is to use unbonded, unteamed NICs, without any additional layers of virtualization.
os绑定和分组能与HAIP一起使用么
当然，尽管oracle最佳时间使用不绑定，不分组的网卡，并且在虚拟化上也没有额外的层级
12 . Is the HAIP active even if there is only one NIC per node for the cluster interconnect?


Yes.  This cannot be disabled manually (with the exception on Solaris where, when IPMP is in use, HAIP will not be enabled during installation).
HAIP 在集群私网中的每个只有一个网卡的节点也能active？
当然，它不能被手动禁用，除了solaris使用的IPMP（网卡负载均衡功能）
13. Is there any limit to how many redundant interconnect NICs that can be used by clusterware?


Yes. Clusterware will use up to four NICs, even if more are available.
集群私网冗余网卡有最大限制么
是的，最多支持4个。
14. With HAIP, are all the interconnect NICs active concurrently?


The default is for all interconnect NICs to be active.  The Oracle best practice to have all NICs active.
HAIP 条件下，所有的内部网卡都是同时active？
默认都是active，最佳实践也是活动的
15. Can I manually failover or failback HAIP?


No. There is no command that allows you to directly control failover and failback of HAIP.  Clusterware does this automatically.
能够手动故障转移和恢复么
不能，没有提供命令直接控制转移和恢复，集群软件自动实现故障转移和恢复。
16. Is HAIP supported with pre-11.2.0.2 databases?


The default behaviour for pre-11.2.0.2 databases is to use the fixed IP address associated with NICs and not use the HAIP.


The recommendation is to use OS level NIC bonding/teaming for pre 11.2.0.2 databases.
HAIP 支持11.2.0.2之前的版本么
11.2.0.2之前的数据库使用固定ip不能使用HAIP
建议的版本是11.2.0.2之后，之前的版本是可以使用os 层级的网卡绑定和分组功能
17. What is the recommendation regarding using OS level NIC virtualization with HAIP?


Oracle recommends using just HAIP, with no additional OS level NIC virtualization.
使用os层的虚拟网卡有什么建议
建议只是使用HAIP，不要附加其他OS级别的虚拟网卡技术
18. Can HAIP feature be disabled manually?


No, It's NOT supported to disable HAIP while the cluster is up and running. There are certain situations where HAIP feature is disabled during installation. Please refer to Note 1210883.1 Section Miscellaneous. For IPMP implementation on Solaris case, cluster_interconnects is required to set to IPMP IP. For other platforms, OS bonding technology should be used if 
more than 1 private network is used.


 HAIP特性能被手工禁用么
 不能，当HAIP启动运行时不支持被禁用。只有在安装的特定情况下可以被禁用。参考 Note 1210883.1 


19. Can RDS be used with HAIP?


Yes with restrictions.  See  Doc ID 745616.1
RDS 可以和HAIP一起使用么
是的，但是有限制 参考Doc ID 745616.1