DOCSLIB.ORG

Router Products Configurationguide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Router Products Configurationguide Software Release 9.21 Chapters to ci co OlE Router Products ConfigurationGuide Chapters to6 Software Release 9.21 Corporate Headquarters PO Box 3075 1525 OBrien Drive Menlo Park CA 94026 415 326-1941 800 553-NETS Customer Order Number DOC-RTCG9.21 Cisco Document Assembly Number 83-0120-01 Text Part Number 78-1241-01 The products and specifications configurations and other technical information regarding the products contained in this manual are subject to change without notice All statements technical information and recommendations contained in this manual are believed to be accurate and reliable but are without of and take full for their of in this presented warranty any kind express or implied users must responsibility application any products specified manual incidental or limitation how warranties so Some states do not allow limitation or exclusion of liability for consequential or damages on long implied last and also have other that the above limitations or exclusions may not apply to you This warranty gives Customers specific legal rights you may rights vary from state to state instruction This equipment generates uses and can radiate radio frequency energy and if not installed and used in accordance with the manual may cause with the limits for device interference to radio communications This equipment has been tested and found to comply Class computing pursuant to Subpart of Part 15 of FCC Rules which are designed to provide reasonable protection against such interference when operated in commercial will be environment Operation of this equipment in residential area is likely to cause interference in which case the user at his own expense required to take whatever measures may be required to correct the interference The third software be included with and will be to the software license following party may your product subject agreement The Cisco implementation of TCP header compression is an adaptation of program developed by the University of California Berkeley UCB as part of UCB public domain version of the UNIX operating system All rights reserved Copyright 1981 Regents of the University of Califomia Network Time Protocol NTP Copyright 1992 David Mills The University of Delaware makes no representations about the suitability of this software for any purpose Point-to-Point Protocol Copyright 1989 Carnegie Mellon University All rights reserved The name of the University may not be used to endorse or promote products derived from this software without specific prior Written permission The Cisco of is of the and the of implementation TN3270 an adaptation tn3270 curses termcap programs developed by University California Berkeley of domain version of the UNIX All reserved 198 of the of UCB as part UCBs public operating system rights Copyright 1-1988 Regents University California XRemote is trademark of Network Computing Devices Inc Copyright 1989 Network Computing Devices Inc Mountain View California N.C.D makes no representations about the suitability of this software for any purpose The Window System is trademark of the Massachusetts Institute of Technology Copyright 1987 by Digital Equipment Corporation Maynard Massachusetts and the Massachusetts Institute of Technology Cambridge Massachusetts All rights reserved THIS MANUAL CISCOS SOFTWARE AND TIlE SOFTWARE OF THE ABOVE-LISTED SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES EXPRESSED OR IMPLIED INCLUDING THOSE OF MERCHANTABILITY AND FITNESS FOR PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING USAGE OR TRADE PRACTICE IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANYINDIRECT SPECIAL CONSEQUENTIAL OR INCIDENTAL DAMAGES INCLUDING WITHOUT LIMITATION LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL EVEN IF CISCO HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES Notice of Restricted Rights disclosure Use duplication or by the Government is subject to restrictions as set forth in subparagraph of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 and subparagraph 1ii of the Rights in Technical Data and Computer Software clause at DFARS 252.227- 7013 The information in this manual is subject to change without notice Access Without Compromise CDDI CiscoWorks Cisco Intemetwork Operating System Netscape SMARTnet Tite Packet and UniverCD are trademarks and Cisco Systems and the Cisco logo are registered trademarks of Cisco Systems Inc All other products or services mentioned in this document are the trademarks service marks registered trademarks or registered service marks of their respective owners Router Products Configuration Guide Copyright 1988-1993 Cisco Systems Inc All rights reserved Printed in USA SOFTWARE LICENSE READ CAREFULLY BEFORE USING ThIS SOFTWARE LICENSE AGREEMENT PLEASE READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THE SOFTWARE BY USING THE SOFTWARE YOU AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS LICENSE IF YOU DO NOT AGREE WITH THE TERMS OF THIS LICENSE PROMPTLY RETURN THE UNUSED SOFTWARE MANUAL AND RELATED EQUIPMENT WITH PROOF OF PAYMENT TO THE PLACE OF PURCHASE FOR FULL REFUND Cisco Inc to Customer nonexclusive and nontransferable license to use the Cisco software Systems Cisco grants Customer Software in object code form solely on single central processing unit owned or leased by Customer or otherwise embedded in equipment provide by Cisco Customer may make one archival of the software Customer affixes such all and copy provided to copy copyright confidentiality proprietary notices that appear on the original Except as expressly authorized above CUSTOMER SHALL NOT COPY IN WHOLE OR IN PART SOFTWARE OR DOCUMENTATION MODIFY THE SOFTWARE REVERSE COMPILE OR REVERSE ASSEMBLE ALL OR ANY PORTION OF THE SOFTWARE OR RENT LEASE DISTRIBUTE SELL OR CREATE DERIVATIVE WORKS OF THE SOFTWARE Customer that of the licensed agrees aspects materials including the specific design and structure of individual programs constitute trade secrets and/or copyrighted material of Cisco Customer not to disclose or otherwise make available such trade secrets or material in form agrees provide copyrighted any third the to any party without prior consent of Cisco Customer agrees to implement reasonable security measures to protect such trade secrets and material Title Software copyrighted to and documentation shall remain solely with Cisco Cisco LIMITED WARRANTY warrants that the Software will substantially conform to the published specifications for such Software if used properly in accordance with the Documentation for of from the date of To be for Customer must all period ninety 90 days shipment eligible remedy report warranted problems within the warranty period to the party which supplied the Product to Customer or to the Cisco Service Partner if the Software was multinational exported under the uplift program Ciscos sole and exclusive obligation and Customers exclusive remedy with respect to nonconforming Software upon contact will be at Ciscos option and potentially through the Sales or Service Partner either to provide correction or workaround for any reproducible errors or ii to refund to Customer the license fee for the Software in the event that license fee was paid and the other remedy is not available or if the license fee was zero refund the of the hardware less calculated on basis Customer that it will price depreciation straightline agrees with Cisco or its Sales or Service Partner in the environment in which the error occurred Customer to cooperate creating Further agrees supply any necessary equipment for such tests This Limited does not to Software which has been as authorized has not been Warranty apply altered except by Cisco installed operated repaired or maintained in accordance with any installation handling maintenance or operating instructions supplied by Cisco has been subjected to unusual physical or electrical stress misuse negligence or accident is used in ultra hazardous activities has been used in such way that Cisco or its Sales Partner cannot reasonably reproduce the Software error has been exported from the original country of destination without payment of an uplift or has been In no event does Cisco warrant that the Software is error free or that Customer will be able to its networks without misapplied operate problems or interruptions THIS WARRANTY IS IN LIEU OF AND CISCO DISCLAIMS ALL OTHER WARRANTIES EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR PARTICULAR PURPOSE IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT SPECIAL CONSEQUENTIAL OR INCIDENTAL DAMAGES INCLUDING WITHOUT LIMITATION LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS CISCO SOFTWARE EVEN IF CISCO HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES SOME STATES DO NOT ALLOW LIMITATION OR EXCLUSION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES OR LIMITATION ON HOW LONG IMPLIED WARRANTIES LAST SO ThE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO CUSTOMER Customer will with all laws and if it the This restriction shall survive comply applicable export regulations exports products termination of this Agreement This License is effective until terminated Customer terminate this License at lime the software with may any by destroying together all copies thereof Cisco terminate this License if the Customer fails with condition hereof may immediately to comply any term or Upon any termination of this
Load more

Recommended publications
  • User Interface Commands
    CHAPTER 2 User Interface Commands This chapter describes the commands used to access user and privileged EXEC command modes. It provides a description of the help command and features, lists the command editing keys and functions, and details the command history feature. This chapter also includes the EXEC commands that can be used to set various terminal parameters on a temporary basis (for the duration of a session). It includes the Telnet commands you can use to make a connection from a terminal to a remote router in order to configure the router. The commands to actually configure these parameters on a more permanent basis are provided in the “Terminal Line and Modem Support Commands” chapter in the Router Products Command Reference publication. You need enter only enough characters of a command to uniquely identify the command, thereby abbreviating the command syntax you type. For user interface task information and examples, refer to the “Understanding the User Interface” chapter of the Router Products Configuration Guide. User Interface Commands 2-1 clear line clear line Use the clear line EXEC command to return a terminal line to idle state. clear line line-number Syntax Description line-number Absolute line number Default None Command Mode EXEC Usage Guidelines Use this command to log out of a specific session running on another line. If the line uses a modem, the modem will be disconnected. Example In the following example, line 3 is reset: clear line 3 2-2 Router Products Command Reference connect connect To make a Telnet connection, enter the connect EXEC command at the system prompt.
    [Show full text]
  • CSE 142 Python Slides
    CSE 390a Lecture 4 Persistent shell settings; intro to shell scripting slides created by Marty Stepp, modified by Jessica Miller & Ruth Anderson http://www.cs.washington.edu/390a/ 1 Lecture summary • persistent settings for your bash shell • basic script syntax and running scripts • shell variables and types • control statements: the for loop 2 .bash_profile and .bashrc • Every time you log in to bash, the commands in ~/.bash_profile are run . you can put any common startup commands you want into this file . useful for setting up aliases and other settings for remote login • Every time you launch a non-login bash terminal, the commands in ~/.bashrc are run . useful for setting up persistent commands for local shell usage, or when launching multiple shells . often, .bash_profile is configured to also run .bashrc, but not always Note: a dot (.) in front of a filename indicates a normally hidden file, use ls –a to see 3 Exercise:Edit your .bashrc • Exercise : Make it so that our attu alias from earlier becomes persistent, so that it will work every time we run a shell. • Exercise : Make it so that whenever you try to delete or overwrite a file during a move/copy, you will be prompted for confirmation first. 4 .plan • Another fun settings file • Stored in your home directory • Contains information you’d like others to be able to see . is displayed when the finger protocol is run • Exercise: create a quick .plan file, and make sure it works with finger 5 Shell scripts • script: A short program meant to perform a targeted task.
    [Show full text]
  • NBAR2 Standard Protocol Pack 1.0
    NBAR2 Standard Protocol Pack 1.0 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 © 2013 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 1 CHAPTER 2 BGP 3 BITTORRENT 6 CITRIX 7 DHCP 8 DIRECTCONNECT 9 DNS 10 EDONKEY 11 EGP 12 EIGRP 13 EXCHANGE 14 FASTTRACK 15 FINGER 16 FTP 17 GNUTELLA 18 GOPHER 19 GRE 20 H323 21 HTTP 22 ICMP 23 IMAP 24 IPINIP 25 IPV6-ICMP 26 IRC 27 KAZAA2 28 KERBEROS 29 L2TP 30 NBAR2 Standard Protocol Pack 1.0 iii Contents LDAP 31 MGCP 32 NETBIOS 33 NETSHOW 34 NFS 35 NNTP 36 NOTES 37 NTP 38 OSPF 39 POP3 40 PPTP 41 PRINTER 42 RIP 43 RTCP 44 RTP 45 RTSP 46 SAP 47 SECURE-FTP 48 SECURE-HTTP 49 SECURE-IMAP 50 SECURE-IRC 51 SECURE-LDAP 52 SECURE-NNTP 53 SECURE-POP3 54 SECURE-TELNET 55 SIP 56 SKINNY 57 SKYPE 58 SMTP 59 SNMP 60 SOCKS 61 SQLNET 62 SQLSERVER 63 SSH 64 STREAMWORK 65 NBAR2 Standard Protocol Pack 1.0 iv Contents SUNRPC 66 SYSLOG 67 TELNET 68 TFTP 69 VDOLIVE 70 WINMX 71 NBAR2 Standard Protocol Pack 1.0 v Contents NBAR2 Standard Protocol Pack 1.0 vi CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 NBAR2 Standard Protocol Pack Overview The Network Based Application Recognition (NBAR2) Standard Protocol Pack 1.0 is provided as the base protocol pack with an unlicensed Cisco image on a device.
    [Show full text]
  • Edition with Romkey, April 16, 1986 (PDF)
    PC/IP User's Guide MASSACHUSETTS INSTITUTE OF TECHNOLOGY Laboratory For Computer Science Network programs based on the DoD Internet Protocol for the mM Personal Computer PC/~ release or March, 1986; document updated Aprill4, 1986 by: Jerome H. Saltzer John L. Romkey .• Copyright 1984, 1985, 1986 by the Massachusetts Institute or Technology Permission to use, copy, modlt'y, and distribute these programs and their documentation ror any purpose and without ree ls hereby granted, provided that this copyright and permission notice appear on all copies and supporting documentation, the name or M.I.T. not be used in advertising or publlclty pertalnlng to dlstrlbutlon or the programs without written prior permission, and notice be glven in supporting documentation that copying and distribution ls by permlsslon or M.I.T. M.I.T. makes no representations about the suitablllty or this software for any purpose. It is provided "as ls" without express or Implied warranty. - ii - CREDITS The PC/IP packages are bullt on the work of many people in the TCP/IP community, both at M.I.T. and elsewhere. Following are some of the people who directly helped in the creation of the packages. Network environment-John L. Romkey Terminal emulator and customizer-David A. Bridgham Inltlal TFTP-Kari D. Wright Inltlal telnet-Louls J. Konopelskl Teinet model-David D. Clark Tasking package-Larry W. Allen Development system-Christopher J. Terman Development environment-Wayne C. Gramlich Administrative Assistant-Muriel Webber October 3, 1985. This document is in cover .mss - iii- - iv Table of Contents 1. Overview of PC/IP network programs 1 1.1.
    [Show full text]
  • CSE 391 Lecture 4
    CSE 391 Lecture 4 Persistent shell settings; users/groups; permissions slides created by Marty Stepp, modified by Jessica Miller and Ruth Anderson http://www.cs.washington.edu/391/ 1 Lecture summary • Persistent settings for your bash shell • User accounts and groups • File permissions • The Super User 2 .bash_profile and .bashrc • Every time you log in to bash (e.g. ssh attu), the commands in ~/.bash_profile are run . you can put any common startup commands you want into this file . useful for setting up aliases and other settings for remote login • Every time you launch a non-login bash terminal (e.g. bash), the commands in ~/.bashrc are run . useful for setting up persistent commands for local shell usage, or when launching multiple shells . Do not put things that would produce output in .bashrc (e.g. echo) . often, .bash_profile is configured to also run .bashrc, but not always Note: a dot (.) in front of a filename indicates a normally hidden file, use ls –a to see 3 Exercise:Edit your .bashrc • Exercise : Make it so that our attu alias from earlier becomes persistent, so that it will work every time we run a shell. • Exercise : Make it so that whenever you try to delete or overwrite a file during a move/copy, you will be prompted for confirmation first. 4 Making Changes Visible • After editing your .bashrc or .bash_profile, how do you make the aliases etc. in the file take effect? . .bash_profile • log on again (e.g ssh attu), or • bash -l (el not one) will start a login shell, or • source .bash_profile .
    [Show full text]
  • Uncovering Network Perimeter Vulnerabilities in Cisco Routers According to Requirements Defined in Pci Dss 2.0 David E
    Regis University ePublications at Regis University All Regis University Theses Summer 2011 Uncovering Network Perimeter Vulnerabilities in Cisco Routers According to Requirements Defined in Pci Dss 2.0 David E. Naples Regis University Follow this and additional works at: https://epublications.regis.edu/theses Part of the Computer Sciences Commons Recommended Citation Naples, David E., "Uncovering Network Perimeter Vulnerabilities in Cisco Routers According to Requirements Defined in Pci Dss 2.0" (2011). All Regis University Theses. 472. https://epublications.regis.edu/theses/472 This Thesis - Open Access is brought to you for free and open access by ePublications at Regis University. It has been accepted for inclusion in All Regis University Theses by an authorized administrator of ePublications at Regis University. For more information, please contact [email protected]. Regis University College for Professional Studies Graduate Programs Final Project/Thesis Disclaimer Use of the materials available in the Regis University Thesis Collection (“Collection”) is limited and restricted to those users who agree to comply with the following terms of use. Regis University reserves the right to deny access to the Collection to any person who violates these terms of use or who seeks to or does alter, avoid or supersede the functional conditions, restrictions and limitations of the Collection. The site may be used only for lawful purposes. The user is solely responsible for knowing and adhering to any and all applicable laws, rules, and regulations relating or pertaining to use of the Collection. All content in this Collection is owned by and subject to the exclusive control of Regis University and the authors of the materials.
    [Show full text]
  • Miineport W1 Series User's Manual
    MiiNePort W1 Series User’s Manual Edition 5.0, November 2017 www.moxa.com/product © 2017 Moxa Inc. All rights reserved. MiiNePort W1 Series User’s Manual The software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement. Copyright Notice © 2017 Moxa Inc. All rights reserved. Trademarks The MOXA logo is a registered trademark of Moxa Inc. All other trademarks or registered marks in this manual belong to their respective manufacturers. Disclaimer Information in this document is subject to change without notice and does not represent a commitment on the part of Moxa. Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time. Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use. This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication. Technical Support Contact Information www.moxa.com/support Moxa Americas Moxa China (Shanghai office) Toll-free: 1-888-669-2872 Toll-free: 800-820-5036 Tel: +1-714-528-6777 Tel: +86-21-5258-9955 Fax: +1-714-528-6778 Fax: +86-21-5258-5505 Moxa Europe Moxa Asia-Pacific Tel: +49-89-3 70 03 99-0 Tel: +886-2-8919-1230 Fax: +49-89-3 70 03 99-99 Fax: +886-2-8919-1231 Moxa India Tel: +91-80-4172-9088 Fax: +91-80-4132-1045 Table of Contents 1.
    [Show full text]
  • Finger RFC #1288
    Network Working Group D. Zimmerman Request for Comments: 1288 Center for Discrete Mathematics and Obsoletes: RFCs 1196, 1194, 742 Theoretical Computer Science December 1991 The Finger User Information Protocol Status of this Memo This memo defines a protocol for the exchange of user information. This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This memo describes the Finger user information protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies RFC 1196. Table of Contents 1. Introduction ........................................... 2 1.1. Intent ............................................... 2 1.2. History .............................................. 3 1.3. Requirements ......................................... 3 1.4. Updates .............................................. 3 2. Use of the protocol .................................... 4 2.1. Flow of events ......................................
    [Show full text]
  • AIS Data Profile 30 December 2016
    AIS Data Profile 30 December 2016 STIX Tab STIX Sub-Tab IN/OUT Examples Field Guidance Type Text Type STIX Core STIX Type BOTH [Company Name]:[Column A]- @id This is a required field - NCCIC will replace on xs:QName Schema restricted text [Company Unique ID] dissemination with NCCIC values. (partial) BOTH 1.1.1 @version This is a required field - DHS will not accepted stix:STIXPackageVersionEnum Vocabulary defined text anything other than 1.1.1 If anything other than the accepted value is submitted the field will be removed during the sanitization process. BOTH 2002-05-30T09:00:00 @timestamp This is a required field - Schema restricted text - xs:dateTime Schema restricted text This field should be date and time only. BOTH NA STIX_Header This is a required Container Object. stix:STIXHeaderType Container BOTH NA Indicators Container Object stix:IndicatorsType Container BOTH NA TTPs Container Object stix:TTPsType Container BOTH NA Courses_of_Action Container Object stix:CoursesOfActionType Container BOTH NA Exploit_Targets Container Object stix_common:ExploitTargetsType Container STIX Header Type BOTH Provides an unstructured, text Title Review Field - On automated dissemination this xs:string Free form text title field will be replaced by an auto-generated Title. The submitted contents will be reviewed/modified/sanitized and disseminated via human manual process. Future capabilities may eliminate the human review process. BOTH See Vocab Tab Package_Intent This is a required field - Reference the Vocab stixCommon:ControlledVocabularyStringType Vocabulary defined text Tab - stixVocabs:PackageIntentEnum-1.0 stixVocabs:PackageIntentEnum-1.0 If anything other than the accepted value is submitted the field will be removed during the sanitization process.
    [Show full text]
  • Section 4 Network Programming and Administration Exercises
    Lab Manual SECTION 4 NETWORK PROGRAMMING AND ADMINISTRATION EXERCISES Structure Page Nos. 4.0 Introduction 48 4.1 Objectives 48 4.2 Lab Sessions 49 4.3 List of Unix Commands 52 4.4 List of TCP/IP Ports 54 3.5 Summary 58 3.6 Further Readings 58 4.0 INTRODUCTION In the earlier sections, you studied the Unix, Linux and C language basics. This section contains more practical information to help you know best about Socket programming, it contains different lab exercises based on Unix and C language. We hope these exercises will provide you practice for socket programming. Towards the end of this section, we have given the list of Unix commands frequently required by the Unix users, further we have given a list of port numbers to indicate the TCP/IP services which will be helpful to you during socket programming. To successfully complete this section, the learner should have the following knowledge and skills prior to starting the section. S/he must have: • Studied the corresponding course material of BCS-052 and completed the assignments. • Proficiency to work with Unix and Linux and C interface. • Knowledge of networking concepts, including network operating system, client- server relationship, and local area network (LAN). Also, to successfully complete this section, the learner should adhere to the following: • Before attending the lab session, the learner must already have written steps/algorithms in his/her lab record. This activity should be treated as home- work that is to be done before attending the lab session. • The learner must have already thoroughly studied the corresponding units of the course material (BCS-052) before attempting to write steps/algorithms for the problems given in a particular lab session.
    [Show full text]
  • Terminal / Remote Access Server Reference Manual
    Terminal / Remote Access Server Reference Manual version 1.2 Reference Manual - Terminal / Remote Access Server Conventions To help with reading and using this reference manual, we will use the following conventions : Bold : ACS commands. Only commands are displayed in bold font, not parameters. Italic : Commands parameters and examples values are displayed in italic font. Text box All text typed during an ACS session GRAY Commands syntax - 2 - Reference Manual - Terminal / Remote Access Server CONTENTS AUDIT...................................................................................................................................5 CLOSE SESSION................................................................................................................8 DHCP...................................................................................................................................9 DOMAIN.............................................................................................................................11 EXIT...................................................................................................................................13 FINGER..............................................................................................................................14 HELP..................................................................................................................................15 IFCONFIG..........................................................................................................................16
    [Show full text]
  • Command Reference Master Index
    COMMAND REFERENCE MASTER INDEX Cisco lOS Release 12.0 Documentation also available on CD-ROM and the World Wide Web Cisco SYSTEMS Command Reference Master ndex Cisco lOS Release 12.0 Corporate Headquarters Cisco Systems Inc 170 West Tasman Drive San Jose CA 95134-1706 USA http/Iwwwcisco.com Tel 408 526-4000 800 553-NETS 6387 Fax 408 526-4100 Customer Order Number DOC-785857 Text Part Number 78-5857-01 CHANGE WITHOUT HE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO TO BE ACCURATE BUT ARE NOTICE ALL STATEMENTS INFORMATION AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED RESPONSIBILITY FOR THEIR PRESENTED WITHOUT WARRANTY OF ANY KIND EXPRESS OR IMPLIED USERS MUST TAKE FULL APPLICATION OF ANY PRODUCTS THE INFORMATION THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN YOU ARE UNABLE TO PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE IF COPY LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY CONTACT YOUR CISCO REPRESENTATIVE FOR with the limits for Class of Class devices This has been tested and found to comply The following information is for FCC compliance equipment interference when the 15 of the FCC rules These limits are to reasonable protection against harmful digital device pursuant to part designed provide if not installed and used environment This and can radiate radio-frequency energy and equipment is operated in consmercial equipment generates uses communications of this in residential area is in accordance with the instruction
    [Show full text]