Professional Documents
Culture Documents
COPYRIGHTS
2004, TruePosition, Inc. All Rights Reserved
TRADEMARKS
TruePosition and the TruePosition logo are registered Trademarks of TruePosition, Inc. in the United States, the European Union, Argentina, Mexico, and other countries. Finder, Anyphone, iFind, ServiceGate, and SCOUT are trademarks of TruePosition, Inc.
Sun, Sun Microsystems, the Sun logo, Sun Fire, Solaris, and all Java-based marks are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. Windows is a registered trademark or trademark of Microsoft Corporation in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. Other brands and their products are registered trademarks or trademarks of their respective holders and will be noted as such.
CONFIDENTIALITY
This document and the information contained herein is the proprietary and confidential information of TruePosition, Inc. It is provided under nondisclosure agreement and may not be reproduced or used for purposes outside the scope of such agreement.
WARRANTY
TruePosition provides this document as is without warranty of any kind, express or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. In no event shall TruePosition be liable for any damages of any kind, arising out of or related to the use or inability to use this document, even if TruePosition has been advised of the possibility thereof.
Contents
1. 1.1. 1.2. 1.3. 1.4. 1.5. 1.5.1. 1.5.2. 1.6. 1.7. 1.8. 2. 2.1. 2.2. 2.3. 2.4. 2.5. 2.6. 2.6.1. 2.6.2. 2.7. 2.7.1. 2.7.2. 2.7.3. 2.7.4. 2.7.4.1. 2.7.4.2. 2.8. 2.8.1. 2.8.2. 2.8.3. 2.9. 2.9.1. 2.10. 2.11. 3. 3.1. 3.2. 3.3. 3.3.1. OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1 Organization of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Writing Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Safety Conventions in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3 Applicable Documents from TruePosition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3 Other Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4 If You Need Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4 AMS SYSTEM ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1 Installing the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1 Installing the Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1 About the AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1 A-Interface Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2 Accessing AMS Through the EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2 Logging Onto AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2 Account/Password Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3 Password Authentication Rules and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3 Viewing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4 SSH Through the EMS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4 Log Files/Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5 Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6 Remotely through SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6 As Root User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6 From the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7 Using AMS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7 Viewing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7 Editing Config Files from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7 Viewing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7 Stopping the AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 AMS Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 AMS Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 Verify AMS is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9 USING THE AMS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1 Viewing Module Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1 Using the AMS Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2 Accessing AMS through EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
iii
Tables
TABLE 1-1: TABLE 1-2: TABLE 1-3: TABLE 1-4: TABLE 1-5: TABLE 2-1: TABLE 2-2: TABLE 2-3: TABLE A-1: ORGANIZATION OF THE DOCUMENT WRITING CONVENTIONS SYMBOLS TRUEPOSITION DOCUMENTS APPLICABLE DOCUMENTS AMS USAGE AND PERMISSION PRIVILEGES COMMANDS USED FOR INVOKING NETWORK ELEMENTS COMMANDS ABBREVIATIONS AND ACRONYMS 1-2 1-2 1-3 1-3 1-4 2-3 2-5 2-6 A-1
iv
1.
OVERVIEW
Contents
1.1. 1.2. 1.3. 1.4. 1.5. 1.5.2. 1.6. 1.8. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Conventions in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents from TruePosition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If You Need Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-1 1-1 1-2 1-2 1-3 1-3 1-4
1.1.
Purpose
This manual provides information pertaining to the administration of Agilents Abis Monitoring System (AMS) component.
1.2.
Audience
This document is intended for AMS server administrators responsible for managing: password maintenance Secure Shell (SSH) starting and stopping AMS remote login root/user system privileges Module Telemetry configuration
1.3.
Prerequisites
This document assumes that you: are an experienced AMS and Linux system administrator will refer to other technical references pertaining to Linux commands. have been assigned administrator or supervisor privileges
1-1
1.4.
Contents
Overview describes the purpose of the manual, conventions used, applicable documents, the manuals organization, and information for obtaining technical help. AMS Administration describes procedures for conducting AMS system administration. This includes password maintenance, secure shell administration, remote login initially as root (then as non-root), and shutting down the system. Using the GUI provides TruePosition-specific configuration and performance management information for AMS modules. Abbreviations and Acronyms provides abbreviations and acronyms used within the document.
3 Appendix A
1.5.
1.5.1.
Document Conventions
This section describes writing conventions and symbols used throughout the document. Writing Conventions Table 1-2 describes the writing conventions used consistently throughout this document.
Meaning
Enter the literal string Names for buttons Press the indicated key on the keyboard Enter the reference in the <> brackets Indicates a window prompt or a file name Enter the literal string Names for buttons
Example
Enter vi hosts. Click the Command and Response button [Enter] Type <ip address> Password: Enter vi hosts. Click the Command and Response button
Action/Result
vi hosts Function is executed. Press the Enter key. For example: 204.64.7.135 Enter the password vi hosts Function is executed.
1-2
1.5.2.
Safety Conventions in this document This document uses the following symbols.
!
WARNING
This symbol indicates that dangerous voltage levels are present within the equipment. These voltages are not insulated and may be of sufficient strength to cause serious bodily injury when touched. The symbol may also appear on schematics.
1.6.
1-3
1.7.
Describes...
Known defects How to troubleshoot hardware/software How to install hardware/software Onsite verification that an EMR server is installed and correctly configured How to configure parameters and alarms how to use the Linux operating system
Document Number
e4260-90160-100 (Version 2.10) e4260-90160-159 (Revision 1) e4260-90160-106 (Edition 2.10) e4260-90160-108 (Edition 1.20)
Available from...
Agilent Technologies Agilent Technologies Agilent Technologies Agilent Technologies
1.8.
1-4
2.
Contents
2.1. 2.2. 2.3. 2.4. 2.5. 2.6. 2.7. 2.8. 2.9. 2.10. Installing the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-Interface Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing AMS Through the EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging Onto AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using AMS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMS Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-1 2-1 2-2 2-2 2-2 2-4 2-7 2-8 2-8
2.1.
2.2. 2.3.
2-1
The AMS server never stops searching for new signals. If a new A-bis or A-interface is provisioned on the network, the AMS autodetects and monitors the signalling channel. As signals are discovered, they are added to dynamic tables (which contain topology information being stored on the AMS server network). Captured messages are sent by the AMS: to the WLG optionally through A-links for processing
Processed information identifies emergency calls as well as call location and radio channels.
2.4.
A-Interface Support
Some equipment manufacturers (e.g., Nokia, Nortel) require cell ID discovery on the AMS through Abis/A-link message correlation. This method of cell discovery is only required when System Information Type 3 and/or 6 messages are infrequently sent on Abis links. The AMS must be connected to the appropriate A-interface links to enable this feature. In order for you to enable CGI discovery (for use in Abis monitoring deployments), it may be necessary to monitor an A-interface. You will need to cable an A-interface link from a BSC to each server that monitors at least one cell from that BSC. For information on associated Abis alarms that may occur, refer to Agilents acceSS7 Location Data Feed Documentation Release A.01.20 and EMS Alarm Troubleshooting Guide.
2.5.
2.6.
You must initially log in as root; all AMS administrative functions are controlled by root.
The following sections describe procedures for: account/password administration password authentication logging in: by telneting from a terminal window remotely as root
2-2
through the Secure Shell (SSH) through the web interface 2.6.1. shutting down AMS
Account/Password Administration
Note:
The following account/password procedures are provided as general guidelines. It is up to the discretion of the system administrator to create users by following these guidelines.
Table 2-1 describes the usage and permission privileges that can be assigned to groups to control access to the system.
Permissions
Ensure that . is not in the search path. Ensure that root login files do not source: - non-root files - files that are group-or world-writable Ensure that any root cron jobs do not source non-root files that are group- or world-writable.
2.6.2.
Consider the following tips when creating passwords: Do not allow blank passwords. Do not use NIS or NIS+. Re-authenticate after inactivity of more than 15 minutes. Abort login attempt after three consecutive failures. Passwords require a maximum age of 60 days.
The following are additional guidelines regarding passwords: Passwords should not be reused within the longest of the following time periods: six months
2-3
three aging periods five password changes Passwords can be changed daily; you may need to do this more than once. Consider changing passwords to at least eight characters in length; the default AMS root password is only three characters. Consider adding at least one numeric character; the default AMS root password provides no numeric characters. Passwords should contain at least one character from the English Language alphabet. Passwords should not contain the UserID as part of the password.
2.7.
CAUTION
!
2.7.1. 1 2
These procedures should only be followed after a shutdown command is issued. See section 2.9.1: AMS Shutdown for AMS shutdown procedures
SSH Through the EMS GUI Follow these steps: Go to the EMS Topology tree. Right-click AMS.
CAUTION
Do not attempt to access or change module parameters through the AMS MUX (SSH). Accessing the command line interface only functions through AMS.
2-4
(The SSH Authorization dialog appears.) 4 5 6 2.7.2. At the login: prompt, type root R At the Password: prompt, type the root password R A bash shell window appears with the command # prompt.
By doing...
cd /var/opt/mls/logs cd /opt/EMRFeed/config/ cd /var/opt/mls/config/
2-5
To check...
Delta between measurements (run this twice to show successful module decoding of traffic) Delta between measurements (run this twice to show CurrentCycle and LastTimeCycle) Delta between measurements (run twice for the number of LAPD frames recd from the acquisition module) Card detection verification (for the acquisition module) Other Configuration files
7 2.7.3.
If the TAC instructs you, use the text editor of choice to edit the appropriate file.
At the # prompt, type: <root> R Type: <root password> R where <root password> is the root password of the remote server.
2.7.4.
Remotely through SSH Data stored on the AMS file system is accessable through the Secure Shell (SSH). For more information about SSH and logging on through EMS, refer to the EMS Administration Guide. As Root User If you cannot log in as root, contact your system administrator. If you can log in: 1 2 3 4 5 Open a standard terminal window on the local workstation or laptop from where a remote session to the server will be set up. Type ssh -l <root name> <Server IP Address> R Type <root password> R where <root password> is the root password of the remote server. To confirm the login, type id R Type <root password> R where <root password> is the root password of the remote server. Since you are working in the Linux environment, you should see information similar to the following:
2-6
AMS Administration Guide Connected to <ip address>. Escape character is ^]. MontaVista Linux 2.1, Carrier Grade Edition Linux/i686 2.4.17 mvlcge21-tsrlt2
From the Command Line You can also use the command line to log into AMS as user; this procedure is described below.
CAUTION
!
1 2
This is not the recommended method of login; you may inadvertently damage files or directories as root.
Use the following directions: Confirm that you have an active AMS account with an appropriate password. At the login: prompt, type username and password, and R
2.8.
2.8.1.
2.8.2.
Editing Config Files from the Command Line Depending upon your environment, you may need to re-configure the following Module Telemetry view parameters: LCS_REASON_FILTER LCS_PCS1900 LCS_SUBRATE_LIST LCS_E1T1_FRAMING LCS_DS3_FRAMING LCS_DS3_MONITOR_POINT LCS_PROTECT_CARDS (if OC-3 cards are being used)
For more information on configuring parameters, refer to Agilents acceSS7 Location Software Configuration and Interfacing Specification. 2.8.3. Viewing Statistics You can use the AMS web interface to view traffic and configuration statistics in the AMS Module Telemetry window.
2-7
For more information on viewing parameters, see Viewing Module Parameters on page 3-1. For information on changing traffic statistics or configuration parameters, refer to the Agilent acceSS7 Location Software Configuration and Interfacing Specification.
2.9.
2.9.1.
AMS Shutdown
Note:
A shutdown of the AMS is necessary after a serious hardware problem or for a planned maintenance downtime. Any AMS shutdown should be done before performing hardware maintenance or physically moving the server.
If you want the AMS to shut down after ten seconds, type:
shutdown -h 10
To reset the AMS, complete the following: 1 Confirm that you are logged in as root via ssh.
2-8
Type:
mls restart
Another way is to just click on http://192.168.170.44:7070. If AMS is not running, the web server will be down, and no page will display.
2-9
2-10
3.
3.1.
Description
The Module Telemetry window displays a static list of running modules. You can view the following read-only information: Module identifier Module name Instance name(s)
Click on a modules Instance Name to access configuration, SNMP, traffic statistics, or Maverick Event Bus (MEB) informational windows. These windows do not allow you to view the current module status and parameters; you must edit the parameter values from the command line as root. Refer to Section 2 for more information.
3.2.
3-1
3.3.
3-2
AMS Administration Guide http://<IP address>:7070 After you press R, the MEB
3-3
appMLSMeasReportForwarder
appMPLSTrafficStats
3-4
3.3.1.
Accessing AMS through EMS If you want to view parameters or statistics on the AMS modules loaded, follow these directions. 1 2 For the AMS Web Interface, select AMS:Group:1:1. Right-click Ams1:2 or 1:1, and AMS Web Interface.
3-5
3-6
APPENDIX A.
The following abbreviations and acronyms are used throught this document.
Meaning
A-1
A-2
7221-1782-0000 Revision B