8950 vam (8950 voice activation manager) - nokia · pdf file8950 vam (8950 voice activation...

8950 VAM (8950 Voice Activation Manager)System Administration GuideRelease 16.0

365-370-368R16.0Issue : GA-1

July 2010

Copyright © 2009 Alcatel-Lucent. All Rights Reserved.

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alacatel-Lucent), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Alacatel-Lucent and the business management owner of the material.

For permission to reproduce or distribute, please contact:

Product Development Manager: +1 317 322 6847 1 800 645 6759 (continental U.S.)

Notice

Every effort was made to ensure that this information product was complete and accurate at the time of printing. However, information is subject to change.

Mandatory customer information

This information product does not contain any mandatory customer information.

Interference information: Part 15 of FCC rules

NOTE: This equipment has been tested and found to comply within the limits.

Trademarks

Alcatel-Lucent, Lucent, and http://www.alcatel-lucent.com are registered trademarks of Alcatel-Lucent.

Cisco is a registered trademark of Cisco Systems, Inc.

CORBA is a trademark of the Object Management Group.

ERICSSON is a registered trademark of the Telefonaktiebolaget LM Ericsson.

EWSD is a registered trademark of Siemens Information and Communication Networks, Inc.

Hewlett-Packard, HP, HP-UX, GlancePlus, JetDirect, OpenView, PA-RISC, and PerfView are registered U.S. trademarks of the Hewlett-Packard Company.

INFORMIX is a registered trademark of Informix Software, Inc.

Internet Explorer, Windows, and Windows NT are U.S. registered trademarks of the Microsoft Corporation.

Netscape Communicator and Netscape Navigator are U.S trademarks of Netscape Communications Corporation.

NORTEL Networks is a trademark of NORTEL Networks.

Orbix is a registered trademark of IONA Technologies.

Pentium is a trademark of Intel Corporation.

Persistence is a trademark of Persistence Software, Inc.

PostScript is a registered trademark of Adobe Systems Incorporated.

SCSI is a registered trademark of Security Control Systems, Inc.

SPARC is a registered trademark of SPARC, International, Inc. Products bearing the SPARC trademark are based on architecture developed by Sun Microsystems, Inc.

Sun Microsystems and Sun Workstation are registered trademarks of Sun Microsystems, Inc licensed to Sunsoft, Inc; and Java is a trademark of Sun Microsystems, Inc.

UNIX is a registered trademark of the Open Group.

Microsoft is a registered trademark and Windows and Windows NT are trademarks of Microsoft Corporation in the United States and in other countries.Pentium is a registered trademark of Intel Corporation.

All other products or services mentioned in this document are identified by the trademarks, service marks, or product names as designated by the companies who mark those products. Inquiries concerning such trademarks should be made directly to those companies.

Ordering information

The ordering number for this information product is 365-370-368R16.0.

Support

Information product support

Alacatel-Lucent provides a referral telephone number for support. Use this number to report errors or to ask questions about the information product. This is a non-technical number. The referral telephone number is +1 317 322 6847 or 1 800 645 6759 (continental U.S.).

Technical support

Technical assistance can be obtained by calling the Regional Technical Assistance Center (RTAC) at 1 800 225 RTAC (continental U.S.) or +1 630 224 4672 for in-hours and emergency out-of-hours support.

Developed by Alcatel-Lucent Customer Training and Information Products

Issue: GA-1, July 2010A- I

System Administration Guide365-370-368R16.0

Table Of Content

..............................................................................................................................................................................................................................................

1 VAM System OverviewAbout 8950 VAM 1-2

8950 VAM Benefits 1-2

Better, Cheaper, Faster Service Activation 1-2

Improved Customer Service and Satisfied Subscribers 1-2

Improved Provisioning 1-2

State-of-the-Art Technology 1-2

Interworks with Most Popular NEs 1-3

The Alcatel-Lucent Name 1-3

A Total Integrated Offering 1-3

People and 8950 VAM 1-3

8950 VAM System Topology 1-4

The Work Centers 1-5

The Central Computers 1-5

The Switches 1-6

8950 VAM Applications 1-6

Task Execution Interface 1-6

Task Builder Environment 1-6

Graphical User Interface 1-6

Hyper Text Transport Protocol Security (HTTPS) 1-7

Direct Communication to Supported Switches 1-7

API Programmability 1-7

1-7

Issue: GA-1, July 2010A - I I


1-7

8950 VAM File System Configuration 1-7

8950 VAM Application Software 1-7

8950 VAM File System and Log files 1-8

Main File Systems 1-8

8950 VAM Software Components 1-8

Application Programs, Tools, and Utilities 1-8

Upgrade Options 1-9

Operating Systems and Browsers 1-9

Database Management System 1-9

8950 VAM Software Naming Conventions 1-9

GENERIC RELEASES 1-10

PATCH RELEASES 1-10

RTU’s and Licenses for 8950 VAM 1-10

Right To Use 1-10

Licenses 1-10

About Alcatel-Lucent Electronic Delivery (LED) Website 1-11..............................................................................................................................................................................................................................................

2 VAM System MonitoringSystem Admin Tasks 2-2

Check Filesystem space 2-2

Cleanup /rc file system space 2-3

Check database space 2-3

Check int/root mail 2-4

Change root password 2-5

Change int password 2-5

Alternate option to change int password 2-5

VAM Software VERSIONS 2-6

Check Informix Logical Logs 2-7

Crontab Customization 2-8

Issue: GA-1, July 2010A - III


..............................................................................................................................................................................................................................................

3 VAM Hardware Admin/MonitoringHARDWARE OVERVIEW 3-2

HP Enterprise Server Hardware Configuration 3-2

Hardware configuration 3-2

Physical processor Mode 3-2

HP System Virtual System Names 3-3

Hardware Admin Support 3-4

HP System Admin 3-5

HP System Shutdown 3-5

HP System Startup 3-5

HP System reboot 3-6

HP System boot (Single-User) 3-6

From Multi-User Mode 3-6

From Firmware Mode 3-6

HP System Boot Admin 3-7

Replacing the Disk 3-9

Flex Backup Solution 3-11

Alcatel-Lucent Backup Solution 3-12

Configure Alcatel-Lucent Backup Solution 3-13

Run Flex Config Backup (Live) 3-16

Run Flex Config Backup (BU) 3-17

Flex Config Recovery - Overview 3-18

Live HP System (L1) Recovery - FLEX 3-18

Backup HP System (BU) Recovery - FLEX: 3-23

Flex Config Failover - (DUPLEX) 3-25..............................................................................................................................................................................................................................................

4 VAM Application Admin/MonitoringVAM Full Application Shutdown 4-2

VAM Full Appplication Startup 4-4

VAM Core Appplication Admin 4-5

VAM Application Status 4-5

VAM Application Shutdown 4-7

Issue: GA-1, July 2010A - I V


VAM Application Startup 4-8

VAM Application Debug 4-9

Informix Software Admin 4-11

Informix status 4-11

Informix shutdown 4-11

Informix startup 4-11

VAM Application Component Admin 4-13

JGUID Process 4-13

Orbix Process 4-13

Tasktoolkit Status 4-14

Toolkit shutdown 4-15

Toolkit startup 4-15

Software Upgrades 4-16

Archive VAM Database 4-17

VAM System DB Audit 4-20

VAM Application Menu Items 4-24

Access VAM Main Menu 4-24

Link Administration Menu 4-25

User Administration Menu 4-26

Switch Administration Menu 4-27

Switch Database Load Menu 4-28

System Commands Menu 4-29

VAM Parameter Configuration Menu 4-30

Workgroup Admin Menu 4-31..............................................................................................................................................................................................................................................

5 VAM User AdministrationUser Administration 5-2

Access User Administration Menu 5-2

Access Workgroup Admin Menu 5-2

Access Firewall Administration GUI 5-3

Access via GUI Interface 5-3

Workgroup Admin Overview 5-4

Issue: GA-1, July 2010A - V


Add a workgroup 5-4

Change workgroup Info 5-5

Delete workgroup 5-6

User Login Admin Overview 5-7

Add a User account 5-7

Update a User Account 5-9

Delete a User Account 5-10

Change User Login Password 5-11

Password Change Directly by User 5-11

Password Change by System Admin (Menu) 5-12

Password Change by System Admin (GUI) 5-12

Firewall Administration 5-13

Access Firewall Administration GUI 5-13

Firewall - 5ESS Views 5-14

Firewall - DMS TABLES 5-16

Firewall - Switch CLLI Access 5-18

Firewall - Features Access 5-20..............................................................................................................................................................................................................................................

6 VAM Switch AdminSwitch Administration Overview 6-2

Option 1: Shadowed Switches (5ESS & DMS) 6-2

Option 2: NON-Shadowed Switches 6-2

Shadow Switch Admin - Overview 6-3

Prerequisite Information: 6-3

Shadow Switch Administration GUI 6-4

Adding a New Switch - Shadow 6-5

Querying Switch Information - Shadow 6-8

Update Switch Information - Shadow 6-9

Delete a Switch - Shadow 6-10

NON-Shadow Switch Admin Overview 6-11

Switch Type/Generic List: TGI Info 6-11

NON-Shadow Switch Administration GUI 6-14

Adding a New Switch - Non-Shadow 6-15

Issue: GA-1, July 2010A - V I


Querying Switch Information - Non-Shadow 6-17

Update Switch Information - Non-Shadow 6-18

Delete a Switch - Non-Shadow 6-19

EMS Administration Overview 6-20

EMS Type/Generic List: 6-20

Add an EMS network Element 6-22

Query an EMS network Element 6-23

Update an EMS network Element 6-24

Delete an EMS network Element 6-25

EMM Administration Overview 6-26

EMM System Topology 6-26

Helpful Hints: on 8950 VAM Server 6-27

Helpful Hints on EMM Server: 6-27

Add EMM System 6-30

Query EMM System Information 6-31

Update EMM System Information 6-32

Delete a EMM System 6-33..............................................................................................................................................................................................................................................

7 VAM Links AdminLink Admin Introduction 7-2

Link Administration Menu 7-2

Linkadmin utility 7-3

Recent Change Links Admin 7-4

Option 2: RC Link Connect 7-4

Option 3: RC Link Disconnect 7-6

Option 4: RC Link Monitors 7-7

Option 5: RC Link Verify 7-8

Helpful hints for verifying a RC link connection and it’s displayed message output: 7-8

Option 6: DMS Password Change Interval 7-10

Option 7: Configure Inactivity Timeout 7-11

7-11

Echo Back Links Admin 7-12

Issue: GA-1, July 2010A - VII


Option 2: EB Link Connect 7-12

Option 3: EB Link Disconnect 7-14

Option 4: EB Link Monitors 7-15

Option 5: EB Link Verify 7-16

System Links Status Menu Admin 7-17

Option 2: Display Link Address Info 7-17

Option 4: Display Detailed Link Status 7-18

Option 5: Display Links Status Statistics 7-19

Option 6: Display Link Status - Switch Inhibit 7-20

Option 7: Update Heartbeat Interval 7-21

Prerequisite: 7-21

Option 8: Display The Time Links Have Been Up/Down 7-23

Recent Change/Echo-Back Link Status 7-24

Troubleshooting Links 7-25

Debug RC Links Information 7-25

Window1: Ensure SWCOM process is running 7-25

Window2: Monitor RC Link traffic data 7-25

Window 3: Administer Link Configuration 7-27

Links Checks in 5ESS Switch 7-28

Ensure 5ESS Processes Running 7-28

Ensure 5ESS ‘Heartbeat’ Defined 7-28

Ensure 8.1 RCV Success Messages..7-28

Link Sharing Configuration Menu Admin 7-29

Option 2: EB Link Sharing Configuration 7-29

Option 3: Display EB Shared Link Information 7-31

Option 3: Activate EB Shared Link Monitors 7-32

DMS Surveillance Bypass Menu Admin 7-33

Option 2: Enable Bypass File Downloading 7-33

Option 3: Disable Bypass File Downloading 7-35

Option 4: Initiate Bypass File Downloading 7-36

Option 5: View Bypass File Downloading Errors 7-37

EchoBack Filter Table Configuration 7-38

Issue: GA-1, July 2010A - V I I I


Add EB Filter Entry 7-39

Query EB Filter Entry 7-39

Update EB Filter Entry 7-40

Remove EB Filter Entry 7-40..............................................................................................................................................................................................................................................

8 Switch Database Load AdministrationSwitch Database Dump & Load Topology 8-2

Tape: 5ESS Dump & Load Process 8-3

Tape: Create Dump List (5ESS) 8-3

Tape: Update Dump List (5ESS) 8-5

Tape: Generate Dump Script (5ESS): 8-7

Tape: Switch data dump (5ESS): 8-10

Tape: Read Switch Data tapes (5ESS) 8-11

Tape: Read Global CNI data (5ESS) 8-11

Tape(s): Read Binary ODD data (5ESS) 8-14

Network (ASM) : 5ESS Dump & Load Process 8-19

Network (ASM): Create Dump List (5ESS) 8-19

Network (ASM): Generate Dump Script (5ESS): 8-21

Network (ASM): Switch data dump (5ESS): 8-23

Network (ASM): Read Switch Data (5ESS) 8-26

Tape: DMS Dump & Load Process 8-28

Tape: Create Dump List (DMS) 8-28

Tape: Generate Dump Script (DMS): 8-30

Tape: Switch data dump (DMS): 8-33

Tape: Read Switch Data (DMS) 8-34

Network (SDM) : DMS Dump & Load Process 8-37

Network(SDM) : Create Dump List (DMS) 8-37

Network (SDM): Generate Dump Script (DMS) 8-39

Network (SDM): Switch data dump (DMS) 8-41

Network (SDM): Read Switch Data (DMS) 8-42

Network (RC Link) : DMS Dump & Load Process 8-44

Network (RC Link) : Create Dump List (DMS) 8-45

Issue: GA-1, July 2010A - IX


Network (RC Link): Read Switch Data (DMS) 8-46

Loading Data to Database 8-48

Monitoring Dump & Load 8-50

Dump & Load Monitoring via States 8-52

Switch Database Sync (Surveillance System) 8-54

Manual Sync via Menu 8-55

Removing OFR data files 8-56

switch Data Transfer (SDT) Migration 8-57

Prerequisite for Switch Migration 8-57

Switch Data Transfer (SDT) - Save 8-60

Switch Data Transfer (SDT) - Install 8-63

Switch Data Transfer (SDT) - Delete 8-65..............................................................................................................................................................................................................................................

9 VAM Feature Configuration5E-ASM Network-Based D&L 9-3

VAM HP System Activities 9-3

ASM System Activities 9-3

DMS Network-Based Dump & Load via SDM 9-5

SuperNode Data Manager (SDM) 9-5

Background 9-5

Feature Activation Pre-Requisite: 9-6

Important items regarding the use of SDM 9-7

Configure SecureShell (SSH) 9-8

Introduction to SSH 9-8

HP’s SSH document 9-8

Setting up SSH 9-8

Example 1: Dump and Load in the remsh scenario: 9-9

Example 2: Dump and Load in the ssh scenario 9-10

Packages 9-10

For Solaris 10: 9-10

Configure HP-UX VAM server and OSW machines 9-11

Verifying permissions of the SSH configuration files 9-14

Permissions (ssh configuration files) 9-14

Issue: GA-1, July 2010A - X


Disabling insecure services 9-14

VAM SSH Feature Enabling 9-16

Check status of SSH support (HP & OSW): 9-17

Check status of SSH support (OSW & ASM): 9-17

Enable SSH support (HP & OSW): 9-18

Enable SSH support (OSW & ASM): 9-18

Disable SSH support (HP & OSW): 9-19

Disable SSH support (OSW & ASM): 9-19

Configure Proactive System Monitoring 9-20

Monitoring Scripts Overview 9-20

Table List of Monitoring Scripts Available: 9-21

Proactive System Monitoring Menu 9-25

Configure Proactive Monitoring scripts 9-26

Display Proactive Monitoring scripts 9-28

Update Printer/E-mail for Monitoring scripts 9-29

Update Parameter for Monitoring scripts 9-30

Local Scripts for Proactive Monitoring Menu 9-32

Activate Local Proactive Monitoring scripts 9-33

Add new Local Proactive Monitoring scripts 9-34

Add new Local Proactive Monitoring scripts 9-35

Display Local Proactive Monitoring scripts 9-36

Delete Local Proactive Monitoring scripts 9-37

Password Ageing Feature 9-38

Password Ageing Feature Activation 9-38

Configure Password Ageing Feature 9-39

Configure Password Retention Feature 9-40

Auto Code Opening (ACO) 9-41

ACO Tool Benefits: 9-41

ACO System Overview 9-41

ACO Tool Functions: 9-42

ACO System Architecture 9-43

ACO ORDER GENERATION 9-45

Issue: GA-1, July 2010A - XI


ACO REPORTS AND LOGS 9-47

Acknowledgment Report 9-47

Auto Code Processing Log 9-47

Auto Code Immediate Action Report 9-47

Scheduled Code Opening Report 9-48

Code Opening Disposition Report 9-48

Auto Code Exceptions Report 9-48

Auto Code Order Creation Log Report 9-48

Administrative Table Update Log 9-48

Management Summary Report 9-48

ACO Shell Scripts 9-48

ACO Error Codes 9-50

ACO Code Opening Disposition Codes 9-53

ACO Feature Activation 9-54

ACO Domain Info Configuration 9-55

Cross Central Configuration 9-58

Cross Central Feature Activation 9-58

Configure Remote Login Capability 9-59

Configuration Cross Central - Remote Host 9-59

Update sqlhosts file 9-59

Sync switch_mach_addr DB table 9-59

Configuration Cross Central - Local Host 9-60

Configure LDS table for Cross Central Feature 9-60

ISQL check of sw_mach_addr INFORMIX Table 9-60

Local HP server check (sw_mach_addr) 9-60

Remote HP server check (sw_mach_addr) 9-60

Synchronize Workgroup Information 9-61

Synchronize Switch Information 9-61

Synchronize User Login Information 9-62

Test getallcllis script 9-63

Tunable Parameters Configuration 9-64

Access Tunable Parameters Screen 9-64

Issue: GA-1, July 2010A - X I I


Tunable Parameters Options 9-65

Add Tunable Parameters Entry 9-67

Query Tunable Parameters Entry 9-67

Update Tunable Parameters Entry 9-68

Delete Tunable Parameters Entry 9-68..............................................................................................................................................................................................................................................

10 Task Toolkit: Configuration & ManagementTask ToolKit Management 10-2

Task Management Terminology 10-2

Task Packaging 10-2

RCAT Database 10-2

Global Data (Task-specific) 10-2

Global data tables 10-2

Customer-specific global data tables 10-2

Packaging Strategies 10-2

RCAT Packaging 10-3

Single-Task Packaging 10-3

Setting up multiple environments 10-3

Managing Task Development 10-4

Single Task Packaging 10-5

Load Starter Package 10-5

Load Sample Package 10-6

Single Task Management 10-7

Unload a Task 10-7

Sample Command: 10-7

Load a Task 10-9

Sample command: 10-9

Merge a Task 10-11

Merge Tasks Tool Algorithm 10-11

Deep Delete Tasks 10-13

ALL Tasks Management 10-14

Unload All Tasks 10-14

Issue: GA-1, July 2010A - XIII



Load All Tasks 10-16


RCAT Database Management 10-18

RCAT Database Save (Tape) 10-18

Tgui01 Database Save - Tape 10-18

Task Builder Database Save - Tape 10-19

RCAT Database Save (File System) 10-20

Tgui01 Database Save - FileSystem 10-20

Task Builder Database Save - FileSystem 10-20

RCAT Database Restore (Tape) 10-22

RCAT Database Restore (File System) 10-23

Task ToolKit Permissions 10-24

Task Permissions Terminology 10-25

Resources 10-25

Resource Groups 10-26

Work/Task Group 10-27

Permissions Admin High Level Overview 10-28

Resource Group Administration 10-29

Access ResourceGroups Screen 10-29

Add ResourceGroups Screen 10-30

Query Resource Groups 10-30

Update Resource Group 10-31

Delete Resource Group 10-31

Relate Resource Group & Resources 10-32

Access ResourceGroup/Resource Screen 10-32

Add ResourceGroup/Resource Relation 10-33

Query ResourceGroup/Resource Relation 10-33

Delete ResourceGroup/Resource Relation 10-34

Relate Task Groups & Resource Groups 10-35

Access TaskGroup/ResourceGroup Screen 10-35

Add TaskGroup/ResourceGroup Relation 10-36

Issue: GA-1, July 2010A - X I V


Query TaskGroup/ResourceGroup Relation 10-36

Delete TaskGroup/ResourceGroup Relation 10-37

Task Application User Session Timeout 10-38

Configure Task Execution Session Timeout 10-38

Configure Task Builder Session Timeout 10-39..............................................................................................................................................................................................................................................

11 External Systems ManagementTOA Application Management 11-2

TOA Directory Layout 11-2

TOA Configuration 11-4

TOA Application Shutdown 11-5

TOA Application Startup 11-6

SOAP Interface Management 11-7

SOAP Interface Advantages 11-7

SOAP Interface Disadvantages 11-7

CORBA Interface Management 11-8

CORBA Interface Advantages 11-8

CORBA Interface Disadvantages 11-8

Upstream System Integration 11-10

High-Level Steps: Upstream System Integration 11-10..............................................................................................................................................................................................................................................

12 System TipsProduct Technical Support Guidelines 12-2

System Name 12-2

Simple Abstract 12-2

Initial Step 12-2

Severity Level 12-2

Product Support Contact 12-3

Alcatel-Lucent Hotline - AR 12-3

Issue: GA-1, July 20101- 1


1 VAM System Overview

Overview

The purpose of this chapter is to provide information about 8950 VAM system overview and configuration.

Issue: GA-1, July 20101 - 2


About 8950 VAM The purpose of this section is to provide information about 8950 VAM product.

8950 VAM Benefits8950 VAM is a valuable service activation system that can bring telephony service providers higher revenues and cost reductions.

Better, Cheaper, Faster Service Activation 8950 VAM provides a flexible service activation platform and Task Builder tool for user-configurable data entry set-up, translations, and validation rules. 8950 VAM is a single point of access to multi-vendor switches and a single service activation solution for multiple services including POTS/PSTN, ISDN, Centrex, PBX, and trunk side provisioning.

In addition, the minimal manual intervention and flow-through API support that 8950 VAM affords to service providers leads to reduced service activation costs.

Improved Customer Service and Satisfied Subscribers8950 VAM improves the quality and level of service that service providers provide to their subscribers. 8950 VAM ’s Service Activation scheduling feature reduces set-up time and it provides quick responses and acknowledgments to CSRs, thus enabling them to better serve subscribers.

Improved Provisioning8950 VAM ’s task-oriented, NE-independent service activation platform minimizes the on-the-job training and learning curve historically associated with the translation job function.

8950 VAM enables service providers to improve the accuracy of switch provisioning through its user-configurable validation rules, which significantly reduces error-repair costs.

State-of-the-Art Technology8950 VAM offers service providers its object oriented, JavaTM/CORBA, Web enabled Client/Server technology and a service activation platform that is data driven through user-configurable translations and validation rules.

Most importantly, 8950 VAM offers service providers its one-of-a-kind Task Builder Tool.



Interworks with Most Popular NEsFor North American installations, 8950 VAM interworks with Alcatel-Lucent’s 5ESS® Switches and Sonus Softswitches and certain versions of NORTEL Networks Digital Multiplex System (DMS) Switches.

For installations beyond North America, 8950 VAM interworks with the Alcatel-Lucent’s 5ESS Switch running its international Software Release 5EExx, along with certain versions of Nortel’s DMS Switches and Siemens Information and Communication Networks EWSD® Digital Switching System.

The Alcatel-Lucent Name8950 VAM is backed by Alcatel-Lucent’s proven record of building provisioning solutions and Alcatel-Lucent’s global success in provisioning multi-vendor, multi-application networks of varying sizes.

A Total Integrated Offering8950 VAM offers service providers an integrated hardware and software package that is a feature-rich environment in which to process RC orders. The 8950 VAM product spans the Network Management and Element Management Layers of the Telecommunications Management Network (TNM) through its:

• Flow-through of upstream tasks or business management level software requests• Downstream switch interfaces that are supported for switch configurations in and beyond

North America

The 8950 VAM product package is augmented by related services and support—which includes customer documentation, applicable training courses, and an assortment of installation and maintenance services.

People and 8950 VAM 8950 VAM provides a service activation platform for service providers—who are the local or long distance carriers of voice, data, and video services. Subscribers are those people who purchase voice, data, and video services for their residences, their small offices/home offices (SOHOs), businesses, or corporations from these local or long distance service providers.



8950 VAM System TopologyIt is a three-level system consisting of the Central computers, the EMM and the Switches. Figure 1-1 shows a view of the levels. Different computers may be located in multiple locations, all connected together via networks.



Figure 1-1 System Topology

The Work CentersA Work Center is the location where the 8950 VAM supported provisioning and translations are performed. There may be different locations throughout a company. Personnel performing the provisioning and translations are referred to as End Users. Work Centers are connected to the Centrals through a Wide Area Network (WAN) using the TCP/IP protocol.

The Central ComputersThe Centrals hold the database associated with all of the supported switches as well as the application programs required to query the database; build, change, copy, or delete.



The SwitchesThe next level of this system is comprised of network switches. The Alcatel-Lucent 5ESS© switch is fully supported by 8950 VAM . Each switch has dedicated communication links to the Element Mediation Module (EMM). The 8950 VAM Central communicates with the EMM via a TCP/IP interface. All communications from the Central to the switch flow via a TCP/IP interface via the EMM, as shown in Figure 1-1.

8950 VAM Applications8950 VAM provides a rich suite of capabilities that permits a high degree of automation for repetitive translation tasks, including:

Task Execution Interface • Involves entering only the parameters that change for each order. Based on those parameters,

the system automatically creates an order consisting of the complete set of properly sequenced Recent Changes needed to accomplish the designated task.

Task Builder Environment • A tool based on a set of dynamic order templates that can be customized by each user. The Task

Builder Environment enables users to create and enter orders of Recent Changes as a high level task, provides flexible copy and edit capabilities, and can establish user permissions that restrict the set of users allowed to manage the task order templates.

• Translations Interface for the Shadow database only, that manages various switches, supports multiple switch generics and provides historical data of recent changes. The Translations Interface automates recent changes which support trunking, routing, charging, and complex services. 8950 VAM provides a network-wide view of the switched network.

NOTE:The shadow database contains the tables that are a copy of the records in the switches or Network Elements served by 8950 VAM . These tables are synchronized with the switches through the autonomous message process.

Graphical User Interface8950 VAM can be accessed via a PC-based, web enabled browser.

• The interface provides the user with a variety of windows that present information and choices in a “easy to use” manner.

• The interface also presents a series of “widgets” (Icon, Menus, Menu Bar, Dialog Boxes, Push Buttons, Action Buttons and Scroll Boxes) which provide you with a simple and intuitive way to initiate actions.

• The interface helps you perform the following administration tasks:— User Administration



— Workgroup Administration

— Switch Administration

— Link Monitoring Administration

— Permission Administration

— Recent Change Link Administration

— Automated Code Opening Administration (for Shadow database only)

— Firewall Administration

Hyper Text Transport Protocol Security (HTTPS) The Hyper Text Transport Protocol Security (HTTPS) feature adds Secure Socket Layer (SSL) encryption support to the 8950 VAM Translation Interface and TaskExecution applications. This feature does not support SSL encryption to the upstream CORBA connections.

After a user has logged in via the ‘https’ connection, interaction with the 8950 VAM applications is exactly the same as with an unsecure connection. However, all messages to/from 8950 VAM will be encrypted using the server certificate.

Direct Communication to Supported SwitchesThis system has access to all the supported switches via a link to The Element Mediation Module (EMM).

API ProgrammabilityA system upstream of the Task Toolkit program can achieve translations flow-thru by meeting the Application Programming Interface (API). A significant portion of the routine RC activity can be automated, resulting in dramatic increases in technicians’ productivity. This capability is made available through the API Interface.

8950 VAM File System Configuration

8950 VAM Application Software

The 8950 VAM application software runs on an HP-UX 11i UNIX Platform. The Live Machine runs the full set of application software. The Backup Machine, with no user activity, runs only a small subset.



The system is comprised of UNIX file systems and Informix database tables:• 7 file systems: /, /var, /usr, /tmp, /rc, /tgui, /opt, /stand• Up to 16 swap areas: swap, swap2, swap3, ... , swap16• 2 databases comprised of up to 32 Logical Volumes: DB1 - DB32

The LVM (Logical Volume Manager) and VxVM (Veritas Volume Manager) software is used to manage all disk space. File systems are mounted on logical volumes, which may span multiple disks and are extensible.

The file system-logical volume mappings are specified in the file: /etc/checklist

8950 VAM File System and Log files

Main File Systems

There are many file systems on the 8950 VAM server, but there are three of main importance:

• / --> The root file system is where the HP-UX application files and its kernel reside. Other special user files, UNIX-related configuration files, and temporary files also reside here. For more information on these topics, see the HP-UX documentation.

• /rc --> This file system is for the 8950 VAM error logs and monitors for the 8950 VAM Platform software. This file system also contains all the user login information.

• /tgui --> This is the file system that contains the Task Execution and Task Builder software and configuration files.

— /tgui Areas of Interest; Areas in the /tgui file system of interest to root and int users are the ones where the following are kept:

— Log Files, Error Logs, Configuration Files, Utilities

8950 VAM Software Components8950 VAM software is a collection of software components that are created, manufactured, and distributed by Alcatel-Lucent and/or third-party vendors. Alcatel-Lucent integrates these software components and offers them as a single product.

Each component of 8950 VAM software is loaded on and runs on the desktops or servers. 8950 VAM software is distributed to customers as generic releases and point releases. Patches are electronically transmitted to customers when they are required.

Application Programs, Tools, and Utilities8950 VAM application programs, tools, and utilities enable translation technicians to process RC orders and the system administrators to administer and maintain the entire 8950 VAM system. A set of Power Tools enable tasks to be executed in batch; and the



more flexible tools available in Task Toolkit, enable tasks to be built based on a set of requirements and to be processed by entering only those parameters that change for each RC order.

Upgrade OptionsYou can upgrade the following components:

• 8950 VAM Component• Task Toolkit Component• Task Builder Component• SSG (Soft Switch Gateway) Component. SSG component is only supported on 64 bit HP

hardware platforms not 32 bit hardware platforms

The upgrade procedures vary depending on your site specific configuration information. For detailed upgrade procedures, see the release bulletins that accompany each software upgrade.

Operating Systems and Browsers8950 VAM software components also consist of industry-standard UNIX® and Windows™ based operating systems that govern overall system processes and compatible browsers, such as Netscape Navigator and Internet Explorer, that control access to corporate intranets and the global Internet.

Database Management SystemFor North American installations, the 8950 VAM database and its management system contain a shadow (copy) of all switch data. The switch data is initially extracted from the particular switch and is automatically kept synchronized. Once the data is extracted and synchronized, numerous types of queries of that data can be made.

8950 VAM Software Naming ConventionsThis software is described in terms of features, capabilities and benefits. The software package will carry a four digit designation. The first two digits signify the generic release number. The last two digits signify the patch release number.

Issue: GA-1, July 20101 - 1 0


Figure 1-2 Naming Convention for Generic and Patch Releases

GENERIC RELEASES• A generic release consists of a “core package” and a group of feature packages. The core

provides enhancements to the infrastructure of all of the software. Features are packaged and released periodically. Customers can review the features and purchase specific sets of features.

PATCH RELEASES

A patch release will contain fixes to reported software problems and minor enhancements to either the core or to specific features.

— Patch releases will be issued periodically.

— Patch releases will be issued automatically to customers with Service Contracts.

— Patch releases may be ordered separately by customers without Service Contracts.

RTU’s and Licenses for 8950 VAM

Right To UseNew generics of 8950 VAM software are purchased and delivered under a Right-To-Use (RTU). There are two RTU's associated with 8950 VAM . They are:

• The initial RTU• An update RTU

Each will be separately described and priced.

LicensesIn addition to the RTU, there are several licenses associated with 8950 VAM software. The license authorizes you to operate the various vendor-supplied software packages purchased by Alcatel-Lucent and incorporated into the 8950 VAM software. Licenses are required for:

• HP-UX© (Central) – The UNIX operating system supplied by HP.• INFORMIX ©(Central) – The database management software.• ORBIX©

• BaseWorx©

Example: Release 16.0.X

16.0.X = The Generic Release

.X = The Patch Release

Issue: GA-1, July 20101 - 11


..............................................................................................................................................................................................................................................About Alcatel-Lucent Electronic Delivery (LED) Website

The Alcatel-Lucent Electronic Delivery (LED) website helps you access product support information, including manuals and guides, release information, technical notes, and downloads. Browse the Product Index in the LED website to view the list of web supported products to find documentation and downloads.

Issue: GA-1, July 20101 - 1 2




2 VAM System Monitoring

Overview

The purpose of this chapter is to provide information about 8950 VAM Application administration. The following topics will be covered:

• VAM System Admin Tasks

• VAM Software versions

• Cronjob information



System Admin TasksThis chapter details many of the administrative tasks that should be perform by the administrator of the system on a periodic routine basis. Any problems and/or issues with any of the tasks should be referred to the ALU product support team for further technical help and debug.

Check Filesystem space1. Log in as int/root from either the console or a PC via telnet into the L1 machine:

login: int or root Password: <password>

2. Issue the following command:

[-int] bdf

Result: A similar messages will appear on the screen.

Filesystem kbytes used avail %used Mounted on/dev/vg00/lvol3 524288 144038 356499 29% //dev/vg00/lvol1 512499 43330 417919 9% /stand/dev/vg00/lvol8 4194304 1632390 2402781 40% /var/dev/vg00/lvol7 4194304 1247946 2762279 31% /usr/dev/vg00/lvol4 4194304 139325 3802370 4% /tmp/dev/vg01/tgui 4194304 271617 3677898 7% /tgui/dev/vg00/lvol6 8388608 4889529 3280434 60% /opt/dev/vg00/lvol5 524288 16592 475971 3% /home/dev/vg01/rc 4194304 1570244 2461054 39% /rc

Useful UNIX Commands:• find /rc -size +1000000c -print• ls -latr | sort -nk5 or ls -latr | sort -rnk5• du /rc | sort -nk1



Cleanup /rc file system space1. Log in as int from either the console or a PC via telnet into the L1 machine:

login: int Password: <int_password>

• Menu option: [xxxxx-int] menu — 9) System Commands Menu

— 9) Remove Old Error Files

Remove all error files more than how many days old? <input_days>

• Other directories to cleanup: /rc/data, /rc/users/int, /rc/odd_load

Check database space1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] /tgui/bin/chk_db_space

• Ignore the output for “rootdbs”

• Look under column “free” and ensure mimimum of 100K blocks are free.


dbsnum dbspace size used free

1 rootdbs 2160640 1660681 499959 2 db2 3133440 550699 2582741 3 db3 4182016 2162887 2019129 4 db4 4182016 1468634 2713382 5 db5 4182016 849619 3332397 6 db6 4182016 1222622 2959394 7 db7 4182016 624731 3557285 8 db8 3201024 135078 3065946



Check int/root mail1. Log in as int/root from either the console or a PC via telnet into the L1 machine:



[-int] mailx


mailx Revision: 1.179.214.2 PHNE_34304 Date: 07/01/23 01:29:55 Type ? for help."/usr/mail/int": 9428 messages 9428 new>N 1 [email protected] Thu Aug 23 16:58 15/638 N 2 [email protected] Thu Aug 23 21:37 15/500 Create DARICS Data File F N 3 [email protected] Thu Aug 23 21:37 13/488 Merge 5E16FR5 Data File F N 4 [email protected] Fri Aug 24 00:20 15/552 Transfer DARICS Data File. . . . .. . . . .. . . . .N 20 [email protected] Wed Aug 29 21:37 15/500 Create DARICS Data File F?

Useful mailx commands

d --> deletes the message. d1-20 --> Deletes messages 1 thru 20.

q --> quit with save. x --> Quit without saving.

h --> print header of message. help --> Help menu options.



Change root password1. Log in as root from either the console or a PC via telnet into the L1 machine:

login: root Password: <root_password>


# passwd

Changing password for rootNew password: <New Password>Re-enter new password: <Retype_New Password>Passwd successfully changed

Change int password1. Log in as root from either the console or a PC via telnet into the L1 machine:



# passwd int

Changing password for intNew password: <New Password>Re-enter new password: <Retype_New Password>Passwd successfully changed

3. Issue the following commands:

# su - int

[xx-int] /topasrc/bin/retro_user_pw


retro_user_pw: Password retrofit for CONNECTVU users started.retro_user_pw: passwords for CONNECTVU users updated.

Alternate option to change int password

• Menu option: [xxxxx-int] menu — 2) 8950 VAM System Administration Menu

— 6) User Administration Menu

— Use “Change” option to change password.

• Alternate option to change int password:— Use GUI interface to access “User Admin Screen” and change

password.



VAM Software VERSIONS

8950 VAM Application Versions

1. Log in as int/root from either the console or a PC via telnet into the L1 machine:



[# or int] cat /version*


#### 8950 VAM Release: 16.0.1 ####

#### 8950 VAM SoftSwitch Gateway Release: 16.0.1 ####

#### 8950 VAM TGUI Release: 16.0.1 ####

#### VitalSuite Voice AM TOA Release: 12.2.1.1 ####

NOTE:You will see software release information for your appropriate software loaded on the VAM system.

INFORMIX Version

1. Log in as int/root from either the console or a PC via telnet into the L1 machine:

login: int Password: <int password>


[int] onstat -


IBM Informix Dynamic Server Version 9.40.HC5 -- On-Line -- Up 11 days 19:56:17 -- 390192 Kbytes

8950 VAM Software version

8950 VAM Softswitch version

8950 VAM Tasktoolkit version

8950 VAM TOAz version



Check Informix Logical Logs1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] onstat -l


IBM Informix Dynamic Server Version 9.40.HC5 -- On-Line -- Up 11 days 19:58:13 -- 390192 Kbytes

Physical LoggingBuffer bufused bufsize numpages numwrits pages/io P-1 0 16 559127 38069 14.69 phybegin physize phypos phyused %used 2:53 358400 186198 0 0.00

Logical LoggingBuffer bufused bufsize numrecs numpages numwrits recs/pages pages/io L-1 0 16 20546965 566684 38877 36.3 14.6 Subsystem numrecs Log Space used OLDRSAM 20546965 1132528300

address number flags uniqid begin size used %usedd5636fc8 4 U-B---- 514 3:53 148480 148480 100.00d54e4da8 5 U---C-L 515 3:148533 148480 79591 53.60d54e4df0 6 U-B---- 510 3:297013 148480 148480 100.00d54e4e38 7 U-B---- 511 3:445493 148480 148480 100.00d54e4e80 8 U-B---- 512 3:593973 148480 148480 100.00d54e4ec8 9 U-B---- 513 3:742453 148480 148480 100.00 6 active, 6 total

Options to review:• Logical log = FULL when %USED=100 & Flag does NOT have “B”.• Logical Log = Empty, when %used=100 & flag has “B”.• Under “flags” column, “B” means log space is fully backed up.



Crontab CustomizationThe crontab utility is used to execute commands automatically at predefined times and dates. The CRON is a process on the 8950 VAM system that runs commands at specified times and dates. The schedule of the jobs to be run for the VAM system are briefly described below.

! CAUTION:DO NOT modify any of the cron job w/out confirmation from the ALU product support team within Alcatel-Lucent.

Root cron customization

1. Log in as root from either the console or a PC via telnet into the VAM system.

login: root Password: <root password>

2. Create the crontab entries per your requirements into a “hidden-file” called crontab into the root directory. Add any cron entries into the file as required.

# ls -la /.crontab

NOTE:The system will automatically merge the file on an-ongoing basis.

• Do NOT make any custom changes to the /var/spool/cron/crontabs directory. Updates for cron in this directory will NOT be kept if the system is rebooted and/or upgrade to a new VAM software release.

3. If you want to change to take affect immediately, then run the following as root.

# /rc/rc.d/cron_update

• If you do NOT run the following, the cron updates will take place during next system reboot.

User Login cron customization

1. Log in as the specific user from either the console or a PC via telnet into the VAM system.

login: <user> Password: <user password>

2. Create the crontab entries per your requirements into a “hidden-file” called crontab into the home directory for the specified user. Add any cron entries into the file as required using your favorite editor.

$ vi /rc/users/<User_Login>/.crontab

3. Ensure that the crontab file per your requirements is created into a “hidden-file” called /crontab into the home directory for the specified user. To check if the file exists, run the following.

$ ls -la /rc/users/<User_Login>/.crontab



NOTE:The system will automatically merge the file on an-ongoing basis.

• Do NOT make any custom changes to the /var/spool/cron/crontabs directory. Updates for cron in this directory will NOT be kept if the system is rebooted and/or upgrade to a new VAM software release.

4. If you want to change to take affect immediately, then run the following as root.

# /rc/rc.d/cron_update

• If you do NOT run the following, the cron updates will take place during next system reboot.

Details of 8950 VAM cron jobs for INT login:

• /topasrc/bin/VERDAEMON --> Checks to see that the 8950 VAM Daemon process is running every hour.

• /topasrc/bin/conn_links --> Sends a Connect Links command from cron once every hour to keep the links up all the time.

• /topasrc/bin/VER_SRVRS --> Verifies 8950 VAM Servers on the system every 30 minutes on the hour and half-hour to restart any processes that may have died or hung.

• topasrc/bin/AUTO-SNDR --> Sends orders to the switch at the due date and time.• /topasarc/bin/getdloadtime --> Script reads rc5_sw_prof_fid table for a list of DMS

switches, and based on a comparison with the value for the hour stored in file_dload_time, makes the decision to download TNM files from the switch.

• /topasrc/bin/RESET_NST --> Resets the number of restarts for the 8950 VAM processes in the system back to zero (maximum value=5) every day at midnight.

• /topasrc/bin/RM_OLDFLS 30 --> Removes all the process error files after a specified period of days (default=30 days).

• /topasrc/bin/stat_files--> Moves the output of <sysname>.stat file to <sysname>.yyyymm file.

• /topasrc/bin/rti_cron--> Checks the Feature Name table to see whether the customer inventory tables feature is turned on and checks rsv_rti table value settings.

• /topasrc/bin/trans_bmpfile--> Invokes the tools to transfer the BMP data file to the BMP Production and Disaster Recovery sites.

• /topasrc/bin/send_daricsfile--> Sends data files created in 8950 VAM and TRUNK to the user system via the CONNECT:Direct interface.

• /topasrc/bin/DMSPWD--> Updates the password for DMS switches when the password interval expires.

• /topasrc/bin/run_clean--> Routine that calls other routines to clean up database resources every fifteen minutes.

• /topasrc/bin/noc_cron--> Checks the Feature Name table to see whether the customer inventory tables feature is turned on and checks NOC table value settings.

Issue: GA-1, July 20102 - 1 0


• /topasrc/bin/ars_cron --> Synchronizes the data in the inv_ars_feat custom inventory table with the data in the shadow database tables.

• /topasrc/bin/reserve_cron--> Synchronizes the data in the inv_gen_rsv custom inventory table with the data in the shadow database tables.

• /topasrc/bin/rsv_si_cron--> Re-synchronizes the reservation data in the Custom Inventory table with the Shadow Database.

• /topasrc/bin/rsv_callattr_cron--> Synchronizes the data in the custom inventory table inv_rsv_callattr.

• /topasrc/bin/rsv_simap_cron--> Synchronizes the custom inventory SI mapping table inv_scr_index.

• /topasrc/bin/rsv_ltid_cron --> Synchronizes the data in the custom inventory table inv_rsv_ldid.

• /topasrc/bin/echo_tnm CRON DMS--> Runs audit of TNM files for all DMS switches to sync database.

• /topasrc/bin/echo_tnm CRON 5E--> Runs audit of TNM files for all 5ESS switches to sync database.

• /topasrc/bin/create_bmpfile--> Creates the BMP file and sets up the proper 8950 VAM runtime environment.

• /topasrc/bin/creat_daricsFile --> Queries the shadow database and creates the files to send to the DARICS machine.

• /topasrc/bin/time_link_up 1--> Executes each day to capture information and produce a report from the sysadm menu of up and down times for links from these pre-created files.

• /topasrc/bin/SAVE_FLS --> Saves all the system error files from <processname>.err to <process name>.<date> five minutes before midnight

• /topasrc/bin/SystemMonitoringTool --> Invokes the Proactive System Monitoring tool at a time specified by the Administrator.

• /topasrc/bin/UIipc_cln -s --> Cleans up the rc5_ipc_fid table for users not occupying a socket. The rc5_ipc_fid table controls the allocation of socket port numbers used by ROUT and Ulasyipc

• /topasrc/bin/start_ubic --> Starts the UBIC process that processes ecel files if the feature is enabled.

• /topasrc/bin/purge_nbi_log --> Purges the trace and error files generated by the SOAP North Bound Interface processes.

Issue: GA-1, July 20102 - 11


Issue: GA-1, July 20102 - 1 2




3 VAM Hardware Admin/Monitoring

Overview


• VAM Hardware Admin

— HP System reboot, shutdown, startup

• HP System Booting options

• System Backups/Restore



HARDWARE OVERVIEW8950 VAM hardware is a collection of industry-standard, electronic devices that are created, manufactured, and distributed by various third-party vendors and Alcatel-Lucent. The hardware consists of devices that reside and function in the following environments:

• Work Center environment, which includes end user desktops, the 8950 VAM system console, and local and network printers.

• Switch/Network environment, which includes 8950 VAM-supported digital switching systems (Class 5 Switches) and intermediary devices such as packet switches, routers, and terminal servers that provide an interface to the switching systems.

• HP Server environment, which includes the HP servers, their associated printers and HP consoles, and, for North American installations configured with the shadow database, an Off-Switch Workstation (OSW).

• 8950 VAM relies on the HP Enterprise Server family to process user requests and to housethe following information: The database associated with all supported switches & theapplication programs required to provision the switches.

The devices residing in these environments are interconnected to each other and to the other areas by a LAN/WAN network.

HP Enterprise Server Hardware Configuration8950 VAM hardware platform is supported on the HP 9000 Enterprise Server of PA-RISC processor family architecture. The hardware systems can be configured in DUPLEX mode (2 physical processors) or SIMPLE Mode (Single processor).

Hardware configuration• Flexible Configuration: ALU makes minimal requirements & customer makes the final

system configuration; can be in SIMPLE or DUPLEX mode. ALU makes recommendation on DISK Redundancy, LVM config, etc.

— All Hardware must be Flexible Configurations.

Physical processor ModeVAM Hardware systems can be configured in DUPLEX mode or SIMPLEX Mode.

• DUPLEX will have two physical processors, or Physical Machines, and are identified as "A" and "C" processors.

• SIMPLE will have a single processor as “A” processor.

Each processor can function as a live system (L1) or backup System (BU) depending on the boot disk. These run two distinct system names, also known as Virtual Machines.



HP System Virtual System NamesAll 8950 VAM systems are configured to have a Live system boot disk and Backup system boot disk. This information should be available as comments in file: /etc/fstab . Configuration file for the system role: /etc/local/config.d

Based upon the disk that is used for booting, the system may either be the Live (L1) or the Backup (BU) system.

Virtual Machine - a specific set of software which can run on either (but not more than one) physical processor at any one time. The following virtual machines exist:

• Live System = Normally every day operations system for application that contains, the VAM Application, database, GUI software, etc.

• Backup System = System used to perform emergency admin functions that contains minimal VAM Application software.

NOTE:Some customer may have two physical system hardware (Duplex Configuration) and thus they run Live system on processor and Backup system on the other processor. For customers with a single physical processor (Simplex Configuration), the machine can only be either the Live or Backup system.

Live (L1)System Backup (BU) System

Volume Group = /dev/vg00 & /dev/vg01 Volume Group = /dev/BU

Application Available = yes Application Available = no

Database Available = yes Database Available = no

Normal Operation Use Emergency Operation Use

grep -i mach /etc/local/config.d

--> VMACH=L1

grep -i mach /etc/local/config.d

--> VMACH=BU



Hardware Admin Support— Alcatel-Lucent does NOT support any of the customer’s hardware systems unless specifically

stated in contracts. Technical support needed for the systems should be directed each customer’s Local Hardware technical support team.

• ALU does NOT provide Hardware support on systems.• Customer is responsible for their Hardware support.

Additional Hardware support can be found from the hardware vendor’s appropriate website. If you have any further questions/concerns, contact the ALU Technical support for details.



HP System AdminThe following process can be used to perform a complete 8950 VAM hardware administration.

! WARNING:Any problems during this process should be referred to your HP Hardware support team.

HP System Shutdown1. Log in as int from either the console or a PC via telnet into the L1 machine:



# cd /

# shutdown -h 0 --> System shutdown message appears.

NOTE:You may power off any hardware components that is desired. Any problems during this process should be referred to your HP Hardware support team. Refer to the HP website for further info on your hardware platform.

HP System Startup1. Ensure that all your HP system peripherals are powered up and fully operational.

2. You may need to access the console (web console, direct console, etc.) and issue the following sequence of commands to power-up the system. (Slight variations may occur & further help should be directed to your HP support contacts).

— At the CM> or GSP> prompt, press “<Control>” & “b” keys simultaneously.

GSP> <Crtl> b

GSP> rs

Execution of this command irrecoverably halts all system processing andI/O activity and restarts the computer system.

Type Y to confirm your intention to restart the system: (Y/[N]) y -> SPU hardware was successfully issued a reset.

! CAUTION:At this point, the system will reboot & boot messages will appear on the screen. The 8950 VAM application will auto start if the flag (Navis_Voice_AM=1) is set in the file: /etc/rc.config.d/Navis_Voice_AM.



HP System reboot1. Log in as int from either the console or a PC via telnet into the L1 machine:



# cd /

# shutdown -r 0 --> System shutdown message appears.

HP System boot (Single-User)

From Multi-User Mode1. Log in as int from either the console or a PC via telnet into the L1 machine:



# cd /

# shutdown 0 --> System shutdown message appears.

From Firmware Mode1. From the console, perform the following.

— At the CM> or GSP> prompt, press “<Control>” & “b” keys simultaneously.

GSP> <Crtl> & b

GSP> rs

. . . . .Type Y to confirm your intention to restart the system: (Y/[N]) y

. . . . .

. . . . .Main Menu: Enter command or menu >Process is starting autoboot processTo discontinue, press any key within 10 seconds --> Ensure to interrupt the autoboot.

2. Interrupt the auto-boot by pressing any key on the system:

Main Menu: Enter command or menu > bo priInteract with IPL (Y or N)?> yISL> hpux -is --> System will boot to single user mode.



HP System Boot AdminThe following information can be used as a reference to setup boot configuration parameters on the HP system. The following details should be used as reference, please refer to the vendor for complete details & accuracy of the steps as they may change and not fully reflected here.

Prerequisite

• You must know the primary & alternate boot path’s for Live System.• You must know the primary boot path for Backup system. (Alternate path does NOT exist).

Configuration of the boot path can occur from the following stages of the system boot process:

• System is fully booted into Multi-User mode• System is interrupt booted into MAIN Menu mode• System is interrupt booted into ISL mode

Multi-User Mode Boot Config

1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Run the following commands to boot from the just configured boot path’s:

# lvlnboot -v --> Lists boot disks defined in system.

# setboot --> Lists the current boot path settings

# setboot -p <Primary_bootdisk_Address>

# setboot -a <Alternate_bootdisk_Address> -s off -b on

— The admin should have the disk address of the live boot disk.

# setboot --> Ensure that boot path are set per your requirements

• Reboot system via:

# cd /

# shutdown -r 0



Interrupt Boot BCH Main Menu Mode Boot Config

1. Once you have accessed the Interrupt the auto-boot Main Menu prompt, run the following.

Main Menu: Enter command or menu > path --> Lists boot disks defined in system.

Main Menu: Enter command or menu > path pri <Primary_bootdisk_Address>

Main Menu: Enter command or menu > path alt <Alternate_bootdisk_Address>

Main Menu: Enter command or menu > bo pri --> Boot system to primary path.Interact with IPL (Y or N)?> n

Interrupt Boot ISL Mode Boot Config

1. Once you have accessed the Interrupt the auto-boot Main Menu prompt, run the following.

Main Menu: Enter command or menu > bo priInteract with IPL (Y or N)?> y

ISL> primpath <Primary_BootPath>ISL> altpath <Alternate_BootPath>

ISL> display --> Lists the current boot path settings

ISL> hpux boot /stand/vmunix --> Boot to default boot level

ISL> hpux -is --> Boot to single-user mode (if applicable)

ISL> hpux -lm --> Boot LVM Maintenance mode (if applicable)



Replacing the DiskFor any failed disks on the system, your hardware technical support team should be contacted to perform this operation. This section provides insight information about the standard procedure to replace a disk that may be used.

High Level overview

• Determine address of failed disk • Replace the failed disk• Issue commands to add/sync the disk.

1. Log in as root from either the console or a PC via telnet into the L1 machine:


2. Run the “ioscan” command to find address of failed disk. You will need to find the scsi address from the line that has hardware address.

# ioscan -funC disk

3. Detach all the paths to the failed physical volume.

# pvchange -a N /dev/dsk/cX tYdZ

4. At this point, the failed physical volume should be replaced.

5. Sync the disk and activate the system VG via command.

# vgcfgrestore -n VG /dev/rdsk/cXtYdZ (use raw device address)

— X is the controller number;

— Y is the SCSI ID;

— Z is usually 0 unless SAN or disk array technology is used.

# vgchange -a y <VGNAME>

# vgsync <VGNAME> &

— Where <VGNAME> is the Volume Group name (ex: /dev/vg01).

6. The following command must be run if you replacing a failed bootable disk to fix any lifboot corruption. If you’re NOT sure, run the commands anyway.

# / Instal l / l i fboot

7. Enter the following to remove the file called /etc/local/.disk_problem:

# /etc/ local/disk_check -r

Issue: GA-1, July 20103 - 1 0


Issue: GA-1, July 20103 - 11


Flex Backup Solution This section provides information about scheduling a HP System Backup for 8950 VAM .

HP-UX 11.11 now supports two volume managers:• Logical Volume Manager (LVM)• VERITAS Volume Manager (VxVM)

The Alcatel-Lucent supplied Backup and Recovery solution only supports the Logical Volume Manager (LVM) not the VERITAS Volume Manager (VxVM). The vast majority of HP-UX 11.11 deployments use LVM for at least the boot drive and almost all HP customers using VxVM are sophisticated enough to provide a corresponding backup and recovery solution that complements the VxVM managed hardware (usually Storage Area Networks [SANs]).

Logical Volume Manager (LVM)

All Logical Volumes must be either mirrored at the LVM level OR be media protected by RAID-0,3,5 controllers at the hardware level (for example, HP's RAID-0,3,5 controllers).

• These controllers hide the RAID-0,3,5 details from LVM and hence are supported. • These hardware implemented RAID controllers also have a redundant controller interface to

LVM. SAN devices also fall into the category.• LVM disk stripping (RAID-0,3,5) is not supported because most of the LVM stripping modes

can not be mirrored at the LVM level. The one exception is LVM Extent-based-Stripping, but it's not supported by the Alcatel-Lucent bundled Backup and Recovery solution due to it's generally poor striping performance.

• It also does not support files managed with Audit Control List (ACL) either. Most VAM customers are not interested in these HP-UX advanced feature anyway.

Some of the limitations listed are imposed by the vendor provided bundled software being used (either HP and IBM/Informix).

Customers are always strongly encouraged to use their own Backup and Recovery solution. Most VAM customers have their own Backup and Recovery Procedures Standards in place and prefer to use them over this locally provided solution.

• Any backup solution that is chosen, supplied by Alcatel-Lucent or otherwise, should be tested for at least one complete backup and recovery cycle BEFORE the VAM server is placed into production status!

• This is critical because each VAM server is unique to each customer with the deployment of Flex Configurations.

• It's not cost effective for Alcatel-Lucent to test all Flex Configuration equipment combinations in its lab environments.

Issue: GA-1, July 20103 - 1 2


Alcatel-Lucent Backup SolutionThe Backup portion of the solution does not rely on either disk mirroring or the file system snapshot technologies. In other words it does not backup mirrored copies of the disks that are taken "offline" or change the disk mirroring states in any way.

• Disk mirroring integrity is maintained during the backup and hence not exposed to single points of failure.

• The bundled solution does not use "Point-in-time" file system snapshots. HP's optional software component, OnlineJFS, implements the file system snapshot feature for VxFS file systems. Flex Configuration backups always run on the Live server. VAM customers are strongly encouraged to purchase and use this software especially when High Availability solutions are being implemented.

• For Duplex configurations, each performs its one backup (e.g. runs locally on each server). A backup of the Live server's disks is always done using the Live server. A backup of the Backup server's disk is always done using the Backup server.

• For Simplex configurations, A backup of the Live server's disks is always done using the Live server. A backup of the Backup server's disk is always done booting system into single-user mode.

• The solution simply uses wrapper shell and perl scripts that are table driven from configuration files stored in the file system and database. These configuration objects are populated once when the server is deployed and again upon each new VAM release upgrade.

The Alcatel-Lucent bundled Backup and Recovery solutions uses wrapper shell and perl scripts that are table driven from configuration files stored in the file system and database and simply involves making tape based backup copies of:

• OS file systems & VAM application file systems (FS Tape)• VAM Informix database (raw disk storage) - (DB Tape)

Admins performing the backups should be very familiar with both vendor's underlying provided software components. The solution utilizes HP and IBM/Informix bundled software.

NOTE:The bundled solution provides a command line interface that can be invoked via the UNIX "cron" service. Backups should always be scheduled at the least busy period of each day. Avoid scheduling times that are exact 5 minute multiples.

A two tape drive minimum is required for a backup set, one to maintain backup copies for the file systems and the other for the VAM database.

! CAUTION:Only simple locally attached tape drive devices are supported (e.g. no stackers or tape library devices).

Issue: GA-1, July 20103 - 13


All backup and recovery wrapper activity is logged to files that reside in /tmp. Files in /tmp remain there for 7 days before being purged.

• File systems are backed up using HP's dump and vxdump utilities. — They are restored with corresponding HP utilities: restore and vxrestore.

— /tmp file system & any Logical Volumes associated with swap areas are NOT backed up nor restored.

• VAM's Informix database is backed up and restored using the IBM/Informix Storage Manager (ISM) component.

• Also, the database portion of the backup media is always verified as the last step of each backup. Verification failure causes a backup failure (e.g. tape cartridges remain online and do not eject).

— For the IBM/Informix software component, ISM, IBM/Informix documents in either PDF and HTML formats are available at http://www.ibm.com/software/data/informix/pubs/library/.

— You can also order hardcopy versions of these manuals from the IBM Publications Center at http://www.ibm.com/software/howtobuy/data.html.

• IBM Informix Storage Manager Administrator(TM)s Guide Version 2.2 (G251-2299-00),

• IBM Informix Storage Manager Backup and Restore Guide Version 9.4 (G251-1240-00)

• IBM Informix Storage Manager Backup and Restore Guide Version 10.0 (G251-2269-00) (foradditional reference material only VAM uses 9.4).

• Alcatel-Lucent recommends using the highest performance tape drives supported by the hardware and software components (HP and IBM/Informix).

• This methodology reduces the media involved to a minimum which results in a higher quality backup solution from both an equipment and human error perspective.

• Further Alcatel-Lucent strongly recommended that daily Live server backups are scheduled with a minimum of a 14 day retention policy.

• Backups of the Backup boot drive should be run at least once every three months or whenever software on this boot drive is modified (e.g. addition or removal of 3rd party software, OS patch installations, VAM software upgrades) and have a 3 copy retention minimum.

Configure Alcatel-Lucent Backup Solution The following steps should only be run if you plan to setup and configure the Alcatel-Lucent recommended and provided system backup solution. These steps should be run on Live & Backup systems.

• This is a one time configuration, unless you run into problems and/or have configuration changes in software/hardware.

• Live HP server required config files & ISM configuration• Backup HP server only required configuration of config files.

Issue: GA-1, July 20103 - 1 4


Setup backup config Files.



2. create backup file (/etc/userbackupdata) in 2 column format. 1st column = LV Name, 2nd column = TAPE Device address using your favorite editor on the HP system.

# vi /etc/userbackupdata

— You will need to separate the DB chunks onto 1 tape device and the File systems onto another tape device.

• Sample FS entry: /dev/vg00/lvol1 /dev/rmt/0m— For swap & /tmp, you may just put /dev/null in 2nd field. Do not backup.

— Sample command to list all LVM’s ( vgdisplay -v | awk '/LV Name/ {print $3}' )

• Sample DB chunk entry: /dev/vg01/chunk01 /dev/rmt/1m— You should backup all DB chunks.

• Sample (/etc/userbackupdata) file

/dev/vg00/lvol1 /dev/rmt/1m/dev/vg00/lvol2 /dev/null/dev/vg00/lvol3 /dev/rmt/1m/dev/vg00/lvol4 /dev/null/dev/vg00/lvol5 /dev/rmt/1m/dev/vg00/lvol6 /dev/rmt/1m/dev/vg00/lvol7 /dev/rmt/1m/dev/vg00/lvol8 /dev/rmt/1m/dev/vg01/rc /dev/rmt/1m/dev/vg01/tgui /dev/rmt/1m/dev/vg01/chunk01 /dev/rmt/0m/dev/vg01/chunk02 /dev/rmt/0m/dev/vg01/chunk03 /dev/rmt/0m/dev/vg01/chunk04 /dev/rmt/0m/dev/vg01/chunk05 /dev/rmt/0m. . . . . . .. . . . . . .. . . . . . ./dev/vg01/chunk63 /dev/rmt/0m/dev/vg01/chunk64 /dev/rmt/0m/dev/vg01/chunk65 /dev/rmt/0m/dev/vg01/chunk66 /dev/rmt/0m

• For live system setup, you should input all the FS & DB chunks. • On the Backup system, you only have the FS. DB chunks do not exist on the backup system.

3. Setup config files for dump & vxdump.

# touch /var/adm/dumpdates

Issue: GA-1, July 20103 - 15


# touch /var/adm/vxdumpdates

Configure ISM - (Live System Only)

ISM configuration is only required on the Live HP server. The BU server does NOT contain any DB thus, this step should be skipped.

4. Run the following steps to configure ISM:

# . /topasrc/bin/stenv (do not forget the dot)

# /rc/informix/bin/ism_shutdown

# /rc/informix/bin/ism_startup -init

# /etc/local/ISM_add_devs -o -L m -l /dev/rmt/<X>mn -s /dev/rmt/<X>mn

— You should substitute the <X> with your tape drive that will save the DB backup.

5. Bounce Informix :

# /rc/shutdown.d/stop_informix

# /rc/rc.d/start_informix

6. At this point, the Alcatel-Lucent provided backup configuration is complete.

Issue: GA-1, July 20103 - 1 6


Run Flex Config Backup (Live)The following steps should be used to perform a FULL system backup of the Live HP server. The output of the command goes to standard out & thus each admin can configure the output to their specific needs (log file, mail, etc.).

NOTE:It is strongly advised that backups are performed on a daily basis & put into cron if required.




# /etc/local/flexonlinebackup -f


Useful Backup Log Files

Logs Directory: /tmp/bck.<yymmdd>/<sysname>

OS Log File: stat_bckup<PID>

DB Log File: stat_bckup<PID>_db

ISM Log File: /rc/data/bar_act.log

Additional Files: /tmp/bck*

Issue: GA-1, July 20103 - 17


Run Flex Config Backup (BU)1. Log in as root from either the console or a PC via telnet into the BU machine:


# shutdown 0 (Run only if in SIMPLEX Configuration to boot into Single-User Mode)


# /etc/local/flexonlinebackup -F


• Logs Directory: /tmp/bck.<yymmdd>/<sysname>• OS Log File: stat_bck<PID>

Issue: GA-1, July 20103 - 1 8


Flex Config Recovery - OverviewLive HP System Recovery Overview

A complete recovery of the Live server's storage is a two step process that requires you to boot from the backup boot disk.

• Step 1 of the process recovers the Live OS and VAM application file systems from tape to disk• Step 2 recovers the database from tape to disk.

At the completion of these two steps, the Live disks are NOT in LVM mirrored state. LVM Live disk mirroring must be enabled manually by the admin following a recover completion.

NOTE:However, the VAM application can be made available during the mirroring resync processing. The resync processing could take several hours to complete depending on the hardware, capacity of the drives and number of drives involved.

Live HP System (L1) Recovery - FLEX

File System Recovery - L1

STEP 1: The file system recovery step is performed by booting the system from the Backup server boot disk.

2. Ensure that the File System backup tapes are (write-protected) and mounted in the available tape drive of the system.

3. Issue the following command to start the file system recover:

1. Ensure you are logged in as root on the backup boot disk; depending on whether your system is SIMPLEX or DUPLEX.

• DUPLEX Systems: Halt the L1 processor & Log in as root from the console on the BU processor:


• SIMPLEX Systems: Login on the processor & reboot the system. You must interrupt boot the disk and ensure you boot of the Backup boot disk.

Issue: GA-1, July 20103 - 19


# /etc/local/flexonlinerecover /dev/rmt/1mn (do NOT forget the “n” option)

— The assumption is that tape address = /dev/rmt/1mn

INFO: The file system backup tape(s) should be loaded write-protected with:the white tab pushed to the left (DAT) OR the black tab pushed to the left (DLT) OR the red tab pushed to the right (LTO).Press the [ENTER] key when ready to continue.

• Press <CR> to start the recovery.


flexonlinerecover: 19:48:55 Rewinding /dev/rmt/1m.0+1 records in0+1 records outDate of backup in tape drive /dev/rmt/1mn is: 2003_11_05_14:26

Is this information correct? (Y|N) [D:N] y

NOTE:If the tape in the drive is NOT the FS backup, you will receive a warning message to change the tape out.


flexonlinerecover: 19:49:07 c3t3d0 is BOOTABLE.flexonlinerecover: 19:49:08 BACKUP DEVICE is /dev/rmt/1mn.pvcreate -f /dev/rdsk/c8t2d0Physical volume "/dev/rdsk/c8t2d0" has been successfully created.mkdir /dev/extramknod /dev/extra/group c 64 0x10000vgcreate -A n -s 64 -p 20 -e 1016 -l 255 /dev/extra /dev/dsk/c8t2d0Volume group "/dev/extra" has been successfully created.pvcreate -B -f /dev/rdsk/c3t3d0--------------------------------------------------------------flexonlinerecover: 20:46:29 Recovery completed.

• Logs Directory: /tmp/rec.<yymmdd>/<sysname>• OS Log File: stat_rec<PID>

4. Issue the following command to reboot the system to Live Boot disk:

# setboot -p <live_bootdisk_address>


# shutdown -r 0

Database Recovery - L1

STEP 2: The database recovery step is performed by booting the system from the Live server boot disk.

Issue: GA-1, July 20103 - 2 0


5. Ensure that the Database backup tapes are (write-protected) and mounted in the available tape drive of the system.



7. Issue the following command to start the database recover:

# /etc/local/flexdbrecover /dev/rmt/0mn (do NOT forget the “n” option)


Device /dev/rmt/0m has tape with label 2008_04_01_11:12_0.Is this information correct? (Y|N) [D:N] y

• Type “Y” and Press <CR> to start the recovery.


start_ism: is starting the ISM daemons.start_ism: Bootstrap information is not printeddlt tape 2008_04_01_11:12_0 mounted on /dev/rmt/0mn, write protectedExecuting onbar -r -pPhysical restore complete. Logical restore required before work can continue.Executing onbar -r -lWaiting for Informix to go Off-line.flexdbrecover: Completed successfully.Now set the system's primary and alternate boot paths, if necessary, then reboot the system to complete the restore processing.

• DB Log File: stat_rec<PID>_db• ISM Log File: /rc/data/bar_act.log

Issue: GA-1, July 20103 - 21


• SIMPLEX Systems: Reboot the processor as the Live (L1) system via :# setboot -p <live_bootdisk_Primary_Address>

# setboot -a <live_bootdisk_Alternate_Address> -s off -b on


# cd /

# shutdown -r 0

• DUPLEX Systems: Reboot the system as the BU system on Processor C.# setboot -p <BU_bootdisk_Primary_Address>

# setboot -a <BU_bootdisk_Alternate_Address> -s off -b on


• Boot the other processor as the L1 system from halted state.— At the CM> or GSP> prompt, press “<Control>” & “b” keys simultaneously.

— Interrupt boot & boot up as the Live system.

8. Perform one of the following steps according to your configuration..

Issue: GA-1, July 20103 - 2 2


9. You should now configure all disk mirrors again per your configuration. The same applies to the configuration of each alternate link path (redundant controller paths).

Issue: GA-1, July 20103 - 23


Backup HP System (BU) Recovery - FLEX:

File System Recovery - BU

A complete recovery of the Backup server's storage, usually a single disk, is a one step process. This single step only recovers the Backup OS file systems from tape to disk and is performed by booting the system from the Live server boot disk.

2. Ensure that the File System backup tapes are (write-protected) and mounted in the available tape drive of the system.

3. Issue the following command to start the file system recover:

# /etc/local/flexonlinerecover /dev/rmt/1mn (do NOT forget the “n” option)


INFO: The file system backup tape(s) should be loaded write-protected with:the white tab pushed to the left (DAT) OR the black tab pushed to the left (DLT) OR the red tab pushed to the right (LTO).Press the [ENTER] key when ready to continue.

• Press <CR> to start the recovery.


flexonlinerecover: 19:48:55 Rewinding /dev/rmt/1m.0+1 records in0+1 records outDate of backup in tape drive /dev/rmt/1mn is: 2003_11_05_14:26

Is this information correct? (Y|N) [D:N] y

NOTE:If the tape in the drive is NOT the FS backup, you will receive a warning message to change the tape out.

1. Ensure you are logged in as root on the Live server (L1) boot disk; depending on whether your system is SIMPLEX or DUPLEX.

• DUPLEX Systems: Halt the BU processor & Log in as root from the console on the Live (L1) processor:


• SIMPLEX Systems: Login on the processor & reboot the system. You must interrupt boot the disk and ensure you boot of the Live (L1) boot disk.

Issue: GA-1, July 20103 - 2 4



flexonlinerecover: 19:49:07 c3t3d0 is BOOTABLE.flexonlinerecover: 19:49:08 BACKUP DEVICE is /dev/rmt/1mn.pvcreate -f /dev/rdsk/c8t2d0Physical volume "/dev/rdsk/c8t2d0" has been successfully created.mkdir /dev/extramknod /dev/extra/group c 64 0x10000vgcreate -A n -s 64 -p 20 -e 1016 -l 255 /dev/extra /dev/dsk/c8t2d0Volume group "/dev/extra" has been successfully created.pvcreate -B -f /dev/rdsk/c3t3d0--------------------------------------------------------------flexonlinerecover: 20:46:29 Recovery completed.

• SIMPLEX Systems: Reboot the processor as the Live (L1) system via :# setboot -p <live_bootdisk_Primary_Address>



# cd /

# shutdown -r 0

• DUPLEX Systems: Log off the current processor as the BU system # exit

• Boot the other processor as the L1 system from halted state.— At the CM> or GSP> prompt, press “<Control>” & “b” keys simultaneously.

— Interrupt boot & boot up as the Live system.

4. Perform one of the following steps according to your configuration.

Issue: GA-1, July 20103 - 25


Flex Config Failover - (DUPLEX)The recovery process whereby a failed processor is manually switched over to its backup processor is called a failover. VAM only supports a planned failover which allows an orderly shutdown of the system before the redundant system takes over.

• This process involves shutting down the failed processor and/or booting the processor to its alternate name.

• This failover process only works on DUPLEX processor configuration. • Hence, the Live system becomes the Backup system and Backup system becomes the Live

system.• Failover process should only be used when you have a hardware failure on the Live system;

BU system is NOT required for daily operations.

! CAUTION:It is extremely important for the admin to have the appropriate bootable OS disk addresses of the Live (L1) and Backup (BU) system.

1. Shutdown & halt the current Live System via required process depending on the state of the processor. Refer to details earlier in this chapter.

! WARNING:The processor running Live system must be halted before running the next steps, else you will damage the system & will have to perform full system recovery.

2. Log in as root from the console into the BU machine:

• Physical Processor= A• System= Live (L1)• VG= /dev/vg00

HARDWARE FAILURES

BEFORE Failover

• Physical Processor= C• System = Backup (BU)• VG= /dev/BU

AFTER Failover

• Physical Processor= A• System= (BU)• VG= /dev/BU

System Halted or reboot to BU.

• Physical Processor= C• System= Live (L1)• VG= /dev/vg00

Issue: GA-1, July 20103 - 2 6



# setboot -p <live_bootdisk_Primary_Address>



# cd /

# shutdown -r 0

NOTE:At this point, the current physical processor will reboot & boot up as the Live system.

3. The system processor that was halted previously can be brought up as the Backup system once any hardware problems (If applicable) have been resolved. Run the following steps:

From Firmware Mode

• From the console, perform the following.— At the CM> or GSP> prompt, press “<Control>” & “b” keys simultaneously.

GSP> <Crtl> & b

GSP> rs

. . . . .Type Y to confirm your intention to restart the system: (Y/[N]) y

. . . . .

. . . . .Main Menu: Enter command or menu >Process is starting autoboot processTo discontinue, press any key within 10 seconds --> Ensure to interrupt the autoboot.

4. Interrupt the auto-boot by pressing any key on the system and setup boot path to boot as BU system.

Main Menu: Enter command or menu > bo priInteract with IPL (Y or N)?> y

ISL> primpath <Primary_BU_BootPath> --> Setup bootpath for BU disk.

ISL> altpath <Alternate_BU_BootPath> --> Setup bootpath for BU disk.

ISL> display --> Will display set values for booting

ISL> hpux boot /stand/vmunix --> Will boot to default level.

• Allow for normal system boot to Live (L1) system. (Application will auto start). Refer to VAM Application startup chapter for further details.

5. Normal system verification should be completed per customer requirements.



4 VAM Application Admin/Monitoring

Overview


• VAM Application Admin

— stop, start, check status, etc.

• Fix Application status problems

• Informix start/stop

• TaskToolkit Admin


• Stop/start Webserver



VAM Full Application ShutdownThe following process can be used to perform a complete 8950 VAM application shutdown. This shutdown will stop the following subsystems:

• Informix Database• TaskToolkit Application• All CORE VAM Application components1. Log in as int from either the console or a PC via telnet into the L1 machine:



# /sbin/init.d/Navis_Voice_AM stop


jguid daemon 4006 successfully stopped.stunnel daemon 4052 successfully stopped.stoptgui: Stopping Task ToolKit server processes. Please wait...stoptgui: Calling stopAsyncSOAP. Please wait.stoptgui: Calling stopTBLDR. Please wait.stoptgui: Calling stop_tgserv. Please wait.stoptgui: Calling stopOAMserver. Please wait.

Checking 8950 VAM status. Please wait...

. *** NVAM IS DOWN ***shutdn: RCRequest SOAP service undeployed.[Tue Jan 20 16:55:58 2009] [warn] PassEnv variable JPIVERSIONWINDOWS was undefined[Tue Jan 20 16:55:58 2009] [warn] PassEnv variable JPIVERSIONSOLARIS was undefined[Tue Jan 20 16:55:58 2009] [warn] PassEnv variable JPIVERSIONHPUX was undefined[Tue Jan 20 16:55:58 2009] [warn] PassEnv variable JPIVERSIONLINUX was undefined[Tue Jan 20 16:55:58 2009] [warn] PassEnv variable JPIVERSION was undefinedstop_tomcat: stopping tomcatstop_tomcat (DEBUG): Stopping Tomcat service.Waiting for Informix to go Off-line..#


# su - int

int> /topasrc/binstop_jguid stop

int> exit


jguid daemon 21068 successfully stopped.

int> exit




# su - toa

toa> /topasrc/binstop_jguid stop


stop_toa: Wed Jan 21 07:22:37 EST 2009 Stopping TOA processes.stop_toa: java process for TOA=SocketServer PID=4062 successfully stopped.stop_toa: java process for TOA=BatchProcessor PID=4101 successfully stopped.stop_toa: java process for TOA=OrderProcessor PID=4103 successfully stopped.stop_toa: java process for TOA=Responder PID=4105 successfully stopped.

toa> exit

5. Issue the following command to ensure all Application components are stopped:

# ps -ef | grep -i informix

# ps -ef | grep -iv root

NOTE:You should monitor the output & ensure that all application processes are shutdown accordingly. You may have to manually kill other processes that are not needed.



VAM Full Appplication StartupThe following process can be used to perform a complete 8950 VAM application startup. This startup will start the following subsystems:

• Informix Database• TaskToolkit Application• All CORE VAM Application components1. Log in as int from either the console or a PC via telnet into the L1 machine:



# /sbin/init.d/Navis_Voice_AM start


jguid daemon 4006 successfully stopped.stunnel daemon 4052 successfully stopped.stoptgui: Stopping Task ToolKit server processes. Please wait...stoptgui: Calling stopAsyncSOAP. Please wait.stoptgui: Calling stopTBLDR. Please wait.stoptgui: Calling stop_tgserv. Please wait.



VAM Core Appplication AdminThe following process can be used to perform admin activity on the 8950 VAM application.

VAM Application StatusThis option will check status of all VAM application components (except Informix Database).



• Check VAM application Status: [xxxxx-int] /tgui/bin/rstat• Menu option: [xxxxx-int] menu

— 2) 8950 VAM System Administration Menu

— 4) Check System Status



-------------------------------------------------------------------- PROC-NAME SRV-NAME PID STATUS #RESTART LIMIT -------------------------------------------------------------------- ACO_DIST ACO_DIST 3285 ON 0 5 ACO_GEN ACO_GEN_01 3286 ON 0 5

. . . . .

. . . . .

. . . . .CNFG CONFIG 3298 ON 0 5

DBUPD ECHOB 3299 ON 0 5 DBUPDDIST DBUPD 3300 ON 0 5 DBUPDPROC DBUPDPROC01 3301 ON 0 5

. . . . .

. . . . .

. . . . .

• PROC-NAME = Name of the process• SRV-NAME = Server name of the process• PID = Process id number of the SRV-NAME

• REQUIRED = Total number of server processes necessary for the application to run properly.• LIMIT = value of 5 representing the maximum number of times the SRV-NAME can be restarted.

STATUS = Status of the SR V-NAME.• ON = the number of servers up and running.• SUSP = number of server processes in suspend state• DOWN = number of server processes not running

The system status field definitions



SWCOM APRILPATCH5RC 3325 ON 0 5 SWCOM ASWITCH5E14RC 3326 ON 0 5 SWCOM ASWITCH5E15RC 3327 ON 0 5

. . . . .

. . . . .

. . . . .MICOM 5E16TESTCLLEB 3365 ON 0 5

MICOM ALBQNMMADC2EB 3366 ON 0 5 MICOM ALBQNMNEDC0EB 3367 ON 0 5 MICOM ALBQNMNESTUEB 3368 ON 0 5

. . . . .

. . . . .

. . . . .--------------------------------------------------------------------

PROCESS SUMMARY: ON=125 SUSP=0 DOWN=0 TOTAL=125

--------------------------------------------------------------------

*** NVAM IS UP ***

Status of Translation Interface Server:

UID PID PPID C STIME TTY TIME COMMAND int 4158 1 0 Jan 24 ? 0:00 jguid JGUIDStatus of RCRequest SOAP Service:

RCRequest SOAP Service is disabled.

Status of Task Toolkit Servers (Platform):

CURRENT RUN LEVEL IS: Administrative

DEMONS:Demon Name Pid Process Name Strt Persist Respawnsccd 3684 ccd -f $CCP_DIR -e / R Yes 0logdaemon 3685 logdaemon R Yes 0

Status of Task Toolkit Servers (Application):CURRENT RUN LEVEL IS: Running

DEMONS:Demon Name Pid Process Name Strt Persist Respawnslogdaemon 3947 logdaemon -a R Yes 0tmgr 4017 tmgr -A tmgr -I amgr R No 0rap 4018 rap -A rap R No 0SOReqHdlr1 4090 SOReqHdlr -A reqHdlr R No 0

. . . . .

. . . . .

. . . . .Status of Task Toolkit Servers (OA&M and Builder):

There could be up to 1 Task Builder server(s) running.

Server Name PID COMMAND



Orbix Daemon 3242 orbixd -s -o int OA&M Server 3494 OAMserver -s OAM_SERVER -D tgui01 Task Builder 4125 /tgui/bin/BUILDER BUILDER1 tgui01 NS 3267 java Tomcat 2999 java

Press RETURN to go back to MENU

VAM Application ShutdownThis option will check shutdown of all VAM application components (except Informix Database).





— 3) Shut Down 8950 VAM Application

Do you want to continue with 8950 VAM SHUTDOWN [y/n]? yPlease enter reason for SHUTDOWN. <Free format field>


stoptgui: Stopping Task ToolKit server processes. Please wait...stoptgui: Calling stopAsyncSOAP. Please wait.stoptgui: Calling stopTBLDR. Please wait.stoptgui: Calling stop_tgserv. Please wait.stoptgui: Calling stopOAMserver. Please wait.


*** NVAM IS DOWN ***shutdn: RCRequest SOAP service undeployed.[Wed Jan 28 08:54:12 2009] [warn] PassEnv variable JPIVERSIONWINDOWS was undefined[Wed Jan 28 08:54:12 2009] [warn] PassEnv variable JPIVERSIONSOLARIS was undefined[Wed Jan 28 08:54:12 2009] [warn] PassEnv variable JPIVERSIONHPUX was undefined[Wed Jan 28 08:54:12 2009] [warn] PassEnv variable JPIVERSIONLINUX was undefined[Wed Jan 28 08:54:12 2009] [warn] PassEnv variable JPIVERSION was undefinedstop_tomcat: stopping tomcatstop_tomcat (DEBUG): Stopping Tomcat service.




VAM Application StartupThis option will check shutdown of all VAM application components (except Informix Database).





— 2) Start Up 8950 VAM Application

Do you want to start 8950 VAM [y/n]? [n] y

• You will be prompted to start all the RC & EB link, answer “y” or let it timeout-default to “y” automatically.


Waiting for INFORMIX to come On-line.INFORMIX is On-line.strt_tomcat: starting tomcat

. . . . .

. . . . .8950 VAM system is coming up. Please wait...Checking 8950 VAM status. Please wait...

-------------------------------------------------------------------- PROC-NAME SRV-NAME PID STATUS #RESTART LIMIT -------------------------------------------------------------------- ACO_DIST ACO_DIST 22888 ON 0 5 ACO_GEN ACO_GEN_01 22889 ON 0 5

. . . . .

. . . . .

. . . . .DBUPD ECHOB 22902 ON 0 5

DBUPDDIST DBUPD 22903 ON 0 5 DBUPDPROC DBUPDPROC01 22904 ON 0 5

. . . . .

NOTE: For any failures, do NOT shutdown the application, you should continue the startup & fix the problem via “Verify ATP Servers” menu option.

Do You Want To Shut Down 8950 VAM? n



. . . . .

. . . . .HBCNTRL DMSHBCNTRL 22918 ON 0 5

QUERY QUERY 22919 ON 0 5 RC SRCHG 22920 ON 0 5 SERVDBUPD SERVDBUPD 22921 ON 0 5 SREF SREF 22922 ON 0 5 SWCOM 5E16TESTCLLRC 22923 ON 0 5

SWCOM APRILPATCH5RC 22928 ON 0 5 SWCOM ASWITCH5E14RC 22929 ON 0 5

DMSWCOM ASWITCHSN05RC 22931 ON 0 5. . . . .. . . . .. . . . .

--------------------------------------------------------------------

PROCESS SUMMARY: ON=125 SUSP=0 DOWN=0 TOTAL=125

--------------------------------------------------------------------

*** NVAM IS UP ***starttgui: Starting up Task Toolkit server processes. Please wait...starttgui: Calling strtOAMserver. Please wait.starttgui: Calling strt_tgserv. Please wait.starttgui: Calling strtTBLDR. Please wait.starttgui: Calling strtAsyncSOAP. Please wait.Daemon jguid successfully started.Daemon /rc/apache/sbin/stunnel successfully started.Sending output to nohup.out

Reset number of server restarts.

Do you want to connect all Recent Change links [y/n]? [y] yEstablishing RC links.nohup swcom_sm -h ALL -c >/dev/null &

Do you want to connect all Echo-Back links [y/n]? [y] yEstablishing Echo-Back links.nohup micom_sm -h ALL -c >/dev/null &Press RETURN to go back to MENU

VAM Application DebugThis option will re-start any VAM application processes that are DOWN.



• Menu option: [xxxxx-int] menu

Issue: GA-1, July 20104 - 1 0



— 9) System Commands Menu

— 2) Verify 8950 VAM Servers

2. Run the following to ensure application working properly:



— 4) Check System Status

NOTE:For further assistance, please conact the appropriate 8950 VAM technical support team.

Issue: GA-1, July 20104 - 11


Informix Software Admin! WARNING:

Please note that bounce of the Informix software will require a bounce of the VAM application.

Informix statusLog File : /rc/data/ol_atp.log





— You should see “oninit” processes running.

# tail /rc/data/ol_atp.log

— You should see checkpoint completion messages.

Informix shutdown1. Log in as int from either the console or a PC via telnet into the L1 machine:





Waiting for Informix to go Off-line.


— Ensure that all informix “oninit” processes are down.

Informix startup1. Log in as int from either the console or a PC via telnet into the L1 machine:





starting informix# ps -ef | grep -i informix

Issue: GA-1, July 20104 - 1 2


— You should see oninit processes running.


informix 4195 4193 0 14:21:22 ? 0:01 /rc/informix/bin/oninitinformix 4193 4192 0 14:21:22 ? 0:00 /rc/informix/bin/oninitinformix 4198 4193 0 14:21:24 ? 0:00 /rc/informix/bin/oninitinformix 4194 4193 0 14:21:22 ? 0:00 /rc/informix/bin/oninitinformix 4197 4193 0 14:21:23 ? 0:00 /rc/informix/bin/oninit root 4211 3942 1 14:29:52 pts/1 0:00 grep -i informixinformix 4199 4193 0 14:21:25 ? 0:00 /rc/informix/bin/oninitinformix 4192 1 0 14:21:19 ? 0:06 /rc/informix/bin/oninitinformix 4196 4193 0 14:21:23 ? 0:00 /rc/informix/bin/oninit

Issue: GA-1, July 20104 - 13


VAM Application Component Admin! WARNING:

Please note that bounce of the Informix software will require a bounce of the VAM application.

JGUID Process1. Log in as int from either the console or a PC via telnet into the L1 machine:


• Check JGUID status: int] /topasrc/bin/chk_jguid


Status of Translation Interface Server:

UID PID PPID C STIME TTY TIME COMMAND int 17467 1 0 Jan 21 ? 0:00 jguid JGUID

• Stop JGUID: int] /topasrc/bin/stop_jguid


jguid daemon 17467 successfully stopped.stunnel daemon 7140 successfully stopped.

• Start JGUID: int] /topasrc/bin/start_jguid


Daemon jguid successfully started.Daemon /rc/apache/sbin/stunnel successfully started.

Orbix Process1. Log in as int from either the console or a PC via telnet into the L1 machine:


• Check Orbix status: int] ps -ef | grep -i orbix


int 10812 1 0 16:22:43 ? 0:00 orbixd -s -o intint 12536 12421 1 17:05:52 pts/3 0:00 grep -i orbix

• Stop Orbix: int] /topasrc/bin/stop_orbix

Issue: GA-1, July 20104 - 1 4



• Start Orbix: int] /topasrc/bin/start_orbix


[12930:New Connection (peach.mh.lucent.com,IT_daemon,*,int,pid=12925,optimised) ][12931:New Connection (peach.mh.lucent.com,IT_daemon,*,int,pid=12925,optimised) ]

Tasktoolkit Status1. Log in as int from either the console or a PC via telnet into the L1 machine:


• Check Tasktoolkit Status: [xxxxx-int] /tgui/bin/chk_tgui_stat• Menu option: [xxxxx-int] menu


— 3) Task Toolkit Administration Menu

— 2) Check Status of Task Toolkit Servers


Status of Task Toolkit Servers (Platform):CURRENT RUN LEVEL IS: Administrative. . . . .. . . . .Status of Task Toolkit Servers (Application):CURRENT RUN LEVEL IS: RunningDEMONS:Demon Name Pid Process Name Strt Persist Respawns

logdaemon 6900 logdaemon -a R Yes 0tmgr 6972 tmgr -A tmgr -I amgr R No 0rap 6973 rap -A rap R No 0SOReqHdlr1 7040 SOReqHdlr -A reqHdlr R No 0SOReqHdlr2 7041 SOReqHdlr -A reqHdlr R No 0. . . . .. . . . .. . . . .Server Name PID COMMAND

Orbix Daemon 6069 orbixd -s -o int OA&M Server 6447 OAMserver -s OAM_SERVER -D tgui01 Task Builder 7075 /tgui/bin/BUILDER BUILDER1 tgui01 NS 6095 java Tomcat 5910 java


Issue: GA-1, July 20104 - 15


Toolkit shutdownLog File : /tgui/stoptgui.log




[xxxxx-int] /tgui/bin/stoptgui



Toolkit startupLog File : /tgui/starttgui.log




[xxxxx-int] /tgui/bin/starttgui


starttgui: Starting up Task Toolkit server processes. Please wait...starttgui: Calling strtOAMserver. Please wait.starttgui: Calling strt_tgserv. Please wait.starttgui: Calling strtTBLDR. Please wait.starttgui: Calling strtAsyncSOAP. Please wait.

Issue: GA-1, July 20104 - 1 6


Software UpgradesSoftware upgrades are issued periodically to enhance the system and/or to remedy any system problems. The updates are available as:

• Major application release — The software is available on DVD Media & Electronic Software bundle.

— Upgrade instructions are available on ALU-LED website.

• Periodic monthly patches— The software & install documents is available in Electronic Software bundle from the ALU

website only.

• Customer requested Expedited patches— The software is available on Electronic Software bundle only with customer specific

instructions.

Issue: GA-1, July 20104 - 17


Archive VAM DatabaseDue to 8950 VAM database space constraints, old recent change (RC) data must be deleted from the database periodically. However, due to various legal requirements, this data must also remain available for some time.

• The 8950 VAM database archive feature provides for this functionality. The archive process is comprised of two steps.

— The first step is to copy the old RC data to a file and remove the old RC data from the database.

— The second step is to copy the old RC data file onto a tape.

NOTE:You can re-synchronize the rejected RCs before proceeding to archive the database.

Save to HP System File System



2. Access the Cleanup DB Resources Menu as follows:

[xxxxx-int] menu


— 9) System Commands Menu— 4) Clean Up Database Resources— 8) Switch Database Load Menu

3. Answer the following prompts accordingly:

Running this tool will archive existing rejected RCs. Note that existing rejected RCs can be resynchronized using the Resynchronize Rejected RCs feature with menu 2-8-10. Do you wish to abort the archive tool now? (Y/N)[D: N] n

• Type n and press <Enter>.

Do you want to select all orders? [Entering Y will archive all orders in all states. Entering N will archive only orders in CPD and CAN states.] (Y/N) [D: N] y

• Type y and press <Enter>.

Available space on /rc/data file system.

Filesystem kbytes used avail %used Mounted on/dev/vg01/rc 2051553 1261139 585258 68% /rc

Do you want to continue with database cleanup/archive? (Y/N) [D: Y] y

Issue: GA-1, July 20104 - 1 8



Enter number of days of RC data to archive. Must be 14 days or older: <# of days>

• Input the <# of days> to archive and press <Enter>.

Do you want to enable message logging to file (/rc/data/SAVEDB_021209/RCdbcln.<mmddyy><seq>.log)? (Y/N) [D: N] y


Database cleanup/archive may take up to several hours to complete.Check the latest log file under /rc/data/SAVEDB_021209 to verify that the database archive/cleanup is completed. The log file name format is RCdbcln.<mmddyy><seq>.log. Archived RC data will be saved in directory SAVEDB_021209 under /rc/data. Once database cleanup/archive is completed use option "Write Archived RC Data to a Tape" of the "System Command Menu" to write archived data to a tape.Press RETURN to go back to MENU

• press <Return> to go back to Menu.

• Keep selecting option 1) Exit to completely exit back to UNIX prompt.

Monitor DB Archive processing

4. Run the following commands to monitor DB Archive process:

[xxxxx-int] ps -ef | grep -i RCdbcln

• If you see /topasrc/bin/RCdbcln, the process is still running:int 3 2 ttyq7 0:00 grep RCdbcln int 4 7 ttyq7 0:07 /topasrc/bin/RCdbcln -dXX -l -b -DSAVEDB_MMDDYY

NOTE:The above step will run in the background for several hours. Only after the RCdbcln process has completed should the data be archived to the DAT tape.

• Once the RCdbcln process is no longer running, the data has been removed from the database and saved to the SAVEDB_<date> directory. It should now be written to tape.

• You must verify whether the .dat files are present in the /topasrc/bin/RCdbcln/SAVEDB_MMDDYY directory.

Write Data Tape Device

5. Access the Write Archive Data to Tape Menu as follows:

[xxxxx-int] menu


— 9) System Commands Menu— 5) Write Archived RC Data to a Tape

Issue: GA-1, July 20104 - 19



Please enter archive data directory name? SAVEDB_<mmddyy>

• Input directory name SAVEDB_<mmddyy> and press <Enter>.

Do you want to write archived RC data to a tape? [D: Y] y

• Input Y and press <Enter>.

Make sure you first label the tape properly with the following information:Database Archive from ATP Central peachArchive Data Directory SAVEDB_021209 & Archive date 02/12/2009Press <Return> to continue...

• press <Enter>.

The following drives type(s) 9-TRACK DAT DLT ON peach are available:1) d002) d013) quitSelect the number corresponding to the Tape Drive you wish to use: <Choice>

• Input <Tape #> and press <Enter>.

Writing archive to tape drive "/dev/rmt/c1t8d0BEST" please wait...(Using tape drive with immediate report mode enabled (reel #1).)99 blocksArchived RC data successfully saved to tape.Removing archive data files from the file system. Please wait...Archive data files successfully removed.




Issue: GA-1, July 20104 - 2 0


VAM System DB AuditA system DB audit performs periodic system maintenance and reporting of any database specific issues that may be encountered. It is highly recommend to perform a DB audit of the system atleast once per calendar year to detect & alleviate any DB issues. Benefits of DBaudit:

• Allows time for correcting any problem(s) that the database audit may encounter.• Errors encountered can be debug further with ALU product support team.

! CAUTION:Normal DBaudit process should be performed with the VAM application shutdown; thus, it is highly recommended to run it during off-peak hours.




# /Install/disableServs

3. Stop VAM application (int login):

# su - int


— 3) Shut Down 8950 VAM Application

Do you want to continue with 8950 VAM SHUTDOWN [y/n]? yPlease enter reason for SHUTDOWN. <Free format field>



[xxx-int] exit

4. Stop cron & bounce informix:

# /sbin/init.d/cron stop



# tail /rc/data/ol_atp.log

NOTE:A “checkpoint completed” message is an indication that the engine has started successfully.

5. Run the following to shutdown all login activity except, print spoolers, root, & informix login. You may wish to leave other logins that may apply to your environment.

Issue: GA-1, July 20104 - 21


# ps -ef | grep -i root

NOTE:Do NOT kill “/usr/sbin/lpsched” and “oninit” ; (local environment rules apply)

# kill -TERM <pid> where <pid> is the process id.

6. Run the following to start DBaudit:

# su - informix

$ onstat -g ses

• You should only see sessions owned by INFORMIX (kill all other processes if applicable).

$ nohup /Install/audit_db 2>&1 &

NOTE:DBaudit duration may take upto to 6 hours depending on your system config. Your output will go to file nohup.out in local directory.

7. Enter the following commands to view the listed output:

$ grep -Ei “WARNING|ERROR” /tmp/*.audit_db.out

TBLspace data check for osps:int.remote_errorsTBLspace data check for osps:informix.errorsValidating indexes for osps:int.remote_errors...Validating indexes for osps:informix.syserrors...TBLspace data check for starterdb:informix.syserrorsValidating indexes for starterdb:informix.syserrors...TBLspace data check for sysmaster:informix.syserrorsValidating indexes for sysmaster:informix.syserrors...TBLspace data check for sysutils:informix.syserrorsValidating indexes for sysutils:informix.syserrors...TBLspace data check for tbldrdb:informix.syserrorsValidating indexes for tbldrdb:informix.syserrors...TBLspace data check for tgui01:informix.syserrorsValidating indexes for tgui01:informix.syserrors...WARNING:No syssyntable records found.WARNING:No syssyntable records found.WARNING:No syssyntable records found.WARNING:No syssyntable records found.WARNING:No syssyntable records found.

! CAUTION:You see multiple occurrences of the last line in the above output. The ONLY rported output should be the lines shown above. If anything else is reported, contact the ALU product support team.

8. Preserve the report file by entering:

$ exit

# mv /tmp/*audit_db.out ~int

# chown int:rcadm ~int/*audit_db.out

Issue: GA-1, July 20104 - 2 2


9. Re-enable system access & restart VAM application

# /Install/enableServs

# /sbin/init.d/cron start

# su - int


— 2) Start Up 8950 VAM Application

Do you want to start 8950 VAM [y/n]? [n] y

• After application startup is complete, press <Return> to go back to Menu.

• Keep selecting option 1) Exit to completely exit back to UNIX prompt & logoff.

Issue: GA-1, July 20104 - 23


Issue: GA-1, July 20104 - 2 4


VAM Application Menu ItemsThe following will give high-level overview of all menu options available in the VAM application and it’s purpose & description.

Access VAM Main Menu1. Log in as int from either the console or a PC via telnet into the L1 machine:


• Menu option: [xxxxx-int] menu

NVAM System Administration Menu1) Exit2) Start Up NVAM Application3) Shut Down NVAM Application 4) Check System Status5) Link Administration Menu6) User Administration Menu7) Switch Administration Menu8) Switch Database Load Menu9) System Commands Menu10) NVAM Configuration Menu11) Workgroup/CLEC Administration Menu

Options (1 thru 4)

1 = Exit menu

2= Start VAM Application

3 = Stop VAM Application

4 = Get Application status

Option 5 = Allows admin for RC & EB Links

Option 6 = Allows admin for User Logins

Option 7 = Allows Admin for Switch definitions

Option 8 = Allows Admin for Switch dump & Load

Option 9 = Allows Admin for DB cleanup, archive, error files admin, Feature admin, switch db admin, & disk space modeling.

Option 10 = Allows Admin for EB filter, GUI/Monitor locks, Level2 validations admin, Domain & inventory table admin, proactive monitoring, password aging,

Option 11 = Allows Admin for Work Group Admin

Issue: GA-1, July 20104 - 25


Link Administration MenuThis menu item allows complete administration of all switch links associated with the VAM application.




— 5) Link Administration Menu

Link Administration Menu1) Return to NVAM System Admin Menu2) Recent Change Links Menu3) Echo-Back Links Menu4) System Links Status Menu5) Link Sharing Configuration Menu6) DMS Surveillance System Bypass Menu7) Recent Change/Echo-Back Link Status

Options (1 thru 4)

1 = Exit menu

2= Admin RC Links

3 = Admin EB Links

4 = All system switch links

Option 5 = Allows admin for EB links in shared mode.

Option 6 = Allows Admin for DMS Switch survelliance bypass

Option 7 = Report RC & EB Links status

Issue: GA-1, July 20104 - 2 6


User Administration MenuThe menu item is used to perform user administration on VAM system. This menu items is NOT the recommended way to perform user admin functions. Refer to the GUI interface for all VAM user admin functions.





**USER ADMINISTRATION***LOGIN:USER NAME:TELNO:LOCATION:ARC:PRINTER:WORK GROUP:DEFAULT CLLI:DEFAULT APPL:COMMENTS:UNIX LP OPTIONS:REPORT PAGE LENGTH:EXPERT USER:

PRIVILEGE: Add Delete Query Change Switches WorkGroups ExitAdd User Login ID

Menu item = Allows admin for user logins.

Issue: GA-1, July 20104 - 27


Switch Administration Menu1. Log in as int from either the console or a PC via telnet into the L1 machine:



— 7) Switch Administration Menu

Switch Administration Menu

1) Return to 8950 VAM System Administration Menu2) Display/Update Switch Information3) Display/Update Switch Associations4) Display/Update Switch Cut-Thrus5) Display S.R. and S.U. Levels of 5ESS SwitchSelection:

Option 2 = Allows admin for Switch Information (add/del/update switch into VAM)

Option 3 = Allows Admin for Switch Association (Associate with task component)

Option 4 = Configure direct switch cut-thru access information

Option 5 = Display Switch Software ReleaseInformation

Issue: GA-1, July 20104 - 2 8


Switch Database Load Menu1. Log in as int from either the console or a PC via telnet into the L1 machine:



— 8) Switch Database Load Menu

Switch Database Load Menu

1) Return to 8950 VAM System Administration Menu2) Dump List/Dump Script Menu3) Read Switch Data4) Load Data to Database5) Switch Database Load Monitoring6) Use TNM/SCCS Data to Synchronize Database7) Remove Successful OFR Load Data Files8) Defaults Administration Menu9) Load Feature Definition Mapping10) Resynchronize Rejected RCs11) Inventory Initialization

Option 7 = Allows admin for Switch Defaults

Option 8 = Allows Admin for purging switch data/logs

Option 9 = Allow Admin for feature definitions

Option 10 = Allow Admin for reject RCs for switches

Option 11 = Allow Admin for Inventory Initialization

Options (1 thru 4)

1 = Exit menu

2= DumpList/Dump Script

3 = Read Switch data

4 = Load Switch to database

5 = DB Load Monitoring

6 = Run TNM Sync

Issue: GA-1, July 20104 - 29


System Commands Menu1. Log in as int from either the console or a PC via telnet into the L1 machine:




8950 VAM Parameters Configuration Menu

1) Return to 8950 VAM System Administration Menu2) Display/Change Echoback Filter Table3) Display/Change GUI Login Lock Out Level4) Display/Change Monitors ON Lock Out Level5) Level 2 Validations Configuration Menu6) Update 8950 VAM Domain Information Table7) Update Inventory Tables Primary Host Name8) Configure Number of Simultaneous User Sessions9) Configure Proactive Monitoring System10) Configure DARICS Interface11) Configure Password Aging12) Configure Number of Login AttemptsSelection:

Option 6 = Allows admin for Domain Infor table

Option 7 = Allows admin for inventory table

Option 8 = Allow admin for simultaneous user sessions

Option 9 = Allows admin for proactive monitoring system

Option 10 = Allow admin for DARICS interface

Option 11 = Allow Admin for password aging

Option 12 = Allow Admin for # of login attempts

Options (1 thru 4)

1 = Exit menu

2= EB Filter table admin

3 = Admin GUI access

4 = Admin system monitor levels

5 = Admin Level 2 Validations

Issue: GA-1, July 20104 - 3 0


VAM Parameter Configuration Menu1. Log in as int from either the console or a PC via telnet into the L1 machine:



— 10) 8950 VAM Configuration Menu

System Commands Menu

1) Return to 8950 VAM System Admin Menu2) Verify 8950 VAM Servers3) Reset Number of Server Restart4) Clean Up Database Resources5) Write Archived RC Data to a Tape6) Read Archived RC Data from a Tape7) Report Old Recent Change Data8) Save Error Files9) Remove Old Error Files10) Broadcast a Message to All Users11) Set Purge Interval for ifc_status Table12) 8950 VAM Feature Control Menu13) Copy Switch Machine Address Table to Remote Central(s)14) Capture Input Data for the Disk Space Model15) DB Audit MenuSelection:

Option 7 = Allows admin for Old Recent Change data

Option 8 = Allows for for saving system error files

Option 9 = Allow for removing saved system error files

Option 10 = Allows you to send broadcast message to all users

Option 11 = Allow for purge interval for ifc_status table

Option 12 = Allow Admin for Feature Configuration

Option 13 = Allow Admin for switch address table to other centrals

Option 14 = Allow Admin for Disk space model

Option 15 = Allow Admin for DB Audit menu

Options (1 thru 4)

1 = Exit menu

2= Fix VAM process issues

3 = Reset Process counts

4 = Admin DB resources

5 = Write DB data to tape

6 = Read DB data to FS

Issue: GA-1, July 20104 - 31


Workgroup Admin Menu1. Log in as int from either the console or a PC via telnet into the L1 machine:



— 11) Workgroup/CLEC Administration Menu

Workgroup/CLEC Administration Menu1) Return to 8950 VAM System Admin Menu2) Workgroup/CLEC Administration3) Workgroup/CLEC Recent Change Permissions4) Workgroup/CLEC Switch Permissions5) Ext Sys Default Workgrup/CLEC Admin

Selection:

Options (1 thru 4)

1 = Exit menu

2= Admin Workgroups

3 = Admin Workgroup RC permissions

4 = Admin Workgroup Switch Permissions

5 = Admin Workgroup to ext systems

Issue: GA-1, July 20104 - 3 2




5 VAM User Administration

Overview


• Application user Admin (5E & DMS)

— Add, delete, update, etc.

• Debug User login issues

• User login permissions & monitoring



User Administration This chapter will discuss in detail administration of application users for the VAM application. This chapter can be used as a reference to perform the following:

• User Administration menu option• Workgroup admin menu options• Firewall & Permissions options

Access User Administration Menu

Access Workgroup Admin Menu

Access via GUI Interface1. Access the VAM launch page via a browser interface & login as int.

Launch Page address: http://<FQDN_HP_Server>/HTML/index.html


— Select System Administration icon

— Select User Administration option





— Select Work Group Administration option



Access Firewall Administration GUI




— Select Firewall Administration icon



Workgroup Admin OverviewAdding a VAM application user in the system involves adding a user into the system and also associating that user into a specific work group.

• Associating a user into a specific work group allows for permissions set for that work group (switch access, 5E-View/DMS-Table access, & Printer access).

• Where applicable - Task Permissions must also be performed for the user/workgroup (discussed in another chapter).

• It is highly recommended that you pre-define all your workgroup into the system per your requirements before performing user accounts administration.

NOTE:The “STAFF” workgroup is pre-defined into that system & has full permissions for switches, Views/Tables, & all printers.

Add a workgroupWorkgroups allows an admin to group specific user accounts into a set of permission structures (switches, View/Table, Printer).

! CAUTION:With each workgroup created; permissions admin must also be performed. Thus, more work groups means more permissions admin work. It is highly recommended to setup a proper plan & process for user accounts & their permissions structure to ensure minimal admin work required.

• Work group name can be upto 5 alpha-numeric characters long. (NO special characters are allowed).

1. Access the Work Group Menu via the GUI Interface as follows:

1.1 Access the VAM launch page via a browser interface & login as int.







2. You will need to input the following information to add the workgroup into the system.

• *Work Group Name: = workgroup you wish to add into system.• Customer Id: = unique numeric # for workgroup (can be left BLANK).• Telephone: = Telephone # for workgroup admin.• Contact Name: = Admin Name info for the workgroup • Location: = Location info for workgroup (can be left BLANK).• Description: = Brief Description for the workgroup.• Comments: = Brief Comments for workgroup.

— Click Add button once all the data is input. press Clear button to start over.

Change workgroup Info• The “Change” option to the work group allows you to change the “Description, Contact Name, Location, and Comments fields only.


2. Change the information for the “Description, Contact Name, Location, and Comments fields as required.

— Click Query button to find & select work group to change. press Clear button to start over.

— Click Update button once all the data is input. press Clear button to start over.








Delete workgroup • The “Delete” option to the work group allows you to Delete the workgroup from the system.

! CAUTION:You can only delete a workgroup if there are NO users associated with the workgroup that you wish to delete. Any issues encountered with this option should be directed to the product support team.


2. Select the user to delete as follows:

— Click Query button to find & select work group to Delete. press Clear button to start over.

— Click Delete button to remove the work group & answer the following prompt:

“Are you sure you want to delete this Work Group?”

— Click Ok button to remove the work group.








User Login Admin OverviewAdding a VAM application user in the system involves adding a user into the system and also associating that user into a specific work group.

• Refer to previous pages for the workgroup admin options.

User Admin can be performed via the GUI Interface (Recommended Method) and/or the Menu interface.

Add a User accountUser accounts admin can be performed via the GUI Interface (Recommended Method) and/or the Menu interface.

1. Access the User Administration Menu via the GUI Interface as follows:

2. The user administration GUI screen will be displayed.

3. You will need to input the following information to add the user into the system.

• *Login: = User Login id you wish to add into system.• User Name: = User’s Full Name.• Work Group: = From Pull-Down Menu, select work group for user.• Primary CLLI: = From Pull-Down Menu, select default CLLI for user• TelNo: = User’s Telephone Number.• Location: = Address location of User. • Arc: = Authorization Reporting Code (can be left BLANK).• Primary Printer: = From Pull-Down Menu, select printer for user reports functions.• Restricted: = From Pull-Down Menu, select Y or N to restrict user UNIX access.• Application Access: = From Pull-Down Menu, select appropriate option.

— ATP(Translation Interface), TTK (Task Toolkit), or ALL (Both Apps).








• Passwd: = Input user password information.• ReEnter Passwd: = Re-Input user password information.• Comments: = Any user information comments (if applicable).• Unix LP Options: = Unix lp option (optional).• REPORT PAGE LENGTH: = Input report page length (can be left BLANK).• EXPERT USER: = From Pull-Down Menu, to provide features options for advanced users.

— NONE (No expert option to define),

— COVER SHEET (allows user to skip cover sheet creation for orders), or

— IMMEDIATE SEND PLUS COVER SHEET (Allows user to skip cover sheet & ready order option).

4. To add the user account, (at the bottom of the GUI screen)

— Click Add button once all the data is input. press Clear button to start over.



Update a User Account The following process should be used to update a user account from the system. Refer to the “Add a user account” section to find the options that can be updated.


2. You must first query for the use id that you wish to make the modifications as described below:

— Click Query button to find & select user to change. press Clear button to start over.

3. Change the information for the fields to make the modifications as described below:

— Select appropriate fields to update and input the data.

— Click Update button once all the data is input.






Issue: GA-1, July 20105 - 1 0


Delete a User AccountThe following process should be used to delete a user account from the system.


2. You must first query for the use id that you wish to delete as described below:


3. You can now, delete the user as follows:

— Click Delete button to remove the User id. A pop-up window will be displayed:

“Are you sure you want to delete this user?”

— Press OK button to the prompt to re-confirm the user delete.






Issue: GA-1, July 20105 - 11


Change User Login PasswordThe following process should be used to update a user account’s password in the system. Two options are available to change a password:

• Option 1: The User can change the password themselves. (Must know current password)• Option 2: System Admin can change the password for the user.

Password Change Directly by User1. Access the GUI Change Password Menu via the GUI Interface as follows:

1.2 Change the Password as required.— Username: <User Login Name>

— New Password: <Type new use password>

— Re-enter New Password: <Re-type new use password>

• Press Accept button to change the password.



login: <user> Password: <login_password>

— Select User Options button on Left pane GUI screen

— Select Change Password option

Issue: GA-1, July 20105 - 1 2


Password Change by System Admin (Menu)1. Access the User Admin Menu Interface to change a user’s password in the system as follows:

1.1 Log in as int from either the console or a PC via telnet into the L1 machine:


[xxxxx-int] menu


— 6) User Administration Menu— Select <Change> option or simply press “c” key (query option can be used to look for a workgroup.)

— Type in the LOGIN to change and press <Esc> key.

— press <Enter> key 8 times and type Y at prompt to change user password.

— Type <New Password> & <Re-enter New Password> and press <ESC> key.

Password Change by System Admin (GUI)2. Access the Work Group Menu via the GUI Interface as follows:

3. You must first query for the use id that you wish to delete as described below:


4. You can now, update the user password as follows:

— Input the new password in the fields: “Passwd” & “ReEnter Passwd”

— Click Update button to change the password.






Issue: GA-1, July 20105 - 13


Firewall AdministrationFirewall administration is used to configure permissions for user’s of the Translation Interface Application (other name used --> TI app, JAVA GUI app, ATP App, etc) to specific set of switch access, 5ESS views, DMS Tables, & Application features.

! CAUTION:Applies only to NORTH AMERICAN MARKET CUSTOMERS!

• Admin is done per workgroup basis & NOT login basis. • By default, work groups have FULL-access to all options.

The GUI Firewall feature allows you to administer access to different switches, classes, tables, and features.

— An admin can limit access to “Read-Only” or “No Access” for a specific workgroup.

— By default, a workgroup has full access.

Access Firewall Administration GUI1. Access the Firewall Admin Menu via the GUI Interface as follows:





Issue: GA-1, July 20105 - 1 4


Firewall - 5ESS Views1. Access the Firewall Admin Menu via the GUI Interface as follows:

2. From the Work Group pull-down menu in the center of the page, select the workgroup for which you want to perform Firewall operations.

3. At the bottom of the page are the following four buttons as follows:

— Click on “Classes” button to perform firewalling on 5ESS Classes/Views.





Classes Tables CLLI Features

Firewall Administration

Work Group

Issue: GA-1, July 20105 - 15


4. A web page with two column view will be displayed.

• The available 5ESS Classes views will be displayed on the left column.• The list of permission configured classes will be displayed on the Right column.

4.1 In the Upper-Left Corner of the GUI screen, you must select either the “READ ONLY” or “NO ACCESS” option for permissions.

— To set permissions on all the classes: click on the <ALL> button (all items in left-column will be high-lighted) and then press the <ACCEPT> button.

— To set permissions on specific classes, in the left column windows, press the <Ctrl> key & select each of the specific class views (becomes high-lighted); Once all items are selected, then press the <ACCEPT> button.

— To remover permissions on all the classes: click on the <CLEAR> button (all items in right-column will be high-lighted) and then press the <ACCEPT> button.

— To remove permissions on specific classes, in the right column windows, press the <Ctrl> key & select each of the specific class views (becomes high-lighted); Once all items are selected, then press the <ACCEPT> button.

READ ONLY NO ACCESSFIRE WALL: CLASSESWORK GROUP ID: ATAB

"The available CLASSES are shown in the left list box, and the restricted (Read-Only or No Access) CLASSES are shown in the right list box."

1.11- BRCS Feature Assignment (5112,5113)1.11V- BRCS Feature Verify (5112,5113)1.12- BRCS Feature Activation (5123,5124)1.15- Verify Multiple DNS1.20- AUTO Call back (56162, 56163)

AVAILABLE CLASSES READ ONLY

ALL CLEAR ACCEPT

Issue: GA-1, July 20105 - 1 6


Firewall - DMS TABLES1. Access the Firewall Admin Menu via the GUI Interface as follows:



— Click on “Tables” button to perform firewalling on DMS Tables.







Work Group

Issue: GA-1, July 20105 - 17



• The available DMS Tables views will be displayed on the left column.• The list of permission configured Tables will be displayed on the Right column.


— To set permissions on all the Tables: click on the <ALL> button (all items in left-column will be high-lighted) and then press the <ACCEPT> button.

— To set permissions on specific Tables, in the left column windows, press the <Ctrl> key & select each of the specific table (becomes high-lighted); Once all items are selected, then press the <ACCEPT> button.

— To remover permissions on all the Tables: click on the <CLEAR> button (all items in right-column will be high-lighted) and then press the <ACCEPT> button.

— To remove permissions on specific Tables, in the right column windows, press the <Ctrl> key & select each of the specific Table (becomes high-lighted); Once all items are selected, then press the <ACCEPT> button.

"The available TABLES are shown in the left list box, and the restricted (Read-Only or No Access) TABLES are shown in the right list box."

READ ONLY NO ACCESSFIRE WALL: TABLESWORK GROUP ID: ATAB

AABSOSTACDADMINACDENLOGACDGRPACDLOGIN

AVAILABLE TABLES READ ONLY

ALL CLEAR ACCEPT

Issue: GA-1, July 20105 - 1 8


Firewall - Switch CLLI Access1. Access the Firewall Admin Menu via the GUI Interface as follows:



— Click on “CLLI” button to perform firewalling on Switch CLLIs.







Work Group

Issue: GA-1, July 20105 - 19



• The available Switch CLLI’s will be displayed on the left column.• The list of permission configured Switch CLLI’s will be displayed on the Right column.


— To set permissions on all the Switch CLLIs: click on the <ALL> button (all items in left-column will be high-lighted) and then press the <ACCEPT> button.

— To set permissions on specific Switch CLLIs, in the left column windows, press the <Ctrl> key & select each of the Switch CLLI (becomes high-lighted); Once all items are selected, then press the <ACCEPT> button.

— To remover permissions on all the Switch CLLIs: click on the <CLEAR> button (all items in right-column will be high-lighted) and then press the <ACCEPT> button.

— To remove permissions on specific Switch CLLIs, in the right column windows, press the <Ctrl> key & select each of the specific Switch CLLI (becomes high-lighted); Once all items are selected, then press the <ACCEPT> button.

"The available CLLIs are shown in the left list box, and the restricted (Read-Only or No Access) CLLIs are shown in the right list box."

READ ONLY NO ACCESS

FIRE WALL: CLLIsWORK GROUP ID: ATAB

5E16TESTCLLTESTSWCH001TESTSWCH002TESTSWCH003TESTSWCH004

AVAILABLE CLLIs READ ONLY

ALL CLEAR ACCEPT

Issue: GA-1, July 20105 - 2 0


Firewall - Features Access1. Access the Firewall Admin Menu via the GUI Interface as follows:



— Click on “Features” button to perform firewalling on Switch CLLIs.







Work Group

Issue: GA-1, July 20105 - 21



• The available Switch CLLI’s will be displayed on the left column.• The list of permission configured Switch CLLI’s will be displayed on the Right column.


— To set permissions on all the Switch CLLIs: click on the <ALL> button (all items in left-column will be high-lighted) and then press the <ACCEPT> button.

— To set permissions on specific Switch CLLIs, in the left column windows, press the <Ctrl> key & select each of the Switch CLLI (becomes high-lighted); Once all items are selected, then press the <ACCEPT> button.

— To remover permissions on all the Switch CLLIs: click on the <CLEAR> button (all items in right-column will be high-lighted) and then press the <ACCEPT> button.

— To remove permissions on specific Switch CLLIs, in the right column windows, press the <Ctrl> key & select each of the specific Switch CLLI (becomes high-lighted); Once all items are selected, then press the <ACCEPT> button.

"The available CLLIs are shown in the left list box, and the restricted (Read-Only or No Access) CLLIs are shown in the right list box."

READ ONLY NO ACCESS

FIRE WALL: CLLIsWORK GROUP ID: ATAB

5E16TESTCLLTESTSWCH001TESTSWCH002TESTSWCH003TESTSWCH004

AVAILABLE CLLIs READ ONLY

ALL CLEAR ACCEPT

Issue: GA-1, July 20105 - 2 2




6 VAM Switch Admin

Overview

The purpose of this chapter is to provide information about 8950 VAM Switch administration. The following topics will be covered:

• Switch Admin (Shadow & Non-Shadow)

— Add, delete, update, etc.

• EMS Switch Administration

• EMM Administration



Switch Administration OverviewThis chapter will discuss in detail administration of Switches for the VAM application. There are three types of switch configuration that are supported:

Option 1: Shadowed Switches (5ESS & DMS)

The shadowed switches provides provisioning functionality for 5ESS & DMS switches and allows the VAM system to replicate the database of the switch into the VAM system.

! CAUTION:Applies only to NORTH AMERICAN MARKET CUSTOMERS!

• Shadowed switch will allow access to the Translation Interface GUI application from the 8950 VAM launch page.

Option 2: NON-Shadowed Switches

The NON-shadowed switches provides provisioning functionality for various switch types but it does NOT replicate the database of the switch into the VAM system.

• Shadowed switch will allow access to the TaskTool Kit & Task Builder GUI application from the 8950 VAM launch page.

• Softswitch Gateway and IMS provisioning are considered part of the Task Toolkit



Shadow Switch Admin - OverviewThe following section will detail the steps required to add, delete, and update a Shadowed switch into the 8950 VAM application.

Adding a VAM application user in the system involves adding a user into the system and also associating that user into a specific work group.

• It is highly recommended that you pre-define all your workgroup into the system per your requirements before performing user accounts administration.

• It is suggested that you first perform the RC/EB growth procedures, since information acquired during those procedures will need to be entered into the following switch information screens.

— The growth procedures are found in the Alcatel-Lucent support web at the following folder: 8950 VAM, Common Release Folder, Common Manuals & Guides, folder: 5ESS Switch Procedures folder, or the DMS Switch Procedures folder.

Prerequisite Information:

The customer must have the following information available before adding any of the shadowed switches into the system.

• SWITCH CLLI Name: The 11 Character Switch CLLI name.• Switch Generic: Actual generic of the switch being added into system.• Switch Name defined in the switch Database:

— 5ESS: ECD Form: EAIOPT, Key: EAIOP0, & 5th Field value of SYSNAME:

— DMS: Contact DMS Switch Engineer for details.

• OFFICE ID: The office ID information will help in verification of LINK connections.— 5ESS: RCV View 8.1 & Field Value under KEY.

— DMS: Table OFCENG & Field Value under KEY.

• Link Interface for RC Link & EB Link— The protocol interface being used to connect the link must be identified by network admin.

— Available Options: DK-X25, DK-ASY, IP-ASM, IP-ASY-DY, IP-ASY-AI, IP-EIU, IP-VSOS, IP-X25-AI, IP-X25-DY, and IP-SDM.



Shadow Switch Administration GUIAccess via GUI Interface

1. Access the VAM launch page via a browser interface & login as int.




— Select Switch Administration option (Ensure Shadowed Switch option is selected)

NOTE:It may take atleast 2-3 minutes for the following Switch Admin GUI screen to appear.



Adding a New Switch - Shadow

2. You will need to input the following information to add the switch into the system.

• The following Fields as same for all switch types to be added.— Switch Generic: From the pull-down menu, select the Generic of switch to add.

• DMS Switch Generics: NCS15, SN06, SN062, SN07, SN08, SN09, SN10.

• 5ESS Switch Generics: 5E14, 5E15, 5E16, & 5E16FR5.

— Switch Clli: Input the 11 character switch Clli identifier.

— Switch Name: Input the switch name defined in the actual switch database (Refer to switch engineering admin for further details).

— RC Serv: Auto populated based upon Switch clli Name (SWCOM process Name).

— EB Serv: Auto populated based upon Switch clli Name (MICOM process Name).

• The following Fields are for DMS switch type only.— DMS Login: Login Name to use to connect the switch links (RC & EB links).

— DMS Password: (DMS Switch Only) Password for the Login Id to connect the switch links (RC & EB links).

• The following Fields are for 5ESS switch type only.— ASM Login: Login Name used to connect to the 5ESS ASM system.

— ASM Machine Name (D&L): The hostname of the ASM system. (DNS should be aware of the hostname; else /etc/hosts file should be updated accordingly).

Access Shadow Switch Admin via GUI Interface1. Access the VAM launch page via a browser interface & login as int.





NOTE:It may take atleast 2-3 minutes (JAVA Applet loading) for the Switch Admin GUI screen to appear.

— Select Switch Add tab on the GUI screen.



• The following Fields as same for all switch types to be added.— Inhibit Retry Interval: Input a value in minutes that the 8950 VAM system should use to

re-send data to the RC Link if a switch is inhibited. (Min value = 10 ; MaX value = 999).

— Office ID: The office id information used in verification of RC Link connection.

• 5ESS Switch: RCV View 8.1 & Field Value under KEY.

• DMS Switch: Table OFCENG & Field Value under KEY.

• ALL Other Switch Types or to skip RC Link verification: Leave default value ofCVUNOVERIFY.

— MAX RC VCS: Input the total # of virtual circuits that you wish to connect for RC Link.

• 5ESS Switch: Can have upto four 5E virtual RC link circuits. Input value of 1 thru 4.

• ALL Other Switch Types: Leave default value of 1.

• For further details on the following two field, consult your network & switch engineers.— RC Link Intf: From the pull-down menu, select the interface for RC Link connect.

• DK-X25: Datakit connectivity 5ESS Switch Only.

• DK-ASY: Datakit connection DMS switch only.

• IP-ASM: IP connection for 5ESS only (ASM feature required).

• IP-ASY-DY: IP connection via Dynastar/Cisco router for DMS switch only.

• IP-ASY-AI: IP connection via AI system for DMS switch only.

• IP-EIU: IP connection for DMS switch only.

• IP-VSOS: IP connection for DMS switch only.

• IP-X25-AI: IP connection via AI system for 5ESS switch only.

• IP-X25-DY: IP connection via Dynastar/Cisco router for 5ESS switch only.

• IP-SDM: IP connection for DMS switch only.

— EB Link Intf: From the pull-down menu, select the interface for EB Link connect.

• DK-X25: Datakit connectivity 5ESS Switch Only.

• DK-ASY: Datakit connection DMS switch only.

• IP-ASM: IP connection for 5ESS only (ASM feature required).

• IP-ASY-DY: IP connection via Dynastar/Cisco router for DMS switch only.

• IP-ASY-AI: IP connection via AI system for DMS switch only.

• IP-EIU: IP connection for DMS switch only.

• IP-VSOS: IP connection for DMS switch only.

• IP-X25-AI: IP connection via AI system for 5ESS switch only.

— A new window will appear & you will need to populate (login, password, Security Class, & port information.



• IP-X25-DY: IP connection via Dynastar/Cisco router for 5ESS switch only.

— A new window will appear & you will need to populate (login, password, Security Class, & port information.

• IP-SDM: IP connection for DMS switch only.

• The following Fields as same for all switch types to be added.— RC Dialstring/IP Address: IP Address and/or Datakit dialstring for the RC Link for the

specific switch. (DNS server and/or /etc/hosts may need to be updated).

— EB Dialstring/IP Address: IP Address and/or Datakit dialstring for the RC Link for the specific switch. (DNS server and/or /etc/hosts may need to be updated).

— CCP Name: Upstream system name associated with Task Toolkit. (Populate this field only if specified by ALU 8950 VAM support personnel.



Querying Switch Information - Shadow

2. The switch Query GUI screen will be displayed, and the following three fields can be used for the data query.

NOTE:Wildcard key * key can be used in fields that have input values.

• You may query the data on either of the 3 fields.— Switch CLLI: — Switch Name:

— Switch Generic:

3. Once the switch Query GUI screen displays the information; the full data can be viewed by selecting the appropriate switch.

— Click on “Back To PROFILE SUMMARY” Button and Click on “NEW Query” button to query on another office record.







— Select Switch Query tab on the GUI screen.



Update Switch Information - Shadow

2. The Query Data Input GUI screen will be displayed, and the following three fields can be used for the data query.

— Switch CLLI: — Switch Name:

— Switch Generic:


• You may query the data with a wildcard key * and Click “SUBMIT” when done.3. Once the switch Query GUI screen displays the information; select the switch to update by

clicking the switch name entry.

4. On the “Switch Profile” GUI screen; update the switch information fields as required.

— Click on “SUBMIT” Button to update the office record.

— Click on “Back To PROFILE SUMMARY” Button to return to previous screen.







— Select Switch Update tab on the GUI screen.

Issue: GA-1, July 20106 - 1 0


Delete a Switch - Shadow

2. The switch Query GUI screen will be displayed, and the following three fields can be used for the data query.


• You may query the data on either of the 3 fields.— Switch CLLI: — Switch Name:

— Switch Generic:

3. Once the switch Query GUI screen displays the information; the full data can be viewed by selecting the appropriate switch.

4. On the “Selected Switch Profile” GUI screen; answer the prompt “Do you want to delete this switch?”

— Click on “YES” Button to delete the office record.

• The following message will be displayed: “Deleting the switch. Please Wait..”

• Confirmation message: “Switch is deleted successfully” is displayed.

— Click on “NO” Button to return to previous screen.







— Select Switch Delete tab on the GUI screen.

Issue: GA-1, July 20106 - 11


NON-Shadow Switch Admin OverviewThe following section will detail the steps required to add, delete, and update a Non-Shadowed switch into the 8950 VAM application. Non-Shadow switches are used by customers outside the North American Markets.

• This switch type is used primarily for the Task ToolKit and Task Builder application.• The following switch types can be added as a NON-Shadowed switch.• List of supported switch type and switch generic:

Switch Type/Generic List: TGI Info

TGI Info (Switch Type/Switch generic) Description

5020MGC/MG631 5020MGC/MG64

5100CMS/CMS100

5101VMS/AVMS42

5420CTS/CT1500

5420PCM/PCM10

5450AGC/AGCF51

5529APC/AP2140

8670GUP/GUP501

8950AAA/AAA523

AAG/AAG631

AAG/AAG64

ANP/AN82

AXE/AF29AXE/AF46

BGCF/BG131BGCF/BG142BGCF/BG1500BGCF/BG61BGCF/BG611

BIGCF/BI1423BIGCF/BI1500BIGCF/BI61

Issue: GA-1, July 20106 - 1 2


CDOT/MAXLCDOT/MAXXL

DMS/NCS15DMS/SN06DMS/SN062DMS/SN07DMS/SN08DMS/SN09DMS/SN10

E/E10B

ENUM/ENUM12

ENUMDIR/ENUMDR

ERIC/E10

FS3K/FS13FS3K/FS14

FS5K/F101FS5K/F11FS5K/F142FS5K/F21FS5K/F30FS5K/F31

Broadworks switches

HSS/HS30HSS/HS60HSS/HS70HSS/HS71HSS/HS72

HSS Switches

LCM/LC62LCM/LC63

LCM switches

MGCF/MG53MGCF/MG62MGCF/MG63

MGCF switches

NEC/N61

S1240/EC72


Issue: GA-1, July 20106 - 13


SIEMENS/S15

SONUS/S51SONUS/S60SONUS/S65

To add SONUS switches into system.

SUNVMS/SUN20


Issue: GA-1, July 20106 - 1 4


NON-Shadow Switch Administration GUI





— Select Switch Administration option (Ensure Non-Shadowed Switch option is selected)

NOTE:It may take atleast 2-3 minutes for the following Switch Admin GUI screen to appear.

Issue: GA-1, July 20106 - 15


Adding a New Switch - Non-Shadow

2. You will need to input the following information to add the switch into the system.

• The following Fields as same for all switch types to be added.— Switch Id: Input the name of the switch to be added.

— TGI Info: From the pull-down list, select the switch type and generic of the switch. (Refer to Non-Shadow Admin- overview section “Switch Type/Generic List: TGI Info” for full information on the available list.

— Upstream Name: Input the upstream system name that is associated with this switch (If applicable); otherwise leave it blank.

— RC Inhibit: This field can be used to either send/block service orders processing for the particular switch. From the pull-down list, select on the of the following two options:

• Resume: This value will allow the system to send service orders to the switch.

• Inhibit: This value will block the system to send service orders to the switch.

— Connect Status: This field represents the status of the link connection to the switch. The admin must set the status initially, then link status will be synchronized via the link_event message from EMM system. From the pull-down list, select one the of the four options:

• Connect: Connection to link is active & working.

• Disconnect: Link to switch is dis-connected. (Order processing will NOT occur).

• Wait: The link is inhibited (Switch engineering blocked order processing).

• IsConnectdown: Status of link is unknown.

Access Non-Shadow Switch Admin via GUI Interface1. Access the VAM launch page via a browser interface & login as int.







Issue: GA-1, July 20106 - 1 6


• Congested: This values is only for OMCP switches; where the link has congestion traffic and order processing will be slow.

— Current EMM: This field is used when a switch can be connected via 2 separate EMMS systems (primary or secondary). From the pull-down list, select the EMM connected to switch:

• Primary: Switch link is connected via primary EMM system.

• Secondary: Switch link is connected via secondary EMM system.

— EMM: Input the hostname of the EMM system.

— Secondary EMM: Input the hostname of the secondary EMM system.

NOTE:The EMM hostname must be defined in the CCP Name Administration GUI (From System Admin, select CCP Name Admin option).

— Alias: Not required.

— Password: Not required.

— Work Domain: The work domain of the switch.

3. After all of the field information is input, click the “SUBMIT” button to add the switch into the system.

4. To verify that the switch is added into the system, the following steps can be taken:

• From the Permission Administration screen:— Go to the RESOURCES screen and verify whether the switch configured exists in the list.

— Go to the RELATE RESOURCE GROUPS AND RESOURCES and verify whether the switch configured exists in the list.

• Go to the Task Execution Screen, bring up any Task screen and verify that the switch configured in the Switch Name list exists.

— Minute: The minute time when configuration requests with a default release method are released to the switch. Used with Automatic Release. This field is used for the option called "Default" under Release Method in the Task Execution GUI. Default = "1 a.m."

— Release Hour: The hour time when configuration requests with a default release method are released to the switch. Used with Automatic Release. This field is used for the option called "Default" under Release Method in the Task Execution GUI. Default = "1 a.m."

! CAUTION:If a value is specified for the (fields: Minute & Release Hour ) you will have to stop and restart the task application for the values to take effect.

Issue: GA-1, July 20106 - 17


Querying Switch Information - Non-Shadow

2. The switch Query GUI screen (Query Data Input) will be displayed, and the following three fields can be used for the data query.


— Switch ID: This is a free format input value that can be used to query any switch names.

— TGI Info: Pull-down list to query for a particular switch generic.

— Connect Status: Pull-down list to query on a specific switch connection.

• You may query the data on either of the 3 fields; click on the “SUBMIT” button once you have specified the query criteria.

3. Once the switch Query is compete, the data will be displayed in “Switch Profile Summary” GUI screen. The full data can be viewed by selecting the appropriate switch item.

— Click on any of the displayed item to display the full data.

— Click on “Back To PROFILE SUMMARY” Button and Click on “NEW Query” button to query on another office record.







— Select Switch Query tab on the GUI screen.

Issue: GA-1, July 20106 - 1 8


Update Switch Information - Non-Shadow

• When you are trying to update any of the switch information, you must first query the data and select the switch to update.

2. The switch Update GUI screen (Query Data Input) will be displayed, and the following three fields can be used for the data query.






3. Once the switch Query is compete, the data will be displayed in “Switch Profile Summary” GUI screen.

— Click on any of the displayed item to update the selected switch.

— If you selected the wrong switch, click on “Back To PROFILE SUMMARY” Button and select the correct switch. (Click on “NEW Query” button to start the query again.)

4. On the “Switch Profile” GUI screen; update the switch information fields as required.

— Click on “SUBMIT” Button to update the office record.

— Click on “Back To PROFILE SUMMARY” Button to return to previous screen.







— Select Switch Update tab on the GUI screen.

Issue: GA-1, July 20106 - 19


Delete a Switch - Non-Shadow

• When you are trying to delete a switch, you must first query for the switch to delete.2. The switch Delete GUI screen (Query Data Input) will be displayed, and the following three fields

can be used for the data query.






3. Once the switch Query is compete, the data will be displayed in “Switch Profile Summary” GUI screen.

— Click on any of the displayed item to delete the selected switch.

— If you selected the wrong switch, click on “Back To PROFILE SUMMARY” Button and select the correct switch. (Click on “NEW Query” button to start the query again.)

4. From “Selected Switch Profile” GUI, answer the prompt “Do you want to delete this switch?”


• The following message will be displayed: “Deleting the switch. Please Wait..”

• Confirmation message: “Switch is deleted successfully” is displayed.








Issue: GA-1, July 20106 - 2 0


EMS Administration OverviewElement Management System (EMS) manages one or more network elements of a particular type and provides an interface over which OSSs can provision services on the network element. This admin GUI interface is used to add the following switch types & generics into the VAM application:

EMS Type/Generic List:

For ems_types = OMCP: There are two parameters:• OMCP_SESSION_RECOVER: When its value is “Y”, it will enable the EMS ID to always

stay in the connected session. There is no default value for this field.• CSI_TELICA_SESSION_RFSH_FREQ: If the value for this field is “15”, then the session

will refresh itself in every 15 mins. This value should be ideally less or equal to the Switch timeout value. Again there is no default value.

For all values of ems_types; A parameter:• EMS_READ_TIMEOUT: Signifies the session timeout interval. Default value is 1 min.

EMS TYPE Generics/Release data

AAA523 AAA 5.2.3

AGCF51 AGCF 5.1

ANYPATH ANYPATH 10.0, ANYPATH 8.2

AP2140 APC 2.1.40

AVMS42 AVMS 4.2

ENUM ENUM 1.2

ENUMDIR ENUMDIR 1.2

GUP501 GUP 5.0.1

OCIP BROADWORKS 13.0 & BROADWORKS 14.0

OMCP OMCP 10.0.0, OMCP 10.1.0, OMCP 11.0.0, OMCP 12.0.0, OMCP 13.0.1, OMCP 9.9.0

SOAP SOAP_SBI

SONUS SONUS 5.1, SONUS 6.0, SONUS 6.5

SUNVMS SUNVMS 2.0

eSMR eSM R25SU6, eSM R26SU2, eSM R26SU3, eSM R26SU4, eSM R26SU5, eSM R26SU6, eSM R26SU7, eSM R26SU8

Issue: GA-1, July 20106 - 21


EMS Administration GUIThe EMS Administration GUI is used to configure network elements into application.

Access EMS Administration via GUI Interface1. Access the VAM launch page via a browser interface & login as int.




— Select EMS Administration option

Issue: GA-1, July 20106 - 2 2


Add an EMS network Element The process should be used to define a EMS network element into the 8950 VAM system.

2. You will need to input the following information to add the EMS network element into the system.

— EMS ID: Actual name of the EMS network element.

— EMS TYPE: Select the type of network element to be defined from pull-down list.

— EMS URL: Web address of the network element for connectivity.

— EMS Login: Login id to be used for the EMS connection..

— EMS Password: Password for the EMS connection.

— EMS INV LOGIN: Login id for the EMS INV connection.

— EMS INV PASSWORD: Password for the EMS INV connection.

— EMS PING TIME: Enter ESM PING TIME (in min). range of 15-480 only.

• ESM PING TIME should only be entered if EMS TYPE is eSM

— FS3K PING TIME: Enter FS3K PING TIME (in min). range of 15-480 only.

• FS3K PING TIME should only be entered if EMS TYPE is BROADWORKS

— EMS Attributes: Enter EMS Attribute Name. (30 alphanumeric characters max).

NOTE:You may define upto 10 EMS Attributes for the EMS element.

3. After all of the field information is input, click the “ADD” button to add the EMS element.






Issue: GA-1, July 20106 - 23


Query an EMS network Element

2. You may query the EMS network element by any of the following field.











• After all of the field information is input, click the “QUERY” button to query the EMS element.

• If you wish to query for all the data, just simply click the “QUERY” button.

3. Once the switch Query is compete, the data will be displayed in “EMS Admin Summary” GUI screen. The full data can be viewed by selecting the appropriate EMS element.

— Click on any of the displayed item to display the full data.

— Click on “Return To EMS Administration Menu” Button to query on another record.






Issue: GA-1, July 20106 - 2 4


Update an EMS network Element

• When you are trying to update any of the EMS network elements , you must first query the data and select the network element to update.

2. Click the “Query” button to query on all the the EMS network elements defined in the system.

— From the output list, click on any of the displayed elements to update.

3. You may update the EMS network element by any of the following field.











• After all of the field information is input, click the “UPDATE” button to update the EMS element.






Issue: GA-1, July 20106 - 25


Delete an EMS network Element

• When you are trying to delete any of the EMS network elements , you must first query the data and select the network element to delete.

2. Click the “Query” button to query on all the the EMS network elements defined in the system.

— From the output list, click on any of the displayed elements to delete.

— Click “Cancel” button to start over.

3. Once the network element is selected, a pop-up will prompt for: “Are you sure you want to delete this EMS ID ?”

— Click on “Okay” Button to delete the element.

• The following message will be displayed: “Doing delete . Please Wait..”

• Confirmation message: “EMS ID <name> successfully deleted.” is displayed.

— Click on “Cancel” Button to NOT delete the element.






Issue: GA-1, July 20106 - 2 6


EMM Administration OverviewElement Mediation Module (EMM) manages one or more 5ESS switch elements and provides an interface over which the 8950 VAM application can provision services on the 5ESS switch element.

• The EMM system is used in International markets (NON-North American) where X.25 connection to the switches is NOT directly connected to the 8950 VAM system. The EMM system serves as a gateway to provision service orders directly into the 5ESS switch.

EMM System Topology

mtds

SOReqHdlr5SOReqHdlr1

ldshndlr

cvuifc_EMMEMM

distributor

RCtrans5ESS

Databserespntfr

tmgr

1

2

3

4 5

7

8

9 10

6

•GUI Order sent by USER

•Order Validated & sent for processing.

•Order RCV from EMM

•Order Data created.

•Order sent for processing •EMM & 5ESS Processes the order

•Order marked processed.

•ORDER updated in DB & GUI

mtds



ldshndlr

cvuifc_EMMEMM

distributor

RCtrans

EMMdistributor

RCtrans5ESS

Databserespntfr

tmgr

1

2

3

4 5

7

8

9 10

6

•GUI Order sent by USER

•Order Validated & sent for processing.

•Order RCV from EMM

•Order Data created.

•Order sent for processing •EMM & 5ESS Processes the order

•Order marked processed.

•ORDER updated in DB & GUI

Issue: GA-1, July 20106 - 27


Helpful Hints: on 8950 VAM Server• How to check the TCP connection to the EMM server?

[xxx-int] netstat -a | grep 10001[xxx-int] ping <IP of EMM server>[xxx-int] netstat -rn[xxx-int] traceroute

Helpful Hints on EMM Server:• How to check the TCP connection to the 8950 VAM server?

# netstat -a | grep 10001

• How to check whether [NE] is running on EMM?# emmps | grep [NE]_cm

• How to check the Connection Status for a NE <switch>?# ConStat -n <switch>

NOTE:The D connections, TtyDCon and SprDCon, should be CONNECTED.

• How to trace the data flow from EMM (5ESS + switch acknowledgements)?# Spy -n <switch> TtyDCon

• How to look at the database readout from the switch when using a Verify (RDDB-) RCAT?# Spy -n <switch> SplrDCon

• How to set up a tracer <switch>_cm (or <switch>)?# telnet <emm machine># cd /opt/emm/config# tracer –I 1 –l15 –n 10000 <switch>_cm

• –I 1 = index 1

• –l15 = level 15 (on)

• –n 10000 = number of lines

• How to turn of a tracer <switch>_cm (or <switch>)?

Issue: GA-1, July 20106 - 2 8


# tracer –I 1 –l15 –n 10000 <switch>_cm

• –I 1 = index 1

• –l1 = level 1 (off)

• –n 10000 = number of lines

• Location of traces files in EMM system: # cd /opt/emm/traces# view <switch>_cm

• How to do an x25check on EMM?— If you have problems with the connection to the 5ESS, it can be helpful to know if a connection

can be made on the lowest level of x25. To check this, go to the unix shell and execute the command:

# /usr/sbin/x25check -i natacc00 <DTE address of the switch>

NOTE: If the connection succeeds you receive the message:

X25CHECK (c) COPYRIGHT Hewlett-Packard Company 1988.

Test Starts on .. Wed Mar 18 11:56:11 1998 Initialization of the test... CALL packet sent ...

The following figures have been measured on the network: Set up time : 244 ms Remote Connection Succeeded

Issue: GA-1, July 20106 - 29


CCP NAME Administration GUIThe CCP Name Administration GUI is used to configure EMM system into application.

Access CCP Administration via GUI Interface1. Access the VAM launch page via a browser interface & login as int.



— Select Application Administration icon

— Select CCP Name Administration option

Issue: GA-1, July 20106 - 3 0


Add EMM System The process should be used to define a new EMM system into the 8950 VAM system. Once this EMM system is defined, then it can be associated with a particular 5ESS switch and the 5ESS switch can be defined into the VAM system as a NON-Shadow switch.

2. You will need to input the following information to add the EMM into the system.

• The following Fields as same for all switch types to be added.— CCP Name: Name of the EMM system to be added into 8950 VAM server.

— CCP Hostname: The host name of the EMM system. (local /etc/hosts file & DNS server must know this particular hostname you are adding.)

— CCP Port Number: Input the tcp port number to connect to EMM system. (Default value = 10001). Refer to EMM admin team for this information.

NOTE:The CCP Port number can be obtained from the EMM system from the file: “/opt/emm/config/Dist”; look for value for ANCMisaSAP(10001 = default).

— Message Header Format: From the Pull-down list select value of 0.

— Orders to Process: From the Pull-down list select value of 1.

3. After all of the field information is input, click the “ADD” button to add the EMM into the system.

• Once all the EMM systems are added into the system, they can be associated with a particular 5ESS NON-Shadow switch as primary/secondary EMM.

4. You must provide the 8950 VAM server hostname & IP address to the EMM system administrator and ensure that the information is added into the EMM system.

NOTE:Refer to “EMM Admin Overview” section for further debugging/helpful hints information.






Issue: GA-1, July 20106 - 31


Query EMM System Information

‘2. Click the “Query” button to query on all the the CCP network elements defined in the system.

— Click the “Next” or “Prev” button to browse the CCP network elements and then click the “Select” button to view data for the network element.







Issue: GA-1, July 20106 - 3 2


Update EMM System Information

• When you are trying to update any of the CCP Name network elements information, you must first query the data and select the network element to update.

2. Click the “Query” button to query on all the the CCP network elements defined in the system.



3. Once the network element is selected, you may update any of the following fields information:

— CCP Name: Name of the EMM system to be added into 8950 VAM server.

— CCP Hostname: The host name of the EMM system. (local /etc/hosts file & DNS server must know this particular hostname you are adding.)

— CCP Port Number: Input the tcp port number to connect to EMM system. (Default value = 10001). Refer to EMM admin team for this information.

NOTE:The CCP Port number can be obtained from the EMM system from the file: “/opt/emm/config/Dist”; look for value for ANCMisaSAP(10001 = default).

— Message Header Format: From the Pull-down list select value of 0.

— Orders to Process: From the Pull-down list select value of 1.

4. After all of the field information is input, click the “Update” button to change the EMM info.






Issue: GA-1, July 20106 - 33


Delete a EMM System

‘2. Click the “Query” button to query on all the the CCP network elements defined in the system.



3. Once the network element is selected, Click on the “Delete” button and answer the prompt “Do you want to delete information for this CCP Name ?”


• The following message will be displayed: “Deleting date from ccpname_info table . Please Wait..”

• Confirmation message: “Record deleted from ccpname_info table.” is displayed.






Issue: GA-1, July 20106 - 3 4




7 VAM Links Admin

Overview


• RC & EB Links Admin (5E & DMS)


• Debug Links issues

• Link growth Overview

• Links status & monitoring



Link Admin IntroductionThis chapter will discuss in detail administration of switch links for the Translation Interface (Shadow database) application.

• Non-Shadow application links will addresses in another chapter. (International customers whose links connect via the EMM systems).

! CAUTION:Links Admin Menu applies only to NORTH AMERICAN MARKET CUSTOMERS!

This chapter can be used as a reference to perform administration of all the menu items associated with the Link Administration menu option shown below:

Link Administration Menu1. Log in as int from either the console or a PC via telnet into the L1 machine:




Link Administration Menu1) Return to NVAM System Admin Menu2) Recent Change Links Menu3) Echo-Back Links Menu4) System Links Status Menu5) Link Sharing Configuration Menu6) DMS Surveillance System Bypass Menu7) Recent Change/Echo-Back Link Status

Options (1 thru 4)

1 = Exit menu

2= Admin RC Links

3 = Admin EB Links

4 = All system switch links

Option 5 = Allows admin for EB links in shared mode.

Option 6 = Allows Admin for DMS Switch surveillance bypass

Option 7 = Report RC & EB Links status



Linkadmin utility

• Refer to UNIX Command, under each menu item to use this particular utility.• Examples:

— To connect RC Link: linkadmin RC CONNECT

— To disconnect EB Link: linkadmin EB DISCONNECT

— To activate EB Monitors: linkadmin EB MONITORS

— To test RC Link connection: linkadmin RC TSTMSG

The linkadmin utility can be used to access the menu items as shown below.

Usage details: linkadmin <link_type> <Operation>

<link_type>:

RC --> Recent Change

EB --> Echo-Back

HB --> Heart-Beat (only with INTRVL)

<operation>:

CONNECT --> Connect to a switch

DISCONNECT --> Disconnect from a switch

MONITORS --> Turn a switch's interface monitors ON or OFF

TSTMSG --> Send a test message to a switch

PASSWD --> Set password change interval for DMS RC link

INTRVL --> Set heartbeat interval (only with HB)

VCCONFIG --> Configure number of 5E RC virtual channels (only with RC)

TIMEOUT --> Disable/Enable Inactivity Timeout for DMS RC link

EBLKSHARE --> For Echo-Back shared link configuration

EBLKSHARE_INFO --> For Echo-Back shared link configuration information

EBLKSHARE_MON --> For Echo-Back shared link (TRKCOM) Monitors



Recent Change Links Admin

Option 2: RC Link Connect • Enhancement in 8950 VAM enables SWCOM and DMSWCOM processes to automatically

reconnect a disconnected link after 15 minutes.1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the RC Links connect Menu as follows:

[xxxxx-int] menu



— 2) Recent Change Links Menu

— 2) Connect to a Switch

• UNIX Command: [xxxxx-int] linkadm RC CONNECT

3. List of switches will be displayed on the screen as follows.

Recent Change Links Menu

1) Return to Link Administration Menu2) Connect to a Switch3) Disconnect from a Switch4) Turn Interface Monitors ON / OFF5) Verify RC Link Connection6) Update Password Change Interval7) Configure Inactivity Timeout Interval

Selection:

Recent Change Link Connection ============================= |PICK CLLI: 5E16TESTCLL ALBQNMMADC2 ALBQNMNEDC0 ALBQNMNESTU ALBQNMSHDC0 ||APRILPATCH5 ASWITCH5E14 ASWITCH5E15 ASWITCHSN05 ATTARCLLI11 ATTCORE5E16 ||CHMBGADGDS0 CHRXNCRXDS0 CLMBOH1165T CLSPCO11DC0 DLLSTX37DC0 DUMPTSTSN09 ||ELTRCA11DS0 FRSNCA01DS0 GNBPNCEMDS0 JCVLFLWFDC0 LSVKNV99DC0 LSVLKY27DS0 ||LTRKARFCDC0 MMPKTNLMDS1 MNTRLBEFORE MTRL122TEST MTRL130TEST MTRLPQQQ00T ||MTRLTESTFNL NIRMALYSN09 NRB5E16FR5N PEACHACOSW1 PEACHACOSW2 PHLAPAFGDSE ||PRCMFL03DS1 RDMDWASYDS1 SFOYPQ0100T STCGPADNDS0 TEST5E16FR5 TESTDMSSN07 ||TESTDUMPLOA TESTMRJAVAA TULSOK35DC0 WLANCA01DS0 WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |



— Use <Space Bar> to highlight the switch to disconnect and press <Enter>.

4. Default information defined under the Switch Admin menu to connect the RC Links will be displayed:

NOTE:The prompt that is display will vary upon the type of link type connection and switch type being used to connect; this output is only a reference in this chapter.

The following information will be used for connection to 5E16TESTCLL:

Dialstring: peachOffice ID: CVUNOVERIFYDo you want to continue? (Y|N) [D: Y] y

— To connect the link, type y and press <Enter>

— To update new link connect information, type n and press <Enter>. You will be prompted to re-enter the information again and re-connect the link.

5. Successful Link Connect Message will be displayed as follows.

Recent Change Link connected for CLLI ALBQNMNESTU.


— press <Return> & Keep selecting option 1) Exit to completely exit menu.



Option 3: RC Link Disconnect 1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the RC Links Disconnect Menu as follows:

[xxxxx-int] menu




— 3) Disconnect from a Switch

• UNIX Command: [xxxxx-int] linkadm RC DISCONNECT



4. Answer the following prompt:

Are you ready to disconnect Recent Change link for <SwitchCLLI> [y/n]?

— To disconnect the link, type y and press <Enter>

— To exit the disconnect, type n and press <Enter>

5. Successful Link Disconnect Message will be displayed as follows.

Recent Change link disconnected for ALBQNMMADC2



Recent Change Link Disconnection ================================ |PICK CLLI: 5E16TESTCLL ALBQNMMADC2 ALBQNMNEDC0 ALBQNMNESTU ALBQNMSHDC0 ||APRILPATCH5 ASWITCH5E14 ASWITCH5E15 ASWITCHSN05 ATTARCLLI11 ATTCORE5E16 ||CHMBGADGDS0 CHRXNCRXDS0 CLMBOH1165T CLSPCO11DC0 DLLSTX37DC0 DUMPTSTSN09 ||ELTRCA11DS0 FRSNCA01DS0 GNBPNCEMDS0 JCVLFLWFDC0 LSVKNV99DC0 LSVLKY27DS0 ||LTRKARFCDC0 MMPKTNLMDS1 MNTRLBEFORE MTRL122TEST MTRL130TEST MTRLPQQQ00T ||MTRLTESTFNL NIRMALYSN09 NRB5E16FR5N PEACHACOSW1 PEACHACOSW2 PHLAPAFGDSE ||PRCMFL03DS1 RDMDWASYDS1 SFOYPQ0100T STCGPADNDS0 TEST5E16FR5 TESTDMSSN07 ||TESTDUMPLOA TESTMRJAVAA TULSOK35DC0 WLANCA01DS0 WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |



Option 4: RC Link Monitors 1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the RC Links Monitors Menu as follows:

[xxxxx-int] menu




— 4) Turn Interface Monitors ON / OFF

• UNIX Command: [xxxxx-int] linkadm RC MONITORS




Turn monitors ON or OFF?

— To turn on monitors, type ON and press <Enter>

— To turn off monitors, type OFF and press <Enter>

5. Monitors status Message will be displayed as follows.

Recent Change Monitors turned ON for ALBQNMMADC2Press RETURN to go back to MENU


6. Once the monitors are activated, the data will be written to the following file:

• Monitors File: /rc/data/<SwitchClli>RC.mon

Monitor Recent Change Link Activity =================================== |PICK CLLI: 5E16TESTCLL ALBQNMMADC2 ALBQNMNEDC0 ALBQNMNESTU ALBQNMSHDC0 ||APRILPATCH5 ASWITCH5E14 ASWITCH5E15 ASWITCHSN05 ATTARCLLI11 ATTCORE5E16 ||CHMBGADGDS0 CHRXNCRXDS0 CLMBOH1165T CLSPCO11DC0 DLLSTX37DC0 DUMPTSTSN09 ||ELTRCA11DS0 FRSNCA01DS0 GNBPNCEMDS0 JCVLFLWFDC0 LSVKNV99DC0 LSVLKY27DS0 ||LTRKARFCDC0 MMPKTNLMDS1 MNTRLBEFORE MTRL122TEST MTRL130TEST MTRLPQQQ00T ||MTRLTESTFNL NIRMALYSN09 NRB5E16FR5N PEACHACOSW1 PEACHACOSW2 PHLAPAFGDSE ||PRCMFL03DS1 RDMDWASYDS1 SFOYPQ0100T STCGPADNDS0 TEST5E16FR5 TESTDMSSN07 ||TESTDUMPLOA TESTMRJAVAA TULSOK35DC0 WLANCA01DS0 WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |



Option 5: RC Link Verify The Update Password Change Interval menu option automatically changes the password for TaskToolKit supported DMS Recent Change Links.

• By default, the time interval for the password change is 80 days. • A cron job runs every day to check the time interval. When it reaches the specified days from

the menu, the cron job automatically generates the password and updates your database.1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the RC Links Verify Status Menu as follows:

[xxxxx-int] menu




— 5) Verify RC Link Connection

• UNIX Command: [xxxxx-int] linkadm RC TSTMSG



4. RC Link status Message will be displayed as follows.

Verifying connection to host ALBQNMMADC2. Please wait...Recent Change link is not connected for ALBQNMMADC2



Helpful hints for verifying a RC link connection and it’s displayed message output:• LINK is down = The link is down, attempt to reconnect using the menu application.

Verify Recent Change Link Connectivity======================================

|PICK CLLI: 5E16TESTCLL ALBQNMMADC2 ALBQNMNEDC0 ALBQNMNESTU ALBQNMSHDC0 ||APRILPATCH5 ASWITCH5E14 ASWITCH5E15 ASWITCHSN05 ATTARCLLI11 ATTCORE5E16 ||CHMBGADGDS0 CHRXNCRXDS0 CLMBOH1165T CLSPCO11DC0 DLLSTX37DC0 DUMPTSTSN09 ||ELTRCA11DS0 FRSNCA01DS0 GNBPNCEMDS0 JCVLFLWFDC0 LSVKNV99DC0 LSVLKY27DS0 ||LTRKARFCDC0 MMPKTNLMDS1 MNTRLBEFORE MTRL122TEST MTRL130TEST MTRLPQQQ00T ||MTRLTESTFNL NIRMALYSN09 NRB5E16FR5N PEACHACOSW1 PEACHACOSW2 PHLAPAFGDSE ||PRCMFL03DS1 RDMDWASYDS1 SFOYPQ0100T STCGPADNDS0 TEST5E16FR5 TESTDMSSN07 ||TESTDUMPLOA TESTMRJAVAA TULSOK35DC0 WLANCA01DS0 WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |



• Link is up and idle = The link is okay, no traffic across the link.• Link is up and busy = The link is okay, but some of the Virtual Channels (VCs) are processing

Recent Changes.• Service <SWCOM> for hostCLLI <CLLI> is not responding = The menu application got an

inappropriate response from SWCOM process. The SWCOM process may be busy; try again later.

• Service <SWCOM> for hostCLLI <CLLI> is hung = The menu application timed out waiting for a status response from SWCOM process. The SWCOM process may be busy; try again later.

• Service <SWCOM> for hostCLLI <CLLI> is unknown = The menu application timed out waiting for a status response from SWCOM process. The SWCOM process may be busy; try again later.

• RC Link not connected = This message is displayed when the RC Link information is wrong or Switch is down.

NOTE:For the last three cases, some more useful steps to be taken:

NOTE:Verify that the <SWCOM> process is ON, using Check System Status from the menu application. If not, then restart the process using Verify 8950 VAM Servers from the menu application.

• Kill the <SWCOM> process and restart it via Verify 8950 VAM Servers. This is not recommended as it may affect the status of the RCs that are in XMT (transmit) state.

Issue: GA-1, July 20107 - 1 0


Option 6: DMS Password Change Interval This option allows you to enable/disable the inactivity time-out for DMS Recent Change Links, and also allows you to set the inactivity time-out interval from minimum of 30 min to maximum of 1500 min.

• Currently, in DMS switches, the RC links time out for an inactivity period of 30 minutes and free up the switch resources (when this option is enabled).

• By disabling this option, the RC Link does not time-out for the inactivity period.1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the RC Links DMS Password Change Interval Menu as follows:

[xxxxx-int] menu




— 6) Update Password Change Interval

• UNIX Command: [xxxxx-int] linkadm RC PASSWD




Enter password interval for ASWITCHSN05 [D: 80]OK to update password interval to 30? [Y]

— Input the # of days for password update and press <Enter>

— Type Y and press <Enter> to reconfirm.

5. DMS Password update Message will be displayed as follows.

Password interval successfully updatedPress RETURN to go back to MENU


Update Password Change Interval for DMS RC Link ================================================ |PICK CLLI: ASWITCHSN05 DUMPTSTSN09 GNBPNCEMDS0 NIRMALYSN09 TESTDMSSN07 ||WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |

Issue: GA-1, July 20107 - 11


Option 7: Configure Inactivity Timeout 1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the RC Links Verify Status Menu as follows:

[xxxxx-int] menu




— 7) Configure Inactivity Timeout Interval

• UNIX Command: [xxxxx-int] linkadm RC TIMEOUT




(D)isable/(E)nable Inactivity Timeout for ASWITCHSN05 [D: E]

— To Disable, type D and press <Enter>

— To Enable, type E and press <Enter>

5. DMS RC Timeout status Message will be displayed as follows.

Inactivity timeout has been disabled.Press RETURN to go back to MENU


Disable/Enable Inactivity Timeout for DMS =========================================

|PICK CLLI: ASWITCHSN05 DUMPTSTSN09 GNBPNCEMDS0 NIRMALYSN09 TESTDMSSN07 ||WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |

Issue: GA-1, July 20107 - 1 2


Echo Back Links AdminThe following activities are not tracked on the Echo Back channel because the 5ESS does not produce RCV SUCCESS messages, or because the messages do not contain enough data to build a Verify.

The following should be avoided, since they may cause the shadow database to get out of synchronization:

• Office Data Base Editor: There are no messages on the Echo Back channel when the Office Data Base Editor is used. If use of the Editor is widespread, the switch should be dumped and reloaded. Consider using Power Tools instead of the Editor.

• RC BATCH without the VERBOSE Option: There are no messages on the Echo Back channel if RC BATCH is used without the VERBOSE option. If using RC BATCH, make sure the VERBOSE option is set.

• Use of the 9.15 view: The 9.15 RCV SUCCESS messages do not contain enough information to update the 9.3 views. Use the Power Tools instead.

• Use of Copy Views, 1.10, 5.10, 23.30, 23.33, 23.34: The RCV SUCCESS messages from Copy Views do not contain enough data to update the respective class 1, 5 and 23 views. Use the Copy Operation or Power Tools instead of Copy Views.

• Use of Global Recent Change (Class 28) views: The RCV SUCCESS messages from these views do not contain enough data to update the respective class 1 and class 23 views. Use Power Tools instead of Global Recent Change.

Option 2: EB Link Connect • Enhancement in 8950 VAM enables SWCOM and DMSWCOM processes to automatically

reconnect a disconnected link after 15 minutes.1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the EB Links connect Menu as follows:

Echo-Back Links Menu

1) Return to Link Administration Menu2) Connect to a Switch3) Disconnect from a Switch4) Turn Interface Monitors ON / OFF5) Verify EB Link Connection

Selection:

Issue: GA-1, July 20107 - 13


[xxxxx-int] menu



— 3) Echo-Back Links Menu

— 2) Connect to a Switch

• UNIX Command: [xxxxx-int] linkadm EB CONNECT



4. Default information defined under the Switch Admin menu to connect the EB Links will be displayed:

NOTE:The prompt that is display will vary upon the type of link type connection and switch type being used to connect; this output is only a reference in this chapter.

The following information will be used for connection to 5E16TESTCLL:

Dialstring: peachDo you want to continue? (Y|N) [D: Y] y

— To connect the link, type y and press <Enter>

— To update new link connect information, type n and press <Enter>. You will be prompted to re-enter the information again and re-connect the link.

5. Successful Link Connect Message will be displayed as follows.

Echo-Back Link connected for CLLI ALBQNMNESTU.



Echo-Back Link Connection ========================== |PICK CLLI: 5E16TESTCLL ALBQNMMADC2 ALBQNMNEDC0 ALBQNMNESTU ALBQNMSHDC0 ||APRILPATCH5 ASWITCH5E14 ASWITCH5E15 ASWITCHSN05 ATTARCLLI11 ATTCORE5E16 ||CHMBGADGDS0 CHRXNCRXDS0 CLMBOH1165T CLSPCO11DC0 DLLSTX37DC0 DUMPTSTSN09 ||ELTRCA11DS0 FRSNCA01DS0 GNBPNCEMDS0 JCVLFLWFDC0 LSVKNV99DC0 LSVLKY27DS0 ||LTRKARFCDC0 MMPKTNLMDS1 MNTRLBEFORE MTRL122TEST MTRL130TEST MTRLPQQQ00T ||MTRLTESTFNL NIRMALYSN09 NRB5E16FR5N PEACHACOSW1 PEACHACOSW2 PHLAPAFGDSE ||PRCMFL03DS1 RDMDWASYDS1 SFOYPQ0100T STCGPADNDS0 TEST5E16FR5 TESTDMSSN07 ||TESTDUMPLOA TESTMRJAVAA TULSOK35DC0 WLANCA01DS0 WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |

Issue: GA-1, July 20107 - 1 4


Option 3: EB Link Disconnect 1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the EB Links Disconnect Menu as follows:

[xxxxx-int] menu




— 3) Disconnect from a Switch

• UNIX Command: [xxxxx-int] linkadm EB DISCONNECT




Are you ready to disconnect EB Link for <SwitchCLLI> [y/n]?

— To disconnect the link, type y and press <Enter>

— To exit the disconnect, type n and press <Enter>

5. Successful Link Disconnect Message will be displayed as follows.

EB Link disconnected for ALBQNMMADC2



Echo-Back Link Disconnection ============================= |PICK CLLI: 5E16TESTCLL ALBQNMMADC2 ALBQNMNEDC0 ALBQNMNESTU ALBQNMSHDC0 ||APRILPATCH5 ASWITCH5E14 ASWITCH5E15 ASWITCHSN05 ATTARCLLI11 ATTCORE5E16 ||CHMBGADGDS0 CHRXNCRXDS0 CLMBOH1165T CLSPCO11DC0 DLLSTX37DC0 DUMPTSTSN09 ||ELTRCA11DS0 FRSNCA01DS0 GNBPNCEMDS0 JCVLFLWFDC0 LSVKNV99DC0 LSVLKY27DS0 ||LTRKARFCDC0 MMPKTNLMDS1 MNTRLBEFORE MTRL122TEST MTRL130TEST MTRLPQQQ00T ||MTRLTESTFNL NIRMALYSN09 NRB5E16FR5N PEACHACOSW1 PEACHACOSW2 PHLAPAFGDSE ||PRCMFL03DS1 RDMDWASYDS1 SFOYPQ0100T STCGPADNDS0 TEST5E16FR5 TESTDMSSN07 ||TESTDUMPLOA TESTMRJAVAA TULSOK35DC0 WLANCA01DS0 WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |

Issue: GA-1, July 20107 - 15


Option 4: EB Link Monitors 1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the EB Links Monitors Menu as follows:

[xxxxx-int] menu




— 4) Turn Interface Monitors ON / OFF

• UNIX Command: [xxxxx-int] linkadm EB MONITORS





— To turn on monitors, type ON and press <Enter>

— To turn off monitors, type OFF and press <Enter>


Echo-Back Monitors turned ON for ALBQNMMADC2Press RETURN to go back to MENU


6. Once the monitors are activated, the data will be written to the following file:

• Monitors File: /rc/data/<SwitchClli>EB.mon


Issue: GA-1, July 20107 - 1 6


Option 5: EB Link Verify 1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the EB Links Verify Status Menu as follows:

[xxxxx-int] menu




— 5) Verify EB Link Connection

• UNIX Command: [xxxxx-int] linkadm EB TSTMSG



4. EB Link status Message will be displayed as follows.

Verifying connection to host ALBQNMNEDC0. Please wait...Echo-Back link is not connected for ALBQNMNEDC0



Verify Recent Change Link Connectivity======================================

|PICK CLLI: 5E16TESTCLL ALBQNMMADC2 ALBQNMNEDC0 ALBQNMNESTU ALBQNMSHDC0 ||APRILPATCH5 ASWITCH5E14 ASWITCH5E15 ASWITCHSN05 ATTARCLLI11 ATTCORE5E16 ||CHMBGADGDS0 CHRXNCRXDS0 CLMBOH1165T CLSPCO11DC0 DLLSTX37DC0 DUMPTSTSN09 ||ELTRCA11DS0 FRSNCA01DS0 GNBPNCEMDS0 JCVLFLWFDC0 LSVKNV99DC0 LSVLKY27DS0 ||LTRKARFCDC0 MMPKTNLMDS1 MNTRLBEFORE MTRL122TEST MTRL130TEST MTRLPQQQ00T ||MTRLTESTFNL NIRMALYSN09 NRB5E16FR5N PEACHACOSW1 PEACHACOSW2 PHLAPAFGDSE ||PRCMFL03DS1 RDMDWASYDS1 SFOYPQ0100T STCGPADNDS0 TEST5E16FR5 TESTDMSSN07 ||TESTDUMPLOA TESTMRJAVAA TULSOK35DC0 WLANCA01DS0 WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |

Issue: GA-1, July 20107 - 17


System Links Status Menu Admin

Option 2: Display Link Address Info1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the System Links Status Menu as follows:

[xxxxx-int] menu



— 4) System Links Status Menu

— 2) Display Address / Dialstring Information

3. Switch Links address info & status of switches will be displayed on the screen as follows.

— Press n to access next screen, p for previous screen or q to quit.

System Links Status Menu

1) Return to Link Administration Menu2) Display Address / Dialstring Information3) Display Real Time Links Status4) Display Detailed Links Status Information5) Display Links Status Statistics6) Display Link Status - Switch Inhibit7) Update Heartbeat Interval8) Display The Time Links Have Been Up/Down

Selection:

Dialstring Information

SERVICE DEFAULT ACTUAL-------------------------------------------------------------------------5E16TESTCLLRC peach Link to switch is down.5E16TESTCLLEB peach Link to switch is down.ALBQNMMADC2RC ganga.iidc.lucent.com Link to switch is down.ALBQNMMADC2EB ganga.iidc.lucent.com Link to switch is down...................................N for next page, Q to quit:

Issue: GA-1, July 20107 - 1 8


Option 4: Display Detailed Link Status1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 4) Display Detailed Links Status Information



• Service --> Switch Process Service Name (RC = Recent Change Link; EB = Echoback link.)• Monitor Status --> Monitors will either be ON or OFF.• Links In Service --> 5ESS RC Links may be upto 4; DMS RC Links upto 1; EB Links = 3.• COM Interface --> Referst to the Interface used to make physical connection to the link.• Shared (EB) --> Y if shared with TRUNK system, else N. EB Link only.

Detailed Link Status Information

SERVICE MONITOR STATUS LINKS IN SERVICE COM INTERFACE SHARED(EB)------------------------------------------------------------------------------5E16TESTCLLRC OFF 0 DK-X255E16TESTCLLEB OFF 0 DK-X25 NALBQNMMADC2RC ON 0 IP-X25-AIALBQNMMADC2EB ON 0 IP-X25-AI N..................................ASWITCHSN05RC OFF 0 DK-ASYASWITCHSN05EB OFF 0 DK-ASY NATTARCLLI11RC OFF 0 DK-X25 N for next page, Q to quit:

Issue: GA-1, July 20107 - 19


Option 5: Display Links Status Statistics1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 5) Display Links Status Statistics


— Press q to access query screen or use space bar. You can Query on any of the options, Link, Time, Reason, Status, Date

• Link --> Query on specific Service Name (Ex: <switch>RC or <switch>*)

• Status --> valid values are DOWN, OK, WAIT

• Time --> Enter time, format is <hh:mm:ss>

• Date --> Enter date, format is <mm/dd/yyyy>

— WildCard Star *, can be used in the Query Format.

LINK STATUS STATISTICS

Link: Status: Time: Date: Reason:




-------------------------------------------------------------------------------Status Options: Query ExitQuery link status information

Issue: GA-1, July 20107 - 2 0


Option 6: Display Link Status - Switch Inhibit1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 6) Display Link Status - Switch Inhibit

3. Use the <SPACE> or <ARROW> keys to highlight the Query option and press <Enter>.

— You may query on any of the displayed field or leave blank to query on all data.

• press <ESC> key once all the data is input.

— If you make a mistake and wish to start over, press the <Delete> key.

4. The following data is displayed:

• SWITCH CLLI --> Switch hostclli• RC LINK STATUS --> Status of the switch’s Recent Change Link.• EXT SYS INHIBIT --> Y = System Inhibited from performing RC functionality

N = System is NOT Inhibited from performing RC functionality• EXT SYS NAME --> TASKGUI refers to system being used for ToolKit Application.

To abort any operation, press <Del> key, use CONTROL-N & CONTROL-P to page

SWITCH CLLI RC LINK STATUS EXT SYS INHIBIT EXT SYS NAME ----------- -------------- --------------- ------------

-------------------------------------------------------------------------------Options: Query ExitQuery for Switch CLLI and/or Switch ID

Issue: GA-1, July 20107 - 21


Option 7: Update Heartbeat Interval8950 VAM uses a periodic ‘heartbeat’ communication to monitor whether the link is up or down. To enable the ‘heartbeat’ interface to the specific switch link, you must enter a Recent Change message to the particular switch.

Prerequisite:• 5ESS SWITCH: A record with the field “CONST” equal to “KEY” needs to be created in the

5ESS 10.36 View. — If the 10.36 View does not have a record with CONST=KEY, the ‘heartbeat’ processing on 8950

VAM fails.

• DMS SWITCH: You should see, OCCNAME with the value CVHEARTBEAT (i.e., change, no change RC). The login process occurs again and the user can now send RC’s.

NOTE:If you are not familiar with creating Recent Changes on the SWITCH, contact your appropriate Switch System Administrator.




[xxxxx-int] menu




— 7) Update Heartbeat Interval




Issue: GA-1, July 20107 - 2 2



Current heartbeat interval for ALBQNMMADC2 is set to 30 minutesDo you want to change this value (Y|N) [D: Y]

— Type Y and press <Enter>

Update heartbeat interval for ALBQNMMADC2 to [13-1500 minutes]

— Type <HB Value> in minutes and press <Enter>

The value you have entered is 30. OK to update? (Y|N) [D: Y]


Heartbeat interval for ALBQNMMADC2 successfully updatedPress RETURN to go back to MENU


Issue: GA-1, July 20107 - 23


Option 8: Display The Time Links Have Been Up/Down1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 8) Display The Time Links Have Been Up/Down


Hostclli Selection

1) 5E16TESTCLL 2) ATTARCLLI11

3) ASWITCH5E14 4) TESTDMSSN09

5) ASWITCH5E15 6) TESTDMSSN077) EXIT

Enter the number of the switch CLLI:

• Select the corresponding hostclli number and press <Enter>.


All times since midnight through 21:00:18 on 03/16/2009 for central peach.

For Hostclli: ALBQNMMADC2 5E16F RCOS Channel UP Down Percent Last Time in Date Time Time Up Time State Last State01/15/2009 23:50:02 0:00:00 100.0 - -01/16/2009 23:50:02 0:00:00 100.0 - -01/17/2009 23:50:02 0:00:00 100.0 - -01/18/2009 23:50:02 0:00:00 100.0 - -......................................................................................................02/03/2009 23:50:04 0:00:00 100.0 - -02/04/2009 23:50:03 0:00:00 100.0 - - N for next page, Q to quit:


— Select option number to exit menu item.

Issue: GA-1, July 20107 - 2 4


Recent Change/Echo-Back Link Status1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu



— 7) Recent Change/Echo-Back Link Status


Recent Change/Echo-Back Link Status

Num of Num of Active Active HOSTCLLI rc-link-status Channels eb-link-status Channels------------------------------------------------------------------------------5E16TESTCLL DOWN 0 DOWN 0ALBQNMMADC2 DOWN 0 UP 1ALBQNMNEDC0 DOWN 0 DOWN 0ALBQNMNESTU UP 1 UP 3ALBQNMSHDC0 UP 1 UP 3APRILPATCH5 DOWN 0 DOWN 0ASWITCH5E14 DOWN 0 DOWN 0ASWITCH5E15 UP 1 UP 3ASWITCHSN05 DOWN 0 DOWN 0ATTARCLLI11 DOWN 0 DOWN 0ATTCORE5E16 UP 2 UP 3CHMBGADGDS0 UP 4 UP 3CHRXNCRXDS0 DOWN 0 DOWN 0CLMBOH1165T DOWN 0 DOWN 0CLSPCO11DC0 DOWN 0 DOWN 0DLLSTX37DC0 DOWN 0 DOWN 0DUMPTSTSN09 UP 1 UP 1 N for next page, Q to quit:


— Keep selecting option 1) Exit to completely exit menu.

Issue: GA-1, July 20107 - 25


Troubleshooting LinksThe purpose of this section is to provide information about troubleshooting links in 8950 VAM. The following steps should be used as a reference to debug links issues.

To debug link issues, you will upto 3 simultaneous telnet window sessions.

Debug RC Links Information

Window1: Ensure SWCOM process is running

Open a telnet window into the HP Server and ensure the SWCOM Process is okay and then finally run a tail on the SWCOM logs file.

1. You must ensure that that SWCOM process is running for the specified switch via command:

[xxxxx-int] ps -ef | grep -i <SwitchName>RC

1.1 If SWCOM process is NOT running, then you can restart with command:

[xxxxx-int] ckproc

or menu item:

[xxxxx-int] menu



— 2) Verify 8950 VAM Servers

1.2 If process is running, you can kill the process once you have obtained the PID with ps command and re-start the process.

[xxxxx-int] ps -ef | grep -i <SwitchName>RC (Note the PID of process)

[xxxxx-int] kill <PID> (use the -9 option if required)

[xxxxx-int] ckproc (This command will restart the killed process)

2. You will need to monitor the process logs file located in /rc/data/<SwitchName>RC.err file.

[xxxxx-int] tail -f /rc/data/<SwitchName>RC.err

Window2: Monitor RC Link traffic data

In a second telnet window, you must activate RC link monitors for the specified switch and monitor the activity across the link.

3. You must activate RC link monitors for the specified switch. The monitors will be located in /rc/data/<SwitchName>RC.mon file.

[xxxxx-int] tail -f /rc/data/<SwitchName>RC.mon

Issue: GA-1, July 20107 - 2 6


Sample 5ESS RC Link traffic data

Sample 5ESS Heart Beat message data

03/17 09:37:58REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:5ACTION:CONNECT RQSTDATA:RCOS1

03/17 09:37:59REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:7ACTION:X.25 CONN ACCEPTDATA:3801149

Link ID 1: Connect Request

Link ID 1: Connect Accept

• You should see similar connect/Accept message for each Link ID 1 thru 4.

03/17 09:42:10REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:40ACTION:SNDDATA:11p0FORM="10V36"&"CHG",CONST="KEY",CHG^M

03/17 09:42:14REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:13ACTION:RCVDATA:11 11p11 OK

RCV 10.36 Change Send

RCV 10.36 Successful

• You should see a SND message and RCV on the same Link ID (1, 2, 3, or 4).

Issue: GA-1, July 20107 - 27


Sample 5ESS RC message data (4.14 View)

Window 3: Administer Link Configuration

Open a telnet window into the HP Server and try to administer the LINK issue as needed (Connect RC Link, Disconnect RC Link, Connect EB Link, Disconnect EB Link, etc).

03/17 12:07:32REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:62ACTION:SNDDATA:11j0FORM="RC_HGRPAS"&"VFY",NPA=714,OFFCOD=210,HUNDGRP=35,VFY

03/17 12:07:38REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:1024ACTION:RCVDATA:11 11j11FORM=RC_HGRPAS&VFYNPA=714OFFCOD=210HUNDGRP=35RMTYPE=CCKTSM=1PKTSM=0HRI=PORTEDOUT=CKTCNT=0PKT..............................................................................................................................HGCX5[4]=CKT.

03/17 12:07:42REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:1024ACTION:RCVDATA:11 11j1MLHGCX5[5]=CKT.MLHGCX5[6]=CKT.MLHGCX5[7]=CKT.MLHGCX5[8]=CKT.MLHGCX5[9]=CKT.MLHGC..............................................................................................................................MLHGPX1[4]=PKT.MLHGPX1[5]=PKT.M

03/17 12:07:51REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:357ACTION:RCVDATA:11 ..............................................................................................................................

03/17 12:07:51REM_PARTNER:5ETOPASRC LINK_ID:1 DATA LENGTH:8ACTION:RCVDATA:11 11j0

Action SND=Data Sent to the switch.

DATA:11j0 = Data Msg sent to switch. (11J is format & 0 means data) sent).

Action RCV=Data received from switch.

DATA:11j1 = Msg received; (DATA LENGTH:1024 = additional data).

DATA:11j0 = Message End; (DATA LENGTH < 1024 = End of data).

Issue: GA-1, July 20107 - 2 8


Links Checks in 5ESS SwitchThe purpose of this section is to provide information about RC links verification in 5ESS switch. The following steps should be used as a reference only, for further details, refer to the following documents available on the Alcatel-Lucent LED web site.

• 5ESS RECENT CHANGE GROWTH PROCEDURES• 5ESS ECHO BACK GROWTH PROCEDURES”• DMS RECENT CHANGE GROWTH PROCEDURES• DMS ECHO BACK GROWTH PROCEDURES”

Ensure 5ESS Processes Running1. You must login to the 5ESS switch at a UNIX level and ensure that the following 3 processes are

active and running properly.

• HMtopsip, TMtopprpc, & TOPperp1.1 If the above 3 processes are NOT running in the switch, a Level-1 Craft Init may be required in the

switch.

NOTE:While this procedure does not impact call processing, it **does** interrupt all I/O interface channels and must be coordinated with 5ESS office personnel.

Ensure 5ESS ‘Heartbeat’ Defined8950 VAM uses a periodic ‘heartbeat’ communication to monitor whether the link is up or down. To enable the 8950 VAM ‘heartbeat’ interface across this link, a recent change message must establish the following translation within the 5ESS.

2. A record with the field “KEY” set to the value of “KEY” must be created in the 5ESS or DRM 10.36 View. If the 10.36 View does not have this record, the heartbeat processing on 8950 VAM will fail.

NOTE:If you are not familiar with creating recent changes on the 5ESS or DRM, consult your 5ESS Switch Administrators.

Ensure 8.1 RCV Success Messages3. If the Echo Back link receives no RCV SUCCESS messages and no heartbeat messages, it

might be an indication that in the 8.1 View, field RC VERBOSE (on screen 3 of the view) needs to be set to a value of “Y” to flag those messages for routing to the Echo Back channel.

• Refer to RECENT CHANGE GROWTH PROCEDURE document; consult Switch Admin.• Change to 8.1 view may present a delay upto an hour.

Issue: GA-1, July 20107 - 29


Link Sharing Configuration Menu AdminThis menu item is used to administer Echo Back links that can be used in a shared mode with the Alcatel-Lucent 8950 TRUNK application. In this configuration the TRUNK Application will share the Echo Back Link of the VAM Application.

Customers that have NOT purchased the Alcatel-Lucent 8950 TRUNK application can ignore these menu items.

Option 2: EB Link Sharing ConfigurationThis menu item should be used to configure the EB link in the 8950 VAM system to be shared by the 8950 TRUNK Application. Configuration of the Echo-Back Link must occur on both systems. It is the responsibility of the appropriate admin to configure the correct information to activate the Echo Back Link in a shared mode.




[xxxxx-int] menu



— 5) Link Sharing Configuration Menu

— 2) Echo-Back Link Sharing

• UNIX Command: [xxxxx-int] linkadm EB EBLKSHARE

Link Sharing Configuration Menu

1) Return to Link Administration Menu2) Echo-Back Link Sharing3) Echo-Back Shared Link Configuration Information4) Echo-Back Shared Link (TRKCOM) Monitors

Selection:

Issue: GA-1, July 20107 - 3 0





Enter EB link configuration type (S for Shared, D for Direct) [D:S]

— Type s and press <Enter>

Enter TRUNK machine name (up to 8 characters):

— Type <TrunkSystemHostname> and press <Enter>

Enter IP address for trunk1: 135.192.100.101

— Type <TrunkSystemIPAddress> and press <Enter>

TRUNK machine name is <TrunkSystemHostname>TRUNK machine IP address is xxx.xxx.xxx.xxxIs this information correct? (Y|N) [D:Y] y


5. Update status Message will be displayed as follows.

Provide the following information to the TRUNK machine Administrator:ATP machine name is peachATP machine IP address is 135.112.176.161Switch CLLI is ALBQNMMADC2Echo-Back service is ALBQNMMADC2EBTCP port number for ALBQNMMADC2EB is 24096/tcp


— The above display information should be used to configure the 8950 TRUNK System.



Issue: GA-1, July 20107 - 31


Option 3: Display EB Shared Link Information1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 3) Echo-Back Shared Link Configuration Information

• UNIX Command: [xxxxx-int] linkadm EB EBLKSHARE_INFO



4. EB Shared Link information will be displayed as follows.

The following is the EB shared link configuration information:TRUNK machine name is trunk1ATP machine name is peachATP machine IP address is 135.112.176.161Switch CLLI is ALBQNMMADC2Echo-Back service is ALBQNMMADC2EBTCP port number for ALBQNMMADC2EB is 24096/tcp


— The above display information should be used to configure the 8950 TRUNK System.



Issue: GA-1, July 20107 - 3 2


Option 3: Activate EB Shared Link Monitors1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 4) Echo-Back Shared Link (TRKCOM) Monitors

• UNIX Command: [xxxxx-int] linkadm EB EBLKSHARE_MON





— type ON or OFF and press <Enter>

Select TRKCOM instance from the following:TRKCOM_1 is servicing: ALBQNMMADC2EBPress RETURN to continue...

— Output will display switch associated with TRKCOM process number, press <Enter>

Enter TRKCOM instance number (1 to 1)

— Type TRKCOM Instance number and press <Enter>

— Monitors status Message will be displayed as follows.

Select TRKCOM instance from the following:TRKCOM_1 is servicing: ALBQNMMADC2EBPress RETURN to continue...


5. Once the monitors are activated, the data will be written to the file displayed previously.

• Example Monitors File: /rc/data/TRKCOM_1.mon

Monitor Recent Change Link Activity =================================== |PICK CLLI: 5E16TESTCLL ALBQNMMADC2 ALBQNMNEDC0 ALBQNMNESTU ALBQNMSHDC0 ||APRILPATCH5 ASWITCH5E14 ASWITCH5E15 ASWITCHSN05 ATTARCLLI11 ATTCORE5E16 ||TESTDUMPLOA TESTMRJAVAA TULSOK35DC0 WLANCA01DS0 WNVLILACDS1 ALL || ||Arrow keys, Space bar & backspace all move cursor. Return selects option. |

Issue: GA-1, July 20107 - 33


DMS Surveillance Bypass Menu AdminIn addition to the recent change update via systems such as TNM or NMA, 8950 VAM offers an alternative to provide “sync” information that keeps the mirror database in “sync.” Surveillance System Bypass retrieves 24-hour Echo Back messages from the DMS switch and acts as an alternative to the use of an external system to gather Echo Back information.

Option 2: Enable Bypass File Downloading1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu



— 6) DMS Surveillance System Bypass Menu

— 2) Enable Bypass File Downloading


Hostclli Selection





— Select the corresponding hostclli number and press <Enter>.

DMS Surveillance System Bypass Administration Menu

1) Return to Link Administration Menu2) Enable Bypass File Downloading3) Disable Bypass File Downloading4) Initiate Bypass File Download5) View Bypass File Downloading Errors

Selection:

Issue: GA-1, July 20107 - 3 4



Enter file download time (00-23 hours) for ASWITCHSN05 [D: ]:

— Input value between 0 to 23 and press <Enter>

Press RETURN to continue...


Issue: GA-1, July 20107 - 35


Option 3: Disable Bypass File Downloading1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 3) Disable Bypass File Downloading


Hostclli Selection







Are you sure you want to disable file download for ASWITCHSN05? (Y|N) [D: N]:


Press RETURN to continue...


Issue: GA-1, July 20107 - 3 6


Option 4: Initiate Bypass File Downloading1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 4) Initiate Bypass File Download


Enter date (yyyy/mm/dd) to download data files [D: ]

— Input date in format <yyyy/mm/dd> and press <Enter>

Hostclli Selection







File download request successfully sent to selected switch CLLI(s).



Issue: GA-1, July 20107 - 37


Option 5: View Bypass File Downloading Errors1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 5) View Bypass File Downloading Errors


Enter date (yyyy/mm/dd) to download data files [D: ]

— Input date in format <yyyy/mm/dd> and press <Enter>

Hostclli Selection







***** BYPASS ERRORS FOR CLLI GNBPNCEMDS0 *****03/16 22:42:00 : Downloading of DLOG file for 20090316 is being stopped becauseof the error in sending [DLOG] command to the switch. RC link not connected.



Issue: GA-1, July 20107 - 3 8


EchoBack Filter Table ConfigurationThis menu allows for configuration of EB message from the 5ESS switch to be provided with a priority of High (H), Medium (M), or Low (L) for processing the RCVs by VAM system.



2. Access the Echo Back Filter Table Menu as follows:

[xxxxx-int] menu



— 2) Display/Change Echoback Filter Table

3. The following screen will be displayed to configure the Echo Back Filter Table.

To abort any operation, hit <Del> key. Use Control-N & Control-P to page

SWITCH CLLI ORIGINATOR ID VIEW NUMBER RC FUNC_CODE PRIORITY ----------- ------------- ----------- ------------ --------

------------------------------------------------------------------------------Options: Query Add Update Remove ExitQuery for Switch CLLI and/or Switch ID

Issue: GA-1, July 20107 - 39


Add EB Filter Entry1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— Use <Space Bar> to highlight the Add option and press <Enter>.

3. You will need to input the following information to add the entry into the system.

• SWITCH CLLI: = Input the switch clli information.• ORIGINATOR ID: = Input the term ID from the 5ESS switch.• VIEW NUMBER: = Input the 5ESS View number.• RC FUNC CODE: = Input I (insert), D(delete), C(change) for RCV function.• PRIORITY: =Input H (high), M (medium), L (low) for the priority.

— press <ESC> key once all the data is input.


4. Exit the menu screen via the following:


Query EB Filter Entry1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— Use <Space Bar> to highlight the Query option and press <Enter>.

3. You will need to input the data in any of the following fields to Query the entry into the system.

• SWITCH CLLI: = Query the switch clli information.• ORIGINATOR ID: = Query the term ID from the 5ESS switch.• VIEW NUMBER: = Query the 5ESS View number.• RC FUNC CODE: = Query I (insert), D(delete), C(change) for RCV function.

Issue: GA-1, July 20107 - 4 0


• PRIORITY: =Query H (high), M (medium), L (low) for the priority.— press <ESC> key once all the data is input.




Update EB Filter Entry1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— Use <Space Bar> to highlight the Update option and press <Enter>.

3. You will need to query for the record to update first via the Query option and then update the data for the following fields:

• ORIGINATOR ID: = Update the term ID from the 5ESS switch.• VIEW NUMBER: = Update the 5ESS View number.• RC FUNC CODE: = Update I (insert), D(delete), C(change) for RCV function.• PRIORITY: =Update H (high), M (medium), L (low) for the priority.

— press <ESC> key once all the data is input.




Remove EB Filter Entry1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu



Issue: GA-1, July 20107 - 41



— Use <Space Bar> to highlight the Remove option and press <Enter>.

3. You will need to query for the record to update first via the Query option. Once the record to be deleted is found, move the cursor to that record and press <Esc> key.


Are you sure you want to delete this switch? (Y/N) [N]

— Input Y and press <CR>.




Issue: GA-1, July 20107 - 4 2




8 Switch Database Load Administration

Overview

The purpose of this chapter is to provide information about Switch Database Loads in 8950 VAM application. Detailed information will be provided on switch information transferred from a particular switch type into the VAM server. The following topics will be covered:

• High Level detail of Dump & Load Process

— ASM, Network method, and/or Tape method.

• 5ESS/DMS Script Tape Process

• 5ESS/DMS Database Load process

• Synchronization of surveillance files



Switch Database Dump & Load TopologyIn order for 8950 VAM to support an additional switches, the data from that switch must be loaded into the 8950 VAM database. Once this data is loaded into the database, then users’ can start to provision that switch. The steps required to extract the data from the switch and load into the 8950 VAM data base is called the “Database Dump & Load process. The Dump & Load can be performed via the following methods:

The high level steps required to complete the entire Dump & Load of a particular switch consists of the following four steps. Three of the steps will be performed on the 8950 VAM systems and one on particular switch system. The actual process will vary slightly depending on the Dump & Load method used from above table. The high level steps are as follows:1. Creation of a Dump script (on the VAM system).

– For Tape method: You will have to ship tapes to the switch site.– For Network method: Shipping of tapes are eliminated.

2. Dumping of actual switch data (on the switch system).– For Tape method: Switch technician will extract switch data & write onto new tapes &

ship back to 8950 VAM HP server location.– For Network method: Switch technician will have to extract data, but VAM 8950 will

pickup the data via network.3. Read switch data & convert Binary to OFR switch data (on the VAM system).

– Once data is read via Tape/Network method, SUN OSW system will be used to convert the ODD to OFR data record.

4. Load of switch data into 8950 VAM database (on the VAM system).– For Tape/Network method: Same process to load the data into the database.

Dump & Load Methods 5ESS DMS

Tape based (DAT Media) Yes Yes

Network via ASM system (Feature required) Yes No

Network via RC Link (Feature required) No Yes

Network via SDM (Feature required) No Yes



Tape: 5ESS Dump & Load ProcessTo complete the entire tape based 5ESS switch dump & load process, the following high-level steps must be completed.

Step 1: Tape: Create Dump List (5ESS)

Step 2: Tape: Generate Dump Script (5ESS)

Step 3: Tape: Switch data dump (5ESS)

Step 4: Tape: Read Switch Data (5ESS)

Step 5: Load Switch Data into Database

Tape: Create Dump List (5ESS)The Dump script must be created on tape drives that the switch and VAM HP server supports. (typically 4mm DAT tape). After the tape is created, it must be shipped to the appropriate switch site along with the 5ESS Tape based Dump & Load procedures available on the 8950 VAM Download website.

! CAUTION:It is the responsibility of the customer to ensure that the tape device on the switch site and 8950 VAM HP server’s tape device are compatible and that compatible media is used. (Ex: DDS-1, DDS-2, etc.)

Prior to starting this procedure you must have the following:• The 11-Character Switch CLLI name and the Switch RELEASE #.• One set of blank tapes with the following labels: (up to 5 Dat tapes total).

— 8950 VAM Dump Script: <11 Character Switch CLLI Name>

— Global/CNI: <11 Character Switch CLLI Name

— ODD1 Binary Tape: <11 Character Switch CLLI Name>

— ODD2 Binary Tape: <11 Character Switch CLLI Name> (If applicable)

— ODD3 Binary Tape: <11 Character Switch CLLI Name> (if applicable)

NOTE:Most offices will NOT requires up to 3 ODD tapes, the 3rd tape is only used from very large offices. It is also highly recommended that you ship 2 sets of each media to avoid any physical tape issues and/or read errors.

• Shipping details for shipping the Dump Script tape & the blank ODD tapes.





2. Access the Create Dump List Menu as follows:

[xxxxx-int] menu



— 2) Dump List/Dump Script Menu

— 2) Create Dump List

3. Select the number for the switch to create the dump list:

Hostclli Selection1) 5E16TESTCLL 2) ATTARCLLI11

3) ASWITCH5E14 4) TEST5E16FR5




NOTE:Once the Dumplist is created, you will see the following output.

Successfully create: /rc/data/odd_load/JANPATCHTES/DumpList


4. At this point, the dumplist for the switch is created.

— Press <Return> to go to Generate Dump Script Menu.

— Keep selecting option 1) Exit to completely exit back to UNIX prompt.



Tape: Update Dump List (5ESS)Normally all the views/tables will be dumped; however, the following process can be used to generate a dumplist with your choice of view/tables.




[xxxxx-int] menu




— 3) Update Dump List

3. Select the number for the switch to update the dump list:






DUMP SELECTION SCREEN

SWITCH CLLI: <SwitchName> RELEASE: <ReleaseNumber>

VIEW/TABLE/FORM DUMP (Y/N) -------- ----------

<DEL> ABORT <CTRL-N> PAGE DOWN <CTRL-P> PAGE UP--------------------------------------------------------------------------------Options: Update ExitCreate dump parameter list file



4. Use the <SPACE> or <ARROW> keys to highlight the Update option and press <Enter>. You will need to input the SWITCH CLLI and RELEASE information on the screen.

• press <ESC> key once all the data is input.

• The cursor will be under “VIEW/TABLE/FORM” field, press <Esc> Key again.

• The cursor will be under “DUMP Y/N” field; You may use arrow keys and change anyinformation you do NOT wish to dump to a value of “N”. Once all changes are complete, press<Esc> Key again.


Update Successfully

5. If you wish to use the current setting, you must go thru the steps to create the dumplist as shown in the previous section. At this point, the dumplist for the switch is updated.

— Select Exit option

— press <Return> to go to Generate Dump Script Menu.




Tape: Generate Dump Script (5ESS):1. Log in as int from either the console or a PC via telnet into the L1 machine:


2. Access the Generate Dump Script Menu as follows:

[xxxxx-int] menu




— 4) Write Tape to be Shipped to the Switch







Hostclli TEST5E16FR5 Release Selection1) alcatel5E16FR52) EXITEnter the number of the switch release:

• Select the corresponding release number and press <Enter>.


Select the number of the Machine on which the tape drive you wish to use is located:1) peach (Central)2) osw1.mh.lucent.com (OSW)3) Other machine4) EXITEnter the number of the machine name:

Machine Selection (Tape Device)

4. Perform the following steps to write data to tape applicable to your environment:

4.1 For Tape Device on HP System: Answer the following prompts:



• Select the corresponding number for central and press <Enter>.

The following drives type(s) 9-track DAT ON peach are available:1) d02(Uncompressed/DDS1)2) quitSelect the number corresponding to the Tape Drive you wish to use:

• Select the corresponding number for drive and press <Enter>.

Use DumpList Created Jan 15 16:56? [ Default Y ]



(Using tape drive with immediate report mode enabled (reel #1).)43 blocks

Tape written, now reading its contents to verify.

100644 int 30 Jan 15 16:56:25 2009 DumpList100644 int 42 Jan 15 17:15:00 2009 FILES.SUM100755 int 21535 Jan 15 17:15:00 2009 rc5e_dump43 blocks

ALL DONE


4.2 For Tape Device on SUN OSW System:: Answer the following prompts:

• Select the corresponding number for SUN OSW system and press <Enter>.

The following DAT drives ON "osw1" are available:( 1 ) d00(Uncompressed)( 2 ) quitSelect the number corresponding to the Tape Drive you wish to use:





*******************FILES.SUMDumpListrc5e_dump********************. . . .. . . .. . . .Tape written, now reading its contents to verify.



-rw-r--r-- 1 int staff 26 FEB 10 17:16 2000, FILES.SUM43 Blocks -rw-r--r-- 1 int staff 30 FEB 10 17:16 2000, DumpList-rw-r--r-- 1 int staff 21523 FEB 10 17:16 2000, rc5e_dump. . ALL DONEPress Return to go back to the menu

4.3 For Tape Device on Other Machine: Perform the following:

• You must work with the ALU product support team to configure access to these system. Thismethodology requires additional configuration.

• It is the responsibility of the customer to ensure there are NO incompatibility issues with tapedrives on the required system.

• Contact the ALU product technical support team for further help.

5. At this point, remove the Dump Script tape from the tape drive and ship the tape(s) to appropriate folks at the switch site.

• The Script tape is now created. You may wish to re-run the steps again to create a secondcopy of the script tape.

Issue: GA-1, July 20108 - 1 0


Tape: Switch data dump (5ESS):• The switch administrators will perform the required dump of the switch data and ship back the

data to the VAM administrators for loading to the VAM database. The switch data tapes will consist of a single Global CNI data tape & one or more Binary ODD data tape(s).

• This process will occur directly at the 5ESS switch location once the switch technician receives the Dump & Load scripts from the 8950 VAM administrators.

• Detailed steps by step procedures are available on the ALU LED download site in the document: “5ESS_OFFICE_TAPE_DUMP_PROCEDURES”. You must have this document to complete the switch dump.

• Once switch dump has been completed, the tapes can be shipped back to the 8950 VAM HP server location.

NOTE:NOTE: This process will take place at the switch site.

Issue: GA-1, July 20108 - 11


Tape: Read Switch Data tapes (5ESS)This step is the third of four steps involved in the complete Switch Database Load Procedure. In this step, the (GLOBAL & CNI tape) and (1 or more Binary ODD tapes) were generated at the switch site by the switch administrators and sent back directly to the 8950 VAM HP Server Administrator.

These tapes (GLOBAL/CNI and ODD tapes) will be read into 8950 VAM HP server and converted to switch database load records to be loaded into the 8950 VAM database.

The following are prerequisites to starting this procedure:• A GLOBAL/CNI data tape should have arrived from the switch.• 1 or more Binary-ODD tapes should have arrived from the switch. • The 11-Character CLLI code and Switch RELEASE # of the switch is required. (Obtained

from the 8950 VAM System Administrator. The same information used to generate the Dump Script tape.).

• The Recent Change and Echo Back links should be operational to the switch.

! CAUTION:It is strongly recommended to run the option to read switch data directly from the CONSOLE of the HP server to ensure dropped connection/window time-out does NOT affect the entire operation.

Tape: Read Global CNI data (5ESS)• Mount the “Global & CNI” data tape in the appropriate system drive.1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu



— 3) Read Switch Data

— 2) Read 5ESS CNI Tape

Issue: GA-1, July 20108 - 1 2








clli=TEST5E16FR5 gen=5E16FR5 release=alcatel5E16FR5 central=peachEnter Input Device Type (TAPE or EFT)? [Default: TAPE]: TAPE

• Input TAPE and press <Enter>.



4. Perform your specific step to read data from tape applicable to your environment:




• Select the corresponding number for device and press <Enter>.


Using Tape Device: d02 peach /dev/rmt/c7t0d0BEST

01/16/2009 11:45:41 Checking tape /dev/rmt/c7t0d0BESTReading tape:/rc/odd_load/TEST5E16FR5. . . . .. . . . .. . . . .

Issue: GA-1, July 20108 - 13


Successful tape read to peachPress RETURN to go back to MENU






Using Tape Device: d02 osw1 /dev/rmt/c7t0d0BEST

01/16/2009 11:45:41 Checking tape /dev/rmt/c7t0d0BESTReading tape:/rc/odd_load/TEST5E16FR5. . . . .. . . . .. . . . .Successful tape read to osw1Press RETURN to go back to MENU





5. At this point, remove the Global CNI Tape from the system and mount the 1st Binary ODD tape on the drive again. Press <Return> to go to Read Switch Data Menu.

Issue: GA-1, July 20108 - 1 4


Tape(s): Read Binary ODD data (5ESS)• Mount in order the “Binary ODD” data tape in the appropriate system drive.6. Read the Binary the ODD data as follows:

— 3) Read 5ESS ODD/OFR Tape Or DMS Tape7. Answer the following prompts accordingly:






clli=TEST5E16FR5 gen=5E16FR5 release=alcatel5E16FR5 central=peachEnter Input Device Type (TAPE or EFT)? [Default: TAPE]: TAPE

— Input TAPE and press <Enter>.



Issue: GA-1, July 20108 - 15








Using Tape Device: d02 /dev/rmt/0h08/09/1999 10:22:27 Checking Tape /dev/rmt/0hIs this a COPY: ODD tape? (Y or N)

• Type “Y” and press <Enter>.

Load data from tape...dd if=/dev/rmt/0hn bs = 10000|dd of=Part1 bs=100000+8699 records in0+8699 records outNot done yet.... . .. . .. . .Done reading the tape, please remove tape from tape drive.Is there another COPY:ODD tape? (Y or N)

• For multiple Binary ODD Tape Read: mount the next tape in the drive and type “Y”and press <Enter>.

• Once all Binary ODD Tapes are read into the system, press “N” and press <Enter>.

• After this prompt, the conversion of the Binary data to OFR data will occur and maytake up to a few hours depending upon system specs and size of switch data.


Rewinding the tape...-rw-r--r-- 1 int staff 45188243 Jan 9 10:26 part1 -rw-r--r-- 1 int staff 25188240 Jan 9 10:26 part2 -rw-r--r-- 1 int staff 5188243 Jan 9 10:26 part3-rw-r--r-- 1 int staff 34188249 Jan 9 10:26 part4Compressing Data...rmt: sw= TEST5E16FR5rmt: rmt: osw= oswtstaremittable:/osw/prog/local/bin:/osw/prog/oswbin:/osw/prog 5E13_1/BWM99-0015/pag/sparcsol: /usr/bin:processing /osw/data01/TEST5E16FR5/odd.tape/part1completed /osw/data01/TEST5E16FR5/odd.tape/part1processing /osw/data01/TEST5E16FR5/odd.tape/part2

Issue: GA-1, July 20108 - 1 6


completed /osw/data01/TEST5E16FR5/odd.tape/part2Successful ODD Tape Load to /osw/data01/TEST5E16FR5.

Do you want to selectively load the ODD Data?(Y or N)[Default=N]

• You can simply let it timeout or type “N” and press <Enter>.


Start data conversion: this may take some time, please be patient...Fri Jan 16 12:40:10 EST 2009/osw/prog/5e13_1/BWM99-0015/pag/sparcsol/offswofr-o /osw/data01/TEST5E16FR5-m /osw/prog/5e13_1/BWM99-0015/mask-i /osw/data01/TEST5E16FR5/etc/ofrlist-d /osw/data01/TEST5E16FR5/etc/oddfile-l /osw/data01/TEST5E16FR5/Log-e /osw/prog/5e13_1/BWM99-0015/rc-creal 0m34.06suser 0m3.40ssys 0m15.22sSTART:5051:10.38START:5107:18.112008-10-25 12:45:36 Tape Conversion CompleteData from tape read successfully.... Press RETURN to go back to MENU







Load data from tape...dd if=/dev/rmt/0hn bs = 10000|dd of=Part1 bs=100000+8699 records in0+8699 records outNot done yet.... . .. . .. . .

Issue: GA-1, July 20108 - 17


Done reading the tape, please remove tape from tape drive.Is there another COPY:ODD tape? (Y or N)

• For multiple Binary ODD Tape Read: mount the next tape in the drive and type “Y”and press <Enter>.

• Once all Binary ODD Tapes are read into the system, press “N” and press <Enter>.

• After this prompt, the conversion of the Binary data to OFR data will occur and maytake up to a few hours depending upon system specs and size of switch data.


Rewinding the tape...-rw-r--r-- 1 int staff 45188243 Jan 9 10:26 part1 -rw-r--r-- 1 int staff 25188240 Jan 9 10:26 part2 -rw-r--r-- 1 int staff 5188243 Jan 9 10:26 part3-rw-r--r-- 1 int staff 34188249 Jan 9 10:26 part4Compressing Data...rmt: sw= TEST5E16FR5rmt: rmt: osw= oswtstaremittable:/osw/prog/local/bin:/osw/prog/oswbin:/osw/prog 5E13_1/BWM99-0015/pag/sparcsol: /usr/bin:processing /osw/data01/TEST5E16FR5/odd.tape/part1completed /osw/data01/TEST5E16FR5/odd.tape/part1processing /osw/data01/TEST5E16FR5/odd.tape/part2completed /osw/data01/TEST5E16FR5/odd.tape/part2Successful ODD Tape Load to /osw/data01/TEST5E16FR5.

Do you want to selectively load the ODD Data?(Y or N)[Default=N]

• You can simply let it timeout or type “N” and press <Enter>.


Start data conversion: this may take some time, please be patient...Fri Jan 16 12:40:10 EST 2009/osw/prog/5e13_1/BWM99-0015/pag/sparcsol/offswofr-o /osw/data01/TEST5E16FR5-m /osw/prog/5e13_1/BWM99-0015/mask-i /osw/data01/TEST5E16FR5/etc/ofrlist-d /osw/data01/TEST5E16FR5/etc/oddfile-l /osw/data01/TEST5E16FR5/Log-e /osw/prog/5e13_1/BWM99-0015/rc-creal 0m34.06suser 0m3.40ssys 0m15.22sSTART:5051:10.38START:5107:18.112008-10-25 12:45:36 Tape Conversion CompleteData from tape read successfully.... Press RETURN to go back to MENU

Issue: GA-1, July 20108 - 1 8






9. At this point, Data conversion from Binary ODD data to OFR data has completed. With the OFR data, you will be ready to load the data into the system database.

— remove all the data tapes from the system.

— press <Return> to go to Read Switch Data Menu.


Issue: GA-1, July 20108 - 19


Network (ASM) : 5ESS Dump & Load ProcessTo complete the entire network based 5ESS switch dump & load process via ASM, the following high-level steps must be completed.

Step 1: Network (ASM): Create Dump List (5ESS)

Step 2: Network (ASM): Generate Dump Script (5ESS)

Step 3: Network (ASM): Switch data dump (5ESS)

Step 4: Network (ASM): Read Switch Data (5ESS)


Network (ASM): Create Dump List (5ESS)Network Based Dump & Load eliminates the use of tapes in the dump & load process and utilizes a TCP/IP link between the 5E/ASM and the HP Server. By utilizing the higher bandwidth TCP/IP link and the 5E/ASM, the dump script, CNI data, and 5ESS ODD data are transferred more efficiently.

The Network based Dump and Load process is almost the same as tape based Dump & Load without the tapes transfer to switch sites. In these steps, the switch data will be loaded onto the HP server via the network from the ASM system. In order to use this method, you must purchase the “Network based Dump & Load” feature & have access to ASM system in the switch network.

• The first step is for the 8950 VAM Server to generate a Dump Script and transfer it to the Administrative Services Module (ASM) for use by the 5ESS switch. The switch will use this Dump Script to provide switch data to the ASM.

• Secondly, the ASM will get the switch data and store it, then send it to the Off-Switch Workstation (OSW).

• Thirdly, the OSW converts the switch data and loads the information into the HP Server database.

• Finally load data into the 8950 VAM database.

Issue: GA-1, July 20108 - 2 0


Prerequisite:

Prior to starting this procedure you must have the following:• The 11-Character Switch CLLI name and the Switch RELEASE #.




[xxxxx-int] menu

















Issue: GA-1, July 20108 - 21


Network (ASM): Generate Dump Script (5ESS):1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 5) Write Dump Script to ASM







Hostclli TEST5E16FR5 Release Selection1) alcatel5E16FR52) EXITEnter the number of the switch release:





Now, check the network availability.This may take about one minute...The link is available, now remote copy files to the ASM...Remote copy FILES.SUM to the ASM...Remote copy DumpList to the ASM...Remote copy rc5e_net_dump to the ASM...Remote copy cni_dump to the ASM...Remote copy asm_dl_env to the ASM...Remote copy is complete, now check them to verify.

Issue: GA-1, July 20108 - 2 2


The checksum and sizes of files to be transferred to remote ASM:5e14295600347130DumpList1705798349 9000 rc5e_net_dump34739410196002cni_dump2903809813247asm_dl_envThe checksum and sizes of files transferred to remote ASM:5e142956003471 30 DumpList1705798349 9000 rc5e_net_dump3473941019 6002 cni_dump2903809813 247 asm_dl_envALL DONEPress RETURN to go back to MENU

4. At this point, the Dump Script information is now on the ASM system.

• The switch administrators will then perform the required dump of the switch data in the ASMand inform the 8950 VAM administrator that the process is complete.

Issue: GA-1, July 20108 - 23


Network (ASM): Switch data dump (5ESS):The purpose of this section is to provide information about executing Dump Script for 5ESS switch in the ASM system. This procedure executes the Dump Script on the ASM machine, to get the Global CNI and ODD data from the switch and store it in the ASM database archive.

• For executing the following procedure, contact the person having “root” access to the ASM (normally, the Switch Technician). This is equivalent to the 5E Technician making CNI and ODD tapes.

NOTE:You need to log on to the ASM machine associated with the switch from which you are performing the Dump/Load procedure.

Prerequisite Information:

— ASM machine name and IP Address associated with the particular switch CLLI.

— Root login password for ASM system.

— Node name and/or ASM login id associated for particular switch.

1. Log in as root from either the console or a PC via telnet into the ASM machine:


2. Run the “rc5e_net_dump” script in the appropriate ASM Node login for the switch to extract the switch data.

# cd /users/<node#>/cvubin/rc5e_net_dump

— Where <node#> = the user id for the particular node being used.

— The following log files can be monitored in the ASM system during the data extraction process:

• /tmp/<node#>_asmdump.log

• /users/<node#>/cvudata/asmdump.log

— You should see a successful message once this data extraction is complete.


Please wait... this may take a few minutesBEGIN: 01/12/2000 14:23:21Delete data-ready flag file ...Make data directory ...Get .version fileThis Dump is Built for Generic: 5e14This Switch is Generic: 5e14(1)02.00Check 5ESS generic ... OKBegin to dump GLOBAL CNI data ...Copying cni_dump to ASM: /updtmp/cvutmp ...Copying DumpList to 3b21: /updtmp/cvutmp ...Remote execute 3b21:cni_dump ...

Issue: GA-1, July 20108 - 2 4


/updtmp/cvutmp/cni Does Not Exist. Creating.../updtmp/cvutmp/cni/log Does Not Exist. Creating...### MAIN: 200001121423 BEGIN TO DUMP CNI & GLOBAL DATA ### CNI: DUMP Start Time: Wed 01/12/00 14:23:38 ### CNI: 200001121423 Starting cni.c.r.. ######## CNI: 200001121423 Starting cni.g... ######## CNI: 200001121423 Starting cni.m... ######## CNI: DUMP End Time: Wed 01/12/00 14:23:48 *****### ODB: DUMP Start Time: Wed 01/12/00 14:23:48 *****GLOBAL PARAMETERS: ### ODB: 200001121423 Starting GLP194GLOBAL PARAMETERS: ### ODB: 200001121424 Starting GLP193### ODB: DUMP END Time: Wed 01/12/00 14:24:36 ****### MAIN: 200001121424 Creating FILES.LST for electronic transfer ######## MAIN: 200001121424 Dump Done #####Copy all cni data from 3b21 ...End of CNI data dumping.Begin to dump ODD data ...Copy odbe command to 3b21 ...Get number of odd data blocks ... 2752Copy odd data from AM ... ...........vcp: disk copy completedCopy imrodd.out ...Copy cmpodd.out ... Copy cpodd.out ... Get SM data ... - /no5odd/smdata1/imodd1.outEND of odd data dumping. Package CNI and ODD data ...a cni/ 0Ka cni/log/ 0Ka cni/log/odbe.log 1Ka cni/log/cnierr.m... 0Ka cni/log/cniout.m... 2Ka cni/log/cnierr.g... 0Ka cni/log/cniout.g... 2Ka cni/log/cnierr.c.r.. 0Ka cni/log/cniout.c.r.. 3Ka cni/log/DMPout 1Ka cni/log/DMPerr 1Ka cni/log/envirn 1Ka cni/log/ofrlist 1Ka cni/dump.done 1Ka cni/FILES.SUM 1Ka cni/FILES.LST 1Ka cni/NO5ODD.LST 1Ka cni/GLOFFICE 1Ka cni/GLP193 8Ka cni/15_17 1Ka cni/GLP194 8Ka cni/15_9 1Ka cni/15_11 1Ka cni/VERSION 1K

Issue: GA-1, July 20108 - 25


a no5odd/ 0Ka no5odd/cidata/ 0Ka no5odd/cidata/imrodd.out 32847Ka no5odd/data0/ 0K a no5odd/data0/cmpodd.out 28769Ka no5odd/data0/cpodd.out 10241Ka no5odd/smdata1/ 0Ka no5odd/smdata1/imodd1.out 2263Ka no5odd/.version 1Ka no5odd/vcpdata.d.Z 11KCompress data ...a CHCGILFRDS0.cni.tar.Z 23,789Ka CHCGILFRDS0.odd.tar.Z 24,329KDelete tmp directory ...Create data-ready flag file ...Now the CNI and ODD data (CHCGILFRDS0.tar) are ready in /users/node0/cvudata in the asmEND: 01/12/2000 14:32:26----------------------------------------- Dumping CNI & ODD data successful !!!----------------------------------------

Issue: GA-1, July 20108 - 2 6


Network (ASM): Read Switch Data (5ESS)This step is the third of four steps involved in the complete Switch Database Load Procedure. In this step, the GLOBAL & CNI data and Binary ODD data were generated on the ASM system by the switch administrators.

This data (GLOBAL/CNI and BINARY ODD ) will be read into 8950 VAM HP server and converted to switch database load records to be loaded into the 8950 VAM database.

The following are prerequisites to starting this procedure:• ASM switch data dump must be successfully completed.• The Recent Change and Echo Back links should be operational to the switch.





[xxxxx-int] menu




— 4) Read 5ESS/ASM Data From Network via ASM








clli=CHCGILFRDS0 gen=5E14 release=cso5E14 HP Server=orangeasmname=135.111.86.10 asmlogin=gong

Issue: GA-1, July 20108 - 27


Now, Check Network Availability.....135.111.86.10 is aliveData is ready, It was created at:Jan 25 02:20

The Switch SU Level is: A 0929842844 5e14(1)02,00 BWM99-0012Do you wish to continue[Default is Y]



We are going to get CNI and ODD data, please wait...Remote copy CHCGILFRDS0.tar...The size of CHCGILFRDS0.tar on ASM is 2837778.Remote copy may take a few minutes......Received data file size is 2837778.Remote copy succeeded!

Are you sure to load full views?(Y or N) [Default:Y]



#### 2000-08-31 09:34 Begin load full views... ######### 2000-08-31 09:34 End load, a ofrlist created now #####Start data conversion, this may take two hours, please be patient...

BEGIN:offswofr:2000-08-31:09:34:25/osw/prog/5e14_1/BWM99-0015/pag/sparcsol/offswofr-o /osw/data01/CHCGILFRDS0-m /osw/prog/5e14_1/BWM99-0015/mask-i /osw/data01/CHCGILFRDS0/etc/ofrlist-d /osw/data01/CHCGILFRDS0/etc/oddfile-l /osw/data01/CHCGILFRDS0/Log-e /osw/prog/5e14_1/BWM99-0015/rc-creal 0m34.06suser 0m3.40ssys 0m15.22sSTART:5051:10.38START:5107:18.111999-10-25 12:45:36 Conversion Complete...........Data from asm read successfullyPress RETURN to go back to MENU

4. At this point, Data conversion from Binary ODD data to OFR data has completed. With the OFR data, you will be ready to load the data into the system database.

— press <Return> to go to Read Switch Data Menu.


Issue: GA-1, July 20108 - 2 8


Tape: DMS Dump & Load ProcessTo complete the entire tape based 5ESS switch dump & load process, the following high-level steps must be completed.

Step 1: Tape: Create Dump List (DMS)

Step 2: Tape: Generate Dump Script (DMS)

Step 3: Tape: Switch data dump (DMS)

Step 4: Tape: Read Switch Data (DMS)


Tape: Create Dump List (DMS)The DumpScript must be created on tape drives that the switch and VAM HP server supports. (typically 4mm DAT tape). After the tape is created, it must be shipped to the appropriate switch site along with the DMS Tape based Dump & Load procedures available on the 8950 VAM Download website.

! CAUTION:It is the responsibility of the customer to ensure that the tape device on the switch site and 8950 VAM HP server’s tape device are compatible and that compatible media is used. (Ex: DDS-1, DDS-2, etc.)

Prior to starting this procedure you must have the following:• The 11-Character Switch CLLI name and the Switch RELEASE #.• One set of blank tapes with the following labels: (up to 4 Dat tapes total). It is highly

recommended to send two sets of tapes to switch site.— 8950 VAM Dump Script: <11 Character Switch CLLI Name> (2 copies)

— DUMPTAB Tape1: <11 Character Switch CLLI Name>

— DUMPTAB Tape2: <11 Character Switch CLLI Name> (If applicable)

NOTE:Some offices may NOT requires up to 2 DUMPTAB tapes. It is also highly recommended that you ship 2 sets of each media to avoid any physical tape issues and/or read errors.

• Shipping details for shipping the Dump Script tape & the blank DUMPTAB tapes.

Issue: GA-1, July 20108 - 29





[xxxxx-int] menu

















Issue: GA-1, July 20108 - 3 0


Tape: Generate Dump Script (DMS):1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 4) Write Tape to be Shipped to the Switch







Hostclli TESTDMSSN09 Release Selection1) alcatelSN092) EXITEnter the number of the switch release:


Switch: NRBSN09VSOS Release: teleportSN09 Generic: SN09 Do you want to create a script tape for this generic? [Default:Y]

• Input Y and press <Enter>

4. Answer the following prompts for the tape selection options.


Issue: GA-1, July 20108 - 31



5. Perform the following steps to write data to tape applicable to your environment:






Making a DMS tape . . . . .. . . . .. . . . .Completed DMS tape writing.







Making a DMS tape . . . . .. . . . .. . . . .Completed DMS tape writing.






Issue: GA-1, July 20108 - 3 2


6. At this point, remove the Dump Script tape from the tape drive and ship the tape(s) to appropriate folks at the switch site.

• The Script tape is now created. You may wish to re-run the steps again to create a secondcopy of the script tape.

Issue: GA-1, July 20108 - 33


Tape: Switch data dump (DMS):• The switch administrators will perform the required dump of the switch data and ship back the

data to the VAM administrators for loading to the VAM database. The switch data tapes will consist of a one or more DUMPTAB data tape(s).

• This process will occur directly at the DMS switch location once the switch technician receives the Dump & Load scripts from the 8950 VAM administrators.

• Detailed steps by step procedures are available on the ALU LED download site in the document: “DMS_OFFICE_TAPE_DUMP_PROCEDURES”. You must have this document to complete the switch dump.

• Once switch dump has been completed, the tapes can be shipped back to the 8950 VAM HP server location.

Issue: GA-1, July 20108 - 3 4


Tape: Read Switch Data (DMS)This step is the third of four steps involved in the complete Switch Database Load Procedure. In this step, (1 or more DUMPTAB tapes) were generated at the switch site by the switch administrators and sent back directly to the 8950 VAM HP Server Administrator.

The tape(s) (DUMPTAB ) will be read into 8950 VAM HP server and converted to switch database load records to be loaded into the 8950 VAM database.

The following are prerequisites to starting this procedure:• 1 or more DUMPTAB data tapes should have arrived from the switch. • The 11-Character CLLI code and Switch RELEASE # of the switch is required. (Obtained

from the 8950 VAM System Administrator. The same information used to generate the Dump Script tape.).

• The Recent Change and Echo Back links should be operational to the switch.


• Mount in order the 1st “DUMPTAB” data tape in the appropriate system drive.1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu




— 3) Read 5ESS ODD/OFR Tape Or DMS Tape







Hostclli TESTDMSSN09 Release Selection

Issue: GA-1, July 20108 - 35


1) alcatelSN092) EXITEnter the number of the switch release:











• Type “Y” and press <Enter>


Load data from tape.... . .. . .. . .Data from tape read successfully.... Press RETURN to go back to MENU





Issue: GA-1, July 20108 - 3 6





Load data from tape.... . .. . .. . .Data from tape read successfully.... Press RETURN to go back to MENU





5. At this point, you are ready to load the data into the 8950 VAM database.

— Remove all the data tapes from the system.

— Press <Return> to go to Read Switch Data Menu.


Issue: GA-1, July 20108 - 37


Network (SDM) : DMS Dump & Load ProcessTo complete the entire network based DMS switch dump & load process via SDM, the following high-level steps must be completed.

Step 1: Network (SDM): Create Dump List (DMS)

Step 2: Network (SDM): Generate Dump Script (DMS)

Step 3: Network (SDM): Switch data dump (DMS)

Step 4: Network (SDM): Read Switch Data (DMS)


Network(SDM) : Create Dump List (DMS)Network Based Dump & Load eliminates the use of tapes in the dump & load process and utilizes the TCP/IP connection between the DMS switch and the 8950 VAM HP Server. One option is to use the “Nortel Supernode Data Manger (SDM” network method to complete the DMS Dump & Load.

• The Nortel SuperNode Data Manager (SDM) allows for Table Editor/SERVORD connectivity via TCP/IP between the Nortel DMS family of switches and 8950 VAM. In order for 8950 VAM to be able to communicate with the DMS family of switches via this new interface, appropriate software changes are required on both sides (8950 VAM System & DMS switch).

— Refer to the appropriate technical support teams of the product for details.

The high level process to complete this Dump & Load is the same, but the steps are different as documented in this section.

Feature Requirements:

The following two features must be enabled in the 8950 VAM system:• DMS DUMP AND LOAD VIA SDM (Must be purchased)

• TCP/IP TO NORTEL SDM (Must be purchased)

• An RC link must be established between the 8950 VAM HP Server and the DMS switch.

Prior to starting this procedure you must have the following:• The 11-Character Switch CLLI name and the Switch RELEASE #.

Issue: GA-1, July 20108 - 3 8





[xxxxx-int] menu

















Issue: GA-1, July 20108 - 39


Network (SDM): Generate Dump Script (DMS)In this process the dump script data script (cvuatp_dump_start & cvuatp_ddu) are sent via FTP to the SDM system.




[xxxxx-int] menu




— 7) Create SDM-DMS dump script for Disk based Dump and Load







Enter disk volume on switch to store the table files:

• Type the DMS disk volume name (place in DMS for temp data storage) and press <Enter>.The disk volume info can be obtained from the DMS switch technician .

Enter login to be used during FTP:

• Type the user login of the SDM system and press <Enter>.

Enter password: Re-enter password:

• Type the password (twice) and press <Enter>.

Enter the destination directory name on SDM:~sdm1/

• Type data directory location on SDM system and press <Enter>.

Issue: GA-1, July 20108 - 4 0



Information Entered is:

HOSTCLLI: TESTDMSSN09Switch Generic: SN09 DMS Disk Volume: sfdevLogin: sdm1Destination Directory: ~sdm1/tmp

Do you want to continue ( Y/N )? [Default N]:

• If all information is correct: Type “Y” and press <Enter>.

• If all information is incorrect: Type “N” and press <Enter>.

Have you run menu 8,2 to update DumpList for full dump? [ Default Y ]


Remove existing files from SDM in FTP Directory? [Default:Y]



Making a DMS tape Creating FTP based DMS dump scripts...Dump scripts for TESTDMSSN09 successfully createdunder sfdev volume on switch


Issue: GA-1, July 20108 - 41


Network (SDM): Switch data dump (DMS)The purpose of this section is to provide information about executing Dump Script for DMS switch. Contact the person who has access to the DMS switch (normally the Switch Technician) in order to execute the following procedure. This is equivalent to the switch technician making a Dump tape.

When the Dump Script command finishes "gathering" the table files, all the DMS table files will be on the DMS switch under the specified disk volume. Depending on how the switch was configured on the 8950 VAM system, one of these will occur:

• If PASS-THROUGH=N, the table files are automatically ftp'd over from the DMS switch to the SDM box's destination directory.

• If PASS-THROUGH=Y, the table files are NOT copied to the SDM box, they remain in the DMS switch.

The name of the two Dump Scripts are cvuatp_dump_start and cvuatp_ddu.• The cvuatp_dump_start script is a wrapper script which invokes the cvuatp_ddu script.

Prerequisites:

• Before running the script, the switch technician/administrator MUST verify that there is enough disk space available on the DMS switch in the specified disk volume.

• For executing the following procedure, contact the person having “admin level” access to the DMS switch (normally, the Switch Technician). This is equivalent to the DMS Technician making the DUMPTAB tape.

1. Log into the DMS switch console.

2. Run the following script from the “CI:” prompt, in the DMS switch to extract the switch data.

CI: > read CVUATP_DUMP_START


2003/06/23 09:21 WNVLILAADS5 NCS15/XPM15/SPM16 -- XAC 5/6/02CI:DRCI:2003/06/23 09:21 WNVLILAADS5 NCS15/XPM15/SPM16 -- XAC 5/6/02----------------------------------------------------------------EMPTY TABLEReturn code is: 3012003/06/23 09:21 WNVLILAADS5 NCS15/XPM15/SPM16 -- XAC 5/6/02DRCI:8950 VAM/CONNECTVU DISK DUMP COMPLETECI:

NOTE:The switch technician must verify the output for switch errors.

Issue: GA-1, July 20108 - 4 2


Network (SDM): Read Switch Data (DMS)In this step, the data from the DMS switch will be FTP’d from DMS switch into the 8950 VAM HP Server into the /rc/odd_load/<CLLI> directory.

Depending on how the switch was configured on the 8950 VAM system, one of the following will occur:

• If PASS-THROUGH=N, the 8950 VAM server will go to the SDM box and ftp the table files from the SDM box .

• If PASS-THROUGH=Y, the 8950 VAM server will go to the DMS switch (via SDM) and ftp the table files from the DMS.





[xxxxx-int] menu




— 8) Read DMS Data from Network via SDM3. Answer the following prompts accordingly:






Hostclli TESTDMSSN09 Release Selection1) alcatelSN092) EXIT

Issue: GA-1, July 20108 - 43


Enter the number of the switch release:



Getting the dumped files from the switch. Depending on the network speed, this may take some time.Please wait for a success or a failure message ..... . .. . .. . .Data from tape read successfully.... Press RETURN to go back to MENU

NOTE:At this point, all the data is FTP onto the /rc/odd_load/<CLL> directory in the 8950 VAM server.




Issue: GA-1, July 20108 - 4 4


Network (RC Link) : DMS Dump & Load ProcessThe purpose of this section is to provide information about DMS Network-Based Dump and Load via RC Link for 8950 VAM.

• Due to limited bandwidth on the RC channel, however, this feature is intended for partial dump and load only, and is not intended to replace the existing tape-based procedure for the full DMS table dump.

Feature Requirements:

The following two features must be enabled in the 8950 VAM system:• DMS DUMP AND LOAD VIA FTP (Must be purchased)

• NETWORK BASED DUMP AND LOAD - DMS (Must be purchased)

• An RC link must be established between the 8950 VAM HP Server and the DMS switch.

To complete the entire network based DMS switch dump & load process via SDM, the following high-level steps must be completed.

Step 1: Network (RC Link): Create Dump List (DMS)

Step 2: Network (RC Link): Read Switch Data (DMS)


Issue: GA-1, July 20108 - 45


Network (RC Link) : Create Dump List (DMS)Prior to starting this procedure you must have the following:

• The 11-Character Switch CLLI name and the Switch RELEASE #.1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu

















Issue: GA-1, July 20108 - 4 6


Network (RC Link): Read Switch Data (DMS)In this step, the data from the DMS switch will be extracted from DMS switch into the 8950 VAM HP Server into the /rc/odd_load/<CLLI> directory via RC Link.




[xxxxx-int] menu




— 5) Read DMS Data From Network via RC-LINK







Hostclli TESTDMSSN09 Release Selection1) alcatelSN092) EXITEnter the number of the switch release:


WARNING: Don't continue during RC link heavy traffic time!Do you want to continue ( Y/N )? [Default N]:

• Type “y” and press <Enter>.

There are some tables dumped before but not loaded into database yet!Do you want to re-dump them( Y/N)? [Default: Y]:


WARNING: The DumpList contains some large tables listed as following:'DNINV' It may take a long time to dump these tables.Do you want to continue( Y/N )? [Default N]:

Issue: GA-1, July 20108 - 47




Verify RC link status......Ok!

#### 2009-01-19 13:32:36 BEGIN TO DUMP TABLES (Total 1) ####--- Processing 'DNINV' (1 / 1) ---Sending 'DUMP_TABLE DNINV' request......Ok!.......Checking the integrity of table DNINV......Ok!'DNINV' read into directory '/rc/odd_load/DUMPTSTSN09 '#### 2009-01-19 13:32:54 END DUMP TABLES ####Tables dumping complete.





Issue: GA-1, July 20108 - 4 8


Loading Data to DatabaseThis section provides information about loading the data into the database in 8950 VAM. This process is the same for DMS & 5ESS switches and/or tape or network based methods.

• It is strongly recommended that the load of the data to the database should be performed during a quiet period in the system to avoid any failures.

! WARNING:You must run the loading of the switch data from the CONSOLE of the HP Server. If you do NOT run this from the CONSOLE, then you may run into failure issues for any time-out and/or dropped connections.



2. Access the ODD LOAD Follow-UP Menu as follows:

[xxxxx-int] menu



— 4) Load Data to Database








2009-06-03-11:41:27 Found 232 Views to Process11:41:27 Checking 1 of 232: 1.1111:41:27 Checking 2 of 232: 1.2211:41:27 Checking 3 of 232: 1.3711:41:27 Checking 4 of 232: 1.4511:41:27 Checking 5 of 232: 1.5. . . . . .. . . . . .. . . . . .11:42:10 Checking 230 of 232: 9.711:42:10 Checking 231 of 232: 9.8

Issue: GA-1, July 20108 - 49


11:42:10 Checking 232 of 232: 9.9You can query the Load process by Switch Database Load Monitoring menu.Press RETURN to go back to MENU

4. At this point, the system will load the data into the database.



NOTE:It is recommended to use the “Switch Database Load Monitoring menu” to monitor the progress of the switch load.

Issue: GA-1, July 20108 - 5 0


Monitoring Dump & Load The purpose of this section is to provide information about monitoring the state of the data during the loading process.

• The following steps are optional. They are used to monitor operations during the loading process.

• Follow these steps to monitor the state of the views during the loading process:1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu



— 5) Switch Database Load Monitoring


Hostclli Selection1) 5E16TESTCLL 2) ATTARCLLI113) EXIT




ODD LOAD FOLLOW-UP

SWITCH CLLI: DUMPTSTSN09 RELEASE: ALLSN09 DIRECTORY : /rc/odd_load/DUMPTSTSN09 STATE STATE VIEW PROGRAM STATE DATE TIME COMMENT -------- ---------- ------- -------- -------- -----------------------

To abort any operation, hit <DEL>, use CONTROL-N & CONTROL-P to page-------------------------------------------------------------------------Options: Query Run Update Clli States ExitQuery for load info based on Switch CLLI and Release

Issue: GA-1, July 20108 - 51


4. From the ODD Load Follow-UP Screen you can perform the following queries, updates, etc.

— Use the <SPACE> or <ARROW> keys to highlight the Query option and press <Enter>. You can Query on any view and/or press <Esc> key to query all views.

— STATE field has following options:

• CPD = Complete state

• ERROR = Failed state

• RDY = Ready for load into system. Load will only occur when state is in “RDY” state.

— Options to Query on:

• != means NOT equal to

• <> means NOT equal to

• = means equal to

— <Esc> key means to commit; <Del> key means to kill/interrupt.

5. The following operations can be performed after D&L process has completed:

• For any data that failed to load, you can use the “Update” option and change the status to“RDY” state and then use the “Run” option to re-load the data.

NOTE:Do NOT forget to run “TNM/SYNC option to sync the data missing from the time the D&L occurred in the switch to the time the data actually loaded into the 8950 VAM database.

Issue: GA-1, July 20108 - 5 2


Dump & Load Monitoring via StatesThe purpose of this section is to provide information about monitoring the states of the data during the loading process.

• Follow these steps to monitor the states of the views during the loading process:1. Log in as int from either the console or a PC via telnet into the L1 machine:



[xxxxx-int] menu



— 5) Switch Database Load Monitoring


Hostclli Selection1) 5E16TESTCLL 2) ATTARCLLI113) EXIT




ODD LOAD FOLLOW-UP

SWITCH CLLI: DUMPTSTSN09 RELEASE: ALLSN09 DIRECTORY : /rc/odd_load/DUMPTSTSN09 STATE STATE VIEW PROGRAM STATE DATE TIME COMMENT -------- ---------- ------- -------- -------- -----------------------

To abort any operation, hit <DEL>, use CONTROL-N & CONTROL-P to page-------------------------------------------------------------------------Options: Query Run Update Clli States ExitQuery for load info based on Switch CLLI and Release

Issue: GA-1, July 20108 - 53


4. Use the <SPACE> or <ARROW> keys to highlight the States option and press <Enter>. .

NOTE:You will see a list of the views that are being processes for Loading into the data and then after some time, the “ODD LOAD STATES” screen will appear.

• 8950 VAM will now process the switch dump data. This process is monitored continuously by the system. The window is refreshed every two (2) minutes.

— To view current state, select Refresh Option.

• During the LOAD process, views are in the RDY state and then go to either CPD or ERROR state.

NOTE:If you “lose” the ODD Load States (Percent) Screen, repeat the steps at the beginning of this procedure (Load Data To Database), but this time choose States option, instead of Run option.

It is not necessary to wait in front of the console for the completion of the process. However, ensure that ALL views are processed. ALL views must be in CPD state before continuing with the reconnect and synchronization steps.

ODD LOAD STATES

SWITCH CLLI : DUMPTSTSN09 RELEASE : ALLSN09 DIRECTORY : /rc/odd_load/DUMPTSTSN09

---------------------------------- +------------------------------+ | View # (Load Error) : | View States Number Percent | | | DNINV | TOTAL 1 [100%] | | RDY 0 [0%] | | QUEUED 0 [0%] | | NLDMAIN 0 [0%] | | LOAD 0 [0%] | | OTHER 0 [0%] | | WARNING 0 [0%] | | ERROR 1 [100%] | | CPD 0 [0%] | | | | ----------------------------------- +------------------------------+ Options: querybyState querybyView Refresh Exit Query for load info based on state

Issue: GA-1, July 20108 - 5 4


Switch Database Sync (Surveillance System)The purpose of this section is to provide information about Switch Database Synchronization between Surveillance systems (TNM, NMA, SCCS,etc) and 8950 VAM. There are cases when data from switch and 8950 VAM system may not be fully sync, this method helps in reducing the out-of-sync conditions.

Example out-of-sync condition:• EB Link is DOWN and changes are made directly into the switch. • D&L method via Tapes; in this method the data can be extracted on Day 1 & loaded into the

system on Day 3. The changes in switch for Day 2 is lost.

To alleviate this condition, 8950 VAM has the capability to sync the data via (RCV Success) messages collected in the switch surveillance systems. This data must be sent over to 8950 VAM system daily. 8950 VAM will process this data daily via a cron mechanism. There are two methods to sync the data:

• Manual Sync (Menu option): This option is completed via the menu utility document below. This option should be used after a successful load of a switch. This option can also be used to sync the last 30 days of data into the VAM system.

— This is accomplished via the menu utility and will process data up to 30 days for a specified switch.

— After an initial switch load - to synchronize data from the time an office dump is generated, to the time the data is loaded onto 8950 VAM. The manual re-synchronization operation must be initiated the day after the LOAD process has been completed.

— After a switch generic upgrade - to synchronize data from the time an office dump is generated, to the time the data is loaded onto 8950 VAM. The manual re-synchronization operation must be initiated the day after the LOAD process has been completed.

— When there is a failure to maintain database synchronization for a given switch.

• Auto Sync (cron) : This option will perform a sync on a daily basis via a cron from the 8950 VAM HP server. This method required configuration and setup with assistance of 8950 VAM product support team. It required certain requirements from customer side as well. Please consult the 8950 VAM product support team for further details.

— Normally this process is automatically run for all switches on a daily basis via the UNIX “cron” (at 6 AM for DMS and 7 AM for 5E). This process will synchronize data received from TNM/NMA/SCCS for the previous day only.

Issue: GA-1, July 20108 - 55


Manual Sync via MenuThe purpose of this section is to provide information about working with the Use TNM/SCCS Data to Synchronize Database menu option in 8950 VAM.




[xxxxx-int] menu



— 6) Use TNM/SCCS Data to Synchronize Database






Enter date the switch dump was put on tape (default:12/21/2008):

• Type the sync start date “<mm/dd/yyyy>” and press <Enter>.

NOTE:You may want to go back 2-3 days back to sync data after a dump & load.


Verifying if ManualVerify order needs to be created, please stand by...Check RC-Summary screen for MV<mmddyyyy> order and user-id of INTPress RETURN to go back to MENU

4. Exit the menu options.

— Press <Return> to go to Switch Database Load Menu.


5. Monitor the TNM sync process via the following:

— Unix command: ps -ef | grep “ECHO_BACK ECHOb”

— Log file: /rc/data/ECHOb.<MMDDYY>

— Check order status: Use the “Translation GUI & check from ORDER Summary Screen”

Issue: GA-1, July 20108 - 5 6


Removing OFR data filesThe purpose of this section is to provide information about removing OFR data files in 8950 VAM. After the switch data has been successfully loaded and any data load errors have been cleared up, the switch data should be removed from the 8950 VAM file systems.

• This will help prevent File System Full errors in the /rc file system of the HP Server, and the /osw file system of the OSW machine. Most importantly, it will eliminate confusion about logistics the next time the same switch is read and loaded.

• If using the ASM network-based method, the switch data tar files will also need to be removed from the ASM machine.




[xxxxx-int] menu



— 7) Remove Successful OFR Load Data Files








Please wait, removing OFR load data files for TEST5E16FR5.Press RETURN to go back to MENU

4. Exit the menu options.

— Press <Return> to go to Switch Database Load Menu.


Issue: GA-1, July 20108 - 57


switch Data Transfer (SDT) MigrationThe purpose of this section is to provide information about switch data migration planning in 8950 VAM where you have multiple HP servers.

! WARNING:The Switch Data Migration tool is provided as is ; Customers are responsible for any problems associated with this tool/utility. All issues with this tool will be considered as a billable/enhanced services work.

NOTE:Alcatel-Lucent 8950 VAM product team does offer a complete SDT migration solution as an enhanced services. Please contact the 8950 VAM product team for further details.

Each HP Server contains switch databases, communication link information for each switch and information files about the TNM/NFM or NMA system serving the switches. As new HP Servers are added to the network, there may be a need to move some of the switch databases from one HP Server to another.

• Moves may be triggered by the need to balance switch loads across HP Servers, or to accomplish other geographical efficiencies.

! CAUTION:For systems using the Automated Code Opening (ACO) feature, additional steps are required on the Source HP Server before the migration and on the Target HP Server after the migration

The switch data transfer migration tool consists of three options used to migration/move the switch from one HP server (source machine) to the new HP server (target machine). The following three options are provided:

• Option 1: Save option: This options allows the admin to extract the data from the source system database and save onto local file system on the source HP server. Once the data is saved, you may transfer the data via network or tape to the target HP server.

• Option 2: Install option: This options allows the admin to install the data into the new HP server (targer HP server) after the data has been extracted from the old HP server (source HP server).

• Option 3: Delete option: This options allows the admin to delete the data from the source system database after all the data migration has been completed.

Prerequisite for Switch Migration• Identify the HP Servers involved in the migration. The HP Server currently containing the

switch database is designated as the Source HP Server and the HP Server that will contain the database after the migration is designated as the Target HP Server.

Issue: GA-1, July 20108 - 5 8


• Identify the routing information from the Target HP Server to each switch involved in the migration.

• Identify the TNM/NFM or NMA systems serving each switch involved in the migration.• Identify the routing information between each TNM/NFM or NMA system and each Target HP

Server involved in the migration.• Schedule the migration and confirm availability of appropriate personnel.• Notify affected users that access to the affected HP Servers will be interrupted until the

migration is complete.• Notify the users when migration is complete and office access is enabled.• Ensure the back-up of all of the involved HP Servers.• Complete system backups on all machines involved in the migration.• Ensure that a communication path exists between the new Target HP Server and their

Workstations and between the new Target HP Server and the migrating switch.• Ensure TCP/IP or UUCP communication links between each affected TNM/NFM Server and

the new Target HP Server.• Ensure that the appropriate TNM/NFM systems are set up to transmit the office data for each of

their migrating switches to the new Target HP Server in addition to the continued transmission of that data to the Source HP Server. The dual transmission of data files is an interim measure only. After migration testing, the TNM/NFM system reverts to single transmissions to the new HP Server.

After Migration, customers should verify that the HP Server system is responding correctly and that migrated switching systems are operational on the new Target HP Server.

SDT tool warning/error messages

Warning/Message Explanation

WARNING: This machine is an (ATP_TGUI) machine, switch <Switch Name> cannot be migrated to a Non (ATP_GUI) machine. Verify that your target machine is of the same architecture.

For the SDT Save option, sdt checks the /.MACH file on the server to determine the server configuration.

Is <Switch Name> being migrated between servers in the same TTK cluster? (y/n):

Is the CLLI being moved between centrals in a cross central environment?

ACO is in progress for switch <Switch Name>, do you wish to continue?

The switch that the administrator is attempting to perform SDT on has Automated Code Opening active.

Issue: GA-1, July 20108 - 59


No ACOs in progress for switch <Switch Name>-press RETURN to continue.

The switch that the Administrator is attempting to run SDT on does not have Automated Code Opening active.

Switch <Switch Name> links must be down before SDT can continue, do you wish to take the links down?

For SDT Save option, the SWCOM and MICOM links are turned down if Y is entered.

There are n DB updates in progress for switch <Switch Name>, do you wish to wait for their completion?

SDT checks for orders in the switch in the DBUPD queue and gives the number. It checks every minute and repeats the message until no updates are in progress

No DB updates in progress for switch <Switch Name> press RETURN to continue.

SDT checks for orders in the switch in the DBUPD queue and gives the number. If none are in progress, it continues.

SDT has completed successfully. Table results can be found in /rc/data/SDT <Clli Name>.trc

SDT has finished loading or unloading all of the tables for an SDT switch and has detected no internal table failures. This applies to both the save (Source) and insert (Target) options.

SDT has FAILED-Table unload results can be found in /rc/data/SDT<Clli Name>.trc

NOTE: SDT is incomplete and should NOT be migrated to the target server until SDT has run successfully.

Failed to save XXXX data for the following tables: <Table Name(s)>

Do you want to retry the tables that were unsuccessful?

For both the SDT save (Source) or insert (Target) option, the internal tables list is NOT empty, indicating an internal table failure. If you answer yes to the retry prompt, it causes SDT to retry the failed tables. If you answer No, it causes SDT to abort at that point.

Warning/Message Explanation

Issue: GA-1, July 20108 - 6 0


Switch Data Transfer (SDT) - SaveThe switch data transfer migration tool consists of three options used to migration/move the switch from one HP server (source machine) to the new HP server (target machine). The following section details the information on the option to save the data:

• Option 1: Save option: This options allows the admin to extract the data from the source system database and save onto local file system on the source HP server. Once the data is saved, you may transfer the data via network or tape to the target HP server.


1. Log in as int from either the console or a PC via telnet into the Live (L1) source HP Server machine:



[xxx-int] sdt


1) 5E16TESTCLL 16) DLLSTX37DC0 31) PEACHACOSW1 2) ALBQNMMADC2 17) ELTRCA11DS0 32) PEACHACOSW2 3) ALBQNMNEDC0 18) FRSNCA01DS0 33) PHLAPAFGDSE 4) ALBQNMNESTU 19) GNBPNCEMDS0 34) PRCMFL03DS1 5) ALBQNMSHDC0 20) JCVLFLWFDC0 35) RDMDWASYDS1 6) APRILPATCH5 21) LSVKNV99DC0 36) SFOYPQ0100T 7) ASWITCH5E14 22) LSVLKY27DS0 37) STCGPADNDS0 8) ASWITCH5E15 23) MMPKTNLMDS1 38) TEST5E16FR5 9) ASWITCHSN05 24) MNTRLBEFORE 39) TESTDMSSN0710) ATTARCLLI11 25) MTRL122TEST 40) TESTDUMPLOA11) ATTCORE5E16 26) MTRL130TEST 41) TESTMRJAVAA12) CHMBGADGDS0 27) MTRLPQQQ00T 42) TULSOK35DC013) CHRXNCRXDS0 28) MTRLTESTFNL 43) WLANCA01DS014) CLMBOH1165T 29) NIRMALYSN09 44) WNVLILACDS115) CLSPCO11DC0 30) NRB5E16FR5N 45) EXIT


— From the list of switches, input the number of the switch to save.

Enter Switch Data Transfer type (s=save, d=delete, i=install): s

— Input value of s for the save option.

Enter directory to store switch data (default /tmp/5E16TESTCLL):

— Input the <Full_Path_DirName> to save the data.

Log file for this SDT is: /rc/data/SDT5E16TESTCLL.trc

Issue: GA-1, July 20108 - 61


WARNING: This machine is a ATP_TGUI machine, switch 5E16TESTCLL cannot be migrated to a Non ATP_TGUI machine. Verify that your target machine is of the same architecture. Do you want to continue? (y/n): y

— If you’re moving data within same VAM architecrute, input y and press <CR>.

Is switch 5E16TESTCLL being migrated between servers in the same TTK cluster? (y/n): y

— If you’re moving the data into a X-central environment, input y and press <CR>.

— If you’re moving the data into a NON-X-central environment, input n and press <CR>.

Saving 5E16TESTCLL data from table aco_gen_queue.2009/04/16 09:44:19 Number of records stored for table aco_gen_queue=02009/04/16 09:44:19 Number of records unloaded for table aco_gen_queue=0

No ACOs in progress for switch 5E16TESTCLL - press RETURN to continue

— To continue, press <CR>.

Loading 5E16TESTCLL data from table firewall.2009/04/16 09:44:22 Number of records to load for table firewall=132009/04/16 09:44:22 Number of records loaded for table firewall=13

No DB updates in progress for switch 5E16TESTCLL - press RETURN to continue

— To continue, press <CR>.


• A scrolling list of database tables being saved will be displayed.Saving 5E16TESTCLL data from table aco_disp.2009/04/16 09:45:25 Number of records stored for table aco_disp=02009/04/16 09:45:25 Number of records unloaded for table aco_disp=0

Saving 5E16TESTCLL data from table aco_dms_clsvscrc.2009/04/16 09:45:25 Number of records stored for table aco_dms_clsvscrc=02009/04/16 09:45:25 Number of records unloaded for table aco_dms_clsvscrc=0

......................................................

......................................................

......................................................Saving 5E16TESTCLL data from table sref_sched_fid.2009/04/16 09:48:06 Number of records stored for table sref_sched_fid=02009/04/16 09:48:06 Number of records unloaded for table sref_sched_fid=0

SDT has completed successfullyTable unload results can be found in /rc/data/SDT5E16TESTCLL.trc

4. Answer the following prompts accordingly to transfer data to new (target) HP server.

1) Electronically transfer (rcp) 5E16TESTCLL data to remote machine.2) Write 5E16TESTCLL data to tape.3) EXITSelection: 1

Issue: GA-1, July 20108 - 6 2


— To transer data via network (rcp), input 1 and press <CR>.

— To transer data via tape (rcp), input 2 and press <CR>.

4.1 If you chose the network option, then answer the following information.

Enter remote machine name: <Target_HP_Server>

— Input the <Target_HP_server_Name> and press <CR>.

Transfering data files from /tmp/5E16TESTCLL to merlin. Please wait.Transfering data files from /rc/odd_load/5E16TESTCLL to merlin. Please wait.Transfering data files from /rc/tnm to merlin. Please wait.Transfering data files from /var/spool/uucppublic/tnm to merlin. Please wait.

4.2 If you chose the tape option, then answer the following information.

The following drives type(s) 9-TRACK DAT DLT ON peach are available:1) d002) d013) quitSelect the number corresponding to the Tape Drive you wish to use:

— Input the <Tape_Device_Number> and press <CR>.

<CLLI> data successfully written to tape.

Issue: GA-1, July 20108 - 63


Switch Data Transfer (SDT) - InstallThe switch data transfer migration tool consists of three options used to migration/move the switch from one HP server (source machine) to the new HP server (target machine). The following section details the information on the option to save the data:

• Option 2: Install option: This options allows the admin to install the data into the new HP server (targer HP server) after the data has been extracted from the old HP server (source HP server).





[xxx-int] sdt





Enter Switch Data Transfer type (s=save, d=delete, i=install): i

— Input value of i for the save option.

1) Install 5E16TESTCLL data from the file system.2) Read 5E16TESTCLL data from tape.3) EXITSelection: 2

— To install data via network (rcp), input 1 and press <CR>.

— To install data via tape (rcp), input 2 and press <CR>.

Issue: GA-1, July 20108 - 6 4


3.1 If you chose the network option, then answer the following information.

Enter directory which contains switch data (default /tmp/5E16TESTCLL):

— Input the <Directory_Name> and press <CR>.

3.2 If you chose the tape option, then answer the following information.


— Input the <Tape_Device_Number> and press <CR>.

Enter directory to hold data from tape (default /tmp/5E16TESTCLL):

— Input the <Directory_Name> and press <CR>.


• A scrolling list of database tables being saved will be displayed.No 5E16TESTCLL data for table aco_disp.No 5E16TESTCLL data for table aco_dms_clsvscrc.No 5E16TESTCLL data for table aco_dms_lata.No 5E16TESTCLL data for table aco_dms_lcascr.No 5E16TESTCLL data for table aco_dms_mumr.No 5E16TESTCLL data for table aco_dms_ratetype.No 5E16TESTCLL data for table aco_dms_stdprt.No 5E16TESTCLL data for table aco_home_npa.No 5E16TESTCLL data for table aco_sched...................................................................................................................................................................No 5E16TESTCLL data for table userorder.No 5E16TESTCLL data for table edited_rc.

SDT has completed successfullyTable insert results can be found in /rc/data/SDT5E16TESTCLL.trc5E16TESTCLL data for all tables successfully installed.

4. Answer the following prompt to delete the dirctory..

Do you want to remove directory /tmp/5E16TESTCLL? y

— Input y and press <CR>.

Issue: GA-1, July 20108 - 65


Switch Data Transfer (SDT) - DeleteThe switch data transfer migration tool consists of three options used to migration/move the switch from one HP server (source machine) to the new HP server (target machine). The following section details the information on the option to save the data:

• Option 3: Delete option: This options allows the admin to delete the data from the source system database after all the data migration has been completed.





[xxx-int] sdt





Enter Switch Data Transfer type (s=save, d=delete, i=install): s

— Input value of s for the save option.

Database tables will be locked during delete. OK to continue? (y/n)y

— To continue, input y and press <CR>.

OK to delete data for 5E16TESTCLL? (y/n)y

— To continue, input y and press <CR>.


Log file for this SDT is: /rc/data/SDT5E16TESTCLL.trc

Issue: GA-1, July 20108 - 6 6


Deleting 5E16TESTCLL data from table aco_disp.2009/04/16 10:34:27 Number of records deleted from table aco_disp=0

Deleting 5E16TESTCLL data from table aco_dms_clsvscrc.2009/04/16 10:34:28 Number of records deleted from table aco_dms_clsvscrc=0

Deleting 5E16TESTCLL data from table aco_dms_lata.2009/04/16 10:34:29 Number of records deleted from table aco_dms_lata=0

Deleting 5E16TESTCLL data from table aco_dms_lcascr.2009/04/16 10:34:30 Number of records deleted from table aco_dms_lcascr=0

Deleting 5E16TESTCLL data from table aco_dms_mumr.2009/04/16 10:34:32 Number of records deleted from table aco_dms_mumr=0

......................................................

......................................................

......................................................Deleting 5E16TESTCLL data from table sub_rc_action.2009/04/16 10:42:00 Number of records deleted from table sub_rc_action=0

Deleting 5E16TESTCLL data from table(s) requestaction requestitem configurationreq.2009/04/16 10:42:01 Records from table(s) requestaction requestitem configurationreq were deleted successfully

SDT has completed successfullyTable delete results can be found in /rc/data/SDT5E16TESTCLL.trcDeleting /rc/odd_load/5E16TESTCLL files.Removing SCCS/TNM data.Remove 5E16TESTCLL from Switch Administration menu.

4. To completely remove the switch from the system, you must delete the switch information from the system. Refer to the switch administration for full details on how to remove a switch from the system.



9 VAM Feature Configuration

Overview

The purpose of this chapter is to provide information about 8950 VAM Feature configuration. The following topics will be covered

• 5ESS ASM Feature Management

• DMS SDM D&L Management

• SSH Management

• Proactive Monitoring Management

• Password Ageing Feature Management

• Auto-Code Opening Feature Management

• Cross Central Management



5E-ASM Network-Based D&L The purpose of this section is to provide information about configuring 5E-ASM Network-Based Dump and Load.

VAM HP System Activities1. Log in as int from either the console or a PC via telnet into the L1 machine:




— 9) Remove Old Error Files

— 12) 8950 VAM Feature Control Menu

— 2) Enable Features

• Enable Feature Name: “NETWORK BASED DUMP AND LOAD - 5ESS”2. Update the Switch CLLI definitions to reflect the ASM system information.

• ASM MACHINE, ASM LOGIN, RC LINK INTF= IP_ASM, EB LINK INTF = IP_ASM3. Create .rhosts file for the node login & ASM System Name on HP & OSW System.

• Using your favorite editor, input entry for ASM server & node login info.

# vi /rc/users/int --> (On HP Server)

# vi /export/home/int --> (On OSW Server)

# exit --> (Completely log off as root)

ASM System Activities4. Log in as root or iroot on the appropriate ASM & perform the following:


login: iroot Password: <iroot_password>

5. Determine the node number, nodeX is the node number associated with the switch in VAM system switch configuration.

# cat /app/asm/var/nmbd/nodes

Result: A similar messages will appear on the screen. Database Output

2:ACTIVE:10.10.17.1:NONREF:vdci:2:nsc0d3:NW0Vyy:CST6CDT: 1:ACTIVE:10.10.9.1:BACKUP:vdci:1:nsc0d1:NW0Vxx:EST5EDT: 0:ACTIVE:0:PRIMARY:dci:0:nsc0d2:NW021D:CST6CDT:0

• The leftmost number is the node number.



• This nodeX must match the value in the 8950 VAM application field ASM LOGIN which is found by using menu 7,2 Switch Information and doing a QUERY by the switch name.

• Compare the IP address, the office id associated with the 8.1view, and the timezone to determine which node number is associated with which CLLI.

NOTE:The node number is NOT the same as the SM number.

6. In the ASM system create the login for the determined node number.

# cd /app/asm/sbin

# addnusr node<x>

— where <x> is the node number from previous steps.

New password: <New_Password>Re-enter new password: <New_Password_Again>

NOTE:At the first initial login attempt to the newly created login ID, the ASM system will require the user to choose a new password.

7. Disable password aging for the added login.

# passwd -x -1 node<x> --> (option is lowercase letter “x” and number “one”; substiture node#)

# chmod 777 /users/node<x>

— where <x> is the node number from previous steps.


8. Log in to the ASM with the new user just created & chnage the password.

login: node<x> Password: <Node_Login_password>

Choose a new password.New password: <New_Password>Re-enter new password: <New_Password_Again>

9. Create .rhosts file for the node login created & input the IP address of HP & OSW systems & login id = “int”

• Using your favorite editor, input entry for HP & OSW server & int login.

# vi /users/node<x>/.rhosts




DMS Network-Based Dump & Load via SDMThe purpose of this section is to provide information about DMS Network-Based Dump and Load via SDM in 8950 VAM .

SuperNode Data Manager (SDM)The Nortel SuperNode Data Manager (SDM) allows for Table Editor/SERVORD connectivity via TCP/IP between the Nortel DMS family of switches and 8950 VAM . In order for 8950 VAM to be able to communicate with the DMS family of switches via this new interface, appropriate software changes are required on both sides.

Background8950 VAM maintains several links to the switch in order to perform Recent Change/Verify communications, and synchronize its Shadow Database, which is the integral part of the system. These links are the Recent Change (RC) links used for the Table Editor/Service Order System (SERVORD) and the Echo-Back (EB) links respectively. Shadow Database synchronization is also realized with the help of surveillance systems such as TNM, through the audit functionality of 8950 VAM .

8950 VAM currently communicates with the Nortel DMS family of switches via a data network device called Datakit using asynchronous (TY6/12) channels, either directly or through a terminal server.

A new interface to the Nortel SDM provides the Table Editor/SERVORD and Echo-Back connectivity between the Nortel DMS switch and 8950 VAM . The communication between 8950 VAM and the switch is done via a Telnet session over TCP/IP that is established between 8950 VAM and the SDM. Figure 1-4, “Network Configuration and Message Flow” (1-5) depicts this network configuration.

Network Based Dump & Load eliminates the use of tapes in the dump & load process and utilizes the TCP/IP connection between the DMS switch and the 8950 VAM HP Server.



Feature Activation Pre-Requisite:The purpose of this section is to provide information about the prerequisites for DMS Network-Based Dump and Load via SDM in 8950 VAM . Prior to starting this procedure the following must have occurred:

The following two features must be enabled in the Feature Lock Table:• DMS DUMP AND LOAD VIA SDM• TCP/IP TO NORTEL SDM

An RC link must be established between the 8950 VAM HP Server and the DMS switch.

Network connectivity must exist among the two machines (HP server, SDM machine), with the following ports opened in the firewall:

Port Number Service

Machine Affected Description

23* telnet HP-SDM Default port for RC Link.

20 & 21 ftp HP-SDM Used by software to transfer files.

** HP-SDM Unique port for EB link.* You can choose a different port number to suit your requirement.

** Choose a UNIQUE port number that is not used by any other process.

8950 VAM

DMS Switch

SDMFiber Connection

EB Messages

RCV Messages

TCP/IP Network

Network Configuration & Message flow Diagram



NOTE:These are the ports needed by 8950 VAM to be opened bi-directionally between the SDM machine and the respective 8950 VAM machine.

Important items regarding the use of SDMThe following list contains important information regarding the use of SDM for the DMS network-based dump and load process:

• SDM provides the Table Editor/SERVORD connectivity and Echo-Back connectivity. If cut-through is available, it will continue to be supported in the same manner.

• There is no firewall between the 8950 VAM server and SDM.• 8950 VAM is responsible for managing the communication links up to the Nortel SDM unit.

The physical internal connectivity between SDM and the DMS switch is supported by Nortel and is considered transparent to 8950 VAM .

• The SDM prompt is a dollar sign ($).• The format of the echo-back log messages from the SDM are the same as those currently sent

from DMS.• Password aging on SDM is not the same as password aging on DMS. That is, password aging

will not allow the same password to be sent again.• Login and password on SDM will each have a maximum length of eight characters.• SDM has the ability to detect a network failure. If the LAN goes down, the SDM will drop the

connection to 8950 VAM as well as the connection to the DMS switch within 10 minutes. Similarly, if the connection between the switch and SDM goes down, SDM will drop the connection to 8950 VAM within 10 minutes.

• The internal communication between the SDM and DMS100 switch will be supported by NORTEL. 8950 VAM ‘s SDM support is directly dependent on the availability, quality and support given by Nortel.

• If the echo-back link is a shared echo-back link, then it is the responsibility of the other system to meet the SDM interface.

• The format of the Table Editor/Service Order messages through SDM will be the same as that currently supported for direct DMS switch connectivity.

SDM is supported either with the pass-through feature or without the pass-through feature. This is on a switch by switch basis.

• If you wish to use the pass-through feature then PASS-THROUGH must be set to "Y" on the switch administration menu.



Configure SecureShell (SSH)The purpose of this section is to provide information about Secure Shell (SSH) and to describe the procedure on how to setup the SSH feature for the HP-UX and Solaris servers.

Introduction to SSHSSH is a suite of programs that allows secured login to remote host computers, to execute commands safely on remote computers, and to provide secure encrypted and authenticated communications between two hosts over a network (secured or unsecured). It is different from the rsh (Remote Shell) in the way that the rsh protocol passes the password in clear text format. Anyone sniffing the network between the two computers can capture the password and hence will be able to collect and misuse the confidential information. SSH transmits the login information (userid and password) in encrypted form over the network and only the servers can decrypt it. Hence nobody else on the network will be able to collect and misuse any confidential information. Thus ssh should be preferred and used instead of telnet, rlogin, rsh or other insecure access methods when logging in to other host(s).

• Similarly, scp (Secure Copy) is a non-interactive command-line tool for securely transmitting files from a machine to another. It is a secure replacement for rcp and provides a similar command-line syntax.

• The authentication method that is certified, uses 2048 bit RSA keys and no passphrases.• The 8950 VAM interface software between these two servers, HP and SUN, requires an SSH

promptless mode of operation using the int account.

HP’s SSH documentHP also has a very detailed document on its SSH version.

• The HP document is titled HP-UX Secure Shell Getting Started Guide HP-UX 11i v1, HPUX 11i v2, and HP-UX 11i v3, and the part number for this pdf document is 5991-9493.

• This document is available for download from the following website: http://www.docs.hp.com• 8950 VAM follows the HP guide lines shown in the section, Configuring Public-Key

Authentication, of this document.

Setting up SSHMake sure that both servers, HP and SUN, have the necessary SSH software already installed and the default system wide SSH configuration files have not been altered from their factory installed settings.

http://www.docs.hp.com



NOTE:Setting up SSH is a one time effort. You will need to do this only once when you are configuring the feature.

Make sure that the directories ~int/.ssh are not present, on either the 8950 VAM HP server or the 8950 VAM SUN OSW workstation, when this procedure is started.

Two example diagrams are shown to display the remsh and ssh scenarios.

Example 1: Dump and Load in the remsh scenario:

Issue: GA-1, July 20109 - 1 0


Example 2: Dump and Load in the ssh scenario

Packages

The SSH package names supported are as follows: For HP-UX 11.11:• KRNG11i - HP-UX Kernel Random Number Generator• T1471AA - HP-UX Secure Shell (version A.04.50.003 and above)

NOTE:Earlier versions of HP's SSH have known security issues. The 8950 VAM 12.0, 12.2 and 13.0 versions are certified with these bundles.

For Solaris 10: • SUNWsshdu - SUN Secure Shell must be patched upto SOLARIS 10 Update 8 (October 2009)

of the Solaris 10 patch bundle.• Both HP and SUN SSH implementations are based on the public domain version of SSH and

OpenSSH.

Issue: GA-1, July 20109 - 11


NOTE:OS patch bundles are updated with every 8950 VAM release.

Configure HP-UX VAM server and OSW machines1. On the 8950 VAM server while logged in as root do the following:


• Add PubkeyAuthenticat ion yes to the SSH system wide configuration file, /opt/ssh/etc/sshd_config. Make this as the last line in the file. Also ensure no other un-commented entries exist for the parameter.

# vi /opt/ssh/etc/sshd_config

— Go to the end of the file and add the entry: PubkeyAuthentication yes

— Write, save, and quit the file: :wq!

2. Send the HUP signal to the sshd pid to have it re-read the config file.

# ps -ef | grep -i sshd

# kill -HUP <PID_FROM_ABOVE_OUTPUT>

3. On the 8950 VAM server while logged in as int do the following.

# su - int

[xxx-int] ssh-keygen -t rsa -b 2048


Generating public/private rsa key pair.Please be patient.... Key generation may take a few minutes.Enter file in which to save the key (/home/int/.ssh/id_rsa): <CR>Created directory '/home/int/.ssh'.Enter passphrase (empty for no passphrase): <CR>Enter same passphrase again: <CR>Your identification has been saved in /home/int/.ssh/id_rsa.Your public key has been saved in /home/int/.ssh/id_rsa.pub.The key fingerprint is:47:69:f2:c6:53:ea:e1:14:7e:82:7c:ab:5c:9e:b9:71 int@VAM_HP_SERVERWhere "<CR>" means the <enter> or <return> key.

Issue: GA-1, July 20109 - 1 2


4. On the SUN OSW server while logged in as root do the following.


• Add PubkeyAuthenticat ion yes to the SSH system wide configuration file, /etc/ssh/sshd_config. Make this the last line in the file. Also ensure no other un-commented entries exist for the parameter.

# vi /etc/ssh/sshd_config

— Go to the end of the file and add the entry: PubkeyAuthentication yes


5. Send the HUP signal to the sshd pid to have it re-read the config file.

# ps -ef | grep -i sshd


6. On the SUN OSW server while logged in as int do the following.

# su - int

$ ssh-keygen -t rsa -b 2048

NOTE:Don't use a passphrase.


Generating public/private rsa key pair.Enter file in which to save the key (/home/int/.ssh/id_rsa): <CR>Created directory '/home/int/.ssh'.Enter passphrase (empty for no passphrase): <CR>Enter same passphrase again: <CR>Your identification has been saved in /home/int/.ssh/id_rsa.Your public key has been saved in /home/int/.ssh/id_rsa.pub.The key fingerprint is:86:bf:b5:f0:ee:41:4c:38:ea:ce:f6:a1:fc:e4:75:49 int@VAM_OSW_SERVERWhere "<CR>" means the enter or return key.

7. Copy the int public key to the 8950 VAM server using the following command:

$ cat ~/.ssh/id_rsa.pub | ssh -l int <8950_VAM_Server> 'cat ->> $HOME/.ssh/authorized_keys'

Are you sure you want to continue connecting (yes/no)? yes


The authenticity of host 'VAM_HP_SERVER (111.222.333.555)' can't be established.RSA key fingerprint is b6:36:ba:bb:f2:5c:db:04:4d:80:7e:92:43:bd:28:0a.Are you sure you want to continue connecting (yes/no)? yes

Issue: GA-1, July 20109 - 13


Warning: Permanently added 'VAM_HP_SERVER,111.222.333.555' (RSA) to the list of known hosts.

Password: <enter int password for VAM_HP_Server>

— At the above prompt, you must supply the int password of VAM HP server.

8. Change the permissions of the file, $HOME/.ssh/authorized_keys of the VAM_HP_SERVER.

$ ssh -l int <VAM_HP_SERVER> chmod u=rw,go= '$HOME/.ssh/authorized_keys'

9. On the 8950 VAM server while logged in as int, copy the int public key to the SUN OSW server using the following command:

[xxx-int] cat ~/.ssh/id_rsa.pub | ssh -l int <OSW_System> 'cat - >>$HOME/.ssh/authorized_keys'

Are you sure you want to continue connecting (yes/no)? yes


The authenticity of host 'VAM_OSW_SERVER (111.222.333.444)' can't be established.RSA key fingerprint is a9:ca:e8:3d:b2:de:c6:a5:7f:03:f3:88:47:07:88:e5.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added 'VAM_OSW_SERVER, 111.222.333.444' (RSA) to the list of known hosts.

Password: <enter int password for VAM_OSW_Server>

— At the above prompt, you must supply the int password of VAM OSW server.

10. Change the permissions of the file, ~/.ssh/authorized_keys of the OSW system.

[xxx-int] ssh -l int <SUN_OSW_System> chmod u=rw,go= '$HOME/.ssh/authorized_keys'

11. Validating the int account for promptless SSH mode in both directions.

• While logged in as int on the SUN OSW server, execute the following command:$ ssh <8950VAM_HP_SERVER> date

— This should give promptless mode of execution of the ‘date’ command on the VAM_HP_SERVER.

• Similarly, while logged in as int on the 8950 VAM server, execute the following command:[xxx-int] ssh <VAM_OSW_SERVER> date

— This should give promptless mode of execution of the ‘date’ command on the VAM_OSW_SERVER.

Issue: GA-1, July 20109 - 1 4


Verifying permissions of the SSH configuration filesThe file permissions must be setup as outlined below on both the HP and SUN servers. Any deviations from these permissions will cause promptless SSH mode failures. Failures are logged in /var/adm/syslog/syslog.log on the HP server and /var/adm/messages on the SUN server.

Permissions (ssh configuration files)

Disabling insecure servicesNOTE:Be sure that ssh is setup and working before disabling both rlogin and telnet. If you are remotely logged in via telnet and disable telnet, you will loose your current remote session. The same goes for rlogin.

12. Once ssh configuration is complete, you may disable the approprite insecure services on the SUN OSW system while logged in as root :


12.1 For Solaris 9: the services are enabled/disabled via a manual edit of /etc/inetd.conf followed by a SIGHUP signal to the inetd.

# vi /etc/inetd.conf

— You may comment out the entries in the file for : telnet, ftp, rlogin, rexec


• Send the HUP signal to the inetd pid to have it re-read the config file.

# ps -ef | grep -i inetd


12.2 For Solaris 10: the services are enabled/disabled by running the following commands:

File/Directory Permissions

$HOME (home directory) drwx------ or drwxr-xr-x

$HOME/.ssh drwx------

$HOME/.ssh/authorized_keys -rw-------

$HOME/.ssh/id_rsa -rw-------

$HOME/.ssh/id_rsa.pub -rw-r--r--

$HOME/.ssh/known_hosts -rw-r--r--

Issue: GA-1, July 20109 - 15


# svcadm disable telnet

# svcadm disable ftp

# svcadm disable rexec

# svcadm disable rlogin

# svcadm disable shell:default

# svcadm disable shell:kshell (for the Kerberos shell only)

12.1 For VAM HP Server: the services are enabled/disabled via a manual edit of /etc/inetd.conf followed by a SIGHUP signal to the inetd.

# vi /etc/inetd.conf

— You may comment out the entries in the file for : telnet, ftp, rexec, login, shell, kshell (for Kerberros shell only), and klogin (for Kerberos rlogin only).


• Send the HUP signal to the inetd pid to have it re-read the config file.

# /usr/sbin/inetd -c

Issue: GA-1, July 20109 - 1 6


VAM SSH Feature EnablingAt the VAM OSW application level, a new OSW SSH feature support utility exists that allows the VAM administrator to:

• Check the status of the HP-OSW SSH and OSW-ASM SSH features• Enable both • Disable both

The utility must be run by the int user on both the VAM HP server and the OSW server to activate the SSH feature. To enable the features, two feature lock passwords are required (passwords are only required on the VAM HP server), one for each feature.

NOTE:The SSH features are enabled with OSWssh_feat_util script and not by the typical feature administration menu.

The utility is located on both the HP server & SUN OSW server as the following location:

On VAM HP server: /topasrc/bin/OSWssh_feat_util

ON SUN OSW server: /osw/prog/bin/OSWssh_feat_util

The utility can be run from any of the server and be used for the Seven options as follows:• 1) Check - SSH SUPPORT BETWEEN HP AND OSW• 2) Check - SSH SUPPORT BETWEEN OSW AND ASM• 3) Enable - SSH SUPPORT BETWEEN HP AND OSW• 4) Enable - SSH SUPPORT BETWEEN OSW AND ASM• 5) Disable - SSH SUPPORT BETWEEN HP AND OSW• 6) Disable - SSH SUPPORT BETWEEN OSW AND ASM• 7) Exit

Issue: GA-1, July 20109 - 17


Check status of SSH support (HP & OSW):• On HP VAM server: [xxx-int] /topasrc/bin/OSWssh_feat_util• On SUN OSW server: [$-int] /osw/prog/bin/OSWssh_feat_util

OSW SSH Feature support utility.

1) Check - SSH SUPPORT BETWEEN HP AND OSW2) Check - SSH SUPPORT BETWEEN OSW AND ASM3) Enable - SSH SUPPORT BETWEEN HP AND OSW4) Enable - SSH SUPPORT BETWEEN OSW AND ASM5) Disable - SSH SUPPORT BETWEEN HP AND OSW6) Disable - SSH SUPPORT BETWEEN OSW AND ASM7) ExitWhat operations do you wish to perform (1-7)? 1


DISABLED OSW SSH Feature support utility.

Check status of SSH support (OSW & ASM):• On HP VAM server: [xxx-int] /topasrc/bin/OSWssh_feat_util• On SUN OSW server: [$-int] /osw/prog/bin/OSWssh_feat_util





Issue: GA-1, July 20109 - 1 8


Enable SSH support (HP & OSW):• On HP VAM server: [xxx-int] /topasrc/bin/OSWssh_feat_util• On SUN OSW server: [$-int] /osw/prog/bin/OSWssh_feat_util



Enter the password: <password by "feat_cntrlGenPw" utility>


ENABLED OSW SSH Feature support utility.

Enable SSH support (OSW & ASM):• On HP VAM server: [xxx-int] /topasrc/bin/OSWssh_feat_util• On SUN OSW server: [$-int] /osw/prog/bin/OSWssh_feat_util


1) Check - SSH SUPPORT BETWEEN HP AND OSW2) Check - SSH SUPPORT BETWEEN OSW AND ASM3) Enable - SSH SUPPORT BETWEEN HP AND OSW4) Enable - SSH SUPPORT BETWEEN OSW AND ASM5) Disable - SSH SUPPORT BETWEEN HP AND OSW6) Disable - SSH SUPPORT BETWEEN OSW AND ASMWhat operations do you wish to perform (1-7)? 4

Enter the password: <password by "feat_cntrlGenPw" utility>


ENABLED OSW SSH Feature support utility.

Issue: GA-1, July 20109 - 19


Disable SSH support (HP & OSW):• On HP VAM server: [xxx-int] /topasrc/bin/OSWssh_feat_util• On SUN OSW server: [$-int] /osw/prog/bin/OSWssh_feat_util





Disable SSH support (OSW & ASM):• On HP VAM server: [xxx-int] /topasrc/bin/OSWssh_feat_util• On SUN OSW server: [$-int] /osw/prog/bin/OSWssh_feat_util





Issue: GA-1, July 20109 - 2 0


Configure Proactive System MonitoringProactive System Monitoring allows the System Administrator to monitor both the system and application levels of 8950 VAM for errors and possible problems. This tool consists of scripts with parameters that can be configured and scheduled by the Administrator to monitor specific processes at specified times, and to send error/warning messages, based on the configured parameters, to ‘int’ mail addresses and selected printer(s). A single script is initiated by a cronjob which executes each individual script that performs a specific function. Each of these scripts can be individually enabled or disabled.

• This utility also allows the Administrator to add locally-generated scripts to perform additional functions. Once added, these scripts can be enabled, disabled or deleted by the Administrator.

Monitoring Scripts OverviewThe following table lists the configured standard scripts, their actions, and their outputs. By default, all scripts are delivered enabled; each of the scripts has four priority level messages:

• Priority Level 1: Highest warning message for the utility. Immediate action should be taken.• Priority Level 2: Urgent warning message for the utility; Could adversely affect system.• Priority Level 3: Mid-level warning message for the utility.• Priority Level 4: Lowest warning message for the utility.

Issue: GA-1, July 20109 - 21


Table List of Monitoring Scripts Available:

Script Action Message OutputCore Files Looks for core files in all directories Reports the full path of the core file(s) and also

the process that produced the core file(s)

File System Space

Monitors each file system to ensure adequate space is available based on two specific thresholds. Default thresholds are provided, and the Administrator can modify them. There is one set of thresholds for all file systems.Default Lower Threshold = 85%Default Upper Threshold = 90%

Two thresholds are reported:1) Priority level 4 message:% space level at which administrator should begin cleaning up2) Priority level 3 message:% space level that will adversely affect performance if not addressed immediately

System Mirroring

Monitors:1) State of each Logical Volume (LV) is mirrored2) Each LV is mirrored 100%3) 1st and 2nd copies are specified for each LV4) 3rd copy is not specified for an LV

Priority level 1 message noting any/all of the 4 mirroring states not in compliance with desired state.

The Administrator is warned not to Re-Boot the machine.

Backup Failure The 8950 VAM System should be backed up every 5 days. This script monitors for successful backups or error conditions

1) Priority level 2 message reports if most recent backup was unsuccessful2) Priority level 3 message reports successful backup did not occur in the last 5 days to remind the Administrator that a backup should be scheduled

Informix dbspace

Ensures adequate amount of space on each database to execute applications based on a specified lower limit of free blocks for each database.Default Value = 100,00 Blocks

Priority level 1 message reports that free space is below specified limit, gives database name and number of free memory blocks

Large /var and mail files

Recursively searches for all log / mail files larger than the specified file size.Default Value = 1000000

Priority level 3 message notes the full path and size of the file

Issue: GA-1, July 20109 - 2 2


Informix Monitors state of informix and the presence of /rc/data/at* fields that carry important information on Informix crashes

Priority level 1 message sent when the presence of /rc/data/at* files is detected or if the Informix process is not running

Informix Monitoring

Checks on the INFORMIX engine Checks the status of “oninit” process.

This script shall not attempt to fix any failure. This script shall not attempt to restart INFORMIX engine. This will be considered a severity level 2 messageThis script shall not attempt to fix any failure. This script shall not attempt to restart INFORMIX engine. This will be considered a severity level 2 message

Informix Locks Checks and tests INFORMIX locks with waiters count

Informix Memory Blocks

Checks available free onstate memory blocks.

Surveillance There should be a file for each switch that contains a surveillance system echo back message. These files will be in /rc/tnm directory for 5ESS switches and in /rc/tnm_dms directory for DMS switches. It will be unusual to have no file or no data within the file. This script will identify such conditions.

If the script detects that such a file doesn't exist for a given day, it will send a level 3 message to the system administrator.

CPU Utilization Monitors all processes accumulating excessive cpu time that could adversely affect system operation based on a specified upper limit (Application processes that normally run for long periods are excluded from the list of monitored processes).Default Value = 20

A priority level 3 message reports the process or processes accumulating CPU time and specific information on time usage

Recent Change (RC) and Echo Back (EB) Links

Ensures that RC and EB links are up and running to maintain Shadow db sanity

Priority level 2 message reports all switches for which either RC link or EB link or both are DOWN.

Large Application Log Files and Trace Files

Searches for large log files in /rc/data directory based on specified file size and also reports on Trace Files.Default Value = 10000000

Priority level 3 message provides full path and present size of any large log file(s) detected and also notifies the user about the existence of tracing file(s)

Script Action Message Output

Issue: GA-1, July 20109 - 23


Switch Dump/Load Directories

Searches for sub-directory of switches that have been dumped/loaded and not modified in the last 30 days

Priority level 3 message reports complete path information on detected sub-directories

Application Process restart

Searches for processes that have been re-started

Priority level 3 message reports process name and number of times re-started

Invalid switch Names

Detects switch names not recognizable by 8950 VAM

Priority level 2 message reports all invalid switch names detected

Last Boot Time Recognizes the condition when the system is not booted beyond the specified interval

When the script encounters such a condition, the script shall report this condition. This script should state when the machine was booted last time and should also give a warning message to the administrator. The script shall NOT attempt to boot the machine. This will be considered a severity level 3 message.

Shared Memory Segments

Finds out the condition when the number of shared memory segments exceeds the specified number.Default Lower Value = 64Default Upper Value = 128

When the script encounters such a condition, the script shall report this condition. The script will state the current and recommended number of allocated shared memory segments. This will be considered a severity level 2 message.

SAR Information for Completed Orders

Collects the SAR information for the given day and the order activity in 20 minute intervals

The log (output) message is located in /rc/data/system_monitoring with the file name collect_sar_inf.<yymmdd>. There will be one file per day regardless of how many times the data is collected.

Top 25 Processes

Reports the top 25 processes on the given 8950 VAM central at a particular instance. The script also generates output from the ps command.

Log (output) message is located in /rc/data/system_monitoring with the file name top_processes.<yymmdd>. There will be one file per day regardless of how many times the data is collected

Number of Users Logged in for TE & TI

Reports the number of users logged in to Translations Interface and Task Execution GUI for a given day. This number is cumulative from the beginning of the day and is not the number of currently active users. The script distinguishes multiple logins from the same user, i.e. the second login from the same user will be counted toward the number of users.

Log (output) message is located in /rc/data/system_monitoring with the file name num_of_users.<yymmdd>. There will be one file per day regardless of how many times the data is collected


Issue: GA-1, July 20109 - 2 4


Number of Orders Processed (System Performance)

Reports the number of orders entered into the system and the number of orders executed in the system

Log (output) message is located in /rc/data/system_monitoring with he file name system_performance.<yymmdd>. There will be one file per day regardless of how many times the data is collected

Number of Created RCs per Switch per Task

Reports workload for each switch, in terms of number of RCs processed, grouped by task for the given day and also reports workload per source, i.e. TI GUI/TE GUI .

Log (output) message is located in /rc/data/system_monitoring with he file name work_load_per_switch.<yymmdd>. There will be one file per day regardless of how many times the data is collected.

Number of Items in LDS Handler Queue

Reports number of items in lds handler queue at a given instance of time and groups this number by switch name, task name and user id.

Log (output) message is located in /rc/data/system_monitoring with the file name xmt_item_count.log.<yymmdd>. There will be one file per day regardless of how many times the data is collected, for example, xmt_item_count.log.041103


Issue: GA-1, July 20109 - 25


Proactive System Monitoring MenuThis menu item allows complete administration of all proactive system monitoring associated with the VAM application.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System

Proactive System Monitoring Menu

1) Exit2) Enable/Disable scripts3) List Scripts Status 4) Update Printer name or email address for priority5) Update parameters for scripts6) Menu for locally generated scriptsSelection:

Option 2 = Allows Enable/Disable for monitoring scripts.

Option 3 = Provides list of available monitoring scritps & it’s status.

Option 4 = Allows updates for printers/admin e-mail address for monitoring output.

Option 5 = Allows modification of parameters for monitoring scritps.

Option 6 = Allows admin of local scripts by administrators.

Issue: GA-1, July 20109 - 2 6


Configure Proactive Monitoring scriptsThis menu item allows complete administration of all proactive system monitoring associated with the VAM application.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 2) Enable/Disable scripts

2. Answer the following prompts accordingly for each of the monitoring scripts to monitor:

• To start the script monitoring, type y and press <Enter>.

• To stop the script monitoring, type n and press <Enter>.

Script to find core files (Y|N)[D: Y] <Input_Answer>Script to check File System Space (Y|N)[D: Y]<Input_Answer>Script to check System Mirroring (Y|N)[D: Y]<Input_Answer>Script to check Backup Failure (Y|N)[D: Y] <Input_Answer>Script to check Informix database space (Y|N)[D: Y]<Input_Answer>Script to check Large /var files (Y|N)[D: Y] <Input_Answer>Script to check Informix errors (Y|N)[D: Y] Script to check CPU utilization (Y|N)[D: Y] Script to check rc/echo back links (Y|N)[D: Y] Script to check Large log files (Y|N)[D: Y] Script to check Switch dump directories (Y|N)[D: Y] Script to check Process restart (Y|N)[D: Y] Script to check Invalid switches (Y|N)[D: Y] Script to check Surveillance (Y|N)[D: Y] Script to check counter value of cvurequest_sq table (Y|N)[D: N] Script to check last boot time (Y|N)[D: Y] Script to check shared memory segments (Y|N)[D: Y] Script to check Informix table extents (Y|N)[D: N] Script to enable informix monitoring (Y|N)[D: Y] Script to report SAR information for completed orders (Y|N)[D: Y] Script to report top 25 processes daily (Y|N)[D: Y] Script to report number of users logged in for TI and TE (Y|N)[D: Y] Script to report number of orders processed (Y|N)[D: Y] Script to report number of created RCs per switch per task (Y|N)[D: Y] Scriptto report number of Items in LDS Handler Queue (Y|N)[D: Y]

3. Answer the reconfirmation prompt accordingly:

Do you want to use above values? (Y|N) [D: N]

Issue: GA-1, July 20109 - 27


• To confirm the option for all the monitoring scripts, type y and press <Enter>.

• To un-do changes to the option for all the monitoring scripts, type n and press <Enter>.

4. Exit the menu option accordingly.

— press <Return> to go to Proactive System Monitoring Menu.


Issue: GA-1, July 20109 - 2 8


Display Proactive Monitoring scriptsThis menu item display a list and it’s status of all proactive system monitoring scripts associated with the VAM application.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 3) List Scripts Status

2. A status display of all the monitoring scripts will be shown:


Script to find core files (Y|N) : ENABLEDScript to check File System Space (Y|N) : ENABLEDScript to check System Mirroring (Y|N) : ENABLEDScript to check Backup Failure (Y|N) : ENABLEDScript to check Informix database space (Y|N) : ENABLEDScript to check Large /var files (Y|N) : ENABLEDScript to check Informix errors (Y|N) : ENABLEDScript to check CPU utilization (Y|N) : ENABLEDScript to check rc/echo back links (Y|N) : ENABLEDScript to check Large log files (Y|N) : ENABLEDScript to check Switch dump directories (Y|N) : ENABLEDScript to check Process restart (Y|N) : ENABLEDScript to check Invalid switches (Y|N) : ENABLEDScript to check Surveillance (Y|N) : ENABLEDScript to check counter value of cvurequest_sq table (Y|N) : DISABLEDScript to check last boot time (Y|N) : ENABLEDScript to check shared memory segments (Y|N) : ENABLEDScript to check Informix table extents (Y|N) : DISABLEDScript to enable informix monitoring (Y|N) : ENABLEDScript to report SAR information for completed orders (Y|N) : ENABLEDScript to report top 25 processes daily (Y|N) : ENABLEDScript to report number of users logged in for TI and TE (Y|N) : ENABLEDScript to report number of orders processed (Y|N) : ENABLEDScript to report number of created RCs per switch per task (Y|N) : ENABLEDScript to report number of Items in LDS Handler Queue (Y|N) : ENABLED

Press Enter to Continue..



— keep selecting option 1) Exit to completely exit back to UNIX prompt.

Issue: GA-1, July 20109 - 29


Update Printer/E-mail for Monitoring scriptsThis menu item display a list and it’s status of all proactive system monitoring scripts associated with the VAM application. This menu item allows you to identify and printer name and an e-mail address for each of the monitoring scripts output.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 4) Update Printer name or email address for priority


NOTE:You can input multiple e-mail addresses by using a comma as the separator.

Printer Name [D: ] E-mail address [D: ]

Printer Name for priority 1 [D: ] E-mail address for priority 1 [D: ]




3. Answer the reconfirmation prompt accordingly:







Issue: GA-1, July 20109 - 3 0


Update Parameter for Monitoring scriptsThis menu item display a list and it’s status of all proactive system monitoring scripts associated with the VAM application. This menu item allows you to identify and printer name and an e-mail address for each of the monitoring scripts output.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 5) Update parameters for scripts


File System Space lower threshold(%) [D: 85]

— Input the % level to generate a priority level 4 message for FS space.

File System Space upper threshold(%) [D: 90]

— Input the % level to generate a priority level 3 message FS space.

Number of free blocks in informix database [D: 100000]

— Input the value to generate a priority level 1 message for DB Space.

Maximum file size for /var files [D: 1000000]

— Input value % to generate a priority level 3message for file size in /var FS.

Allowed CPU time to accumulate [D: 20]

— Input the value to generate a priority level 3 message for CPU time.

Maximum file size for log files [D: 10000000]

— Input the value to generate a priority level 3 message for log files.

Lower limit for counter value of cvurequest_sq table [D: ]

— Input the % level to generate a priority level 4 message

Upper limit for counter value of cvurequest_sq table [D: ]

— Input the % level to generate a priority level 3 message

Issue: GA-1, July 20109 - 31


Permitted boot time interval between two system boot in days [D: 60]

— Input the value to generate a priority level 3 message for system boot time.

Maximum number of allowed shared memory segments [D: 2]

— Input the value to generate a priority level 2 message for Informix shared memory.

Informix per table lower extent count threshold [D: ]

— Input the value for a lower extent.

Informix per table upper extent count threshold [D: ]

— Input the value for a upper extent

3. Once all the information has been provided, answer the reconfirmation prompt accordingly:







Issue: GA-1, July 20109 - 3 2


Local Scripts for Proactive Monitoring MenuThis menu item allows the administrator to use the customer specific scripts into the proactive monitoring feature.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 6) Menu for locally generated scripts

Proactive System Monitoring Menu

1) Exit2) Enable/Disable locally generated Script Executing3) Add new Scripts4) Display Scripts5) Delete ScriptsSelection:

Option 2 = Allows Enable/Disable for local monitoring scripts.

Option 3 = Allows adding of monitoring scritps.

Option 4 = Allows listing of monitoring scripts.

Option 3 = Allows deleting of monitoring scritps.

Issue: GA-1, July 20109 - 33


Activate Local Proactive Monitoring scriptsThis menu item allows complete administration of all local scripts for proactive system monitoring associated with the VAM application.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 6) Menu for locally generated scripts— 2) Enable/Disable locally generated Script Executing

2. Answer the following prompts accordingly to activate/de-activate local monitoring:

• Prompt To Activate:System is not configured to execute locally generated scripts Would you like to change it (y/n)? [D: n]

• To activate the script monitoring, type y and press <Enter>.

• Prompt to De-Activate:System is configured to execute locally generated scripts Would you like to change it (y/n)? [D: n]

• To de-activate the script monitoring, type y and press <Enter>.




Issue: GA-1, July 20109 - 3 4


Add new Local Proactive Monitoring scriptsThis menu item allows complete administration of all local scripts for proactive system monitoring associated with the VAM application.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 6) Menu for locally generated scripts— 3) Add new Scripts

2. Answer the following prompts accordingly to add new script(s):

Enter the name of script:

• Input full path of script name and press <Enter>.

Do you have parameters for script <script> (y/n) ? [D: n]

• If there are parameters to the script type y and press <Enter>.

• If there are NO parameters to the script type n and press <Enter>.

• Prompt If there are parameters: Enter Parameters for script naytest2 ( Leave it blank to exit )Enter Parameter 1 : 10Enter Parameter 2 : yEnter Parameter 3 :

• Input all parameter values and when done <Enter>.

3. Answer the following prompts accordingly to add new additional script(s):

Do you want to enter another script [y/n] [D: n]: n

• To add more local script monitoring, type y and press <Enter>. If you wish to add morescripts, refer to previous step for parameter inputs.

• To NOT add more local scripts, type n and press <Enter>.




Issue: GA-1, July 20109 - 35


Add new Local Proactive Monitoring scriptsThis menu item allows complete administration of all local scripts for proactive system monitoring associated with the VAM application.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 6) Menu for locally generated scripts— 3) Add new Scripts

2. Answer the following prompts accordingly to add new script(s):

Enter the name of script:

• Input full path of script name and press <Enter>.

Do you have parameters for script <script> (y/n) ? [D: n]

• If there are parameters to the script type y and press <Enter>.

• If there are NO parameters to the script type n and press <Enter>.

• Prompt If there are parameters: Enter Parameters for script naytest2 ( Leave it blank to exit )Enter Parameter 1 : <input_1stParameter>Enter Parameter 2 : <Input_2ndParameter>Enter Parameter 3 : <CR>

• Input all parameter values and when done <Enter>.


Do you want to enter another script [y/n] [D: n]: n

• To add more local script monitoring, type y and press <Enter>. If you wish to add morescripts, refer to previous step for parameter inputs.

• To NOT add more local scripts, type n and press <Enter>.




Issue: GA-1, July 20109 - 3 6


Display Local Proactive Monitoring scriptsThis menu item displays all local scripts activated for proactive system monitoring associated with the VAM application.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 6) Menu for locally generated scripts— 4) Display Scripts• The output will display all locally added/configured monitoring scripts.


Script Name : monitor_ftpScript Name : monitor_spaceScript Name : monitor_databaseScript Name : monitor_testHit Enter to Continue




Issue: GA-1, July 20109 - 37


Delete Local Proactive Monitoring scriptsThis menu item allows you to delete any local scripts added for proactive system monitoring associated with the VAM application.




— 10) 8950 VAM Configuration Menu— 9) Configure Proactive Monitoring System— 6) Menu for locally generated scripts— 5) Delete Scripts


Enter the script name, you wish to delete

• Input the name of local script to delete and and press <Enter>.

• If you wish to delete more scripts, re-run the steps again.




Issue: GA-1, July 20109 - 3 8


Password Ageing FeaturePassword Aging is the concept that a user must periodically change his or her password in order to continue to authenticate to services. If the password is not changed within a specific amount if time, it expires and must be reset. Password aging forces the user to change passwords after a system administrator-specified period of time. Password aging can also force a user to keep a password for a certain number of weeks before changing it.

The Password Aging feature includes the following:• New user passwords assigned by the Administrator must be changed by the user during the

first login session. They may be changed by the user at any time during the session by clicking the User Options button on the navigation bar of the GUI Screen.

• New user logins are stored in T. (temp). The user MUST use the temporary login within 14 days after they have been assigned or the password expires.

• User passwords are valid for a period set by the Administrator, or for a default period of 45 days, and must be changed by the user before the expiration of the time period.

• If a user password is not used for a period of 45 days, it is disabled and must be re-enabled by the Administrator.

• If a user exceeds the threshold for failed logins in a single session, the password is blocked; Only the system administrator can reset a blocked password.

• All user logins are recorded and stored in a log file accessible to the Administrator. Administrators can monitor the status of each user account via the Unix shell.

Password Ageing Feature ActivationThe following features must be activated on the 8950 VAM HP server via the Feature control menu:





Feature Name Description

PASSWORD AGING Feature to configure when passwords expire.

PASSWORD RETENTION Feature to configure when logins/passwords are disabled.

Issue: GA-1, July 20109 - 39


— 12) 8950 VAM Feature Control Menu— 2) Enable Features


Do you want to enable ALL NVAM Features? (Y|N) [D: N] n

• Type n and press <Enter>

Enable feature?

• Input the <Feature Name> and press <Enter>

Is feature name entered <Feature Name>? (Y|N) [D: Y] y

• Input the y and press <Enter>

Enter password for <Feature Name>?

• Input the <Feature Password> and press <Enter>. You can repeat the steps to active thenext feature.


— press <Return> to go to Feature Control Menu.


Configure Password Ageing FeatureThe following steps should be taken to configure password Ageing in VAM application. Once configured, the # of days before a password change is requested can be specified before a user logs into the application.




— 10) 8950 VAM Configuration Menu— 11) Configure Password Aging


------------------------------------------------------------User Password Aging. Use carriage return to terminate response.Enter 'exit' from any prompt to exit.------------------------------------------------------------Enter the number of days before passwords expire (1 - 9999).Current value is set to: default value of 45 days.Enter new value:

• Type the new value in <Days> and press <Enter>

Issue: GA-1, July 20109 - 4 0


Set Password Aging for 90 days? (Y|N) [D:N] y

• To reconfirm, type y and press <Enter>




Configure Password Retention FeatureThe following steps should be taken to configure User Login Retention in VAM application. Once configured, the # of login attempts can be specified before a user login is locked out of the application.

• More than 10 incorrect logins by a user results in the password being disabled. Only the Administrator may re-set/re-assign passwords once they are disabled.

• If a user account has been disabled, the user receives a message notifying them of this upon attempting a login.

• All user logins are recorded and stored in a log file accessible to the Administrator. Administrators can monitor the status of each user account via the Unix shell.




— 10) 8950 VAM Configuration Menu— 12) Configure Number of Login Attempts


------------------------------------------------------------------Number of Login Attempts.Use carriage return to terminate response.Enter 'exit' from any prompt to exit.-------------------------------------------------------------------

Enter the number of login attempts (1 - 10).Current value is set to: 10 .Enter new value:

• Type the new value in <Login_Attempts> and press <Enter>

Set Password Aging for <X> days? (Y|N) [D:N] y

• To reconfirm, type y and press <Enter>

Issue: GA-1, July 20109 - 41


Auto Code Opening (ACO)The Automated Code Opening Feature significantly enhances the operations environment in the customer environment by automating a significant percentage of the code opening translations activity currently performed manually.

The Automated Code Opening tool automates most of the activities that are currently manually performed by translations technicians for opening new codes. Data needed to open new NXX codes is downloaded into 8950 VAM automatically on a daily basis via FTP file transfer from the company’s Code Administration System.

A link to the code administration system allows 8950 VAM to automatically flow both database information and completed code openings back to the Code Administration System, thereby providing timely and accurate feedback.

Automated Code Openings automates GROWTH jobs, including status reporting to the Code Administration system. Translations Technicians are still responsible for translations pertaining to network rearrangements.

ACO Tool Benefits:• Validates the data based on its shadow database.• Derives the appropriate rating and routing like codes using both information from the code

administration systems and user defined rule sets.• Automatically generates and schedules all required code openings for the upcoming month.• Provides reports that identify codes for which orders have been successfully scheduled as well

as codes that cannot be handled automatically and must be opened manually. • Provides Management Summary Reports to allow management and system administrators to

track the efficiency of the Automated Code opening process.

The scope of this feature is limited to 5ESS and DMS-100 switches and to the processing of code opening translations for new NXX codes based on the concept of the existence of like rating and routing codes.

ACO System OverviewThe Automated Code Opening process is driven by an interface to a customer code opening application (Ex: COTS application). One such customer application operates in each domain of 8950 VAM HP server, and drives the code openings in the switches in that domain. Each such customer code opening system is connected to an 8950 VAM HP Server (called the Primary Central) in the domain via a TCP/IP network.

• Information transfer in both directions over this interface will be via regularly scheduled (daily) cron jobs executed in the Primary Central using ftp.

• A manual mode exists whereby a user can open new NPA and NXX codes.

Issue: GA-1, July 20109 - 4 2


• In the manual mode, the user will be allowed to select a set of switches and enter a set of codes. The manual code opening mode will generate orders of recent changes (to open each specified code on each selected switch) and leave them for manual scheduling & execution via the existing 8950 VAM GUI.

ACO Tool Functions:• Receive file from customer code opening system containing code opening and network

rearrangement requests, parse and validate it, and return an acknowledgment report.• Update internal scheduling data• Identify code openings for which orders are to be generated on the current day, according to the

schedule• Generate verifies to ensure that view records in the 8950 VAM shadow are in sync with the

switch• Generate and schedule orders of recent changes to perform the code openings• Generate reports indicating outcomes and statistics

Issue: GA-1, July 20109 - 43


ACO System ArchitectureThe following diagram shows the topology of a Code Opening domain. Note that there is one Primary Central and one customer code opening system in the domain, and that there is connectivity among all the Centrals in the domain and between the customer code opening system and the Primary Central.

All 8950 VAM HP Servers perform the following functions:• Identify code opening order generation and network rearrangement actions that are scheduled

for the current day, and generate the necessary recent changes and table updates.• Generate reports that are available for viewing by the GUI.

In addition, the Primary 8950 VAM HP Server also performs the following functions:• Receives and processes code opening and network rearrangement requests• Generates reports and transmits them to the customer Code Opening system• Serves as the home for the Global Tables

Network (TCP/IP)

COTS System(Code Opening System)

PRIMARY 8950 VAM Server

Non PRIMARY 8950 VAM Server

Non PRIMARY 8950 VAM Server

Switch

Switch

Switch

ACO Architecture

Issue: GA-1, July 20109 - 4 4


• A subsystem shown as Request Processor executes only on the Primary Central• Subsystems shown as Code Opener and Report Generators run on all Centrals• Global tables reside on the Primary Central and are accessed by Non-primary Centrals using

Informix distributed query/update capabilities• Local tables reside on each Central

User’s GUI

Primary 8950 VAM server

Global DB Table

Local DB Table

Request Processor

Report Generators

Code Opener

User’s GUI

Non Primary 8950 VAM server

Local DB Table

Report Generators

Code Opener

Issue: GA-1, July 20109 - 45


ACO ORDER GENERATIONThe Code Opening subsystem comprises several new processes that communicate among processes is via socket messages.

• ACO_RQST is executed via a cron an d run on the Primary HP Server once a day as specified in crontab, which is taken from the aco_rqst_cron_time value in the HP Server Domain Information Table. ACO_RQST reads and processes the request from the request file received from the Code Administration System.

• ACO_SCHED is executed by cron daily at a time specified in the crontab file. It determines code opening jobs that are to be generated today and sends them to ACO_DIST for order generation.

• ROUT/GUI subsystem sends code opening job sets to ACO_DIST for order generation, specifying a set of CLLIs and a set of codes.

• ACO_DIST is a daemon process that receives code opening jobs and queues them for dispatch to multiple instances of ACO_GEN processes.

— It distributes the jobs among the ACO_GEN processes when they indicate that they are free to execute a job.

— The objective of ACO_DIST is to perform multiple code opening order generation jobs concurrently with the constraints that at most one code opening occur for a switch at one time and that the verifies for a code opening order generation be throttled.

• Each ACO_GEN is a daemon process that performs order generation for the given job by implementing the switch specific order generation algorithms. Verifies that are performed during order generation follow the path ACO_GEN -> SWCOM/DMSWCOM -> DBUPD -> ACO_GEN

• ACO_POST is a daemon process that receives notification from DBUPD of completion/rejection of orders generated and scheduled earlier.

— It updates the Scheduled Code Opening and Code Opening Disposition tables to reflect the status of the code opening operation. Recent change orders follow the path

AUTO-SNDR -> SREF -> SWCOM/DMSWCOM -> DBUPD -> SREF -> ... -> DBUPD -> ACO_POST

• DBUPD process will be modified to notify ACO_POST whenever an order with order name is completed/rejected.

Issue: GA-1, July 20109 - 4 6


Global

Primary or Non-Primary Central

ACO_SCHED (cron)

ACO_DIST

ACO_GEN

SWCOM/

DBUPD

ACO_POST

Tables Single job,

Jobs to be Job ID

Job complete,

Job Set ID

Send verify

Verify/RCcomplete

Verify(pool, say 5)

(one per switch)

GUI/ROUT

complete

Job Set Tables

Job Queue

SREF AUTO-SNDR (cron)Sendorder

SendRC

Ordercomplete

RCcomplete

DMSWCOM

generatedtoday

Status, Log/Report lines

Logs/ Reports

Status query

Outcome

UIasyipc

Log/Reportlines

Issue: GA-1, July 20109 - 47


ACO REPORTS AND LOGS

Acknowledgment Report• This report will be generated by ACO_RQST in directory $DATAFILEDIR/aco/rpts with

file name specified by field aco_ack_file in table atp_domain_info. It will be transmitted to the customer code opening system in directory specified by field aco_rem_rpts_dir, and will be available for viewing from the Report Browser GUI.

Auto Code Processing Log• This report will be generated by ACO_RQST in directory $DATAFILEDIR/aco/rpts with

file name specified by field aco_proc_rpt_file in table atp_domain_info. It will be printable by the System Administrator and will be available for viewing from the Report Browser GUI.

Auto Code Immediate Action Report

Report Created by Disposition

1 Acknowledgment Report ACO_RQST -- Primary Central only

Transmitted at completion of request processing.

2 Auto Code Processing Log ACO_RQST -- Primary Central only

Sent to printer designated by SA. Can be viewed using log browser from Primary Central

3 Auto Code Immediate Action Report

ACO_RQST -- Primary Central only


4 Scheduled Code Opening Report GUI Can be viewed from GUI using query-by-example

5 Code Opening Disposition Report

GUI Transmitted to customer code opening system. Can be viewed from GUI using query-by-exam-ple

6 Auto Code Exceptions Report ACO_GEN and ACO_SCHED -- Each Central


7 Auto Code Order Creation Log Reports

ACO_GEN -- Each Central Can be viewed using log report browser from GUI.

8 Administrative Table Update Log

GUI Can be viewed using log report browser from GUI.

9 Management Summary Report GUI GUI only

Issue: GA-1, July 20109 - 4 8


• This report will be generated by ACO_RQST in directory $DATAFILEDIR/aco/rpts with file name specified by field aco_immed_rpt_file in table atp_domain_info. It will be printable by the System Administrator and will be available for viewing from the Report Browser GUI.

Scheduled Code Opening Report• This report will be generated by the GUI from the aco_sched table at the time it is requested

by the user.

Code Opening Disposition Report• This report will be generated by aco_rpts in directory $DATAFILEDIR/aco/rpts with

file name specified by field aco_disp_rpt_file in table atp_domain_info. It will be transmitted to the customer code opening system in directory specified by field aco_rem_rpts_dir, and will be available for viewing from the Report Browser GUI.

Auto Code Exceptions Report• This report will be generated by ACO_GEN/ACO_DIST in directory $DATAFILEDIR/aco/rpts with file name specified by field aco_excep_rpt_file in table atp_domain_info. It will be printable by the System Administrator and will be available for viewing from the Report Browser GUI.

Auto Code Order Creation Log Report• This report will be generated by ACO_GEN/ACO_DIST in directory $DATAFILEDIR/aco/rpts with file name specified by field aco_creat_rpt_file in table atp_domain_info. It will be available for viewing from the Report Browser GUI.

Administrative Table Update Log• This report will be generated by the Table Administration GUI in directory $DATAFILEDIR/aco/rpts with file name specified by field aco_tblupd_rpt_file in table atp_domain_info. It will be available for viewing from the Report Browser GUI.

Management Summary Report• This report will be generated by the GUI from the aco_disp table at the time it is requested

by the user.

ACO Shell ScriptsThe following shell scripts are located in the topasrc/bin directory.

Issue: GA-1, July 20109 - 49


• aco_rqst is run on Primary HP Servers that receive and process the code opening request files at the time specified by aco_rqst_cron_time value in the HP Server Domain Information Table. It generates reports related to that process, then prints them to the printer specified in the default_printer value in the HP Server Domain Information Table.

• aco_sched executes processes after ACO_RQST has successfully run on any given day (as indicated by last_rqst_date in the global aco_control table), and updates the scheduled code opening table. If ACO_RQST has not run on a given day, aco_sched re-tries for the number of times specified by aco_sched_limit in the 8950 VAM Domain Information table. The number of minutes that aco_sched delays between re-tries is set in aco_sched_intvl in the 8950 VAM Domain Information Table. After each unsuccessful attempt, this script sends e-mail to the addresses specified in the atp_domain_info table.

• aco_rpts generates code opening disposition reports on each Primary HP Server, transmits them to COTS, and updates the aco_control table on successful FTP of each disposition report. It also prints exception reports for each HP Server in that domain to the printer specified in the HP Server Domain Information Table.

• aco_sortlog sorts Automated Code Opening logs (Order Creation logs and Exception logs) in the sequence: office - code - date.

Issue: GA-1, July 20109 - 5 0


ACO Error CodesThe following tables lists the generated error codes based on the related process, the name of the error file related to the process, the specific error message and an explanation of the message, and the corrective actions to be taken in response to each error message.Error Code Messages and Administrator Actions

Process Error File Message/Explanation ActionsACO_RQST ACO_RQST.err Positive Integer: Start-up failure, no

parsing done.Call Support

ACO_SCHED ACO_SCHED.err c_send to aco_dist failed. aco_dist hasn’t responded to the message sent by aco_sched even though the message was retried 3 times at an interval of 2 min.

Determine if aco_dist is suspended or is down.Bring it back up in either case.

upd_effd_gentoday failed. Updating all rows in aco_sched with gen_today to null failed hence aco_sched null stopped processing

Re-run aco_sched

aco_sched failed with -244. This is a contention problem.

Make sure that aco_sched is run on all the HP Servers, but not all at the same time. Re-run aco_sched.

ACO_DIST ACO_DIST.err -9 DB error-Call Support

ACO_GEN ACO_GEN.err 22222 Check Link

33333 Internal error-Call Support

-81 DB error-Call Support

ACO_POST ACO_POST.err upd_sch_tbl ( ) func failed for orderid:[ACnpanxx-ddmmyy]

Call Support

Issue: GA-1, July 20109 - 51


aco_rqst aco_rqst.err Failed to readatp_domain_info table

Try to run aco_rqst / aco_sched again

Not Primary HP Server. Exit! This is a valid error:aco_rqst does run on non-primary HP Servers

Remote Login can not be null. Exit! Enter remote Login in the HP Server Domain Information table

Remote Password can not be Null. Exit!

Fill in remote password in the 8950 VAM domain table

Can not print Immediate Action Report for HP Server

Check the printer that is specified in the atp_domain table

Failed to updateaco_control table

If aco_control table is not updated with the last run date for aco_rqst, aco_sched will not be run. Re-run aco_rqst script.

aco_sched aco_sched.err Request processing has not yet run today. Exiting!

When aco_rqst runs, it updates aco_control on successful completion.If aco_control is not updated, aco_sched will not run. This script retries to check aco_control entry for the number of times specified in the domain info table, then it exits.Check all e-mails associated with aco_rqst.

aco_sched failed with error code -4, check correspondent error/trace

Possible database errors from aco_sched.

Call Support

Process Error File Message/Explanation Actions

Issue: GA-1, July 20109 - 5 2


aco_rpts aco_rpts.err Could not print exception report for HP Server

When exception report fails to run, determine whether printer setup is correct

Not primary HP Server. Exit! Valid error. Does not run on non-primary HP Servers.

Remote address cannot be NULL. Exit!

Enter remote address in the Domain Information table

Remote password cannot be Null. Exit!

Enter remote password in Domain Information table

Remote login cannot be Null. Exit! Enter remote login in Domain Information table

FTP disposition report failed. Exit! Determine whether login information in HP Server Domain Information table is correct

Process Error File Message/Explanation Actions

Issue: GA-1, July 20109 - 53


ACO Code Opening Disposition CodesThe following tables shows various disposition codes that the ACO Process sets for jobs in the Code Opening Disposition Table (CODT).

Code DispositionREJ1 Order could not be created for growth job because route like and/or rate like

codes were not available.

REJ2 Order could not be created for growth job for other reasons.

REJ3 Order was created and scheduled but rejected by the switch.

REJ4 Order could not be created within the jeopardy interval because rate like or route like code needed to open code had INHIBIT FLAG set toY.

REJ5 Order was created and partially completed in switch but one of the RCs in the order is stuck in transit state. (e.g. shadow database update in 8950 VAM failed for the RC)

REJ6 Order could not be created within the jeopardy interval due to inability to complete verifications because the link was down.

REJ7 Order contained at least one RC that successfully completed in the switch but failed to update the 8950 VAM shadow database.

REJ8 Duplicate order ID

REJ9 Order could not be created within the jeopardy interval because COTS growth job was within the jeopardy interval. (This occurs automatically for several successive days when an office is first turned up for Automated Code Opening.)

SCH Order scheduled for transmission to switch for growth job

CPD Order completed in switch for growth job

CAN Job cancelled by COTS

JPDY Job is in jeopardy and converts to REJ if the condition is not corrected by the jeopardy interval.

REJA Reject code for feature Group I-failure to find a code index value for a toll code. (i.e. route like code is “Non-Toll”)

HOLD Rehome orders automatically generated but not scheduled.

Issue: GA-1, July 20109 - 5 4


ACO Feature ActivationThe following features must be activated on the 8950 VAM HP server via the Feature control menu:

NOTE:Contact the 8950 VAM product support team for the the passwords associated with the features.




— 9) System Commands Menu— 12) 8950 VAM Feature Control Menu— 2) Enable Features




Enable feature?










CODE OPENING - AUTO Feature to configure for automatic ACO.

CODE OPENING - MANUAL 5ESS Feature to configure for manual 5ESS ACO.

CODE OPENING - MANUAL DMS-100 Feature to configure for manual DMS ACO.

Issue: GA-1, July 20109 - 55


ACO Domain Info Configuration1. Log in as int from either the console or a PC via telnet into the L1 machine:



— 10) 8950 VAM Configuration Menu— 6) Update 8950 VAM Domain Information Table


Please read carefully the following important information before attempting to update NVAM Domain Information. No user input data, but the primary host value, is validated or verified in any sense. So please enter only valid values. Not all the fields are required. Some fields are required for AUTO CODE OPENING and some are required for MANUAL CODE OPENING. Please consult CODE OPENING feature documentation for more details on which fields are required for which feature. If a required field is not populated the CODE OPENING feature MAY NOT work properly! If you want to unset an existing value in a field enter "unset" or "UNSET" for that field.

Do you want to continue (Y|N) [D: N] y

• Type y and press <Enter>

Primary host [D: peach]

• Input the <primary 8950 VAM server name> and press <Enter>

Remote IP address [D: 135.112.176.161]

• Input <IP Address> of primary VAM server and press <Enter>

Remote login [D: int]

• Type int and press <Enter>

Remote password [D: int123]

• Type <int_Password> and press <Enter>

Code opening administrator's email #1 [D: int]

• Input <1st_Admin_email> and press <Enter>


• Input <2nd_Admin_email> and press <Enter>


• Input <3rd_Admin_email> and press <Enter>


• Input <sys_Admin_email> and press <Enter>

Link down retry limit [D: 4]

Issue: GA-1, July 20109 - 5 6


• Input the number of times to retry and press <Enter>

Link down retry interval (min) [D: 6]

• Input interval time in minutes to retry and press <Enter>

Number of retries for ftp [D: 4]

• Input <# of FTP> retries, and press <Enter>

Ftp retry interval (min) [D: 10]


Number of retries for ACO schd [D: 4]


ACO sched retry interval (min) [D: 10]


Request cron time (i.e. 00 07 * * *) [D: 15 18 * * *]

• Input the request script time and press <Enter>

Scheduled cron time (i.e. 00 07 * * *) [D: 30 18 * * *]

• Input the scheduled script time and press <Enter>

Reports cron time (i.e. 00 07 * * *) [D: 45 10 * * *]

• Input the reports script time and press <Enter>

Remote directory for request file [D: /rc/data/aco/rqst]

• Leave default values and press <Enter>

Request file name [D: cots_file_als]

• Input requst file name and press <Enter>

Remote directory for ack file [D: /rc/data/aco/rqst]

• Input remote ack directory name and press <Enter>

Remote ack file name [D: ack_file_als]

• Input remote ack file name and press <Enter>

Remote directory for reports [D: /rc/data/aco/rpts]

• Leave default value and press <Enter>

Process log file name [D: aco_log_file]


Immediate action report file name [D: imm_act_rpt]


Disposition report file name [D: aco_disp_rpt]


Exceptions report file name [D: aco_excep_rpt]

Issue: GA-1, July 20109 - 57



Order creation log file name [D: aco_ord_creation_log]


Table update log file name [D: aco_tbl_upd_log]


Management report file name [D: aco_mang_rpt]


Default printer name [D: port]

• Input the default printer on 8950 VAM server and press <Enter>

3. After all the prompts have been answered, you will be prompted to re-confirm the information:

Primary host: "peach"Remote IP address: "135.112.176.161"Remote login: "int"Remote password: "int123"Code opening administrator's email #1: "int"Code opening administrator's email #2: "int"Code opening administrator's email #3: "int"Code opening administrator's email #4: "int"Link down retry limit: "4"Link down retry interval: "6"Number of retries for ftp: "4"Ftp retry interval: "10"Number of retries for ACO schd: "4"ACO sched retry interval: "10"Request cron time: "15 18 * * *"Scheduled cron time: "30 18 * * *"Reports cron time: "45 10 * * *"Remote directory for request file: "/rc/data/aco/rqst"Request file name: "cots_file_als"Remote directory for ack file: "/rc/data/aco/rqst"Remote ack file name: "ack_file_als"Remote directory for reports: "/rc/data/aco/rpts"Process log file name: "aco_log_file"Immediate action report file name: "imm_act_rpt"Disposition report file name: "aco_disp_rpt"Exceptions report file name: "aco_excep_rpt"Order creation log file name: "aco_ord_creation_log"Table update log file name: "aco_tbl_upd_log"Management report file name: "aco_mang_rpt"Default printer name: "port"

Do you want to use the above values? (Y|N) [D: N] y

• Type y and press <Enter>




Issue: GA-1, July 20109 - 5 8


Cross Central ConfigurationCross central configuration is a feature in 8950 VAM Translation Interface application where the user’s GUI has access to all switches from multiple 8950 VAM HP servers. This feature is available for customers whose environment has multiple 8950 VAM HP servers.

Cross Central Feature ActivationThe following features must be activated on the 8950 VAM HP server via the Feature control menu:

NOTE:Contact the 8950 VAM product support team for the the passwords associated with the features.




— 9) System Commands Menu— 12) 8950 VAM Feature Control Menu— 2) Enable Features




Enable feature?









CROSS CENTRAL Feature to configure for X-central in multiple HP server configuration.

Issue: GA-1, July 20109 - 59



Configure Remote Login Capability Make sure that you can remsh from both machines to one another without being prompted for password. This will make the integration steps go smoothly. For customers with the Secure Shell feature, similar steps must be taken for ssh capability.

• It is the responsibility of the 8950 VAM HP server admin to ensure that “remsh” capability exists as user “int” and “root” between the local 8950 VAM Server & the remote 8950 VAM server being configured for cross central.

NOTE:Consult your local UNIX system admin teams for further help on remote login capability.

Configuration Cross Central - Remote Host

Update sqlhosts file4. On the Remote HP Server, run the script “updhostsfls” to update the /etc/hosts,

~informix/etc/sqlhosts and /etc/hosts.equiv for cross central feature as follows:

4.1 Log in as root from either the console or a PC via telnet into the L1 machine of the Remote Host HP Server.

Login: root

Password: <root password>

4.2 Issue the following commands on the Remote HP Server as root:

# /topasrc/bin/updhostsfls A

— When prompted for the Central Name, input the Cross Central hostname.

NOTE:Make sure all the central names are added via this script.

4.3 Verify that the “sqlhosts” files are set correctly.

# cat ~informix/etc/sqlhosts

— In the file, make sure that there is a line for each Cross Central Name

# exit

Sync switch_mach_addr DB table5. Now sync up all the switch information in the sw_mach_addr table on the remote HP server.

[xxxxx-int] /topasrc/bin/swmachaddr

5.1 Another way to sync up all the switch information in the sw_mach_addr table is to perform the following:

[xxxxx-int] /topasrc/bin/cpswmachadd

Issue: GA-1, July 20109 - 6 0


— When prompted, enter local HP Server central name.

Configuration Cross Central - Local Host

Configure LDS table for Cross Central Feature6. Issue the following command on the Local HP Server as int:

[xxxxx-int] /topasrc/bin/var_pass_age CROSSC_LDS

------------------------------------------------------------Cross Central lds flag. Current value is set to: NUse carriage return to terminate response.Enter 'exit' from any prompt to exit.------------------------------------------------------------Set Cross Central lds flag (Y|N) [D:Y]

— If you want to configure the system for Cross Central Feature, input N

— If you do NOT want to configure the system for Cross Central Feature, input Y

ISQL check of sw_mach_addr INFORMIX TableThe Cross Central Feature can only work when the sw_mach_addr INFORMIX table on both the Local and Remote HP Servers are in sync.

7. Perform an isql select to query the sw_mach_addr table as int from both the systems (local and remote host).

Local HP server check (sw_mach_addr)7.1 Issue the following commands on the Local HP Server as int.

[xxxxx-int] isql osps <<!

select * from sw_mach_addr

!

— Your output under the following columns should have switch information for all the centrals.

NOTE:The same switch MUST not be defined on multiple centrals. Please check and remove any additional occurrences.

Remote HP server check (sw_mach_addr)7.2 Issue the following commands on all the Remote HP Server as int.

[xxxxx-int] isql osps <<!

select * from sw_mach_addr

!

Issue: GA-1, July 20109 - 61


— Your output under the following columns should have switch information for all centrals:

Synchronize Workgroup InformationTo ensure that the Cross Central Feature works properly, you will need to verify that the Workgroups from the Local Central are defined in the Remote Central.

• For Detailed Information on Adding Workgroups, please refer to the Section in this chapter on Workgroup Configuration.

8. Perform a query of the Workgroup Information from the Local System as int, you will need to add the same Workgroup Information on the Remote System.



— 11) Workgroup/CLEC Administration Menu— 2) Workgroup/CLEC Administration• Use the “Query” option to query all the workgroups.

NOTE:You should write this information down so that exactly the same Workgroup information can be added to the Remote HP Server.

9. Issue the following steps on each of the Remote HP Server as int to Add the Workgroup Information found in the Local HP Server from previous step.



— 11) Workgroup/CLEC Administration Menu— 2) Workgroup/CLEC Administration• Use the “Add” option to query all the workgroups.

NOTE:The Workgroup information should now be in sync and should be exactly the same in the Remote and Local HP Servers.

Synchronize Switch InformationTo ensure that the Cross Central Feature Works properly, you will need to ensure that all switch information is sync’d across all HP server systems.

NOTE:You can perform this step in any of the Cross-Centralled HP Server Machine.

10. Issue the following commands on the Remote HP Server to sync up all the switch information

Issue: GA-1, July 20109 - 6 2



[xxxxx-int] /topasrc/bin/syncswmachaddr

You may select one of the following options -1) Audit2) Sync sw_mach_addr3) Update sw_mach_addr with updated sw_generic4) EXITPlease enter option number:

— Select option “1” to perform an audit.

— Select option “2” to sync sw_mach_addr table.

— Select option “3” to perform update of switch generics.

— Select option “4” to exit.

Synchronize User Login InformationTo ensure that the Cross Central Feature Works properly, you will need to verify that the User Login Information from the Local Central is defined in the Remote Central.

• You will need to perform the following steps to synchronize the user login information of the Local HP Server into the Remote HP Server.

NOTE:You must perform this step in the Remote HP Server Machine.

11. Issue the following commands on the Remote HP Server to sync up all the login information


[xxxxx-int] /topasrc/bin/cc_synchuser

Do you want to continue? (Y|N) [D: N] yEnter remote central name: <Input the Local Central Name>

11.1 Verify the login have been build at UNIX level.

[xxxxx-int] cat /etc/passwd

11.2 Verify that the login has been built at Menu level:

[xxxxx-int] menu



• Use the “Query” option to query the user information.

Issue: GA-1, July 20109 - 63


Test getallcllis scriptIn order to test the getallcllis utility, and ensure that the cross central configuration is done correctly, you will need to use a sample user login that is built in the system. This information can be found from the /etc/passwd file.

12. Perform the following steps to test the getallcllis script on each of the HP servers configured for cross central.


# su - <Sample_User_Login>

$ getallcllis

— This will output all the Switch CLLI Codes defined in the system.

$ exit

# exit

Issue: GA-1, July 20109 - 6 4


Tunable Parameters ConfigurationThe tunable parameters configuration GUI is used to configure system/application specific parameters in the system .

Access Tunable Parameters Screen

Access ResourceGroups screen via GUI Interface1. Access the VAM launch page via a browser interface & login as int.




— Select Tunable Parameters option

— Click on the the Add/Delete/Update button

Issue: GA-1, July 20109 - 65


Tunable Parameters Options

The following Tunable parameter options are delivered with the system. DO NOT change them!


MoreInfo_INFO This parameter is used to display task Universal Switch Feature Name (USFN) values when using the Task Execution application. As shown in the preceding table, the parameter is mapped to a USFN by placing the USFN name in the parameter value field. There is a set of More Information parameters ranging from MoreInfo_INFO1Prefix through MoreInfo_INFO9Suffix that allows 10 USFN values to be displayed.

• By requesting a Task Execution query with more information, the values are displayed within the order summary screen.

ExpireCPD This parameter indicates the number of days that a completed task order is retained without being purged from the database. The range of allowable values is 1 through 45 days. The cron job reads this value before determining whether to purge a completed order from the database.

ExpireERR This is the same as ExpireCPD. It is for orders with ERR status.

ExpireREJ This is the same as ExpireCPD. It is for orders with REJ status.

ExpireCAN This is the same as ExpireCPD. It is for orders with CAN status.

ExpireVFY This is the same as ExpireCPD. It is for orders that have VFY status.

UserMaxQuery This parameter specifies the number of outstanding task queries executing at the same time for each user instance.

• The value ranges from 0 (no limit is set) through 4. The default value is 0.noOfRetriesForRCB

This parameter specifies the maximum number of retry attempts allowed for resource busy. A resource busy condition is determined by the switch failure response message the text that matches the text value contained in the USFN_value remap table entries 'retry1' or 'retry2' where:

• retry1 [retry RC only once regardless of maximum setting]• retry2 [retry RC up to RCB_retries maximum attempts])

— The default value of this parameter is 5 retries.

retryIntervalForRCB

This parameter indicates the amount of time to set the timer for resending an RC to a switch after a status of "resource busy" is detected.

• The default value of this parameter is 5 minutes.RCTimeOutInterval

This parameter indicates the amount of time to set the timer for sending "status_rqst" to the switch after the RC timer expires.

• The default value for this parameter is 5 minutes.

Issue: GA-1, July 20109 - 6 6


ReptExpiredTime

This parameter indicates the amount of time to set the timer for resending a query request to an EMM after the report timer expires.

• The default value of this parameter is 5 minutes.num_ldshndlrs This parameter specifies the number of LDS action handler processes that can process

order requests.

NBI_EXPIRE_LOG

This parameter controls the purging interval for the set of error log and trace files created by the SOAP NBI feature.

• The default value is 45, (Min value = 1 and Max value = 90).• This parameter is applicable only for the SOAP_NBI optional feature.

NBI_ORDQUERY_SIZE

This parameter controls the maximum number of orders that will be returned in a query request.

• The default value = 1000, (Min value = 1 and a Max value = 2000). • This parameter is applicable only for the SOAP_NBI optional feature.

NBI_INIT_POOLSIZE

This parameter specifies the initial set of backend server connections created by the SOAP NBI Server.

• The default value =5 (Min value =1 and Max value = NBI_MAX_POOLSIZE).

• This parameter is applicable only for the SOAP_NBI optional feature.NBI_MAX_POOLSIZE

This parameter specifies the maximum number of backend server connections created by the SOAP NBI Server at any point of time.

• The default value = 15, (Min value = 1 and Max value = 20).• This parameter is applicable only for the SOAP_NBI optional feature.

upbatch_cron This parameter specifies the value which is to be used for UBIC to start the start_ubic through crontab process.

• The default value = 0015.


Issue: GA-1, July 20109 - 67


Add Tunable Parameters Entry1. Access Tunable Parameters screen via GUI Interface as shown previously

— Refer to Heading “Access Tunable Parameters Screen”.

2. You will need to input the following information to add the Tunable Parameter entry into the system.

— Parameter Name: The name of parameter .

— Parameter Value: Value associated with parameter name.

! WARNING:All information for Parameter Name & Parameter Value must be obtained from the Alcatel-Lucent Product team for the specific activity being performed.

3. Click the “Add” button to add the Tunable Parameter in the system.

— Click the “Return to MainTunableParameter screen” option on the bottom GUI screen to return to previous GUI screen.

— Click “Task Toolkit Admin Menu” hyper-link to start over.

Query Tunable Parameters Entry1. Access Tunable Parameters screen via GUI Interface as shown previously


— Click on the the Filter button

— (If you already clicked on Add/Del/Update button, click the Return to Main Tunable Params Screen button & then click on the Filter button.

2. You may query on any of the following fields to query the data or not filter on any data.

— Parameter Name: Input Parameter Name and then from the pull down list , select either equal or NotEqual

— Parameter Value: Input Parameter Value and then from the pull down list , select either equal or NotEqual.

3. Click the “Submit” button to query the Tunable Parameters in the system.



Issue: GA-1, July 20109 - 6 8


Update Tunable Parameters Entry1. Access Tunable Parameters screen via GUI Interface as shown previously


2. You may query for the specific record to update via the following steps:



3. Once the list of query result is displayed, click on the entry to update.

— Parameter Name: Update Parameter Name as needed.

— Parameter Value: Update Parameter Value as needed.

4. Click the “Update” button to update the Tunable Parameters in the system.



Delete Tunable Parameters Entry1. Access Tunable Parameters screen via GUI Interface as shown previously


2. You may query for the specific record to delete via the following steps:



3. Once the list of query result is displayed, select the entry to display the specific entry.

4. Click the “Delete” button and answer the following prompt to delete the Tunable Parameter entry:

“Are you sure you want to delete this Tunable Parameter?”

— click on Okay button.





10 Task Toolkit: Configuration & Management

Overview

The purpose of this chapter is to provide information about 8950 VAM application TaskToolkit Management. The following topics will be covered

• Complete TaskToolkit Management

Issue: GA-1, July 20101 0 - 2


Task ToolKit ManagementThis chapter provides information about performing the following tasks in 8950 VAM. setting up and initializing multiple Recent Change Action Table database environments.

• Loading and unloading tasks from the RCAT database.• Loading and unloading global data from the RCAT database.• Retrieving and decrypting task and global data from the archive files provided in the starter

package.• Merging tasks• Purging the RCAT database.• Dumping and restoring the RCAT database.

Task Management Terminology

Task Packaging • Task Packaging describes the unloading of task definition data so that it can be moved between

Task Toolkit databases.

RCAT Database• The Recent Change Action Table (RCAT) database contains the task definitions used by the

Task Executor to create recent changes for network element provisioning. The data contained in these database tables is of two types:

Global Data (Task-specific)• Global data is the information that applies to all tasks in the database. Examples of global data

include switch type information, methods information, and central-specific information such as system tuning parameters and activated features.

Global data tables• The following database tables contain global data: querytask, query_field, lds_tgi, lds_type.

— The querytask and query_field tables contain both global and task-specific data. Method data is treated as global data, while query data is treated as task-specific.

Customer-specific global data tables• The following database tables contain data that is global to all tasks in the database but specific

to a particular customer: feat_coms, feat_name, treatmenttrans, respdatamap, tunableparameter, usfn_valuemap, Task-specific data.

— Task-specific data is the data that defines a particular task. This data is available in database tables such as rc_task, rc_query, usfn_valueremap, and label.

Packaging Strategies

Issue: GA-1, July 201010 - 3


• Task packaging involves unloading data from the database tables into flat files. These files can then be moved and loaded into another database. There are two packaging strategies:

RCAT Packaging• RCAT packaging involves loading and unloading all of the data, both global and task-specific,

contained in the database. This is done using the rcat_dump and rcat_restore tools.

Single-Task Packaging• Single-task packaging is the strategy that allows for unloading and moving the data for one or

more tasks without having to dump the entire RCAT database. — You can move tasks between databases that have the same global data using the unload_task

and load_task tools.

— You can also move global data between databases using the unload_globaldata tool and load global data option of the cv_tguidb tool.

Starter packages• The Task Toolkit is installed with a starter package of task definitions. This package contains a

set of sample tasks that can be used as working models for customers to develop their own business-specific tasks using Task Builder.

— All Task Toolkit customers receive the sample task package. In addition, customers may contract with Alcatel-Lucent to build custom task packages specific to their business rules.

— Starter packages contain encrypted archives of task definition files (.task), data (.dat) files and control (.ctl) files. These are decrypted and made ready for loading into the database using the enable_globaldata and enable_tasks tools.

• The starter package files include:— tasks.a archive containing the sample task and any other contracted tasks.

— global_rcat.info A file containing the global archives.

— global_global.a The archive containing global data.

— global_SAMPLE.a The archive containing global data specific to the sample tasks

— global_[cust_key].a The archive containing customer-specific global data. The [cust_key] is a customer-specific key provided to you by Alcatel-Lucent along with your new installation or upgrade software.

• The sample starter package has been built according to the single-task packaging strategy designed to accommodate task development through the Task Builder.

— Other starter packages may have been developed using the RCAT packaging strategy and delivery of the tasks contained in them requires reinstalling the entire database.

— If you are using one of these starter packages, you will need to migrate to the single-task packaging environment.

Setting up multiple environments

Issue: GA-1, July 20101 0 - 4


• When building tasks, it is strongly recommended that you do not build tasks in the same database being used to execute tasks, as this can lead to unexpected results if a task builder is modifying shared objects when a task executor is attempting to execute a task.

— To facilitate setup of multiple environments, use the ttk_multienv tool. This will setup another database called tbldrdb in addition to the tgui01 database.

— You can then build tasks in tbldrdb and when they are tested and ready, migrate them to tgui01 where task executors will have access to them.

— Migration can be done using either the rcat_dump and rcat_load or the single-task packaging tools.

Managing Task Development• The following is a high-level view of the task development process using the single-task

packaging strategy. — Load the Task Builder database tbldrdb with task definition data delivered with the installation

or upgrade of Task Toolkit. The enable_globaldata and enable_tasks tools are used to retrieve the task and global data from the starter package archives.

— Global data must be loaded first, since this data is required for the tasks to load properly. This can be done using the cv_tguidb tool. If a clean database is desired, the purge option of this tool can be used to delete all global and task data from the current tbldrdb database.

— Task data is loaded next. The user can load all delivered tasks using the load_all_tasks tool or load individual tasks retrieved from the archive using the load_task tool. Custom tasks can also be loaded at this point.

— Develop and test tasks using the Task Builder. Modifications to tasks loaded from the archives or another database can also occur at this point.

— Move tasks from the development environment (tbldrdb) to the production environment (tgui01).

• Individual tasks and global data can be moved using the single-task management tools.

• A task can be unloaded at the RCAT level and merged with a similar task for a different switchversion using the merge_tasks tool.

• The entire database can be moved using the rcat_dump and rcat_restore tools.

Issue: GA-1, July 201010 - 5


Single Task PackagingSingle-task packaging is the strategy that allows for unloading and moving the data for one or more tasks without having to dump the entire RCAT database.

Load Starter PackageThe Task Toolkit is installed with a starter package of task definitions. This package contains a set of sample tasks that can be used as working models for customers to develop their own business-specific tasks using Task Builder.

All Task Toolkit customers receive the sample task package. In addition, customers may contract with Alcatel-Lucent to build custom task packages specific to their business rules.



2. Perform the following step to install the Starter Package:

[xxx-int] /Install_tgui/cv_tguidb

CONNECTVU-APX Customer name is set to "<CustomerName>".Is this correct? (Y|N) [D: N] y . . . . .

2.1 Answer the following prompt to Load starter package:

Task ToolKit Database Management1) Exit2) Perform Task ToolKit Database Migration3) Load Task Starter Package into Task ToolKit Database4) Load Permissions Starter Package into Task ToolKit Database5) Purge Global and Task Data from Task Tool Kit Database6) Load Single Task Global Data into Task Tool Kit DatabaseSelection [1-6]

— Select option: 3)Load Task Starter Package into Task ToolKit Database

— Then, select option 4) Load Permissions Starter Package into Task ToolKit Database

Do you want to continue with loading permissions data? (Y|N) [D: N] y

— Select option 1) Exit

— [xxx-int] exit

Issue: GA-1, July 20101 0 - 6


Load Sample PackageThe sample starter package has been built according to the single-task packaging strategy designed to accommodate task development through the Task Builder.




[xxx-int] upd_customer “SAMPLE”

3. Issue command that will extract *.dat and *.ctl files from the global_global.a archive.

[xxx-int] cd /tgui/TASKS

[xxx-int] enable_globaldata

[xxxx-int] ls *.a

— Ensure *.a files are there in system.

4. Perform the following step to install the SAMPLE RCATs/TASKs.

[xxxxx-int] /Install_tgui/cv_tguidb

CONNECTVU-APX Customer name is set to "SAMPLE".Is this correct? (Y|N) [D: N] y

5. Answer the following prompt to Load starter package:

Task ToolKit Database Management1) Exit2) Perform Task ToolKit Database Migration3) Load Task Starter Package into Task ToolKit Database4) Load Permissions Starter Package into Task ToolKit Database5) Purge Global and Task Data from Task Tool Kit Database6) Load Single Task Global Data into Task Tool Kit DatabaseSelection [1-6]

— Select 6) Load Single Task Global Data into Task Tool Kit Database

Do you want to load from the (A)rchive Package or (U)nloaded data? (A|U) [D:A] A

— Then, Select option 4) Load Permissions Starter Package into Task ToolKit Database

Do you want to continue with loading permissions data? (Y|N) [D: N] y

— Select option 1) Exit

6. Issue command that will extract *.task files from the Tasks.a archive & Load the tasks:

[xxxx-int] enable_tasks

[xxxx-int] load_all_tasks

7. Re-set the customer name to original name:

[xxx-int] upd_customer “<Original_Customer_Name>”

Issue: GA-1, July 201010 - 7


Single Task ManagementSingle-task management is the strategy that allows for unloading and moving the data for a single task without having to dump the entire RCAT database.

Unload a TaskThe unload_task tool extracts task definition data from the database for the RCAT data for a specified task name and writes that task definition data to a flat file. It can also unload the group container tasks associated with the task name.

• The unload_task tool does not delete the data from the database. By default, unload_task performs task cleanup but there is an option to bypass it.

• The unload_task tool unloads data from a set of tables that contain information related to task definition.

• In addition, unload_task reinstates any string-named objects that were renamed when the task was previously loaded by load_task to their original names.

• Objects with numeric names that were renamed will not be restored.



2. Issue the following commands to unload the task:

[xxx-int] mkdir -p /tmp/TASKS

NOTE:Run unload_task from a directory where task development is being performed.

[xxx-int] cd /tmp/TASKS

[xxx-int] unload_task [-q <qualcode>/<qualvalue>] <task_name> <database>

— where -q <qualcode>/<qualvalue> (refer to table above).

— <task_name> is the name of the task.

— <database> is the name of database to unload from (tgui01 = default or tbldrdb).

Sample Command:[xxx-int] unload_task -q ST/5ESS APOTS tgui01 (Example Command)


Qualcode qualvalue

ST (switch Type) 5020MGC, 5ESS, DMS, FS5K, MGCF, SONUS

TGI (Type Generic Issue) 5120, 5130l, 5150, 5140, 5165

LDS (tgui switch name) <actual_Switch_Name>

Issue: GA-1, July 20101 0 - 8


17:45:40 unload_task:: Started unloading ....

unload_task: Unloading rcats for qual code/value [ST/5ESS] for task [445567] from database [tgui01]unload_task:Task [445567] doesn't exist in the database.[peach-int] unload_task -q ST/5ESS APOTS tgui01 17:46:08 unload_task:: Started unloading ....

unload_task: Unloading rcats for qual code/value [ST/5ESS] for task [APOTS] from database [tgui01]17:46:08 unload_task:APOTS: Extracting table rc_task....................................................................................................................................................................+++ Unloaded at rcat level Rename file [APOTS.task] before unloading another rcat of same task...Unloaded task has been cleaned up successfully...17:46:16 unload_task:APOTS: Completed unloading successfully .....

3. You will see the following output files; three output files and one directory are created with the tool:

• <taskName>.unload.log is the output log file.• <taskName>.unload.err is the output error file.• <TaskName>.task is the output file that contains the names of the tables processed

together with counts of rows unloaded.• <taskName> (Directory) contains files resulting from the cleanup.


[peach-int] pwd/tmp/TASKS[peach-int] ls -ltotal 108drwxr-xr-x 5 int rcadm 1024 Apr 22 17:53 APOTS-rw-r--r-- 1 int rcadm 43227 Apr 22 17:53 APOTS.task-rw-r--r-- 1 int rcadm 0 Apr 22 17:53 APOTS.unload.err-rw-r--r-- 1 int rcadm 4294 Apr 22 17:53 APOTS.unload.log-rw-r--r-- 1 int rcadm 15 Apr 22 17:53 label.log-rw-r--r-- 1 int rcadm 62 Apr 22 17:53 log.22691-rw-r--r-- 1 int rcadm 8 Apr 22 17:53 purge.log-rw-r--r-- 1 int rcadm 920 Apr 22 17:53 results-rw-r--r-- 1 int rcadm 998 Apr 22 17:53 useless.log

4. Issue the following command to restart the ldshndlr & SOReqHdlr.

[xxx-int] run_rapsim LDS

[xxx-int] run_rapsim RCAT

[xxx-int] exit

Issue: GA-1, July 201010 - 9


Load a TaskThe load_task tool tool reads data from a flat file that the unload_task tool created and loads that data into the RCAT database. The load_task tool loads only one task at a time.

The load_task tool resolves naming conflicts by renaming objects if necessary, as follows:

• For names that are strings, a new name is created by prefixing the old name with “zz_” and suffixing it with an “_” followed by a five digit number. Template ID fields are an exception.

— A new template id name is generated by extracting the template name substring, renaming as specified for generic string names, and spliced with the qualifier code/qualifier value portion to obtain a new name that conforms to the convention for template IDs.

— The old name might have to be truncated to accommodate the prefix and suffix strings. If a task that has renamed objects is subsequently unloaded, unload_task restores the original names of these objects while writing to the task file.

• For names that are numeric, a new name is generated as a number that is one greater than the highest number existing in the database (with a minimum value of 10001).

— Renamed numeric objects are not restored to their original names when the objects are unloaded.



2. Issue the following commands to load the task:


NOTE:Ensure that the task being loaded exists on the appropriate directory.

[xxx-int] load_task [-u] [-c] <OldTaskName> <NewTaskName> <database>

— where -u updates the database. If -u is omitted, the tool runs in report-only mode and does not update the database.

— where -c prevents (USFN) Universal Switch Feature Name conflicts.

— <OldTaskName> is the name of task that was unloaded via unload_task tool.

— <NewTaskName> is the new name of the task that you wish to give.

— <database> is the name of database to unload from (tgui01 =default or tbldrdb).

Sample command:[xxx-int] /tgui/bin/load_task -u -c APOTS NewAPOTS tgui01 (Example Command)


18:50:51 load_task: Initializing ...18:50:51 load_task: Reading task file ...18:50:56 load_task: Dumping task data to log file ...18:50:56 load_task: Checking qualifier codes and values ...

Issue: GA-1, July 20101 0 - 1 0


18:50:56 load_task: Checking dangles ...18:50:57 load_task: Checking orphans ...18:50:58 load_task: Pre-processing task data ...18:50:58 load_task: Updating TN type label to that of the new task name ...18:50:58 load_task: Purging old data ...18:50:58 load_task: Checking conflicts ...18:51:02 load_task: Post-processing task data ...18:51:02 load_task: Dumping task data to log file ...18:51:03 load_task: Checking dangles ...18:51:04 load_task: Checking orphans ...18:51:04 load_task: Writing task data to database ...load_task: Done


• <NewTaskName>.load.log is the output log file.• <NewTaskName>.load.err is the output error file.• <NewTaskName>.load.trc is the output trace file.


[peach-int] pwd/tmp/TASKS[peach-int] ls -l-rw-r--r-- 1 int rcadm 111 Apr 22 18:51 NewAPOTS.load.err-rw-r--r-- 1 int rcadm 2024 Apr 22 18:51 NewAPOTS.load.log-rw-r--r-- 1 int rcadm 903027 Apr 22 18:51 NewAPOTS.load.trc




[xxx-int] exit

Issue: GA-1, July 201010 - 11


Merge a TaskThe merge_tasks tool merges two .task files containing data for two tasks with the same names but different switch versions by merging RCAT-related information. This merged .task file is then loaded into the database. This tool is dependent on the load_task and unload_task tools for its execution.

The tool is designed to load and merge both tasks on one database (input database) and unload the merged task to another database (output database). When the tool executes, it will prompt you for the names of these databases. The default values are tbldrdb for the input database and tgui01 for the output database.

Merge Tasks Tool Algorithm

The following steps are performed by the merge_tasks tool. The number in braces after each step indicates the number to be used with the -s option if you want the algorithm to begin at that step.

Merger Tasks Tool Assumptions

The following assumptions, recommendations, and restrictions apply to the use of the merge_tasks tool:

• This tool should be used in a multi-environment, with the two tasks merged in the tbldrdb database and the merged task loaded to the tgui01 database.

• The task name to be used for the merged task is on the first line of <taskName1>.task• The two files must have the same task name contained within the file.

-s Value Option Detail

10 Runs load_task to load the task (task 1) from the <taskName1>.task file

20 Notes the task number for task 1 from the rc_task table

30 Renames the task in <taskName2>.task (task 2) to some arbitrary name and changes all task name-related entries in <taskName2>.task accordingly, including entries in tables rc_task, label, upstreamtrans (requesttype).

40 Runs load_task to load task 2 from <taskName2>.task

50 Changes the task number of task 2 to that of task 1 (as noted in Step 2) in the rcat and lds_typesubtask tables, if either the qualifiercode or the qualifiervalue of the RCATs in task 2 are different from task 1

60, 65 Runs unload_task to unload task 1. The RCATs should now be merged & Runs load_task to load the merged task file <taskName1>.task into the database

65 Runs unload_task to unload task 1. The RCATs should now be merged. If you run the merge_tasks tool with the -s 65 option, only Step 6 will be executed; if you run it with -s 60, both Step 6 and Step 7 will be executed[60, 65]

70 Runs load_task to load the merged task file <taskName1>.task into the database

Issue: GA-1, July 20101 0 - 1 2


• Since the second task is renamed T<taskName1>_new as part of the process, there must not be a task with the same name on the database where the tasks are being merged.

• There can be only one label of type TN with the task name in the entries of the label table in <taskName2>.task

• There can be only one entry with the task name in the rc_task and upstreamtrans tables in <taskName2>.task






[xxx-int] merge_tasks [-s <num>] <TaskName1>.task <TaskNames>.task

— -s <num> designates the number of the step in its’ process where merge_tasks will begin. Using this option, you can restart the process where needed if an error should occur. Allowable values for <num> are 10, 20, 30, 40, 50, 60, 65, 70.

— <TaskName1>.task is the file containing task data, including the family name and help data you want the merged task to have.

— <TaskName.2>task the file containing task data to be merged.


• merge_tasks<processID>.log is the tool output log file.• temp<processID>.log is the log file.• temp<processID>.err is the error log file.• temp<processID>.out is the output log file.4. Issue the following command to restart the ldshndlr & SOReqHdlr.



[xxx-int] exit

Issue: GA-1, July 201010 - 13


Deep Delete TasksUse the Deep Delete shell level tool to completely remove the task data from the system.






[xxx-int] DeepDelete_Task -t <TaskName> -d [tbldrdb|tgui01] -r

— -t <TaskName> is the name of task to delete.

— -d [tbldrdb|tgui01] is the database name..

— -r an optional parameter that generates a report with out any delete action. (Preview mode).




[xxx-int] exit

Issue: GA-1, July 20101 0 - 1 4


ALL Tasks ManagementAll-tasks management is the strategy that allows for unloading and moving the data for all tasks without having to dump the entire RCAT database.

Unload All TasksThe unload_all_tasks tool creates one or more flat files for each task named within a list. The list is contained within a file named /tgui/TASKS/unload_list.d. If this file does not exist, the command unload_all_tasks will create the file with a list of tasks that reside within the indicated database.



2. Issue the following commands to unload the task:


[xxx-int] unload_all_tasks <database>

— <database> is the name of database to unload from (tgui01=default or tbldrdb).

Sample Command:[xxx-int] unload_all_tasks tgui01 (Example Command)


unload_all_tasks: No unload_list.d file exists. Will query the databaseunload_all_tasks: and create an unload_list.d file.unload_all_tasks: started [Thu Apr 23 13:53:57 EDT 2009]13:53:57 unload_task:: Started unloading .... unload_task: Unloading all rcats for task [ACXGP5ESS] from database [tgui01]13:53:57 unload_task:ACXGP5ESS: Extracting table rc_task13:53:57 unload_task:ACXGP5ESS: Extracting table rcat Found RCAT for qualCode[ST],qualValue[5ESS] 13:53:57 unload_task:ACXGP5ESS: Extracting table taskfamily13:53:57 unload_task:ACXGP5ESS: Extracting table rcat_query13:53:57 unload_task:ACXGP5ESS: Extracting table rcat_query_mapping13:53:57 unload_task:ACXGP5ESS: Extracting table querytask....................................................................................................................................................................13:56:14 unload_task:VFY_POTS: Extracting table regexpcheck13:56:14 unload_task:VFY_POTS: Extracting table regexpitem13:56:14 unload_task:VFY_POTS: Extracting table label...Unloaded task has been cleaned up successfully...13:56:19 unload_task:VFY_POTS: Completed unloading successfully ..... unload_all_tasks: unload_task was successful for task VFY_POTSunload_all_tasks completed

Issue: GA-1, July 201010 - 15


3. You will see the following output files; three output files and one directory are created with the tool for each task unloaded:

• /tgui/TASKS (Directory) contains source data from the unload.• <taskName>.unload.log is the output log file for the specified task.• <taskName>.unload.err is the output error file for the specified task.• <taskName>.task is the output file that contains the names of the tables processed

together with counts of rows unloaded.• unload_all_tasks.log is the output log file for all tasks.• unload_list.d is the file that contains list of all tasks being unloaded.


[peach-int] pwd/tgui/TASKS[peach-int] ls -l[peach-int] pwd/tgui/TASKS[peach-int] ls -ltotal 1658drwxr-xr-x 5 int rcadm 1024 Apr 23 13:54 ACXGP5ESS-rw-r--r-- 1 int rcadm 18635 Apr 23 13:54 ACXGP5ESS.task-rw-r--r-- 1 int rcadm 0 Apr 23 13:53 ACXGP5ESS.unload.err-rw-r--r-- 1 int rcadm 4543 Apr 23 13:54 ACXGP5ESS.unload.logdrwxr-xr-x 5 int rcadm 1024 Apr 23 13:54 ACXLN5ESS-rw-r--r-- 1 int rcadm 23086 Apr 23 13:54 ACXLN5ESS.task-rw-r--r-- 1 int rcadm 0 Apr 23 13:54 ACXLN5ESS.unload.err-rw-r--r-- 1 int rcadm 4545 Apr 23 13:54 ACXLN5ESS.unload.log....................................................................................................................................................................-rw-r--r-- 1 int rcadm 1643 Apr 23 13:56 unload_all_tasks.log-rw-r--r-- 1 int rcadm 786 Apr 23 13:53 unload_list.d-rw-r--r-- 1 int rcadm 230 Apr 23 13:56 useless.log

NOTE:Once the unload is complete, you may bundle up the directory (tar, cpio, ftp, rcp, etc) to install elsewhere on another system.

Issue: GA-1, July 20101 0 - 1 6


Load All TasksThe load_all_tasks tool loads all tasks into the specified database, which is tgui01 by default. It does this by first reading the list of tasks within the file /tgui/TASKS/tasks_list.d. It then calls load_task to load the task data into the database. All view tables are updated for task execution by default.





[xxx-int] load_all_tasks <database>

— <database> is the name of database to load from (tgui01=default or tbldrdb).

Sample Command:[xxx-int] load_all_tasks tgui01 (Example Command)


load_all_tasks: No load_list.d file exists. Will query the databaseload_all_tasks: and create an load_list.d file.load_all_tasks: started [Thu Apr 23 13:53:57 EDT 2009]13:53:57 load_task:: Started loading .... load_task: loading all rcats for task [ACXGP5ESS] from database [tgui01]13:53:57 load_task:ACXGP5ESS: Extracting table rc_task13:53:57 load_task:ACXGP5ESS: Extracting table rcat Found RCAT for qualCode[ST],qualValue[5ESS] 13:53:57 load_task:ACXGP5ESS: Extracting table taskfamily13:53:57 load_task:ACXGP5ESS: Extracting table rcat_query13:53:57 load_task:ACXGP5ESS: Extracting table rcat_query_mapping13:53:57 load_task:ACXGP5ESS: Extracting table querytask....................................................................................................................................................................13:56:14 load_task:VFY_POTS: Extracting table regexpcheck13:56:14 load_task:VFY_POTS: Extracting table regexpitem13:56:14 load_task:VFY_POTS: Extracting table label...loaded task has been cleaned up successfully...13:56:19 load_task:VFY_POTS: Completed loading successfully ..... load_all_tasks: load_task was successful for task VFY_POTSload_all_tasks completed

3. You will see the following output files; three output files and one directory are created with the tool for each task loaded:

• /tgui/TASKS (Directory) contains source data from the load.• <taskName>.load.log is the output log file for the specified task.• <taskName>.load.err is the output error file for the specified task.

Issue: GA-1, July 201010 - 17


• <taskName>.task is the output file that contains the names of the tables processed together with counts of rows loaded.

• load_all_tasks.log is the output log file for all tasks.• load_list.d is the file that contains list of all tasks being loaded.


[peach-int] pwd/tgui/TASKS[peach-int] ls -l[peach-int] pwd/tgui/TASKS[peach-int] ls -ltotal 1658drwxr-xr-x 5 int rcadm 1024 Apr 23 13:54 ACXGP5ESS-rw-r--r-- 1 int rcadm 18635 Apr 23 13:54 ACXGP5ESS.task-rw-r--r-- 1 int rcadm 0 Apr 23 13:53 ACXGP5ESS.load.err-rw-r--r-- 1 int rcadm 4543 Apr 23 13:54 ACXGP5ESS.load.logdrwxr-xr-x 5 int rcadm 1024 Apr 23 13:54 ACXLN5ESS-rw-r--r-- 1 int rcadm 23086 Apr 23 13:54 ACXLN5ESS.task-rw-r--r-- 1 int rcadm 0 Apr 23 13:54 ACXLN5ESS.load.err-rw-r--r-- 1 int rcadm 4545 Apr 23 13:54 ACXLN5ESS.load.log....................................................................................................................................................................-rw-r--r-- 1 int rcadm 1643 Apr 23 13:56 load_all_tasks.log-rw-r--r-- 1 int rcadm 786 Apr 23 13:53 load_list.d-rw-r--r-- 1 int rcadm 230 Apr 23 13:56 useless.log

4. Once the load is complete, you may bundle up the directory (tar, cpio, ftp, rcp, etc) to install elsewhere on another system.Issue the following command to restart the ldshndlr & SOReqHdlr.



[xxx-int] exit

Issue: GA-1, July 20101 0 - 1 8


RCAT Database ManagementRCAT database management is the term used to describe packaging and moving of the entire task database from one environment to another on the same HP server or across servers.

The rcat_dump and rcat_restore tools are used to unload all of the data from a task database and reload it to another task database, either on the same server or on another server.

• The rcat_dump tool will unload data to a tape, which can then be used to move the data to another server.

— When moving data between databases on the same server, as for example when you move data between the tgui01 and the tbldrdb environments, you can also choose to use the -notape option.

Using rcat_dump -notape will put the resulting data files in a local file system on the same server. From there, they can be restored to the desired database on that server using the rcat_restore -notape tool.

When the rcat_dump and rcat_restore tools are used, a successfully restored task database:

• is identical to the task database from which data was dumped if it was restored to the same server.

• is identical, except for server-specific data if a restore across servers was performed.

RCAT Database Save (Tape)1. Log in as int from either the console or a PC via telnet into the Live (L1) source HP Server machine:


2. Setup the Task Toolkit environment as follows:

[xxxxx-int] cd /tgui/tgserver/aop14.7/asos/ANCMi*/oam/config_data/maa/

[xxxxx-int] . ./app_setup (do not forget the leading dot)

3. Issue the following command to stop TaskToolKit application:




4. At this point, you must make a decision on which database to unload to tape:

Tgui01 Database Save - Tape

Issue: GA-1, July 201010 - 19


4.1 To unload the TaskToolKit database, run the following:

[xxx-int] /tgui/bin/rcat_dump -U

Task Builder Database Save - Tape4.2 To unload the Task Builder database, run the following:

[xxx-int] /tgui/bin/rcat_dump -N


rcat_dump: Unloading rcat database to the file system. Please wait.Please insert a blank writeable tape in the appropriate tape drive.


Press RETURN to continue:

— Press <CR> to continue.


— Select the number corresponding to the tape drive and press <CR> to continue.


rcat_dump: Copy to tape succeeded."

6. Once the tape is created successfully, it can be used to restore the tasks onto another VAM server and/or VAM database. (Refer to RCAT Restore options).

7. Issue the following command to re-start the TaskToolKit application.




Issue: GA-1, July 20101 0 - 2 0


RCAT Database Save (File System)The following steps should be used to move the entire set of tasks from one database to another database on another HP server and/or system database.

• Unload Source Directory: $ANCM_ROOT/data/RCAT/Update

Once the unload is complete, the admin can transfer that data to another system via (rcp,ftp, tar, etc) to be restored onto the new system.










4. At this point, you must make a decision on which database to unload to File System:

Tgui01 Database Save - FileSystem4.1 To unload the TaskToolKit database, run the following:

[xxx-int] /tgui/bin/rcat_dump -U -notape

Task Builder Database Save - FileSystem4.2 To unload the Task Builder database, run the following:

[xxx-int] /tgui/bin/rcat_dump -N -notape


rcat_dump: Unloading rcat database to the file system. Please wait.rcat_dump: tables successfully unloaded to file system.

5. Once the data is unloaded, the data will reside in the following directory.


Issue: GA-1, July 201010 - 21


• The data can be used to restore the task environment onto another VAM system and/or VAM database. (Refer to RCAT Restore options).





Issue: GA-1, July 20101 0 - 2 2


RCAT Database Restore (Tape)1. Log in as int from either the console or a PC via telnet into the Live (L1) source HP Server machine:









4. To restore the Task database, run the following steps:

[xxx-int] /tgui/bin/rcat_restore


! WARNING:If the following question is answered incorrectly, the script will overwrite the specific information on the machine resulting in a loss of data on the existing system.

Were the tasks that are being restored dumped from another central?

— If the rcat_unload was done on the same VAM server, type no and press <CR>. .

— If the rcat_unload was done on a another VAM server, type yes and press <CR>. .

Enter the database name to which the tasks will be restored.

— To restore the Task Toolkit database, type tgui01 and press <CR>.

— To restore the Task builder database, type tbldrdb and press <CR>.





Issue: GA-1, July 201010 - 23


RCAT Database Restore (File System)The following steps should be used to restore the entire set of tasks via File System.


Prior to starting thie process, the Source data must be transferred from the source VAM server to the target VAM server via (rcp,ftp, tar, etc) to be restored onto the new system. It is recommended that you transfer the data onto the same directory structure.










4. To restore the Task database, run the following steps:

[xxx-int] /tgui/bin/rcat_restore -notape


Enter the database name to which the tasks will be restored.

— To restore the Task Toolkit database, type tgui01 and press <CR>.

— To restore the Task builder database, type tbldrdb and press <CR>.





Issue: GA-1, July 20101 0 - 2 4


Task ToolKit PermissionsPermissions administration is a set of functions for managing the use of 8950 VAM activities and resources. The permissions structure allows a grouping of users into a set of defined access permissions for a set of resource types via switches, printers, tasks, admin, reservations, service order, sysadmin.

• Activities are grouped by type within task groups• Resources are grouped within resource groups. • Each task group is mapped to one or more resource groups. • The administrator assigns users to specific task groups based on their roles and responsibilities.

In this way, permissions administration provides the means to control the use of a 8950 VAM system.

1. Relate users to Work/Task Groups.• Done via “adduser” via User Admin GUI

Users

Work/Task Group

Resource Groups

Resources

2. Relate Work/Task Group to Resource group.

• Done via “Relate TASKGrp & RsrcGrp” from Permissions Admin GUI

3. Relate Resouce Group to Resources.

• Done via “Relate RsrcGrp & Rsrc” from Permissions Admin GUI

Issue: GA-1, July 201010 - 25


Task Permissions TerminologyResourcesResources are differents elements in the system that can be either system defined and/or user defined elements. They are classified via resource type into one of the following category and can be assigned are

• Admin:Activities an application administrator can perform (permadmin, taskadmin, tunableadmin).

• Printer: User defined.• Reservation: Not Used (System Defined)• Service order: Types of service orders a user can execute for the Service Order user interface

(ForceComplte, GroupPermsOnly,TaskFamily, TaskOrderSummary,EditRC).• Switch: User defined during switch add• Systemadmin: Activities a system administrator can perform (Unix).• Task: Recent Change Action Tables (RCATs) (User/System defined).

The resources are either system defined and/or user defined in the database. Each new switch, and/or task added via the GUI interface automatically adds the switch as an new resource. Printer must be manually added to the database.

Thus, the printers are the only resources that can be added via the perms admin reource GUI screen. Once all resources are defined in the system, you must establish a relation and categorize them into individual Resouce Groups. This relation will allow a grouping of resources into Resource groups.

System Delivered Resource Types Description

TaskOrderSummary Enables a user to access the Task Order summary screen on Task ToolKit application.

TaskFamily Eables a user to access the Task Family screen on the Task Toolkit applicaion.

editRC Enables a user to have permission to modify failed RCs & resubmit.

permadm Enables a user to access the permissions access GUI.

taskadm For int user only.

tunableadm For int user only.

UNIX For int user only.

ForceComplete Allows users ability to Force complete an order.

GroupPermissionOnly For int users only.

Issue: GA-1, July 20101 0 - 2 6


Resource GroupsA resource group defines a specific set of resources available to a user. Each resource group has only one type of resource.

• For example, the activity “search order” and a switch cannot be part of the same resource group.

• However, an individual resource may belong to more than one resource group. • A resource group is usually associated with more than one task group. Resource groups drive

what navigation tree items are available to users: — Resources in a resource group are the tasks of that group; Resource groups are assigned to

task groups.

There are certain resource groups that are provided with the system as default. These resource groups have default resource assignments that cannot be changed:

It is the responsiblity of the admin to create Resource Groups as required. The Resouce groups created are classified and/or group by Resource Type of the following seven items:

• Admin, Printer, Reservation, Service Order, Switch, Systemadmin, & Task.

Thus, you may create a Resouce Groups called: • TestAdmin, TestPrinters, TestReservation, TestServiceOrder, TestSwitch, TestSysadmin, &

TestTasks.

Resource Groups Description

AllPrinters Enables a user to access the Task Order summary screen on Task ToolKit application.

AllSwitches Eables a user to access the Task Family screen on the Task Toolkit applicaion.

AllTasks Enables a user to have permission to modify failed RCs & resubmit.

ForceComplete Enables a user to access the permissions access GUI.

taskadm For int user only.

tunableadm For int user only.

UNIX For int user only.

ForceComplete Allows users ability to Force complete an order.

GroupPermissionOnly For int users only.

Issue: GA-1, July 201010 - 27


Work/Task Group A task group is same as a work group (used in “adduser” functionality) and defines the activities that are available to a particular group of users. It includes system-supplied and customer-defined activities.

• The activities assigned to a task group allow the users of the task group to perform their job. — Each user login can only be assigned to one task group.

Task groups are created to categorize a set of users into a specific set of groups. In the Translation Interface Application, the name used is called a work group. In the Task Toolkit environment, the same concept is called Task Group.

NOTE:Refer to chapter User Administration on “Task/Work Group” Admin.

Issue: GA-1, July 20101 0 - 2 8


Permissions Admin High Level OverviewPerforming permissions administration in the Task Toolkit environment is a three step process as follows:

• Step One: Releate a user to a Task/Work Group. — This step groups a user login into a specific Task/Work group and is completed when you

define a new user into the system. Refer to “User Admin” chapter for complete details.

• Step Two: Relate Task Groups and Resource Groups.— In the step, you must first define all the Resource Groups you wish to define in the system. The

Resouce groups defined are by Resource types.

— Once the Resource Groups are defined, then you must associate and/or group the Task/Work Groups to the defined set of Resource Groups.

• Step Three: Relate Resource Groups and Resources. — In this step, you associate a network elements (Resources) to the created Resource Groups.

You must complete the admin for each Resouce group that you have related to the Task Group in the previous step.

1. Relate users to Work/Task Groups.• Done via “adduser” via User Admin

Users

Work/Task Group

Resource Groups

Resources

2. Relate Work/Task Group to Resource group.

• Done via “Relate TASKGrp & RsrcGrp” from Permissions Admin GUI

3. Relate Resouce Group to Resources.

• Done via “Relate RsrcGrp & Rsrc” from Permissions Admin GUI

Issue: GA-1, July 201010 - 29


Resource Group AdministrationAccess ResourceGroups Screen

Access ResourceGroups screen via GUI Interface1. Access the VAM launch page via a browser interface & login as int.




— Select Permissions Administration option

— Select Resource Groups option & Click on the the Add/Delete/Update button.

Issue: GA-1, July 20101 0 - 3 0


Add ResourceGroups Screen1. Access ResourceGroups screen via GUI Interface as shown previously

— Refer to Heading “Access ResourceGroups Screen”.

2. You will need to input the following information to Add the Resource Group into the system.

— Resource Group Name: Name of the resource group you wish to add.

— Resource Type Name: From the pull-down list, select the resource type for the Resource group.

3. Click the “Add” button to add the Resource Group in the system.

— Click the “Return to MainResourceGroups screen” option on the bottom GUI screen to return to previous GUI screen.

— Click “Permissions Administration ” hyper-link to start over.

Query Resource Groups1. Access ResourceGroups screen via GUI Interface as shown previously


— Click on Filter button from the ResourceGroups GUI screen.

2. At this point, you can query the data for Resource Group via multiple methods as follows options:

— Resource Group Name: From Pull-down list, you can query for a specific value for the resource name and second pull-down list, you may select equal or Not equal to option.

— Resource Type Name: From the pull-down list, select the resource type for the Resource group and second pull-down list, you may select equal or Not equal to option.

— User Defined Ind: From the pull-down list, you may select Y or N option.

3. Click the “Submit” button to query the Resource Group in the system.


Issue: GA-1, July 201010 - 31


Update Resource Group1. Access ResourceGroups screen via GUI Interface as shown previously


2. You will need to input the following information to update the Resource Group into the system.

— Resource Group Name: Name of the resource group you wish to update.


NOTE:You may also query for the Resource Group to update and then update the information as needed.

3. Click the “update” button to update the Resource Group in the system.



Delete Resource Group1. Access ResourceGroups screen via GUI Interface as shown previously


2. You will need to input the following information to update the Resource Group into the system.

— Resource Group Name: Name of the resource group you wish to update.


NOTE:You may also query for the Resource Group to delete and then delete the information as needed.

3. Click the “Delete” button to update the Resource Group in the system.



Issue: GA-1, July 20101 0 - 3 2


Relate Resource Group & ResourcesAccess ResourceGroup/Resource Screen

Access ResourceGroupResource Screen via GUI Interface1. Access the VAM launch page via a browser interface & login as int.





— Select Relate Resource Groups and Resources option & Click on the the Add/Delete button.

Issue: GA-1, July 201010 - 33


Add ResourceGroup/Resource Relation1. Access ResourceGroupResource screen via GUI Interface as shown previously

— Refer to Heading “Access ResourceGroupsResource Screen”.

2. You will need to input the following information to add the ResourceGroup/Resource relation into the system.

— Resource Group Name: From the pull-down list, select the Resource Group Name to create the association for.

— Resource Name: From the pull-down list, select the resource to associate for the Resource group to.

3. Click the “Add” button to add the ResourceGroup/Resource relation in the system.

— Click the “Return to MainResourceGroupsResources screen” option on the bottom GUI screen to return to previous GUI screen.


Query ResourceGroup/Resource Relation1. Access ResourceGroupResource screen via GUI Interface as shown previously


— Click on Filter button from the ResourceGroups/Resources screen.

2. You will need to input the following information to query the ResourceGroup/Resource relation into the system.

— Resource Group Name: From the pull-down list, select the Resource Group Name to search for.

— Resource Name: From the pull-down list, select the resource to search for.

3. Click the “Submit” button to query the ResourceGroup/Resource relation in the system.



Issue: GA-1, July 20101 0 - 3 4


Delete ResourceGroup/Resource Relation1. Access ResourceGroupResource screen via GUI Interface as shown previously


2. You will need to input the following information to update the ResourceGroup/Resource relation into the system.

— Resource Group Name: From the pull-down list, select the Resource Group Name to create the association for.

— Resource Name: From the pull-down list, select the resource to associate for the Resource group to.

3. Click the “Delete” button to delete the ResourceGroup/Resource relation from the system.

At the prompt: “Are you sure you want to delete this item?” click on Okay button.

NOTE:You may also query for the specific ResourceGroup/Resource item via a query option and then delete the information as needed.



Issue: GA-1, July 201010 - 35


Relate Task Groups & Resource GroupsAccess TaskGroup/ResourceGroup Screen

Access ResourceGroupResource Screen via GUI Interface1. Access the VAM launch page via a browser interface & login as int.





— Select Relate Task Groups and Resource Groups option & Click on the the Add/Delete button.

Issue: GA-1, July 20101 0 - 3 6


Add TaskGroup/ResourceGroup Relation1. Access ResourceGroupResource screen via GUI Interface as shown previously

— Refer to Heading “Access TaskGroup/ResourceGroup Screen”.

2. You will need to input the following information to add the TaskGroup/ResourceGroup relation into the system.

— Task Group Name: From the pull-down list, select the Task Group Name to create the association for.

— Resource Group Name: From the pull-down list, select the Resource Group Name to associate for.

3. Click the “Add” button to add the TaskGroup/ResourceGroup relation in the system.

— Click the “Return to MainTaskGroup/ResourceGroup screen” option on the bottom GUI screen to return to previous GUI screen.


Query TaskGroup/ResourceGroup Relation1. Access ResourceGroupResource screen via GUI Interface as shown previously


— Click on Filter button from the TaskGroup/ResourceGroup screen.

2. You will need to input the following information to query the TaskGroup/ResourceGroup relation into the system.

— Task Group Name: From the pull-down list, select the Task Group Name to query for.

— Resource Group Name: From the pull-down list, select the Resource Group Name to query for.

3. Click the “Submit” button to query the TaskGroup/ResourceGroup relation in the system.



Issue: GA-1, July 201010 - 37


Delete TaskGroup/ResourceGroup Relation1. Access ResourceGroupResource screen via GUI Interface as shown previously


— Click on Filter button from the TaskGroup/ResourceGroup screen.

2. You will need to input the following information to delete the TaskGroup/ResourceGroup relation into the system.

— Task Group Name: From the pull-down list, select the Task Group Name to delete.

— Resource Group Name: From the pull-down list, select the Resource Group Name to delete.

3. Click the “Delete” button to delete the TaskGroup/ResourceGroup relation from the system.

At the prompt: “Are you sure you want to delete this item?” click on Okay button.

NOTE:You may also query for the specific TaskGroup/ResourceGroup item via a query option and then delete the information as needed.



Issue: GA-1, July 20101 0 - 3 8


Task Application User Session TimeoutThe Task Builder application has the same security feature which is used for Task Execution application. By default, after 8 hours of no interaction, the session will be discontinued. The default timeout is set to 480 minutes (8 hours). However, you can change the timeout for both Task Execution & Task Builder Application.

Configure Task Execution Session Timeout1. Log in as int from either the console or a PC via telnet into the Live (L1) source HP Server machine:



[xxx-int] /tgui/bin/stoptgui



3. Perform the following steps, to configure the session timeout value:

[xxx-int] cd /tgui/DOCS

[xxx-int] chmod +w TGui.properties

[xxx-int] vi TGui.properties

— Search for an entry for “session.timeout” and input a new desired value in terms of “milli-seconds”.

— Once the changes are complete, then save the file with “ :wq! “.

[xxx-int] chmod +w TGui.properties

4. Issue the following command to start TaskToolKit application:

[xxx-int] /tgui/bin/starttgui



Issue: GA-1, July 201010 - 39


Configure Task Builder Session Timeout1. Log in as int from either the console or a PC via telnet into the Live (L1) source HP Server machine:



[xxx-int] /tgui/bin/stoptgui



3. Perform the following steps, to configure the session timeout value:

[xxx-int] cd /tgui/DOCS/JFC_TBLD

[xxx-int] chmod +w Tbld.properties

[xxx-int] vi Tbld.properties

— Search for an entry for “session.timeout” and input a new desired value in terms of “milli-seconds”.

— Once the changes are complete, then save the file with “ :wq! “.

[xxx-int] chmod +w Tbld.properties

4. Issue the following command to start TaskToolKit application:

[xxx-int] /tgui/bin/starttgui



Issue: GA-1, July 20101 0 - 4 0




11 External Systems Management

Overview

The purpose of this chapter is to provide information about 8950 VAM application TOA Application Management. The following topics will be covered

• External System Interface Management

• TOA Application Management

Issue: GA-1, July 20101 1 - 2


TOA Application ManagementThis chapter provides information about TOA (Technology Object Adaptor) application. The TOA application processes are independent of the VAM application, and the intent is that the TOA function as a separate application, with its own logs, database, and configuration.

The TOA application will require configuration parameters for itself, the VAM instance it connects to via the FCIFC protocol, and each KANVAS system it will send response files. Each configuration file will be a Java properties file and reside in the config directory. It will be the responsibility of the TOA administrator to manually edit the files to set the correct values. Installation for the TOA shall consist of:

• creating the TOA administrative login and group, • creating the TOA runtime environment directories, • copying in the application software, doing initial application configuration, and creating the

TOA database and tables. • The administrative user for the TOA will be called ‘toa’ and belong to the ‘toa’ group. • The installation script will create the UNIX login and group if not already present.

The system will also create a login that will be used to FTP from KANVAS. This will be caused “kanvas”. No shell access will be allowed for this login.

TOA Directory LayoutThe following information represents a layout of the TOA component in the VAM system.

/toa (toa root)

Install_toa

libbin config

logs

rc.d

shutdown.d

data

users

input response reports save

Issue: GA-1, July 201011 - 3


• Install_TOA: The installation script for the TOA are kept here.• bin: This directory contains all application executable for TOA. As the application is in java,

this will consist of the shell scripts that launch the java applications. • lib: This directory contains all Java jar files used by the application. This includes third party

as well as application jars.• config: This directory contains all application configuration files. These are primarily Java

properties files.• logs: The logs directory contains all application log files. Each log file is a large logfile and

will be rolled daily. Additional log files may be produced by the shell scripts that start and stop processes.

— logs/archive: Application log files are to be moved to the archive directory after a configured interval, and purged after another interval.

• rc.d: This directory contains the script that starts the TOA application.• shutdown.d: This directory contains the script that stops the TOA application.• data: The data directory contains directories for batch files from KANVAS. Files are ftp’d

from KANVAS into the input directory, and remain there until processed. Successful files are moved to the saved directory, files that did not process are moved to the fail directory. The data directory also has subdirectories for report files and response files. If file system space becomes an issue, these directories may be symbolic links to directories in other file systems.

— data/input: Batch input files are stored here.

— data/response: The response files for batches that complete processing are generated here before being ftp’d to KANVAS.

— data/resp-save: The response files are moved here after being transmitted to KANVAS. Note that metafiles are removed, not saved.

— data/reports: Any report generated is stored here.

— data/saved: Batch input files are moved here after successful processing.

— data/failed: Batch input files are moved here if errors occurred during processing.

• users: The home directory of the “toa” user and any other users for the TOA application are kept here.

Issue: GA-1, July 20101 1 - 4


TOA ConfigurationThe TOA application will require configuration parameters for itself, the VAM instance it connects to via the FCIC protocol, and each KANVAS system it will send response files. Each configuration file will be a Java properties file and reside in the config directory. It will be the responsibility of the TOA administrator to manually edit the files to set the correct values.

The configuration file for the TOA application will be “toa.properties”. It contains the following:

Value name Description

toa.pollSleep The time to wait before doing another check for batch input files (in milliseconds). The default value delivered will be 60 seconds (60000 milliseconds)

toa.inputDir The directory where batch files are FTP’d by KANVAS. The default value delivered is <TOA_ROOT>/batchdir

toa.saveDir The directory where batch files are moved after successfully being entered into the database. The default value delivered is <TOA_ROOT>/SAVE_DIR.

toa.failDir The directory where batch files are moved if processing fails. The default value delivered is <TOA_ROOT>/FAILED.

toa.position The “position id” for this instance of the TOA application. This is a 1-6 digit number that can be assigned by the administrator.

toa.name The name of the TOA instance. This can be up to six characters. The name will be transmitted in the *C1 line for the FCIF message and will be blank padded if the less than six characters.

toa.node The “node number” for the TOA instance. This is a 2-digit number, and will be zero filled when transmitted if a single digit. The default value is 1. (The name and node are used in the ‘origination’ field of the *C1 line of the FCIF packet message.)

toa.dbURL The JDBC URL used to access the database.

toa.connectRetry The wait time (in milliseconds) between attempts to connect to the VAM system for FCIF. Default value is 30 seconds (30000 milliseconds).

Issue: GA-1, July 201011 - 5


TOA Application Shutdown1. Log in as toa from either the console or a PC via telnet into the L1 machine:

login: toa Password: <root_password>


# /toa/shutdown.d/stop_toa


stop_toa: Wed Apr 29 16:12:26 EDT 2009 Stopping TOA processes.stop_toa: java process for TOA=SocketServer PID=4312 successfully stopped.stop_toa: java process for TOA=BatchProcessor PID=4339 successfully stopped.stop_toa: java process for TOA=OrderProcessor PID=4342 successfully stopped.stop_toa: java process for TOA=Responder PID=4353 successfully stopped.

3. Issue the following command to ensure all toa process are down:

# ps -ef | grep -i toa

toa.noHandshakeTimeout If handshake mode is enabled, the FCIF connection will be dropped if no handshake request is received within the configured time. The default value for this is 12 minutes (720000 milliseconds). If handshake mode is not enabled, this should be set to zero.

toa.batchCheckSleep The time the response process waits between checks for completed batches. The default value is 3 minutes. (180000 milliseconds).

toa.metaDays The number of days of response files to store in a meta file. Default is 3 days

toa.SOMfile The full path to the SOM.properties file. See section 3.2 for more details. This should not be modified by the administrator.

toa.mutations The full path to the supported list of mutations. This should not be modified by the administrator.

toa.rootDir The root of the TOA installation. This should be set to <TOA ROOT> at installation time and not modified.

Value name Description

Issue: GA-1, July 20101 1 - 6


TOA Application Startup1. Log in as toa from either the console or a PC via telnet into the L1 machine:

login: toa Password: <root_password>


# /toa/rc.d/start_toa


start_toa: Wed Apr 29 16:19:04 EDT 2009 starting TOA process(es)start_toa: starting process: TOA=SocketServer (PID=24117) ...start_toa: starting process: TOA=BatchProcessor (PID=24121) ...start_toa: starting process: TOA=OrderProcessor (PID=24123) ...start_toa: starting process: TOA=Responder (PID=24125) ...start_toa: ... (10 second pause to verify process launch) ...start_toa: Process 24117 started for SocketServer.start_toa: Daemon java successfully started.start_toa: Process 24121 started for BatchProcessor.start_toa: Daemon java successfully started.start_toa: Process 24123 started for OrderProcessor.start_toa: Daemon java successfully started.start_toa: Process 24125 started for Responder.start_toa: Daemon java successfully started.

Issue: GA-1, July 201011 - 7


SOAP Interface ManagementSOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) as its message format, and usually relies on other Application Layer protocols (most notably Remote Procedure Call (RPC) and HTTP) for message negotiation and transmission. SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built.

SOAP Interface Advantages• Using SOAP over HTTP allows for easier communication through proxies and firewalls than

previous remote execution technology.• SOAP is versatile enough to allow for the use of different transport protocols. The standard

stacks use HTTP as a transport protocol, but other protocols are also usable (e.g., SMTP).• SOAP is platform independent.• SOAP is language independent.

SOAP Interface Disadvantages• Because of the verbose XML format, SOAP can be considerably slower than competing

middleware technologies such as CORBA. • When relying on HTTP as a transport protocol and not using WS-Addressing or an ESB, the

roles of the interacting parties are fixed. • Most uses of HTTP as a transport protocol are done in ignorance of how the operation would

be modeled in HTTP[citation needed]. • When relying on HTTP as a transport protocol a firewall designed to only allow web browsing

cannot simply allow all HTTP-using packets; instead it has to perform more detailed (and thus less efficient) analysis of the HTTP packages.

The 8950 VAM product has the capability to interface to Upstream Order Management systems and downstream network elements via the SOAP interface. The capability is an optional feature that the customer can purchase from the Alcatel-Lucent 8950 VAM product team. Please contact the Alcatel-Lucent Hotline for further assistance and/or contact your local Alcatel-Lucent customer representative for details.

Issue: GA-1, July 20101 1 - 8


CORBA Interface ManagementThe Common Object Requesting Broker Architecture (CORBA) is a standard defined by the Object Management Group (OMG) that enables software components written in multiple computer languages and running on multiple computers to work together. CORBA is a mechanism in software for normalizing the method-call semantics between application objects that reside either in the same address space (application) or remote address space (same host, or remote host on a network).

CORBA uses an interface definition language (IDL) to specify the interfaces that objects will present to the outside world. CORBA then specifies a “mapping” from IDL to a specific implementation language like C++ or Java.

CORBA Interface AdvantagesCORBA brings to the table many benefits that no other single technology brings in one package. These benefits include:

• Language Independence: CORBA at the outset was designed to free engineers from the hang-ups and limitations of considering their designs based on a particular software language.

• OS Independence: CORBA's design is meant to be OS-independent. CORBA is available in Java (OS-independent), as well as natively for Linux/Unix, Windows, Sun, Mac and others.

• Freedom from Technologies: One of the main implicit benefits is that CORBA provides a neutral playing field for engineers to be able to normalize the interfaces between various new and legacy systems.

• Strong Data Typing: CORBA provides flexible data typing, for example an "ANY" datatype. CORBA also enforces tightly coupled datatyping, reducing human errors.

• High Tune-ability: There are many implementations available that have many options for tuning the threading and connection management features.

• Freedom From Data Transfer Details: When handling low-level connection and threading, CORBA provides a high-level of detail in error conditions.

• Compression: CORBA marshals its data in a binary form and supports compression.

CORBA Interface Disadvantages• Location transparency: CORBA's notion of location transparency objects reside in the same

address space and accessible with a simple function call are treated the same as objects residing elsewhere (different processes on the same machine, or different machines).

• Design and process deficiencies: The creation of the CORBA standard is also often cited for its process of design by committee. There was no process to arbitrate between conflicting proposals or to decide on the hierarchy of problems to tackle.

• Problems with implementations: Working implementations of CORBA have been very difficult to acquire. Some poorly designed implementations have been found to be complex, slow, incompatible and incomplete.

Issue: GA-1, July 201011 - 9


• Firewalls: CORBA (more precisely, IIOP) uses raw TCP/IP connections in order to transmit data.

The 8950 VAM product currently uses the CORBA interface for Upstream Order Management systems and some inter-process communications within the application. This interface is delivered with the system and is readily available for use. However, for integration with a Upstream Order Management system, the customer must adhere to the the correct IDL of the VAM application. Please contact the Alcatel-Lucent Hotline for further assistance and/or contact your local Alcatel-Lucent customer representative for details.

Issue: GA-1, July 20101 1 - 1 0


Upstream System IntegrationFor customers wishing to integration and/or use an upstream order management system for Flow-Thru of service order managements, the following high-level steps can be used as a guideline.

NOTE:For setup/configuration of some of the items, a billable service and/or Feature activation may be required. It is the responsibility of the customer to work with the product Technical support team to complete this.

High-Level Steps: Upstream System Integration1. Interface option must be decided for the Upstream Order Management system whether it’s SOAP or

CORBA.

• IDL integration must be completed and/or any system interface issues must be discussed andresolved.

2. Once the interface option is chosen, a used login/password must be configured for the specific Upstream Order Management system via the USER Admin GUI.

• The user login/password information should be given to Upstream System Admin team.

3. In the 8950 VAM application, each switch must be configured and associated with the Upstream Order Management System

• Use menu “Add/Update Switch Association” Menu to complete this step.

4. Complete 8950 VAM Application system bounce to ensure all integration is complete.

5. Complete all required steps in the Upstream Order Management system.

6. Final steps are to complete initial sanity & full systems testing of the Interface to ensure orders are being processed.

Issue: GA-1, July 201011 - 11


Issue: GA-1, July 20101 1 - 1 2




12 System Tips

Overview

8950 VAM is a dynamic system involving computer systems located in different areas connected through communication networks. There are instances where the 8950 VAM system may not be fully operational. It is the responsibility of the System Administrator to see that the 8950 VAM system is fully functional. Following and learning some of the general guidelines in this chapter assists you in solving 8950 VAM System Administration problems.

The purpose of this chapter is to provide information about 8950 VAM application Management, troubleshooting & tips. The following topics will be covered

• System Tips

• System Troubleshooting

Issue: GA-1, July 20101 2 - 2


Product Technical Support GuidelinesIt is extremely important that you have the following pieces of information for any technical support help that you will need from the Alcatel-Lucent Product support team. Having this information helps in identifying the problem quickly and leads to a quicker system resolution.

System NameIt is important to know which computer system has the problem. Identifying the system name can greatly reduce the time needed to isolate the location of the problem.

Simple AbstractIt is critical that the user give specific details on the problem. It is recommended to note down errors, so that you do not forget them. This information can greatly reduce the time required to troubleshoot errors or problems.

Initial StepKnowing whether the problem has occurred before, or how the problem can be reproduced may help find system errors and lead to permanent fixes or future enhancements.

Severity LevelThe severity level of the problem that is detected. Severity levels are defined as follows:

Severity 1: Major system failure. System inoperative with critical effect on customer operation; system cannot be activated through normal procedures.

Severity 2: System partially inoperative (limited functionality) affecting a critical feature.

Severity 3: Non-critical feature inoperative or absent; system is still functioning.

Severity 4: System inquiries; non operational impacting problems or questions.

! CAUTION:The Technical support engineer from Alcatel-Lucent may change the severity level of the ticket if the level is NOT correctly defined.

Issue: GA-1, July 201012 - 3


Product Support ContactThe Alcatel-Lucent Hotline is in operation 24 hours a day, 7 days a week to solve problems regarding the 8950 VAM product.

• The Hotline response schedule is based on the severity level of the trouble report and your Service Level Agreement. The Hotline response schedule is based on the severity level of the trouble report.

• Alcatel-Lucent Technical Support Contact: 1-866-LUCENT8 (1-866-582-3688).When you call the hotline, provide the following information:

• Name - The name of the person calling the hotline.• Phone # - The telephone number of the individual to be contacted for support on the problem.• Company Name & Location - The name of the company and the location of the work center

where the problem has occurred.• Product Name - The product name is 8950 VAM.• Application Release Number: Your 8950 VAM application release number.• Abstract - A brief high level description of the problem detected.

Alcatel-Lucent Hotline - ARThe Alcatel-Lucent Hotline generates a Assistance Request (AR) that is used for trouble tracking. Procedures are in place to ensure that your calls receive a response in a timely manner.

• To track your problem, make a note of the AR number generated by the Alcatel-Lucent Hotline representative in your personal records and check the status of the trouble report monthly.

• The Alcatel-Lucent Hotline representative forwards your AR to the appropriate customer support group.

• An engineer from the customer support group will call you when the AR is received.

NOTE:It is not the responsibility of the Alcatel-Lucent Hotline representative to keep track of the status of your problem. The product support engineer will handle all status of the AR.

Issue: GA-1, July 20101 2 - 4


8950 vam (8950 voice activation manager) - nokia · pdf file8950 vam (8950 voice activation...

Documents