DOCSLIB.ORG

Junos Troubleshooting in the NOC 12.B

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Junos Troubleshooting in the NOC 12.B Junos Troubleshooting in the NOC 12.b Lab Guide Worldwide Education Services 1133 Innovation Way Sunnyvale, CA 94089 USA 408-745-2000 www.juniper.net Course Number: EDU-JUN-JTNOC This document is produced by Juniper Networks, Inc. This document or any part thereof may not be reproduced or transmitted in any form under penalty of law, without the prior written permission of Juniper Networks Education Services. Juniper Networks, theJuniper Networks logo. Junos. NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Jnc. in the United States and other countries. All other trademarks, service marks, registered trademarks. or registered service marks are the propertyof their respective owners. Junos Troubleshooting in the NOC Lab Guide, Revision 12.b Copyright© 2014Juniper Networks, Inc. All rights reserved. Printed in USA. Revision History: Revision 10.a-December 2010 Revision 11.a-June 2011 Revision 12.a-March 2013 Revision 12.b-January 2014 The information in this document is current as of the date listed above. The information in this document has been carefully verified and is believed to be accurate for software Release 12.2R2.5. Juniper Networks assumes no responsibilities for any inaccuracies that may appear in this document. In no event willJuniper Networks be liable for direct. indirect, special, exemplary, incidental, or consequential damages resulting from any defect or omission in this document, even if advised of the possibility of such damages. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. YEAR 2000 NOTICE Juniper Networks hardware and software products do not suffer from Year 2000 problems and hence are Year 2000 compliant. The Junos operating system has no known time-related limitations through the year 2038. However. the NTP application is known to have some difficulty in the year 2036. SOFTWARELICENSE The terms and conditions for using Juniper Networks software are described in the software license provided with the software. or to the extent applicable, in an agreement executed between you andJuniper Networks, orJuniper Networks agent. By usingJuniper Networks software, you indicate that you understand and agree to be bound by its license terms and conditions. Generally speaking, the software license restricts the manner in which you are permitted to use theJuniper Networks software, may contain prohibitions against certain uses, and may state conditions under which the license is automatically terminated. You should consult the software license for further details. Contents Lab 1: The Troubleshooting Process ..................................... 1-1 Part 1: Troubleshooting Scenario 1 .......................................................... 1·2 Part 2: Troubleshooting Scenario 2 .......................................................... 1-4 Part 3: Troubleshooting Scenario 3 .......................................................... 1-6 Lab 2: Identifying Hardware Components ................................. 2-1 Part 1: Logging In Using the CU ............................................................. 2-2 Part 2: Verifying Initial Device Configuration ................................................... 2-3 Part3: Identifying Hardware and Key Components ............................................. 2-7 Part 4: Utilizing Online Resources............ ................................................ 2-9 Lab 3: Using Monitoring Tools and Establishing a Baseline .................. 3-1 Part 1: Viewing Alarms, Environmental Conditions, and Hardware Inventory ......................... 3-2 Part 2: Establishing a Baseline .............................................................. 3-9 Part 3: Locating Online Resources .......................................................... 3-17 Lab 4: Monitoring Hardware and Environmental Conditions .................. 4-1 Part 1: Monitoring Memory and Storage ...................................................... 4-2 Part 2: Viewing Boot and System Logs ........................................................ 4-7 Part 3: Monitoring the Chassis and Environment .............................................. 4-13 Lab 5: Control Plane Monitoring and Troubleshooting ....................... 5-1 Part 1: Examining User Processes and Daemons ............................................... 5-2 Part 2: Generating Core Files .............................................................. 5-10 Part 3: Configuring Routing Protocols and Routing Tables ....................................... 5-13 Part 4: Configuring Bridging ............................................................... 5-27 Lab 6: Monitoring and Troubleshooting Ethernet Interfaces .................. 6-1 Part 1: Performing Interface Troubleshooting .................................................. 6-2 Part 2: Performing Loopback Testing ........................................................ 6-13 Part 3: Configuring Ethernet OAM ...........................................................6-19 Lab 7: Isolating and Troubleshooting PFE Issues ........................... 7-1 Part 1: Examining the Forwarding Table ...................................................... 7-2 Part 2: Configuring Load Balancing .......................................................... 7-7 Part 3: Troubleshooting Firewall Filters ...................................................... 7-11 Lab 8: Troubleshooting Routing Protocols ................................ 8-1 Part 1: Modifying the Existing Configurations .................................................. 8-2 Part 2: Troubleshooting OSPF Adjacencies ......................•••••......................... 8-3 Part 3: Troubleshooting BGP Sessions ....................................................... 8-19 Part 4: Troubleshooting Routing Loops ..........................•........................... 8-34 Lab 9: Monitoring the Network .......................................... 9-1 Part 1: Modifying the Existing Configurations .................................................. 9-2 Part 2: Configuring and Monitoring SNMP .......................•.........••.....•............ · 9-3 Part 3: Configuring and Monitoring RMON .................................................... 9·11 Part 4: Configuring and Monitoring In line JFlow ............................................... 9-19 Part 5: Configuring and Monitoring Inline Port Mirroring .............•.......................... 9-23 www.juniper.net Contents • iii iv • Contents www.juniper.net Course Overview This three-day course is designed to provide introductory troubleshooting skills for engineers in a network operations center (NOC) environment. Key topics within this course include troubleshooting methodology, troubleshooting tools, hardware monitoring and troubleshooting, interface monitoring and troubleshooting, troubleshooting the data plane and control plane on devices running the Junos operating system, staging and acceptance methodology, troubleshooting routing protocols, monitoring the network, and working with JTAC. This course is based on Ju nos operating system Release 12.2R2.5. Objectives After successfully completing this course, you should be able to: Reduce the time it takes to identify and isolate the root cause of an issue impacting your network. Gain familiarity with Ju nos products as they pertain to troubleshooting. Become familiar with online resources valuable to Junos troubleshooting. Gain familiarity with Junos tools used in troubleshooting. Identify and isolate hardware issues. Troubleshoot problems with the control plane. Troubleshoot problems with interfaces and other data plane components. Describe the staging and acceptance methodology. Troubleshoot routing protocols. Describe how to monitor your network with SNMP, RMON, JFlow, and port mirroring. Become familiar with JTAC procedures. Intended Audience The course content is aimed at operators of devices running the Junos OS in a NOC environment. These operators include network engineers, administrators, support personnel, and reseller support personnel. Course Level Junos Troubleshooting in the NOC is an introductory-level course. Prerequisites Students should have basic networking knowledge and an understanding of the Open Systems Interconnection (OSI) reference model and the TCP/IP protocol suite. Students should also attend the Introduction to the Junos Operating System (IJOS) course and the Junos Routing Essentials (JRE) course, or have equivalent experience prior to attending this class. www.juniper.net Course Overview • v Course Agenda Day1 Chapter 1: Course Introduction Chapter 2: Troubleshooting as a Process The Troubleshooting Process Lab Chapter 3: Junos Product Families Identifying Hardware Components Lab Chapter 4: Troubleshooting Toolkit Monitoring Tools and Establishing a Baseline Lab Day2 Chapter 5: Hardware and Environmental Conditions Monitoring Hardware and Environmental Conditions Lab Chapter 6: Control Plane Control Plane Monitoring and Troubleshooting Lab Chapter 7: Data Plane: Interfaces Monitoring and Troubleshooting Ethernet Interfaces Lab Chapter 8: Data Plane: Other Components Isolating and Troubleshooting PFE Issues Lab Day3 Chapter 9: Staging and Acceptance Testing Chapter 10: Troubleshooting Routing Protocols Troubleshooting Routing Protocols Lab Chapter 11: High Availability Chapter 12: Network Monitoring Monitoring the Network Lab Chapter 13: JTAC Procedures Appendix A: Interface Troubleshooting vi • Course Agenda www.juniper.net Document Conventions CLI
Load more

Recommended publications
  • Polycom Realpresence Collaboration Server (RMX) Deployment Guide for Maximum Security Environments
    [Type the document title] Military Unique Deployment Guide Version 8.3.0.J May 2014 | DOC2714B Polycom® RealPresence® Collaboration Server (RMX) 1500/2000/4000 Deployment Guide for Maximum Security Environments Polycom Document Title 1 Trademark Information POLYCOM® and the names and marks associated with Polycom's products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. This software has achieved UC APL certification. This document provides the latest information for security-conscious users running Version 8.3.0.J software. The information in this document is not intended to imply that DoD or DISA certifies Polycom RMX systems. Support Information For support on your Polycom systems, contact Polycom Global Services at 1-888-248-4143 or go to the Polycom Support Contact page (http://support.polycom.com/PolycomService/support/us/support/ Contact_Us.html). Documentation Feedback Polycom appreciates your help as we work to improve its product documentation. Send your comment to [email protected]. © 2014 Polycom, Inc. All rights reserved. Polycom, Inc. 6001 America Center Drive San Jose CA 95002 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format.
    [Show full text]
  • Polycom RMX™ 2000/4000 Administrator's Guide
    Polycom RMX™ 2000/4000 Administrator’s Guide Version 5.0 | December 2009 | DOC2518B Trademark Information Polycom®, the Polycom “Triangles” logo, and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common-law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. Portions, aspects and/or features of this product are protected under United States Patent Law in accordance with the claims of United States Patent No: US 6,300,973; US 6,492,216; US 6,496,216; US 6,757,005; US 6,760,750; US 7,054,620; US 7,085,243; US 7,113,200; US 7,269,252; US 7,310,320. PATENT PENDING © 2009 Polycom, Inc. All rights reserved. Polycom, Inc. 4750 Willow Road Pleasanton, CA 94588-2708 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc., retains title to and ownership of all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g., a book or sound recording).
    [Show full text]
  • Irmx Installation and Startup
    iRMX® Installation and Startup RadiSys Corporation 5445 NE Dawson Creek Drive Hillsboro, OR 97124 (503) 615-1100 FAX: (503) 615-1150 www.radisys.com 07-0683-01 December 1999 EPC, iRMX, INtime, Inside Advantage, and RadiSys are registered trademarks of RadiSys Corporation. Spirit, DAI, DAQ, ASM, Brahma, and SAIB are trademarks of RadiSys Corporation. Microsoft and MS-DOS are registered trademarks of Microsoft Corporation and Windows 95 is a trademark of Microsoft Corporation. IBM and PC/AT are registered trademarks of International Business Machines Corporation. Microsoft Windows and MS-DOS are registered trademarks of Microsoft Corporation. Intel is a registered trademark of Intel Corporation. All other trademarks, registered trademarks, service marks, and trade names are property of their respective owners. December 1999 Copyright 1999 by RadiSys Corporation All rights reserved. ii Quick Contents Section I. Choosing Your Installation Chapter 1. Introduction Section II. iRMX Installation Procedures Chapter 2. Installing on iRMX development/target systems that are PC-compatible Platforms with no DOS Chapter 3. Installing on iRMX development/target systems that are PC-compatible Platforms with DOS Chapter 4. Installing on iRMX Development/Target Systems that are Multibus II Platforms Chapter 5. Installing the iRMX III OS on Multibus I Systems Chapter 6. Installing on Windows NT systems used as iRMX development systems Section III. iRMX Getting Started Chapters Chapter 7. DOSRMX Specifics Chapter 8. iRMX for PCs Specifics Chapter 9. Getting Acquainted with the Operating System Chapter 10. Where To Go From Here Section IV. Appendices Appendix A. Installed Directories Appendix B. Limitations Appendix C. Configuration Requirements for PC Platforms Appendix D.
    [Show full text]
  • Inspector D4000™ Auto Optic Operator's Guide
    ™ Inspector D4000 Auto Optic ’s Guide Operator Manual P/N 002-7856 Revision: D September 2014 THIS MANUAL APPLIES ONLY TO FIRMWARE A.10 OR LATER Use Inspector D4000 Auto Optic Manual (Rev C) for firmware versions A.06 - A.09 Use Inspector 4000 Manual (Revision H) for earlier firmware versions A.05 and earlier RJS Technologies 701 Decatur Ave North, Suite 107 Minneapolis, MN 55427 U.S.A. +1 (763) 746-8034 www.rjs1.com Copyrights The copyrights in this manual are owned by RJS. All rights are reserved. Unauthorized reproduction of this manual or unauthorized use of the Inspector D4000 software may result in imprisonment of up to one year and fines of up to $10,000.00 (17 U.S.C. 506). Copyright violations may be subject to civil liability. Reference RJS P/N 002-7856 Revision D All Rights Reserved. ’s Guide ™ Auto Optic Operator Inspector D4000 TABLE OF CONTENTS 1.0 PREFACE 1 1.1 PROPRIETARY STATEMENT 1 1.2 STATEMENT OF FCC COMPLIANCE: USA 1 1.3 STATEMENT OF FCC COMPLIANCE: CANADA 1 1.4 CE: 1 1.5 DOCUMENTATION UPDATES 1 1.6 COPYRIGHTS 1 1.7 UNPACKING AND INSPECTION 1 1.8 INSTALLING BATTERIES 2 1.9 TECHNICAL SUPPORT 3 1.10 TRADEMARKS 3 2.0 WARRANTY 4 2.1 GENERAL WARRANTY 4 2.2 WARRANTY LIMITATIONS 4 2.3 SERVICE DURING THE WARRANTY PERIOD 4 3.0 INTRODUCTION 5 3.1 RJS INSPECTOR D4000 DESCRIPTION AND FEATURES 5 3.2 MAINTENANCE 5 3.3 TEMPERATURE SPECS 5 4.0 THE RJS INSPECTOR D4000 AUTO OPTIC 6 5.0 MAIN MENU SELECTIONS 7 5.1 CALIBRATION 7 POWER ON 7 VERIFYING THAT UNIT IS CALIBRATED 7 CALIBRATING THE UNIT 7 5.2 SCAN 8 5.3 SETUP 10 5.4 STORAGE 15
    [Show full text]
  • Embedded Systems - ECE)​​ I -M.TECH I -Semester (AUTONOMOUS-R18
    Presentation on Principles of Distributed Embedded Systems (Embedded Systems - ECE)​​ I -M.TECH I -Semester (AUTONOMOUS-R18) Prepared by, Dr. S. Vinoth Associate Professor UNIT - I REAL TIME ENVIRONMENT 2 UNIT - I REAL-TIME ENVIRONMENT .Real-time computer system requirements .classification of real time systems .simplicity, global time .internal and external clock synchronization .real time model. Real time communication .temporal relations, dependability .power and energy awareness .real time communication .event triggered .rate constrained .time triggered. 3 What is an Embedded system? 4 What is a real-time system? . A real-time system is any information processing system which has to respond to externally generated input stimuli within a finite and specified period –the correctness depends not only on the logical result but also the time it was delivered –failure to respond is as bad as the wrong response! . The computer is a component in a larger engineering system => EMBEDDED COMPUTER SYSTEM 99% of all processors are for the embedded systems market 5 Terminology • Hard real-time — systems where it is absolutely imperative that responses occur within the required deadline. E.g. Flight control systems. • Soft real-time — systems where deadlines are important but which will still function correctly if deadlines are occasionally missed. E.g. Data acquisition system. • Real real-time — systems which are hard real-time and which the response times are very short. E.g. Missile guidance system. • Firm real-time — systems which are soft real-time but in which there is no benefit from late delivery of service. A single system may have all hard, soft and real real-time subsystems In reality many systems will have a cost function associated with missing each deadline.
    [Show full text]
  • RMX Release Notes 8.9.0
    RELEASE NOTES Version 8.9 | January 2020 | 3725-74103-000L Polycom® RealPresence® Collaboration Server 1800/2000/4000/Virtual Edition Polycom announces the release of the Polycom RealPresence Collaboration Server 8.9 software. This document provides the latest information about this release. Contents Contents 1 What’s New in This Release 2 System Capabilities and Constraints 4 Resource Capacities 8 Security Updates 12 Products Tested with this Release 12 Upgrade Information for the RealPresence Collaboration Server 14 Known Issues 21 Known Limitations 22 Resolved Issues 22 Copyright and Trademark Information 27 Plantronics + Polycom NOW TOGETHER AS POLY, Inc. 1 Release Notes RealPresence Collaboration Server 1800/2000/4000/Virtual Edition - Version 8.9 What’s New in This Release RealPresence Collaboration Server 8.9 includes the features and functionality of previous releases, the software fixes identified in the Resolved Issues section, and the following new features. Secure Meeting Lobby for Locked Conferences This release of the RealPresence Collaboration Server implements a secure meeting lobby option for callers that try to join an active locked conference. When implemented, the RealPresence Collaboration Server does the following: ● Puts a caller who tries to join an active locked conference into the secure meeting lobby, plays the designated IVR message, and displays the designated slide. ● Sends a notification to all conference chairpersons (with AVC endpoints) that one or more callers are waiting in the lobby. The notification identifies the most recent five callers to join the lobby by user or site name and provides a total number of callers waiting in the lobby. Callers stay in the meeting lobby until the chairperson unlocks the conference or until a designated time-duration elapses.
    [Show full text]
  • Memorandum DCL-22 Page 1 of 36 Pages Digital Computer Laborator,Y Massachusetts Institute of Technology Cambridge 39. Massachuse
    Memorandum DCL-22 Page 1 of 36 pages Digital Computer Laborator,y Massachusetts Institute of Technology Cambridge 39. Massachusetts SUBJECT: Utility Control Program To: Scientific and Engineering Computation Staff and Operators From: F. C. Helwig Date: November 22. 1954 Abstract: The S&EC Group has developed a large library of utility tapes which includes input programs, conversion programs. post-mortem programs and equipment checking programs. The more frequently used programs in thislibrar.y have been semi­ permanently recorded either on the nagmetic drums or as numbered blocks on magnetic tape. The selection and use of programs from the librar.f is initiated by a utility control program which has been semi­ pennanently recorded in group 11 of the auxiliary drum. Individual Dist:ribution List 5 .• Manber P. R. Bagley J. Ackley A.J.Roberts P.M.Arden ooL-22 page 2 Index Page 1. General. Description. 0 0 • 0 • 0 ••.• '. 0 • 0 •••• 0 ••••• '••••• e •••.•••••.• 0· ••• 6 2. The Automatic Read-In Mode. o ••••••••••••• e· •••••••••••••••••••• 6 2.1 Drum Utility Programs, .................................... 6 2.2 Utility Program Selection ••••••••••••••••••••••••••••••• 7 2.2.1 Illegal Initial Characters •••••••••••••••••••••••. 7 2.·2.2 CS I Binary Tapes ••• o. 0 ••• 00.0 ••••• 0· ~ •••••.•••.•••• 7 2,"2·.3 Fence Tapes. 0" ••••.•••.••••.•.••••••.•.•.••• 0· ••••••.•••·.·7 2.2.4 Tapes with Flexo Titles ••••••••••· •••••••••••••••• 7 2.2.4.1 Ulegal and Ignorable Characters ••••••••••. 7 2.2.4.2 CS II Binary (fb) Tapes •••.••••••••••' •••••• 8 2.2.4.:3 CS II Flexo (fc) Tapes ••••••••••••.•.••••••• 8 2.2.4.4 Post-Mortem Request (fp) Tapes •••••.•.•••• 8 2.2.4.5 Summer Session (fs) Tapes ••••••••••••••••• 8 2.2.4.• 6 Single Address Computer(f2s) Tapes •••••••.• 8 2.2.4.7 Three Address Computer (f2t) Tapes •••••••• 8 2.3 Computer Logging •••••.•• 0".0 ••• 0 ••••' ••••••••••••••••••••• 9 2.3.1 Flexo Tape Titles •• 0 ••• 0· •••••.• o ••.•.•.•••••••••••••• 9 The Various Computer Logs 0 ••' ..................'0' •• 9 2.3.2 .
    [Show full text]
  • Realpresence Collaboration Server (RMX) 1500/1800/2000/4000
    Getting Started Guide Version 8.3 | January 2014 | DOC2740A RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Trademark Information POLYCOM® and the names and marks associated with Polycom's products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. © 2014 Polycom, Inc. All rights reserved. Polycom, Inc. 6001 America Center Drive San Jose CA 95002 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc., retains title to and ownership of all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g., a book or sound recording). Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc., is not responsible for printing or clerical errors. Information in this document is subject to change without notice. i Contents Contents . i System Overview . 1 About the Polycom® RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Getting Started Guide .
    [Show full text]
  • Irmx 86™ INSTALLATION GUIDE
    iRMX 86™ INSTALLATION GUIDE Manual Number: 9803125-03 Copyright © 1980, 1981 Intel Corporation I Intel Corporation, 3065 Bowers Avenue, Santa Clara, California 95051 I REV. REVISION HISTORY PRINT DATE -01 Original Issue 4/80 -02 Update to reflect Release 2 of the iRMX 86 10/80 software and hardware requirements. -03 Update to reflect changes to support 5/81 Release 3 of the iRMX 86 Operating System; new chapter for the Start-Up System; the Files Utility chapter is moved to Chapter 8; new hardware information to support new controller boards; various minor technical and typographical errors are corrected. Additional copies of this manual or other Intel literature may be obtained from: Literature Department Intel Corporation 3065 Bowers A yen ue Santa Clara, CA 95051 The information- in this document is subject to change without notice. Intel Corporation makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Intel Corporation assumes no responsibility for any errors that may appear in this document. Intel Corporation makes no commitment to update nor to keep current the information contained in this document. Intel Corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in an Intel product. No other circuit patent licenses are implied. Intel software products are copyrighted by and shall remain the property of Intel Corporation. Use, duplication or disclosure is subject to restrictions stated in Intel's software license, or as defined in ASPR 7-104.9(a)(9).
    [Show full text]
  • Inspector D4000™ Laser Operator's Guide
    ™ Inspector D4000 Laser ’s Guide Operator Manual P/N 002-7858 Revision: E April 2018 THIS MANUAL APPLIES ONLY TO FIRMWARE A.17 OR LATER Use Inspector D4000 Laser Manual (Rev D) for firmware versions A.12 - A.16 Use Inspector D4000 Laser Manual (Rev C) for firmware versions A.10 - A.11 Use Inspector D4000 Laser Manual (Rev B) for firmware versions A.06 - A.09 Use Laser Inspector 1000 Manual for earlier firmware versions A.05 and earlier RJS Technologies 701 Decatur Ave North, Suite 107 Minneapolis, MN 55427 U.S.A. +1 (763) 746-8034 www.rjs1.com Copyrights The copyrights in this manual are owned by RJS. All rights are reserved. Unauthorized repro- duction of this manual or unauthorized use of the Inspector D4000 software may result in impris- onment of up to one year and fines of up to $10,000.00 (17 U.S.C. 506). Copyright violations may be subject to civil liability. Reference RJS P/N 002-7858 Revision E All Rights Reserved. ’s Guide ™ Laser Operator Inspector D4000 TABLE OF CONTENTS COPYRIGHTS II 1.0 PREFACE 1 1.1 PROPRIETARY STATEMENT 1 1.2 STATEMENT OF FCC COMPLIANCE: USA 1 1.3 STATEMENT OF FCC COMPLIANCE: CANADA 1 1.4 CE: 1 1.5 DOCUMENTATION UPDATES 1 1.6 COPYRIGHTS 1 1.7 UNPACKING AND INSPECTION 1 1.8 INSTALLING BATTERIES 2 1.9 TECHNICAL SUPPORT 2 1.10 TRADEMARKS 3 2.0 WARRANTY 4 2.1 GENERAL WARRANTY 4 2.2 WARRANTY LIMITATIONS 4 2.3 SERVICE DURING THE WARRANTY PERIOD 4 3.0 INTRODUCTION 5 3.1 WARNINGS 5 3.2 RJS INSPECTOR D4000 DESCRIPTION AND FEATURES 6 3.3 MAINTENANCE 7 3.3 TEMPERATURE SPECS 7 4.0 THE RJS INSPECTOR D4000 LASER 8 5.0
    [Show full text]
  • Mobile and Embedded Device
    Mobile and Embedded Device Selecting an Operating System Why use an OS? ● In our previous work we have seen how to execute a number of tasks on our system ● Some of these tasks can run asynchronously – For example interrupt driven tasks ● So if we want to exploit the resources of our system efficiently we require some software support to do this – Namely an operating system Which Operating System? ● There are a number of choices when selecting an OS – Size, cost, features ● Free – FreeRTOS: http://www.freertos.org – TinyOS: http://www.tinyos.net – Chibios: http://www.chibios.org/ – eCos, uKOS, EROS, Nut/OS – Various Linux flavours ● Commercial – VxWorks: http://www.windriver.com – QNX: http://www.qnx.com – SafeRTOS: http://www.highintegritysystems.com/safertos.html – uC/OSII: http://www.micrium.com – Salvo: http://www.pumpkininc.com – INTEGRITY, VelOSity, THEOS, RMX Why FreeRTOS ● Free (Both “Speech” and “Beer”) – No Royalties, Open Source – Although documentation costs ● Lightweight – Low overhead, simple code ● Portable – ~8 major architectures officially supported, more unofficially ● Cooperative or Preemptive – We're going to be using preemptive ● Good Documentation – http://www.freertos.org – Look under FreeRTOS API – Functional docs plus code examples ● Developed by an Ex-Student! – Richard Barry, BSc CRTS What required from an OS? ● For small embedded systems they are required to be – Small memory footprint – Efficient use of resources – Fast ● We require what is normally called an 'executive' rather than an operating system – Lots
    [Show full text]
  • INTRODUCTION to the Irmx™86 OPERATING SYSTEM
    INTRODUCTION TO THE iRMX™86 OPERATING SYSTEM Order Number: 9803124-03 Copyright © 1980, 1982, Intel Corporation J Intel Corporation, 3065 Bowers Avenue, Santa Clara, California 95051 I REV. REVISION HISTORY PRINT DATE -01 ORIGINAL ISSUE 4/80 -02 Release 2.0 of the iRMX 86 Operating System 11/80 -03 Release 4.0 of the iRMX 86 Operating System 1/82 Additional copies of this manual or other Intel literature may be obtained from: Literature Department Intel Corporation 3065 Bowers Avenue Santa Clara, CA 95051 The Information in this document is subject to change without notice. Intel Corporation makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Intel Corporation assumes no responsibility for any errors that may appear in this document. Intel Corporation makes no commitment to update nor to keep current the information contained in this document. Intel Corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in an Intel product. No other circuit patent licenses are implied. Intel software products are copyrighted by and shall remain the property of Intel Corporation. Use, duplication or disclosure is subject to restrictions stated in Intel's software license, or as defined as ASPR 7-104.9(a)(9). No part of this document may be copied or reproduced in any form or by any means without the prior written consent of Intel Corporation. The following are trademarks ofIntel Corporation and its affiliates and may be used only to identify Intel products: BXP Insite iSBC Multibus CREDIT Intel iSBX Multimodule intel Library Manager Plug-A-Bubble ICE Intelevision MCS PROMPT iCS Intellec Megachassis RMX/80 im iOSP Micromainframe System 2000 iMMX iRMX Micromap UPI IA526!182! 6K YDJ PREFACE If you are looking for a high-level introduction to the iRMX 86 Operating System, this manual will satisfy you.
    [Show full text]