[Contents] [Prev] [Next] [Index] [Report an Error]

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.

Adding Virtual Router Objects

Use the following configuration statements to add a virtual router:



shared network device name virtual-router  name  {
sae-connection [ sae-connection ...]; 
snmp-read-community  snmp-read-community ; 
snmp-write-community  snmp-write-community ; 
scope [ scope ...]; 
tracking-plug-in [ tracking-plug-in ...];
}

To add a virtual router:

From configuration mode, access the configuration statements for virtual routers. You must specify the name of a device with lowercase characters. This sample procedure uses proxy_device as the name of the router object. For third-party devices, use the name default for the virtual router. user@host# edit shared network device proxy_device virtual-router default
Specify the addresses of SAEs that can manage this router. This step is required for the SAE to work with the router. [edit shared network device proxy_device virtual-router default] user@host# set sae-connection [ sae-connection ...]
To specify the active SAE and the redundant SAE, enter an exclamation point (!) after the hostname or IP address of the connected SAE. For example:
[edit shared network device proxy_device virtual-router default] user@host# set sae-connection [sae1! sae2!]
(Optional) Specify an SNMP community name for SNMP read-only operations for this virtual router. [edit shared network device proxy_device virtual-router default] user@host# set snmp-read-community snmp-read-community
(Optional) Specify an SNMP community name for SNMP write operations for this virtual router. [edit shared network device proxy_device virtual-router default] user@host# set snmp-write-community snmp-write-community
(Optional) Specify service scopes assigned to this virtual router. The scopes are available for subscribers connected to this virtual router for selecting customized versions of services. [edit shared network device proxy_device virtual-router default] user@host# set scope [ scope ...]
(Optional) Specify the plug-ins that track interfaces that the SAE manages on this virtual router. [edit shared network device proxy_device virtual-router default] user@host# set tracking-plug-in [ tracking-plug-in ...]

(Optional) Verify your configuration.

[edit shared network device proxy_device virtual-router default] 
user@host# show 
sae-connection 10.8.221.45;
snmp-read-community ********;
snmp-write-community ********;
scope POP-Toronto;
tracking-plug-in flexRadius;

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:

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
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
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
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
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

(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:

From configuration mode, access the configuration statements for the third-party device driver. user@host# edit shared sae configuration driver third-party
Specify the name of the community manager.[edit shared sae configuration driver third-party] user@host# set sae-community-manager sae-community-manager

(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;

[Contents] [Prev] [Next] [Index] [Report an Error]