Manuale d’uso / di manutenzione del prodotto LBI-39169 del fabbricante Ericsson
Vai alla pagina of 90
LBI-39169 ericssonz User’s Guide EDACS NETWORK MANAGEMENT.
LBI-39169 2 NOTICE! This manual covers Ericsson and General Electric products manufactured and sold by Ericsson Inc . NOTICE! This product m ay on ly be us ed for the fu nctions desc ribed in this manual . Use of the produ ct for other purpos es shall constitute a violation of the license.
LBI-39169 3 TABLE OF CONTENTS Section/Paragraph Page 1. PREFACE ........................................................................................................................................................... 9 1.1 MANUAL ORGANIZATION .....
LBI-39169 4 TABLE OF CONTENTS Section/Paragraph Page 8.3 IDENTIFYING THE CAUSE OF ALARMS ............................................................................................. 31 8.3.1 Using Hierarchical Maps....................................
LBI-39169 5 TABLE OF CONTENTS Section/Paragraph Page 13.14 LOADING MIBS.................................................................................................................................... 63 14. PROCEDURES .............................
LBI-39169 6 LIST OF FIGURES AND TABLES Figure Title Page Figure 1 - EDACS Menu on Main Menu Bar ...........................................................................................................17 Figure 2 - Example of Map Traversal..........
LBI-39169 7 LIST OF FIGURES AND TABLES Figure Title Page Figure 33 - Traffic Filter Window ............................................................................................................................ 55 Figure 34 - Multisite Monitor Legend .
LBI-39169 8 This page intentionally left blank.
PREFACE LBI-39169 9 1. PREFACE This is one of four manuals for the EDACS Ne twork Manager . T his manual provid es op erating instr uctions for users and administrators of the Network Manager system.
LBI-39169 PREFACE 10 Section 13 Using OpenView Network Node Ma nager - T his section pr ovides sup plemental information on using some of the features available through HP OpenView Network Node Manager. Section 14 Procedures - This section pro vides p ro cedures for custo mizing, configuring, and maintaining the Network Manager application.
DOCUMENTATION LBI-39169 11 2. DOCUMENTATION In may be necessar y to consult one or more o f the follo wing documents when ope rating the Network Manage ment system.
LBI-39169 DOCUMENTATION 12 System Manager Documentation: LBI-38703 - EDACS VAX/VMS Sy stem Man ager Installation , Setup, and Troubleshooting Technical R eference Manual LBI-38984 - EDACS VAX/VMS System Manager User’s Guide AE/LZT 123 1908/1 - Keyboard Mapping Template.
INTRODUCTION LBI-39169 13 3. INTRODUCTION The International Organization for Standards (ISO) Netw o rk Management forum identifies five functional areas of network management, often referred to simply as “FCAPS.” T his model se rves as the basis for the Network Ma nagement system.
LBI-39169 INTRODUCTION 14 3.1 FAULT MANAGEMENT Fault Managem ent is responsible for detecting, isolating, and repo rting anomalous conditions affecting network operation.
INTRODUCTION LBI-39169 15 3.4 PERFORMANCE MANAGEMENT Performan ce Managem ent is respon sible for characterizing the us age and efficien cy of the n etwork. This area is conceptually composed of three major areas: • Utilization -- Provides inform ation regarding w hich aspects of, an d the degree to wh ich, the netw ork interfaces are being used.
LBI-39169 INTRODUCTION 16 3.5.2 System Access Security Managemen t is responsible f or administerin g user access to netw ork resources, including the Network Elem ents (NEs) themselves.
INTRODUCTION LBI-39169 17 Background Network Map Overlays This standard HP OpenView Network Node Manag er feature allows customers to flexibly place netw ork icons on top of actual area maps. Topological maps (in standard GIF format) are easily added, but are not provided.
LBI-39169 NETWORK MANAGER BASICS 18 4. NETWORK MANAGER BASICS 4.1 PULLDOWN MENU SELECTION PROCEDURE USING THE MOUSE Select one of the two options below to select the Pulldown Menu: Position the cursor to the desired menu option, and quickly press/release the left mouse button once.
NETWORK MANAGER BASICS LBI-39169 19 4.4 MAP TRAVERSAL The followi ng submaps are ex amples of m ap traversal. The first two subm aps contain backg round graphics, while the last two do not. Background graphics may be loaded in all submaps. Exploding the EDACS icon brings up a screen similar to that shown below.
LBI-39169 NETWORK MANAGER BASICS 20 Explodin g th e Swi tching Center icon (S W Ctr #37) on the IMC Node 37 su bmap bring s up a Sw itch Cen ter 37 subm ap similar to the screen shown below. Explodin g a Si te icon (such as Site 1) on the IMC Node 37 su bmap bring s up the Si te 1 subm ap simila r to the screen shown below.
STARTUP PROCEDURES LBI-39169 21 5. STARTUP PROCEDURES Use the fo llow ing p rocedur es to login and star t a Network Manager w ork se ssion. A Network Manager work session is described as the time between logging in and logging out.
LBI-39169 STARTUP PROCEDURES 22 5.2 ENDING A NETWORK MANAGER WORK SESSION Use the following procedures to properly end a work session. CAUTION When you finish a working sessio n, DO NOT turn o ff the Network Ma nager Statio n. T his equip ment is par t o f a multi- user network, and other p eople may be using it.
RETRIEVING THE SOFTWARE VERSION LBI-39169 23 6. RETRIEVING THE SOFTWARE VERSION The Software Version feature allows you to obtain the versio ns of software installed on the Netw or k Manager platform and software installed on directly connected devices and the devices they proxy for.
LBI-39169 RETRIEVING THE SOFTWARE VERSION 24 Major Version The Minor Software vis ion is an integer number representing the minor software revision number, for example the number “1” in 2.1. Description The description field provides a brief description of the software component.
EDACS HELP LBI-39169 25 7. EDACS HELP EDACS Help has been integrated into the OpenView Netw or k Node Manager help system. EDA CS Help items are preceded with “EDACS” to make them easily identifiable. F ile... On H elp D ispla y Legend I ndex G lo ssary On V ersion Help I ndex A pplication T asks F1 F unctions A pplic ation On Help .
LBI-39169 MONITORING EDACS FAULT CONDITIONS 26 8. MONITORING EDACS FAULT CONDITIONS Fault Management is responsible for detecting, isolating, and rep orting alarm or fault cond itions affecting the various Managed Elements (ME) in the EDACS network. 8.
MONITORING EDACS FAULT CONDITIONS LBI-39169 27 Table 1 - Status Colors/Levels Category Status Condition Status Meaning Icon Color Administrative Unmanaged Users can set this value, which indicates that the object should not be monitored and that the status should be ignored.
LBI-39169 MONITORING EDACS FAULT CONDITIONS 28 The user is able to determine the Managed Element’ s op erating conditio n at a glance by ob serving the ico n’s color. Upon receiv ing an alarm, the even t is logged and the icon color is ch anged to the color representing the severity of th e alarm.
MONITORING EDACS FAULT CONDITIONS LBI-39169 29 /usr/EDACS/conf/C/ed_trapd.conf . The severity levels and category w ill not be resto red and will rem ain as custo m ized by the user. The restore operation will not erase the actions which have been associated with individual alarms.
LBI-39169 MONITORING EDACS FAULT CONDITIONS 30 8.2.5 UnManaging Devices If a device is u ndergoing m aintenance, it may be desirable to unm anage its associated icon to prevent its state from propagating up the map levels. To unmanage a device, perform the following: 1.
MONITORING EDACS FAULT CONDITIONS LBI-39169 31 8.3 IDENTIFYING THE CAUSE OF ALARMS 8.3.1 Using Hierarchical Maps After the Network Manager alerts the user to an alar m either by changing an ico ns color or thr ough a popup wi ndow, i t will be necessary to identify the responsible element causing the fault indication and isolate the cause.
LBI-39169 MONITORING EDACS FAULT CONDITIONS 32 device polling will be displayed. The display is in a short report (list) format, w ith each entry in the report listing the time stamp, alarm description, and severity level of the event.
MONITORING EDACS FAULT CONDITIONS LBI-39169 33 8.3.2.1 Notification of New Events To know when events have been receiv ed, examine the ev ent notification indicator ligh ts in the Event Categories window. The indicator lights will change to corresponding color of the most severe alarm logged.
LBI-39169 MONITORING EDACS FAULT CONDITIONS 34 8.3.2.3 Deleting Events Events continue to app ear in an Event Browser list until you delete them or the maxim um number of events for the browser h as been reached. The primary reason to delete events is so y ou can determine w hen n ew events occu r.
MONITORING EDACS FAULT CONDITIONS LBI-39169 35 The Network Manager will display the Event Description w indo w providing the technical details associated with the event and possible corrective action.
LBI-39169 CONFIGURING EDACS DEVICES 36 9. CONFIGURING EDACS DEVICES The N etwork Manager provide s a single poi nt of contro l and can co nfigure devic es by either br inging up clients running on th e Network Manager or by logg ing into devices with the native access mode.
CONFIGURING EDACS DEVICES LBI-39169 37 9.1.1 Starting The CEC/IMC Session From the Network Manager, invoke the CEC/IMC Manager client using the following procedure: 1. On the Switch Center submap, highlight the IMC Manager icon. 2. From the Main Menu bar, select the EDACS->Configuration->Configure m enu ite m .
LBI-39169 CONFIGURING EDACS DEVICES 38 Before proceeding, it is recommen ded that th e user be completely fam iliar with using the CEC/IMC Manager f or Windows NT. Complete instructions may be found in LBI-39224. 9.1.2 Sample CEC/IMC Manager Screens Some sample CEC/IMC Manager screens for configuration follow.
CONFIGURING EDACS DEVICES LBI-39169 39 Figure 20 - Console User Profile Configuration Example Screen 9.2 TELNET SESSIONS TO THE PI, BCU, CAL, AND EDG Telnet access into each device is password-protected. Therefore, th e user requesting access m ust have login priv ileges for the rem ote device.
LBI-39169 CONFIGURING EDACS DEVICES 40 T his brings up the the System Manager Us er Menu sc reen (F igure 22 ). Fro m this po int o n all System Manage r operations are as described in LBI-38984. NOTE When telneting into the System Manager, the key board is remapped for use with the VAX/VMS op erating system.
CONFIGURING EDACS DEVICES LBI-39169 41 9.4 USER ACTION LOGGING The EDACS Net work Manag er logs the EDA CS Config uration fun ctions reboot, restart, an d shutdow n. Each logged action includes th e host name, us er name, tim e, date, description of action, and targeted EDA CS IP Address.
LBI-39169 TRANSFERRING DEVICE FILES 42 10. TRANSFERRING DEVICE FILES Occassionally, it m ay be necessaary to transfer device files; such as co nfiguration files for editing, activity data for billing, etc.
TRANSFERRING DEVICE FILES LBI-39169 43 PI Activity Data Transfer Example This is an example of transferring the PI activity record sep01.log to the users HOME directory. Connected to 192.168.201.30. 220 192.168.201.30 pSOSystem FTP server (NTL68K/1.0.
LBI-39169 TRANSFERRING DEVICE FILES 44 BCU CDR Data Transfer Example This is an exam ple of transferring a CDR record , t2250609.CDR, from the BCU to the user’ s home directory . T h e user may then use a third party application that reads CDR records.
TRANSFERRING DEVICE FILES LBI-39169 45 System Manager Activity Data Transfer Example This is an example of transferring an Activity data file , ACT_01-SEP-1996.03;1, from the System Manger to the user’ s home directory. The user may then use a third party application that reads CDR records.
LBI-39169 MONITORING PERFORMANCE TRENDS 46 11. MONITORING PERFORMANCE TRENDS Performance trends can be u sed to d eterm ine utilization and accessibility o r to tun e system perform ance. Trends can be viewed on a per site or Radio Switch basis. The results of these trends are presented on the 2-D line graphs.
MONITORING PERFORMANCE TRENDS LBI-39169 47 11.1.1 Line Graph Example The example of a line graph, shown in Figure 26, illustrates the ease and clarity w ith which the EDACS Netw ork Manager pl atform pres ents data.
LBI-39169 MONITORING PERFORMANCE TRENDS 48 Both of these program s will convert the “xw d” format to “TIF” and “GIF” formats w hich are easily im po rted into other applications.
MONITORING PERFORMANCE TRENDS LBI-39169 49 11.2 TRACKING EDACS DEVICE UTILIZATION The Perfo rm a nce -> Utilization menu item allow s the user to chart the totals for call types pertaining to this EDACS device. The entries on the Pe rformance sub-bar, see Figure 27, are d etailed belo w.
LBI-39169 MONITORING PERFORMANCE TRENDS 50 11.3 TRACKING EDACS DEVICE ACCESSIBILITY The Performance -> Accessibility m enu item allow s the u ser to chart the queu ed, busy, and deni ed call information f or this EDACS device. All of the following graphs will be displayed for either nodes or sites.
MONITORING PERFORMANCE TRENDS LBI-39169 51 11.4 COMPARING PERFORMANCE FROM MULTIPLE SITES OR NODES The Performance -> Compare menu item allows the user to chart a single MIB value for multiple nodes or sites. The following graphs w ill d isplay a single performance parameter for m ultiple nodes or sites on the same graph.
LBI-39169 MONITORING REAL-TIME CALL ACTIVITY 52 12. MONITORING REAL-TIME CALL ACTIVITY Real-tim e call activity can be displayed on both node (Multisite Monitor) and site (Site Monito r) levels.
MONITORING REAL-TIME CALL ACTIVITY LBI-39169 53 12.1 USING THE MULTISITE MONITOR APPLICATION The Multisite Monitor ap plication monitors call activity for one user-s p ecified node. All w ind ows can be m anipulated (i.e., resized, iconized, closed) via standard window border operations.
LBI-39169 MONITORING REAL-TIME CALL ACTIVITY 54 The Optio ns menu has f o ur options: T raffic Filter, Legend, Statistics Rows, and Quiet Drops. The Options menu is discussed in the next section.
MONITORING REAL-TIME CALL ACTIVITY LBI-39169 55 Each filter ty p e also has a textual setting. There are five textual options. Only one may be in effect at a time for a specific call type. 1. None No textual information is displayed. 2. Filter ID One- or two-letter default designation for filter type (Example: EM, IN, GR, ID, GD, IT, TI, TG, CC).
LBI-39169 MONITORING REAL-TIME CALL ACTIVITY 56 12.1.2 Viewing Call Type Colors The Legen d button activates a sm all window that serves as a key for the current T raffic Filter settings (see Figure 34). Beside each filter is a button that conveys the filter’s current state, color, and textual settings.
MONITORING REAL-TIME CALL ACTIVITY LBI-39169 57 12.2 USING THE SITE MONITOR APPLICATION The Site Monitor application m onito rs call activity for an individual site. T he Site Monitor window co ntains a main men u bar, w ork area, and scroll bars (see Figu re 35).
LBI-39169 MONITORING REAL-TIME CALL ACTIVITY 58 F ile S t ati st i cs Rows P hone Di git s Fin e T im ing Q ui et Drops K eyi ng Updates O pti ons Hel p St ati st ics Rows . Tu rns ON or OFF the St ati st ic Ro w dis playi ng Last Queued Call , Las t Deni ed Cal l, Las t System Bu sy Call and last Conv ert-to-Callee Call .
USING OPENVIEW NETWORK NODE MANAGER LBI-39169 59 13. USING OPENVIEW NETWORK NODE MANAGER This sectio n briefly descr ib es some of the features availab le thr ough O pe nVie w Network Nod e M anage r. W e suggest the you become fam iliar with the HP OpenView Network Node Manager User’s Guide.
LBI-39169 USING OPENVIEW NETWORK NODE MANAGER 60 13.5 THRESHOLD TRAPS ON COLLECTED DATA The user m ay specify the generation of an event based upon the value of a mon itored perform ance parameter or that parameter’ s exceeding a user- defined thres hold.
USING OPENVIEW NETWORK NODE MANAGER LBI-39169 61 T he r ingBell utility takes two argue ments. The value of the auguments are insignificant as lo ng as the fo rmat is correct. ringBell <selectionName> <message in quotes> T he ringBell utility performs tw o actio ns.
LBI-39169 USING OPENVIEW NETWORK NODE MANAGER 62 13.11 MULTIPLE EDACS NETWORK MANAGER SESSIONS OpenView Network Node Manager supports m ultiple login ses sions. Multiple session s can be accomplish ed by using an X-Station or by using a PC running PC Xware.
USING OPENVIEW NETWORK NODE MANAGER LBI-39169 63 13.13 CUSTOMIZING ICONS 13.13.1 Icon Labels Modificat ions to fields other than “ Label” in t he Sym bol Description are not supported an d may adversely affect system behavior. To change icon labels, depress the right mouse button while positioned on the icon and select Describe /Modify Symbol.
LBI-39169 PROCEDURES 64 14. PROCEDURES 14.1 REBOOTING THE NETWORK MANAGER From the root profile enter: > /etc/shutdown -r now 14.2 SYSTEM SHUTDOWN PROCEDURES Use the following procedure to properly shutdown the Network Manager system. CAUTION Stopping the system improperly can corrupt (damage) the file systems.
PROCEDURES LBI-39169 65 • Console • Jessica PBX Interface (PI) • Billing Correlation Unit/ Centralized Activity Logger (BCU/CAL) NOTE: The site devices are not included in this list. Their status is obtained through the System Manager Proxy Agent.
LBI-39169 PROCEDURES 66 14.5 ADDING SYMBOLS TO EDACS MAPS Use the following procedure to add symbols to the EDACS Maps. To drag a symbol onto an OpenView Network Node Manager Map, 1. Select the EDIT-> Add Object M enu item from the Op enView Network No de M anager main menu bar.
PROCEDURES LBI-39169 67 HP application wh ich finds IPs. It is also possible that directly connected elemen ts may be added prior to their discovery by the IPMAP application. Care m ust be taken to ensu re that the object created is also used by IPMAP.
LBI-39169 PROCEDURES 68 4. Enter the following command to restore permissions. > chmod 444 /usr/EDACS/nls/C/msm_msg.msg <ENTER> (MSM message file) or > chmod 444 /usr/EDACS/nls/C/sm_msg.msg <ENTER> (SM message file) 5. As the root user, generate new catalog files by executing the following : > /usr/EDACS/bin/edacsMsgUpdate 6.
PROCEDURES LBI-39169 69 T he be ginning of this output will list the number of ob jec ts in the data base. T her e should b e roughly three times the number of EDACS elements. 2. Enter: > /usr/OV/bin/ovobjprint > Filename This will output the contents to a file called “Filename.
LBI-39169 PROCEDURES 70 2. Select the enterp rise of the agent reporting the traps, and the traps defined for the agent will be displayed in the middle w ind ow.
PROCEDURES LBI-39169 71 14.18 RESTORING A FULL SYSTEM IMAGE FROM THE BACKUP To restore a full system image from the backup, perform the following steps: 1. As root user: Use console login. > /etc/shutdown now <ENTER> System will shutdown and come back up in single-user mode.
LBI-39169 TROUBLESHOOTING 72 15. TROUBLESHOOTING This section presents various methods for solving technical difficulties with the Network Manager. 15.1 CD-ROM DOES NOT WORK Problem: /etc/update exits with error that all devices are not mounted. Solution: The /etc/checklist file should have only list the hard drives.
TROUBLESHOOTING LBI-39169 73 15.4 EDACS ICON IS BLUE Problem: The EDACS icon is blue. Solution: A blue icon indicates that the element is not managed by the EDACS Network Manager application. This can happen if another icon is added with the same EDACS Identifiers as this one.
LBI-39169 TROUBLESHOOTING 74 15.8 POPUP STATES NO NODE LICENSE Problem: This popup will occur either if there is no node license or if there is no application license. Solution: Use ls_stat to determine if either of these conditions exist. 15.9 PERFORMANCE NOT SHOWING TRAFFIC Problem: No traffic indicated on MSM, SM, or 2D line graph.
TROUBLESHOOTING LBI-39169 75 15.11 APPLICATION DOES NOT RESPOND TO VERIFICATION REQUEST WHEN ADDING ICON Problem: Application does not respond to Verification request when adding icon. When hit verify a second time, OpenView will not call application again.
LBI-39169 TROUBLESHOOTING 76 Network Manager stations and ensure the interval is set to a value of 30 seconds or more. This will significantly reduce the number of nuisance failures. 15.14 IMC DETECTED LINK FAILURES Problem: The IMC reports a link failure.
TROUBLESHOOTING LBI-39169 77 The only viable solution is to refrain for using color-intensive background graphics in the OpenView submaps. 15.16 POPUP WARNING Problem: An xnmevent popup warns that only 10 popups can be generated at a time. Solution: The /usr/OV/appdefaults/XNm resource file sets the xnmevents.
LBI-39169 GLOSSARY 78 16. GLOSSARY TERM DEFINITION ACU A larm and C on trol U nit. The ACU provides 32 alarm inpu ts and 8 relay outputs and allow s for external device alarm ing to the Sy stem Manag er. T he ACU and Test Unit (TU) form the Test and Alarm Unit (TAU).
GLOSSARY LBI-39169 79 TERM DEFINITION SCAT, and CNI systems. Callee The party to whom the call is placed, i.e., an individual or group of radios. Caller The originating party of the call request, i.
LBI-39169 GLOSSARY 80 TERM DEFINITION CNI C onventio nal N etwork I nterface − A conventional base statio n can be connected to the C EC/IMC switch via a CNI. The CNI is form ed by a GET C shelf located at the con ventional station that m akes the station appear to a MIM as an EDACS site.
GLOSSARY LBI-39169 81 TERM DEFINITION EDACS EDACS, sh ort for E nha nced D igital A ccess C ommunications S ystem, is a registered tradem ark of Ericsson Inc.
LBI-39169 GLOSSARY 82 TERM DEFINITION HP OV NNM Hewl ett-Packard O pen V iew N etw ork N ode M anager. Management platform that prov ides common managem ent function s, such as data collection and reporting, using standard protocols and software interfaces.
GLOSSARY LBI-39169 83 TERM DEFINITION Management Information Base Management Information Base. A description of the data stor ed in a Netw ork Element sim ilar to a C structure. A MIB definition allows the EDACS Network Manager to read and write values in a Network Element.
LBI-39169 GLOSSARY 84 TERM DEFINITION NM See Network Manager. Node A terminal of any branch of a netw ork, or a term inal comm on to two or m ore branches. Node Number This is the EDACS Node Num ber which uniquely specif ies an IMC/CEC/StarGate in the EDACS network.
GLOSSARY LBI-39169 85 TERM DEFINITION enables the RSM computer to request status information from radios within the network. Router A sy stem us ed to connect separate LANs and WA Ns into an internet, and to route traff ic between th e networks. In the Network Manager system , a router is needed to go from Ethernet to T1 physical m edia.
LBI-39169 GLOSSARY 86 TERM DEFINITION SNMP See Simple Network Management Protocol. StarGate In EDACS trunking, links up to eight EDACS w id e-area multisite networks to create a single, seamless network. StarGate Controller A StarGate Contro ller is an IMC sw itch specifically con figured for distributed multisite operation.
GLOSSARY LBI-39169 87 TERM DEFINITION login information is databased to allow the CEC/IMC to track individual radio units as they mov e from system -to-sy stem.
LBI-39169 INDEX 88 17. INDEX —A— Accounting Management, 14 Transferring Device Files, 42 Adding a Connection, 68 Adding Custom Menu Items, 60 Adding Descriptions To Objects, 69 Adding Object Descr.
INDEX LBI-39169 89 Introduction, 13 —J— Jessica Manuals, 12 —L— Line Graphs, 47 Loading MIBs, 64 Loading/Unloading MIBS, 60 logging Out of Network Manager, 22 Login Screen, 21 —M— Managing.
LBI-39169 INDEX Ericsson Inc. Private Radio Systems Mountain View Road Lynchburg, Virginia 24502 1-800-592-7711 (Outside USA, 804-592-7711) Printed in U.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Ericsson LBI-39169 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Ericsson LBI-39169 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Ericsson LBI-39169 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Ericsson LBI-39169 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Ericsson LBI-39169, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Ericsson LBI-39169.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Ericsson LBI-39169. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Ericsson LBI-39169 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
