IMPORTANT:
Before You Begin
IMPORTANT:
Step 1 - Verifying Hardware Status
Step 2 - Setting the WEM Server's Database Environment Strings
Step 4 - Installing the WEM Software
Step 5 - Configuring WEM Client Session Management Parameters
Step 6 - Configuring IP Multipathing (IPMP) on WEM Server (Optional)
Setting the PostgreSQL Database System Environment Configurations
Solaris Servers
Determining the Best Installation Method
Parameter | Description | Default Value |
---|---|---|
System Setting for Postgres | ||
N/A | This dialog or script section is informational and contains no configurable parameters.Information pertaining to these variables is located in the Setting the PostgreSQL Database System Environment Configurations section in this chapter. | N/A |
EMS Installation Mode | ||
Standalone EMSFailover Mode | This dialog or script section determines how the installation will proceed depending on the type of environment the EMS will be running in. Select Failover Mode if you are configuring a redundant High Availability cluster.Future releases will support a Scalable installation mode. | Enabled |
Destination directory for Element Management System | ||
Directory Name | 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.
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.
|
/<ems_dir>/ which is /users/ems by default |
Global Configuration | ||
Select the IP Address | 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. | Null |
Enter the IP Address | 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 serverThe IP address must be entered in the field provided.The IP address specified must be ICMP reachable. | Null |
SSL Configuration | ||
Enforce SSL | 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.If the Enforce SSL option is enabled, the configuration settings for the chassis should be changed as needed. | Enabled |
CFEMS Server Configuration | ||
Content Filtering / Blacklisting Configuration | ||
Enable Content Filtering | This option allows the user to configure the Master Content Rating Database Server (MCRDBS) and Central Decision Point (CDP). By default, this option is enabled. | Enabled |
Enable Blacklisting | Blacklisting is enabled by default. | Enabled |
Blacklisting Configuration | ||
NCMEC Database Configuration: | ||
URL | Enter the cumulative.csv file path at NCMEC. | Null |
User Name | Enter the username required for authentication at the NCMEC site. | Null |
Password | Enter the password required for authentication at the NCMEC site. | Null |
Import interval(Hrs) | Enter the cumulative.csv file import interval in hours. | 24 |
Export to CDP interval(Hrs) | Enter the time interval in hours for Content Filtering Server to export OPTCMDB-BL to CDP. The range is from1 to 5 hours. | 2 |
IWF Database Configuration: | ||
IWF Database Import Path | Provide the path for the IWF database. | Null |
Import Interval | Enter the import interval in hours | 24 |
Master Content Rating Database (MCRDBS): | ||
MCRDBS Host Name | Enter the host name for an MCRDBS server in the field provided. | Null |
MCRDBS Host IP Address | Enter the host IP address of the MCRDBS to which Content Filtering server statistics files are to be sent. | Null |
MCRDBS User Name | Enter a username for the MCRDBS in the field provided. | Null |
MCRDBS Password | Enter a password for the MCRDBS user in the field provided. The password is case sensitive. | Null |
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. | 24 |
Full Database Import Path | Enter the path to locate the SFMDB files in MCRDBS.For example: <Mcrdbs server path>/cfems/<cfems ip address>/sfmdb | Null |
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. | 24 |
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 | Null |
Full Database Backup Limit (number) | Enter the backup limit for full databases. | 4 |
Incremental Database Backup Limit (Days) | Enter the backup limit in days for incremental databases. | 30 |
Archive Database Files | Select 1 if you want to archive the database files. | 1 |
EMS Client Configuration | ||
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. | . |
Fixed Port Range | ||
Fixed Port | 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. | Disabled |
Start Port | 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.Ports 1 to 1024 are reserved and should not be used. | 40000 |
End Port | 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.Ports 1 to 1024 are reserved and should not be used. | 40010 |
Central Decision Point (CDP): | ||
CDP User Name | Enter a username for the CDP in the field provided. | Null |
CDP Password | Enter a password for the CDP user in the field provided. The password is case sensitive. | Null |
CDP Host Name | Enter the CDP host name in the field provided. | Null |
CDP Host IP Address | Enter the host IP address of the CDP to which CDP statistics files are to be sent. | Null |
Optimized Database Export Interval(Hrs) | Enter the time interval in hours for Content Filtering Server to export the OPTCMDB files to CDP. The range is from 2 to 4320 hours. | 72 |
Optimized Incr Database Export Interval(Hrs) | Enter the time interval in hours for Content Filtering Server to export the OPTCMDB incremental files to CDP. The range is from 2 to 720 hours. | 24 |
Optimized Database File Export Path | Enter the path for Content Filtering Server to export the OPTCMDB files to CDP. | Null |
Trap Configuration | Select 1 to enable trap notifications. | 1 |
Apache Server Configuration | ||
Apache Port (HTTP) | 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. | 80 |
Apache Port (HTTPS) | 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.Apache port HTTP and HTTPS both should be different to establish the successful connection between WEM client and WEM server. | 443 |
Administrator Email-ID | Enter an e-mail address for the web server administrator in the field provided. Use the username@domain format. | root@localhost |
EMS Server Configuration | ||
IMG Session Management (ISM): | ||
Corba Communication Port | Enter the TCP port over which CORBA communication occurs with the system in the field provided.This field will not be displayed if the Enforce SSL parameter in the SSL Configuration panel is enabled.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. | 14132 |
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.This field will not be displayed if the Enforce SSL parameter in the SSL Configuration panel is disabled.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. | 14131 |
Application Server ID | Enter the name by which the WEM CORBA application server is identified to the chassis.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. | CISCO |
Application Server Password | Enter the password used by the WEM CORBA application server when communicating with the chassis.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. | Null |
Network Management System (NMS): | ||
FTP User Name | 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. | staradmin |
FTP Password | Enter a password for the FTP user in the field provided. The password is case sensitive. | Null |
User Limit | 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. | 10 |
Security Admin Limit | 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. | 5 |
User Session 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. | 5 |
Context User Limit | 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. | 5 |
FTP Session Limit | 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. | 5 |
Storage Server Directory | Enter the name of the directory in which the WEM database backup files would be stored. | ./flash |
Syslog Config File | Enter the directory path for the syslog configuration file. This is needed for the WEM’s syslog event viewing functionality.If the file is not found in the specified directory, an error message is displayed. | /etc/syslog.conf |
EMS Server Configuration (contd.) | ||
Fault Management (FM): | ||
SNMP Trap Port | 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. | 162 |
SMTP Server Name | 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.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. | Null |
Sender Email-ID | 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.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. | Null |
Bulk Statistics: | ||
Bulkstat FTP User Name | 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. | anonymous |
Bulkstat FTP Password | 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. | Null |
Host IP Address | 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. | 127.0.0.1 |
Host Base Directory | 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. | /tmp |
Archive Bulkstat Files | 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. | Disabled |
Generate XML Files | Select this option if
the server is to create XML files containing processed bulkstatistic
information for forwarding to a remote server.
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.Since the Bulkstat Server
process is responsible for XML file generation, if this option is
not enabled, the Bulkstat Server process is not started. |
Disabled |
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. | Disabled |
User Administration | ||
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. | Null |
Hardware Inventory | ||
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. | Null |
EMS Process Monitor Configuration | ||
Poll Interval (sec) | Enter the frequency at which process table queries are performed. The interval is measured in seconds. | 30 |
Number Of Retries | 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. | 10 |
Timeout Interval (sec) | 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. | 330 |
SMTP Server Name | 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. |
To Email-ID | 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. | Null |
Monitor Process | 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.
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:
EMS Server
Bulkstat Server
Bulkstat Parser
Script Server
Northbound Server |
EMS Server: Enabled Bulkstat Server: Disabled Bulkstat Parser: Enabled Script Server: Disabled Northbound Server: Disabled |
Postgres Configuration | ||
User Name | Enter a username for
the Postgres database administrator in the field provided.
To
ensure proper operation and data integrity, the PostgreSQL database
instances installed with the WEM should only be used by the application.
|
postgres |
Password | Enter a password for the user in the field provided. The password is case sensitive. | Null |
Use Local Installation | Select this option to
install Postgres on the local serverIf enabled, the system's
local IP address of 127.0.0.1 is used.
This option is not
present in the console-based installation script.
|
Enabled |
Use Remote Installation | Select this option to
install Postgres on a remote system.If enabled, configure
the IP address of the server in the field provided.
This option is not
present in the console-based installation script.
|
Disabled |
Element Management System Installation Confirmation | ||
This dialog or script section is informational and contains no configurable parameters. | N/A | |
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.
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:
Apache Server
EMS Processes
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.
|
All components selected |
Startup Script Panel | ||
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.
This must be disabled
if you have a redundant High Availability server cluster. See the
appendices for more information.
|
Enabled |
Starting WEM Server...
WEM Server started.
PID: 1370
Logfile generated as:
./log/SERVER_LOG_20051220_142931/SERVER_LOG
Starting Script Server...
Script Server started.
PID: 1389
Logfile generated as:
./log/SCRIPT_LOG_20051220_142937/SCRIPT_LOG
The following table
lists the processes that are started at installation.
Process | Log File |
---|---|
EMS Server | .server.log |
Script Server | .scriptserver.log |
BulkStat Server | .bulkstatserver.log |
BulkStat Parser Server | .bulkstatparser.log |
Monitor Server (if enabled) | .watchdog.log |
NorthBound Server | .northboundserver.log |
Notification Service | .notifyservicescript.log |
cp uninst /<ems_dir>/_uninst/
cp ems_migrate /<ems_dir>/server/scripts
cp README.ems_migrate /<ems_dir>/server/scripts
IMPORTANT:
./inst -console
A message appears
welcoming you to the WEM installation.
Starting WEM Server...
WEM Server started.
PID: 1370
Logfile generated as:
./log/SERVER_LOG_20051220_142931/SERVER_LOG
Starting Script Server...
Script Server started.
PID: 1389
Logfile generated as:
./log/SCRIPT_LOG_20051220_142937/SCRIPT_LOG
The following table
lists the processes that are started at installation:
Process | Log File |
---|---|
EMS Server | .server.log |
Script Server | .scriptserver.log |
BulkStat Server | .bulkstatserver.log |
BulkStat Parser Server | .bulkstatparser.log |
Monitor Server (if enabled) | .watchdog.log |
NorthBound Server | .northboundserver.log |
Notification Service | .notifyservicescript.log |
cp uninst /<ems_dir>/_uninst/
cp ems_migrate /<ems_dir>/server/scripts
cp README.ems_migrate /<ems_dir>/server/scripts
IMPORTANT:
Configuring IPMP on WEM Server
IMPORTANT:
eeprom local-mac-address?=true
<hostname>-<NIC_1>
netmask <netmask> broadcast+group
<multipath_grp> deprecated -failover standby up
<hostname> is
name of the Host and <NIC_1>
is the network device to be set as Standby.
<multipath_grp>
is Multipath Interface Group name given to the group of network
devices in a multipath configuration.
<netmask> is
the sub-netmask used by network.
<hostname>-<NIC_2>
netmask 255.255.255.0 broadcast+group <multipath_grp>
deprecated -failover up addif <hostname>-active
netmask 255.255.255.0 broadcast+failover up
<hostname> is
name of the Host and <NIC_2>
is the network device to be set as Active.
<multipath_grp>
is Multipath Interface Group name given to the group of network
devices in a multipath configuration.
<multipath_IP_address> <hostname>-active
<test_IP_address_NIC_1> <hostname>-NIC_1
<test_IP_address_NIC_2> <hostname>-NIC_2
multipath_IP_address is
the IP address allocated to a Multipath Interface Group that is
shared between all devices in the group (either by load sharing or Active-Standby).
test_IP_address_NIC_1 is
the IP addresses assigned to <NIC_1>
interface of the multipath group, they do not move but should not
be used for connections in or out of the host.
test_IP_address_NIC_2 is
the IP addresses assigned to <NIC_2>
interface of the multipath group, they do not move but should not
be used for connections in or out of the host.
shutdown -i 6 -g 0 -y
eeprom local-mac-address?=true
<my_address>
netmask + broadcast + group <multipath_grp>
up
<my_address>
is associated with Multipath IP address <multipath_IP_address>
in the /etc/host file.
<multipath_grp>
is Multipath Interface Group name given to the group of network
devices in a multipath configuration.
group <multipath_grp> up
shutdown -i 6 -g 0 -y