8000 INM SR6.0 Third Party HW & SW Requirements

8000 Intelligent Network Manager SR6.0Third Party Hardware and Software Requirements

76.8060-70222D09.12.2014

Document Information

Revision History

Document No. Date Description of Changes

76.8060-70222D 09.12.2014 mTera UTP added in chapters 2.3, 2.4, 2.8, 2.9, 5.1.3 and 5.4.Product family limitation in DSC removed from chapter 2.9.Linux support for 5500 added in chapter 2.4 and the 5500 datamodified in chapter 5.4.OpenSwitch Server data added in chapter 5.1.4.Sybase Replication Server and Sybase OpenSwitch Server tablesadded in chapter 5.1.6.Chapter 5.4.5 OpenSwitch Server Software and chapter 5.4.6Replication Server Software added.

76.8060-70222C 07.10.2014 Hot Standby data added in chapters 2.2.2 and 4.8615 Smart Router added in the Recommendation for MaximumNumber of Nodes per Communication Server table in chapter 2.3.Sybase ASE 15.7 version updated to SP122 in chapter 5.4.3.

76.8060-70222B 11.07.2014 The document has been rebranded.Windows 8.1 support for a workstation added in chapters 1, 5.2,5.3, 5.4 and 5.4.1.Configuration definitions modified in chapter 1.8115 NTU and 8155 Access Switch added in the Recommendationfor Maximum Number of Nodes per Communication Server tablein chapter 2.3 and 8100 EFM added in chapters 2.3, 2.5 and 5.1.3.Numbers in the SSC and DSC data modified in chapters 2, 2.8 and2.9.A note on 6300 Craft Terminal not being supported in SSC addedin chapter 2.8 and 6300 Adapter notes modified in chapters 2.3and 5.4.2.Minimum required disk space per user with ThinClient user dataadded in chapter 5.1.6.A note on Eiconcard limitation in Windows Server 2012 removedand V6R10 added in chapter 5.1.7.Sybase ASE 15.7 version updated to SP110 in chapter 5.4.3.ThinClient Server version updated to Citrix XenApp 7.5 and theoperating system data to Windows Server 2012 R2 in chapter 5.4.4.

© 2014 Coriant. All rights reserved.

This manual is protected by U.S. and international copyright laws, conventions and treaties. Your right to use this manual issubject to limitations and restrictions imposed by applicable licenses and copyright laws. Unauthorized reproduction, modification,

distribution, display or other use of this manual may result in criminal and civil penalties.

The specifications and information regarding the products in this manual are subject to change without notice. All statements,information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,

express or implied. Users must take full responsibility for their application of any products.

Adobe® Reader® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

8000 Intelligent Network Manager SR6.0 76.8060-70222DThird Party Hardware and Software Requirements © 2014 Coriant.

2

Document Information

Terms and Conventions

Term Explanation

CPU Central Processing Unit

DCN Data Control Network

DNS Domain Name Service

DSC Dual Server Configuration

IP Internet Protocol

LAN Local Area Network

NMRS Network Management Resilience Service

NTP Network Time Protocol

NTU Network Terminating Unit

PMS Performance Management System

RAID Redundant Array of Inexpensive Disks

RAM Random Access Memory

SSC Single Server Configuration

TCP Transmission Control Protocol

WINS Windows Internet Naming Service

76.8060-70222D 8000 Intelligent Network Manager SR6.0© 2014 Coriant. Third Party Hardware and Software Requirements

3


4

Table of Contents

Table of Contents

About the Manual .............................................................................................................. 7

Objectives....................................................................................................................................................................... 7Audience......................................................................................................................................................................... 7Related Documentation .................................................................................................................................................. 7Document Conventions .................................................................................................................................................. 7Product Name Rebranding ............................................................................................................................................. 8Documentation Feedback............................................................................................................................................... 8

1 General ......................................................................................................................... 9

2 8000 Intelligent Network Manager System Configurations ..................................... 11

2.1 8000 Intelligent Network Manager Workstation ................................................................................................. 132.2 Database Server ................................................................................................................................................... 13

2.2.1 Separate Performance Database with Partitioning .............................................................................. 132.2.2 Replication Server ............................................................................................................................... 14

2.3 Communication Server ........................................................................................................................................ 142.4 Management Server ............................................................................................................................................. 152.5 DXX Server (8100 Adapter)................................................................................................................................ 162.6 Recovery Server .................................................................................................................................................. 162.7 8100 Service Computer ....................................................................................................................................... 162.8 Single Server Configuration ................................................................................................................................ 172.9 Dual Server Configuration - 8000 Intelligent Network Manager........................................................................ 172.10 8000 Intelligent Network Manager ThinClient Solution..................................................................................... 18

3 DCN, LAN and LAN-IC Requirements........................................................................ 19

3.1 DCN..................................................................................................................................................................... 193.2 LAN Configuration.............................................................................................................................................. 203.3 LAN and LAN-IC................................................................................................................................................ 213.4 Networking Configuration................................................................................................................................... 22

4 Database Protection Levels ....................................................................................... 23


5

Table of Contents

5 Computer Requirements for 8000 Intelligent Network Manager............................. 26

5.1 RAM, CPU and Disk Requirements ................................................................................................................... 265.1.1 Single Server Configuration ................................................................................................................ 275.1.2 Dual Server Configuration................................................................................................................... 275.1.3 Multi-server Configuration .................................................................................................................. 275.1.4 Network Manager Resilience Service Hardware Requirements ......................................................... 295.1.5 Disk Requirements for Workstations................................................................................................... 295.1.6 Disk Requirements for Servers............................................................................................................ 295.1.7 Accessories Needed for Servers .......................................................................................................... 32

5.2 Minimum Requirements for Service Computers................................................................................................. 335.3 Minimum Requirements for Workstations .......................................................................................................... 345.4 Software Sets ....................................................................................................................................................... 34

5.4.1 Workstation Software .......................................................................................................................... 355.4.2 Server Software – Management Server and Communication Server .................................................. 355.4.3 Database Server Software.................................................................................................................... 355.4.4 ThinClient Server Software ................................................................................................................. 365.4.5 OpenSwitch Server Software............................................................................................................... 365.4.6 Replication Server Software................................................................................................................ 365.4.7 VMware ............................................................................................................................................... 36

5.5 Displays ............................................................................................................................................................... 365.6 Preinstalled Computers........................................................................................................................................ 37


6

About the Manual

About the Manual

Objectives

This manual describes all the needed third party software components and versions (operatingsystems and software versions) in the 8000 Intelligent Network Manager system. It also describesthe relevant requirements and recommendations of the 8000 Intelligent Network Manager system.

Audience

This manual is intended for system administrators and system specialists.

Related Documentation

The document numbering scheme consists of the document ID, indicated by numbers, and thedocument revision, indicated by a letter. The references in the Related Documentation table beloware generic and include only the document ID. To make sure the references point to the latestavailable document versions, please refer to the relevant product document program on the Tellabsand Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation > DataNetworking > 8000 Intelligent Network Manager > Technical Documentation.

8000 Intelligent Network Manager SR6.0Software Installation Manual (76.8060-70201)

Provides instructions on installing and configuring8000 Intelligent Network Manager in differentcomputer platforms (workstation, servers).

8000 Intelligent Network Manager SR6.0Installation and Configuration Guide forManagement Server and Recovery Server(76.8060-70202)

Provides instructions on installing and configuring8000 Intelligent Network Manager ManagementServer and Recovery Server.

Web Reporter for 8000 Intelligent NetworkManager SR6.0Installation and Configuration Manual(76.8060-70215)

Provides instructions on installing and configuringthe Web Reporter tool.

8000 Intelligent Network Manager SR6.0Installation and Configuration Guide forNorthbound Interface (76.8060-70204)

Provides instructions on installing and configuringthe Northbound Interface in 8000 IntelligentNetwork Manager.

Document Conventions

This is a note symbol. It emphasizes or supplements information in the document.


7

https://www.portal.tellabs.com/global/portal/home.jsp

About the Manual

This is a caution symbol. It indicates that damage to equipment is possible if the instructionsare not followed.

This is a warning symbol. It indicates that bodily injury is possible if the instructions are notfollowed.

Product Name Rebranding

Product names are being rebranded and as a result the product name format consists of a numericalidentifier and a descriptive part.

Additionally, the previous Tellabs 7300 product family is renamed and the individual product namesare also changed. The table below lists previous and new product names. You may see instancesof both the previous and the new product names in the customer documents during the transitionperiod to the new naming system.

Previous Product Name New Product Name

Tellabs® 7300 metro Ethernet switching series 7090 Packet Transport Platform Series

Tellabs® 7305 7090-05 CE

Tellabs® 7307 7090-07 CE

Tellabs® 7310 7310

Tellabs® 7325 7090-25 CE

Tellabs® 7345 7090-45 CE

Documentation Feedback

Please contact us to suggest improvements or to report errors in our documentation:

Email: [email protected]


8

1 General

1 General

8000 Intelligent Network Manager (8000 INM) SR6.0 has been designed to use Windows 7,Windows 8.1, Windows Server 2008, Windows Server 2012 and Red Hat Enterprise Linux andSybase Adaptive Server Enterprise relational database. With this design it is possible to builda flexible system that easily adapts to changes in a managed network and to changes in theorganization of network management tasks.

The supported 8000 INM system configurations are listed in the following.

• Single Server Configuration (SSC)

• Small and medium-sized networks with a limited number of users

• Dual Server Configuration (DSC)

• Medium-sized networks

• Multi-server Configuration

• Scalable configuration to meet various network and operation requirements

For more detailed information on the different supported configurations, refer to 8000 IntelligentNetwork Manager Software Installation Manual.

8000 Intelligent Network Manager can adapt to centralized or distributed management schemes,and can grow when the needs of an operator develop. An operator can minimize startup costs in asmaller Coriant network by managing their entire network with a single server system configuration.When the needs of an operator and their network grow, new management workstations and serverscan be added at any time to build up to a multi-server 8000 INM system configuration.

8000 Intelligent Network Manager may work on other types of machine configurations thanthe specified ones, but it cannot be guaranteed.The requirements in this document apply to new purchases only. Coriant also requiresexisting customers to follow up with this document. When planning to change some part ofthe 8000 INM system configuration, it is to be done according to the requirements of thisdocument.Check that you always use the most recent version of this document.Before updating the 8000 INM system, contact Coriant Customer Services.

It is recommended to use the latest version of the Norton (Symantec) antivirus program inyour workstations and servers. Norton may affect the performance of servers.

8000 Intelligent Network Manager has been designed and tested to be the only applicationrunning on the computers. Running other applications on the same computers is notsupported and Coriant strongly recommends against it.


9

1 General

A support agreement for the third party hardware and software components is highlyrecommended.

It is the responsibility of the end customer to ensure their compliance to the third partylicensing terms and conditions.


10

2 8000 Intelligent Network Manager System Configurations

2 8000 Intelligent Network Manager SystemConfigurations

In the 8000 Intelligent Network Manager system configurations, the network manager componentsare distributed over several computers (some optional).

• Workstation(s)

• Database Server

• Communication Server(s)

• Management Server(s)

• DXX Server(s)

• Recovery Server(s)

• 8100 Service Computer

8000 INM can be configured depending on the size of the network, the number of concurrent usersand the type of nodes used. The different supported configurations are described in 8000 IntelligentNetwork Manager Software Installation Manual. As an example the 8000 INM components in amulti-user environment is shown in the figure below.


11


Fig. 1 Example of Multi-user 8000 INM Configuration

It is recommended that all the 8000 Intelligent Network Manager server computers (DatabaseServer, Communication Servers, Management Servers, DXX Servers and Recovery Server) arelocated in the same LAN segment to provide a more reliable operation. However, 8000 INMworkstations can be distributed to different locations using routers.

For more information, refer to the hardware and software requirements in chapter 5 ComputerRequirements for 8000 Intelligent Network Manager.

The recommendation of the maximum number of workstations is based on the Coriant evaluation ofthe 8000 INM system performance. Configuration of the servers and workstations and the DCNnetwork is required to fulfill at least the minimum requirements of the large networks describedin chapters 3 DCN, LAN and LAN-IC Requirements and 5 Computer Requirements for 8000Intelligent Network Manager. Several internal and external factors such as the functions utilized forprovisioning and the amount of collected PMS data set memory and CPU capacity requirementsfor the system. Additionally, the quality of DCN and the number of managed nodes may affect theoverall performance of the system and the total maximum number of workstations can vary.

The tables below show the recommendations for the maximum number of workstations and themaximum number of workstations per server.


12


Recommendation for Maximum Number of Workstations

Maximum Number of Workstations

Workstation 1501

Recommendation for Maximum Number of Workstations per Server

Type of Server Maximum Number of Workstations

Management Server 40

ThinClient Server 20

Single Server Configuration 10

Dual Server Configuration 10

A maximum of 30 000 Coriant network elements is supported.

When calculating the number of network elements in the system, the number of other objects mayalso have an impact on the required hardware. For example, it is supposed that there are on average5 Network Terminating Units (NTUs) per node. If you have more than 5 NTUs per node, use thefollowing formula: number of NTUs/5 = number of nodes. For example, if you have a network with1 000 nodes and there are 10 000 NTUs, the requirements will be as for a network with 2 000 nodes.Additionally, the 8800 NEs can be very dense and should be counted as 5 nodes for 8830 SmartRouter and 8840 Smart Router, and 10 nodes for 8860 Smart Router.

2.1 8000 Intelligent Network Manager Workstation

8000 Intelligent Network Manager workstation functions as an access point to an 8000 INM systemnetwork and its elements for a remote operator through a graphical user interface. There is onlyone workstation type. However, workstation software can be run also in Management Servercomputer. Workstation connects to a Management Server running a Satellite Service. Note that theworkstation can only be run on the Management Server with Windows as the operating system andthus, workstation is not supported on Linux.

2.2 Database Server

The database hardware requirements vary according to the actual size of the 8000 IntelligentNetwork Manager system network. Sybase database is supported on Windows and Linux servers.Solaris is only supported for the existing customer installations.

2.2.1 Separate Performance Database with Partitioning

Separate performance database (PM DB) with partitioning is a scalability enhancement to the8000 Intelligent Network Manager system. It increases the efficiency of the PM application andNetwork Manager Resilience Service. Furthermore, as a result of separation, it protects the 8000INM configuration database from filling up due to high amount of PMS data.

1In case of pure 8100 network, the maximum number of workstations is 800.


13


It is recommended to consider taking separate PM DB with partitioning into use, if the dailycollected amount of PM data exceeds 10 million rows. Furthermore, if some of the followingconditions are met in a customer network, it is strongly recommended that separate PM DB withpartitioning is taken into use.

1. The performance data deletion time exceeds two hours.

2. Administrative burden is introduced by:

• Database size being too large for efficiently taking database backups.

• Database size constantly approaching its limits and introducing need for DB size incrementsor size monitoring.

• Replication latency is over the desired switch over time period.

3. Customer perceives PM reports being too slow.

These conditions are meant to act as guidelines and their applicability towards an individual customernetwork might vary. The guidelines have been established based on customer cases and testing.

Note that a separate performance database requires an additional Sybase partitioning license perDatabase Server.

2.2.2 Replication Server

Replication Server handles the replication from primary to secondary database in the NetworkManager Resilience Service (NMRS) Warm or Hot Standby environment. In the 8000 IntelligentNetwork Manager system configuration Linux Database Servers must be used.

There are recommendations for general guidelines in chapter 5.1.4 Network Manager ResilienceService Hardware Requirements, but optimal server specifications must be carried out based on aspecific network.

When planning a Network Manager Resilience Service, contact your Coriant representative.Before purchasing any Network Manager Resilience Service, the exact supported softwareversion numbers and the latest details need to be checked from Coriant.

2.3 Communication Server

Communication Server is used for managing 5500, 6300, 7090, 7100, 8100 EFM, 8600, 8800 andmTera UTP network elements. Communication Server is supported on Windows. Linux server issupported for the 5500, 7090, 7100 and mTera UTP network elements.

The number of required Communication Servers depends on the size of the network. Arecommendation for a maximum number of nodes per a single Communication Server is presentedin the table below. Each server takes care of one or several areas in a network and can run severalparallel adapters (e.g. 7090, 7100, 8600 and 8800). It is recommended to run the adapters in separateCommunication Servers, especially if the number of managed network elements is significant.

MARBENTM OSIAM OSITP4, version 1.2 is used for the 6300 network element communication.


14


6300 Adapter is only supported in Windows Server 2008.

Recommendation for Maximum Number of Nodes per Communication Server

Node Type Number of Nodes per Communication Server

5500 nodes, or 50

6300 nodes, or 500

7090 nodes, or 500

7100 Nano, or 300

7100 OTS, or 100

mTera UTP, or 300

8115 NTU, or 5000

8155 Access Switch, or 500

8602 Smart Router, or 5000


8606 Ethernet Aggregator, or 2500








8800 Smart Routers 100

For example, a single Communication Server can handle up to 30 x 8660 Smart Routers and 4000 x8605 Smart Routers with PMS.

These recommendations are general guidelines for dimensioning the 8000 Intelligent NetworkManager system. The optimum number of Communication Servers needed for a network depends onthe number of nodes, the node inventories (the number and type of physical and logical interfaces),the set of PMS counters monitored, the overall 8000 INM activity (operations per second in thenetwork), the fault and performance polling targets etc.

2.4 Management Server

The Management Server functions as a framework for different 8000 Intelligent Network Managerapplication logic divided into services each running processes of its own.

The installation of the different service types is done by selecting the appropriate service forManagement Server in 8000 Intelligent Network Manager Setup Wizard.

Management Server is supported on Windows. Additionally, Linux server is supported for the5500, 7090, 7100 and mTera UTP networks.


15


Only one workstation can be run on the Windows Management Server.

For more information related to different services, refer to 8000 Intelligent Network ManagerInstallation and Configuration Guide for Management Server and Recovery Server.

2.5 DXX Server (8100 Adapter)

DXX Server is used for managing 8100 network elements. However, note that CommunicationServer is used for managing the 8100 EFM network elements. Refer to 2.3 Communication Server.The number of required DXX Servers depends on the size of the network. Each server takes careof one or several areas in the network. Increasing the number of DXX Servers also increases thereliability of network management.

In a DXX Server one X.25 port is required per 250 subracks. A DXX Server can have a maximumof four X.25 ports (using dual port X.25 cards), i.e. a total of 1000 subracks. Normally this means700-800 nodes, depending on the number of 8170 Cluster Nodes. When using asynchronous linksyou can have two links with a maximum of approximately 50 subracks per link, i.e. a total of 100subracks. With four X.25 ports and two asynchronous links the total is 1100 subracks in a DXXServer. When using IP links you can have 250 subracks per IP link. A single DXX Server canhandle up to 1500 subracks.

If you have several NTUs (more than five) per node, take into account that it can slow down faultpolling if there are numerous faults in the NTUs.

DXX Server with the X.25 card is not supported in a virtualized server environment.

2.6 Recovery Server

The Recovery Server component is used for circuit and trunk protection. It is possible to have asecond Recovery Server for backup purposes.

The DXX Server and Recovery Server can be run in a common machine if the network size is up toapproximately 350 nodes and there are no other DXX Servers in the network.

2.7 8100 Service Computer

8100 Service Computer (SC) is used for monitoring and controlling the operation of a single 8100system node. The only 8000 Intelligent Network Manager user interface component installedon SC is Node Manager for the 8100 nodes.

You can install the 6300 Craft Terminal which is used for controlling network elements of the 6300system, in the same computer as the SC. If you use the serial port for communication, only one ofthe programs can be run at a time. If you use the IP link for the SC communication, Craft Terminal(using the serial port) can be run at the same time.


16


2.8 Single Server Configuration

The Single Server Configuration (SSC) for small networks is a system in which the ManagementServer, Communication Server and the database are all located in one physical entity. In theWindows operating system the management system configuration supports up to ten users. The SSCis supported on Windows servers. Additionally, there is Single Server configuration support for the5500, 7090, 7100 and mTera UTP networks in Linux. However, running a workstation on the serveritself is only supported in Windows. The maximum number of supported network elements is 30 percent compared to a single Communication Server (refer to chapter 2.3 Communication Server).

Fig. 2 Example of Single Server Configuration

See the hardware and software requirements in chapter 5 Computer Requirements for 8000Intelligent Network Manager.

6300 Craft Terminal is not supported in SSC.

2.9 Dual Server Configuration - 8000 Intelligent Network Manager

The Dual Server Configuration (DSC) is a setup with two physical servers in which the DatabaseServer and Management Server are located on one physical server while the second one hosts theCommunication Server. In the Windows operating system the management system configurationsupports up to ten workstations, out of which one can be located on the combined Database andManagement Server. The DSC is supported on Windows and Linux servers. There is Dual Serverconfiguration support for the 5500, 7090, 7100 and mTera UTP networks in Linux. However,running a workstation on the server itself is only supported in Windows. The maximum numberof supported network elements is the same as for a single Communication Server (refer to chapter2.3 Communication Server).


17


Fig. 3 Example of Dual Server Configuration

See the hardware and software requirements in chapter 5 Computer Requirements for 8000Intelligent Network Manager.

2.10 8000 Intelligent Network Manager ThinClient Solution

8000 Intelligent Network Manager ThinClient is a solution that replaces the 8000 INM workstationwith a client/server application which saves bandwidth, simplifies upgrades and maintenance andprovides flexible remote access. The ThinClient solution is based on Citrix XenApp. ThinClientsolution is not supported in Linux.


18

3 DCN, LAN and LAN-IC Requirements


3.1 DCN

An inband or outband Data Control Network (DCN) can be used between 8000 Intelligent NetworkManager and network elements. In the figure below a reference mobile transmission networkis described for DCN dimensioning. For a typical network (as shown in the figure below), therecommended DCN bandwidths are at least as follows.

• 10 Mbps to core nodes,

• 1 Mbps to hub nodes (aggregating up to ten cell sites), and

• 256 kbps to cell site nodes (128 kbps without PMS).

Fig. 4 Mobile Transmission Network


19


3.2 LAN Configuration

It is recommended that the LAN is dedicated to 8000 Intelligent Network Manager computers.When building an Ethernet LAN for 8000 INM, special attention should be paid to the connectionsbetween servers. A main management LAN interconnects the Database Server and various 8000INM servers.

Below is a figure of the main management LAN and some requirements for it.

• Ethernet bandwidth of at least 100 Mbps is required.

• Switch-based technology is required.

• The main management LAN should be dedicated for use with 8000 INM only.

• Tolerated maximum latency is 10 ms.

• If the database is replicated, the network speed requirements for the replication database equal tothe 8000 INM LAN.

Fig. 5 8000 INM Main Management LAN


20


There are some requirements for the LAN configuration.

• Workstation (previously satellite workstation) down-link

• Segment(s) of LAN that interconnect remote workstations to the Management Server.

• Hubs and switches can be used.

• Every computer having a database connection (all servers) should have reliable and error freenetwork connection.

• Note that one such computer behind slow database connection will slow down the wholenetwork management system.

It is recommended not to use auto-negotiation for the speed and duplex settings in switch ports andserver NICs on the 8000 INM LAN.

3.3 LAN and LAN-IC

It is possible to connect workstations to servers from remote locations using TCP/IP. In such a casethe communication link capacity between the locations should be as recommended in the followingtable. These capacities guarantee a reasonable workstation startup time, depending on the size of thenetwork. It is assumed that only one workstation is started up at a time.

Recommendations for communication link capacity between workstations and the mainmanagement LAN, based on workstation startup time

Maximum Number of Network Elements inthe Network

Minimum Communication Link Capacity

1000 512 kbps

> 1000 1 Mbps

> 10000 2 Mbps

> 30000 4 Mbps

The capacity should be reserved as specified above even if there is only one workstation in a remotelocation. However, if there are several workstations in a remote location, the link capacity must beset at least to the values listed in the following table.

Recommendations for communication link capacity between workstations and the mainmanagement LAN, based on the number of workstations in remote LAN

Number of Workstations in RemoteLocation

Minimum Communication Link Capacity

1-3 512 kbps

4-10 2 Mbps

11-20 4 Mbps

The capacity must be selected as the maximum of the capacities based on the workstation startuptime and number of workstations in a remote location.


21


The communication links between the locations must be reliable, as the quality of these linksshall be better than 99.99% in Error-Free Seconds. If the quality of communication links is worsethan required, Coriant cannot guarantee that 8000 Intelligent Network Manager or its parts workefficiently.

3.4 Networking Configuration

It is highly recommended to use the Windows domain network model when more than ten computersare used for network management.

For ease of administration of the computers, the servers and workstations should be connected toa domain if there are more than ten computers in the management LAN. This should be done,especially, if users are using unique accounts to access the computers. In a Windows domain, theuser accounts are stored centrally in one computer that does the user authentication.

A workgroup model (Peer-to-Peer) network can be used if there are less than 10 computers in themanagement LAN, or if the users are using the same username and password.

It is also recommended to have Windows Internet Naming Service (WINS) and/or Domain NameService (DNS) servers running in the LAN. These servers provide name resolution services to othercomputers in the network, so that they can resolve computer names into an IP address that enablescomputers on a network to find one another and transfer information. The name resolution servicesshould not be running in any of the dedicated 8000 Intelligent Network Manager servers. Separateservers are needed. All servers must have fixed IP addresses.

It is highly recommended to enable Network Time Protocol (NTP) client service on the Databaseand Replication Servers as well as enable NTP in all 8600 network elements.

Management and Communication Servers should use either NTP or Windows domain time serviceto keep the clocks synchronized.


22

4 Database Protection Levels


There are several ways of minimizing the data loss in case of Database Server failures.

• Scheduled database dumps. You always need to take scheduled dumps of the database. Frequencyof transaction dumps should be set according to the level of network activity. This also definesthe risk level in case of failures. Taking database dumps is the only way to restore the previousdatabase state e.g. in case of human errors.

• Mirrored disk drives. Mirroring provides protection against hard disk failures. It means usingredundant disks in Database Server.

• Clustering. Clustering protects the database from any single point of failure in Database Server.Clustering provides protection within one site. Note that this solution must be purchased directlyfrom the server supplier.

• Network Manager Resilience Service is currently available in Cold, Warm and Hot Standby.

• Cold Standby means having an inactive spare Database Server with ready configurations.

• Warm Standby is a resilience service, which provides a way to manually configure connec-tions from the main database to the replicated backup database in a case of failure.

• Hot Standby is a resilience service, which transfers connections from the main database tothe replicated backup database automatically in a case of failure. The automatic transferdoes not cause any traffic outages. However, it can be noticed as a short delay in the8000 Intelligent Network Manager usage.

When planning a Network Manager Resilience Service, contact your Coriant representative.Before purchasing any Network Manager Resilience Service, the exact supported softwareversion numbers and the latest details need to be checked from Coriant.


23


Sched-uledDatabaseDumps

MirroredDiskDrives

Cluster-ing

ColdStandby

WarmStandby

HotStandby

Obliga-tory / op-tional

Obligatory Obligatory Optional Optional Optional Optional

Distancebetweenprimaryandbackupserver

Unlimited Within theserver

8 m - 15 kmdependingon the cablemedia

Unlimited UnlimitedwithNMRSWarmStandby

UnlimitedwithNMRSHotStandby

Failover:automatic/ manual

Manual Automatic Manual Manual Manual Automatic

Recoverytime

Time ofrestoringthedatabasedumps

Real time Start-uptime of thedatabasesoftware

Time ofrestoringthedatabasedumps

Time ofstarting8000 INMsystem,somelatencydependingon theconnectionbetweenthe servers

Real time,somelatencydependingon theconnectionbetweenthe servers

Backuplevel

Transac-tion level,frequencyof trans-action logdumps

Disk I/O Disk I/Oand virtualserver host

Transac-tion level,frequencyof trans-action logdumps

Transac-tion level

Transac-tion level

Loss incase offailure

Databasemodifi-cationsdone af-ter the lasttransactiondump

No loss No loss Databasemodifi-cationsdone af-ter the lasttransactiondump

Unfinishedtransac-tions

Unfinishedtransac-tions

Config-urationrequire-ments

Diskspace andseparatebackupmedia (e.g.a tape)

Separatedisk drives

IdenticalDatabaseServerhardware,shareddisk arraysystem,clustersoftware

Diskspace andseparatebackupmedia (e.g.a tape).IdenticalDatabaseServerhardware,aconnectionbetweenthe servers.

Identi-cal Data-base Serverhardware,a con-nectionbetweenDatabaseServersand Repli-cationServer

IdenticalDatabaseServerhardware,a con-nectionbetweenDatabaseServersand Repli-cationServer


24


Sched-uledDatabaseDumps

MirroredDiskDrives

Cluster-ing

ColdStandby

WarmStandby

HotStandby

Additionalrequire-ments

Dumpsmust betestedregularly

None Orderedfrom Or-acle. Aprerequi-site fromOracle:two trainedcluster ad-ministra-tors.

Dumpsmust betestedregularlyin the coldbackup

TwotrainedReplica-tion Serveradministra-tors. Auto-matic mon-itoring forsystem.

TwotrainedReplica-tion Serveradmin-istrators.Automaticmonitoringfor system.

Supporteddatabaseplatforms

Windows,Solaris2,Linux

Windows,Solaris2,Linux

Solaris2 Windows,Solaris2,Linux

Linux Linux

Mayrequirestartingother8000 INMservers

Yes No Yes Yes Yes No

2 Solaris is supported only for the currently installed base and should not be used in new deployments.


25

5 Computer Requirements for 8000 Intelligent Network Manager

5 Computer Requirements for 8000 IntelligentNetwork Manager

5.1 RAM, CPU and Disk Requirements

The recommendations in this chapter are general guidelines and minimum requirements. Additionalmemory and/or faster processor may provide better performance.

When purchasing new servers for 8000 Intelligent Network Manager, it is recommended to use a64-bit operating system with a minimum of 8 GB of RAM. Moreover, when upgrading existingservers to a 64-bit operating system it is recommended to install a minimum of 8 GB of RAM.

When upgrading to SR6.0 it is possible to continue using servers running a Windows 32-bitoperating system if the memory requirement for those servers is less than or equal to 4 GB of RAM.Refer to the RAM and CPU requirement table below for more details.

The RAM and CPU requirements depend on the actual network size. To make reading easier, thenetwork size is defined as follows.

Network Size Definition

Small Medium Large

1 - 2 Communication Servers 3 – 6 Communication Servers > 6 Communication Servers

The number of Communication Servers is calculated as described in 2.3 Communication Server.

If performance history data collection is going to be used, contact your Coriant representativefor more detailed information about the Database Server requirements.


26


5.1.1 Single Server Configuration

Hardware Minimum CPU Minimum RAM

SSC 1 x Intel Xeon 6-core 1.9 GHz(64-bit) or better

8 GB

5.1.2 Dual Server Configuration

Hardware Minimum CPU Minimum RAM

DSC - Server 1 (DatabaseServer, Management Server)

1 x Intel Xeon 6-core 1.9 GHz(64-bit) or better

8 GB

DSC - Server 2 (CommunicationServer)

1 x Intel Xeon quad-core 2.2GHz or better (<100 nodes)2 x Intel Xeon quad-core 2.2GHz or better (>100 nodes)

4 GB

5.1.3 Multi-server Configuration

Minimum CPU3 Minimum RAM (based on the network size)

Hardware Small Medium Large

Workstation 1 x Intel Core 2Duo 2 GHz orbetter

2 GB 4 GB 4 GB

Database Server(x64)

1 x Intel Xeonquad-core 2.2GHz or better(<3000 nodes)2 x Intel Xeonquad-core 2.2GHz or better(>3000 nodes)

8 GB 16 GB 32 GB

3To match the physical CPUs to virtual CPUs in the virtualized server environment, contact your virtual server environment supplier.


27


Minimum CPU3 Minimum RAM (based on the network size)


Database Server(sparc)4

1 x OracleSPARC VIIquad-core orbetter (<3000nodes)2 x OracleSPARC VIIquad-core orbetter (<10000nodes)4 x OracleSPARC VIIquad-core orbetter (>10000nodes)

8 GB 16 GB 32 GB

CommunicationServer6300

1 x Intel Core 2Duo 2 GHz orbetter

1 GB 2 GB 4–8 GB

CommunicationServer55007090710086008100 EFM8800mTera UTP

1 x Intel Xeonquad-core 2.2GHz or better(<100 nodes)2 x Intel Xeonquad-core 2.2GHz or better(>100 nodes)

4 GB 6 GB 8 GB

ManagementServer

1 x Intel Xeonquad-core 2.2GHz or better

4 GB 6 GB 8 GB

DXX Server 1 x Intel Core 2Duo 2 GHz orbetter

1 GB 1 GB >1 GB

Recovery Server 1 x Intel Core 2Duo 2 GHz orbetter

1 GB 1 GB >1 GB

ThinClient Server 2 x Intel Xeonquad-core 2.2GHz or better

2 GB Base + 2GB per supported8000 INMworkstations+ 256 MB persupported 8100workstations

2 GB Base + 3GB per supported8000 INMworkstations+ 512 MB persupported 8100workstations

2 GB Base + 3GB per supported8000 INMworkstations+ 1 GB persupported 8100workstations

4 Only supported for the currently installed base and should not be used in new deployments.


28


5.1.4 Network Manager Resilience Service Hardware Requirements

Minimum CPU Minimum RAM (based on the network size)


ReplicationServer

1 x Intel Xeon6-core 1.9 GHz(64-bit) or better

8 GB 16 GB 32 GB

OpenSwitchServer

1 x Intel Xeon6-core 1.9 GHz(64-bit) or better

8 GB 16 GB 32 GB

For the latest information on the operating system and Sybase versions, contact your Coriantrepresentative.

5.1.5 Disk Requirements for Workstations

The recommendations in this chapter regarding disks apply to 8000 Intelligent Network Managerworkstations. These recommendations are general guidelines and minimum requirements.Additional disk size or protection mechanisms can be used.

The recommended minimum size of the physical disks is 100 GB.

8000 Intelligent Network Manager Workstations in Windows

8000 INM workstations Disk 1 – OS + 8000 INM software

5.1.6 Disk Requirements for Servers

The recommendations in this chapter regarding disks apply to 8000 Intelligent Network Managerservers and Database Servers. These recommendations are general guidelines and minimumrequirements. Additional disk size or protection mechanisms can be used.

The disks can be categorized into two categories.

• Internal (I) – Disks that reside physically internal to the server hardware.

• External (E) – Disks that reside external to the server hardware on a storage device e.g. FibreChannel Disk Array or Storage Area Network (SAN).

The disks represented in the below tables are virtual disks, not physical disks. The actual number ofphysical disks underneath a virtual disk depends on the implemented protection mechanism and thevendor. The operating system (OS) disk is recommended to be protected by RAID 1, i.e. mirroring,whereas the database disks are recommended to be protected by RAID 1+0.

The recommended minimum sizes of the physical disks are 146 GB for internal and 300 GB forexternal disks.


29


8000 Intelligent Network Manager Servers

Windows/Linux5 (1 disk)

Disk 1(I/E) RAID 1 Operating System and 8000INM software

Single Server/Dual Server Configuration

Windows/Linux5 (4 disks)

Disk 1 (I/E) RAID 1 Operating System, Sybase ASE,8000 INM software, Master,tempdb and systemprocs.

Disk 2 (I/E) RAID 1 Data Volume

Disk 3 (I/E) RAID 1 Log Volume

Disk 4 (I/E) RAID 1 Backup

Sybase Database Servers

Windows/Linux (5 or 6 disks)

Disk 1 (I/E) RAID 1 Operating System and SybaseASE software

Disk 2 (I/E) RAID 10 (or 1) Master, tempdb, systemprocsand Data Volume

Disk 3 (I/E) RAID 10 (or 1) Log Volume

Disk 4 (I/E) RAID 5 (or 1, 6 or 10) Backup

Disk 5 (I/E) RAID 10 (or 1) Separate PM Data (optional)

Disk 6 (I/E) RAID 10 (or 1) Separate PM Log (optional)

Solaris 2(4 disks)

Disk 1 (I) RAID 1 Operating System and SybaseASE software

Disk 2 (E) RAID 10 (or 1) Master, tempdb, systemprocs,Data Volume

Disk 3 (E) RAID 10 (or 1) Log Volume

Disk 4 (E) RAID 5 (or 1, 6 or 10) Backup

Sybase Replication Server

Linux (4 disks)

Disk 1 (I) RAID 1 Operating System and SybaseREP software

Disk 2 (I) RAID 1 Replication Volume

5 Linux currently supports the 5500, 7090 and 7100 network elements.


30


Sybase OpenSwitch Server

Linux (2 disks)

Disk 1 (I) RAID 1 Operating System and SybaseOSW software

The recommended configuration for the 8000 Intelligent Network Manager Database Server disksystem (without the optional separate PM database) is presented below.

Fig. 6 Recommended Database Server Disk System

The disks can reside as internal disks inside the Database Server, or in an external disk system.


31


Database Server Disk System Capacities by Network Size

IO Requirement for Dataand Log

RAID Group Capacity

MB/s IOPS6 master,procs,db8000data,tempdbdata

db8000 log,tempdb log

Backup

Smallnetwork

10 MB/s 135 IOPS 50 GB 100 GB 200 GB

Mediumnetwork

50 MB/s 670 IOPS 250 GB 500 GB 2.5 TB

Largenetwork

200 MB/s 2600 IOPS 500 GB 1000 GB 5 TB

Network Share Server for ThinClient User Data

Minimum required disk space per user 50 MB

5.1.7 Accessories Needed for Servers

The following accessories are related to the 8000 Intelligent Network Manager servers and DatabaseServers. The specifications may vary according to the vendor.

Accessories for Database Servers

External Disk Array

Hardware

Model compatibility Supporting Dual Fibre Channel (FC) RAID and large disks

Disk system software Vendor specific Disk system software e.g. Veritas VolumeManager, zfs, Solaris Volume Manager, Red Hat Native Driver,EMC storage management software

Backup Tape Device

Hardware

Drive LTO drive

6 IOPS measured from the disk HW level and recorded in 8000 Intelligent Network Manager testing. Based on the results, IOPS measured from theOS level is 1.5 times IOPS from the disk HW level.


32


Other components

Drives DVD-ROM drive

LAN adapter With four on-board RJ45 10/100/1000Base-T (Copper) GigabitFast Ethernet ports

Display VT 100 or compatible terminal, terminal concentrator or graphicterminal supported by vendor

Accessories for 8000 Intelligent Network Manager Servers

Accessories Set – X.25 Adapter DXX Server on Windows

Eiconcard for X.25 Eiconcard S94 (310-208)Eiconcard S94/66 (310-828)Eiconcard S94 V2 (306-296) Revision 50Eiconcard S94 PCI Express (306-298)

Eiconcard connection support Windows V6R8 for XP, Windows 7 and Server 2008 (32-bitversion)Windows V6R8 for XP, Windows 7, Server 2008 and Server 2008R2 (64-bit version)Windows V6R10 for 64-bit Win 7, Win 8, Server 2003, 2008 R2and 2012(included in the 8000 Intelligent Network Manager installationDVD)

USB to Serial Adapter

USB to serial adapter Targus - connectivity series, USB to Serial (RS232) Adapter

5.2 Minimum Requirements for Service Computers

The network manager Service Computer software will run on laptop computers which meet thespecifications below. Note that Coriant can properly support only 3rd party hardware and softwaretested by Coriant. In case of problems with other computer types, the vendor of that equipmentshould be contacted.

The requirements for Service Computer laptops are listed in the following.

• a laptop computer certified for Microsoft Windows 7 or Windows 8.1 (follow the minimum re-quirements specified by the operating system vendor)

• manufacturer provided hardware drivers

• serial port available

• parallel or USB port available

Minimum performance requirements are listed in the following.

• Intel Pentium II processor with 300 MHz clock frequency or better

• 512 MB or more RAM (1 GB if Craft Terminal is used in the same computer as manager ServiceComputer)


33


• 2 MB or more memory in display adapter

• 4 GB hard disk or larger with 650 MB free space after installation of Service Computer software

5.3 Minimum Requirements for Workstations

The 8000 Intelligent Network Manager workstation software will run on desktop computers whichmeet the specifications listed below.

The general requirements for workstations are listed in the following.

• a computer certified forMicrosoftWindows 7 orWindows 8.1 (follow the minimum requirementsspecified by the operating system vendor)

• manufacturer provided hardware drivers

Minimum performance requirements are listed in the following.

• the amount of RAM is dependent on the size of network. (The minimum amount of requiredRAM should be checked from the table in chapter 5.1 RAM, CPU and Disk Requirements .)

• a display adapter capable of at least 1280 x 1024 resolution with 16-bit color depth is recom-mended

• an Ethernet adapter with a capacity of at least 100 Mbps

Keep in mind that the processor clock speed and the amount of RAM affects the performanceof the computer. For better performance, select your workstations among the latestcomputer models. Using slow management workstations may affect the performance ofother workstations as well.

When buying new workstations for 8000 INM, it is recommended to use a at least 2 GB of RAM.

5.4 Software Sets

8000 Intelligent Network Manager supports the Windows 7, Windows 8.1, Windows Server 2008and Windows Server 2012 operating systems. Linux Management Server and CommunicationServer are supported for the 5500, 7090, 7100 and mTera UTP networks. Windows, Linux andSolaris are supported for the Database Server.


34


5.4.1 Workstation Software

Operating system with 8000 INM Windows 7 Professional/Enterprise, English with the latestMicrosoft recommended patches (64–bit version)OrWindows 8.1 Pro/Enterprise, English with the latest Microsoftrecommended patches (64–bit version)

Software for reading help files in8000 INM

Current version of Adobe Acrobat Reader

5.4.2 Server Software – Management Server and Communication Server

Operating system with 8000 INM Windows Server 2008 R2 Standard Edition or better, English(Service Pack 1 or higher) with the latest Microsoft recommendedpatches (64-bit version)OrWindows Server 2012 R2 Standard Edition or better, English withthe latest Microsoft recommended patches (64-bit version)OrRed Hat Enterprise Linux 6 (6.3 or higher) with the latestrecommended patches (64-bit version)

Communication Server with 6300Adapter

MARBENTM OSIAM OSITP4, version 1.2

6300 Adapter is only supported in Windows Server 2008.

5.4.3 Database Server Software

Sybase

Windowsoperating system

Windows Server 2008 R2 Standard Edition or better, English (Service Pack 1 orhigher) with the latest Microsoft recommended patches (64-bit version)OrWindows Server 2012 R2 Standard Edition or better, English with the latestMicrosoft recommended patches (64-bit version)

WindowsDatabase Serversoftware

Sybase ASE Enterprise Edition 15.5 for Windows x64 64-bit – ESD#5.2(EBF20630) or the latest Sybase recommended patchesOrSybase ASE Enterprise Edition 15.7 for Windows x64 64-bit – SP122

Unix operatingsystem

Solaris 10 9/10 or higher with the latest Oracle recommended patches(64-bit version)

Unix DatabaseServer software

Sybase ASE Enterprise Edition 15.5 for Oracle Solaris SPARC 64-bit – ESD#5.2(EBF20632) or the latest Sybase recommended patchesOrSybase ASE Enterprise Edition 15.7 for Oracle Solaris SPARC 64-bit – SP122


35


Linux operatingsystem

Red Hat Enterprise Linux 6 (6.3 or higher) with the latest recommended patches(64-bit version)

Linux DatabaseServer software

Sybase ASE Enterprise Edition 15.7 for Linux x86-64 64-bit – SP122

With new 8000 INM installations, it is recommended to use the Enterprise Edition of SybaseAdaptive Server Enterprise.

5.4.4 ThinClient Server Software

Windows operating system Windows Server 2012 R2 Standard Edition or better, English(Service Pack 1 or higher) with the latest Microsoft recommendedpatches (64-bit version)

Application Server Citrix XenApp 7.5 (Windows Server 2012 R2, 64-bit version)Citrix recommended Hotfix Rollup Packs and hotfixes

5.4.5 OpenSwitch Server Software

Operating system Red Hat Enterprise Linux 6 (6.3 or higher) with the latestrecommended patches

OpenSwitch Server Software Sybase OpenSwitch 15.1 for Linux x86 – ESD#7 (EBF20877) orthe latest Sybase recommended patches

5.4.6 Replication Server Software

Operating system Red Hat Enterprise Linux 6 (6.3 or higher) with the latestrecommended patches

Replication Server Software Sybase Replication Server 15.7.1 for Linux x86-64 64-bit – SP121(EBF22360) or the latest Sybase recommended patches

5.4.7 VMware

VMware version 5.0 or higher, supported by the used Windows operating system

5.5 Displays

Specification display with 1280 x 1024 resolution or better

Recommendation 19" or larger screen

Small fonts should be used in Windows.


36


5.6 Preinstalled Computers

Preinstalled servers are available from Coriant. These servers are delivered with the requiredsoftware preinstalled (e.g. operating system, Sybase and/or 8000 Intelligent Network Manager).These computers are also tested before shipping. Note that the required Sybase and 8000 INMlicenses need to be ordered separately in accordance to the customer specific 8000 INM setup.When arriving on-site those pre-installed servers then only need to be commissioned according tothe customer specific design and after applying/activating the licenses are ready to be used.


37

Date post:	17-Feb-2016
Category:	Documents
Upload:	marco-mejia
View:	40 times
Download:	16 times

8000 INM SR6.0 Third Party HW & SW Requirements

Documents