Mutually-aware configuration table

When you configure an OpenSwitch to be mutually aware, a configuration table is created and saved to both Adaptive Servers, which eliminates any single point of failure created by one Adaptive Server. This table can be accessed by both the primary and secondary OpenSwitch servers.

The primary OpenSwitch server is responsible for updating the configuration table on the Adaptive Servers.

When you configure OpenSwitch by manually editing the configuration file, the mutually-aware configuration table is created the first time you start the OpenSwitch server.

Table 6-2 lists the columns in the mutually-aware configuration table created in the Adaptive Servers:

**Table 6-2: Mutually-aware configuration table**
Column	Description
Pool	Name of the Adaptive Server connection pool. Each pool corresponds to exactly one row.
Pool_status	Status of this pool in the OpenSwitch configuration.
Pool_mode	Select: Chained – to have all connections routed to the first server defined within the pool, and have administrative switch requests or automatic failovers send all connections to the next server in the pool. Balanced – to have all servers in a pool used simultaneously (load-balanced) until a server fails, at which time all connections on the failed server are redistributed, in round-robin fashion, among the remaining servers.
Pool_cache	The number of seconds a connection is kept alive after a client disconnects. If the same client, using the same user name and password, reconnects during this duration, the connection can be handed off without establishing a new connection, which reduces the overhead of establishing connections each time a client connects.
Attr_username	User name attribute for this pool, if any.
Attr_appname	Application name attribute for this pool, if any.
Attr_hostname	Host name attribute for this pool, if any.
Attr_type	Whether this pool handles “site” or “client” connections.
Primary_server	Name of the primary server in this pool.
Primary_status	The status of the primary server in the OpenSwitch configuration. Primary_status is the same as the server status in the [SERVER] section of the OpenSwitch configuration file, which may be different from the pool-specific server status under the [POOL] section. A mutually-aware OpenSwitch server does not currently support pool-based server status.
Primary_type	Whether the primary server is a high-availability server.
Primary_cfgstore	Whether CFG_STORAGE is set for the primary server.
Primary_cmonuser	The primary server-specific CMON user name.
Primary_cmonpwd	The primary server-specific CMON password.
Secondary_server	Name of the secondary server in this pool.
Secondary_status	The status of the secondary server in the OpenSwitch configuration. Secondary_status is the same as the server status in the [SERVER] section of the OpenSwitch configuration file, which may be different from the pool-specific server status under the [POOL] section. A mutually-aware OpenSwitch server does not currently support pool-based server status
Secondary_type	Whether the secondary server is a high-availability server.
Secondary_cfgstore	Whether CFG_STORAGE is set for the secondary server.
Secondary_cmonuser	The secondary server-specific CMON user name.
Secondary_cmonpwd	The secondary server-specific CMON user name.
Replication_status	The status of the pool replication direction, as determined by the RCM. Currently displays only “Normal.” Reserved for future use.
Timestamp	The timestamp for this entry.
Updated_by	Name of the OpenSwitch server that updated this entry.
Sequence_num	A unique identification number generated by the master OpenSwitch for each update event.

If you use rp_pool_status or rp_server_status to change the status of a pool or server at runtime for a mutually-aware OpenSwitch, the change is propagated to the companion OpenSwitch server and stored in the Adaptive Server configuration table to ensure maximum redundancy and persistence between OpenSwitch start-ups.

Currently, only changes to the pool and server status made using rp_pool_status and rp_server_status are propagated to the companion and stored in the configuration tables. Runtime changes to other pool or server attributes, and changes to the pool and server status made using rp_cfg, are not propagated to the companion and stored in the configuration tables.