Netsm110 - Server Administration Guide

FNC-1500-0050-110
BOOKS
SERVER ADMINISTRATION GUIDE
Installation Guide
Server Administration
Guide
Introduction
Topology Management
Configuration Management
Connection Management
Cross-Connect Management
NE Maintenance
NE Software Management
NETSMART 1500
VERSION 5
ISSUE 1, JANUARY 2007
NE Performance Management
NE User Management
TL1 Editor
External Interfaces
Reports
Master Index
FUJITSU NETWORK COMMUNICATIONS INC.
Copyrights, Trademarks, and Disclaimers
NETSMART is a trademark of Fujitsu Network

Communications Inc. (USA). All Rights Reserved
Oracle is a registered trademark of Oracle Corporation.

Orbix is a registered trademark of IONA Technologies.
FLASH is a trademark of Fujitsu Network Communications

Inc. (USA). All Rights Reserved
FLASHWAVE (and design) is a trademark of Fujitsu
Network Communications Inc. (USA). All Rights Reserved
Cisco is a registered trademark of Cisco Systems, Inc.
Solaris is a trademark of Sun Microsystems, Inc. in the

United States and other countries.
Sun and Sun Microsystems are trademarks of Sun
Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group.
Netscape is a registered trademark of Netscape

Communications Corporation in the United States and other
countries.
All other products or services mentioned in this document are identified by the trademarks, service marks, or product names as
designated by the companies that market those products or services or own those marks. Inquiries concerning such products,
services, or marks should be made directly to those companies.
This document and its contents are provided by Fujitsu Network Communications Inc. for guidance purposes only. This
document is provided as is with no warranties or representations whatsoever, either express or implied, without notice, to make
including without limitation the implied warranties of merchantability and fitness for purpose. Fujitsu Network
Communications Inc. does not warrant or represent that the contents of this document are error free. Furthermore, the contents
of this document are subject to update and change at any time without notice by Fujitsu Network Communications Inc., since it
reserves the right, changes in equipment design or components as progress in engineering methods may warrant. No part of the
contents of this document may be copied, modified, or otherwise reproduced without the express written consent of Fujitsu
Network Communications Inc.
Unpublished work and only distributed under restriction.
Copyright Fujitsu Network Communications Inc. All Rights Reserved.
NETSMART 1500 Version 5

Server Administration Guide
Fujitsu and Fujitsu Customer Use Only
FNC-1500-0050-110
Issue 1, January 2007
Document Change Notice
DOCUMENT CHANGE NOTICE

This notice lists the reasons for, location of, and a description of document changes. When the changes are
extensive, a general statement giving the nature of the revisions is provided.
Reason for Document Change:
Updated for Version 5
Location of Change
Description of Change
Throughout
New UNIX terminal screen captures
Section 2.2.2
Added a note to indicate that the NETSMART servers must be DOWN

when changing passwords.
Section 2.10.2
Added note that certain Oracle Database Maintenance tasks are no longer
supported. Although those tasks still display in the UNIX terminal view,
the descriptions of the tasks have been removed.
Section 3.23
New Section. Set Branding Image in Toplogy View
Section 3.24
New Section. Remove Branding Image from Topology View
FNC-1500-0050-110

Table of Contents
Also includes:
List of Figures
List of Tables
1
Introduction
1.1
Overview of Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2
1.2
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . .
1-3
1.3
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3
1.3.1
1.3.2
Fujitsu Technical Assistance Center . . . . . . . . . . . .

World Wide Web . . . . . . . . . . . . . . . . . . . . . . . . .
1-3
1-4
2.1
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2
2.2
Oracle User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5
2.2.1
2.2.2
2.2.3
2.2.4
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Database Passwords . . . . . . . . . . . . . . .
Verifying Database Passwords . . . . . . . . . . . . . . . .
Resetting Database Passwords to Default . . . . . . . .
2-5
2-6
2-7
2-9
Status Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-10
2.3.1
2.3.2
2.3.3
2.3.4
2-11
2-13
2-14
2-15
2
Oracle Administration
2.3
FNC-1500-0050-110
Check Database Consistency . . . . . . . . . . . . . . . . .

Database and Connection Status . . . . . . . . . . . . . .
OS Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Monitor . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents
2.4
Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-18
2.4.1
2.4.2
2.4.3
Startup Normal . . . . . . . . . . . . . . . . . . . . . . . . . . .
Startup Archive . . . . . . . . . . . . . . . . . . . . . . . . . . .
Startup by Ending Backup . . . . . . . . . . . . . . . . . . .
2-18
2-19
2-22
Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-23
2.5.1
2.5.2
Shutdown Normal . . . . . . . . . . . . . . . . . . . . . . . . .
Shutdown Abort (Abnormal) . . . . . . . . . . . . . . . . .
2-23
2-24
2.6
Standard Database Backup . . . . . . . . . . . . . . . . . . . . . . . . .
2-25
2.7
Recovery from a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-29
2.7.1
2.7.2
2.7.3
2.7.4
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering from a Backup . . . . . . . . . . . . . . . . . . .
Restoring Backup of HA on a non-HA System . . .
Restoring Backup of HA on an HA System . . . . . .
2-29
2-30
2-35
2-35
2.8
Oracle Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-36
2.9
Alert Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-37
2.9.1
2.9.2
2.9.3
2.9.4
2-37
2-38
2-39
2.5
Alert Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check Size of Alert File . . . . . . . . . . . . . . . . . . . . .
Check Size of File Systems . . . . . . . . . . . . . . . . . . .
Check Size of File System Containing Archived
Redo Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check for Missing Archived Redo Log Files . . . . . .
2-40
2-41
Automated Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-43
2.10.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10.2 Maintenance Scripts. . . . . . . . . . . . . . . . . . . . . . . .
2-43
2-46
System and Configuration Information . . . . . . . . . . . . . .
2-59
2.11.1
2.11.2
2.11.3
2.11.4
2.11.5
2.11.6
2.11.7
2-60
2-63
2-63
2-65
2-65
2-66
2-66
2.9.5
2.10
2.11
System Equipment Inventory Reports . . . . . . . . . .

Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Control Files . . . . . . . . . . . . . . . . . . . . . .
Redo Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backup Files on Disk . . . . . . . . . . . . . . . . . . . . . . .
Core Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii Server Administration Guide
FNC-1500-0050-110
Table of Contents
2.11.8 Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.11.9 Database E-Mail Notification. . . . . . . . . . . . . . . . .
2-66
2-66
Export Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-67
2.12.1 Export of NETSMART 1500 LOGS . . . . . . . . . . .

2.12.2 Export of PM LOGS . . . . . . . . . . . . . . . . . . . . . . .
2-68
2-69
3.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3
3.2
Creating UNIX Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-7
3.3
Starting Up and Shutting Down . . . . . . . . . . . . . . . . . . . . .
3-8
2.12
3
NETSMART 1500
Administration
3.3.1
3.3.2
3.3.3
3.3.4
3.4
Start Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start Client on the Server . . . . . . . . . . . . . . . . . . . .
Shut Down Server . . . . . . . . . . . . . . . . . . . . . . . . .
Shut Down Client . . . . . . . . . . . . . . . . . . . . . . . . .
3-8
3-9
3-10
3-11
Troubleshooting Server and Clients . . . . . . . . . . . . . . . . .
3-12
3.4.1
3.4.2
3-12
Check the Status of Server Processes. . . . . . . . . . . .

Recover from a NETSMART 1500 Client Error
(UNIX Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recover from a NETSMART 1500 Server Error . .
Restore Server . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manage NETSMART 1500 Service Packs and
Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-13
3-14
3-15
Enabling/Disabling Program Groups. . . . . . . . . . . . . . . . .
3-16
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.5.7
3.5.8
3.5.9
3.5.10
3-17
3-18
3-19
3-19
3-20
3-21
3-22
3-22
3-23
3-24
3.4.3
3.4.4
3.4.5
3.5
FNC-1500-0050-110
Enable Performance Management . . . . . . . . . . . . .

Disable Performance Management. . . . . . . . . . . . .
Enable EMLNML . . . . . . . . . . . . . . . . . . . . . . . . .
Disable EMLNML. . . . . . . . . . . . . . . . . . . . . . . . .
Enable TL1 Uplink . . . . . . . . . . . . . . . . . . . . . . . .
Disable TL1 Uplink . . . . . . . . . . . . . . . . . . . . . . . .
Enable FLASHWAVE 7400 Node Managers. . . . .
Disable FLASHWAVE 7400 Node Managers . . . .
Enable Webservice . . . . . . . . . . . . . . . . . . . . . . . . .
Disable Webservice . . . . . . . . . . . . . . . . . . . . . . . .
3-16

iii
Table of Contents
3.5.11
3.5.12
3.5.13
3.5.14
Enable SNMP Uplink . . . . . . . . . . . . . . . . . . . . . .

Disable SNMP Uplink. . . . . . . . . . . . . . . . . . . . . .
Enable All Optional Program Groups . . . . . . . . . .
Disable All Optional Program Groups . . . . . . . . . .
3-25
3-26
3-26
3-27
3.6
NETSMART 1500 Trace Menu . . . . . . . . . . . . . . . . . . . . . . . .
3-28
3.7
Installing NE Software Generics . . . . . . . . . . . . . . . . . . . . .
3-28
3.7.1
Install from CD Using NETSMART 1500

Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install from CD Using UNIX Client . . . . . . . . . . .
Install from Remote Network Drive. . . . . . . . . . . .
3-29
3-34
3-36
3.8
Configuring the ObjectStream License . . . . . . . . . . . . . . .
3-37
3.9
Export Security Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-39
3.10
Import Security Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-40
3.11
Resync NE Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-41
3.12
Configuring the Communication Server/NE Logon. . . .
3-42
3.12.1 NE Logon Reconnect Algorithm . . . . . . . . . . . . . .

3.12.2 NE Logon Delay Algorithm . . . . . . . . . . . . . . . . . .
3.12.3 Modifying Communication Server Properties . . . .
3-42
3-44
3-44
3.13
Security E-Mail Notification . . . . . . . . . . . . . . . . . . . . . . . . .
3-45
3.14
Broadcast Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-46
3.14.1 Sending Messages from a Command Line . . . . . . .

3.14.2 Sending Messages from the Web Administration
Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.14.3 Client Notification. . . . . . . . . . . . . . . . . . . . . . . . .
3-46
Pre-Logon Warning Banner Administration . . . . . . . . . .
3-49
3.15.1 Enable the Pre-Logon Warning Banner . . . . . . . . .

3.15.2 Disable the Pre-Logon Warning Banner. . . . . . . . .
3.15.3 Import the Pre-Logon Warning Banner from a
File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.15.4 Retrieve and Edit the Pre-Logon Warning
Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.15.5 Check the Status of Pre-Logon Warning Banner . .
3-50
3-51
3.7.2
3.7.3
3.15
iv Server Administration Guide
3-48
3-48
3-51
3-52
3-53
FNC-1500-0050-110
Table of Contents
3.16
3.17
3.18
Enabling/Disabling RTRV-HDR Logging . . . . . . . . . . . . . .
3-55
3.16.1 Enable RTRV-HDR Logging. . . . . . . . . . . . . . . . .

3.16.2 Disable RTRV-HDR Logging . . . . . . . . . . . . . . . .
3-55
3-56
NETSMART 1500 License Administration . . . . . . . . . . . . .
3-58
3.17.1 Display NETSMART 1500 License Information . .

3.17.2 Upgrade NETSMART 1500 License . . . . . . . . . . .
3.17.3 Upgrade NETSMART 1500 License for HA . . . . .
3-58
3-59
3-69
Service Pack Installation on HA-Enabled Federations .
3-73
3.18.1 Online Installation of Service Pack on

HA Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.18.2 Offline Installation of Service Pack on
HA Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.19
3-73
3-74
Transaction Debugging Client. . . . . . . . . . . . . . . . . . . . . . .
3-76
3.19.1 Start the Transaction Debugging Client. . . . . . . . .

3.19.2 Transaction Debugging Client Options . . . . . . . . .
3-77
3-77
3.20
LNE Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-80
3.21
Connection Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-82
3.22
Topology Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-84
3.23
Configure SONET-SDH Terminology Mapping . . . . . . . .
3-88
3.24
Set Branding Image in Topology View . . . . . . . . . . . . . . .
3-90
3.25
Remove Branding Image from Topology View . . . . . . . .
3-90
4.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2
4.2
Power Down UNIX Workstation . . . . . . . . . . . . . . . . . . . . .
4-3
4.3
Start Up Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4
4.4
Restart UNIX Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4
4.5
Shut Down Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-5
4
UNIX System
Administration
FNC-1500-0050-110

Table of Contents
4.6
Configure UNIX User Accounts . . . . . . . . . . . . . . . . . . . . . .
4-5
4.6.1
4.6.2
4.6.3
Configure NETSMART 1500 Server Accounts . . .

Configure NETSMART 1500 Client Accounts . . .
Add CDE Controls to NETSMART 1500
Client Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6
4-6
4.7
Add UNIX User Accounts Using Local Files. . . . . . . . . . . .
4-11
4.8
Delete UNIX User Accounts Using Local Files . . . . . . . . .
4-13
4.9
Understand UNIX Log Files. . . . . . . . . . . . . . . . . . . . . . . . . .
4-13
4.10
Set the Date and Time on the UNIX System . . . . . . . . . . .
4-14
4.10.1 Change the Date and Time Backward . . . . . . . . . .

4.10.2 Change the Date and Time Forward . . . . . . . . . . .
4-14
4-16
UNIX System Information . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-17
4.11.1
4.11.2
4.11.3
4.11.4
4.11.5
4.11.6
4.11.7
System Processes . . . . . . . . . . . . . . . . . . . . . . . . . .
System Messages . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Swap Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Activities Menu . . . . . . . . . . . . . . . . . . . . .
Cronjobs Menu . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defunct Processes. . . . . . . . . . . . . . . . . . . . . . . . . .
4-18
4-19
4-20
4-20
4-21
4-25
4-26
Back Up the UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-27
4.12.1 Perform a Full System Backup . . . . . . . . . . . . . . . .

4.12.2 Back Up the NETSMART 1500 Application. . . . .
4.12.3 View a Log File of the Backup . . . . . . . . . . . . . . . .
4-27
4-28
4-30
4.13
Admintool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-31
4.14
Restore UNIX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-31
4.15
Restore Root (/) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-31
4.11
4.12
vi Server Administration Guide
4-8
FNC-1500-0050-110
Table of Contents
5
Network
Administration
5.1
5.2
5.3
5.4
5.5
5.6
FNC-1500-0050-110
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2
5.1.1
5.1.2
Start FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stop FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-4
5-4
TCP/IP and OSI Networks with NETSMART 1500 . . . . . .
5-5
5.2.1
5.2.2
OSI Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . .
TCP/IP Connectivity . . . . . . . . . . . . . . . . . . . . . . .
5-5
5-6
OSI Startup and Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . .
5-7
5.3.1
5.3.2
Start an OSI Communications Stack . . . . . . . . . . .

Stop an OSI Communications Stack . . . . . . . . . . .
5-8
5-9
OSI Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-11
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
5.4.8
List OSI Processes . . . . . . . . . . . . . . . . . . . . . . . . .

Restart OSI and FTAM . . . . . . . . . . . . . . . . . . . . .
Set NSAP Address . . . . . . . . . . . . . . . . . . . . . . . . .
Display NSAP Address. . . . . . . . . . . . . . . . . . . . . .
Add Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Route . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Dynamic Routes . . . . . . . . . . . . . . . . . . . .
5-12
5-12
5-13
5-15
5-16
5-16
5-17
5-17
TARP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-18
5.5.1
5.5.2
5.5.3
5.5.4
5.5.5
5.5.6
5.5.7
5.5.8
Set TARP TID. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Display TARP TID . . . . . . . . . . . . . . . . . . . . . . . .
Add Manual Adjacency . . . . . . . . . . . . . . . . . . . . .
Delete Manual Adjacency. . . . . . . . . . . . . . . . . . . .
Display Manual Adjacency. . . . . . . . . . . . . . . . . . .
Add Manual TARP Entries . . . . . . . . . . . . . . . . . .
Delete Manual TARP Entries. . . . . . . . . . . . . . . . .
Display Manual TARP Entries. . . . . . . . . . . . . . . .
5-19
5-19
5-19
5-20
5-20
5-21
5-21
5-21
IP Address Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-22

vii
Table of Contents
6
Service Support
6.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2
6.2
Edit Support Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2
6.3
List Support Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
6.4
Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
6.5
FTP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
6.6
Archive Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-4
6.7
Archive System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-6
6.8
Edit Property Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-7
6.9
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-12
6.10
Check Solaris Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-12
6.11
Collect Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . .
6-14
6.11.1
6.11.2
6.11.3
6.11.4
System Information . . . . . . . . . . . . . . . . . . . . . . . .
NETSMART Information . . . . . . . . . . . . . . . . . . .
ORACLE Information . . . . . . . . . . . . . . . . . . . . . .
All Information . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-15
6-16
6-17
6-17
7.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2
7.2
Understanding HA States and Roles . . . . . . . . . . . . . . . . .
7-2
7.3
Starting NETSMART 1500 HA Services . . . . . . . . . . . . . . .
7-5
7.3.1
7.3.2
Starting NETSMART 1500 HA Services . . . . . . . .

Checking NETSMART 1500 HA Status . . . . . . . .
7-5
7-8
Stopping NETSMART 1500 HA Services . . . . . . . . . . . . . .
7-13
7
High Availability
Administration
7.4
7.4.1
7.4.2
Stopping HA Services on Active and Passive

Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping HA Services on Passive Only Systems . . .
viii Server Administration Guide
7-13
7-14
FNC-1500-0050-110
Table of Contents
7.5
Initiating Manual Failover. . . . . . . . . . . . . . . . . . . . . . . . . . .
7-15
7.6
Understanding Automatic Failover . . . . . . . . . . . . . . . . . .
7-18
7.7
Recovering from a Crash . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-21
7.8
Understanding Node Isolation Behavior . . . . . . . . . . . . .
7-23
7.9
Understanding Data Loss Scenarios . . . . . . . . . . . . . . . . .
7-24
7.9.1
7.9.2
Data Loss Due to Multiple Resource Failure . . . . .

Data Loss when Active System Is Isolated . . . . . . .
7-24
7-25
7.10
Understanding Client Installation and Behavior . . . . . .
7-26
7.11
Unconfiguring NETSMART 1500 HA Service . . . . . . . . . .
7-27
7.12
HA Quick Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-31
7.12.1
7.12.2
7.12.3
7.12.4
7.12.5
7.12.6
7.12.7
Cluster Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start in Single-Node Mode . . . . . . . . . . . . . . . . . .
Shutdown Cluster . . . . . . . . . . . . . . . . . . . . . . . . .
Enable Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disable Failover . . . . . . . . . . . . . . . . . . . . . . . . . . .
Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering Crashed Node . . . . . . . . . . . . . . . . . . .
7-31
7-31
7-32
7-32
7-32
7-33
7-33
Hints and FAQs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-34
7.13.1 Hints for Working with HA. . . . . . . . . . . . . . . . . .

7.13.2 Frequently Asked Questions. . . . . . . . . . . . . . . . . .
7-34
7-35
A.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-2
A.2
Server Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-2
7.13
A
Server and Client Port
Usage
FNC-1500-0050-110

ix
Table of Contents
A.3
Client Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-3
Index
x Server Administration Guide
FNC-1500-0050-110
List of Figures
LIST OF FIGURES
FIGURE
TITLE
Figure 3-1
Figure 3-2
Figure 3-3
Figure 4-1
Figure 7-1
Figure 7-2
Figure 7-3
Figure 7-4
Software Repository Management Window, 3-32

Install Software Generic Dialog Box, 3-33
Warning Dialog Box, 3-49
Admintool: Users Dialog, 4-31
System State Transition Possibilities, 7-4
Heartbeat Failure Causing Failover, 7-18
Network Isolation of PassiveNo Failover, 7-19
Multiple Resource Failure Scenario, 7-24
FNC-1500-0050-110

xi
List of Tables
LIST OF TABLES
TABLE
TITLE
Table 1-1
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 2-6
Table 3-1
Table 3-2
Typographic Conventions, 1-3

Oracle Database Administration Menu Items, 2-2
Oracle UNIX User Account Information, 2-5
Database Monitor Statistics, 2-15
Automated Oracle Maintenance Jobs, 2-44
Tablespaces Used for Oracle Data, 2-64
Tablespaces Used for NETSMART 1500 Data, 2-64
NETSMART 1500 Administration Menu Items, 3-5
NETSMART 1500 Administrator UNIX User Account
Information, 3-7
NE Logon Reconnect Algorithm Parameters, 3-43
NE Logon Delay Algorithm Parameter, 3-44
Property Values to Configure SONET-SDH Terminology
Mapping, 3-89
UNIX Administration Menu Items, 4-2
Software Download User Account Information, 4-6
useradd Command Field Descriptions, 4-12
Date Command Field Descriptions, 4-15
Network Administration Menu Items, 5-2
Property Files and Key Values, 6-9
Possible Associated Roles, 7-2
Possible Associated States, 7-2
Possible Combinations of Roles and States, 7-3
System Isolation Behavior, 7-23
Color Conventions for Dashboard Node Icons, 7-26
Server Port Usage, A-2
Table 3-3
Table 3-4
Table 3-5
Table 4-1
Table 4-2
Table 4-3
Table 4-4
Table 5-1
Table 6-1
Table 7-1
Table 7-2
Table 7-3
Table 7-4
Table 7-5
Table A-1
xii Server Administration Guide
FNC-1500-0050-110
1
CHAPTERS/APPENDIXES
INTRODUCTION
1 Introduction
2 Oracle Administration
This chapter includes the following sections:
3 NETSMART 1500
Administration
NO.
SECTION
4 UNIX System
Administration
1.1
Overview of Practice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2
5 Network Administration
1.2
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3
6 Service Support
1.3
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3
PAGE
7 High Availability
Administration
A Server and Client Port Usage
FNC-1500-0050-110

CHAPTER 1
Introduction
Overview of Practice
1.1
Overview of Practice
This practice provides descriptions and procedures related to server administration.
Information in this practice is organized as follows:
Chapter 1, IntroductionProvides a brief introduction to this book and information
about contacting and using Fujitsu Network Communications Inc. (FNC) technical
support
Chapter 2, Oracle AdministrationDescribes procedures for managing the Oracle
database, including startup, shutdown, recovery, and backup
Chapter 3, NETSMART 1500 AdministrationDescribes procedures for
NETSMART 1500 software, including optional features such as creating schedules
for NE remote backup
Chapter 4, UNIX System AdministrationDescribes the tasks usually performed by a
UNIX system administrator; assumes the user has root privileges
Chapter 5, Network AdministrationDescribes procedures for protocol and interface
settings
Chapter 6, Service SupportDescribes the Service Support menu options available in
in Heartbeat
Chapter 7, High Availability AdministrationDescribes procedures related to systems
configured with high availability (HA)
Appendix A, Server and Client Port UsageLists the ports used in NETSMART 1500
client and server systems
1-2 Server Administration Guide
FNC-1500-0050-110
CHAPTER 1
Introduction
Typographical Conventions
1.2
Typographical Conventions
Visual cues throughout the NETSMART 1500 Element Management System documentation
are used to help you easily locate and interpret information. Typographical conventions
(particular fonts used to indicate a type of word) are listed and explained in Table 1-1 [p. 1-3].
Table 1-1: Typographic Conventions
1.3
Type Style
Used for:
Initial Caps
Window or dialog box title
Bold
A word or phrase that is being defined or otherwise deserves special emphasis
Italics
Menu, menu item, button, icon, field, region, or other GUI object
Courier
Text that the user types, text that is displayed as a message on the screen, or a file name
ALL CAPS
Keyboard key (such as CTRL or SHIFT)
< variable>
Bracketed term denotes variable to be replaced with an appropriate value
Technical Support
This section includes the following subsections:
NO.
SUBSECTION
PAGE
1.3.1
Fujitsu Technical Assistance Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3
1.3.2
World Wide Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4
In addition to the standard product-specific documentation set, FNC provides technical

support in many different forms.
1.3.1
Fujitsu Technical Assistance Center

The Fujitsu Technical Assistance Center (FTAC or TAC) offers telephone support to answer
questions concerning NETSMART 1500 software, other FNC products, or
documentation-related issues. Call FTAC any time at 1-800-USE-FTAC (1-800-873-3822).
FNC-1500-0050-110

1-3
CHAPTER 1
Introduction
Technical Support
1.3.2
World Wide Web

The FNC home page offers information about the latest products, documentation, sales
offices, registration for training classes, access to the FTAC, and FNC news. The FNC home
page is located at http://www.fnc.fujitsu.com.
The Fujitsu Online Customer Information System (FOCIS) Web site provides access to the
latest technical information about FNC products. The system incorporates all the
information on the FNC Bulletin Board System (BBS) and more. The FOCIS Web site is at
https://partners.fnc.fujitsu.com. From that Web site, FNC customers can register and log on
FOCIS to access the following options:
Product Change Notices
Information Bulletins
Manufacture Discontinued Notices
Manuals
Software downloads and links
Training information
Keyword searching
E-mail to FNC
Document downloads
NETSMART 1500 license keys
FNC-1500-0050-110
2
CHAPTERS/APPENDIXES
ORACLE ADMINISTRATION
1 Introduction
WARNING:
3 NETSMART 1500
Administration
4 UNIX System
Administration
6 Service Support
7 High Availability
Administration
Many of the operations described in this chapter use the Heartbeat

tool. When using Heartbeat with root enabled, do not press CTRL+C.
Doing so may cause Heartbeat to terminate abnormally. CTRL+C may
be used with Heartbeat when root is not enabled.

NO.
SECTION
PAGE
2.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2
2.2
Oracle User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5
2.3
Status Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-10
2.4
Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-18
2.5
Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-23
2.6
Standard Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-25
2.7
Recovery from a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-29
2.8
Oracle Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-36
2.9
Alert Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-37
2.10
Automated Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-43
2.11
System and Configuration Information . . . . . . . . . . . . . . . . .
2-59
2.12
Export Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-67
FNC-1500-0050-110

CHAPTER 2
Overview
2.1
Overview
The Oracle database is used to store configuration and state information for NEs and for
internal NETSMART 1500 objects.
Database administration uses the Oracle Administration option of the Heartbeat tool. This
option provides the following menu, which is the starting point for most of the procedures
described in this chapter:
ORACLE DATABASE ADMINISTRATION
1. Status Scripts
2. Startup/Shutdown Procedures
3. Backup/Recovery Procedures
4. Alert Scripts
5. Maintenance Scripts
6. Export Procedures
d. Disable Root Access (return to netsmart)
m. Go back to the Main Menu
q. Quit
Table 2-1 [p. 2-2] lists the menu and submenu items available from this menu and shows
where to go for additional information.
Table 2-1: Oracle Database Administration Menu Items
Menu Item
Reference
1. Status Scripts
Section 2.3, Status Scripts [p. 2-10]

1. Check Database Consistency
Section 2.3.1, Check Database Consistency [p. 2-11]
2. Database & Connection Status
Section 2.3.2, Database and Connection Status

[p. 2-13]
3. OS Monitor
Section 2.3.3, OS Monitor [p. 2-14]
4. Database Monitor
Section 2.3.4, Database Monitor [p. 2-15]
2. Startup/Shutdown Procedures
Section 2.4, Startup [p. 2-18], and Section 2.5,

Shutdown [p. 2-23]
1. Startup Normal
Section 2.4.1, Startup Normal [p. 2-18]
2. Startup Archive
Section 2.4.2, Startup Archive [p. 2-19]
3. Shutdown Normal
Section 2.5.1, Shutdown Normal [p. 2-23]
4. Shutdown Abort
Section 2.5.2, Shutdown Abort (Abnormal) [p. 2-24]
5. Startup by Ending backup
Section 2.4.3, Startup by Ending Backup [p. 2-22]
FNC-1500-0050-110
CHAPTER 2
Overview
Table 2-1: Oracle Database Administration Menu Items (Cont.)

Menu Item
Reference
3. Backup/Recovery Procedures
1. Backup
Section 2.6, Standard Database Backup [p. 2-25]
3. CANCEL Based (Recovery)
Section 2.7, Recovery from a Backup [p. 2-29]
4. Alert Scripts
Section 2.9, Alert Scripts [p. 2-37]

1. Alert Monitor
Section 2.9.1, Alert Monitor [p. 2-37]
2. Check Size of Alert File
Section 2.9.2, Check Size of Alert File [p. 2-38]
3. Check Size of File Systems
Section 2.9.3, Check Size of File Systems [p. 2-39]
4. Check Size of File System containing

Archived Redo Log Files
Section 2.9.4, Check Size of File System Containing

Archived Redo Log Files [p. 2-40]
5. Check for missing Archived Redo Log

Files
Section 2.9.5, Check for Missing Archived Redo Log

Files [p. 2-41]
FNC-1500-0050-110
Section 2.10.2, Maintenance Scripts [p. 2-46]

1. Clean Old Compressed ALERT Files
Section 2.10.2, subsection Clean Old Compressed

ALERT Files [p. 2-48]
2. Clean Old ORACLE trace File
Section 2.10.2, subsection Clean Old ORACLE Trace

File [p. 2-48]
3. Clean Old Files and Old Archived

Redo Files
Section 2.10.2, subsection Clean Old Files and Old

Archived Redo Files [p. 2-49]
4. Clean Old Log and out Files
Section 2.10.2, subsection Clean Old Log and out

Files [p. 2-50]
5. Find Max Contiguous space available

in Datafile for an Object
Section 2.10.2, subsection Find Max Contiguous Space

Available in Datafile for an Object [p. 2-50]
6. Recreate Indexes on a Table
Section 2.10.2, subsection Recreate Indexes on a Table

[p. 2-51]
7. Give additional space to the Tablespace
Section 2.10.2, subsection Give Additional Space to the

Tablespace [p. 2-52]
8. Select tape to remove from AutoLoader
This option no longer supported.
9. Edit Oracle crontab
Section 2.10.2, subsection Edit Oracle crontab

[p. 2-52]

2-3
CHAPTER 2
Overview
Table 2-1: Oracle Database Administration Menu Items (Cont.)

Menu Item
(Cont.)
Reference
10. Disk Array Status
11. Check index usage on select queries
Section 2.10.2, subsection Check Index Usage on Select

Queries [p. 2-54]
12. Check invalid DB scripts
Section 2.10.2, subsection Check Invalid DB Scripts

[p. 2-54]
13. Generate zip file for Oracle logs
Section 2.10.2, subsection Generate Zip File for Oracle

Logs [p. 2-55]
14. Raid controller Battery Status
15. Reset Raid controller Battery Age
16. Analyze Data Schema
Section 2.10.2, subsection Analyze Data Schema

[p. 2-55]
17. Time Offset for Oracle Scheduled

Jobs
Section 2.10.2, subsection Time Offset for Oracle

Scheduled Jobs [p. 2-56]
18. Select Backup Device and Path
Section 2.10.2, subsection Select Backup Device and

Path [p. 2-57]
6. Export Procedures
Section 2.12, Export Procedures [p. 2-67]

1. Export of NETSMART 1500 LOGS
Section 2.12.1, Export of NETSMART 1500 LOGS

[p. 2-68]
2. Export of PM LOGS
Section 2.12.2, Export of PM LOGS [p. 2-69]
FNC-1500-0050-110
CHAPTER 2
Oracle User Account
2.2
Oracle User Account

2.2.1
NO.
SUBSECTION
PAGE
2.2.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5
2.2.2
Changing Database Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-6
2.2.3
Verifying Database Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-7
2.2.4
Resetting Database Passwords to Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-9
Overview
An Oracle UNIX user account is required to:
Administer the Oracle database
Troubleshoot Oracle database problems
Run background Oracle processes
The Oracle UNIX user account information is listed in Table 2-2 [p. 2-5].
Table 2-2: Oracle UNIX User Account Information
User
Shell
Home
Group
oracle
/bin/csh
/opt/NetSmart/oracle
dba
Note: Typical installations use local files rather than Network Information Services (NIS) or NIS+.
This information is needed for configuring the UNIX user account in NIS or NIS+. Provide
this information to the network System Administrator to set up the NIS or NIS+ UNIX user
account.
If the Oracle UNIX user account is set up using local files on the NETSMART 1500 server
instead of NIS or NIS+, the installation sets up the account automatically. No additional
configuration is required.
FNC-1500-0050-110

2-5
CHAPTER 2
Oracle User Account
2.2.2
Changing Database Passwords

Passwords for Oracle accounts are encrypted and can be user defined. This procedure allows
you to change, verify, and reset the system to a default password and applies to the following
IDs: SYS, SYSTEM, DBSNMP.
Note: In a high availability (HA) configuration, both systems should have the same passwords
for SYS and SYSTEM IDs. If the passwords are changed on one system, change the same
passwords on other system.
Note: This procedure must be done when NETSMART 1500 servers are DOWN.
Follow this procedure to change database passwords.

Step
1
Task
Logon as user oracle and enter at the prompt:

$>
cd $MAINT
$>
orapass_chng
The system displays:

To Change Password
----------------Please select from following
C|c) Change Password
V|v) Verify Password
R|r) Reset Password to Default
Q|q) QUIT
Enter c to display the following:

1) SYS
2) SYSTEM
3) DBSNMP
4) OUTLN
Q|q) QUIT
FNC-1500-0050-110
CHAPTER 2
Oracle User Account
Enter 3 to display the following:

Changing password for DBSNMP
Please enter new password :
Please reenter new password for confirmation :
Password changed successfully
Enter the password.

Note: The password must not contain special charactersspecial characters are not supported.
The system prompts you to reenter the new password for confirmation and then displays that
the password was changed successfully.
5
2.2.3
Enter q to quit.
Verifying Database Passwords

This procedure allows you to change, verify, and reset the system to a default password and
applies to the following IDs: SYS, SYSTEM, DBSNMP.
Note: In a high availability (HA) configuration, both systems should have same passwords for
SYS and SYSTEM IDs. If the passwords are changed on one system, change the same
Follow this procedure to verify database passwords.

Step
1
Task

$>
cd $MAINT
$>
orapass_chng
FNC-1500-0050-110

2-7
CHAPTER 2
Oracle User Account

Please select from following
Q|q) QUIT
Enter v to display the following:

1) SYS
2) SYSTEM
3) DBSNMP
4) OUTLN
Q|q) QUIT
Enter 2.
Enter the password you want to verify.

The system displays that the password was verified.
Press ENTER to continue. The system displays:

Q|q) QUIT
Enter v to display the following:

1) SYS
2) SYSTEM
3) DBSNMP
4) OUTLN
Q|q) QUIT
FNC-1500-0050-110
CHAPTER 2
Oracle User Account
Enter 1.
The system prompts you to enter the password you want to verify and then displays that the
password was verified.
2.2.4
Enter q to quit.
Resetting Database Passwords to Default

This procedure allows you to reset the system password to default and applies to the following
IDs: SYS, SYSTEM, DBSNMP.
Note: In a high availability (HA) configuration, both systems should have same passwords for
SYS and SYSTEM IDs. If the passwords are changed on one system, change the same
Follow this procedure to reset default database passwords.

Step
1
Task

$>
cd $MAINT
$>
orapass_chng

Q|q) QUIT
Enter r to display the following:

1) SYS
2) SYSTEM
3) DBSNMP
4) OUTLN
A|a) All Above
Q|q) QUIT
FNC-1500-0050-110

2-9
CHAPTER 2
Status Scripts
Enter a to display the following:

Changing password to default for SYS
Changing password to default for SYSTEM
Changing password to default for DBSNMP
Changing password to default for OUTLN
Press ENTER to continue. The system displays:

Q|q) QUIT
2.3
Enter q to exit the procedure.
Status Scripts
This section describes the Oracle database status scripts. It includes the following subsections:
NO.
SUBSECTION
PAGE
2.3.1
Check Database Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-11
2.3.2
Database and Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-13
2.3.3
OS Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-14
2.3.4
Database Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-15
The database status scripts monitor availability and collect statistics on the Oracle database.
Many of these scripts are run daily from the Oracle users crontab. The scripts that run daily
automatically notify you of potential database availability problems though e-mail to the
Oracle user account.
FNC-1500-0050-110
CHAPTER 2
Status Scripts
If needed, the database status scripts can be run manually through Heartbeat.
2.3.1
Check Database Consistency

This script validates the consistency of the data contained in the Oracle database. This script
should be run during off-peak hours.
Check database consistency as follows:
Step
1
Task
From the common desktop environment (CDE) toolbar, open the Heartbeat menu
OR
From the Command Line enter netsmart heartbeat
Enter e in the Main Menu to log on as root.
Enter 2 Oracle Administration.
Enter 1 Status scripts.
Enter 1 Check Database Consistency.

The script runs and displays progress messages. The following output file is generated:
$NETSMART_HOME/oracle/scripts/operation/reco/out/
run_consistency_checks.<timestamp>
HINT:
To determine if any failures occurred, search for IR.Failure in the output file. Report any
failures to NETSMART product support.
FNC-1500-0050-110

2-11
CHAPTER 2
Status Scripts
A screen similar to the following displays:

Sun Microsystems Inc.
SunOS 5.10
Generic Patch October 2006
You have new mail.
Validating DB objects
Consistency check for the database Tue Jul 11 13:47:30 PDT 2006: 13:47:30
Running Netsmart Consistency Checks ....
=============================================
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
auditdetail_tasklog_check
clienthashmap_proplist_check
clienthashmap_check
binfileobject_check
CTPUtilization_NE
CTPUtilization_PNEComponent
ne_customerinfo_check
ne_neuser_check
ne_servicemanager_1_check
ne_servicemanager_2_check
ne_servicemanager_check
NeDatabase_swfile
nesync_ne_check
neuser_actgrp_check
neuser_ne_check
neusr_actgrp_phase2
actgrp_actgrpdetails_check
actgrp_neact_actgrp_check
actgrp_neact_neact_check
pconnection_customerattr_check
pconnection_endpoints_check
pcourseleg_ne_check
pcourseleg_pconnection_check
pcourselegpcrossconnect
PEC_NE_Check
peqptconn_attributes_check
peqptconn_tne_check
playoutleg_ne_check
playoutleg_pconnection_check
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
13:47:31
13:47:31
13:47:31
13:47:32
13:47:32
13:47:32
13:47:33
13:47:33
13:47:33
13:47:34
13:47:34
13:47:34
13:47:34
13:47:35
13:47:35
13:47:35
13:47:36
13:47:36
13:47:36
13:47:36
13:47:37
13:47:37
13:47:37
13:47:38
13:47:38
13:47:38
13:47:39
13:47:39
13:47:39
screen display continues on next page
FNC-1500-0050-110
CHAPTER 2
Status Scripts
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
pnec_ne
pnecomponent_do_storage_check
pnecomponent_tne_check
psnc_snccustomerattr_check
resyncdetail_tasklog_check
Swgen_swfile
xcnecheck
topo_check.run_consistency_checks(&m)
pm_15min_check
pm_1day_check
pm_polled_check
:
:
:
:
:
:
:
:
:
:
:
13:47:39
13:47:40
13:47:40
13:47:40
13:47:41
13:47:41
13:47:41
13:47:42
13:47:42
13:47:42
13:47:43
consistency check output file is

/opt/NetSmart/oracle/scripts/operation/reco/out/run_consistency_checks.01J
ul134731
In case of consistency check failure, please forward this file to NETSMART
support for analysis
Hit any key to Continue.
2.3.2
Database and Connection Status

This script validates that the Oracle database processes are running and that a connection to
the database is available.
Check the database and connection status as follows:
Step
1
Task
From the CDE toolbar, open the Heartbeat menu

OR
Enter 1 Status Scripts.
Enter 2 Database & Connection Status.
FNC-1500-0050-110

2-13
CHAPTER 2
Status Scripts
The script runs and displays output to the screen:

SunOS 5.10
Generic June 2006
You have new mail.
Database is Up and Running...
2.3.3
If any error is reported, contact FNC technical support for further assistance.
OS Monitor
This script displays a report on operating system (OS) performance monitoring.
Note: This item is used only by FNC personnel for troubleshooting.
Monitor OS performance as follows:

Step
1
Task

OR
Enter 1Status Scripts.
Enter 3 OS Monitor.
FNC-1500-0050-110
CHAPTER 2
Status Scripts
The performance monitoring report displays. The following example shows a system with no
reported problems:
Note: This item is used only by FNC personnel for troubleshooting.
SunOS 5.10
Generic June 2006
You have new mail.
Performance Monitoring Report for node nvt1 at 06/20/06 11:37:18
Collecting Unix system performance statistics - Please wait 5 seconds...
Free swap space 4878 Mbytes
Free memory 120 Mbytes
CPU user mode 0
CPU system mode 10
CPU idle mode 98
Analyzing disk system performance statistics - Please wait 10 seconds...
The disk subsystem is performing normally...)
Processing Unix cache performance statistics - Please wait 5 seconds...
(The Cache statistics is performing normally...)
2.3.4
Database Monitor
This script collects the Oracle database statistics listed in Table 2-3 [p. 2-15]. These statistics
are used by a database administrator to tune database performance.
Table 2-3: Database Monitor Statistics
Name
Description
Ideal Value
Buffer cache hit ratio
Percentage of requests for a row or index that are found in the

database buffers (If the row or index is not in the database
buffers, requested information is reloaded from disk.)
90% or higher
SQL cache hit ratio
Percentage of SQL requests that have to be reparsed because their

entries in the Oracle library cache were replaced by other SQL
statements
2% or lower
Data dictionary cache

hit ratio
Percentage of cache hits for the Oracle dictionary cache
85% or higher
Sort area statistics
Lists the number of sort requests performed in memory and disk

and identifies the number of rows sorted
Less than 1% for the ratio of

disk sorts to memory sorts
Redo latch contention

statistics
Monitors statistics for the three types of redo log latches: redo
allocation, redo copy, redo writing
1% or lower for the WTW

misses and IMM misses
ratios
Redo log information
Lists the redo logs available on the system
Not applicable
Extents report
Details of the tables and indexes in the Oracle database
Not applicable
FNC-1500-0050-110

2-15
CHAPTER 2
Status Scripts
Table 2-3: Database Monitor Statistics (Cont.)

Name
Description
Ideal Value
Tablespace summary
report
Percentage of space and fragmentation on all tablespaces
20% or higher for free space,

75% or lower for the
fragmentation percentage
System input/output on
physical disks
Lists the number of physical reads and writes for each data file
Not applicable
Rollback segment
details
Lists information about the rollback segments on the system

(The type of information includes table space, storage
parameters, number of extents occupied, current size, and
status.)
Not applicable
Rollback shrink/extend
report
Lists shrink, extend, and wrap statistics on the rollback segments
Not applicable
Execute the database monitor script as follows:

Step
1
Task

OR
Enter 1 Status Scripts.
Enter 4 Database Monitor.
FNC-1500-0050-110
CHAPTER 2
Status Scripts
The script executes. The values of the statistics listed in Table 2-3 [p. 2-15] display on the
screen as shown in the following example:
DBA Report for nms on Tue Jun 11 11:48:04 CDT 2006
****************************************
Buffer Cache Hit Ratio is : 99.6970796
SQL Cache Hit Ratio is : .096648812
Data Dictionary Hit Ratio is : 99.385048
Sortarea Info
=============
Sort (Memory) : 15119 Sort (Disk) : 19 Sort (Rows) : 3559268
Tunebuffer Info
===============
>
SGA CACHE STATISTICS
>
********************
>
SQL Cache Hit rate = 99.9
>
Dict Cache Hit rate = 99.38
>
Buffer Cache Hit rate = 99.7
>
Redo Log space requests = 86
>
>
INIT.ORA SETTING
>
****************
>
Shared Pool Size = 47000000 Bytes
>
DB Block Buffer = 30000 Blocks
>
Log Buffer = 25600000 Bytes
:
:
Note: For a complete listing, see Section 2.3.4, Database Monitor [p. 2-15].
Review the statistics reported. Refer to Table 2-3 [p. 2-15] for detailed information about the
individual statistics. If any of the values in the report are not in the standard operating range,
contact FNC technical support for further assistance.
FNC-1500-0050-110

2-17
CHAPTER 2
Startup
2.4
Startup
Note: The procedures in this section should be used only if NETSMART 1500 is not running.
This section describes the three ways to start the Oracle database with NETSMART 1500
software not running. It includes the following subsections:
NO.
SUBSECTION
PAGE
2.4.1
Startup Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-18
2.4.2
Startup Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-19
2.4.3
Startup by Ending Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-22
Under normal operation, NETSMART 1500 starts the Oracle database. The procedures in
this section should be used only if NETSMART 1500 is not running. Refer to Section 3.4,
Troubleshooting Server and Clients [p. 3-12], for instructions on NETSMART 1500
shutdown.
2.4.1
Startup Normal
The startup-normal method sets the database to run in archive mode so that archive redo files
are created. Archive redo files allow the database to recover if a problem occurs. When
NETSMART 1500 starts up, it starts up the Oracle database in this way.
Start Oracle using the startup-normal method as follows:
Step
Task
Verify that NETSMART 1500 is not running.

OR
FNC-1500-0050-110
CHAPTER 2
Startup
Enter 2 Startup/Shutdown Procedures.
Enter 1 Startup Normal.

If recovery is in progress, a warning displays:
Presently Recovery may be going on If you want to start database, please
abort the Recovery Do you want to continue startup ( Y/N ) ?
Otherwise, the system display for a normal startup is similar to the one shown below:
Sun Microsystems Inc. SunOS 5.10 Generic Patch October 2006
You have new mail.
Database is started.
2.4.2
Startup Archive
WARNING:
Do not start the Oracle database using the startup-archive method without the direction of
Fujitsu Network Communications Inc. (FNC) technical support.
The startup-archive method forces the database to start in archive mode after it has been
running in a nonarchive mode. The startup-archive method normally should not be used. It is
used only after the database has been run in nonarchive mode for database recovery.
Start Oracle using the startup-archive method as follows:
Step
Task

OR
FNC-1500-0050-110

2-19
CHAPTER 2
Startup
Enter 2 Startup Archive.
FNC-1500-0050-110
CHAPTER 2
Startup
The database starts in archive mode. The system display is similar to the one shown below:
You have new mail.
SunOS 5.10
Generic Patch
October 2006
LSNRCTL for Solaris: Version 10.2.0.2.0 - Production on 07-JUL-2006

11:32:37
Copyright (c) 1991, 2003, 2006 Oracle Corporation. All rights reserved.
Starting /opt/NetSmart/oracle/product/10g/bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 10.2.0.2.0 - Production
System parameter file is
/opt/NetSmart/oracle/product/10g/network/admin/listener.
ora
Log messages written to
/opt/NetSmart/oracle/product/10g/network/log/listener.log
Listening on:
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=karma.nms.fnc.fujitsu.com)(
PORT=1521)))
Connecting to
(ADDRESS=(PROTOCOL=TCP)(Host=karma.nms.fnc.fujitsu.com)(Port=1521))
STATUS of the LISTENER
-----------------------Alias
LISTENER
Version
TNSLSNR for Solaris: Version 10.2.0.2.0 Production
Start Date
07-JUL-2006 11:32:37
Uptime
0 days 0 hr. 0 min. 0 sec
Trace Level
off
Security
OFF
SNMP
OFF
Listener Parameter File
/opt/NetSmart/oracle/product/10g/network/admin/listener
.ora
Listener Log File
/opt/NetSmart/oracle/product/10g/network/log/listener.l
og
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=karma.nms.fnc.fujitsu.com)(PORT
=1521)))
Services Summary...
Service "nms" has 1 instance(s).
Instance "nms", status UNKNOWN, has 1 handler(s) for this service...
FNC-1500-0050-110

2-21
CHAPTER 2
Startup
The command completed successfully

Connected to an idle instance.
ORACLE instance started.
Total System Global Area
Fixed Size
Variable Size
Database Buffers
Redo Buffers
Database mounted.
332108028
454908
184549376
134217728
12886016
bytes
bytes
bytes
bytes
bytes
Database altered.
Statement processed.Database altered.
2.4.3
Startup by Ending Backup

WARNING:
Do not start the Oracle database using this method without the direction of FNC technical
support.
This method is used only after a backup of the Oracle database is aborted abruptly; for
example, if the NETSMART 1500 system is rebooted while the NETSMART 1500 software
and Oracle database are running. The startup-by-ending-backup method starts the Oracle
database by ending the previously aborted backup.
Start Oracle using the startup-by-ending-backup method as follows:
Step
Task

OR
FNC-1500-0050-110
CHAPTER 2
Shutdown
Enter 5 Startup by Ending_backup.

Sun Microsystems Inc. SunOS 5.10 Generic June 2006

Starting Database....
2.5
Shutdown
Note: The Oracle shutdown procedures described in this section should be used only if NETSMART
1500 is not running or if NETSMART 1500 is running in an error condition.
This section describes two ways to shut down the Oracle database. It includes the following
subsections:
NO.
SUBSECTION
PAGE
2.5.1
Shutdown Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-23
2.5.2
Shutdown Abort (Abnormal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-24
Under normal operation, the Oracle database is shut down by the NETSMART 1500
shutdown procedures described in Chapter 3, NETSMART 1500 Administration,
Section 3.3.3, Shut Down Server [p. 3-10].
2.5.1
Shutdown Normal
The shutdown-normal method produces a graceful shutdown. All Oracle database users (such
as the NETSMART 1500 software) must be disconnected from the database when the
shutdown-normal method is invoked. Shutdown-normal is the method NETSMART 1500
uses to shut down the Oracle database.
Shut down Oracle using the shutdown-normal method as follows:
Step
1
Task
FNC-1500-0050-110

2-23
CHAPTER 2
Shutdown

OR
Enter e from the Main Menu to log on as root.
Enter 3 Shutdown Normal.

The database shuts down normally. If any Oracle connections exist, the process waits until the
connections are closed. Users must log off before the shutdown can complete. A screen similar
to the following displays:
SunOS 5.10
Generic Patch
October 2006
You have new mail.

database is going down.. In Normal mode
Database shutdown complete...
2.5.2
Shutdown Abort (Abnormal)

WARNING:
The shutdown-abort method of shutting down the Oracle database should be used only
with the direction of FNC technical support.
The shutdown-abort (abnormal) method is not used in normal situations. This method shuts
the database down without warning users (such as the NETSMART 1500 software). This
shutdown is used for database recovery (refer to Section 2.7, Recovery from a Backup
[p. 2-29]) or for emergencies, such as when normal shutdown fails or when the database
hangs up.
Shut down Oracle using the shutdown-abort (abnormal) method as follows:
Step
1
Task
FNC-1500-0050-110
CHAPTER 2
Standard Database Backup

OR
Enter e from the Main Menu to log on as root.
Enter 4 Shutdown Abort.

All connections are killed and the database shuts down abnormally. A screen similar to the
following displays:

SunOS 5.10 Generic June 2006
You have new mail.
database is going down.. In abort modeDatabase shutdown complete...
2.6

This section describes how to do an Oracle database backup. This section is for backups using
a standard DAT drive.
HINT:
Check that the backup device type is set correctly before following this procedure. If the
backup device type is set to Standalone or Autoloader, the restore tries to restore from
tape. Restore from tape will not be tried if the backup device is set to None or Custom.
Refer to Section 2.10.2, subsection Select Backup Device and Path [p. 2-57], for more
information.
A backup of the Oracle database is done while the Oracle database is running. The backup
stores Oracle tablespaces, archived redo log files, and control files on the tape.
Note: Backups should be run during off-peak hours.
FNC-1500-0050-110

2-25
CHAPTER 2
Take a backup of the Oracle database as follows:

Step
Task
Insert a new write-enabled tape into the tape drive.

OR
Enter 3 Backup/Recovery procedures.
Enter 1 Backup.
FNC-1500-0050-110
CHAPTER 2
Backup files are placed in /nsdata/nms/backup/fulldb_<timestamp>. A screen

similar to the following displays:
--------------------------------------For Logs, Please see
/opt/NetSmart/oracle/scripts/operation/out/nsdbbackup.28June120749
--------------------------------------Doing Disk to Disk Full Database Instance Backup
------------------------------------------Previous Backup Details
Size of Backup : 108339200 Bytes
Date : Sun June 25 10:09:26 PDT 2006
------------------------------------------Backup control file generated and creation script is
/opt/NetSmart/oracle/new_control.sql
Program Successfully Completed..
Hot / OnLine Backup
Starting backup of Tablespace SYSTEM
12:08:10 : system_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace RBS
12:09:39 : rbs_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace TOOLS
12:10:16 : tools_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace USERS
12:10:29 : users_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_META
12:10:42 : d_meta_01.dbf to /nsdata/nms/backup/fullDb_0528031208
FNC-1500-0050-110

2-27
CHAPTER 2
Starting backup of Tablespace D_DOCMGT

12:11:33 : d_docmgt_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace REPLIC_TS
12:12:01 : replic_ts_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_ACTIVITYEVENT
12:12:16 : d_activityevent_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_EMLNML
12:12:33 : d_emlnml_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_FAULTHISTORY
12:12:38 : d_faulthistory_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_NETSMART
12:12:56 : d_netsmart_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_OF
12:13:12 : d_of_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_PM
12:13:27 : d_pm_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_PMCORE
12:13:39 : d_pmcore_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_SYSTEMEVENT
12:13:42 : d_systemevent_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_TL1EVENT
12:14:00 : d_tl1event_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace D_TL1UPLINKEVENT
12:14:17 : d_tl1uplinkevent_01.dbf to
/nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace I_EMLNML
12:14:35 : i_emlnml_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace I_NETSMART
12:14:37 : i_netsmart_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace I_PM
12:14:46 : i_pm_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace I_PMCORE
12:14:59 : i_pmcore_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Starting backup of Tablespace TEMP
12:15:09 : temp_01.dbf to /nsdata/nms/backup/fullDb_0528031208
Backed up corresponding archive files /nsdata/nms/backup/fullDb_0528031208
Backup control file copied to /nsdata/nms/backup/fullDb_0528031208
Hot/OnLine Backup set creation (Disk to Disk) completed successfully !
Program Successfully Completed ..
Copying Backup from Disk to Tape
Sun June 25 12:15:51 PDT 2006
/nsdata/nms/backup/fullDb_0528031208
Backup of Database files is over Sun June 25 12:18:17 PDT 2006
Copying Backup from Disk to Tape completed successfully
--------------------------------------screen display continues on next page
FNC-1500-0050-110
CHAPTER 2
Recovery from a Backup
For Logs, Please see

/opt/NetSmart/oracle/scripts/operation/out/nsdbbackup.25June120749
--------------------------------------Doing Disk to Disk Archived Redo Logs Backup
Last File Copied was 24_1.arc
Redo Log file 25_1.arc available
Copying Backup from Disk to Tape
/nsdata/nms/backup/archRedo_0625061218
Backup of Archived Redo files is over Sun June 25 12:18:36 PDT 2006
2.7

2.7.1
NO.
SUBSECTION
PAGE
2.7.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-29
2.7.2
Recovering from a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-30
2.7.3
Restoring Backup of HA on a non-HA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-35
2.7.4
Restoring Backup of HA on an HA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-35
Overview
This section describes how to restore the contents of Oracle database and how to restore the
backup from an high availability (HA) system on a non-HA system.
FNC-1500-0050-110

2-29
CHAPTER 2
2.7.2
Recovering from a Backup

HINT:
Check that the backup device type is set correctly before following this procedure. If the
backup device type is set to Standalone or Autoloader, the restore tries to restore from
tape. Restore from tape will not be tried if the backup device is set to None or Custom.
Refer to Section 2.10.2, subsection Select Backup Device and Path [p. 2-57], for more
information.
This section describes how to restore the contents of the Oracle database.
CAUTION:
After the Oracle database recovery is completed, making a backup of the newly restored
Oracle database is important. The following procedure includes steps for backing up the
Oracle database after recovery is complete.
Recover from a backup tape as follows:

Step
Task
Shut down each NETSMART 1500 client by selecting Exit from the File menu of each
NETSMART 1500 client graphical user interface (GUI).
Stop the NETSMART 1500 server. (Refer to Section 3.3.3, Shut Down Server [p. 3-10].)

OR
Enter 3 Backup/Recovery.
Insert the backup tape from the previous day into the tape drive on the NETSMART 1500
server.
Enter 3 CANCEL Based Recovery.
FNC-1500-0050-110
CHAPTER 2
Data recovery begins. A screen similar to the following displays. A completion message
displays when recovery is complete.
--------------------------------------For Logs, Please see
/opt/NetSmart/oracle/scripts/operation/out/nsdbbackup.25Jun132023
--------------------------------------Starting Restoration from TAPE to DISK
Sun Jun 25 13:20:26 PDT 2006
Restoration of Files from HOT Backup
Restoration will be done from /dev/rmt/0n
Make sure that /dev/rmt/0n is ONLINE
Please insert database BACKUP DAT in /dev/rmt/0n
Restoration will start in 1 Minute.
Restoration can proceed
-----------------------------------------------------------------Date
: Sun Jun 25 12:15:48 PDT 2006
Type of Backup
: On Demand HOT/OnLine Backup of Database
System
: swagat.nms.fnc.fujitsu.com
NetSmart Version
: 5.0
Database Name
: nms
Size of Backup
: 109459456 Bytes
MaxNeCount
: 1000
App Servers
: 2
CheckSum
: 60111496853
-----------------------------------------------------------------Are you restoring correct backup ?
Do you want to continue ? :y/n: y
STARTING RESTORATION Of Database Files AT Sun Jun 25 13:20:46 PDT 2006
Restoring all the files
It will take time, please wait .....
FNC-1500-0050-110

2-31
CHAPTER 2
fufullDb_0528031208/rbs_01.dbf.Z
fullDb_0528031208/tools_01.dbf.Z
fullDb_0528031208/users_01.dbf.Z
fullDb_0528031208/d_meta_01.dbf.Z
fullDb_0528031208/d_docmgt_01.dbf.Z
fullDb_0528031208/replic_ts_01.dbf.Z
fullDb_0528031208/d_activityevent_01.dbf.ZfullDb_0625061208/d_emlnml_01.db
f.Z
fullDb_0528031208/d_faulthistory_01.dbf.Z
fullDb_0528031208/d_netsmart_01.dbf.Z
fullDb_0528031208/d_of_01.dbf.Z
fullDb_0528031208/d_pm_01.dbf.Z
fullDb_0528031208/d_pmcore_01.dbf.Z
fullDb_0528031208/d_systemevent_01.dbf.Z
fullDb_0528031208/d_tl1event_01.dbf.Z
fullDb_0528031208/d_tl1uplinkevent_01.dbf.Z
fullDb_0528031208/i_emlnml_01.dbf.Z
fullDb_0528031208/i_netsmart_01.dbf.Z
fullDb_0528031208/i_pm_01.dbf.Z
fullDb_0528031208/i_pmcore_01.dbf.Z
fullDb_0528031208/temp_01.dbf.Z
fullDb_0528031208/28_1.arc.Z
fullDb_0528031208/27_1.arc.Z
fullDb_0528031208/bkp_control.ctl
fullDb_0528031208/dbfile_bkp.ctl
fullDb_0528031208/new_control_resetlog.sql
fullDb_0528031208/fullDb_headerRestoration of Database files is over Sun
Jun 25 13:22:58 PDT 2006
Restoration Can Proceed after controlfile for backup check
Restoration From Tape to Backup Disks is Over
Restoring from DISK for fullDb onLine lastCommit
Starting Recovery lastCommit Based
Checking for Validation of database installation
Checking for Host names
Host names mismatch
database is going down.. In abort mode
database is going down.. In abort mode
Database is up and running !!!
Connectivity test is successful !!!
FNC-1500-0050-110
CHAPTER 2
Removing obsolete archived redo log files

Archival Sequence set to 0
Validating DB objectsNow running consistency check for the database Sun Jun
25 13:46:52 PDT 2006
It will take some time , Please wait ...
Running Netsmart Consistency Checks ....
=============================================
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
checking
auditdetail_tasklog_check : 13:54:21
clienthashmap_proplist_check : 13:54:22
CTPUtilization_NE : 13:54:22
CTPUtilization_PNEComponent : 13:54:23
inactive_nemgrarray_check : 13:54:23
ne_customerinfo_check : 13:54:23
ne_neuser_check : 13:54:24
ne_servicemanager_1_check : 13:54:24
ne_servicemanager_2_check : 13:54:25
ne_servicemanager_check : 13:54:25
ne_sm_coe_check : 13:54:25
NeDatabase_swfile : 13:54:26
nesync_ne_check : 13:54:26
neuser_actgrp_check : 13:54:27
neuser_ne_check : 13:54:27
neusr_actgrp_phase2 : 13:54:27
neusr_neact_phase1 : 13:54:28
pconnection_customerattr_check : 13:54:28
pconnection_endpoints_check : 13:54:29
pconnpcourseleg2 : 13:54:29
pconnpcourseleg3 : 13:54:30
pcourseleg_ne_check : 13:54:30
pcourseleg_pconnection_check : 13:54:30
pcourselegpcrossconnect : 13:54:31
PEC_NE_Check : 13:54:31
PECATTR_PEC_Check : 13:54:31
peqptconn_attributes_check : 13:54:32
peqptconn_tne_check : 13:54:32
playoutleg_ne_check : 13:54:33
playoutleg_pconnection_check : 13:54:33
FNC-1500-0050-110

2-33
CHAPTER 2
checking pnec_ne : 13:54:33

checking pnec_sm_check : 13:54:34
checking pnecomponent_do_storage_check : 13:54:34
checking pnecomponent_tne_check : 13:54:35
checking psnc_snccustomerattr_check : 13:54:35
checking resyncdetail_tasklog_check : 13:54:36
checking sm_ne_coe_check : 13:54:36
checking Swgen_swfile : 13:54:36
checking xcnecheck : 13:54:37
checking pm_15min_check : 13:54:37
Recovery Over
------------MRE001,0 Take Fresh Backup
// SCRIPT: transferBackupSet on swagat.nms.fnc.fujitsu.com
// We recommend you immediately take Hot/Cold backup because
// You cannot recover your database from your previous HOT/Online backups.
// You cannot recover your database till last transaction
// from your previous COLD/Offline backups.
------------------------------------------------------------------
Remove the backup tape from the tape drive to prevent accidental erasure.
10
Do a normal shutdown of the Oracle database. (Refer to Section 2.5.1, Shutdown Normal
[p. 2-23].)
11
Start the NETSMART 1500 server. (Refer to Section 3.3.1, Start Server [p. 3-8].)
12
Do a backup of the system. (Refer to Section 2.6, Standard Database Backup [p. 2-25].)
13
Insert a new tape for the automated backup process.
FNC-1500-0050-110
CHAPTER 2
2.7.3
Restoring Backup of HA on a non-HA System

This section describes how to restore the backup of high availability (HA) on a non-HA
system.
Note: The non-HA system must be licensed for the same number of NEs and other optional
components as that of the HA system.
Step
Task
Use Heartbeat menu to restore backup. Refer to Section 2.7.2, Recovering from a Backup
[p. 2-30], for more information.
Use the Heartbeat menu to Unconfigure HA. Refer to Section 7.11, Unconfiguring
NETSMART 1500 HA Service [p. 7-27], for more information.
2.7.4
Restoring Backup of HA on an HA System

This section describes how to restore the backup of high availability (HA) on a non-HA
system.
Step
Task
Bring down the cluster. Refer to Section 7.12.3, Shutdown Cluster [p. 7-32], for more
information.
Use Heartbeat menu to restore backup. Refer to Section 2.7.2, Recovering from a Backup
[p. 2-30], for more information.
Bring up the active system in single node. This puts the active in active suspended (AS) state.
Do a netsmart startup on single node on the active system by choosing cluster startup. Refer
to Section 7.12.1, Cluster Startup [p. 7-31], for more information. This triggers a active
suspended to active fail (AS_AF) and put the passive also in passive fail (PF) state.
Do a startup on the active system choosing cluster startup. Refer to Section 7.12.1, Cluster
Startup [p. 7-31], for more information. This internally triggers an active failed to active up
(AF_AU) state, internally adding the second node.
FNC-1500-0050-110

2-35
CHAPTER 2
Oracle Purge
2.8
Oracle Purge
NETSMART 1500 stores TL1 events, fault history, 15-minute performance monitoring data,
and 24-hour performance monitoring data (all referred to as log data) in log tables. This
historical data is available from the log tables until it is deleted by purging. Purging is required
to make space for new data. There are two purging mechanisms:
Daily rolloverDoes a backup of the log data that is older than 365 days and then
deletes that data from the system at the end of the day.
Threshold purgeDeletes log data from the log tablespaces when the disk is at or
above 80 percent of maximum capacity. The purge deletes historical log data until the
disk falls below 60 percent capacity. This task runs every hour.
If your system has a very large storage capacity, threshold purge does not occur, but the log
table can contain no more than 365 days of historical data due to daily rollover.
When disk usage for the log data tablespaces reaches 70 percent, the purge monitoring utility
sends an e-mail to the Oracle Administrator. Upon receiving this e-mail, the Oracle
Administrator should back up all of the data using the backup procedure described in
Section 2.6, Standard Database Backup [p. 2-25].
Various scheduled reports are generated by NETSMART 1500. All of these reports are stored
in the appropriate directories on the disk and are backed up daily by the Oracle nightly
backups.
Depending on the size of the reports and the configuration of the database, the disk space is
appropriately allocated. For reports reaching the thresholds size limit on the disk, the reports
are deleted starting with the oldest one. The corresponding database entry for the report is
also dropped. The delete threshold limit for the reports is 90 percent of the allocated directory
space in the disk. On HA systems, periodically the reports are the snapshot reports copied to
the backup system from the active system. When user-initiated, the reports are recreated on
the backup system through the help of scripts.
FNC-1500-0050-110
CHAPTER 2
Alert Scripts
2.9
Alert Scripts
This section describes the database alert scripts. It includes the following subsections:
NO.
SUBSECTION
PAGE
2.9.1
Alert Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-37
2.9.2
Check Size of Alert File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-38
2.9.3
Check Size of File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-39
2.9.4
Check Size of File System Containing Archived Redo Log Files . . . . . . . . . . . . . . . . . . .
2-40
2.9.5
Check for Missing Archived Redo Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-41
Database alerts notify the Oracle user if there may be a problem with the Oracle database.
The database alert scripts are run daily from the Oracle users crontab. The Oracle user is
automatically notified of potential database problems through e-mail to the Oracle user
account.
If required, database alert scripts can be run manually through Heartbeat.
2.9.1
Alert Monitor
The alert monitor script is responsible for logging errors reported by the Oracle database.
Execute the alert monitor script as follows:
Step
1
Task

OR
Enter 4 Alert scripts.
Enter 1 Alert Monitor.
FNC-1500-0050-110

2-37
CHAPTER 2
Alert Scripts
The alert monitor script runs and checks for warnings or errors in the alert_nms.log file
as shown in the following output sample:
You have new mail.
SunOS 5.10
Generic June 2006
No Alert Messages since it last executed

2.9.2
If any errors are reported, contact FNC technical support.
Check Size of Alert File

This script monitors the size of the Oracle alert log file. When the size of the file reaches
5 MB, the file is compressed and renamed.
Check the size of the alert file as follows:
Step
1
Task

OR
Enter 2 Check Size of Alert File.
FNC-1500-0050-110
CHAPTER 2
Alert Scripts
The script runs and displays the size of alert_nms.log file. If the original size of the alert
file is 5 MB or greater, it is compressed and renamed as shown in the following output sample:
You have new mail.
SunOS 5.10
Generic June 2006
Sizes of Alert Files after compression if any:

-rw-r--r--
1 oracle
dba
71803 Jun 20 08:34 alert_nms.log

2.9.3
Check Size of File Systems

This script monitors the available space in the UNIX file system partitions used by the Oracle
database.
Check the size of the UNIX file system partitions as follows:
Step
1
Task

OR
Enter 3 Check size of FileSystems.
FNC-1500-0050-110

2-39
CHAPTER 2
Alert Scripts
The script runs and displays available free space in the UNIX partitions. A screen similar to
the following displays:
SunOS 5.10
Generic Jun 2000
You have new mail.
Sun Jun 25 10:22:25 CDT 2006
Filesystem / has 14016 MB of free space left
Filesystem /nsdata has 26182 MB free space left
2.9.4
If there is less than 300 MB free in one of the partitions, contact FNC technical support for
further assistance.
Check Size of File System Containing Archived Redo Log Files

This script monitors the available space in the UNIX file system storing the archived redo
logs. If 70 percent of the available space is used, a message is reported, and a backup of the
archived redo logs is initiated.
WARNING:
If 90 percent of the available space is used and the backup of the archived redo logs fails
due to unavailability of a tape, the archived redo log files are deleted.
Execute the script as follows:

Step
1
Task

OR
Enter 4 Check size of File System containing Archived Redo Log Files.
FNC-1500-0050-110
CHAPTER 2
Alert Scripts
The script runs and displays the available disk space in the archived redo log file partition. If
70 percent of the space is used, a message indicates that a backup of the archived log files has
been initiated. A screen similar to the following displays:
You have new mail.
SunOS 5.10
Generic June 2006
Filesystem /nsdata/nms/arch has enough free space (026182 MB)

2.9.5
Check for Missing Archived Redo Log Files

This script monitors the archived redo log files to ensure that all required files exist. If any files
are missing, partial recovery of the database may not be possible. In this case, you should do a
backup of the database immediately so that a valid and current backup of the database is
available. (Refer to Section 2.6, Standard Database Backup [p. 2-25].)
Check for missing archived redo log files as follows:
Step
1
Task

OR
Enter 5 Check for Missing Archived Redo Log Files.
FNC-1500-0050-110

2-41
CHAPTER 2
Alert Scripts
The script runs and verifies that all redo log files are available. If any are missing from
sequence, they are displayed. A screen similar to the following displays:
SunOS 5.8
Generic June 2006
You have new mail.
Last Archived Redo Log File Copied to tape was 10_1.arc
Beginning to search for missing Archived redo Log files...
Search Completed...
All Archived Redo Log Files are present.
If any redo log files are reported missing, you should do a backup of the database immediately
so that a valid and current backup of the database is available. (Refer to Section 2.6, Standard
Database Backup [p. 2-25].)
FNC-1500-0050-110
CHAPTER 2
Automated Maintenance
2.10
NO.
SUBSECTION
PAGE
2.10.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-43
2.10.2
Maintenance Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-46
Oracle maintenance jobs are set up during NETSMART 1500 installation. These jobs run
from the Oracle users crontab.
Note: Modifying Oracle maintenance jobs installed in the Oracle users crontab is not
recommended.
2.10.1
Overview
One of the maintenance tasks that is automatically configured to run daily at midnight is a
backup of the database (part of the eod.sh script). For this job, the tape used to store the
backup must be changed daily. The tapes storing the backup information should be stored in
off-site archives.
The Oracle Administrator must check e-mail regularly, because various cronjobs can generate
warning and error e-mail messages. E-mails are sent to the Oracle user for database-related
script status. Section 2.11.9, Database E-Mail Notification [p. 2-66], explains how the Oracle
Administrator e-mail address is specified.
FNC-1500-0050-110

2-43
CHAPTER 2
The maintenance jobs listed in Table 2-4 [p. 2-44] are executed at specific intervals during the
day to check for various system problems.
Note: These jobs can be executed manually, if required, from the Oracle user. All the scripts
listed in Table 2-4 [p. 2-44] are on the NETSMART 1500 server in the following directory:
/opt/NetSmart/oracle/scripts/maintenance.
Table 2-4: Automated Oracle Maintenance Jobs
Script Name
Interval Script is Run
Description
alert_mon
Every 15 minutes
This job checks for any messages/errors from the Oracle

database. Oracle logs status, warning, and error messages in an
alert log. This job sends an e-mail to the Oracle user if there are
any errors/warnings.
arch_miss
Every 3 hours
This job monitors the Oracle archived redo log files and verifies
that all the redo logs exist. If any are missing, an e-mail is sent to
the Oracle user, informing the administrator of the problem and
suggesting that an immediate backup of the system be
performed.
audit_purge.sh
Once per day at 5 a.m.
This job purges the audit tables.
chk_alert
Once per day at 11 p.m.
This job checks the size of the alert log. If the size exceeds a
predefined threshold (typically 5 MB), the file is compressed
and renamed with a timestamp. A new alert log is created.
chk_arch
Every 3 hours
This job monitors available space in the file system where the
Oracle archived redo log files are stored. If the archived redo logs
are occupying more than 70 percent of the partition capacity, a
backup of the archived log files is initiated. If the disk space use
reaches 90 percent, the archived redo log files are deleted.
chk_fs
Every 3 hours
This job checks for disk space problems in the following disk
partitions: /, /var, /usr/, and several of the /opt partitions. E-mail
is sent to the Oracle user, identifying the disk space use status.
chk_iostat
Every hour
This job checks for disk and I/O statistics.
chk_rpt_space
Every 3 hours
This job monitors the report file system. If the files have
occupied more than 90 percent of the allotted space it deletes
the files starting with the oldest one and drops the
corresponding database table till the space reaches less than 75
percent of the allotted space
clean_alert
Every Sunday at 7 a.m.
This job removes compressed Oracle alert log files that are more
than 30 days old.
clean_arch
This job removes archived log files that are more than 7 days
old.
clean_log
This job removes various log and output files that are more than
45 days old.
FNC-1500-0050-110
CHAPTER 2
Table 2-4: Automated Oracle Maintenance Jobs (Cont.)

Script Name
Description
clean_trc
This job removes any Oracle trace files that are more than 7 days
old.
conn_db
Every 15 minutes
This job verifies connectivity to the database. If the script

cannot connect to the database, an e-mail is sent to the Oracle
user to inform the NETSMART 1500 Administrator to restart
the Oracle listener.
dbarpt
Every hour
This job collects statistics on the Oracle database. The statistics

can identify whether tuning of the Oracle database is required. A
report is generated and e-mailed to the Oracle user if there is
information that requires follow up.
gather_stats
Every 3 hours
This job generates table statistics for better performance gain.
icheck
This job checks if index usage is optimal for predefined queries

and analyzes schema, if required.
monitor_log_space
Every hour
This job monitors the log tablespaces to see whether capacity has
reached the 70 or 90 percent thresholds. The tables in the log
tablespaces include fault history, TL1 event, 15-minute
performance monitoring, and 24-hour performance
monitoring. If the capacity has reached 70 percent, an e-mail is
sent to the Oracle user. If the 90 percent threshold is reached, a
purge is initiated.
nesecurity_purge
Once per day at 4:30 a.m.
This job purges Ne security data.
os_monitor
Every 20 minutes
This job monitors various Sun Solaris operating system

statistics, such as the following: CPU use, free swap space,
memory use, disk system statistics, and cache statistics. A report
is generated and e-mailed to the Oracle user to inform the
NETSMART 1500 Administrator of any follow-up task.
prebkup
This job creates a list of control files, redo log files, and database
files that are to be backed up. The output of this script is used by
the eod.sh script, which performs a backup of the database.
The location of this script is
/opt/NetSmart/oracle/scripts/operation/bkup.
roll_ns
Every hour
This jobs removes the oldest partition from the log tables (front
end).
report_mail
Once per day at 11:30 p.m.
This job sends the reports generated by the dbarpt and

os_monitor scripts to the Oracle user. The e-mail is sent only
if the reports contain information that requires the attention of
the NETSMART 1500 Administrator.
rmbu_purge.sh
Once per day at 5 a.m.
This job purges specific tables related to RMBU.
FNC-1500-0050-110

2-45
CHAPTER 2
Table 2-4: Automated Oracle Maintenance Jobs (Cont.)

Script Name
Description
stat_reco
This job creates a list of all of the control files, redo log files, and
database files. This list is used by database recovery scripts. The
location of this script is
/opt/NetSmart/oracle/scripts/operation/reco.
tl1batch_purge
Every hour
This job purges records older that 2 hours in tl1hbevent table.

The table is sized for 3 hours worth of data, which means that
every hour one hours worth of data is deleted.
validate.ksh
This job checks for invalid database objects and then validates if
it finds any.
pmregister_purge.sh
This job checks for PM tables and deletes relevant records.
2.10.2
Maintenance Scripts
This subsection includes the following items:
ITEM
PAGE
Clean Old Compressed ALERT Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-48
Clean Old ORACLE Trace File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-48
Clean Old Files and Old Archived Redo Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-49
Clean Old Log and out Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-50
Find Max Contiguous Space Available in Datafile for an Object . . . . . . . . . . . . . . .
2-50
Recreate Indexes on a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-51
Give Additional Space to the Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-52
Edit Oracle crontab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-52
Check Index Usage on Select Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-54
Check Invalid DB Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-54
Generate Zip File for Oracle Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-55
Analyze Data Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-55
Time Offset for Oracle Scheduled Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-56
Select Backup Device and Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-57
FNC-1500-0050-110
CHAPTER 2
The ORACLE DATABASE MAINTENANCE menu options shown below are run through
cronjobs. However, they also can be run from Heartbeat.
Note: Menu options 8, 10, 14, and 15 involving disk arrays and RAID are not supported in this
release. Menu option 18 is partially supported. Autoloader and RAID are not supported.
O R A C L E
D A T A
B A S E
M A I N T E N A N C E
1. Clean Old Compressed ALERT Files

2. Clean Old ORACLE Trace File
3. Clean Old Files and Old Archived Redo Files
4. Clean Old Log and out Files
5. Find Max Contiguous Space Available in Datafile for an Object
6. Recreate Indexes on a Table
7. Give Additional Space to the Tablespace
8. Select Tape to Remove from AutoLoader
9. Edit Oracle crontab
10. Disk Array Status
11. Check Index Usage on Select Queries
12. Check Invalid DB Scripts
13. Generate Zip File for Oracle Logs
14. Raid Controller Battery Status
15. Reset Raid Controller Battery Age
16. Analyze Data Schema
17. Time Offset for Oracle Scheduled Jobs
18. Select Backup Device and Path
p. Go back to the Previous Menu
q. Quit
FNC-1500-0050-110

2-47
CHAPTER 2
Clean Old Compressed ALERT Files

Executing this option deletes compressed Oracle files that are more that 15 days old. A screen
You have new mail.
clean_alert run on Sun Jun 25 15:18:03 CDT 2006 Present compressed alert
files if any
clean_alert over Sun Jun 25 15:18:03 CDT 2006
clean listener log run on Sun Jun 25 15:18:03 CDT 2006 Present compressed
listener files if any
clean listener log over Sun Jun 25 15:18:03 CDT 2006
clean oracle mail files run on Sun Jun 25 15:18:03 CDT 2006 Present
compressed oracle mail files if any
clean oracle mail files over Sun Jun 25 15:18:03 CDT 2006
Clean Old ORACLE Trace File

Executing this option deletes Oracle trace files that are more that 7 days old. A screen similar
SunOS 5.10
You have new mail.
Sun Jun 25 11:02:37 CDT 2006
After removal of *.trc files
Generic June 2006
./nms_ora_11935.trc
-rw-r----- 1 oracle dba 2504 Jun 25 20:00 ./nms_ora_11935.trc
./nms_ora_28102.trc
-rw-r----- 1 oracle dba 2505 Jun 25 1 20:00 ./nms_ora_28102.trc
clean_trc over Sun Jun 25 11:02:37 CDT 2006
./nms_ora_11935.trc
./nms_ora_28102.trc
./nms_ora_17859.trc
./nms_ora_13277.trc
./nms_ora_25411.trc
./nms_ora_17859.trc
FNC-1500-0050-110
CHAPTER 2
Clean Old Files and Old Archived Redo Files

Executing this option deletes archived redo log files that are more that 7 days old. A screen
Sun Micro25Jun2006systems Inc.
You have new mail.
SunOS 5.10
Generic June 2006
Sun Jun 25 13:27:28 CDT 2006

./schema.out
-rwxr-xr-x 1 oracle
dba
2425 Jun 25 17:34 ./schema.out
./DBArep25Jun2006.log
./purge_backup.25Jun2006:20:00:00
./backup_control.25Jun2006
./backup_control.25Jun2006
./os_monitor.25Jun2006
clean_ log over Sun Jun 25 13:27:28 CDT 2006
./backup_control.25Jun2006: No such file or directory
./arch_backup.25Jun2006
./conn_db.25Jun2006
-rw-r--r-- 1 oracle
dba
307 Jun 25 22:00 ./arch_backup.25Jun2006
./exp_backup.25Jun2006:20:10:05-rw-r--r-- 1 oracle dba 305 Jun 25 20:10
./exp_backup.25Jun2006:20:10:05
./conn_db.25Jun2006
./exp_backup.25Jun2006:20:10:05
./conn_db.25Jun2006: No such file or directory
./stat_db.25Jun2006
-rw-r--r-- 1 oracle
dba
168 Oct 6 23:50 ./stat_db.25Jun2006
./chk_fs.25Jun2006
-rw-r--r-- 1 oracle
dba
421 Oct 6 22:00 ./chk_fs.25Jun2006
./chk_orafs.25Jun2006
-rw-r--r-- 1 oracle
dba
79 Oct 6 22:00 ./chk_orafs.25Jun2006
./chk_archfs.25Jun2006
-rw-r--r-- 1 oracle
dba
79 Oct 6 22:00 ./chk_archfs.25Jun2006
./arch_miss.25Jun2006
-rw-r--r-- 1 oracle
dba
173 Oct 6 22:00 ./arch_miss.25Jun2006
-rw-r--r-- 1 oracle
dba
2583 Jun 25 00:10
FNC-1500-0050-110

2-49
CHAPTER 2
Clean Old Log and out Files

Executing this option deletes log files and output files that are more that 15 days old. A screen

You have new mail.
Sun Jun 25 15:42:19 CDT 2006
clean_ log over Sun Jun 25 15:42:19 CDT 2006
Find Max Contiguous Space Available in Datafile for an Object

This option should be run, when required, by a user with database administration (DBA)
knowledge. The output of this procedure displays how much maximum contiguous space is
available in a tablespace of an object.
The script prompts you for the name of the table or index. A screen similar to the following
displays:
SunOS 5.10
Generic June 2006
Enter name for the TABLE/INDEX : corbaobjectentry

Max Next Extent size can be :
Owner Object_name
Datafile
Name Max_next(KB)
------ --------------- -------------------- -----------FENICS CORBAOBJECTENTR d_netsmart01.dbf
2047992
Y
FENICS CORBAOBJECTENTR d_netsmart03.dbf
Y
1661160

Y
1996752

Y
511992
Owner Object_name
Datafile
Name Max_next(KB)
------ --------------- -------------------- -----------Hit any key to Continue.
FNC-1500-0050-110
CHAPTER 2
Recreate Indexes on a Table

This option should be run, when required, by a user with DBA knowledge. Executing this
option recreates indexes on fragmented tables. A screen similar to the following displays:
You have new mail.
SunOS 5.10
Generic June 2006
Please enter owner of the table for which indexes to be recreated :

ownername
Please enter name of the table for which indexes to be recreated :
tablename
FNC-1500-0050-110

2-51
CHAPTER 2
Give Additional Space to the Tablespace

option provides additional tablespace. You are prompted to enter the name of the tablespace
to be extended. You can enter ? to get a list of tablespace names, as shown in the following
example:
You have new mail.
Enter the Tablespace name to be extended [?,q] ?
Enter one of the following Tablespace names : Please enter a
string which matches one of the following patterns:
system
tools
users
d_meta
d_docmgt
d_activityevent
d_emlnml
d_faulthistory
d_netsmart
d_pm
d_systemevent
d_tl1event
d_tl1uplinkevent
i_emlnml
i_netsmart
i_pm
rbs
temp
Enter the Tablespace name to be extended [?,q] temp
Tablespace TEMP extended.
Edit Oracle crontab

option changes the default time that various Oracle maintenance jobs are run.
CAUTION:
Contact FNC technical support at 1-800-USE-FTAC before using this option.
FNC-1500-0050-110
CHAPTER 2
This option opens the crontab file in your default editor. A screen similar to the following
displays:
This file contains cron entries which are to be run through "oracle" id.
DAILY SCRIPTS
Every 15 mins.
5,20,35,50 * * * * cd /opt/NetSmart/oracle/scripts/maintenance ;
nohup /opt/NetSmart/oracle/scripts/maintenance/alert_mon &
5,20,35,50 * * * * cd /opt/NetSmart/oracle/scripts/maintenance ;
nohup /opt/NetSmart/oracle/scripts/maintenance/conn_db &
5,20,35,50 * * * * cd /opt/NetSmart/oracle/scripts/maintenance ; nohup
/opt/NetSmart/oracle/scripts/maintenance/stat_db &
Every 20 mins.
.....
/bkup/backup &
WEEKLY SCRIPTS
Every Sunday at 7.00 hours
0 7 * * 0 cd /opt/NetSmart/oracle/scripts/maintenance ; nohup /opt
NetSmart/oracle/scripts/maintenance/clean_alert &
NetSmart/oracle/scripts/maintenance/clean_trc &
NetSmart/oracle/scripts/maintenance/analyze_tab &
FNC-1500-0050-110

2-53
CHAPTER 2
Check Index Usage on Select Queries

This option checks whether indexes are being used when the selected queries are invoked. A
screen similar to the following displays:
You have new mail.
Index usage check...
Starting to analyze statements...
STATEMENT: select componentid from fenics.pnecomponent where neid='X' and
componentid='Y'
STATEMENT: select componentid from fenics.pnecomponent where
componentid='x'
STATEMENT: select componentid from fenics.PNEComponent WHERE OID = 'x'
STATEMENT: select neid from fenics.pnecomponent where oid in ('x','k')
STATEMENT: delete from fenics.fault where oid ='k'
STATEMENT: select neid from fenics.pcrossconnect where
(pcrossconnect.neid='x') and ((totpname='y') and (fromtpname='i'))
STATEMENT: Select oid from fenics.pnecomponent
STATEMENT: SELECT oid, neid FROM fenics.NE
STATEMENT: select oid from fenics.nonkeygroup
STATEMENT: select * from fenics.corbaobjectentry where objoid='x'
STATEMENT: select * from fenics.physicallink where
a_end_portnamingattribute='x'
STATEMENT: select tid from pm.pmmonval15min where tid='x'
Check Invalid DB Scripts

This option revalidates Database Objects that are invalid. Executing this option tries to
validate the objects five times. After the fifth try, a list of database objects that are still in an
invalid state is displayed. A screen similar to the following displays:
You have new mail.
SunOS 5.10
Generic June 2006
Validating schema : FENICS

Success.
FNC-1500-0050-110
CHAPTER 2
Generate Zip File for Oracle Logs

This option generates a ZIP file of the oracle logs and tells where the file is created. A screen
SunOS 5.10
You have new mail.
Generating file : /tmp/NSDBlog.tar
Generic June 2006
Archive of log files created : /opt/nsoracle/remoteadminlogs/NSDBlog

<timestamp: DDMONHHMMSSYY>
Analyze Data Schema

This option analyzes and reports the data schema. A screen similar to the following displays:
SunOS 5.10
Generic June 2006
You have new mail.
Starting table analysis...
Schema FENICS is analyzed schema analyzed and report generated in
/opt/NetSmart/oracle/scripts/maintenance/out/analyze_tab.25Jun072401
Starting table analysis...Schema PM is analyzed schema analyzed and report
generated in
/opt/NetSmart/oracle/scripts/maintenance/out/analyze_tab.25Jun073400
FNC-1500-0050-110

2-55
CHAPTER 2
Time Offset for Oracle Scheduled Jobs

This option allows you to enter an offset for the entire database job schedule. A screen similar
SunOS 5.10
Generic June 2006
Enter the no of Hours you want the Oracle Scheduled jobs to be offset (for
HELP enter '?') [?,q] ?
The Input entered will be used to Offset the Scheduled Oracle jobs
by
that many Hours (valid range is +-1 to +-12)
Enter the no of Hours you want the Oracle Scheduled jobs to be offset (for
HELP enter '?') [?,q] +1
Changed the timings of Scheduled Oracle cron jobs by 1 Hours
FNC-1500-0050-110
CHAPTER 2
Select Backup Device and Path

This option selects a backup device and path. A screen similar to the following displays:
SunOS 5.10
Generic February 2000
Current Backup Device Type is Standalone.

Select new device type:
1. Standalone
2. Autoloader
3. Custom
4. None
5. NoBackupNoRecovery
6. QUIT
Enter choice : 2
Currently selected Tape Device Path is /dev/rmt/0.
Select new device:
1. /dev/rmt/0
2. QUIT
Enter choice : 1
No changes in Backup Device Type..
Changing Backup Device Type from Standalone to Autoloader ...
Backup types are described as the following:
Standalone(default) Backup uses both the hard-drive and a tape device. The tape
device holds only one tape. This backup method is used for configurations of fewer
than 4000 NE.
Note: Autoloader Backup is not supported in this release.
FNC-1500-0050-110
CustomBackup uses both the hard-drive and a tape device, however, the backup tape
device is an external entity and user is responsible for moving the backup from the
hard-drive to the tape device. Used for 8000 NE configurations. The tape device
requires additional software not included with the NETSMART 1500 NMS
application.

2-57
CHAPTER 2
NoneOnly hard-drive backup provided. This backup is used in debugging situations

and is not used in normal operations.
NoBackupNoRecoveryNeither hard-drive backup or tape backup is taken. The

database runs in no archive log mode. No space is allocated either for backup or for
database archive logs. This backup method is used only in the development
environment.
FNC-1500-0050-110
CHAPTER 2
System and Configuration Information
2.11

This section identifies files and configuration information that may be useful when
troubleshooting the Oracle database. It includes the following subsections:
NO.
SUBSECTION
PAGE
2.11.1
System Equipment Inventory Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-60
2.11.2
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-63
2.11.3
Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-63
2.11.4
Database Control Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-65
2.11.5
Redo Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-65
2.11.6
Backup Files on Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-66
2.11.7
Core Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-66
2.11.8
Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-66
2.11.9
Database E-Mail Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-66
FNC-1500-0050-110

2-59
CHAPTER 2
2.11.1
System Equipment Inventory Reports

The sys_info_report script generates compressed reports about system equipment
inventory from data stored in the pne_component_do_storage table. This subsection
explains how to use the script to generate a report and uncompress it.
Note: Additional options for using the sys_info_report script are described in the following
help display available from the NETSMART 1500 Equipment Inventory Information menu
(displayed after Step 4 [p. 2-61] of the following procedure).
HELP
---This program gets system equipment inventory information for all the
attributes defined in the menu.
User can select one of the attributes as the driving criteria for the
report.
The driving criteria accepts wild card (*).
The report is generated by default in
/opt/NetSmart/oracle/out/eqpt_inventory_report directory.
Attributes in the report are separated by space.
"NULL" is listed for those attributes whose values are not found.
Total Disk Space required may be around 75 MB per 1,000 NEs. Note that the
final report will be compressed and the size of the file will be
significantly smaller.
Total Time required may be around 7 Mins per 1,000 NEs.
Usage : ./sys_info_report
or
./sys_info_report OUTPUT_DIR="<dir_name>"
RESULT_FILE="<result_file>"
where
-- OUTPUT_DIR is directory where final report file is generated.
By default, it is /opt/NetSmart/oracle/out/eqpt_inventory_report
-- RESULT_FILE is the final system info file created.
By default it is named as sys_info_<query attribute>.<time stamp>.Z
Generate a system equipment inventory report as follows:

Step
1
Task
Log on the NETSMART 1500 server as user oracle (refer to Section 2.2, Oracle User
Account [p. 2-5]) or netsmart (refer to Section 3.2, Creating UNIX Accounts [p. 3-7]).
FNC-1500-0050-110
CHAPTER 2
Open a terminal window. (Right-click in the desktop background to bring up the workspace
menu, and then select Tools and then Terminal.)
Enter the following command to change directories:

cd /opt/NetSmart/oracle/scripts/maintenance
Enter the following command to start the script:

./sys_info_report
The NETSMART 1500 Equipment Inventory Information menu displays:

NETSMART1500 SYSTEM EQUIPMENT INVENTORY
INFORMATION----------------------------------------------1. TID
2. AID
3. TYPE
4. CLEI
5. DOM
6. SERIALNO
7. UNITNAME
8. VENDOR_ID
9. VENDOR_REV
h. Help
q. Quit Enter the search Criteria ...
Enter the number of the attribute you want the search criteria to apply to.
In the following example, number 3 was entered to select the TYPE attribute:
3
Enter the Search value for TYPE ( Press Enter for selecting all values )
Enter a search string for the selected attribute (or press ENTER to get a full report).
Note: The search string can include the * (asterisk) wildcard character. For the example shown
below, the search string DS* was entered.
FNC-1500-0050-110

2-61
CHAPTER 2
The report is generated, compressed, and stored as shown in the following example:
DS*
*********************************************
Start time is Sun Jun 25 10:47:49 CDT 2006
*******************************************************
Creating Query Files Sun Jun 25 10:47:49 CDT 2006
Processing for AID Sun Jun 25 10:48:43 CDT 2006
Processing for TYPE Sun Jun 25 10:48:46 CDT 2006
Processing for CLEI Sun Jun 25 10:49:49 CDT 2006
Processing for DOM Sun Jun 25 10:49:55 CDT 2006
Processing for SERIALNO Sun Jun 25 10:50:15 CDT 2006
Processing for UNITNAME Sun Jun 25 10:50:20 CDT 2006
Processing for VENDOR_ID Sun Jun 25 10:50:49 CDT 2006
Processing for VENDOR_REV Sun Jun 25 10:51:20 CDT 2006
*******************************************************
Creating NETSMART1500 System Equipment Inventory Information File :
/opt/NetSmart/oracle/out/eqpt_inventory_report/sys_info_TYPE.26Jun104749.Z
Sun Jun 25 10:51:20 CDT 2006
*******************************************************
Deleting Temporary Files
*******************************************************
Process Finished Sun Jun 25 10:51:20 CDT 2006
*******************************************************
The display shows the name of the compressed inventory report file. Its file name is:
sys_info_<query attribute>.<time stamp>.Z
By default, the file is stored in the following directory:

/opt/NetSmart/oracle/out/eqpt_inventory_report
Enter the following commands to change directories and uncompress the report file:
cd /opt/NetSmart/oracle/out/eqpt_inventory_report
uncompress sys_info_<query attribute>.<time stamp>.Z
The file name is:

sys_info_<query attribute>.<time stamp>
The file is uncompressed and stored in directory:

/opt/NetSmart/oracle/out/eqpt_inventory_report
FNC-1500-0050-110
CHAPTER 2
The following is a sample report:

Note: You can view the file using UNIX commands such as more or less.
#*************************************************************************
#
NETWORK ELEMENTS EQUIPMENT REPORT
#*************************************************************************
# Report Driving Criteria
: TYPE
# Additional Selection Criteria
: where TYPE like DS*
# Reporting Time
: Sun Jun 25 10:51:20 CDT 2006
#*************************************************************************
TID AID TYPE
CLEI
DOM SERIALNO UNITNAME VENDOR_ID VENDOR_REV
**************************************************************************
600-ADX-05 IFA6-10 DS3 SNI45E0BAA 00.07
01285 IFA6-D3U1 FC9520D3U1 05
600-ADX-05 IFA6-11 DS3 SNI4EE0BAA 99.04
00306 IFA6-D3U1 FC9520D3U1 01
00004 IFA6-D3U1 FC9520D3U1 05
600-ADX-06 IFA6-11 DS3 SNI4EE0BAA 99.04
00234 IFA6-D3U1 FC9520D3U1 01
00367 IFA6-D3U1 FC9520D3U1 03
600-ADX-06 IFA6-3 DS1P SN2PEFABAA 00.05
00355 IFA6-D1U1 FC9520D1U1 02
600-ADX-06 IFA6-4 DS1B SNP8360CAA 00.04
00179 IFA6-D1U1 FC9520D1U1 01
600-ADX-06 IFA6-5 DS1E DS1_E 99.10
00112 IFA6-D1U1 FC9520D1U1 01
2.11.2
Log Files
Log files keep records of various activities, events, and reports:
2.11.3
The log files generated during database backup are stored in

/opt/NetSmart/oracle/scripts/operation/bkup/out.
The log files generated during database restoration are stored in

/opt/NetSmart/oracle/scripts/operation/reco/out.
The log files generated from various Oracle maintenance scripts are stored in
/opt/NetSmart/oracle/scripts/maintenance/out.
Tablespaces
Oracle stores data logically in tablespaces and physically in data files associated with the
corresponding tablespace. Each tablespace consists of one or several data files. NETSMART
1500 and Oracle-specific data are collectively stored in many tablespaces.
FNC-1500-0050-110

2-63
CHAPTER 2
Table 2-5 [p. 2-64] defines tablespaces for Oracle data, and Table 2-6 [p. 2-64] defines
tablespaces for NETSMART 1500.
Table 2-5: Tablespaces Used for Oracle Data
Tablespace
Description
SYSTEM
Used internally by Oracle
ROLLBACK
Used by Oracle for transaction rollback and read consistency
TEMP
Used by Oracle for sorting on disk
TOOLS
Used to store any Oracle tool data
USERS
Used to store data for users other than NETSMART 1500, such as other
Oracle users created by the System Administrator
SYSAUX
Used internally by Oracle
Table 2-6: Tablespaces Used for NETSMART 1500 Data (1 of 2)

Tablespace
Description
D_ACTIVITYEVENT
Contains activity events data
D_DOCMGT
Contains NETSMART 1500 documentation pages
D_EMLNML
Contains NETSMART 1500 EML and NML data
I_EMLNML
Contains index data for the EMLNML data
D_FAULTHISTORY
Contains NETSMART 1500 alarms history
D_META
Contains data and indexes for the Metamodel data (Metamodel data consists
of static tables that describe the characteristics of the NEs managed by
NETSMART 1500.)
D_NETSMART
Contains NETSMART 1500 data
I_NETSMART
Contains indexes for the NETSMART 1500 tables
D_OF
Contains Open Fusion data
D_PM
Contains log data tables, such as 15-MIN PM and 24-HOUR PM

information
D_PMCORE
Contains PM core data
I_PMCORE
Contains PM index data
REPLIC_TS
Contains HA data (if HA is enabled)
I_PM
Contains indexes for the D_PM tables
D_RNAUDITEVENT
Contains NETSMART 1500 RNAUDITEVENT log table data
D_SYSTEMEVENT
Contains system event data
D_TL1EVENT
Contains TL1 events and retrieve headers data
D_TL1UPLINKEVENT
Contains TL1 uplink events data
FNC-1500-0050-110
CHAPTER 2
Table 2-6: Tablespaces Used for NETSMART 1500 Data (2 of 2)
2.11.4
Tablespace
Description
I_SYSTEMEVENT
Contains system event index data
I_TL1EVENT
Contains TL1 events index data
I_TL1UPLINKEVENT
Contains TL1 uplink events index data
I_FAULTHISTORY
Contains fault history index data
I_ACTIVITYEVENT
Contains activity events index data
I_RNAUDITEVENT
Contains NETSMART 1500 RNAUDITEVENT log table index data
MIG
Used during release migration
DW
Used for storing data warehouse table data
CDC
Used for storing change records from transaction tables that are involved in
data warehouse schema
Database Control Files

The Oracle database requires control files to start. The control files are created during
NETSMART 1500 installation and are used to control the database options and operations in
NETSMART 1500. The control files are duplicated to ensure that they are always available
for Oracle startup.
The control files are stored in the following locations:
2.11.5
/opt/NetSmart/oracle/nms/oradata/control01.ctl
/nsdata/nms/oradata/control02.ctl
/nsdata/nms/oradata/control03.ctl
Redo Files
Redo log files collect the transaction history of the NETSMART 1500 Oracle database. The
log files are mirrored over two different locations. If one of the mirrored files is damaged, the
database continues to run using the second mirror.
The following are the primary redo log files for a 4x4x8 system:
/nsdata/nms/oradata/redonms01a.log
On a 2x2x4 system, the destination is the same as primary.
FNC-1500-0050-110

2-65
CHAPTER 2
Archived redo log files are created when the NETSMART 1500 database is running in archive
mode, which is the default mode for NETSMART 1500. The archived log files are backed up
nightly by the NETSMART 1500 backup script eod_backup executed as root as a nightly
cronjob.
2.11.6
Backup Files on Disk

During the daily backup procedure (part of the eod_backup script), the data files associated
with all the tablespaces are copied into the directory /nsdata/nms/backup before being
moved to tape and then deleted.
2.11.7
Core Files
Oracle core dumps are stored in /opt/NetSmart/oracle/admin/nms/cdump. This
directory is cleaned on a weekly basis by an Oracle maintenance job.
2.11.8
Trace Files
Trace files can provide information related to an error identified by the Oracle database. Trace
files are generated by various background processes and by Oracle. These trace files are stored
in the following locations:
/opt/NetSmart/oracle/admin/nms/bdump
/opt/NetSmart/oracle/admin/nms/udump
These directories are cleaned on a weekly basis by an Oracle maintenance job.
2.11.9
Database E-Mail Notification

E-mail notification to the Oracle Administrator is controlled by the following file on the
NETSMART 1500 server:
$ORACLE_BASE/scripts/operation/oraenv_ksh
Here, $ORACLE_BASE is an environmental variable set in file

/opt/NetSmart/oracle/.cshrc.
Example: If ORACLE_BASE is set to /opt/NetSmart/oracle, then the file is
/opt/NetSmart/oracle/scripts/operation/oraenv_ksh.
The following entry within that file specifies the Oracle Administrator e-mail address:
mail_admin=<E-mail Address>
FNC-1500-0050-110
CHAPTER 2
Export Procedures
2.12
Export Procedures
NO.
SUBSECTION
PAGE
2.12.1
Export of NETSMART 1500 LOGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-68
2.12.2
Export of PM LOGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-69
The processes in the Oracle Database Import/Export menu shown below are on-demand
maintenance scripts. They are not monitoring scripts and should be run only by designated
DBA users when necessary.
1.) Export
2.) Export
d. Disable
m. Go back
p. Go back
q. Quit
FNC-1500-0050-110
of NETSMART 1500 LOGS

of PM LOGS
Root Access (return to netsmart)
to the Main Menu
to the Previous Menu

2-67
CHAPTER 2
Export Procedures
2.12.1
Export of NETSMART 1500 LOGS

This option exports NETSMART 1500 log tables in compressed mode and stores them on
tape using cpio.
Enter path name to keep export dump [ /opt/NetSmart/oracle/exp_bkp ] [?]
Export: Release 10.2.0.2.0 - Production on Sun Jun 25 13:07:51 2006
(c) Copyright 2006 Oracle Corporation. All rights reserved.
Connected to: Oracle8i Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning option
JServer Release 10.2.0.2.0 - Production
Export done in US7ASCII character set and US7ASCII NCHAR character set
About to export specified tables via Conventional Path ...
. . exporting table
TL1EVENT
. . exporting partition
TL1EVENT_0
0 rows exported
TL1EVENT_1
0 rows exported
TL1EVENT_2
0 rows exported
TL1EVENT_3
0 rows exported
TL1EVENT_4
0 rows exported
TL1EVENT_5
0 rows exported
TL1EVENT_6
0 rows exported
TL1EVENT_7
0 rows exported
TL1EVENT_8
0 rows exported
TL1EVENT_9
0 rows exported
TL1EVENT_10
0 rows exported
TL1EVENT_11
0 rows exported
FNC-1500-0050-110
CHAPTER 2
Export Procedures
2.12.2
Export of PM LOGS
This option exports PM log tables in compressed mode and stores them on tape using cpio.
Connected to: Oracle8i Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning option
JServer Release 10.2.0.2.0 - Production
Export done in US7ASCII character set and US7ASCII NCHAR character set
About to export specified tables via Conventional Path ...
. . exporting table
PMMONVAL15MIN_0
0 rows exported
PMMONVAL15MIN_0
0 rows exported
PMMONVAL15MIN_1
0 rows exported
PMMONVAL15MIN_2
0 rows exported
PMMONVAL15MIN_3
0 rows exported
PMMONVAL15MIN_4
0 rows exported
PMMONVAL15MIN_5
0 rows exported
PMMONVAL15MIN_30
0 rows exported
.................................................................
. . exporting table
PMMONVAL24HOUR
PMMONVAL24HOUR_0
0 rows exported
PMMONVAL24HOUR_1
0 rows exported
PMMONVAL24HOUR_6
0 rows exported
................................................................
PMMONVAL24HOUR_30
0 rows exported
Export terminated successfully without warnings.
Backup will be done on /dev/rmt/0n
Make sure that /dev/rmt/0n is ONLINE
and containing Write Enabled DAT for Backup
STARTING BACKUP Of export File/s AT Sun Jun 25 13:10:09 CST
2006
Backup will Start after 1 seconds.
Starting backup to Tape...
FNC-1500-0050-110

2-69
3
CHAPTERS/APPENDIXES
NETSMART 1500 ADMINISTRATION
1 Introduction
3 NETSMART 1500
Administration
NO.
SECTION
4 UNIX System
Administration
3.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-3
3.2
Creating UNIX Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-7
6 Service Support
3.3
Starting Up and Shutting Down . . . . . . . . . . . . . . . . . . . . . . . .
3-8
7 High Availability
Administration
3.4
Troubleshooting Server and Clients . . . . . . . . . . . . . . . . . . . .
3-12
3.5
Enabling/Disabling Program Groups. . . . . . . . . . . . . . . . . . . .
3-16
3.6
NETSMART 1500 Trace Menu . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-28
3.7
Installing NE Software Generics . . . . . . . . . . . . . . . . . . . . . . . .
3-28
3.8
Configuring the ObjectStream License. . . . . . . . . . . . . . . . . .
3-37
3.9
Export Security Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-39
3.10
Import Security Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-40
3.11
Resync NE Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-41
3.12
Configuring the Communication Server/NE Logon. . . . . . .
3-42
3.13
Security E-Mail Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-45
3.14
Broadcast Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-46
3.15
Pre-Logon Warning Banner Administration . . . . . . . . . . . . .
3-49
3.16
Enabling/Disabling RTRV-HDR Logging . . . . . . . . . . . . . . . . .
3-55
3.17
NETSMART 1500 License Administration . . . . . . . . . . . . . . . .
3-58
3.18
Service Pack Installation on HA-Enabled Federations . . . .
3-73
FNC-1500-0050-110
PAGE

CHAPTER 3
NETSMART 1500 Administration
NO.
SECTION
PAGE
3.19
Transaction Debugging Client. . . . . . . . . . . . . . . . . . . . . . . . . .
3-76
3.20
LNE Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-80
3.21
Connection Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-82
3.22
Topology Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-84
3.23
Configure SONET-SDH Terminology Mapping . . . . . . . . . . .
3-88
3.24
Set Branding Image in Topology View . . . . . . . . . . . . . . . . . .
3-90
3.25
Remove Branding Image from Topology View . . . . . . . . . . .
3-90
FNC-1500-0050-110
CHAPTER 3
Overview
3.1
Overview
This chapter provides administrative information and describes administrative tasks for the
NETSMART 1500 server and client software.
WARNING:
Many of the operations described in this chapter use the Heartbeat tool. When using
Heartbeat with root enabled, do not press CTRL+C. Doing so may cause Heartbeat to
terminate abnormally. CTRL+C may be used with Heartbeat when root is not enabled.
FNC-1500-0050-110

3-3
CHAPTER 3
Overview
NETSMART 1500 is administered using the NETSMART 1500 Administration option of the
Heartbeat tool. This option provides the following menu, which is the starting point for most
of the procedures described in this chapter.
N E T S M A R T 1500 A D M I N I S T R A T I O N
1. Start NETSMART 1500 Server Processes +
2. Stop NETSMART 1500 Server +
3. Check NETSMART 1500 Server Status +
4. Start NETSMART 1500 Client +
5. Enable Program Groups +
6. Disable Program Groups +
7. NETSMART 1500 Trace Menu
8. Load NE Software Generic Files *
9. Start ObjectStream License Manager *
10. Export Security Data +
11. Import Security Data +
12. Resync NE Data
13. NETSMART 1500 HA Configuration
14. NETSMART 1500 HA Unconfiguration
15. Pre-login Warning Banner Operations
16. Enable/Disable RTRV-HDR Logging
17. Upgrade Netsmart 1500 License *
18. License Information
19. Transaction Debugging Client
20. LNE Discovery
21. Connection Discovery
22. Topology Discovery Administration
23. Set Branding Image to display in Topology GUI client
24. Remove Branding Image from Topology GUI client
25. PCN and PNE Update
26. Change PCN and PNE Update Schedule
27. Display PCN and PNE Update Schedule
q. Quit
* may require root access
+ can only be executed by NETSMART 1500 administrator
Select a number/letter (case insensitive):
Note: Menu items denoted with an asterisk (*) require root access. Menu items denoted with a
plus sign (+) can be executed only by the NETSMART 1500 Administrator.
Table 3-1 [p. 3-5] lists the menu and submenu items for NETSMART 1500 administration
and where they are described in this practice.
FNC-1500-0050-110
CHAPTER 3
Overview
Table 3-1: NETSMART 1500 Administration Menu Items

Menu Item
Reference
1. Start NETSMART 1500 Server Processes
Section 3.3.1, Start Server [p. 3-8]
2. Stop NETSMART 1500 Server
Section 3.3.3, Shut Down Server [p. 3-10]
3. Check NETSMART 1500 Server Status
Section 3.4.1, Check the Status of Server Processes [p. 3-12]
4. Start NETSMART 1500 Client
Section 3.3.2, Start Client on the Server [p. 3-9]
5. Enable Program Groups
Section 3.5, Enabling/Disabling Program Groups [p. 3-16]
1. Enable PM
Section 3.5.1, Enable Performance Management [p. 3-17]
2. Enable EMLNML
Section 3.5.3, Enable EMLNML [p. 3-19]
3. Enable TL1Uplink
Section 3.5.5, Enable TL1 Uplink [p. 3-20]
4. Enable FW74NM
Section 3.5.7, Enable FLASHWAVE 7400 Node Managers

[p. 3-22]
5. Enable Webservice
Section 3.5.9, Enable Webservice [p. 3-23]
6. Disable SNMPUplink
Section 3.5.11, Enable SNMP Uplink [p. 3-25]
7. Enable all of the above
Section 3.5.13, Enable All Optional Program Groups [p. 3-26]
6. Disable Program Groups
Section 3.5, Enabling/Disabling Program Groups [p. 3-16]
1. Disable PM
Section 3.5.2, Disable Performance Management [p. 3-18]
2. Disable EMLNML
Section 3.5.4, Disable EMLNML [p. 3-19]
3. Disable TL1Uplink
Section 3.5.6, Disable TL1 Uplink [p. 3-21]
4. Disable FW74NM
Section 3.5.8, Disable FLASHWAVE 7400 Node Managers

[p. 3-22]
5. Disable Webservice
Section 3.5.10, Disable Webservice [p. 3-24]
6. Disable SNMPUplink
Section 3.5.12, Disable SNMP Uplink [p. 3-26]
7. Disable all of the above
Section 3.5.14, Disable All Optional Program Groups [p. 3-27]
Section 3.6, NETSMART 1500 Trace Menu [p. 3-28]
8. Load NE Software Generic Files
Section 3.7, Installing NE Software Generics [p. 3-28]
9. Start ObjectStream License Manager
Section 3.8, Configuring the ObjectStream License [p. 3-37]
10. Export Security Data
Section 3.9, Export Security Data [p. 3-39]
11. Import Security Data
Section 3.10, Import Security Data [p. 3-40]
FNC-1500-0050-110

3-5
CHAPTER 3
Overview
Table 3-1: NETSMART 1500 Administration Menu Items (Cont.)

Menu Item
Reference
12. Resync NE Data
Section 3.11, Resync NE Data [p. 3-41]
FNC-1500-0050-100, Installation Guide, Section 4.3, Configuring

the Server [p. 4-8]
Section 7.11, Unconfiguring NETSMART 1500 HA Service

[p. 7-27]
Section 3.15, Pre-Logon Warning Banner Administration [p. 3-49]
1. Enable pre-login warning banner
Section 3.15.1, Enable the Pre-Logon Warning Banner [p. 3-50]
2. Disable pre-login warning banner
Section 3.15.2, Disable the Pre-Logon Warning Banner [p. 3-51]
3. Import file for pre-login warning

banner text
Section 3.15.3, Import the Pre-Logon Warning Banner from a File

[p. 3-51]
4. Edit pre-login warning banner text
Section 3.15.4, Retrieve and Edit the Pre-Logon Warning Banner

[p. 3-52]
5. Current status of pre-login warning

banner
Section 3.15.5, Check the Status of Pre-Logon Warning Banner

[p. 3-53]
Section 3.16, Enabling/Disabling RTRV-HDR Logging [p. 3-55]
1. Enable RTRV-HDR Logging
Section 3.16.1, Enable RTRV-HDR Logging [p. 3-55]
2. Disable RTRV-HDR Logging
Section 3.16.2, Disable RTRV-HDR Logging [p. 3-56]
17. Upgrade Netsmart 1500 License
Section 3.17.2, Upgrade NETSMART 1500 License [p. 3-59]
Section 3.17.1, Display NETSMART 1500 License Information

[p. 3-58]
Section 3.19, Transaction Debugging Client [p. 3-76]
20. LNE Discovery
Section 3.20, LNE Discovery [p. 3-80]
Section 3.21, Connection Discovery [p. 3-82]
Section 3.22, Topology Discovery [p. 3-84]
Section 3.24, Set Branding Image in Topology View [p. 3-90]
24. Remove Branding image from Topology GUI client
Section 3.25, Remove Branding Image from Topology View

[p. 3-90]
25. Start PCN and PCE Update
FNC-1500-0050-420, Reports, Chapter 4, Section 4.3 [p. 4-3].

Updates the data required for PCN and equipment reports
FNC-1500-0050-110
CHAPTER 3
Creating UNIX Accounts
Table 3-1: NETSMART 1500 Administration Menu Items (Cont.)

Menu Item
Reference
FNC-1500-0050-420, Reports, Chapter 4, Section 4.3 [p. 4-3].

Modifies the update schedule for running PCN and PNE updates
FNC-1500-0050-420, Reports, Chapter 4, Section 4.3 [p. 4-3],

Displays the PCN and PNE Update Schedule
3.2
Creating UNIX Accounts

A special UNIX account is provided for the NETSMART 1500 Administrator to:
Administer the NETSMART 1500 server
Troubleshoot NETSMART 1500 server problems
Run background NETSMART 1500 processes
The user name for this account is netsmart. Table 3-2 [p. 3-7] lists the user account
information.
Table 3-2: NETSMART 1500 Administrator UNIX User Account Information
User
Shell
Home
Group
netsmart
/bin/csh or
/bin/ksh
/opt/NetSmart
netsmart
This information is needed for Lightweight Directory Access Protocol (LDAP), NIS, or NIS+
setup of the UNIX user account. Provide this information to the Network System
Administrator to set up LDAP, NIS, or NIS+ user account verification.
If the NETSMART 1500 system is configured to use local files instead of LDAP, NIS, or
NIS+, the installation sets up the account automatically. No additional configuration is
required.
The NETSMART 1500 software requires a separate logon for the NETSMART 1500 system
(used when starting the NETSMART 1500 client graphical user interface [GUI]) in addition
to the UNIX logon. Upon installation, the NETSMART 1500 software is configured to use
the NETSMART 1500 UNIX user account and password for both logons.
Note: The NETSMART 1500 UNIX user account is not required on NETSMART 1500 clients, and
the install does not configure a NETSMART 1500 UNIX user account on client systems.
FNC-1500-0050-110

3-7
CHAPTER 3
Starting Up and Shutting Down
The NETSMART 1500 software on NETSMART 1500 clients is owned by the root UNIX
user account. Therefore, any UNIX user accounts that are created for NETSMART 1500
should not have a home directory under /opt/NetSmart. They should use a home
directory such as /home or /users, depending on the local site conventions for UNIX user
accounts.
3.3

NO.
SUBSECTION
PAGE
3.3.1
Start Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-8
3.3.2
Start Client on the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-9
3.3.3
Shut Down Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-10
3.3.4
Shut Down Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-11
The NETSMART 1500 server and client applications are started separately. The following
procedures describe how to start up and shut down the NETSMART 1500 server and clients.
Note: A NETSMART 1500 server system contains both server and client software; therefore, both
the NETSMART 1500 server and client can be started on a NETSMART 1500 server system. A
NETSMART 1500 client system contains only client software; therefore, only the NETSMART 1500
client can be started on a NETSMART 1500 client system.
3.3.1
Start Server
Start the NETSMART 1500 server application as follows:
Step
Task
Turn on the server workstation, monitor, and peripheral equipment.
At the common desktop environment (CDE) welcome screen, log on with the NETSMART
1500 Administrator user name (netsmart) and password.

OR
FNC-1500-0050-110
CHAPTER 3
Enter 1 NETSMART 1500 Administration.
Enter 1 Start NETSMART 1500 Server Processes.

NETSMART 1500 processes start on the server. The display is similar to the following:
Checking for NETSMART 1500 services...
Starting NETSMART 1500 Servers.
Using OpenORB 1.3.1
Checking current federation status (Sat Dec 16 10:26:16 PST 2006)
Starting HANS (Sat Dec 16 10:26:16 PST 2006)
bubs.nms.fnc.fujitsu.com: Starting HANS (Sat Dec 16 10:26:16 PST 2006)
bubs.nms.fnc.fujitsu.com: Starting NETSMART Database (Sat Dec 16 10:27:32 PST 2006)
Reconciling roles (Sat Dec 16 10:28:30 PST 2006)
bubs.nms.fnc.fujitsu.com: Switching Heartbeat to Active (Sat Dec 16 10:28:30 PST 2006)
bubs.nms.fnc.fujitsu.com: Switching Database to Active (Sat Dec 16 10:28:31 PST 2006)
bubs.nms.fnc.fujitsu.com: Switching Netsmart services to Active (Sat Dec 16 10:28:33 PST 2006)
bubs.nms.fnc.fujitsu.com: Switching DCN to Active (Sat Dec 16 10:28:34 PST 2006)
Starting federation bubs (Sat Dec 16 10:28:36 PST 2006)
bubs.nms.fnc.fujitsu.com: Starting NETSMART services (Sat Dec 16 10:28:37 PST 2006)
======================================================================
NETSMART 1500 Federation bubs
Hostname: bubs.nms.fnc.fujitsu.com: Active
======================================================================
done
3.3.2
Start Client on the Server

Use the following procedure to start a NETSMART 1500 client on the server.
CAUTION:
In general, you should not run the NETSMART 1500 client on the server. Running the client
on the server consumes server memory and degrades performance. Some graphics cards
may also degrade performance because of Java compatibility issues. A list of acceptable
graphics cards is included in the technical information bulletin (TIB) titled NETSMART 1500
Version 5 Software Release Notes. This TIB is available from the FOCIS Web site at
https://partners.fnc.fujitsu.com.
Note: To start a NETSMART 1500 client on UNIX workstation or PC (not the server), refer to
FNC-1500-0050-200, Introduction, Section 4.7, Client Startup [p. 4-5].
FNC-1500-0050-110

3-9
CHAPTER 3
Start the NETSMART 1500 client on the server as follows:

Step
1
Task

OR
Enter 4 Start NETSMART 1500 Client.

The NETSMART 1500 initialization screen displays, followed by the client logon dialog box.
Enter a valid NETSMART 1500 user name and password, and then click Login.
The Topology Management window displays when the system has finished initializing.
3.3.3
Shut Down Server

This section describes how to stop the NETSMART 1500 server application. This procedure
does not shut down the Oracle database.
Note: Choosing Exit from the File menu does not stop NETSMART 1500.
WARNING:
When the NETSMART 1500 server is shut down, the managed NEs are not affected.
However, the NETSMART 1500 software no longer monitors all NEs.
Shut down the NETSMART 1500 server application as follows:

Step
1
Task

OR
Choose Stop NETSMART 1500 Server.
FNC-1500-0050-110
CHAPTER 3
NETSMART 1500 shuts down, and the server displays messages similar to those shown
below:
NETSMART 1500 Servers are going down. This will take a while....
Using OpenORB 1.3.1
Shutting down HA federation bubs (Tue Dec 19 10:41:39 PST 2006)
Checking current federation status (Tue Dec 19 10:41:39 PST 2006)
bubs.nms.fnc.fujitsu.com: Stopping NETSMART services (Tue Dec 19 10:41:39
PST 2006)
bubs.nms.fnc.fujitsu.com: Stopping NETSMART Database (Tue Dec 19 10:42:49
PST 2006)
Validating the cookie (Tue Dec 19 10:44:34 PST 2006)
Stopping HANS (Tue Dec 19 10:44:34 PST 2006)
null (Tue Dec 19 10:46:01 PST 2006)
HA federation is now down (Tue Dec 19 10:46:01 PST 2006)
======================================================================
NETSMART 1500 Federation bubs
Hostname: bubs.nms.fnc.fujitsu.com: Unknown
======================================================================
done
If any clients are attached to the server, a message displays to each client that the connection
has been lost, and each client stops functioning.
3.3.4
Shut Down Client

When a NETSMART 1500 client is shut down, the managed NEs are not affected. Assuming
that the NETSMART 1500 server is still running, the NETSMART 1500 server continues to
monitor the NEs.
Shut down the NETSMART 1500 client application as follows:
Step
1
Task
In the NETSMART 1500 client GUI, select Exit from the File menu.
A confirmation dialog box opens stating that this action will halt the NETSMART 1500
client.
Click OK to continue.
The NETSMART 1500 client shuts down.
FNC-1500-0050-110

3-11
CHAPTER 3
Troubleshooting Server and Clients
3.4

3.4.1
NO.
SUBSECTION
PAGE
3.4.1
Check the Status of Server Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-12
3.4.2
Recover from a NETSMART 1500 Client Error (UNIX Client) . . . . . . . . . . . . . . . . . . . . . . .
3-13
3.4.3
Recover from a NETSMART 1500 Server Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-14
3.4.4
Restore Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-15
3.4.5
Manage NETSMART 1500 Service Packs and Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-16
Check the Status of Server Processes

Check which NETSMART 1500 server processes are active as follows:
Step
1
Task

OR
Enter 3 Check NETSMART 1500 Server Status.
FNC-1500-0050-110
CHAPTER 3
A report similar to the following displays:

Running /opt/NetSmart/bin/netsmart status
NETSMART 1500: Checking status..
======================================================================
NETSMART 1500 Summary Status
======================================================================
-- Summary ----------------------------------------------------------Federation: federation1
NETSMART Services: Available
Configuration: Single node
Version: 5. 0.0
License: 10 users, 50 NEs, TL1UPLINK, HA, PM
-- Server status ----------------------------------------------------......................................................................

Hostname
Type
Role
State
Clients
......................................................................
karma
Primary
Active
Up
0
......................................................................
======================================================================
Usage:
"netsmart
"netsmart
"netsmart
"netsmart
done
status"
status ha"
status list"
status all"
NETSMART summary status

High Availability status
NETSMART servers list
All of the above
3.4.2
Recover from a NETSMART 1500 Client Error (UNIX Client)

Recover from a NETSMART 1500 client error as follows:
Step
1
Task
Shut down the client. (Refer to Section 3.3.4, Shut Down Client [p. 3-11].)
FNC-1500-0050-110

3-13
CHAPTER 3
Restart the client. (Refer to FNC-1500-0050-200, Introduction, Section 4.7.1, Starting a

Client on Solaris [p. 4-6].)
Did the client restart?

If YES:
You have finished this procedure.
If NO:
Continue with Step 4 [p. 3-14].
Reboot the NETSMART 1500 client using the following command as the root user:
/usr/sbin/shutdown -i6 -y -g30
Note: The -g30 option specifies a 30-second delay period, which may or may not be needed.
After the reboot is complete, restart the NETSMART 1500 client. (Refer to
FNC-1500-0050-200, Introduction, Section 4.7.1, Starting a Client on Solaris [p. 4-6].)
If the NETSMART 1500 client still fails, contact Fujitsu Network Communications Inc.
(FNC) technical support.
3.4.3
Recover from a NETSMART 1500 Server Error

Some NETSMART 1500 server errors may generate an e-mail message to the NETSMART
1500 Administrator. For example, if a server process fails, an e-mail message informs the
NETSMART 1500 Administrator of the failure and recommends restarting the NETSMART
1500 processes. Other errors may also require the NETSMART 1500 processes to be
restarted.
Recover from a NETSMART 1500 server error as follows:
Step
Task
Shut down all NETSMART 1500 clients. (Refer to Section 3.3.4, Shut Down Client
[p. 3-11].)
Shut down the NETSMART 1500 server. (Refer to Section 3.3.3, Shut Down Server
[p. 3-10].)
Restart the NETSMART 1500 server. (Refer to Section 3.3.1, Start Server [p. 3-8].)
FNC-1500-0050-110
CHAPTER 3
Did the server restart?

If YES:
If NO:
Reboot the NETSMART 1500 server using the following command as the root user:
/usr/sbin/shutdown -i6 -y -g30
After the reboot is completed, restart the NETSMART 1500 server. (Refer to Section 3.3.1,
Start Server [p. 3-8].)
Did the server restart?

If YES:
If NO:
Contact FNC technical support for assistance.
Restart the NETSMART 1500 clients. (Refer to Section 3.3.2, Start Client on the Server
[p. 3-9].)
Verify that all system functions are working properly.
3.4.4
Restore Server
Use the Solaris ufsrestore command to restore files from tape. Refer to the
ufsrestore man page for additional information. There are no Heartbeat menu items
available for restoring UNIX files backed up through the NETSMART 1500 back-up
procedure.
You can also use the Admintool described in Section 4.13, Admintool [p. 4-31].
FNC-1500-0050-110

3-15
CHAPTER 3
Enabling/Disabling Program Groups
3.4.5
Manage NETSMART 1500 Service Packs and Patches

Concerning NETSMART 1500 service packs and software patches:
3.5
Service packsare released periodically to provide support for new releases and NEs,
feature enhancements, and problem corrections. They are cumulative.
Software patchesare released periodically as problem corrections. Patches are

installed on top of the most recent service pack. For instance, to install patch v5
sp510.1 you must first install service pack v5 sp510. (This admonition applies only to
the server; clients automatically install a service pack and patch when running Auto
Update.)

This section describes how to enable and disable optional features. It includes the following
subsections:
NO.
SUBSECTION
PAGE
3.5.1
Enable Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-17
3.5.2
Disable Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-18
3.5.3
Enable EMLNML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-19
3.5.4
Disable EMLNML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-19
3.5.5
Enable TL1 Uplink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-20
3.5.6
Disable TL1 Uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-21
3.5.7
Enable FLASHWAVE 7400 Node Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-22
3.5.8
Disable FLASHWAVE 7400 Node Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-22
3.5.9
Enable Webservice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-23
3.5.10
Disable Webservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-24
3.5.11
Enable SNMP Uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-25
3.5.12
Disable SNMP Uplink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-26
3.5.13
Enable All Optional Program Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-26
3.5.14
Disable All Optional Program Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-27
FNC-1500-0050-110
CHAPTER 3
NETSMART 1500 contains optional features. These features are disabled by default during
the NETSMART 1500 installation. The optional NETSMART 1500 features are as follows:
PMThis feature collects performance monitoring (PM) statistics from NEs.
WebserviceThis feature allows users limited access to NETSMART 1500 through a
Web browser.
EMLNMLThis feature supports the Element Management Layer Network
Management Layer (EMLNML) interface for communicating with an
EMLNML-compliant NMS.
TL1 uplinkThis feature provides uplink to TL1OSS communications.
SNMP uplinkThis feature acts as an SNMP agent for SNMP-based fault
management.
FW74NMThis feature enables and disables the node managers for FLASHWAVE
7410 and FLASHWAVE 7420 NEs.
Note: You can check the status (active/inactive) of these features using Heartbeat as described
in Section 3.4.1, Check the Status of Server Processes [p. 3-12].
The NETSMART 1500 processes associated with each of the above features are referred to as
a program group. Optional program groups can be started and stopped independently from
the set of core (nonoptional) NETSMART 1500 processes.
The NETSMART 1500 software remembers which optional program groups have been
enabled/disabled even after NETSMART 1500 is stopped and subsequently restarted.
3.5.1
Enable Performance Management

Enable the PM optional program group as follows:
Step
1
Task

OR
Enter 5 Enable Program Groups.
Enter 1 Enable PM.
FNC-1500-0050-110

3-17
CHAPTER 3
The PM optional program group is enabled. Messages similar to the following display:
Running /opt/NetSmart/bin/netsmart startgroup pm
Group pm starting...
nvt1, PM-ES, Server started, Sun Jun 25 14:53:55 PDT 2006
nvt1, PerformanceManagement, Server started, Sun Jun 25 14:53:55 PDT 2006
pm, Server group started, Sun Jun 25 14:53:55 PDT 2006
Group pm started.
done
3.5.2
Disable Performance Management

Disable the PM optional program group as follows:
Step
1
Task
From the CDE toolbar, open the Heartbeat menu.

OR
From the Command Line, enter netsmart heartbeat.
Enter 6 Disable Program Groups.
Enter 1 Disable PM.

The PM optional program group is disabled. Messages similar to the following display:
Running /opt/NetSmart/bin/netsmart stopgroup pm
Stopping group pm
nvt1, PerformanceManagement, Server terminated, Sun Jun 25 14:53:55 PDT
2006
nvt1, PM-ES, Server terminated, Sun Jun 25 14:53:55 PDT 2006
pm, Server group stopped, Sun Jun 25 14:53:55 PDT 2006
Stopped group pm
done
FNC-1500-0050-110
CHAPTER 3
3.5.3
Enable EMLNML
This procedure enables the EMLNML optional program group.
Enable EMLNML as follows:
Step
1
Task

OR
Enter 2 Enable EMLNML.

EMLNML is enabled. Messages similar to the following display:
Running /opt/NetSmart/bin/netsmart startgroup emlnml
New IIOP Connection (dilbert.peakss.com,IT_daemon, null,,pid=0)
New IIOP Connection (dilbert.peakss.com,fenicsd, null,,pid=0)
Now starting group emlnml
-889262717: New Connection dilbert.peakss.com:45106) ]
emlnml, Server group started, Sun Jun 25 14:53:55 PDT 2006
done
Note: This action works only if EMLNML is licensed.
3.5.4
Disable EMLNML
Disable EMLNML as follows:
Step
1
Task

OR
FNC-1500-0050-110

3-19
CHAPTER 3
Enter 2 Disable EMLNML.

EMLNML is disabled. Messages similar to the following display:
Running /opt/NetSmart/bin/netsmart stopgroup emlnml
New IIOP Connection (dilbert.peakss.com,IT_daemon, null,,pid=0)
New IIOP Connection (dilbert.peakss.com,fenicsd, null,,pid=0)
Now stopping group emlnml
-889221706: New Connection
dilbert.peakss.com:45127) ]
dilbert, EmlNmlServer, Server terminated, Sun Jun 25 14:53:55 PDT 2006
emlnml, Server group stopped, Sun Jun 25 14:53:55 PDT 2006
done
3.5.5
Enable TL1 Uplink

Enable the TL1 uplink optional program group as follows:
Step
1
Task

OR
Enter 3 Enable TL1Uplink.
FNC-1500-0050-110
CHAPTER 3
The TL1 uplink optional program group is enabled. Messages similar to the following display:
Running /opt/NetSmart/bin/netsmart startgroup tl1uplink
Group tl1uplink starting...
nvt1, TL1UplinkServer, Server started, Sun Jun 25 14:53:55 PDT 2006
tl1uplink, Server group started, Sun Jun 25 14:53:55 PDT 2006
Group tl1uplink started.
done
Note: This action works only if TL1 uplink is licensed.
3.5.6
Disable TL1 Uplink

Disable the TL1 uplink optional program group as follows:
Step
1
Task

OR
Enter 3 Disable TL1Uplink.

The TL1 uplink optional program group is disabled. Messages similar to the following
display:
Running /opt/NetSmart/bin/netsmart stopgroup tl1uplink
Stopping group tl1uplink
nvt1, TL1UplinkServer, Server terminated, Sun Jun 25 14:53:55 PDT 2006
tl1uplink, Server group stopped, Sun Jun 25 14:53:55 PDT 2006
Stopped group tl1uplink
done
FNC-1500-0050-110

3-21
CHAPTER 3
3.5.7
Enable FLASHWAVE 7400 Node Managers

Enable the FLASHWAVE 7400 node managers as follows:
Step
1
Task

OR
Enter 4 Enable FW74NM.

The FW74NM optional program group is enabled. Messages similar to the following display:
Running /opt/NetSmart/bin/netsmart startgroup fw74nm
Group fw74nm starting...
nvt1, SNMPServer, Server started, Sun Jun 25 14:53:55 PDT 2006
fw74nm, Server group started, Sun Jun 25 14:53:55 PDT 2006
Group fw74nm started.
done
3.5.8
Disable FLASHWAVE 7400 Node Managers

Disable the FLASHWAVE 7400 node managers as follows:
Step
1
Task

OR
FNC-1500-0050-110
CHAPTER 3
Enter 4 Disable FW74NM.

The FW74NM optional program group is disabled. Messages similar to the following display:
Running /opt/NetSmart/bin/netsmart stopgroup fw74nm
Stopping group fw74nm
nvt1, SNMPServer, Server terminated, Sun Jun 25 14:53:55 PDT 2006
fw74nm, Server group stopped, Sun Jun 25 14:53:55 PDT 2006
Stopped group fw74nm
done
3.5.9
Enable Webservice
Enabling the Webservice option allows access to limited NETSMART 1500 features through
a Web browser.
Enable Webservice as follows:
Step
1
Task

OR
Enter 5 Enable Webservice.
FNC-1500-0050-110

3-23
CHAPTER 3
The Webservice option is enabled. Messages similar to the following display:

Running /opt/NetSmart/bin/netsmart startgroup webservice
Group webservice starting...
nvt1, NSWebService, Server started, Sun Jun 25 14:53:55 PDT 2006
webservice, Server group started, Sun Jun 25 14:53:55 PDT 2006
Group webservice started.
done
3.5.10
Disable Webservice
Disable Webservice as follows:
Step
1
Task

OR
Enter 5 Disable Webservice.

The Webservice option is disabled. Messages similar to the following display:
Running /opt/NetSmart/bin/netsmart stopgroup webservice
Stopping group webservice
webservice, Server group stopped, Sun Jun 25 14:53:55 PDT 2006
Stopped group webservice
done
FNC-1500-0050-110
CHAPTER 3
3.5.11
Enable SNMP Uplink

Enable the SNMP uplink optional program group as follows:
Note: SNMP uplink listens on UDP port 162. If required, this can be modified with the properties
file $NETSMART_PROP_HOME_/Properties/SNMPUplinkServer/
SNMPUplinkServer.properties. If other SNMP agents, such as Sun Solaris installed
agents, are running on this system, SNMP uplink can be reconfigured by editing the same
properties file. Refer to FNC-1500-0050-410, External Interfaces, Chapter 5, SNMP Uplink
Management, for more information.
Step
1
Task

OR
Enter 6 Enable SNMPUplink.

The SNMP uplink optional program group is enabled. Messages similar to the following
display:
Running /opt/NetSmart/bin/netsmart startgroup snmpuplink
Group snmpuplink starting...
nvt1, SNMPUplinkServer, Server started, Sun Jun 25 14:53:55 PDT 2006
snmpuplink, Server group started, Sun Jun 25 14:53:55 PDT 2006
Group snmpuplink started.
done
Note: This action works only if SNMP uplink is licensed.
FNC-1500-0050-110

3-25
CHAPTER 3
3.5.12
Disable SNMP Uplink

Disable the SNMP uplink optional program group as follows:
Step
1
Task

OR
Enter 6 Disable SNMPUplink.

The SNMP uplink optional program group is disabled. Messages similar to the following
display:
Running /opt/NetSmart/bin/netsmart stopgroup snmpuplink
Stopping group snmpuplink
nvt1, SNMPUplinkServer, Server terminated, Sun Jun 25 14:53:55 PDT 2006
snmpuplink, Server group stopped, Sun Jun 25 14:53:55 PDT 2006
Stopped group snmpuplink
done
3.5.13
Enable All Optional Program Groups

Enable all optional program groups as follows:
Step
1
Task

OR
FNC-1500-0050-110
CHAPTER 3
Enter 6 Enable all of the above.

The optional program groups are enabled in sequence. After a program group is enabled, press
any key to go to the next.
3.5.14
Disable All Optional Program Groups

Disable all optional program groups as follows:
Step
1
Task

OR
Enter 6 Disable all of the above.

The optional program groups are disabled in sequence. After a program group is disabled,
press any key to go to the next.
FNC-1500-0050-110

3-27
CHAPTER 3
NETSMART 1500 Trace Menu
3.6
NETSMART 1500 Trace Menu

The NETSMART TRACES menu shown below is not for general use and is not described in
this documentation. FNC technical support will provide instructions on its use if needed.
N E T S M A R T T R A C E S
1. On-Demand Trace
e. Enable Root Access
q. Quit
3.7
Installing NE Software Generics

NO.
SUBSECTION
PAGE
3.7.1
Install from CD Using NETSMART 1500 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-29
3.7.2
Install from CD Using UNIX Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-34
3.7.3
Install from Remote Network Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-36
An NE software generic is the software component for a Fujitsu NE. As new features are
added to the NEs, new software generics are distributed. The software generics are distributed
on CDs.
This section describes how to install the NE software generics into NETSMART 1500.
Procedures for this activity differ based on the configuration of the machine used. The
following subsections describe procedures for installing NE software generics using a machine
with a CD drive and a machine without a CD drive.
Note: For more information about administration of NE software, refer to FNC-1500-0050-260,
NE Software Management.
Note: For an alternative method of loading NE software generic files using a server script, refer
to Section 3.7, Installing NE Software Generics [p. 3-28].
FNC-1500-0050-110
CHAPTER 3
3.7.1
Install from CD Using NETSMART 1500 Server

This procedure describes how to install NE software generics from a CD using the Heartbeat
tool running on the NETSMART 1500 server. The server must have a CD drive, and the
media containing the files must match the drive. The machine should be able to run a
NETSMART 1500 client.
Note: This procedure requires root access to the NETSMART 1500 server.
Install NE software from a CD using Heartbeat as follows:

Step
1
Task

OR
Enter 8 Load NE Software Generic Files.

L O A D
N E
S O F T W A R E
G E N E R I C
F I L E S
This option will get the NE generic software files from the CD
and load them into a user specified directory.
Enter the media in which you have files to be copied
1 floppy
2 cdrom
3 harddisk
Enter selection (default: harddisk) [?,??]:
Insert the first CD into the CD drive.
FNC-1500-0050-110

3-29
CHAPTER 3
Enter 2 if installing from a CD.

Enter selection (default: harddisk) [?,??]: 2
Getting Network Element Generic Software
Enter a destination directory for the download files
[default=/opt/NetSmart/download_files]:
Enter the desired destination directory, or press RETURN/ENTER to accept the default.
Enter a destination directory for the download files
[default=/opt/NetSmart/download_files]:
Creating subdirectory /opt/NetSmart/download_files/F600201V ..
Copying files from CDROM #1 ..
1) a600201v.pgm to
/opt/NetSmart/download_files/F600201V/A600201V.PGM
2) d600201v.pgm to
/opt/NetSmart/download_files/F600201V/D600201V.PGM
3) f600201v.con to
/opt/NetSmart/download_files/F600201V/F600201V.CON
4) f600201v.sig to
/opt/NetSmart/download_files/F600201V/F600201V.SIG
5) h600201v.pgm to
/opt/NetSmart/download_files/F600201V/H600201V.PGM
6) ipl_25~1.hex to
/opt/NetSmart/download_files/F600201V/IPL_25~1.HEX
7) ipl_25~2.hex to
/opt/NetSmart/download_files/F600201V/IPL_25~2.HEX
8) m600201v.pgm to
/opt/NetSmart/download_files/F600201V/M600201V.PGM
9) s600201v.pgm to
/opt/NetSmart/download_files/F600201V/S600201V.PGM
Copy of files from CDROM #1 completed
Ejecting CDROM ...
Is there a CDROM #2 in this set (y/n)? [y,n,?]
FNC-1500-0050-110
CHAPTER 3
Is there another CD in this set?

If YES:
Insert the CD as follows:
a.
Remove the last CD from the drive.
b.
Insert the next CD in the drive.
c.
Enter y.
d.
Repeat this step (Step 8 [p. 3-31]).
If NO:
Enter n.
Is there a CDROM #2 in this set (y/n)? [y,n,?] n
Copy completed successfully for NE F600201V
Start the NETSMART 1500 client. (Refer to Section 3.3.2, Start Client on the Server
[p. 3-9].)
The NETSMART 1500 client starts up and displays the Topology Management window after
logon and initialization.
10
From the Applications menu, select Maintenance > Software Repository Management.
FNC-1500-0050-110

3-31
CHAPTER 3
The Software Repository Management window opens (Figure 3-1 [p. 3-32]).
Figure 3-1: Software Repository Management Window
11
Select the Software Generic tab by clicking the Software Generic tab in the lower-left corner of
the screen.
12
Click the Install toolbar icon in the upper-left corner of the screen.
FNC-1500-0050-110
CHAPTER 3
The Install Software Generic dialog box opens (Figure 3-2 [p. 3-33]).
Figure 3-2: Install Software Generic Dialog Box
13
In the Source Hostname field, enter the name of the machine where the temporary directory in
Step 7 [p. 3-30] was created. The name of the machine may already be entered correctly by
default.
OR
In the Source IP Address field, enter the IP address of the machine where the temporary
directory in Step 7 [p. 3-30] was created. The IP address may already be entered correctly by
default.
14
In the User Name field, enter a valid UNIX user name. The user name is used by the File
Transfer Protocol (FTP) process to log on the machine with the IP address specified in
Step 13 [p. 3-33].
15
In the Password field, enter the password associated with the UNIX user name specified in
Step 14 [p. 3-33].
16
In the Source Directory field, enter the name of the directory where the software generic files
are located. If the default directory suggested in Step 7 [p. 3-30] was used, then enter
/opt/NetSmart/download_files.
17
In the Select FGA Date fields, select the date that should be associated with the software
generic. By default, the current date and time are selected.
FNC-1500-0050-110

3-33
CHAPTER 3
18
Click Ok.
The files associated with the software generic are now installed in NETSMART 1500.
19
3.7.2
Place the disks or CDs in a secure location.
Install from CD Using UNIX Client

This procedure describes how to install NE software generics on NETSMART 1500 using a
UNIX client machine with a CD drive. The media containing the files must match the CD
drive that is on the machine. The machine should be able to run a NETSMART 1500 client.
Note: You must use a UNIX client or the NETSMART 1500 server to copy the NE software
generics from the media to the server.
Install NE software from CD as follows:

Step
Task
Enter the following command to create a temporary directory to store the files that make up
the software generic:
mkdir /tmp/software_generic
Note: You must have a directory for each NE type and load level.
Insert the first (or next) CD into the CD drive of the machine.
The CD is automatically mounted.
Copy the files on the CD to the temporary directory created in Step 2 [p. 3-34] by entering
the following command:
cp /cdrom/cdom0/* /tmp/software_generic
Enter eject cdrom to eject the CD.
If there are more CDs that are part of the software generic, remove the last CD from the drive,
and repeat Steps 3 [p. 3-34] through 5 [p. 3-34] for the next CD.
Start the NETSMART 1500 client. (Refer to Section 3.3.2, Start Client on the Server
[p. 3-9].)
FNC-1500-0050-110
CHAPTER 3
The NETSMART 1500 client starts up and opens the Topology Management window after
logon and initialization.
8
From the Administration menu, select Maintenance > Software Repository Management.
Click the Software Generic tab in the lower-left corner of the screen.
10
The Install Software Generic dialog box opens (Figure 3-2 [p. 3-33]).
11
In the Source Hostname field, enter the name of the machine where the temporary directory in
Step 2 [p. 3-34] was created. The name of the machine may already be entered correctly by
default.
OR
In the Source IP Address field, enter the IP address of the machine where the temporary
directory in Step 2 [p. 3-34] was created. The IP address may already be entered correctly by
default.
12
In the User Name field, enter a valid UNIX user name. The user name is used by the FTP
process to log on the machine with the IP address specified in Step 11 [p. 3-35].
13
In the Password field, enter the password associated with the UNIX user name specified in
Step 12 [p. 3-35].
14
In the Source Directory field, enter the name of the directory where the software generic files
are located. If the directory suggested in Step 4 [p. 3-34] was used, then enter
/tmp/software_generic.
15
16
Click Ok.
17
At the UNIX prompt in the terminal window, enter the following command to delete the
temporary directory that was created and all files in that directory:
FNC-1500-0050-110

3-35
CHAPTER 3
rm -fr /tmp/software_generic
18
3.7.3
Place the disks or CDs in a secure location.
Install from Remote Network Drive

This section describes how to install NE software generics using a machine without a CD
drive. The procedure is also used if the media containing the software generic does not match
the type of drive available on the local machine.
This procedure assumes that the contents of the CDs have been loaded on a remote machine
that is accessible using FTP. If the remote machine is a Solaris-based system, refer to Steps 3
[p. 3-34] through 6 [p. 3-34] in Section 3.7.2, Install from CD Using UNIX Client [p. 3-34].
The local machine should have the ability to run a NETSMART 1500 client.
Install NE software from a remote network drive as follows:
Step
Task
Start the NETSMART client. (Refer to Section 3.3.2, Start Client on the Server [p. 3-9].)
Select Applications > Maintenance > Software Repository Management.

Click the Software Generic tab in the lower-left corner of the screen.
The Install Software Generic window opens (Figure 3-2 [p. 3-33]).
In the Source Hostname field, enter the name of the remote machine where the software
generic files are loaded. If the remote machine does not have a name, leave this field blank.
In the Source IP Address field, enter the IP address of the remote machine where the software
generic files are loaded.
In the User Name field, enter a valid user name for the remote machine. The user name is used
by the FTP process to log on the remote machine.
In the Password field, enter the password associated with the user name specified in Step 7
[p. 3-36].
FNC-1500-0050-110
CHAPTER 3
Configuring the ObjectStream License
In the field under Directory Info, enter the fully qualified directory path where the software
generic files are located.
Note: You cannot use the CD-ROM or browse buttons; you must type the path.
10
11
Click Ok.
3.8

This section describes how to configure the ObjectStream license. This process involves
setting the new license key, and then stopping and restarting the license server.
Configure the ObjectStream license as follows:
Step
Task
Log on the NETSMART 1500 server as root.
At the prompt, enter cd /opt/NetSmart/install.
At the prompt, enter ./set-ObjLic.

You are prompted to enter the ObjectStream license key.
At the prompt, enter the ObjectStream license key.

The screen displays License set when the ObjectStream license key is set correctly.
Stop the ObjectStream License server. At the prompt, enter the following command:
/etc/init.d/OBJStream stop
To confirm that the ObjectStream License server has stopped, enter the following command:
ps -ef | grep -i objstream | grep -v grep
FNC-1500-0050-110

3-37
CHAPTER 3
If the process is still running, a line displays showing details of the ObjectStream process;
otherwise, no line displays.
8
Start the ObjectStream License server. At the prompt, enter the following command:
/etc/init.d/OBJStream start
FNC-1500-0050-110
CHAPTER 3
Export Security Data
3.9
Export Security Data

Selecting this option generates security access data in a file called addAccessGroup.cfg
and user data in a file called addSecurityUser.cfg. By default, the files are stored in
$NETSMART_PROP_HOME/Properties/nif directory. However, you can specify a
different directory in which to store these files. This menu should be used to export security
data in text files that can be later imported through Import Security Data for a different
NETSMART 1500 server.
Running ExportSecurity
Enter a directory for exporting files or use default:
[/opt/NetSmart/Properties/nif] [?,q]
Running ExportSecurity
Enter a directory for exporting files or use default
[/opt/NetSmart/Properties/nif]:
/opt/NetSmart/Properties/nif
Found addAccessGroup.cfg
Found addSecurityUser.cfg
ContainerInitComponent.initializeComponents(): total no. of application
components loaded = 1
FNC-1500-0050-110

3-39
CHAPTER 3
Import Security Data
3.10
Import Security Data

Selecting this option allows importing of security data from text files that are generated by the
Security Export utility from a different NETSMART 1500 server. The files are
addAccessGroup.cfg and addSecurityUser.cfg. These files should be located in
the following directory: $NETSMART_PROP_HOME/Properties/nif.
Running ImportSecurity
This utility expects data files addSecurityUser.cfg and/or
addAccessGroup.cfg
Enter a directory for importing files or use default:
Running ImportSecurity
This utility expects data files addSecurityUser.cfg and/or
addAccessGroup.cfg
Enter a directory for importing files or use default:
/opt/NetSmart/Properties/nif
Importing Roles and Users
ContainerInitComponent.initializeComponents(): creating component "FwJVM"
ContainerInitComponent.initializeComponents(): component "FwJVM" was
created successfully
Role ATMManagementUser already exists.
Role NetSmartUserAdmin already exists.
Role EmlNmlUser already exists.
Role CrossConnectsUser already exists.
Role NetSmartServerAdmin already exists.
Role ProfileManagementUser already exists.
Role BLSRUser already exists.
Role PerformanceManagementUser already exists.
Role ConfigurationUser already exists.
Role NECutThroughUser already exists.
Role ConnectionManagementUser already exists.
Role AlarmsUser already exists.
Role ReadOnlyUser already exists.
User netsmart already exists
FNC-1500-0050-110
CHAPTER 3
Resync NE Data
3.11
Resync NE Data
This option should be executed during a migration process with a release upgrade or a
hardware upgrade of NETSMART 1500. Normally, the option is invoked automatically by
the logical restore function. However, you can choose to invoke it after the logical restore. The
resync function, which performs a resync and update of the NETSMART 1500 database,
performs a first time logon of the NEs so that NETSMART 1500 has the updated NE
information.
In such scenarios, you can execute it from this menu option. This action forces logons to all
the NEs that existed and were autodiscovered before migration. It also resynchronizes all
equipment, cross-connects, shelves, and alarms for those NEs.
Resync Network Initiated. Please wait..
Done with initialization
Logged into MAXFLM1502402 successfully
Resync Network Done.
For all NEs that failed, manually login from GUI
FNC-1500-0050-110

3-41
CHAPTER 3
Configuring the Communication Server/NE Logon
3.12

NO.
SUBSECTION
PAGE
3.12.1
NE Logon Reconnect Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-42
3.12.2
NE Logon Delay Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-44
3.12.3
Modifying Communication Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-44
This section describes the parameters that control NE logon retries and NE logon delay. An
NE logon retry is initiated in NETSMART 1500 when the NE logon fails on initial
NETSMART 1500 startup. The NE logon delay is the time that the system waits after TCP is
established with an NE before sending an ACT-USER command to the NE. This section
provides an overview of the algorithms and describes how to modify configurable parameters.
Note: UID should be a Level 4 UID user to avoid password-aging problems.
3.12.1
NE Logon Reconnect Algorithm

Upon NE initial logon failure, an NE logon reconnect algorithm is initiated. The reconnect
algorithm is used only for NEs that have been autodiscovered. For NEs that have not been
autodiscovered, a reconnect is initiated by an end user requesting logon to the NE through the
NETSMART 1500 client GUI.
The reconnect algorithm is controlled by three configurable parameters that are stored in the
NETSMART 1500 communication server properties files. The number of these properties
files depends on the configuration of the NETSMART 1500 server. For a 2x2x4 system, there
is one properties file. For a 4x4x8 system, there are two properties files. For an 8x8x24 system,
there are four properties files. The communication server properties files are stored in the
following location for a 2x2x4 system:
/opt/NetSmart/Properties/DefaultProperties/CommsServer/
CommunicationServer.properties
FNC-1500-0050-110
CHAPTER 3
Table 3-3 [p. 3-43] lists the configurable communication server parameters associated with
the NE logon reconnect algorithm, a description of each, and their default values.
Table 3-3: NE Logon Reconnect Algorithm Parameters
Parameter Name
Description
Default Value
comms.connection.loginInitialRetryTime
Time that the NETSMART 1500 communication server

waits in between initial logon attempts for a given NE.
45 seconds
comms.connection.loginInitialRetries
The number of attempts the NETSMART 1500

communication server initiates for a successful initial
logon. The NETSMART 1500 communication server
waits a period defined by the parameter
comms.connection.loginInitialRetryTime
before each initial logon attempt.

comms.connection.loginBackOffRetryTime
The time the NETSMART 1500 communication server

waits before performing an initial logon after having
attempted the maximum number of initial retries (defined
by comms.connection.loginInitial
Retries).
300 seconds
Upon initial logon failure, the NETSMART 1500 communication servers use the reconnect
algorithm to control logon attempts. There are two parts to the algorithm: the initial retry and
the back-off retry. The initial retry is used after the first failed attempt.
During the initial retry, the communication servers wait 45 seconds (default value for the
comms.connection.loginInitialRetryTime parameter) between each retry and
attempt to connect to the NE five times (default value for the
comms.connection.loginInitialRetries parameter). If the NE is not
successfully logged on during the initial retry period, then the back-off retry time period is
used.
During this period, the communication servers try to log on an NE every 300 seconds
(default value of the comms.connection.loginBackOffRetryTime). The number
of tries during this period is infinite.
A NETSMART 1500 user can force an NE to the initial retry algorithm by logging off and
logging back on an NE through the NETSMART 1500 client GUI. If a NETSMART 1500
end user tries to initiate a logon by clicking login on the NETSMART 1500 client GUI, the
following message may be displayed: NETSMART is already attempting to
re-establish communications with this NE. In this scenario, the user must
select logout and then login to force the NE back into the initial retry algorithm.
FNC-1500-0050-110

3-43
CHAPTER 3
3.12.2
NE Logon Delay Algorithm

Table 3-4 [p. 3-44] lists the configurable communication server parameter associated with the
NE logon delay algorithm, a description, and its default value.
Table 3-4: NE Logon Delay Algorithm Parameter
3.12.3
Parameter Name
Description
Default Value
comms.connection.ACT-USER.waitTime
Time that the NETSMART 1500

communication server waits to send an
NE the ACT-USER command after
TCP establishment
1000
milliseconds
Modifying Communication Server Properties

This section describes how to modify communication server properties that control the
reconnect algorithm as discussed in Section 3.12.1, NE Logon Reconnect Algorithm
[p. 3-42], and Section 3.12.2, NE Logon Delay Algorithm [p. 3-44].
Modify communication server properties as follows:
Step
Task
Log on the NETSMART 1500 server as user netsmart.
Identify the parameters that must be changed. (Refer to Table 3-3 [p. 3-43].)
Edit the following communication server properties file using the preferred UNIX editor:
/opt/NetSmart/Properties/DefaultProperties/CommsServer/
CommunicationServer.properties
Stop the NETSMART 1500 servers. (Refer to Section 3.3.3, Shut Down Server [p. 3-10].)
Start the NETSMART 1500 servers. (Refer to Section 3.3.1, Start Server [p. 3-8].)
The new values of the communication server configuration parameters are in effect.
FNC-1500-0050-110
CHAPTER 3
Security E-Mail Notification
3.13
Security E-Mail Notification

NETSMART 1500 sends security notifications to an e-mail account controlled by the
following file on the NETSMART 1500 server:
$NETSMART_PROP_HOME/Properties/Security/Security.properties
Here, $NETSMART_PROP_HOME is an environmental variable set in file

/opt/NetSmart/.cshrc.
Example: If NETSMART_PROP_HOME is set to /opt/NetSmart/
Properties/Security/Security.properties.the following entries
within that file specify the address that security e-mails are sent to:
fenics.framework.security.emailAddressForNotification=<E-mail
Address>fenics.framework.security.smtpHost=<smtpHost>
FNC-1500-0050-110

3-45
CHAPTER 3
Broadcast Messages
3.14
Broadcast Messages
This procedure includes the following subprocedures:
NO.
SUBPROCEDURE
PAGE
3.14.1
Sending Messages from a Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-46
3.14.2
Sending Messages from the Web Administration Page . . . . . . . . . . . . . . . . . . . . . . . . . .
3-48
3.14.3
Client Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-48
At times, NETSMART 1500 Administrators must inform users (NETSMART 1500 Clients)
about any administrative tasks to be done on the server, such as maintenance work, server
shutdown, restart, or failover. Using the Broadcast feature, these messages can be broadcast to
all clients connected to the federation. These broadcast messages give users the opportunity to
save their work and exit their respective client before systems are turned off.
The NETSMART 1500 administrator can send broadcast messages in the two ways:
Using a command line (netsmart rwall)
Using a Web interface
Messages contain a priority, time tamp, host name from which they are sent, and the content
itself.
3.14.1
Sending Messages from a Command Line

The netsmart rwall command1 is used to send messages to connected NETSMART
1500 clients.
Note: This command can only be executed on a NETSMART 1500 server.
Use the following procedure to send a broadcast message from a NETSMART 1500 server
using a command line:
Step
1
Task
Log on the NETSMART 1500 server as netsmart.
1 The netsmart rwall
command is a NETSMART 1500specific function and does not use the UNIX rwall
command.
FNC-1500-0050-110
CHAPTER 3
Broadcast Messages
Enter netsmart rwall at the command prompt.

Example: nvt% netsmart rwall
Please enter message to send to all NETSMART 1500 users:
Use "." followed by enter on a new line to end message
Type the message you want to broadcast, and press RETURN.

Example: nvt% Server maintenance will begin in 30 minutes. Please save
your work and log off your client by 1200.
On a new line, type a period (.), and press RETURN.

Please choose message priority:
Please select from the following
(0): Abort this operation
(1): High priority
(2): Normal priority
Choose a number from the above:
Assign a priority to the message by typing 1 for High priority or 2 for Normal
priority.
Example: Choose a number from the above: 2
Press RETURN.
The command tries to send messages to the connected NETSMART 1500 clients. After the
command completes sending the message, a confirmation message is displayed at the prompt.
This confirmation message displays the delivery status of the message, including information
about any delivery successes, failures, and time-outs that occurred while the message was
being sent.
FNC-1500-0050-110

3-47
CHAPTER 3
Broadcast Messages
The status displays as:

Checking current federation status (Sun Jun 25 14:53:55 PDT 2006)
rwall: Message sent, waiting for 10 seconds for clients to receive rwall
rwall: Delivery attempted to 4 client(s), 4 succeeded, 0 failed, 0 timed
out
nvt1%
3.14.2
Sending Messages from the Web Administration Page

The NETSMART 1500 Administrator can send broadcast messages to NETSMART 1500
clients through a Web browser by using the Send Broadcast Message dialog box. The Send
Broadcast Message dialog box is accessed from the Administration page of the NETSMART
1500 home page.
Refer to FNC-1500-0050-200, Introduction, Chapter 8, About the NETSMART 1500 Home
Page, for detailed instructions on accessing the NETSMART 1500 home page and sending
broadcast messages from the Web Administration page.
3.14.3
Client Notification
No action is required on the part of a NETSMART 1500 client user to view a Broadcast
message. When a NETSMART 1500 client receives a message, the Admin Broadcast Message
dialog box pops up, displaying the details associated with the message. Refer to
FNC-1500-0050-200, Introduction, Section 8.3.7, Sending a Broadcast Message [p. 8-21], for
a detailed description of the Client Notification feature.
FNC-1500-0050-110
CHAPTER 3
Pre-Logon Warning Banner Administration
3.15

NO.
SUBPROCEDURE
PAGE
3.15.1
Enable the Pre-Logon Warning Banner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-50
3.15.2
Disable the Pre-Logon Warning Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-51
3.15.3
Import the Pre-Logon Warning Banner from a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-51
3.15.4
Retrieve and Edit the Pre-Logon Warning Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-52
3.15.5
Check the Status of Pre-Logon Warning Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-53
The pre-logon warning banner displays legal or business policies that you want users to
acknowledge before they log on to your NETSMART 1500 system. By default, the feature is
disabled. If enabled, the Warning dialog box (Figure 3-3 [p. 3-49]) opens, and the user must
click I Agree before they can log on.
Figure 3-3: Warning Dialog Box
FNC-1500-0050-110

3-49
CHAPTER 3
The content of the warning is specified in HTML as shown by this example:

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Mozilla/4.7 [en] (X11; I; SunOS 5.10
sun4u)
[Netscape]">
<head1>
</head>
<body>
<center>
<h1>
Warning</h1></center>
<b>This system is for the regulated use of authorized users only.</b> The
company strictly prohibits any unauthorized activity directed toward
itsnetworks and computer systems. If you access or attempt to access the
networksand computer systems, you expressly consent to having your
activities monitored( including keystroke monitoring ) at any time for
surveillance, investigationor system maintenance purposes. Also, you are
subject to all Company policiesapplicable to use of this system.
<br><b>You should assume that the Company will vigorously investigate
legaland policy violations. </b>The Company may report legal violations to
thecriminal authorities and also pursue civil legal action. Policy
violationsby authorized users will be subject to disciplinary action.
</body>
</html>
3.15.1
Enable the Pre-Logon Warning Banner

Enable the pre-logon warning banner as follows:
Step
1
Task

OR
Enter 15 Pre-login Warning Banner Operations.
Enter 1 Enable pre-login warning banner.
FNC-1500-0050-110
CHAPTER 3
The pre-logon warning banner is enabled.

Running warnBannerEnable
Please wait while we enable pre-login warning banner ...
PreLogin Warning Banner: Warning banner enabled
3.15.2
Disable the Pre-Logon Warning Banner

Disable the pre-logon warning banner as follows:
Step
1
Task

OR
Enter 2 Disable pre-login warning banner.

The pre-logon warning banner is disabled. A screen similar to the following displays:
Running warnBannerDisable
Please wait while we disable pre-login warning banner ...
PreLogin Warning Banner: Warning banner disabled
3.15.3
Import the Pre-Logon Warning Banner from a File

Use this procedure to import the text for a pre-logon warning banner from a text file. The text
file should be similar to the one shown in Table 3-5 [p. 3-89]. You are prompted for the
absolute path file name of the file you want to import.
FNC-1500-0050-110

3-51
CHAPTER 3
Import the pre-logon warning banner as follows:

Step
1
Task

OR
Choose 3 Import file for pre-login warning banner text.

The system prompts you to enter the file path and name:
Running warnBannerInstall
Enter absolute path and name for the warning banner file : [?,q]
Enter the absolute path and name of the file that you want to import.
Example: /opt/NetSmart/tmp/newBanner
The file is imported. A screen similar to the following displays:
Enter absolute path and name for the warning banner file : [?,q]
/opt/NetSmart/tmp/newBanner
Please wait while we import pre-login warning banner file :
/opt/NetSmart/tmp/newBanner
PreLogin Warning Banner: Imported warning banner text
3.15.4
Retrieve and Edit the Pre-Logon Warning Banner

Use this procedure to retrieve the existing pre-logon warning banner and open it in your
default text editor.
FNC-1500-0050-110
CHAPTER 3
Edit the pre-logon warning banner as follows:

Step
1
Task

OR
Choose 4 Edit pre-login warning banner text.

The system retrieves the existing pre-logon warning banner and displays it in your default text
editor:
Running warnBannerEdit
Please wait while we retrieve the existing pre-login warning banner to
edit...
3.15.5
Check the Status of Pre-Logon Warning Banner

Check the current status (enabled/disabled) of the pre-logon warning banner as follows:
Step
1
Task

OR
Choose 5 Current status of pre-login warning banner.
FNC-1500-0050-110

3-53
CHAPTER 3
The status (enabled/disabled) of the pre-logon warning banner is reported:

Running warnBannerStatus
Please wait while we retrieve the current status of pre-login warning
banner ...
PreLogin Warning Banner: Warning Banner is currently disabled !
FNC-1500-0050-110
CHAPTER 3
Enabling/Disabling RTRV-HDR Logging
3.16

NO.
SUBSECTION
PAGE
3.16.1
Enable RTRV-HDR Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-55
3.16.2
Disable RTRV-HDR Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-56
These subsections describe how to enable or disable TL1 Heartbeat event logging. When TL1
Heartbeat event logging is enabled, commands sent from NETSMART 1500 and responses
received are logged in the TL1 Heartbeat event log, which can be viewed using TL1 Heartbeat
Log Management (refer to FNC-1500-0050-420, Reports, Section 3.6, TL1 Heartbeat Log
Management [p. 3-12]).
CAUTION:
These procedures are not permanent across server restarts. After a restart, TL1 Heartbeat
event logging reverts to the default as described below.
The default state of TL1 Heartbeat event logging is controlled by the following
communication server property, which has a value of false (disabled) at installation.
comms.mediator.enableRTRV-HDRLogging=false
However, you can change the default to enabled by changing the value of
comms.mediator.enableRTRV-HDRLogging to true using the process described in
Section 3.12.3, Modifying Communication Server Properties [p. 3-44].
3.16.1
Enable RTRV-HDR Logging

Enable RTRV-HDR Logging as follows:
Step
1
Task

OR
Enter 16 Enable/Disable RTRV-HDR Logging.
FNC-1500-0050-110

3-55
CHAPTER 3
The TL1 Heartbeat event logging is enabled. A screen similar to the following displays:
Note: This update is lost when servers restart unless steps are taken to save it. Refer to
Section 3.16, Enabling/Disabling RTRV-HDR Logging [p. 3-55], for information on making
changes permanent across restarts.
Running tl1heartbeat enable
VBBindInterceptor() instantiated
POA created: /
POA created: fwjvm-zappa:1024699431705ContainerPOA
POA created: ComponentPOAPOA created:
ContainerInitComponentContainerInitComponent.initializeComponents():
creating component
"FwJVM"
POA created: FwJVM
ContainerInitComponent.initializeComponents(): total no. of
applicationcomponents loaded = 1
============================================================
Found 2 Communication Servers
Updating CommunicationServer-2
Updated CommunicationServer-2 Successfully
============================================================
Updated 2/2 Servers Successfully
This update will be lost when Servers Restart. Please consult the
documentation on how to make these changes permanent
============================================================
3.16.2
Disable RTRV-HDR Logging

Disable RTRV-HDR logging as follows:
Step
1
Task

OR
FNC-1500-0050-110
CHAPTER 3
Enter 16 Enable/Disable RTRV-HDR Logging.

The TL1 Heartbeat event logging is disabled. A screen similar to the following displays:
Note: This update is lost when servers restart unless steps are taken to save it. Refer to
Section 3.16, Enabling/Disabling RTRV-HDR Logging [p. 3-55], for information on making
changes permanent across restarts.
Running tl1heartbeat disable
VBBindInterceptor() instantiated
POA created: /
POA created: fwjvm-zappa:1024699482546ContainerPOA
POA created: ComponentPOA
POA created: ContainerInitComponent
ContainerInitComponent.initializeComponents(): creating component
"FwJVM"
POA created: FwJVM
============================================================
Found 2 Communication Servers
============================================================
Updated 2/2 Servers Successfully
This update will be lost when Servers Restart. Please consult
the documentation on how to make these changes permanent
============================================================
FNC-1500-0050-110

3-57
CHAPTER 3
NETSMART 1500 License Administration
3.17

3.17.1
NO.
SUBSECTION
PAGE
3.17.1
Display NETSMART 1500 License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-58
3.17.2
Upgrade NETSMART 1500 License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-59
3.17.3
Upgrade NETSMART 1500 License for HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-69
Display NETSMART 1500 License Information

Display NETSMART 1500 License Information as follows:
Step
1
Task

OR
Enter 18 License Information.
FNC-1500-0050-110
CHAPTER 3
NETSMART 1500 license information displays:

*****
Heartbeat
-> M A I N
M E N U
-> 1. NETSMART 1500 Administration

-> 18. License Information
*****
Userid: netsmart
Federation: henley
L I C E N S E
I N F O R M A T I O N
Licensed Number Of NEs
: 50
Licensed Number Of User Sessions
: 10
Maintenance Agreement policy
: BRONZE
Maintenance Duration
: 0
Optional Features Licensed
: PM EMLNML TL1UPLINK
This is a Lab Evaluation copy

The Lab Evaluation license will expire in: 1 day(s)
3.17.2
Upgrade NETSMART 1500 License

This subprocedure includes the following subtasks:
SUBTASK
PAGE
Upgrading NE and User Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-62
Upgrading a Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-65
Upgrading a Maintenance Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-67
FNC-1500-0050-110

3-59
CHAPTER 3
This subsection describes how to upgrade your NETSMART 1500 license. You can upgrade
your NETSMART 1500 license to:
Change or upgrade the number of NEs that can be managed
Change or upgrade the number of concurrent user sessions
Obtain or upgrade a license for optional NETSMART 1500 features
Change or upgrade the duration of maintenance contracts
You can do a license upgrade when servers are running (online upgrade) or when servers are
not running (offline upgrade). All upgrades require a new license key. Refer to
FNC-1500-0050-100, Installation Guide, Section 2.4.2, Obtain NETSMART 1500 License
Key [p. 2-10], for more information. The new license key can include any combination of the
possible upgrades.
You can add the number of NEs and the concurrent user sessions by obtaining a license key
for the additional number of NEs or user sessions that you want. For example, if you have a
50-NE license and want to upgrade to a system with 200 licensed NEs, obtain a license key
for the 150 additional NEs, and then do the NETSMART 1500 license upgrade process.
CAUTION:
You cannot upgrade the number of NEs beyond the hardware capacity of your system. The
NE Utilization report (FNC-1500-0050-300, Datacomm and Security Management,
Section 2.3, NEU Management [p. 2-5]) displays the maximum capacity of your hardware.
The licensing factor for FLASHWAVE 4010 NEs is 0.2 for 10 percent of licensed network
element units (NEUs) and 1 for the remaining FLASHWAVE 4010 NEs. For example, if you
have purchased a license key for 50 NEUs but you want to add only FLASHWAVE 4010
NEs, you can calculate how many FLASHWAVE 4010 NEs you can add based on the
following:
10 percent of 50 NEUs is five NEUs.
The weight for FLASHWAVE 4010 NEs is 0.2; therefore, if you add five
FLASHWAVE 4010 NEs, it would be equal to one regular NE.
Five NEUs are equal to 25 FLASHWAVE 4010 NEs.
The NEU for the 26th FLASHWAVE 4010 NE will be 1.
The total FLASHWAVE 4010 NEs that can be added is 45 (90 percent of 50 NEUs at
regular factor 1) plus 25 (10 percent of 50 NEUs at FLASHWAVE 4010 factor 0.2.).
A maximum of 140% of licensed NEs can be configured by using the maximum

supported FLASHWAVEY 4010 NEs.
Thus, you can add 70 FLASHWAVE 4010 NEs for a 50 NE license key.
FNC-1500-0050-110
CHAPTER 3
For changing a maintenance contract, upgrade the license policy (GOLD, SILVER, or
BRONZE) or the maintenance duration (specified number of days). As an example of adding
to the duration of the contract, if the initial maintenance duration was for 200 days from the
installation date, upgrading the maintenance duration by 100 days sets the maintenance
duration to 300, starting from the installation date.
Upgrade your NETSMART 1500 license as follows:
Step
Task
Obtain a license key for the upgrade. Refer to FNC-1500-0050-100, Installation Guide,
Section 2.4.2, Obtain NETSMART 1500 License Key [p. 2-10].

OR
At the Heartbeat menu, enable root password.
Enter 17 Upgrade NETSMART 1500 License.
Enter the license key (not case-sensitive).
Enter 18 License Information to inspect the summary information.

Refer to the subsections on the following pages for examples of screens that display when
upgrading a license.
FNC-1500-0050-110

3-61
CHAPTER 3
Upgrading NE and User Sessions

In this example, the system displays current NETSMART 1500 license information and then
prompts you to enter the upgrade license key:
*****
Heartbeat
-> M A I N
M E N U

-> 17. Upgrade NETSMART 1500 License
*****
Userid: root (netsmart)
Federation: henley
L I C E N S E
U P G R A D E
Current License Information
: 50
: 10
: BRONZE
: 0
: EMLNML TL1UPLINK
/opt/NetSmart/install/licenseupgrade
*** NETSMART 1500 Upgrade of License ***

***
*** Finding Current Federation***
Federation: henley
Please enter the License Key for NETSMART 1500 License Upgrade [?,q]
47beqed2531jn3f6547b9x8ytknafy85sohb3f0rscilu
FNC-1500-0050-110
CHAPTER 3
After entering the license key for the upgrade, the system completes the upgrade and displays
a summary of how the upgrade impacts your system. This example shows information from
the license key that indicates an upgrade in the licensed number of NEs and user sessions:
*************** Information from License key ***************
: 1
: 1
: none
: 0
Optional Features Licensed : none
************************************************************
License upgrade completed successfully

Deleting info from about.html
Adding Info to about.html
If the attempted upgrade is beyond the hardware capacity of your system, the license upgrade
aborts, and a message displays similar to the one below. For example, if you try to update
1,000 NEs to 3,000 NEs, the procedure will fail if the hardware supports only 2,000 NEs. For
hardware upgrade information, refer to FNC-1500-0050-100, Installation Guide, Chapter 3,
Software and Hardware Upgrades.
The NE capacity does not allow update of NEs to 3000. The System allows
upgrade up to 2000 NEs. You are required to do an Hardware Upgrade first,
if you want to update the installation to 3000 NEs
License upgrade was not successful
License upgrade was unsuccessful for the following reason:
Check failed on the license key. Upgrade attempted with an invalid license
key
FNC-1500-0050-110

3-63
CHAPTER 3
The summary information for upgrading the NEs and user sessions displays:
*****
Heartbeat
-> M A I N M E N U
*****
Userid: netsmart
Federation: henley
L I C E N S E

:
:
:
:
:
51
11
BRONZE
0
EMLNML TL1UPLINK
FNC-1500-0050-110
CHAPTER 3
Upgrading a Feature
After entering the license key for the upgrade, the system completes the upgrade and displays
the optional feature licensed (in this example, PM) as shown in the following example.
Additionally, for feature upgrades, online upgrades prompt you for automatic enabling of the
feature.
: 0
: 0
: none
: 0
: PM
************************************************************

For online upgrades, the system prompts the following:

Feature PM is licensed. Do you want to enable this feature (Y/N)?
If you enter Y, the feature is enabled. Otherwise, it is disabled by default. Certain features may
require additional configuration and cannot be enabled automatically. During online feature
upgrade, the system displays:
Feature X could not be enabled because it requires configuration.
During feature upgrades, certain features, such as EMLNML and HA, cannot be upgraded
because they need to be installed. If an upgrade is attempted for a feature that requires
installation, the system displays:
Feature EMLNML could not be licensed because it requires installation.
Please re-install by obtaining a new license key.
FNC-1500-0050-110

3-65
CHAPTER 3
The summary information for upgrading a feature displays:

*****
Heartbeat
-> M A I N
M E N U

*****
Userid: netsmart
Federation: henley
L I C E N S E
: 51
: 11
: BRONZE
: 0
FNC-1500-0050-110
CHAPTER 3
Upgrading a Maintenance Contract

Maintenance upgrades are performed to change either the maintenance policy or the
maintenance duration. The following example is an upgrade that changes the maintenance
policy to GOLD and extends the duration by 200 days. After entering the license key for the
maintenance contract, the system displays:
: 0
: 0
: GOLD
: 200
: none
************************************************************

FNC-1500-0050-110

3-67
CHAPTER 3
The summary information for upgrading a maintenance contract displays:

*****
Heartbeat
-> M A I N
M E N U

*****
Userid: netsmart
Federation: henley
L I C E N S E
: 51
: 11
: GOLD
: 200
FNC-1500-0050-110
CHAPTER 3
3.17.3
Upgrade NETSMART 1500 License for HA

This section describes license upgrades on an existing dual-node system. For a single-node
system, you can do a license upgrade when servers are running (online upgrade) or when
servers are not running (offline upgrade).
The upgrade must be done from the active node. All types of upgrades, such as the number of
NEs or a feature being licensed, are applied on both the nodes. The upgrade on a dual-node
system is an atomic operation. If it succeeds, the changes are reflected in both the nodes. If it
fails, no changes are applied to any of the nodes.
If an upgrade is tried on a non-active (passive) node, the following displays:
Trying to execute license upgrade on a node not in Active role. Please
execute the upgrade on the Active node.! Exiting.
If an upgrade is tried with either an unreachable peer node or the role of the peer node is not
in the UP state, the following message displays:
Upgrade failed due to
1. Unreachable peer node
2. Required servers not running on peer node. Please check connectivity to
the peer node and try again.
Step
1
Task

OR
Enter 18 License Information.
FNC-1500-0050-110

3-69
CHAPTER 3
NETSMART 1500 license information displays:

Userid: netsmart
Federation: clapton
L I C E N S E
: 1000
: 50
: SILVER
: 0
: PM TL1UPLINK HA
Enter 17 Upgrade NETSMART 1500 License.
FNC-1500-0050-110
CHAPTER 3

Userid: root (netsmart)
Federation: clapton
L I C E N S E
U P G R A D E
Current License Information
: 1000
: 50
: SILVER
: 0

: PM TL1UPLINK HA
/opt/NetSmart/install/licenseupgrade
*** NETSMART 1500 Upgrade of License ***
***
*** Finding Current Federation
***
Federation: clapton
Please enter the License Key for NETSMART 1500 License Upgrade [?,q]
Enter the license key.
FNC-1500-0050-110

3-71
CHAPTER 3

: 0
: 1
: none
: 0
: none
************************************************************

Enter 20 License Information to inspect the summary information.

*****
Heartbeat
-> M A I N
M E N U

*****
Userid: netsmart
Federation: clapton
L I C E N S E
: 1000
: 51
: SILVER
: 0
: PM TL1UPLINK HA
FNC-1500-0050-110
CHAPTER 3
Service Pack Installation on HA-Enabled Federations
3.18

NO.
SUBSECTION
PAGE
3.18.1
Online Installation of Service Pack on HA Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-73
3.18.2
Offline Installation of Service Pack on HA Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-74
Service pack installation on HA-enabled federations is similar to that for non-HA enabled
systems. However, the service pack installation process must be done on both server machines
of the HA pair.
Depending on the fixes in the service pack, there are two ways of installation on HA
platforms:
Online service pack installationdoes not require cluster shutdown.
Offline service pack installationrequires shutdown of both HA pair servers.

Note: Contact FTAC or refer to the documentation accompanying each service pack for the
recommended method of installation.
3.18.1
Online Installation of Service Pack on HA Platforms

This procedure assumes that the HA pair is running in active and passive roles.
Step
1
Task
Bring down the passive node by running the commands:

% nsadmin setState node.netsmart GracefulDown
% netsmart stophans
Note: Do not use netsmart stopall to bring the passive server down.
FNC-1500-0050-110

3-73
CHAPTER 3
Follow the procedure specified in Section 2.8, Service Pack Installation [p. 2-42] to install the
service pack on the passive server. During this process, the active server continues to be
available for NETSMART 1500 clients.
Note: The active host should be used mostly for monitoring and minimal configuration changes to
prevent the replication queues from getting full before the passive is brought back. Do not do a bulk
resynchronization of NEs during the service pack installation processthis is to avoid full database
resynchronization after the passive node is brought up.
After the passive server installation of the service pack is completed, the passive node must be
reactivated. To do this, log on to the active node as netsmart and execute netsmart
start to start the HA cluster.
If the queues are not full, this step does not cause a full database resynchronization and
finishes in 5 to 10 minutes.
CAUTION:
Do not start in single node modethis results in two active systems updating the same
database.
4
After the completion of Step 3 [p. 3-74], and the passive node is UP, a manual HA failover
can be initiated.
This process switches the roles of active and passive servers and is documented in
FNC-1500-0050-110, Server Administration Guide, Chapter 7. During this time, the clients
cannot communicate with the servers and the downtime is less than 20 minutes.
The clients are automatically prompted to auto-upgrade, after the failover is completed and
passive server with the service pack installed becomes active.
3.18.2
Install the service pack on the now passive server using the procedure described in Step 1
[p. 3-73] above.
Offline Installation of Service Pack on HA Platforms

The offline process of installing service packs on HA platforms requires stopping netsmart
services on both active and passive servers and thus involves a significantly longer downtime
for the clients. Follow the steps below to install the service pack on HA platforms.
Step
Task
Login on to the active node with your netsmart user login and password.
Initiate the netsmart stopall command.
FNC-1500-0050-110
CHAPTER 3
Choose the cluster shutdown option when prompted.
Login as root on both machines making up the HA pair.
Install the service pack following the procedure specified in FNC-1500-0050-100, Installation
Guide, Chapter 3.
From the active server, login as netsmart user and initiate netsmart start to start the HA
cluster. The netsmart services will start on the active and passive servers.
Note: After Step 3 [p. 3-75], the clients will lose communication with the server cluster. Once the HA
cluster is brought back up in Step 6 [p. 3-75], the clients will auto-detect the upgraded server software
and prompt for an auto-upgrade of client software.
FNC-1500-0050-110

3-75
CHAPTER 3
Transaction Debugging Client
3.19

NO.
SUBSECTION
PAGE
3.19.1
Start the Transaction Debugging Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-77
3.19.2
Transaction Debugging Client Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-77
This section describes the Transaction Debugging Client and explains how to start and use the
utility.
At times, the incorrect behavior of the system might leave a transaction incomplete. Because
the transaction service acquires write locks on the participating persistent objects, an
incomplete transaction makes these objects unusable.
The transaction debugging client provides a way to find out about incomplete transactions,
their duration, the list of persistent objects the transactions are holding, and a way to roll back
the transactions forcefully. The client also identifies transactions that have gone out of context
and that have left some persistent objects locked. For these transactions, the utility provides
details about where and when the locks were acquired on them and releases them if possible.
The following are the most common causes of incomplete transactions:
Transaction was started using Current.begin() but was never committed

(Current.commit()) or rolled back (Current.rollback()).
The number of Current.begin() calls is not equal to the total number of

Current.commit() and Current.rollback() calls in a nested transaction.
A transaction was started inside a try catch block and, in an exception, was not rolled
back.
A transaction was started inside a try catch block, and the exception was never caught.
The following are the most common causes of PObject locks:
Incomplete transaction due to various reasons listed above.
Attempt to acquire a lock outside the transaction. This lock is not released unless it is
specifically released by the developer.
FNC-1500-0050-110
CHAPTER 3
3.19.1
Start the Transaction Debugging Client

The Transaction debugging client is integrated with Heartbeat. Follow these steps to start the
client:
Step
Task
Start Heartbeat.
Enter 1 Netsmart 1500 Administration.
Enter 21 Transaction Debugging client.
3.19.2
Transaction Debugging Client Options

This subsection describes the options supported by the debugging client. It includes the
following items:
ITEM
PAGE
List the Current Transactions in the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-77
Get the Starting Time of the Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-78
Print the Stack Trace of a Specific Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-78
Get the List of Persistent Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-78
Roll Back a Specific Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-78
Enable PObject Stack Trace Recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-78
Disable PObject Stack Trace Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-78
Check whether PObject Stack Trace Recording is Enabled . . . . . . . . . . . . . . . . . . . .
3-78
Get the List of Transaction IDs Holding Locks of Persistent Objects . . . . . . . . . . .
3-79
Get the Dump of Information about the Reader/Writer Queues for a Specific
Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-79
Get the List of All the Stack Traces of Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-79
Drop All the Locks for a Specific Transaction ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-79
List the Current Transactions in the System

This option accepts the name of the active server from the user. The option then connects to
that server and gets the list of all active transactions in that server.
FNC-1500-0050-110

3-77
CHAPTER 3
Get the Starting Time of the Transaction

This option accepts the transaction ID of an active transaction in the specific server and finds
out the starting time of that transaction. If the returned starting time of the transaction is too
old, the reason may be that the transaction context is already out of scope. This failure
happens mostly with an orphaned distributed transaction in the remote machine.
Print the Stack Trace of a Specific Transaction

Every transaction, when freshly started, records the stack trace by default. This option accepts
the transaction ID of an active transaction in the specific server and retrieves the stack trace of
the beginning of the transaction.
Get the List of Persistent Objects

This option accepts the transaction ID of an active transaction in the specific server and gets
the list of all of the Persistent Objects participating in that transaction. If the PObject Stack
Trace recording is enabled, this option can also show the detailed stack trace of how the lock
was acquired on the Persistent object while participating in the transaction. Also, if the object
is a persistent object, the respective OID is displayed to make the debugging easier.
Roll Back a Specific Transaction

Given a transaction ID of an active transaction in the specific server, this option rolls back the
transaction (undoing all of the changes made) and completely removes it from the system.
Enable PObject Stack Trace Recording

This option enables the stack trace recording for the persistent objects participating in the
transaction. This option is effective only for the transactions that are started after enabling the
recording. Transactions that exist before that are not supported.
Disable PObject Stack Trace Recording

This option disables the stack trace recording for the persistent objects participating in the
transaction. This option is effective only for the transactions that are started after enabling the
recording. Transactions that exist before that are not supported.
Check whether PObject Stack Trace Recording is Enabled

This option checks whether the PObject Stack Trace Recording option is enabled for a
specific server and then displays the appropriate message.
FNC-1500-0050-110
CHAPTER 3
Get the List of Transaction IDs Holding Locks of Persistent Objects

The option retrieves the list of all transaction IDs that are holding the locks on persistent
objects. The list may contain the transaction IDs that are out of context but are still holding
onto the locks.
Get the Dump of Information about the Reader/Writer Queues for a Specific
Transaction
The option retrieves the information about the reader/writer queues of the specific lockset for
a specific transaction.
Get the List of All the Stack Traces of Locks

This option lists all of the available stack traces recorded for a specific transaction when the
lock was acquired.
Drop All the Locks for a Specific Transaction ID

This option releases all of the locks held for the specific transaction ID.
FNC-1500-0050-110

3-79
CHAPTER 3
LNE Discovery
3.20
LNE Discovery
This section describes using the LNE Discovery feature in Heartbeat. With this feature, you
can discover, view, and delete subnetworks. This procedure uses the option LNE Discovery as
an example.
Follow these steps for LNE Discovery:
Step
Task
Start Heartbeat.
Enter 20 LNE Discovery.

Starting LNE Discovery tool ...
Using OpenORB 1.3.1
Initializing ......
Found subnetworks in the System

Would you like to view subnetworks in the System:(y/n): y
Enter y to view the subnetworks.
FNC-1500-0050-110
CHAPTER 3
LNE Discovery

(1) LNE-1105466055449
(2) LNE-1105466055451
(3) LNE-1105466055452
(4) LNE-1105466055456
(5) LNE-1105466055457
(6) LNE-1105466055461
(7) LNE-1105466055464
(8) FLM150ROM_OC3_CHAIN
(9) FLM150ROM_EC1_CHAIN
/*****************************************/
Please choose one of the following options:
/*****************************************/
(1)..Perform Subnetwork Discovery for the entire NETSMART 1500

system.
(2)..Perform Subnetwork Discovery and preserve existing subnetworks.
(m)..Go back to the Main Menu.
Enter choice :
Enter the desired choice:
Option 1 deletes all existing subnetworks and then rediscovers them.
Option 2 discovers subnetworks for links that do not belong to any subnetwork and
preserves existing subnetworks.
Option m aborts the operation and goes back to main menu.
FNC-1500-0050-110

3-81
CHAPTER 3
Connection Discovery
3.21
This section describes using the Connection Discovery feature in Heartbeat. With this menu,
you can do a variety of discovery functions. This procedure uses the option Discover TDM
(SONET/SDH) Connections as an example.
Note: The Connection Discovery script does not delete existing connections.
Follow these steps for Connection Discovery:

Step
Task
Start Heartbeat.
Enter 21 Connection Discovery.

The system displays the Connection Discovery menu:
Userid:
kzhu
Federation:
frakenberry
C O N N E C T I O N
D I S C O V E R Y
1. Discover TDM (SONET/SDH) Connections

2. Discover WDM Connections
3. Discover TDM and WDM Connections
4. Check the status of Connection Discovery
5. Stop Connection Discovery
q. Quit

Enter 1 Discover TDM (SONET/SDH) Connections.
FNC-1500-0050-110
CHAPTER 3

Userid:
kzhu
Federation:
frakenberry
DISCOVER TDM (SONET/SDH) CONNECTIONS
1. Save discovered connections to files only

2. Save discovered connections to files & NETSMART
q. Quit

Enter 2 Save discovered connections to files & NETSMART.

The discovered connections are saved to the Connection Management tree and also to a file in
/netsmart/home/.
FNC-1500-0050-110

3-83
CHAPTER 3
Topology Discovery
3.22
Topology Discovery
If the Network Topology Discovery component is installed, you may access the Topology
Discovery Administration client by selecting the 22 Topology Discovery Administration option
from the NETSMART 1500 Administration menu. From the Topology Discovery
Administration menu you can select the options described in this section.
The state of the Topology Discovery server displays along with the available administrative
options for the server. The Topology Discovery server can be in any one of the following four
states:
DOWNState that indicates that the Topology Discovery server is not active; that is, no
NE polling activity is scheduled.
STARTINGTransient, intermediate state that indicates the Topology Discovery

server is initializing for NE polling activities. This state is reached when the Topology
Discovery server is enabled from a DOWN state
UPState that indicates that the Topology Discovery server is active; that is, NE
polling is scheduled for execution to discover a network's NEs and links.
STOPPINGTransient, intermediate state that indicates that the Topology Discovery

server is terminating polling activities and cleaning up all allocated resources. This state
is reached when the Topology Discovery server is disabled from an UP state.
The Topology Discovery server is not enabled as part of the initial NETSMART 1500 server
startup. To enable the server, please refer to the Enable server menu option description. The
enabling and disabling of the Topology Discovery server is logged in the Activity Console and
Log of NETSMART 1500.
Menu options for the Topology Discovery Administration Client menu include:
0) Quit
Selecting this option exits the client and returns the user to the Heartbeat administration
menu.
1) Disable server
Selecting this option disables the Topology Discovery server if it is in the UP state, and stops
all NE polling activities. If the Topology Discovery server is in the DOWN, STARTING, or
STOPPING state, this action has no effect.
Note: When the Topology Discovery server has been disabled, all discovered data is flushed
from the server. The Refresh button flashes in the NETSMART 1500 Topology window and the
disable operation is logged in the NETSMART 1500 Activity Console and Log.
FNC-1500-0050-110
CHAPTER 3
Topology Discovery
If the disable request is accepted, the following message displays:

StateChange from UP to STOPPING
This indicates that the server is terminating polling activities and releasing resources. When
the cleanup is complete, the following message displays:
StateChange from STOPPING to DOWN
Once this message is received, disabling of the Topology Discovery server is complete. Note
that it may take several minutes for this last message to appear due to active polling activities
that are allowed to complete before cleanup can be initiated.
CAUTION:
If you disable and then restart the NETSMART 1500 topology server, the disable operation is
remembered and the topology discovery server is not enabled when the server comes back
into service.
2) Enable server
Selecting this option enables the Topology Discovery server if it is in the DOWN state, to
start NE polling. If the Topology Discovery server is in the UP, STARTING, or STOPPING
state, this action has no effect.
Note: The TOPODISCOVERY security area is automatically created by the NETSMART 1500
Version 5 application if Topology Discovery is enabled during the NETSMART 1500 Version 5
installation. You must add the user ID and password ID (UID/PID) for this security areaif no
UID/PIDs are found for the TOPODISCOVERY security area, the Topology Discovery server will not
start.
Once the TOPODISCOVERY security area is defined, the following recommendations

should be strictly enforced:
The TOPODISCOVERY account group should not be shared with any other security
areas.
The TOPODISCOVERY security area should not be associated with any NEs.
The TOPODISCOVERY security area and account group should not be deleted.
You may modify the accounts in the TOPODISCOVERY account group to further
customize the NE logon accounts that Topology Discovery will use for its NE polls.
If the enable request is accepted, the following message displays:
StateChange from DOWN to STARTING
FNC-1500-0050-110

3-85
CHAPTER 3
Topology Discovery
This indicates that the server is initializing for NE polling. When initialization is complete,
the following message displays:
StateChange from STARTING to UP
When this message is received, enabling of the Topology Discovery server is complete. The
Topology Discovery server continuously polls NEs to discover new NEs and links until it is
disabled.
If the NETSMART 1500 Topology Server is restarted, the enable operation is remembered
such that the Topology Discovery server is enabled when the Topology Server comes back into
service.
3) Re-load filters
Selecting this option reloads the filters specified in the property file:
${NETSMART_HOME}/Properties/TopologyServer/discovery/
Filter.properties
Filters allow you to fine-tune the set of discovered NEs that will be reported by Topology
Discovery. Currently, filters can be defined based on TID, OUI (Organizationally Unique
Identifier), or system ID (from the OSI network address for the NE).
For each filter, you can specify one of the two available policies: ACCEPT or REJECT.
ACCEPT indicates that any NEs matching the filter criteria will be reported. REJECT
indicates that any NEs matching the filter criteria will not be reported.
There is a set of preloaded filters that is stated in the comments of the property file. By
default, discovered NEs are reported if no matching filters are found.
FNC-1500-0050-110
CHAPTER 3
Topology Discovery
Modify the property file if you wish to specify filters. Each filter is in the following format:
filter.<type>.<target> = <policy>
where:
<type> is tid, oui, or sysid.
<target> is the one of the following:
NE TID if the specified <type> is tid
3-octet OUI if the specified <type> is oui
6-octet system ID if the specified <type> is sysid
<policy> is ACCEPT or REJECT.
Examples:
Define a REJECT TID filter for the NE FLASHWAVE4100-B:
filter.tid.FLASHWAVE4100-B = REJECT
Define a REJECT OUI filter for Cisco routers:
filter.oui.00107B = REJECT
Define an ACCEPT system ID filter for the NE FLM150H:
filter.sysid.00000E4622A4 = ACCEPT
After the changes are complete, select this option to reload the filters. The following message
displays:
* All previously loaded filters will be removed and replaced with the
filters defined in the property file <full path of the property file>
Continue (y/n) [n]?
If you entered y, the following message displays:

Loading filters from <full path of the property file>
Filters successfully loaded
If you entered n (default), the following message displays:

Filters not loaded
Regardless of which option you select, the Topology Discovery Administration menu is
displayed afterwards.
FNC-1500-0050-110

3-87
CHAPTER 3
Configure SONET-SDH Terminology Mapping
Use this procedure to display the Topology Discovery Administration menu.

Step
Task
Start Heartbeat.
Enter 1 NETSMART 1500 Administration menu.
Enter 22 Topology Discovery Administration.

The Topology Discovery Administration menu displays:
=================================================================
T o p o l o g y
D i s c o v e r y
A d m i n i s t r a t i o n
=================================================================
* Server state is DOWN
0) Quit
1) Disable server
2) Enable server
3) Re-load filters
Enter choice:
3.23
Type a desired choice.

The SONET-SDH terminology feature is described in FNC-1500-0050-235, Cross-Connect
Management, Section 6.2, SONET-SDH Terminology Mapping [p. 6-4]. This section
describes how to make the feature available or unavailable to all clients of the server. By
default, the feature is unavailable.
Note: If SONET-SDH terminology mapping is made available, users can configure the feature
(for their client only) as described in FNC-1500-0050-235, Cross-Connect Management,
Section 6.2, SONET-SDH Terminology Mapping [p. 6-4].
If you make the SONET-SDH terminology feature available, you must choose between three
modes of availability (values 1, 2, or 3 as described in Table 3-5 [p. 3-89]).
FNC-1500-0050-110
CHAPTER 3
CAUTION:
If the SONET-SDH terminology mapping feature is available (configuration value set to 1, 2,
or 3 as described in Table 3-5 [p. 3-89]), you cannot switch directly to another mode of
availability (value 1, 2, or 3). You must first make the feature unavailable (set configuration
value to 0, and restart the server). For example, to change from 2 to 3, apply the procedure
below to change from 2 to 0, and then apply it again to change from 0 to 3.
Configure SONET-SDH terminology mapping for all clients as follows:

Step
Task
Log on the NETSMART 1500 server as user netsmart.
Open the following server properties file in your preferred UNIX editor.
/opt/NetSmart/Properties/TopologyServer/meta/
UserPrefDefault.properties
Edit the file to change the value of the following property to 0, 1, 2, or 3 (refer to Table 3-5
[p. 3-89]):
fenics.gui.crossconnect.isMappedDisplay
Note: You cannot switch between values 1, 2, and 3. Refer to the earlier caution.
Table 3-5: Property Values to Configure SONET-SDH Terminology Mapping
Value
Description
UnavailableSONET-SDH terminology mapping is unavailable, and an individual client

cannot enable it.
Availablea and disabledSONET-SDH terminology mapping is available but is disabled by

default for all clients so that only native rates are displayed. Any user can enable terminology
mapping and configure it using the XC tab of the User Preference dialog box.
Availablea with SONET mapped enabledSONET-SDH terminology mapping is available

and is enabled by default for all clients with SDH rates mapped to equivalent SONET rates. Any
user can disable or reconfigure terminology mapping (for their client only) using the XC tab of the
User Preference dialog box.
Availablea with SDH mapped enabledSONET-SDH terminology mapping is available and is

enabled by default for all clients with SONET rates mapped to equivalent SDH rates. Any user
can disable or reconfigure terminology mapping (for their client only) using the XC tab of the
User Preference dialog box.
If SONET-SDH terminology mapping is available, users can enable, disable, or configure the feature (for their
client only) as described in FNC-1500-0050-235, Cross-Connect Management, Section 6.2.1, Set SONET-SDH
Terminology Mapping Preferences [p. 6-4].
FNC-1500-0050-110

3-89
CHAPTER 3
Set Branding Image in Topology View
Save changes, and exit the editor.
Stop the NETSMART 1500 servers. (Refer to Section 3.3.3, Shut Down Server [p. 3-10].)
Start the NETSMART 1500 servers. (Refer to Section 3.3.1, Start Server [p. 3-8].)
3.24
Set Branding Image in Topology View

NETSMART 1500 Version 5 enables users to display their own branding image for the
background in the Topology Window. The image must be 48 or fewer pixels wide by 24 or
fewer pixels high and must be in .jpg format.
Use the following procedure to set the branding image:
Step
Task
Start Heartbeat.
From the menu that displays, enter 23 Set Branding Image to display in Topology GUI client.
The following dialog displays:
Please select the image file that needs to be displayed in Topology GUI
clients
Note: The image has to be of 48 or less pixels wide by 24 or less
pixels high and should be in jpg format
Enter absolute path and name for the branding image file:
[?,q]
After typing the absolute path and name for the branding image file, press Enter.
The image selected will now display on the Topology View GUI.
3.25
Remove Branding Image from Topology View

If the Topology View is displaying a branding image you want to remove, NETSMART 1500
V5 enables you to remove it through the NETSMART 1500 Administration menu.
FNC-1500-0050-110
CHAPTER 3
Remove Branding Image from Topology View
Use the following procedure to remove the branding image:

Step
Task
Start Heartbeat.
From the menu that displays, enter 24 Remove Branding image from Topology GUI client.
The following dialog displays:
Running removeCustomerBrandingImage
Do you want to remove customer brand image from Topology GUI clients? [y/n]
(default=n)
At the prompt, type y and then press Enter.

The branding image will be removed from the Topology View display.
FNC-1500-0050-110

3-91
4
CHAPTERS/APPENDIXES
UNIX SYSTEM ADMINISTRATION
1 Introduction
This chapter includes the following procedures:
3 NETSMART 1500
Administration
NO.
PROCEDURE
4 UNIX System
Administration
4.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2
4.2
Power Down UNIX Workstation. . . . . . . . . . . . . . . . . . . . . . . . .
4-3
6 Service Support
4.3
Start Up Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4
7 High Availability
Administration
4.4
Restart UNIX Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-4
4.5
Shut Down Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-5
4.6
Configure UNIX User Accounts . . . . . . . . . . . . . . . . . . . . . . . . .
4-5
4.7
Add UNIX User Accounts Using Local Files. . . . . . . . . . . . . . .
4-11
4.8
Delete UNIX User Accounts Using Local Files . . . . . . . . . . . .
4-13
4.9
Understand UNIX Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-13
4.10
Set the Date and Time on the UNIX System . . . . . . . . . . . . . .
4-14
4.11
UNIX System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-17
4.12
Back Up the UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-27
4.13
Admintool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-31
4.14
Restore UNIX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-31
4.15
Restore Root (/) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-31
FNC-1500-0050-110
PAGE

CHAPTER 4
UNIX System Administration
Overview
4.1
Overview
WARNING:
Some operations described in this chapter use the Heartbeat tool. When using Heartbeat
with root enabled, do not press CTRL+C. Doing so may cause Heartbeat to terminate
abnormally. CTRL+C may be used with Heartbeat when root is not enabled.
This chapter provides UNIX system administration procedures for NETSMART 1500
client workstations and servers.
UNIX administration uses the UNIX System Administration option of the Heartbeat tool.
This option provides the following menu, which is the starting point for most of the
procedures described in this chapter:
U N I X A D M I N I S T R A T I O N
1. System Processes
2. System Backup *
3. NETSMART 1500 Backup *
4. Backup Log
5. System Messages
6. Disk Usage
7. Swap Info *
8. System Activities Menu
9. Cronjobs Menu
10. Defunct Processes
11. Admintool *
q. Quit
Table 4-1 [p. 4-2] lists the menu and submenu items for UNIX administration, as well as
where they are described in this practice.
Table 4-1: UNIX Administration Menu Items
Menu Item
Reference
1. System Processes
Section 4.11.1, System Processes [p. 4-18]
2. System Backup
Section 4.12.1, Perform a Full System Backup [p. 4-27]
3. NETSMART 1500 Backup
Section 4.12.2, Back Up the NETSMART 1500 Application [p. 4-28]
4. Backup Log
Section 4.12.3, View a Log File of the Backup [p. 4-30]
5. System Messages
Section 4.11.2, System Messages [p. 4-19]
FNC-1500-0050-110
CHAPTER 4
Power Down UNIX Workstation
Table 4-1: UNIX Administration Menu Items (Cont.)

Menu Item
Reference
6. Disk Usage
Section 4.11.3, Disk Usage [p. 4-20]
7. Swap Info
Section 4.11.4, Swap Info [p. 4-20]
8. System Activities Menu
Section 4.11.5, System Activities Menu [p. 4-21]
1. sar
Section 4.11.5, subsection 1. sar [p. 4-22]
2. vmstat
Section 4.11.5, subsection 2. vmstat [p. 4-22]
3. iostat
Section 4.11.5, subsection 3. iostat [p. 4-23]
4. uptime
Section 4.11.5, subsection 4. uptime [p. 4-23]
5. netstat
Section 4.11.5, subsection 5. netstat [p. 4-24]
9. Cronjobs Menu
Section 4.11.6, Cronjobs Menu [p. 4-25]

1. List netsmart crontab
Section 4.11.6, subsection 1. List netsmart crontab [p. 4-25]
2. Edit netsmart crontab
Section 4.11.6, subsection 2. Edit netsmart crontab [p. 4-26]
10. Defunct Processes
Section 4.11.7, Defunct Processes [p. 4-26]
11. Admintool
Section 4.13, Admintool [p. 4-31]
4.2
Power Down UNIX Workstation

This section describes how to power down a NETSMART 1500 client workstation or server.
The following procedures should be used before removing power from the UNIX workstation
or server.
CAUTION:
The NETSMART 1500 client or server application must be properly shut down before
turning off power to the UNIX workstation or server. Turning off the NETSMART 1500 client
workstation or server without using the following procedures could result in corrupted files
or a loss of data. Refer to Chapter 3, NETSMART 1500 Administration, Section 3.3.3, Shut
Down Server [p. 3-10], for NETSMART 1500 server shut-down procedures. Refer to
Chapter 3, NETSMART 1500 Administration, Section 3.3.4, Shut Down Client [p. 3-11], for
NETSMART 1500 client shut-down procedures.
FNC-1500-0050-110

4-3
CHAPTER 4
Start Up Workstation
Power down a NETSMART 1500 client workstation or server as follows:

Step
Task
At the CDE prompt, log on the system as the root user.
At the UNIX prompt, enter init 5 to immediately shut down the system.
OR
At the UNIX prompt, enter shutdown -i0 -g60 -y to warn any users logged on the
system before shutdown. Shutdown occurs 60 seconds after users are warned. The -g60
option specifies a 60-second period where any users on the system are informed that the
system is about to be shut down.
4.3
When the OK prompt is displayed, turn off the computer, monitor, and any peripheral
equipment, if necessary.
Start Up Workstation
The operating system automatically starts when the UNIX workstation or server is turned on.
There are no additional startup procedures required.
4.4
Restart UNIX Workstation

CAUTION:
The NETSMART 1500 client or server application must be properly shut down before
restarting a UNIX workstation or server. Turning off the NETSMART 1500 client workstation
or server without using the following procedures could result in corrupted files or a loss of
data. Refer to Chapter 3, NETSMART 1500 Administration, Section 3.3.3, Shut Down Server
[p. 3-10], for NETSMART 1500 server shutdown procedures. Refer to Chapter 3, NETSMART
1500 Administration, Section 3.3.4, Shut Down Client [p. 3-11], for NETSMART 1500 client
shutdown procedures.
To restart a UNIX workstation or server, use the following tasks.

Step
1
Task
Log on the UNIX system as root.
FNC-1500-0050-110
CHAPTER 4
Shut Down Workstation
At the UNIX prompt, enter /usr/sbin/shutdown -i6 -g60 -y to restart the

system.
The -g60 option specifies a 60-second period where any users on the system are informed
that the system is about to be shut down.
Note: The reboot process typically takes a few minutes. However, when the system reboots and
runs the file system check program (fsck), the reboot can take up to 60 minutes. The amount of
time varies depending on the number and size of disks, which can be 4, 8, or 24 disks.
4.5
Shut Down Workstation

To shut down and power off a workstation or server, use the procedures in Section 4.2, Power
Down UNIX Workstation [p. 4-3].
To shut down the workstation or server for a reboot, use the procedures in Section 4.4, Restart
UNIX Workstation [p. 4-4].
4.6
Configure UNIX User Accounts

NO.
SUBSECTION
PAGE
4.6.1
Configure NETSMART 1500 Server Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6
4.6.2
Configure NETSMART 1500 Client Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-6
4.6.3
Add CDE Controls to NETSMART 1500 Client Accounts . . . . . . . . . . . . . . . . . . . . . . . . . .
4-8
This section describes the NETSMART 1500 server and client accounts needed to run the
NETSMART 1500 software.
Note: In this section, adding, changing, and deleting UNIX accounts is done through
commands. However, doing UNIX administrative functions through AdminTool, described in
Section 4.13, Admintool [p. 4-31], is also possible.
To log on as the root user, you can enter su - or su -u; however, by doing so, you no
longer have access to NETSMART 1500 user commands.
FNC-1500-0050-110

4-5
CHAPTER 4
4.6.1
Configure NETSMART 1500 Server Accounts

The NETSMART 1500 server requires the following user accounts:
Oracle database administrator (DBA) account
NETSMART 1500 administrator account
Software download account
The Oracle DBA account information is described in Chapter 2, Oracle Administration,

Section 2.2, Oracle User Account [p. 2-5].
The NETSMART 1500 administrator account is described in Section 3.2, Creating UNIX
Accounts [p. 3-7].
Table 4-2 [p. 4-6] provides software download user account information.
Table 4-2: Software Download User Account Information
User
Shell
Home
Group
swdl1
/bin/csh
/opt1/swdl1
other
The software download account is required for:
NE software download to an NE
NE remote memory backup to an NE
NE remote memory restore to an NE
This information is needed for Network Information Services (NIS) or NIS+ setup of the user
account. Provide the information to the Network System Administrator to set up NIS or
NIS+ user account verification.
Note: The NETSMART 1500 software allows any valid group for the software download user.
If the UNIX system is configured to use local files instead of NIS or NIS+, the NETSMART
1500 installation creates the account automatically. No additional configuration is required.
4.6.2
Configure NETSMART 1500 Client Accounts

Any UNIX user can run the NETSMART 1500 client application. Refer to Section 4.7, Add
UNIX User Accounts Using Local Files [p. 4-11], for information about adding a new UNIX
user account. This section assumes that the UNIX user account has already been created.
FNC-1500-0050-110
CHAPTER 4
The following configuration tasks must be done for a UNIX user to have the correct
configuration to execute the NETSMART 1500 client application.
Configure a NETSMART 1500 client account as follows:
Step
Task
Log on the UNIX host as the UNIX user.
Determine whether the users UNIX shell is ksh or csh. The shell was specified when the
UNIX user account was initially added to the system.
Note: To determine their UNIX shell, a user can enter echo $shell. The system displays either
/bin/csh or /bin/ksh.
Use a text editor, such as vi, to edit the appropriate file in the users home directory:
File for csh
File for ksh
.cshrc
.profile
Note: To determine their home directory, a user can enter cd (to make their home directory the
current directory) and then enter pwd. The system displays the current (home) directory.
Add the following lines to the file:

For csh, add these lines:
setenv NETSMART_HOME /opt/NetSmart
source $NETSMART_HOME/client_env.csh
For ksh, add these lines:

NETSMART_HOME=/opt/NetSmart; export NETSMART_HOME
. $NETSMART_HOME/client_env.sh
Note: In the second ksh line, the second character is a space. The first three characters are
period (.), space ( ), and then dollar sign ($).
FNC-1500-0050-110

4-7
CHAPTER 4
4.6.3
Add CDE Controls to NETSMART 1500 Client Accounts

The NETSMART 1500 client application can be executed from the command line or can be
started from the common desktop environment (CDE) toolbar. The procedures documented
in Section 4.6.2, Configure NETSMART 1500 Client Accounts [p. 4-6], show how to set up
a users environment to allow the user to run the client application from the command line.
Some users prefer to have a graphical user interface (GUI) interface to launch the
NETSMART 1500 client. This section describes how to add controls to the CDE toolbar to
allow a user to start the NETSMART 1500 client from the CDE toolbar.
The following tasks describe how to add the necessary controls to an individual users account.
Setting up these controls for all users logging on the NETSMART 1500 system is also
possible. To add these controls to all user accounts, make the changes described below in the
directory /etc/dt/appconfig/types/C instead of the directory
<users_home_directory>/.dt.
Note: These operations are for use on the NETSMART server only.
FNC-1500-0050-110
CHAPTER 4
Add CDE controls to a NETSMART 1500 client account as follows:

Step
1
Task
Create the file <users_home_directory>/.dt/types/netsmart.dt with the

following content:
# Action to launch the NETSMART 1500 Client. Runs the default federation.
ACTION NetSmartClient
LABEL NETSMART Client
TYPE COMMAND
EXEC_STRING /bin/ksh -c /opt/NetSmart/bin/client-start
ICON Dtsiflexrclient
WINDOW_TYPE TERMINAL
DESCRIPTION NMS - Fujitsu Network Management Client
}
# Action to launch the NETSMART 1500 Client. Prompts user for fed.
ACTION NetSmartClientPrompt
{
TYPE COMMAND
EXEC_STRING /bin/ksh -c /opt/NetSmart/bin/client-start %(String)"Name of
the NETSMART federation:"%
DESCRIPTION NMS - Fujitsu Network Management Client
}
# Action to launch NETSMART heartbeat (only valid on servers)
ACTION NetSmartHeartbeat
{
LABEL NETSMART Heartbeat
TYPE COMMAND
EXEC_STRING sh -c /opt/NetSmart/bin/heartbeat
ICON Dtsiheartbeat
DESCRIPTION NMS - Fujitsu Network Management Heartbeat
}
FNC-1500-0050-110

4-9
CHAPTER 4
Create the file <users_home_directory>/.dt/types/netsmart.fp with the

following content:
# This creates the NETSMART control on the main panel
CONTROL NETSMART
{
TYPE icon
CONTAINER_NAME Top
CONTAINER_TYPE BOX
POSITION_HINTS 1
ICON Dtsiheartbeat
LABEL NMS Heartbeat
PUSH_ACTION NetSmartHeartbeat
DROP_ACTION none
HELP_STRING NETSMART
}
# This creates a subpanel of the NETSMART control
SUBPANEL NETSMARTSubpanel
{
CONTAINER_NAME NETSMART
TITLE Fujitsu Network Management
}
#
# Add elements to the NETSMARTSubpanel
# The generic NETSMART 1500 Client. Runs the default federation
CONTROL NETSMARTClient
{
TYPE icon
CONTAINER_NAME NETSMARTSubpanel
CONTAINER_TYPE SUBPANEL
POSITION_HINTS 1
LABEL NETSMART Client - default
PUSH_ACTION NetSmartClient
HELP_TOPIC FPOnItemTerm
HELP_VOLUME FPanel
}
# Prompts user for the name of the federation to run.
CONTROL NETSMARTClientPrompt
{
TYPE icon
FNC-1500-0050-110
CHAPTER 4
Add UNIX User Accounts Using Local Files
CONTAINER_NAME NETSMARTSubpanel
CONTAINER_TYPE SUBPANEL
PUSH_ACTION NetSmartClientPrompt
HELP_TOPIC FPOnItemTerm
HELP_VOLUME FPanel
}
Copy the two icon files Dtsiflexrclient.m.pm and Dtsiheartbeat.m.pm into

the <users_home_directory>/.dt/icons directory from the
/opt/NetSmart/.dt/icons directory.
Restart the users Workspace Manager. To do this, right-click on the desktop and click Restart
Workspace Manager.
4.7

This section describes how to add a UNIX user account to a UNIX host that uses local files
for user account administration.
Note: Users are typically added using NIS or NIS+. The local site System Administrator must add
user accounts if NIS or NIS+ is used for user account administration.
Note: If the NETSMART 1500 system uses local files for user account administration, the
NETSMART 1500, Oracle, and software download (SWDL) swdl1 user accounts are automatically
added by the install process if the user accounts do not already exist.
Add UNIX user accounts using local files as follows:

Step
Task
Log on the UNIX host as the root user (or enter su -u).
If a new UNIX group is needed, enter /usr/sbin/groupadd <groupname> to create

the group. If the group already exists, skip this step.
Example: /usr/sbin/groupadd netsmart
FNC-1500-0050-110

4-11
CHAPTER 4
Enter /usr/sbin/useradd -c <comment> -d <homedir> -g <groupname>

-s <shell> <username>. Each field surrounded by angle brackets must be replaced
with appropriate data. Table 4-3 [p. 4-12] describes each of the fields.
Example: /usr/sbin/useradd -c "John Doe" -d /export/home/jdoe -g
netsmart -s /bin/ksh jdoe
Table 4-3: useradd Command Field Descriptions
Field
Description
comment
Description of the use; typically the users full name
homedir
Fully qualified path of the users home directory
groupname
Valid UNIX group name
shell
Logon shell to be used by the user, typically /bin/ksh or /bin/csh
username
User ID
Enter /bin/mkdir -p <homedir> to create the users home directory.

Example: /bin/mkdir -p /export/home/jdoe
Enter /bin/chown <username>:<groupname> <homedir> to apply the correct

permissions to the directory. For additional information, refer to the groupadd and
useradd man pages.
Enter passwd <username> to set the user password.

Example: passwd jdoe
The system prompts to enter and reenter a password.
Enter and reenter the new password.
To configure the new user to be able to run the NETSMART 1500 client software, follow the
instructions in Section 4.6.2, Configure NETSMART 1500 Client Accounts [p. 4-6].
FNC-1500-0050-110
CHAPTER 4
Delete UNIX User Accounts Using Local Files
4.8
Delete UNIX User Accounts Using Local Files

This procedure describes how to delete a UNIX user from a UNIX host that uses local files for
user account administration.
Note: Users are typically added using NIS or NIS+. Contact the network administrator before
using the following procedures.
CAUTION:
Because you may uninstall NETSMART 1500 if the users home directory is
/opt/NetSmart, check with your system administrator before using this procedure.
Step
4.9
Task
Log on the UNIX host as the root user (or enter su -u).
Enter /usr/sbin/userdel <username> to remove the user.
Enter /bin/rm -rf <homedir> to remove the users home directory.
If necessary, remove the users group by typing /usr/sbin/groupdel <groupname>.

If there are other users that still have this group, skip this step.
Understand UNIX Log Files

This section describes the various Solaris system log files.
The main Solaris system log file is /var/adm/messages. This file contains system-related
information, such as the following:
The time of the last system reboot
Any errors that may have occurred during the last reboot
Network errors that may have occurred on the system
System time adjustments
Failed root logon attempts
FNC-1500-0050-110

4-13
CHAPTER 4
Set the Date and Time on the UNIX System
The /var/adm directory contains several message files. The most recent messages are in
/var/adm/messages (and in messages.0); the oldest are in messages.3. After a
certain time (usually 10 days), a new messages file is created. The messages.0 file is
renamed messages.1, messages.1 is renamed messages.2, and messages.2 is
renamed messages.3. The old /var/adm/messages.3 is deleted.
Because /var/adm stores large files containing messages, crash dumps, and other data, this
directory can consume a lot of disk space. To keep the /var/adm directory from growing
too large, unneeded files should be removed periodically.
4.10

This procedure describes how to set the date and time for the NETSMART 1500 server. It
includes the following subprocedures:
4.10.1
NO.
SUBPROCEDURE
PAGE
4.10.1
Change the Date and Time Backward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-14
4.10.2
Change the Date and Time Forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-16
Change the Date and Time Backward

The following describes how to change the date and time to be earlier than the current system
date and time. This procedure must be followed to ensure that the ObjectStream license
continues to work.
CAUTION:
This procedure must not be used to change the date and time forward. Refer to
Section 4.10.2, Change the Date and Time Forward [p. 4-16], for the procedure on changing
the date and time forward.
Note: The ObjectStream license key associated with the NETSMART 1500 server is required for
this procedure. Refer to Section 3.8, Configuring the ObjectStream License [p. 3-37], for more
information on configuring the ObjectStream license.
Change the UNIX system date and time backward as follows:

Step
1
Task
Shut down all NETSMART 1500 clients. On the client GUIs, select Exit from the File menu.
FNC-1500-0050-110
CHAPTER 4
Shut down the NETSMART 1500 server and all Oracle processes. Type netsmart
stopall at the UNIX command prompt, and then press RETURN.
The remaining steps must be done as root user. Enter su -.
Enter the correct password for user root.
Enter /usr/bin/date <mmddHHMMyy> to change the date.

Table 4-4 [p. 4-15] describes the components of the date field.
Table 4-4: Date Command Field Descriptions
Field
Description
mm
2-digit value of the month
dd
2-digit value for the day of the month
HH
2-digit value for the hour of the day, using a 24-hour clock (for example, 00 is 12:00 a.m., and 23 is
11:00 p.m.)
MM
2-digit value of the minute of the hour
yy
Last two digits of the year (for example, 06 for year 2006)
Example: To set the date to November 20, 2006 at 1:19 p.m., the following command
is entered: /usr/bin/date 1120131906.
6
Enter the following: touch /etc/passwd
Enter the following: touch /etc/group
Enter the following: touch /dev
Enter the following: touch /usr/lib
10
Enter the following: rm /var/adm/utmp
11
Enter the following: rm /var/adm/wtmp
12
Enter the following: rm /etc/OBJStream/License/config/*
13
Enter the following: /opt/NetSmart/install/set-ObjLic
FNC-1500-0050-110

4-15
CHAPTER 4
14
Enter the ObjectStream license associated with the server when requested.
15
Reboot the system by entering the following: sync; sync; reboot
16
After the server has rebooted, restart the NETSMART 1500 server. (Refer to Section 3.3,
Starting Up and Shutting Down [p. 3-8].)
4.10.2
Change the Date and Time Forward

Change the UNIX system date and time forward as follows:
Step
Task
Verify that NETSMART 1500 is up and that all NEs are logged on.
As user netsmart, shut down the NETSMART 1500 server. (Refer to Section 3.3.3, Shut
Down Server [p. 3-10].)
Log on as the root user (enter su - and enter the password).
Enter /usr/bin/date <mmddHHMMyy> to change the date.

Refer to Table 4-4 [p. 4-15] for components of the date field.
Start the NETSMART 1500 server.

Refer to Section 3.3.1, Start Server [p. 3-8], for information on starting the NETSMART
1500 server.
Verify that all NEs log back on.
FNC-1500-0050-110
CHAPTER 4
UNIX System Information
4.11

NO.
SUBPROCEDURE
PAGE
4.11.1
System Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-18
4.11.2
System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-19
4.11.3
Disk Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-20
4.11.4
Swap Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-20
4.11.5
System Activities Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-21
4.11.6
Cronjobs Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-25
4.11.7
Defunct Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-26
FNC-1500-0050-110

4-17
CHAPTER 4
4.11.1
System Processes
The System Processes command displays a list of all system processes. A screen similar to the
following displays:
S Y S T E M
P R O C E S S E S
You can either list a particular application process name, or list all
system processes.
Enter process name (or leave blank for all):
UID
PID PPID C
STIME TTY
TIME CMD
root
0
0 0 Sep 21 ?
0:00 sched
root
1
0 0 Sep 21 ?
0:25 /etc/init root
2
0 0 Sep 21 ?
0:00 pageout
root
3
0 0 Sep 21 ?
6:36 fsflush
root
234
1 0 Sep 21 ?
0:00 /opt/NetSmart/OBJStream
License/ObjectStream_lmd
-r /opt/NetSmart/OBJ
root
160
1 0 Sep 21 ?
0:00 /usr/lib/nfs/lockd
root
309
1 0 Sep 21 ?
0:00 /usr/lib/saf/sac -t 300
root
179
1 0 Sep 21 ?
0:00 /usr/lib/autofs/automountd
root
318
291 0 Sep 21 ?
0:00 mibiisa -p 32823
root
123
1 0 Sep 21 ?
0:00 /usr/sbin/rpcbind...
root
194
1 0 Sep 21 ?
0:00 /usr/sbin/cron
root
231
1 0 Sep 21 ?
0:00 /usr/lib/power/powerd
root
247
1 0 Sep 21 ?
0:02 /usr/lib/utmpd
root
315
309 0 Sep 21 ?
0:00 /usr/lib/saf/ttymon
netsmart
316
313 1 Sep 21 ?
0:53 /usr/openwin/bin/Xsun :0
-nobanner -auth /var/dt/A:0Ew6gR_
root
310
1 0 Sep 21 console 0:00 /usr/lib/saf/ttymon -g -h -p
pslab6 console login:
-T sun -d /dev/console -l c
netsmart
422 379
0 Sep 21 pts/2
0:00 [ sdt_shel ]
root
291
1 0 Sep 21 ?
0:00 /usr/lib/snmp/snmpdx -y -c
/etc/snmp/conf
root
301
1 0 Sep 21 ?
0:00 /usr/lib/dmi/dmispd
root
302
1 0 Sep 21 ?
0:00 /usr/lib/dmi/snmpXdmid -s
pslab6
--More--
FNC-1500-0050-110
CHAPTER 4
4.11.2
System Messages
Executing this command displays the latest UNIX system messages. A screen similar to the
following displays:
S Y S T E M
B A C K U P
SunOS pslab6 5.10 Generic_105181-14 sun4u sparc SUNW,Ultra-60
Filesystem
kbytes
/dev/dsk/c0t0d0s0
/dev/dsk/c0t0d0s4
/dev/dsk/c0t0d0s3
/dev/dsk/c0t0d0s5
/dev/dsk/c0t1d0s1
/dev/dsk/c1t2d0s1
/dev/dsk/c1t3d0s0
120739
578351
290065
5601004
6718025
6718025
8782097
used
avail
21053
87613
393818 126698
18577 242482
1528175 4016819
6459706 191139
6560447
90398
5020224 3674053
capacity
20%
76%
8%
28%
98%
99%
58%
Mounted on
/
/usr
/var
/opt
/opt2
/opt3
/opt4
To restore filesystems: Select the required volume from the System Messages
File
Sep 21 07:27:53 pslab6 unix: pci@1f,4000/scsi@3/disk@0,0:a fstype ufs
Sep 21 07:27:53 pslab6 unix: PCI-device: ebus@1, ebus #0
Sep 21 07:27:53 pslab6 unix: su0 at ebus0: offset 14,3083f8
Sep 21 07:27:53 pslab6 unix: su0 is /pci@1f,4000/ebus@1/su@14,3083f8
Sep 21 07:27:53 pslab6 unix: su1 at ebus0: offset 14,3062f8
Sep 21 07:27:53 pslab6 unix: su1 is /pci@1f,4000/ebus@1/su@14,3062f8
Sep 21 07:27:53 pslab6 unix: keyboard is </pci@1f,4000/ebus@1
su@14,3083f8> major <37> minor <0>
Sep 21 07:27:53 pslab6 unix: mouse is </pci@1f,4000/ebus@1/su@14,3062f8>
major <37> minor <1>
Sep 21 07:27:53 pslab6 unix: stdin is </pci@1f,4000/ebus@1/su@14,3083f8>
major <37> minor <0>
Sep 21 07:27:53 pslab6 unix: SUNW,ffb0 at root: UPA 0x1e 0x0
Sep 21 07:27:53 pslab6 unix: SUNW,ffb0 is /SUNW,ffb@1e,0
Sep 21 07:27:53 pslab6 unix: stdout is </SUNW,ffb@1e,0> major <51> minor
- more --<56%>
FNC-1500-0050-110

4-19
CHAPTER 4
4.11.3
Disk Usage
Executing this command lists the current usage of the disk partitions. A screen similar to the
following displays:
Disk Utilization
/dev/dsk/c0t0d0s0
/dev/dsk/c0t0d0s4
/dev/dsk/c0t0d0s3
/dev/dsk/c0t0d0s5
/dev/dsk/c0t1d0s1
/dev/dsk/c1t2d0s1
/dev/dsk/c1t3d0s0
120739 21053 87613 20% /

578351 393818 126698 76% /usr
290065 18577 242482 8% /var
5601004 1528175 4016819 28% /opt
6718025 6459706 191139 98% /opt2
6718025 6560447 90398 99% /opt3
8782097 5020224 3674053 58% /opt4
4.11.4
Swap Info
Executing this command displays the current status of the swap configuration on the server. A
swap space information for pslab6
# swap -s
total: 28808k bytes allocated + 6176k reserved = 34984k used, 8011256k
available
# swap -l
swapfile dev swaplo blocks free
/dev/dsk/c1t2d0s0 32,256 16 4194272 4194272
/dev/dsk/c0t0d0s1 32,121 16 4194272 4194272
/dev/dsk/c0t1d0s0 32,128 16 4194272 4194272
FNC-1500-0050-110
CHAPTER 4
4.11.5
System Activities Menu

ITEM
PAGE
1. sar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-22
2. vmstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-22
3. iostat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-23
4. uptime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-23
5. netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-24
The SYSTEM ACTIVITY menu provides submenu options that aid in checking for
bottlenecks, disks, CPU, or I/O. This menu appears as follows:
S Y S T E M A C T I V I T Y
1. sar
2. vmstat
3. iostat
4. uptime
5. netstat
q. Quit
FNC-1500-0050-110

4-21
CHAPTER 4
1. sar
System activity report (sar) outputs CPU usage for usr, sys, wio, and idle. A screen
S A R
SunOS
nvt1 5.8 Generic_108528-14 sun4u
07:51:14
07:51:19
07:51:24
07:51:29
07:51:34
07:51:39
Average
%usr
9
16
19
20
23
17
06/24/02
%sys
8
8
11
10
11
%wio
0
0
0
0
0
%idle
84
75
70
70
66
10
73
2. vmstat
Executing this command displays CPU and disk statistics. A screen similar to the following
displays:
V M S T A T
procs
r b w
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
swap
202568
6785008
6785008
6784992
6784944
memory
free
159896
718528
718512
718496
718448
re mf
0 102
0 254
0 106
0
56
0
0
page
disk
pi po fr de sr f0 s1 s1 s2 in
0 0 0 0 0 0 2 0 0 136
0 0 0 0 0 0 1 0 0 197
0 0 0 0 0 0 1 0 0 281
0 1 1 0 0 0 8 1 0 252
0 0 0 0 0 0 1 0 0 266
faults
cpu
sy cs us sy id
2517 91 2 1 97
1711 144 7 2 91
1691 202 1 1 98
1415 113 0 1 99
1142 148 0 0 99
FNC-1500-0050-110
CHAPTER 4
3. iostat
Executing this command displays the output from the Solaris iostat utility. A screen similar to
I O S T A T
tin
0
0
0
0
0
tty
fd0
sd15
sd16
sd21
tout kps tps serv kps tps serv kps tps serv kps tps serv us sy
4
0
0 468 15
2
92
3
0
3
0
0
0 2 1
47
0
0
0
6
2
10
2
0
1
0
0
0 6 4
16
0
0
0
3
0
11
3
0
1
0
0
0 0 0
16
0
0
0
3
0
7
3
0
1
0
0
0 0 0
16
0
0
0
5
1
17
2
0
1
0
0
0 0 0
cpu
wt id
1 96
1 89
0 99
0 100
0 100
4. uptime
Executing this command displays uptime statistics. A screen similar to the following displays:
U P T I M E
1:43pm up 1 day(s), 6:16, 2 users, load average: 0.08, 0.11, 0.11
FNC-1500-0050-110

4-23
CHAPTER 4
5. netstat
Executing this command displays the output from the Solaris netstat utility. A screen similar
N E T S T A T
TCP: IPv4
Local Address
Remote Address
Swind Send-Q Rwind
-------------------- -------------------- ----- ------ ----localhost.32850
localhost.32772
32768
0 32768
localhost.32772
localhost.32850
32768
0 32768
localhost.32853
localhost.32772
32768
0 32768
localhost.32772
localhost.32853
32768
0 32768
localhost.32856
localhost.32848
32768
0 32768
:
:
:
nvt1.57171
nvt1.listener
32768
0 32768
nvt1.57172
nvt1.12350
32768
0 32768
nvt1.57173
nvt1.listener
32768
0 32768
nvt1.57174
nvt1.12350
32768
0 32768
nvt1.57175
nvt1.listener 32768 0 32768 0 TIME_WAIT
Recv-Q State
------ ------0 ESTABLISHED
0 ESTABLISHED
0 ESTABLISHED
0 ESTABLISHED
0 ESTABLISHED
0
0
0
0
TIME_WAIT
TIME_WAIT
TIME_WAIT
TIME_WAIT
Active UNIX domain sockets

Address Type
Vnode
Conn Local Addr
Remote Addr
3000267d298 stream-ord 300055c2bc0 00000000 /var/tmp/.oracle/s#29485.1
3000267d5f8 stream-ord 30001aea690 00000000 /tmp/.X11-unix/X0
3000267d7a8 stream-ord 00000000 00000000
3000267d958 stream-ord 300046efcf8 00000000 /tmp/orb_29875_0
FNC-1500-0050-110
CHAPTER 4
4.11.6
Cronjobs Menu
ITEM
PAGE
1. List netsmart crontab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-25
2. Edit netsmart crontab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-26
This submenu helps administer crontab files. This submenu appears as follows:
C R O N T A B
1.
2.
e.
m.
p.
q.
A D M I N I S T R A T I O N
List netsmart crontab

Edit netsmart crontab
Enable Root Access
Go back to the Main Menu
Go back to the Previous Menu
Quit
1. List netsmart crontab

This option lists the current crontab for the entered user ID. This example displays the user
netsmart crontab:
0 * * * * /opt/NetSmart/bin/purge
0 0,6,12,18 * * * /opt/NetSmart/bin/purge_logs_hourly
0 * * * * /opt/NetSmart/bin/backup_logs
FNC-1500-0050-110

4-25
CHAPTER 4
2. Edit netsmart crontab

WARNING:
Before changing or editing the netsmart crontab option, contact the Fujitsu Technical
Assistance Center (FTAC).
Users can use this option to edit their own crontab. This example displays the user root
crontab:
#ident "@(#)root 1.14 06/07/31 SMI" /* SVr5.0 1.1.4.1 */
#
# The root crontab should be used to perform accounting data collection.
#
# The rtc command is run to adjust the real time clock if and when
# daylight savings time changes.
#
10 3 * * 0,4 /etc/cron.d/logchecker
10 3 * * 0 /usr/lib/newsyslog
15 3 * * 0 /usr/lib/fs/nfs/nfsfind
1 2 * * * [ -x /usr/sbin/rtc ] && /usr/sbin/rtc -c > /dev/null 2>&1
~
~
....
~
~
"/tmp/crontab0M1P3j" 21 lines, 742 characters
4.11.7
Defunct Processes
This command checks for defunct processes. A screen similar to the following displays:
netsmart 1170
481
0:00 <defunct>
FNC-1500-0050-110
CHAPTER 4
Back Up the UNIX System
4.12

NO.
SUBPROCEDURE
PAGE
4.12.1
Perform a Full System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-27
4.12.2
Back Up the NETSMART 1500 Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-28
4.12.3
View a Log File of the Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-30
This section describes the tasks used for a full (that is, Level 0) backup of all the files on the
NETSMART 1500 system as well as a NETSMART 1500 backup.
4.12.1
Perform a Full System Backup

This procedure initiates a full level-zero backup of all partitions local to the system. Because
this activity affects performance, it is best done during off-peak hours.
Do a full system backup as follows:
Note: A blank tape must be inserted into the tape drive and be in ready state before starting
this procedure. Multiple tapes are required for a full system backup.
Step
Task
Ensure that a blank tape is inserted into the tape drive.
Enter 4 UNIX System Administration.
Enter 2 System Backup.
FNC-1500-0050-110

4-27
CHAPTER 4
The backup initiates. A screen similar to the following displays:

S Y S T E M
B A C K U P
SunOS pslab6 5.10 Generic_105181-14 sun4u sparc SUNW,Ultra-60

Filesystem
/dev/dsk/c0t0d0s0
/dev/dsk/c0t0d0s4
/dev/dsk/c0t0d0s3
/dev/dsk/c0t0d0s5
/dev/dsk/c0t1d0s1
/dev/dsk/c1t2d0s1
/dev/dsk/c1t3d0s0
kbytes
120739
578351
290065
5601004
6718025
6718025
8782097
used
21053
393818
18577
1528175
6459706
6560447
5020224
avail
z87613
126698
242482
4016819
191139
90398
3674053
capacity
20%
76%
8%
28%
98%
99%
58%
Mounted on
/
/usr
/var
/opt
/opt2
/opt3
/opt4
To restore filesystems: Select the required volume from the

filesystem list above, then count down to the entry on the list.
Note: Volume 1 is this dd block.
ERROR: Sorry, tape device /dev/rmt/0 could not be accessed.
Contents of /etc/dumpdates:--------------------------/dev/rdsk/c0t0d0s0
0 Sun Jun 25 01:00:09 2006
/dev/rdsk/c0t0d0s4
0 Sun Jun 25 01:00:41 2006
/dev/rdsk/c0t0d0s3
0 Sun Jun 25 01:10:12 2006
/dev/rdsk/c0t0d0s5
0 Sun Jun 25 01:10:45 2006
/dev/rdsk/c0t1d0s1
0 Sun Jun 25 01:23:29 2006
/dev/rdsk/c1t2d0s1
0 Sun Jun 25 01:46:03 2006
/dev/rdsk/c1t3d0s0
0 Sun Jun 25 02:15:43 2006
4.12.2
Back Up the NETSMART 1500 Application

This section describes how to back up the NETSMART 1500 server application software and
configuration files.
To back up the UNIX operating system, the Heartbeat tool can be used. Refer to
Section 4.12.1, Perform a Full System Backup [p. 4-27], for more information on backing up
the full UNIX system.
WARNING:
This section does not contain procedures for backing up the Oracle database. Refer to
Section 2.6, Standard Database Backup [p. 2-25], for more information on backing up the
Oracle database.
FNC-1500-0050-110
CHAPTER 4
The following procedure backs up all files and directories listed in the file
/opt/NetSmart/bin/admin/backup_list.txt. By default, only the following files
and directories are backed up:
/opt/NetSmart/bin
/opt/NetSmart/client_env.csh
/opt/NetSmart/client_env.sh
/opt/NetSmart/Properties
/opt/NetSmart/install
The user can edit the backup_list.txt file to include any combination of files and/or
directories for backup.
Back up the NETSMART 1500 server application software as follows:
Step
Task
Ensure that a blank tape is inserted into the tape drive.
Enter 4 UNIX System Administration.
Enter 3 NETSMART 1500 Backup.

The system backs up the specified directories to tape and, at completion, ejects the tape.
Screens similar to the following display:
SunOS boco 5.10 Generic_105181-17 sun4u sparc SUNW,Ultra-2
Directories/Files from disk /dev/dsk/c0t0d0s6
/opt/NetSmart/bin,/opt/NetSmart/client_env.csh,/opt/NetSmart/client_env.sh
,/opt/NetSmart/boco,/opt/NetSmart/install
To restore files/directories: Select the required entry from the list
above, then count down to the entry on the list.
Note: Volume 1 is this dd block.
FNC-1500-0050-110

4-29
CHAPTER 4
4.12.3
View a Log File of the Backup

A log file of the backup can be viewed through the following tasks:
Step
Task
Select the Heartbeat icon on the CDE.
Enter 4 Unix System Administration.
Enter 4 Backup Log.

The screen displays the latest log file. A screen similar to the following displays:
S Y S T E M
B A C K U P
L O G S
Choose a log file to view

1) /opt/NetSmart/logs/backups/log.Sun
2) /opt/NetSmart/logs/backups/log.Thu
#? 12006
Sun Jun 25 01:00:01 CDT 2006
Tape label written successfully for tape device /dev/rmt/0n.
ufsdump 0ucf /dev/rmt/0n /dev/dsk/c0t0d0s0 DUMP: Writing 63 Kilobyte
records
DUMP: Date of this level 0 dump: Sun Jun 25 01:00:09 2006
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rdsk/c0t0d0s0 (pslab6:/) to /dev/rmt/0n.
DUMP: Mapping (Pass I) [regular files]
DUMP: Mapping (Pass II) [directories]
DUMP: Estimated 45132 blocks (22.04MB).
DUMP: Dumping (Pass III) [directories]
DUMP: Dumping (Pass IV) [regular files]
DUMP: 45106 blocks (22.02MB) on 1 volume at 810 KB/sec
DUMP: DUMP IS DONE
DUMP: Level 0 dump on Sun Jun 25 01:00:41 2006
....
ufsdump 0ucf /dev/rmt/0n /dev/dsk/c0t0d0s3
DUMP: Writing 63 Kilobyte records
DUMP: Date of this level 0 dump: Sun Jun 25 01:10:12 2006
DUMP: Date of last level 0 dump: the epoch
--More--(29%)
FNC-1500-0050-110
CHAPTER 4
Admintool
4.13
Admintool
This option displays the Solaris Admintool: Users dialog box. For further information, refer to
the Sun system administration documentation. An example of the Admintool: Users dialog is
shown in Figure 4-1 [p. 4-31].
Figure 4-1: Admintool: Users Dialog
4.14
Restore UNIX Files

The Solaris ufsrestore command is used to read the back-up tapes and to restore files
from tape. Refer to the ufsrestore main page for additional information.
4.15
Restore Root (/)

Restoring a damaged/(root) file system from backup differs from other types of restore
operations. The Solaris 10 (October 2000) installation CD-ROM is used to boot the system
and reload the root file system. For a complete description of the steps necessary to restore
root, refer to the Restoring Files and File Systems chapter in the Sun Solaris 10, Administering
File Systems Answer Book.
FNC-1500-0050-110

4-31
5
CHAPTERS/APPENDIXES
NETWORK ADMINISTRATION
1 Introduction
WARNING:
3 NETSMART 1500
Administration
4 UNIX System
Administration
6 Service Support
7 High Availability
Administration
Many of the operations described in this chapter use the Heartbeat

tool. When using Heartbeat with root enabled, do not press CTRL+C.
Doing so may cause Heartbeat to terminate abnormally. CTRL+C may
be used with Heartbeat when root is not enabled.

NO.
SECTION
PAGE
5.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-2
5.2
TCP/IP and OSI Networks with NETSMART 1500 . . . . . . . . .
5-5
5.3
OSI Startup and Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-7
5.4
OSI Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-11
5.5
TARP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-18
5.6
IP Address Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-22
FNC-1500-0050-110

CHAPTER 5
Network Administration
Overview
5.1
Overview
NO.
SUBSECTION
PAGE
5.1.1
Start FTAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-4
5.1.2
Stop FTAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-4
Network administration uses the Network Administration option of the Heartbeat tool. This
option provides the following menu, which is the starting point for most of the procedures
described in this chapter:
N E T W O R K
1.
2.
3.
4.
5.
6.
e.
m.
q.
Start FTAM * (Requires OSI Stack existence)

Stop FTAM * (FTAM will restart if NETSMART server is running)
Start OSI *
Stop OSI * (OSI Stack will restart if NETSMART server is running)
OSI Menu
TARP Menu
Disable Root Access
Quit

+ can only be executed by NETSMART administrator
Table 5-1 [p. 5-2] lists the menu and submenu items for network administration as well as
where they are described in this practice.
Table 5-1: Network Administration Menu Items
Menu Item
Reference
1. Start FTAM
Section 5.1.1, Start FTAM [p. 5-4]
2. Stop FTAM
Section 5.1.2, Stop FTAM [p. 5-4]
3. Start OSI
Section 5.3.1, Start an OSI Communications Stack [p. 5-8]
4. Stop OSI
Section 5.3.2, Stop an OSI Communications Stack [p. 5-9]
FNC-1500-0050-110
CHAPTER 5
Overview
Table 5-1: Network Administration Menu Items (Cont.)

Menu Item
Reference
5. OSI Menu
Section 5.4, OSI Menu [p. 5-11]

1. List OSI Processes
Section 5.4.1, subsection List OSI Processes [p. 5-12]
2. Restart OSI and FTAM
Section 5.4.2, subsection Restart OSI and FTAM [p. 5-12]
3. Set NSAP Address
Section 5.4.3, subsection Set NSAP Address [p. 5-13]
4. Display NSAP Address
Section 5.4.4, subsection Display NSAP Address [p. 5-15]
5. Add Route
Section 5.4.5, subsection Add Route [p. 5-16]
6. Delete Route
Section 5.4.6, subsection Delete Route [p. 5-16]
7. Display Route
Section 5.4.7, subsection Display Route [p. 5-17]
8. Display Dynamic Routes
Section 5.4.8, subsection Display Dynamic Routes [p. 5-17]
6. TARP Menu
FNC-1500-0050-110
Section 5.5, TARP Menu [p. 5-18]

1. Set TARP TID
Section 5.5.1, subsection Set TARP TID [p. 5-19]
2. Display TARP TID
Section 5.5.2, subsection Display TARP TID [p. 5-19]
3. Add Manual Adjacency
Section 5.5.3, subsection Add Manual Adjacency [p. 5-19]
4. Delete Manual Adjacency
Section 5.5.4, subsection Delete Manual Adjacency [p. 5-20]
5. Display Manual Adjacency
Section 5.5.5, subsection Display Manual Adjacency [p. 5-20]
6. Add Manual TARP Entries
Section 5.5.6, subsection Add Manual TARP Entries [p. 5-21]
7. Delete Manual TARP Entries
Section 5.5.7, subsection Delete Manual TARP Entries [p. 5-21]
8. Display Manual TARP Entries
Section 5.5.8, subsection Display Manual TARP Entries [p. 5-21]

5-3
CHAPTER 5
Overview
5.1.1
Start FTAM
This option starts the File Transfer, Access, and Management (FTAM) protocol process. A
O S I
1.
2.
d.
m.
p.
q.
S T A C K
S E L E C T I O N
Ftl2k.1
Ftl2k.2
Disable Root Access (return to netsmart)
Go back to the previous menu
Quit
1
Starting (possibly additional) FTAM Responder...(results described in
/opt/NetSmart/Log/osi.log)
5.1.2
Stop FTAM
This option stops the FTAM process. A screen similar to the following displays:
Note: The FTAM process restarts if the NETSMART server is running.
O S I
1.
2.
d.
m.
p.
q.
S T A C K
S E L E C T I O N
Ftl2k.1
Ftl2k.2
Quit
1
Stopping FTAM Responder...
(results described in /opt/NetSmart/Log/osi.log)
FNC-1500-0050-110
CHAPTER 5
TCP/IP and OSI Networks with NETSMART 1500
5.2

NO.
SUBSECTION
PAGE
5.2.1
OSI Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-5
5.2.2
TCP/IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-6
The NETSMART 1500 server can support the following protocols when communicating
with the NEs:
Transmission Control Protocol/internet Protocol (Tcp/ip) and Open Systems

Interconnection (OSI)
TCP/IP only
Before installing NETSMART 1500, you should know what types of communication
protocols the NETSMART 1500 server will be using. Adding OSI support to NETSMART
1500 after the installation of a TCP/IP-only configuration is more difficult than adding it at
time of installation. If a network uses purely TCP/IP communication with the NEs but may
use OSI support later, installing both TCP/IP and OSI support during initial installation is
recommended rather than TCP/IP-only support.
5.2.1
OSI Connectivity
NETSMART 1500 requires a minimum of two network interface cards (NICs) when running
with OSI connectivity. Some server configurations require more. Refer to
FNC-1500-0050-100, Installation Guide, Section 1.4, Hardware Platforms [p. 1-4].
For NETSMART 1500 to function properly, the selected NICs must be within the first 10
devices for a particular driver. If the machine is set up using hme or qfe devices, only hme0
hme9 or qfe0qfe9 are allowed.
The NICs chosen for OSI communication can be used for both TCP/IP and OSI
communication.
Each OSI interface requires a unique Ethernet address. The Ethernet address is also referred to
as the media access control (MAC) address. By default, all Ethernet cards on a PCI-based Sun
Solaris machine are configured with the same Ethernet address. By setting the EEPROM
variable local-mac-address? to true and rebooting the system, each Ethernet card is
configured with a unique address. If the EEPROM setting is not available on the system,
unique addresses must be manually assigned to each of the cards. These addresses can be
calculated by the installation or can be specified for each Ethernet card during the installation.
FNC-1500-0050-110

5-5
CHAPTER 5
To determine whether the system supports the EEPROM variable, enter the command
eeprom | grep mac. If the response is local-mac-address?=false, the variable
is supported, and the command EEPROM local-mac-address?=true can be used to
tell the system to use unique addresses. This command takes effect upon rebooting the
system.
Each interface used to connect with OSI NEs is required to have a unique network service
access point (NSAP) address. The NSAP address is similar to an IP address in TCP/IP
connectivity. Refer to Section 5.4.3, Set NSAP Address [p. 5-13], for more information on
the NSAP address.
5.2.2
TCP/IP Connectivity
ITEM
PAGE
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-6
Single IP Address for All TCP/IP Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-7
General
The NETSMART 1500 server software handles TCP/IP connectivity using standard routing
tables set up on the host machine. These routes are set up from within the Solaris operating
system, not from within the NETSMART 1500 server application. (An exception is using a
single IP address for all communication to the NEs, which is discussed in Section 5.2.2,
subsection Single IP Address for All TCP/IP Communication [p. 5-7].) The main pages for
ifconfig, route, and routed contain more information about routing. The assumption is that
the user has a basic understanding of IP routing.
Each NIC used to communicate to IP-based NEs must be configured with an IP address and
a host name. The IP address of each card should be on the subnet of the destination IP NEs.
If the NIC cards are on a different subnet, a static route should be added to the system.
These IP addresses and static routes need to be visible even after a NETSMART 1500 server
host reboot. Therefore, the IP addresses and static routes should be configured in the
appropriate /etc files on the host machine.
Setting up IP Multipathing is recommended if multiple NICs are used to connect to NEs.
Multipathing provides fault tolerance to NIC failures and load balancing of outbound traffic.
Multipathing avoids the need for interface load balancing, as was required in previous versions
of Solaris.
FNC-1500-0050-110
CHAPTER 5
OSI Startup and Shutdown
Single IP Address for All TCP/IP Communication

If the NETSMART 1500 Administrator uses a single IP address for all the TCP/IP-related
communications with the IP NEs, the following can be done manually after the installation
has completed.
Edit the System.properties file located in /opt/NetSmart/Properties. Change
the line:
#comms.networkaddress.localaddress =
to
comms.networkaddress.localaddress = xxx.xxx.xxx.xxx
Where xxx.xxx.xxx.xxx is the IP address of the intended NIC.

When a NETSMART 1500 server is configured with this option, failure of this interface
causes all communication with IP-based NEs to fail unless IP multipathing is configured to
provide tolerance to NIC failures. Hence, configuring IP multipathing for this option is
recommended.
5.3

NO.
SUBPROCEDURE
PAGE
5.3.1
Start an OSI Communications Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-8
5.3.2
Stop an OSI Communications Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-9
Under normal operating circumstances, OSI is started when the NETSMART 1500 server
application is started using Heartbeat (refer to Section 3.3.1, Start Server [p. 3-8]). The OSI is
shut down when the NETSMART 1500 server application is stopped using Heartbeat (refer
to Section 3.3.3, Shut Down Server [p. 3-10]).
There may be instances, such as NETSMART 1500 troubleshooting, when starting and
stopping the OSI processes independent of the main NETSMART 1500 server application
are necessary.
FNC-1500-0050-110

5-7
CHAPTER 5
Refer to Section 5.3, OSI Startup and Shutdown [p. 5-7], for more information on OSI
startup and shutdown menu options.
Note: Stopping the OSI processes works only when the NETSMART 1500 server application is not
running. If the NETSMART 1500 server application is running and the OSI processes are shut
down, the shutdown appears as a communications failure to the NETSMART 1500 server
application, and the OSI processes are automatically restarted.
Refer to Section 3.3.3, Shut Down Server [p. 3-10], for procedures on shutting down the
NETSMART 1500 server.
5.3.1
Start an OSI Communications Stack

Start an OSI communications stack as follows:
Step
Task
Enter 4 NETWORK Administration.
Enter 3 Start OSI.

A menu listing the possible OSI stacks displays:
O S I
1.
2.
d.
m.
p.
q.
S T A C K
S E L E C T I O N
tl2k.1
tl2k.2
Quit
Select a number/letter (case insensitive): 1
Enter the number corresponding to the OSI stack that needs to be started. A screen similar to
Do you want to [c]ontinue or [q]uit (default = c)?
Enter c to continue.
FNC-1500-0050-110
CHAPTER 5
The OSI processes associated with the selected OSI stack start. A screen similar to the
following displays:
Starting (possibly additional) OSI Stack...(results described in
/opt/NetSmart/gordon/Log/osi.log)
5.3.2
Stop an OSI Communications Stack

Note: Stopping the OSI processes works only when the NETSMART 1500 server application is not
running. If the NETSMART 1500 server application is running and the OSI processes are shut down, the
shutdown appears as a communications failure to the NETSMART 1500 server application, and the
OSI processes are automatically restarted.
Stop an OSI communications stack as follows:

Step
Task
Enter 4 Stop OSI.

A menu listing the possible OSI stacks displays:
Note: The OSI stack restarts if the NETSMART 1500 server is running.
O S I
1.
2.
d.
m.
p.
q.
S T A C K
S E L E C T I O N
tl2k.1
tl2k.2
Quit
Enter the number corresponding to the OSI stack that must be stopped. A screen similar to
Do you want to [c]ontinue or [q]uit (default = c)?
FNC-1500-0050-110

5-9
CHAPTER 5
Enter c to continue.
The OSI processes associated with the selected OSI stack stop. A screen similar to the
following displays:
Stopping OSI Stack... (results described in
/opt/NetSmart/gordon/Log/osi.log)
FNC-1500-0050-110
CHAPTER 5
OSI Menu
5.4
OSI Menu
NO.
SUBSECTION
PAGE
5.4.1
List OSI Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-12
5.4.2
Restart OSI and FTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-12
5.4.3
Set NSAP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-13
5.4.4
Display NSAP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-15
5.4.5
Add Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-16
5.4.6
Delete Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-16
5.4.7
Display Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-17
5.4.8
Display Dynamic Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-17
Executing this option displays the OSI Menu:

O S I
1.
2.
3.
4.
5.
6.
7.
8.
d.
m.
p.
q.
FNC-1500-0050-110
M E N U
List OSI Processes +

Restart OSI and FTAM * (May lose connection to some or all NEs.)
Set NSAP Address *
Display NSAP Address
Add Route +
Delete Route +
Display Route
Display Dynamic Routes
Go back to previous menu
Quit

5-11
CHAPTER 5
OSI Menu
5.4.1
List OSI Processes

This option displays whether or not the FTAM Responder and OSI stack are running. A
O S I
1.
2.
e.
m.
p.
q.
S T A C K
S E L E C T I O N
gotl2k.2
gotl2k.1
Enable Root Access
Quit

N E T W O R K
P R O C E S S E S
This option will tell you if the FTAMResponder and OSIstack are running.If
they are not, you can go back to the previous menu and start them ifneeded.
Ftl2k.2
FTAMResponder Ftl2k.2 is running
ptl2k.2
OSI stack ptl2k.2 is running
5.4.2
Restart OSI and FTAM

This option restarts the Marben OSI processes. A screen similar to the following displays:
R E S T A R T I N G
O S I
A N D
F T A M
Do you want to [c]ontinue or [q]uit (default = c) ? c

Restarting stack...
Please provide a name for the FTAM Responder (ENTER for default):
Please provide a name for the OSI Stack (ENTER for default):
FTAM Responder and OSI Stack has been restarted
FNC-1500-0050-110
CHAPTER 5
OSI Menu
5.4.3
Set NSAP Address

CAUTION:
Changing OSI addresses disrupts service to NEs temporarily while the address change takes
effect.
CAUTION:
Using an incorrect OSI address causes permanent loss of service to NEs until a valid address
is configured.
This section describes the format of an OSI address and how to change it on the system.
The OSI addresses required by NETSMART 1500 are normally configured during the initial
NETSMART 1500 server installation. However, there may be times when modifying the OSI
address (or addresses) for a NETSMART 1500 server is necessary. Each NETSMART 1500
server has a minimum of two OSI interfaces, each with a unique OSI address (also known as
an NSAP address).
An OSI address consists of 40 hexadecimal characters divided into several sections. The
user-modifiable portions of the OSI address are:
Organization6 characters
Domain4 characters
Area4 characters
To modify an OSI address, use the following tasks:

Step
Task
Enter 5 OSI Menu.
Enter Set NSAP address.
FNC-1500-0050-110

5-13
CHAPTER 5
OSI Menu
A menu of possible OSI stacks displays:

O S I
1.
2.
3.
d.
m.
p.
q.
S T A C K
S E L E C T I O N
gotl2k.1
gotl2k.2
all
Quit
Enter the OSI stack with the address to be modified.

You are prompted for the NSAP address.
The NSAP Address consists of the following:
H39840f80oooooo0000ddddaaaaETHERNETXX
where
ooooo = organization
dddd = domain
aaa = area
You will be prompted for these pieces of information. If you enter values
that are less than the those specified, the values will be padded with
zeroes
Enter a value for ORGANIZATION (default=000000)?
Enter a value for DOMAIN (default=0000)?
Enter a value for AREA (default=0000)?
Enter the new values for the Organization, Domain, and Area sections of the OSI address, and
then press ENTER.
OR
Accept the default value, if it is correct, by pressing ENTER.
FNC-1500-0050-110
CHAPTER 5
OSI Menu
After the address modification is completed, Heartbeat automatically restarts the OSI
processes to ensure that the new addresses take effect. A screen similar to the following
displays:
Using Ethernet hme1
Editing file /opt/NetSmart/marben/bin/gotl2k.1
Device=hme1
Stack =Setting the following variables
LOCNET =H39840f80000000000000000000080020ab294500
LOCNSAP =H39840f80000000000000000000080020ab29451d
TARPNSAP=H39840f80000000000000000000080020ab2945af
def suf 0 Chme
def pri 0 01000000
$load ositl2k ptl2k.1 Ftl2k.1
$def ptl2k.1
calling setnsap with parameter: -dgotl2k.1
FTAM Responder and OSI Stack has been restarted
5.4.4
Display NSAP Address

This command displays the network service access point (NSAP) address. A screen similar to
O S I
1.
2.
3.
d.
m.
p.
q.
S T A C K
S E L E C T I O N
gotl2k.1
gotl2k.2
all
Quit Select a number/letter (case insensitive):
D I S P L A Y
N S A P
A D D R E S S
NSAP Address:
H39840f800000000000000001090800209ac7080020a4c4330800209ac3a71d
Hit any key to Continue
FNC-1500-0050-110

5-15
CHAPTER 5
OSI Menu
5.4.5
Add Route
This option adds an OSI route for an OSI stack. The first screen lists the OSI stacks. The
following sample screen then displays:
A D D
R O U T E
0. Complete
1. Relayed
Select a route type (default=Complete) [?] 0
Enter NSAP to route to: ........................................
[?] 123987ADBH234234098SD<N098345MNBSDF12346
Enter SNPA to route from: ............
[?] 987654321abc
5.4.6
Delete Route
This option deletes an OSI route. The first screen lists the OSI stacks. The following sample
screen then displays:
Select the number of the route to delete
1) R(Route)_234444444444444444444444444444444444(To)_5555(From)_0(Entry)
2) C(Route)_39840f80001090800208096e91d(To)_none(From)_0(Entry)
3) 1(Route)_none(To)_none(From)_0(Entry)#? 1
Deleting Route (234444444444444444444444444444444444)
FNC-1500-0050-110
CHAPTER 5
OSI Menu
5.4.7
Display Route
This option displays the static OSI routes. The first screen lists the OSI stacks. The following
sample screen then displays:
D I S P L A Y
R O U T E S
Rte: C=Complete
R=Relayed
Rte
===
R
C
1
To
======================================
39840f8000000000000000000000000060ac
1235987987345asdf12312987asdf3245988
none
From
===========================
000000000000000
987654987456abc
none
Hit any key to Continue
5.4.8
Display Dynamic Routes

This option displays the dynamic OSI routes. The first screen lists the OSI stacks. The
following sample screen then displays:
D I S P L A Y D Y N A M I C R O U T E
Nsap
=======================================
39840f800000000000000000000000e64704d1d
39840f800000000000000000000000e6402abaf
39840f800000000000000000000000e6402acaf
39840f800000000000000000000000e3a0feeaf
39840f800000000000000000000000e4625f7af
Snpa
=============
00000e4610af
00000e6402ab
00000e6402ac
00000e3a0fee
00000e4625f7
Hit any key to continue
FNC-1500-0050-110

5-17
CHAPTER 5
TARP Menu
5.5
TARP Menu
NO.
SUBSECTION
PAGE
5.5.1
Set TARP TID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-19
5.5.2
Display TARP TID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-19
5.5.3
Add Manual Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-19
5.5.4
Delete Manual Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-20
5.5.5
Display Manual Adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-20
5.5.6
Add Manual TARP Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-21
5.5.7
Delete Manual TARP Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-21
5.5.8
Display Manual TARP Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-21
This option displays the target identifier (TID) Address Resolution Protocol (TARP)
submenu:
T A R P
1.
2.
4.
5.
6.
7.
8.
9.
d.
m.
p.
q.
M E N U
Set TARP TID *

Display TARP TID
Add Manual Adjacency +
Delete Manual Adjacency +
Display Manual Adjacency
Add Manual TARP Entries +
Delete Manual TARP Entries +
Display Manual TARP Entries
Quit
FNC-1500-0050-110
CHAPTER 5
TARP Menu
5.5.1
Set TARP TID

This option enables you to select an OSI stack and then change the host TID. A screen
S E T
T A R P
T I D
The TARP TID is currently PSLAB70. If you would like to change it

enter the new value below. The ID can be no longer than 7 characters
and must be alphanumeric. If you enter a value less than 7 characters
in length, I will pad it with zeroes.
Just hit return if you do not want to change the TARP TID
Enter a TARP TID (default=PSLAB70) [?]
Running OSI_processes
5.5.2
Display TARP TID

This option enables you to select an OSI stack, then displays the current host TID. A screen
D I S P L A Y
T A R P
T I D
TARP TID: PSLAB70

5.5.3
Add Manual Adjacency

This option can be run only by the NETSMART 1500 Administration user created during
installation. It enables you to select an OSI stack and then add manual adjacencies. A screen
Enter the Level (1 or 2) [?] 1
Enter NET for the Manual Adjacency:
........................................
> [?] 134872499719873d9873498729872c9287837283
Would you like to make these changes active in the stack? [y/n] (default=n)
y
Applying changes to the stack.
FNC-1500-0050-110

5-19
CHAPTER 5
TARP Menu
5.5.4
Delete Manual Adjacency

This option enables you to select an OSI stack and delete the specified manual adjacency. This
option can be run only by the NETSMART 1500 Administration user created during
installation. A screen similar to the following displays:
O S I
S T A C K
S E L E C T I O N
1. gotl2k.
2. gotl2k.2
3. s/gotl2k/gotl2k/
Enter stack? 1
Enter the number of the manual adjacency to delete
1) 1(Level)_123456789a123456789b123456789c123456789d(NET)
#? 1
Deleting Manual Adjacency (1 H123456789a123456789b123456789c123456789d)
5.5.5
Display Manual Adjacency

This option enables you to select an OSI stack and display the manual adjacencies. A screen
D I S P L A Y M A N U A L A D J A C E N C I E S
Level NET Address
==================================================================
1
123456789a123456789b123456789c123456789d
FNC-1500-0050-110
CHAPTER 5
TARP Menu
5.5.6
Add Manual TARP Entries

This option enables you to select an OSI stack and add TARP entries to the database. This
option can be run only by the NETSMART 1500 Administration user created during
installation. A screen similar to the following displays:
Enter NET for the Manual Tarp Entry:
........................................
> [?] 987654321a987654321b987654321c9876543200
Enter TID for the Manual Tarp Entry: ...................
> [?] ne-tarp-id-4tarp123
Would you like to make these changes active in the stack? [y/n] (default=n)
y
Applying changes to the stack.
5.5.7
Delete Manual TARP Entries

This option enables you to delete the manual TARP entries. A screen similar to the following
displays:
D E L E T E M A N U A L T A R P E N T R I E
Select the number of the Manual TARP Entry to delete
1) 987654321a987654321b987654321c9876543200(NET)_ne-tarp-id-4tarp123(TID)
#?
5.5.8
Display Manual TARP Entries

This option displays the TARP entries that have been added manually. A screen similar to the
following displays:
D I S P L A Y M A N U A L T A R P E N T R I E S
NET
TID
========================================
==============================
987654321a987654321b987654321c9876543200
ne-tarp-id-4tarp123
FNC-1500-0050-110

5-21
CHAPTER 5
IP Address Change
5.6
IP Address Change
CAUTION:
Changing the IP address is not recommended. If the IP address or host name of the server
must be changed, contact Fujitsu Network Communications Inc. (FNC) technical support at
1-800-USE-FTAC.
CAUTION:
The host name must stay the same, or licensing will fail.
CAUTION:
Changing IP addresses on a NETSMART 1500 server disrupts service to TCP/IP NEs
temporarily while the address change takes effect.
CAUTION:
Using an incorrect IP address causes permanent loss of service to TCP/IP NEs until a valid
address is configured. In addition, an invalid IP address may make the NETSMART 1500
server inaccessible on the TCP/IP network, causing you to be unable to Telnet or log on the
NETSMART 1500 server. If you change IP addresses, you should change them only while
logged on the console of the NETSMART 1500 server, not over the network.
FNC-1500-0050-110
6
CHAPTERS/APPENDIXES
SERVICE SUPPORT
1 Introduction
3 NETSMART 1500
Administration
NO.
SECTION
4 UNIX System
Administration
6.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2
6.2
Edit Support Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-2
6 Service Support
6.3
List Support Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
7 High Availability
Administration
6.4
Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
6.5
FTP Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-3
6.6
Archive Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-4
6.7
Archive System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-6
6.8
Edit Property Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-7
6.9
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-12
6.10
Check Solaris Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-12
6.11
Collect Debug Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-14
FNC-1500-0050-110
PAGE

CHAPTER 6
Service Support
Overview
6.1
Overview
The Service Support menu provides access to the service support logs. The menu options
shown below are described in the following subsections:
S E R V I C E
S U P P O R T
Hotline: 1-800-USE-FTAC
1. Edit Support Log
2. List Support Log
3. Support Information
4. FTP Information
5. Archive Log Files
6. Archive System *
7. Edit Property Files +
8. System Information
9. Check Solaris Patches
10. Collect Debug Information *
q. Quit
6.2
Edit Support Log

The Edit Support Log option displays the support log file
/opt/NetSmart/logs/supportlog in your default editor. This log can be used to
keep a record of issues and the responses from Fujitsu Network Communications Inc. (FNC).
Sun Jun 25 14:27:49 CDT 2006
---------------------------~
~
~
~
~
~
~
~
"/opt/NetSmart/logs/supportlog" 4 lines, 60 characters
FNC-1500-0050-110
CHAPTER 6
Service Support
List Support Log
6.3
List Support Log

The List Support Log option displays the contents of the current support log
/opt/NetSmart/logs/supportlog. A screen similar to the following displays:
L I S T
S U P P O R T
L O G
Sun Jun 25 14:27:49 CDT 2006

----------------------------
6.4
Support Information
This option displays the address and phone number for Fujitsu Technical Assistance Center
(FTAC) support. A screen similar to the following displays:
G E N E R A L
S U P P O R T
For Technical Assistance call 1-800-USE-FTAC (1-800-873-3822)

Fujitsu Network Communications, Inc.
2801 Telecom Parkway,
Richardson, TX 75082
FAX (972) 479-2901
For Sales assistance please call 1-800-777-FAST
6.5
FTP Information
FTP Information displays information for FTP file transfer with FNC. A screen similar to the
following displays:
F T P
Site : fncftp.fnc.fujitsu.com
Login : nms
Password : nms
FNC-1500-0050-110

6-3
CHAPTER 6
Service Support
Archive Log Files
6.6
Archive Log Files

This option archives the log files and provides the option of transferring (using FTP) the files
to FNC for analysis. A partial display is shown as follows:
Note: The tar files are created in /opt/NetSmart/logs/archives. For the example below:
/opt/netsmart2.2/logs/archives/06241431/ftp.tar.
A R C H I V E
L O G
F I L E S
Do you want to [c]ontinue or [q]uit (default = c) ? c

/opt/netsmart2.2/bin/heartbeat[15]: -e
Please enter c for continue or q for quit: not found
Creating Log on system
SunOS nvt1 5.10 Generic_108528-14 sun4u sparc SUNW,Ultra-4
Type a short description of the system condition below.
Hit ^D to end.
FNC-1500-0050-110
CHAPTER 6
Service Support
Archive Log Files
Type a description followed by CTRL+D to end the description.

Preparing system info files for FTP to Fujitsu
SunOS nvt1 5.10 Generic_108528-14 sun4u
14:33:01
%usr
%sys
%wio
14:33:06
74
14
0
14:33:11
77
11
1
14:33:16
69
13
3
14:33:21
83
9
0
14:33:26
31
8
0
06/25/06
%idle
13
11
15
8
61
Average 67 11 1 22 procs memory page disk faults cpu

r b w
swap
free
re mf pi po fr de sr f0 m4 s0 s1 in sy cs us sy id
0 0 0 5848176 443608 78 424 190 0 0 0 0 0 5 3 4 547 2254 2405 18 9 73
0 0 0 5570624 300408 72 632
0 0 0 0 0 0 2 1 1 610 104448 2876 54 11 35
1 0 0 5543896 294176 129 1179
0 1 1 0 0 0 6 0 2 726 105406 3062 72 13 15
1 0 0 5619712 305000 79 678
1 3 3 0 0 0 6 53 2 929 84544 3082
58 14 28
1 0 0 5557720 311408 61 943
0 0 0 0 0 0 1 25 1 797 104926 2902 85 13
3
tty
md40
sd0
sd1
sd2
cpu
tin tout kps tps serv kps tps serv kps tps serv kps tps serv us sy wt id
0
2 244
5
7
9
3
19 86
4
6 79
3
6 18 9
1 73
0
47 10
2
4
0
0
0 10
1
4
0
0
0 87 7
0 6
0
16 24
6
5
0
0
0 22
3
6
0
0
0 62 18 1 20
0
16 44
5
5
2
1
3 19
2
5 16
1
4 51 14 0 34
0
16 10
2
4
0
0
4 10
1
4
0 0
0 76 12 0 12
Disk Utilization/dev/dsk/c0t0d0s0 16805482 2295376 14342052 14% /
Swap space information for nvt1#
swap -s
total: 1242144k bytes allocated + 1260976k reserved = 2503120k used, 5591416k
available
# swap -l
swapfile dev swaplo blocks free
/dev/dsk/c0t0d0s1 32,1 16 1027200 1020320
/nsdata/NSSwapFile - 16 12287984 12281104
Total swap on server nvt1: 6817 MBytes.
Process table information:
Prepare tar file for FTP to Fujitsu (y/n)? [y/n] (default=n) y
FNC-1500-0050-110

6-5
CHAPTER 6
Service Support
Archive System
When you select y, the following displays;

The file /opt/netsmart5/logs/archives/06241431/ftp.tar is ready to ftp to
Fujitsu.
Put info onto tape /dev/rmt [y/n] (default=n) n
6.7
Archive System
The Archive System option creates an archive file. An example of the system display is shown
below:
A R C H I V E S Y S T E M
Creating archive in /opt/netsmart5/archives/files/062402.143750
FNC-1500-0050-110
CHAPTER 6
Service Support
Edit Property Files
6.8
Edit Property Files

The Edit Property Files option allows you to select a directory from the Property File
directories and then edit a specific property file. A screen similar to the following displays:
P R O P E R T Y
F I L E
D I R E C T O R I E S
Please select a directory

1) Current directory
2) ApplicationServer-1
3) ApplicationServer-2
4) BankClient
5) BankServer-1
6) BankServer-2
7) clientRepository
8) CommunicationServer-1
9) CommunicationServer-2
10) ConnectionManager
11) COSServer
12) DataServicesManager
13) DefaultProperties
14) EmlNmlServer
15) fenicsd
16) Framework
17) fwjvm
18) GUIClient
19) isrepository
20) nedlrepository
#?
FNC-1500-0050-110
21)
22)
23)
24)
25)
26)
27)
28)
29)
30)
31)
32)
33)
34)
35)
36)
37)
38)
39)
40)
neTimeSyncScheduler
nif
NotifService
Nsh
NSWebService
PerformanceManagement
PM-ES
PresentationServer-1
rmbuscheduler
Scheduler
Security
SessionManager
SNMPServer
SwmgrServer
TARPServer
TL1UplinkServer
TopologyServer
UPSManager
Return to previous menu
Stop listing directories

6-7
CHAPTER 6
Service Support
Edit Property Files
As an example, if you select option 1 (Current directory), the list of property files to edit is
listed (as shown in the following example). When you select a file, the file is opened in your
default editor.
E D I T
P R O P E R T Y
F I L E S
Use this option to edit one of the many property files that wereconfigured
during installation.
Please select one of the following
1) Component.properties
2) Container.properties
3) CORBAFactory.properties
4) DB.properties
5) FenicsNodes.properties
6) JavaGroups.properties
7) NetsmartServer.properties
8) NetsmartServices.properties
9) NSContexts.properties
10) PersistentFactory.properties
#?
11)
12)
13)
14)
15)
16)
17)
18)
19)
Process.properties
Server.properties
ServerAssignment.properties
ServerGroups.properties
System.properties
Trace.properties
vbj.properties
Return to previous menu
Stop editing files
Table 6-1 [p. 6-9] lists some of the more important property files and their key values. All
property files are located in the following directory:
/opt/NetSmart/Properties
CAUTION:
When editing property files, ensure there are no extra spaces at the end of each line.
FNC-1500-0050-110
CHAPTER 6
Service Support
Edit Property Files
Table 6-1: Property Files and Key Values

Property file (s)
Function(s)
Key Value(s)
ApplicationServer-<n>/
ApplicationServer-<n>
.properties
Controls the validation of a facility

state before deletion of a
cross-connect by performing an
additional check if the
cross-connect drops to an
EC-1/DS3 or DS1 port. If the
state of the drop side facility is In
Service, a warning displays.
To make the additional check before deleting the

cross-connect, change default value false in
Controls the delay to be

introduced after sending the
ENT-EQPT/DLT-EQPT
command and before sending the
RTRV-EQPT command to the
HUB card in FLASH-192.
In versions before Version 5.2,
there is some delay on the NE
before the state change takes place
due to ENT-EQPT/DLT-EQPT.
If a RTRV-EQPT command is
sent immediately after the
ENT-EQPT command, the
resulting state change is not
correctly reported.
FNC-1500-0050-110
emlcrossconnectmanager.
validateFacility=false to true.
Do this for all ApplicationServer files.

Restart NETSMART 1500 to make changes
permanent.
To get the correct state of the HUB card, send the
RTRV-EQPT command after some delay. This
delay can be changed in
Flash192_HUB_waitTimer = 20000.
The above value is in milliseconds. Do this for all

ApplicationServer property files.
Restart NETSMART 1500 for changes to be
effective.
Note: The delay is not introduced with
FLASH-192 Versions 5.2 and above.

6-9
CHAPTER 6
Service Support
Edit Property Files
Table 6-1: Property Files and Key Values (Cont.)

Property file (s)
Function(s)
Key Value(s)
Properties/
TimeZone.properties
Controls which time zone is

displayed as default in the Add
NE/Edit NE dialog box and which
time zones are added.
TimeZone0 is for the default time zone and is

changed for the new default.
The default file is:
TimeZone0=EST
TimeZone1=MST
TimeZone2=CST
TimeZone3=GMT
TimeZone4=PST
TimeZone5=Sydney(Australia)
TimeZone6=Adelaide(Australia)
TimeZone7=Brisbane(Australia)
TimeZone8=Singapore
TimeZone9=Japan
TimeZone10=HongKong
TimeZone11=Indianapolis(America)
To change the default time zone to CST, you

would change TimeZone0 to CST.
TimeZone0=CST
TimeZone1=MST
TimeZone2=EST
TimeZone3=GMT
TimeZone4=PST
etc.
The order does not matter, only the number for

each time zone.
Note: Entering an invalid time zone does not
generate an error but will cause the NE time to be
set to GMT when time synchronization is done.
GUIClient
/ApplicationGraphics
/NEData_en.properties
Changes the color for various

alarm attributes.
Caution: Because some colors are
not readily visible on a screen, the
default colors are recommended.
There are a number of parameters where you

specify a color. For example, the default value of
color for critical alarms is
alarmCritical.color = red. Another
example is the default color code for the warning
alarm, which is alarmWarning.color =
#a52a2a.
The user can change the colors with predefined
colors, which are red, green, blue, black, cyan,
dark gray, light gray, magenta, orange, and pink.
The user can also specify a more exact color in
hexadecimal by stringing the red, green, and blue
values (0255 for each), converting each one to
hexadecimal, and then putting a # sign before the
string, as shown with the
alarmWarning.color.
If no color is specified or if the color is not
readable, the default is black.
FNC-1500-0050-110
CHAPTER 6
Service Support
Edit Property Files
Table 6-1: Property Files and Key Values (Cont.)

Property file (s)
Function(s)
Key Value(s)
GUIClient/
ApplicationGraphics/
ApplicationGraphics_en
.properties
Changes the name of the severity

of an alarm in NETSMART 1500.
For example, the user can change
the warnings from the default WN
to any 2-letter word (usually all
caps).
The following are the default values for critical

alarms:
counterCritical.label = CR
counterCritical.shortLabel = CR
counterCritical.toolTip =
Critical Alarms
Caution: Ensure that there are no extra spaces at

the end of each line.
This is specific to the client workstation for
which the change is done and is not reflected in
all the clients. To reflect in all of the clients, the
property files for all the clients would need to be
changed.
counterSystem.color=yellow sets the
color of the system event toolbar icon to yellow.
Default is blue.
GUIClient/
GUIClient.properties
FNC-1500-0050-110
After exiting NETSMART 1500

Client (File->Exit), controls
whether the logon screen is
displayed again.
If WindowsStyleLogout = true, after the

GUI client exits, the logon screen is displayed
again, which saves time to run client-start.
If WindowsStyleLogout = false, the
client exits fully, and the user must run the
client-start to start the logon. This is the default
setting.

6-11
CHAPTER 6
Service Support
System Information
6.9
System Information
System Information displays details about the host system, including host name, IP address,
host ID, software level, and patches that have been applied. A screen similar to the following
displays:
S Y S T E M
Hostname: nvt1
Hostid: 80a76a66
Release: 5.10
Kernel architecture: sun4u
Application architecture: sparc
Hardware provider: Sun_Microsystems
Domain: nvt.domain
Kernel version: SunOS 5.10 Generic 108528-14 June 2006
IP Address: 167.254.235.1 n

The following patches have been installed:
109134-19
109889-01
110369-04
110370-02
110373-02
110374-06
110376-01
110833-01
110853-01
108528-09
108528-10
6.10
Check Solaris Patches

The Check Solaris Patches option displays system information and Solaris patches to be loaded.
C H E C K I N G
S O L A R I S
P A T C H E S
There are no patches required

FNC-1500-0050-110
CHAPTER 6
Service Support
Check Solaris Patches
Refer to FNC-1500-0050-100, Installation Guide, Section B, Solaris Patches [p. B-1], for
more information.
FNC-1500-0050-110

6-13
CHAPTER 6
Service Support
Collect Debug Information
6.11

NO.
SUBSECTION
PAGE
6.11.1
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-15
6.11.2
NETSMART Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-16
6.11.3
ORACLE Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-17
6.11.4
All Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-17
The Collect Debug Information menu shown below provides menu options to archive debug
data to tar files as described below.
D E B U G I N F O R M A T I O N
1. System Information
2. NETSMART Information
3. ORACLE Information
4. All Information
q. Quit
FNC-1500-0050-110
CHAPTER 6
Service Support
6.11.1
System Information
The System Information option archives system debug data to
/tmp/NETSMARTDataLog_system.tar.Z. A screen similar to the following displays:
Getting System information
Generating file :/tmp/NETSMARTDataLog_system.tar
a /tmp/NETSMARTDataLog_system/ 0K
a /tmp/NETSMARTDataLog_system/hostname.xxx 1K
a /tmp/NETSMARTDataLog_system/hosts 1K
a /tmp/NETSMARTDataLog_system/defaultdomain 1K
a /tmp/NETSMARTDataLog_system/defaultrouter 1K
a /tmp/NETSMARTDataLog_system/nodename 1K
a /tmp/NETSMARTDataLog_system/nsswitch.conf 1K
a /tmp/NETSMARTDataLog_system/inetd.conf 7K
a /tmp/NETSMARTDataLog_system/uname-a 1K
a /tmp/NETSMARTDataLog_system/ifconfig-a 1K
a /tmp/NETSMARTDataLog_system/netstat-rn 1K
a /tmp/NETSMARTDataLog_system/sysdef 17K
a /tmp/NETSMARTDataLog_system/env.lst 3K
a /tmp/NETSMARTDataLog_system/crontab.lst 1K
a /tmp/NETSMARTDataLog_system/messages 0K
a /tmp/NETSMARTDataLog_system/varadm_nsevents.tar 1K
a /tmp/NETSMARTDataLog_system/pkgparam-v 1K
a /tmp/NETSMARTDataLog_system/pkginfo-i 1K
a /tmp/NETSMARTDataLog_system/showrev-p 47K
End Time : Sun Jun 25 14:55:44 CDT 2006
Archive of log Data created : /tmp/NETSMARTDataLog_system.tar.Z
FNC-1500-0050-110

6-15
CHAPTER 6
Service Support
6.11.2
NETSMART Information
The NETSMART Information option archives NETSMART 1500 debug data to
/tmp/NETSMARTDataLog_netsmart.tar.Z. A screen similar to the following
displays:
Getting NETSMART information
/opt/NetSmart/Properties/ApplicationServer-1/ApplicationServer-1.propertie
s 1K
a /opt/NetSmart/Properties/ApplicationServer-1/DB.properties 1K
a /opt/NetSmart/Properties/BankClient/BankClient.properties 1K
a /opt/NetSmart/Properties/BankClient/Container.properties 1K
a /opt/NetSmart/Properties/BankServer-1/BankServer-1.properties 1K
a /opt/NetSmart/Properties/BankServer-1/Container.properties 1K
:
:
:
a /opt/netsmart5/install/log/dbConfig.log 1K
a /opt/netsmart5/install/log/dbConfig.trace 18K
a /opt/netsmart5/install/log/DBInstall.log 45K
a /opt/netsmart5/install/log/applyOraclePatches.tmp.2531 5K
a /opt/netsmart5/install/log/DBInstall.sh.tmp.685 1K
a /opt/netsmart5/install/log/start_schema.tmp.3041 1K
a /opt/netsmart5/install/log/start_schema.tmp.14790 1K
Generating file : /tmp/NETSMARTDataLog_netsmart.tar
a /tmp/NETSMARTDataLog_netsmart/ 0K
a /tmp/NETSMARTDataLog_netsmart/NETSMART_PROPERTIES.tar 898K
a /tmp/NETSMARTDataLog_netsmart/NETSMART_Trace.tar 15K
a /tmp/NETSMARTDataLog_netsmart/NETSMART_Log.tar 334K
a /tmp/NETSMARTDataLog_netsmart/NSINSTALL_LOG.tar 166K
End Time : Sun Jun 25 14:56:17 CDT 2006
Archive of log Data created : /tmp/NETSMARTDataLog_netsmart.tar.Z
FNC-1500-0050-110
CHAPTER 6
Service Support
6.11.3
ORACLE Information
The ORACLE Information option archives database debug data to /tmp/NSDBlog.tar.Z.
SunOS 5.10
You have new mail.
Generating file : /tmp/NSDBlog.tar
Generic June 2006
Archive of log files created : /opt/nsoracle/remoteadminlogs/NSDBlog

<timestamp: DDMONHHMMSSYY>
6.11.4
All Information
The All Information option performs all of the previous menu options. Debug data is archived
to the following files:
/tmp/NETSMARTDataLog_system.tar.Z
/tmp/NETSMARTDataLog_netsmart.tar.Z
/tmp/NSDBlog.tar.Z
FNC-1500-0050-110

6-17
7
CHAPTERS/APPENDIXES
HIGH AVAILABILITY ADMINISTRATION
1 Introduction
3 NETSMART 1500
Administration
NO.
SECTION
4 UNIX System
Administration
7.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2
7.2
Understanding HA States and Roles . . . . . . . . . . . . . . . . . . . .
7-2
6 Service Support
7.3
Starting NETSMART 1500 HA Services . . . . . . . . . . . . . . . . . .
7-5
7 High Availability
Administration
7.4
Stopping NETSMART 1500 HA Services . . . . . . . . . . . . . . . . .
7-13
7.5
Initiating Manual Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-15
7.6
Understanding Automatic Failover . . . . . . . . . . . . . . . . . . . . .
7-18
7.7
Recovering from a Crash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-21
7.8
Understanding Node Isolation Behavior . . . . . . . . . . . . . . . .
7-23
7.9
Understanding Data Loss Scenarios . . . . . . . . . . . . . . . . . . . .
7-24
7.10
Understanding Client Installation and Behavior . . . . . . . . .
7-26
7.11
Unconfiguring NETSMART 1500 HA Service . . . . . . . . . . . . .
7-27
7.12
HA Quick Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-31
7.13
Hints and FAQs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-34
FNC-1500-0050-110
PAGE

CHAPTER 7
High Availability Administration
Overview
7.1
Overview
This chapter provides procedures for systems configured with NETSMART 1500 high
availability (HA). This chapter assumes that all users are System Administrators experienced
with UNIX who have read and understand FNC-1500-0050-100, Installation Guide,
Section 4.1, Overview [p. 4-2].
The procedures in this chapter use the following host names in the examples:
7.2
haorbison is the primary host.
garcia is the secondary (back-up) host.
hafed is the federation name.
Understanding HA States and Roles

Each subsystem, primary as well as secondary, has an associated state and a designated role.
This section defines possible roles and states. Table 7-1 [p. 7-2] defines HA-related roles.
Table 7-1: Possible Associated Roles
Role
Definition
Active
Intended to be used
Passive
Intended as a passive to an active resource
Table 7-2 [p. 7-2] defines HA-related states.

Table 7-2: Possible Associated States
States
Definition
Up
Resource is working.
InProgress
Resource is in the process of coming up.
Failed
Resource is not working due to failure.
GracefulDown
Resource is not working due to graceful shutdown.
Suspended
Operation of the resource has been temporarily suspended.
FNC-1500-0050-110
CHAPTER 7
Table 7-3 [p. 7-3] defines valid combinations of roles and states for an HA node.
Table 7-3: Possible Combinations of Roles and States
Role/State
Definition
Abbreviation
Active/Up
Resource is intended to be active and working.
a/u
Active/Failed
Resource is intended to be active and has failed.
a/f
Active/GracefulDown
Resource is intended to be active and has been gracefully shut

down.
a/g
Active/Suspended
Resource is intended to be active and has been temporarily

suspended.
a/s
Passive/Up
Resource is intended to be passive and is working.
p/u
Passive/Failed
Resource is intended to be passive and has failed.
p/f
Passive/GracefulDown
Resource is intended to be passive and has been gracefully shut

down.
p/g
Passive/Suspended
Resource is intended to be passive and has been temporarily

suspended.
p/s
FNC-1500-0050-110

7-3
CHAPTER 7
Figure 7-1 [p. 7-4] details all of the transitions that are possible for an HA system.
Installed & Configured state on Primary
Active/Failed
Failure
Active/Suspended (as)
suspend/resume
ActiveGracefulDown (ag)
shutdown
(re)start
error starting up
failure detected
Active/Up (au)
manual
failover
cleanup
Active/Failed (af)
repaired
manual/auto
failover
detects another
active resource
failure detected
repaired
Passive/Up (pu)
(re)start
cleanup
shutdown
Passive/Suspended (ps)
error starting up
Passive/GracefulDown (pg)
Failure
Passive/Failed
Installed & Configured state on Secondary
m1615ao_2
resume/suspend
Passive/Failed (pf)
Figure 7-1: System State Transition Possibilities
FNC-1500-0050-110
CHAPTER 7
Starting NETSMART 1500 HA Services
7.3

This procedure describes how to start the NETSMART 1500 HA services and then check HA
status. It includes the following subprocedures:
NO.
SUBPROCEDURE
PAGE
7.3.1
Starting NETSMART 1500 HA Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-5
7.3.2
Checking NETSMART 1500 HA Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-8
In the examples used in this procedure, the intent is to start services on the primary machine
in the active role and on the secondary machine in the passive role. By default, primary is
configured to come up in the active role and secondary in the passive role. These roles can be
changed while starting the servers.
In the examples used in this procedure, host names haorbison and garcia were installed
with all optional packages, but none of the optional packages were enabled. Also, this example
federation supports both IP and OSI.
7.3.1

NETSMART 1500 services can be started from either of the nodes. The examples used in this
procedure show starting up services from the primary host.
Follow this procedure to start NETSMART 1500 HA services:
Step
Task
Log on haorbison as user netsmart.
At the command prompt, enter netsmart start.
FNC-1500-0050-110

7-5
CHAPTER 7

Note: The list of options presented is based on what was discovered by the HA software.
Starting NETSMART 1500 Servers.
Using OpenORB 1.3.1
(1): Cluster startup
(2): Single node startup
Enter 1 Cluster startup from the screen display options.
FNC-1500-0050-110
CHAPTER 7

haorbison.nms.fnc.fujitsu.com: Starting HANS (Sat Dec 16 11:39:09 PST 2006)
haorbison.nms.fnc.fujitsu.com: Starting NETSMART Database (Sat Dec 16
11:40:07 PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching Heartbeat to Active (Sat Dec 16
11:40:15 PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching Database to Active (Sat Dec 16
11:40:16 PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching Netsmart services to Active (Sat
Dec 16 11:40:17 PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching DCN to Active (Sat Dec 16 11:40:17
PST 2006)
garcia.nms.fnc.fujitsu.com: Starting HANS (Sat Dec 16 11:40:18 PST 2006)
ORBAdaptor: setting fedhost to haorbison.nms.fnc.fujitsu.com
garcia.nms.fnc.fujitsu.com: Starting NETSMART Database (Sat Dec 16 11:41:18
PST 2006)
garcia.nms.fnc.fujitsu.com: Switching Heartbeat to Passive (Sat Dec 16
11:41:26 PST 2006)
garcia.nms.fnc.fujitsu.com: Switching Database to Passive (Sat Dec 16
11:41:26 PST 2006)
garcia.nms.fnc.fujitsu.com: Switching Netsmart services to Passive (Sat Dec
16 11:41:27 PST 2006)
garcia.nms.fnc.fujitsu.com: Switching DCN to Passive (Sat Dec 16 11:41:27
PST 2006)
======================================================================
NETSMART 1500 Federation haorbison
Primary: haorbison.nms.fnc.fujitsu.com: Active
Backup: garcia.nms.fnc.fujitsu.com: Passive
======================================================================
(1): Switch active/passive machines
(2): Configuration is okay, continue with startup
Enter 2 Configuration is okay, continue with startup from the screen

display options.
FNC-1500-0050-110

7-7
CHAPTER 7
The system checks the current status and displays:

Starting HANS (Sat Dec 16 11:55:56 PST 2006)
haorbison.nms.fnc.fujitsu.com: Starting NETSMART Database (Sat Dec 16
11:55:56 PST 2006)
garcia.nms.fnc.fujitsu.com: Starting NETSMART Database (Sat Dec 16 11:55:56
PST 2006)
Starting federation haorbison (Sat Dec 16 11:56:06 PST 2006)
haorbison.nms.fnc.fujitsu.com: Starting HA heartbeat links (Sat Dec 16
11:56:07 PST 2006)
garcia.nms.fnc.fujitsu.com: Starting HA heartbeat links (Sat Dec 16
11:56:16 PST 2006)
haorbison.nms.fnc.fujitsu.com: Starting database replication (Sat Dec 16
11:56:16 PST 2006)
garcia.nms.fnc.fujitsu.com: Starting database replication (Sat Dec 16
11:57:41 PST 2006)
haorbison.nms.fnc.fujitsu.com: Starting NETSMART services (Sat Dec 16
11:59:07 PST 2006)
garcia.nms.fnc.fujitsu.com: Starting NETSMART services (Sat Dec 16 12:00:55
PST 2006)
======================================================================
Services may take about 1530 minutes to start before presenting the following status:
======================================================================
haorbison.nms.fnc.fujitsu.com%
NETSMART 1500 HA services are now activated and are up and running on both
haorbison and garcia. A client can connect to the hafed federation and invoke any of
the NETSMART 1500 features. In the above example, node garcia would take over the
functionality of haorbison in case of failure. Note that the NETSMART 1500 Heartbeat
state shows as Passive/Up. HA software has successfully connected itself with the services on
haorbison.
7.3.2
Checking NETSMART 1500 HA Status

This procedure describes how to check HA status.
FNC-1500-0050-110
CHAPTER 7
Check the status of NETSMART 1500 HA as follows:

Step
Task
Log on haorbison as user netsmart.
At the command prompt, enter netsmart status.

haorbison.nms.fnc.fujitsu.com% netsmart status
======================================================================
======================================================================
-- Summary ----------------------------------------------------------Federation: allfed
Configuration: HA (Dual node)
Version: 5.0.0
License: 5 users, 25 NEs, HA, PM
FNC-1500-0050-110

7-9
CHAPTER 7
-- Server status ----------------------------------------------------......................................................................

Hostname
Type
Role
State
Clients
......................................................................
allman.nms.fnc.fujitsu.com
Primary
Active
Up
0
firefly.nms.fnc.fujitsu.com
Backup
Passive
Up
0
......................................................................
======================================================================
Usage:
"netsmart status" - NETSMART summary status
"netsmart status ha" - High Availability status
"netsmart status list" - NETSMART servers list
"netsmart status all" - All of the above
allman.nms.fnc.fujitsu.com% netsmart status all
======================================================================
======================================================================
-- Summary ----------------------------------------------------------Federation: allfed
Configuration: HA (Dual node)
Version: 5.0.0
License: 5 users, 25 NEs, HA, PM
FNC-1500-0050-110
CHAPTER 7
-- Server status ----------------------------------------------------......................................................................

Hostname
Type
Role
State Clients
......................................................................
Primary
Active
Up
0
Backup
Passive
Up
0
......................................................................
======================================================================
======================================================================
NETSMART 1500 High Availability Status
======================================================================
-- HA Resource status -----------------------------------------------......................................................................
Resource
(Primary)
(Backup)
Role
State
Role
State
......................................................................
NETSMART
Active
Up
Passive
Up
Heartbeat
Active
Up
Passive
Up
Servers
Active
Up
Passive
Up
Database
Active
Up
Passive
Up
Replication
Active
Up
Passive
Up
-- HA communication links -------------------------------------------......................................................................
Type
From
To
Status
Throughput Latency
Queue
(Bytes/sec) (ms)
(bytes)
.......................................................................
Heartbeat
Primary
Backup
Up
47.25
Heartbeat
Primary
Backup
Up
47.25
Heartbeat
Backup
Primary
Up
48.0
Heartbeat
Backup
Primary
Up
69.625
Replication Primary
Backup
Up
-1.0
-1.0
null
Replication Backup
Primary
Up
-1.0
-1.0
null
-NETSMART services ------------------------------------------------screen display continues on next page
FNC-1500-0050-110

7-11
CHAPTER 7
Current active host: allman.nms.fnc.fujitsu.com

......................................................................
Server name
Status
Date
......................................................................
FTAMResponder
Security
TopologyServer
DataServicesManager
SwmgrServer
OSIstack
ObjLicMgr
CommunicationServer-1
ApplicationServer-2
ApplicationServer-3
TL1UplinkServer
NSWebService
SessionManager
ConnectionManager
ApplicationServer-1
SNMPServer
Framework
ApplicationServer-4
Usage:
"netsmart
"netsmart
"netsmart
"netsmart
status"
status ha"
status list"
status all"
Down
Up
Up
Up
Up
Down
Up
Up
Up
Up
Up
Up
Down
Down
Up
Up
Up
Down
Up
Up
Up
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Sun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
Jun
10:29:16
10:38:50
10:38:50
10:38:51
10:38:50
10:29:16
10:38:54
10:38:49
10:38:49
10:38:50
10:38:49
10:38:51
10:29:16
10:29:16
10:38:49
10:38:51
10:38:50
10:29:16
10:38:49
10:38:51
10:38:51
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
2006
NETSMART summary status

High Availability status
NETSMART servers list
All of the above
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
FNC-1500-0050-110
CHAPTER 7
Stopping NETSMART 1500 HA Services
7.4

NO.
SUBPROCEDURE
PAGE
7.4.1
Stopping HA Services on Active and Passive Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-13
7.4.2
Stopping HA Services on Passive Only Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-14
NETSMART 1500 HA services can be brought down as a cluster from both primary and
back-up systems. Optionally, the system can be brought down on passive-only systems.
7.4.1
Stopping HA Services on Active and Passive Systems

Doing this procedure stops all NETSMART 1500 HA services on both active and passive
systems.
Stop HA services on active and passive systems as follows:
Step
Task
Log on as user netsmart to either garcia or haorbison.
At the command prompt, enter netsmart stopall.

Using OpenORB 1.3.1
(1): Cluster shutdown
(2): Passive node shutdown only (switch to single-node mode)
Note: This command takes about 1015 minutes to complete.
Enter 1 Cluster shutdown from the screen display options.

All NETSMART 1500 HA services on both active and passive systems stop.
FNC-1500-0050-110

7-13
CHAPTER 7
7.4.2
Stopping HA Services on Passive Only Systems

Doing this procedure stops all NETSMART 1500 HA services on passive-only systems.
Stop HA services on passive systems as follows:
Step
Task
Log on as user netsmart on to haorbison.
At the command prompt, enter netsmart stopall.

Using OpenORB 1.3.1
(1): Cluster shutdown
(2): Passive node shutdown only (switch to single-node mode)
Note: This command takes about 10-15 minutes to complete
Enter 2 Passive node shutdown only (switch to single-node mode)

from the screen display options.
All NETSMART 1500 HA services on passive systems stop.
FNC-1500-0050-110
CHAPTER 7
Initiating Manual Failover
7.5

NETSMART 1500 HA product supports a manual failover feature where the passive system
takes over the role of the active system. The failover time varies but is most often about 30
minutes.
Failover time is defined as the interval between the time the passive system detects the active
system failure and the time the passive system is connected and logged on (in a best-effort
manner) to the same number of NEs that the active system was logged on at the time of the
last snapshot before the active failure.
The failover is logged as a System Event. After the passive systems servers are all up as is
expected after a NETSMART start, clients are notified and can start using the new active
system.
To initiate a manual failover, the following conditions must be true:
One of the nodes (Primary or Secondary) should be in Active-Up state
The other node should be in Passive-Up state.
The manual failover request continues only if these conditions are met.
In the examples used in this procedure, haorbison is assumed to be in Active-Up state, and
garcia is assumed to be in Passive-Up state.
Initiate manual failover as follows:
Step
1
Task
Log on as user netsmart to the node that is currently in Active-Up state

OR
Log on as user netsmart to the node that is currently in Passive-Up state and then execute
the failover command.
At the command prompt, enter netsmart failover.
FNC-1500-0050-110

7-15
CHAPTER 7

Warning: Running netsmart failover is a time consuming operation.
Warning: There will be some downtime of NETSMART 1500 services.
Warning: Downtime may vary depending on amount of data (30 minutes - 2
hours)
Are you sure you wish to continue ? [y/n] [y/n] (default=n) y
Enter password for [netsmart]:
Enter netsmart password
Press ENTER to confirm that you want to continue.
Enter the netsmart password.

authenticating.....
Authenticated user netsmart
Performing Netsmart failover
Using OpenORB 1.3.1
ORBAdaptor: setting fedhost to garcia.nms.fnc.fujitsu.com
Checking current federation status (Thu Dec 21 11:43:44 PST 2006)
haorbison.nms.fnc.fujitsu.com: Stopping HA heartbeat links (Thu Dec 21
11:43:45 PST 2006)
garcia.nms.fnc.fujitsu.com: Stopping HA heartbeat links (Thu Dec 21
11:43:46 PST 2006)
garcia.nms.fnc.fujitsu.com: Stopping NETSMART services (Thu Dec 21 11:43:47
PST 2006)
garcia.nms.fnc.fujitsu.com: Switching Netsmart services to Passive (Thu Dec
21 11:44:51 PST 2006)
garcia.nms.fnc.fujitsu.com: Switching Database Replication to Passive (Thu
Dec 21 11:44:52 PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching Database Replication to Active
(Thu Dec 21 11:47:21 PST 2006)
garcia.nms.fnc.fujitsu.com: Switching Heartbeat to Passive (Thu Dec 21
11:50:08 PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching Heartbeat to Active (Thu Dec 21
11:50:09 PST 2006)
garcia.nms.fnc.fujitsu.com: Switching Database to Passive (Thu Dec 21
11:50:10 PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching Database to Active (Thu Dec 21
11:50:11 PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching DCN to Active (Thu Dec 21 11:50:18
PST 2006)
FNC-1500-0050-110
CHAPTER 7
Restarting NETSMART services on new passive in the background .. (Thu Dec 21

11:50:18 PST 2006)
garcia.nms.fnc.fujitsu.com: Starting NETSMART services (Thu Dec 21 11:50:18
PST 2006)
haorbison.nms.fnc.fujitsu.com: Switching Netsmart services to Active (Thu
Dec 21 11:50:19 PST 2006)
Restarting NETSMART services on new passive in the background .. done (Thu
Dec 21 11:51:35 PST 2006)
garcia.nms.fnc.fujitsu.com: Switching DCN to Passive (Thu Dec 21 11:52:37
PST 2006)
haorbison.nms.fnc.fujitsu.com: Starting HA heartbeat links (Thu Dec 21
11:52:38 PST 2006)
garcia.nms.fnc.fujitsu.com: Starting HA heartbeat links (Thu Dec 21
11:52:47 PST 2006)
======================================================================
======================================================================
In the above example, haorbison reports Passive-Up state, and garcia reports Active-Up
state.
5
Optionally, check the status of NETSMART 1500 HA services on both nodes. Refer to
Section 7.3.2, Checking NETSMART 1500 HA Status [p. 7-8], for more information.
During a manual failover, clients are notified of the failover in progress. After the passive
system is in a state to allow clients to connect, it sends a message to the clients, and the clients
can then failover to the new active system. During failover, clients are not allowed to do any
operations other than getting progress information of the failover. Refer to Section 7.10,
Understanding Client Installation and Behavior [p. 7-26], for more information.
FNC-1500-0050-110

7-17
CHAPTER 7
Understanding Automatic Failover
7.6

When the passive system detects a heartbeat loss to the active system, the passive system takes
over the role of the active system. To avoid this undesirable effect, the passive system polls
NETSMART 1500 clients to find out their connectivity to the active system. If more than 50
percent of the visible clients report that they are unable to see the active system, the passive
system takes over as shown in Figure 7-2 [p. 7-18]. Otherwise, the passive system assumes that
the loss of heartbeat is due to a failure in the interconnect network and takes no action as
illustrated in Figure 7-3 [p. 7-19].
Note: The passive system takes no action if it detects that no NETSMART 1500 clients are
connected or logged on or that the network interconnect to the NETSMART 1500 clients is lost.
In both cases, the NETSMART 1500 HA service sends an e-mail to the administrator.
Autofailover is set to 10 minutes for a heartbeat lossthis helps to prevent spurious failovers.
NETSMART 1500
Clients
NETSMART CORBA
Traffic
Primary
Backup
Heartbeat Links (2)

Data Replication Link
Active
Passive
DCN
DCN
NEs
m1615ar_1
In use
Standby
Failed
Figure 7-2: Heartbeat Failure Causing Failover
FNC-1500-0050-110
CHAPTER 7
NETSMART 1500
Clients
NETSMART CORBA
Traffic
Primary
Backup
Heartbeat Links (2)

Data Replication Link
Passive
Active
DCN
DCN
NEs
m1615as_1
In use
Standby
Failed
Figure 7-3: Network Isolation of PassiveNo Failover
Failover time varies but is generally about 30 minutes. Failover time is defined as the interval
between the time the passive system detects the active system failure and the time the passive
system is connected and logged on (in a best-effort manner) to the same number of NEs that
the active system was logged on during the last snapshot before the active failure. The event
and best-effort cause of the failover is logged as a System Event. In addition, an e-mail is sent
to the administrator.
After the passive system is functional, connected clients are notified and start using the new
active system. The clients cannot autonomously decide to switch to another machine.
FNC-1500-0050-110

7-19
CHAPTER 7
Failover is non-revertive. After a passive system has become the new active system, a user or
administrator must actively initiate the process of reverting back to the repaired active system.
After a failover, no monitoring of the failed active system is done. The system goes into
Single-Node NETSMART 1500 mode.
When the failed active system is repaired and NETSMART 1500 HA services are restarted,
the system comes up as a passive system. A manual failover can then be initiated for reverting
back.
During an automatic failover, clients are notified of the failover in progress. After the passive
system is in a state to allow clients to connect, it sends a message to the clients, and the clients
can then failover to the new active system. During failover, clients may not be allowed to do
any operations other than getting progress information of the failover. Refer to Section 7.10,
Understanding Client Installation and Behavior [p. 7-26], for more details.
During a passive system failure or crash, the active system detects the failure, logs a System
Event, and sends an e-mail to the administrator. All transactions that are executed on the
active system begin queueing up after the passive system is down. Every 10 percent increment
in queue size results in an e-mail being sent to the administrator. If the queue becomes full,
queueing is disabled, and the passive system must be re-added to the active system to be
functional again. The queue can usually accommodate 24 hours worth of NETSMART 1500
activity. The passive system, after being repaired, can be restarted by executing the
netsmart start command. Refer to Section 7.3, Starting NETSMART 1500 HA
Services [p. 7-5], for more information.
FNC-1500-0050-110
CHAPTER 7
Recovering from a Crash
7.7

This section describes how to recover from a crash. A system is considered crashed when the
termination of NETSMART 1500 HA services was not graceful. Crash scenarios can be as
follows:
The system was powered off, or there was a power failure.
The system had a hardware problem, such as a CPU failure.
The site where the system resides was destroyed.
NETSMART 1500 HA services where terminated ungracefully (for example, by

executing netsmart clean command).
A system is determined to be in a failed state when an attempt to start the services is not
successful (for example, if the netsmart start command terminates without completing
properly). In such cases, when a reattempt is made to start services, NETSMART 1500 HA
service detects and does recovery before proceeding to the normal startup procedure.
The recovery process puts the node in gracefuldown (gd) state of the last known role
(passive or active). For example, a node that is in a passive-failed state would be put into
passive-gracefuldown state.
In the examples used in this procedure, the assumption is that haorbison was in active-up
state before it crashed. The system then repairs and restarts haorbison and tries to restart
NETSMART 1500 HA services. The peer system (garcia) was also down, and, after
recovery, a try is made to bring this system back up in the active-up state.
For using a database recovery on an HA system using the database backup, refer to
Section 2.7.4, Restoring Backup of HA on an HA System [p. 2-35].
Follow this procedure to recover from a crash:
Step
1
Task
At the command prompt, enter netsmart start.

(1): Cluster startup
(2): Single node startup
Enter 1 Cluster startup from the screen display options.
FNC-1500-0050-110

7-21
CHAPTER 7

haorbison.nms.fnc.fujitsu.com: Starting HANS (Sun Jun 25 15:58:53 PDT 2006)
haorbison.nms.fnc.fujitsu.com: Starting NETSMART Database (Sun Jun 25
16:00:58 PDT 2006)
POA created: ha-transient
Reconciling roles (Sun Jun 25 16:07:39 PDT 2006)
haorbison.nms.fnc.fujitsu.com: Switching Heartbeat to Passive (Sun Jun 25
16:07:39 PDT 2006)
haorbison.nms.fnc.fujitsu.com: Switching Database to Passive (Sun Jun 25
16:07:41 PDT 2006)
haorbison.nms.fnc.fujitsu.com: Switching Netsmart services to Passive (Sun
Jun 25 16:07:45 PDT 2006)garcia.nms.fnc.fujitsu.com: Starting NETSMART
Database (Sun Jun 25 16:07:48 PDT 2006)
======================================================================
NETSMART 1500 Federation federation1
Primary: haorbison.nms.fnc.fujitsu.com: Passive
Backup: garcia.nms.fnc.fujitsu.com: Active
======================================================================
(1): Switch active/passive machines
(2): Configuration is okay, continue with startup
2
Enter 2 Configuration is okay, continue with startup from the screen

display options.
Recovery can be done on both systems. NETSMART 1500 HA services detect the state of the
whole HA system and provide appropriate options for restarting the HA services.
Note: An automatic check for whether recovery is needed or not is done every time an attempt
is made to start NETSMART 1500 HA services.
FNC-1500-0050-110
CHAPTER 7
Understanding Node Isolation Behavior
7.8
Understanding Node Isolation Behavior

This section describes the behavior of system isolation. A system is considered isolated when
the network interconnects connecting the node to the rest of the system (clients, peer node
heartbeat interconnect) fail. Table 7-4 [p. 7-23] shows the active node as isolated. The
behavior of NETSMART 1500 HA services is based on the current state and role of the
system.
Table 7-4 [p. 7-23] describes system state before isolation and its behavior.
Table 7-4: System Isolation Behavior
State Before Isolation
Behavior
Active
ActiveActive system detects that it lost connectivity to the passive system

and the clients. The data replication engine (DRE) continues to queue up the
data (for 24 hours before failure), and the system still remains in active-up
state with Heartbeat in the active-failed state.
PassivePassive system detects that it lost connectivity to the active system
and thus starts automatic failover only if a configurable percentagea of clients
vote that they cannot see the active system. NETSMART 1500 HA services
go into active-up state on this system with Heartbeat in an active-down state.
RepairAs soon as the isolated active systems network interconnects are
repaired, it detects that the other system has taken over as active and thus goes
into a passive-failed state. Recovery is needed to repair the passive system to
get it back into an up state so that it can take over if the active system
subsequently fails. To re-initiate the NETSMART 1500 HA services, follow
the recovery procedure in Section 7.7, Recovering from a Crash [p. 7-21].
Passive
PassivePassive system detects that it lost connectivity to the active system

and the clients. The system goes into the passive-failed state.
ActiveActive system detects that it lost connectivity and puts the Heartbeat
and DRE in failed state. DRE continues to queue up for 24 hours before
aborting the queuing. The 24-hour queue is based on NETSMART
performance benchmarking numbers.
RepairTo re-initiate the NETSMART 1500 HA services, follow the
recovery procedure Section 7.7, Recovering from a Crash [p. 7-21].
This parameter is defined in the HA properties file but is not visible as a configurable parameter in the
configuration process. The default value is 50 percent.
FNC-1500-0050-110

7-23
CHAPTER 7
Understanding Data Loss Scenarios
7.9

NO.
SUBPROCEDURE
PAGE
7.9.1
Data Loss Due to Multiple Resource Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-24
7.9.2
Data Loss when Active System Is Isolated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-25
NETSMART 1500 HA services make every attempt to minimize data loss, but there are some
scenarios where data loss can occur. This section documents data loss scenarios.
7.9.1
Data Loss Due to Multiple Resource Failure

Data loss due to multiple resource failure is a scenario where NETSMART 1500 HA services
would be unable to recover a certain time periods worth of data. The scenario in Figure 7-4
[p. 7-24] illustrates that the data replication link interconnect failed first, resulting in
NETSMART 1500 HA services queueing up data packets on the active-system side.
Note: NETSMART 1500 HA services are configured to queue 24 hours of data.
Heartbeat
Passive
m1615an_1
DRE
Active
Figure 7-4: Multiple Resource Failure Scenario
After a certain time (for example, an hour), the active system crashes, resulting in an
automatic failover to the passive system. Because the data replication engine (DRE) link was
down, the passive side NETSMART 1500 HA services are activated in active mode with one
hour of old data. When the failed active system is repaired and recovered, the data in the
queues is dropped, and the node database is resynced with the surviving active system, thus
resulting in data loss.
Note: Before initiating recovery, NETSMART 1500 database backup can be initiated from the
Heartbeat tool. This backup ensures that any log information or faults are not lost.
FNC-1500-0050-110
CHAPTER 7
7.9.2
Data Loss when Active System Is Isolated

ITEM
PAGE
Data Loss after Switching Roles with DRE Link Down . . . . . . . . . . . . . . . . . . . . . . . . .
7-25
Data Loss after Database Crash on Active Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-25
Data loss can occur if the active system is isolated, failover occurs, and the old active node
continues to operate as active. When communication between the servers is reestablished, the
old active system goes into a passive-failed state, but the data that was accumulated on the
active server is not resynced during recovery. If the data must be saved, NETSMART 1500
database backup can be initiated from Heartbeat. This backup ensures that any log
information or faults are not lost.
Data Loss after Switching Roles with DRE Link Down

If the DRE link is down while stopping NETSMART 1500 servers, some data on the active
system might not be replicated to the passive system. If you select a different active system at
the subsequent startup, the data that was queued on the active system might be lost. To
recover the data, NETSMART 1500 database backup can be initiated from Heartbeat. This
backup ensures that any log information or faults are not lost.
Data Loss after Database Crash on Active Server

If the database crashes on the active system (for example, due to storage failure), and the
passive system is subsequently switched to become the active system, data that was on the old
active system but had not yet been replicated to the passive system is lost. To recover the data,
NETSMART 1500 database backup can be initiated from Heartbeat. This backup ensures
that any log information or faults are not lost.
FNC-1500-0050-110

7-25
CHAPTER 7
Understanding Client Installation and Behavior
7.10
Understanding Client Installation and Behavior

NETSMART 1500 HA client installation asks whether or not the federation being installed is
HA. If yes is selected, it prompts for the secondary server address, and the remaining
installation is a normal NETSMART 1500 client installation.
The NETSMART 1500 HA client behaves exactly like a single-node client when active HA
services are available. Apart from regular behavior, the NETSMART 1500 HA client provides
the following features:
When starting a NETSMART 1500 HA client, NETSMART automatically detects

the active system and connects to it.
During a manual or automatic failover, a failover progress dialog opens, freezes all other
application windows, and displays the progress of the failover. When the failover is
complete, all open application windows are closed and reopened automatically. This
action ensures that new connections are established to the new active system.
The NETSMART 1500 HA client adds a new application called HA Status Monitor,
which can be invoked from the Applications > Administration menu of any application
window. The HA Status Monitor displays the current status of the HA subsystem and
has a console that displays real time streaming of HA messages.
Dashboard displays the federation name and role of both the primary and back-up node in
the federation status panel. The federation name displays above the icons for each node. The
larger icon represents the active node, and the smaller icon represents the passive node. Colors
of the Dashboard node monitor icon represent the state of the primary and backup node as
defined in Table 7-5 [p. 7-26].
Table 7-5: Color Conventions for Dashboard Node Icons
Color
State
Green
Up
Red
Down
Yellow
In progress
Gray
Unknown
Run your mouse pointer over the federation icon for a ToolTip that displays the role of the
node and the state of the node.
FNC-1500-0050-110
CHAPTER 7
Unconfiguring NETSMART 1500 HA Service
7.11

HA software is not removed; it is deactivated. Although you can do unconfiguration on any
node, running this procedure on the passive system first and then on the active system (if
possible) is recommended. The unconfiguration tool unconfigures only the node on which it
is executed. You must run the tool separately on both nodes to unconfigure completely.
Unconfigure NETSMART 1500 HA service by following this procedure.
Step
Task
Log on as user netsmart.
Shut down the system by entering the following command at the command prompt:
netsmart stopall
Refer to Section 7.4, Stopping NETSMART 1500 HA Services [p. 7-13].

Note: This command takes about 1015 minutes to complete.
At the command prompt, start the Heartbeat tool by typing heartbeat.

The following screen displays:
M A I N
M E N U
1. NETSMART 1500 Administration

2. Oracle Administration*
3. UNIX System Administration
4. Network Administration
5. Service Support
q. Quit
Enter 1 NETSMART 1500 Administration from the screen display options.
FNC-1500-0050-110

7-27
CHAPTER 7

N E T S M A R T 1500 A D M I N I S T R A T I O N
12. Resync NE Data
20. LNE Discovery
q. Quit
Enter e Enable Root Access.
FNC-1500-0050-110
CHAPTER 7

*** Enabling Root Access ***
Enter ROOT Password: Enter root accounts passwd here
N E T S M A R T 1500

12. Resync NE Data
20. LNE Discovery
q. Quit
Enter 13 NETSMART 1500 HA UnConfiguration.
FNC-1500-0050-110

7-29
CHAPTER 7

UNCONFIGURING NETSMART 1500 HA for hafed
***
*** NETSMART 1500 HA UnConfigure confirmation.
***
Do you really want to unconfigure HA on this host (Y) [?] Y
Removing HA Configuration from this node
***
*** Logging
***
Log sent to /opt/netsmart2.2/install/log/unconfigureHA.log
***
*** Updating HANS on Primary and Backup.
***
Unconfigured HANS on this node..
***
*** Removing DRE configuration on this node...
***
Sun Microsystems Inc.SunOS 5.8Generic Patch June 2006
You have new mail.
Deactivating DRE on this site : Sun Jun 25 13:57:50 PDT 2006
Removing crontab entries for DRE : Sun Jun 25 13:57:50 PDT 2006
Removing DRE transaction errors : Sun Jun 25 13:57:51 PDT 2006
Removing Pending DRE transactions : Sun Jun 25 13:57:51 PDT 2006
Removing DRE replication groups : Sun Jun 25 13:57:53 PDT 2006
Removing DRE jobs : Sun Jun 25 13:58:22 PDT 2006
Removing DRE conflict reporting mechanism : Sun Jun 25 13:58:22 PDT 2006
Removing DRE account : Sun Jun 25 13:58:24 PDT 2006
Stopping DRE listener : Sun Jun 25 13:58:38 PDT 2006
Sun Microsystems Inc.SunOS 5.8Generic Patch June 2006
You have new mail.
Unconfigured DRE on this node.
Hit enter to continue
Enter q Quit.
FNC-1500-0050-110
CHAPTER 7
HA Quick Commands
7.12
HA Quick Commands
This section describes some quick commands that can be used. It includes the following
subsections:
7.12.1
NO.
SUBSECTION
PAGE
7.12.1
Cluster Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-31
7.12.2
Start in Single-Node Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-31
7.12.3
Shutdown Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-32
7.12.4
Enable Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-32
7.12.5
Disable Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-32
7.12.6
Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-33
7.12.7
Recovering Crashed Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-33
Cluster Startup
Start a cluster as follows:
Step
Task
Use the command netsmart start for this operation.
Enter 1 for Cluster startup.

The system provides information on current roles, allowing you to change roles or start the
system with the current role.
7.12.2
Start in Single-Node Mode

Start up in single-node mode as follows:
Step
1
Task
FNC-1500-0050-110

7-31
CHAPTER 7
HA Quick Commands
Enter 2 for single-node startup.
Select the node you want to start.

No services are launched on the other node.
7.12.3
Shutdown Cluster
Shut down a cluster as follows:
Step
Task
Use the command netsmart stopall for this operation.
Enter 1 for cluster shutdown.

If DRE is out of sync, a warning displays on the screen, and shutdown continues. Resync is
done automatically when the cluster is started.
7.12.4
Enable Failover
Go from single-node mode to cluster mode as follows:
Step
Task
Enter 1 for cluster startup.

DRE resync is done if needed. If active is already master, servers are not brought down
(runtime node addition).
7.12.5
Disable Failover
Shut down passive node only as follows:
Step
Task
Use the command netsmart stopall for this operation.
Enter 2 for passive node shutdown only.

If DRE is out of sync, a warning message displays on screen.
FNC-1500-0050-110
CHAPTER 7
HA Quick Commands
7.12.6
Failover
Use the command netsmart failover for this operation. No input is required.
7.12.7
Recovering Crashed Node

Recover a crashed node as follows:
Step
Task
Enter 1 for cluster startup.

The system provides information on current roles.
Enter 2 to start up the cluster.

If required, DRE resync is done.
FNC-1500-0050-110

7-33
CHAPTER 7
Hints and FAQs
7.13
Hints and FAQs

7.13.1
NO.
SUBSECTION
PAGE
7.13.1
Hints for Working with HA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-34
7.13.2
Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-35
Hints for Working with HA

Consider the following hints when working with HA:
Before configuring NETSMART 1500 HA for a federation that manages a large set of
NEs, populate the NETSMART 1500 database first with NEs, and then initiate HA
configuration. If you populate the data after HA is configured, the passive receives this
data through the relatively slower replication process. If you populate the data first, the
configuration does an export/import of the data to the backup, which is relatively faster
because it is a bulk operation.
Set up e-mail systems in such a way that e-mails are received by the administrator from
both the primary and back-up systems. Ideally, NETSMART 1500 and Oracle account
e-mails should be forwarded from both the primary and secondary systems to the
administrator.
Always create a database backup on a node before recovering the node.
If possible, avoid HA configuration or DRE resync operations during database

end-of-day backups (normally scheduled at midnight).
Because NETSMART 1500 HA does not replicate the Solaris user IDs and passwords,
administrators are advised either to use a non-file-based authentication mechanism
(such as common LDAP, NIS, and NIS+) or to create user IDs on both the HA nodes
with the same password.
FNC-1500-0050-110
CHAPTER 7
Hints and FAQs
7.13.2
Frequently Asked Questions

How did you arrive at the 24-hour queuing figure for DRE, and what happens when the queue
gets filled?
The 24-hour figure is a requirement of a reasonable queue size. The queue is sized to be able
to accommodate 24 hours of NETSMART 1500 usage, based on NETSMART 1500 capacity
and performance benchmarks. The idea is that it would be reasonable to expect a failed
passive to be repaired within 24 hours, failing which, the active stops queueing data for the
passive node. The 24 hours is the guaranteed time of queueing supported.
If the system is not used to capacity or is used lightly, the active node can continue to queue
data for the passive for more than 24 hours. After the queue is filled, the active node removes
the passive node. This action means that the active node no longer queues transactions for the
passive node. To restore the passive node, a full refresh of the passive node database is
necessary. This process can take anywhere from 45 minutes to 2 hours, depending on the
amount of data. This process occurs as part of the netsmart start command on a
repaired passive node.
How do I check the size of the DRE queue?
The size of the queue is displayed whenever the netsmart status all command is
executed on an HA system.
What happens after the recovery? Should I check anything else? What about clients?
After the recovery, the netsmart status command indicates that the two nodes are
operational. Clients do not need to be checked; they should already be using the newly active
machine.
Can I change the host name or federation name of the server after installing the HA component?
No. The restriction is a NETSMART 1500 limitation for an HA system.
How do I test the functionality, such as Heartbeat and DRE links, other than by doing a manual
failover?
Seeing Heartbeat or DRE link status as Active-Up and Passive-Up, respectively, on the two
nodes is the test. The HA software periodically tests the links.
How do I verify that the passive node is actually being updated?
If the Passive DRE, as shown in netsmart status, is in Passive-Up state, the passive node is
being updated. You do not need to run more tests because everything is automated.
FNC-1500-0050-110

7-35
A
CHAPTERS/APPENDIXES
SERVER AND CLIENT PORT USAGE
1 Introduction
This appendix includes the following sections:
3 NETSMART 1500
Administration
NO.
SECTION
4 UNIX System
Administration
A.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-2
A.2
Server Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-2
6 Service Support
A.3
Client Port Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-3
PAGE
7 High Availability
Administration
FNC-1500-0050-110

APPENDIX A
Server and Client Port Usage
Overview
A.1
Overview
This appendix lists the ports used in NETSMART 1500 client and server systems.
A.2
Server Port Usage

Table A-1 [p. A-2] describes TCP port usage for NETSMART 1500 servers. These ports
should be accessible to all NETSMART 1500 clients.
Note: SNMP uplink listens on UDP port 162. If required, this can be modified with the following
properties file: $NETSMART_PROP_HOME_/Properties/SNMPUplinkServer/
SNMPUplinkServer.properties.
Note: If other SNMP agents, such as a Sun agent, are running on this system, SNMPUplink can
be reconfigured by editing the same properties file mentioned above.
Table A-1: Server Port Usage (1 of 2)
Server
Ports
Containermanagement
120002049
fenicsd
1205012099
Oracle
1521
httpd
7600
COSServer
1210012199
PM-ES
1220012249
Framework
1225012299
Security
1230012349
TARPServer
1235012399
13000(13000+NumOfCommunicationServers*50)
SessionManager
1240012449
ApplicationServer
15000(15000+NumOfApplicationServers*50)
EmlNmlServer
1260012649
TL1UplinkServer
1265012699
1270012749
A-2 Server Administration Guide
FNC-1500-0050-110
APPENDIX A
Server and Client Port Usage
Client Port Usage
Table A-1: Server Port Usage (2 of 2)

Server
Ports
DataServicesManager
1275012799
ConnectionManager
1280012849
SNMP Uplinka b
1600016050
SNMPServer
1290012949
ReportServer
1700017050
a SNMP
b
A.3
uplink listens on UDP port 162. If required, modifiy this with the following properties file:
$NETSMART_PROP_HOME_/Properties/SNMPUplinkServer
/SNMPUplinkServer.properties
If other SNMP agents, such as Sun, are running on this system, SNMPUplink can be reconfigured by editing the
same properties file in footnote a.
Client Port Usage

The NETSMART 1500 client does not use any predefined port numbers.
FNC-1500-0050-110

A-3
Index
A
sending
from command line 3-46
from Web administration page 3-48
viewing 3-48
alert scripts
alert files
checking size 2-38
deleting 2-48
alert monitor, running 2-37
archived redo log files
missing, checking for 2-41
size, checking 2-40
file systems, checking size 2-39
notifying Oracle user 2-37
C
CDE (common desktop environment)
controls, adding to NETSMART 1500 client
accounts 4-8
client
recovering from errors 3-13
shutting down 3-11
starting
on server 3-9
troubleshooting 3-12
archive file, creating 6-6

archived redo log files
deleting 2-49
missing, checking for 2-41
size, checking 2-40
communication
server, NE logon. See NE log-on configuration.
configurations
SONET-SDH terminology mapping 3-88
backup
automated maintenance 2-43
full system 4-27
NETSMART 1500 application 4-28
performing 2-25
preventing erasure 2-34
recovering from 2-30
recovery from
HA on HA system 2-35
HA on non-HA system 2-35
Oracle database 2-29
startup by ending 2-22
UNIX system 4-27, 4-30
broadcast messages
FNC-1500-0050-110
control files, database 2-65
D
database
administration. See Heartbeat tool.
alert scripts. See alert scripts.
automated maintenance jobs, listed 2-44
backing up, online 2-25
backup files, location of 2-66
configuration information 2-59
connection status, checking 2-13
consistency, checking 2-11

Index
control files. See control files, database.

core dumps 2-66
e-mail notification 2-66
generating system equipment inventory reports 2-60
importing/exporting 2-67
log files 2-63
maintenance
automated 2-43
scripts 2-43, 2-47
monitoring
database statistics 2-15
OS performance 2-14
purging Oracle 2-36
recovering from
backup 2-30
server error 3-14
UNIX client error 3-13
redo log files 2-65
restore
Oracle 2-29, 2-30
See also Oracle.
shutting down. See Oracle.
starting up. See Oracle.
status scripts 2-10
tablespaces 2-64
trace files 2-66
debug data
archiving to tar files
all information 6-17
NETSMART 1500 information 6-16
Oracle database information 6-17
system information 6-15
debug information menu 6-14
delay algorithms, parameters 3-44
E
e-mail
NETSMART 1500 security 3-45
Oracle administrator 2-66
EML-NML
disabling 3-19
enabling 3-19
F
files
archive, creating 6-6
checking size, UNIX 2-39
database 2-59
properties
editing 6-7
key values table 6-8
restoring UNIX 4-31
FLASHWAVE 7400 node managers
disabling 3-22
enabling 3-22
fragmented tables, recreating indexes on 2-51
FTAM
restarting 5-12
starting 5-4
stopping 5-4
FTP (File Transfer Protocol)
information to FNC 6-3
G
generics. See software generics.
H
HA (high availability) 2-35
automatic failover, understanding 7-18
checking status 7-8
client installation behavior 7-26
crashes, recovering from 7-21
data loss scenarios 7-24
manual failover, initiating 7-15
procedures 7-1 7-33
quick commands 7-31 7-33
starting 7-5
stopping
on active and passive systems 7-13
on passive only systems 7-14
system isolation behavior 7-23
unconfiguring 7-27
Heartbeat tool
administration procedures 3-4 3-88
I-2 Server Administration Guide
FNC-1500-0050-110
Index
database administration 2-2

menu items 3-4
network administration
FTAM, starting and stopping 5-4
menu 5-2
service support 6-2
setting up UNIX accounts 3-7
UNIX system administration 4-2 4-31
with root enabled warning 2-1
home page
Web administration
receiving broadcast messages 3-48
sending broadcast messages 3-48
hot backups
archived redo log files 2-41
multipathing, IP support for NETSMART 1500 5-6
N
NE software generics. See software generics.
NEs
log-on configuration
communication server properties, modifying 3-44
log-on delay 3-44
log-on retries and delay parameters 3-42
reconnect algorithm 3-42
resynchronizing
data 3-41
software generics. See software generics.
NETSMART 1500
administration
optional features 3-16
See also Heartbeat tool.
license
upgrading 3-59
upgrading for HA 3-69
log tables, exporting 2-68
ObjectStream license, configuring 3-37
optional features
disabling 3-19 3-27
enabling 3-19 3-26
patches, managing 3-16
security e-mail 3-45
system information 6-12
user
accounts. See user accounts, NETSMART 1500.
warning banner, pre-logon 3-49
I
IP address
changing 5-22
IP multipathing
setting up 5-6
L
license
NETSMART 1500
displaying 3-58
upgrading 3-59
upgrading for HA 3-69
ObjectStream, configuring 3-37
log
files
archiving 6-4
database 2-63
for UNIX system backup 4-30
logical
restore, invoking resync function 3-41
M
maintenance services
database. See database maintenance.
FNC-1500-0050-110
manual adjacency, TARP. See TARP manual adjacency.
NETSMART 1500 client

port usage A-3
shutting down 3-11
starting
on server 3-9
NETSMART 1500 server
backing up 4-28
communication with NEs 5-5
IP multipathing 5-6
port usage A-2
restoring 3-15
shutting down 3-10

I-3
Index
starting 3-8
starting up 2-18
archive 2-19
by ending backup 2-22
normal 2-18
trace files 2-66
user account 2-5
network
NSAP address
displaying 5-15
See also OSI address.
O
object tablespace, finding contiguous space 2-50
ObjectStream license, configuring 3-37
optional features
disable (all) 3-27
enable (all) 3-26
See also EML-NML, PM, TL1 uplink.
Oracle
alert scripts. See alert scripts.
automated maintenance jobs, listed 2-44
backup
backup 2-25
control files, location 2-65
core dumps, location 2-66
data, tablespaces for 2-64
database administration, Heartbeat menu items 2-2
database objects, validating 2-54
database scripts, status 2-10 2-15
editing crontab 2-52
e-mail to Oracle administrator 2-66
files. See database files.
import/export procedures 2-67
logs, generating ZIP files 2-55
maintenance scripts 2-47 2-57
maintenance, automated 2-43
passwords
changing 2-6, 2-9
verifying 2-7
PM log tables, exporting and storing 2-69
purging 2-36
queries, checking index usage 2-54
restoring database 2-29, 2-30
See also database.
shutting down 2-23
abnormal 2-24
normal 2-23
OSI (Open Systems Interconnection)

addresses
changing 5-13
See also NSAP address.
connectivity 5-5
menu 5-11
route
adding 5-16
deleting 5-16
displaying 5-17
stack 5-7
listing processes 5-12
restarting processes 5-12
starting processes 5-8
stopping processes 5-9
output and log files, deleting 2-50
P
parameters
configuring communication servers 3-42
patches
checking Solaris 6-12 6-17
NETSMART 1500 3-16
performance management (PM)
disabling 3-18
enabling 3-17
port usage
client A-3
server A-2
pre-logon warning banner 3-49
checking status 3-53
disabling 3-51
enabling 3-50
importing text 3-51
retrieving and editing 3-52
properties
FNC-1500-0050-110
Index
file
service
support, Heartbeat 6-2
and key values 6-8

editing 6-7
shutting down
database. See Oracle.
NETSMART 1500 client 3-11
NETSMART 1500 server 3-10
SNMP uplink
disabling 3-26
enabling 3-25
reconnect algorithm
and NE logon 3-42
modifying properties 3-44
software
patches, managing 3-16
recovery
from client error 3-13
from server error 3-14
software generics
CD installation
on NETSMART 1500 server 3-29
on UNIX client 3-34
installing from
network drive 3-36
server 3-29
UNIX client 3-34
restore
files, UNIX 4-31
Oracle database 2-29
resync
NE data 3-41
SONET-SDH
terminology mapping
enabling and disabling feature 3-88
RTRV-HDR 3-55
support
log
editing 6-2
listing 6-3
scripts
automated Oracle maintenance 2-43
database status 2-10
Oracle database alerts 2-37
security
data
tablespaces
database 2-64
extending 2-52
exporting 3-39
importing 3-40
servers
checking processes status 3-12
communication, configuring log-on retries and delays
3-42
installing software generics 3-29

recovering from errors 3-14
restoring files from tape 3-15
shutting down 3-10
starting
client on 3-9
NETSMART 1500 3-8
FNC-1500-0050-110
TARP
manual adjacency
adding 5-19
deleting 5-20
displaying 5-20
manual entries
adding 5-21
deleting 5-21
displaying 5-21
menu 5-18
TID
displaying 5-19
setting 5-19

I-5
Index
TCP/IP
and OSI networks with NETSMART 1500 5-5
connectivity 5-6
time
and date, setting on UNIX system 4-14
TL1 Heartbeat log manager
and RTRV-HDR logging 3-55
disabling 3-56
enabling 3-55
TL1 uplink
disabling 3-21
enabling 3-20
trace
files, deleting 2-48
menu 3-28
transaction debugging client 3-76
options 3-77
starting 3-77
troubleshooting
database information 2-59
NETSMART 1500, configuring

client accounts 4-6
server accounts 4-6
recovering from client error 3-13
restoring
files 4-31
root (/) 4-31
Solaris admintool users dialog 4-31
swap information 4-20
system
activities menu 4-21
backup 4-27
messages 4-19
processes 4-18
user accounts
adding using local files 4-11
deleting 4-13
workstation
powering down 4-3
restarting 4-4
starting up 4-4
upgrading
release or hardware, resync NE data 3-41
U
UNIX
accounts. See user accounts, UNIX.
adding CDE controls to NETSMART 1500 client
accounts 4-8
administration menu items 4-2
backing up system 4-27 4-30
backup log 4-30
changing date and time
backward 4-14
forward 4-16
cronjobs menu 4-25
date and time, setting 4-14
defunct processes, checking 4-26
disk usage 4-20
files
checking size 2-39
checking size of archived redo log files 2-40
installing NE software generics 3-34
log files, understanding 4-13
user accounts
Oracle 2-5
UNIX
adding using local files 4-11
configuring 4-5
creating NETSMART 1500 administrator 3-7
deleting using local files 4-13
W
warning banner, pre-logon 3-49
Web administration operations
sending and receiving broadcast messages 3-48
Web GUI
Web administration
disabling 3-24
enabling 3-23
workstation
UNIX, powering down 4-3
UNIX, restarting 4-4
FNC-1500-0050-110

Netsm110 - Server Administration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Netsm110 - Server Administration Guide

Uploaded by

Copyright:

Available Formats

FNC-1500-0050-110

SERVER ADMINISTRATION GUIDE

FUJITSU NETWORK COMMUNICATIONS INC.

Copyrights, Trademarks, and Disclaimers

NETSMART is a trademark of Fujitsu Network

Oracle is a registered trademark of Oracle Corporation.

FLASH is a trademark of Fujitsu Network Communications

Solaris is a trademark of Sun Microsystems, Inc. in the

Netscape is a registered trademark of Netscape

NETSMART 1500 Version 5

Fujitsu and Fujitsu Customer Use Only

Document Change Notice

DOCUMENT CHANGE NOTICE

Updated for Version 5

New UNIX terminal screen captures

Added a note to indicate that the NETSMART servers must be DOWN

New Section. Set Branding Image in Toplogy View

New Section. Remove Branding Image from Topology View

Fujitsu and Fujitsu Customer Use Only

NETSMART 1500 Version 5

Fujitsu Technical Assistance Center . . . . . . . . . . . .

Oracle User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Check Database Consistency . . . . . . . . . . . . . . . . .

Fujitsu and Fujitsu Customer Use Only

NETSMART 1500 Version 5

Standard Database Backup . . . . . . . . . . . . . . . . . . . . . . . . .

Recovery from a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System and Configuration Information . . . . . . . . . . . . . .

System Equipment Inventory Reports . . . . . . . . . .

NETSMART 1500 Version 5

ii Server Administration Guide

Fujitsu and Fujitsu Customer Use Only

2.11.8 Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.12.1 Export of NETSMART 1500 LOGS . . . . . . . . . . .

Creating UNIX Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting Up and Shutting Down . . . . . . . . . . . . . . . . . . . . .

Troubleshooting Server and Clients . . . . . . . . . . . . . . . . .

Check the Status of Server Processes. . . . . . . . . . . .

Enabling/Disabling Program Groups. . . . . . . . . . . . . . . . .

Enable Performance Management . . . . . . . . . . . . .

Fujitsu and Fujitsu Customer Use Only

NETSMART 1500 Version 5

Enable SNMP Uplink . . . . . . . . . . . . . . . . . . . . . .

NETSMART 1500 Trace Menu . . . . . . . . . . . . . . . . . . . . . . . .

Installing NE Software Generics . . . . . . . . . . . . . . . . . . . . .

Install from CD Using NETSMART 1500

Configuring the ObjectStream License . . . . . . . . . . . . . . .

Export Security Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Import Security Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring the Communication Server/NE Logon. . . .

3.12.1 NE Logon Reconnect Algorithm . . . . . . . . . . . . . .

Security E-Mail Notification . . . . . . . . . . . . . . . . . . . . . . . . .

3.14.1 Sending Messages from a Command Line . . . . . . .

Pre-Logon Warning Banner Administration . . . . . . . . . .

3.15.1 Enable the Pre-Logon Warning Banner . . . . . . . . .

NETSMART 1500 Version 5

iv Server Administration Guide

Fujitsu and Fujitsu Customer Use Only

Enabling/Disabling RTRV-HDR Logging . . . . . . . . . . . . . .

3.16.1 Enable RTRV-HDR Logging. . . . . . . . . . . . . . . . .

NETSMART 1500 License Administration . . . . . . . . . . . . .

3.17.1 Display NETSMART 1500 License Information . .

Service Pack Installation on HA-Enabled Federations .