> - Downloads
> - Setting Up SAE Communities
> - Related Topics
> - Setting Up SAE Communities (C-Web Interface)
> - Configuration Tasks for Integrating Third-Party Network Devices
> - Configuring the SAE Community Manager
> - Overview of Integrating Network Devices into the SRC Network
> - Logging In Subscribers and Creating Sessions

> # Setting Up SAE Communities

> Tasks to configure SAE communities are:

> - If there is a firewall in the network, configuring the firewall to allow SAE messages through.
> 1. Configuring the SAE Community Manager
> 2. Specifying the Community Manager in the SAE Device Driver

> ## Configuring the SAE Community Manager

> Use the following configuration statements to configure the SAE community manager that manages third-party network 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, sae_mgr is the name of the community manager.
>    `
>    user@host# edit shared sae 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 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 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 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 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 configuration external-interface-features sae_mgr CommunityManager]
>        user@host# show
>        CommunityManager {
>          keepalive-interval 30;
>          threads 5;
>          acquire-timeout 15;
>          blackout-time 30;
>        }

> ## Specifying the Community Manager in the SAE Device Driver

> Use the following configuration statements to specify the community manager in the SAE device driver.

> `
> shared sae configuration driver third-party {
>   sae-community-manager sae-community-manager ;
> }
> `

> To specify the community manager:

> 1. From configuration mode, access the configuration statements for the third-party device driver.
>    `
>    user@host# edit shared sae configuration driver third-party
>    `
> 2. Specify the name of the community manager.
>    `
>    [edit shared sae configuration driver third-party]
>    user@host# set sae-community-manager sae-community-manager
>    `
> 3. (Optional) Verify the configuration of the third-party device driver.

>        [edit shared sae configuration driver third-party]
>        user@host# show
>        sae-community-manager sae_mgr;

> #### Published: 2009-09-15

> Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.