18 Tellabs 8000 Network Manager R17A Third Party Hardware and Software Requirements

Tellabs ® 8000 Network Manager R17A
Third Party Hardware and Software Requirements
70002_18
12.02.2010
Document Information
Revision History
Document No. Date Description of Changes

70002_18 12.02.2010 Updated to R17A-SP3.
ThinClient Server RAM requirements edited in chapter 5.4.6.
Windows Server 2008 R2 (64-bit version) support added in
chapters 6.3.2, 6.3.3 and 6.3.4.
70002_17 27.11.2009 Updated to R17A-SP2.
The recommendation for the maximum number of workstations per
server for ThinClient Server has been updated in chapter 2.
Network Management Resilience Service data edited and hot
stand-by added in chapter 4.
Fig. 9 updated in chapter 6.
Data on tested computers edited in chapter 6.1.2.
Solaris 10 data updated in chapter 6.5.1.
HW data of Network Management Resilience Service updated in
chapter 6.8.1.
70002_16 30.09.2009 Updated to R17A-SP1.
Citrix Presentation Server has been renamed as Citrix XenApp in
chapters 2.17 and 5.4.6.
Data related to Tellabs 8800 updated in the node number
recommendation table in chapter 2.8.
Fig. 9 updated in chapter 6.
Requirement related to Windows Service Packs added in chapter
6.1.1.
IBM System x3550 M2 1U rack server, HP ProLiant ML350 G6
and HP ProLiant DL360 G6 added in and HP ProLiant ML350
G5 removed from chapter 6.1.2.
Management Server and Communication Server operating system
data updated in and Web Reporter Server data removed from
chapter 6.3.2.
Database Server operating system data updated and a 64-bit
software recommendation added in chapter 6.3.3.
ThinClient Server operating system and application server data
updated in chapter 6.3.4.
Sun SPARC Enterprise T5220, Netra T5220, Sun Fire V890, Sun
Fire V490 and Sun Netra 1290 replaced by Sun SPARC Enterprise
M4000 Server in chapter 6.5.1.
Unix Database Server software data updated in chapter 6.5.2.
DLT drive removed from the table in chapter 6.5.4.
© 2010 Tellabs. All rights reserved.
This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and international copyright laws, conventions and
treaties. Your right to use this manual is subject 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 following trademarks and service marks are owned by Tellabs Operations, Inc. or its affiliates in the United States and/or
other countries: TELLABS ®, TELLABS ® logo, TELLABS and T symbol ®, and T symbol ®.
Any other company or product names may be trademarks of their respective companies.
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.
Tellabs ® 8000 Network Manager R17A 70002_18

Third Party Hardware and Software Requirements © 2010 Tellabs.
2
Document Information
Terms and Conventions
Term Explanation
DCN Data Control Network
DNS Domain Name Service
IP Internet Protocol
LAN Local Area Network
OCNM Online Core Network Monitoring
RAID Redundant Array of Inexpensive Disks
TCP Transmission Control Protocol
WINS Windows Internet Naming Service
70002_18 Tellabs ® 8000 Network Manager R17A

© 2010 Tellabs. Third Party Hardware and Software Requirements
3
4
Table of Contents
Table of Contents
About the Manual .............................................................................................................. 8
Objectives....................................................................................................................................................................... 8
Audience......................................................................................................................................................................... 8
Related Documentation .................................................................................................................................................. 8
Documentation Feedback............................................................................................................................................... 8
1 General ......................................................................................................................... 9
2 Tellabs 8000 Network Manager System Configurations.......................................... 11
2.1 Tellabs 8000 Network Manager Standard Workstation....................................................................................... 13

2.2 Tellabs 8000 Network Manager Satellite Workstation ........................................................................................ 13
2.3 Tellabs 8000 Network Manager Power Workstation........................................................................................... 13
2.4 DXX Server (8100 Adapter)................................................................................................................................ 13
2.5 Database Server ................................................................................................................................................... 14
2.5.1 Off-line Database Kit for Reporting .................................................................................................... 14
2.6 Recovery Server .................................................................................................................................................. 14
2.7 Private Subnetwork Components ........................................................................................................................ 14
2.7.1 Management Server with Private Subnetwork Service ....................................................................... 15
2.7.2 Private Subnetwork Workstation ......................................................................................................... 15
2.8 Communication Server ........................................................................................................................................ 16
2.9 Management Server............................................................................................................................................. 17
2.9.1 Fault Service ........................................................................................................................................ 17
2.9.2 Web Reporter Service .......................................................................................................................... 17
2.9.3 Northbound Interface Service.............................................................................................................. 17
2.9.4 SLA Service ........................................................................................................................................ 17
2.10 Route Master........................................................................................................................................................ 18
2.11 Satellite Service ................................................................................................................................................... 18
2.12 Tellabs 8100 Service Computer........................................................................................................................... 18
2.13 Single Computer Configuration — Tellabs 8000 Manager in 8100 Mode.......................................................... 19
2.14 Dual Computer Configuration — Tellabs 8000 Manager in 8100 Mode ............................................................ 20
2.15 Single Computer Configuration for Tellabs 8600 Networks ............................................................................... 21
2.16 Dual Computer Configuration for Tellabs 8600 Networks ................................................................................. 21
2.17 Tellabs 8000 Network Manager ThinClient Solution.......................................................................................... 22
3 DCN, LAN and LAN-IC Requirements........................................................................ 23

5
Table of Contents
3.1 DCN for Tellabs 8600.......................................................................................................................................... 23

3.2 LAN Configuration.............................................................................................................................................. 24
3.3 LAN and LAN-IC................................................................................................................................................ 25
3.4 Networking Configuration................................................................................................................................... 26
4 Database Protection Levels ....................................................................................... 27
5 RAM and CPU Requirements for Tellabs 8000 Network Manager .......................... 30
5.1 Network Size ....................................................................................................................................................... 30

5.2 Database Servers.................................................................................................................................................. 30
5.2.1 Number of CPUs in Networks of Different Size ................................................................................. 30
5.2.2 Required Minimum RAM Size of Database Servers........................................................................... 31
5.3 Management Servers ........................................................................................................................................... 31
5.4 Other Hardware ................................................................................................................................................... 31
5.4.1 Required RAM Size of Other Hardware ............................................................................................. 31
5.4.2 SCC for Tellabs 8600 Networks RAM Requirement .......................................................................... 32
5.4.3 DCC for Tellabs 8600 Networks RAM Requirement ......................................................................... 32
5.4.4 SCC Configuration in 8100 Mode RAM Requirement ....................................................................... 33
5.4.5 DCC Configuration in 8100 Mode RAM Requirement....................................................................... 33
5.4.6 ThinClient Server RAM Requirement................................................................................................. 33
6 Hardware and Software Requirements for Tellabs 8000 Network Manager .......... 34
6.1 Computer Sets...................................................................................................................................................... 34

6.1.1 Minimum Requirements for Workstations .......................................................................................... 35
6.1.2 Tested Computers ................................................................................................................................ 35
6.2 Accessories .......................................................................................................................................................... 42
6.2.1 Accessories Set – X.25 Adapter for Windows .................................................................................... 42
6.2.2 USB to Serial Adapter ......................................................................................................................... 42
6.3 Software Sets ....................................................................................................................................................... 42
6.3.1 Workstation Software .......................................................................................................................... 43
6.3.2 Server Software – Management Server and Communication Server .................................................. 43
6.3.3 Database Server Software.................................................................................................................... 44
6.3.4 ThinClient Server ................................................................................................................................ 45
6.3.5 Replication Server Software................................................................................................................ 45
6.4 Displays ............................................................................................................................................................... 45
6.4.1 Workstation Display ............................................................................................................................ 45
6.4.2 Server Display ..................................................................................................................................... 46
6.5 Unix Server Sets .................................................................................................................................................. 46
6.5.1 Sun SPARC Enterprise M4000 Server ................................................................................................ 46
6.5.2 Unix Database Server Software........................................................................................................... 47
6.5.3 Route Master Software ........................................................................................................................ 47
6.5.4 Backup Tape Device ............................................................................................................................ 47
6.6 Preinstalled Computers........................................................................................................................................ 47
6.7 Minimum Requirements for Tellabs 8100 Service Computers ........................................................................... 47
6.8 Network Management Resilience Service........................................................................................................... 48

6
Table of Contents
6.8.1 Hardware ............................................................................................................................................. 48

6.8.2 Software............................................................................................................................................... 49

7
About the Manual
About the Manual
Objectives
Tellabs ® 8000 Network Manager Third Party Hardware and Software Requirements describes
all the needed third party software components and versions in the Tellabs ® 8000 network manager
system (operating systems, service packs, database server versions, client versions, web browsers).
It also describes the recommended computer platforms, LAN configurations and minimum
performance requirements for computers.
Audience
This manual is intended for system administrators and system specialists.
Related Documentation
Tellabs ® 8000 Network Manager R17A Provides detailed instructions on how Tellabs
Software Installation Manual (70170_XX) 8000 network manager and third party software
are installed on Tellabs 8000 network manager
computers.
Tellabs ® 8000 Network Manager R17A Describes Tellabs 8000 network manager
System Description (70168_XX) architectures, all major software applications and
key concepts of the software.
Tellabs ® 8000 Network Manager R17A Provides instructions on how to install and
Installation and Configuration Guide for configure Tellabs 8000 network manager servers,
Management Server, Route Master and Recovery route master and other components.
Server (70171_XX)
Web Reporter for Tellabs ® 8000 Network Provides instructions on installing the Web
Manager R17A Reporter tool.
Installation and Configuration Manual
(70185_XX)
Tellabs ® 8000 Network Manager R17A Provides instructions on installing and configuring
Installation and Configuration Guide for the Northbound Interface service of Management
Northbound Interface (70173_XX) Server of Tellabs 8000 network manager.
Documentation Feedback
Please contact us to suggest improvements or to report errors in our documentation:
Email: fi-documentation@tellabs.com
Fax: +358.9.4131.2430

8
1 General
1 General
The Tellabs ® 8000 network manager R17A is designed to use Windows XP, Windows Server
2003 and Windows Server 2008 (in limited configurations) operating systems and the Sybase
Adaptive Server Enterprise relational database. With this design it is possible to build a flexible
system that easily adapts to changes in a managed network and to changes in the organization of
network management tasks.
The different Tellabs 8000 network manager system configurations supported are:
• Single Computer Configuration (SCC)

• Dual Computer Configuration (DCC)
• Multi-User Tellabs 8000 network manager
For more detailed information about the different supported configurations, refer to Tellabs ® 8000
Network Manager Software Installation Manual and Tellabs ® 8000 Network Manager System
Description.
The Tellabs 8000 network manager can adapt to centralized or distributed management schemes,
and can grow when the needs of an operator develop. An operator can minimize start-up costs in a
smaller Tellabs network by managing their entire network with a Single-User system configuration.
When the needs of an operator and their network grow, new management workstations and servers
can be added at any time to build up to a Multi-User Tellabs 8000 network manager system
configuration.
The Tellabs 8000 network manager has two different installation modes:
• 8000 Manager Mode contains Tellabs 8000 network manager with support for Tellabs ® 8600
managed edge system, Tellabs ® 8100 managed access system, Tellabs ® 6300 managed transport
system, Tellabs ® 7100 optical transport system, Tellabs ® 7300 metro Ethernet switching series
and Tellabs ® 8800 multiservice router series nodes.
• 8100 Manager Mode contains Tellabs 8000 network manager without support for Tellabs 8600,
Tellabs 7100, Tellabs 7300 and Tellabs 8800 nodes.
Using 8100 Manager Mode for installation is recommended if there are no plans to install Tellabs
8600 system nodes to the network in the near future. This mode corresponds to the Tellabs
8100 manager installation. 8000 Manager Mode is recommended and even required in some
configurations if there is an existing Tellabs 8600 system network or if there are plans to install
Tellabs 8600 system nodes to the network.
In the same network management system, there can be computers installed in both modes, i.e. some
can be installed using 8000 Manager Mode and others using 8100 Manager Mode. An operator can
install up to 100 workstations in 8000 Manager Mode.

9
1 General
Tellabs 8000 network manager may work on other types of machine configurations than the
specified ones, but it cannot be guaranteed.
The requirements in this document apply to new purchases only. Tellabs also requires
existing customers to follow up with this document. When planning to change some part
of the Tellabs 8000 network manager system configuration, it is to be done according to
the requirements of this document.
Check that you always use the most recent version of this document.
Before updating the Tellabs 8000 network manager system, contact Tellabs Customer
Services.
It is recommended to use the latest version of the Norton (Symantec) antivirus program in
your workstations and servers. Norton may affect the performance of servers.
It is not allowed to use other than specified programs on your Tellabs 8000 network manager
servers. Using other programs requires written permission from Tellabs. Using other than
specified programs on your Tellabs 8000 network manager workstations is not recommended.

10
2 Tellabs 8000 Network Manager System Configurations
2 Tellabs 8000 Network Manager System

Configurations
In Tellabs 8000 network manager system configurations, the network manager components are
distributed over several obligatory or optional computers:
• Standard Workstation(s)
• Power Workstation(s)
• Satellite Workstation(s)
• DXX Server(s)
• Database Server
• Recovery Server(s)
• Private Subnetwork Workstation(s)
• Communication Server(s)
• Management Server(s)
• Route Master(s)
• 8100 Service Computer
Tellabs 8000 network manager can be configured depending on the size of the network, the number
of concurrent users and the type of nodes used. The different supported configurations are described
in Tellabs ® 8000 Network Manager Software Installation Manual and Tellabs ® 8000 Network
Manager System Description. As an example the Tellabs 8000 network manager components in a
multi-user environment is shown in the figure below.

11
Fig. 1 Example of Multi-User Tellabs 8000 Network Manager Configuration
It is recommended that all the Tellabs 8000 network manager server computers (Database Server,
DXX Servers, Recovery Server, Management Servers, Communication Servers and Route Masters)
are located in the same LAN segment to provide a more reliable operation. However, Tellabs 8000
network manager workstations can be distributed to different locations using routers.
See the hardware and software requirements in chapter 6 Hardware and Software Requirements
for Tellabs 8000 Network Manager.
The tables below show the recommendations for the maximum number of workstations and the
maximum number of workstations per server.
Recommendation for Maximum Number of Workstations

Type of Workstation Maximum Number of Workstations
Standard/Satellite Workstation in 100
8000 Manager Mode
Standard Workstation 200
Satellite Workstation 800
Power Workstation 10
Recommendation for Maximum Number of Workstations per Server

Type of Server Maximum Number of Workstations
Management Server 20

12
Type of Server Maximum Number of Workstations

Fault Server 20
Satellite Server 40
ThinClient Server 20
2.1 Tellabs 8000 Network Manager Standard Workstation
Tellabs 8000 network manager Standard Workstation functions as an access point to a Tellabs
8000 system network and its elements for an operator through a graphical user interface. Standard
Workstation is connected to the main management LAN. An operator can install up to 200 Standard
Workstations including a maximum of 100 workstations in 8000 Manager Mode.
2.2 Tellabs 8000 Network Manager Satellite Workstation
Tellabs 8000 network manager Satellite Workstation functions as an access point to a Tellabs
8000 system network and its elements for a remote operator through a graphical user interface.
The load on the system caused by one Satellite Workstation is about 25 per cent of that of one
Standard Workstation, so if you have no Standard Workstations the maximum number of Satellite
Workstations is 800 with 20 Management Servers.1
2.3 Tellabs 8000 Network Manager Power Workstation
A Power Workstation is running Standard Workstation software and some 8600 services in the
same PC connected to the main management LAN. One Tellabs 8000 network manager Power
Workstation functions as an access point to a Tellabs 8000 system network and its elements for an
operator through a graphical user interface. An operator can install up to 10 Power Workstations.
An operator can install up to 100 workstations (including Standard, Satellite and Power
Workstations) in the 8000 Manager Mode.
2.4 DXX Server (8100 Adapter)
DXX Server is used for managing Tellabs 8100 network elements. The number of required DXX
Servers depends on the size of the network. Each server takes care of one or several areas in
the network. Increasing the number of DXX Servers also increases the reliability of network
management.
1The maximum number of Standard Workstations is 200, four Satellite Workstations approximately equals one workstation, which follows that the
maximum number of Satellite Workstations is 800.

13
In a DXX Server one X.25 port is required per 250 subracks. A DXX Server can have a maximum
of four X.25 ports (using dual port X.25 cards) meaning a total of 1000 subracks. Normally this
means 700-800 nodes, depending on the number of Tellabs ® 8170 cluster nodes. When using
asynchronous links you can have two links with a maximum of approximately 50 subracks per link,
which means a total of 100 subracks. With four X.25 ports and two asynchronous links the total is
1100 subracks in a DXX Server. When using IP links you can have 250 subracks per IP link. A
single DXX Server can handle up to 1500 subracks.
If you have several NTUs (more than five) per node, take into account that it can slow down fault
polling if there are a lot of faults in the NTUs.
2.5 Database Server
The database hardware requirements vary according to the actual size of Tellabs 8000 system
network. In a Multi-User Tellabs 8000 network manager system configuration, either Solaris or
Windows servers can be used.
2.5.1 Off-line Database Kit for Reporting
The Off-line Database Kit for Reporting provides an off-line database which can be used as a
safe environment for making various kinds of analyses without disturbing the normal use of the
management system. It enables reporting and statistical calculations for link, network element
and NTU faults for several years. The fault history database reduces the need to store data in
the on-line database.
2.6 Recovery Server
The Recovery Server component is used for circuit and trunk protection. It is possible to have a
second Recovery Server for backup purposes.
The DXX Server and Recovery Server can be run in a common machine if the network size is up to
approximately 350 nodes and there are no other DXX Servers in the network.
2.7 Private Subnetwork Components
The Private Subnetwork is an optional feature. The Multi-User Tellabs 8000 network manager
system configuration with Private Subnetwork implemented is shown in Fig. 2.

14
Fig. 2 Private Subnetwork in Multi-User Tellabs 8000 Network Manager System Configuration
2.7.1 Management Server with Private Subnetwork Service
The Management Server with Private Subnetwork Service is installed on the management network
of the operator, where it provides communication to Private Subnetwork Workstations residing in
the customer premises. The maximum number of nodes in one Private Subnetwork is 1500. If the
Private Subnetwork feature is not used, the Private Subnetwork Service can be omitted.
2.7.2 Private Subnetwork Workstation
The Private Subnetwork Workstation component is installed in the customer premises via a router.
The Private Subnetwork Workstation communicates through a Management Server with Private
Subnetwork service, which resides in the management network of the operator.

15
2.8 Communication Server
Communication Server is used for managing e.g. Tellabs 8600, Tellabs 6300, Tellabs 7100, Tellabs
7300 and Tellabs 8800 network elements.
The number of required Communication Servers depends on the size of the network. A
recommendation for a maximum number of nodes per a single Communication Server is presented
in the table below. Each server takes care of one or several areas in a network and can run several
parallel adapters (e.g. Tellabs 8600, Tellabs 6300, Tellabs 7100, Tellabs 7300 and Tellabs 8800). It
is recommended to run the adapters in separate Communication Servers, especially if the number
of managed network elements is significant.
Marben OSIAM OSITP4 version 1.07.1.0 must be used if a Gigabit Ethernet adapter is used for
Tellabs 6300 network element communication.
Recommendation for Maximum Number of Nodes per Communication Server

Node Type Number of Nodes per Number of Nodes per
Communication Server with Communication Server without
PMS PMS
Tellabs 8660 edge 100 500
switch, or
Tellabs 8630 access 250 1000
switch, or
switch, or
switch, or
switch, or
Tellabs 8606 – 2500
Ethernet aggregator,
or
Tellabs 8800 MSR 100 500
nodes, or
Tellabs 7100 OTS, – 100
or
Tellabs 7100 Nano – 500
OTS, or
Tellabs 7300 nodes – 2000
Tellabs 6300 nodes 500 500
For example, a single Communication Server can handle up to 100 x Tellabs 8660 edge switch
nodes and 2000 x Tellabs 8605 access switch nodes without PMS, or 20 x Tellabs 8660 edge switch
nodes and 1600 x Tellabs 8605 access switch nodes with PMS.

16
These recommendations are general guidelines for dimensioning the Tellabs 8000 manager system.
The optimum number of Communication Servers needed for a network depends on the number of
nodes, the node inventories (the number and type of physical and logical interfaces), the set of PMS
counters monitored, the overall NMS activity (operations per second in the network), the fault
and performance polling targets etc.
2.9 Management Server
The Management Server functions as a framework for the different Tellabs 8000 manager
application logic. This application logic is divided into services each running a process of its own.
All the services can be run in the same server or different services can be located in different servers.
Some services can be run only in one server, whereas some can be run in different servers at the
same time so that they are backing up or load balancing each other.
The installation of the different server types is done by selecting the appropriate service for
Management Server in Tellabs 8000 Network Manager Setup Wizard.
One Management Server supports up to 20 Standard Workstations, depending on how the services
are distributed and used.
2.9.1 Fault Service
Fault service is a Management Server service that can run in one or more Management Servers
providing Fault services. The benefit of using a Fault service is that it offloads the Database
Server and the workstations. The Fault service should be used if Fault Management System is
used from more than one workstation. One Management Server with Fault Service supports
twenty workstations.
2.9.2 Web Reporter Service
The Web Reporter service component is used for the Web Reporter for Tellabs 8000 manager
reporting tool to provide information from the database. The Web Reporter tool requires a separate
license. For information on the required browser in the workstation see Web Reporter for Tellabs ®
8000 Network Manager Installation and Configuration Guide.
2.9.3 Northbound Interface Service
Northbound Interface service provides information and services for third party Operations Support
Systems (OSS). This includes information on network element faults, faulty circuits and customers
as well as services for executing Tellabs 8000 manager macros. See Tellabs ® 8000 Network
Manager Installation and Configuration Guide for Northbound Interface for details.
2.9.4 SLA Service
The SLA service component is used for calculating 24-hour G.826 performance history data for
TDM circuits and trunks in the network. Performance history data is calculated into the Tellabs
8000 manager database to be accessed through the Northbound Interface service. SLA service
requires a Performance Management license.

17
It is recommended to use a dedicated Management Server for SLA Service.

SLA Service must not be configured in more than one Management Server in the whole
Tellabs 8000 network manager system.
2.10 Route Master
Route Master contains the Online Core Network Monitoring (OCNM, a Tellabs proprietary feature)
function for Tellabs 8600 networks. The Route Master is optional software component running
on Linux.
The OCNM function is used for auto-discovering the topology of the MPLS core network, and for
monitoring the bandwidth reservation status of the links in both the core and the access networks.
OCNM stores this data into the Tellabs 8000 manager database, where they can be viewed with the
Tellabs 8000 manager tools.
Route Master can be used if the operator wants to use Online Core Network Monitoring for
auto-discovering the core MPLS network topology and for monitoring the bandwidth reservation
status of links.
When using the Route Master function the corresponding front end services shall be configured
to Management Server by using Network Manager Setup Wizard. See Tellabs ® 8000 Network
Manager Installation and Configuration Guide for Management Server, Route Master and Recovery
Server for details.
2.11 Satellite Service
Satellite service and Satellite Workstation offer better throughput and system performance.
Management Server running Fault service should be used when using the Fault Management System
in Satellite Workstations. See Tellabs ® 8000 Network Manager Installation and Configuration
Guide for Management Server, Route Master and Recovery Server for details.
One Management Server with Satellite service can support a maximum of 40 Satellite Workstations.
When the maximum number of Satellite Workstations is supported, no other services can be
configured in the same Management Server.
2.12 Tellabs 8100 Service Computer
Tellabs 8100 Service Computer (SC) is used for monitoring and controlling the operation of a single
Tellabs 8100 system node. The only Tellabs 8000 network manager user interface component
installed on SC is Node Manager for Tellabs 8100 nodes.
You can install the Tellabs 6300 Craft Terminal version 3.0.2, which is used for controlling network
elements of the Tellabs 6300 system, in the same computer as the SC. If you use the serial port for
communication, only one of the 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.

18
2.13 Single Computer Configuration — Tellabs 8000 Manager in 8100

Mode
The Single Computer Configuration (SCC) Tellabs 8000 network manager is a system in which the
Tellabs 8000 manager workstation, DXX Server and Tellabs 8000 manager database are all installed
in one computer. The Single Computer Configuration Tellabs 8000 network manager is typically
used to manage small networks up to several tens of Tellabs 8100 nodes (50 nodes maximum).
Fig. 3 Single Computer Configuration Tellabs 8000 Manager System Configuration in 8100
Mode
Note that the Recovery Server function is not included in this system configuration. Communication
Server cannot be set up in the same PC as SCC. This means that you need a separate computer in
addition to SCC for managing Tellabs 6300 managed transport system or third party nodes.
The Single Computer Configuration in 8100 mode can be used in networks containing only
Tellabs 8100 system nodes.

19
2.14 Dual Computer Configuration — Tellabs 8000 Manager in 8100

Mode
The Dual Computer Configuration (DCC) Tellabs 8000 network manager is a system in which
Tellabs 8000 manager workstation and DXX Server are installed on one computer and Tellabs
8000 manager database is installed on another. The Dual Computer Configuration Tellabs 8000
network manager is typically used to manage small networks up to a couple of hundred Tellabs
8100 nodes (400 nodes maximum).
Fig. 4 Dual Computer Configuration Tellabs 8000 Manager System Configuration in 8100 Mode
Note that the Recovery Server function is not included in this configuration.
The Dual Computer Configuration as such can be used only when 8100 manager installation
mode has been used and there are only Tellabs 8100 nodes in the network.

20
2.15 Single Computer Configuration for Tellabs 8600 Networks
The Single Computer Configuration (SCC) for Tellabs 8600 networks is a system in which the
Tellabs 8000 manager workstation, Management Server, Communication Server and database are all
located in one computer. The SCC for Tellabs 8600 network configuration supports up to 50 Tellabs
8600 system nodes. Only Tellabs 8600 system nodes are supported in this configuration.
Fig. 5 Single Computer Configuration for Tellabs 8600 Networks
The Single Computer Configuration in 8000 mode can be used in networks containing only
Tellabs 8600 system nodes.
2.16 Dual Computer Configuration for Tellabs 8600 Networks
The Dual Computer Configuration (DCC) for Tellabs 8600 networks is a system in which the
Tellabs 8000 manager workstation, Management Server and database are all located in one
computer and Communication Server is installed on another. The DCC for Tellabs 8600 network
configuration supports up to 500 Tellabs 8600 system nodes. Only Tellabs 8600 system nodes
are supported in this configuration.

21
Fig. 6 Dual Computer Configuration for Tellabs 8600 Networks
The Dual Computer Configuration as such can be used only when 8000 manager installation
mode has been used and there are only Tellabs 8600 nodes in the network.
2.17 Tellabs 8000 Network Manager ThinClient Solution
Tellabs 8000 network manager ThinClient is a solution that replaces Tellabs 8000 standard or
satellite workstation with a client/server application which saves bandwidth, simplifies upgrades and
maintenance, and provides flexible remote access. ThinClient solution is based on Citrix XenApp
which has previously been referred to as Citrix Presentation Server. One ThinClient Server can
support the maximum of twenty concurrent users.

22
3 DCN, LAN and LAN-IC Requirements
3.1 DCN for Tellabs 8600
An inband or outband DCN (Data Control Network) can be used between Tellabs 8000 manager
and Tellabs 8600 nodes. In the figure below a reference mobile transmission network is described
for DCN dimensioning. For a typical network (as shown in the figure below), the recommended
DCN bandwidths are at least:
• 10 Mbit/s to core nodes,

• 1 Mbit/s to hub nodes (aggregating up to ten cell sites), and
• 256 kbit/s to cell site nodes (128 kbit/s without PMS).
Fig. 7 Mobile Transmission Network

23
3.2 LAN Configuration
It is recommended that the LAN is dedicated to Tellabs 8000 network manager computers. When
building an Ethernet LAN for Tellabs 8000 network manager, special attention should be paid to the
connections between servers. A main management LAN interconnects the Database Server and
various Tellabs 8000 network manager servers.
Below is a figure of the main management LAN and some requirements for it.
• Ethernet bandwidth of at least 100 Mbit/s is required.

• Switch-based technology is required.
• The main management LAN should be dedicated for use with Tellabs 8000 network manager
only.
Fig. 8 Tellabs 8000 Network Manager Main Management LAN

24
There are some requirements for the LAN configuration:
• Standard Workstation down-link

• Segment(s) of LAN that interconnect workstations to the main management LAN
• Requires Ethernet bandwidth equal to or greater than 100 Mbit/s
• Hubs can be used, but switches are preferred
• Satellite (or Private Subnetwork) Workstation down-link
• Segment(s) of LAN that interconnect remote workstations to the Management Server
• Hubs can be used
• Every computer having a database connection (Standard Workstations, Power Workstations and
all Servers) should have reliable and error free network connection
• Note that one such computer behind slow database connection will slow down the whole
network management system.
3.3 LAN and LAN-IC
It is possible to connect workstations to servers from remote locations using TCP/IP. In such a case
the communication link capacity between the locations should be as recommended in the following
table. These capacities guarantee a reasonable workstation startup time, depending on the size of the
network. It is assumed that only one workstation is started up at a time.
Recommendations for communication link capacity between Satellite or Private Subnetwork

Workstations and the main management LAN, based on workstation startup time
Maximum Number of Network Elements in Minimum Communication Link Capacity
the Network (kbit/s)
1000 512 kbit/s
> 1000 1 Mb
> 10000 2 Mb
> 30000 4 Mb
The capacity should be reserved as specified above even if there is only one workstation in a remote
location. However, if there are several workstations in a remote location, the link capacity must be
set at least to the values listed in the following table.
Recommendations for communication link capacity between Satellite or Private Subnetwork

Workstations and the main management LAN, based on the number of workstations in
remote LAN
Number of Workstations in Remote Minimum Communication Link Capacity
Location (kbit/s)
1-3 512
4-10 2 Mb
11-20 4 Mb

25
The capacity must be selected as the maximum of the capacities based on the workstation startup
time and number of workstations in a remote location.
The communication links between the locations must be reliable, as the quality of these links shall
be better than 99.99% in Error-Free Seconds. If the quality of communication links is worse than
required, Tellabs cannot guarantee that Tellabs 8000 network manager or its parts work efficiently.
3.4 Networking Configuration
It is highly recommended to use the Windows domain network model when more than ten computers
are used for network management.
For ease of administration of the computers, the servers and workstations should be connected to
a 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, the
user 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 the
management LAN, or if the users are using the same username and password.
It is also recommended to have WINS (Windows Internet Naming Service) and/or DNS (Domain
Name Service) servers running in the LAN. These servers provide name resolution services to other
computers in the network, so that they can resolve computer names into an IP address that enables
computers on a network to find one another and transfer information. The name resolution services
should not be running in any of the dedicated Tellabs 8000 network manager servers. Separate
servers are needed. All servers must have fixed IP addresses.

26
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. Frequency
of transaction dumps should be set according to the level of network activity. This also defines
the risk level in case of failures. Taking database dumps is the only way to restore the previous
database state e.g. in case of human errors.
• Mirrored disk drives. Mirroring provides protection against hard disk failures. It means using
redundant disks in Database Server. Raid level 1 is recommended. Raid level 5 should not be
used unless the disk array contains hardware raid controller.
• 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 directly
from the server supplier.
• Network Manager Resiliency Service (NMRS) is currently available in cold, warm and hot stand-
by.
• Cold stand-by means having an inactive spare Database Server with ready configurations.
• Warm stand-by is a resiliency 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 stand-by is a resiliency service, which transfers connections from the main database to
the replicated backup database automatically in a case of failure. The automatic transfer
does not cause any traffic outages. However, it can be noticed as a short delay in the Tellabs
8000 manager usage.
When planning a Network Management Resiliency Service, contact your Tellabs

representative. Before purchasing or installing any Network Management Resiliency Service,
the exact supported software version numbers and the latest details need to be checked
from Tellabs.

27
Sched- Mirrored Cluster- Cold Warm Hot

uled Disk ing Stand-by Stand-by Stand-by
Database Drives
Dumps
Obliga- Obligatory Obligatory Optional Optional Optional Optional
tory / op-
tional
Distance Unlimited Within the 8 m - 15 km Unlimited Unlimited Unlimited
between server depending with with
primary on the NMRS NMRS hot
and back- cable warm stand-by
up server media stand-by
Failover: Manual Automatic Auto- Manual Manual Automatic
automatic matic/man-
/ manual ual
Recovery Time of Real time Start-up Time of Time of Real time,
time restoring time of the restoring starting some
the database the Tellabs latency
database software database 8000 depending
dumps dumps system on the
some connection
latency between
depending the servers
on the
connection
between
the servers
Back-up Transac- Disk I/O Disk I/O Transac- Transac- Transac-
level tion level, and virtual tion level, tion level tion level
frequency server host frequency
of trans- of trans-
action log action log
dumps dumps
Loss in Database No loss No loss Database Unfinished Unfinished
case of modifi- modifi- transac- transac-
failure cations cations tions tions
done af- done af-
ter the last ter the last
transaction transaction
dump dump
Config- Disk Separate Identical Disk Identi- Identi-
uration space and disk drives Database space and cal Data- cal Data-
require- separate Server separate base Server base Server
ments back-up hardware, back-up hardware, hardware,
media (e.g. shared media (e.g. a con- a con-
a tape) disk array a tape). nection nection
system, Identical between between
cluster Database Database Database
software Server Servers, Servers,
hardware, Replica- Replica-
a tion Server tion Server,
connection Open
between Switch
the servers. Servers

28
Sched- Mirrored Cluster- Cold Warm Hot

uled Disk ing Stand-by Stand-by Stand-by
Database Drives
Dumps
Additional Dumps None Ordered Dumps Two Two
require- must be from Sun. must be trained trained
ments tested A prereq- tested Replica- Replica-
regularly uisite from regularly tion Server tion and
Sun: two in the cold administra- OpenSwitch
trained back-up tors. Auto- Server
cluster ad- matic mon- adminis-
ministra- itoring for trators.
tors. system. Automatic
monitoring
for system.
Supported Windows, Windows, Solaris Windows, Win- Solaris
database Solaris Solaris Solaris dows/Linux
platforms See
limitations.
Solaris
May Yes No Yes Yes Yes No
require
starting
other
Tellabs
8000
manager
servers

29
5 RAM and CPU Requirements for Tellabs 8000 Network Manager
5 RAM and CPU Requirements for Tellabs 8000

Network Manager
The recommendations in this chapter regarding memory apply to Tellabs 8000 network manager
R17A with Windows XP, Windows Server 2003 and Windows Server 2008.
5.1 Network Size
The RAM and CPU requirements in the hardware depend on the actual network size. To make
reading easier, the network size is here indicated as number of nodes. The number of other objects
may also have an impact on the required hardware. For example, below it is supposed that there are
on average 5 NTUs per node. If you have more than 5 NTUs per node, use the following formula:
number of NTUs/5 = number of nodes. For example, if you have a network with 1 000 nodes and
there are 10 000 NTUs, the requirements will be as for a network with 2 000 nodes.
A maximum of 30 000 Tellabs network elements (including Tellabs 8100, Tellabs 8600, Tellabs
6300, Tellabs 7100, Tellabs 7300 and Tellabs 8800 nodes) are supported in R17A.
5.2 Database Servers
The Database Server hardware requirements (e.g. RAM size, the number of CPUs and number of
disks) vary according to the actual Tellabs 8000 system network size. The number of workstations
and management computers accessing the Database Server also has an impact on the requirements.
See a summary of these requirements in the tables below, and also refer to 6 Hardware and Software
Requirements for Tellabs 8000 Network Manager.
If performance history data collection for Tellabs 8600 network elements is going to be used,
contact your Tellabs representative for more detailed information about Database Server
requirements.
5.2.1 Number of CPUs in Networks of Different Size
To ensure better performance when the network size grows, extra CPUs with the recommended
Database Servers are needed. This is illustrated in the table below.

30
5.2.2 Required Minimum RAM Size of Database Servers
Number of Nodes 1-1000 1000-5000 5000 - 30000

in the Network
PC-based Database 4 GB 8 GB Unix platform

Server RAM size (MB) recommended
Unix-based Database 4 GB 8 GB 16 GB
Server RAM size (MB)
See chapter 6 Hardware and Software Requirements for Tellabs 8000 Network Manager for UNIX
and Windows based Database Servers as well as the High Availability solutions.
5.3 Management Servers
The required minimum amount of RAM in Management Servers is 4 GB.
5.4 Other Hardware
5.4.1 Required RAM Size of Other Hardware
The RAM requirements are approximations for normal usage. Depending on which applications are
used the memory consumption varies.
Minimum amount of RAM (MB)

Number of Nodes in the Network
Hardware < 3000 3000-10000 10000 - 30000
Standard Workstation 512 512 >1 GB
in the 8100 Mode2
2 Note that the use of several sessions requires considerably more RAM in the workstations than the use of just one session. Using Tellabs 6300 Craft
Terminal in the same workstation as Tellabs 8000 network manager workstation requires 512 MB additional RAM.

31
Number of Nodes in the Network

Hardware < 3000 3000-10000 10000 - 30000
Standard Workstation 1 GB 2 GB 2 GB
in the 8000 Mode
Satellite Workstation 256 512 512
in the 8100 Mode
Satellite Workstation 1 GB 2 GB 2 GB
in the 8000 Mode
Power Workstation 2 GB 3 GB 3 GB
Private Subnetwork 512 512 512
Workstation
DXX Server 512 512 >1 GB
Communication Server 1 GB 2 GB 2 GB
Recovery Server 512 512 >1 GB
Private Subnetwork 512 1 GB >2 GB
Service3
Web Reporter Service 512 512 >1 GB
Fault Service / Satellite 1 GB 2 GB >2 GB
Service
Northbound Interface 512 1 GB 2 GB
Service
Route Master 1 GB 2 GB 2 GB
Multiple processors are recommended for all computers in a network of over 20 000 network
elements. Multiple processors also improve performance in smaller networks. Having two
processors is a requirement for all servers in a network of over 20 000 network elements.
5.4.2 SCC for Tellabs 8600 Networks RAM Requirement
In an SCC for Tellabs 8600 networks configuration the Tellabs 8000 manager workstation,
Management Server, Communication Server and database are all located in one computer. The
minimum RAM requirement for that machine is 4 GB. A multi-processor computer is required
in this configuration.
5.4.3 DCC for Tellabs 8600 Networks RAM Requirement
In DCC configuration for Tellabs 8600 networks the Tellabs 8000 manager workstation, Management
Server and Database Server are located in one computer. The minimum RAM requirement for that
machine is 4 GB. Communication Server is located in a dedicated computer and the minimum RAM
requirement for that machine is 1 GB. Multi-processor computers are required in this configuration.
3A large number of Private Subnetwork trunk events (in the vpntrunkevent table) increases RAM usage.

32
5.4.4 SCC Configuration in 8100 Mode RAM Requirement
The SCC configuration consists of one computer, which has the Database Server, workstation and
DXX Server in the same computer. The RAM requirement in the SCC computer is at minimum
2 GB.
5.4.5 DCC Configuration in 8100 Mode RAM Requirement
The DCC configuration consists of two computers, one Database Server and one Combined
workstation and DXX Server. The RAM requirement in the Database Server hardware is shown in
chapter 5.2.2 Required Minimum RAM Size of Database Servers and the RAM requirement in the
Combined workstation and DXX Server hardware is at minimum 2 GB.
5.4.6 ThinClient Server RAM Requirement
ThinClient Server executes Citrix XenApp and parallel user sessions of Tellabs 8000 network
manager standard or satellite workstation. The RAM requirement in the ThinClient Server
computer is at minimum 4 GB. If more than ten workstations are connected to the server 16 GB is
recommended.

33
6 Hardware and Software Requirements for Tellabs 8000 Network Manager
6 Hardware and Software Requirements for

Tellabs 8000 Network Manager
Fig. 9 Recommended Software and Computer Types for Each Setup
Hardware-based disk mirroring (RAID 1) should be used in Database Servers.
6.1 Computer Sets
The Tellabs 8000 network manager software has been tested to run on the computer types mentioned
below. Preinstalled computers are available from Tellabs. These ready-to-run computers are
delivered with the required third party software installed (e.g. Windows and Sybase). These
computers are tested with a Tellabs 8000 system network before shipping. Note that the required
licenses need to be ordered separately in accordance to the customer specific Tellabs 8000 manager
setup. For the Unix machines, contact your Tellabs representative.

34
6.1.1 Minimum Requirements for Workstations
The Tellabs 8000 network manager workstation (Standard, Satellite and Power Workstation)
software will run on desktop computers which meet the specifications listed below. Tellabs 8000
network manager may work on other types of machine configurations than the ones presented in
this document, but it cannot be guaranteed. In case of problems with other computer types, the
vendor of the equipment should be contacted. Note that for servers you should use the specified
computer models. Windows Server 2003 R2 or 2008 with the latest service packs and critical
updates should be installed.
The general requirements for workstations are:
• A desktop computer designed for Microsoft Windows XP

• Manufacturer provided hardware drivers
Minimum performance requirements are:
• Intel Pentium IV processor

• The amount of RAM is dependent on the size of network. (The minimum amount of required
RAM should be checked from the table in chapter 5.4.1 Required RAM Size of Other Hardware.)
• A display adapter capable of 1280 x 1024 resolution with 16-bit color depth is recommended
• 20 GB hard disk or bigger
• An Ethernet adapter with a capacity of 100 Mbit/s.
Keep in mind that the processor clock speed and the amount of RAM affects the performance
of the computer. For better performance, select your workstations among the latest
computer models. Using slow management workstations may affect the performance of
other workstations as well.
6.1.2 Tested Computers
Note that you should use the specified computer models for servers. For workstations other models
can also be used as long as the requirements above are followed.
IBM System x3200

Computer model IBM System x3200
Processors Dual Core Intel ® Pentium ® D 915 or Quad Core
RAM See chapter 5 RAM and CPU Requirements for Tellabs 8000
Network Manager.
Hard disk Two 3.5" slim-high bays for hot-swappable SAS HDD
Drives Ultrabay Enhanced: CD or CD/DVD

LAN adapter Broadcom BCM5721 10/100/1000 on system board
LAN adapter (optional) NetXtreme 1000 T+ Dual-Port PCI-X 1GbE

35
Display controller ATI ES 1000 video on system board. 16 MB SDRAM video

memory.
Expansion slots Three PCI 32-bit/33MHz, one PCI Express x1, one PCI Express x8
Serial ports 2
LAN adapter for Tellabs 6300 10/100 Mbps LAN adapter. Gigabit LAN adapters are not
node communication supported.
IBM System x3250

Processors One Intel LGA 775 Xeon 3000 series, Pentium D or Celeron D
Network Manager.

LAN adapter Two Broadcom NetXtreme gigabit Ethernet interfaces
Display controller ATI ES 1000 video on system board. 16 MB DDR video memory.
Expansion slots Two PCI Express x8 slots, one low-profile and one ¾-length full
height. One Eicon PCI Express x8
Serial ports 1
IBM System x3400

Processors Intel Quad-Core Xeon
Network Manager.
LAN adapter Broadcom 5721 10/100/1000 on system board

LAN adapter (optional) NetXtreme 1000 T+ Dual-Port PCI-X 1GbE
memory.
Expansion slots Three PCI Express x8, one PCI 32-bit/33 MHz, two PCI-X
64-bit/133MHz
Serial ports 2

36
IBM System x3500

Processors 1 or 2 Intel Quad-Core Xeon
Network Manager.
Integrated ServeRAID-8k
LAN adapter Dual LAN adapter Broadcom 5721 10/100/1000 on system board
memory.
Expansion slots Three high-speed PCI-E and two PCI-X adapter slots offer
potential investment protection by supporting high-performance
adapters, such as 10Gb Ethernet, Fibre Channel and InfiniBand
cards, none of which will run in older 33MHz and 66MHz
conventional PCI slots.
Serial ports 2
IBM System x3550 M2 1U Rack Server for Management Server

Computer model IBM System x3550 M2
Processors 1 or 2 Quad-core Xeon or Dual-core Xeon
Network Manager.
Hard disks Two 2.5" hot-swap SAS/SATA
Drives Ultrabay Enhanced CD-RW/DVD Combo
LAN adapter Two Broadcom BCM5709 gigabit Ethernet interfaces

Display controller ATI Radeon ES1000 video on system board. 16 MB SDRAM
video memory
Expansion slots Two x16 PCIe slots (5GBps)
Serial ports 1
IBM System x3650 2U for Database Server

Processors 1 or 2 Intel Quad-Core Xeon
Network Manager.
Hard disks 8 x IBM xSeries 146GB 2,5" 10k U320 HS SAS hot-swap plug
hard drive (when 1+1 mirrored)
Drives (default) CD-RW / DVD-ROM drive
LAN adapter Default: Dual Gigabit Ethernet Controllers (2x Broadcom

BCM5708)

37
Display controller Default: ATI Radeon ES1000, 16MB SDRAM

Storage controller ServeRAID-8k-l (32MB cache, 400MHz DDR2)
standard—internal SAS
Expansion slots 4 x PCI-E
Tape backup device 80/160 GB Half High VS160 Tape Drive (SCSI)
HP ProLiant ML350 G6 for Management Server4

Computer model HP ProLiant ML350 G6, Base Model
Processors 1 or 2 Intel Xeon Quad Core
Network Manager.
Hard disks Hot-Swappable SAS HDD
Drives (default) CD-ROM drive
LAN adapter Default: NC373i Multifunction Gigabit Server Adapter
Display controller Default: ATI ES1000 Video Controller with 16 MB SDRAM
Video Memory
Expansion slots 3 x PCI-X, 3 x PCI Express
Serial ports 1
Accessories
LAN adapter for Tellabs 8100, HP NC7771 Gigabit Server Adapter
Tellabs 8600 and Tellabs 8800
network element communication
Rack mount kit Optional: HP ML350 G6 Tower to Rack Conversion Kit
HP ProLiant ML350 G6 for Database Server

RAM 6 GB or 12 GB. See chapter 5 RAM and CPU Requirements for
Tellabs 8000 Network Manager.
Hard disks 8 x Hot-Swappable SAS SFF HDD 1 + 1 mirrored)
Drives (default) DVD-ROM drive
LAN adapter 2 Gigabit Ethernet adapter (NC326i Dual ports Gigabit Network
Adapter W/O TOE)
Display controller Ati RN50, 64 MB video standard
Storage controller HP Smart Array P410i SAS/SATA controller
Expansion slots 1 x PCI Express Gen 2 x16 (x8 speed), 1 x PCI Express Gen 2 x8
(x8 speed), 4 x PCI Express Gen 2 x8 (x4 speed)
Tape backup device Optional:
HP 2 x PCI-X
Storageworks 100 MHz
VS160 (replaces
Internal 1 x PCI Express slot)
DLT drive
4Note that HP ML350 G6 has only one physical COM port. Another asynchronous port is available using a USB to serial adapter.

38
Accessories
Rack mount Optional: ProLiant ML350 G6 Tower-to-Rack Conversion Kit
HP ProLiant ML350 G6 for Recovery Server and Communication Server

Processors 1 or 2 Intel Xeon Quad-Core or Dual-Core
Network Manager.
Hard disks Hot plug SFF SAS
Drives (default) HP Half-Height SATA DVD-ROM Optical Drive
LAN adapter Default: NC326i Dual ports Gigabit Network Adapter W/O TOE
Display controller Default: Integrated ATI RN50, 64MB video standard
Storage controller HP Smart Array E200i/128 BBWC Controller
Expansion slots 1 x PCI Express Gen 2 x16 (x8 speed), 1 x PCI Express Gen 2 x8
(x8 speed), 4 x PCI Express Gen 2 x8 (x4 speed)
Serial ports 1
HP ProLiant DL360 G6 for DXX Server and Communication Server5

Computer model HP ProLiant DL360 G6
Form factor Rack mountable, 1U
Network Manager.
Hard disks Hot-Swappable SAS HDD
Drives (default) CD-ROM drive (default: NONE)
LAN adapter Default: NC373i Multifunction Gigabit Server Adapter, 2 ports
Display controller Default: Integrated ATI ES1000
Expansion slots 2 x PCI-Express
Serial ports 1
Accessories
Conversion kit for Eicon adapter HP DL36X PCI-X conversion kit (405154-B21)
HP ProLiant DL360 G6 for Management Server

Computer model HP ProLiant DL360 G6
Form factor Rack mountable, 1U
5Note that HP DL360 G6 can accommodate only one Eicon S94 adapter with PCI-X bus. A PCI-X conversion kit is required in order to install the
Eicon adapter. Also note that HP DL360 G6 has only one physical COM port. Another asynchronous port is available using a USB to serial adapter.

39
Processors 1 or 2 Intel Xeon Quad-Core or Dual-Core

Network Manager.
Hard disks Hot plug SFF SAS, Hot plug SFF SATA
Drives (default) CD-ROM drive (default: NONE)
LAN adapter Default: NC382T Dual Port Multifunction Gigabit Network
Adapters
Display controller Default: Integrated ATI ES1000, 32MB video standard
Expansion slots Two PCI-Express Gen 2 expansion slots: (1) full-length, full-height
slot; (1) low-profile slot
Serial ports 1
Accessories
Conversion kit for Eicon adapter HP DL36X PCI-X conversion kit (405154-B21)

Computer model HP ProLiant DL380 G5, Base Model
Processors 1 or 2 Intel Xeon Dual Core or Quad Core
Network Manager.
Hard disks Hot plug 2.5-inch SAS or Hot plug 2.5-inch SATA
Drives CD-ROM drive
LAN adapter Default: 2 x NC373i Multifunction Gigabit Server Adapter
Display controller Default: ATI ES1000, 32MB

Expansion slots 3x PCI-E
Serial ports 1
HP ProLiant DL380 G5 2U for Database Server

Computer model HP DL380R05 QC 2P/8M 4G P400 PERF
Processors 1 or 2 Intel Quad Core Xeon
Network Manager.
Hard disks 8x HP 145 GB 10krpm SAS 2,5" Hot Plug hard drive (when 1+1
mirrored)
Drives (default) CD-ROM drive
LAN adapter Default: 2 Embedded NC373i Multifunction Gigabit Network
Adapters with TCP/IP Offload Engine
Display controller Default: Integrated ATI ES1000, 32MB video standard

40
Storage controller HP Smart Array P400/512MB BBWC Controller (RAID

0/1/1+0/5/6)
Expansion slots 1x PCIe, 2 x PCI-X 64-bit/133MHz
Tape backup device HP StorageWorks SAS DLT Tape Drives for non-mirrored system,
External6
HP StorageWorks USB DAT Tape Drives for 4+4 mirrored system,
External

Computer model HP ProLiant DL580 G5, Base Model
Network Manager.
Smart Array P400i, RAID 0,1,5
Hard disks Hot plug 2.5-inch SAS or Hot plug 2.5-inch SATA
Drives DVD-ROM drive
LAN adapter Default: 2 x NC373i Multifunction Gigabit Server Adapter
Display controller Default: ATI ES1000, 32MB

Expansion slots http://h18000.www1.hp.com/products/quick-
specs/12770_na/12770_na.pdf
Serial ports 1
HP Blade System c7000

Enclosure HP BladeSystem c7000 Enclosure
Computer model HP ProLiant BL460c
Processors 1 or 2 Dual Core Intel Xeon, 5100 series
Network Manager.
Hard disks HP 2,5" SAS Hot Plug
Drives (default) N/A
CD-ROM drive (default) N/A

Expansion slots7 Two additional I/O expansion slots for mezzanine card
LAN adapter Two integrated single port NC373i Multifunction Gigabit Server
Adapters
LAN communication HP BLC 1 GB Enet Pass Thru Mod Option kit (16 ports) or HP
GbE2c 16 Port Gigabit Ethernet Blade Switch (410917-B21)
6Connecting hard drive cage and SAS tape to the same SAS Controller using split cable (supplied with tape drive) deactivates 1 of the hard drive
bays. Actual hard drive bay deactivated depends on where split cable plugs into SAS drive connector. Example: 3x SAS cable connector plugged
into SAS drive connector (5-8) on the back of the hard drive cage would mean drive bay 8 is deactivated.
7You cannot use an Eicon adapter in a Blade server.

41
Display controller Integrated ATI RN-50 1600x1280x64K 16M color (32 MB DDR1
memory)
Power supply units According to the number of Blade servers
FAN units According to the number of Blade servers
Accessories
Mezzanine card Two additional I/O expansion slots (e.g. 3rd LAN port) via
mezzanine card
Pass Thru Module for the second HP BLC 1 GB Enet Pass Thru Mod Option kit or HP GbE2c 16
LAN port8 Port Gigabit Ethernet Blade Switch (410917-B21)
6.2 Accessories
6.2.1 Accessories Set – X.25 Adapter for Windows
Eiconcard for X.25 Eiconcard S94 (310-208)

Eiconcard S94/66 (310-828)
Eiconcard S94 V2 (306-296) Revision 50
Eiconcard S94 PCI Express (306-298)
Eicon support Eiconcard Connections for Windows V6R7 for XP, Vista, Server
2003 and Server 2008 (32-bit and 64-bit versions) are included in
Tellabs 8000 Network Manager installation DVD.
6.2.2 USB to Serial Adapter
USB to serial adapter Targus - connectivity series, USB to Serial (RS232) Adapter
6.3 Software Sets
Tellabs 8000 network manager R17A supports Windows XP, Windows Server 2003 and Windows
Server 2008 operating systems. Solaris is supported for Database Server and Linux for Route Master.
8An optional 16 port Pass Thru Module kit or a switch is required for LAN communication outside the Blade enclosure. One 16-port Pass Thru
Module or switch provides only one external LAN port for each Blade server. If you need to take another LAN port into use in one or more servers,
another Pass Thru Module or switch is required. If you need to use a 3rd LAN port, a third Pass Thru Module/switch and a mezzanine card in the
Blade server is required. The LAN ports of the Pass Thru Module can be connected only to a Gigabit (or 10/100/1000) port of an Ethernet switch or
router. The Ethernet Blade Switch can be connected to 10, 100 or 1000BASE-T port.

42
6.3.1 Workstation Software
Operating system with Tellabs Windows XP Professional, English + Service Pack 2

8000 manager R17A Or
Windows XP Professional, English + Service Pack 3
Note that the x64 version is not supported.
Database connection with Tellabs Sybase CTISQL Utility/15.0/P-EBF13563 ESD #4/PC
8000 network manager R17A Intel/BUILD1500-073/OPT/Wed Apr 26 23:02:46 2006
Or
Sybase CTISQL Utility/15.0/P-EBF14167 ESD #7/PC
Intel/BUILD1500-093/OPT/Wed Dec 13 20:04:04 2006
Software for reading help files in Adobe Acrobat Reader 6.0 or later with search capability.
Tellabs 8000 network manager
R17A
6.3.2 Server Software – Management Server and Communication Server
Operating system with Tellabs Windows Server 2003 + Service Pack 2 (32-bit or 64-bit version)
8000 network manager R17A Or
Windows Server 2003 R2 + Service Pack 2 (32-bit or 64-bit
version)
Or
Windows Server 2008 + Service Pack 2 (64-bit version)
Or
Windows Server 2008 R2 (64-bit version)
Or
Communication Server with Marben OSIAM OSITP4, version 1.07.1.0
Tellabs 6300 Adapter Note that the 64-bit version is not supported.
The Windows Server 2008 operating system is not supported in Communication Server with
Tellabs 6300 Adapter.

43
6.3.3 Database Server Software
Operating system Windows Server 2003 + Service Pack 2 (32-bit or 64-bit version)
with Tellabs 8000 Or
network manager Windows Server 2003 R2 + Service Pack 2 (32-bit or 64-bit version)
R17A Or
Or
Database server Adaptive Server Enterprise/15.0.2/EBF 15683
software with ESD#5 (32-bit)
Tellabs 8000 Adaptive Server Enterprise/15.0.2/EBF 15683 ESD#5/P/NT
network manager (IX86)/Windows 2000/ase1502/2528/32-bit/OPT/Tue Jun 17
R17A 09:13:11 2008
Or
Adaptive Server Enterprise/15.0.2/EBF 15688
ESD#5 (64-bit)
ESD#5/P/X64/Windows Server/ase1502/2528/64-bit/OPT/Tue
Jun 17 09:16:15 2008
Or
ESD#6 (32-bit)
Adaptive Server Enterprise/15.0.2/EBF 15963 ESD#6/P/NT
(IX86)/Windows 2000/ase1502/2537/32-bit/OPT/Wed Oct 01
21:41:43 2008
Or
ESD#6 (64-bit)
ESD#6/P/X64/Windows Server/ase1502/2536/64-bit/OPT/Tue
Sep 30 21:55:30 2008
Tellabs recommends 64-bit version software in Database Server.

44
6.3.4 ThinClient Server
Operating system with Tellabs Windows Server 2003 + Service Pack 2 (32-bit version)
Windows Server 2003 R2 + Service Pack 2 (32-bit version)
Or
Or
Or
Application Server Citrix Presentation Server 4.5,
Hotfix Rollup Pack PSE450W2K3R03
Or
Citrix XenApp 5.0,
Hotfix Rollup Pack XAE500W2K8X64021
6.3.5 Replication Server Software
Operating system with Tellabs Windows Server 2003 + Service Pack 2 (32-bit or 64-bit version)
Windows Server 2003 R2 + Service Pack 2 (32-bit or 64-bit
version)
Or
Red Hat Enterprise 4 or later
Or
SuSe Enterprise 9 or later
Or
Solaris (The version depends on the Unix server used. For more
information, refer to 6.5 Unix Server Sets.)
6.4 Displays
6.4.1 Workstation Display
Specification SVGA display with 1280x1024 resolution,

17" screen size minimum
Recommendation 19" or larger screen
Small fonts should be used in Windows.

45
6.4.2 Server Display
Specification SVGA display with 1024 x 768 resolution,

15" screen size minimum
Recommendation 17" screen size
6.5 Unix Server Sets
For the Unix machines, contact your Tellabs representative.
6.5.1 Sun SPARC Enterprise M4000 Server
Hardware
Computer model Sun SPARC Enterprise M4000 Server

Processors 1 or 2 Processor boards with 2 x SPARC64 VII quad-core
processors
Network Manager
Hard disks 2 x 146 GB SAS
Drives DVD-ROM drive

LAN adapter With four on-board RJ45 10/100/1000Base-T (Copper) Gigabit
Fast Ethernet ports
Display VT 100 or compatible terminal, terminal concentrator or Sun
graphic terminal
Software
Operating system Solaris 10 10/09 or later
with the latest Sun recommended patches
Disk system software Veritas Volume Manager, zfs or Sun Volume Manager
Disk Array
Model Sun StorEdge 2540 FC
Disks 12x 146 GB SAS
Controller card Dual FC RAID controller

46
6.5.2 Unix Database Server Software
Database Sybase Adaptive Server 15.0.2 + EBF 15651 for 64 bit versions.
server software Output of “select @@version” from ISQL:
Adaptive Server Enterprise/15.0.2/EBF 15651 ESD#4/P/Sun_svr4/OS
5.8/ase1502/2528/64-bit/FBO/Sat Apr 5 09:36:08 2008
Or
Sybase Adaptive Server 15.0.2 + EBF 15959 for 64 bit versions.
Output of “select @@version” from ISQL:
Adaptive Server Enterprise/15.0.2/EBF 15959 ESD#6/P/Sun_svr4/OS
5.8/ase1502/2537/64-bit/FBO/Thu Oct 2 05:54:54 2008
6.5.3 Route Master Software
Route Master software with Red Hat Enterprise Linux ES version 3 update 5.
Tellabs 8000 network manager
R17A
6.5.4 Backup Tape Device
Hardware
Drive LTO drive
6.6 Preinstalled Computers
Preinstalled computers are available from Tellabs. These ready-to-run computers are delivered with
the required 3rd party software installed (e.g. Windows and Sybase). These computers are tested
with a system network before shipping. Note that the required licenses need to be ordered separately
in accordance to the customer specific Tellabs 8000 manager setup.
6.7 Minimum Requirements for Tellabs 8100 Service Computers
The Tellabs 8100 network manager Service Computer software will run on laptop computers which
meet the specifications below. Note that Tellabs can properly support only 3rd party hardware
and software tested by Tellabs. In case of problems with other computer types, the vendor of
that equipment should be contacted.
The requirements for Service Computer laptops are:
• A laptop computer designed for Microsoft Windows XP

• Manufacturer provided hardware drivers
• Serial port available
• Parallel or USB port available.
Minimum performance requirements:

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

• 512 MB or more RAM (1 GB if Tellabs 6300 Craft Terminal is used in the same computer as
Tellabs 8000 manager Service Computer)
• 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.
6.8 Network Management Resilience Service
6.8.1 Hardware
Open Switch Server
Number of 1 - 25 25 - 100 101 - 250

Users/Servers in
the Network
PC (Linux) Based Server
Server model HP DL360 G6 UNIX server UNIX server
recommended recommended
Operating system Linux
RAM 4 GB
CPU 1
Disk 2 x ≥ 72 GB
UNIX (Solaris) Based Server
Server model Sun SPARC Enterprise Sun SPARC Enterprise Sun SPARC Enterprise
T5220 T5220 M4000
Operating system Solaris Solaris Solaris
RAM 4 GB 8 GB ≥ 16 GB
CPU 1 1 4
Disk 2 x ≥ 72 GB 2 x ≥ 146 GB 2 x ≥ 146 GB
Replication Server
Number of Nodes 1 - 1000 1000 - 5000 5000 - 30000

in the Network
PC (Linux) Based Server
Server model HP DL360 G6 HP DL360 G6 UNIX server
recommended
Operating system Linux Linux
RAM 4 GB 8 GB
CPU 1 1
Disk 4 x ≥ 72 GB 4 x ≥ 146 GB
UNIX (Solaris) Based Server

48
Number of Nodes 1 - 1000 1000 - 5000 5000 - 30000

in the Network
Server model Sun SPARC Enterprise Sun SPARC Enterprise Sun SPARC Enterprise
T5220 T5220 T5220
Operating system Solaris Solaris Solaris
RAM 4 GB 8 GB ≥ 16 GB
CPU 1 1 1
Disk 4 x ≥ 72 GB 2 x ≥ 146 GB 4 x ≥ 146 GB
6.8.2 Software
For the latest information on the operating system and Sybase versions, contact your Tellabs
representative.

49

18 Tellabs 8000 Network Manager R17A Third Party Hardware and Software Requirements

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

18 Tellabs 8000 Network Manager R17A Third Party Hardware and Software Requirements

Caricato da

Copyright:

Formati disponibili

Tellabs ® 8000 Network Manager R17A

Third Party Hardware and Software Requirements

Document No. Date Description of Changes

© 2010 Tellabs. All rights reserved.

Tellabs ® 8000 Network Manager R17A 70002_18

Terms and Conventions

70002_18 Tellabs ® 8000 Network Manager R17A

About the Manual .............................................................................................................. 8

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

2.1 Tellabs 8000 Network Manager Standard Workstation....................................................................................... 13

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

70002_18 Tellabs ® 8000 Network Manager R17A

3.1 DCN for Tellabs 8600.......................................................................................................................................... 23

4 Database Protection Levels ....................................................................................... 27

5.1 Network Size ....................................................................................................................................................... 30

6.1 Computer Sets...................................................................................................................................................... 34

Tellabs ® 8000 Network Manager R17A 70002_18

6.8.1 Hardware ............................................................................................................................................. 48

70002_18 Tellabs ® 8000 Network Manager R17A

About the Manual

This manual is intended for system administrators and system specialists.

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

Tellabs ® 8000 Network Manager R17A 70002_18

• Single Computer Configuration (SCC)

70002_18 Tellabs ® 8000 Network Manager R17A

Tellabs ® 8000 Network Manager R17A 70002_18

2 Tellabs 8000 Network Manager System

70002_18 Tellabs ® 8000 Network Manager R17A

Fig. 1 Example of Multi-User Tellabs 8000 Network Manager Configuration

Recommendation for Maximum Number of Workstations

Recommendation for Maximum Number of Workstations per Server

Tellabs ® 8000 Network Manager R17A 70002_18

Type of Server Maximum Number of Workstations

2.1 Tellabs 8000 Network Manager Standard Workstation

2.2 Tellabs 8000 Network Manager Satellite Workstation

2.3 Tellabs 8000 Network Manager Power Workstation

2.4 DXX Server (8100 Adapter)

70002_18 Tellabs ® 8000 Network Manager R17A

2.5 Database Server

2.5.1 Off-line Database Kit for Reporting

2.6 Recovery Server

2.7 Private Subnetwork Components

Tellabs ® 8000 Network Manager R17A 70002_18

2.7.1 Management Server with Private Subnetwork Service

2.7.2 Private Subnetwork Workstation

70002_18 Tellabs ® 8000 Network Manager R17A

2.8 Communication Server

Recommendation for Maximum Number of Nodes per Communication Server

Tellabs ® 8000 Network Manager R17A 70002_18

2.9 Management Server

2.9.1 Fault Service

2.9.2 Web Reporter Service

2.9.3 Northbound Interface Service

2.9.4 SLA Service

70002_18 Tellabs ® 8000 Network Manager R17A

It is recommended to use a dedicated Management Server for SLA Service.

2.10 Route Master

2.11 Satellite Service

2.12 Tellabs 8100 Service Computer

Tellabs ® 8000 Network Manager R17A 70002_18

2.13 Single Computer Configuration — Tellabs 8000 Manager in 8100

70002_18 Tellabs ® 8000 Network Manager R17A

2.14 Dual Computer Configuration — Tellabs 8000 Manager in 8100