ORACLE在HP-UX下的系列问题处理(38)

　　OV IT/O: 无法在SG环境中通过防火墙分配模板问题描述
　　
　　我无法在Service Guard环境中通过防火墙分配模板，同时，安装代理软件时没有任何问题。
　　
　　为什么会出现这个问题，如何解决？
　　
　　配置信息
　　
　　操作系统 - HP-UX
　　版本 - 10.20
　　硬件系统 - HP9000
　　应用程序 - Oracle 7.2.3
　　
　　解决方法
　　
　　你最初的问题是由于rpcd向代理程序报告物理结点的源地址。
　　
　　根据你的防火墙配置的方式，在通过防火墙时，你不能用MC Service Guard配置IT/O。
　　
　　这个问题可以追溯到这样的事实，即UDP是传输协议，没有办法锁定无连接协议的源地址。
　　
　　当数据包发送给治理结点时选择目标地址，操作系统根据治理服务器中的网络路由表分配源地址。由于同一个网络号使用相同的主机号，因此使用给定网卡(MC Service Guard)上的第一个地址，我们不能改变这个行为。
　　
　　这个问题的解决方法是使用传输控制协议(TCP)进行传输。由于TCP是一个基于连接的协议，因此会话过程中源地址是统一的。假如治理结点在可再定位的地址打开一个会话，那么从治理服务器到治理结点的所有流量（在该会话中）将都以这个可再定位的地址作为源地址。
　　
　　你也可以考虑重新配置防火墙，接受来自可再定位地址和固定地址的数据包。
　　
　　当前的技术还无法为你马上提供一个解决方法。
　　.........following with all English text ....
　　Problem Description
　　
　　I cannot distribute templates in a Service Guard environment over the
　　firewall. At the same time, I don't have any problems installing the agent software.
　　
　　Why am I having this problem, and do you have a solution?
　　
　　Configuration Info
　　
　　Operating System - HP-UX
　　Version - 10.20
　　Hardware System - HP9000
　　Application - Oracle 7.2.3
　　
　　Solution
　　
　　Your initial problem is due to rpcd reporting back to the agent with the source address of the physical node.
　　
　　Based upon the way your firewall is configured, you cannot configure IT/O with MC Service Guard while passing through a firewall.
　　
　　The problem can be traced to the fact that UDP is the transport protocol,and there is no way to lock down the origination address for a connectionless protocol.
　　
　　When a packet is sent to a managed node, the destination address is selected, and the operating system assigns the source address according to network routing tables in the management server. Since two host numbers exist for the same network number, the first address on a given
　　Network Interface Card (MC Service Guard) is used. We can't change this behavior.
　　
　　The solution to this problem is to use Tranmission Control Protocol (TCP) as the transport. Because TCP is a connection-based protocol, the origination address is consistent for the session. If the managed node opens a session to the relocatable address,
all traffic from the
　　management server to the managed node (in that session) will have the
　　relocatable address as the source address.
　　
　　You could also consider reconfiguring the firewalls to allow packets from the relocatable address and the stationary address.
　　
　　With the current technology, it is not possible to give you an immediate solution.