| Parameter |
Description |
Default Value |
System Setting for Postgres
|
|
|
This dialog or script
section is informational and contains no configurable parameters.
|
|
|
|
|
|
This dialog or script
section determines how the installation will proceed depending on
the type of environment the EMS will be running in. If you have
a standalone server, please select this mode.
IMPORTANT:
Future releases will
support a Scalable installation mode.
|
|
|
|
If you have High Availability cluster environment,
please select this mode.
|
|
Destination directory
for Element Management System
|
|
|
The directory on the
server in which the WEM is to be installed.
The directory can be
manually entered in the field provided or selected using the Browse
function.
IMPORTANT:
If you are configuring
a High Availability installation using redundant servers in a clustered
environment there are certain requirements regarding identical
setups on both servers. Refer to the appendices for more information before proceeding.
For
Failover mode, enter the global disk path for shared data directory.
This
directory will be used to store certain data files such as bulkstat,
log and so on and will be used as central data point between Cluster
servers.
|
/<ems_dir>/ which
is /users/ems by
default
|
|
|
|
|
Choose this option to
select one of the server IP addresses automatically detected by
the WEM installation process.
For the GUI-based installation,
the IP address is selected from the drop-down menu.
IMPORTANT:
For Cluster Failover mode installation,
always choose the Virtual IP Address configured on the HA.
|
|
|
|
Choose this option to
manually specify an IP address. This option can be used to specify
an address that has not yet been configured on the server
The IP address must be
entered in the field provided.
IMPORTANT:
The IP address specified
must be ICMP reachable.
IMPORTANT:
For
Cluster Failover mode installation, always enter the Virtual IP
Address configured on the HA.
|
|
|
|
|
|
If this option is selected,
then the Secure Sockets Layer (SSL) connection is established for
client-to-server and server-to-boxer communication. By default,
the SSL encryption feature is enabled.
IMPORTANT:
If the Enforce SSL option
is enabled, the configuration settings for the chassis should be
changed as needed.
|
|
| CFEMS Server Configuration |
Content Filtering / Blacklisting
Configuration
|
|
|
This option allows the
user to configure the Master Content Rating Database Server (MCRDBS).
By default, this option is enabled.
|
|
|
|
Blacklisting is enabled
by default.
IMPORTANT:
For North American installations,
support is required for both the IWF and NCMEC blacklisting databases. Users
can enable blacklisting for one or both databases at prompts during
the installation regardless of whether you use the GUI or the command
line for the installation.
|
|
Blacklisting Configuration
|
NCMEC Database Configuration:
|
|
|
Enter
the cumulative.csv file path at NCMEC. |
|
|
|
Enter the username required
for authentication at the NCMEC site.
|
|
|
|
Enter the password required
for authentication at the NCMEC site.
|
|
|
|
Enter the cumulative.csv
file import interval in hours.
|
|
IWF Database Configuration:
|
|
|
Provide the path for
the IWF database.
|
|
|
|
Enter the import interval
in hours
|
|
Master Content Rating
Database (MCRDBS):
|
|
|
Enter
the host name for an MCRDBS server in the field provided. |
|
|
|
Enter the host IP address
of the MCRDBS to which Content Filtering server statistics files
are to be sent.
|
|
|
|
Enter a username for
the MCRDBS in the field provided.
|
|
|
|
Enter a password for
the MCRDBS user in the field provided. The password is case sensitive.
|
|
Full Database Import Interval(Hrs)
|
Enter the time interval
in hours for Content Filtering Server to import various databases
from MCRDBS (Databases: SFMDB). The range is from 2 to 4320 hours.
|
|
Full Database Import Path
|
Enter the path to locate
the SFMDB files in MCRDBS.
For example: <Mcrdbs
server path>/cfems/<cfems ip address>/sfmdb
|
|
Incremental Database
Import Interval(Hrs)
|
Enter the time interval
in hours for Content Filtering Server to import various databases
from MCRDBS (Databases: SFMDB-INC). The range is from 2 to 720 hours.
|
|
Incremental Database
Import Path
|
Enter the path to locate
the SFMDB-INC files in MCRDBS.
For example: <MCRDBS
server path>/cfems/<cfems ip address>/sfmincdb
|
|
Full Database Backup
Limit (number)
|
Enter the backup limit
for full databases.
|
|
Incremental Database Backup
Limit (Days)
|
Enter the backup limit
in days for incremental databases.
|
|
|
|
Select 1 if you want
to archive the database files.
|
|
|
|
WEM Identifier Information
|
If applied at installation
time, this identification information will allow users to know which
particular WEM they are logged into: useful for working with more
than one WEM keeping track of multiple screens. This text would
be saved to the img.html and imgdebug.html files
so each time the user logged in the data would be retrieved and
provide the WEM identifier detail on each screen automatically.
|
. |
|
|
|
|
There are a number of
applications on the WEM that require event notifications such as
graphing, protocol monitoring, Front and Rear view (FRV) screens,
alarms, and software upgrades. Each one requires a dedicated port
for itself.
Select this option if
the WEM Server is to send requests (notifications) to WEM Clients
on fixed ports.
This is useful if a firewall
exists between the Server and the Client. The assigned ports can
be opened in the firewall to allow notifications.
By default, if enabled,
the Server uses a block of 11 ports beginning with the port number
specified in by Start Port. If this option is not enabled, the operating
system randomly selects open ports for use.
|
|
|
|
If the Fixed Port option
is enabled, this parameter specifies the initial port number to
use for the block of consecutive fixed ports.
The port can be configured
to any integer value from 1 through 65535.
IMPORTANT:
Ports 1 to 1024 are reserved
and should not be used.
|
|
|
|
If the Fixed Port option
is enabled, this parameter specifies the last port number to use
for the block of consecutive fixed ports.
The port can be configured
to any integer value from 1 through 65535.
IMPORTANT:
Ports 1 to 1024 are reserved
and should not be used.
|
|
Apache Server Configuration
|
|
|
Enter the TCP port that
the Apache web server communicates on in the field provided. Enter
the port number as an integer, ranging from 0 through 65535.
|
|
|
|
Enter the TCP port that
the Apache web server communicates securely on in the field provided.
Enter the port number as an integer, ranging from 0 through 65535.
IMPORTANT:
Apache port HTTP and
HTTPS both should be different to establish the successful connection
between WEM client and WEM server.
|
|
|
|
Enter an e-mail address
for the web server administrator in the field provided. Use the username@domain format.
|
|
|
|
IMG Session Management
(ISM):
|
|
|
Enter the TCP port over
which CORBA communication occurs with the system in the field provided.
IMPORTANT:
This field will not be
displayed if the Enforce SSL parameter in the SSL Configuration
panel is enabled.
IMPORTANT:
This setting must be
identical to the iiop-port setting on the system. The parameter
entered here is used as a default value by the application. Once
the server installation is complete, a chassis to be managed can
be configured each with their own IMG Port value through the client interface.
Enter this value as an
integer, ranging from 0 to 65535.
|
|
Corba Communication Port
(SSL)
|
Enter the port over which
CORBA communication occurs with the system in the field provided.
The corba communication port is configured same as the SSL port
on the boxer.
IMPORTANT:
This field will not be
displayed if the Enforce SSL parameter in the SSL Configuration
panel is disabled.
IMPORTANT:
This setting must be identical
to the siop-port setting on the chassis. The parameter entered here
is used as a default value by the application. Once the server installation
is complete, additional Chassis to be managed can be configured
with unique Port values through via the WEM client interface.
Enter this value as an
integer, ranging from 0 to 65535.
|
|
|
|
Enter the name by which
the WEM CORBA application server is identified to the chassis.
IMPORTANT:
This name must match the Application
Server ID name configured on the chassis for WEM to be able to manage
the system. The Application Server ID name entered here is used
as a default value by the application. Once the server installation
is complete, additional Chassis to be managed can be configured
with unique Application Server ID names via the WEM client interface.
|
|
Application Server Password
|
Enter the password used
by the WEM CORBA application server when communicating with the
chassis.
IMPORTANT:
This password must match the Application
Server Password configured on the chassis for WEM to be able to
manage the system. The password entered here is used as a default
value by the application. Once the server installation is complete,
additional Chassis to be managed can be configured with unique passwords
via the WEM client interface.
|
|
Network Management System
(NMS):
|
|
|
Enter a name for the
WEM user with FTP privileges on the chassis in the field provided.
For FTP to work properly
between the WEM server and any chassis, an administrator user with
FTP privileges must be configured through the system’s
CLI. It is highly recommended that this CLI administrator be configured
using the “nocli” option, allowing only FTP privileges
into the system.
If the WEM server is
to manage multiple chassis, then this same CLI user must be configured
on each of the chassis.
|
|
|
|
Enter a password for
the FTP user in the field provided. The password is case sensitive.
|
|
|
|
Enter the maximum number
of WEM users that can simultaneously access the server.
The number can be configured
to any integer value from 1 through 100.
|
|
|
|
Enter the maximum number
of WEM users with Security Administrator privileges
that can simultaneously access the server.
The number can be configured
to any integer value from 1 to the number specified as the User Limit.
|
|
|
|
Enter the maximum number
of sessions allowed for a single WEM user.
The number can be configured
to any integer value from 0 to the number specified as the User Limit. A value
of 0 disables the implementation of user limits on a per-context
basis.
|
|
|
|
Enter the maximum number
of Web Element Management user sessions allowed on a per-system
context basis.
The number can be configured
to any integer value from 0 to the number specified as the User Limit. A value
of 0 disables the implementation of user limits on a per-context
basis.
|
|
|
|
Enter the maximum number
of simultaneous FTP sessions allowed to the chassis through the
WEM.
The number can be configured
to any integer value from 1 through 20.
|
|
|
|
Enter the name of the
directory in which the WEM database backup files would be stored.
|
|
|
|
Enter the directory path
for the syslog configuration file. This is needed for the WEM’s
syslog event viewing functionality.
IMPORTANT:
If the file is not found
in the specified directory, an error message is displayed.
|
|
EMS Server Configuration
(contd.)
|
|
|
|
|
Enter the TCP port over
which SNMP traps are received from the system in the field provided.
Enter this value as an integer, ranging from 0 to 65535.
|
|
|
|
Enter a host name or
IP address for a Simple Mail Transfer Protocol (SMTP) server, if
needed, in the field provided.
This is the mail server
to which notifications are sent.
IMPORTANT:
This parameter must be
configured in order to send e-mails to new users when a trap is
generated. E-mail can be configured for a trap in Alarm Configuration
screen. 'SMTP Server name' is used as the E-mail Server for those mails.
|
|
|
|
Configure the e-mail
address to which the system is to send notifications in the field
provided. The e-mail address should be in the form username@domain.
IMPORTANT:
This parameter must be
configured in order to send e-mails to new users when a trap is
generated. E-mail can be configured for a trap in Alarm Configuration
screen. 'Sender E-mail ID' is used as the 'From' (Originator) for
those mails.
|
|
|
|
|
|
Enter the name of the
user with FTP privileges on the external network management server.
This parameter is used
in conjunction with the Bulkstat
FTP Perform Operation parameter.
|
|
|
|
Enter the password of
the user with FTP privileges on the external network management
server.
This parameter is used
in conjunction with the Bulkstat
FTP User Name parameter.
|
|
|
|
Enter the IP address
of the external network management server to which XML-parsed bulkstatistic
files are to be sent.
This parameter is used
in conjunction with the Bulkstat
FTP Perform Operation parameter.
|
|
|
|
Enter the directory on
the external network management server to which the bulkstatistic
files are to be written. The default directory is /tmp.
This parameter is used
in conjunction with the Bulkstat
FTP Perform Operation parameter.
|
|
|
|
Select this option if
the WEM is to archive bulkstatistic information from the chassis.
Archived data is stored
to the /<ems_dir>/server/bulkstat_archive directory
by default.
|
|
|
|
Select this option if
the server is to create XML files containing processed bulkstatistic
information for forwarding to a remote server.
IMPORTANT:
This option must be checked
if you are installing on a server running RHEL O/S otherwise
the installation will fail with the following message: "X connection
to localhost:10.0 broken (explicit kill or server shutdown)."
XML-parsed data is stored
in the /<ems_dir>/server/xmldata directory
by default.
IMPORTANT:
Since the Bulkstat Server
process is responsible for XML file generation, if this option is
not enabled, the Bulkstat Server process is not started.
|
|
Bulkstat FTP Perform Operation
|
Select this option if
the server is to transfer XML-parsed bulkstatistic data files to
an external network management server.
Bulkstatistic information
retrieved from the chassis via FTP is stored in the /<ems_dir>/server/data directory
by default prior to processing.
|
|
|
|
EMS Administrator E-Mail Address
|
Enter an e-mail ID to
be used as the originator for e-mails generated during new user
account creation or password resets.
|
|
|
|
Hardware Notifier Email-ID
|
Enter an e-mail ID to
be used as the originator for e-mails generated as a result of a
hardware change.
|
|
EMS Process Monitor Configuration
|
|
|
Enter the frequency at
which process table queries are performed. The interval is measured
in seconds.
|
|
|
|
Configure the number
of times the system attempts to communicate with a process prior
to taking action.
If the process has not
responded to the final attempt within the configured timeout interval,
the system considers it unreachable and takes action.
|
|
|
|
Configure the amount
of time the system should wait prior to re-attempting to communicate
with an un-responsive process in the field provided. The interval
is measured in seconds.
Once the time interval
has been reached, the system re-attempts communication for the configured
number of retries prior to considering the process unreachable and
taking action.
|
|
|
|
Enter a host name or
IP address for a Simple Mail Transfer Protocol (SMTP) server, if
needed, in the field provided.
This is the mail server
to which notifications are sent when processes fail/start.
|
Takes setting from previous
SMTP parameter.
|
|
|
Configure the e-mail
address of the individual to be notified in the field provided.
E-mail notifications are sent to this individual when the system
cannot communicate with a process. The e-mail address should be in
the form username@domain.
|
|
|
|
EMS Process Monitor functionality
is capable of monitoring WEM server processes at pre-configured
intervals. In the event of a process becoming unresponsive, the
system sends notifications and can re-spawn the process. Refer to
the WEM Process Monitor chapter
for additional information.
IMPORTANT:
Special rules apply
to starting processes that will update dateabases whenever you are
installing redundant WEM servers using clustering software. Refer
to the appendices for more information before starting database processes.
The following processes
can be monitored:
|
Bulkstat Server: Disabled
Northbound
Server: Disabled
|
|
|
|
|
Enter a username for
the Postgres database administrator in the field provided.
CAUTION:
To
ensure proper operation and data integrity, the PostgreSQL database
instances installed with the WEM should only be used by the application.
|
|
|
|
Enter a password for
the user in the field provided. The password is case sensitive.
|
|
|
|
Select this option to
install Postgres on the local server
If enabled, the system's
local IP address of 127.0.0.1 is used.
IMPORTANT:
This option is not
present in the console-based installation script.
|
|
|
|
Select this option to
install Postgres on a remote system.
If enabled, configure
the IP address of the server in the field provided.
IMPORTANT:
This option is not
present in the console-based installation script.
|
|
Element Management System
Installation Confirmation
|
|
|
This dialog or script
section is informational and contains no configurable parameters.
|
|
Component Starting Panel
(Select the components to be started)
|
Select the components
to be started
|
Select the WEM software
components to start as part of the installation.
IMPORTANT:
Special rules apply
to starting services and databases when you install redundant WEM
servers using clustering software. Refer to the appendices for more information before continuing.
The following components
are available:
IMPORTANT:
Successful installation
of the WEM application requires that the Apache Server and EMS processes
be started. The default setting is to enable them. Though prompts
are provided to disable them, it is highly recommended that you do
not modify the default behavior.
|
|
|
|
Start EMS at machine startup
|
Select this option to
enable the WEM to start automatically each time the server on which
it is installed is rebooted.
IMPORTANT:
This must be disabled
if you have a redundant High Availability server cluster. See the
appendices for more information.
|
|