Applies To:

Show Versions Show Versions

Archived Manual Chapter: 3-DNS Reference Manual v4.5.10: The bigdb Database and bigdb Keys
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

This article has been archived, and is no longer maintained.



E

 

The bigdb Database and bigdb Keys



Working with the bigdb database

The bigdbTM database holds certain configuration information for the 3-DNS Controller. You use the bigpipe db command to load configuration information into the bigdb database. The default.txt file contains the default information for the bigdb database.

Using the bigpipe db command

You can view and set the bigdb keys using following options of the bigpipe db command. Note that these keys are set automatically when you use the Configuration utility to configure the 3-DNS Controller.

To display the current setting of a bigdb configuration key

To display the value of a bigdb key, use the following syntax:

b db get <key | regular_exp>

For example, the following command displays the value of the Local.Bigip.Failover.ForceActive key, which causes the unit to always be the active unit in a redundant system. By default, this key is set to 0 (zero), which is off.

b db get Local.Bigip.Failover.ForceActive

You can use the following command to display the value of all local keys:

b db get Local.*

To set a bigdb configuration key

To create (set) a bigdb key, use the following syntax:

b db set <key>

To create a bigdb key and also assign a value to it, use the following syntax:

b db set <key> = <value>

For example, the following command causes the unit to always try to be the active unit in a redundant system:

b db set Local.Bigip.Failover.ForceActive = 1

To disable a bigdb key

To disable a bigdb key, use the following syntax.

b db unset <key | regular_exp>

For example, the following command disables the Local.Bigip.Failover.UnitId key:

b db unset Local.Bigip.Failover.UnitId

The following command disables all local keys:

b db unset set Local.*


Working with the default.txt file

The default.txt file documents the keys that are valid in the bigdb database. This file is located in the /config/default.txt directory. It contains all the possible database keys, comments that document these keys, and the default values used by programs that run on the 3-DNS Controller.

Note


The values in the default.txt file are default values; several of the keys listed are not present in the bigdb database.

 

The default.txt file is intended to serve as documentation only. In order for the system to work, some of the keys, such as those that represent IP addresses and port numbers, need to be set to values other than the default values. Additionally, some of the key names listed are wildcard keys. These keys are not valid key names.

For a list of the keys in the bigdb database that are applicable to a 3-DNS Controller, see the following section.


Supported bigdb keys on a 3-DNS Controller

The bigdb database contains failover and system keys for the 3-DNS Controller. Configuration options in the bigdb database that the 3-DNS Controller supports include:

  • Fail-over

  • CORBA

The bigdb keys for each of these features are described in the following series of tables. You can view and set the bigdb keys using the bigpipe db command, as described in Using the bigpipe db command, on page E-1 .


Fail-over and cluster keys

The fail-over and cluster keys control fail-over from the active to the standby unit in a 3-DNS redundant system. If you change one of these values, you must update the 3-DNS configuration using the bigpipe failover init command (which is the same command as bigstart reinit sod). This command forces the system to reread the bigdb database and use the new values. To run this command, type the following:

b failover init

Table E.1, on page E-4 , lists the fail-over and cluster keys.


 

Fail-Over Key Name and Default Value

Description

Common.Bigip.Failover.AwaitPeerAliveDelay = 2

Delay in seconds before testing whether peer is active. The default value is 2.

Common.Bigip.Failover.AwaitPeerDeadDelay = 1

Delay in seconds before testing whether the peer has failed. The default value is 1.

Common.Bigip.Failover.NoSyncTime

By default, one unit in a redundant system synchronizes its time with the other unit. Set this key to 1 to turn off the time synchronization feature.

Common.Bigip.Failover.DbgFile

File into which sod logs the fail-over debug information.

Common.Bigip.Failover.PrintPeerState = 0

The default value for this key is 0. The fail-over utility writes the state of its connection to its peer. This information is written to the fail-over utility's debug log file.

Common.Bigip.Failover.UseTty00 = 0

The fail-over utility uses /dev/tty00 for hard wired fail-over.

Common.Bigip.Failover.UseTty01 = 1

The fail-over utility uses /dev/tty01 for hard wired fail-over.

Local.Bigip.Failover.ForceActive = 0

This unit always attempts to become the active unit in a redundant system.

Local.Bigip.Failover.ForceStandby = 0

This unit goes to standby whenever it senses that its peer is alive.

Common.Sys.Failover.Network = 0

Use the network as a backup to, or instead of, the serial line for fail-over if this value is 1. By default, this feature is 0 (off).

Common.Sys.Failover.NetTimeoutSec = 3

When using network failover, after sending a ping to this unit's peer, wait this many seconds for a response to the ping before timing out and sending another ping.

Common.Sys.Failover.NetRetryLimit = 3

When using network failover, if the ping times out, then resend the ping this many times before initiating a reboot for the peer unit.

Common.Bigip.Failover.On3DNSFail = true

This variable, if set, will cause a fail-over if the 3dnsd daemon dies.

 

 


CORBA keys

Table E.2 lists the CORBA keys contained in the bigdb database.

 

Key Names

Description

Common.Bigip.CORBA.IIOPPort ="683"

Default CORBA IIOP port used for the iControlTM API.

Common.Bigip.CORBA.SSLPort ="684"

Default CORBA IIOP SSL port used for the iControlTM API.

Common.Bigip.CORBA.AddrResolveNumeric="true"

When set to true, the CORBA portal resolves client addresses numerically.

 






Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)