DOCSLIB.ORG

Lenovo Chassis Management Module 2 Command-Line Interface Reference Guide Note

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lenovo Chassis Management Module 2 Command-Line Interface Reference Guide Note Lenovo Chassis Management Module 2 Command-Line Interface Reference Guide Note Before using this information and the product it supports, read the general information in Appendix B “Notices” on page 491, the Warranty Information document, and the Safety Information and the Environmental Notices and User Guide documents on the Lenovo documentation CD. Nineth Edition (May 2019) © Copyright Lenovo 2016, 2019. LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is delivered pursuant to a General Services Administration (GSA) contract, use, reproduction, or disclosure is subject to restrictions set forth in Contract No. GS-35F-05925. Contents Chapter 1. Introduction . 1 chlog command . 83 Before you begin . 1 chmanual command . 86 Notices and statements in this document . 2 cimsub command . 88 Accessibility features for the Lenovo Flex System cin command . 91 CMM . 2 cinstatus command . 97 clear command . 98 Chapter 2. Command-line interface clearlog command. 100 use and reference . 5 config command . 102 Command-line interface guidelines . 5 console command. 107 Command targets . 6 coolingzones command . 108 Commands and user authority . 10 crypto command . 110 Cabling the CMM . 15 date command . 113 Networked connection . 16 dhcpinfo command . 115 Direct client connection . 16 displaylog command . 119 Serial cable connection . 16 displaysd command . 125 Starting the command-line interface . 17 dns command . 127 CMM network access tag . 18 env command . 131 IPv6 addressing for initial connection . 19 ethoverusb command . 136 Telnet connection . 20 events command . 138 Serial connection . 21 exit command . 141 Secure Shell (SSH) connection . 21 files command . 141 CMM ports . 24 fod command . 143 Configuring Lenovo Flex System chassis components by using the CLI . 25 fruactlog command . 144 Configuring the CMM for CLI operation . 26 fsmcm command . 145 Serial over LAN . 28 fuelg command . 147 Starting an SOL session. 28 groups command . 159 Ending an SOL session . 29 health command . 164 Specifying a URL for file transfer . 29 help command . 171 External authentication of certificates . 30 history command . 173 Importing an LDAP certificate with non-mutual ifconfig command . 174 authentication. 33 info command . 202 Importing an LDAP certificate with mutual iocomp command . 209 authentication. 34 ldapcfg command . 211 led command . 221 Chapter 3. Command reference . 37 list command. 224 accesscontrol command . 37 monalerts command . 226 accseccfg command. 39 ntp command . 235 advfailover command . 49 permgroups command . 238 airfilter command . 51 ping command . 242 alarm command. 52 pmpolicy command . 245 alertcfg command . 56 portcfg command . 247 alertentries command . 58 ports command . 250 autoftp command . 63 power command . 264 baydata command . 66 pwrprofile command . 271 bootmode command. 71 read command . 280 bootseq command . 73 remotechassis command . 285 chconfig command . 76 © Copyright Lenovo 2016, 2019 i reset command . 289 displaysd command errors . 429 scale command . 291 dns command errors . 430 sddump command . 296 env command errors . 431 sdemail command . 297 ethoverusb command errors . 431 security command. 298 events command errors. 431 service command . 301 exit command errors . 432 smtp command . 304 files command errors. 432 snmp command . 306 fod command errors . 433 sol command. 319 fruactlog command errors. 433 sshcfg command . 326 fsmcm command errors . 434 sslcfg command . 328 fuelg command errors . 434 syslog command . 346 groups command errors . 437 tcpcmdmode command . 351 health command errors . 438 temps command . 354 help command errors . 439 trespass command . 355 history command errors . 439 uicfg command . 357 ifconfig command errors . 439 update command . 361 info command errors . 444 uplink command . 368 iocomp command errors . 444 users command. 372 ldapcfg command errors . 445 vlan command . 391 led command errors . 445 volts command . 403 list command errors . 446 write command . 404 monalerts command errors . 446 ntp command errors . 446 Chapter 4. Error messages . 407 permgroups command errors . 447 Common errors . 407 ping command errors . 449 accseccfg command errors . 409 pmpolicy command errors . 449 advfailover command errors . 411 portcfg command errors . 449 airfilter command errors . 411 ports command errors . 450 alarm command errors . 411 power command errors . 452 alertcfg command errors . 412 pwrprofile command errors . 453 alertentries command errors . 412 read command errors . 456 autoftp command errors . 413 remotechassis command errors . 457 baydata command errors . 414 reset command errors . 457 bootmode command errors . 414 scale command errors . 459 bootseq command errors . 415 sddump command errors . 459 chconfig command errors . 416 sdemail command errors . 460 chlog command errors . 418 security command errors . 460 chmanual command errors . 418 service command errors . 461 cimsub command errors . 419 smtp command errors . 461 cin command errors . 419 snmp command errors . 462 cinstatus command errors . 420 sol command errors . 463 clear command errors . 421 sshcfg command errors . 464 clearlog command errors . 422 sslcfg command errors . 465 config command errors . 422 syslog command errors. 469 console command errors . 423 tcpcmdmode command errors . 470 coolingzones command errors . 423 temps command errors . 470 crypto command errors. 424 trespass command errors . 471 date command errors . 425 uicfg command errors . 471 dhcpinfo command errors . 426 update command errors . 472 displaylog command errors . 427 uplink command errors . 476 ii Lenovo Chassis Management Module 2 Command-Line Interface Reference Guide users command errors . 477 Electronic emission notices . 494 vlan command errors. 481 Federal Communications Commission (FCC) volts command errors . 484 statement . 494 write command errors . 484 Industry Canada Class A emission compliance statement . 494 Appendix A. Getting help and Avis de conformité à la réglementation technical assistance . 487 d'Industrie Canada. 494 Australia and New Zealand Class A Before you call . 487 statement . 494 Using the documentation . 488 European Union EMC Directive conformance Getting help and information from the World Wide statement . 494 Web . 488 Germany Class A statement . 495 How to send service data . 488 Japanese electromagnetic compatibility Creating a personalized support web page . 488 statements . 496 Software service and support . 488 Korea Communications Commission (KCC) Hardware service and support . 489 statement . 496 Taiwan product service . 489 Russia Electromagnetic Interference (EMI) Class A statement . 496 Appendix B. Notices. 491 People's Republic of China Class A electronic emission statement . 497 Trademarks . 492 Taiwan Class A compliance statement . 497 Important notes . 492 Taiwan BSMI RoHS declaration . 498 Recycling information . 492 Particulate contamination ..
Load more

Recommended publications
  • Powerview Command Reference
    PowerView Command Reference TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PowerView User Interface ............................................................................................................ PowerView Command Reference .............................................................................................1 History ...................................................................................................................................... 12 ABORT ...................................................................................................................................... 13 ABORT Abort driver program 13 AREA ........................................................................................................................................ 14 AREA Message windows 14 AREA.CLEAR Clear area 15 AREA.CLOSE Close output file 15 AREA.Create Create or modify message area 16 AREA.Delete Delete message area 17 AREA.List Display a detailed list off all message areas 18 AREA.OPEN Open output file 20 AREA.PIPE Redirect area to stdout 21 AREA.RESet Reset areas 21 AREA.SAVE Save AREA window contents to file 21 AREA.Select Select area 22 AREA.STDERR Redirect area to stderr 23 AREA.STDOUT Redirect area to stdout 23 AREA.view Display message area in AREA window 24 AutoSTOre ..............................................................................................................................
    [Show full text]
  • Lab Intro to Console Commands
    New Lab Intro to KDE Terminal Konsole After completing this lab activity the student will be able to; Access the KDE Terminal Konsole and enter basic commands. Enter commands using a typical command line interface (CLI). Explain the use of the following commands, ls, ls –al, dir, mkdir, whoami, Explain the directory structure of a typical user. This lab activity will introduce you to one of the many command line interfaces available in Linux/UNIX operating systems and a few of the most basic commands. The command line interface you will be using for this lab activity is the console called the Konsole and is also referred to as Terminal. Note: As you notice, in the KDE system many features are written with the capital letter “K” in place of the first letter or the utility to reflect the fact it was modified for the KDE system. The original UNIX system did not use a graphical user interface GUI but rather was a command line interface (CLI) similar to the command prompt in Windows operating systems. The command line interface is referred to as a shell. Even today the command line interface (the shell) is used to issue commands on a Linux server to minimize system resources. For example, there is no need to start the GUI on the server to add a new user to an existing system. Starting the GUI will reduce the system performance because it requires RAM to run the GUI. A GUI will affect the overall performance of the server when it is supporting many users (clients).
    [Show full text]
  • UEFI Shell Specification
    UEFI Shell Specification January 26, 2016 Revision 2.2 The material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material or to any contribution thereto. The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this information is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses and of lack of negligence, all with regard to this material and any contribution thereto. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." The Unified EFI Forum, Inc. reserves any features or instructions so marked for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SPECIFICATION AND ANY CONTRIBUTION THERETO. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR ANY CONTRIBUTION THERETO BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS DOCUMENT, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Linux Networking 101
    The Gorilla ® Guide to… Linux Networking 101 Inside this Guide: • Discover how Linux continues its march toward world domination • Learn basic Linux administration tips • See how easy it can be to build your entire network on a Linux foundation • Find out how Cumulus Linux is your ticket to networking freedom David M. Davis ActualTech Media Helping You Navigate The Technology Jungle! In Partnership With www.actualtechmedia.com The Gorilla Guide To… Linux Networking 101 Author David M. Davis, ActualTech Media Editors Hilary Kirchner, Dream Write Creative, LLC Christina Guthrie, Guthrie Writing & Editorial, LLC Madison Emery, Cumulus Networks Layout and Design Scott D. Lowe, ActualTech Media Copyright © 2017 by ActualTech Media. All rights reserved. No portion of this book may be reproduced or used in any manner without the express written permission of the publisher except for the use of brief quotations. The information provided within this eBook is for general informational purposes only. While we try to keep the information up- to-date and correct, there are no representations or warranties, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the information, products, services, or related graphics contained in this book for any purpose. Any use of this information is at your own risk. ActualTech Media Okatie Village Ste 103-157 Bluffton, SC 29909 www.actualtechmedia.com Entering the Jungle Introduction: Six Reasons You Need to Learn Linux ....................................................... 7 1. Linux is the future ........................................................................ 9 2. Linux is on everything .................................................................. 9 3. Linux is adaptable ....................................................................... 10 4. Linux has a strong community and ecosystem ........................... 10 5.
    [Show full text]
  • How to Change the ADNP/9200 Factory-Set IP Address for LAN2
    DIL/NetPC ADNP/9200 – microHOWTO How to change the ADNP/9200 Factory-Set IP Address for LAN2 The IP address for the ADNP/9200 LAN2 Ethernet interface is based on a U-Boot environment variable. The factory-set value for this default IP address is 192.168.1.126. Please see also: mHTA9200-05.pdf: How to change the U-Boot IP Addresses for the LAN1 Ethernet Interface and mHTA9200-04.pdf: How to change the ADNP/9200 Factory-Set IP Address for LAN1 (ipaddree usage). • 1. Step: Set the ADNP/9200 RCM jumper for RCM enable. Then power-up your ADNP/9200 and interrupt the U-Boot auto boot process. Change to the U-Boot command line interface. Then enter the U-Boot command printenv. U-Boot> printenv bootargs=console=ttyS0,115200 root=/dev/ram bootdelay=3 baudrate=115200 ethaddr=02:80:ad:20:57:23 ethaddr2=02:80:ad:20:57:24 bootfile="img-dnp9200" netmask=255.255.255.0 ipaddr=192.168.0.126 ipaddr2=192.168.1.126 bootcmd=bootm 0x10040000 serverip=192.168.0.1 stdin=serial stdout=serial stderr=serial Environment size: 300/4092 bytes U-Boot> • 2. Step: The U-Boot command setenv <name> allows you to change the value for an environ- ment variable. The command saveenv stores the new value in the ADNP/9200 flash memory. U-Boot> setenv ipaddr2 192.168.3.126 U-Boot> saveenv Saving Environment to Flash... Un-Protected 1 sectors Erasing Flash... done Erased 1 sectors Writing to Flash... done Protected 1 sectors U-Boot> • 3.
    [Show full text]
  • Freebsd Command Reference
    FreeBSD command reference Command structure Each line you type at the Unix shell consists of a command optionally followed by some arguments , e.g. ls -l /etc/passwd | | | cmd arg1 arg2 Almost all commands are just programs in the filesystem, e.g. "ls" is actually /bin/ls. A few are built- in to the shell. All commands and filenames are case-sensitive. Unless told otherwise, the command will run in the "foreground" - that is, you won't be returned to the shell prompt until it has finished. You can press Ctrl + C to terminate it. Colour code command [args...] Command which shows information command [args...] Command which modifies your current session or system settings, but changes will be lost when you exit your shell or reboot command [args...] Command which permanently affects the state of your system Getting out of trouble ^C (Ctrl-C) Terminate the current command ^U (Ctrl-U) Clear to start of line reset Reset terminal settings. If in xterm, try Ctrl+Middle mouse button stty sane and select "Do Full Reset" exit Exit from the shell logout ESC :q! ENTER Quit from vi without saving Finding documentation man cmd Show manual page for command "cmd". If a page with the same man 5 cmd name exists in multiple sections, you can give the section number, man -a cmd or -a to show pages from all sections. man -k str Search for string"str" in the manual index man hier Description of directory structure cd /usr/share/doc; ls Browse system documentation and examples. Note especially cd /usr/share/examples; ls /usr/share/doc/en/books/handbook/index.html cd /usr/local/share/doc; ls Browse package documentation and examples cd /usr/local/share/examples On the web: www.freebsd.org Includes handbook, searchable mailing list archives System status Alt-F1 ..
    [Show full text]
  • Linux Kung Fu Introduction
    Linux Kung Fu Introduction What is Linux? What is the difference between a client and a server? What is Linux? ▪ Linux generally refers to a group of Unix-like free and open-source operating system distributions that use the Linux kernel. ▪ Examples of Linux distributions: – Arch Linux – CentOS – Debian – Fedora – Linux Mint – Red Hat Enterprise Linux (RHEL) – Slackware Linux – Ubuntu Servers versus Clients ▪ Servers provide services ▪ Clients consume services ▪ Examples: ▪ Examples: – Database servers – Laptops and personal computers – DHCP servers – Cellular phones – DNS servers – Tablets and iPads – File servers – Mail servers – Web servers The Terminal The Terminal ▪ Your shell prompt can be a useful source of information. ▪ The shell prompt can be customized. – This can be done by changing the variable $PS1. ▪ You enter commands in the terminal. The Terminal ▪ you@ubnetdef:~$ – Username: you – Host name: ubnetdef – Current working directory: ~ – Superuser: No ($) ▪ root@universe:/etc/init.d# – Username: root – Host name: universe – Current working directory: /etc/init.d – Superuser: Yes (#) Basic Linux Commands $ pwd ▪ The pwd command prints the name of the current working directory. – Essentially, it tells you where you are. ▪ $ sjames5@ubnetdef:~$ pwd – /home/sjames5 $ echo ▪ The echo command echoes (or displays) text. – $ echo “I love the terminal!” ▪ The text is sent to standard output by default, but can be redirected. – $ echo “Why did you redirect me?” > redirect.txt $ clear ▪ The clear command clears the terminal’s screen if possible. $ ls ▪ The ls command lists the contents of a directory. – $ ls – $ ls /etc ▪ To include hidden entries: – $ ls -a – $ ls -A ▪ Did you want more information? – $ ls -l ▪ They can even be used together! – $ ls -Al /var $ cd ▪ The cd command can be used to change your current working directory.
    [Show full text]
  • Commands with the Answers
    Catonsville Ubuntu-MD Loco Meeting October 22, 2016 1. View the file /var/log/syslog one page at a time a. cat /var/log/syslog |more 2. Declare variables for /var/log/syslog and /etc/logrotate.conf a. SYSLOG=”/var/log/syslog” b. LOGROTATE=”/etc/logrotate.conf” 3. View the first 5 lines of /var/log/syslog using the declared variable a. head -n5 $SYSLOG 4. View a live view of the last 5 lines of /var/log/syslog using the declared variable a. tail -n5 -f $SYSLOG 5. Search for all instances of the words log and rotate in /etc/logrotate.conf using the declared variable a. grep –Ew ‘log|rotate’ $LOGROTATE 6. Count all instances of the word log or rotate in /etc/logrotate.conf using the declared variable a. grep –Ewc ‘log|rotate’ $LOGROTATE 7. Count all instances of blank lines in /etc/logrotate.conf using the declared variable a. grep –c ‘^$’ $LOGROTATE 8. Count all the words in /etc/logrotate.conf using the declared variable a. cat $LOGROTATE | wc -w 9. Create a new group account… student a. groupadd student 10. Create a new standard user account… student1, primary group is student a. useradd –gstudent student1 11. Create a new privileged user account… instructor a. useradd –Gsudo instructor 12. Create a new directories called projects, assignments, quizzes, tests in /data a. mkdir –p /data/{projects,assignments,quizzes,tests} 13. Assign all files created in quizzes and tests directories with the group instructor a. chmod g+s /data/{quizzes,tests} 14. Create new files called assignment_1.txt thru assignment_9.txt in the home directory a.
    [Show full text]
  • LESSON 2 ESSENTIAL COMMANDS Lesson 2: Essential Commands
    LESSON 2 ESSENTIAL COMMANDS Lesson 2: Essential Commands WARNING The Hacker Highschool Project is a learning tool and as with any learning tool there are dangers. Some lessons, if abused, may result in physical injury. Some additional dangers may also exist where there is not enough research on possible effects of emanations from particular technologies. Students using these lessons should be supervised yet encouraged to learn, try, and do. However ISECOM cannot accept responsibility for how any information herein is abused. The following lessons and workbooks are open and publicly available under the following terms and conditions of ISECOM: All works in the Hacker Highschool Project are provided for non-commercial use with elementary school students, junior high school students, and high school students whether in a public institution, private institution, or a part of home-schooling. These materials may not be reproduced for sale in any form. The provision of any class, course, training, or camp with these materials for which a fee is charged is expressly forbidden without a license, including college classes, university classes, trade-school classes, summer or computer camps, and similar. To purchase a license, visit the LICENSE section of the HHS web page at http://www.hackerhighschool.org/licensing.html. The Hacker Highschool Project Project is an open community effort and if you find value in this project, we ask that you support us through the purchase of a license, a donation, or sponsorship. 2 Lesson 2: Essential Commands Table
    [Show full text]
  • CS252: Systems Programming
    CS252: Systems Programming Gustavo Rodriguez-Rivera Computer Science Department Purdue University General Information Web Page: http://www.cs.purdue.edu/homes/cs252 Office: LWSN1210 E-mail: [email protected] Textbook: Book Online: “Introduction to Systems Programming: a Hands-on Approach” https://www.cs.purdue.edu/homes/grr/SystemsProgrammingBook/ Recommended: Advanced Programming in the UNIX Environment by W. Richard Stevens. (Useful for the shell. Good as a reference book.) Mailing List We will use piazza PSOs There is lab the first week. The projects will be explained in the labs. TAs office hours will be posted in the web page. Grading Grade allocation Midterm: 25% Final: 25% Projects and Homework: 40% Attendance 10% Exams also include questions about the projects. Course Organization 1. Address space. Structure of a Program. Text, Data, BSS, Stack Segments. 2. Review of Pointers, double pointers, pointers to functions 3. Use of an IDE and debugger to program in C and C++. 4. Executable File Formats. ELF, COFF, a.out. Course Organization 5. Development Cycle, Compiling, Assembling, Linking. Static Libraries 6.Loading a program, Runtime Linker, Shared Libraries. 7. Scripting Languages. sh, bash, basic UNIX commands. 8. File creation, read, write, close, file mode, IO redirection, pipes, Fork, wait, waitpid, signals, Directories, creating, directory list Course Organization 9. Project: Writing your own shell. 10. Programming with Threads, thread creation. 11. Race Conditions, Mutex locks. 12. Socket Programming. Iterative and concurrent servers. 13. Memory allocation. Problems with memory allocation. Memory Leaks, Premature Frees, Memory Smashing, Double Frees. Course Organization 14. Introduction to SQL 15. Source Control Systems (CVS, SVN) and distributed (GIT, Mercurial) 16.
    [Show full text]
  • Ip COMMAND CHEAT SHEET
    ip COMMAND MODIFYING ADDRESS AND LINK PROPERTIES CHEAT SHEET SUBCOMMAND DESCRIPTIONS AND TASKS addr add Add an address for Red Hat Enterprise Linux ip addr add 192.168.1.1/24 dev em1 Add address 192.168.1.1 with netmask 24 to device em1 addr del Delete an address IP QUERIES ip addr del 192.168.1.1/24 dev em1 SUBCOMMAND DESCRIPTIONS AND TASKS Remove address 192.168.1.1/24 from device em1 addr Display IP Addresses and property information link set Alter the status of the interface (abbreviation of address) ip link set em1 up ip addr Bring em1 online Show information for all addresses ip link set em1 down ip addr show dev em1 Bring em1 offline Display information only for device em1 ip link set em1 mtu 9000 Set the MTU on em1 to 9000 link Manage and display the state of all network interfaces ip link set em1 promisc on Enable promiscuous mode for em1 ip link Show information for all interfaces ip link show dev em1 Display information only for device em1 ADJUSTING AND VIEWING ROUTES ip -s link SUBCOMMAND DESCRIPTIONS AND TASKS Display interface statistics route add Add an entry to the routing table Display and alter the routing table route ip route add default via 192.168.1.1 dev em1 ip route Add a default route (for all addresses) via the local gateway List all of the route entries in the kernel 192.168.1.1 that can be reached on device em1 ip route add 192.168.1.0/24 via 192.168.1.1 maddr Manage and display multicast IP addresses Add a route to 192.168.1.0/24 via the gateway at 192.168.1.1 ip maddr ip route add 192.168.1.0/24 dev em1 Display
    [Show full text]
  • Network Troubleshooting Methodology
    NETWORK CONCEPTS 1.8 Implement the following network troubleshooting methodology: Network Troubleshooting Procedure 1. Establish the symptoms. 2. Identify the affected area. 3. Establish what has changed. 4. Select the most probable cause. 5. Implement a solution. 6. Test the result. 7. Recognize the potential effects of the solution. 8. Document the solution. 1 Establish the Symptoms •Determine exactly what is going wrong, and note the effect of the problem on the network. •Assign a priority to the problem. •In a large network environment, it is essential to establish a system of priorities that dictate which calls get addressed first. •Most often, the severity of the problem determines who gets attention first. 2 Rules for Establishing Priorities •Shared resources take precedence over individual resources. •Network-wide problems take precedence over workgroup or departmental problems. •Departmental issues should be rated according to the function of the department. •System-wide problems take precedence over application problems. 3 Identify the Affected Area •See if the problem can be duplicated. •Network problems that you can easily duplicate are far easier to fix, primarily because you can easily test to see if your solution was successful. •Having the user reproduce the problem can sometimes lead to the solution. •If the problem can be duplicated, you can start determining the actual source of the problem. 4 •Eliminate the elements that are not the cause, in a logical and methodical manner. Establish What Has Changed •When a computer or other network component that used to work properly now does not work, some change has probably occurred. •Major changes, such as the installation of new hardware or software, are obvious possible causes of the problem.
    [Show full text]