Escolar Documentos
Profissional Documentos
Cultura Documentos
Guide
Document id: DNA-M-ServerAdmin
Warning
This is a class A product. In a domestic environment this product may cause radio interference in which case the user
may be required to take adequate measures.
FDA
This product complies with the DHHS Rules 21CFR 1040.10 and 1040.11, except for deviations pursuant to Laser
Notice No. 50, dated June 24, 2007.
Contents
1. System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1. Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.1. Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.2. Complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.3. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.4. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.5. Disk space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.6. Virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Client workstation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4. DCN Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. MariaDB database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1. Assumptions and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2. MariaDB Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.1. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.2. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3. MariaDB Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3.1. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3.2. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4. MariaDB configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4.1. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4.2. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3. Setting up the DNA-M Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1. Managing users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1.1. Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1.2. User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.3. Assigning user groups to user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.4. Display Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2. NTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3. DNA-M Server Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3.1. Available DNA-M server preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3.2. DNA-M Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3.3. DNA-M PM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3.4. DNA-M PCE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.5. DNA-M WS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.6. DNA-M Webstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.7. DNA-M Web Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.4. Adjustments for large DNA-M Server installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.4.1. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.4.2. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.5. DNA-M Server GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.5.1. TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.5.2. Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.5.3. Node Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.5.4. SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.5.5. RADIUS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.5.6. Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.5.7. Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5.8. Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.5.9. PM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.5.10. Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.5.11. Alarm Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.5.12. External Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.5.13. Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.5.14. Server Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4. Maintaining DNA-M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.1. Server Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2. Server logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2.1. Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.2.2. Logging configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.2.3. Retrieving log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3. DNA-M Server Startup and Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3.1. Command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3.2. DNA-M Server GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.4. Upgrading the license file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.5. Upgrading the DNA-M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.6. Preparation for upgrade analysis of the XTM nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5. Scalability options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.1. Stand-alone PM server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2. Dedicated database host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2.1. Database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2.2. DNA-M Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6. Backup Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1. Synchronization and backup methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.1. Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.2. Hot standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.3. Script-based cold standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.2. Setting up a cold standby script-based backup server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2.1. Server Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2.2. Configuration of the primary server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2.3. Configuration of the secondary server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2.4. Backing up the primary server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.2.5. Transfer backup of primary server to secondary server . . . . . . . . . . . . . . . . . . . . . . . . 47
6.2.6. Automating the synchronization process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.3. Change server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.3.1. Synchronize servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.3.2. Change automated scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.3.3. Switching primary and secondary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7. Firewall configuration for DNA-M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8. Internationalization support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1. Configuration of Japanese Locale Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1.1. RedHat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.1.2. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.2. MariaDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.3. DNA-M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.3.1. DNA-M Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.3.2. DNA-M Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
9. Red Hat Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.1. User level configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.2. Network buffer sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.3. Congestion control using Westwood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.4. ARP cache parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
1. System Requirements
1. System Requirements
1.1. Server Requirements
Table 1. Supported Operating Systems
Linux Windows
Red Hat Enterprise (RHEL) 6.6 x86-64 Windows Server 2008 R2 64-bit
Red Hat Enterprise (RHEL) 7.1 x86-64 Windows Server 2012 R2 64-bit
Hardware requirements and recommendations vary based on size and complexity of the
transmission network.
1.1.1. Size
Scaling the network size by increasing the number of active network elements (NE) taxes the DNA-
M Server with a larger memory footprint. Internal testing with a large number of NEs, each having an
average of 12 traffic interfaces, show a marginal memory consumption of approximately 5 MB per
NE (additional consumption for all other subsystems not included). For the network size
classification in the table below we assume network elements (NE) with 12 interfaces on average.
1.1.2. Complexity
The number of NEs is only one aspect of DNA-M’s system requirements. Another aspect is the
topological complexity of the transmission network which is harder to quantify. The memory
consumption mentioned above is based on a network model with a simple linear topology (point-to-
point links). Introducing more complex topological structures like rings or mesh layouts will
significantly increase DNA-M’s memory and CPU usage on the system. In general the expected
system load is highly dependent on the number of possible paths between any two points in the
network (on all layers). As a rule of thumb: If the network is ROADM switched it should be
classified as "Large" or "Xlarge" irrespective the number of NEs. Up to 10000 NEs are
supported in a network with a reasonably mixed complexity, for example 6000 TM nodes and
4000 EDU nodes.
1.1.3. Windows
The host machine onto which you intend to install the DNA-M Server must meet the following
requirements:
RAM 8 GB
1.1.4. Linux
The host machine onto which you intend to install the DNA-M Server must meet the following
requirements:
RAM 16 GB
RAM 32 GB
1.1.6. Virtualization
The current version of the DNA-M system has been tested on some Linux-based virtualization
technologies. There is no technical reason for the DNA-M server being unable to operate correctly
on a virtual machine as long as the size and resource recommendations described above are
followed. Make sure that the necessary system resources are made available to the virtual machine.
The above system requirements apply to the specifications of the virtual machine not the virtual
host/hypervisor.
Memory 4 GB
1.3. Limitations
Table 7. Limitations
Number of simultaneously connected DNA-M clients 50
The size of an upgrade file is about 10-30 MB. The figure below illustrates the time to perform a SW
upgrade to a node as a function of the DCN bandwidth. It can be seen that the time to download a
20MB file in one hour requires a DCN bandwidth of about 50 Kbps (uncontended).
Figure 1. Theoretical time take to download a 20MB file as a function of the DCN bandwidth
2. MariaDB database
Infinera, and this documentation, supports any MariaDB 10.x version, when downloading from the
official MariaDB site, we recommend to download latest stable 10.x available
DNA-M uses MariaDB as the default database. MariaDB is a fork of the original
MySQL application, fully compatible with MySQL, and commands, most
directories and settings are still named mysql. A database created with a previous
MySQL installation can be used with MariaDB with no changes to the actual
database, as long as the upgrade instructions in this guide are followed.
2.2.2. Windows
The DNA-M Server requires a MariaDB server to run. Instructions on how to install the latest stable
version can be found at https://mariadb.com/kb/en/mariadb/installing-mariadb-msi-packages-on-
windows/
should be executed each time you upgrade to a new MariaDB version. The script
checks all tables in all databases for incompatibilities with the current version of
MariaDB Server and upgrades the system tables.
2.3.1. Linux
The DNA-M Server requires a MariaDB server to run and instructions on how to install the latest
stable version can be found at https://mariadb.com/kb/en/mariadb/upgrading-from-mysql-to-mariadb/
2.3.2. Windows
The DNA-M Server requires a MariaDB server to run. Instructions on how to install the latest stable
version can be found at https://mariadb.com/kb/en/upgrading-mariadb-on-windows/
2.4.1. Linux
Recommended configuration (my.cnf):
[mysqld]
# Path to installation directory. All paths are usually resolved relative to this.
# basedir = /opt/mysql
#================================================================
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections = 300
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
table_open_cache = 300
# The maximum size of a query packet the server can handle as well as
# maximum query size server can process
max_allowed_packet = 16M
query_cache_size = 0
#================================================================
#*** INNODB Specific options ***
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# Enable multiple tablespaces (i.e. store each InnoDB table and its indexes
# in its own file) to prevent the file ibdata1 from growing.
innodb_file_per_table
#================================================================
# MySQL Slow Query Log
#slow_query_log=1
#long_query_time=1
#slow_query_log_file=/var/lib/mysql/mysql_slow.log
#log-queries-not-using-indexes
#================================================================
# General Query Log
#general-log
#general-log-file=/var/lib/mysql/general.log
#log-output=file
#================================================================
[mysqldump]
quick
max_allowed_packet = 32M
#================================================================
[mysql]
no-auto-rehash
#================================================================
Manual steps:
SELECT ENGINE,
SUM(DATA_LENGTH + INDEX_LENGTH)/1024/1024 "Engine Size [MB]",
COUNT(ENGINE) FROM information_schema.TABLES t
WHERE t.TABLE_SCHEMA NOT IN ('information_schema','mysql') AND
t.table_schema='tnmdb' GROUP BY ENGINE ORDER BY ENGINE ASC;
Output example:
+--------+------------------+---------------+
| ENGINE | Engine Size [MB] | COUNT(ENGINE) |
+--------+------------------+---------------+
| InnoDB | 3689.84375000 | 52 |
+--------+------------------+---------------+
2.4.2. Windows
Recommended configuration (my.ini)
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
[mysqld]
# Path to installation directory. All paths are usually resolved relative to this.
#basedir = "C:/Program Files/MySQL/MySQL Server 5.5/"
# Example:
# Change the path if a custom data directory is being used.
# datadir = "D:/db"
#================================================================
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections = 200
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
table_cache = 300
# The maximum size of a query packet the server can handle as well as
# maximum query size server can process
max_allowed_packet = 16M
query_cache_size = 0
#================================================================
#*** INNODB Specific options ***
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size = 2G
# Enable multiple tablespaces (i.e. store each InnoDB table and its indexes
# in its own file) to prevent the file ibdata1 from growing.
innodb_file_per_table
#================================================================
[mysqldump]
quick
max_allowed_packet = 32M
#================================================================
[mysql]
no-auto-rehash
#================================================================
Manual steps:
SELECT ENGINE,
SUM(DATA_LENGTH + INDEX_LENGTH)/1024/1024 "Engine Size [MB]",
COUNT(ENGINE) FROM information_schema.TABLES t
WHERE t.TABLE_SCHEMA NOT IN ('information_schema','mysql') AND
t.table_schema='tnmdb' GROUP BY ENGINE ORDER BY ENGINE ASC;
Output example:
+--------+------------------+---------------+
| ENGINE | Engine Size [MB] | COUNT(ENGINE) |
+--------+------------------+---------------+
| InnoDB | 3689.84375000 | 52 |
+--------+------------------+---------------+
3.1.1. Users
Open the dialog box in File > Users. Three types of users can be defined:
Admin Admin The administrator may perform all DNA-M operations including
modifying user data
Operator Operator The operator may perform all DNA-M operations except modifying
user data
Readonly Readonly May access all DNA-M functions but is not allowed to modify any
data
It is strongly recommended that the default passwords are changed since all
Infinera DNA-M systems are delivered with the same default settings.
To add a user, click Add, select the desired user type and enter the user name and password.
Figure 2. User
To delete a user, select the user and click Delete. All users except the admin user can be deleted.
RADIUS may be used in the DNA-M Server to take advantage of centralized user
authentication.
Refer to RADIUS client.
To enable the access profiles feature the User groups option should be selected
in File > Users menu in the DNA-M Server GUI.
To create a user group, click on File > Users groups > Add. Give a name and description for that
user group and choose the access control objects and entries that the group should have access to.
To enable a user group, the Enabled checkbox also needs to be checked.
Subnets:
A user group define read or read-write access to one, several or all subnets.
• Read access
• Only view subnet details
• Write access
• Add or delete nodes in subnet
• Add or delete subnets in the subnet
• Delete the subnet
Managed Elements:
A user group define read or read-write access to one, several or all managed elements.
• Read access
• Only view details of the managed element
• Write access
• Delete the managed element
Configuration operations listed for access control for each managed element
List of Services:
A user group define write access to one, several or all services
• Read access
• Requires read access to both A-end node and Z-end node of the service
• Write access
• Perform corresponding operations on the service
• Requires write access to all nodes in the service
An admin user is devoid of access profiles and no user groups will affect its
access rights
To assign users to a user group, click on *File > Users. Select the user that needs to be assigned to
a user group and click Edit. A user can be assigned several user groups, and the rights granted will
be a combination of the highest possible access rights.
DNA-M Server by editing some parameters in the configuration file, described in the following
sections.
Changing the name of the main server in server.conf will only have effect on the
management domain name (MD name) if it is done before a fresh install of the
DNA-M Server.
Server configuration is done in server.conf, and in order for changes made to take effect the server
needs to be restarted.
For instance, to change the name of the DNA-M Server that is displayed during client login, edit the
following lines in the tnmserver section:
In Windows, the configuration text files cannot be edited with Notepad. Please
use an editor capable of handling UNIX style new lines (for example WordPad).
Make sure the changed files are saved in the appropriate format. No tabs are
allowed in the configuration file, only spaces may be used.
db.jdbcUser db.jdbcPassword
Changing the name of the main server in server.conf will only have effect on the
management domain name (MD name) if it is done before a fresh install of the
DNA-M Server.
main.neSetTrapAddress Whether server sets the nodes trap destination address, possible
values: true,false
main.neTrapAddress Address to configured in nodes (SNMP sink address) for sending traps
to the server
rmi.firstport First port number for Java RMI export. If set to 0 an system assigned
anonymous will be used
javavm.java.rmi.server.hostname If NAT is used, address to reach the server outside the NAT
javavm.java.rmi.server.hostname If NAT is used, address to reach the server from outside the NAT
client.heapsize Allocated memory (Java heap size) for the webstarted client, default:
1024m
main.rmi.registry.port Port for the DNA-M server´s Java RMI registry, default: 1099
cli.path.windows Path to default application for opening node CLI on Windows client
web.path.windows Path to default browser application for opening node web GUI and User
Guide on Windows client
cli.path.linux Path to default application for opening node CLI on Linux client
web.path.linux Path to default browser application for opening node web GUI and User
Guide on Linux client
server.port Port for accessing the web apps from a browser, default: 8081
server.ssl.key-alias Alias that identifies the key in the key store, default: server
server.ssl.key-store Path to the key store that holds the SSL certificate (typically a jks file),
default: keystore
dna.mtosi.url URL to the DNA MTOSI web services interface, format: http://<IP-
address>:<port>/mtosi. Specifying a URL will make the Alarm web app
retrieve the active alarms from the DNA server, which is required when
DNA and DNA-M are integrated, otherwise the alarms will be retrieved
from the DNA-M server only.
Before adjusting the size of the memory heap space make sure that your host can
manage large networks.
3.4.1. Windows
Configuring of the Java Virtual Machine (JVM) memory settings is done in the .ini configuration files
for each individual application, by default located in C:\Program
Files\transmode\tnm\<application_name>\bin
Specify vm.heapsize.preferred to your desired value, e.g:
vm.heapsize.preferred=2048m.
3.4.2. Linux
Configuring of the Java Virtual Machine (JVM) memory settings is done in the sysconfig
configuration file, /etc/sysconfig/tnmserver. Recommended configuration:3.5.2.1 DNA-M Server
Specify variables at the top to your desired values
For networks up to 2000 nodes, we recommend setting the initial and maximum heap size to
16GB and the size of the young generation space to 2GB.
MAIN_INITHEAP=16G
MAIN_MAXHEAP=16G
MAIN_NEWSIZE=2G
For up to 4000 nodes, use a heap size of 42G, and young generation of 4G.
MAIN_INITHEAP=42G
MAIN_MAXHEAP=42G
MAIN_NEWSIZE=4G
For up to 10000 nodes, use heap size of 64G, and young generation of 4G.
MAIN_INITHEAP=64G
MAIN_MAXHEAP=64G
MAIN_NEWSIZE=4G
PM_MAXHEAP=1G
WS_MAXHEAP=2G
PCE_MAXHEAP=2G
DNA-M Server settings can be changed in the Options menu in the DNA-M Server GUI
TFTP root directory Root directory for the TFTP server (configured in server.conf)
The TFTP server allows write requests only to the selected destination directory,
Upload. Using the embedded TFTP server requires write access for user starting
DNA-M.
3.5.2. Logs
All records exceeding the log limits will be deleted each hour and upon
configuration changes of upon values
3.5.2.2. Syslog
DNA-M supports sending events (e.g. set operations) and node configuration changes to remote
Syslog server.
The tab for EDU nodes contains list of accepted EDU firmware versions. To use
EDU firmware released before upcoming DNA-M release it can be added in this
section in order for DNA-M to accept nodes running this new firmware.
Contact Infinera customer service at http://www.infinera.com before doing so
Alarm event log size Size of alarm events log. Each alarm change generates one event.
Typically an alarm will generate two events; one when the alarm is
raised and one when the alarm is cleared.
Set agent-addr to orig.addr Enables setting of original IP address in notifications sent by agent
Alarm filter Active alarm filter for SNMP agent, alarms matching filter is not export
by SNMP agent
Heartbeat interval Interval in minutes for SNMP heartbeat trap feature (value of 0 disables
heartbeat)
Trap type SNMP version for the notifications (v1 traps or v2c notifications)
Refer to DNA-M Northbound Interfaces for details on trap contents and supported MIBs.
Refer to Alarm Overview for detailed information about alarms for the TM 3000 Series.
The login attempt is denied if any of the RADIUS servers reject the authentication
request. If the primary server rejects the authentication request the secondary
server is not used even if enabled. If both RADIUS servers are unreachable the
DNA-M servers own user database is used.
3.5.6. Alarms
DNA-M supports auto-acknowledgement and layered alarm, and these are configured under
Options > Alarms
Name Description
Active alarms clear time-out Minimum time for alarm to remain cleared to leave active state
Enable Trail and Network Connection Enables Trail and Network Connection alarms
alarms
Enable Trail and Network Connection Enables Trail and Network Connection alarm filtering and customize its
alarm filtering severity levels
Trail and Network Connection alarm filtering will be run for each matching alarm
and enabling this may cause a large number of processes to be started which
may degrade the DNA-M server performance
Alarm Severity Assignment allows the user to customize severity of a given OID.
The customized severity will be shown in DNA-M Client and northbound export, both via Web
Services and SNMP agent
For example, if the first row of the table contains an OID 1.3.6.1.4.1.8708.2.1.2.7.11 with an
assigned alarm severity as Critical, and the second row contains an OID 1.3.6.1.4.1.8708.2.1.2.7
with an assigned severity as Major, the alarms that matches the first row will be of severity Critical
and all other alarms that starts with the OID as in the second row will be of the severity Major.
If the second row is moved up and made the first row using the Move Up button, all the alarms that
starts with the OID 1.3.6.1.4.1.8708.2.1.2.7 as in the first row will be of severity Major, including the
OID 1.3.6.1.4.1.8708.2.1.2.7.11 since it is a child of the first row. By using Move Up for a parent
alarm, all the child alarms that are found after the parent in the assignment table will be assigned the
parent’s severity. By using Move Up for a child alarm, to bring it above the parent alarm, the child
alarm will retain its original assigned alarm severity. Move Down works in the opposite way of that of
the example given above. By using Move Down of a child alarm, bringing it below a parent alarm,
the child alarm will be assigned the parent’s severity. By using Move Down on a parent alarm, to
move it below a child alarm, the child alarm will be assigned its original alarm severity. The following
fields are associated with the above operations of Alarm Severity:
be a part of one of the predefined OIDs from this list. For instance the OID
1.3.6.1.4.1.8708.2.1.2.5.2 filters the "Test of quality of service type warning
alarm". To change the severity of all test alarms it is enough to enter the string
1.3.6.1.4.1.8708.2.1.2.5
It is recommended to log-out from the client and log-in again after setting the
alarm severity assignment in the server gui.
difference between measured loss and a saved reference value exceeds a threshold. The reference
value is saved using Amplifier View in Transmission Control
Poll Interval Poll interval between each link loss measurement, range between 15
minutes to 7 days specified in minutes, hours or days with m,h or d
without
The size of the Poll interval should reflect what kind of link loss measurement
that is wanted. For measuring fiber aging, a poll interval of 24h or larger is
recommended. If fiber intrusion measurement is wanted, an interval of 15min is
recommended.
3.5.7. Users
Configuring user defaults for new users and RADIUS authenticated users is done in Options >
Users
Disable user after failed login attempts Enables disabling of user after given failed login attempts
Failed login attempts limit Limit for number of failed login attempts, before user is disabled
Enable user and reset password Enables and resets disabled user
Default - object positions locked on GUI Enables object positions lock, at every login. User have to disable lock
map to move objects
3.5.8. Upload
Upload configuration is done in Options > Upload
DNA-M server destination directory Destination directory of DNA-M server where upload configurations is
stored
Upload to TFTP server Enables configuration of upload time, TFTP server and TFTP server
destination directory in TM node
Upload to DNA-M server Enables upload of node configuration (TS series release 17.0 and later)
Cross-Connect backup hour Hour for automatic cross-connect backup for ROADM boards
3.5.9. PM Server
Configuration of Performance Management is done in Options > PM Server
EDU to EMXP services - MEG name is Indicates that MEG names are uniquely defined for each EDU service
unique for each service (required for outside-traffic PM measurements)
If the PM server is stopped while the EDUs keep transferring their PM report files
to the PM server, a significant number of files will be stored in the edufiles
directory. There is no limitation on how many files that can be stored in the
edufiles directory, hence there is a risk that the disc may be filled over time unless
there is a cron job or other service clearing the edufiles directory from
unprocessed files. An additional safety would be to configure the edufiles
directory on a separate partition that has a size limit not to put the PM and DNA-M
server at risk.
Max. notification queue size Maximum number of notifications in queue for notification consumer,
oldest notifications will be discarded
Notification basic auth. user Notification user name in superior OSS system
Enable GCT for Administrators Enables GuiCutThrough login for admin users
Disable suppression of TL equiv. route Disabling export Topological Links with same name
SyncGEM server address Address of SyncGEM server from which DNA-M will receive alarm
notifications
3.5.13. Browser
Configuration of DNA-M´s handling of the System´s browser, when accessing ENM is done in
Options > Browser
User name and password Access ENM using default account in nodes (Node properties) or in
DNA-M (DNA-M user)
To use DNA-M account option, the account with the appropiate user rights must
be specified in the nodes. The user type readonly does not support auto-login
4. Maintaining DNA-M
This section describes how to maintain the DNA-M Server
Status menu in DNA-M Server GUI provides information about DNA-M status.
Nodes Node related information such as IP-address, name, node family and
status of the node
The DNA-M Server will detect the configuration change automatically, and does NOT need to be
restarted. It can take up to two minutes for the change to take effect.
Additionally, the log file size and the log file rotation behavior can be controlled through the logging
configuration files.
Check the logback.xml directly for more information.
When performing a restart of the DNA-M Server all connected DNA-M Client
users will be logged out.
4.3.1.1. Linux
Start
Shutdown
Status
Stopping separate servers is not supported via service, instead use DNA-M
Server GUI, or kill the process by using the process ID
4.3.1.2. Windows
Start
Shutdown
DNA-M GUI provides a more safe and controllable shutting down of DNA-M
Server, PM and/or WS server. Hence It is recommended to use the DNA-M
Server GUI to shut down any of the three servers already mentioned
Start the DNA-M Server by selecting Control > Start. The DNA-M Server will be up and running
when the Server status field in the lower right corner shows Up on a green background.
To stop the DNA-M Server, select Control > Stop. The DNA-M Server will be stopped when the
Server status field in the lower right corner shows Down on a red background.
If any module gets the status Warning displayed on a yellow background after
server startup, control the corresponding log file, see Server Logging
• /etc/tnm/upgrade_impact_resources/json/release on Linux
• C:\Program Files\transmode\tnm\conf\upgrade_impact_resources\json\release on Windows
5. Scalability options
There are two options to increase the size of the network that the DNA-M Server can manage.
Dedicated database host Retains a centralized server architecture but allows MariaDB database
server to run in separate host to decrease overall load on the DNA-M
Server
1. Install and configure the MariaDB database server on the dedicated host according to MariaDB
2. Initialize the database according to DNA-M Installation Guide for Windows or DNA-M Installation
Guide for Linux
3. Login into MariaDB
mysql -uroot -p
4. Grant remote access to database, with <tnmhost> replaced by hostname or IP address of DNA-M
address
The password d4NaZ9j3k has to be entered literally for the DNA-M server
processes to operate correctly.
• Uncomment, and replace localhost in server.conf with the address of your dedicated host
#db.host: <tnmhost>
Script-based cold standby configuration Backs up database and node files at pre-determined intervals
6.1.1. Replication
The update of the database from the primary server (master) to the backup server (slave) is
continuous. The back-up DNA-M server cannot run at the same time as the main DNA-M server, but
the back-up host and database must be running. Replication does not include back-up of node
configurations that are stored on the primary server. Back-ups of node configurations may be
transferred between the primary and back-up server using scripts. If needed, switching between the
master and slave server is done manually. Information about database replication can be found in
the replication manual, Database Replication Guide for Linux and Windows.
It is recommended to perform this synchronization every 24 hours. The backup DNA-M server is
started manually if the primary DNA-M server fails. This is the recommended configuration, because
it requires less management traffic to the NEs. A setup of this kind is described in the following
steps.
To be able to run the secondary server after a restore operation without any need for handson
configuration, the parameters for SNMP agent address and the TFTP server address must be set in
the server.conf file on each host
For back-up purposes, the two hosts must be run simultaneously. The upload
function must have identical configuration on both the DNA-M server and, if
applicable, the separate PM server. Also, all changes done to the secondary
server will disappear after the next synchronization.
To avoid any truncation problems, when restoring the secondary server later
on, avoid any white spaces in the directory path for the shared directory.
Do not use the shared directory for other purposes than synchronizing the
DNA-M servers since all non DNA-M related files will be removed.
a. Linux
# exportfs -i -o rw <hostname>:<shared_directory>
b. Windows
> net share <share name>=<path to shared_directory> /GRANT:<user>,FULL /REMARK:"{productName} Script-based backup server"
The shared directory need to have write permission for the data transfer to
work, this is done by the option /GRANT:<user>,FULL when creating the
shared directory.
Refer to http://support.microsoft.com (select your Windows server version, and search for net
share).
Linux
Windows
Refer to http://support.microsoft.com (select your Windows server version, and search for net
use).
Linux
# cd /opt/transmode/tnm/mainserver/scripts
Windows
Linux
Windows
The options given are: DNA-M database name (-n), database user name (-u),
database password (-p), DNA-M installation directory (-i) and the network
mounted data transfer UNC path (-d), as stated in step 1.
The option (-p) for a database password should be excluded if no password has been set for the
MariaDB root user.
Additional options:
Execution without this option will give the backup file the same file name as the defined
database name (-n), e.g. tnmdb.sql. If the backup file should be given another file name than
the default, append the option -b to the command above:
Linux: -b<backup file name>.sql
Windows: -b <backup file name>.sql
4. Backup was successfully completed if a file named backupedOK.txt exists in the shared transfer
directory together with all backup files.
Linux
# cd /opt/transmode/tnm/mainserver/scripts
Windows
2. Execute the script to to update the secondary server using the backup files from the primary
server.
Linux
Windows
Additional options:
The DNA-M Server will be shut down during execution of the restore script. If the secondary
server should be restarted after execution of the restore script, append the option -r to the
command above.
3. Restoring was successfully completed if a file named restoredOK.txt exists in the shared
transfer directory, and the secondary now contains the same data and setting as the orimary
server.
6.2.6.1. Linux
3. Let the cron job run once and check the backup_primary.log and restore_secondary.log
afterwards. The scripts will set the $? environment variable to 1 if something goes wrong during
execution.
6.2.6.2. Windows
3. Let the scheduled jobs run once and check the backup_primary.log and restore_secondary.log
afterwards. The scripts will set the errorlevel environment variable to 1 if something goes wrong
during execution.
secondary server is synchronized with the primary server. Perform the procedures
for backup and restore as described in Backing up the primary server and
Transfer backup of primary server to secondary server.
• On primary server
1. Follow the instructions described in Configuring the secondary server
The servers are now re-configured, follow instructions starting in Backing up the primary server to
setup backup and automation
Table 50. Ports used between DNA-M Server and DNA-M Client
Type Source port / Location Destination port / location Protocol Remark
Table 51. Ports used between any web browser and DNA-M Server
Type Source port / Location Destination port / location Protocol Remark
HTTP - / Web browser (Web apps) 8081 / DNA-M Server TCP Configurabl
e
HTTP - / Web browser (Java web start) 9000 / DNA-M Server TCP Configurabl
e
Table 52. Ports used between DNA-M Server and higher level SNMP Agents (northbound OS)
Type Source port / Location Destination port / location Protocol Remark
Table 53. Ports used between RADIUS server and DNA-M Server
Type Source port / Location Destination port / location Protocol Remark
Table 54. Ports used between Syslog server and DNA-M Server
Type Source port / Location Destination port / location Protocol Remark
Table 55. Ports used between DNA-M Server, DNA-M Client, NE and NTP Server
Type Source port / Location Destination port / location Protocol Remark
Table 56. Ports used between DNA-M Server, DNA-M Client and RabbitMQ server
Type Source port / Location Destination port / location Protocol Remark
8. Internationalization support
This section describes how to configure operating system (Linux and Windows) and MariaDB to use
UTF-8, in particular, Japanese characters. Support for UTF-8 is limited to text strings local to the
DNA-M Server and DNA-M Client.
• Strings that are relevant to ME´s are not supported (e.g. node name)
• String from configuration files are not supported (e.g. main.serverName and
main.serverDescription in server.conf)
• Encryption in UTF-8 encoding is not supported (e.g. DNA-M user password)
Language change will take effect after next login to the server
8.1.2. Windows
Japanese language support is usually configured via Control Panel > Region and Language
8.2. MariaDB
MariaDB needs to configured to use UTF-8 for all tables.
The following configuration applies only for new DNA-M installations, where no
previous DNA-M database has been used. The described MariaDB configuration
will not convert an existing database to use UTF-8 encoding.
[client]
default-character-set=utf8
[mysqld]
character-set-server=utf8
[mysqldump]
default-character-set=utf8
[mysql]
default-character-set=utf8
[mysqladmin]
default-character-set=utf8
[mysqlcheck]
default-character-set=utf8
[mysqlimport]
default-character-set=utf8
[mysqlshow]
default-character-set=utf8
[myisamchk]
default-character-set=utf8
[myisampack]
default-character-set=utf8
Verify that both MariaDB server and client are speaking UTF-8
+--------------------------+----------------------------------+
| Variable_name | Value |
+--------------------------+----------------------------------+
| character_set_client | utf8 |
| character_set_connection | utf8 |
| character_set_database | utf8 |
| character_set_filesystem | binary |
| character_set_results | utf8 |
| character_set_server | utf8 |
| character_set_system | utf8 |
| character_sets_dir | /opt/mysql/mysql/share/charsets/ |
+--------------------------+----------------------------------+
If you see latin1 mentioned anywhere, double-check your MariaDB configuration, and make sure
you have restarted the MariaDB daemon.
8.3. DNA-M
DNA-M server and client needs to be configured to support Japanese Locale
If DNA-M is not running by root user, above lines need to be changed accordingly
net.core.wmem_max = 1048576
net.core.wmem_default = 1048576
net.core.rmem_max = 1048576
net.core.rmem_default = 1048576
# modprobe tcp_westwood
# echo westwood > /proc/sys/net/ipv4/tcp_congestion_control
# cat /proc/sys/net/ipv4/tcp_congestion_control
westwood
# cat /proc/sys/net/ipv4/tcp_allowed_congestion_control
westwood cubic reno
If nodes are on the same subnet as the DNA-M server add the following lines to /etc/sysctl. conf
net.ipv4.neigh.default.gc_thresh1 = 65535
net.ipv4.neigh.default.gc_thresh2 = 65535
net.ipv4.neigh.default.gc_thresh3 = 65535
You should not need to reboot after making changes to /etc/sysctl.conf. Just run the command:
# sysctl -p