To set up Novell BorderManager 3.7 e-mail notification:
In NetWare® Administrator, locate the object in the NDS® or Novell eDirectoryTM tree where the alert configuration will be specified > right-click the object > select Details.
An alert can be configured only for an Organization (O), Organizational Unit (OU), or Server object.
Click the Novell BorderManager 3.7 Alert page.
Select one of the following notification schemes:
Inherit disables the E-mail Alert and E-mail Servers lists for the selected NDS or eDirectory object. If these lists have been previously configured, the recipients and servers in the lists are deleted after you click OK.
To view the inherited information, click Effective Configuration. The Effective Configuration information is read-only. To change the alert information, identify the NDS or eDirectory container in the Location of Specification field and open the Novell BorderManager 3.7 Alert page from that container's Details page.
(Optional) If you selected Send Alert earlier, specify the alert conditions for which you want notification.
Specify E-mail Alert Recipients and E-mail Servers.
NOTE: The Novell BorderManager 3.7 server must be configured with at least one e-mail server. Otherwise, alert notification will fail.
Click Add for the E-mail Alert field and enter the e-mail address of the person to be notified by Novell BorderManager 3.7 Alert.
Add as many e-mail recipients as necessary. There is no upper limit on the number of recipients that can be added.
(Optional) To remove a recipient from the list, highlight the recipient's e-mail address and click Delete for the E-mail Alert field.
Click Add for the E-mail Server's field and enter the e-mail server name or IP address for the recipients added in Step 5a.
The first server in the list is the primary e-mail server. The primary server receives alert messages and routes them to other e-mail servers on the network, if necessary.
All other servers in the list act as backup e-mail servers if the primary server fails to route the e-mail. This can occur if e-mail forwarding has been disabled on the primary server or if the primary server is down.
Add as many e-mail servers as necessary. Although there is no upper limit on the number of backup servers that can be added, Novell BorderManager 3.7 Alert sends alerts to only one e-mail server on the list.
HINT: To increase the performance of Novell BorderManager 3.7 Alert, enter the IP addresses of e-mail servers. When IP addresses are used, the Novell BorderManager 3.7 server is not required to process Domain Name System (DNS) lookups to resolve the DNS hostnames of e-mail servers.
(Optional) To remove an e-mail server's from the list, highlight the e-mail server name or IP address > click Delete for the E-mail Server field.
(Optional) To change an e-mail server's status as a primary or backup server, click the Up-arrow or Down-arrow to move the e-mail server's name or IP address up or down the list.
Click OK to save the configuration and exit the Details page.
Clicking OK saves the configuration changes in NDS or eDirectory and notifies BRDSRV.NLM that a configuration change has occurred. Alert configurations are updated on each NDS or eDirectory replica during normal NDS or eDirectory synchronization.
If you enabled an alert configuration for an entire organization, it might take a while for all Novell BorderManager 3.7 servers to be notified of the configuration change in NDS or eDirectory.
(Optional) If you enabled an alert configuration for an entire organization and want a specific server to use the alert configuration immediately, rather than after NDS or eDirectory synchronization occurs, complete the following substeps:
Double-click the Server object representing the Novell BorderManager 3.7 server you want to begin using the alert configuration immediately.
From the Server object's Details page, click Novell BorderManager 3.7 Alert to view the Novell BorderManager 3.7 Alert page for the server.
Click Refresh Server.
IMPORTANT: When you first open the Novell BorderManager 3.7 Alert page, the Refresh Server button is available. Clicking Refresh Server causes BRDSRV.NLM to read the new alert configuration for this server only. It does not trigger a full NDS or eDirectory synchronization. If you modify the alert configuration for this Server object, the Refresh Server button is inactive and no longer an option.