Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Rendezvous Gateway : Redundancy and the Gateway

Redundancy and the Gateway
Figure 8 illustrates gateway configuration for redundant operation, and Figure 9 illustrates the behavior during failover.
Figure 8 Gateway: Symmetric Configuration for Redundancy
 
Configuration
Configure the two gateway pairs symmetrically.
Task A Routing Table Entries
1.
2.
Task B NAB LANs
3.
4.
Task C Neighbors
5.
6.
7.
8.
Task D GP LAN
9.
Do not configure this local network for B2. To understand the reason, see the neighbor connection in Figure 9, which you added in Task C.
10.
Do not configure this local network for A2. To understand the reason, see the neighbor connection in Figure 9, which you added in Task C.
Task E Subject Gating
11.
12.
13.
14.
15.
Copy subject gating from A1 (see step 13) to B1 (not B2). To understand the reason, see the neighbor connection in Figure 9, which you added in Task C.
16.
Copy subject gating from B1 (see step 14) to A1 (not A2). To understand the reason, see the neighbor connection in Figure 9, which you added in Task C.
After steps 1316, A1 and B1 should have identical subject gating configurations with respect to the GP LAN.
 
Router Name
In steps 1 and 2, the router name of the backup gateway must be identical to the router name of its counterpart primary gateway. One might think this is illegal, because router names must be unique throughout a WAN (see Routing Table Entry in TIBCO Rendezvous Administration).
Nonetheless, in this situation the backup gateway remains idle until failover. While idle, the backup gateway does not expose its router instances to the WAN, so name collision does not occur.
At failover, the backup gateway enters the running state, and exposes its router instances to the WAN. At that time, the primary gateway is unavailable, so name collision still does not occur.
Normal Operation
Figure 8 illustrates gateway operation in the normal situation, in which both P-7500s are available:
Virtual router B2 is waiting in the backup role.
Virtual router A2 is waiting in the backup role.
 
An idle gateway does not communicate with neighbors or local networks, and does not forward any data. You can configure it through its browser administration interface, but otherwise it is effectively invisible and inert. In this respect, an idle gateway behaves like an idle routing daemon.
(In contrast, routing daemons, instances of rvrd, are in a redundant configuration, they are always running—rather than waiting idle. They can communicate with their neighbors and local networks, and they can forward data.)
Failover Behavior
Figure 9 Gateway: Redundant Failover
 
Figure 9 illustrates failover when P-7500 B fails:
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved