![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Each P-7500 system in an active/active redundancy pair can serve clients and send and receive RV messages during normal operating conditions. However, should one of the systems fail, the active system can provide the service ordinarily provided by both of the systems individually. This model differs from an active/standby model where a primary system provides service to clients and sends and receives data, and the backup system waits in standby mode but only provides service should the primary system fail.To support active/active redundancy, each P-7500 system uses a primary and backup virtual router. When both systems are active, the primary virtual routers on both systems are active, but the backup virtual routers are idle. If one of the systems in the redundant pair goes out of service, the backup virtual router of the active system changes to an active state, and it provides service for clients and handles the RV messages that typically use the primary virtual router of the system that is out of service.To enable the backup virtual router of one system to assume the role of its mate’s primary virtual router when a system failure occurs, the configuration of the virtual routers on each system must mirror one another. That is, the backup virtual routers on both systems must have the same configuration as the primary virtual routers they backup.
P-7500 1 Backup
Virtual Router P-7500 2 Primary
Virtual Router P-7500 2 Backup
Virtual Router P-7500 1 Primary
Virtual Router
Use of RV Gateway services is not mandatory for system redundancy; you can configure a redundant pair of P-7500 systems without it. However, if you do need to use RV Gateway services with a redundant P-7500 system pair, then primary and backup Rendezvous Gateway Daemons (RVGDs) are required on each system. For more information on configuring RV Gateway services, refer to Chapter 2, “Managing TIBCO Rendezvous Tasks”.For each P-7500 system, physical interfaces on the Network Acceleration Blade (NAB) must be bound to distinct IP interfaces, each identified by an IP address and subnet mask. It is these IP interfaces that clients connect to.To enable active/active redundancy, primary and backup instances of the IP interfaces are created for each system in a redundant pair. The same IP interfaces are used by each system, but they are assigned as primary on one and as backup on the other. Therefore, if one system goes out of service, a backup IP interface can still be accessed by the client on the active system.These primary and backup IP interfaces are associated with the primary and backup virtual routers on each system in the redundant pair.Figure 8 illustrates a simplified example of the primary and backup IP interfaces and virtual routers used by a redundant pair. Figure 9 illustrates the same redundant pair in a failover situation.
• On P-7500 2, the physical interface 1/6/1 contains two IP interfaces. 1/6/1:1 is configured as the primary IP interface with IP address 192.168.171.133/19, and 1/6/1:2 is configured as the backup IP interface with IP address 192.168.181.110/19.
• To maintain service if P-7500 2 goes down, the mate system, P-7500 1, also contains the IP interfaces 1/6/1:1 and 1/6/1:2. However the IP addresses assigned to these IP interfaces are reversed. For P-7500 1, the primary IP interface 1/6/1:1 is configured with IP address 192.168.181.110/19, and the backup IP interface 1/6/1:2 is configured with IP address 1192.168.171.133/19.
An ip number from 1 to 3 indicates the type of IP interface (primary, backup, or static). A typical association is 1 for primary, 2 for backup, and 3 for static. However, this is not enforced.In addition to the IP interfaces to which a client connect, the following components of the P-7500 system must also be associated with an IP interface and given a redundant configuration:
• VRRP interface—A P-7500 redundant pair uses the Virtual Router Redundancy Protocol (VRRP) as described in RFC 3768 to indicate the status of the virtual routers. To facilitate communication between each system of the redundant pair, a VRRP interface is used on each system. Primary and backup instances are also required for each VRRP interface, and to enable redundancy, the IP addresses assigned for both primary VRRP interfaces must match the IP addresses for their backup VRRP interfaces.
• RV Interface—The RV interface is used for the RVGD to communicate with the NAB and for generating client _INBOX subscriptions. On each system of the redundant pair, one instance of the RV interface must be configured as primary and another as backup, and both instances must be assigned a IP address. To enable redundancy, the IP addresses assigned for both primary RV interfaces must match the IP addresses for their backup RV interfaces.
• eth2 Interface—The RV Gateway uses the Ethernet 2 (eth2) physical interface to communicate with the TIBCO Messaging Appliance P-7500 system and other RV entities in the network. The eth2 interface is active only when RV Gateway services are running on the system. Therefore, if RV Gateway services are not running on your network, you do not need to configure eth2.
In a redundant configuration, two IP interfaces must be configured for eth2. On each system of the redundant pair, one IP interface of eth2 must be configured as primary (eth2:1) and another as backup (eth2:2), and both IP interfaces must be assigned an IP address. The IP addresses for both primary eth2 interfaces must match the IP addresses for their backup eth2 interfaces.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |