DOCSLIB.ORG

Unix As an Application Server in a Network Operating System Environment

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Unix As an Application Server in a Network Operating System Environment 50-30-30 DATA COMMUNICATIONS MANAGEMENT UNIX AS AN APPLICATION SERVER IN A NETWORK OPERATING SYSTEM ENVIRONMENT Scott Koegler INSIDE Integrating with the Networking Environments, Network Server vs. Application Server, File Service, Printing across the Network, Internet/Intranet Services, Coping with a Mixed Environment INTRODUCTION Networks have evolved to become the mainstay of corporate America. Millions of personal computers are connected to network servers run- ning applications ranging from personal productivity to corporate ac- counting, yet the demands on the network continue to increase. These demands typically take two forms. The first is the availability of applica- tion software specifically tailored to the operations of an organization. The second is the need to run processor-intensive applications in a per- sonal computing environment. Both of these situations require in- creased horsepower from individual computing components, and in some cases the required horsepower is just not available from net- worked components. Today’s network architectures have been maximized to provide su- perb performance for file and print sharing tasks, but still may not always offer the level of performance required. Although the network operating system can provide network servic- es, it is not typically optimized for PAYOFF IDEA application processing. Even in those Today’s distributed systems can become highly cases where an application can be complex even when the network is homoge- run on a network server, doing so neous. Maintaining a consistent NOS environ- may degrade the performance of the ment lets network administrators develop a depth entire network, making the proposi- of understanding that often leads to better effi- ciencies in both day-to-day operations and in tion counterproductive. troubleshooting. 06/98 Auerbach Publications © 1999 CRC Press LLC Even with the stunning advances in hardware systems and program- ming techniques, many companies find that the specific applications that fit their operations were created to run in multiuser environments rather than in network environments. In many cases this is the result of migrat- ing an application from a mainframe system and resulting programs re- main optimized for the multiuser rather than networked systems. IS UNIX STILL GOOD FOR ANYTHING? UNIX has a long history in the computing world. The simple fact that it is still around must mean more than that it is just hanging on. In fact, UNIX has enjoyed a resurgence of interest over the last couple years, largely because of the growth of the Internet. But UNIX has other strengths beyond the Internet. The original advantages of UNIX were with its file system, multitask- ing kernel, and easy configurability. None of those early considerations have deteriorated, and they are still not fully duplicated in the newer op- erating systems. To be sure, both NetWare and NT have advantages with regard to market availability, commercial support, and a wide range of software options, but the basics still can be filled easily and inexpensive- ly with UNIX services. UNIX is a mature operating system and has been fairly well debugged and enjoys a wide, mostly independent, support group via the Internet. Its scalability, as of this writing, puts NetWare and NT Server in the little leagues. INTEGRATING WITH THE NETWORKING ENVIRONMENTS Networks have become commonplace, and the architecture has em- braced Ethernet as the predominant standard. Novell NetWare continues to maintain a 60% plus share of network server installations, and Mi- crosoft NT server continues to build an increasing market share. In the past, these operating systems imposed their own network protocols on their environment. Customer demand forced simplified integration, and both vendors supplied solutions and the third-party solutions, but the connectivity was generally less than seamless. The stunning rise in pop- ularity of the Internet and its associated TCP/IP protocol has had the ef- fect of forcing these two major network operating system suppliers to support this protocol as a ground-leveling standard. The net result to the user is that both Novell and Microsoft now supply the TCP/IP protocol as a part of their base product offering. In fact, Novell now offers TCP/IP as a selectable replacement for its long-standing IPX protocol. What this means in a practical sense is that it is easier than ever for an organization to implement easily a variety of operating systems based on its business needs and application requirements rather than on what the net- working vendor’s dictates. It is now commonplace to find a corporate IT shop with a mixture of Novell and Microsoft servers on the same network. WHY BOTHER WITH ANOTHER OS? Although NetWare is a highly efficient file and print server, with Internet services included as part of the file server function, it does not offer the application services available in Windows NT. NT can provide a combi- nation of file and print services along with robust application service support and Internet services as well. UNIX can supply nearly all the same facilities, and with TCP/IP now a networking mainstay, integrates into the LAN environment almost with- out being noticed. But, because there are few practical differences be- tween the available solutions, there needs to be some compelling reason to increase the complexity of the corporate LAN, even if only marginally. The most often cited reasons for installing a UNIX server in a LAN en- vironment fall into two categories: application support and price. In short, if an application is only available as a UNIX application, the choice is reduced to finding an application that runs on the existing network or installing the necessary UNIX resources. Organizations have somewhat more flexibility when installing a new application than when trying to in- tegrate a legacy system into a LAN environment. The good news in either of the situations is that connecting an existing UNIX application to a net- work is likely to be easier than either converting the function to a differ- ent application that is LAN based or redeveloping the application to run on the LAN. The combination of Windows and a good terminal emulator can deliver a very powerful combination that leverages the strengths of all the available applications and operating systems. The second powerful consideration in favor of UNIX is the wide range of vendors offering similar versions of the same operating system. A by- product of this competition is the availability of highly competent operat- ing systems at very low prices. This is not to say that all UNIX OSs are the same. Some proprietary versions, like the IBM AIX and the DG version, weigh in at the same or greater costs than the popular Network Operating Systems (NOS). But at the other end of the range are systems like the SCO UNIX and, at the extreme low end, the Calera Linux. To be sure, there are differences in the variations in both capabilities and support, and these differences need to be factored into any decision, but depending on the level of in-house expertise, nearly all can be viable solutions. One of the other things that can provide a benefit in the UNIX envi- ronment is the existence of a mature and widespread user-support com- munity. The UNIX community has been the premier example of noncommercial systems development for many years. Programs ranging from small utilities to full applications and even the operating system it- self have been available through the efforts of programmers around the world. Possibly the best example is the Linux version of UNIX, which was developed by a loosely coordinated group of programmers who each contributed his or her efforts to developing a state-of-the-art OS that is available, complete with source code, simply by downloading it. The commercial versions of Linux add several features that make this user- supported system viable in a corporate environment. But at under $500 for a full license, it is a tough competitor. OPERATIONAL CONSIDERATIONS The introduction of multiple hardware and software platforms into a computing environment is a normal, if unwelcome, reality. It increases the range of knowledge required for internal support and adds to the list of vendors involved in the organization and, because of these factors, should not be entered into simply for the sake of adding a new environ- ment. However, given a valid business reason for doing so, there are tools and systems that minimize the impact. Modern IT systems provide increased management capabilities through a variety of facilities. The availability of the Simple Network Management Protocol (SNMP) has made the management of heteroge- neous networks possible by providing a common protocol that nearly all system software and hardware vendors have implemented. With this kind of consistency, it is now possible to view a range of network servic- es through a common console. This means that the differences in man- agement of various platforms are minimized through the common interface. Day-to-day activities can be incorporated into a centralized sys- tem that decreases the load on the IT staff and reduces the integration of yet another operating system into a routine function. NETWORK SERVER VERSUS APPLICATION SERVER The role of the server needs to be taken into consideration when con- templating adding computing resources. In fact, one of the main reasons for adding a UNIX server to an existing networked environment is the different function the server will fill. In a typical networked environment, the processing load is distributed, not always evenly, across the client PCs, the server, and the network ca- ble. Client/server systems attempt to do a better job at this load distribu- tion, but these systems have never really delivered on their promise of low cost, quick development, and high performance.
Load more

Recommended publications
  • SUCCESS STORY. Security Software Porting from Netware to Novell Linux
    SUCCESS STORY. >_ >_ Security Software Porting From Netware To Novell >_ Linux About the The Client is a leader in the development of real-time monitoring, auditing and computer forensics Client technologies for Windows and Novell networks. Its ⧄agship product is used to secure the assets of the world’s largest corporations, banks, and government agencies, educational and healthcare institutions. Business The Client had a signi⣴cant install base for its ⧄agship software on Novell Netware OS. Novell’s Challenge adoption of Linux as the migration path for Netware OS created both an opportunity and a challenge for the Client. To continue supporting its Netware user base through Linux migration, the client wanted to port its monitoring and auditing solution to support SUSE Linux, Novell eDirectory and NSS (Novell Storage Services). The Client did not have in-house Linux Systems programming expertise, especially with ⣴le systems & security knowledge and approached Silicus. Silicus The software had two parts – the agent (client) and the server. The agent was a module that was Solution installed on the PC’s to be audited, and sends information on PC activities to a server installed at a centralized location. Termination of Netware required the agent to be re-developed/ported to Linux. Silicus commenced a feasibility study to address a few unknowns in the project: • Identify the auditing modules available on SuSE Linux • XML libraries that could be used • Multi-threading architecture to be used for agent development Silicus created a software architecture and design for the remote management agent. The agent was developed leveraging 3rd party tools to perform the auditing, monitoring of the Linux systems and communication with the remote server.
    [Show full text]
  • Novell Management Tools
    04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 91 CHAPTER 3 Novell Management Tools Using ConsoleOne ConsoleOne is a Java-based tool for managing your network and its resources. It can be launched by running CONSOLEONE.EXE from where it was installed (default: SYS:PUBLIC\MGMT\CONSOLEONE\1.2\BIN). By default, it lets you manage Novell eDirectory objects, schema, parti- tions, and replicas and NetWare server resources. If you install other Novell products, the appropriate management capabil- ities are automatically snapped into the version of ConsoleOne installed on that server. ConsoleOne is installed during the NetWare 6.5 installation, but can also be re-installed or installed locally from the Novell client’s CD. ConsoleOne also supports remote server console access through a Java applet called RConsoleJ. To access the NetWare 6.5 server console remotely, launch ConsoleOne and browse to the desired server. Select Tools, and then Remote Console. Accessing Web Manager Web Manager is a Web-based “home page” for accessing most of the NetWare 6.5 Web-based tools and services. To access Web Manager, open your Web browser and enter your Web server’s domain name or IP address, followed by a colon and the Web Manager port, which by default is 2200. For example: 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 92 92 PART I Getting Started https://www.quills.com:2200 or https://137.65.192.1:2200 Accessing iManager iManager provides role-based management of your NetWare network, together with a nearly comprehensive set of administrative tools.
    [Show full text]
  • Novell Cluster Services,. for Linux. and Netware
    Novell Cluster Services,. for Linux. and NetWare. ROB BASTIAANSEN SANDER VAN VUGT Novell PRESS. Novell. Published by Pearson Education, Inc. 800 East 96th Street, Indianapolis, Indiana 46240 USA Table of Contents Introduction 1 CHAPTER 1: Introduction to Clustering and High Availability 5 Novell Cluster Services Defined 5 Shared Disk Access 6 Secondary IP Addresses 7 Clustering Terminology 8 High-Availability Solutions Overview 12 Novell Cluster Services 12 Business Continuity Clustering 13 PolyServe Matrix Server 15 Heartbeat Subsystem for High-Availability Linux 16 When Not to Cluster Applications 16 Availability Defined 18 High Availability Defined 18 Calculating Average Downtime 21 Avoiding Downtime 22 Hardware 22 Environment 23 Software 23 Procedures 24 Novell Cluster Services Requirements 24 Hardware Requirements 24 Software Requirements 26 CHAPTER 2: Examining Novell Cluster Services Architecture 27 Novell Cluster Services Objects and Modules 27 Cluster eDirectory Objects 28 Cluster Modules 31 IH Novell Cluster Services for Linux and NetWare Heartbeats, Epoch Numbers, and the Split Brain Detector 35 Removing a Failing Slave Node 36 Removing a Failed Master Node 37 Summary 37 CHAPTER 3: Clustering Design 39 Cluster Design Guidelines 39 How Many Nodes to Choose 39 Using a Heartbeat LAN or Not 40 Use NIC Teaming 41 Choosing Storage Methods 42 Mirror the Split Brain Detector Partition 48 Selecting Applications to Run in a Cluster 48 eDirectory Cluster Guidelines 50 Creating a Failover Matrix 52 Application-Specific Design Guidelines
    [Show full text]
  • KUNCI JAWABAN CHAPTER 2 CCNA-RS-ITN-SIM-1 Configuring a Network Operating System Chapter 2 Exam
    KUNCI JAWABAN CHAPTER 2 CCNA-RS-ITN-SIM-1 Configuring a Network Operating System Chapter 2 Exam Mandar 3 Oktober 2016 CCNA-RS-ITN-SIM-Ganjil-2016 MANDAR 3 OKTOBER 2016 KUNCI JAWABAN CHAPTER 2 1. Which two features are characteristics of flash memory? (Choose two.) Flash provides nonvolatile storage. The contents of flash may be overwritten. 2. A network administrator is planning an IOS upgrade on several of the head office routers and switches. Which three questions must be answered before continuing with the IOS selection and upgrade? (Choose three.) What models of routers and switches require upgrades? Do the routers and switches have enough RAM and flash memory for the proposed IOS versions? What features are required for the devices? 3. Which procedure is used to access a Cisco 2960 switch when performing an initial configuration in a secure environment? Use the console port to locally access the switch from a serial or USB interface of the PC. 4. A network administrator needs to keep the user ID, password, and session contents private when establishing remote CLI connectivity with a switch to manage it. Which access method should be chosen? SSH 5. A router has a valid operating system and a configuration stored in NVRAM. When the router boots up, which mode will display? user EXEC mode 6. Which two functions are provided to users by the context-sensitive help feature of the Cisco IOS CLI? (Choose two.) displaying a list of all available commands within the current mode determining which option, keyword, or argument is available for the entered command 7.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • The Arcos Network Operating System
    AT-A-GLANCE The ArcOS TM Network Operating System History has repeatedly proven that large industries transition from The ArcOS Advantage vertical integration to best-in-class horizontal segmentation as the urgent business need for innovation outstrips the ability/intent of the incumbents to deliver. The networking industry is in exactly such Agile situation, but it lags the compute and, to a large extent, the storage tiers in terms of this transition. Network operations teams are hampered by inflexible, proprietary systems that are expensive to build, operate, Automated processes accelerate and manage. This model does not fit well into today’s digital business and streamline network expectations of a more agile and innovation-friendly smart infrastructure. provisioning, operations, and deployment. Built-in YANG/ Recently, there has been an explosion of networking merchant silicon OpenConfig support simplifies options in the market that continue to redefine what is possible. integration into existing Additionally, the networking hardware ecosystem continues to evolve frameworks. with a proliferation of readily available leading-edge network platforms from multiple ODMs. But the fundamental problem has been the lack of a modern, scalable, and viable software network operating system that enables the transition from a proprietary, closed approach to an open integration approach. Elastic Arrcus addresses this problem by delivering ArcOS, an independent, open, Linux-based network operating system, as a high-quality alternative Modular software on white box/ to vertically integrated OEMs, to meet and exceed the modern smart brite box network hardware network infrastructure requirements. maximizes flexibility in building a scale-out architecture for a variety of network environments A Modern Network Operating System for the Data Center, (physical, virtual, cloud).
    [Show full text]
  • 1. Introduction
    Network Operating Systems Partha Dasgupta Department of Computer Science and Engineering Arizona State University Tempe AZ 85287-5406 USA [email protected] [Note: Written in 1997, Appeared in Encyclopedia of Electrical Engineering] 1. Introduction Network Operating Systems extend the facilities and services provided by computer operating systems to support a set of computers, connected by a network. The environment managed by a network operating system consists of an interconnected group of machines that are loosely connected. By loosely connected, we mean that such computers possess no hardware connections at the CPU – memory bus level, but are connected by external interfaces that run under the control of software. Each computer in this group run an autonomous operating system, yet cooperate with each other to allow a variety of facilities including file sharing, data sharing, peripheral sharing, remote execution and cooperative computation. Network operating systems are autonomous operating systems that support such cooperation. The group of machines comprising the management domain of the network operating system is called a distributed system. A close cousin of the network operating system is the distributed operating system. A distributed operating system is an extension of the network operating system that supports even higher levels of cooperation and integration of the machines on the network (features include task migration, dynamic resource location, and so on) (1,2). An operating system is low-level software controlling the inner workings of a machine. Typical functions performed by an operating system include managing the CPU among many concurrently executing tasks, managing memory allocation to the tasks, handling of input and output and controlling all the peripherals.
    [Show full text]
  • System Software
    PowerPoint Presentation to Accompany Chapter 5 System Software Visualizing Technology Copyright © 2014 Pearson Educaon, Inc. Publishing as Pren=ce Hall Objectives 1. Explain what an operating system does. 2. Compare the most common stand-alone operating systems. 3. Compare specialized operating systems. 4. Compare the most common network operating systems. 5. List and explain important disk utility software. 6. Identify the certifications and careers related to system software. Visualizing Technology Copyright © 2014 Pearson Educaon, Inc. Publishing as Pren=ce Hall Objective 1: Overview Who’s Being Bossy Now? 1. Discuss the job of the operating system 2. Discuss how the OS manages and controls hardware 3. Discuss how the OS interacts with software Key Terms § API (application § OS (operating system) programming interface) § PnP (Plug and Play) § Device driver § System software § GUI (graphical user interface) § Multitasking Visualizing Technology Copyright © 2014 Pearson Educaon, Inc. Publishing as Pren=ce Hall Operating System (OS) § System software § Interface to communicate with the hardware and software § A computer cannot run without an operating system installed Windows 8 interface Visualizing Technology Copyright © 2014 Pearson Educaon, Inc. Publishing as Pren=ce Hall Operating System Provides graphical user interface (GUI) Manages resources (mul=tasKing) Manage and controls hardware (PnP) Interacts with soMware (API) Visualizing Technology Copyright © 2014 Pearson Educaon, Inc. Publishing as Pren=ce Hall Which operating system is on your computer? Is it the latest version? If you have not upgraded, why not? If you could change the OS, would you? Which OS would you use instead? Visualizing Technology Copyright © 2014 Pearson Educaon, Inc. Publishing as Pren=ce Hall Objective 2: Overview Running the Show on Personal Computers 1.
    [Show full text]
  • DR DOS for the Zfx86
    DR DOS for the ZFx86 Cost Effective, Reliable, Rapid Deployment of Embedded Systems w DR DOS on the ZFx86 gets products to market quickly at the lowest development and ownership cost. w Thousands of compatible applications, drivers and utilities available free or at minimal cost. w Full documentation available. DR DOS 7.03 Key Features of DR DOS Online Manual - DRDOS is supplied with a complete The ideal embedded DOS system, online manual that contains detailed information about all designed for out-of-the-box of the features of the operating system including the basic implementation into ROM or Flash commands, and the advanced utilities. It also has online ROM with tools and associated help available for all its commands. documents available in the DRDOS Memory Management - Memory management features OEM Documentation Kit. include a set of device drivers and commands that enable w 100% MS-DOS 6.22 compatible.. you to manage memory efficiently and make as much memory as possible available to your applications. w Comprehensive DOS utility set DOS Protected Mode Services - DOS Protected Mode w Multitasking, with API for developers Services (DPMS) interface allows specially-implemented w DPMS memory manager in addition to DPMI device drivers and TSRs to operate in extended memory. w Stacker disk compression This makes more memory within the first megabyte w NWCACHE - disk caching program available to applications and other conventionally-written drivers and TSRs. Both Stacker* (the disk compression w EMM386 memory manager program), and NWCACHE (the disk cache) use DPMS. w DOS Protected Mode Services (DPMS) Disk Compression - The disk compression component w Multitasking enables you to store more information by compressing the w DR-DOS provides a full multitasking environment data.
    [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]
  • The Era of Microsoft? Technological Innovation, Network Externalities, and the Seattle Factor in the US Software Industry
    The Era of Microsoft? Technological Innovation, Network Externalities, and the Seattle Factor in the US Software Industry Edmund A. Egan Working Paper 87 January 1996 Edmund A. Egan is a Doctoral Candidate in the Department of City and Regional Planning at the University of California at Berkeley. - 1 - Abstract Microsoft Corporation, the largest company in the US software industry, has been under anti-trust scrutiny from the Department of Justice for most of the 1990s. In 1995, its planned acquisition of Intuit, Inc. prompted a Silicon Valley law firm, on behalf of unnamed complainants, to submit a White Paper to the DOJ, on the subject of Microsoft's long-term strategy. The White Paper, relying on the theoretical concepts of network externalities and lock- in effects, argues that Microsoft will use Intuit's products to attain monopolistic positions in network operating systems, on-line services, and electronic commerce, and will eventually be in a position to affect the content transmitted over electronic networks. This paper disputes that claim. First, an analysis of Microsoft's growth vs. the US packaged software industry a whole is presented, indicating that Microsoft actually has a fairly small share of total employment and sales. Secondly, a detailed review of the White Paper's argument is followed by a discussion of Microsoft's competitors, whose products also benefit from network externalities and lock-in effects. Ultimately, innovation will be more important than leverage for Microsoft. However, the paper argues that Microsoft's location in Seattle may prove to be a liability when it comes to rapid innovation; the corporation has grown much more rapidly than the Seattle software industry as a whole.
    [Show full text]
  • Configure a Network Operating System
    Instructor Materials Chapter 2: Configure a Network Operating System CCNA Routing and Switching Introduction to Networks v6.0 Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1 Chapter 2: Configure a Network Operating System Introduction to Networks v6.0 Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 3 Chapter 2 - Sections & Objectives . 2.1 IOS Bootcamp • Explain the purpose of Cisco IOS. • Explain how to access a Cisco IOS device for configuration purposes. • Explain how to navigate Cisco IOS to configure network devices. • Describe the command structure of Cisco IOS software. 2.2 Basic Device Configuration • Configure hostnames on a Cisco IOS device using the CLI. • Use Cisco IOS commands to limit access to device configurations. • Use IOS commands to save the running configuration. 2.3 Address Schemes • Explain how devices communicate across network media. • Configure a host device with an IP address. • Verify connectivity between two end devices. Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 4 2.1 IOS Bootcamp Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 5 IOS Bootcamp Cisco IOS . Operating Systems • Every computer requires an operating system to function, including computer-based network devices such as switches, routers, access points, and firewalls. These network devices use an operating system called a network operating system. • An operating system has two basic parts. Shell and Kernel • A shell providers user interface. • A kernel interacts with hardware. Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 6 IOS Bootcamp Cisco IOS . Operating Systems • Operating System interface could either be Command-Line-Interface (CLI) or Graphical-User-Interface (GUI) Presentation_ID © 2008 Cisco Systems, Inc.
    [Show full text]