Data Collection System

Transcription

1 Data Collection System V8.1 Issue 1 Maintenance Guide R8.1 Issue 1 March 2006 Issue 1- March 2006

2 Copyright 2004, Lucent Technologies All Rights Reserved Notice Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change. Preventing Toll Fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party, for example, a person who is not a corporate employee, agent, subcontractor, or working on your company s behalf. Note that there may be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Providing Telecommunications Security Telecommunications security (of voice, data, and/or video communications) is the prevention of any type of intrusion to (that is, either unauthorized or malicious access to or use of your company s telecommunications equipment) by some party. Your company s telecommunications equipment includes both this Lucent product and any other voice/data/video equipment that could be accessed via this Lucent product (that is, networked equipment ). An outside party is anyone who is not a corporate employee, agent, subcontractor, or working on your company s behalf. Whereas, a malicious party is anyone (including someone who may be otherwise authorized) who accesses your telecommunications equipment with either malicious or mischievous intent. Such intrusions may be either to/through synchronous (time-multiplexed and/or circuit-based) or asynchronous (character-, message-, or packet-based) equipment or interfaces for reasons of: Utilization (of capabilities special to the accessed equipment) Theft (such as, of intellectual property, financial assets, or toll-facility access) Eavesdropping (privacy invasions to humans) Mischief (troubling, but apparently innocuous, tampering) Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent) Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company (including but not limited to, human/data privacy, intellectual property, material assets, financial resources, labor costs, and/or legal costs). Your Responsibility for Your Company s Telecommunications Security The final responsibility for securing both this system and its networked equipment rests with you a Lucent customer s system administrator, your telecommunications peers, and your managers. Base the fulfillment of your responsibility on acquired knowledge and resources from a variety of sources including but not limited to: Installation documents System administration documents Security documents Hardware-/software-based security tools Shared information between you and your peers Telecommunications security experts To prevent intrusions to your telecommunications equipment, you and your peers should carefully program and configure your: Lucent-provided telecommunications systems and their interfaces Lucent-provided software applications, as well as their underlying hardware/software platforms and interfaces Any other equipment networked to your Lucent products. Lucent Technologies does not warrant that this product or any of its networked equipment is either immune from or will prevent either unauthorized or malicious intrusions. Lucent Technologies will not be responsible for any charges, losses, or damages that result from such intrusions. Federal Communications Commission Statement Part 15: Class A Statement. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his/her own expense. Part 15: Personal Computer Statement. This equipment has been certified to comply with the limits for a Class B computing device, pursuant to Subpart J or Part 15 of FCC Rules. Only peripherals (computing input/output devices, terminals, printers, etc.) certified to comply with the Class B limits may be attached to this computer. Operation with noncertified peripherals is likely to result in interference to radio and television reception. Part 68: Network Registration Number. This equipment is registered with the FCC in accordance with Part 68 of the FCC Rules. It is identified by a FCC registration number. Part 68: Answer-Supervision Signaling. Allowing this equipment to be operated in a manner that does not provide proper answer-supervision signaling is in violation of Part 68 rules. This equipment returns answer-supervision signals to the public switched network when: Answered by the called station Answered by the attendant Routed to a recorded announcement that can be administered by the CPE user This equipment returns answer-supervision signals on all DID calls forwarded back to the public switched telephone network. Permissible exceptions are: A call is unanswered A busy tone is received A reorder tone is received Canadian Department of Communications (DOC) Interference Information This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio interference regulations of the Canadian Department of Communications. Le Présent Appareil Nomérique n émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A préscrites dans le reglement sur le brouillage radioélectrique édicté par le ministére des Communications du Canada. European Union Declaration of Conformity Lucent Technologies declares that the equipment specified in this document conforms to the referenced European Union (EU) Directives and Harmonized Standards listed below: EMC Directive89/336/EEC Low-Voltage Directive73/23/EEC The CE mark affixed to the equipment means that it conforms to the above directives. Technical Support LUCENT8 International

3 Contents About This Manual iii Organization iii Conventions iii Related Documentation iv Chapter 1 Maintenance Utilities Alarms Printers GUI Operations Troubleshooting Adding the Server Name to DCS Title Bar Changing System Colors Screen Colors: XJam Colors Description Table Changing System Fonts Backing Up the Data Collection System What Needs To Be Backed Up References Application Maintenance Overview Maintenance Responsibility Application Environment Variables Backup Recovering from System Failures Guidelines for Restoring the System References Issue 1 March 2006 i

4 Data Collection System V8.1 Installation and Maintenance Guide Recovering from Disk Subsystem Failures Identifying and Restoring Lost Information Backup Information Gaps Missing Information Disk Subsystem Failures Recovery Procedure ii Issue 1 March 2006

5 About This Manual Organization This manual has one chapter as described below: Chapter 1, Maintenance. This chapter describes the maintenance procedures related to the Data Collection System 8.1. Conventions The following conventions are used in this manual: Data Collection System is referred to as DCS. Voice Processing Module (either a Sierra or CA) is referred to as VPM. The term Enter is used in this document to refer to either the Enter or Return key on the keyboard, depending on whether you are using a terminal or PC. Calls attention to information that supplements the main text or deserves emphasis. Important: Calls attention to a situation that can cause a serious inconvenience. Issue 1 March 2006 iii

6 Data Collection System V8.1 Maintenance Guide! CAUTION: Call attention to a situation that could result in harm to software, loss of data, or an interruption in service, if incorrectly performed.! WARNING: Calls attention to a situation that could result in harm to hardware or equipment, if incorrectly performed. The following typographical conventions are used: Bold Italics Bold italics Courier Any action that the user must take, including the names of buttons, entries, options selected, and keys pressed. Used for titles of books, volumes in a set of books, and for emphasis of a word or words. Used for variables within commands. Indicates prompts, fields, and other text that appear on the terminal. Related Documentation Related documents include the following: Data Collection System V8.1 Operations Guide, R8.1 iv Issue 1 March 2006

7 1 Maintenance This chapter will show you how to: Edit system configurations Back up DCS application databases and logs Restore the following DCS software and data in case of a system or disk failure: Application executables Application administrative database Application configuration database Primary data Application log messages Utilities Utilities are described in the following sections. Alarms Alarms and error messages are detailed in the DCS online help. For more information, see Chapter 19, Alarms, in the Data Collection System V8.1 Operations Guide, P/N Issue 1 March

8 Data Collection System V8.1 Maintenance Guide Printers The DCS uses printers that are configured into the UNIX lp subsystem. Follow the steps as mentioned below to enable/add new printer or access to printer on systems runnning DCS. 1) Login as root 2). Modify /etc/passwd to add user lp ex: lp:x:71:8:line Printer Admin:/usr/spool/lp: 3). Add following in /etc/services file (it was commented out during the dcs installation ) printer 515/tcp spooler # line printer spooler 4) Add following in /etc/inet/inetd.conf file. printer stream tcp6 nowait root /usr/lib/print/in.lpd in.lpd 5). Execute svcadm enable svc:/application/print/server The Printer can also be enabled either using a solaris print manager or with lp commands Using Solaris Print manager. 1. cd /usr/sadm/admin/bin 2../printmgr & this will invoke a gui screen where u can enter the printer options. Using command line 1) lpadmin -p Printername -v /dev/null 2) lpadmin -p Printername -m netstandard 3) lpadmin -p Printername -D "testing printer" 4) lpadmin -p Printername -o dest=printers IP adress:9100 -o protocol=tcp -o timeout=5 5) lpadmin -d Printername ( will set the printer as defualt printer ) 1-2 Issue 1 March 2006

9 Maintenance After lpadmin command you should execute two additional commands before you can use printer: enable Printername accept Printername if you need more information regarding printer setup, refer SUN Printer Setup documentation. To use the default printer, refer Chapter 17, Reports, in the Data Collection System V8.1 Operations Guide, P/N GUI Operations Remote GUI operations of the DCS requires an X-windows client configured with a minimum screen setup of 1024 x 768 pixels. 1) The DCS GUI may appear differently on an X-windows client than on a Sun client. 2) Also you need to configure the DSIPLAY parameters as follows setenv DISPLAY=IPADDRESS:0.0 (for csh) export DISPLAY=IPADDRESS:0.0 (for ksh) - (if you local machine IP is , execute export DISPLAY= :0.0 ) 3) Also execute xhost + on DCS server to allow XTERM client connection. (you can find xhost in /usr/x/bin dir A bug exists in the DCS that causes overlapping GUI windows to flicker. When this occurs, click the active window and drag it to another part of the screen. The flickering should stop. Issue 1 March

10 Data Collection System V8.1 Maintenance Guide Troubleshooting Troubleshooting commands are included in Chapter 26, Utilities and Troubleshooting, in the Data Collection System V8.1 Operations Guide, P/N Adding the Server Name to DCS Title Bar The server name of the DCS can be added to the title bar. 1. Log in as appadm. 2. Enter RUNGUI Enter name of the X workstation/terminal you are using now: 3. Enter your workstation name or terminal name and press Enter. Your workstation name or terminal name must exist in /etc/hosts file. You can also enter your workstation or terminal IP adress, i.e. XXX.XXX.XXX.XXX:0 4. DCS menu bar window and the warning message window are displayed on your terminal. Click OK button on the warning message window to close this window. 5. Select Navigation from the menu bar. 6. Select System. 7. Select Parameters. 8. Update System Name field to the server name you want to use for this DCS. The value of System Name field will be displayed also at the beginning of the title bar followed by the screen name, on all application screens. Changing System Colors The colors of the DCS screens can be changed by each user. 1-4 Issue 1 March 2006

11 Maintenance Use the following procedure to change the color on all DCS screens. 1. Log in as root. 2. Go to the home directory of the user. Example cd /opt/dcs/appadm 3. Edit the XJam file. Example vi XJam 4. Search for this text string to change the background for the menu bar and dialog boxes:! Set the location of the X rgb color dbase file.!this must be changed to reflect the site-specific location. XJam.rgbFileName: /usr/openwin/lib/x11/rgb.txt! Set any GUI colors in your color scheme. XJam*foreground: black XJam*background: #d6cbb1! XJam.rgbFileName is a file of the most common colors. 5. Change the background to the desired color by modifying this line: XJam*foreground: black XJam*background: #d6cbb1 Example Change #d6cbb1 to white. 6. Search for this text string to change the colors of the fields and buttons on the screens:!set the 16 Jam colors. These are mandatory, as JAM needs a way! to map the 16 Basic colors to actual GUI values. But you can! modify the values to suit your needs. 7. Modify the colors using the XJam colors description table as a guideline. Issue 1 March

12 Data Collection System V8.1 Maintenance Guide Notes: See Screen Colors: XJam Colors Description Table in this guide for more information. Color choices can be found in the XJam.rgbFileName. Example From Step 4, the file pathname would be /usr/openwin/lib/x11/rgb.txt 8. Write the file. 1-6 Issue 1 March 2006

13 Maintenance Screen Colors: XJam Colors Description Table Use the information in Table 1-1 as a guideline for modifying colors. Each of the field definitions pertain to a certain area on the DCS screen. Table 1-1. XJam Colors Description Table Field Definition Screen Area Default Color (Brown and Tan) in Hex Example to Change the Background to White and the Buttons to Blue XJam.black: Characters on Proprietary window # XJam.blue: Printer screen #0000a8 white XJam.green: Form backgrounds #d6cbb1 white XJam.cyan: Function buttons #8b4513 medium blue XJam.red: #a80000 XJam.magenta: #a800a8 XJam.yellow: #a85400 XJam.white: Background for enhanced reports #a8a8a8 white XJam.hi_black: # XJam.hi_blue: Fields that can be changed on Select #faebcd white XJam.hi_green: Field backgrounds for database qbe and New #cabba4 white XJam.hi_cyan: #54ffff XJam.hi_red: Critical alarm field #ff5454 XJam.hi_magenta: Non-updatable fields and 8 Update/View function button characters #d1b67f white XJam.hi_yellow: Major alarm field #ffff54 XJam.hi_white: Background of Proprietary window #ffffff Issue 1 March

14 Data Collection System V8.1 Maintenance Guide Changing System Fonts The font size of the DCS screens may be by each user. Changing fonts will change the screen size and the alignment of reports and logs. Use the following procedure to change the font size on the DCS screens. 1. Log in as root. 2. Go to the home directory of the user. Example cd /opt/dcs/appadm 3. Edit the XJam file. Example vi XJam 4. Search for this text sting to change the font:!specify the application-wide default font. Use a more fully qualified string! to set fonts for parts of your application (e.g. XJam*message*fontlist for! message boxes). XJam*fontList: fixed 5. Add these lines to the file, if they are not there: Examples XJam*fontList: -b&h-lucida-bold-r-normal-sans p-0-iso XJam*fontList: -sony-fixed-medium-r-normal c-80-iso XJam*fontList: -*-helvetica-bold-r-normal--*-140-*-*-p-*-*-* XJam*fontList: -*-fixed-bold-r-normal-*-*-*-*-*-*-*-*-* 6. Comment out all of the lines but the one you want to use. Changing fonts will change the screen size and the alignment of reports and logs. 1-8 Issue 1 March 2006

15 Maintenance Backing Up the Data Collection System Backups provide recovery from possible system crashes and should be performed on a regular basis. Additionally, you should backup the DCS whenever the following occurs: DCS software is upgraded The system configuration is changed What Needs To Be Backed Up The following system software, databases, and file systems need to be backed up: System Root Disk System file systems /usr and /var References Use these references to perform backups: To backup the root disk, /usr, and /var, follow the procedures documented in the UNIX System Administration manuals for backup operations. To backup Informix database and the network configuration files, see Chapter 24, Database Backup, Restore, and Audit, in the Data Collection System 8.1 Operations Guide, P/N Application Maintenance Overview The following sections describe application maintenance. Maintenance Responsibility The application group administrator is responsible for application maintenance. Issue 1 March

16 Data Collection System V8.1 Maintenance Guide Application Environment Variables The application environment consists of various environment variables defined in the file /etc/env.$apptag where $APPTAG is the name chosen for the application. The environment variables are defined when you log in as the DCS application group administrator. Backup You should backup and restore application components using the standard UNIX utilities like cpio and tar. Log in under the administrator root login. Important: Make sure you preserve file ownership and permissions. Recovering from System Failures System failure is a disastrous situation where some or all of the disk subsystems containing the UNIX system software and/or application software are lost beyond recovery. Guidelines for Restoring the System After a system failure, restore your system with backup media. If backup media is unavailable, you may have to re-install the Solaris operating system and the DCS application. References See the UNIX documentation for restoring the system from backup media or for reinstalling the operating system Issue 1 March 2006

17 Maintenance Recovering from Disk Subsystem Failures Use the data disk subsystem failures recovery procedure (see Recovering from Disk Subsystem Failures ) when a disk subsystem fails and when it is not possible to recover it using plex reconstruction under the Solaris Volume Manager. Important: You must first identify the part of the application or system data that was lost as a result of the failure. Identifying and Restoring Lost Information Use the information in Table 1-2 as an aid in identifying and restoring lost data. Table 1-2. Identifying and Restoring Lost Information Item Var. in etc/env.$apptag Description How to restore Application Files FOC_ROOT Application executables/files Application Local View Administrative Database ROAMCNFG FOC_DATABASE Application local view under BaseWorX Application administrative database under Informix Backup/restore tool used to back up. Backup/restore tool used to back up. Use Informix tools. Application Logs FOC_LGDIR Application logs Backup/restore tool used to back up. Configuration Files None System Configuration files used by the application Database None DMrestore script run from the UNIX prompt Backup/restore tool used to back up. Use $FOC_ ROOT/bin/DMrestore to restore the database. Issue 1 March

18 Data Collection System V8.1 Maintenance Guide Backup If application specific information is lost, attempt to restore it from previously backed up media using the appropriate restore tools and procedures. Information Gaps Information gaps may occur after you restore from a backup copy. The system administrator must determine what information is missing after a restore and update the DCS appropriately. Example If a network element was added after the backup was made, you must again add the network element after the restore. Missing Information Some information can never be recreated when a restore is done from an old backup. Example Log messages Disk Subsystem Failures Recovery Procedure Use the following procedure to recover from a billing data disk subsystem failures. 1. Determine the device names of the failed disks on the failed disk subsystem. 2. Access the file /etc/vfstab to find out which file systems are affected by the disk subsystems failure. 3. Use the DCS utility nedir_list all to determine which data is stored under the affected file systems Issue 1 March 2006

19 Maintenance 4. Examine the collection logs and transmission logs to find out which of the primary data files are lost. Example Primary data files collected from the NE, but not transmitted to the billing entity. If collection and/or transmission logs are unavailable, contact the network element and billing entity to determine which primary data files are lost. 5. Recover the failed disk subsystems and create the required file systems on the recovered disk subsystems, or temporarily make the required file systems to some other disks subsystem until the failed disk subsystems are recovered. The DCS utility audit_adb can be used to audit the administrative database and create any missing billing file systems of the network elements. 6. Disable the polling scheduled collection for each of network elements affected by the failure. 7. Request collection of the lost primary data files from the network element. 8. Remove the block on scheduled collection for each of the network elements. Issue 1 March

20 Data Collection System V8.1 Maintenance Guide 1-14 Issue 1 March 2006

21 Index A administrative database, restoring 11 application files, restoring 11 application logs, restoring 11 audit_adb utility 13 B backup necessary backups 9 restoring lost information/data 11 strategy 9 C Collector application, utilities audit_adb 13 nedir_list all 12 color changing 5 7 description table 7 configuration files, restoring 11 D disk subsystem failures information gaps 12 missing information 12 recovery from 11 E environment variables APPTAG 10 FOC_DATABASE 11 FOC_ROOT 11 FOC-LGDIR 11 ROAMCNFG 11 F files /etc/vfstab 12 XJam 4??, 5 8 fonts, changing system 8 L local view, restoring 11 N nedir_list all utility 12 network element 13 Issue 1 April 2005 IN-1

22 Data Collection System V8.1 Installation and Maintenance Guide R restoring administrative database 11 application files 11 application logs 11 configuration files 11 local view 11 system 10 S system backing up 9 backup strategy 9 failures 10 recovery 10 U UNIX utilities 10 V volume manager 11 X XJam file 4??, 5 8 IN-2 Issue 1 March 2006