1. ACLI Reference Guide
  2. ACLI Configuration Elements N-Z
  3. redundancy

redundancy

The redundancy element establishes HA parameters for a Oracle Communications Session Border Controller that participates in an HA architecture.

Parameters

state
Enable or disable HA for the Oracle Communications Session Border Controller
  • Default enabled
  • Values enabled | disabled

    Note:

    This parameter is not RTC supported.
log-level
Select the starting log level for the HA process. This value supersedes the value configured in the process-log-level field in the system-config element for the HA process
  • Default: info
  • Values:
    • emergency
    • critical
    • major
    • minor
    • warning
    • notice
    • info
    • trace
    • debug
    • detail
health-threshold
Enter the health score at which standby Oracle Communications Session Border Controller switches over to the Active state and takes control of all system functionality as the active Oracle Communications Session Border Controller
  • Default: 75
  • Values: Min: 1 | Max: 100
emergency-threshold
Enter the low health score value that triggers the initializing standby Oracle Communications Session Border Controller to become the active Oracle Communications Session Border Controller immediately. In addition, the active but unhealthy Oracle Communications Session Border Controller, regardless of its health, will not relinquish its Active state if the HA Oracle Communications Session Border Controller peer poised to become active upon switchover also has a health score below this emergency-threshold value.
  • Default: 50
  • Values: Min: 1 | Max: 100
port
Enter the port number on which the border element redundancy protocol is listening
  • Default: 9090
  • Values: Min: 1025 | Max: 65535

    Note:

    This parameter is not RTC supported.
advertisement-time
Enter the time in milliseconds the Oracle Communications Session Border Controller continually sends its health score to its HA Oracle Communications Session Border Controller peer(s)
  • Default: 500
  • Values: Min: 50 | Max: 999999999
percent-drift
Set the percentage of an HA Oracle Communications Session Border Controller peer’s advertisement time for this HA Oracle Communications Session Border Controller to wait before considering its peer to be out of service
  • Default: 210
  • Values: Min: 100 | Max: 65535
initial-time
Enter the number of milliseconds to set the longest amount of time the Oracle Communications Session Border Controller will wait at boot time to change its state from initial to either becoming active or becoming standby. This field is independent of the advertisement-time and percent-drift parameters; it is a timer used to decide the state transition.
  • Default: 1250
  • Values: Min: 5 / Max: 999999999
becoming-standby-time
Enter the time in milliseconds to wait before transitioning to the Standby state. This field allows the HA Oracle Communications Session Border Controller enough time to synchronize with its HA Oracle Communications Session Border Controller peer. If the HA Oracle Communications Session Border Controller has not become fully synchronized within the time frame established in this field, it will be declared out of service. We recommend setting this parameter to no less than 180000 if configuration checkpointing is used.
  • Default: 45000
  • Values: Min: 5 / Max: 999999999
becoming-active-time
Enter the time in milliseconds a previously standby Oracle Communications Session Border Controller takes to become active. This field applies to the following scenarios:
  • When the health of an active Oracle Communications Session Border Controller has failed
  • When the standby Oracle Communications Session Border Controller is healthier than the active Oracle Communications Session Border Controller
becoming-active-time
Enter the time in milliseconds a previously standby Oracle Communications Session Border Controller takes to become active. This field applies to the following scenarios:
  • When the health of an active Oracle Communications Session Border Controller has failed
  • When the standby Oracle Communications Session Border Controller is healthier than the active Oracle Communications Session Border Controller
    This is a transitional state.
    • Default: 100
    • Values: Min: 5 / Max: 999999999
cfg-port
Enter the port number from which HA checkpoint messages are sent and received. This field supports Configuration Checkpointing. Setting the cfg-port field value to 0 disables configuration checkpointing.
  • Default: 1987
  • Values: Min: 1025 / Max: 65535; 0

    Note:

    This parameter is not RTC supported.
cfg-max-trans
Enter the size of the HA checkpoint transaction list to store in memory at a time
  • Default: 10000
  • Values: Min: 0 / Max: 4294967295

    Note:

    This parameter is not RTC supported.
cfg-sync-start-time
Enter the time in milliseconds before HA Oracle Communications Session Border Controller begins sending HA configuration checkpointing requests. This timer begins immediately upon entering the Active state. As long as the active peer is healthy and active, it remains in a constant cycle of (re)setting this parameter’s timer and checking to see if it has become standby.
  • Default: 5000
  • Values: Min: 0 / Max: 4294967295

    Note:

    This parameter is not RTC supported.
cfg-sync-comp-time
Enter the time in milliseconds the standby Oracle Communications Session Border Controller waits before checkpointing with the active Oracle Communications Session Border Controller to obtain the latest configuration transaction information once the initial checkpointing process is complete.
  • Default: 1000
  • Values: Min: 0 / Max: 4294967295

    Note:

    This parameter is not RTC supported.
gateway-heartbeat-interval
Enter the time in seconds between heartbeats on the front interface gateway. This parameter is applicable until a front interface gateway failure occurs. This parameter applies globally to Oracle Communications Session Border Controllers operating in an HA node, but can be overridden on a network interface-by-network interface basis by the value configured in the gw-heartbeat: heartbeat field of the gw-heartbeat subelement in the network-interface element.
  • Default: 0
  • Values: Min: 0 / Max: 65535

    Note:

    This parameter is not RTC supported.
gateway-heartbeat-retry
Enter the number of front interface gateway heartbeat retries after a front interface gateway failure occurs. The value configured in this field applies globally to Oracle Communications Session Border Controllers operating in HA pair architectures, but can be overridden on a per network interface basis by the value configured in the gw-heartbeat: retry-count field.
  • Default: 0
  • Values: Min: 0 / Max: 65535

    Note:

    This parameter is not RTC supported.
gateway-heartbeat-timeout
Enter the heartbeat retry timeout value in seconds between subsequent ARP requests to establish front interface gateway communication after a front interface gateway failure occurs. The value configured in this field applies globally to Oracle Communications Session Border Controllers operating in HA pair architectures, but can be overridden on a network interface basis by the value configured in the gw-heartbeat: retry-timeout field.
  • Default: 1
  • Values: Min: 0 / Max: 65535

    Note:

    This parameter is not RTC supported.
gateway-heartbeat-health
Enter the health score amount to subtract if the timeout value set in the gateway-heartbeat-timeout field has been exceeded without receiving a response from the front interface gateway. The value configured in this field applies globally to Oracle Communications Session Border Controllers operating in HA nodes, but can be overridden on a network interface basis by the value configured in the gw-heartbeat > health-score field of the gw-heartbeat. A field value of 0 means that the health score is not affected.
  • Default: 0
  • Values: Min: 0 / Max: 100

    Note:

    This parameter is not RTC supported.
media-if-peercheck-time
Enter the amount of time in milliseconds for the standby system in an HA node to receive responses to its ARP requests via the front interface before it takes over the active role from its counterpart. A value of 0 turns the HA front interface keepalive off
  • Default: 0
  • Values: Min: 0 / Max: 500
peers
Access the peers subelement

Path

redundancy is an element under the system path. The full path from the topmost ACLI prompt is: configure terminal , and then system , and then redundancy.

Note:

This is a single instance configuration element.