DOCSLIB.ORG

HP TCP/IP Services for Openvms Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
HP TCP/IP Services for Openvms Management HP TCP/IP Services for OpenVMS Management Order Number: BA548-90006 July 2006 This manual describes how to configure and manage the TCP/IP Services product. Revision/Update Information: This manual supersedes Compaq TCP/IP Services for OpenVMS Management, Version 5.4. Software Version: HP TCP/IP Services for OpenVMS Version 5.6 Operating System: HP OpenVMS Alpha Version 8.3 HP OpenVMS I64 Version 8.3 Hewlett-Packard Company Palo Alto, California © 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. UNIX is a registered trademark of The Open Group. Microsoft, Windows and Windows NT are US registered trademarks of Microsoft Corporation. ZK6526 The HP TCP/IP Services for OpenVMS documentation is available on CD-ROM. This document was prepared using DECdocument, Version 3.3-1b. Contents Preface ............................................................ xxiii Part 1 Connecting to the Network 1 Managing TCP/IP Services 1.1 Getting Started ............................................. 1–1 1.1.1 Logical Names . ........................................ 1–2 1.1.2 Modifying Your Configuration ............................... 1–3 1.1.3 Saving Changes . ........................................ 1–3 1.1.4 Starting and Stopping the Software ........................... 1–4 1.1.5 Editing Configuration Files . ................................ 1–5 1.2 Enabling PATHWORKS/Advanced Server and DECnet-over-TCP/IP Support . ................................................ 1–6 1.2.1 Starting and Stopping the PWIP Driver ....................... 1–6 1.3 Setting Up User Accounts and Proxy Identities ..................... 1–7 1.4 Configuring a TCP/IP Cluster . ................................ 1–8 1.4.1 Setting Up an ARP-Based Cluster ............................ 1–8 1.5 Auxiliary Server ............................................. 1–9 1.5.1 How the Auxiliary Server Works ............................. 1–9 1.5.1.1 Rejecting Client Requests ............................... 1–9 1.5.1.2 Configuring the Auxiliary Server . ....................... 1–9 1.6 Enabling Services ............................................ 1–11 1.6.1 Setting Up Event Logging . ................................ 1–11 2 Configuring Interfaces 2.1 Key Concepts ............................................... 2–1 2.2 Configuring Network Controllers ................................ 2–1 2.3 Configuring Network Interfaces . ................................ 2–2 2.3.1 Specifying the Interface .................................... 2–2 2.3.2 Specifying the Network Mask ............................... 2–3 2.3.3 Specifying Additional IP Addresses ........................... 2–3 3 Configuring and Managing Serial Lines 3.1 Key Concepts ............................................... 3–1 3.1.1 PPP and SLIP . ........................................ 3–1 3.1.2 Assigning an IP Address to Your PPP or SLIP Interface ........... 3–2 3.1.3 Serial Line Internet Protocol ................................ 3–2 3.1.4 Point-to-Point Protocol ..................................... 3–3 3.2 Setting Up a PPP Interface (Alpha Only) . ....................... 3–3 iii 3.2.1 Setting Up Your Host for PPP Connections ..................... 3–4 3.2.1.1 Installing the Terminal Driver ............................ 3–4 3.2.1.2 Configuring the Modem . ................................ 3–5 3.2.1.3 Setting Up an Asynchronous Port . ....................... 3–6 3.2.1.4 Configuring a PPP Interface ............................. 3–7 3.2.1.5 Enabling IP Forwarding (Dialup Provider Only) .............. 3–7 3.2.1.6 Initiating a PPP Connection ............................. 3–8 3.2.2 Removing the PPP Configuration ............................. 3–9 3.3 Setting Up a SLIP Interface . ................................ 3–10 3.3.1 Setting Up Hard-Wired SLIP Lines ........................... 3–11 3.3.2 Setting Up SLIP Dialup Lines ............................... 3–11 3.3.3 Setting Up Your Host as a SLIP Dialup Provider . ............... 3–13 3.3.4 Connecting a Host to the LAN ............................... 3–14 3.3.5 Setting Up a SLIP Gateway with Proxy ARP ................... 3–14 3.3.6 Shutting Down SLIP ...................................... 3–15 3.4 Solving Serial Line Problems . ................................ 3–15 3.4.1 Solving PPP Problems ..................................... 3–16 4 Configuring and Managing Routing 4.1 Key Concepts ............................................... 4–1 4.1.1 Static Routing . ........................................ 4–1 4.1.2 Dynamic Routing . ........................................ 4–1 4.1.2.1 Routing Daemon (ROUTED) ............................. 4–2 4.1.2.2 Gateway Routing Daemon (GATED) ....................... 4–2 4.2 Configuring Static Routes ..................................... 4–3 4.2.1 Creating a Default Route . ................................ 4–3 4.2.2 Manually Defining Static Routes ............................. 4–3 4.2.2.1 Examples ............................................ 4–4 4.2.3 Displaying Manually Defined Routes . ....................... 4–5 4.3 Enabling and Disabling Dynamic Routing . ....................... 4–6 4.4 Configuring GATED . ........................................ 4–6 4.4.1 Datagram Reassembly Time ................................ 4–7 4.4.2 Enabling Forwarding ...................................... 4–7 4.4.3 Extending Routing ........................................ 4–8 4.4.4 Interface Routes . ........................................ 4–9 4.4.5 Manually Configuring a Hardware Address ..................... 4–10 5 Configuring and Managing failSAFE IP 5.1 Key Concepts ............................................... 5–1 5.2 Configuring failSAFE IP ...................................... 5–2 5.2.1 Configuring failSAFE IP Manually ........................... 5–2 5.2.2 Modifying the failSAFE IP Configuration Parameters ............. 5–3 5.2.3 Creating and Displaying Home Interfaces ...................... 5–5 5.3 Managing failSAFE IP ........................................ 5–5 5.3.1 failSAFE IP Logical Names . ................................ 5–6 5.3.2 Customizing failSAFE IP . ................................ 5–7 5.3.3 Reestablishing Static and Dynamic Routing .................... 5–7 5.3.4 Displaying the Status of Interfaces ........................... 5–8 iv 5.3.5 Guidelines for Configuring failSAFE IP . ....................... 5–8 5.3.5.1 Validating failSAFE IP . ................................ 5–8 5.3.5.2 Configuring Failover Time ............................... 5–9 5.3.5.3 Avoiding Phantom Failures .............................. 5–10 5.3.5.4 Creating IP Addresses with Home Interfaces . ............... 5–10 5.3.5.5 Private Addresses Should Not Have Clusterwide Standby Interfaces ............................................ 5–10 Part 2 BIND 6 Configuring and Managing BIND Version 9 6.1 Key Concepts ............................................... 6–2 6.1.1 How the Resolver and Name Server Work Together .............. 6–2 6.1.2 Common BIND Configurations ............................... 6–2 6.1.2.1 Master Servers ........................................ 6–3 6.1.2.2 Slave Servers . ........................................ 6–3 6.1.2.3 Caching-Only Servers . ................................ 6–3 6.1.2.4 Forwarder Servers ..................................... 6–3 6.2 Security Considerations ....................................... 6–4 6.2.1 Access Control Lists ....................................... 6–4 6.2.2 Dynamic Update Security . ................................ 6–5 6.2.3 TSIG . ................................................ 6–5 6.2.4 TKEY . ................................................ 6–8 6.2.5 SIG(0) . ................................................ 6–8 6.2.6 DNSSEC ............................................... 6–8 6.2.6.1 DNSSEC Restrictions . ................................ 6–10 6.3 Migrating from BIND Version 4 to BIND Version 9 . ............... 6–11 6.3.1 Navigating Two Different BIND Environments . ............... 6–11 6.4 BIND Service Startup and Shutdown ............................ 6–12 6.5 Configuring the BIND Server . ................................ 6–13 6.5.1 Configuration File Elements ................................ 6–13 6.5.2 Address Match Lists ...................................... 6–15 6.5.3 Configuration File Format . ................................ 6–16 6.5.3.1 The ACL Statement .................................... 6–18 6.5.3.2 The CONTROLS Statement .............................. 6–18 6.5.3.3 The INCLUDE Statement ............................... 6–19 6.5.3.4 The KEY Statement .................................... 6–19 6.5.3.5 The LOGGING Statement ............................... 6–20 6.5.3.5.1 The Channel Phrase ................................ 6–21 6.5.3.5.2 The Category Phrase ................................ 6–22 6.5.3.6 The MASTERS Statement ............................... 6–24 6.5.3.7 The OPTIONS Statement
Load more

Recommended publications
  • Software Product Description and Quickspecs
    VSI OpenVMS Alpha Version 8.4-2L2 Operating System DO-DVASPQ-01A Software Product Description and QuickSpecs PRODUCT NAME: VSI OpenVMS Alpha Version 8.4-2L2 DO-DVASPQ-01A This SPD and QuickSpecs describes the VSI OpenVMS Alpha Performance Release Operating System software, Version 8.4-2L2 (hereafter referred to as VSI OpenVMS Alpha V8.4-2L2). DESCRIPTION OpenVMS is a general purpose, multiuser operating system that runs in both production and development environments. VSI OpenVMS Alpha Version 8.4-2L2 is the latest release of the OpenVMS Alpha computing environment by VMS Software, Inc (VSI). VSI OpenVMS Alpha V8.4-2L2 is compiled to take advantage of architectural features such as byte and word memory reference instructions, and floating-point improvements, which are available only in HPE AlphaServer EV6 or later processors. This optimized release improves performance by taking advantage of faster hardware-based instructions that were previously emulated in software. NOTE: VSI OpenVMS Alpha V8.4-2L2 does not work on, and is not supported on, HPE AlphaServer pre-EV6 systems. OpenVMS Alpha supports HPE’s AlphaServer series computers. OpenVMS software supports industry standards, facilitating application portability and interoperability. OpenVMS provides symmetric multiprocessing (SMP) support for multiprocessing systems. The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Actual system performance depends on the type of computer, available physical memory, and the number and type of active disk and tape drives. The OpenVMS operating system has well-integrated networking, distributed computing, client/server, windowing, multi-processing, and authentication capabilities.
    [Show full text]
  • Muxserver 380 Hardware Installation Manual Order Number EK-DSRZD-IM-002
    MUXserver 380 Hardware Installation Manual Order Number EK-DSRZD-IM-002 2nd Edition Second Edition - February 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation (Australia) Pty. Limited. Digital Equipment Corporation (Australia) Pty. Limited assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation (Australia) Pty. Limited or its affiliated companies. Copyright ©1992 by Digital Equipment Corporation (Australia) Pty. Limited. All Rights Reserved. Printed in Australia. The postpaid READER’S COMMENTS form on the last page of this document requests the user’s critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem UWS DEC/MMS IAS VAX DECnet MASSBUS VAXcluster DECstation PDP VMS DECsystem–10 PDT VT DECSYSTEM–20 RSTS DECUS RSX DECwriter ULTRIX dt Contents Preface viii Chapter 1 Introduction 1.1 Overview of the MUXserver 380 Network . ................................1–1 1.2 Typical MUXserver 380 Network Configuration ...............................1–2 1.3 The MUXserver 380 . .................................................1–3 1.4 Connecting the MUXserver 380 . ........................................1–6 1.5 Installation Overview . ................................................1–10 1.6 Items Required for MUXserver 380 Installation .............................1–11 1.7 Service Options ......................................................1–12 1.7.1 Digital On-Site Service .
    [Show full text]
  • Decserver 90M Installation Guide
    DECserver 90M Installation Guide Part Number: IG-DSRVH-00 April 2002 This document describes how to install and troubleshoot the DECserver 90M. Revision/Update Information: This is a new document. Digital Networks makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital Networks or an authorized sublicensor. Copyright © 2001 DNPG, LLC (“Digital Networks”). All rights reserved. Digital Networks 486 Amherst St. Nashua , NH 03063-1224 Web site: www.digitalnetworks.net Digital Networks is the tradename of DNPG, LLC, and is not affiliated with Compaq Computer Corporation. DIGITAL, the Digital Logo and DEC are used under license from Compaq Computer Corporation. clearVISN, Multistack, MultiSwitch, and ThinWire are trademarks of Cabletron Systems, Inc. All other trademarks and registered trademarks are the property of their respective holders. NOTICES FCC Notice — Class A Computing Device: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
    [Show full text]
  • ETS4P4 Terminal Server
    ETS4P4 Terminal Server Installation Guide Thank you for purchasing this Lantronix ETS Ethernet Terminal Server. As the newest addition to our successful Ethernet terminal server family, the ETS uses software for multiprotocol Ethernet connections that has over 5 years of real-world feedback and de- velopment behind it. Lantronix is constantly improving the capabilities of our prod- ucts, and we encourage you to take advantage of new features through our FREE software upgrades (available via ftp over the Internet or BBS.) Our Flash ROM products, including this ETS, provide the sim- plest means for upgrades and installation. I hope you find this manual easy to use, and thorough in its explanation of the power- ful features you can now access on your network. Brad Freeburg President Contents 1 Introduction Overview...........................................................................1-1 Configuration ................................................1-1 Software ..........................................................1-2 About the Manuals ..........................................................1-2 2 Installation Overview...........................................................................2-1 ETS Components..............................................................2-1 Installation ........................................................................2-2 Selecting a Location for the ETS ..................2-2 Connecting to the Ethernet...........................2-2 Connecting a Terminal..................................2-3
    [Show full text]
  • Configuring Asynchronous Lines and Interfaces
    Configuring Asynchronous Lines and Interfaces This chapter describes how to configure asynchronous line features in the following main sections: • How to Configure Asynchronous Interfaces and Lines • How to Configure Other Asynchronous Line and Interface Features • Configuration Examples for Asynchronous Interfaces and Lines Perform these tasks, as required, for your particular network. To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the “Identifying Supported Platforms” section in the “Using Cisco IOS Software” chapter. For a complete description of the commands in this chapter, refer to the Cisco IOS Dial Technologies Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online. How to Configure Asynchronous Interfaces and Lines To configure an asynchronous interface, perform the tasks described in the following sections as required: • Configuring a Typical Asynchronous Interface (As required) • Creating a Group Asynchronous Interface (As required) • Configuring Asynchronous Rotary Line Queueing (As required) • Configuring Autoselect (As required) Configuring a Typical Asynchronous Interface To configure an asynchronous interface, use the following commands beginning in global configuration mode: Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines Command Purpose Step 1 Router(config)# interface async number Brings up a single asynchronous interface and enters interface configuration mode. Step 2 Router(config-if)# description description Provides a description for the interface.
    [Show full text]
  • SSH Terminal-Line Access
    SSH Terminal-Line Access The SSH Terminal-Line Access feature provides users secure access to tty (text telephone) lines. tty allows the hearing- and speech-impaired to communicate by using a telephone to type messages. • Finding Feature Information, page 1 • Prerequisites for SSH Terminal-Line Access, page 1 • Restrictions for SSH Terminal-Line Access, page 2 • Information About SSH Terminal-Line Access, page 2 • How to Configure SSH Terminal-Line Access, page 3 • Configuration Examples for SSH Terminal-Line Access, page 5 • Additional References, page 6 • Feature Information for SSH Terminal-Line Access, page 7 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for SSH Terminal-Line Access Download the required image to your router. The secure shell (SSH) server requires the router to have an IPSec (Data Encryption Standard (DES) or 3DES) encryption software image from Cisco IOS Release 12.1(1)T or a later release. The SSH client requires the router to have an IPSec (DES or 3DES) encryption software image from Cisco IOS Release 12.1(3)T or a later release.
    [Show full text]
  • Single-Port Terminal Server Model 2120
    Device Servers Single-Port Terminal Server Model 2120 The Patton Model 2120 Single Port Terminal Server brings RS-232 serial devices onto the LAN using the flexibility of Ethernet and TCP/IP protocols. Control and Monitor Serial Devices thernet continues to be the most com- user-defined IP address and port. Once con- Control and monitor your RS-232 asynchronous mon office networking infrastructure. nected to the remote host, data is passed terminals and devices over the local area network ENow, Ethernet is making its way from transparently end-to-end. The built-in DHCP the office to the shop floor. Traditional RS- Client allows the Model 2120 to dynamically Supports a Wide Range of Data Rates 232 environments require the use of multi- obtain an IP address and a subnet mask from User-selectable async data port serial cards, expensive cables, and the a master server. With SLIP and PPP connec- rates up to 115.2 kbps personnel to manage multiple systems. tions, remote users can Patton’s Model 2120 Single Port Terminal access the network and it Connects Directly to the LAN Server provides a quick, simple, and cost will appear as if they were 802.3 10Base-T LAN connection effective solution for connecting traditional locally connected. via RJ-45 connects to any hub/switch RS-232 terminals and devices to the LAN. Why go to the expense and hassle of installing Special Rates Available Standard TCP/IP Protocols Supported The Model 2120 enables you to bring all sys- Call for Details TCP, UDP, IP, ICMP, TELNET, ARP, DHCP, tems and equipment together onto one local outdated multi-port serial FTP, SLIP, PPP, DNS, WINS, and PAP area network.
    [Show full text]
  • Managing Serial Devices in a Networked Environment
    Managing Serial Devices in a Networked Environment Lantronix, Inc. 15353 Barranca Parkway Irvine, CA 92618 Tel: +1 (949) 453-3990 Fax: 1+ (949) 453-3995 Introduction The proliferation of network management technology in both hardware and software has provided the network manager with an extensive tool kit. Still, many devices being used today support only serial management. Such devices provide a serial management port for attaching terminals or PCs to perform management functions. These serial-only devices may also require the network manager to implement costly and sometimes cumbersome workarounds to be included in the management scheme. This paper explores the technological advances in Device Server design that make it possible to manage serial-only devices over a network. Management via Serial Communications: Non-networked Techniques Networked communication seems like a birthright to current PC users. However, one should remember that for many years serial communication was the only way to transmit data from one device to another. Many industrial, medical and monitoring devices were designed long before the current advancements in integrated circuits made Ethernet technology so inexpensive. Some of these devices would even qualify as legacy equipment, built with internal processing capabilities far below that of current desktop PCs. The only management option provided on many of these products is a serial port. Usually RS-232, this port is intended to connect directly to a PC or dumb terminal which displays device status information and/or grants access to device configuration information. In some cases, the PC is tasked with processing raw data sent over the serial port, due to the fact that the device itself does not have the bandwidth to do so.
    [Show full text]
  • Openvms I/O User's Reference Manual
    OpenVMS I/O User’s Reference Manual Order Number: AA–PV6SD–TK April 2001 This manual contains the information necessary to interface directly with the I/O device drivers supplied as part of the Compaq OpenVMS operating system. Several examples of programming techniques are included. This document does not contain information on I/O operations using the OpenVMS Record Management Services. Revision/Update Information: This manual supersedes the OpenVMS I/O User’s Reference Manual, OpenVMS Alpha Version 7.2, OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P in the United States and other countries. Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the United States and other countries. Motif, OSF/1, and UNIX are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein.
    [Show full text]
  • IOLAN Electric Utility Terminal Server
    IOLAN Electric Utility Terminal Server perle.com/products/electric-utility-terminal-server.shtml 8, 16 and 32 serial ports on RJ45 - software selectable RS232/422/485 Advanced security features for NERC CIP critical cyberasset substation compliance Substation hardened for harsh electrical utility and industrial applications Universal high voltage power supply: nominal 125v DC / 250v DC or 115v AC / 230v AC Dual Feed low voltage power supply: nominal 24v DC /48v DC Dual 10/100/1000 Ethernet with Redundant Path Technology Built-in failsafe alarm relay Electrical utility engineers and project managers that require a cost effective serial-to-Ethernet solution to help meet NERC-CIP compliance for the protection of critical cyberassets in substations must consider the IOLAN SDS HV/LDC Terminal Server. In addition to the most extensive security features available, these IOLAN’s are designed to meet harsh environments associated with Power Substations with attributes such as support for substation AC and DC voltage ranges, extended operating temperatures and meeting emission, immunity and safety approvals associated with substation IT equipment. Ideal for Electrical utility engineers and Project Managers requiring a high performance serial to Ethernet interface for serial RS232 or RS485 based devices such as SCADA based RTUs and protection relays. Environments that require a serial terminal server with unique environmental, form factor, or power inputs in harsh environments Substation Automation projects where using secured communications in remote
    [Show full text]
  • Adv. Console Access (T12)
    Adv. Console Access (T12) Advanced Remote Console Access version 1.6 David K. Z. Harris [email protected] This presentation will be temporarily available at: http://www.conserver.com/consoles/LISA2002-T12.pdf © 2002 David K. Z. Harris Pg. 1 This presentation is a supplement to my console services web pages located at http://www.conserver.com/consoles/. These pages have a substantial amount of information noted below each slide. I do this to help minimize the amount of note-taking that you need to do in class, and this should give you more time to listen to the tutorial. However, if you feel that you learn better by taking notes, please feel free to do so. ©2002, David K. Z. Harris 1 About BigBand Networks Ø BigBand Networks makes Digital Video grooming hardware for Cable and Satellite companies, to help them make better use of the bandwidth they now have. © 2002 David K. Z. Harris Pg. 2 Essentially, the hardware and software produced by BigBand Networks can aggregate information on a broadband network, turning a bunch of allocated frequencies into one “Big Band”, allowing the users to spread their data across many channels. The serial consoles on the BMR chassis run at 115 Kbps, and are VERY verbose. The output is ideal for realtime system monitoring, and statistics gathering, but would be a horror to log for any significant amount of time. While the chassis normally uses SNMP for management, the serial console also regularly streams information and updates. Administrators can use a Command Line Interface to manage the devices, and automated configuration can be done using ASCII text uploads, or send/expect scripts, etc.
    [Show full text]
  • Installing Conserver
    Installing Conserver version 1.0 David K. Z. Harris [email protected] Bryan Stansell [email protected] http://www.certaintysolutions.com/consoles/LISA2K-2.zip http://www.conserver.com/consoles/LISA2K-2.zip © 2000 Certainty Solutions, Inc. Pg. 1 This presentation is a supplement to my console services web pages located at http://www.certaintysolutions.com/consoles/LISA2K-2.zip. These pages have a substantial amount of information noted below each slide. We do this to help minimize the amount of note-taking that you need to do in class, and this should give you more time to listen to the instructors. If you feel that you learn better by taking notes, please feel free to do so. This presentation is meant to be a follow-up to a Basic Serial presentation. While this presentation can stand on its own, there is only a small amount of review of the earlier topic. During this tutorial, we will be discussing the topic of Console Servers as a generic application, but our technical emphasis will be on the Conserver application, which is freely available from http://www.conserver.com/. For most purposes in this tutorial, “Console Server” and “Conserver” can be used interchangeably. ©2000, David K. Z. Harris Certainty Solutions: Certainty in an uncertain world M12-2 v1.0 1 Pertinent Job History Ø Network Equipment Technologies ² (Comdesign, Bridge Communications) Ø Telebit Corp. Ø Cisco Systems, Inc. Ø Apple Computer, Inc. Ø Synopsys, Inc. Ø Global Networking & Computing ² (We’re now Certainty Solutions.) © 2000 Certainty Solutions, Inc. Pg. 2 Before moving into networking, David Harris was a hardware hacker, working in repair and R&D roles.
    [Show full text]