3JL Planning Guide

IMPORTANT NOTICE: This document contains confidential information that is proprietary to Alcatel-Lucent. No part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.

www.alcatel-lucent.com

Alcatel, Lucent, Alcatel-Lucent, and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. © 2008 Alcatel-Lucent. All rights reserved.

5520 Access Management System (AMS)

Release 8.4.0

3JL 00112 AAAA RKZZA Edition 01

P L A N N I N G G U I D E

5520 AMS 8.4.0 Planning Guide

Alcatel-Lucent 3JL 00112 AAAA RKZZA October, 2008 | 2

Contents 1 Introduction ................................................................................ 3 2 Hardware requirements ................................................................. 3

2.1 Server requirements ....................................................................... 4 Reference configuration .................................................................. 5 Validated hardware........................................................................ 5 Equivalent servers ......................................................................... 5 Lab trial hardware ......................................................................... 6

2.2 Client requirements ....................................................................... 6 Minimum PC client requirements........................................................ 6 Solaris presentation server requirements .............................................. 7

3 Disk capacity & operating system requirements.................................... 7 3.1 Disk requirements for servers ............................................................ 7 3.2 Operating system requirements for servers ........................................... 8

4 Software requirements .................................................................. 9 4.1 Software kit bundling...................................................................... 9 4.2 System operation and maintenance..................................................... 9

When does Alcatel-Lucent create updates?...........................................10 5 Bandwidth requirements .............................................................. 10

External communication .................................................................10 Internal communication in a clustered site...........................................11

6 Firewall requirements ................................................................. 11 7 Terminology .............................................................................. 12 8 Documentation .......................................................................... 13

8.1 Customer documentation ................................................................13 Downloading customer documentation PDF files from SDS.........................14 Downloading customer documentation PDF files from OLCS.......................14

8.2 Customer feedback .......................................................................15 9 Glossary ................................................................................... 15



1 Introduction The Alcatel-Lucent 5520 Access Management System (AMS) is an Element Management

System (EMS), which provides remote management for the Alcatel-Lucent access portfolio

for fulfillment, maintenance and troubleshooting operations. The system provides fault,

configuration, and performance management of the underlying access networks by means of

an intuitive graphical user interface and hierarchical tree navigation. All of these are updated

with real-time alarm and status information. The system also supports several productivity

features, such as equipment profile management, NE back-up/restore and NE software

management, greatly facilitating network operations.

5520 AMS R8 is based on the new generation Access Management platform. The new

platform is based on Java and provides widely modular architecture. Management plug-ins

providing NE support enable better coverage of new NE types and releases by enabling

improved synchronization with NE deliveries and their support by the management system.

5520 AMS also brings advanced OSS interfaces based on Web Services (XML/SOAP) as well

as advanced features for scalability and redundancy.

The 5520 AMS product suite enables Alcatel-Lucent to bring a single Element Management

System to market, that covers the full access network portfolio.

This guide covers the planning aspects of the 5520 8.4.0 core product. It provides basic

guidance based on the performed validation testing. For more information, contact your ALU

representative.

2 Hardware requirements The 5520 AMS uses a client-server architecture pattern. Management applications operate on

a central server infrastructure (site) and clients. The clients are deployed on the same

machine or on separate machines, and they connect to the site to perform management

operations.

The 5520 AMS client can either be deployed on a Windows PC or on a dedicated presentation

server. A typical reason for using a dedicated presentation server is the existence of a high

latency network between the client PC and the 5520 AMS server. In such cases, performance

is improved by using a presentation server that is located close to the server. The

presentation server can be accessed using remote desktop access (validated with Citrix for

this release).

The 5520 AMS server is qualified to be deployed on the SUN SPARC Solaris 10 platform.

The 5520 AMS server site consists of 3 components:

• Application server(s):5520 AMS applications software running the business logic and

underlying platform. Application servers in a cluster run in a load balancing fashion



that allows you to either scale the solution by adding additional servers or to provide

high availability by over-dimensioning the cluster to ensure operation during a failure

of one of the servers. It is recommended to use similar machines for application

servers within a single site.

• Database/file server(s): the MySql server and fileserver for managing/accessing files.

Redundancy is supported.

• Storage: hosts the DB file and shared file system. Storage can be as simple as a local

disk on the database server, but it is more commonly a storage array that provides

data and controller redundancy (required for setting up redundant databases servers).

For efficient backups, use ZFS as the file system on those disks. Apart from this

shared storage, each application server will require some local storage.

The components mentioned above can be combined to create numerous different solutions.

The selection of the proper solution needs to be based on the management need, required

system availability and protection, planned growth, and existing hardware.

Examples of typical solutions:

• Single server with local disk: small non high-available system with no growth path

• Minimal cluster: 2 physical servers with colocated application and database server

(co-hosted on same machine) and a storage array for hosting data. Either of the

servers can take over the activities of the other, as long they are properly dimensioned.

• Full cluster: 2 or more application servers and a redundant pair of database servers

with a storage array. All application and data servers run on different physical

machines.

When planning the site setup and which server size to use, you should consider:

• The number of concurrent users and the number and family of network elements to be managed.

• The type of availability that is required. Is it needed to have full application, data and storage redundancy or not? If you use a storage array, two application servers, and two database servers, you can cope with single component failures. By spreading these roles over multiple machines you reduce the granularity of a single component failure.

• Network growth. Consider the size of the current network to be managed as well as the kind of growth that is expected over the next few years. Doing this up front can reduce future costs and increase network efficiency.

2.1 Server requirements

The following configuration has been validated both in single server and cluster setup.



Based on the measured performance, server requirements are given in the form of equivalent

machines (equivalence is based on the machine specifications). Some additional guidance is

also provided in this section. For more information, contact your Alcatel-Lucent sales

representative.

Reference configuration

• Total of 4000 network elements

• Mix of 700 7342 ISAM FTTU nodes and 3300 7302/7330 ISAM FTTN nodes

• Total of 2456000 configured user ports

• Steady state alarm load of 200 alarms / min

• Alarm peak rate of 2000 alarms / min

• Assume 200 operators, 100 concurrently active (typical GUI navigation load)

Validated hardware

The reference configuration has been validated on the following setups:

• Single server: SUN T2000, 8 core 1.2GHz UltraSPARC T1, 32 GB RAM, disk 146GB

o Testing shows 16GB RAM to be sufficient

• Minimal cluster: 2 x SUN T2000, 8 core 1.2GHz UltraSPARC T1, 32 GB RAM, disk

146GB (1 combined application and simplex database server and 1 additional

application server)

o Testing shows 16GB RAM to be sufficient on each server

o Load from database server is minimal, so if solution is chosen with separated

database server, a less powerful machine can be chosen for that database

server (contact your ALU representative for more information).

• Loaded SW: 5520 AMS 8.4.0 DR4 loads for core including 1 7302/7330 ISAM FTTN

plug-in and 1 7342 ISAM FTTU plug-in

• Testing shows 16G of RAM to be sufficient (both for single server and clustered

servers)

Future testing on bigger configurations is planned and will be included in future releases of

this document.

Equivalent servers

Based on the server specifications, the following servers are considered equivalent:



Table 1: Equivalent servers

Type CPU CPU speed Mhz/ on chip

mem)

Chips

Sun Fire V490/V890 (Dual Core) US-IV+ 2100/32MB 3



Sun Fire V490/V890 (Dual Core) US-IV 1200/16MB 6






SPARC Enterprise M4000 (Dual Core) SPARC64 VI 2150/5MB 3

SPARC Enterprise M4000 (Quad Core) SPARC64 VII 2400/5MB 2

Sun Fire T1000/T2000 (8 Cores) UltraSPARC T1 1200/3MB 1

Sun Fire T1000/T2000 (8 Cores) UltraSPARC T1 1400/3MB 1

Sun SPARC Enterprise T5x20 (4 Cores) UltraSPARC T2 1200/4MB 1

Lab trial hardware

To manage less then 10 NEs the minimum configuration is a Solaris SPARC machine with 4

GB of RAM. This configuration can be used for lab demos and/or trials.

2.2 Client requirements

Minimum PC client requirements

Table 1 lists the required hardware for the minimum client configuration for a PC

hosting a GUI. Configurations exceeding these requirements are also acceptable.

Table 1: Client configurations

Hardware Minimum requirements

CPU (1) Pentium IV or compatible 1GHz

RAM 1 GB RAM

Hard Disk 20-GB hard disk

Network Speed 10/100 Base-T connection

Media CD-ROM or DVD-ROM

Video Capacity Video card supporting at least 1024x768 resolution and 24-bit color



Solaris presentation server requirements

Table 2 lists the required hardware for the minimum client configuration for a Solaris

presentation server hosting one or more GUIs. Configurations exceeding these

requirements are also acceptable.

Table 2: Solaris presentation server configuration

Hardware Minimum requirements

CPU or Cores (2) UltraSPARC 1.5GHz (per 20 operators)

RAM 8 GB RAM (per 20 operators)

Hard Disk 20-GB hard disk (per 20 operators)

Network Speed 10/100/1000 Base-T connection

Media CD-ROM or DVD-ROM

Video Capacity N/A

3 Disk capacity & operating system requirements Disk requirements described in this section are currently specified only for the validation

configuration platform.

3.1 Disk requirements for servers

The storage can be split into 3 categories:

• Product SW on each server

• Local data (logs, temp files, etc) on each server

• Shared data (DB hosting and shared files for NE backups, SW loads, etc.) for each site.

o For a redundant database it is required to host the shared data on a storage

array, SAN or something similar using ZFS which can be mounted from both

DB servers. ZFS over NFS is not supported.

o For a simplex server either UFS or ZFS can be used for shared data, however

ZFS is preferred.

o For a single server all data can be hosted on the local disk (using UFS or ZFS –

preferred).

The required disk space is dependent on the required configuration. Use the value below to

extrapolate to your case and contact your sales representative if you require more

information.



Table 3: Reference configuration (4000 NE) server(s) disk requirements (typical storage for backup and alarms)

File System / Mount Point Size (GB) Per server

Size (GB) Per Site

File System Type

SW 4 - UFS

LOCAL 4 - UFS/ZFS

SHARED - 60 ZFS

SWAP 16(2*RAM) - UFS

Total 24 60

3.2 Operating system requirements for servers

The 5520 AMS R8.4.0 is currently only qualified for use on the Sun Microsystems Solaris

10 operating system.

Install Solaris 10 using the instructions provided by Sun and observe local practices with

respect to security concerns.

Note: Alcatel-Lucent recommends installing Solaris 10 using the Initial Install option,

not the Upgrade Install option. When prompted to enter the installation type, choose

“Entire Group”.



4 Software requirements This section describes the software requirements to run the 5520 AMS. The 5520 AMS

software kits and Right to Use (RTU) licenses are available in the 5520 AMS Customer

Release Notes. Please contact your sales representative to place your order.

• For servers, 5520 AMS R8.4.0 and higher requires prior installation of Solaris Server

OS Version 10. It is recommended that the latest Solaris patches be installed on the

server.

• For clients, 5520 AMS R8.4.0 and higher requires prior installation of Windows

XP/Windows Vista. It is recommended that the latest Microsoft patches be installed

on the client.

• The 5520 AMS requires various third party software applications. All necessary third

party software is included in the software package.

4.1 Software kit bundling

The 5520 AMS software kits include the following:

• Software, including:

o Core system software

o Plug-in NE management, organized by NE Family and Software Version

o Plug-in premium applications

• Documentation, including:

o Core system (planning , installation and migration, administration, and user Guides)

o NE Operations and Maintenance using 5520 AMS, organized by NE family and software version

o Premium applications user guides

o Customer release notes

4.2 System operation and maintenance

No ongoing maintenance is necessary for the 5520 AMS. Shutting down or rebooting the

5520 AMS is not service affecting to the NE.

The 5520 AMS supports the process for including software updates. Updates are files

delivered to the customer to introduce new features or to correct a problem in a

particular version of the software. These updates are subsequently rolled into the next

release of 5520 AMS when it becomes available.



When does Alcatel-Lucent create updates?

An update is created to:

• Support the release of a new NE or feature

• Fix a problem that, without an acceptable workaround, prevents deployment or

continued service of the 5520 AMS

Note: A new NE feature does not warrant a point release, but it needs support in the

5520 AMS.

5 Bandwidth requirements External communication

A 5520 AMS site requires network bandwidth for communication between the following

components:

Table 4: Network bandwidth

Component Activity Bandwidth

EMS to NE Database backup and restore 128 Kbps

EMS to NE Software download 128 Kbps

EMS to NE Management commands 1-5 Kbps

NE to EMS Trap notifications 1-5 Kbps

EMS to Authenticator EMS User authentication < 1 Kbps1

EMS to MySQL Server Operations requiring persistency 5 Kbps

EMS client to EMS server Operations 40-80Kbps bi-directional for single user activity

To calculate overall bandwidth requirements for a typical network management profile,

estimate the maximum number of concurrent operations for each activity in the table above,

multiplied by the bandwidth needs, and add these together.

Table 5: Sample network bandwidth calculations

Activity Bandwidth Concurrent operations Total bandwidth

Database backup and restore

128 Kbps 50 6,400 Kbps

Software download 128 Kbps 10 1,280 Kbps

Management commands 1-5 Kbps 100 100-500 Kbps

Trap notifications 1-5 Kbps 2 1-10 Kbps

Operations requiring persistency

5 Kbps 10 50 Kbps

1 This contributes insignificant bandwidth requirements and may be ignored for the purposes of overall network bandwidth calculations.



Activity Bandwidth Concurrent operations Total bandwidth

TOTAL 7,831 – 8,240 Kbps

The maximum bandwidth requirements for this particular network management profile are

approximately 8.24 Mbps, assuming the upper-end bandwidth requirements are used.

Similar calculations should be made for exceptions to the typical network management

profile such as mass NE upgrades, alarm “storms”, bulk provisioning, inventory retrieval,

disaster recovery, and so on.

Internal communication in a clustered site

In a clustered site, the interconnection between the nodes of the local cluster (application

nodes and DB servers) needs to be a dedicated private LAN (i.e. separate NIC) or behave as

such (100Mbps is sufficient). If redundancy is required for this communication path, IPMP

must be used (2 NICs).

6 Firewall requirements A 5520 AMS site requires port access for communication between the following components:

Table 6: Port activity

Component Activity Port Protocol Service

EMS to/from NE Database backup and restore

69 UDP TFTP

EMS to/from NE Software download 69 UDP TFTP

EMS to/from NE Secure cut through 22 UDP SSH

EMS to/from NE Database backup and restore

22 UDP SSH/SFTP

EMS to/from NE Software download 22 UDP SSH/SFTP

EMS to NE Management commands

161 UDP SNMP

NE to EMS Trap notifications 162 UDP SNMP

EMS to Client Name resolution 1098 TCP JBOSS Naming

EMS to Client Name resolution 1100 TCP JBOSS Naming

EMS to Client Name resolution 1101 TCP JBOSS HA Naming

EMS to Client Name resolution 1102 UDP JBOSS HA Naming

EMS to Authenticator User authentication 1812 UDP RADIUS

EMS to Authenticator User authentication 389 UDP LDAP

EMS to MySQL Server Operations requiring persistency

3307 TCP MySQL Server

Client to EMS Operations invoked by a Client

4444 TCP JBOSS RMI


4445 TCP JBOSS Pooled RMI



Component Activity Port Protocol Service


4447 TCP JBOSS HA RMI


4448 TCP JBOSS pooled HA RMI

Client to EMS Download of Client software

8080 TCP HTTP

EMS to Client Message reports to Client

8093 TCP JBOSS JMS

In a clustered site, the servers (application and/or database servers) need to be networked in

a private LAN without a firewall. To achieve redundancy, you can use IPMP on the network

connections. For this reason, it is recommended that you use multiple NICs: typically , one

NIC for the client subnet, one for the server subnet, and two for the internal LAN (if

redundancy through IPMP is required). However, it is also possible to run all the traffic

through a single dedicated NIC. This network interconnects application and database servers

which are colocated in a single server room.

7 Terminology The following terms must be understood to ensure proper application of the EMS.

• The EMS operating system

The 5520 AMS software runs on the UNIX-based Sun Solaris Operating System with

a patch cluster based on the latest provided by Sun. The operating system must be

present on each of the EMS computing platforms before the 5520 AMS software can

be installed or run.

• EMS server platform

The physical computing platform and UNIX operating system at the center of the

EMS system. The server is a central repository for data and the communications hub

for all communications to and from the managed network elements.

• EMS server application

The EMS software running on the EMS server platform. The server provides all key

EMS functions and manages network information.

• EMS client platform

The physical computing platform and UNIX operating system that supports the EMS

client application software. One or more EMS client instances may be run on the

platform concurrently.

• EMS client application

The 5520 AMS GUI that runs on the EMS client workstation. The client application

communicates with the EMS server to allow operator control of the network. One



instance of the client can be run on the server or on a separate platform (the EMS

client workstation) for better performance.

• EMS client instance

Each time the EMS client application is run, an instance of the client is created.

Multiple client instances may exist concurrently on a single computing platform. The

number of EMS client instances allowed represents the maximum number of users

who can use the EMS at one time.

• EMS system

Refers to the combination of the EMS server, client applications, and platforms. One

EMS system may, for example, include one EMS server platform running one EMS

server application, along with five EMS client platforms supporting one client

instance each. Another system might include two client platforms running five client

instances each, attending an identical EMS server platform and application.

• Local communications network (LCN)

A local data network used to interconnect computing devices. The most common

implementations presently use Ethernet as the physical/electrical format, and

support message routing using TCP/IP.

• Local area/wide area network (LAN/WAN)

A data network that can span several sites and is generally used to connect computing

devices within a single enterprise (e.g., multiple corporate campuses).

• Data communications network (DCN)

A data network for connecting managed systems or devices (such as

telecommunications equipment) with management systems (usually computing

devices). Distinguished from the LCN and LAN/WAN by the type of connection to the

systems used to deliver service. The traditional implementation for telephony is an

X.25 packet-switched network or private line.

8 Documentation 8.1 Customer documentation

The Support Documentation Service (SDS) and OnLine Customer Service (OLCS)

websites give customers online access to the latest Alcatel-Lucent customer

documentation. Use the following procedures to go to either of these sites and view or

download a wide range of documentation, including product manuals and

documentation updates.



Downloading customer documentation PDF files from SDS

The 5520 AMS R8.4.0 customer documentation can be obtained by download from the

Support Documentation Services (SDS) website. To download the 5520 AMS R8.4.0

customer documentation from SDS, follow this procedure:

1. Go to: http://www.alcatel-lucent.com/osds/.

2. Log in, using your SDS account. A customized Customer Center window is displayed.

3. In the navigation tree, click Documentation.

4. In the Product Name Look-up text box, type 5520 AMS and click Go.

5. In the Product Name Look-up Results window, click 5520 AMS (Access Management

System).

6. Under Documentation and downloads, click Manuals and Guides.

All of the 5520 AMS documentation is listed. You can further refine your search by

Release or other categories, using the tools provided at the top of the page

7. To view a document, click on the PDF link that appears to the left of the document.

The PDF opens.

8. To save a copy of the PDF, choose File -> Save As, then navigate to the location you

want to save it to, enter a filename, and click Save.

Downloading customer documentation PDF files from OLCS

The 5520 AMS R8.4.0 customer documentation can be obtained by download from the

OnLine Customer Support (OLCS) website. To download the 5520 AMS R8.4.0

customer documentation from OLCS, follow this procedure:

1. Go to the OLCS web page by performing one of the following:

a. Go to http://www.alcatel-lucent.com and click MyAccess.

b. Go to http://www.alcatel-lucent.com/wps/portal/support and click

MyAccess.

2. Click Login to OLCS, and log in, using your OLCS account. A customized Customer

Center window is displayed.

3. In the navigation tree, click Documentation.

4. In the Product Name Look-up text box, type 5520 AMS and click Go.

5. In the Product Name Look-up Results window, click 5520 AMS (Access Management

System).

6. Under Documentation and downloads, click Manuals and Guides.

All of the 5520 AMS documentation is listed. You can further refine your search by

Release or other categories, using the tools provided at the top of the page



7. To view a document, click on the PDF link that appears to the left of the document.

The PDF opens.

8.2 Customer feedback

We value your feedback. Please direct questions or comments about Alcatel-Lucent

documentation to: [email protected].

9 Glossary Term Expansion

APC Access Provisioning Center

AWS Access management Work Station

CPU central processor unit

DCN data communications network

EMS Element Management System

FTP File Transfer Protocol

GUI graphical user interface

IP Internet protocol

LAN local area network

LCN local communications network

MTOSI Multi-Technology Operations System Interface

NE Network Element

OA&M operations, administration, and maintenance

OAD OSS Alarm Dispatcher

OSS Operations Support System

QoS Quality of Service

SDC Statistics and Data Collector

SOAP Simple Object Access Protocol

SNMP simple network management protocol

TCP Transmission Control Protocol

TFTP Trivial File Transfer Protocol

UDP User Diagram Protocol

WAN Wide-area Network

XML eXtensible Markup Language

End of document

3JL Planning Guide

Documents

Transcript of 3JL Planning Guide