Applies To:

Show Versions Show Versions

Manual Chapter: BIG-IP® Network and System Management Guide: Appendix B - Configuring bigdb Database Keys
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>


B

Configuring bigdb Database Keys


Introducing the bigdb database

Every BIG-IP® system includes a bigdb database. The bigdb database holds a set of bigdb configuration keys, which define the behavior of various aspects of the BIG-IP system. For example, the bigdb key Failover.Active Mode, when set to enable, causes a redundant system to operate in active-active mode, instead of the default active/standby mode.

You can change the value of a bigdb key in two ways:

  • The Configuration utility
    When you use the Configuration utility to configure various BIG-IP features, you are actually resetting bigdb key values. In this case, the bigdb keys are invisible to users.
  • The bigpipe db command
    You can reset bigdb key values directly using the bigpipe db command. This command is useful if you prefer not to use the Configuration utility to configure a BIG-IP feature, or if configuration of a particular aspect of BIG-IP system behavior is not available through the Configuration utility. The syntax for displaying and setting bigdb keys is:
  • bigpipe db all list bigpipe db <key name> <value>

Tip


For more information on using the bigpipe db command, see the online man page for the command.

Some of the bigdb database keys for system management that you might want to configure pertain specifically to redundant systems and user accounts.

Summarizing bigdb keys for redundant system administration

There are several bigdb keys that you can use to configure and manage a redundant system. These keys pertain to the following redundant-system features:

  • Failover
  • Connection mirroring
  • Configuration synchronization
  • System fail-safe

Using failover keys

The bigdb keys that you can configure for failover are shown in Table B.1 . These keys are listed in alphabetical order.

Table B.1 bigdb database keys pertaining to failover
Key Name
Default Value
Description
Failover.ActiveMode
disable
Enables or disables active-active mode. Use active-active mode if set to 1. By default, this is 0 (off) and active/standby mode is used. Possible values are enable and disable.
Failover.DbgFile
/var/log/sodlog
Specifies the file into which the sod service logs the failover debug information.
Failover.FailbackDelay
60
For an active-active system, when the failed unit becomes active again, specifies the number of seconds that you want the system to wait before failback occurs.
Failover.FailedStandbyActive
disable
Controls whether a standby unit with a failover condition becomes active when the peer unit fails. Possible values are enable and disable.
Failover.ForceActive
disable
Specifies that the failover daemon should always attempt to become the active unit. Possible values are enable and disable.
Failover.ForceStandby
disable
Specifies that the failover daemon should switch to a standby state whenever the current unit senses that its peer is alive. Possible values are enable and disable.
Failover.Ipaddr
No default value
Specifies the IP address for the management interface. If you specify this address, the BIG-IP system uses the address as the primary failover address when failover occurs. In this case, the BIG-IP system uses the IP address that you specified in the Primary Failover Address setting of the Configuration utility for state mirroring purposes only.
Failover.Peer.Ipaddr
No default value
Specifies the IP address for the management interface of the peer unit. If you specify this address, the BIG-IP system uses the address as the primary failover address when failover occurs. In this case, the BIG-IP system uses the IP address that you specified in the Primary Failover Address setting of the Configuration utility for state mirroring purposes only.
Failover.IsRedundant
false
Defines whether the BIG-IP system is a unit of a redundant pair. Possible values are true and false.
Failover.ManFailBack
disable
If using active-active mode, specifies that the system should wait until the surviving unit receives a command before surrendering resources to a rebooted machine. Possible values are enable and disable.
Failover.MemoryRestartPercent
97
Defines the amount of memory usage that causes the BIG-IP system to reboot.
Failover.Network
0
Specifies whether the system should use the network as a backup to, or instead of, the hard-wired connection for failover. Possible values are 0 (off) and 1 (on).
Failover.PrintPeerState
disable
Specifies that the failover daemon (/sbin/sod) should write the state of its connection (hard-wired or network) to its peer. The system writes this information to the failover daemon's debug log file. Possible values are enable and disable.
Failover.Standby.LinkDownTime
0
Defines the amount of time in tenths of seconds that the system's interfaces are down before switching to a standby state. For example, a value of 50 represents 5 seconds.
Failover.UnitId
1
Specifies the ID of the unit. Each BIG-IP system must have a unique unit ID of 1 or 2 in the event that network communication is not possible with its peer.
Failover.UseTty00
disable
Specifies that the failover daemon should use /dev/tty00 for hard-wired failover. Possible values are enable and disable.
Failover.UseTty01
disable
Specifies that the failover daemon should use /dev/tty01 for hard-wired failover. Possible values are enable and disable.

 

Using connection mirroring keys

The bigdb keys that you can configure for connection mirroring are shown in Table B.2 . These keys are listed in alphabetical order

Table B.2 bigdb database keys pertaining to connection mirroring
Key Name
Default Value
Description
StateMirror.Ipaddr
No default value
Specifies the unit's primary static self IP address that its peer uses to mirror connections.
StateMirror.PeerIpaddr
No default value
Specifies the peer unit's primary static self IP address that a unit uses to mirror connections.
StateMirror.PeerListenPort
1028
Defines the port on which the BIG-IP system listens for connections from the active unit.
StateMirror.Secondary.Ipaddr
No default value
Specifies the unit's secondary static self IP address that its peer uses to mirror connections.
StateMirror.SecondaryPeerIpaddr
No default value
Specifies the peer unit's secondary static self IP address that a unit uses to mirror connections.
StateMirror.State
enable
Defines whether connection mirroring is enabled or disabled for a redundant system. Possible values are enable and disable.

.

Using configuration synchronization keys

The bigdb keys that you can configure for synchronizing configuration data are shown in Table B.3 . These keys are listed in alphabetical order.

Table B.3 bigdb database keys pertaining to configuration synchronization
Key Name
Default Value
Description
Configsync.Autodetect
enable
Defines whether the Configuration utility should automatically detect configuration status and display it on all Configuration utility screens. Possible values are enable and disable.
Configsync.LocalConfigTime
0
Specifies the most recent date and time that the configuration of the current unit changed.
Configsync.LocalSyncedTime
0
Specifies the date and time that the configuration of this unit was synchronized with the peer unit.
Configsync.password
No default value
Defines the password of the user account that has permission to synchronize configuration data.
Configsync.PeerConfigTime
0
Specifies the most recent date and time that the configuration of the peer unit changed.
Configsync.PeerState
unknown
Defines whether the peer's synchronization state is known. Possible values are known and unknown.
Configsync.PeerUpdatedTime
0
Specifies the date and time that this unit successfully informed its peer of a configuration change on this unit.
Configsync.State
-1
Specifies the configuration state of this box. Possible values are:
-1 - Uninitiated or disabled config state.
0 - Synchronized.
1 - Configuration on current unit was modified. Recommend configuration synchronization to peer unit.
2 - Configuration on peer unit was modified. Recommend configuration synchronization from peer unit.
3 - Configuration modified on both units. Manual intervention required.
Configsync.username
admin
Defines the user account that has permission to synchronize configuration data.

 

Using system fail-safe keys

The bigdb keys that you can configure for system fail-safe are shown in Table B.4 . These keys are listed in alphabetical order.

Table B.4 bigdb database keys pertaining to system fail-safe
Key Name
Default Value
Description
Switchboard.Failsafe
enable
Enables or disables fail-safe when the switch board fails. Possible values are enable and disable.
Switchboard.Failsafe.Action
failover
Specifies the action that the system takes when the switch board fails. Possible values are failover, reboot, and restart_all.

 

Summarizing bigdb keys for user account administration

You can configure a set of bigdb keys to manage administrative user accounts for a BIG-IP system. These keys and their descriptions appear in Table B.5 , and are listed in alphabetical order.

Table B.5 bigdb database keys pertaining to user accounts
Key Name
Default Value
Description
User.AcceptedEULA
none
Specifies fields that the Setup utility populates. Possible values are none, internal, non-production, and production.
Users.Default.Role
127
Specifies a numeric value for the default role for remote user accounts.
Users.LocalOnly
root,admin
Specifies those user accounts that must reside locally on the BIG-IP system and therefore cannot reside on a remote authentication server.
Users.Name.admin
0
Specifies a numeric value for the admin account.
Users.Name.support
0
Specifies a numeric value for the support account.
Users.Name.[user name]
127
Specifies a numeric value for any user account that is not root, admin, or support.

 

Summarizing bigdb keys for event logging

The bigdb keys that you can configure to set the minimum log level on local traffic and authentication events are shown in Table B.6 . These keys are listed in alphabetical order. For information on all possible key values, see Chapter 17, Logging BIG-IP System Events .

Table B.6 bigdb database keys pertaining to setting log levels
Key Name
Default Value
Description
Bigdb.loglevel
Informational
Sets the minimum log level for events related to populating and persisting bigdb database variables.
log.arp.level
Warning
Sets the minimum log level for events related to ARP packets and the ARP cache. These events include IPv6 neighbor discovery events.
log.config.level
Notice
Sets the minimum log level for MCP events related to configuring the Traffic Management Microkernel (TMM).
log.deflate.level
Error
Sets the minimum log level for events related to HTTP compression.
log.http.level
Error
Sets the minimum log level for events related to HTTP protocol processing.
log.ipnet.level
Notice
Sets the minimum log level for events related to packets discarded due to exceptional circumstances, such as bad checksums or unhandled protocol versions.
log.layer4.level
Notice
Sets the minimum log level for events related to TCP, UDP, and FastL4 protocol and packet processing.
log.net.level
Warning
Sets the minimum log level for events related to Layer 1 and Layer 2 processing.
log.pva.level
Informational
Sets the minimum log level for events generated by the Packet Velocity® ASIC service pvad.
log. rules.level
Informational
Sets the minimum log level for events related to run-time processing or iRules.
log.ssl.level
Warning
Sets the minimum log level for events related to SSL protocol processing.
log.tmm.level
Notice
Sets the minimum log level for general events such as TMM startup and shutdown.

 

Summarizing bigdb keys for HTTP compression

You can configure a set of bigdb keys to manage the way that the BIG-IP system handles the compression of HTTP server responses. These keys and their descriptions appear in Table B.7 , and are listed in alphabetical order.

Table B.7 bigdb database keys pertaining to HTTP data compression
Key Name
Default Value
Description
Compression.Hardware.Ratio
4
Used only when the Compression.Strategy key is set to ratio. This ratio defines how each compressible response is load balanced between compression devices.
Compression.Offload.Ratio
4
Used only when the Compression.Strategy key is set to ratio. This ratio defines how each compressible response is load balanced between compression devices.
Compression.Strategy
speed
Sets the way that the system directs traffic flow. Possible values are speed, size, and ratio:
speed - The system uses the hardware to the fullest extent possible. The speed value is best used for bulk compression and for limiting CPU overhead.
size - When the key is set to the size value, the system performs as much compression in the software as possible. Normally, the system uses a ratio of TMM and Offload. When both are busy, compression is performed in the hardware. The size value gives the best ratio at the expense of CPU overhead.
ratio - The system uses the three bigdb keys Compression.Hardware.Ratio, Compression.Offload.Ratio, and Compression.TMM.Ratio, with the goal of limiting CPU overhead while giving good compression ratios.
Compression.TMM.Ratio
1
Used only when the Compression.Strategy key is set to ratio. This ratio defines how each compressible response is load balanced between compression devices.

 

Configuring bigdb settings for RAM Cache

You can fine tune the RAM Cache implementation by changing settings in the bigdb database. We recommend that you change these settings only while under the direction of an F5 support representative. The following bigdb setting is available for the RAM Cache feature.

Table B.8 bigdb database key pertaining to the HTTP RAM Cache feature
Key Name
Default Value
Description
RamCache.MaxMemoryPercent
50
Defines the percentage of TMM memory that is available to all RAM Cache instances. This means that the RAM Cache size is represented by this statement:
ramcacheprofile1 + ramcacheprofile2 + ramcacheprofile3 must not equal more than Total Memory times the Ramcache.MaxMemoryPercent divided by 100.
Note: Changes to this setting take effect only after restarting the BIG-IP system services, including the TMM service.

 

Configuring bigdb settings for SYN cookie protection

You can configure certain bigdb keys to enable SYN cookie protection, a feature of some Packet Velocity® ASIC (PVA) systems. The bigdb settings in Table B.9 are available for the SYN cookie protection feature.

Table B.9 bigdb database key pertaining to the SYN cookie protection feature
Key Name
Default Value
Description
Pva.SynCookies.Full.ConnectionThreshold
500000
Defines a threshold for the number of current connections. If this value is above the threshold, SYN cookie protection is enabled for virtual servers that reference a Fast L4 profile with the PVA Acceleration setting set to Full.
Pva.SynCookies.Assist.ConnectionThreshold
500000
Defines a threshold for the number of current connections. If this value is above the threshold, SYN cookie protection is enabled for virtual servers that reference a Fast L4 profile with the PVA Acceleration setting set to Assisted.
Pva.SynCookies.ClientWindow
0
Defines the TCP window size in the initial PVA-generated SYN cookie SYN+ACK packet to the client. We highly recommend that you retain the default value.

 

 




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)