#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'TCP/IP ReferenceTCP/IP ReferenceNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=13 ID="BP1"About This ReferenceThis reference describes TCP/IP (Transmission Control Protocol/Internet Protocol) concepts for NetWare® 4.1 software. This reference is written for network supervisors who are interested in learning about Novell's TCP/IP implementation.RENDERAS="SECT1"Chapter SummariesThis section briefly summarizes each chapter in this reference. Use these summaries to help you locate specific topics, or to help you decide which portions of this reference contain new information.IDREF="FM12930"Chapter 1, "Introduction to TCP/IP," provides general information about TCP/IP.IDREF="FM81316"Chapter 2, "TCP/IP Concepts," presents an overview of the TCP/IP suite of protocols and its use for connecting dissimilar computers.IDREF="FM99805"Chapter 3, "IP Addressing Concepts," describes how to assign IP addresses, Internet addresses, and subnetwork addresses.IDREF="FM54844"Chapter 4, "TCP/IP Routing Protocol Concepts," gives information about routing functions.IDREF="FM17675"Chapter 5, "Network Database File Management," presents information about how to use four name files to convert internal data into more identifiable network names.IDREF="FM89908"Chapter 6, "SNMP Concepts," describes how to use SNMP to exchange information about the configuration and status of nodes on a TCP/IP network.IDREF="FM20503"Chapter 7, "TCP/IP Configuration Parameters," gives information about how to configure the TCP/IP parameters.PAGENUM=14 ID="BP2"RENDERAS="SECT1"Conventions Used in This ReferenceThe NetWare 4.1 TCP/IP Reference uses the documentation conventions described in this section. Specifically, these conventions are used for the following:MARK=BULLETIDREF="FM78328"Parameter Paths IDREF="FM35718"TerminologyIDREF="FM80317"New Terms and Important InformationIDREF="FM22762"System Messages IDREF="FM24995"User InputIDREF="FM26816"Special CharactersIDREF="FM49928"Graphic SymbolsRENDERAS="SECT2"ID="FM78328"Parameter PathsThis reference uses a special format to show the path to a parameter. For example, rather than specifying "Load INETCFG; from the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"Protocols; from the CLASS=MENUITEM MOREINFO="NONE"Protocol Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"AppleTalk; from the CLASS=MENUITEM MOREINFO="NONE"AppleTalk Configuration menu, select CLASS=MENUITEM MOREINFO="NONE"Static Routes Configuration (the CLASS=MENUITEM MOREINFO="NONE"Configured Static Routes for On-Demand Calls menu appears); then press MOREINFO="NONE"<Insert> (the CLASS=MENUITEM MOREINFO="NONE"Static Route Configuration menu appears)," the following format is used:Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"AppleTalk > Select CLASS=MENUITEM MOREINFO="NONE"Static Routes Configuration (CLASS=MENUITEM MOREINFO="NONE"Configured Static Routes for On-Demand Calls menu appears) > Press MOREINFO="NONE"<Insert> (CLASS=MENUITEM MOREINFO="NONE"Static Route Configuration menu appears)The name of the menu that appears after each selection is specified only if it is not obvious.PAGENUM=15 ID="BP3"RENDERAS="SECT2"ID="FM35718"TerminologyThe following terms summarize frequently performed actions:MARK=BULLET"Select" means to use the cursor keys to highlight an item and press MOREINFO="NONE"<Enter>. "Enter" means to type the indicated text and press MOREINFO="NONE"<Enter> (as one complete operation). It is shown in one of two ways; for example:Enter MOREINFO="NONE"LOAD MOREINFO="NONE"INETCFG or MOREINFO="NONE"LOAD INETCFG MOREINFO="NONE"<Enter>RENDERAS="SECT2"ID="FM80317"New Terms and Important InformationHighlighting emphasizes new terms and important information.RENDERAS="SECT2"ID="FM22762"System MessagesRegular (nonboldface, nonitalic) monospaced character strings represent system prompts or responses; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"message exampleRENDERAS="SECT2"ID="FM24995"User InputThis reference uses the following conventions to denote user input:MARK=BULLETMOREINFO="NONE"Highlighted monospaced character strings represent user input, which must be entered exactly as shown; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD TCPIP MOREINFO="NONE"<Enter> or MOREINFO="NONE"Load tcpip MOREINFO="NONE"<Enter>Highlighted and lowercase character strings show descriptive names for items that you must replace with appropriate values. For example, in the following NetWare console command, you replace driver with the specific name of a driver:FORMAT="LINESPECIFIC"MOREINFO="NONE"UNBIND IP FROM driver MOREINFO="NONE"<Enter>
PAGENUM=16 ID="BP4"RENDERAS="SECT2"ID="FM26816"Special CharactersThis reference uses special characters to denote the following:MARK=BULLETAsterisks * in text denote third-party trademarks.Angle brackets < >, brackets [ ], braces { }, vertical bar |, parenthesis ( ), and quotation marks " are used as metacharacters and, as such, you must not type these as part of user input.Angle brackets < > enclose a descriptive name for any value that is provided as output by a computer; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"Error: <IP address> is illegal.
   Must be class A, B, or C.Characters enclosed in angle brackets can also represent keys; for example:MARK=BULLET"Press MOREINFO="NONE"<Ins>" means you press the MOREINFO="NONE"<Insert> key on your keyboard. Keys joined by a plus sign are pressed in combination. "Press MOREINFO="NONE"<Ctrl>+<Alt>+<Delete>" means you press those keys simultaneously.Square brackets [ ] enclose an option item; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IP TO board_name ADDR=ip_addr
   [MASK=mask_addr] MOREINFO="NONE"<Enter>If a command, such as the preceding one, is too long to fit on one line, it wraps to the next line; such a command must be entered after the console prompt (:) but before the end-of-line (EOL) character.Braces { } enclose multiple items separated by the vertical bar | character. You must specify only one of the items; for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD TCPIP [FORWARD={YES|NO}]MOREINFO="NONE"<Enter>Vertical bars | separate items in a list of alternatives. If the list is enclosed in square brackets [ ], you can use any one or none of the items. If the list is enclosed in braces { }, you must use any one, but only one, of the items. PAGENUM=17 ID="BP5"RENDERAS="SECT2"ID="FM49928"Graphic SymbolsIn printed documentation, the following symbols appear in the left margin to identify different categories of information:PERFORMANCE="REQUIRED"This symbol identifies the first step of a procedure. To accomplish a specific task, follow the steps in the procedure.This symbol indicates sidelights, discussions, and general points of interest related to the current subject.This symbol points out key concepts or facts about the product. This symbol alerts you to situations that can produce critical or irreversible errors if you do not follow instructions carefully.This symbol points out hints, tips, or helpful information that you should know.Online documentation omits these symbols, but either maintains the font change or labels the information for easy identification.RENDERAS="SECT1"Related Novell PublicationsSee the following Novell publications for related information.This reference describes the TCP/IP NLM, which is required by all NetWare applications that use TCP/IP. Use this reference with the appropriate versions of the documentation to learn more about NetWare. The following NetWare documents are available from any authorized Novell dealer:MARK=BULLETBOOK="cfg1_enu" COLLECTION="nw41"NetWare 4.1 Basic Protocol Configuration GuideBOOK="cfg2_enu" COLLECTION="nw41"NetWare 4.1 Advanced Protocol Configuration and Management GuideBOOK="nlsp_enu" COLLECTION="nw41"NetWare 4.1 NLSP  Migration GuideBOOK="ipxrtenu" COLLECTION="nw41"NetWar 4.1 IPX  ReferenceBOOK="atrefenu" COLLECTION="nw41"NetWare 4.1 AppleTalk* ReferencePAGENUM=17 ID="BP6"PAGENUM=18The following publications are also related to NetWare:MARK=BULLETNetWare NFS Supervisor's Guide, Part Number 100-000955-001, Novell, Inc., 1991.Network C for NLM Software Developer's Kit, Part Number 884-000011-003, Novell, Inc., 1991.RENDERAS="SECT1"Additional ReadingThe following Internet documents define and provide background information about the standard TCP/IP software:MARK=BULLETCase, J. and others, A Simple Network Management Protocol, RFC 1098, University of Tennessee at Knoxville, April 1989.Deering, S., ICMP Router Discovery Messages, RFC 1256, September 1991.Hedrick, C., Routing Information Protocol, RFC 1058, Rutgers University, June 1988.McCloghrie, K. and M. Rose, Management Information Base for Network Management of TCP/IP-Based Internets: MIB II, RFC 1213, Hughes LAN and Performance System International, March 1991.Mills, D., Exterior Gateway Protocol Formal Specification, RFC 904, International Telegraph and Telephone Co., April 1984.J. Mogul and J. Postel, Internet Standard Subnetting Procedure, RFC 950, Stanford University and ISI, August 1985.Moy, J., OSPF Version 2, RFC 1583, Proteon, March 1994.Plummer, D.C., Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48-bit Addresses for Transmission on Ethernet Hardware, RFC 826, Massachusetts Institute of Technology, November 1982.Postel, J. B. and Reynolds, J. K., Standard for the Transmission of IP Datagrams over IEEE 802 Networks, RFC 1042, USC/Information Sciences Institute, February 1988.PAGENUM=19 ID="BP7"Postel, J. B., Internet Control Message Protocol-DARPA Internet Program Protocol Specification, RFC 792, USC/Information Sciences Institute, September 1981.Postel, J. B., Internet Protocol, RFC 791, USC/Information Sciences Institute, September 1981.Postel, J. B., Transmission Control Protocol-DARPA Internet Program Protocol Specification, RFC 793, USC/Information Sciences Institute, September 1981.Postel, J. B., User Datagram Protocol, RFC 768, USC/Information Sciences Institute, August 1980.Tsuchiya, P., On the Assignment of Subnet Numbers, RFC 1219, Bellcore, April 1991.The preceding protocol specifications, as well as other protocol-related information, are gathered in the DDN Protocol Handbook, which is available from the following centers:TYPE="VERT"DDN Network Information Center14200 Park Meadow Dr., Suite 200Chantilly, VA 22021, USATYPE="VERT"Defense Technical Information CenterCameron StationAlexandria, VA 22314, USAThe following publications provide background information about computer networks and the principles, protocols, and architecture of TCP/IP:MARK=BULLETComer, Douglas, Internetworking with TCP/IP, Volume I, Prentice-Hall, 1991.Tanenbaum, Andrew S., Computer Networks, Prentice-Hall, 1988.LABEL="1"PAGENUM=1 ID="BP8"ID="FM12930"Introduction to TCP/IPThis chapter introduces TCP/IP as well as lists the files and features used by the Novell® TCP/IP implementation. The following topics are discussed:MARK=BULLETIDREF="FM25475""TCP/IP Concepts"This section describes the history of TCP/IP and general TCP/IP concepts.IDREF="FM37422""TCP/IP Subsystem Contents"This section lists the NetWare® Loadable ModuleTM (NLMTM) files and database files.IDREF="FM14866""TCP/IP Features"This section provides a list of Novell's TCP/IP features.RENDERAS="SECT1"ID="FM25475"TCP/IP ConceptsTCP/IP (Transmission Control Protocol/Internet Protocol) is a popular suite of standard networking protocols. These protocols are widely used, enabling dissimilar nodes in a heterogeneous environment to communicate with one another.IDXID="w9117"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9118"BOOK="_idx" COLLECTION="nw41" TIDREF="i1888"The general concept of connecting a network of dissimilar computers arose from research conducted by the 
Defense Advanced Research Projects Agency (DARPA)IDXID="w9119"BOOK="_idx" COLLECTION="nw41" TIDREF="i912"
. Within the framework of that research, DARPA developed the TCP/IP suite of protocols to communicate among networks and implemented an internetwork called the IDXID="w9120"BOOK="_idx" COLLECTION="nw41" TIDREF="i293"ARPAnet, which later evolved into the IDXID="w9121"BOOK="_idx" COLLECTION="nw41" TIDREF="i1863"InternetPAGENUM=2 ID="BP9". The TCP/IP suite of protocols defines formats and rules for the transmission and receipt of information independent of any given network organization or computer hardware. Although the protocols were developed for the Internet, TCP/IP is now the de facto standard as numerous private and public organizations use it for their networking.The network, as conceived by DARPA and implemented with the TCP/IP suite of protocols, is a packet-switched networkIDXID="w9122"BOOK="_idx" COLLECTION="nw41" TIDREF="i3195"
. A packet-switched network transmits information on the network in small segments, called IDXID="w9123"BOOK="_idx" COLLECTION="nw41" TIDREF="i3194"packets. If one computer transmits a lengthy file to another computer, for example, the file is divided into many packets at the origin and then reassembled at the destination. The TCP/IP protocols define the format of these packets. This definition includes the origin of the packet, the destination of the packet, the length of the packet, and the type of packet, as well as the way computers on the networks are to receive and retransmit packets.TCP/IP is a transport subsystem that brings TCP/IP connectivity to the NetWare operating system. This subsystem includes a collection of 
NLM files for NetWare designed to support applications requiring TCP/IP connectivity, such as the NetWare for NFS* (Network File System) product. IDXID="w9124"BOOK="_idx" COLLECTION="nw41" TIDREF="i2859"IDXID="w9125"BOOK="_idx" COLLECTION="nw41" TIDREF="i3907"
TCP/IP routing capabilities allow forwarding of IP traffic from one network to another. TCP/IP uses the Routing Information Protocol (RIP), Exterior Gateway Protocol (EGP), or Open Shortest Path First (OSPF) protocol to communicate with other routers. This lets all routers in the internetwork discover the internetwork configuration without human intervention.In addition to routing services, TCP/IP provides transport interfaces for the use of higher-level network services. This interface is used by NFS and by third-party applications written for either the 4.3BSD* UNIX® socket interface or the STREAMSTM Transport Layer IDXID="w9126"BOOK="_idx" COLLECTION="nw41" TIDREF="i4563"
Interface (TLI).IDXID="w9127"BOOK="_idx" COLLECTION="nw41" TIDREF="i4303"IDXID="w9128"BOOK="_idx" COLLECTION="nw41" TIDREF="i2368"
TCP/IP supports Ethernet, token ring, FDDI, and ARCNET* networks through the Novell IDXID="w9129"BOOK="_idx" COLLECTION="nw41" TIDREF="i3081"
Open Data-Link InterfaceTM (ODITM) specification. Therefore, it works with any network adapters of these types supported by a NetWare LAN driver certified for version 3.12 or later.For more information about TCP/IP and the TCP/IP suite of protocols, refer to IDREF="FM81316"Chapter 2, "TCP/IP Concepts." For information about TCP/IP addressing and TCP/IP subnetworking, refer to IDREF="FM99805"Chapter 3, "IP Addressing Concepts."PAGENUM=3 ID="BP10"RENDERAS="SECT1"ID="FM37422"TCP/IP Subsystem ContentsNetWare 4.1 TCP/IP Subsystem software includes the following NLM and database files:IDXID="w9130"BOOK="_idx" COLLECTION="nw41" TIDREF="i2925"MARK=BULLETNetWare TCP/IP NLM file (TCPIP.NLM)IDXID="w9131"BOOK="_idx" COLLECTION="nw41" TIDREF="i4448"Simple Network Management Protocol NLM file (IDXID="w9132"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP.NLM)SNMP Event Logger NLM file (IDXID="w9133"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMPLOG.NLM)TCP/IP Console NLM file (IDXID="w9134"BOOK="_idx" COLLECTION="nw41" TIDREF="i4445"
TCPCON.NLM)IP static route Configuration NLM file (IPCONFIG.NLM)IDXID="w9135"BOOK="_idx" COLLECTION="nw41" TIDREF="i1921"Sample Internet database files (HOSTS, NETWORKS, PROTOCOL, and SERVICES)IDXID="w9136"BOOK="_idx" COLLECTION="nw41" TIDREF="i925"ICMP Echo NLM files (IDXID="w9137"BOOK="_idx" COLLECTION="nw41" TIDREF="i3314"IDXID="w9138"BOOK="_idx" COLLECTION="nw41" TIDREF="i4536"
PING.NLM and TPING.NLM)BootP Forwarder NLM file (IDXID="w9139"BOOK="_idx" COLLECTION="nw41" TIDREF="i506"
BOOTPFWD.NLM)IP Filter support (IDXID="w9140"BOOK="_idx" COLLECTION="nw41" TIDREF="i1498"
IPFLT.NLM)IP IDXID="w9141"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"
Tunnel (IDXID="w9142"BOOK="_idx" COLLECTION="nw41" TIDREF="i4607"
IPTUNNEL.LAN)The TCP/IP NLM files are installed in the SYS:SYSTEM directory. The Internet database files are installed in the SYS:ETC\SAMPLES directory.IDREF="FM93553"Figure 1-1 shows the TCP/IP Subsystem Overview.PAGENUM=4 ID="BP11"LABEL="1-1" FLOAT="0"IDXID="w9143"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"ID="FM93553"TCP/IP Subsystem OverviewFILEREF="fig1_10.tif"IDREF="FM59709"Figure 1-2 illustrates the architectural relationships of the TCP/IP subsystem.PAGENUM=5 ID="BP12"LABEL="1-2" FLOAT="0"IDXID="w9144"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"ID="FM59709"TCP/IP Subsystem Architectural RelationshipsFILEREF="fig1_20.tif"RENDERAS="SECT1"ID="FM14866"TCP/IP FeaturesIDXID="w9145"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"The TCP/IP software includes the following features:MARK=BULLETIDREF="FM13618"TCP/IP Application SupportIDREF="FM10980"IP RoutingMARK=BULLETIDREF="FM40346"RIPIDREF="FM39408"OSPFIDREF="FM34709"EGPIDREF="FM16324"Static RoutingIDREF="FM16751"Router DiscoveryIDREF="FM14279"Subnetwork SupportMARK=BULLETIDREF="FM23946"Variable Subnetwork SupportIDREF="FM18703"Subnet ZeroPAGENUM=6 ID="BP13"IDREF="FM27922"Directed BroadcastIDREF="FM23104"BOOTP ForwardingIDREF="FM36226"TCP/IP Network ManagementIDREF="FM22281"Internetworking Configuration UtilityIDREF="FM21880"LAN ConnectivityThe rest of this chapter discusses these features in more detail.RENDERAS="SECT2"ID="FM13618"TCP/IP Application SupportTCP/IP application support provides a transport interface for the use of higher-level network services. This interface is used by NetWare NFS and by third-party applications that are written for either the 4.3BSD UNIX socket interface or the STREAMS Transport Layer Interface (TLI). The transport interface provides access to either the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP) transport services.RENDERAS="SECT2"ID="FM10980"IP RoutingTCP/IP's IP routing capabilities allow forwarding of IP traffic from one network to another. Routers on a TCP/IP internetwork exchange information about themselves. The TCP/IP software supports link state, distance vector, and static routing.RENDERAS="SECT3"ID="FM40346"RIPThe Routing Information Protocol (RIP) uses the distance vector algorithm as the basis for routing operations and decisions. RIP is a standard protocol that is based on the IDXID="w9146"BOOK="_idx" COLLECTION="nw41" TIDREF="i1152"
distance vector algorithm. The majority of the TCP/IP sites use RIP.RENDERAS="SECT3"ID="FM39408"OSPFOpen Shortest Path First (OSPF) uses the link state algorithm as the basis for routing operations and decisions. OSPF is a new IGP protocol that is based on a IDXID="w9147"BOOK="_idx" COLLECTION="nw41" TIDREF="i2115"
link state algorithm. It is rapidly gaining acceptance in many public and private sites that have large and complex networks.PAGENUM=7 ID="BP14"RENDERAS="SECT3"ID="FM34709"EGPThe Exterior Gateway Protocol (EGP) is used to exchange routing information between IP internetworks that are under different administrative control.RENDERAS="SECT3"ID="FM16324"Static RoutingStatic routes are configured manually. A static route defines which router to use to reach a remote destination. Routers can use static routes instead of, or in addition to, the routes learned from dynamic routing protocols.RENDERAS="SECT2"ID="FM16751"Router DiscoveryThe Router Discovery protocol is used by routers to advertise their presence on a network. Hosts can use the router discovery protocol to learn about routers on the network.RENDERAS="SECT2"ID="FM14279"Subnetwork SupportTCP/IP allows you to divide your networks into subnetworks for greater ease in administration and troubleshooting.RENDERAS="SECT3"ID="FM23946"Variable Subnetwork SupportTCP/IP allows you to divide your networks into variable size subnetworks for greater ease in administration and troubleshooting. Usually, these subnetworks have a uniform size and can accommodate the same number of hosts. NetWare 4.1 software provides the additional support for different size subnetworks. It does this by allowing the use of variable-length subnetwork masks.RENDERAS="SECT3"ID="FM18703"Subnet ZeroTCP/IP provides support for subnetwork zero when using the OSPF or RIP II routing protocols. These routing protocols include the subnetwork mask and remove the ambiguity between the zero subnetwork and the natural network.PAGENUM=8 ID="BP15"RENDERAS="SECT2"ID="FM27922"Directed BroadcastA directed broadcast is sent to all hosts on a particular IP network or subnetwork. Some applications use directed broadcasts to find or announce services.RENDERAS="SECT2"ID="FM23104"BOOTP ForwardingBOOTP is a protocol used by some hosts to obtain their IP addresses. The host broadcasts a BOOTP request on the local network. If the BOOTP server is attached to the same network as the host, it receives the request and replies with a packet that contains the host's address. If the server is on a different network, a BOOTP forwarder must direct the broadcast to a BOOTP server and forward the reply to the host. The TCP/IP software provides the BOOTPFWD.NLM file, which enables your machine to forward BOOTP request/reply packets between the BOOTP server and BOOTP clients. BOOTP forwarding can be configured for use with four different BOOTP servers.RENDERAS="SECT2"ID="FM36226"TCP/IP Network ManagementYou can monitor and troubleshoot your TCP/IP internetwork with SNMP. SNMP is the most popular network management protocol in the TCP/IP protocol suite. It lets TCP/IP-based network management stations gather information about the configuration and status of nodes on a TCP/IP-based internetwork. RENDERAS="SECT2"ID="FM22281"Internetworking Configuration UtilityThe Internetworking configuration utility (INETCFG) is a menu-driven utility that simplifies the task of configuring LANs to operate with multiple network protocols. INETCFG supersedes the manual use of most LOAD and BIND commands.INETCFG uses a series of windows, menus, and dialog boxes from which you configure related sets of options. This interface enables you to enter names of new configurations, specify protocol and bind options, and override defaults without using the command line.PAGENUM=9 ID="BP16"RENDERAS="SECT2"ID="FM21880"LAN ConnectivityThe TCP/IP software provides connectivity for workstations and servers connected to LAN media such as Ethernet, FDDI, token ring, and ARCNET.RENDERAS="SECT3"ID="FM23068"Permanent ConnectionsPermanent connections can be established during system initialization. These connections stay up continually. If a link error breaks the connection, it is retried automatically.LABEL="2"PAGENUM=11 ID="BP17"ID="FM81316"TCP/IP ConceptsThis chapter contains an overview of the TCP/IP suite of protocols. In addition, it discusses using TCP/IP to connect dissimilar computers. It highlights the main features of TCP/IP for users familiar with network protocols or networking. The following topics are discussed:MARK=BULLETIDREF="FM39439""Overview of TCP/IP Protocol Usage"This section describes how applications use TCP/IP and the OSI protocol layers to transfer data.ID="FM35963"IDREF="FM10290""Internet Protocol"This section describes IP datagrams and how they are transmitted.ID="FM32962"IDREF="FM11169""Routing"This section describes routing, routes, IP addresses, and sending and receiving nodes.ID="FM39582"IDREF="FM23670""Error and Control Messages"This section describes the Internet Control Message Protocol (ICMP).IDREF="FM40744""Transport Layer Protocols"This section describes the User Datagram Protocol (UDP), which allows applications to exchange packets of information, and the Transmission Control Protocol (TCP), which provides reliable packet transmission.PAGENUM=11 ID="BP18"PAGENUM=12IDREF="FM27564""Physical and Internet Addresses"This section describes physical and Media Access Control (MAC) messages and how TCP/IP protocols translate the destination IP address to the physical address.ID="FM27732"IDREF="FM13615""Internet Address to Physical Address Translation"This section describes the mapping of the Internet address to the physical address and the address resolution cache.RENDERAS="SECT1"The TCP/IP Suite of ProtocolsThe protocols in the TCP/IP suite roughly correspond to a network communications model defined by the IDXID="w9148"BOOK="_idx" COLLECTION="nw41" TIDREF="i1859"
International Organization for Standardization (ISO). This model is called the Open Systems Interconnection (OSI) reference model. The OSI model describes an ideal computer network system in which communication on the network occurs between processes at discrete and identifiable layers. Each layer on a given host provides services to layers above it and receives services from the layers below it. IDREF="FM57736"Figure 2-1 illustrates the seven layers of the OSI reference model as defined by ISO, and the roughly corresponding layers of the TCP/IP protocol suite.PAGENUM=13 ID="BP19"LABEL="2-1" FLOAT="0"IDXID="w9149"BOOK="_idx" COLLECTION="nw41" TIDREF="i3090"ID="FM57736"OSI Reference Model and Corresponding TCP/IP LayersFILEREF="b_1.tif"IDXID="w9150"BOOK="_idx" COLLECTION="nw41" TIDREF="i3592"
The layering system lets developers concentrate their efforts on the functions in a given layer. It is not necessary for them to create all the mechanisms to send information across the network. They have to know only what services the software needs to provide to the layer above it, what services the layers below it can provide to the software, and which protocols in the suite provide those services.PAGENUM=14 ID="BP20"IDREF="FM92402"Table 2-1 lists some of the more common protocols in the TCP/IP suite and the services they provide.LABEL="2-1" PGWIDE=1 TOCENTRY="1"IDXID="w9151"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"ID="FM92402"TCP/IP ProtocolsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="26*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"ServiceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Internet Protocol (IP)COLNAME=2 ROTATE="0" MOREROWS="0"Provides packet delivery services (routing) between nodes.COLNAME=1 ROTATE="0" MOREROWS="0"Internet Control Message Protocol (ICMP)COLNAME=2 ROTATE="0" MOREROWS="0"Controls transmission of error and control messages between hosts and gateways.COLNAME=1 ROTATE="0" MOREROWS="0"Address Resolution Protocol (ARP)COLNAME=2 ROTATE="0" MOREROWS="0"Maps Internet addresses to physical addresses.COLNAME=1 ROTATE="0" MOREROWS="0"Reverse Address Resolution Protocol (RARP)COLNAME=2 ROTATE="0" MOREROWS="0"Maps physical addresses to Internet addresses.COLNAME=1 ROTATE="0" MOREROWS="0"Transmission Control Protocol (TCP)COLNAME=2 ROTATE="0" MOREROWS="0"Provides reliable data-stream delivery service between clients.COLNAME=1 ROTATE="0" MOREROWS="0"User Datagram Protocol (UDP)COLNAME=2 ROTATE="0" MOREROWS="0"Provides unreliable datagram delivery service between clients.COLNAME=1 ROTATE="0" MOREROWS="0"File Transfer Protocol (FTP)COLNAME=2 ROTATE="0" MOREROWS="0"Provides application-level services for file transfer.COLNAME=1 ROTATE="0" MOREROWS="0"TELNETCOLNAME=2 ROTATE="0" MOREROWS="0"Provides terminal emulation.COLNAME=1 ROTATE="0" MOREROWS="0"Routing Information Protocol (RIP)COLNAME=2 ROTATE="0" MOREROWS="0"Allows the exchange of distance vector routing information between routers.COLNAME=1 ROTATE="0" MOREROWS="0"Open Shortest Path First (OPSF) ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"Allows the exchange of link state routing information between routers.COLNAME=1 ROTATE="0" MOREROWS="0"Exterior Gateway Protocol (EGP)COLNAME=2 ROTATE="0" MOREROWS="0"Allows the exchange of routing information between exterior routers.PAGENUM=14 ID="BP21"PAGENUM=15RENDERAS="SECT1"ID="FM39439"Overview of TCP/IP Protocol UsageApplications developed for TCP/IP generally use several of the protocols in the suite. The sum of the layers of the protocol suite is also known as the protocol stack. User applications communicate with the top layer of the protocol suite. The top-level protocol layer on the source computer passes information to the lower layers of the stack, which in turn pass it to the physical network. The physical network transfers the information to the destination computer. The lower layers of the protocol stack on the destination computer pass the information to higher layers, which in turn pass it to the destination application.IDXID="w9152"BOOK="_idx" COLLECTION="nw41" TIDREF="i3603"Each protocol layer within the TCP/IP suite has various functions; these functions are independent of the other layers. Each layer, however, expects to receive certain services from the layer beneath it, and each layer provides certain services to the layer above it.IDXID="w9153"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDREF="FM93540"Figure 2-2 shows the layers of the TCP/IP suite. Each layer of the protocol stack on the source computer communicates with that same layer on the destination computer. The layers at the same level on the source and destination computers are IDXID="w9154"BOOK="_idx" COLLECTION="nw41" TIDREF="i3287"peers. The application on the source computer and the application on the destination computer are also peers. From the perspective of the software developer or user, the transfer takes place as if the peer layers sent their packets directly to one another.PAGENUM=16 ID="BP22"LABEL="2-2" FLOAT="0"ID="FM93540"TCP/IP Protocol LayersFILEREF="b_20.tif"An application for transferring files using TCP, for instance, performs the following operations to send the file contents:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The Application layer passes a stream of bytes to the Transport layer on the source computer.The Transport layer divides the stream into TCP segments, adds a header with a sequence number for that segment, and passes the segment to the Internet (IP) layer. The checksum is computed.The IP layer creates a packet with a data portion containing the TCP segment. The IP layer adds a packet header containing source and destination IP addresses. The IP layer also determines the physical address of the destination computer or intermediate computer on the way to the destination host. It passes the packet and the physical address to the Data-Link layer. The checksum is computed again.PAGENUM=17 ID="BP23"The Data-Link layer transmits the IP packet in the data portion of a data-link frame to the destination computer. If the destination is an intermediate computer, then Step 3 happens again until the final destination is reached.At the destination computer, the Data-Link layer discards the data-link header and passes the IP packet to the IP layer.The IP layer checks the IP packet header. If the checksum contained in the header does not match the checksum computed by the IP layer, it discards the packet.If the checksums match, the IP layer discards the IP packet header and passes the TCP segment to the TCP layer. The TCP layer checks the sequence number to determine whether the segment is the correct segment in the sequence.The TCP layer computes a checksum for the TCP header and data. If the computed checksum does not match the checksum transmitted in the header, the TCP layer discards the segment. If the checksum is correct and the segment is in the correct sequence, the TCP layer sends an acknowledgment to the source computer.The TCP layer discards the TCP header and passes the bytes in the segment just received to the application.The application on the destination computer receives a stream of bytes, just as if it were directly connected to the application on the source computer.The following sections describe these interactions in more detail:MARK=BULLETID="FM14999"IDREF="FM10290""Internet Protocol" IDREF="FM11169""Routing"IDREF="FM23670""Error and Control Messages"ID="FM22290"IDREF="FM40744""Transport Layer Protocols"IDREF="FM27564""Physical and Internet Addresses"PAGENUM=18 ID="BP24"RENDERAS="SECT1"ID="FM10290"Internet ProtocolIDXID="w9155"BOOK="_idx" COLLECTION="nw41" TIDREF="i1866"
In the TCP/IP protocol suite, all packets are delivered by the IDXID="w9156"BOOK="_idx" COLLECTION="nw41" TIDREF="i4674"
IP datagram delivery service. Packet delivery is not guaranteed by this service. A packet can be misdirected, duplicated, or lost on the way to its destination. The service is connectionless because all packets are transmitted independently of any other packets. This is in contrast to a telephone network, for instance, where a circuit is established and maintained.TCP/IP applications using the IP datagram delivery service keep track of the delivery status by expecting to receive replies from the destination node, or by using one of the Transport-layer protocols within the TCP/IP suite.IP defines the form that packets must take and the ways to handle packets when they are transmitted or received. The form the packet takes is called an IP datagram. An IP datagram is analogous to a physical frame transmitted on a network. A datagram has a header section containing the sender's and the receiver's IP addresses among other information, and a data section. IDREF="FM49238"Figure 2-3 shows the general form of an IP datagram. Each network type transmits IP packets in the data section of its physical frame. IDXID="w9157"BOOK="_idx" COLLECTION="nw41" TIDREF="i1866"LABEL="2-3" FLOAT="0"ID="FM49238"IP Datagram StructureFILEREF="b_60.tif"PAGENUM=18 ID="BP25"PAGENUM=19When an IP datagram is sent over a network, it is encapsulated in the data portion of the network frame of the physical network. Because the length of the network frame is set independently of IP, by the technical requirements of the physical network, an IP datagram might not fit in a network frame. Also, in traveling to its destination, a datagram can pass across many different types of networks with different physical network frame lengths. Therefore, a router receiving IP datagrams can find the received datagram too big to be forwarded to the next network.To handle this aspect of packet transmission, IP specifies a method for breaking datagrams into fragments. Then the fragments of an IP datagram are IDXID="w9158"BOOK="_idx" COLLECTION="nw41" TIDREF="i1563"reassembled when they arrive at the final destination. Reassembling framents reconstructs the entire IP datagram.RENDERAS="SECT1"ID="FM11169"IDXID="w9159"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"RoutingIDXID="w9160"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"The term routing refers to the transmission of a datagram from one node to another on the same or a different network. The route refers to the paths that are chosen to transmit an IP datagram from its origin to its destination, based on the IP addresses contained in the datagram.Within a network, a node sending an IP datagram can perform the following actions directly:MARK=BULLETQuery all the other nodes on the network for the physical address corresponding to an IP addressEncapsulate the IP datagram in a physical frame containing that physical addressSend the encapsulated IP datagram directly to the destination node's physical address on the networkWhen a datagram is sent to a node on another network, the network portions of the originating IP address and the destination IP address are different. The sending node recognizes this difference and sends the packet to the router that connects the originating network with other networks, as shown in IDREF="FM33238"Figure 2-4. Two networks can be connected only if one router is attached to both networks and can pass data in a form that is compatible with both networks.PAGENUM=20 ID="BP26"LABEL="2-4" FLOAT="0"ID="FM33238"Network RouterFILEREF="b_50.tif"The sending node has a table of IP addresses for one or more computers on the network that serve as routers to other networks. It looks for the IP address of a router in its table and broadcasts an ARP request to the router for the physical address of the router. It then sends the packet containing the IP datagram to the router's physical address. When the router receives the IP datagram, it uses the IP address in the datagram to send the packet to its final destination in a similar manner. If needed, the router sends the packet to the address of another router that can route the packet to its destination.PAGENUM=21 ID="BP27"RENDERAS="SECT1"ID="FM23670"Error and Control MessagesAnother protocol in the TCP/IP suite is the IDXID="w9161"BOOK="_idx" COLLECTION="nw41" TIDREF="i1864"
Internet Control Message Protocol (ICMP). ICMP packets contain information about failures on the network: inoperative nodes and gateways, packet congestion at a gateway, and so on. The IP software, rather than the application, interprets an ICMP message. The IP software then takes the appropriate action with respect to the ICMP message independently of the application. Because an ICMP message might need to travel across several networks to reach its destination, it is encapsulated in the data portion of an IP datagram.ICMP is also used to test connectivity between two nodes. The originating node sends an ICMP echo request or PING and waits for an ICMP echo response from the destination.RENDERAS="SECT1"ID="FM40744"Transport Layer ProtocolsIDXID="w9162"BOOK="_idx" COLLECTION="nw41" TIDREF="i4564"IDXID="w9163"BOOK="_idx" COLLECTION="nw41" TIDREF="i4564"The Transport layer of the TCP/IP protocol suite consists of two protocols:  the IDXID="w9164"BOOK="_idx" COLLECTION="nw41" TIDREF="i4705"
User Datagram Protocol (UDP) and the IDXID="w9165"BOOK="_idx" COLLECTION="nw41" TIDREF="i4560"
Transmission Control Protocol (TCP). UDP provides an unreliable connectionless delivery service to send and receive messages from specific processes on the sending and receiving nodes. TCP adds reliable byte stream-delivery services on top of the IP datagram delivery service.RENDERAS="SECT2"UDPIDXID="w9166"BOOK="_idx" COLLECTION="nw41" TIDREF="i4705"
Within the TCP/IP suite, UDP allows applications to exchange individual packets of information over a network.UDP defines a set of destinations as IDXID="w9167"BOOK="_idx" COLLECTION="nw41" TIDREF="i3597"IDXID="w9168"BOOK="_idx" COLLECTION="nw41" TIDREF="i4705"protocol ports. The protocol also defines two types of protocol ports: well-knownIDXID="w9169"BOOK="_idx" COLLECTION="nw41" TIDREF="i4822"
 port assignments and dynamically bound portsIDXID="w9170"BOOK="_idx" COLLECTION="nw41" TIDREF="i1278"
. In the case of well-known port assignments, certain UDP port numbers are reserved for certain applications. The ports numbered between 1 and 255 are well-known port numbers and are assigned to certain widely used applications. All UDP applications use those same port numbers in the same way. In the case of dynamically bound ports, an application requesting services from a process must query the node first to identify which port the process uses. It can then direct UDP datagrams to that port.IDXID="w9171"BOOK="_idx" COLLECTION="nw41" TIDREF="i3597"PAGENUM=22 ID="BP28"UDP allows multiple clients to use the same port number and different IP addresses. The arriving UDP datagrams are delivered to the client that matches both the port number and destination address. If there is no matching client, the packet is dropped.The UDP datagram is encapsulated in one or more IP datagrams that are, in turn, encapsulated in physical frames. IDREF="FM97229"Figure 2-5 shows a UDP datagram encapsulated in an IP datagram, which is, in turn, encapsulated in an Ethernet frame. IDREF="FM97229"Figure 2-5 also illustrates how the concept of layeringIDXID="w9172"BOOK="_idx" COLLECTION="nw41" TIDREF="i2095"
, discussed at the start of this chapter, affects the construction of packets sent across the network.LABEL="2-5" FLOAT="0"ID="FM97229"UDP Datagram EncapsulationFILEREF="b_70.tif"In this example, the IP address directs the IP datagram to the correct node. At that destination, the IP software extracts the UDP datagram and delivers it to the UDP-layer software. The UDP-layer software delivers the UDP data and control information to the destination protocol port it specifies. The process at that port uses the data in the UDP datagram. The UDP datagram also contains a source protocol port so the destination process can reply correctly.PAGENUM=23 ID="BP29"RENDERAS="SECT2"TCPIDXID="w9173"BOOK="_idx" COLLECTION="nw41" TIDREF="i4443"
For applications that must send or receive large volumes of data, unreliable datagram delivery can become burdensome. Application programmers might have to develop extensive error handling and status information modules to track the progress and state of data transfer for every application. The TCP/IP suite of protocols avoids this problem by using 
TCP, a reliable byte stream-delivery protocol. TCP establishes a connection between two applications and sends a stream of bytes to a destination in exactly the same order that they left the source. Before transmission begins, the applications at both ends of transmission obtain a TCP port from their respective operating systems. These are analogous to the ports used by UDP. The application initiating the transfer, known as the client side, generally obtains a port dynamically. The application responding to the transfer request, known as the server side, generally uses a well-known TCPIDXID="w9174"BOOK="_idx" COLLECTION="nw41" TIDREF="i4443"
 port. The client side is typically the active side and initiates the connection to the passive server side.Like the UDP datagrams, TCP IDXID="w9175"BOOK="_idx" COLLECTION="nw41" TIDREF="i4443"segments are encapsulated in an IP datagram. TCP buffers the stream by waiting for enough data to fill a large datagram before sending a datagram. The stream is unstructured, which means that before transmission of data, both the sending and receiving applications must agree on the meaning of the contents of the stream. The TCP protocol uses IDXID="w9176"BOOK="_idx" COLLECTION="nw41" TIDREF="i1586"full-duplex transmission. Full duplex means two data streams can flow in opposite directions simultaneously. Thus, the receiving application can send data or control information back to the sending application while the sending application continues to send data.The TCP protocol gives each segment a sequence number. At the receiving end of the connection, the application checks successive sequence numbers to ensure that all the segments are received and processed in the order of the sequence numbers. The receiving end sends an acknowledgment to the sender for the segments received. TCP allows the sender to have several segments outstanding before the receiver must return an acknowledgment. When the sending node gets the acknowledgment, it indicates to the application that data sent last was sent successfully. If the sending node does not receive an acknowledgment for a segment within a certain time, it retransmits that segment. This scheme, called positive acknowledgment with retransmission, ensures that the stream delivery is reliable.IDXID="w9177"BOOK="_idx" COLLECTION="nw41" TIDREF="i76"PAGENUM=24 ID="BP30"RENDERAS="SECT1"ID="FM27564"Physical and Internet AddressesAt the Data-Link layer, the nodes on a network communicate with other nodes on that network using addresses specific to that network. A node can be a microcomputer, a file server, an intelligent printer, or any other device with its own TCP/IP implementation. Each node has a physical address for the specific hardware device that connects it to a network. The physical addresses have different forms on different networks, and they are assigned in different ways. For instance, a physical address on an Ethernet network is a 6-byte numeric value, such as 08-00-14-57-69-69. It is assigned by the manufacturer of the Ethernet interface hardware. CCITT X.25 networks use the X.121 standard for physical addresses, which consist of 14-digit numbers.IDXID="w9178"BOOK="_idx" COLLECTION="nw41" TIDREF="i3306"Physical addresses are also called Media Access Control (MAC) addresses. Throughout the rest of this chapter, all references to MAC or physical addresses assume physical addresses on Ethernet, token ring, or FDDI networks. Other network types use other algorithms for determining IP addresses.The IP address for a node is a logical address and is independent of any particular hardware or network topology; it has the same form, regardless of the media type. It is a 4-byte (32-bit) numeric value that identifies both a network and a local host or node (computer or other device) on that network. The 4-byte IP address is usually represented in dotted decimal notation. Each byte is represented by a decimal number, and dots separate the bytes; for example, 129.47.6.17. In some contexts, IP addresses are represented as hexadecimal numbers; for example, 0x81.0x2F.0x6.0x11, or in octal; for example, 0201.057.06.021.An IP address is mapped to a physical address using the Address Resolution Protocol (ARP) on broadcast networks such as Ethernet, token ring, or ARCNET.Nodes using the TCP/IP protocols translate the destination IP addresses to the physical addresses of MAC hardware to send packets to other nodes on the network. Each sending application sends its IP address in the packet as well. The receiving application can reply to the sender by using the source IP address from the packet.IDXID="w9179"BOOK="_idx" COLLECTION="nw41" TIDREF="i1866"IDXID="w9180"BOOK="_idx" COLLECTION="nw41" TIDREF="i1209"PAGENUM=25 ID="BP31"Because IP addresses are not dependent on any particular network type, they can be used to send packets from one network type to another network. On each network type, the TCP/IP software makes the correspondence between physical addresses and IP addresses on its network. If a packet is transmitted to another network, the TCP/IP software translates the destination IP address to the physical address of a router that will forward the packet to the remote network. The receiving application uses the source IP address, which was included in the packet, to reply to the sender in the same manner.IDXID="w9181"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"IDXID="w9182"BOOK="_idx" COLLECTION="nw41" TIDREF="i3306"RENDERAS="SECT1"ID="FM13615"Internet Address to Physical Address TranslationEach different network type uses a particular form for the packets sent by its nodes. These forms include, among other things, the physical address of the destination node. Each physical medium has its own physical address for nodes on that medium. The physical addresses are also called Media Access Control (MAC) addresses. Ethernet or token ring networks use 6-byte MAC addresses. ARCNET uses a 1-byte MAC address.An example of the Ethernet address is shown in IDREF="FM13526"Figure 2-6. The complete MAC address is always unique for each node. The first three bytes represent a unique vendor identification number, and the second three bytes, which can be duplicated across vendors, represent a vendor-assigned board identification number. IDXID="w9183"BOOK="_idx" COLLECTION="nw41" TIDREF="i2200"IDXID="w9184"BOOK="_idx" COLLECTION="nw41" TIDREF="i3306"IDXID="w9185"BOOK="_idx" COLLECTION="nw41" TIDREF="i2251"LABEL="2-6" FLOAT="0"ID="FM13526"Physical Ethernet AddressFILEREF="b_30.tif"IP addresses are independent of the hardware. When an IP packet is transmitted on the network, it is first encapsulated within the physical frame used by that network. IDREF="FM37009"Figure 2-7 shows an IP packet encapsulated in an Ethernet frame. The IP packet contains an Internet address for a node, but the Ethernet frame must have a physical address for it to be delivered on the network. Therefore, the sending node must be able to determine which physical address on the network corresponds to the IP address contained in the IP packet.PAGENUM=26 ID="BP32"LABEL="2-7" FLOAT="0"ID="FM37009"IP Datagram EncapsulationFILEREF="dataenc.tif"RENDERAS="SECT2"Mapping Internet Addresses to Physical AddressesAn IP address is mapped to a physical, or MAC, address using ARP on broadcast networks such as Ethernet, token ring, or ARCNET. When a node sends a packet using IP, it must determine which physical address on the network corresponds to the destination IP address specified in the IP packet. To find the physical address, the node broadcasts an ARP packet containing the destination IP address. The node with the specified destination IP address sends its physical address back to the requesting node.IDXID="w9186"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"IDXID="w9187"BOOK="_idx" COLLECTION="nw41" TIDREF="i3306"IDXID="w9188"BOOK="_idx" COLLECTION="nw41" TIDREF="i100"RENDERAS="SECT2"Address Resolution CacheIDXID="w9189"BOOK="_idx" COLLECTION="nw41" TIDREF="i99"
To speed packet transmissions and reduce the number of broadcast requests that must be examined by every node on the network, each node keeps an address resolution cache. Each time the node broadcasts an ARP request and receives a response, it creates an entry in its address resolution cache. The entry maps the IP address to the physical address. When the node sends another IP packet, it looks up the IP address in its cache. If it finds that IP address, the node uses the corresponding physical address for its packet. IDXID="w9190"BOOK="_idx" COLLECTION="nw41" TIDREF="i100"IDXID="w9191"BOOK="_idx" COLLECTION="nw41" TIDREF="i96"
The node broadcasts an ARP request only if the IP address is not in its cache.LABEL="3"PAGENUM=27 ID="BP33"ID="FM99805"IP Addressing ConceptsThis chapter describes assigning network addresses and subnetwork addresses. The following topics are discussed:MARK=BULLETIDREF="FM15161""Assigning IP Network Addresses"This section describes how to obtain and assign IP addresses as well as the various IP address classes.IDREF="FM22240""Creating Subnetworks"This section presents reasons for dividing your network into smaller networks and describes communication between subnetworks.RENDERAS="SECT1"ID="FM15161"Assigning IP Network AddressesAn IP address is necessary for a node to communicate with other nodes using the TCP/IP protocol suite, including nodes on other private networks as well as those on the Internet. Your network address could be determined in one of the following ways:IDXID="w9192"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"IDXID="w9193"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"MARK=BULLETIf you want your network to join the Internet community, you must first get a registered Internet address from the following organization:TYPE="VERT"DDN IDXID="w9194"BOOK="_idx" COLLECTION="nw41" TIDREF="i2863"
Network Information Center14200 Park Meadow Dr., Suite 200Chantilly, VA 22021USAPAGENUM=28 ID="BP34"If your network is not part of the Internet community, you can choose an arbitrary IP network address. If you choose your IP network address this way, IP addresses for all the nodes on the network must meet the following criteria:IDXID="w9195"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"MARK=BULLETThe network portion of each address must agree with the network address. For example, all nodes on the 129.47 network must use the 129.47 network address.The IP address for each node must be unique within your network.The rest of this section describes how to select an address class.RENDERAS="SECT2"IP Address ClassesEach 4-byte IP address is divided into two parts: MARK=BULLETA network portion, which identifies the networkA host portion, which identifies the node IP addresses are differentiated into three classes based on the two most significant bits of the first of four bytes. This is done so that routers can extract the network portion of the address efficiently.This division can fall at one of three locations within the 32-bit address. These divisions correspond to the three IP address classes: Class A, Class B, and Class C. Regardless of address class, all nodes on any single network share the same network portion; each node has a unique host portion.IDXID="w9196"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"IDXID="w9197"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"RENDERAS="SECT3"Class A AddressesA Class A IP address consists of a 1-byte network portion followed by a 3-byte host portion. The highest-order bit of the network portion is always set to 0. Thus, within an internetwork, there can be a total of 126 Class A networks (1 through 126), with more than 16 million nodes in each (networks 0 and 127 are reserved). PAGENUM=28 ID="BP35"PAGENUM=29For example (`n' = network address and `h' = host address):FORMAT="LINESPECIFIC"MOREINFO="NONE"Class A 0nnnnnnn.hhhhhhhh.hhhhhhhh.
    hhhhhhhh(7 bits of network address, 24 bits of host address)FILEREF="classa0.tif"RENDERAS="SECT3"Class B AddressesA Class B IP address consists of a 2-byte network portion followed by a 2-byte host portion. The two highest-order bits of the network portion are always set to 10. Thus, within a single internetwork there can be approximately 16,000 Class B networks (128.x through 191.x), with more than 65,000 nodes in each. For example (`n' = network address and `h' = host address):FORMAT="LINESPECIFIC"MOREINFO="NONE"Class B 10nnnnnn.nnnnnnnn.hhhhhhhh.
   hhhhhhhh(14 bits of network address, 16 bits of host address)FILEREF="classb0.tif"PAGENUM=29 ID="BP36"PAGENUM=30RENDERAS="SECT3"Class C AddressesA Class C IP address consists of a 3-byte network portion followed by a 1-byte host portion. The three highest-order bits of the network portion are always set to 110. Thus, within a single internetwork, there can be approximately 2 million Class C networks (192.x.x through 223.x.x), with up to 254 nodes in each. For example (`n' = network address and `h' = host address):FORMAT="LINESPECIFIC"MOREINFO="NONE"Class C 110nnnnn.nnnnnnnn.nnnnnnnn.
   hhhhhhhh(21 bits of network address, 8 bits of host address)FILEREF="classc0.tif"RENDERAS="SECT3"Identifying Network ClassesIDXID="w9198"BOOK="_idx" COLLECTION="nw41" TIDREF="i1757"IDXID="w9199"BOOK="_idx" COLLECTION="nw41" TIDREF="i2852"
When the first byte of an IP address fits in the range listed below, it identifies which of the three network classes that address belongs to:TYPE="VERT"MOREINFO="NONE"1-126 (1.h.h.h-126.h.h.h) Class AMOREINFO="NONE"128-191 (128.n.h.h-191.n.h.h) Class BMOREINFO="NONE"192-223 (192.n.n.h-223.n.n.h) Class CAn IP address beginning with 154 is a Class B address, with the first two bytes of the address representing the `n'etwork portion of the address and the last two representing the `h'ost portion. For example, an IP address of 154.1.0.3 means the IP network portion is 154.1.0.0, and the host portion on that network is #.#.0.3.PAGENUM=31 ID="BP37"The network portion of an IP address should be the same for all nodes on that network. The network interface in the server that is connecting to network 89.0.0.0 must have a unique IP host address assigned to it, such as 89.0.0.254.The key to selecting a number for the host portion of the IP address is to ensure that the number selected is unique; that is, that no other host on the network has the same IP address.RENDERAS="SECT2"Selecting an Appropriate Address ClassWhen selecting an IP address class, you must decide on both network numbers and host address portions. Because the first one, two, or three bits of the IP address determine how the entire address is to be interpreted and where the division between network address and host address portion is to occur, you should know the consequences of your choice. When deciding on a network class, you should consider the number of nodes to be supported on your TCP/IP network and the number of networks you plan to configure.IDXID="w9200"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"For example, if you use Class C addresses (the first three bits of the IP address are 110 binary), then you are restricted to 254 nodes on your network.RENDERAS="SECT2"Reserved IP AddressesThe IP addressing rules reserve the following types of IP addresses for special purposes:IDXID="w9201"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"IDXID="w9202"BOOK="_idx" COLLECTION="nw41" TIDREF="i3809"MARK=BULLETNetwork addresses. These are IP addresses in which the host portion is set to all zeros. For example, 129.47.0.0 is the network address (or network number) for a Class B network. These are addresses of networks rather than nodes on a network. By convention, no node is ever assigned a host portion consisting of all zeros.IDXID="w9203"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"IDXID="w9204"BOOK="_idx" COLLECTION="nw41" TIDREF="i2842"Broadcast addresses. These are addresses in which the host portion is set to all ones. A packet with a broadcast address is destined for every node on the network. By convention, no node is ever assigned a host portion consisting of all ones.IDXID="w9205"BOOK="_idx" COLLECTION="nw41" TIDREF="i1867"IDXID="w9206"BOOK="_idx" COLLECTION="nw41" TIDREF="i518"Loopback addresses. The network address 127.0.0.0, and all host addresses on that network, for example 127.0.0.1, are reserved.PAGENUM=32 ID="BP38"Reserved addresses. These are addresses in which the network portion consists of all zeros or all ones.RENDERAS="SECT1"ID="FM22240"ID="FM10211"Creating SubnetworksOne Internet network (at a single Internet network address) can be divided into one or more smaller networks. Listed below are some reasons to divide your network:MARK=BULLETTo use multiple media. It can be impossible, inconvenient, or too expensive to connect all nodes to a single network medium when these nodes are too far apart or already connected to different media.To reduce congestion. Traffic between nodes on a single network uses network bandwidth. As a result, more bandwidth is required when you have more nodes. Splitting nodes into separate networks reduces the number of nodes on a network. If nodes on a single, smaller network speak mostly to other nodes on the same network, congestion is reduced.To reduce CPU use. Reduction of CPU use on connected nodes is similar to reducing congestion. More nodes on a network cause more broadcasts on that network. Even if a broadcast is not sent to a particular node, each node on a network must react to every broadcast before deciding to accept it or discard it.To isolate a network. By splitting a larger network into smaller networks, you limit the impact of one network's problems on another. Such problems can include network hardware failure, such as an open Ethernet tap, or software failures, such as a broadcast storm.To improve security. On a broadcast network medium such as Ethernet, each node on a network has access to all packets sent on that network. By allowing sensitive network traffic only on one network, other network monitors can be prevented from accessing this sensitive traffic.To make efficient use of IP address space.PAGENUM=33 ID="BP39" If you are assigned a Class A or B network number and have multiple, small physical networks, you can divide the IP address space into multiple IP subnetworks and assign them to individual physical networks. Using this method, you do not have to obtain more IP network numbers for each physical network.RENDERAS="SECT2"Subnetwork Addresses and MasksEach subnetwork functions as if it were an independent network. To remote networks, however, the subnetworks collectively appear to be a single, discrete network. This means that the local network needs only one IP network address and that remote networks do not need to pay attention to the location of a node on a particular subnetwork.Communication between a node on a local subnetwork and a node on a different subnetwork is similar to communication between nodes on two different networks. To a user, routing between subnetworks is transparent. Internally, the IP software recognizes any IP addresses that are destined for a subnetwork and sends those packets to the router on that subnetwork.As in network-to-network communication, the routing information for subnetwork communication between subnetworks is maintained in the routing table (by IP) for each node or router. In the case of subnetworks, however, the information consists of the network address and the subnetwork address. When a network is divided into subnetworks, the host address portion of the IP address is divided into two parts, just as the IP address itself is divided into two parts. The host address portion specifies both the subnetwork of the IP network and the node on that subnetwork.Therefore, the 4-byte IP address has the following portions:FILEREF="netaddr.tif"PAGENUM=34 ID="BP40"For instance, if a network has the Class B IP network address portion 129.47, the remainder of the IP address can be divided into subnetwork addresses and host addresses. This division is controlled by the local network to allow the most flexibility for network development at the local site. For example, the subnetwork address could comprise four bits of the remaining two bytes. This allows 15 subnetworks, each with 4094 nodes. In another example, the subnetwork address could comprise eight bits, allowing 254 subnetworks (a subnetwork address of all ones is not valid), each with 254 nodes. NetWare® 4.1supports the use of all zeros in the subnetwork field (IDXID="w9207"BOOK="_idx" COLLECTION="nw41" TIDREF="i4870"
subnet zero). However, a subnetwork field with all ones denotes all subnets of a particular network; therefore, all ones for a subnetwork cannot be used as a local IP address.IDREF="FM92619"Figure 3-1 shows a single IP network divided into two subnetworks. The router shown has physical attachments and IP addresses on both subnetworks (129.47.128.1 and 129.47.192.1). It might also have physical devices and IP addresses (nn.nn.nn.nn) connecting it to other networks.LABEL="3-1" FLOAT="0"ID="FM92619"Network with Two SubnetworksFILEREF="b_80.tif"A subnetwork maskPAGENUM=35 ID="BP41" indicates how the host portion of the IP address is divided into subnetwork addresses and local host address portions. The network mask is a 32-bit number with all ones for all network and subnetwork address portions of the complete IP address and all zeros for host address portions. With a Class B IP network address portion of 129.47 and a 4-bit subnetwork address, for instance, the subnetwork mask consists of 20 ones and 12 zeros. In essence, a subnetwork mask extends the network address portion of an IP address locally. IDREF="FM66545"Figure 3-2 shows examples of IP network addresses, their relationship to the subnetwork mask, and the corresponding subnetwork.IDXID="w9208"BOOK="_idx" COLLECTION="nw41" TIDREF="i4318"LABEL="3-2" FLOAT="0"ID="FM66545"Subnetwork Mask and IP AddressesFILEREF="b_90.tif"RENDERAS="SECT2"Subnet ZeroSubnet zero is a subnetwork with all of the bits in the subnetwork field of the IP address set to 0. For example, subnetwork 130.57.0 with a mask of 255.255.240.0 is a subnetwork zero of network 130.57. See IDREF="FM60446"Figure 3-3.LABEL="3-3" FLOAT="0"ID="FM60446"Subnet ZeroFILEREF="subnz.tif"PAGENUM=36 ID="BP42"The official IP specification reserves the subnet zero addresses and does not allow them to be used as a subnetwork address. However, this policy wastes one subnetwork in the IP address space. To counteract this limitation, Novell's TCP/IP allows the use of subnetwork zero.RENDERAS="SECT2"ID="FM10697"Variable Size SubnetworksA subnetwork of a network can be further divided into smaller units, called variable size subnetworks. These subnetworks are called variable because the size, or length, of the subnetwork varies from subnetwork to subnetwork. When the length of the subnetwork mask increases, the size of the subnetwork decreases because the IP address has a fixed size of 32 bits.A subnetwork mask defines the number of bits that can be used to define the subnetwork and the number of bits to define the host. As the subnetwork mask increases, the number of hosts on a subnetwork decreases. As the subnetwork mask decreases, the number of hosts that can be defined increases. Some network configurations have individual subnetworks with a large number of hosts and other subnetworks with a small number of hosts. Using the same subnetwork masks on all subnetworks can mean either of the following:MARK=BULLETThe mask is too small and you do not have enough subnetwork numbers for all of your subnetworksThe mask is too big and you do not have enough host IDs for all of your hosts on a subnetwork.If the mask is too small or too big, use a variable size subnetwork. By varying the subnetwork mask used on a network, you can match the number and size of subnetworks to your configuration. For example, the subnetwork 1 of network 130.57 with mask 255.255.240.0, 130.57.16.0, can be further divided into 16 sub-subnetworks with 256 hosts each. (Actually, that creates 15 sub-subnetworks with 254 hosts each because subnetwork 16, host 0, and host 255 are not used.) 130.57.16.0   10000010.00111001.00010000.00000000 
   subnetwork 1PAGENUM=37 ID="BP43"130.56.17.0   10000010.00111001.00010001.00000000 
   sub-subnetwork 1 OSPF AND RIPII understand subnetwork masks and support variable size subnetworks. RIP does not work when the network is partitioned into variable length subnetworks, because RIP does not understand subnetwork masks.RENDERAS="SECT2"Assigning Subnetwork AddressesThe method of assigning subnetwork addresses described in this section summarizes the method suggested in RFC 1219, "On the Assignment of Subnetwork Numbers." For a complete description of this method, refer to RFC 1219.Because RIP packets do not carry subnetwork mask information, the RIP routing protocol imposes several restrictions on the use of subnetworks. If you are using RIP, use the same subnetwork mask for all subnetworks belonging to the same network. Using RIPII lifts this restriction.If you are installing the NetWare 4.1 software on a network with subnetworks, use the subnetwork mask already established for the network.Subnetwork addresses and host addresses are typically assigned in numeric order, where both the subnetwork and host addresses are assigned from the left edge of their field. By this method, the border between the subnetwork address and the host address becomes fixed when the first subnetwork (subnetwork address = 1) is assigned. If the number of hosts on a subnetwork or the number of subnetworks required exceeds the limits of the subnetwork mask, this method makes it difficult to adjust the subnetwork mask, because each host must be renumbered.To prepare for changes in the size of the subnetwork mask, RFC 1219 suggests that subnetworks be assigned from the left of the subnetwork address field, and that hosts be assigned, in numeric order, from the right of the host address field. In this way, the subnetwork bits become a mirror image of the host bits. (You must still choose an initial subnetwork mask and use it for all subnetworks in the network.) For example, to apply this method to a Class B IP network with a subnetwork mask of 255.255.255.0, you assign subnetwork addresses as follows:TYPE="VERT"MOREINFO="NONE"1000 0000  (Decimal 128)MOREINFO="NONE"0100 0000  (Decimal 64)MOREINFO="NONE"1100 0000  (Decimal 192)PAGENUM=38 ID="BP44"MOREINFO="NONE"0010 0000  (Decimal 32)MOREINFO="NONE"...Then, you assign host addresses on each subnetwork as follows:TYPE="VERT"MOREINFO="NONE"0000 0001  (Decimal 1)MOREINFO="NONE"0000 0010  (Decimal 2)MOREINFO="NONE"0000 0011  (Decimal 3)MOREINFO="NONE"0000 0100  (Decimal 4)MOREINFO="NONE"...Using this method leaves a buffer zone between the subnetwork and host addresses, which allows for future network growth. The following table shows the relationship of the buffer zone to the subnetwork address and the host address: COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Subnetwork AddressCOLNAME=2 ROTATE="0" MOREROWS="0"Buffer ZoneCOLNAME=3 ROTATE="0" MOREROWS="0"Host AddressVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"1's and 0'sCOLNAME=2 ROTATE="0" MOREROWS="0"0'sCOLNAME=3 ROTATE="0" MOREROWS="0"0's and 1'sTherefore, if the number of subnetworks or the number of hosts on a subnetwork changes, you can easily select a new subnetwork mask for the network.RENDERAS="SECT2"Broadcast AddressesIDXID="w9209"BOOK="_idx" COLLECTION="nw41" TIDREF="i517"There are three types of broadcast addresses: network broadcasts, subnetwork broadcasts, and broadcast addresses. A network broadcast has a destination IP address with the network portion of the IP address set to Class A, B, or C network, and the host field set to all ones. Directed network broadcasts are sent to all hosts on the specified network.If the network is divided into subnets, each subnetwork has a subnetwork broadcast. A subnetwork broadcast has an IP address with the network field set to the network identifier, the subnetwork field set to the subnetwork identifier, and the host field set to all ones.Generally, broadcasts are not forwarded. Network and subnetwork broadcast are forwarded to a destination network, or subnetwork for subnetwork broadcasts, by the intervening routers when you enable the fowarding of directed broadcasts.PAGENUM=39 ID="BP45"PAGENUM=39PAGENUM=40An IP address with both the subnetwork and host field set to all ones, is interpreted as a broadcast directed to all of the subnets on the network. That is, the first router on the specified network broadcasts it to one of its subnets. Then the routers in that network forward and broadcast it to one of their subnetworks.An IP address with all ones, 255.255.255.255, is also a broadcast address. It is directed to all hosts on the subnetwork the broadcast originated from. This broadcast is not forwarded to other networks or subnets.RENDERAS="SECT2"Multicast AddressesA multicast address is used to send packets to a group of hosts or routers. A packet with a multicast address is received by all hosts and routers belonging to that multicast group. A range of Class D addresses is reserved for multicast addresses, from 224.0.0.1 to 239.255.255.255.Novell's TCP/IP uses two sets of multicast addresses. One set is used by OSPF to multicast OSPF packets to OSPF routers. Its addresses are 224.0.0.5 and 224.0.0.6. The other set is used by Router Discovery messages to multicast router advertisements and solicitation messages. Its addresses are 224.0.0.1 and 224.0.0.2.RIPII uses multicast address 224.0.0.9.LABEL="4"PAGENUM=41 ID="BP46"ID="FM54844"TCP/IP Routing Protocol ConceptsThis chapter describes routing topologies and protocols in general, plus the specific protocol mechanisms and concepts of the TCP/IP routing protocols. The following topics are discussed:MARK=BULLETIDREF="FM30957""Advantages of Dynamic Routing"This section describes the advantages of dynamic routing as compared to static routing.IDREF="FM36535""Routing Topologies and Protocols"This section describes Autonomous Systems (ASs) and how information is communicated within and between ASs.IDREF="FM14622""RIP (Routing Information Protocol)"This section describes RIP and the advantages and disadvantages of using this protocol.IDREF="FM40710""OSPF (Open Shortest Path First)"This section describes OSPF and the advantages and disadvantages of using this protocol.IDREF="FM30360""Interactions Between OSPF and Other Routing Protocols"This section describes the interactions of OSPF with other routing protocols.IDREF="FM33090""EGP (Exterior Gateway Protocol)"This section describes EGP and the advantages and disadvantages of using this protocol.PAGENUM=41 ID="BP47"PAGENUM=42IDREF="FM25248""Router Discovery Protocol"This section describes the Router Discovery Protocol and the advantages and disadvantages of using this protocol.IDREF="FM16088""Static Routes"This section describes static routes and when it is appropriate to use this method of routing.RENDERAS="SECT1"ID="FM30957"Advantages of Dynamic RoutingIDXID="w9210"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"
For TCP/IP to perform routing functions, it must have access to current information about available routes. Such information is usually maintained in a routing table, where individual entries specify the following:MARK=BULLETAddress of a final destinationAddress of the next router along the route to the destinationSome sort of cost of reaching the destination (such as distance or number of hops)The entries in the IDXID="w9211"BOOK="_idx" COLLECTION="nw41" TIDREF="i3915"
routing table can be made manually, or they can be made dynamically through the use of routing protocols. Manual entries, called IDXID="w9212"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"static routes, have the disadvantage of becoming outdated. Any change in the network (such as a failure or the addition of a new node) requires manual intervention to reconfigure the static routes on all routers that have access to the affected area. Given the dynamic nature of most networks, the manual maintenance of IDXID="w9213"BOOK="_idx" COLLECTION="nw41" TIDREF="i4272"
static routing tables is usually confined to special circumstances.For most networks, the only way to respond to changes in the network fast enough to maintain connectivity is to use a routing protocol. A routing protocol dynamically detects a change in the network and updates all affected routing tables accordingly. The protocol does this much faster than a person could using static routing.PAGENUM=43 ID="BP48"RENDERAS="SECT1"ID="FM36535"Routing Topologies and ProtocolsIDXID="w9214"BOOK="_idx" COLLECTION="nw41" TIDREF="i3916"
The largest unit in an internet topology is an IDXID="w9215"BOOK="_idx" COLLECTION="nw41" TIDREF="i373"autonomous system (AS). An AS is a collection of networks and routers that exchange routing information using a routing protocol, such as RIP or OSPF. The routing protocols used within an AS are called IDXID="w9216"BOOK="_idx" COLLECTION="nw41" TIDREF="i1851"
Interior Gateway Protocols (IGPs). Routers within an AS generally share routing information with each other freely. However, the routing information that is shared with other ASs is generally restricted. Routers in different ASs use an IDXID="w9217"BOOK="_idx" COLLECTION="nw41" TIDREF="i1407"
exterior routing protocol, such as Exterior Gateway Protocol (EGP), to share information. See IDREF="FM92327"Figure 4-1.Gateway is an older term for router.LABEL="4-1" FLOAT="0"ID="FM92327"Connecting Two Autonomous SystemsFILEREF="autonom.tif"RENDERAS="SECT2"Interior Gateway ProtocolsNovell supports two IDXID="w9218"BOOK="_idx" COLLECTION="nw41" TIDREF="i1851"
IGP protocols: RIP and IDXID="w9219"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
OSPF. RIP is a standard protocol that is based on the IDXID="w9220"BOOK="_idx" COLLECTION="nw41" TIDREF="i1152"
distance vector algorithm. The majority of the TCP/IP sites still use RIP. OSPF is a newer IGP protocol that is based on a IDXID="w9221"BOOK="_idx" COLLECTION="nw41" TIDREF="i2115"
link state algorithm. OSPFIDXID="w9222"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
 is rapidly gaining acceptance in many public and private sites that have larger and more complex networks. When installing existing RIP sites, Novell's software allows both protocols to coexist and share routing information.PAGENUM=43 ID="BP49"PAGENUM=44RENDERAS="SECT2"Exterior Gateway ProtocolsIDXID="w9223"BOOK="_idx" COLLECTION="nw41" TIDREF="i1407"
Exterior routing protocols, such as IDXID="w9224"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
EGP, exchange information between different IDXID="w9225"BOOK="_idx" COLLECTION="nw41" TIDREF="i373"
ASs. Novell supports EGP as its only exterior gateway protocol. A border gateway gets the routing information regarding its own AS through a local IGP protocol. Then it uses EGP to share that information with other border gateways.RENDERAS="SECT1"ID="FM14622"RIP (Routing Information Protocol)IDXID="w9226"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
RIP is a distance vector protocol. A RIP router periodically broadcasts a routing update message that contains an entry for each network it can reach and the cost to that network. RIP routers listen to all RIP broadcast messages. Each entry in a received routing update message is added to the local routing table. The router that sends the routing update message is remembered as the next router or hop on the route to the network in the entry. If a router learns about two routes to a network, it keeps the one with the lower cost. Cost is often defined in RIP in terms of hop count, or the number of routers along the path to the destination. RIP allows a maximum cost or hop count of 15.Once a route is learned it must be refreshed at certain intervals, thereby ensuring that the route is still valid. RIP routers usually broadcast a routing update message containing known routes every 30 seconds. A timer is started when a route is learned from a IDXID="w9227"BOOK="_idx" COLLECTION="nw41" TIDREF="i3917"
routing update message. If subsequent routing update messages do not refresh the route within 180 seconds, the route is assumed to be unusable. Then the route is removed from the routing table.RIPII is an enhancement to IDXID="w9228"BOOK="_idx" COLLECTION="nw41" TIDREF="i3903"
RIP; it includes the subnetwork mask in its routes. The lack of subnetwork mask information limits RIP to advertising only network routes, or requires RIP routers to make assumptions about the subnetwork mask. When RIP is used in a network with subnetworks, all the subnetworks are usually required to use the same subnetwork mask.RIPII can be used in network topologies requiring variable length subnetwork masks and it can support IDXID="w9229"BOOK="_idx" COLLECTION="nw41" TIDREF="i4317"
subnet zeroIDXID="w9230"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
. RIPII can also authenticate routing message exchanges. RIPII uses multicast addresses instead of broadcast addresses. Not all RIP routers support RIPII.PAGENUM=45 ID="BP50"RENDERAS="SECT2"RIP ConceptsIDXID="w9231"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9232"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
Because RIP cannot detect or correct routing loops, routes learned with RIP that exceed 15 hops are invalid. This means that any given source and destination on your network cannot be separated by more than 15 hops. This IDXID="w9233"BOOK="_idx" COLLECTION="nw41" TIDREF="i1684"IDXID="w9234"BOOK="_idx" COLLECTION="nw41" TIDREF="i2354"
hop count limit can make RIP impractical for large networks.RIP routers can also experience inconsistencies in their routing tables. This is due to how long it takes for all of the RIP IDXID="w9235"BOOK="_idx" COLLECTION="nw41" TIDREF="i3915"
routing tables to synchronize with each other when a change or IDXID="w9236"BOOK="_idx" COLLECTION="nw41" TIDREF="i833"
convergence time occurs in the network. The most serious reason for RIP's slow convergence, known as the IDXID="w9237"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
count-to-infinity problem, is illustrated in the scenario shown in IDXID="w9238"BOOK="_idx" COLLECTION="nw41" TIDREF="i4172"IDREF="FM30121"Figure 4-2.LABEL="4-2" FLOAT="0"ID="FM30121"Slow Convergence with RIPFILEREF="f33dest.tif"In IDREF="FM30121"Figure 4-2, the arrows show the route to destination D. Router R2 has learned its route to destination D from router R3. If R3's link to destination D goes down, R3 drops the route to D from its routing table. Since R2 still has a valid route to D that it learned from R3, R2 will send a RIP update to R3 stating that it can reach destination D at a cost of two hops. R3 calculates that it can reach destination D in three hops, one hop to reach R2 and then two more hops to destination D. Then R3 enters a new route to destination D into its routing table. This process creates a routing loop. In this scenario, any data packet that is destined for destination D, received by either R3 or R2, is routed back and forth until its time-to-live counter expires.PAGENUM=46 ID="BP51"As R3 and R2 continue to update each other, the updating process takes some time to resolve. Since R2 does not learn the route to D with a cost of 1 from R3 anymore, its route to D with a cost of 2 eventually expires. Then R2 learns that R3's distance from destination D is three, and it calculates a new cost for its route to destination D, with a cost of four. In the next round, R3 increases its cost to five. Both routers continue to increase their cost to destination D until a cost of 16 is finally reached. This synchronization of routing tables can take several minutes.Novell employs several techniques for solving slow convergence caused by the IDXID="w9239"BOOK="_idx" COLLECTION="nw41" TIDREF="i863"
count-to-infinity problem: NetWare® TCP/IP Split Horizon, Poison Reverse, IDXID="w9240"BOOK="_idx" COLLECTION="nw41" TIDREF="i4229"
and IDXID="w9241"BOOK="_idx" COLLECTION="nw41" TIDREF="i3332"IDREF="FM39075"Triggered Updates.IDXID="w9242"BOOK="_idx" COLLECTION="nw41" TIDREF="i4575"RENDERAS="SECT3"ID="FM76976"Split Horizon and Poison ReverseIDXID="w9243"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"Split Horizon is enabled automatically. With IDXID="w9244"BOOK="_idx" COLLECTION="nw41" TIDREF="i4229"
this feature, routes are not propagated back onto the same interface from which they are learned. To solve the problem shown in IDREF="FM30121"Figure 4-2, Split Horizon prevents R2 from advertising a route for destination D to R3. See IDREF="FM25312"Figure 4-3. Because R3 does not receive misleading information about the route to D, it does not update its routing table with a route to D through R2. R3 stops advertising a route to D; consequently, R2 eventually times out its route to D.LABEL="4-3" FLOAT="0"ID="FM25312"Split HorizonFILEREF="splithzn.tif"PAGENUM=46 ID="BP52"PAGENUM=47Split Horizon without Poison Reverse does not solve the slow convergence problem if more than two routers are involved in the routing loop. For example, one scenario occurs when R3 is one hop away from destination D and routers R1 and R2 are two hops away from destination D. If the link to destination D goes down, R3 learns that destination D is unreachable and stops advertising to R1 and R2.The Split Horizon rule does not allow R1 or R2 to tell R3 about its distance to destination D. As a result, R1 and R2 might conclude that destination D is reachable due to the following scenario.R1 and R2 do not learn the route to D anymore. So the route to D on both routes times out. Suppose the route to D times out on R1 before it does on R2. Within the time that R2 has the route but R1 does not, if R2 advertises the route to R1, R1 takes it and concludes it is three hops from destination D (based on information from R2 that it is two hops from D). Then R1 informs R3 that it is three hops from D. R3 assumes that it is four hops from D, and that D is in the direction of R1. The route with a cost of two eventually times out on R2. Since R3 informs R2 that it is four hops from D, R2 concludes that it is five hops from D and adds a new route for D with a cost of 5. The loop continues.The count-to-infinity problem still exists in this loop of three routers. This problem can be avoided by designing your network not to have loops of three routers or using triggered updates.With Poison Reverse, instead of not being propagated, routes that are learned from an interface are advertised with a cost of 16 on the same interface from which they were learned.RENDERAS="SECT3"ID="FM39075"Triggered UpdatesIDXID="w9245"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9246"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
Triggered Updates cause the router to send a RIP update as soon as a new route is learned or an existing route is lost or changed. The triggered update contains only the affected routes, for example, the route with a cost of 16 if it is lost, or with a new cost if it is changed, or a new route. This way the router minimizes the amount of time it holds on to outdated routes. To solve the slow convergence problem shown in IDREF="FM30121"Figure 4-2, IDXID="w9247"BOOK="_idx" COLLECTION="nw41" TIDREF="i4575"
Triggered Updates causes R3 to advertise destination D as unreachable as soon as the last connection to destination D is deleted.PAGENUM=48 ID="BP53"RENDERAS="SECT2"Subnetting with RIPIDXID="w9248"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"RIP cannot fully support subnetting because it does not include subnetwork mask information in its advertisements (although RIPII can support subnetting). However, a RIP router can derive subnetwork mask information from its interfaces. By assuming that the subnetwork masks are fixed for all subnetworks of the same network, RIP applies the derived subnetwork mask to all remote subnetworks in the same network.This method of subnetwork support requires a fixed subnetwork mask for a given network. As a result, RIP does not support variable length subnetwork masks. (See IDREF="FM10697""Variable Size Subnetworks.") In addition, the subnetwork mask information derived from the interface is applied only to the network to which the interface belongs. Subnetwork information from remote networks is not available to the RIP router. Consequently, RIP does not support subnetworks of remote networks.Because the RIP routers external to the network do not know the subnetworks used within a network, RIP requires that all subnetwork routes are aggregated into a single network route when they are advertised externally. To accomplish this, all subnetworks must be contained within a single network boundary.RENDERAS="SECT1"ID="FM40710"OSPF (Open Shortest Path First)IDXID="w9249"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
OSPF is a IDXID="w9250"BOOK="_idx" COLLECTION="nw41" TIDREF="i2115"
link state routing protocol. Link state routers exchange information about the state of their network connections or links. Using this information, each router can construct the topology of the internetwork and derive routing information. IDXID="w9251"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
Unlike RIP, OSPF does not have the count-to-infinity problem. Therefore, its metric does not have to be limited to 16. An OSPF metric can be as large as 65535. With a larger metric, you can build a larger internetwork. In addition, this allows you to assign a wide range of costs for different types of networks based on characteristics such as bandwidth.PAGENUM=48 ID="BP54"PAGENUM=49OSPF also converges on the common routing information faster than RIP does. This is because OSPF does not have the count-to-infinity problem and OSPF link state information is flooded instantaneously rather than processed on each hop, as in RIP.   The faster convergence prevents loss of connectivity and temporary routing loops.Finally, OSPF generates less traffic. Unlike RIP, which requires periodic updates, OSPF routers update their link state information only when the link state changes, or every 30 minutes, as opposed to 30-second RIP updates. Consequently, more bandwidth is available to the data traffic.For more information about the OSPF protocol, refer to IDXID="w9252"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
RFC 1583.RENDERAS="SECT2"OSPF TopologyIDXID="w9253"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
OSPF areas are connected in a hierarchical manner. The OSPF AS can be partitioned into different regions, called areas. When divided into areas, there must be a special area called the backbone area. All IDXID="w9254"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
OSPF areas are then connected to the IDXID="w9255"BOOK="_idx" COLLECTION="nw41" TIDREF="i390"backbone area. The backbone area is represented in IDREF="FM48099"Figure 4-4 by area 0.Routers that attach an area to the backbone area are called IDXID="w9256"BOOK="_idx" COLLECTION="nw41" TIDREF="i289"area border routers. An area border router has at least one interface in a nonbackbone area and one interface in the backbone area.OSPF routers can exchange information with other ASs or domains running a different routing protocol, such as EGP or RIP. The exchanges between routing protocols are performed by the gateway at the border of the OSPF domain. This gateway is called an Autonomous System Boundary Router, or ASBR. An ASBR must be running EGP or RIP, as well as OSPF, to learn routing information from other domains or ASs. It then disseminates that information throughout the OSPF domain for the OSPF routers. See IDREF="FM48099"Figure 4-4.PAGENUM=50 ID="BP55"LABEL="4-4" FLOAT="0"ID="FM48099"OSPF AreasFILEREF="asbr.tif"RENDERAS="SECT2"Area PartitioningIDXID="w9257"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"As the OSPF domain gets larger, the probability of link state change also increases because it includes more routers and networks. Consequently, each link state change causes route recomputation on all routers, increasing the burden on the CPU. In addition, each computation of a route takes longer because there are more destination networks for which to compute. When the OSPF domain gets too large, you might want to partition it into multiple areas to reduce the burden on the CPU. Novell recommends that you limit the size of an area to include less than 200 routers.Partitioning the OSPF domain into areas provides several advantages. It permits administrative separation of different geographical or organizational groups, such as engineering and marketing. Creating areas allows you to limit the sharing of routing information between areas, making a particular area more secure. In addition, it reduces the number of Link State Advertisements (LSAs) in the area and allows you to isolate an area with frequent topological changes.PAGENUM=50 ID="BP56"PAGENUM=51RENDERAS="SECT2"Area Border RoutersIDXID="w9258"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9259"BOOK="_idx" COLLECTION="nw41" TIDREF="i288"
Area border routers (ABRs)
 share information that advertises destinations through the backbone area into the nonbackbone area. In addition, ABRs share information that advertises destinations through the nonbackbone area into the backbone area. These are called summary link advertisements.IDXID="w9260"BOOK="_idx" COLLECTION="nw41" TIDREF="i4329"RENDERAS="SECT2"Autonomous System Boundary RoutersIDXID="w9261"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9262"BOOK="_idx" COLLECTION="nw41" TIDREF="i374"
Routing information from other ASs (such as RIP) or through exterior gateway protocols (such as EGP) or from other routing protocols, can be combined and disseminated through ASBRs. Because they provide an interface to other ASs and routing protocols, ASBRs have access to routing information that is learned from routers outside the OSPF domain. ASBRs can be internal or area boundary routers, and are not required to participate in the backbone area.RENDERAS="SECT2"Virtual LinksIDXID="w9263"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"A IDXID="w9264"BOOK="_idx" COLLECTION="nw41" TIDREF="i4768"
virtual link enables you to extend a backbone area by joining two partitioned areas. In addition, it allows you to isolate an area with frequent topological changes.Networks and routers in an OSPF backbone area must be interconnected. However, when dividing the OSPF domain into areas, the backbone area can become partitioned due to geographic reasons. The partitioned parts of the backbone area can be reconnected using a virtual link.A virtual link is really a path through the IDXID="w9265"BOOK="_idx" COLLECTION="nw41" TIDREF="i4558"transit area, or nonbackbone area. The ABRs at each end of the virtual link treat the path between the two as a point-to-point link. Using that virtual point-to-point link, the partitioned backbone area is reconnected. See IDREF="FM24152"Figure 4-5. The use of a virtual link is complicated and error-prone. Consequently, Novell recommends that you make every effort to keep the backbone area physically connected. The virtual link should be used only when necessary.PAGENUM=52 ID="BP57"LABEL="4-5" FLOAT="0"ID="FM24152"OSPF Virtual and Transit AreasFILEREF="virtual.tif"RENDERAS="SECT2"Stub AreasIDXID="w9266"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9267"BOOK="_idx" COLLECTION="nw41" TIDREF="i4309"
OSPF also supports the use of stub areas. When there is only a single ABR for an area, all destinations outside the area go through that router. In this case, you might want to configure the area as a stub area. A stub area does not allow its ABRs to advertise external routes. This includes routes to other areas as well as routes external to the OSPF domain. Instead, ABRs advertise a single default route. A stub area saves memory, CPU, and bandwidth resources on all OSPF routers by not generating advertisements for individual destinations.The stub area does not allow its ABRs to pass on external link state advertisements to other areas. Consequently, ASBRs cannot be placed inside a stub area. An ASBR within a stub area circulates external link advertisements only within the area. As a result, all OSPF routers outside the stub area do not learn about external destinations.RENDERAS="SECT2"Hierarchical RoutingIDXID="w9268"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"OSPF has three types of hierarchical routing:MARK=BULLETID="FM18353"IDREF="FM10668""Intra-Area Routing and Inter-Area Routing"IDREF="FM21972""External Link Advertisements"These are described in the section that follows.PAGENUM=52 ID="BP58"PAGENUM=53RENDERAS="SECT3"ID="FM10668"Intra-Area Routing and Inter-Area RoutingIDXID="w9269"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Routing within an area, or IDXID="w9270"BOOK="_idx" COLLECTION="nw41" TIDREF="i1887"intra-area routing, can occur without knowledge of routing information from other areas. However, to route between areas, or IDXID="w9271"BOOK="_idx" COLLECTION="nw41" TIDREF="i1885"inter-area routing, IDXID="w9272"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
packets must be passed to the local area border router and then to the destination's area boundary router before they are passed to the destination area. Inter-area routing requires sharing an area's routing information with other ABRs.RENDERAS="SECT3"ID="FM21972"External Link AdvertisementsIDXID="w9273"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"The routing between the OSPF domain and others, such as RIP or EGP, is done through the ASBRs. This process is called IDXID="w9274"BOOK="_idx" COLLECTION="nw41" TIDREF="i1410"external link advertisements. The ASBRs are located on the border of the OSPF domain. They disseminate the external destinations by flooding external advertisements throughout the OSPF domain.There are two types of external link advertisements, type 1 and type 2. The meaning of the external link advertisement metric depends on the type. See IDREF="FM30360""Interactions Between OSPF and Other Routing Protocols" for more information.RENDERAS="SECT2"OSPF Routers and HostsIDXID="w9275"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"OSPF is a router-to-router protocol that exchanges routing information between routers. Hosts do not participate in OSPF exchanges. As a result, the hosts are not informed about routers and routes discovered by the OSPF protocol. To supply hosts with OSPF router information, you can employ one of the following configurations:MARK=BULLETConfigure the hosts to use default routers.Configure hosts and OSPF routers so they can exchange ICMP Router Discovery messages. This enables hosts to discover the default routers on the network dynamically.Configure OSPF routers to send out RIP update messages to hosts periodically. These messages inform hosts about all available destinations.PAGENUM=54 ID="BP59"The first method requires you to configure hosts to use default routers manually. This is the only workable method if the hosts do not understand Router Discovery messages or RIP messages.The second method requires hosts to support the Router Discovery mechanism of ICMP. If the hosts support it, you can configure the software to generate ICMP Router Advertisement messages periodically that tell hosts that they can act as a default router.The third method requires the hosts to understand RIP messages. Many larger hosts, such as UNIX® workstations, do understand RIP. In this case, you can configure the software to dump its routing table on the network using periodic RIP update messages. (This is the CLASS=MENUITEM MOREINFO="NONE"Send Only option.) The disadvantage of this method is that it incurs high network overhead because RIP update messages are large and are broadcast every 30 seconds.RENDERAS="SECT1"ID="FM30360"Interactions Between OSPF and Other Routing ProtocolsIDXID="w9276"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
The following sections explain the interactions of OSPF with other routing protocols.RENDERAS="SECT2"ID="FM50312"Protocol PreferenceIDXID="w9277"BOOK="_idx" COLLECTION="nw41" TIDREF="i3881"
When multiple routing protocols supply routes to the same destination, the routes are added to the routing table in the following order of preference:MARK=BULLETOSPF IDXID="w9278"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9279"BOOK="_idx" COLLECTION="nw41" TIDREF="i1858"
internal routes have a preference level 1.OSPF IDXID="w9280"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9281"BOOK="_idx" COLLECTION="nw41" TIDREF="i1415"
external type 1 routes have a preference level 2.OSPF IDXID="w9282"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9283"BOOK="_idx" COLLECTION="nw41" TIDREF="i1416"
external type 2 routes and routes from other protocols, such as RIP, EGP, and OSPF external type 2 routes, have a preference level 3.PAGENUM=54 ID="BP60"PAGENUM=55RENDERAS="SECT3"OSPF External Route MetricsIDXID="w9284"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
If two routes have the same preference, the route with the better metric is added to the routing table. For example, when evaluating two OSPF internal routes to the same destination, one with metric 10 and the other with metric 20, the one with metric 10 is added to the routing table. If the metric is the same between an OSPF external type 2 route and a RIP or EGP route, the route received from RIP or EGP is preferred.IDXID="w9285"BOOK="_idx" COLLECTION="nw41" TIDREF="i2434"IDXID="w9286"BOOK="_idx" COLLECTION="nw41" TIDREF="i3882"
Although the route metric determines the preference between two different routes (to the same destination) generated by the same protocol, it might not be possible to determine route preference by comparing the metrics of two routes generated by different protocols. The meaning of the metric differs from protocol to protocol, and is not necessarily comparable.The only case where the metric of different protocols needs to be compared is in the protocol preference level 3, where OSPF external type 2, RIP, and EGP routes are preferred equally.RIP and EGP routes are considered comparable. Therefore, between RIP and EGP routes to the same destination, the route with the smaller metric is added to the routing table. However, comparing OSPF routes to RIP and EGP routes is not as straightforward as comparing RIP and EGP routes.An OSPF external route has two metrics, an internal metric and an external metric. For OSPF type 2 external, the external metric is comparable to RIP and EGP metrics, while the internal metric is much smaller than the external metric. Consequently, when comparing an OSPF external type 2 route with a RIP or EGP route, the OSPF external metric is compared with the RIP or EGP metric.For example, say a RIP and an OSPF route are presented to the same network simultaneously. The RIP route has a metric of 10, and an OSPF external type of 2 has an internal metric of 100 and an external metric of 9. In this case, the OSPF route is added to the routing table because the external metric of 9 is smaller than the RIP metric of 10.However, if the external metric of the OSPF external type 2 route is the same as the metric of the RIP or EGP route, then the RIP or EGP route is selected. This is because of the OSPF route internalPAGENUM=56 ID="BP61" metric. Although it is considered much smaller than the external metric or the RIP or EGP metric, the internal metric still carries weight when comparing two equal-cost routes. For example, if a RIP route with a metric of 10 and an OSPF external type 2 route with an external metric of 10 are both going to the same destination, the RIP route is added to the routing table. IDXID="w9287"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
When added to the IP routing table, the metric of an OSPF route is generally set to the values shown in IDREF="FM33940"Table 4-1.LABEL="4-1" PGWIDE=0 TOCENTRY="1"ID="FM33940"OSPF Metric Translation to IP MetricCOLS=5 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="6*"COLNAME=5 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PreferenceCOLNAME=2 ROTATE="0" MOREROWS="0"TypeCOLNAME=3 ROTATE="0" MOREROWS="0"Internal MetricCOLNAME=4 ROTATE="0" MOREROWS="0"External MetricCOLNAME=5 ROTATE="0" MOREROWS="0"IP MetricVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"OSPF internalCOLNAME=3 ROTATE="0" MOREROWS="0"mCOLNAME=4 ROTATE="0" MOREROWS="0"0COLNAME=5 ROTATE="0" MOREROWS="0"mCOLNAME=1 ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"OSPF external type 1COLNAME=3 ROTATE="0" MOREROWS="0"m1COLNAME=4 ROTATE="0" MOREROWS="0"m2COLNAME=5 ROTATE="0" MOREROWS="0"m1 + m2COLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"OSPF external type 2COLNAME=3 ROTATE="0" MOREROWS="0"m1COLNAME=4 ROTATE="0" MOREROWS="0"m2COLNAME=5 ROTATE="0" MOREROWS="0"m2For example, an OSPF external type 1 route with an internal metric of 100 and external metric of 10 shows 110 in its metric field. However, an OSPF external type 2 route with the same set of metrics shows 10 in its metric field when viewed with IDXID="w9288"BOOK="_idx" COLLECTION="nw41" TIDREF="i4445" TCPCON. Refer to BOOK="cfg2_enu" COLLECTION="nw41"Netware 4.1 Advanced Protocol Configuration and Management Guide for more information about IDXID="w9289"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087" TCPCON.RENDERAS="SECT3"OSPF Advertisements for RIP or EGP RoutesIDXID="w9290"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
Routes that OSPF learns from the RIP or EGP protocols are advertised into the OSPF domain as type 2 external routes only. The external metric the ASBR advertises is the RIP/EGP metric. Novell's implementation of OSPF does not originate type 1 external routes. However, it understands type 1 external routes originated from other routers, and processes them as described in the previous section.RENDERAS="SECT3"RIP Advertisements for OSPF RoutesIDXID="w9291"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9292"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
RIP advertises OSPF internal and external type 1 routes with a metric of 1. For external type 2 routes, it advertises the value of the external metric as the value of the metric recorded in the route entry, plus 1. In essence, RIP treats the entire OSPF domain as a single RIP network with a metric of 1.PAGENUM=57 ID="BP62"RENDERAS="SECT2"Migrating from RIP to OSPFIDXID="w9293"BOOK="_idx" COLLECTION="nw41" TIDREF="i2455"IDXID="w9294"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9295"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
Having both RIP and OSPF enabled on a router does not necessarily cause the router to act as a gateway between RIP and OSPF in both directions. When both OSPF and RIP are running, RIP advertises OSPF routes automatically. However, OSPF does not advertise RIP routes in the OSPF domain (or routes of other protocols) as external routes automatically.To make OSPF advertise the routes of other protocols, you must turn on the OSPF ASBR IDXID="w9296"BOOK="_idx" COLLECTION="nw41" TIDREF="i374"
function. You accomplish this in INETCFG by enabling the ASBR function in theCLASS=MENUITEM MOREINFO="NONE" OSPF configuration window under TCP/IP protocol configurations. For more information about the INETCFG parameters for TCP/IP, refer to IDREF="FM20503"Chapter 7, "TCP/IP Configuration Parameters."Do not enable RIP, OSPF, and the ASBR function of OSPF on too many machines. Having too many RIP/OSPF gateways is inefficient because too many gateways advertise routes to the same destinations. For RIP, it means more bandwidth is used for RIP advertisements. For OSPF, it means memory is consumed for storing too many external link advertisements in the link state databases of every OSPF router.Do not partition either the RIP or OSPF domain. If they are partitioned, the routing information from either domain must be tunneled through the other domain. For example, RIP routing information from one RIP partition will have to be tunneled through an OSPF domain to the other RIP partition. Such tunneling requires unnecessary ASBRs, creating unnecessary external advertisements. Unpartitioned RIP and OSPF domains avoid the redundancy of ASBRs and external advertisements of a partitioned domain. In addition, using unpartitioned domains makes managing the internetwork easier because it simplifies the overall topology of the AS.Novell suggests that you have no more than two or three gateways connecting the RIP and OSPF domains.PAGENUM=57 ID="BP63"PAGENUM=58RENDERAS="SECT3"Configuring OSPF with Third-Party VendorsIDXID="w9297"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Routers from different vendors redistribute routes between protocols. It is possible to create routing loops because a vendor does not increment the hop count when going from RIP to OSPF and back to RIP. In this case, external type 1 routes must be used or no loops must exist in the topology.For example, you might want to run RIP on networks 192.1.1.0 and 192.1.2.0 while you run OSPF on networks 192.1.3.0 and 192.1.4.0. See IDREF="FM40955"Figure 4-6. Then connect 192.1.1.0 and 192.1.2.0 with the RIP router and 192.1.3.0 and 192.1.4.0 with the OSPF router. Between the RIP and OSPF networks, you can install two RIP/OSPF gateways. (The second gateway is the backup in case the first one fails.)LABEL="4-6" FLOAT="0"ID="FM40955"RIP and OSPF Gateway RouterFILEREF="ripospf.tif"Novell strongly advises you to configure all third-party routers to prefer routes as shown in IDREF="FM50312""Protocol Preference." In addition, it is recommended that routers do not originate external type 1 advertisement. Most of the third-party routers follow similar preferences by default. If third-party routers are configured to prefer routes differently from Novell's configuration, problems can occur. For example, a third-party router might prefer RIP routes over OSPF external 2 routes, regardless of metrics. Or, third-party routers might generate OSPF external type 1 routes for the RIP routes that they added. If either of these configurations is enacted, a continuous update loop can occur between the third-party router and the Novell® software (between RIP update, OSPF external 1 update, and OSPF external type 2 update).PAGENUM=58 ID="BP64"PAGENUM=59If you want to run both RIP and OSPF on a router while the route propagation across the protocols is not wanted, then you can suppress the propagation by setting up a filter. For more information about configuring routing information filters, see NetWare 4.1 Advanced Protocol Configuration and Management Guide.RENDERAS="SECT2"OSPF ConceptsIDXID="w9298"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"This section covers the following OSPF concepts that provide IP routing:MARK=BULLETIDREF="FM42600"NeighborsIDREF="FM25853"Designated RouterIDREF="FM41911"AdjacencyIDREF="FM17550"FloodingIDREF="FM18502"Dijkstra AlgorithmThese concepts are described in the following sections.RENDERAS="SECT3"ID="FM42600"NeighborsIDXID="w9299"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9300"BOOK="_idx" COLLECTION="nw41" TIDREF="i2636"
OSPF neighbors are peer OSPF routers on a network. An OSPF router discovers its neighbors through the exchange of Hello packets. In broadcast networks, such as an Ethernet local network, the OSPF router multicasts a Hello packet. That packet is received by all the router's neighbors. In nonbroadcast networks, such as X.25 PDN, the location of the neighbors (IP address) is configured manually. The router sends Hello packets to its configured neighbors to indicate it is alive.In the Hello packet, the originating router lists the ID of neighbors that it has heard from. The receiving router assumes a bidirectional relationship with the originating router if the received Hello contains the ID of the receiving router. All links in OSPF must be bidirectional. Links that are not bidirectional do not participate in OSPF routing.PAGENUM=60 ID="BP65"RENDERAS="SECT3"ID="FM25853"Designated RouterIDXID="w9301"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9302"BOOK="_idx" COLLECTION="nw41" TIDREF="i1001"
Among OSPF routers in a network, there is a special router called the Designated Router (DR). The DR performs two functions on the network: MARK=BULLETIt generates the network link advertisement on behalf of the network.It acts as the coordinator for disseminating and synchronizing the advertisements.Each node in the OSPF domain must advertise its link state. The router advertisement is originated by individual routers. The network advertisement is generated by the DR on the network. The DR lists the IDs of its qualifying neighbors on that network. By linking the network advertisements and router advertisements from all the neighbors, an OSPF router constructs the topological state of the whole OSPF domain.When an advertisement is originated by a router, it must be disseminated to all the OSPF routers in the OSPF domain. In addition, all routers must agree on the internetwork topology. If the routers do not agree, OSPF routing breaks down and loss of connectivity or routing loops can occur. The dissemination and synchronization of link state advertisements among OSPF routers is achieved through the use of adjacencies. The DR is the central point of all adjacent relationships on the network.The DR for a network is selected among all bidirectional neighbors through a selection process. When there is no DR, the neighbors select the DR based on the priority value conveyed in the Hello packets. The router with the highest priority value becomes the DR. Once a DR is selected, it continues to act as the DR until the network goes down. Refer to RFC 1583 for the details of the DR election algorithm.The election process also chooses the backup DR. Both the DR and the backup DR maintain an adjacency relationship to their neighbors. However, the backup DR is not responsible for generating network advertisements for the network. When the DR goes down, the backup DR takes over. Because the backup DR maintains adjacencies with its neighbors, it does not have to reestablish adjacencies. Consequently, the transition from one DR to another is faster with a backup DR.PAGENUM=61 ID="BP66"RENDERAS="SECT3"ID="FM41911"AdjacencyIDXID="w9303"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9304"BOOK="_idx" COLLECTION="nw41" TIDREF="i115"
For OSPF to work properly, all OSPF routers must be in agreement on the link state, or topology, of the OSPF domain. OSPF achieves that by requiring a router to be constantly in sync with some subnetwork of its neighbors. The router is then said to be adjacent to those neighbors. Not all routers need to be in sync with all their neighbors to ensure the synchronization among routers. For example, if A is in sync with B and B is in sync with C, then A will be in sync with C. Therefore, A only needs to be adjacent to B, and not to C. In practice, OSPF simplifies the synchronization by requiring the adjacency only between the DR, backup DR, and their neighbors. If the router is not a DR or a backup DR, it forms an adjacency only with the DR and backup DR. Because there always is a DR, all routers in a OSPF domain are interconnected by the adjacencies, and are in sync with all other routers.Because adjacent neighbors must agree on the link state of the OSPF domain, they exchange their link state databases with each other to synchronize their databases at the beginning. Once their state databases are exchanged and become identical to each other, the adjacent neighbors are said to be full. Only after both neighbors on an adjacency become full is the adjacency considered fully formed.In addition to link state database synchronization, the adjacency serves as the path for disseminating a newly originated link state advertisement throughout the OSPF domain. RENDERAS="SECT3"ID="FM17550"FloodingIDXID="w9305"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9306"BOOK="_idx" COLLECTION="nw41" TIDREF="i1523"
The process of disseminating a link state advertisement is called flooding. A new advertisement is flooded throughout the OSPF domain by disseminating it along the adjacencies. Because all routers are interconnected by adjacencies, they all have a chance to receive the new advertisement.Because all routers must synchronize their link state databases, the flooding must be reliable. OSPF achieves reliability through positive ACK and retransmission. See RFC 1583 for more information.PAGENUM=61 ID="BP67"PAGENUM=62The flooding algorithm can detect duplicate advertisements and install the correct one. For example, a router that goes down and comes back up might encounter an advertisement that it originated. To prevent ambiguity, OSPF uses a sequence number and an age to decide which version of the advertisement is the correct one. See RFC 1583 for more information.RENDERAS="SECT3"ID="FM18502"Dijkstra AlgorithmIDXID="w9307"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9308"BOOK="_idx" COLLECTION="nw41" TIDREF="i1035"
Once the complete link state information becomes available, the OSPF router can compute the reachable network destinations and routes to them. The router must recompute the routing table whenever a new network or router link state advertisement is received. To compute the routes from link state information, OSPF uses the Dijkstra algorithm, a method to compute the shortest path to destinations in a topology. The summary and external link advertisements do not represent topological link states. Instead, they are advertisements of reachable destinations by the originating routers, similar to RIP. Therefore, a change in the summary or external link state advertisements does not require the Dijkstra algorithm to compute the route. These destinations are computed by updating the individual routing entries in the route table according to the change conveyed by the new advertisement. See RFC 1583 for more information about the Dijkstra algorithm.RENDERAS="SECT2"Network Types Supported by OSPFIDXID="w9309"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
OSPF is flexible because it is able to support the following network types:MARK=BULLETIDXID="w9310"BOOK="_idx" COLLECTION="nw41" TIDREF="i523"Broadcast Networks. IDXID="w9311"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
Networks that can support more than two attached routers and can broadcast a single physical message to all the attached routers. Ethernet and token ring are examples of broadcast networks.IDXID="w9312"BOOK="_idx" COLLECTION="nw41" TIDREF="i2960"Nonbroadcast Networks. IDXID="w9313"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"PAGENUM=63 ID="BP68"Networks that can connect more than two routers or hosts but have no broadcast capability. Novell's OSPF support of nonbroadcast networks is simpler than the OSPF specification because it minimizes the configuration at the expense of a slight increase in traffic when you turn your system on. You do not need to configure the priority of the neighbor. However, you must specify the OSPF neighbors because this network does not broadcast data. Novell's OSPF automatically calculates it when you turn on your system. Also, the configuration does not have to be fully symmetric. That is, you do not have to configure all the neighbors for all routers. As long as at least one router has the complete list of neighbors in the network, the configuration will work. This minimizes the chance of malfunction due to misconfiguration.IDXID="w9314"BOOK="_idx" COLLECTION="nw41" TIDREF="i3331"Point-to-Point Networks.IDXID="w9315"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
Serial lines that connect a pair of routers; for example, a 56-Kbps line that connects a remote site to a main campus. This implementation results in more efficient routers.RENDERAS="SECT1"ID="FM33090"EGP (Exterior Gateway Protocol)IDXID="w9316"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
EGP is an IDXID="w9317"BOOK="_idx" COLLECTION="nw41" TIDREF="i1407"
exterior routing protocol that is supported by the software. Exterior routing protocols exchange information between different IDXID="w9318"BOOK="_idx" COLLECTION="nw41" TIDREF="i373"
ASs. The local EGP gets the information about its own IDXID="w9319"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
AS from the local IGPs. Usually, exterior protocols are used only when connecting different companies or when connecting to a commercial service.The information EGP receives from the IGP must be explicitly configured. The exterior routing protocol shares only the information specified in the outgoing route filters. This is desirable because you generally want to limit the information exchanged between different ASs.EGP exchanges routing information between ASs. As mentioned earlier, most companies and organizations usually group all their routers into one AS, and large companies might use more than one AS. In either case, one or more routers within each AS are chosen to use EGP to talk to the outside world, usually over the Internet. These EGP routers are called IDXID="w9320"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"exterior routers.Routers that belong to the same AS are called IDXID="w9321"BOOK="_idx" COLLECTION="nw41" TIDREF="i1852"IDXID="w9322"BOOK="_idx" COLLECTION="nw41" TIDREF="i2636"IDXID="w9323"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
interior neighbors, and routers that belong to different routing protocol domains are called IDXID="w9324"BOOK="_idx" COLLECTION="nw41" TIDREF="i1406"IDXID="w9325"BOOK="_idx" COLLECTION="nw41" TIDREF="i2636"IDXID="w9326"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"exterior neighbors.The first step that EGP takes to establish communication between exterior routers is to perform IDXID="w9327"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"neighbor acquisition. During neighbor acquisition, one exterior router makes a request to another router to agree that they share reachability information. The next step is that the router continually tests whether its EGP neighbors are responding. Finally, reachability information is exchanged periodically between EGP neighbors through the use of Routing Update messages.PAGENUM=64 ID="BP69"RENDERAS="SECT2"Network Design Issues with EGPIDXID="w9328"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
EGP has one major limitation: the distance indicated for a particular destination does not specify the cost to the destination. EGP only reports whether a destination is reachable. Because of this limitation, EGP can only be used in a tree-type network. All routing protocol domains must connect to the same central network, such as the IDXID="w9329"BOOK="_idx" COLLECTION="nw41" TIDREF="i293"
ARPAnet. Consequently, it cannot support a IDXID="w9330"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
looped topology.Another limitation is that EGP can advertise only one route to a given network. Therefore, there can be no load sharing for traffic between any given pair of machines. Also, the use of just one path for a given network can result in packets taking nonoptimal paths during certain traffic conditions on the network.Finally, it is difficult for EGP to switch to an IDXID="w9331"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
alternate route if the primary route fails.RENDERAS="SECT1"ID="FM25248"Router Discovery ProtocolIDXID="w9332"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"The Router Discovery Protocol of the IDXID="w9333"BOOK="_idx" COLLECTION="nw41" TIDREF="i1864"
Internet Control Message ProtocolIDXID="w9334"BOOK="_idx" COLLECTION="nw41" TIDREF="i1864"
 (ICMP)IDXID="w9335"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"
 allows hosts to discover routers on their network and determine which router to use as their default router. When a host needs to send a packet to another network, it first sends the packet to a router that forwards the packet toward the destination. To accomplish this, the host needs to know where the routers are on its network and which one to send packets to.When you configure the router discovery mechanism, the router advertises itself with periodic ICMP router advertisement messages. Then the host listens to this message and decides whether to use a router as the default fowarding router.You can configure the host to solicit the router advertisement on attached networks. All participating routers then reply to the inquiry. By collecting those replies, the host discovers the routers on the network and determines which router to use.A host might not select the best router to forward packets to a specific destination. When the router receives a packet from a host that is better forwarded to another router on the network, the router uses an ICMP Redirect message to notify the host to send packets to a new router.PAGENUM=65 ID="BP70"RENDERAS="SECT2"Router Discovery MessagesIDXID="w9336"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"There are three message types that are used by the Router Discovery Protocol to communicate between hosts and routers:MARK=BULLETIDREF="FM40281"ICMP Router Advertisement MessageIDREF="FM24035"ICMP Router Solicitation MessageIDREF="FM13220"Router Discovery Multicast AddressRENDERAS="SECT3"ID="FM40281"ICMP Router Advertisement MessageIDXID="w9337"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"IDXID="w9338"BOOK="_idx" COLLECTION="nw41" TIDREF="i1864"
The ICMP Router Advertisement Message is ICMP message type 9IDXID="w9339"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"
. This message is used by routers to advertise their presence on the network. This message is broadcast or multicast to all hosts on the network.This message type carries the IP address of the router and its preference level. Hosts use the IP address as the next hop address for destinations that are on other networks. Hosts use the preference level to determine which router to use for forwarding. The router with the highest preference becomes the default router.A value of 0x80000000 is used to specify that the router is not to be used to forward packets. Routers with this value are used only when other routers send ICMP redirect messages to the host. These redirect messages inform the host to use the router (with a value of 0x80000000) as the next hop router for specific destinations.RENDERAS="SECT3"ID="FM24035"ICMP Router Solicitation MessageIDXID="w9340"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"IDXID="w9341"BOOK="_idx" COLLECTION="nw41" TIDREF="i1864"
The ICMP Router Solicitation Message is ICMP message type 10IDXID="w9342"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"
. Hosts use this message to solicit router advertisements from all participating routes on the network.PAGENUM=65 ID="BP71"PAGENUM=66RENDERAS="SECT3"ID="FM13220"Router Discovery Multicast AddressIDXID="w9343"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"The Router Discovery Multicast Address is IP address 224.0.0.1. It is reserved to multicast the router advertisement message to the hosts. The IP address 224.0.0.2 is reserved to multicast the Router Solicitation Message to the routers. If the network does not support multicast, then broadcast address 255.255.255.255 is used for both the Router Advertisement and Router Solicitation messages.RENDERAS="SECT1"ID="FM16088"Static RoutesIDXID="w9344"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"Static routes are manually configured entries in the routing table. For each network or host destination, the IDXID="w9345"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"
network administrator configures the next hop router and the cost associated with the route.Routers can use static routes instead of, or in addition to, the routes learned from dynamic routing protocols such as RIP or OSPF. Usually, static routes are configured for destinations reachable through network interfaces that are not using a routing protocol.A IDXID="w9346"BOOK="_idx" COLLECTION="nw41" TIDREF="i3897"
static default route is often configured for IDXID="w9347"BOOK="_idx" COLLECTION="nw41" TIDREF="i4452"
TCP/IP hosts. This route defines a default router to which the host sends all packets destined for a remote network. If the default router is not the optimal path for a packet, the router can send an IDXID="w9348"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"
ICMP Redirect message to inform the host of the better path. The Router Discovery ProtocolIDXID="w9349"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"
 can be used instead of a default static route. This protocol allows the host to learn the identity of a router on the attached network dynamically.Static routes can be active or passiveIDXID="w9350"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"IDXID="w9351"BOOK="_idx" COLLECTION="nw41" TIDREF="i4270"
. An active static route can be replaced by a lower cost route learned from a dynamic routing protocol. A passive static route cannot be replaced by a route learned from a dynamic routing protocol.LABEL="5"PAGENUM=67 ID="BP72"ID="FM17675"Network Database File ManagementThis chapter describes the four network database files used to convert internal data into more identifiable and workable names. The following topics are discussed:MARK=BULLETIDREF="FM35276""Configuring Database Files"This section describes the four types of network database files and how to access and modify them.IDREF="FM18378""HOSTS File"This section describes the HOSTS file and how to administer it.IDREF="FM25808""NETWORKS File"This section describes the NETWORKS file and how to administer it.IDREF="FM18647""PROTOCOL File"This section describes the PROTOCOL file and how to administer it.IDREF="FM41515""SERVICES File"This section describes the SERVICES file and how to administer it.RENDERAS="SECT1"ID="FM35276"Configuring Database FilesTCP/IP uses four database files to convert internal data, such as IP addresses, into more identifiable and workable names. The user interface for IDXID="w9352"BOOK="_idx" COLLECTION="nw41" TIDREF="i4445"PAGENUM=68 ID="BP73"TCPCON and other NLMTM files uses these database files. You can inform TCP/IP of names and addresses of local nodes and networks by adding that information to these files. The files (HOSTS, NETWORKS, PROTOCOL, and SERVICES) are cached in memory to avoid disk access during lookup. Because of this, TCP/IP takes up more memory. If this is not desirable, keep the size of the database down, or simply delete the files.TCP/IP finds these files in the SYS:ETC\ directory:MARK=BULLETIDREF="FM18378"HOSTS File. This file maps hostnames to IP addresses.IDREF="FM25808"NETWORKS File. This file maps network names to network addresses.IDREF="FM18647"PROTOCOL File. This file maps protocol names to IP protocol numbers.IDREF="FM41515"SERVICES File. This file maps protocol names to service names.If you are configuring TCP/IP for the first time, Novell recommends that you start by copying the sample database files from SYS:ETC\SAMPLES to SYS:ETC. This provides you with some examples to refer to as you add your own entries, and also provides TCP/IP with the PROTOCOL and SERVICES files, which you do not need to modify.You can modify these files using a standard text editor from any NetWare® client, or you can use the EDIT NLM from the NetWare system's console. The following sections describe the formats of the files, which are compatible with the same files on standard 4.3BSD UNIX® systems. The examples in the sample files can also help you create your own entries.The files have the same names and format as the files on UnixWareTM and other UNIX systems. You can use FTP to transfer the files from a UNIX host.Each database file describes a table. Each line of the file describes a separate table entry. Blank lines and comments are ignored. Comments begin with a number sign (#) anywhere in a line and include the number sign and any characters following it on the same line.Do not use the sample addresses provided in the database files if you are connected to the Internet; these addresses are for example only.PAGENUM=69 ID="BP74"RENDERAS="SECT1"ID="FM18378"HOSTS FileIDXID="w9353"BOOK="_idx" COLLECTION="nw41" TIDREF="i693"IDXID="w9354"BOOK="_idx" COLLECTION="nw41" TIDREF="i1695"
The SYS:ETC\HOSTS file contains information about the known hosts on the IP internetwork. Typically, it is centrally administered and distributed to all local hosts. Its format, as shown in IDREF="FM29561"Figure 5-1, is identical to /etc/hosts on UNIX systems. Each entry provides information about a single host. An entry cannot extend beyond one line. LABEL="5-1" FLOAT="0"ID="FM29561"Sample HOSTS FileFILEREF="hosts.tif"The HOSTS file entry has the following format:FORMAT="LINESPECIFIC"MOREINFO="NONE"IP_address host_name [alias [...]]The IP_address is a 4-byte address in standard dotted decimal notation. Each byte is a decimal, hexadecimal, or octal value and is separated by a period. Hexadecimal numbers must start with the character pair 0x or 0X; octal numbers must start with 0.The host_name is the name of the system associated with this internetwork address. The name cannot contain a space, tab, number sign (#), or end-of-line character. Each hostname must be unique.The alias is another name for the same system. Typically, this is a shorter name. A single host can have from one to ten aliases. For example, the host "sales" could have the following address and aliases:FORMAT="LINESPECIFIC"MOREINFO="NONE"129.0.9.5 sales sa localhostPAGENUM=69 ID="BP75"PAGENUM=70The sample file SYS:ETC\SAMPLES\HOSTS is included with the TCP/IP software. When you are configuring TCP/IP for the first time, copy the sample HOSTS file from SYS:ETC\SAMPLES to SYS:ETC. You then edit the SYS:ETC\HOSTS file. You can change your configuration at any time by editing your existing SYS:ETC\HOSTS file.IDXID="w9355"BOOK="_idx" COLLECTION="nw41" TIDREF="i1695"IDXID="w9356"BOOK="_idx" COLLECTION="nw41" TIDREF="i1695"RENDERAS="SECT1"ID="FM25808"NETWORKS FileIDXID="w9357"BOOK="_idx" COLLECTION="nw41" TIDREF="i2890"
The SYS:ETC\NETWORKS file contains information about the networks in your internetwork. Each entry provides information about one network. An entry cannot extend beyond one line. IDREF="FM26569"Figure 5-2 shows a sample NETWORKS file.LABEL="5-2" FLOAT="0"ID="FM26569"Sample NETWORKS FileFILEREF="networks.tif"The NETWORKS file entry has the following format:FORMAT="LINESPECIFIC"MOREINFO="NONE"network_name network_number[/network_mask]
   [alias[...]]The network_name is the name of the network associated with this network number. The name cannot contain a space, tab, number sign (#), or end-of-line character. The network name must be unique.The network_number is the number of the network. Hexadecimal numbers must start with the character pair 0x or 0X. The network_number can be specified with or without trailing zeros. For example, the addresses 130.57 and 130.57.0.0 denote the same IP network.PAGENUM=70 ID="BP76"PAGENUM=71The network_mask is the subnet mask of the network. Like IP addresses, it can be specified in octal, decimal, or hexadecimal notation. This field is optional. If not specified, the subnet mask is deduced so that it excludes all trailing zeros. For example, 130.57.1.0 implies the mask 255.255.255.0.The alias is another name for the same network; you can specify up to ten aliases for a network.The sample file SYS:ETC\SAMPLES\NETWORKS is included with the TCP/IP software. When you are configuring TCP/IP for the first time, copy the sample NETWORKS file from SYS:ETC\SAMPLES to SYS:ETC. Then edit the SYS:ETC\NETWORKS file. You can change your configuration at any time by editing your existing SYS:ETC\NETWORKS file.IDXID="w9358"BOOK="_idx" COLLECTION="nw41" TIDREF="i2890"IDXID="w9359"BOOK="_idx" COLLECTION="nw41" TIDREF="i2890"RENDERAS="SECT1"ID="FM18647"PROTOCOL FileIDXID="w9360"BOOK="_idx" COLLECTION="nw41" TIDREF="i3590"
The SYS:ETC\PROTOCOL file, shown in IDREF="FM44408"Figure 5-3, contains information about the known protocols used on the internetwork. Each line provides information about one protocol. An entry cannot extend beyond one line. LABEL="5-3" FLOAT="0"ID="FM44408"Sample PROTOCOL FileFILEREF="protocol.tif"PAGENUM=71 ID="BP77"PAGENUM=72The PROTOCOL file entry has the following format:FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol_name protocol_number
    [alias [...]]The protocol_name is the name of the Internet protocol associated with this protocol number. The name cannot contain a space, tab, number sign (#), or end-of-line character.The protocol_number is the number of the Internet protocol.The alias is an alternate name for the protocol.The sample file SYS:ETC\SAMPLES\PROTOCOL is included with the TCP/IP software. When you are configuring TCP/IP for the first time, copy the sample PROTOCOL file from SYS:ETC\SAMPLES to SYS:ETC. You can then edit the SYS:ETC\PROTOCOL file. You can change your configuration at any time by editing your existing SYS:ETC\PROTOCOL file.IDXID="w9361"BOOK="_idx" COLLECTION="nw41" TIDREF="i3590"IDXID="w9362"BOOK="_idx" COLLECTION="nw41" TIDREF="i3590"RENDERAS="SECT1"ID="FM41515"SERVICES FileIDXID="w9363"BOOK="_idx" COLLECTION="nw41" TIDREF="i4082"
The SYS:ETC\SERVICES file, shown in IDREF="FM70837"Figure 5-4, contains information about the known services used on the IP internetwork. Each entry provides information about one service. An entry cannot extend beyond one line. LABEL="5-4" FLOAT="0"ID="FM70837"Sample SERVICES FileFILEREF="services.tif"PAGENUM=72 ID="BP78"PAGENUM=73The SERVICES file entry has the following format:FORMAT="LINESPECIFIC"MOREINFO="NONE"service_name port_number/protocol_name
    [alias [...]]The service_name is the name of the service associated with this port number and protocol name. The name cannot contain a space, tab, number sign (#), or end-of-line character. These are generally application, presentation, or session-level services, such as TFTP, FTP, SMTP, and TELNET.The port_number is the number of the Internet port used by the service. The protocol_name is the protocol with which the service is associated. This is generally a transport or network-level protocol, such as TCP or UDP. You must put a slash between the port number and the protocol name (for example, SMTP 25/TCP MAIL).The alias is an alternate name for the service.The sample file SYS:ETC\SAMPLES\SERVICES is included with the TCP/IP software. When you are configuring TCP/IP for the first time, you should copy the sample SERVICES file from SYS:ETC\SAMPLES to SYS:ETC. You can then edit the SYS:ETC\SERVICES file. You can change your configuration at any time by editing your existing SYS:ETC\SERVICES file.IDXID="w9364"BOOK="_idx" COLLECTION="nw41" TIDREF="i2890"IDXID="w9365"BOOK="_idx" COLLECTION="nw41" TIDREF="i2890"LABEL="6"PAGENUM=75 ID="BP79"ID="FM89908"SNMP ConceptsIDXID="w9366"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
This chapter describes TCP/IP network management using the SNMP and SNMPLOG NLMTM files. IDXID="w9367"BOOK="_idx" COLLECTION="nw41" TIDREF="i2868"IDXID="w9368"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9369"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
The following topics are discussed:MARK=BULLETIDREF="FM21389""SNMP Overview"This section introduces the Simple Network Management Protocol (SNMP).IDREF="FM39119""TCPCON"This section describes TCPCON briefly and instructs you where to go for more information.IDREF="FM17307""SNMP"This section describes the network management services provided by SNMP.IDREF="FM33664""SNMPLOG"This section describes how to log SNMP trap messages.RENDERAS="SECT1"ID="FM21389"SNMP OverviewIDXID="w9370"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
SNMP is the most popular network management protocol in the TCP/IP protocol suite. SNMP lets TCP/IP-based network management clients exchange information about the configuration and status of nodes on a TCP/IP-based internetwork. The information available is defined by a set of IDXID="w9371"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"managed objects referred to as the SNMP Management Information Base IDXID="w9372"BOOK="_idx" COLLECTION="nw41" TIDREF="i2314"
(MIB). The subset of managed objects that make up the TCP/IP portion of the MIB is maintained by each IDXID="w9373"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
TCP/IP node. SNMP also generates trap messages used to report significant TCP/IP events asynchronously to interested clients.PAGENUM=76 ID="BP80"TCP/IP supports SNMP access to the complete TCP/IP portion of the MIB, as maintained by the protocol stackIDXID="w9374"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9375"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
. The TCP/IP network management services are provided by three NLM files:MARK=BULLETIDREF="FM39119"TCPCONIDREF="FM17307"SNMPIDREF="FM33664"SNMPLOGThe IDXID="w9376"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP NLM acts as an SNMP IDXID="w9377"BOOK="_idx" COLLECTION="nw41" TIDREF="i141"
AgentIDXID="w9378"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
 for clients. It presents the standard TCP/IP portion of the MIB and generates trap messages required by the TCP/IP protocol stack. TCPCON is a client of the SNMP Agent NLM. It uses SNMP to communicate with the IDXID="w9379"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
TCP/IP protocol stack.The SNMPLOG NLM processes IDXID="w9380"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP trap messages directed to the local TCP/IP node and writes them to the log file:FORMAT="LINESPECIFIC"MOREINFO="NONE"SYS:ETC\SNMP$LOG.BINThis includes trap messages generated locally by SNMP NLM for reporting local events, and trap messages sent to this node from remote nodes for reporting remote events.RENDERAS="SECT1"ID="FM39119"TCPCONIDXID="w9381"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9382"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
TCPCON provides a menu-driven interface for probing the TCP/IP MIB and lets the console operator look at the local trap log maintained by SNMPLOG. IDXID="w9383"BOOK="_idx" COLLECTION="nw41" TIDREF="i4445"
TCPCON may effectively monitor the local node's TCP/IP stack or a remote TCP/IP stack.TCPCON uses SNMP to access the TCP/IP MIB information on the local node directly. TCPCON uses SNMP over UDP or IPX to access information on a remote node. IDREF="FM96643"Figure 6-1 shows the IDXID="w9384"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
local and remote access methods.For information about TCPCON, refer to BOOK="superenu" COLLECTION="nw41"NetWare 4.1 Supervising the Network.PAGENUM=77 ID="BP81"LABEL="6-1" FLOAT="0"ID="FM96643"Local and Remote TCP/IP Access FILEREF="4_1.tif"RENDERAS="SECT1"ID="FM17307"ID="FM16036"SNMPIDXID="w9385"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"The IDXID="w9386"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP NLM performs the IDXID="w9387"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP Agent services required by the TCP/IP module. It provides IDXID="w9388"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP managers, such as TCPCON, access to TCP/IP protocol stack-managed objects. It also generates SNMP trap messages used to report significant TCP/IP events. The IDXID="w9389"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP NLM provides load-time parameters for establishing the community name used during IDXID="w9390"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP message authentication. The community name contained in a request message from an SNMP manager client must match the name established by the agent. The agent discards any request message that contains an invalid community name, without generating a response to the managed client. By default, SNMP NLM provides the monitor community name "public," which is used for read-only SNMP requests. By default, it also disables SNMP write requests. In addition, the SNMP NLM provides a default community name used during SNMP trap message generation.PAGENUM=78 ID="BP82"You can configure three SNMP community name options in the Internetworking Configuration utility (INETCFG). The community name options are:MARK=BULLETMonitor CommunityControl CommunityTrap CommunityEach option sets the community name for the indicated community. Community names are used to authenticate SNMP messages received at the agent. The community name in a message requesting a given access type must match the name defined for that access type by one of the SNMP community options.RENDERAS="SECT1"ID="FM33664"SNMPLOGIDXID="w9391"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
To log SNMP trap messages received by the local TCP/IP node, load the SNMPLOG NLM after loading the TCPIP NLM. Once running, the SNMPLOG NLM writes all arriving SNMP trap messages to disk. SNMPLOG is a background process that does not provide a console interface. If you do not require trap message logging, or if trap messages are being directed to another TCP/IP node, you do not need to load SNMPLOG NLM.Trap message information is written in binary form to the file SYS:ETC\SNMP$LOG.BIN. No size restriction is placed on the log file. To avoid consuming excessive disk space, you should delete the file periodically. If the file does not exist when a trap message is received, SNMPLOG creates it. The log file contents cannot be read by a text editor; however, you can use the TCPCON NLM to view the file contents or delete the file.The TCPIP NLM sends trap messages to the local node unless you specify a remote SNMP manager during TCP/IP protocol configuration (using INETCFG). In other words, unless otherwise instructed, each node logs its own traps. Specifying a SNMP manager redirects traps to some other node. See IDREF="FM11287""SNMP Manager Table" for more information about SNMP Manager parameters.The trap address can be set to the same server on all nodes. In this way, all trap messages from all IDXID="w9392"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"
SNMP Agents can be logged at a single node.LABEL="7"PAGENUM=79 ID="BP83"ID="FM20503"TCP/IP Configuration ParametersIDXID="w9393"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
This chapter describes how to use the Internetworking Configuration IDXID="w9394"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
(INETCFG) utility to configure the TCP/IP parameters for the NetWare® 4.1. The following topics are discussed:MARK=BULLETIDREF="FM11433""Configuring TCP/IP Protocol Parameters"This section describes how to access the TCP/IP parameters and what each parameter does.IDREF="FM28852""Binding TCP/IP to a LAN Interface Parameters"This section describes how to bind TCP/IP to a LAN interface. It also provides a description of the CLASS=MENUITEM MOREINFO="NONE"BIND parameters that apply to LAN interfaces.IDREF="FM30695""Configuring TCP/IP Filtering Parameters"This section describes how to configure the TCP/IP filtering parameters and what each parameter does.RENDERAS="SECT1"ID="FM11433"Configuring TCP/IP Protocol ParametersIDXID="w9395"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9396"BOOK="_idx" COLLECTION="nw41" TIDREF="i3596"
After configuring the network interface boards for your router, select the following menu sequence, starting from the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration main menu:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"CLASS=MENUITEM MOREINFO="NONE"ProtocolsCLASS=MENUITEM MOREINFO="NONE"TCP/IPThe CLASS=MENUITEM MOREINFO="NONE"TCP/IP Configuration window appears, displaying the parameters described in the sections that follow.PAGENUM=80 ID="BP84"RENDERAS="SECT2"TCP/IP StatusIDXID="w9397"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9398"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"Determines whether the TCP/IP protocol is activated during system initialization. If this option is disabled, the configuration is retained, but it is not active.Default: EnabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT2"IP Packet ForwardingIDXID="w9399"BOOK="_idx" COLLECTION="nw41" TIDREF="i1866"IDXID="w9400"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9401"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
Determines whether the server is used as an IP router (Enabled) or as an end node only (Disabled).Default: EnabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT2"RIPIDXID="w9402"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9403"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9404"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
Enables the router to use the Routing Information Protocol (RIP) to exchange routing information with other routers on the network and maintain a dynamic routing table. If disabled, the router does not run RIP, and you must use OSPF, EPG, a static routing table, or a default gateway.Default: EnabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPPAGENUM=80 ID="BP85"PAGENUM=81RENDERAS="SECT2"OSPFIDXID="w9405"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
Select CLASS=MENUITEM MOREINFO="NONE"OSFP to enable the router to use the OSPF protocol to exchange routing information with other routers on the network and maintain a dynamic routing table. If disabled, the router does not run OSPF, and you must use RIP, EPG, a static routing table, or a default gateway.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT2"OSPF Configuration ParametersIDXID="w9406"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"If you have enabled OSPF, select this option to display a window with the OSPF configuration parameters described in the sections that follow.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT3"Router IDIDXID="w9407"BOOK="_idx" COLLECTION="nw41" TIDREF="i3129"Uniquely identifies the router within the OSPF routing domain. It is expressed in dotted IP address format (1.2.3.4). If this parameter is not specified or has a value of 0.0.0.0, the router uses the first IP address bound to an interface.Default: First IP addressUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF ConfigurationPAGENUM=81 ID="BP86"PAGENUM=82RENDERAS="SECT3"Autonomous System Boundary RouterIDXID="w9408"BOOK="_idx" COLLECTION="nw41" TIDREF="i3129"Allows OSPF to include routes learned from other sources such as RIP, static routes, or EGP. To exclude specific routes, enable the CLASS=MENUITEM MOREINFO="NONE"Filter Support parameter and load FILTCFG to configure routing information filters.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF ConfigurationRENDERAS="SECT3"Area Configuration ParametersIDXID="w9409"BOOK="_idx" COLLECTION="nw41" TIDREF="i285"IDXID="w9410"BOOK="_idx" COLLECTION="nw41" TIDREF="i3129"
When this option is selected, the currently configured OSPF areas are displayed. To configure a new area, press MOREINFO="NONE"<Ins> and set the parameters as required. A new window displays the area configuration parameters described in the sections that follow.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF ConfigurationRENDERAS="SECT4"Area IDIDXID="w9411"BOOK="_idx" COLLECTION="nw41" TIDREF="i3129"Uniquely identifies the area. This parameter must be specified when an area is configured; there is no default. It is expressed in dotted IP address format (1.2.3.4). It is often based on the address ranges specified for the area. The CLASS=MENUITEM MOREINFO="NONE"Area ID with a value of 0.0.0.0 refers to the backbone area. The backbone is configured automatically when OSPF is configured for the first time.Default: NoneUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > SelectCLASS=MENUITEM MOREINFO="NONE" Area Configuration > (OSPF Areas menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>PAGENUM=83 ID="BP87"RENDERAS="SECT4"AuthenticationIDXID="w9412"BOOK="_idx" COLLECTION="nw41" TIDREF="i290"Defines the authentication applied to the routing exchanges within an area. If set to CLASS=MENUITEM MOREINFO="NONE"Disabled, no authentication takes place. If set to CLASS=MENUITEM MOREINFO="NONE"Enabled, a 64-bit password is associated with each network in the area. The CLASS=MENUITEM MOREINFO="NONE"Authentication Key (set in the CLASS=MENUITEM MOREINFO="NONE"Bindings options) defines the password used on a particular network.If this parameter is set to CLASS=MENUITEM MOREINFO="NONE"Disabled, the CLASS=MENUITEM MOREINFO="NONE"Authentication Key parameter (set in CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options) has no meaning.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > SelectCLASS=MENUITEM MOREINFO="NONE" Area Configuration > (OSPF Areas menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>RENDERAS="SECT4"Area TypeIDXID="w9413"BOOK="_idx" COLLECTION="nw41" TIDREF="i3129"If set to CLASS=MENUITEM MOREINFO="NONE"Stub, AS External Advertisements are not flooded through the area. All routers connecting to a stub area should agree on the area's type. Stub areas cannot be used as transit areas when configuring a virtual link.Default: Normal If Area Type is set to 0.0.0.0 (backbone), it is not used because the backbone area cannot be a stub area.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > SelectCLASS=MENUITEM MOREINFO="NONE" Area Configuration > (OSPF Areas menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>PAGENUM=83 ID="BP88"PAGENUM=84RENDERAS="SECT4"Stub CostIDXID="w9414"BOOK="_idx" COLLECTION="nw41" TIDREF="i290"This is the cost of the default route advertised in the stub area. Used only when the area type is configured as a stub. The CLASS=MENUITEM MOREINFO="NONE"Stub Cost is used when the default summary link is advertised into the stub area. Set the default to the minimum interface cost of all OSPF enabled interfaces that are not attached to this area.Range: 1 to FFFFFFDefault: 1 Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > SelectCLASS=MENUITEM MOREINFO="NONE" Area Configuration > (OSPF Areas menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>RENDERAS="SECT3"Virtual Link Configuration IDXID="w9415"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9416"BOOK="_idx" COLLECTION="nw41" TIDREF="i4768"IDXID="w9417"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
When you select CLASS=MENUITEM MOREINFO="NONE"Virtual Link Configuration, a new window displays the currently configured OSPF virtual links. To configure a new virtual link, press MOREINFO="NONE"<Ins> and set the parameters as required. A new window displays the virtual link configuration parameters described in the sections that follow.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF ConfigurationRENDERAS="SECT4"Router ID of NeighborIDXID="w9418"BOOK="_idx" COLLECTION="nw41" TIDREF="i4769"Defines the remote end of the virtual link. The hostnames contained in the SYS:ETC\HOSTS file are presented as choices for possible neighbors.This parameter must be configured for a virtual link.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > Select CLASS=MENUITEM MOREINFO="NONE"Virtual Link Configuration > (OSPF Virtual Links menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=85 ID="BP89"RENDERAS="SECT4"Transit AreaIDXID="w9419"BOOK="_idx" COLLECTION="nw41" TIDREF="i4769"Defines the area through which the virtual link must pass to reach the backbone area. One of the router's OSPF enabled interfaces must attach to the transit area, but the transit area cannot be the backbone (0.0.0.0).Previously configured areas are listed as choices.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > Select CLASS=MENUITEM MOREINFO="NONE"Virtual Link Configuration > (OSPF Virtual Links menu appears) > Press MOREINFO="NONE"<Ins>RENDERAS="SECT4"Authentication KeyIDXID="w9420"BOOK="_idx" COLLECTION="nw41" TIDREF="i4769"An 8-byte string that is used as a password when the authentication is enabled for the transit area. Default: NoneUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > Select CLASS=MENUITEM MOREINFO="NONE"Virtual Link Configuration > (OSPF Virtual Links menu appears) > Press MOREINFO="NONE"<Ins>RENDERAS="SECT4"Hello IntervalIDXID="w9421"BOOK="_idx" COLLECTION="nw41" TIDREF="i4769"Time, in seconds, between the transmission of Hello packets on this virtual link.Range: 1 to FFFF (These values must be the same for both routers on the virtual link.)Default: 10 secondsUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > Select CLASS=MENUITEM MOREINFO="NONE"Virtual Link Configuration > (OSPF Virtual Links menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=86 ID="BP90"RENDERAS="SECT4"Router Dead IntervalIDXID="w9422"BOOK="_idx" COLLECTION="nw41" TIDREF="i4769"Time, in seconds, that can expire without the local node seeing any Hello packets from the remote end of the virtual link before it can declare the remote end is down. The value of this parameter must be the same for both routers on the virtual link.Range: 1 to 7FFFFFFFDefault: 40Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Configuration > Select CLASS=MENUITEM MOREINFO="NONE"Virtual Link Configuration > (OSPF Virtual Links menu appears) > Press MOREINFO="NONE"<Ins>RENDERAS="SECT2"Static Routing IDXID="w9423"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"IDXID="w9424"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9425"BOOK="_idx" COLLECTION="nw41" TIDREF="i4271"
Determines whether a static routing database is loaded automatically during a system initialization. If disabled, the static routing database is ignored.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols, Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT2"Static Routing TableIDXID="w9426"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"When you select the CLASS=MENUITEM MOREINFO="NONE"Static Routing Table, a new window displays the currently configured static routing database. To add new routes to the database, pressMOREINFO="NONE" <Ins> and set the parameters as required. When adding a new route, the entry must include the destination network or host address and the address of the next hop. A new window displays the static routing parameters described in the sections that follow. Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPPAGENUM=87 ID="BP91"RENDERAS="SECT3"Route to Network or HostIDXID="w9427"BOOK="_idx" COLLECTION="nw41" TIDREF="i4273"IDXID="w9428"BOOK="_idx" COLLECTION="nw41" TIDREF="i3884"
Determines whether the route applies to datagrams addressed to a specific host or to any host on a given network. There are three options: CLASS=MENUITEM MOREINFO="NONE"Host, CLASS=MENUITEM MOREINFO="NONE"Default Route, and CLASS=MENUITEM MOREINFO="NONE"Network.Default: NetworkUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Static Routing Table > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Static Routes menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>RENDERAS="SECT3"IP Address of Network or HostIDXID="w9429"BOOK="_idx" COLLECTION="nw41" TIDREF="i4273"IDXID="w9430"BOOK="_idx" COLLECTION="nw41" TIDREF="i98"
IP address of the network or host to which data is routed.For network addresses, you can enter only the network portion of the address without trailing zeros. For example, enter 128.1 to route to network 128.1.0.0.An address of 0.0.0.0 indicates a default route and is not allowed. To configure a default route, select CLASS=MENUITEM MOREINFO="NONE"Default Route in the CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host parameter.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Static Routing Table > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Static Routes menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>RENDERAS="SECT3"Subnetwork MaskIDXID="w9431"BOOK="_idx" COLLECTION="nw41" TIDREF="i4273"Use only with network routes. If this parameter is not specified, the natural subnet mask is used.A mask of 255.255.255.255 indicates a host route; however, it is not allowed. To configure a host route, select CLASS=MENUITEM MOREINFO="NONE"Host from the CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host parameter.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Static Routing Table > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Static Routes menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>PAGENUM=88 ID="BP92"RENDERAS="SECT3"Next Hop TypeIDXID="w9432"BOOK="_idx" COLLECTION="nw41" TIDREF="i4273"Indicates the type of the CLASS=MENUITEM MOREINFO="NONE"Next Hop Router on Route parameter. The next hop of this route can be an IP address. When you set the CLASS=MENUITEM MOREINFO="NONE"Next Hop Type parameter to the CLASS=MENUITEM MOREINFO="NONE"Gateway IP Address value, you must specify the IP address of the CLASS=MENUITEM MOREINFO="NONE"Next Hop Router on Route parameter. Default: Gateway IP AddressUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Static Routing Table > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Static Routes menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>RENDERAS="SECT3"Next Hop Router on RouteIDXID="w9433"BOOK="_idx" COLLECTION="nw41" TIDREF="i4273"IDXID="w9434"BOOK="_idx" COLLECTION="nw41" TIDREF="i2916"
Closest router along the route. You can specify this parameter as the IP address name of the next hop router. If you specify an IP address, it must have the same number for the network portion of the address as one of your local interfaces. Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Static Routing Table > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Static Routes menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>RENDERAS="SECT3"Metric for this RouteIDXID="w9435"BOOK="_idx" COLLECTION="nw41" TIDREF="i4273"IDXID="w9436"BOOK="_idx" COLLECTION="nw41" TIDREF="i2434"
The number of hops or routers that data must go through to reach its destination. Routes with lower metric values are chosen first when the router determines the best path. A value of 16 disables the route.Range: 1 to 16Default: 1Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Static Routing Table > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Static Routes menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>PAGENUM=89 ID="BP93"RENDERAS="SECT3"Type of RouteIDXID="w9437"BOOK="_idx" COLLECTION="nw41" TIDREF="i4273"IDXID="w9438"BOOK="_idx" COLLECTION="nw41" TIDREF="i4612"
Specifies the route as CLASS=MENUITEM MOREINFO="NONE"Active or CLASS=MENUITEM MOREINFO="NONE"Passive. Active routes are updated or replaced with information learned from dynamic routing protocols such as RIP. Passive routes are permanent entries. They are entered only by IP during initialization and never time out or are replaced.Default: PassiveUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Static Routing Table > (CLASS=MENUITEM MOREINFO="NONE"TCP/IP Static Routes menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>RENDERAS="SECT2"ID="FM11287"SNMP Manager IDXID="w9439"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
TableIDXID="w9440"BOOK="_idx" COLLECTION="nw41" TIDREF="i4158"IDXID="w9441"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"
When you select the CLASS=MENUITEM MOREINFO="NONE"SNMP Manager Table, a new window displays the currently configured addresses of SNMP management stations that receive SNMP traps from this router. To add a new SNMP management station, pressMOREINFO="NONE" <Ins>. The default is to send SNMP traps to the loopback address of 127.0.0.1. A new window displays the parameter described in the following section.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT3"IP Address of ManagerSpecifies the addresses of SNMP management stations that receive SNMP traps from this router. The default is to send SNMP traps to the loopback address of 127.0.0.1.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" SNMP Manager Table > (SNMP Manager Table menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>PAGENUM=89 ID="BP94"PAGENUM=90RENDERAS="SECT2"FilterIDXID="w9442"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
 SupportIDXID="w9443"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"TCP/IP supports packet forwarding filters and routing information filters. You can configure the filters through the Filter Configuration utility (FILTCFG). However, filter support must be enabled here for TCP/IP to use filter configuration in FILTCFG.For more information about filtering, refer to IDREF="FM30695""Configuring TCP/IP Filtering Parameters."Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT2"TCP/IP Expert Configuration IDXID="w9444"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
OptionsIDXID="w9445"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"When you select CLASS=MENUITEM MOREINFO="NONE"TCP/IP Expert Configuration Options, a new window displays the expert TCP/IP configuration parameters described in the sections that follow.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT3"Directed Broadcast ForwardingIDXID="w9446"BOOK="_idx" COLLECTION="nw41" TIDREF="i1386"Determines whether the router forwards any directed broadcasts that it receives. Because forwarding directed broadcasts increases network traffic, only enable this parameter if your applications require it.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Expert Configuration OptionsPAGENUM=91 ID="BP95"RENDERAS="SECT3"BOOTP Forwarding Configuration ParametersIDXID="w9447"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"When you select CLASS=MENUITEM MOREINFO="NONE"BOOTP Forwarding Configuration, a new window displays the BOOTP configuration parameters described in the sections that follow.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Expert Configuration OptionsRENDERAS="SECT4"BOOTP Packet ForwardingIDXID="w9448"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"Allows the BOOTP packet forwarding service to be enabled or disabled. When enabled, the router forwards received BOOTP broadcasts to a configured BOOTP server.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"BOOTP Forwarding ConfigurationRENDERAS="SECT4"BOOTP Server ListIDXID="w9449"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"When you select this option, a new window displays the currently configured BOOTP server list. To add a new server to the list, press MOREINFO="NONE"<Ins> and set the parameters as required. A new window displays the following BOOTP server configuration parameter: Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"BOOTP Forwarding ConfigurationMARK=BULLETCLASS=MENUITEM MOREINFO="NONE"BOOTP Server AddressIDXID="w9450"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"Specifies the IP address of the BOOTP server. A maximum of four BOOTP servers can be configured. Received BOOTP broadcasts are forwarded to the servers. If no BOOTP servers are configured, BOOTP cannot be enabled. PAGENUM=91 ID="BP96"PAGENUM=92Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"BOOTP Forwarding Configuration > Select CLASS=MENUITEM MOREINFO="NONE"BOOTP Server List > PressMOREINFO="NONE" <Ins>RENDERAS="SECT4"Log OperationIDXID="w9451"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"Determines whether use of the BOOTP forwarder is logged. You can select whether to log to the BOOTP window or to a log file. If you choose to log to a file, you can specify a filename.Default: Do not logUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"BOOTP Forwarding ConfigurationRENDERAS="SECT4"Log FileIDXID="w9452"BOOK="_idx" COLLECTION="nw41" TIDREF="i504"Allows you to specify the name of the file that contains the BOOTP log. This parameter is active when you have selected the CLASS=MENUITEM MOREINFO="NONE"Log to a File option from the CLASS=MENUITEM MOREINFO="NONE"Log Operation parameter. The default filename is sys:\etc\bootp.log.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"BOOTP Forwarding ConfigurationRENDERAS="SECT3"EGPIDXID="w9453"BOOK="_idx" COLLECTION="nw41" TIDREF="i1386"When you select CLASS=MENUITEM MOREINFO="NONE"EGP, the router uses the EGP protocol to exchange routing information with EGP routers in other autonomous systems. If disabled, the router does not run EGP. In addition to enabling EGP, you must configure the routes advertised or accepted by EGP using FILTCFG.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)PAGENUM=93 ID="BP97"Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > Select CLASS=MENUITEM MOREINFO="NONE"BOOTP Forwarding ConfigurationIn addition to enabling EGP, you must use the FILTCFG utility to configure the routes advertised or accepted by EGP.RENDERAS="SECT3"EGP Configuration ParametersIDXID="w9454"BOOK="_idx" COLLECTION="nw41" TIDREF="i1386"When you select CLASS=MENUITEM MOREINFO="NONE"EGP Configuration, a new window displays the EGP configuration parameters described in the sections that follow.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration OptionsRENDERAS="SECT4"Autonomous SystemIDXID="w9455"BOOK="_idx" COLLECTION="nw41" TIDREF="i1386"Uniquely identifies the autonomous system to which this router belongs. The router establishes EGP neighbor relationships with routers in other autonomous systems.Because there is no default, EGP cannot be enabled successfully if the autonomous system number is not specified.Range: 0 to 65535Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > SelectCLASS=MENUITEM MOREINFO="NONE" EGP ConfigurationRENDERAS="SECT4"Maximum Neighbors to AcquireIDXID="w9456"BOOK="_idx" COLLECTION="nw41" TIDREF="i1386"Number of neighbors with which EGP attempts to establish concurrent relationships and exchange EGP information. EGP only establishes relationships with neighbors configured in the CLASS=MENUITEM MOREINFO="NONE"Neighbor List. Only neighbors on directly attached networks are supported.Range: 1 to 8PAGENUM=94 ID="BP98"Default: 1Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options> SelectCLASS=MENUITEM MOREINFO="NONE" EGP ConfigurationRENDERAS="SECT4"Neighbor ListIDXID="w9457"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"When you select this option, a new window displays the neighbor list of currently configured neighbors. To add a new neighbor to the list, pressMOREINFO="NONE" <Ins> and set the parameters as required. A new window displays the neighbor list configuration parameters: Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options> SelectCLASS=MENUITEM MOREINFO="NONE" EGP ConfigurationMARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Neighbor's AddressIDXID="w9458"BOOK="_idx" COLLECTION="nw41" TIDREF="i1386"IP address of the neighbor. Press MOREINFO="NONE"<Ins> to display the host addresses contained in the SYS:ETC\HOSTS file. You can select neighbors from this list.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > SelectCLASS=MENUITEM MOREINFO="NONE" EGP Configuration > SelectCLASS=MENUITEM MOREINFO="NONE" Neighbor List > (CLASS=MENUITEM MOREINFO="NONE"Configured EGP Neighbors menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"Neighbor's Autonomous SystemIDXID="w9459"BOOK="_idx" COLLECTION="nw41" TIDREF="i1386"Uniquely identifies the autonomous system to which the neighbor belongs.Range: 0 to 65535Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Protocols > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert Configuration Options > SelectCLASS=MENUITEM MOREINFO="NONE" EGP Configuration > SelectCLASS=MENUITEM MOREINFO="NONE" Neighbor List > (CLASS=MENUITEM MOREINFO="NONE"Configured EGP Neighbors menu appears) > PressMOREINFO="NONE" <Ins>PAGENUM=95 ID="BP99"RENDERAS="SECT1"ID="FM28852"Binding TCP/IP to a LAN Interface ParametersIDXID="w9460"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9461"BOOK="_idx" COLLECTION="nw41" TIDREF="i2037"
After you configure the TCP/IP protocol parameters, bind TCP/IP to a LAN interface by selecting the following menu sequence, starting from the CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration main menu:IDXID="w9462"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"BindingsPress the MOREINFO="NONE"<Enter> key TCP/IP connection to the LAN interface to which you want to attach.A new window displays the parameters described in the sections that follow.RENDERAS="SECT2"Network InterfaceRead-only parameter that displays the name you assigned to the LAN interface configuration.IDXID="w9463"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP RENDERAS="SECT2"Local IP Address of InterfaceIDXID="w9464"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9465"BOOK="_idx" COLLECTION="nw41" TIDREF="i2165"
The node's local IP address on the network is connected to this interface. The address must be entered as four decimal or hexadecimal numbers separated by dots (for example, 192.89.4.1). Each IP address on an IP internetwork must be unique, and is usually assigned by the network administrator. Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPPAGENUM=95 ID="BP100"PAGENUM=96RENDERAS="SECT2"Subnetwork Mask of Connected NetworkIDXID="w9466"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9467"BOOK="_idx" COLLECTION="nw41" TIDREF="i4318"
Subnetwork mask of the network attached to this interface. This setting must match the mask used by the other nodes on the network. In the mask, each bit of the network portion of the address is set to one, and each bit of the host portion of the address is set to zero. If you do not specify the mask, IP assumes that the network is not divided into subnetworks.You can enter the subnetwork mask in decimal or hexadecimal form.For more information about the subnetwork mask, refer to IDREF="FM99805"Chapter 3, "IP Addressing Concepts."Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP RENDERAS="SECT2"RIP Bind ParametersIDXID="w9468"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9469"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options to display a window with the RIP bind parameters described in the sections that follow. Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP RENDERAS="SECT3"Network InterfaceIDXID="w9470"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9471"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"Read-only parameter that displays the name you assigned to the LAN network interface configuration. Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT3"StatusIDXID="w9472"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"Determines whether RIP packets are sent and received on this interface. This option is enabled by default when RIP is enabled and the interface is bound to IP.Default: EnabledPAGENUM=97 ID="BP101"Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT3"Cost of InterfaceIDXID="w9473"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9474"BOOK="_idx" COLLECTION="nw41" TIDREF="i857"
Enter a number to indicate the preference of the interface to which you are attaching TCP/IP. Use a higher number to discourage the use of the interface. For RIP, the maximum value is 15.Range: 1 to 15Default: 1Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT3"Originate Default RouteIDXID="w9475"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9476"BOOK="_idx" COLLECTION="nw41" TIDREF="i3124"IDXID="w9477"BOOK="_idx" COLLECTION="nw41" TIDREF="i967"
Determines whether the router announces itself as a default router for this network through RIP.Default: Disabled: Present Normal ValueUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT3"Poison ReverseIDXID="w9478"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9479"BOOK="_idx" COLLECTION="nw41" TIDREF="i3332"
Determines whether RIP uses Poison Reverse in RIP updates when this node is acting as a router. If this parameter is disabled, RIP traffic on the network is reduced, at a small cost in stability. For information about RIP and Poison Reverse, refer to RFC 1058.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsPAGENUM=98 ID="BP102"RENDERAS="SECT3"RIP ModeIDXID="w9480"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"Determines whether RIPI, RIPII, RIPI and RIPII, or Send Only is used.Default: RIPIUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT3"RIPII OptionsIDXID="w9481"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"IDXID="w9482"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
This parameter is active when you chose either the RIP or RIPI and RIPII options. Select it to display a screen that allows you to enter the following RIPII parameters: Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT4"IDXID="w9483"BOOK="_idx" COLLECTION="nw41" TIDREF="i3865"
AuthenticationDetermines whether RIPII uses simple authentication or no authentication.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options > SelectCLASS=MENUITEM MOREINFO="NONE" RIP Mode > SelectCLASS=MENUITEM MOREINFO="NONE" RIPII orCLASS=MENUITEM MOREINFO="NONE" RIPI & RIPII > SelectCLASS=MENUITEM MOREINFO="NONE" RIPII OptionsRENDERAS="SECT4"IDXID="w9484"BOOK="_idx" COLLECTION="nw41" TIDREF="i3865"
Authentication KeyA 16-byte string that is used as a password when authentication is enabled on the attached network.Default: NoneUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)PAGENUM=99 ID="BP103"Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options > SelectCLASS=MENUITEM MOREINFO="NONE" RIP Mode > SelectCLASS=MENUITEM MOREINFO="NONE" RIPII orCLASS=MENUITEM MOREINFO="NONE" RIPI & RIPII > SelectCLASS=MENUITEM MOREINFO="NONE" RIPII OptionsRENDERAS="SECT3"Neighbor List ParametersIDXID="w9485"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"When this option is selected, a window displays the currently configured RIP neighbors. To add a new neighbor to the list, press MOREINFO="NONE"<Ins> and set the parameters as required. A new window displays the following RIP neighbors configuration parameter: Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind OptionsRENDERAS="SECT4"IP Address of RIP NeighborIDXID="w9486"BOOK="_idx" COLLECTION="nw41" TIDREF="i3861"Specifies the IP address of the RIP neighbor. If RIP neighbors are configured, RIP update messages are sent to the configured neighbors as unicast. Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"RIP Bind Options > SelectCLASS=MENUITEM MOREINFO="NONE" Neighbor List (RIP Neighbors menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE" (RIP Neighbor Address Configuration menu appearsCLASS=MENUITEM MOREINFO="NONE")RENDERAS="SECT2"OSPF Bind ParametersIDXID="w9487"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9488"BOOK="_idx" COLLECTION="nw41" TIDREF="i1386"
When you select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options, a new window displays the OSPF bind parameters described in the sections that follow.RENDERAS="SECT3"Network InterfaceIDXID="w9489"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Read-only parameter that displays the name you assigned to the LAN network interface configuration. Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsPAGENUM=100 ID="BP104"RENDERAS="SECT3"StatusIDXID="w9490"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9491"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Determines whether OSPF packets are sent and received on this interface. If disabled, this interface is not included in OSPF's internal Link State Advertisements. This option is enabled by default when OSPF is enabled and the interface is bound to IP.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsRENDERAS="SECT3"Cost of InterfaceIDXID="w9492"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Enter a number to indicate the preference of the interface to which you are binding TCP/IP. This is the link state metric cost of sending a packet on this network. Use a higher number to discourage the use of the interface.Range: 1 to 65535Default: 1Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsRENDERAS="SECT3"Area IDIDXID="w9493"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Uniquely identifies the area. It is expressed in dotted IP address format (0.0.0.0). It is often based on the address ranges specified for the area. Selecting this option brings up a list of the previously configured areas. The area ID 0.0.0.0 refers to the backbone area. Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsPAGENUM=101 ID="BP105"RENDERAS="SECT3"PriorityIDXID="w9494"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Determines which router takes precedence when more than one router attempts to become the Designated Router for the attached network. When the priority parameter is set to 0, the router is not eligible as a Designated Router.Range: 0 to 255Default: 1Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsRENDERAS="SECT3"Authentication KeyIDXID="w9495"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"An 8-byte string that is used as a password on the attached network when an area's network has authentication. Default: NoneUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsRENDERAS="SECT3"Hello IntervalIDXID="w9496"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Time, in seconds, between the transmission of Hello packets on this interface. This value must be the same for all routers on this network. Range: 1 to FFFFDefault: 10Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsPAGENUM=102 ID="BP106"RENDERAS="SECT3"Router Dead IntervalIDXID="w9497"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Time, in seconds, that can expire without seeing any Hello packets from a router before it can declare that the router is down. This value must be the same for all routers on this network. Range: 1 to 7FFFFFFFDefault: 40Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsRENDERAS="SECT3"Neighbor ListIDXID="w9498"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"When this option is selected, a window displays the currently configured OSPF neighbors. To add a new neighbor to the list, press MOREINFO="NONE"<Ins> and set the parameters as required. A new window displays the following OSPF neighbors configuration parameter: Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind OptionsRENDERAS="SECT4"IP Address of OSPF NeighborIDXID="w9499"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"Specifies the IP address of the neighbor. It is expressed in dotted IP address format (1.2.3.4). An entry must be inserted for each neighbor that is eligible to become the Designated Router on this nonbroadcast multicast network.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF Bind Options > SelectCLASS=MENUITEM MOREINFO="NONE" Neighbor List (OSPF Neighbors menu appearsCLASS=MENUITEM MOREINFO="NONE") > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE" (OSPF Neighbor Address Configuration menu appearsCLASS=MENUITEM MOREINFO="NONE")PAGENUM=103 ID="BP107"RENDERAS="SECT2"Expert TCP/IP Bind ParametersIDXID="w9500"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9501"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options to display a screen with the expert TCP/IP bind parameters described in the sections that follow.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP RENDERAS="SECT3"Network InterfaceIDXID="w9502"BOOK="_idx" COLLECTION="nw41" TIDREF="i1388"Read-only parameter that displays the name you assigned to the LAN network interface configuration. Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears)RENDERAS="SECT3"Frame TypeIDXID="w9503"BOOK="_idx" COLLECTION="nw41" TIDREF="i1388"Determines the frame type you assigned to the LAN network interface configuration. Default: determined by the media typeUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears)RENDERAS="SECT3"Use of ARPIDXID="w9504"BOOK="_idx" COLLECTION="nw41" TIDREF="i1388"Determines whether the Address Resolution Protocol (ARP) is used on this network. Default: EnabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears)PAGENUM=104 ID="BP108"RENDERAS="SECT3"Broadcast AddressIDXID="w9505"BOOK="_idx" COLLECTION="nw41" TIDREF="i1389"Determines which address the router uses for broadcasting on this network. This address should match the broadcast address of all the other machines on your network.Using the all-ones broadcast (FF.FF.FF.FF) is the safest option because it ensures that the broadcast packet is not forwarded.Default: FF.FF.FF.FF (recommended)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears)RENDERAS="SECT3"Multicast Override IP AddressIDXID="w9506"BOOK="_idx" COLLECTION="nw41" TIDREF="i1388"
Determines the IP address that directs IP multicast packets, overriding IP's standard multicast handling.Novell recommends that you leave this parameter unspecified.Default: NoneUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears)RENDERAS="SECT3"Force Proxy ARPIDXID="w9507"BOOK="_idx" COLLECTION="nw41" TIDREF="i1389"IDXID="w9508"BOOK="_idx" COLLECTION="nw41" TIDREF="i1534"
Determines whether the router is forced to use Proxy ARP. Proxy ARP is useful when devices on the interface do not support IP subnetworking and are not aware that they must go through a router to reach devices on other subnetworks of the same IP network.If Proxy ARP is enabled, the router responds to ARP requests generated for devices on other subnetworks. Proxy ARP is also needed on the parent network of a stub network. The parent network has an IP address range that includes the IP address range of the stub network. The router responds to ARP requests sent on the parent network for devices on the stub network.PAGENUM=105 ID="BP109"When both the parent and stub subnetwork are bound to IP interfaces, the router can detect the parent/stub subnetwork scenario and automatically enable Proxy ARP for the appropriate interfaces. If Proxy ARP is not required, it can still be forced to be enabled with this parameter.For more information about configuring Proxy ARP, refer to BOOK="superenu" COLLECTION="nw41"NetWare 4.1 Supervising the Network.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears)RENDERAS="SECT3"ID="FM11056"Router Discovery OptionsIDXID="w9509"BOOK="_idx" COLLECTION="nw41" TIDREF="i3888"IDXID="w9510"BOOK="_idx" COLLECTION="nw41" TIDREF="i1388"
Select CLASS=MENUITEM MOREINFO="NONE"Router Discovery Options to display a screen with the router discovery parameters described in the sections that follow.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears)RENDERAS="SECT4"Network InterfaceIDXID="w9511"BOOK="_idx" COLLECTION="nw41" TIDREF="i1388"Read-only parameter that displays the name you assigned to the LAN network interface configuration.Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears) > Select CLASS=MENUITEM MOREINFO="NONE"Router Discovery OptionsPAGENUM=105 ID="BP110"PAGENUM=106RENDERAS="SECT4"StatusIDXID="w9512"BOOK="_idx" COLLECTION="nw41" TIDREF="i1388"Determines whether router discovery packets are sent and received on this interface. If IP Packet Forwarding has been enabled, enabling this option causes the server to send router discovery advertisements at a configurable rate and respond to advertisement requests. If IP Packet Forwarding has been disabled, enabling this option causes the server to send router discovery requests to find a router.Default: DisabledUtility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears) > Select CLASS=MENUITEM MOREINFO="NONE"Router Discovery OptionsRENDERAS="SECT4"Destination AddressIDXID="w9513"BOOK="_idx" COLLECTION="nw41" TIDREF="i1388"IP address to which the server sends discovery requests or, if routing is enabled, the IP address to which the router sends discovery responses. The only valid values are the router discovery multicast address and 255.255.255.255.Default: (Router Discovery Multicast)Utility: Load INETCFG (CLASS=MENUITEM MOREINFO="NONE"Internetworking Configuration menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"Bindings > Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP Bind Options (CLASS=MENUITEM MOREINFO="NONE"Expert TCP/IP LAN Options menu appears) > Select CLASS=MENUITEM MOREINFO="NONE"Router Discovery OptionsRENDERAS="SECT1"ID="FM30695"Configuring TCP/IP Filtering ParametersIDXID="w9514"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"IDXID="w9515"BOOK="_idx" COLLECTION="nw41" TIDREF="i4450"IDXID="w9516"BOOK="_idx" COLLECTION="nw41" TIDREF="i1501"
The Filter Configuration utility (FILTCFG) allows you to configure parameters for the following categories of filtering:MARK=BULLETIDREF="FM10021""Outgoing RIP Filters"IDREF="FM29041""Incoming RIP Filters"IDREF="FM40344""Outgoing EGP Filters"PAGENUM=107 ID="BP111"IDREF="FM16718""Incoming EGP Filters"IDREF="FM27065""OSPF External Route Filters"IDREF="FM12188""Packet Forwarding Filters"Select one of these menu items from the main filtering menu. The associated parameters are described in this section.RENDERAS="SECT2"ID="FM10021"Outgoing RIP FiltersIDXID="w9517"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"IDXID="w9518"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
Use to configure an outgoing route RIP filter that filters out advertisement of IDXID="w9519"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"
routing information for a specified network or host to a specified destination. To configure a filter, enter the values for IP Address, Subnetwork Mask, Destination, and Advertised Hop Count.Default: DisabledUtility: Load FILTCFG (Protocol Filters menu appears)Parameter Path: Select TCP/IPRENDERAS="SECT3"StatusAllows you to enable or disable outgoing RIP filters. Changes you make to this field take place immediately.Default: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP FiltersRENDERAS="SECT3"ActionOnce you have enabled the CLASS=MENUITEM MOREINFO="NONE"Status parameter, you can either permit routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list or deny routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list, thereby, permitting routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Use the CLASS=MENUITEM MOREINFO="NONE"Action parameter to specify the action taken when a route matches a filter in the CLASS=MENUITEM MOREINFO="NONE"Filter list. Changes you make to this field take place immediately.PAGENUM=108 ID="BP112"The action you specify in the CLASS=MENUITEM MOREINFO="NONE"Filter list is the opposite of the action you specify in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Default: Deny Routes in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP FiltersRENDERAS="SECT3"FiltersThis window displays the configured TCP/IP outgoing or route advertisement RIP filters. You can add, delete, or modify filters in the list. After you save the changes, TCP/IP updates the new configuration dynamically.The action taken on routes matching filters in this list is described in the CLASS=MENUITEM MOREINFO="NONE"Action field. TCP/IP always examines the CLASS=MENUITEM MOREINFO="NONE"Exception list before the CLASS=MENUITEM MOREINFO="NONE"Filter list. If a route matches a filter in both lists, the CLASS=MENUITEM MOREINFO="NONE"Exception list is always used. Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP FiltersRENDERAS="SECT4"Routes Denied or PermittedThis screen displays a list of routes and where these routes might or might not be sent. This field is populated by the information you define in the next window, called CLASS=MENUITEM MOREINFO="NONE"Define Filter. You can access this screen by pressing insert from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"FiltersPAGENUM=108 ID="BP113"PAGENUM=109From this window, you can access the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the route or network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. There are three options: CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example,130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Valid input in this field is a four-byte mask in dotted hexadecimal or decimal format. User input is converted and displayed in hexadecimal. Trailing zeros are appended, if necessary. For example, 255.255.252 becomes 255.255.252.0. The mask must also cover the natural mask bits of the specified IP Address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=110 ID="BP114"CLASS=MENUITEM MOREINFO="NONE"Destination TypeSpecify whether the CLASS=MENUITEM MOREINFO="NONE"Destination field is an interface or a network. Press MOREINFO="NONE"<Enter> to select from the list.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"DestinationSpecify which routers will receive this route advertisement. The CLASS=MENUITEM MOREINFO="NONE"Action parameter determines if this route is advertised or blocked. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the route will not be advertised to the destination router. If you set the action to CLASS=MENUITEM MOREINFO="NONE"Permit, the route will be advertised to the destination router.If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a destination location from the list of network interfaces. This parameter displays the network interfaces that you loaded in INETCFG.If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Network, press MOREINFO="NONE"<Enter> and type the network CLASS=MENUITEM MOREINFO="NONE"IP Address and CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask for the TCP/IP network.Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"Advertised Hop CountThis field is only available when you define the CLASS=MENUITEM MOREINFO="NONE"Action parameter to permit, or advertise, routes. Specify the hop count or cost advertised with the route. If the hop count value is unspecified, it is determined based on information in the TCP/IP routing table.Valid range: 1-16. A value of 16 disables the route.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=111 ID="BP115"CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>RENDERAS="SECT3"ExceptionsThis window displays exceptions to the configured TCP/IP outgoing or route advertisement RIP filters. You can add, delete, or modify the exception filters in the list. After you save the changes, TCP/IP dynamically adjusts to the new configuration. The action taken on routes matching filters in this list is the opposite of the action specified in the CLASS=MENUITEM MOREINFO="NONE"Action field. For example, if you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to permit routes, the routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list are denied.TCP/IP always examines the CLASS=MENUITEM MOREINFO="NONE"Exception list before the CLASS=MENUITEM MOREINFO="NONE"Filter list. If a route matches a filter in both lists, the behavior specified by the CLASS=MENUITEM MOREINFO="NONE"Exception list is followed.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Outgoing RIP FiltersRENDERAS="SECT4"Exceptions: Routes Always Denied or PermittedA list of routes and where these routes might or might not be sent. This field is populated by the information you define in the next window, called CLASS=MENUITEM MOREINFO="NONE"Define Exception. You can access this window by pressing MOREINFO="NONE"<Ins> from CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes Always Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" ExceptionsPAGENUM=111 ID="BP116"PAGENUM=112From this menu, you can access the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the route or network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. There are three options: CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example, 130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Valid input is this field is a four-byte mask in dotted hexadecimal or decimal format. User input is converted and displayed in hexadecimal. Trailing zeros are appended, if necessary. For example, 255.255.252 becomes 255.255.252.0. The mask must also cover the natural mask bits of the specified IP address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)PAGENUM=113 ID="BP117"Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"Destination TypeSpecify whether the CLASS=MENUITEM MOREINFO="NONE"Destination field is an interface or a network. Press MOREINFO="NONE"<Enter> to select from the list.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"DestinationSpecify which routers will receive this route advertisement. The CLASS=MENUITEM MOREINFO="NONE"Action parameter determines if this route is advertised or blocked. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the route will not be advertised to the destination router. If you set the action to CLASS=MENUITEM MOREINFO="NONE"Permit, the route will be advertised to the destination router.If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a destination location from the list of network interfaces. This parameter displays the network interfaces that you loaded in INETCFG. If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Network, press MOREINFO="NONE"<Enter> and type the network CLASS=MENUITEM MOREINFO="NONE"IP Address and CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask for the TCP/IP network.Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=113 ID="BP118"PAGENUM=114CLASS=MENUITEM MOREINFO="NONE"Advertised Hop CountThis field is only available when you define the CLASS=MENUITEM MOREINFO="NONE"Action parameter to deny routes, thereby permitting routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Specify the hop count or cost advertised with the route. If the hop count value is unspecified, it is determined based on information in the TCP/IP routing table.Valid range: 1-16. A value of 16 disables the route.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>RENDERAS="SECT2"ID="FM29041"Incoming RIP FiltersIDXID="w9520"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9521"BOOK="_idx" COLLECTION="nw41" TIDREF="i3902"IDXID="w9522"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
Incoming RIP filters restrict the acceptance of routing information from the adjacent routers. Configure an incoming or route acceptance RIP filter to filter out routing information for a specified route received from a specified source.Default: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP PAGENUM=115 ID="BP119"RENDERAS="SECT3"StatusAllows you to enable or disable incoming RIP filters. Changes you make to this field take place immediately.Default: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP FiltersRENDERAS="SECT3"ActionOnce you have enabled the CLASS=MENUITEM MOREINFO="NONE"Status parameter, you can either permit routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list or deny routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list, thereby, permitting routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Use the CLASS=MENUITEM MOREINFO="NONE"Action parameter to specify the action taken when a route matches a filter in the CLASS=MENUITEM MOREINFO="NONE"Filter list. Changes you make to this field take place immediately.The action you specify in the CLASS=MENUITEM MOREINFO="NONE"Filter list is the opposite of the action you specify in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Default: Deny Routes in CLASS=MENUITEM MOREINFO="NONE"Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP FiltersRENDERAS="SECT3"FiltersThis window displays the configured TCP/IP incoming or route acceptance RIP filters.You can add, delete, or modify filters in the list. After you save the changes, TCP/IP adjusts to the new configuration dynamically. The action taken on routes matching filters in this list is described in the CLASS=MENUITEM MOREINFO="NONE"Action field.TCP/IP always examines the CLASS=MENUITEM MOREINFO="NONE"Exception list before the CLASS=MENUITEM MOREINFO="NONE"Filter list. If a route matches a filter in both lists, the behavior specified by the CLASS=MENUITEM MOREINFO="NONE"Exception list is always followed.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP FiltersPAGENUM=116 ID="BP120"RENDERAS="SECT4"Routes Permitted or DeniedThis window displays a list of routes and where these routes might or might not be received. This field is populated by the information you define in the next window, called CLASS=MENUITEM MOREINFO="NONE"Define Filter. You can access this window by pressing MOREINFO="NONE"<Ins> from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" FiltersFrom this menu, you can access the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the route or network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. There are three options: CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example, 130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the PAGENUM=117 ID="BP121"CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"Source TypeSpecify the source type used to define the router that originates the accepted or blocked route. Press MOREINFO="NONE"<Enter> to select from the list. The available types are CLASS=MENUITEM MOREINFO="NONE"Interface and CLASS=MENUITEM MOREINFO="NONE"Network.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"SourceSpecify the router that originates the route advertisement. Depending on how you configured the CLASS=MENUITEM MOREINFO="NONE"Action parameter, the filtered route is either accepted or blocked from the specified source. The CLASS=MENUITEM MOREINFO="NONE"Action parameter determines if a route is accepted or blocked. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the route will not be accepted from the source router. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Permit, the route will be accepted from the source router.If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a source location from the list of network interfaces.If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Network, press MOREINFO="NONE"<Enter> and type the network IP addresCLASS=MENUITEM MOREINFO="NONE"s and subnetwork mask for the TCP/IP network.Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>PAGENUM=118 ID="BP122"CLASS=MENUITEM MOREINFO="NONE"Advertised Hop CountThis field is not available in incoming RIP filters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" Filters > (CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>RENDERAS="SECT3"ExceptionsThis window displays exceptions to the configured incoming, or route acceptance, RIP filters. You can add, delete, or modify the CLASS=MENUITEM MOREINFO="NONE"Exception filters in the list. After you save the changes, TCP/IP adjusts to the new configuration dynamically. The action taken on routes matching filters in this list is always the opposite of the action specified in the CLASS=MENUITEM MOREINFO="NONE"Action field. For example, if you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to permit routes, the routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list are denied.TCP/IP always examines the CLASS=MENUITEM MOREINFO="NONE"Exception list before the CLASS=MENUITEM MOREINFO="NONE"Filter list. If a route matches a filter in both lists, the behavior specified by the CLASS=MENUITEM MOREINFO="NONE"Exception list is always followed.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP FiltersPAGENUM=118 ID="BP123"CLASS=MENUITEM MOREINFO="NONE"PAGENUM=119RENDERAS="SECT4"Exceptions: Routes Always Denied or PermittedThis window displays a list of routes and where these routes might or might not be received.This field is populated by the information you define in the next window, called CLASS=MENUITEM MOREINFO="NONE"Define Exception. You can access this window by pressing MOREINFO="NONE"<Ins> from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"ExceptionsFrom this menu, you can access the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the route or network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. There are three options: CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes Always Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example, 130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=119 ID="BP124"PAGENUM=120CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes Always Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"Source TypeSpecify the source type used to define the router that originates the accepted or blocked route. Press MOREINFO="NONE"<Enter> to select from the list. The available types are CLASS=MENUITEM MOREINFO="NONE"Interface and CLASS=MENUITEM MOREINFO="NONE"Network.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes Always Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"SourceSpecify the router that originates the route advertisement. Depending on how you configured the CLASS=MENUITEM MOREINFO="NONE"Action parameter, the filtered route is either accepted or blocked from the specified source. The CLASS=MENUITEM MOREINFO="NONE"Action parameter determines if a route is accepted or blocked. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the route will not be accepted from the source router. If you set the Action parameter to CLASS=MENUITEM MOREINFO="NONE"Permit, the route will be accepted from the source router.If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a source location from the list of network interfaces.If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Network, press MOREINFO="NONE"<Enter> and type the network IP addresCLASS=MENUITEM MOREINFO="NONE"s and subnetwork mask for the TCP/IP network.PAGENUM=121 ID="BP125"Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes Always Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"Advertised Hop CountThis field is not available in incoming RIP filters.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes Always Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming RIP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes Always Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>RENDERAS="SECT2"ID="FM40344"Outgoing EGP FiltersIDXID="w9523"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"IDXID="w9524"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"IDXID="w9525"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
Outgoing EGP filters specify which routes learned from RIP, OSPF, or static routes can be propagated to EGP peers. Use to configure an outgoing EGP filter to filter routing information advertised to EGP peers. Default: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP PAGENUM=122 ID="BP126"RENDERAS="SECT3"StatusAllows you to enable or disable the selected outgoing EGP filter. Changes you make to this field take place immediately.Default: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP FiltersRENDERAS="SECT3"ActionOnce you have enabled the CLASS=MENUITEM MOREINFO="NONE"Status parameter, you can either permit routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list or deny routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list; thereby, permitting routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Use the CLASS=MENUITEM MOREINFO="NONE"Action parameter to specify the action taken when a route matches a filter in the CLASS=MENUITEM MOREINFO="NONE"Filter list. Changes you make to this field take place immediately.The action you specify in the CLASS=MENUITEM MOREINFO="NONE"Filter list is the opposite of the action you specify in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Default: Deny Routes in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP FiltersRENDERAS="SECT3"FiltersThis window displays the configured TCP/IP outgoing EGP filters. You can add, delete, or modify filters in the list. After saving the changes you made, TCP/IP adjusts to the new configuration dynamically.The action taken on routes matching filters in this list is described in the CLASS=MENUITEM MOREINFO="NONE"Action field. TCP/IP always examines the CLASS=MENUITEM MOREINFO="NONE"Exception list before the CLASS=MENUITEM MOREINFO="NONE"Filter list. If a route matches a filter in both lists, the behavior specified by the CLASS=MENUITEM MOREINFO="NONE"Exception list is followed.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP FiltersPAGENUM=123 ID="BP127"RENDERAS="SECT4"Routes Denied or PermittedThis window displays a list of routes and where these routes might or might not be sent. This field is populated by the information you define in the next window, called CLASS=MENUITEM MOREINFO="NONE"Define Filter. You can access this window by pressing MOREINFO="NONE"<Ins> from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"FiltersMARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. For an EGP filter, CLASS=MENUITEM MOREINFO="NONE"Network is the only valid selection for this field. There are two options: CLASS=MENUITEM MOREINFO="NONE"All Routes and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example, 130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)PAGENUM=123 ID="BP128"PAGENUM=124CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"Destination TypeSpecify the type of the CLASS=MENUITEM MOREINFO="NONE"Destination field. The available types are CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Autonomous System. Press MOREINFO="NONE"<Enter> to select from the list.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"DestinationSpecify which routers will receive this route advertisement. The CLASS=MENUITEM MOREINFO="NONE"Action parameter determines if this route is advertised or blocked. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the route will not be advertised to the destination router. If you set the action to CLASS=MENUITEM MOREINFO="NONE"Permit, the route will be advertised to the destination router.If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a destination from the list of network interfaces that you loaded in INETCFG.If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host, press MOREINFO="NONE"<Enter> and type the network address and subnetwork mask for the TCP/IP network.PAGENUM=125 ID="BP129"If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Autonomous System, press MOREINFO="NONE"<Enter> and enter the autonomous system number. Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"Metric ValueThis field is only active when you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to permit routes. Specify the metric or cost advertised with the route. If the metric value is unspecified, it is determined based on information in the TCP/IP routing table.Range: 0-255Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: EmptyUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)PAGENUM=125 ID="BP130"PAGENUM=126RENDERAS="SECT3"ExceptionsThis window displays exceptions to the configured TCP/IP outgoing EGP filters. You can add, delete, or modify the exception filters in the list. After you save the changes, TCP/IP adjusts the new configuration dynamically. The action taken on routes matching the filters in this list is always the opposite of the one specified in the CLASS=MENUITEM MOREINFO="NONE"Action field. For example, if you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to permit routes, the routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list are denied.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP FiltersRENDERAS="SECT4"Exceptions: Routes Always Denied or PermittedThis window displays a list of routes and where these routes might or might not be sent. This field is populated by the information you define in the next screen, calledCLASS=MENUITEM MOREINFO="NONE" Define Exception. You can access this window by pressing MOREINFO="NONE"<Ins> from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"ExceptionsFrom this menu, you can access the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the route or network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. There are two options: CLASS=MENUITEM MOREINFO="NONE"All Routes and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)PAGENUM=126 ID="BP131"PAGENUM=127CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example, 130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"Destination TypeSpecify the type of the CLASS=MENUITEM MOREINFO="NONE"Destination field. The available types are CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Autonomous System. Press MOREINFO="NONE"<Enter> to select from the list.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)PAGENUM=127 ID="BP132"PAGENUM=128CLASS=MENUITEM MOREINFO="NONE"DestinationSpecify which routers will receive this route advertisement. The CLASS=MENUITEM MOREINFO="NONE"Action parameter determines if this route is advertised or blocked. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the route will not be advertised to the destination router. If you set the action to CLASS=MENUITEM MOREINFO="NONE"Permit, the route will be advertised to the destination router.If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a destination from the list of network interfaces that you loaded in INETCFG. If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host, press MOREINFO="NONE"<Enter> and type the network address and subnetwork mask for the TCP/IP network.If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Autonomous System, press MOREINFO="NONE"<Enter> and enter the autonomous system number. Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"Metric ValueThis field is active only when the CLASS=MENUITEM MOREINFO="NONE"Action field is configured to deny routes, thereby permitting routes in the CLASS=MENUITEM MOREINFO="NONE"Exception field. Specify the metric or cost advertised with the route. If the metric value is unspecified, it is determined based on information in the TCP/IP routing table.Range: 0-255Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)PAGENUM=128 ID="BP133"PAGENUM=129CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: EmptyUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Outgoing EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)RENDERAS="SECT2"ID="FM16718"Incoming EGP FiltersIDXID="w9526"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"IDXID="w9527"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"IDXID="w9528"BOOK="_idx" COLLECTION="nw41" TIDREF="i1404"
Incoming EGP Filters specify which routes, learned from EGP, will be added to the router's routing table. Use to configure an incoming EGP filter to filter routing information received from EGP peers.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT3"StatusAllows you to enable or disable incoming EGP filters. Changes you make to this field take place immediately.Default: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP FiltersPAGENUM=129 ID="BP134"PAGENUM=130RENDERAS="SECT3"ActionOnce you have enabled the CLASS=MENUITEM MOREINFO="NONE"Status parameter, you can either permit routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list or deny routes not in the CLASS=MENUITEM MOREINFO="NONE"Filter list, thereby, permitting routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Use the CLASS=MENUITEM MOREINFO="NONE"Action parameter to specify the action taken when a route matches a filter in the CLASS=MENUITEM MOREINFO="NONE"Filter list. Changes you make to this field take place immediately.The action you specify in the CLASS=MENUITEM MOREINFO="NONE"Filter list is the opposite of the action you specify in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Default: Deny Routes in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP FiltersRENDERAS="SECT3"FiltersThis window displays the configured incoming EGP filters. You can add, delete, or modify filters in the list. After you save the changes, TCP/IP updates the new configuration dynamically.The action taken on routes matching filters in this list is described in the CLASS=MENUITEM MOREINFO="NONE"Action field. TCP/IP always examines the CLASS=MENUITEM MOREINFO="NONE"Exception list before the CLASS=MENUITEM MOREINFO="NONE"Filter list. If a route matches a filter in both lists, the CLASS=MENUITEM MOREINFO="NONE"Exception list is used.Default: Empty listUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP FiltersRENDERAS="SECT4"Routes Permitted or DeniedThis window displays a list of routes and where these routes might or might not be received. This field is populated by the information you define in the next window, called CLASS=MENUITEM MOREINFO="NONE"Define Filters. You can access this window by pressing MOREINFO="NONE"<Ins> from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" FiltersPAGENUM=131 ID="BP135"From this menu, you can access the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. For an EGP filter, CLASS=MENUITEM MOREINFO="NONE"Network is the only valid selection for this field. There are two options: CLASS=MENUITEM MOREINFO="NONE"All Routes and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example, 130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)PAGENUM=132 ID="BP136"CLASS=MENUITEM MOREINFO="NONE"Source TypeSpecify the source type used to define the router that originates the accepted or blocked route. Press MOREINFO="NONE"<Enter> to select from the list. The available types are CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Autonomous System.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"SourceSpecify the router that originates the route advertisement. Depending on how you configured the CLASS=MENUITEM MOREINFO="NONE"Action parameter, the filtered route is either accepted or blocked from the specified source. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the route will not be accepted from the source router. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Permit, the route will be accepted from the source router.If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a source location from the list of network interfaces.If yourCLASS=MENUITEM MOREINFO="NONE" Source Type is CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host, press MOREINFO="NONE"<Enter> and type the network address and subnetwork mask for the TCP/IP network. If your CLASS=MENUITEM MOREINFO="NONE"Source Type is Autonomous System, press MOREINFO="NONE"<Enter> and enter the autonomous system number.Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"Metric ValueThis field is not active in incoming EGP filters.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)PAGENUM=133 ID="BP137"Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: EmptyUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)RENDERAS="SECT3"ExceptionsThis window displays exceptions to the configured TCP/IP incoming EGP filters. You can add, delete, or modify the exception filters in the list. After you save the changes, TCP/IP updates to the new configuration dynamically. The action taken on routes matching filters in this list is the opposite of the one specified in the CLASS=MENUITEM MOREINFO="NONE"Action field. For example, if you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to permit routes, the routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list are denied.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP FiltersRENDERAS="SECT4"Exceptions: Routes Always Denied or PermittedThis window displays a list of routes and where these routes might or might not be received. This field is populated by the information you define in the next window, called CLASS=MENUITEM MOREINFO="NONE"Define Exception. You can access this window by pressing MOREINFO="NONE"<Ins> from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > SelectCLASS=MENUITEM MOREINFO="NONE" ExceptionsPAGENUM=134 ID="BP138"From this menu, you can access the following parameters:MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the route to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. For EGP, CLASS=MENUITEM MOREINFO="NONE"Network is the only valid selection for this field. There are two options: CLASS=MENUITEM MOREINFO="NONE"All Routes and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example, 130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)PAGENUM=135 ID="BP139"CLASS=MENUITEM MOREINFO="NONE"Source TypeSpecify the source type used to define the router that originates the accepted or blocked route. Press MOREINFO="NONE"<Enter> to select from the list. The available types are CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Autonomous System.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"SourceSpecify the router that originates the route advertisement. Depending on how you configured the CLASS=MENUITEM MOREINFO="NONE"Action parameter, the filtered route is either accepted or blocked from the specified source. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the route will not be accepted from the source router. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Permit, the route will be accepted from the source router.If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a source location from the list of network interfaces.If yourCLASS=MENUITEM MOREINFO="NONE" Source Type is CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host, press MOREINFO="NONE"<Enter> and type the network address and subnetwork mask for the TCP/IP network. If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Autonomous System, press MOREINFO="NONE"<Enter> and enter the autonomous system number.Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"Metric ValueThis field is not active in incoming EGP filters.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)PAGENUM=136 ID="BP140"Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Incoming EGP Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: CLASS=MENUITEM MOREINFO="NONE"Routes Always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)RENDERAS="SECT2"ID="FM27065"OSPF External Route FiltersIDXID="w9529"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"IDXID="w9530"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"IDXID="w9531"BOOK="_idx" COLLECTION="nw41" TIDREF="i3087"
Configure an OSPF External Route filter to filter out route information that is learned from RIP and EGP and propagated to or blocked from the OSPF domain. These filters determine which networks and hosts in the non-OSPF domains can be seen in the OSPF domain.To configure a filter, enter the values for CLASS=MENUITEM MOREINFO="NONE"IP Address, Subnetwork Mask, and CLASS=MENUITEM MOREINFO="NONE"Metric Value parameters.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT3"StatusAllows you to enable or disable OSPF external route filters. Changes you make to this field take place immediately.Default: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route FiltersPAGENUM=137 ID="BP141"RENDERAS="SECT3"ActionOnce you have enabled the CLASS=MENUITEM MOREINFO="NONE"Status parameter, you can either permit routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list or deny routes in the CLASS=MENUITEM MOREINFO="NONE"Filter list, thereby, permitting routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Use the CLASS=MENUITEM MOREINFO="NONE"Action parameter to specify the action taken when a route matches a filter in the CLASS=MENUITEM MOREINFO="NONE"Filter list. Changes you make to this field take place immediately.The action you specify in the CLASS=MENUITEM MOREINFO="NONE"Filter list is the opposite of the action you specify in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Default: Deny Routes in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route FiltersRENDERAS="SECT3"FiltersThis window displays the configured TCP/IP OSPF external route filters. You can add, delete, or modify filters in this list. After you save the changes, TCP/IP adjusts to the new configuration dynamically. OSPF external route filters define the route that is propagated into the OSPF domain.The action taken on routes matching filters on this list is described in the CLASS=MENUITEM MOREINFO="NONE"Action field. TCP/IP examines the CLASS=MENUITEM MOREINFO="NONE"Exception list before theCLASS=MENUITEM MOREINFO="NONE" Filter list. If a route matches a filter in both lists, the CLASS=MENUITEM MOREINFO="NONE"Exception list is followed.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route FiltersRENDERAS="SECT4"Routes Denied or PermittedThis window displays a list of routes and where these routes might or might not be sent. This field is populated by the information you define in the next window, called CLASS=MENUITEM MOREINFO="NONE"Define Filter. You can access this window by pressingMOREINFO="NONE" <Ins> from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)PAGENUM=138 ID="BP142"Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > SelectCLASS=MENUITEM MOREINFO="NONE" FiltersMARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecify the route or network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. There are three options: CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"IP Address of Network/HostValid input in this field is a four-byte IP address in dotted decimal notation, for example,130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted to 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters > (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> > (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)PAGENUM=138 ID="BP143"PAGENUM=139CLASS=MENUITEM MOREINFO="NONE"Metric ValueThis field is only active when you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to permit routes. Specify the metric or cost advertised with the route. If the metric value is unspecified, it is determined based on information in the TCP/IP routing table.Range: 0-255Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Routes Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Filter menu appears)RENDERAS="SECT3"ExceptionsThis window displays the configured TCP/IP OSPF External Route filters. You can add, delete, or modify filters in the list. After you save the changes, TCP/IP updates to the new configuration dynamically. The action taken on routes matching the filters in this list is the opposite of the action specified in the CLASS=MENUITEM MOREINFO="NONE"Action field. For example, if you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to permit routes, the routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list are denied.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route FiltersPAGENUM=140 ID="BP144"RENDERAS="SECT4"Exceptions: Routes Always Denied or PermittedThis window displays a list of routes and where these routes might or might not be sent. This field is populated by the information you define in the next screen, called CLASS=MENUITEM MOREINFO="NONE"Define Exception. You can access this window by pressing MOREINFO="NONE"<Ins> from CLASS=MENUITEM MOREINFO="NONE"Routes Denied or Permitted.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Route to Network or HostSpecifies the route or network to be filtered. Press MOREINFO="NONE"<Enter> to select from the list. There are three options: CLASS=MENUITEM MOREINFO="NONE"All Routes, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Network.Default: All RoutesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or HostValid input in this field is a four-byte IP address in dotted decimal notation, for example,130.57.172.0. Trailing zeros are appended, if necessary. For example, 130.57 is converted and displayed as 130.57.0.0.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"Subnetwork MaskThis field is only available when you configure CLASS=MENUITEM MOREINFO="NONE"Route to Network or Host as CLASS=MENUITEM MOREINFO="NONE"Network. The value you assigned the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field causes the software to assign a value in the CLASS=MENUITEM MOREINFO="NONE"Subnetwork Mask field automatically. You can edit this value; however, it must be compatible with the value of the CLASS=MENUITEM MOREINFO="NONE"IP Address of Network or Host field and the combined result must be a valid IP address.PAGENUM=141 ID="BP145"Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"Metric ValueThis field is only active when you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to deny routes, thereby permitting routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Specify the metric or cost advertised with the route. If the metric value is unspecified, it is determined based on information in the TCP/IP routing table.Range: 0-255Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"OSPF External Route Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (CLASS=MENUITEM MOREINFO="NONE"Exceptions: Routes always Permitted or Denied menu appears) > PressMOREINFO="NONE" <Ins> (CLASS=MENUITEM MOREINFO="NONE"Define Exception menu appears)PAGENUM=141 ID="BP146"PAGENUM=142RENDERAS="SECT2"ID="FM12188"Packet Forwarding FiltersIDXID="w9532"BOOK="_idx" COLLECTION="nw41" TIDREF="i3176"IDXID="w9533"BOOK="_idx" COLLECTION="nw41" TIDREF="i3214"
Use to configure packet forwarding filters, which limit access to specific services, by filtering out the corresponding user data packets that pass through the router. You can configure exceptions to the filters to allow a subset of the packets to bypass the filters.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IPRENDERAS="SECT3"StatusAllows you to enable or disable the selected packet forwarding filters. Changes you make to this field take place immediately.Default: DisabledUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Packet Forwarding FiltersRENDERAS="SECT3"ActionOnce you have enabled the CLASS=MENUITEM MOREINFO="NONE"Status parameter, you can either permit packets in the CLASS=MENUITEM MOREINFO="NONE"Filter list or deny packets in the CLASS=MENUITEM MOREINFO="NONE"Filter list, thereby, permitting packets in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Use the CLASS=MENUITEM MOREINFO="NONE"Action parameter to specify the action taken when a packet matches a filter in the CLASS=MENUITEM MOREINFO="NONE"Filter list. Changes you make to this field take place immediately.The action you specify in the CLASS=MENUITEM MOREINFO="NONE"Filter list is the opposite of the action you specify in the CLASS=MENUITEM MOREINFO="NONE"Exception list. Default: Deny Packets in Filter ListUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Packet Forwarding FiltersPAGENUM=143 ID="BP147"RENDERAS="SECT3"FiltersThis window displays all configured packet forwarding filters. You can add, delete, or modify packet forwarding filters. Any changes made to the CLASS=MENUITEM MOREINFO="NONE"Filter list are not saved and made active until you exit the CLASS=MENUITEM MOREINFO="NONE"Filter list window and save the changes. You can block or forward data packets, depending on how you have set the CLASS=MENUITEM MOREINFO="NONE"Action parameter. Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Packet Forwarding FiltersRENDERAS="SECT4"Packets Denied or PermittedThis window displays a list of packets and where these packets might or might not be sent. Each filter specifies the CLASS=MENUITEM MOREINFO="NONE"Source, CLASS=MENUITEM MOREINFO="NONE"Packet Type, and the CLASS=MENUITEM MOREINFO="NONE"Destination of the data packet.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Packet Forwarding Filters > SelectCLASS=MENUITEM MOREINFO="NONE" FiltersMARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Source TypeSpecify the source type used to define the node that originates the forwarded or blocked packet. The available source types include CLASS=MENUITEM MOREINFO="NONE"Network, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Interface. Press MOREINFO="NONE"<Enter> to select from the list.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > SelectCLASS=MENUITEM MOREINFO="NONE" Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Packets Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"SourceSpecify the originating node of the packet. Depending on how you configured the CLASS=MENUITEM MOREINFO="NONE"Action parameter, the filtered packet is either forwarded or blocked from the specified source.PAGENUM=143 ID="BP148"PAGENUM=144The CLASS=MENUITEM MOREINFO="NONE"Action parameter determines if a packet is forwarded or blocked. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the packet will not be forwarded. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Permit, the packet will be forwarded.If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a location source from the list of network interfaces. If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host, press MOREINFO="NONE"<Enter> and type in the address and subnetwork mask.Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters> Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Packets Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>CLASS=MENUITEM MOREINFO="NONE"NameDefine the packet type to be filtered. Press MOREINFO="NONE"<Enter> to view a list of defined TCP/IP packet types. You can select a predefined entry; however, predefined packet types cannot be modified or deleted. You can add, delete, or modify a packet type that is not predefined.Default: <ANY>Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP >  Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > SelectCLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Packets Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"ProtocolThis is a read-only field. The software automatically displays the protocol of the packet type you selected in the CLASS=MENUITEM MOREINFO="NONE"Packet Type field.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > SelectCLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Packets Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=144 ID="BP149"PAGENUM=145CLASS=MENUITEM MOREINFO="NONE"PortsDefine a single TCP/IP port or a range of ports separated by a hyphen (-) for the TCP or UDP protocols.Valid port numbers range from 1 to 65535. If you do not define this parameter, it defaults to <All>.The following is sample port input: 46, 2-10, All, <All>.Range: 1-65535Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP> Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > SelectCLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Packets Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"Destination TypeSelect the destination address type. The available destination types include CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, and CLASS=MENUITEM MOREINFO="NONE"Host.Default: InterfaceUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Packets Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"DestinationIf your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a destination from the list of network interfaces that you loaded in INETCFG. If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host, press MOREINFO="NONE"<Enter> and type in the address and subnetwork mask.Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP> Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > SelectCLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Packets Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=145 ID="BP150"PAGENUM=146CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP> Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > SelectCLASS=MENUITEM MOREINFO="NONE"Filters (CLASS=MENUITEM MOREINFO="NONE"Packets Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>RENDERAS="SECT3"ExceptionsThis window displays the exceptions to the filters defined in the CLASS=MENUITEM MOREINFO="NONE"Filter list. The protocol stack checks the exception filters and follows the action defined for matching packets in the CLASS=MENUITEM MOREINFO="NONE"Exception list. If a packet does not match the exception filters, it is checked against the CLASS=MENUITEM MOREINFO="NONE"Filter list. Then the packet is filtered if it matches any filter. You can add, delete, or modify packet forwarding filters. Changes are activated when you exit the CLASS=MENUITEM MOREINFO="NONE"Filter list window and save the changes. The action taken on routes matching the filters in this list is the opposite of the action specified in the CLASS=MENUITEM MOREINFO="NONE"Action field. For example, if you configure the CLASS=MENUITEM MOREINFO="NONE"Action field to permit routes, the routes in the CLASS=MENUITEM MOREINFO="NONE"Exception list are denied.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding FiltersRENDERAS="SECT4"Exceptions: Packets Always Denied or PermittedThis window displays a list of packets and where these packets might or might not be sent. Each filter specifies the CLASS=MENUITEM MOREINFO="NONE"Source, the CLASS=MENUITEM MOREINFO="NONE"Packet Type, and the CLASS=MENUITEM MOREINFO="NONE"Destination of the data packet.Utility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"ExceptionsPAGENUM=147 ID="BP151"MARK=BULLETCLASS=MENUITEM MOREINFO="NONE"Source TypeSpecify the source type used to define the node that originates the forwarded or blocked packet. The available source types include CLASS=MENUITEM MOREINFO="NONE"Network, CLASS=MENUITEM MOREINFO="NONE"Host, and CLASS=MENUITEM MOREINFO="NONE"Interface. Press MOREINFO="NONE"<Enter> to select from the list.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (Exceptions: CLASS=MENUITEM MOREINFO="NONE"Packets Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"SourceSpecify the originating node of the packet. Depending on how you configured the CLASS=MENUITEM MOREINFO="NONE"Action parameter, the filtered packet is either forwarded or blocked from the specified source. The CLASS=MENUITEM MOREINFO="NONE"Action parameter determines if a packet is forwarded or blocked. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Deny, the packet will not be forwarded. If you set the CLASS=MENUITEM MOREINFO="NONE"Action parameter to CLASS=MENUITEM MOREINFO="NONE"Permit, the packet will be forwarded.If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a location source from the list of network interfaces. If your CLASS=MENUITEM MOREINFO="NONE"Source Type is CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host, press MOREINFO="NONE"<Enter> and type in the address and subnetwork mask.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (Exceptions: CLASS=MENUITEM MOREINFO="NONE"Packets Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"NameDefine the packet type to be filtered. Press MOREINFO="NONE"<Enter> to view a list of defined TCP/IP packet types. You can select an entry for the filter being edited. You can also add, delete, or modify a packet type. Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)PAGENUM=148 ID="BP152"Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (Exceptions: CLASS=MENUITEM MOREINFO="NONE"Packets Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"ProtocolThis is a read-only field. The software automatically displays the protocol of the packet type you selected in the CLASS=MENUITEM MOREINFO="NONE"Packet Type field.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (Exceptions: CLASS=MENUITEM MOREINFO="NONE"Packets Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"PortsDefine a single TCP/IP port or a range of ports separated by a hyphen (-) for the TCP or UDP protocols. If you do not define this parameter, it defaults to <All>.The following is sample input: 46, 2-10, All, <All> Range: 1-65535Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP  > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (Exceptions: CLASS=MENUITEM MOREINFO="NONE"Packets Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"Destination TypeSelect the destination address type. The available destination types include CLASS=MENUITEM MOREINFO="NONE"Interface, CLASS=MENUITEM MOREINFO="NONE"Network, and CLASS=MENUITEM MOREINFO="NONE"Host.Default: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (Exceptions: CLASS=MENUITEM MOREINFO="NONE"Packets Always Denied or Permitted menu appears) > PressMOREINFO="NONE" <Ins>PAGENUM=149 ID="BP153"CLASS=MENUITEM MOREINFO="NONE"DestinationUse this parameter to define the destination of the packet. If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Interface, press MOREINFO="NONE"<Enter> and select a destination from the list of network interfaces that you loaded in INETCFG. If your CLASS=MENUITEM MOREINFO="NONE"Destination Type is CLASS=MENUITEM MOREINFO="NONE"Network or CLASS=MENUITEM MOREINFO="NONE"Host, press MOREINFO="NONE"<Enter> and type in the address and subnetwork mask.Default: All InterfacesUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (Exceptions: CLASS=MENUITEM MOREINFO="NONE"Packets Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>CLASS=MENUITEM MOREINFO="NONE"CommentEnter a short description of the filter configured in this list. The CLASS=MENUITEM MOREINFO="NONE"Comment field can be used for future reference.Range: 0 to 49 charactersDefault: NoneUtility: Load FILTCFG (CLASS=MENUITEM MOREINFO="NONE"Protocol Filters menu appears)Parameter Path: Select CLASS=MENUITEM MOREINFO="NONE"TCP/IP  > Select CLASS=MENUITEM MOREINFO="NONE"Packet Forwarding Filters > Select CLASS=MENUITEM MOREINFO="NONE"Exceptions (Exceptions: CLASS=MENUITEM MOREINFO="NONE"Packets Always Denied or Permitted menu appears) > Press MOREINFO="NONE"<Ins>PAGENUM=151 ID="BP154"Glossaryaccess rateSee IDREF="FM38450"AR (access rate).ACK (acknowledgment)An ASCII or EBCDIC code indicating that a message has been received correctly.adapter A piece of hardware, typically an interface card, installed in a computer, that connects the computer to other hardware or devices.addressAn identifier assigned to networks, stations, and other devices so that each device can be separately designed to receive and reply to messages.ID="FM39546"Address and Control Field compression A process of eliminating the CLASS=MENUITEM MOREINFO="NONE"All Stations Address and the CLASS=MENUITEM MOREINFO="NONE"Unnumbered Information fields from HDLC framing, on a per-data link basis, to reduce unneeded overhead when using low bandwidth links.Address Field A frame field comprising the control and management fields, specifying the virtual circuit numbering or Data Link Connection Identifier (DLCI); the flow control; and the frame discard eligibility (DE).ID="FM29747"address resolution cacheAn area of the software that contains entries that map the IP address to the physical address.ID="FM45325"adjacencyThe record that an NLSP router keeps about the state of its connection with a neighbor, and about the attributes of that neighbor. See also IDREF="FM18367"neighbor.administratorThe person who sets up a server, creates user login accounts and passwords, creates groups, sets security, and maintains the server. advertisingThe process by which devices on a network inform other devices on the network of their existence. NetWare software uses the Service Advertising Protocol (SAP) to do this.Annex D An implementation standard (ANSI T1.617) that addresses signaling and other network management functions.ANSI (American National Standards Institute)A nonprofit organization in the U.S. that defines standards in many industries. It is supported by over 1000 trade organizations, professional societies, and companies, and affiliated with the Consultative Committee for International Telegraphy and Telephony (CCITT) and the International Organization for Standardization (ISO).ID="FM38450"AR (access rate)The physical rate of access of the user channel in bits per second (bps). The offered load to the Frame Relay network is bounded by this parameter.AppleTalkThe Apple Computer suite of protocols that enables the hardware and software on an AppleTalk network to interact and to route data.AppleTalk NLM(APPLETLK.NLM) The AppleTalk protocol stack and router, which is included as a NetWare Loadable Module (NLM) file in the NetWare Communication Services software.AppleTalk moduleThe Novell IDXID="w9534"BOOK="_idx" COLLECTION="nw41" TIDREF="i212"
software that includes the basic AppleTalk Phase 2 protocols and an AppleTalk Phase 2 router. AppleTalk networkA collection of connected, individually controlled computers, printers, and other devices, together with the hardware and AppleTalk software used to link them.AppleTalk Phase 2 The latest version of the AppleTalk protocols. Apple introduced AppleTalk Phase 2 in 1989 to provide support for AppleTalk networks with thousands of nodes, for multiple AppleTalk zones on a network, for token ring, and cabling for more efficient routing techniques that improve performance in multiprotocol environments.AppleTalk stackThe suite of AppleTalk Phase 2 protocols in the AppleTalk module.Application layerThe seventh of seven layers of the Open Systems Interconnection (OSI) model; it provides network access to users.areaSee IDREF="FM90443"routing area.ID="FM40289"area addressThe area network number and mask that together define an NLSP routing area. See also IDREF="FM23208"area mask.area boundary routerA type of router that attaches an OSPF area to the backbone area. It has at least one interface in an area and one interface in the backbone area.ID="FM23208"area maskA 32-bit hexadecimal number that indicates how much of an area network number identifies a routing area, and how much identifies a network within the routing area. A typical area mask is FFFFFF00. See also IDREF="FM40289"area address.ID="FM40112"ARPAnetThe internetwork created by the Defense Advanced Research Projects Agency (DARPA) that later evolved into the Internet.ASCII (American Standard Code for Information Interchange)An 8-bit code for data transfer that was adopted by ANSI to ensure compatibility among data devices.asynchronous A data transmission method in which each character is synchronized individually, usually by means of start and stop elements. The gap between each character is not a fixed length.ATCON utilityA diagnostic tool for use at the server. ATCON provides information about the server's AppleTalk stack and router, and about other AppleTalk networks on the internetwork.authenticationA way of verifying that an object sending messages or requests is authorized to do so. See also IDREF="FM27999"PAP (Password Authentication Protocol) authentication; IDREF="FM28101"CHAP (Challenge Handshake Authentication Protocol) authentication.authentication databaseA list of valid remote system IDs and associated DTE addresses. Each entry represents a valid partner that can communicate with a given interface.automatic flow controlA means of controlling the flow of data across a virtual circuit. This is done by setting the window size and the packet size. Automatic flow control can be negotiated in each direction on a per-call basis.backbone networkThe primary connectivity mechanism of a hierarchical distributed system. It ensures that all systems that have connectivity to an intermediate system on the backbone have connectivity to one another.bandwidth The carrying capacity of a circuit, usually measured in bits per second (bps) for digital circuits, or hertz (Hz) for analog circuits.bandwidth-on-demand Having the capacity in an individual virtual circuit to burst above the committed information rate (CIR); also known as dynamic allocation of bandwidth.ID="FM15782"Bc (committed burst)The maximum number of data bits that a network agrees to transfer under typical conditions over a measured time interval.BCUGSee IDREF="FM19075"Bilateral Closed User Group (BCUG).ID="FM38994"Be (excess burst)The maximum number of uncommitted data bits that the network attempts to deliver over a measured time interval.BECN (Backward Explicit Congestion Notification)The notification that is set by the Frame Relay network to indicate that the network has experienced congestion in the reversed packet forwarding direction of the frame. ID="FM19075"Bilateral Closed User Group (BCUG)A facility that offers a finer degree of access control than the Closed User Group (CUG) offers. Bilateral signifies a CUG relationship that has been limited to a pair of DTEs. Access between the pair of DTEs is unrestricted. However, access to or from any other DTE is not possible.bit rateThe rate at which bits (binary digits) are transmitted over a communications line. Usually expressed in bits per second (bps).BOOTPA protocol used by a host to obtain IP addresses. bridgeA device that connects two or more physical networks, forwarding frames between networks based on information in the data-link header. Because a bridge operates at the Data-Link layer, it is transparent to the Network-layer protocols.ID="FM12042"broadcast (noun)A transmission method by which all hosts on a network receive a copy of any frame that is designated for broadcast. (Verb) The act of sending a message to all nodes. Contrast with IDREF="FM78289"multicast.broadcast (verb)The act of sending a message to all nodes.brouterA device that routes some protocols and bridges others.bus topologyThe linear LAN used by Ethernet networks.callA request by one network node to establish communications with another network node; also, the resulting communication session or the virtual circuit over which it is conducted.call authentication A method of protecting against unauthorized access into a system by inbound remote calls. See also IDREF="FM27999"PAP (Password Authentication Protocol) authentication; IDREF="FM28101"CHAP (Challenge Handshake Authentication Protocol) authentication. Call Request packetA type of control packet sent to a DTE to request initiation of a virtual call. CCITT (Consultative Committee for International Telegraphy and Telephony)The group within the International Telecommunications Union (ITU) that defines data communications standards.ID="FM28760"CEPT (European Conference of Postal and Telecommunications Administration)The governing body that created the facility used to transport 30 voice channels at 64 Kbps (for a total of 2.048 Mbps); also known as E1.Challenge Handshake Authentication Protocol (CHAP)See IDREF="FM28101"CHAP (Challenge Handshake Authentication Protocol) authentication. ID="FM28101"CHAP (Challenge Handshake Authentication Protocol) authentication An inbound call protection method that enables the receiving node to issue a challenge sequence that must be modified by the caller to use a secret known by both peer nodes. checksumThe numeric computation that combines the bits of a transmitted message; also, the resulting value. The value is transmitted with the message; the receiver recalculates the checksum and compares it to the received value to detect transmission errors. See also IDREF="FM10080"CRC (Cyclic Redundancy Check).ID="FM20010"CIR (Committed Information Rate)The committed rate of information, in bits per second, at which the network agrees to transfer data on a particular virtual circuit under typical operating conditions.circuitAny path that can carry an electrical current. In the context of NLSP, an internal logical representation of network connectivity between two NetWare Link Services Protocol (NLSP) routers.circuit switchingA procedure for establishing a connection between two end devices. Once connected, it uses a nonsharable path through the network.Clear Request packetA type of control packet sent to a DTE to request the termination of a virtual call.Clear to Send (CTS)A control signal generated by data communications equipment (DCE) to indicate that it can transmit data.clientA node or workstation on a network that requires services from a server.client/server modelA configuration that uses distributed intelligence to treat both the server and the individual workstations as intelligent, programmable devices.clockingA method of time synchronization of communication information.ID="FM31402"Closed User Group (CUG)A facility that allows the configuration of one or more virtual private networks within a larger public network. It allows a user to collect a number of DTEs into a single logical group, and restricts the ability of the group to receive incoming calls from or make outgoing calls to the restricted "open" portion of the network. The number of CUGs is network-dependent. A single DTE can belong to one or more CUGs.coaxialA type of cable that uses two conductors: a central, solid wire core surrounded by insulation and, surrounding that, a braided-wire conductor sheath. A coaxial cable is well-suited for networking because it can accommodate high bandwidth but is relatively resistant to interference.committed burst size (Bc)See IDREF="FM15782"Bc (committed burst). committed information rate (CIR) See IDREF="FM20010"CIR (Committed Information Rate). communications controllerA machine directly attached to a host computer that processes communications to a host. The communications controller is also known as a front-end processor.compressionThe method of compacting data for more efficient transmission. See also IDREF="FM39546"Address and Control Field compression; IDREF="FM39887"Protocol Field compression; IDREF="FM39150"data compression; IDREF="FM41202"header compression. congestionThe existence of excessive traffic on the network.ID="FM37606"configured routerA router configured explicitly on a network. (As opposed to a router that gets its configuration from a seed router.) Compare IDREF="FM41081"learning router. conformance options A set of options that provides access to expert parameters for specific control of the Packet-level and Frame-level operations. This includes changing the frame reject operation, setting the length of a clear confirmation packet, and managing unassigned LCNs.connectionSee IDREF="FM25644"on-demand connection; IDREF="FM40541"permanent connection. consoleThe monitor and keyboard from which the server or host activity can be viewed and controlled.ID="FM15129"control packet A link-control or network-control packet for establishing encapsulation format options, size limits of packets, link setup, peer authentication, or Network-layer protocol management.convergenceThe synchronization process that a network goes through immediately after a route change occurs on the network.convergence timeThe time required for routing information to propagate throughout the network.costA metric assigned to a circuit that determines the likelihood of traffic being routed over that circuit.ID="FM10080"CRC (Cyclic Redundancy Check)A sophisticated checksum algorithm that detects errors. It uses a complex mathematical formula that employs division and addition.CUGSee IDREF="FM31402"Closed User Group (CUG).DARPA (Defense Advanced Research Projects Agency)The U.S. government agency that funded ARPAnet. See also IDREF="FM40112"ARPAnet.ID="FM31483"Data Circuit Terminating Equipment (DCE)Any one of the devices that is not a DTE, but is associated with a single network port. A DCE is responsible for establishing, maintaining, and terminating the connection with a DTE.ID="FM39150"data compression A method to reduce the amount of information transferred over a communications link by replacing previously observed data sequences with more compact sequences. Data compression can be used only if both peers support a common methodology.datagramOne packet of information and associated delivery information that is routed through a packet-switching network.ID="FM27735"Data-Link layerThe second of seven layers of the Open Systems Interconnection (OSI) Reference Model. It is involved in both packaging and addressing information and controlling the flow of separate transmissions over communication lines.Data Link Connection Identifier (DLCI) See IDREF="FM25506"DLCI (Data Link Connection Identifier). ID="FM24195"Data Terminal Equipment (DTE)A generic term for any network-attached, customer-premises or end user equipment operating in packet mode.data rateThe speed at which data bits are transmitted and received. The data rate is usually measured in bits per second (bps). D-bitSee IDREF="FM23372"delivery confirmation bit (D-bit).DCESee IDREF="FM31483"Data Circuit Terminating Equipment (DCE).DDS (Dataphone Digital Service)The AT&T four-wire, digital communications service that operates at speeds from 2,400 bps to 56 Kbps on a point-to-point connection.DE (Discard Eligibility)The bit set by the end node that, when set and supported by the Frame Relay network, allows frames to be discarded in preference to other frames when a network is congested.ID="FM37918"default zoneThe zone name in a zones list that has been specifically defined as the default zone. In the Novell implementation, if no default zone is defined, the first zone name in the zone list is the default zone. See also IDREF="FM23964"zone; IDREF="FM31006"zones list.delayThe time, in microseconds, to send a byte of data from one system to another.ID="FM23372"delivery confirmation bit (D-bit)A component of a user packet. If set to 1, it specifies that an end-to-end acknowledgment is sent by the receiving DTE to the sending DTE. This acknowledges the receipt of a complete packet sequence. If set to 0, it specifies local delivery acknowledgment.ID="FM85927"Designated RouterThe NLSP router responsible for exchanges of link state information on behalf of all other NLSP routers on the same LAN. See also IDREF="FM92617"pseudonode.destination addressThe address in a packet identifying which station is to receive it.destination nodeIn the Open Systems Interconnection (OSI) model, the nodes that represent the host computers at each end of a connection. In a packet-switching network, the node attached to the DTE that is receiving the data.device driverThe software or firmware that translates operating system requests into a format that is recognizable by specific hardware, such as adapters.dial-upRelating to the access to a telephone circuit that requires a manual or automatic dialing sequence to establish a connection.dial-up connectionA type of connection to a Public Data Network (PDN) used primarily by PC users to access data residing on remote hosts. The data transmission rate usually is slower than that of leased lines, and usually has an upper limit of 9600 bps.distance vector algorithmThe class of routing algorithms that periodically broadcast routing information rather than sending information only when a change occurs in a route. Routers using the distance vector algorithm periodically exchange information about accessible networks with their immediate neighbors. Each node on the network consolidates the information it receives and passes it on to other routers, servers, and end nodes.distance vector protocolA protocol that derives best-path information from the best-path information present in adjacent nodes. IP RIP, IPX RIP, and Routing Table Maintenance Protocol (RTMP---an AppleTalk routing protocol) are examples of distance vector protocols.ID="FM25506"DLCI (Data Link Connection Identifier)The 10-bit routing address of the virtual circuit at either the User-Network Interface (UNI) or the Network-Network Interface (NNI). It allows the user and network management to identify the frame as being from a particular permanent virtual circuit (PVC). The DLCI is used for multiplexing several PVCs over one physical link. domainSee IDREF="FM31406"routing domain.DTESee IDREF="FM24195"Data Terminal Equipment (DTE). DTE addressThe X.121 address assigned to the local or remote DTE.DTE/DCE (Data Terminal Equipment/Data Communications Equipment)(DTE) The customer premises equipment, such as terminals and computers, that connect to data communications equipment (DCE) in a packet-switched network.(DCE) The devices that establish, maintain, and terminate a data communications session; they also provide encoding or conversion.EGP (Exterior Gateway Protocol)The routing protocol used by gateways in an internetwork to connect autonomous networks. It is used in the Internet core system.encapsulationThe technique used by Network-layer protocols in which a layer adds header information to the protocol data unit (PDU) from the preceding layer. Also used in enveloping one protocol inside another for transmission (for example, IP inside IPX).end nodeThe machine or unit (node) that serves as an originator and final destination of network traffic, but does not relay traffic originated by other nodes. See IDREF="FM29508"node.end systemThe computer of the Open Systems Interconnection (OSI) model containing application processes that can communicate through all seven layers of the OSI model. Equivalent to an end node.enterprise networkAn internetwork that connects a corporation's local and remote sites.ID="FM32459"EthernetA system of high-performance coaxial cables widely used in the communications industry. Ethernet cables can be part of an AppleTalk network or a TCP/IP network, for example. See also IDREF="FM85060"EtherTalk.ID="FM85060"EtherTalkAn AppleTalk network on Ethernet. An EtherTalk network can be either nonextended (EtherTalk 1.0) or extended (EtherTalk 2.0). See also IDREF="FM32459"Ethernet.excess burst sizeSee IDREF="FM38994"Be (excess burst). extended networkAn AppleTalk Phase 2 network on high-speed media, such as Ethernet or token ring. An extended network is capable of supporting the Phase 2 addressing extensions of a network range and zones list. See also IDREF="FM24859"network range; IDREF="FM31006"zones list.fast selectA facility that expands the Call and Clear User data fields from the typical 16 octets to 128 octets, making the data field more useful for short-duration, low-volume, transaction-oriented applications. This facility is often used in retail point-of-sale and credit card authorization terminal environments.FDDI (Fiber Distributed Data Interface)The ANSI standard for high-speed (100 Mbps) fiber-optic connections.FECN (Forward Explicit Congestion Notification)The notification set by the Frame Relay network to indicate that it has experienced congestion in the packet forwarding direction of the frame.filterThe process on a router that selectively discards packets of a certain type, or packets originating from or destined for a certain location. See IDREF="FM34185"service information filter; IDREF="FM34609"routing information filter.filtering rateThe speed at which packets are checked and discarded.flagA field that is repeated at the beginning and end of a Synchronous Data-Link Control (SDLC) or High-level Data-Link Control (HDLC) frame. It always has a bit pattern of 011111110.flow control negotiationA facility that allows the negotiation, on a per-call basis, of the window size and maximum user packet size used on a virtual call in each direction.fragmentOne piece of a packet that has been divided by fragmentation.fragmentationThe process in which a packet is broken into smaller pieces to fit the size requirements of the physical network it is transmitted across.ID="FM37130"frame (1) The data unit sent using a protocol, such as High-level Data Link Control (HDLC) or Link Access Procedure Balanced (LAPB), to provide Data Link-level communication between two nodes on a network. (2) A group of bits representing data from many channels, as in T1 communications. See also IDREF="FM22645"unnumbered frames.ID="FM16920"Frame layerAn X.25 layer that transports data across the physical link, controls the interchange between the DTE and DCE, and corrects any link errors. Also called the Link layer.ID="FM39539"Frame Rejected frame (FRMR)A type of frame that reports the receipt of an unacceptable frame.Frame Relay A switching interface that operates in packet mode. It uses the LAPB protocol using less processing than X.25 packet switching, making it well-suited to high-speed networking of bursty data. Frame Relay network A private line network that permanently allocates dedicated transmission resources between communication end points. A Frame Relay network uses statistical multiplexing, making transmission resources allocated only when active communications exist. frame switching/relaying technology The process of quickly transporting HDLC (High-level Data Link Control) frames through a network.FRMRSee IDREF="FM39539"Frame Rejected frame (FRMR).full-duplex transmissionIn TCP/IP, the process that allows two data streams to flow in opposite directions simultaneously. The receiving application can send control information back to the sending application while the sending application continues to send data.gatewayAn internetworking device that operates from the network to application layers of the Open Systems Interconnection (OSI) model. Sometimes used as a synonym for router. ID="FM38796"HDLC (High-level Data Link Control)A bit-oriented, synchronous protocol that applies to the Data-Link layer of the Open Systems Interconnection (OSI) model. headerThe information at the beginning of a packet that defines control information, including addressing and control.ID="FM41202"header compression A set of standard compression options intended to eliminate nonessential information from the frame format (including address and control compression, protocol ID (PID) compression, and data compression) and maximize the bandwidth available from Public Switched Telephone Network (PSTN) connections.hierarchical addressingAn addressing scheme whereby a network is partitioned into sections, with the section identifier forming one part of each destination address, and the destination identifier forming another. This allows destination identifiers---such as server names---to be reused in different sections, because the section identifier distinguishes them. There can be more than one level of section.High-level Data-Link Control (HDLC)See IDREF="FM38796"HDLC (High-level Data Link Control). ID="FM74381"hopA measure of distance, in routers, on a network. The number of hops to a destination network is the number of routers that must be traversed to reach the destination network. The number of hops is part of each network entry in a RIP packet. See also IDREF="FM40922"RIP (Routing Information Protocol); IDREF="FM66278"tick.hop countThe routing metric used to measure the distance between a source and a destination; each hop equals the transmission of a packet across one router.ICMP error message (Internet Control Message Protocol)A packet that contains information about failures on the network.ID="FM37209"IETF (Internet Engineering Task Force)The Internet Activities Board (IAB) task force responsible for solving the short-term engineering needs of the Internet.I frameSee IDREF="FM35716"Information frame (I frame).IGP (Interior Gateway Protocol)A type of protocol used to exchange routing table information between collaborating routers in the Internet. The Routing Information Protocol (RIP) and the Open Shortest Path First (OSPF) protocol are examples of IGPs.ID="FM39468"INETCFG (Internetworking Configuration utility)A menu-based NetWare Loadable Module (NLM) file that simplifies the installation of Novell internetworking products by allowing a network administrator to configure interface boards and network protocols. INETCFG enables network administrators to bind protocols to different LAN boards, and also to view the entire configuration or selected portions.ID="FM35716"Information frame (I frame)A type of frame used to transfer packet information. An I frame can also contain data for frame-level flow control.ID="FM22177"Integrated Services Digital Network (ISDN) An evolving set of standards for a digital network that carries both voice and data communications.Interexchange CarrierSee IDREF="FM14600"IXC (Interexchange Carrier). interface groupA set of specified interfaces. It allows protocols to request an X.25 virtual circuit through any one interface from within the group, without having to specify a specific interface.ID="FM17639"internal networkA virtual network that consists of two software nodes: the AppleTalk protocol stack and the AppleTalk router. See also IDREF="FM25948"network.InternetThe collection of networks and gateways that use the TCP/IP suite of protocols. Written in lowercase, it is an abbreviation for internetwork.Internet addressA 32-bit address assigned to hosts using TCP/IP.Internet Engineering Task Force (IETF)See IDREF="FM37209"IETF (Internet Engineering Task Force). ID="FM30635"internetworkAny interconnected group of networks, such as an interconnected group of TCP/IP networks. Network users in an internetwork can share information and network devices. See also IDREF="FM25948"network.Internetworking Configuration (INETCFG) utilitySee IDREF="FM39468"INETCFG (Internetworking Configuration utility).Inverse ARP (Inverse Address Resolution Protocol)A type of protocol that learns the IP address of a remote node's DLCI on a link.IP addressA 32-bit address assigned to hosts using TCP/IP.IP (Internet Protocol)A TCP/IP protocol that provides datagram delivery of messages.IPCP (Internet Protocol Control Protocol) A TCP/IP Network Control Protocol (NCP) for Point-to-Point Protocol (PPP) that provides procedures for establishing, configuring, and terminating interaction between peers over a PPP link.IPX (Internetwork Packet Exchange)A NetWare protocol similar to the Xerox Network Systems (XNS) protocol, providing datagram delivery of messages.IPX addressAn address comprising a four-byte network number, a six-byte node number, and a two-byte socket number. The network number is assigned to each LAN segment, server, or router. The node number identifies a specific system, and is typically the number assigned by the manufacturer or the network interface device. The socket number distinguishes processes within the same computer. IS-IS (Intermediate System-to-Intermediate System)The Open Systems Interconnection (OSI) routing protocol by which intermediate systems exchange routing information. IS-IS is a link state routing protocol.ISDNSee IDREF="FM22177"Integrated Services Digital Network (ISDN). ISO (International Organization for Standardization)An international organization that establishes global standards for communication and information exchange, as well as for many other fields of commercial activity.Kbit/s (Kilobits per second)A data rate equal to 1024 bps.ID="FM14600"IXC (Interexchange Carrier)A long-distance telephone company. keep-alive packet A type of packet sent as an Echo Request to a remote peer; typically, an Echo Response is sent back to the peer sending the request. A keep-alive packet serves as a continuous link-confidence test at the access interface, sent at a specified time period.LAN (local area network)A group of computers and other devices connected by a communications link that allows any device to interact with any other device on the network.LAN driverA device driver that renders the different types of packet frames used by each specific network type into a form that AppleTalk can process.LAPB (Link Access Procedure-Balanced) ProtocolThe Consultative Committee for International Telegraphy and Telephony (CCITT) bit-oriented protocol similar to the Synchronous Data-Link Control (SDLC) protocol.LCNSee IDREF="FM38806"logical channel number (LCN).ID="FM30919"LCP (Link Control Protocol)A packet that provides procedures for establishing, configuring, testing, and terminating the operation of data-link connections.leased lineA dedicated communications line usually leased from a Public Data Network (PDN) vendor on a monthly basis. Current modem technology permits data transmission up to 19.2 Kbps on an analog line. Direct digital service lines are available up to 64 Kbps.ID="FM41081"learning routerOn a router, an interface configured to learn its configuration from a configured router on the same network. Compare IDREF="FM37606"configured router. ID="FM14424"LEC (Local Exchange Carrier)A local company that provides local connections or, if the area is to be expanded, connections to the IXC (Interexchange Carrier).ID="FM78713"level 1 routingThe interaction of routers within the same routing area. See also IDREF="FM90443"routing area.ID="FM93519"level 2 routingRouting between areas to form a routing domain controlled by a single administrative unit (for example, communications) within an organization. See also IDREF="FM31406"routing domain.level 3 routingRouting between routing domains controlled by different administrative units---for example, communications between different companies or academic organizations.lineA circuit, channel, or link that carries data communications signals. linkA channel or line; usually refers to a point-to-point line. In the context of NLSP running on a LAN, a pointer to a Designated Router pseudonode. See also IDREF="FM85927"Designated Router; IDREF="FM92617"pseudonode.Link Control Protocol (LCP)See IDREF="FM30919"LCP (Link Control Protocol). Link layerSee IDREF="FM27735"Data-Link layer; IDREF="FM16920"Frame layer.link-level protocolA set of rules that defines methods for communicating over a channel, circuit, or link.link-state routing algorithmA type of routing protocol in which each router floods information on the state of its links (network attachments) to all nodes in the internetwork. This approach reduces routing loops and network traffic but has greater memory requirements than the distance vector algorithm. NLSP, OSPF, and IS-IS are examples of link state protocols.Link Support Layer (LSL)An implementation of the IDXID="w9535"BOOK="_idx" COLLECTION="nw41" TIDREF="i3079"
Open Data-Link Interface (ODI) specification, LSL serves as an intermediary between the server or router LAN drivers and the communications protocols, such as IPX, TCP/IP, and AppleTalk. LMI (Local Management Interface)An implementation agreement that addresses signaling and other network management functions. load balancingA scheme for distributing network traffic among parallel paths. It provides redundancy while using the available bandwidth efficiently.load sharingThe ability of two or more remote bridges to share their traffic load in a parallel configuration; if one bridge fails, traffic is routed to the next parallel bridge.Local Exchange CarrierSee IDREF="FM14424"LEC (Local Exchange Carrier). LocalTalk networkA system of cables, cable extenders, and connector boxes that connect computers and network devices as part of the AppleTalk network system. LocalTalk kits are manufactured by Apple Computer. Generally, where this reference refers to a LocalTalk connection, you can use any system of cables and connectors that supports AppleTalk protocols at 230.4 Kbps to interconnect Macintosh computers and other AppleTalk devices.logical channelThe mechanism that allows multiple, simultaneous virtual circuits across one physical link.ID="FM38806"logical channel number (LCN)A unique number given to each virtual circuit for a call. It is attached to each packet in the call and differentiates the packets from packets generated by other users for other calls. loopbackA diagnostic test in which a signal is transmitted across a medium while the sending device waits for its return.loopback plugA special connector used to perform echo testing.ID="FM42184"LSP (Link State Packet)A packet generated by an NLSP router that lists the router's neighbors and attached IPX networks.ID="FM23365"MAC (media access control)The Data-Link layer protocol that governs access to transmission media.managed objectA device that is connected to a network and that can be managed by network management software or a protocol such as SNMP.management information baseSee IDREF="FM22835"MIB (Management Information Base).ID="FM22617"Maximum Receive Unit (MRU) See IDREF="FM22617"Maximum Receive Unit (MRU). Maximum Transmission Unit (MTU)See IDREF="FM28534"MTU (Maximum Transmission Unit).M-bitSee IDREF="FM28376"More data mark (M-bit).MbpsA data rate equal to 10 to the sixth power bps; often called megabits per second (1,000,000 bps).media access controlSee IDREF="FM23365"MAC (media access control).ID="FM22835"MIB (Management Information Base)A database of network management information used by the Common Management Information Protocol (CMIP) and the Simple Network Management Protocol (SNMP).modem A device that performs modulation and demodulation, allowing data communications to occur in analog form over telephone circuits. Modulo 8 or 128A packet sequence numbering method that specifies the control over the numbering of sequential data packets in a window. ID="FM28376"More data mark (M-bit)A component of a user packet. If set, it specifies that the next packet sent is a logical continuation of the data in the current packet.MRU (Maximum Receive Unit)An LCP option that enables the sender to inform the peer that it can receive larger frames than the default, or to request that the peer send smaller frames. See also IDREF="FM30919"LCP (Link Control Protocol).ID="FM28534"MTU (Maximum Transmission Unit)The largest packet size, in bytes, that can be sent on a given physical network medium. For example, the MTU for Ethernet is 1500 bytes.ID="FM78289"multicastA transmission method whereby only those devices listening for a specified multicast packet address accept the routing information packet. Contrast with IDREF="FM12042"broadcast (noun).multiplexing A method that allows a single communications circuit to take the place of several parallel ones; often used to allow remote terminals to communicate with front-end processor ports over a single circuit.multiprotocol encapsulation A method used by Network-layer protocols in which a layer adds control information to the protocol data unit (PDU) from the preceding layer. Also used in enveloping one protocol inside another for transmission (for example, IP inside IPX).NAK (negative acknowledgment)A Return signal that reports an error in the message received; the opposite of ACK.name resolutionThe ability to associate a name that the network administrator has assigned with its network location.ID="FM27290"NCP (NetWare Core Protocol)A type of protocol that provides control for interaction between clients and file servers; it defines its own session control and packet-level error checking. Also, in SNA environments, it refers to the network control program, which does the routing and addressing of SNA devices.ID="FM18367"neighborAn NLSP router that can form an adjacency with another NLSP router. Two NLSP routers are considered neighbors when they can communicate directly---that is, without the aid of an intermediate router. See also IDREF="FM45325"adjacency.neighboring routersIn the Open Shortest Path First (OSPF) protocol, two routers that share a route to the same network.NetBIOS (Network Basic Input/Output System)An application program interface typically used on LANs comprising IBM and compatible microcomputers. NetBIOS separates application programs from the networking subsystem, so that application program implementers can support multiple network designs, and a network system can support independently developed applications.NetWareThe Novell network operating system that provides the ability to share services across dissimilar platforms. It uses the NetWare Core Protocol (NCP), Internetwork Packet Exchange (IPX), and Sequenced Packet Exchange (SPX) protocols transparently.NetWare Link/X.25The Novell link state routing protocol for X.25 internetworks.NetWare Loadable ModuleSee IDREF="FM26432"NLM (NetWare Loadable Module).ID="FM25948"networkA collection of interconnected, individually controlled computers, together with the hardware and software used to connect them. See also IDREF="FM17639"internal network; IDREF="FM30635"internetwork.network addressA unique Network-layer number that refers to a logical network device. Also known as a protocol address. See also IDREF="FM35470"network number; IDREF="FM34134"node address.network administrationThe task of managing the software and hardware that connects computers in a network. This task includes assigning addresses to devices, maintaining network data files across the network, and setting up internetwork routing. Network administration can also include system tasks on a server, such as starting up and shutting down the system, adding and removing user accounts, and backing up and restoring data.network architectureA framework of principles to facilitate the operation, maintenance, and growth of a communications network by isolating the user and application programs from network details. Protocols and software are packaged together into a usable network architecture system that organizes functions, data formats, and procedures.Network Control Protocol (NCP)See IDREF="FM27290"NCP (NetWare Core Protocol). Network layerThird of seven layers of the Open Systems Interconnection (OSI) model; it ensures that information arrives at its intended destination and smooths out the differences between network media so higher layers do not need to account for the distinctions.network managementThe process of ensuring consistent reliability and availability of a network, as well as timely transmission and routing of data. It can be performed by dedicated devices or programmed general-purpose devices.network monitoringA network management function that constantly checks the network and reports any problems. Network-Network InterfaceSee IDREF="FM37450"NNI (Network-Network Interface). ID="FM35470"network numberIn an AppleTalk network, a decimal integer between 1 and 65,279. You assign a network number to each nonextended network supporting AppleTalk. See also IDREF="FM24859"network range.In a TCP/IP network, the number of the network. Hexadecimal numbers must start with the character pair 0x or 0X. It can be specified with or without trailing zeros. For example, the addresses 130.57 and 130.57.0.0 denote the same IP network. ID="FM24859"network rangeOn an AppleTalk network, a contiguous range of decimal integers between 1 and 65,279, such as 1-10. You assign a network range to each extended network supporting AppleTalk. See also IDREF="FM35470"network number.network topologyThe arrangement of nodes on a network; usually a star, ring, tree, or bus organization.NFS (Network File System)A distributed file system developed by Sun Microsystems, Inc., that allows a set of computers to access one another's files cooperatively in a transparent manner.ID="FM26432"NLM (NetWare Loadable Module)An application or driver that resides on a NetWare server; it provides additional resource management capabilities.NLSP (NetWare Link Services Protocol)The link state protocol used by IPX routers and servers to share information about their routes with other devices on the network. NLSP enables network managers to interconnect small or large IPX networks without routing inefficiencies.ID="FM37450"NNI (Network-Network Interface)A description of how a Frame Relay network interconnects, enabling users subscribing to different Frame Relay network providers to communicate.ID="FM29508"nodeAn addressable entity on a network. This term sometimes refers to a device itself. Some examples of nodes are Macintosh computers, printers, and file servers. The node acquires a unique 8-bit node number dynamically when it connects to the network. It tries to use that address and node number again when it connects to the network the next time. If the node finds that its previous number is already in use, it tries again until it finds a unique node address. See also IDREF="FM34134"node address.ID="FM34134"node addressA number acquired dynamically by each node when it comes up on a network. You cannot assign an AppleTalk node address explicitly. A device's node address is combined with the network number to form its unique network address. See also IDREF="FM29508"node.nonextended networkAn AppleTalk network that does not support AppleTalk Phase 2 extensions, such as zone lists and network ranges.NRZ (Nonreturn to zero)A binary encoding and transmission scheme in which ones and zeros are represented by opposite and alternating high and low voltages, and there is no return to a reference (zero) voltage between encoded bits.NRZI (Nonreturn to zero inverted)A binary encoding and transmission scheme that inverts the signal on a one and leaves the signal unchanged for a zero; a change in voltage state signals a one-bit and the absence of a change signals a zero-bit.octetA group of eight binary digits operated on as a unit; also called a byte or character.on-demand callA type of call that is activated by the presence of data traffic directed to or through the remote peer system.ID="FM25644"on-demand connection A method that enables occasional access to a remote system instead of a permanent access, thereby saving connection expense and maximizing the use of network resources. This type of connection uses static routing information to advertise the presence of exterior networks, although no route currently exists. Contrast with IDREF="FM40541"permanent connection.on-demand SVCA virtual circuit that is brought down after data has been transmitted over the established Switched Virtual Circuit (SVC). The circuit remains down until more data is queued up for sending, at which point connection is reestablished.OSI (Open Systems Interconnection) model A seven-layer model for data communication.OSPF (Open Shortest Path First) protocolA hierarchical Interior Gateway Protocol (IGP) routing algorithm for IP that is a proposed standard for the Internet. Incorporates least-cost routing, equal-cost routing, and load balancing.packetA group of bits transmitted as a unit of information on a network. These bits include data and control elements. The control elements include the addresses of the packet's source and destination and, in some cases, error-control information. In packet-switching networks, a transmission unit of a fixed maximum size that consists of binary digits representing both data and a header. See also IDREF="FM15129"control packet.packet forwardingThe act of copying a packet from one interface to another through an intermediate system.packet frameA set of information added to a packet to ensure its proper transmission across the network. A frame consists of information in a format that is dependent on the physical medium on which the data travels.Packet layerAn X.25 layer that controls call setup and clearing, packet transfer, and network facility selection.packet sizeThe size of an incoming or outgoing data packet.packet-switched networkA collection of interconnected, individually controlled computers that use packets to transmit information to each other. See IDREF="FM31218"packet switching.ID="FM31218"packet switchingA data communications process whereby messages are broken into finite-sized packets. The message packets are forwarded to the other party over different circuit paths. At the other end of the circuit, the packets are reassembled into the message, which is then passed on to the receiving terminal or device.ID="FM27999"PAP (Password Authentication Protocol) authenticationAn inbound call protection method that enables an exchange of peer ID/password pairs used to validate the calling node. The ID/password pair is compared against a local list of authorized pairs for validation of the calling node.Password Authentication ProtocolSee IDREF="FM27999"PAP (Password Authentication Protocol) authentication. PDNSee IDREF="FM11059"Public Data Network (PDN).PDU (Protocol Data Unit)A block of data and control information exchanged between two nodes by a protocol.ID="FM40541"permanent connection A method that enables a constant connection to a remote peer. Contrast with IDREF="FM25644"on-demand connection.permanent SVCA virtual circuit that is in a connected state until the user or application brings it down.ID="FM29580"permanent virtual circuit (PVC)A continuously available communications path connecting two fixed end points. Similar to a leased line.physical addressThe Data-Link layer address of a network device.Physical layerThe first of seven layers of the Open Systems Interconnection (OSI) model; it details the protocols that govern transmission media and signals.In X.25, a layer of the interface that defines the physical interface between a DTE and DCE. It specifies the procedures used to establish, maintain, and release the physical connections or data circuits between network end points.PING (Packet Internet Grouper)A program used to test the reachability of destinations by sending them an Internet Control Message Protocol (ICMP) echo request and waiting for a reply.pollingAny procedure that sequentially and periodically contacts terminals in a network.Point-to-Point Protocol (PPP)See IDREF="FM12555"PPP (Point-to-Point Protocol). port(1) The logical point of contact between a LAN driver and a protocol that you bind to it. (2) The hardware that enables a component to communicate with a peripheral, such as a parallel port. (3) A unique server input/output address assigned to a LAN driver in NetWare software.ID="FM12555"PPP (Point-to-Point Protocol)An industry-standard protocol that enables point-to-point transmissions of routed data across transmission facilities between interconnected LANs using a synchronous or asynchronous serial interface. ID="FM26161"protocolA set of rules for transmitting data within a network or internetwork. A protocol specifies the format, timing, and sequence in which the network transmits data. Common protocols include AFP, ALAP, RTMP, NCP, and IPX. See also IDREF="FM32333"protocol stack.protocol dependentA term that refers to routing based on a Network-layer or software address. It is specific to the type of Network-layer protocol, such as IP, IPX, or DDP.ID="FM39887"Protocol Field compression A process of reducing the PID (Protocol ID) field to a single byte, from the HDLC framing standard of two bytes, to reduce unneeded overhead when using low bandwidth links.ID="FM32333"protocol stackA complete suite of protocols that includes all layers required to handle transmission and receipt of packets. See also IDREF="FM26161"protocol.protocol suiteA hierarchical set of related protocols.proxy ARPThe technique in which one machine, usually a router, answers ARP requests intended for another machine. By faking its identity, the router accepts responsibility for routing packets to the real destination. It allows a site to use a single IP network address for two physical networks.ID="FM92617"pseudonodeA fictitious NLSP router that represents an entire LAN in the link state database. The Designated Router represents the pseudonode for Link State Packet (LSP) exchanges. See also IDREF="FM85927"Designated Router; IDREF="FM42184"LSP (Link State Packet).pseudo-switchedA dial-up link established over the Public-Switched Telephone Network (PSTN) by using a pair of synchronous modems.PSTNSee IDREF="FM36255"Public Switched Telephone Network (PSTN). ID="FM11059"Public Data Network (PDN)A data network provided for the general public.ID="FM36255"Public Switched Telephone Network (PSTN) A service provider that offers switched circuit lines, such as switched/56 service and asynchronous communications. PSTN offers unrestricted access, thereby making inbound authentication an important consideration.ID="FM98226"PVCSee IDREF="FM29580"permanent virtual circuit (PVC). Q-bitSee IDREF="FM29221"Qualifier bit (Q-bit).ID="FM29221"Qualifier bit (Q-bit)A component of a user packet. It determines whether the user data field contains data for the user or high-level control information.reverse chargingA facility that offers the equivalent of a collect call. This facility is allowed on a per-call basis, and is specified in the Call Request packet by the calling DTE.Receiver Ready packetA type of control packet sent to a DTE to indicate that the receiving DTE is ready for the call. Reset Request packetA type of control packet sent to a DTE to request reset of a virtual call. Restart Request packetA type of control packet sent to a DTE to request restart of a virtual call. ID="FM40922"RIP (Routing Information Protocol)A distance vector protocol that provides a measure of distance, or hops, from a transmitting system to a receiving system.route metricThe measure that determines the preference between two different routes generated by the same protocol to the same destination. In TCP/IP, an OSPF route entry has two metrics: an internal metric and an external metric.routerThe software that connects multiple networks so that all the nodes on each network can access services and nodes on any other network. It operates at the Network layer (Layer 3) of the OSI model for forwarding decisions. An AppleTalk router connects AppleTalk networks into an internetwork so that all the nodes on each network can access services and nodes on any other connected network. It receives and forwards AppleTalk packets on the networks to which it is directly connected. Router Discovery ProtocolA type of protocol that allows hosts to find routers on the locally attached networks. It is a feature of TCP/IP that alleviates the need to configure hosts with a routing table or a default router.routingThe transmission of a datagram from one node to another on the same or a different network. It also refers to the paths that are chosen to transmit an IP datagram from its origin to its destination, based on the IP addresses contained in the datagram.ID="FM90443"routing areaAn administrative domain of connected IPX networks all having the same area address. Users in a routing area have Network-layer access to the same services. See also IDREF="FM78713"level 1 routing; IDREF="FM31406"routing domain.ID="FM31406"routing domainA collection of routing areas joined by level 2 routers. A routing domain can be a company, a university, an agency, or even a public carrier connecting two or more business or academic organizations. Within a routing domain, each local campus---or other suborganization---constitutes a routing area. See also IDREF="FM93519"level 2 routing; IDREF="FM90443"routing area.ID="FM34609"routing information filterA type of filter that restricts the exchange of routing information between routers. These filters increase security by limiting the visibility of selected networks and reduce the network bandwidth consumed by the periodic exchange of routing information between routers.Routing Information TableIn the context of RIP, a table stored in an IPX RIP router that contains network numbers, routes to a particular destination network, and metrics---such as hops and ticks---associated with those routes. The router uses this information to forward packets to their destination by the best possible route. See also IDREF="FM74381"hop; IDREF="FM66278"tick.routing protocolA type of protocol that enables routing through the implementation of a specific routing algorithm. Examples of routing protocols include RIP, OSPF, NLSP, and IS-IS.routing tableA database in a router that keeps track of routes (and in some cases, metrics associated with those routes) to a particular network destination.routing updateA message sent from a router to indicate network reachability and associated cost information; it is typically sent at regular intervals and after a change in network topology.ID="FM14203"SAP (Service Advertising Protocol)A Novell protocol that disseminates information about network services and their addresses to all nodes in an IPX network.segmentA LAN with no routers or bridges.serial transmissionA method of transmission in which bits are sent one after the other on the same wire.Serial Line Internet Protocol (SLIP)See IDREF="FM24730"SLIP (Serial Line IP).serverA combination of controller software and mass-storage devices that allows computer users to share common files and applications on a network. A server on an AppleTalk network might be a Macintosh computer running AppleShare software or an IBM PC (or a compatible computer) running the NetWare Communication Services Manager software.service access interfaceA point that determines what happens between routers and the edge node (or switch) of the Frame Relay network.Service Advertising ProtocolSee IDREF="FM14203"SAP (Service Advertising Protocol).ID="FM34185"service information filterA type of filter that restricts service access by filtering out the packets that advertise the services. These filters keep applications from discovering the location of services, but do not restrict access to services if applications know the locations of the services.Session layerThe fifth of seven layers of the Open Systems Interconnection (OSI) model; it allows dialog control between end systems.ID="FM24730"SLIP (Serial Line IP)An Internet protocol used to run IP over serial lines, such as telephone circuits or RS-232 cables, interconnecting two systems. SLIP is being replaced by the Point-to-Point Protocol (PPP).SMDS (Switched Multimegabit Data Service)The Metropolitan Area Network (MAN) technology based on the IEEE 802.6 standard. It has certain LAN-like characteristics while spanning large geographic distances, for example, the size of a city.SNMP (Simple Network Management Protocol)The TCP/IP protocol that allows network management.ID="FM22405"source route bridgingA type of bridging scheme proposed by IBM that attempts to merge the two most prevalent bridging strategies (source route bridging and transparent bridging); it employs both technologies in one device. No translation is done between the bridging protocols.source routingA bridging mechanism to route frames through a multi-LAN network by specifying in each frame the route it will follow. The route is determined by the end stations through a discovery process supported by source route bridges.source route transparent bridgingSee IDREF="FM22405"source route bridging.split horizon (split-horizon routing)A routing technique by which a router does not advertise routes it learns from an interface out through the same interface, because neighboring routers reachable through that interface know the information already. Distance vector routing protocols typically use split horizon to reduce routing traffic on the network.SRT bridgingSee IDREF="FM22405"source route bridging.standardA set of rules or procedures that has been agreed upon by industry participants.static routingA method of updating entries in a routing table manually.statistical multiplexing A method, usually through a time division multiplexer (TDM), that allocates line time dynamically to each of the various attached terminals, according to whether a terminal is active or inactive at a particular moment. Buffering and queuing functions are also included. It is also called a stat mux.ID="FM17112"Statistical Time-Division Multiplexing (STDM)A method of data transmission that allows X.25 to maximize bandwidth use by dynamically allocating portions of the available bandwidth to active devices on demand. In contrast to time-division multiplexing (TDM), which dedicates a fixed bandwidth of the network medium to connected devices regardless of whether they are active, X.25 provides better throughput. See also IDREF="FM25053"Time-Division Multiplexing (TDM).STDMSee IDREF="FM17112"Statistical Time-Division Multiplexing (STDM). stop bitIn asynchronous transmission, a bit used at the end of a group of bits representing a character; it signals the end of a character.stub networkAn IP network that uses a subset of an existing IP network address and is serviced by a proxy router.subnet address maskA bit mask used to select bits from an Internet address to create a subnet.subnetworkThe portion of the backbone that is partitioned by repeaters, bridges, or routers.subnetwork addressingThe process of using a single Internet ID to identify a number of subnetworks within an organization.SVCSee IDREF="FM35074"switched virtual circuit (SVC).switched link A service, such as switched 56 Kbps, providing for temporary file transfer or management. When the link is idle, the vendor uses the channel for other users. When your link becomes active, whatever 56-Kbps channel is available is switched to your link.ID="FM35074"switched virtual circuit (SVC)A type of virtual circuit that is established dynamically using call setup and call clearing procedures. A permanent SVC is left in a connected state until the user or application brings it down. An on-demand SVC is brought down after data has been transmitted over the established SVC. The circuit remains down until more data is queued up for sending, at which point the connection is reestablished.synchronizationIn T1 transmission, the timing function provided by the framing bit.synchronous Having a mode of data transfer in which information is transmitted in blocks (frames) of bits separated by equal time intervals.System IDA unique, six-byte hexadecimal number that identifies an NLSP router.T1/E1(T1) A high-speed leased line, transmitting at rates up to 1.544 Mbps (in the United States).(E1) A facility used to transport 30 voice channels at 64 Kbps (for a total of 2.048 Mbps). See also IDREF="FM28760"CEPT (European Conference of Postal and Telecommunications Administration).ID="FM41934"TCP (Transmission Control Protocol)The major transport protocol in the Internet suite of protocols, providing reliable, connection-oriented, full-duplex streams; it uses IP for delivery.ID="FM12010"TCP/IP (Transmission Control Protocol/Internet Protocol)The protocol suite developed by the Advanced Research Projects Agency (ARPA). It includes TCP as the primary transport protocol and IP as the Network-layer protocol.TCPCONA diagnostic tool from Novell that provides information about a NetWare server or router TCP/IP stack and about other TCP/IP networks on the internetwork.TDMSee IDREF="FM25053"Time-Division Multiplexing (TDM).telco The telephone company.TelnetA protocol in the TCP/IP suite that governs character-oriented terminal traffic.throughputThe total amount of useful information processed or communicated during a specific time period.throughput classA type of class negotiation that specifies, on a per-call basis, the throughput of data that can be transferred on a virtual circuit. The range is between 75 bps and 64 Kbps.throughput negotiationA type of facility that specifies whether to allow negotiation, on a per-call basis, of the throughput of data that can be transferred on a virtual circuit. If selected, incoming calls containing the Throughput facility are passed to the destination application. Otherwise, any incoming call containing a Throughput facility is cleared if its value does not match the default.ID="FM66278"tickThe time delay to reach a network. The number of ticks is part of each network entry in a RIP packet. A tick is about 1/18 of a second. (There are 18.21 ticks in a second.) See also IDREF="FM40922"RIP (Routing Information Protocol).ID="FM25053"Time-Division Multiplexing (TDM)A type of data transmission that dedicates a fixed bandwidth of the network medium to connected devices, regardless of whether they are active. See also IDREF="FM17112"Statistical Time-Division Multiplexing (STDM).TokenTalkAn AppleTalk network on token ring. topologyThe physical layer of network components (cables, stations, gateways, and hubs). Three basic interconnection topologies are star, ring, and bus networks.translation bridgingA type of bridging required on networks that have dissimilar media access control (MAC) sublayer protocols; translation bridging resolves differences in header formats and protocol specifications.Transmission Control ProtocolSee IDREF="FM41934"TCP (Transmission Control Protocol); IDREF="FM12010"TCP/IP (Transmission Control Protocol/Internet Protocol).transmission mediumThe physical path for carrying information, such as twisted-pair wires, coaxial cable, fiber-optic cable, terrestrial microwave, and satellite transmission methods.transparentA description of a function that operates without being evident to the user.Transport layerThe fourth of seven layers of the Open Systems Interconnection (OSI) model; it provides reliable, end-to-end delivery of data and detects transmission sequential errors.transport network A private or public data network that transfers data between nodes; usually a public packet-switched or circuit-switched network.tunnelingThe process of encapsulating and de-encapsulating one protocol in another. In AppleTalk, the process by which a router supporting AURP encapsulates AppleTalk packets in IP packets and sends them across the TCP/IP internetwork to the router supporting AURP. The router then removes the IP and AURP headers of the packets and forwards them, like other AppleTalk packets, to their destination AppleTalk network.two-way channelA type of channel that allows both incoming and outgoing calls.UDP (User Datagram Protocol)A transport protocol in the Internet suite of protocols. UDP, like TCP, uses IP for delivery; however, unlike TCP, UDP provides for exchange of datagrams without acknowledgments or guaranteed delivery.ID="FM10753"UNI (User-Network Interface)A description of how a router connects and accesses Frame Relay network services.ID="FM22645"unnumbered framesIn the High-level Data-Link Control (HDLC) protocol, the frames used for system administration. In IEEE 802.2, they are called connectionless datagrams. See also IDREF="FM37130"frame. Unsequenced Acknowledgment (UA)A packet that acknowledges the receipt of a Set Mode command. User-Network InterfaceSee IDREF="FM10753"UNI (User-Network Interface). virtual circuit A type of circuit that provides a connection-oriented service similar to that of circuit switching. In packet-switching networks, it is a circuit that appears to be a physical point-to-point circuit. It connects two end points, conveying sequenced data packets reliably; in fact, it shares the underlying links and relay systems with other users of the network.virtual circuit number A method to determine which packets belong to which virtual circuits. Each packet can contain a four-bit logical group number and an eight-bit logical channel number.virtual linkThe software that extends a backbone area by linking two partitioned areas.workstationA node through which a user can access a server or other nodes. ID="FM23964"zoneA logical grouping of devices physically located on one or more networks. Each nonextended network must have exactly one zone name assigned to it. Each extended network must have at least one zone name, and can have up to 255 zone names, assigned to it. See also IDREF="FM37918"default zone; IDREF="FM31006"zones list.ID="FM31006"zones listA list of up to 255 unique zone names. See also IDREF="FM37918"default zone; IDREF="FM23964"zone.