Select the
following options in the installation wizard:
The default security protocol for the web server is TLSv1.2.
To disable TLSv1.1 and below, see the Cisco Unified Communications Domain Manager 11.5(3) Maintain and Operate Guide for detailed information.
If
fips
mode is selected upon installation, the system is enabled for adherence to
Federal Information Processing Standards (FIPS). If fips mode is not selected
upon installation, it can be enabled from the command line interface using the
system
fips enable command.
The following roles are available:
-
AWebProxy role installs only the front-end web server together with ability to distribute load among multiple middleware nodes.
-
An Application node is the main transaction processing engine and includes a web server which can operate by itself, or route
transactions from a web node.
-
A Database node provides persistent storage of data.
-
A Standalone node consists of the Web, Application and Database roles on a single node.
-
A Unified node consists of the Web, Application and Database roles on a single node. On installation, the system needs to
be clustered with other nodes and the cluster provisioned.
Password
protection can be enabled on the Unified CDM boot loader configuration from
theIinstall Wizard upon first install and also from the CLI. The console
example below shows the output:
(1) ip (199.29.21.89)
(2) netmask (255.255.255.0
(3) gateway (199.29.21.1)
(4) dns (199.29.88.56)
(5) ntp (199.29.88.56)
(6) boot password (disabled)
(7) hostname (atlantic)
(8) role (UNDEFINED)
(9) data centre (earth)
(10) platform password (UNDEFINED)
(11) fips mode (disabled)
Select option ? 6
Valid passwords must contain:
at least one lower- and one upper-case letter,
at least one numeric digit
and a special character eg. !#@$%&^*
Password: Please enter platform user password:
Please re-enter password
Password:
NOTE: The system boot password is now set for user platform.
When the
boot password is set, the wizard will show this:
(6) boot password (*****)
For
multi-node installations, also refer to the topic on Clustering the System.
Detailed configuration can be applied from the Command Line Interface (CLI).
Use
network
help or
network for details. For example, domain can be configured
using
network
domain add <domain-name>. For a geo-redundant deployment, the data
center information is equivalent to the location information.
Once all
details are entered, installation will commence. When installation is complete,
the system will reboot.
Log in to the platform and run the following command from the CLI:
Security
updates that are a part of the installation are installed automatically. For a
system upgrade, however, run
security
update to apply all the latest security updates. A system notification
upon completion will instruct the user to reboot. This should always be done,
because some critical updates on a system layer requires this action to be
completed for the security patches to take affect. For a cluster, if a node
does not properly reboot but the console shows all processes have terminated,
you can manually reboot the node without any system corruption.
The system
is ready for use.
The login message would for example looks the same as the following:
Last login: Wed Nov 2 11:12:45 UTC 2016
from oigumbor-m-thwh.visionoss.int on pts/6
Last failed login: Wed Nov 2 11:19:53 UTC 2016
from riza-dell-laptop.visionoss.int on ssh:notty
There were 2 failed login attempts since the last
successful login.
host: dev-test, role: webproxy,application,database,
load: 0.21, USERS: 3
date: 2016-11-02 11:19:57 +00:00, up: 14:19
network: 172.29.253.14, ntp: 172.29.1.15
HEALTH: NOT MONITORED
database: 31Gb
WEB CERT EXPIRED AT: 2016-01-19 07:58:44
Failed logins: 2 since Wed Nov 02 11:19:53 2016
from riza-dell-laptop.visionoss.int
mail - local mail management
keys - ssh/sftp credentials
network - network management
backup - manage backups
voss - voss management tools
log - manage system logs
database - database management
notify - notifications control
schedule - scheduling commands
selfservice - selfservice management
diag - system diagnostic tools
system - system administration
snmp - snmp configuration
user - manage users
cluster - cluster management
drives - manage disk drives
web - web server management
app - manage applications
security - security update tools
The
application: up message indicates the application status.
If the message is
NOT
PROVISIONED, then for a standalone installation, the
system
provision command can be run. This command, however, runs automatically
during the standalone installation.
If the user
failed to log in prior to a successful login, the count, date and origin of the
attempts are shown as
Failed
logins. A successful login resets this login count.
After
provisioning, if the admin or Self-Service GUI needs to be disabled on the web
proxy nodes for security purposes, run the command on the relevant web proxy
node:
web service disable <selfservice|admin>
If needed,
the web service can be enabled again by:
web service enable <selfservice|admin>
These commands will automatically reconfigure and restart the nginx process, so will include some downtime. Request URLs to
the disabled service will redirect the user to the active service. It is not advisable to run these commands on a standalone
configuration.
Feedback