RP/TUX 6.4 - Network failover
(Doc ID 768732.1)
Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo / Tuxedo / 6.4
Information in this document applies to any platform
Tuxedo 6.4.11 on Solaris. Customer is running MP configuration with: 1. Master 2. Backup 3. Slave To simplify this I am just considering 1 and 2 The Master has three ip address 1 ip1 (host name and default ip) not used in ubb 2.ip2 (added through ifconfig) belonging to netgroup N1 3.ip3 (added through ifconfig) belonging to netgroup N2 The Backup has three ip address 1 ip1 (host name and default ip) not used in ubb 2.ip2 (added through ifconfig) belonging to netgroup N1 3.ip3 (added through ifconfig) belonging to netgroup N2 The Netgroup N1 and N2 have the same priority. N1 has a higher net group number than N2 and thus is the default network. The problems reported by the customer: 1. When customer brings down ip2 on Master the ip2 on slave connects to ip1 on master with a random port number. The customer says this would be a problem in his application because they do not want ip1 to be used by tuxedo application and thus it does not have a mention in the ubbconfig in the NETWORK Section. ip1 is a part of the pubic network and thus they do not want any one to use the same. Replication Scenario: 1) An MP configuration was booted across tsserver1 and ts2 using ubbsimple provided on Supportprod 2) Interfaces may need to be added for both master and backup. For example: ifconfig le0:2 iii.ppp.193.159 netmask iii.ppp.193.259 up 3) Bring down primary network on master. For example: ifconfig le0:2 down 4) This is what is in the ulog for the slave: 122725.ts2!tlisten.2407: CMDTUX_CAT:4209: INFO: Accepted request from //126.96.36.199:53591, seq # 3 This ip address //188.8.131.52:53591 is not mentioned in the NETWORK section. This is the machine ip address mentioned in the ubbconfig in the MACHINE section.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document