Configuring the SAE Community Manager

Use the following configuration statements to configure the SAE community manager that manages PCMM device communities:

shared sae configuration external-interface-features name CommunityManager {keepalive-interval keepalive-interval ;
threads threads ;
acquire-timeout acquire-timeout ;
blackout-time blackout-time ;
}

To configure the community manager:

  1. From configuration mode, access the configuration statements for the community manager. In this sample procedure, west_region is the name of the SAE group, and sae_mgr is the name of the community manager.
    user@host# edit shared sae group west-region configuration external-interface-features sae_mgr CommunityManager
  2. Specify the interval between keepalive messages sent from the active SAE to the passive members of the community.
    [edit shared sae group west-region configuration external-interface-features sae_mgr CommunityManager] user@host# set keepalive-interval keepalive-interval
  3. Specify the number of threads that are allocated to manage the community. You generally do not need to change this value.
    [edit shared sae group west-region configuration external-interface-features sae_mgr CommunityManager] user@host# set threads threads
  4. Specify the amount of time an SAE waits for a remote member of the community when it is acquiring a distributed lock. You generally do not need to change this value.
    [edit shared sae group west-region configuration external-interface-features sae_mgr CommunityManager] user@host# set acquire-timeout acquire-timeout
  5. Specify the amount of time that an active SAE must wait after it shuts down before it can try to become the active SAE of the community again.
    [edit shared sae group west-region configuration external-interface-features sae_mgr CommunityManager] user@host# set blackout-time blackout-time
  6. (Optional) Verify the configuration of the SAE community manager.
    [edit shared sae group west-region configuration external-interface-features sae_mgr CommunityManager] 
    user@host# show 
    CommunityManager {
     keepalive-interval 30;
      threads 5;
      acquire-timeout 15;
      blackout-time 30;
    }

Related Documentation