Avaya Configuring Ipx Services Users Manual V 12.20,
2015-06-01
: Avaya Avaya-Configuring-Ipx-Services-Users-Manual-735197 avaya-configuring-ipx-services-users-manual-735197 avaya pdf
Open the PDF directly: View PDF .
Page Count: 360
Download | |
Open PDF In Browser | View PDF |
Configuring IPX Services BayRS Version 12.20 Site Manager Software Version 6.20 BCC Version 4.00 Part No. 117369-B Rev. 00 June 1998 4401 Great America Parkway Santa Clara, CA 95054 8 Federal Street Billerica, MA 01821 Copyright © 1997 Bay Networks, Inc. All rights reserved. Printed in the USA. June 1998. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Bay Networks, Inc. The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license. A summary of the Software License is included in this document. Trademarks ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, and Bay Networks are registered trademarks and Advanced Remote Node, ANH, ARN, ASN, Bay•SIS, BayStack, and the Bay Networks logo are trademarks of Bay Networks, Inc. All other trademarks and registered trademarks are the property of their respective owners. Restricted Rights Legend Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19. Statement of Conditions In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to make changes to the products described in this document without notice. Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein. Portions of the code in this software product are Copyright © 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission. SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties). ii 117369-B Rev. 00 Bay Networks, Inc. Software License Agreement NOTICE: Please carefully read this license agreement before copying or using the accompanying software or installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price 1. License Grant. Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal, nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software License Agreement that accompanies such software and upon payment by the end user of the applicable license fees for such software. 2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws. Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and its licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise disclose to any third party the Software, or any information about the operation, design, performance, or implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however, Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s facility, provided they have agreed to use the Software only in accordance with the terms of this license. 3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Networks and properly installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function substantially as described in its accompanying user manual during its warranty period, which begins on the date Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the Licensee’s requirements, b) that the Software will operate in the hardware or software combinations that the Licensee may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered, except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of 117369-B Rev. 00 iii its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs. 4. Limitation of liability. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE. 5. Government Licensees. This provision applies to all Software and documentation acquired directly or indirectly by or on behalf of the United States Government. The Software and documentation are commercial products, licensed on the open market at market prices, and were developed entirely at private expense and without the use of any U.S. Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS 252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable. 6. Use of Software in the European Community. This provision applies to all Software acquired for use within the European Community. If Licensee uses the Software within a country in the European Community, the Software Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assistance from Bay Networks. 7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason, Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license. 8. Export and Re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports are restricted or embargoed under United States export control laws and regulations, or to any national or resident of such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any military end user or for any military end use, including the design, development, or production of any chemical, nuclear, or biological weapons. 9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement will be governed by the laws of the state of California. Should you have any questions concerning this Agreement, contact Bay Networks, Inc., 4401 Great America Parkway, P.O. Box 58185, Santa Clara, California 95054-8185. LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT. iv 117369-B Rev. 00 Contents About This Guide Before You Begin ........................................................................................................... xviii Conventions ................................................................................................................... xviii Acronyms .........................................................................................................................xix Bay Networks Technical Publications ..............................................................................xxi Bay Networks Customer Service .....................................................................................xxi How to Get Help .............................................................................................................xxii Bay Networks Educational Services ...............................................................................xxii Chapter 1 Starting IPX Services Starting the Configuration Tools .....................................................................................1-1 Starting IPX ....................................................................................................................1-2 Using the BCC .........................................................................................................1-2 Using Site Manager ..................................................................................................1-5 Chapter 2 IPX Concepts Compatibility with Previous Versions of Bay Networks Software ....................................2-1 About the IPX Protocol ...................................................................................................2-2 Network-Level Services ..................................................................................................2-3 Supported LAN Circuits, WAN Circuits, and Frame Formats .........................................2-3 Types of IPX Configurations ...........................................................................................2-5 For More Information About IPX .....................................................................................2-5 117369-B Rev. 00 v Chapter 3 Customizing IPX for LAN Media Assigning a Unique Network Number .............................................................................3-2 Enabling RIP and SAP on an Interface ...........................................................................3-3 Choosing a Frame Encapsulation Type ..........................................................................3-6 Specifying Multiple Interfaces per Circuit ........................................................................3-8 Configuring a Multiple-Host Router ..............................................................................3-11 Configuring a Single-Host Router .................................................................................3-11 IPX Host ID Numbers ...................................................................................................3-12 Setting a Host ID Number for IPX on a Token Ring Circuit ....................................3-13 Token Ring MAC Address Selection ................................................................3-15 Customizing IPX ...........................................................................................................3-15 Chapter 4 Customizing IPX for WAN Media IPX over WAN Media ......................................................................................................4-1 Using IPXCP and IPXWAN ......................................................................................4-2 Running IPXWAN over PPP .....................................................................................4-2 Running IPXWAN over Frame Relay Permanent Virtual Circuits .............................4-3 Negotiating an IPXWAN Connection ........................................................................4-3 Configuring an IPX Service to Run over a WAN .............................................................4-4 Assigning a Unique Network Number .............................................................................4-4 Enabling RIP on an Interface ..........................................................................................4-6 Enabling SAP on an Interface .........................................................................................4-7 Identifying a Circuit .........................................................................................................4-8 Entering an IPX Host ID Number for IPX over ATM ........................................................4-8 Enabling IPXWAN for an Interface .........................................................................4-12 Assigning a Primary Network Number ...................................................................4-14 Entering a Router Name ........................................................................................4-15 Indicating the Protocol Negotiated for an Interface ................................................4-17 Sample IPXCP and IPXWAN Configurations ...............................................................4-18 IPXCP Link Negotiation ................................................................................................4-19 IPXWAN Link Negotiation .............................................................................................4-19 IPXWAN and IPXCP Link Configurations .....................................................................4-20 Configuration 1 (IPXWAN with IPXCP on Both Interfaces) ...........................................4-20 Configuration Guidelines -- Configuration 1 ...........................................................4-21 vi 117369-B Rev. 00 Configuration 2 (IPXWAN on Both Interfaces) ..............................................................4-21 Configuration Guidelines -- Configuration 2 ...........................................................4-21 Configuration 3 (Only IPXCP on Both Interfaces) .........................................................4-22 Configuration Guidelines -- Configuration 3 ...........................................................4-22 Configuration 4 .............................................................................................................4-22 Customizing IPX ...........................................................................................................4-22 Chapter 5 Customizing IPX Customizing IPX Global Operation .................................................................................5-2 Setting the Maximum Number of Paths ....................................................................5-2 Filtering Log Messages ............................................................................................5-3 Specifying the Maximum Number of Equal Cost Paths ............................................5-5 Specifying the Maximum Number of Destinations ...................................................5-6 Entering the Maximum Number of Services ............................................................5-8 Specifying the Granularity for Aging RIP and SAP Information ..............................5-10 Specifying the Aging Pending Frequency ...............................................................5-11 Enabling IPX Default Routing .................................................................................5-13 Multipath Routing and Load sharing ......................................................................5-14 Multipath Routing .............................................................................................5-15 Load Redistribution and Rerouting ..................................................................5-17 Multipath Route Precedence/Priority ...............................................................5-17 Multipath Configurations ..................................................................................5-17 Multiline Circuits ..............................................................................................5-17 Selecting the GNS Response Mode ......................................................................5-20 Specifying the Table Fill Notify Value .....................................................................5-21 Specifying the Size of the Network Table ...............................................................5-22 Specifying the MIB Reply Slot ................................................................................5-22 Customizing an IPX Interface .......................................................................................5-22 Enabling IPX Routing on an Interface ....................................................................5-23 Entering a Symbolic Name for an Interface ............................................................5-24 Assigning a Host Number to an Interface ..............................................................5-25 Enabling Source Routing for an Interface on a Token Ring Circuit ........................5-27 Entering a Broadcast Address ...............................................................................5-28 Entering a Multicast Address .................................................................................5-29 Responding to IPX Watchdog Packets ...................................................................5-31 117369-B Rev. 00 vii Setting the Delay Time ...........................................................................................5-32 Specifying Throughput ...........................................................................................5-33 Setting the Stabilization Timer Delay .....................................................................5-34 Handling Packets Associated with Upper-Layer Protocols ...........................................5-35 The Routing Information Protocol (RIP) .......................................................................5-36 Enabling RIP on the Router ...................................................................................5-38 Choosing the Routing Method ................................................................................5-39 Setting a Cost for an Interface .........................................................................5-41 Specifying the Maximum Number of Hops ......................................................5-43 Indicating the Number of Next-Hop Hosts .......................................................5-44 Enabling RIP Listen and Supply Functions ............................................................5-46 Determining the Pace of RIP Packets ....................................................................5-47 Configurable RIP Timers ........................................................................................5-48 Adjusting the RIP Packet Size ................................................................................5-51 Enabling Multicast Transmission of RIP Packets ....................................................5-52 Configurable Split Horizon .....................................................................................5-54 Fully Meshed Networks ...................................................................................5-54 Non-Fully Meshed Networks ...........................................................................5-55 Updating Routers about a Failed Route .................................................................5-58 Advertising Default Routes in RIP Packets ............................................................5-59 Accepting Default Route Information .....................................................................5-60 Customizing SAP Parameters ......................................................................................5-61 NetWare Directory Services (NDS) and SAP ..................................................5-62 SAP and the NetWare Bindery (NetWare 3.x and Earlier) ..............................5-63 Configurable SAP Timers .......................................................................................5-64 SAP via Default Route ...........................................................................................5-66 Enabling SAP Listen and Supply Functions ...........................................................5-67 Determining the Pace of SAP Packets ...................................................................5-69 Adjusting the SAP Packet Size ...............................................................................5-71 Responding to SAP Nearest Server Requests ......................................................5-72 Using a Multicast Address ......................................................................................5-73 Saving the Service Name ......................................................................................5-74 Transmitting and Receiving SAP Updates over the Same Interface ......................5-75 Updating Routers about a Failed Service ..............................................................5-76 Using Static Services ...................................................................................................5-77 viii 117369-B Rev. 00 Enabling Static Services ........................................................................................5-81 Specifying the Network Address of a Service ........................................................5-83 Specifying the Address of the Host that Provides a Service ..................................5-84 Assigning a Symbolic Name to Your Service .........................................................5-85 Entering the Service Type Number ........................................................................5-86 Entering the Socket Address of a Service ..............................................................5-88 Entering the Hop Count .........................................................................................5-89 Customizing NetBIOS Static Routing ...........................................................................5-90 Activating the Static Route Record in the NetBIOS Routing Table .........................5-91 Entering the Name of the NetBIOS Target Server .................................................5-93 Entering the Target Network Address ....................................................................5-94 Directing a NetBIOS Packet Using Nonstandard Static Routing ............................5-96 Directing a NetBIOS Packet Using Standard Static Routing ..................................5-97 NetBIOS Broadcast Filters .....................................................................................5-98 Configuring an Adjacent Host for an Interface ............................................................5-102 Making the Adjacent Host Record Active .............................................................5-102 Entering the ID of the Adjacent Host ....................................................................5-104 Entering a WAN Address .....................................................................................5-106 Creating a Frame Relay SVC to an Adjacent Host .....................................................5-108 Dial Services ..............................................................................................................5-111 Using Dial-on-Demand Service ............................................................................5-112 Using Static Routing with Dial-on-Demand ..........................................................5-113 Tips for Using Dial-on-Demand with IPX ..............................................................5-114 Local IPX Watchdog Acknowledgment ................................................................5-114 Local SPX Keepalive Acknowledgment ................................................................5-116 Dial Optimized Routing ...............................................................................................5-116 Getting Optimum Performance Using IPX Dial Optimized Routing ......................5-117 Default IPX Dial Optimized Routing Filters ...........................................................5-118 Configuring the Routing Update Delay Timer ......................................................5-119 RIP/SAP Triggered Updates .................................................................................5-119 Determining the Frequency of Scheduled Updates .............................................5-120 Configuring RIP and SAP Broadcast Timers .......................................................5-121 Using Static Routes ....................................................................................................5-124 Specifying the Target Network Address ...............................................................5-126 Entering the Next-Hop Host .................................................................................5-127 117369-B Rev. 00 ix Entering the Hop Count .......................................................................................5-129 Setting the Timer Ticks ........................................................................................5-130 Using Route Filters .....................................................................................................5-131 Using SAP Filters .......................................................................................................5-133 Using SAP Filters at the Server Level ..................................................................5-136 Using SAP Filters at the Network Level ...............................................................5-138 Using Wildcards and Pattern Matching with SAP Filters ......................................5-140 Using Wildcards with SAP Filters .........................................................................5-140 Using Pattern Matching with SAP Filters .............................................................5-142 An Example of Using SAP Filters ..................................................................5-146 Service Name Filters ..................................................................................................5-147 Enabling an IPX Service Name Filter ...................................................................5-147 Entering the Target Service Name .......................................................................5-149 Entering the Target Service Type .........................................................................5-151 Setting the Filter Priority .......................................................................................5-152 Applying Filters to Inbound or Outbound Packets ................................................5-153 Specifying the Protocol ........................................................................................5-154 Specifying How to Process SAP Advertisements ................................................5-156 Specifying a Cost .................................................................................................5-157 Source Route Bridge End Station Support .................................................................5-159 IPX Ping Support ........................................................................................................5-163 Role of Bay Networks Routers in a Client/Server Connection .............................5-163 Example: Client/Server Connection via Bay Networks Router .............................5-165 Deleting IPX from the Router ......................................................................................5-167 Appendix A Site Manager IPX Parameters IPX Configuration Parameters ....................................................................................... A-1 IPXWAN Configuration Parameters ............................................................................... A-7 IPX Global Parameters .................................................................................................. A-9 IPX Advanced Global Parameters ............................................................................... A-13 IPX Interface Parameters ............................................................................................. A-22 IPX Change Circuit Parameters ................................................................................... A-30 IPX RIP Circuit Parameters ......................................................................................... A-35 IPX SAP Circuit Parameters ........................................................................................ A-41 IPX NetBIOS Static Route Configuration Parameters ................................................. A-46 x 117369-B Rev. 00 IPX NetBIOS Static Route Parameters ........................................................................ A-48 Adjacent Hosts Configuration Parameters ................................................................... A-50 IPX Adjacent Hosts Parameters .................................................................................. A-53 IPX Static Route Configuration Parameters ................................................................ A-56 IPX Static Route Parameter Descriptions .................................................................... A-59 IPX Static Service Configuration Parameters .............................................................. A-61 IPX Static Service Parameters .................................................................................... A-64 Route Filter Configuration Parameters ........................................................................ A-67 IPX Route Filter Parameters ........................................................................................ A-69 Service Network Filter Configuration Parameters ........................................................ A-74 IPX Service Network Filter Parameters ....................................................................... A-77 IPX Service Name Filter Configuration Parameters .................................................... A-82 IPX Service Name Filter Parameters ........................................................................... A-84 Appendix B BCC show Commands for IPX Sample Output ............................................................................................................... B-1 Online Help for show Commands .................................................................................. B-1 Commands for IPX ........................................................................................................ B-2 show ipx ......................................................................................................................... B-3 summary ................................................................................................................. B-3 adjacent-hosts ......................................................................................................... B-4 forwards ................................................................................................................... B-4 hosts ........................................................................................................................ B-4 interfaces ................................................................................................................. B-5 rips .......................................................................................................................... B-5 route-filters .............................................................................................................. B-6 routes ...................................................................................................................... B-6 saps ......................................................................................................................... B-7 server-name-filters .................................................................................................. B-7 server-network-filters .............................................................................................. B-8 services ................................................................................................................... B-8 static-netbios-routes ................................................................................................ B-9 static-routes ............................................................................................................. B-9 static-services ....................................................................................................... B-10 stats ....................................................................................................................... B-10 117369-B Rev. 00 xi Appendix C Common Service Types and Identifiers Appendix D Sample IPX Configuration Configuration Particulars ............................................................................................... D-2 Router 1 .................................................................................................................. D-2 Router 2 .................................................................................................................. D-3 Index xii 117369-B Rev. 00 Figures Figure 3-1. Multiple IPX Interfaces per Physical Circuit .............................................3-9 Figure 3-2. Frames Received at a Logical Interface .................................................3-12 Figure 3-3. Frames Issued from a Logical Interface .................................................3-13 Figure 4-1. Frames Received at a Logical Interface ...................................................4-9 Figure 4-2. Frames Issued from a Logical Interface .................................................4-10 Figure 4-3. IPXCP and IPXWAN Configurations ......................................................4-18 Figure 5-1. IPX Multipath ..........................................................................................5-15 Figure 5-2. IPX Multipath Routing -- Equal Least-Cost Routes ................................5-16 Figure 5-3. IPX Configurable RIP Interface Cost ......................................................5-42 Figure 5-4. IPX Configurable RIP Timers .................................................................5-49 Figure 5-5. Split Horizon Enabled in a Fully Meshed Network .................................5-55 Figure 5-6. Split Horizon Disabled in a Non-Fully Meshed Network ........................5-56 Figure 5-7. Static Service Network Configuration ....................................................5-80 Figure 5-8. IPX SAP Filters Prohibiting SAP Broadcasts .........................................5-81 Figure 5-9. NetBIOS Static Routes ..........................................................................5-91 Figure 5-10. NetBIOS Packet Filtering .....................................................................5-100 Figure 5-11. NetBIOS Packet Flow ...........................................................................5-101 Figure 5-12. NetBIOS Broadcast Filtering ................................................................5-102 Figure 5-13. Dial-on-Demand Service ......................................................................5-113 Figure 5-14. IPX Static Routes .................................................................................5-125 Figure 5-15. SAP Filtering ........................................................................................5-135 Figure 5-16. IPX Routers Source Routing across a Token Ring Network ................5-161 Figure 5-17. Sample IPX Network ............................................................................5-166 Figure A-1. IPX Configuration window ....................................................................... A-2 Figure A-2. IPXWAN Configuration Window .............................................................. A-7 Figure A-3. Edit IPX Global Parameters Window ...................................................... A-9 Figure A-4. IPX Advanced Global Parameters Window ........................................... A-13 Figure A-5. IPX Interfaces Window .......................................................................... A-22 Figure A-6. IPX Change Circuit Window .................................................................. A-31 117369-B Rev. 00 xiii Figure A-7. IPX RIP Circuit Window ........................................................................ A-35 Figure A-8. IPX SAP Circuit Window ....................................................................... A-41 Figure A-9. IPX NetBIOS Static Route Configuration Window ................................ A-46 Figure A-10. IPX NetBIOS Static Routes Window ..................................................... A-48 Figure A-11. IPX Adjacent Hosts Configuration Window ........................................... A-50 Figure A-12. IPX Adjacent Hosts Window ................................................................. A-53 Figure A-13. IPX Static Route Configuration Window ............................................... A-56 Figure A-14. IPX Static Routes Window .................................................................... A-59 Figure A-15. IPX Static Service Configuration Window ............................................. A-61 Figure A-16. IPX Static Services Window ................................................................. A-64 Figure A-17. IPX Route Filter Configuration Window ................................................ A-67 Figure A-18. IPX Route Filters Window ..................................................................... A-69 Figure A-19. IPX Service Network Filter Configuration Window ................................ A-74 Figure A-20. IPX Service Network Filters Window .................................................... A-77 Figure A-21. IPX Service Name Filter Configuration Window ................................... A-82 Figure A-22. IPX Service Name Filters Window ........................................................ A-84 Figure D-1. xiv Sample IPX Configuration ....................................................................... D-2 117369-B Rev. 00 Tables Table 2-1. LAN Circuit and Frame Support for IPX Interfaces ..................................2-4 Table 2-2. WAN Circuit and Frame Support for IPX Interfaces .................................2-4 Table 4-1. Configuration Table for IPX over WAN Media .......................................4-20 Table 5-1. Characters in SAP Pattern-Matching Filters .......................................5-142 Table 5-2. Concatenation Rules and Operators ...................................................5-144 Table B-1. IPX Show Commands ............................................................................. B-2 Table C-1. Service Types and Identifiers ................................................................. C-1 117369-B Rev. 00 xv About This Guide If you are responsible for configuring IPX, you need to read this guide. You can now use the Bay Command Console (BCC™) to configure this protocol on a router. In this guide, you will find instructions for using both the BCC and Site Manager. There are a few parameters which you cannot yet configure with the BCC, and, in these cases, you must use Site Manager. If you want to Go to Start IPX on a router and get it running with default settings for parameters. Chapter 1 Learn about the IPX protocol and special aspects of the Bay Networks Chapter 2 implementation of IPX. Enable IPX over LAN media. Chapter 3 Enable IPX over WAN media. Chapter 4 Customize IPX operation to suit your needs. Chapter 5 Obtain information about Site Manager parameters. (This is the same Appendix A information you obtain using Site Manager online Help.) 117369-B Rev. 00 Obtain a description of BCC show scripts. Appendix B Obtain a listing of the common service types and identifiers. Appendix C View a sample IPX configuration. Appendix D xvii Configuring IPX Services Before You Begin Before using this guide, you must complete the following procedures. For a new router: • Install the router (refer to the installation manual that came with your router). • Connect the router to the network and create a pilot configuration file (refer to Quick-Starting Routers, Configuring BayStack Remote Access, or Connecting ASN Routers to a Network). Make sure that you are running the latest version of Bay Networks® Site Manager and router software. For instructions, refer to Upgrading Routers from Version 7–11.xx to Version 12.00. Conventions angle brackets (< >) Indicate that you choose the text to enter based on the description inside the brackets. Do not type the brackets when entering the command. Example: if command syntax is ping, you enter ping 192.32.10.12 bold text Indicates text that you need to enter, command names, and buttons in menu paths. Example: Enter wfsm & Example: Use the dinfo command. Example: ATM DXI > Interfaces > PVCs identifies the PVCs button in the window that appears when you select the Interfaces option from the ATM DXI menu. xviii italic text Indicates variable values in command syntax descriptions, new terms, file and directory names, and book titles. quotation marks (“ ”) Indicate the title of a chapter or section within a book. screen text Indicates data that appears on the screen. Example: Set Bay Networks Trap Monitor Filters 117369-B Rev. 00 About This Guide separator ( > ) Separates menu and option names in instructions and internal pin-to-pin wire connections. Example: Protocols > AppleTalk identifies the AppleTalk option in the Protocols menu. Example: Pin 7 > 19 > 20 vertical line (|) Indicates that you enter only one of the parts of the command. The vertical line separates choices. Do not type the vertical line when entering the command. Example: If the command syntax is show at routes | nets, you enter either show at routes or show at nets, but not both. Acronyms 117369-B Rev. 00 AUI Attachment Unit Interface ARE All-Routes Explorer (frame) ATM asynchronous transfer mode BootP Bootstrap Protocol BRI Basic Rate Interface CCITT International Telegraph and Telephone Consultative Committee (now ITU-T) CSMA/CD carrier sense multiple access with collision detection DLCI data link control layer (Layer 2 of SNA) DLCMI Data Link Control Management Interface GNS get nearest server GUI graphical user interface HDLC high-level data link control IP Internet Protocol IPX Internet Packet Exchange Service IPXCP Internetwork Packet Exchange Control ISDN Integrated Services Digital Network ISO International Organization for Standardization ITU-T International Telecommunication Union–Telecommunications (formerly CCITT) LAN local area network xix Configuring IPX Services xx LSAP link service access point MAC media access control MAU media access unit MDI-X Media-Dependent Interface with Crossover MIB management information base NBMA nonbroadcast multi-access NCP Network Control Protocol NDS NetWare Directory Services NIC Network Information Center or network interface card OSI Open Systems Interconnection OSPF Open Shortest Path First (Protocol) PDN Public Data Network PNN primary network number PPP Point-to-Point Protocol PROM programmable read-only memory RIF routing information field RIP Routing Information Protocol SAP Service Advertisement Protocol SMDS switched multimegabit data service SNAP Subnetwork Access Protocol SNMP Simple Network Management Protocol SPX Sequenced Packet Exchange SRE specific route explore STP shielded twisted pair TCP/IP Transmission Control Protocol/Internet Protocol TFTP Trivial File Transfer Protocol TPE twisted pair Ethernet UTP unshielded twisted pair WAN wide area network XNS Xerox Networking System 117369-B Rev. 00 About This Guide Bay Networks Technical Publications You can now print technical manuals and release notes free, directly from the Internet. Go to support.baynetworks.com/library/tpubs. Find the Bay Networks products for which you need documentation. Then locate the specific category and model or version for your hardware or software product. Using Adobe Acrobat Reader, you can open the manuals and release notes, search for the sections you need, and print them on most standard printers. You can download Acrobat Reader free from the Adobe Systems Web site, www.adobe.com. Documentation sets and CDs are available through your local Bay Networks sales office or account representative. Bay Networks Customer Service You can purchase a support contract from your Bay Networks distributor or authorized reseller, or directly from Bay Networks Services. For information about, or to purchase a Bay Networks service contract, either call your local Bay Networks field sales office or one of the following numbers: Region Telephone number Fax number United States and Canada 800-2LANWAN; then enter Express Routing 978-916-3514 Code (ERC) 290, when prompted, to purchase or renew a service contract 978-916-8880 (direct) Europe 33-4-92-96-69-66 33-4-92-96-69-96 Asia/Pacific 61-2-9927-8888 61-2-9927-8899 Latin America 561-988-7661 561-988-7550 Information about customer service is also available on the World Wide Web at support.baynetworks.com. 117369-B Rev. 00 xxi Configuring IPX Services How to Get Help If you purchased a service contract for your Bay Networks product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you purchased a Bay Networks service program, call one of the following Bay Networks Technical Solutions Centers: Technical Solutions Center Telephone number Fax number Billerica, MA 800-2LANWAN 978-916-3514 Santa Clara, CA 800-2LANWAN 408-495-1188 Valbonne, France 33-4-92-96-69-68 33-4-92-96-69-98 Sydney, Australia 61-2-9927-8800 61-2-9927-8811 Tokyo, Japan 81-3-5402-0180 81-3-5402-0173 Bay Networks Educational Services Through Bay Networks Educational Services, you can attend classes and purchase CDs, videos, and computer-based training programs about Bay Networks products. Training programs can take place at your site or at a Bay Networks location. For more information about training programs, call one of the following numbers: Region Telephone number United States and Canada 800-2LANWAN; then enter Express Routing Code (ERC) 282 when prompted 978-916-3460 (direct) xxii Europe, Middle East, and Africa 33-4-92-96-15-83 Asia/Pacific 61-2-9927-8822 Tokyo and Japan 81-3-5402-7041 117369-B Rev. 00 Chapter 1 Starting IPX Services IPX is the network-layer routing protocol used in the NetWare environment. The primary tasks of IPX are addressing, routing, and switching information packets from one location to another on a network. If you are already familiar with IPX and want to get the protocol up and running quickly, follow the steps below to start IPX using Bay Networks default settings. You supply only the necessary configuration settings and accept all other default settings. For conceptual information on IPX, refer to Chapter 2. For information on customizing the way IPX runs on the router to meet your needs, refer to Chapters 3 through 5. For information on changing the default settings, refer to Appendix B. Starting the Configuration Tools Before configuring IPX services, refer to the following user guides for instructions on how to start and use the Bay Networks configuration tool of your choice. Configuration Tool User Guide Bay Command Console (BCC™) Using the Bay Command Console Site Manager Configuring and Managing Routers with Site Manager These guides also describe generally how to create and modify a device configuration. 117369-B Rev. 00 1-1 Configuring IPX Services Starting IPX IPX can operate over LAN or WAN media. This section describes how to get IPX and, optionally, IPXWAN services up and running on a circuit. We assume that you have read Configuring and Managing Routers with Site Manager. Using the BCC 1. Decide where you want IPX to operate. IPX can run: 2. • Globally on the router • On an individual interface • Over a WAN protocol Start IPX with supplied default values. • Globally on the router: To start IPX globally on the router, navigate to the box level prompt and enter: box# • ipx On an interface: a. Configure a physical interface on an available slot/connector. To configure a physical interface on a slot and connector, navigate to the top-level box prompt and enter: interface_type slot slot_number connector connector_number interface_type is the name of a link module on the router. slot_number is the number of the slot on which the link module is located. connector_number is the number of a connector on the link module. After you configure a physical interface, the BCC returns a prompt that specifies your current working location. For example, the following command configures an Ethernet interface on slot 1, connector 2: box# ethernet ethernet/1/2# 1-2 slot 1 connector 2 117369-B Rev. 00 Starting IPX Services b. Configure an IPX interface on the physical interface. To configure an IPX interface on a physical interface, navigate to the prompt for the physical interface and enter: ipx address address address is any valid address in hexadecimal notation. For example: ethernet/2/4# ipx/19d7e712# c. ipx 19d7e712 Over a WAN protocol. To configure IPX over a WAN protocol, navigate to the box prompt, configure a WAN protocol and then configure IPXWAN by entering: ipxwan address ipxwan_address router-name name primary-network address negotiated-protocol protocol ipxwan_address is the address, in hexadecimal notation, of the IPXWAN interface. name is the symbolic name of the router. address is the address, in hexadecimal notation, of the primary network. protocol is one of the following: wan-rip unnumbered-rip wan-unnumbered-rip 117369-B Rev. 00 1-3 Configuring IPX Services 3. Use IPX. After you supply the required settings to configure IPX globally, on a LAN interface, or on a WAN interface, IPX is completely configured with supplied default values. You can use IPX with the current default settings or you can customize IPX to meet your needs. To determine which IPX interface attributes that you can configure and what their current values are, enter the info command. For example, on a LAN interface, if you enter the info command you will get the following results: ipx/19d7e712# info state enabled encapsulation lsap address 0000f7f7 circuit-name {} host-address 0x broadcast-address 0x multicast-address 0x cost 0 netbios-accept disabled netbios-deliver disabled delay 0 throughput 0 stabilization-timer 0 svcbroadcast disabled To determine what other services you can enable under IPX, enter the help tree command and the BCC will display available services. For example, if you configure IPX on a LAN interface and enter the help tree command, you will get the following results: ipx/19d7e712# help tree The configuration tree below this context is: rip sap static-route adjacent-host static-service route-filter server-network-filter server-name-filter 1-4 117369-B Rev. 00 Starting IPX Services Each service under IPX has configurable attributes. To determine what these arrtibutes are, enter the service name followed by a question mark. The BCC supplies returns any information required to configure the service, as well as a list of configurable attributes. For example, to determine what settings you must supply to configure a static route, enter the static-route ? command and you will get the following results: ipx/19d7e712# static-route ? Usage: "static-route target-network next-hop-host " Or: "static-route / " Parameters of static-route: hops on target-network next-hop-host state ticks You must use this command for each service available under IPX. Using Site Manager To start IPX using Site Manager, follow these steps: 1. Select Configuration Manager in local, remote, or dynamic mode from the Tools menu. The Configuration Manager window appears. 2. Open a configuration file if local or remote mode is selected. 3. Select the circuit you want to configure. If this is a local mode configuration, specify router hardware. 4. Select a protocol. If you are running IPX over a WAN, select a WAN protocol (usually PPP or frame relay). Note: Selecting frame relay, PPP, or SMDS on a WAN circuit automatically enables protocol prioritization. 117369-B Rev. 00 1-5 Configuring IPX Services 5. Select IPX or RIP/SAP (which automatically selects IPX as well) from the Select Protocols window. If you selected RIP/SAP from the Select Protocols window, the router enables both RIP and SAP services using their default values. To change any of these default values, refer to Appendix B. The IPX Configuration window appears. 6. Complete the IPX Configuration window. If you are configuring a LAN or WAN circuit, you must supply the following information: • A configured network number. A configured network number is any valid IPX network address in hexadecimal notation. If you are configuring this interface as Unnumbered RIP, supply the value zero for the configured network number. If you are trying to establish a connection to a Series 5 Bay Networks router, or a router that does not implement IPXWAN or PPP, then you must enter a nonzero network address (for example, the network address of the link). If you are configuring an IPX interface that will enable IPXWAN services, do not supply a configured network number. If you are using Site Manager, you can specify the configured network number by configuring the Configured Network Number (hex) parameter described on page A-2. • The encapsulation method. By default, IPX supplies an encapsulation method that is media dependent. The encapsulation method supports communication on a specific logical link. Check to make sure that the supplied encapsulation method matches the one the clients and servers on the same logical network use, and is appropriate for the physical circuit, as follows: -- Ethernet circuits support Ethernet, LSAP, Novell, and SNAP frames. -- Token ring circuits support LSAP and SNAP frames. -- Synchronous circuits (V.35, RS-232/V.24, RS-422/423, X.21, T1/E1) support SNAP, PPP, and X.25 Point-to-Point (Ethernet) frames. 1-6 117369-B Rev. 00 Starting IPX Services -- FDDI circuits support LSAP and SNAP frames. -- HSSI circuits support PPP and SNAP frames. -- ISDN circuits support PPP frames. If you are using Site Manager, you can specify the encapsulation method by configuring the Configured Encaps parameter described on page A-4. If you are configuring an IPXWAN circuit, you must also supply the following information: • A common network number. The common network number is a network number that you assign to the WAN circuit. If this router is the master during the IPXWAN negotiation and RIP is selected as the routing protocol, then the common network number is used as the IPX network number for the circuit. There is no default for the common network number. You must supply an IPX common network number in hexadecimal format. Valid common network numbers range from 0x00000000 to 0xFFFFFFFD. Do not use the value 0xFFFFFFFE or 0xFFFFFFFF as network numbers. These values are reserved for system use. If you are using Site Manager, you can specify the common network number by configuring the Common Network Number parameter described on page A-5. • A negotiated protocol. The negotiated protocol specifies the protocol that the router supports for the exchange of routing information over this WAN circuit. You can specify either RIP or Unnumbered RIP as the negotiated protocol. For a description of RIP, refer to Chapter 5. If you are using Site Manager, you can specify the negotiated protocol by configuring the Negotiated Protocol(s) parameter described on page A-6. 7. Click on OK. If you did not enable IPXWAN services, IPX is now completely configured using the information you supplied and all other supplied default values. You can now use IPX. If you want to change any of the supplied defaults to fine-tune the way IPX works, refer to Appendix A. 117369-B Rev. 00 1-7 Configuring IPX Services If you enabled IPXWAN services in the IPX Configuration window, the IPXWAN Configuration window appears. You must supply the following information: • A router name. The router name is any symbolic name that you choose for the router. You must choose a name that is unique among those assigned to IPX file servers and routers anywhere in the IPX internetwork. Any IPXWAN (RFC1634-compliant) interface in the node uses this name to identify itself to the IPX router or server at the opposite end of the WAN data link. If you are using Site Manager, you can specify the router name by configuring the Router Name parameter described on page A-7. • A primary network number. A primary network number is a unique string of up to 8 hexadecimal characters that specifies an IPX network number for IPXWAN link negotiation on all slots. You can enter any unused value between 0x00000001 and 0xFFFFFFFD. The value you enter for the primary network number determines whether the local or remote router on the WAN circuit serves as the IPX Link Master. The node with the highest primary network number becomes the IPX Link Master. If you are using Site Manager, specify the primary network number using the Primary Net Number (hex) parameter described on page A-8. 8. 1-8 Click on OK. 117369-B Rev. 00 Chapter 2 IPX Concepts This chapter describes some IPX concepts you will need to know before you begin configuring an interface on a circuit. This chapter provides an overview of the IPX protocol, the network-level services provided by a Bay Networks router running IPX, the types of LAN and WAN circuits IPX supports, and some basic types of IPX configurations. Compatibility with Previous Versions of Bay Networks Software This guide describes only BayRS Version 12.20. Site Manager 6.20 and BayRS Version 12.20 are backward compatible with earlier versions of the router code. You can boot an IPX configuration that operates with an earlier version (for example, 11.xx) on a router that has Version 12.20 software, and the software will update the configuration. You can then go into dynamic mode (or save the updated configuration and go into remote mode) and edit any of the new parameters. When you save the edited configuration, you are saving a Version 12.20 file. In local mode, Site Manager will run IPX configurations from an earlier version using the management information base (MIB) for that version instead of the MIB for Version 12.20. If you choose to continue using a router configuration that you configured under a software version earlier than 12.20 without updating it, you will not get the Version 12.20 features, and you must use the Version 11.xx guide Configuring IPX Services instead of this guide. 117369-B Rev. 00 2-1 Configuring IPX Services About the IPX Protocol The Internet Packet Exchange protocol is the Novell, Inc., adaptation of the Xerox Networking System (XNS) protocol. IPX has the following characteristics: • It is a connectionless datagram delivery protocol. Connectionless means that it does not need a channel established for packet delivery. A datagram is a unit of data that contains all the addressing information required for it to be delivered to its destination. The path or route that one datagram follows to reach a destination is independent of the path or route that another datagram may follow to reach the same destination. • It does not guarantee the delivery of packets. Higher-level protocols assume the responsibility for reliability. The higher-level protocols that IPX uses are SPX and NCP. • It uses the Internet Data Packet (IDP) format. IPX is the network-layer routing protocol used in the NetWare environment. The primary tasks of IPX are addressing, routing, and switching information packets from one location to another on a network. The network interface card (NIC) in a client provides network node addressing. IPX defines the internetwork and intranode addressing as follows: • Network numbers form the basis of the IPX internetwork addressing scheme for sending packets between network segments. Every network segment of an internetwork is assigned a unique network address by which routers forward packets to their final destination network. A network number in the NetWare environment consists of 8 hexadecimal characters. In the following example, 0x indicates that this is a hexadecimal number, and n is any hexadecimal character. 0xnnnnnnnn • 2-2 Socket numbers are the basis for an IPX intranode address; that is, the address of an individual entity within a node. They allow a process (for example, RIP or SAP) to distinguish itself to IPX. To be able to communicate on the network, the process must request a socket number. Any packets IPX receives addressed to that socket are then passed on to the process within the node. 117369-B Rev. 00 IPX Concepts Network-Level Services A Bay Networks router running IPX provides the following network-level support: • Dynamic routing of IPX packets • Multiple IPX interfaces per circuit • IPX over WAN media • IPXWAN and IPXCP • Routing Information Protocol (RIP and Unnumbered RIP) • Service Advertising Protocol (SAP) • Static Route support • Default Route support • Adjacent Host support • Dial-on-Demand support Dynamic routing occurs normally on any IPX interface; brief descriptions of the other supported capabilities follow. Supported LAN Circuits, WAN Circuits, and Frame Formats IPX supports various combinations of physical circuits and data link layer frame formats. You can choose the ones that are appropriate for the types of clients and applications on your network. 117369-B Rev. 00 2-3 Configuring IPX Services Table 2-1 shows the types of LAN circuits and frame formats supported by Bay Networks routers running IPX. Table 2-1. LAN Circuit and Frame Support for IPX Interfaces Frame Type -Novell Terminology Frame Type -Bay Networks Terminology Ethernet ETHERNET_II ETHERNET_802.2 ETHERNET_802.3 ETHERNET_SNAP ETHERNET LSAP NOVELL SNAP Token ring TOKEN-RING TOKEN-RING_SNAP LSAP SNAP FDDI N/A LSAP SNAP Circuit Type Table 2-2 shows the relationships between different WAN circuits,WAN protocols, and frame formats supported by Bay Networks routers running IPX. Table 2-2. WAN Circuit and Frame Support for IPX Interfaces WAN Protocol Frame Format -Bay Networks Terminology --V.35 --RS-232/V.24 --RS-422/423 --X.21 --T1/Fractional T1 --E1/Fractional E1 ATM Frame Relay PPP SMDS X.25 Point-to-Point X.25 PDN Bay Networks Point-to-Point SNAP SNAP PPP SNAP ETHERNET RFC 1356 ETHERNET HSSI ATM Frame Relay PPP SMDS Bay Networks Point-to-Point SNAP SNAP PPP SNAP ETHERNET ISDN PPP PPP Circuit Type Synchronous: 2-4 117369-B Rev. 00 IPX Concepts You can use these tables when you select an encapsulation method on the IPX Configuration window. For more information about the encapsulation method, refer to “Configured Encaps” on page A-4. Types of IPX Configurations The basic types of IPX configurations are: • Standard, with two possible configurations: -- Multiple-Host Router. This common configuration supports one IPX interface per circuit; each interface has a unique IPX host number. -- Single-Host Router. This configuration supports one IPX interface per circuit; every interface shares the same global (“boxwide”) IPX host number. • Special, also with two possible configurations: -- Multiple Interfaces per Circuit. This special configuration supports as many IPX interfaces per circuit as there are frame encapsulation types for the given circuit type. -- Multiple Circuits per Segment. This special configuration supports either concurrent bridging and IPX routing or IPX multiline. For More Information About IPX The following documents provide technical details about IPX protocol implementation. RFC 1634: Novell IPX over Various WAN Media (IPXWAN). (Supersedes RFC 1551 and RFC 1362.) RFC 1552: The PPP Internetwork Packet Exchange Control Protocol (IPXCP). Novell, Inc. Advanced NetWare, V.2.0 Internet Packet Exchange Protocol (IPX) with Asynchronous Event Scheduler. March 19, 1986. Novell, Inc. IPX Router Specification. October 1993. Chappell, Laura and Dan E. Hawkes. Novell’s Guide to NetWare LAN Analysis, Novell Press/Sybex. 1994 117369-B Rev. 00 2-5 Chapter 3 Customizing IPX for LAN Media You can use IPX services over either a LAN or a WAN. This chapter relates specifically to using IPX over a LAN. For information specific to using IPX over a WAN, see Chapter 4. For information about customizing IPX features for both a LAN and a WAN, see Chapter 5. When you configure an IPX service to run over a LAN, make sure you have supplied the appropriate settings in the IPX configuration for: • IPX network number assigned to the IPX circuit • RIP • SAP • The encapsulation method used for each circuit type • Circuit identifier value (Sit manager only) To configure multiple IPX interfaces on a circuit, as well as a multiple-host router, you must also: 117369-B Rev. 00 • Enable IPX globally on the router. • Enable multiple host addressing. • Supply a host number. 3-1 Configuring IPX Services Assigning a Unique Network Number When you initially add an IPX interface to the router configuration, enter a network number for the IPX network segment associated with that interface. The network number must be unique among all other network numbers assigned throughout the IPX internetwork. Using the BCC You can specify a network number only when you first configure an IPX interface. To configure an IPX interface, navigate to the circuit prompt (for example, box; ethernet 2/1) and enter: ipx address address address is the address, in hexadecimal notation, of the ipx interface. For example, to specify the address as 0x00065656, enter: ipx/00045678# ipx address 0x00065656 Note: You cannot change the network number using the BCC after you have configured IPX on an interface. 3-2 117369-B Rev. 00 Customizing IPX for LAN Media Using Site Manager To specify a network number for the IPX network segment associated with an interface, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Configured Network Number (hex) parameter. Click on Help or see the parameter description on page A-2. 5. Click on OK. You return to the Configuration Manager window. Enabling RIP and SAP on an Interface The Configuration Manager sets the default for this parameter based on your selection in the Select Protocols window. If you selected RIP/SAP, both RIP and SAP are enabled. You can disable both RIP and SAP using the IPX Configuration window. You can also disable and reenable just RIP or just SAP using the RIP Circuit window or the SAP Circuit window, both of which are available via the IPX Interfaces window. Using the BCC To enable RIP, you must first configure RIP on an IPX interface. By default, RIP is enabled when you first configure it on an interface. To configure RIP on an IPX interface, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: rip If you already configured RIP on an interface, you can change its current state. To disable RIP on an interface, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: state disabled 117369-B Rev. 00 3-3 Configuring IPX Services To enable RIP, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: state enabled To enable SAP, you must first configure SAP on an IPX interface. By default, SAP is enabled when you first configure it on an interface. To configure SAP on an IPX interface, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: sap If you already configured RIP on an interface, you can change its current state. To disable RIP on an interface, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: state disabled To enable RIP, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: state enabled Using Site Manager To enable or disable both RIP and SAP services at the same time, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the RIP/SAP parameter. Click on Help or see the parameter description on page A-3. 5. Click on OK. 3-4 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX for LAN Media You can also enable or disable RIP or SAP services separately. To enable or disable only RIP services, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The RIP Circuit window opens. 5. Set the Enable parameter. Click on Help or see the parameter description on page A-36. 6. Click on OK. You return to the Configuration Manager window. To enable or disable SAP services only, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The SAP Circuit window opens. 5. Set the Enable parameter. Click on Help or see the parameter description on page A-41. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 3-5 Configuring IPX Services Choosing a Frame Encapsulation Type When you add an IPX interface to the router configuration, you must specify the type of frame encapsulation required for communication between all hosts on the same IPX logical network within the overall IPX internetwork. Choose the encapsulation method that matches the one the clients and servers on the same logical network use and is appropriate for the physical circuit you are configuring: 3-6 • Ethernet circuits support Ethernet, LSAP, Novell, and SNAP frames. • Token ring circuits support LSAP and SNAP frames. • Synchronous circuits (V.35, RS-232/V.24, RS-422/423, X.21, T1/E1) support SNAP, PPP, and X.25 Point-to-Point (Ethernet) frames. • FDDI circuits support LSAP and SNAP frames. • HSSI circuits support PPP and SNAP frames. • ISDN circuits support PPP frames. 117369-B Rev. 00 Customizing IPX for LAN Media Using the BCC To specify the encapsulation method, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: encapsulation method method is one of the following: lsap ethernet novell snap ppp For example, the following command uses lsap as the encapsulation type: encapsulation lsap Using Site Manager To specify the encapsulation method, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Configured Encaps parameter. Click on Help or see the parameter description on page A-4. 5. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 3-7 Configuring IPX Services Specifying Multiple Interfaces per Circuit You can configure one or more IPX interfaces per physical circuit. The number of IPX logical interfaces you can configure on a circuit equals the number of unique frame formats available for that circuit type. (Refer to Table 2-1 for details on circuit types and frame formats.) For example, the Bay Networks router supports four unique frame formats that are suitable for communication over an Ethernet LAN segment. This means that you can configure four different encapsulations for four independent IPX interfaces on a single Ethernet circuit (Ethernet, Novell, LSAP, and SNAP). Each interface and encapsulation configured on a circuit supports a different logical network. To differentiate between IPX interfaces configured on the same physical circuit, the Bay Networks router uses the unique network address and frame format that you assign to each interface. By supporting multiple IPX interfaces on a single physical circuit, a Bay Networks router can service clients on independent logical LANs that coexist on the same physical LAN segment. In Figure 3-1, each client on the right side of the router has a different logical network address and uses a different encapsulation method. If all clients need to access server 1, then only interface 2 of the router needs to support all the different encapsulation methods and multiple logical network addresses for the workstations. Interface 1 of the router needs to support only the SNAP encapsulation method that server 1 supports. 3-8 117369-B Rev. 00 Customizing IPX for LAN Media Real address Encapsulation method Encapsulation method SNAP 0x00000110 SNAP 0x00000111 Novell 0x00000112 LSAP 0x00000113 Ethernet 0x000F123 Server 1 Interface 1 Interface 2 IPX0001A Figure 3-1. Multiple IPX Interfaces per Physical Circuit Note: NetWare users -- If you are upgrading client and server stations on your network to Novell NetWare Version 4.x, you can use the multiple-interface-per-circuit capability to gradually migrate stations on the same network segment to NetWare Version 4.x (that is, from one logical network to another, independent logical network). For example, you can upgrade and migrate NetWare clients from a logical network that supports only Novell (802.3) encapsulated frames to a logical network that supports a more versatile LSAP (802.2 frame type). Choose the following encapsulation methods that are appropriate for the type of physical circuit you are configuring: 117369-B Rev. 00 3-9 Configuring IPX Services • Ethernet circuits support Ethernet, LSAP (802.2), Novell (802.3), and SNAP frames. • Token ring circuits support LSAP and SNAP frames. • FDDI circuits support LSAP and SNAP frames. To enable or disable IPX routing on the router, see Chapter 1. To specify the encapsulation method, see “Choosing a Frame Encapsulation Type” on page 3-6. For more information about configuring a physical LAN circuit, refer to Configuring and Managing Routers with Site Manager. Using the BCC To configure multiple interfaces on a single circuit, you must specify a unique encapsulation type for each interface. To configure multiple interfaces, navigate to the circuit prompt (for example, box; ethernet 2/1) and enter: ipx address address; encapsulation method address is the address, in hexadecimal notation, of the ipx interface. method is one of the following: lsap ethernet novell snap ppp For example, to configure two interfaces on a single circuit, enter: ipx 0x0001; encapsulation lsap 2/1# ipx 0x0002; encapsulation ethernet ethernet 2/1# ethernet 3-10 117369-B Rev. 00 Customizing IPX for LAN Media Using Site Manager Site Manager automatically assigns a circuit identifier to each circuit that you create on an IPX router. You can assign a specific circuit identifier, if necessary. To assign a circuit identifier, complete these tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interface window opens. 4. Set the Circuit Index parameter. Click on Help or see the parameter description on page A-4. 5. Click on OK. You return to the Configuration Manager window. Configuring a Multiple-Host Router A multiple-host router is a common configuration that supports one IPX interface per circuit, and each interface has a unique IPX host number. For this configuration, enable multiple host addressing. The host number of each IPX interface is based on the MAC address of the underlying circuit. For Ethernet or FDDI circuits, you can specify the multiple-host address. See “Host Address (hex)” on page A-51. Configuring a Single-Host Router For this configuration, disable multiple-host addressing. Every IPX interface in the router configuration uses the same global host number, which is one of the following: 117369-B Rev. 00 • A number derived from the router backplane • A number that you enter 3-11 Configuring IPX Services You specify the source for the host number by entering a host number in hexadecimal notation. (If you do not enter a number, the router derives the internal serial number from the router backplane, and uses this number for the global host number.) IPX Host ID Numbers On Bay Networks routers, the IPX host ID number maps to a physical data link layer address (on a specific circuit or physical interface). An IPX logical interface can listen at this address and capture frames transmitted by nodes compatible with IPX on the local data link. Figure 3-2 illustrates this concept in a Bay Networks router that has two IPX logical interfaces, each one configured on a different physical circuit. Local clients/servers IPX server Logical interface Incoming frames Physical interface ATM circuit Ethernet circuit Clients Router ATM Incoming cells Physical interface Logical interface IPX server = Destination (Receive) address IPX0021A Figure 3-2. Frames Received at a Logical Interface Nodes (IPX compatible) on the same logical network and locally attached physical segment must use the host ID number of the IPX logical interface as a data link layer destination address, through which any transmitted frames can ultimately reach their target client or server applications. 3-12 117369-B Rev. 00 Customizing IPX for LAN Media Because an IPX logical interface can receive and send data, the host ID also identifies a source data link layer address from which the interface can send frames to nodes compatible with IPX anywhere else in the same IPX internetwork. Figure 3-3 illustrates this concept in a Bay Networks router configured with two IPX logical interfaces, each one on a different physical circuit type. Local clients/servers Logical interface IPX server ATM circuit Outgoing frames Ethernet circuit Physical interface Router Clients ATM Outgoing cells Physical interface Logical interface IPX server = Source (Transmit) address IPX0022A Figure 3-3. Frames Issued from a Logical Interface Setting a Host ID Number for IPX on a Token Ring Circuit In a configuration with IPX logical interfaces on a token ring circuit, the data link layer address is a MAC-layer address. In Bay Networks routers, you set the MAC-layer address for the circuit and the host ID number for the IPX interface independently. However, the host ID number for every IPX logical interface on a given token ring circuit must be identical to the MAC address set for that circuit. Otherwise, the logical interface would send frames that contained an incorrect source MAC address, or the interface would listen for frames at the wrong MAC address. 117369-B Rev. 00 3-13 Configuring IPX Services Using the BCC To specify the host ID, navigate to the global IPX prompt (for example, box; ipx) and enter: host-address address address is the host address in hexadecimal format. For example, to set the host ID to 0x09873452, enter: ipx# host-address 0x000009873452 Using Site Manager To specify the host ID, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The IPX Global Parameters window opens. 4. Set the Router Host Number (hex) parameter. Click on Help or see the parameter description on page A-11. 5. Click on OK. 3-14 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX for LAN Media Token Ring MAC Address Selection For token ring circuits, you can select the means by which the router determines the MAC address for a circuit to one of the following: • PROM. (This is the default setting.) The circuit retrieves the MAC address that is stored in a PROM on the supporting link module. • BOXWIDE. The circuit generates a MAC address based on the serial number of the backplane of the router. Caution: The IPX boxwide host address and the token ring MAC address must agree when the multiple host addressing is disabled. • CNFG. You can configure a MAC address. Caution: Changing the the way the router determines the MAC address to accommodate IPX configuration requirements can affect other protocol interfaces (for example, LNM Servers or IP) configured on the same circuit(s) with IPX. If necessary, make adjustments to any such (non-IPX) interfaces configured on the router. If you choose the CNFG, you must subsequently enter a valid MAC address override setting. You must repeat this procedure on any token ring circuit for which you choose CNFG (user configured) as the source for the MAC address assigned to the individual physical circuit. For instructions on how to set the MAC address and the MAC address override, see Configuring Ethernet, FDDI, and Token Ring Services. Customizing IPX After selecting a circuit and providing the basic IPX settings, your circuit will be operational. The default values supplied for the remaining settings will apply to most environments. However, if you want to customize your IPX configuration, refer to Chapter 5. 117369-B Rev. 00 3-15 Chapter 4 Customizing IPX for WAN Media You can use IPX services over either a LAN or a WAN. This chapter relates specifically to customizing IPX for use over a WAN. For information specific to using IPX over a LAN, see Chapter 3. For information about customizing IPX features for both LANs and WANs, see Chapter 5. IPX over WAN Media You can establish an IPX connection over any of the WAN media types supported by the Bay Networks IPX router (refer to Table 2-2). The choice of protocols depends on the type of connection and what you want the protocol to do. The WAN protocol PPP uses the IPXCP protocol (RFC 1552). IPXCP supports the routing of IPX packets over wide area links that support only the Point-to-Point Protocol. IPXCP is a data link protocol that is part of PPP. To enable IPXCP, you must first configure the interface to support PPP. For instructions on how to do this, refer to Configuring PPP Services. For the ATM, SMDS, X.25 PDN, X.25 Point-to-Point, and Bay Networks Point-to-Point protocols, once you choose the protocol, only one encapsulation method is allowed for all WAN protocols. For the Frame Relay and PPP WAN protocols, you can optionally run IPXWAN (RFC 1634). Note: Use IPXCP or IPXWAN when you want the routers to negotiate the options required for communication over the WAN link. Alternatively, you can explicitly specify the values for the WAN link without using either IPXCP or IPXWAN, as long as you ensure that what you configure at each end of the link is compatible. 117369-B Rev. 00 4-1 Configuring IPX Services Using IPXCP and IPXWAN Incorporating IPXWAN in the Bay Networks router provides the following benefits: • Adherence to RFCs 1362 and 1634 IPXWAN protocols developed by Novell • A common link negotiation method for WAN media (Frame Relay and PPP) • Interoperability with other routing vendors (for example, Novell) • A standardized means for tick-based routing over WAN media If you configure a local and a remote node to support both IPXCP and IPXWAN, IPXCP always runs first. After the router completes IPXCP negotiation, it discards all IPXCP-negotiated options, and IPXWAN runs. Refer to “Assigning a Unique Network Number” on page 4-4 for more information about specifying support for IPXCP and IPXWAN. Running IPXWAN over PPP IPX uses PPP when operating over point-to-point synchronous networks. With PPP, establishing a connection means that the IPX Control Protocol (NCP) (IPXCP) reaches the open state. PPP lets either side of a connection stop forwarding IPX packets if one end sends an IPXCP terminate request. When a router detects this, it immediately reflects the lost connection in its routing information database. 4-2 117369-B Rev. 00 Customizing IPX for WAN Media Running IPXWAN over Frame Relay Permanent Virtual Circuits Each IPX packet is encapsulated in a Frame Relay frame. When an interface is restarted, IPXWAN exchanges begin immediately over active, direct mode Frame Relay PVCs (those that have remained active before and after restart). • When a router detects that a direct mode Frame Relay PVC has gone from an inactive to an active state, the connection is established; and IPXWAN packet exchange over this newly activated connection begins. • When an active PVC becomes inactive, the router reflects the lost connection in its routing information database. Note: For IPX, you can use Frame Relay’s direct, group, or hybrid mode. For IPXWAN, only direct mode is valid. In Frame Relay, direct mode is a point-to-point connection. Frame Relay group mode (or hybrid mode) involves a point-to-multipoint connection. Negotiating an IPXWAN Connection Establishing an IPXWAN connection involves negotiating which router will be the server. Being the server does not include any special privileges; it indicates which router is the requestor in the ensuing request/response exchanges. A router retains its role -- server or client -- for the remainder of the IPXWAN exchanges. The following options are determined after successful negotiation by the IPXWAN protocol: 117369-B Rev. 00 • WAN link delay used in tick-based routing across the WAN link • Network number for the WAN link • Routing protocol to be implemented over the WAN link 4-3 Configuring IPX Services Configuring an IPX Service to Run over a WAN When you configure IPX over WAN media, you can either configure IPX over a WAN protocol or you can configure IPXWAN services. When configuring IPX over WAN media, make sure you perform the following tasks: • Supply a configured network number (required if IPXWAN is disabled) • Supply appropriate settings for RIP • Supply appropriate settings for SAP • Supply a circuit index (Site Manager only) • Supply the common network number (required for IPXWAN) • Supply the negotiated protocols (required for IPXWAN) In addition, you must also: • Enable IPX globally on the router • Enable multiple host addressing • Supply the router name (required for IPXWAN) • Supply the primary network number (required for IPXWAN) If you are running IPX over an ATM network, you should set the Host Number on the IPX Interfaces window. Assigning a Unique Network Number When you initially add an IPX interface to the router configuration, you must enter the network number of the IPX network segment associated with that interface. You should specify a network number of zero if you are configuring interfaces with unnumbered point-to-point links, and if IPXWAN is not enabled. When the router recognizes a network number of zero, it knows that a lower protocol layer (IPXWAN or IPXCP) on the same circuit must negotiate with the remote IPX host for the network number of the intervening WAN segment. 4-4 117369-B Rev. 00 Customizing IPX for WAN Media Using the BCC You can specify the network number only when you configure IPXWAN services. Once you supply the network number, you cannot change it. To configure IPXWAN services, see “Enabling IPXWAN for an Interface” on page 4-12. To determine the current network number, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555) and enter: address ? Using Site Manager To specify the network number, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Configured Network Number parameter. Click on Help or see the parameter description on page A-2. 5. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 4-5 Configuring IPX Services Enabling RIP on an Interface The default for this parameter depends on the WAN protocol you are using. Using the BCC To enable RIP on an interface, you must first configure RIP on an IPX interface. To configure RIP on an IPX interface, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: rip If you already configured RIP on an interface, you can change its current state. To disable RIP on an interface, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: state disabled To enable RIP, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: state enabled Using Site Manager To enable RIP on the router, complete these tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interface window opens. 4. Choose RIP. The RIP Circuit window opens. 5. Set the Enable parameter. Click on Help or see the parameter description on page A-3. 6. Click on OK. 4-6 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX for WAN Media Enabling SAP on an Interface The default for this parameter depends on the WAN protocol you are using. Using the BCC To enable SAP on an interface, you must first configure SAP on an IPX interface. To configure SAP on an IPX interface, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: sap If you already configured RIP on an interface, you can change its current state. To disable RIP on an interface, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: state disabled To enable RIP, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: state enabled Using Site Manager To enable SAP on the router, complete these tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interface window opens. 4. Choose SAP. The SAP Circuit window opens. 5. Set the Enable parameter. Click on Help or see the parameter description on page A-3. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 4-7 Configuring IPX Services Identifying a Circuit The Site Manager automatically assigns a circuit identifier to each circuit that you create on an IPX router. You can assign a specific circuit identifier, if necessary. You can assign circuit identifiers only by using Site Manager. To assign a circuit identifier, complete these tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interface window opens. 4. Set the Circuit Index parameter. Click on Help or see the parameter description on page A-4. 5. Click on OK. You return to the Configuration Manager window. Entering an IPX Host ID Number for IPX over ATM On Bay Networks routers, the IPX host ID number maps to a physical data link layer address (on a specific circuit or physical interface). An IPX logical interface can listen at this address and capture frames transmitted by nodes compatible with IPX on the local data link. 4-8 117369-B Rev. 00 Customizing IPX for WAN Media Figure 4-1 illustrates this concept in a Bay Networks router that has two IPX logical interfaces, each one configured on a different physical circuit. Local clients/servers IPX server Logical interface Incoming frames Physical interface ATM circuit Ethernet circuit Clients Router ATM Incoming cells Physical interface Logical interface IPX server = Destination (Receive) address IPX0021A Figure 4-1. Frames Received at a Logical Interface 117369-B Rev. 00 4-9 Configuring IPX Services Figure 4-2 illustrates this concept in a Bay Networks router configured with two IPX logical interfaces, each one on a different physical circuit type. Local clients/servers Logical interface IPX server ATM circuit Outgoing frames Ethernet circuit Physical interface Router Clients ATM Outgoing cells Physical interface Logical interface IPX server = Source (Transmit) address IPX0022A Figure 4-2. Frames Issued from a Logical Interface To establish an IPX connection over an ATM network, you must assign a unique host ID number to the ATM interface that is running IPX. To assign a number, you can: 4-10 • Enter a value using the Host Number parameter. • Specify that the global MAC address be used for the host ID by disabling the Multiple Host Address Enable parameter. 117369-B Rev. 00 Customizing IPX for WAN Media Using the BCC To establish an IPX connection over an ATM network if you plan to use multiple host addressing, navigate to the global IPX prompt (for example, box; ipx) and enter: host-address number number is a valid host address in hexadecimal format. For example, the following command assigns the host address 0x0987 to the IPX interface: ipxwan 00055555# host-address 0x098 If you do not plan to use multiple host addressing and want to use the global MAC address as the host number, navigate to the global IPX prompt (for example box; ipx), and enter: multiple-host enabled For example: ipx# 117369-B Rev. 00 multiple-host enabled 4-11 Configuring IPX Services Using Site Manager To establish an IPX connection over an ATM network, complete these tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The IPX Edit Global Parameters window opens. 4. Set the the following parameters: • Router Host Number • Multiple Host Address Enable Click on Help or see the parameter descriptions on pages A-11 and A-10. 5. Click on OK. You return to the Configuration Manager window. Enabling IPXWAN for an Interface If you want to run the IPXWAN protocol over a WAN, you should enable IPXWAN on the IPX interface. Enabling IPXWAN provides a common link negotiation method and a standard means for tick-based routing for WAN media. 4-12 117369-B Rev. 00 Customizing IPX for WAN Media Using the BCC To run IPXWAN over a WAN, configure a WAN (for example, box; serial 3/1; ppp) and enter: ipxwan address ipxwan_address router-name name primary-network address negotiated-protocol protocol ipxwan_address is the address, in hexadecimal notation, of the ipxwan interface. name is the symbolic name of the router. address is the address, in hexadecimal notation, of the primary network. protocol is one of the following: wan-rip unnumbered-rip wan_unnumbered-rips When you first configure IPXWAN, by default IPXWAN services are enabled. To change the IPXWAN state, navigate to the ipxwan prompt (for example, box; serial 3/1; ppp; ipxwan 00055555) and enter: state disabled To disable ipxwan, navigate to the ipxwan prompt (for example, box; serial 3/1; ppp; ipxwan 00055555) and enter enter: ipxwan denabled 117369-B Rev. 00 4-13 Configuring IPX Services Using Site Manager To enable or disable IPXWAN, complete the following tasks:. Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the IPXWAN parameter. Click on Help or see the parameter description on page A-5. 5. Click on OK. You return to the Configuration Manager window. Assigning a Primary Network Number Like Novell routers and servers, a Bay Networks router running the IPXWAN protocol implements a global “internal network,” to which you must assign a priimary network number. IPXWAN requires the primary network number to determine whether the local or the remote router on a WAN link serves as the master or slave during the IPXWAN negotiations. The router with the higher primary network number serves as the master. Using the BCC You can specify the primary network number only when you configure IPXWAN services. Once you supply the primary network number, you cannot change it. To configure IPXWAN services, see “Enabling IPXWAN for an Interface” on page 4-12. To determine the current primary network number, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555) and enter: primary-network ? 4-14 117369-B Rev. 00 Customizing IPX for WAN Media Using Site Manager To specify the primary network number, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Enable IPXWAN. The IPXWAN Configuration window opens. 4. Set the Primary Network Number parameter. Click on Help or see the parameter description on page A-8. 5. Click on OK. You return to the Configuration Manager window. Entering a Router Name Every IPX router can have a router name. During IPXWAN negotiations, the local and remote routers provide each other with their respective router names. Once the link is established, the name lets a router know whom it is connected to. Router names are particularly helpful for network management purposes. A symbolic name, such as “printserv,” has more meaning than just a string of digits. The router name can be up to 47 characters long and can contain the characters A through Z, a through z, 0 through 9, and the special characters underscore (_), hyphen (-), slash (/), and at (@) signs. Some valid names include: 117369-B Rev. 00 • AAaabbBBxxXXXS/1234 • myrouter@first_floor • Chicago_office 4-15 Configuring IPX Services Using the BCC You can assign a router name to the remote route only when you configure IPXWAN services. Once you supply the router name, you cannot change it. To configure IPXWAN services, see “Enabling IPXWAN for an Interface” on page 4-12. To determine the current network number, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555) and enter: router-name ? Using Site Manager To specify the router name, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Enable IPXWAN. The IPXWAN Configuration window opens. 4. Set the Router Name parameter. Click on Help or see the parameter description on page A-7. 5. Click on OK. 4-16 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX for WAN Media Indicating the Protocol Negotiated for an Interface When you specify an IPXWAN interface on a circuit, you must indicate the protocol negotiated for this interface. Using the BCC You can determine the negotiated protocol only when you configure IPXWAN services. Once you supply the negotiated protocol, you cannot change it. To configure IPXWAN services, see “Enabling IPXWAN for an Interface” on page 4-12. To determine the current network number, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555) and enter: negotiated-protocol ? Using Site Manager To specify the negotiated protocol, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Negotiated Protocol parameter. Click on Help or see the parameter description on page A-6. 5. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 4-17 Configuring IPX Services Sample IPXCP and IPXWAN Configurations Figure 4-3 shows a local router communicating with a remote router using IPXCP over PPP, and the same local router communicating with a remote router using IPXWAN over Frame Relay. Network number = 00000003 IPXCP interface IPXCP interface Local router PNN = 00000012 CNN = 00000019 Remote router 1 IPXWAN primary Frame Relay IPXWAN secondary Network number = 0x00000019 Remote router 2 PNN = 00000007 CNN = 00000020 IPX0002A Figure 4-3. 4-18 IPXCP and IPXWAN Configurations 117369-B Rev. 00 Customizing IPX for WAN Media IPXCP Link Negotiation In Figure 4-3, the local router and remote router 1, both configured for IPXCP, negotiate a connection at the data link layer. Once the options are successfully negotiated, the IPXCP interfaces in both the local router and remote router 1 must agree on a unique network number. When you initially configure an IPXCP interface, you assign an IPX network number to that interface. The routers select the higher of the two IPX network numbers. See Configuring PPP Services for instructions on configuring the IPX network number for an IPXCP interface. Note: For PPP communication between a Bay Networks Version 7, 8, 9, 10, or 11 IPX router and a Bay Networks Version 5 IPX router (or any other vendor’s router that does not support IPXCP negotiations), you must manually configure the network number of the IPX interface on both routers. IPXWAN Link Negotiation The local router and remote router 2 are both configured for IPXWAN. When you initially configure an IPXWAN interface, you assign a primary network number (PNN) to the router. The router with the highest PNN becomes the master during IPXWAN negotiations on that WAN link. In Figure 4-3, the local router (PNN=00000012) is the master, and remote router 2 (PNN=00000007) is the slave. During the IPXWAN negotiations, both routers negotiate their link options. If successful, the CNN configured for the interface on the master becomes the IPX network number for the WAN link. Once the IPXWAN negotiations are successful on the WAN link, each router connected on the link can advertise information in its routing/forwarding tables. 117369-B Rev. 00 4-19 Configuring IPX Services IPXWAN and IPXCP Link Configurations Table 4-1 shows the various WAN protocol configurations likely to exist within local and remote IPX router interfaces. Find the configuration that applies to your situation and read the corresponding description. Table 4-1. Configuration Table for IPX over WAN Media Remote IPX Interface PPP with IPXCP; no IPXWAN PPP without IPXCP; no IPXWAN Local IPX Interface IPXWAN with IPXCP IPXWAN but not IPXCP IPXWAN with IPXCP Configuration 1 Configuration 2 Configuration 3 Configuration 4* IPXWAN but not IPXCP Configuration 2 Configuration 2 Configuration 4 Configuration 4 PPP with IPXCP; no IPXWAN Configuration 3 Configuration 4 Configuration 3 Configuration 4 PPP without IPXCP; no IPXWAN Configuration 4* Configuration 4 Configuration 4 Configuration 4 * Bay Networks 11.00 to Bay Networks Series 5.x IPX Router Compatibility Configuration 1 (IPXWAN with IPXCP on Both Interfaces) In this configuration, IPXWAN defers to IPXCP for link negotiation: 4-20 • IPXWAN negotiation supersedes IPXCP negotiation, regardless of whether IPXCP negotiation succeeds. • If IPXWAN negotiates successfully, the IPX interface becomes active. If IPXWAN negotiation fails, the IPX interface cannot become active. 117369-B Rev. 00 Customizing IPX for WAN Media Configuration Guidelines -- Configuration 1 • IPXCP -- Use the value zero for the IPX network number when configuring the local and remote Point-to-Point Protocol interface. • IPXWAN -- Use a unique router name and Primary Network Number in the IPX Global Parameters window when configuring the local routers. You must enable IPXWAN on the interface. To enable IPXWAN, see “Enabling IPXWAN for an Interface” on page 4-12. Configuration 2 (IPXWAN on Both Interfaces) In this configuration, IPXWAN exclusively negotiates an IPX network number for the link. If IPXWAN negotiates successfully, the IPX interface becomes active. If IPXWAN negotiation fails, the IPX interface cannot become active. Configuration Guidelines -- Configuration 2 • IPXCP -- No configuration requirements. • IPXWAN -- Use a unique router name and PNN in the IPX Global Parameters window when configuring the local and remote routers. You must enable IPXWAN on the interface. To enable IPXWAN, see “Enabling IPXWAN for an Interface” on page 4-12. You must also enter a unique common network number for the IPX interface you just configured, except that the common network number can be zero when Unnumbered RIP is configured on both interfaces. 117369-B Rev. 00 4-21 Configuring IPX Services Configuration 3 (Only IPXCP on Both Interfaces) In this configuration, IPXCP exclusively negotiates an IPX network number for the link: • If IPXCP successfully negotiates the number, the IPX interface becomes active on the link. • If IPXCP fails to negotiate a number, the IPX interface cannot become active. Configuration Guidelines -- Configuration 3 • IPXCP -- Use any valid value for the IPX network number when configuring the local or remote PPP interface. • IPXWAN -- No configuration requirements. Configuration 4 In this configuration, the lower layer has no means of negotiating an IPX network number for the link. For this reason, you must manually configure the network number of the local and remote IPX interfaces to the same value. Customizing IPX After selecting a circuit and configuring the associated WAN parameters, your circuit will be operational. The default values set by the Site Manager for the remaining parameters will apply to most environments. However, if you want to configure a circuit in a particular way, refer to Chapter 5. 4-22 117369-B Rev. 00 Chapter 5 Customizing IPX In most cases, after you add a circuit and supply the basic LAN or WAN settings as shown in chapters 3 and 4, you can leave the remaining settings with the default values and begin sending packets over the network. You can customize IPX to fit your environment, using the information in the following sections: Topic Page To determine the default set of IPX values that a circuit inherits from the global 5-2 IPX process. 117369-B Rev. 00 To customize an IPX interface. 5-22 To learn about handling packets associated with upper-layer protocols. 5-35 To learn about and customize the routing information protocol (RIP). 5-36 To learn about and customize SAP. 5-61 To use static services. 5-77 To customize NetBIOS static routing. 5-90 To configure an adjacent host. 5-102 To learn about dial services. 5-111 To learn about and configure dial optimized routing. 5-116 To configure a static route. 5-124 To apply route filters. 5-131 To apply SAP filters. 5-133 To reduce network traffic by configuring service name filters. 5-147 To provide IPX ping support. 5-163 To delete IPX. 5-167 5-1 Configuring IPX Services Customizing IPX Global Operation Any IPX interface you add to a physical circuit inherits a default IPX configuration from the global/slotwide IPX process. Use the information in the following sections to customize the default settings that affect all IPX interfaces. Setting the Maximum Number of Paths You can set the maximum number of paths allowed for a given network destination and routing method from 1 to 1,023 paths. Multiple paths to a given destination use more memory than single paths, but give you redundancy. Specifying multiple paths allows you to do load balancing (see “Specifying the Number of Maximum Path Splits” later in this chapter). Bay Networks recommends that you set the maximum number of paths to the highest number of paths that exist from the router to any destination network, regardless of the cost. Using the BCC To set the maximum number of paths, navigate to the global IPX prompt (for example, box; ipx) and enter: maximum-path integer integer is the an integer from 1 to 1,023. For example, the following command sets the maximum path to 4: ipx# 5-2 maximum-path 4 117369-B Rev. 00 Customizing IPX Using Site Manager To set the maximum number of paths, complete these tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Maximum Path (hex) parameter. Click on Help or see the parameter description on page A-15. 6. Click on OK. You return to the Configuration Manager window. Filtering Log Messages You can filter specified types of log messages. For example, the default setting (Trace) filters out trace messages. The types of log messages that you can filter include: 117369-B Rev. 00 • None • Debug • Info • Trace • Debug Info • Debug Trace • Info Trace • Debug Info Trace 5-3 Configuring IPX Services Do not change the default value of this parameter unless you are an expert IPX user. Changing the value of this parameter produces significant boxwide effects on memory allocation within the router, and these changes can significantly affect router performance. If you are qualified as an expert user, enter a filtering mode that yields a level of performance most appropriate for network applications supported by this router. Using the BCC To filter specified types of log messages, navigate to the global IPX prompt (for example, box; ipx) and enter: log-filter option option is one of the following: debug info trace debug-info debug-trace info-trace For example, the following command causes IPX to filter Info messages: ipx# 5-4 log-filter info 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the filtering mode, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Log Filter parameter. Click on Help or see the parameter description on page A-15. 6. Click on OK. You return to the Configuration Manager window. Specifying the Maximum Number of Equal Cost Paths You can specify the maximum number of equal-cost paths over which IPX will do load balancing to a particular destination. For example, if the maximum path splits is non-zero, and there are five equal-cost routes to a destination, IPX will distribute the packets over the five paths in a round-robin fashion. Using the BCC To set the maximum number of equal-cost paths, navigate to the global IPX prompt (for example, box; ipx) and enter: maximum-path integer integer is the number of equal-cost paths. For example, the following command sets the maximum number of equal-cost paths to 10: ipx# 117369-B Rev. 00 maximum-path 10 5-5 Configuring IPX Services Using Site Manager To specify whether the router will do load balancing to a particular destination, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Maximum Path parameter. Click on Help or see the parameter description on page A-15. 6. Click on OK. You return to the Configuration Manager window. Specifying the Maximum Number of Destinations You can specify the maximum number of destinations (networks) for the router to learn. IPX uses this value to preallocate table sizes for forwarding and network tables. If you use the default value, zero, IPX dynamically allocates the amount of memory it needs for the tables. Do not change the default unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value can significantly affect router performance by affecting the memory usage by IPX and the learning time of the router. If you are qualified as an expert user, enter a value from 0 to 5000 destinations that yields a level of performance most appropriate for network applications supported by this router. 5-6 117369-B Rev. 00 Customizing IPX Using the BCC To set the maximum number of destinations, navigate to the global IPX prompt (for example, box; ipx) and enter: destination-count integer integer is the number of destinations. For example, the following command sets the maximum number of destinations to 15: ipx# destination-count 15 Using Site Manage To specify the maximum number of destinations for the router to learn, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Destination Count parameter. Click on Help or see the parameter description on page A-17. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-7 Configuring IPX Services Entering the Maximum Number of Services You can specify the maximum number of services for the router to learn. IPX uses this value to preallocate table sizes for service tables. If you use the default value, zero, IPX automatically allocates the amount of memory it needs for the tables. Do not change the default unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value can significantly affect router performance by affecting the memory usage by IPX and the learning time of the router. If you are qualified as an expert user, enter a value from 1 to 5000 services that yields a level of performance most appropriate for network applications supported by this router. Using the BCC To set the maximum number of services for the router to learn, navigate to the global IPX prompt (for example, box; ipx) and enter: service-count integer integer is the number of equal-cost paths. For example, the following command sets the maximum number of services to 6: ipx# 5-8 service-count 6 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the maximum number of services for the router to learn, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Service Count parameter. Click on Help or see the parameter description on page A-17. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-9 Configuring IPX Services Specifying the Granularity for Aging RIP and SAP Information You can specify the granularity, in seconds, for aging RIP and SAP information. IPX checks whether any routes have timed out every n seconds, where n is the interval that this parameter specifies. By default, IPX checks for timed out routes every 10 seconds. You can change this setting to a value from 1 to the maximum positive integer (seconds). Note: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. Using the BCC To set the granularity for aging RIP and SAP information, navigate to the global IPX prompt (for example, box; ipx) and enter: aging-frequency integer integer is the number of seconds from 1 to the maximum positive integer. For example, the following command sets the granularity for aging RIP and SAP information to 20: ipx# 5-10 aging-frequency 20 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the granularity for aging RIP and SAP information, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Aging Frequency parameter. Click on Help or see the parameter description on page A-18. 6. Click on OK. You return to the Configuration Manager window. Specifying the Aging Pending Frequency You can specify the number of routes and services to age (process) before pending. A higher number lets the aging process proceed more quickly. Do not change the default value of 100 unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value can significantly affect router performance. If you are qualified as an expert user, enter a value (between 1 and the maximum number of routers and services) that yields a level of performance most appropriate for network applications supported by this router. 117369-B Rev. 00 5-11 Configuring IPX Services Using the BCC To set the number of routes and services to age before pending, navigate to the global IPX prompt (for example, box; ipx) and enter: pend-frequency integer integer is the number of routes and services from 1 to the maximum number of routes and services. For example, the following command sets the number of routes and services to age to 100: ipx# pend-frequency 20 Using Site Manage To specify the number of routes and services to age before pending, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The IPX Global Parameters window opens. 4. Click on Advanced. The IPX Advanced Global Parameters window opens. 5. Set the Aging Pending Frequency parameter. Click on Help or see the parameter description on page A-19. 6. Click on OK. 5-12 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Enabling IPX Default Routing You can globally enable or disable the use of the default route 0xFFFFFFFE for IPX routing. Enabling default routing directs the router to use the default route (if one exists in its routing table) when it receives an IPX packet that does not contain a known IPX destination address within the IPX protocol header. Disabling default routing forces the router to drop a packet whose destination address is unknown, even if a default route exists. Using the BCC To enable the use of the default route, navigate to the global IPX prompt (for example, box; ipx) and enter: default-route enabled To disable the use of the default route, navigate to the global IPX prompt (for example, box; ipx) and enter: default-route disabled 117369-B Rev. 00 5-13 Configuring IPX Services Using Site Manager To globally enable or disable the use of the default route for IPX routing, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The IPX Global Parameters window opens. 4. Click on Advanced. The IPX Advanced Global Parameters window opens. 5. Set the Default Route parameter. Click on Help or see the parameter description on page A-19. 6. Click on OK. You return to the Configuration Manager window. Multipath Routing and Load sharing You can include multiple next-hop destinations as active routes to a destination network. The IPX router can find out about multiple paths by either RIP packets or statically configured routes. The router can forward packets to the multiple next-hop nodes concurrently by multiplexing frame transmissions over the multiple equal-cost paths in a cyclic sequence. This is referred to as IPX multipath or IPX load sharing. 5-14 117369-B Rev. 00 Customizing IPX Multipath Routing Multipath is a “round-robin” or cyclic multiplexing mechanism. When multiple least-cost paths of equal tick delay and hop count exist between IPX source and destination networks, standard RIP operation uses only one of these routes. The multipath feature takes advantage of these multiple equal-cost routes and distributes the packet load among them, balancing the IPX traffic across these routes and maximizing internetwork performance. When you enable multipath routing, the IPX router diverts individual, consecutive frames destined for the same target network to separate IPX interfaces and their associated physical circuits (Figure 5-1). Router Next hop A IPX circuit A B IPX circuit B C IPX circui t C Outgoing sequential frames CBA IPX0005A Figure 5-1. 117369-B Rev. 00 IPX Multipath 5-15 Configuring IPX Services Because the IPX interfaces have duplex functionality, the router can also use multipath to collect frames received from separate IPX interfaces. The router operates this cyclic mechanism at a bandwidth significantly greater than a single IPX interface and its supporting physical circuit can support. The result is that IPX frames flow over multiple parallel LAN or WAN routes concurrently, in effect, aggregating the bandwidth supported by the parallel routes. Each line shares 1/nth of the total load (where n is the number of equal-cost parallel routes or paths to the destination network). By default, the maximum number of paths is set to 1. When you specify the maximum number of paths, set the value to the highest number of paths, in the range of 1 to 1,023, that exist from the router to any destination network, regardless of cost. Any setting greater than 1 engages the multipath mechanism. Figure 5-2 is an example of equal, least-cost, parallel routes used in IPX multipath routing. R2 ES1 Tick Delay = 5 Network A Tick Delay = 5 R3 R4 R1 Tick Delay = 5 Tick Delay = 5 Network B IPX server Tick Delay = 5 Tick Delay = 5 R5 IPX0006A Figure 5-2. 5-16 IPX Multipath Routing -- Equal Least-Cost Routes 117369-B Rev. 00 Customizing IPX Because of the round-robin algorithm, IPX packets that belong to the same data stream may require resequencing at their ultimate destination. Therefore, higher-layer protocols such as SPX must be used in both source and destination IPX routers to provide packet resequencing. To derive maximum benefit from this feature, the source and destination nodes should support burst-mode operation. Load Redistribution and Rerouting If the router with multipath enabled detects a failure, it temporarily redistributes the IPX traffic among the remaining active original least-cost routes. When the router learns (through RIP packets) of the existence of an alternative least-cost route, or when the failed route returns, IPX multipath returns to its original IPX traffic distribution. Multipath Route Precedence/Priority The multipath mechanism generally uses the best path first. However, when two equal-cost paths exist, multipath uses the following priority scheme for route selection: 1. Direct routes (paths to other routers on a segment directly attached to the local router) 2. Routes learned via RIP 3. Statically configured routes Multipath Configurations You can establish equal-cost multipath routes over LAN or WAN segments to support IPX traffic between routers, and between routers and servers. The slower the interconnecting LAN or WAN links, the more difference using multipath will make in client/server throughput. Multiline Circuits The multiline circuits feature allows a single circuit to be composed of up to 16 individual synchronous network data paths. Multiline circuits support provides a level of redundancy not available through conventional single-line circuit configurations. The multiline circuits feature ensures routing circuit availability in the event of a single data path failure. 117369-B Rev. 00 5-17 Configuring IPX Services Equally important, the multiline circuits feature provides increased bandwidth between two sites without the circuit management complexities associated with multiple circuits. Once you have configured and enabled the circuit, the use of multiple data paths to form a single circuit is transparent to both network management and the end-user community. Multiline circuits provide the following methods for transmitting traffic over their data paths: • Address-based data path selection • Random data path selection Address-based data path selection determines the path a packet traverses based on its source and destination addresses. Once a path has been established for a given address pair, subsequent packets will follow the same path. This ensures that packets will be received in the order in which they were sent. This is essential for protocols that cannot tolerate receiving packets out of order. Random data path selection determines the path a packet traverses based on a randomly assigned number that corresponds to a particular data path of the multiline circuit. This algorithm avoids congestion by providing even distribution across multiple data paths. Unlike address-based selection, random data path selection does not guarantee the sequence of packets as they are received at their destination. Consequently, random data path selection is intended for use with protocols whose upper layers provide resequencing techniques. Note: For Bay Networks software Version 7.60 and later, support of multiline circuits is compatible with the Version 5.x “Circuit Groups” feature, except that Version 7.60 and later software does not support LAN media multiline circuits grouping. Multiline circuits can be configured using only synchronous interfaces data paths, including HSSI. All data paths must incorporate the same encapsulation method, maximum transmission unit (MTU), and effective bandwidth. The differences between multiline circuits and IPX multipath are the following: 5-18 • Multiline circuits operate across point-to-point links between two Bay Networks routers, while IPX multipath operates across a random topology (both LAN and WAN). • Multiline is protocol-independent, while IPX multipath is IPX-based. 117369-B Rev. 00 Customizing IPX • Multiline circuits require WAN links of equal bandwidth on which to distribute IPX traffic, while IPX multipath supports links of varying speeds. • Multiline circuits do not support the adoption of alternative links when WAN links fail. Using the BCC To specify the maximum number of paths allowed for a given network destination and routing method, navigate to the global IPX prompt (for example, box; ipx) and enter: maximum-path integer integer is the number, between 1 and 1023, of paths. For example, the following command sets the number of paths to age to 999: ipx# maximum-path 999 Using Site Manager To specify the maximum number of paths allowed for a given network destination and routing method, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The IPX Global Parameters window opens. 4. Click on Advanced. The IPX Advanced Global Parameters window opens. 5. Set the Maximum Path parameter. Click on Help or see the parameter description on page A-15. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-19 Configuring IPX Services Selecting the GNS Response Mode You can specify which server the router will choose when responding to a get_nearest_server request. By default, when a server responds to a get_nearest_server request, the router sorts through all server names alphabetically. You can either accept the default method or specify that the router select the last server learned. Using the BCC To specify which server the router will choose when responding to a get_nearest_server request, navigate to the global IPX prompt (for example, box; ipx) and enter: gns-response option option is one of the following: alphabetical lastlearned For example, the following command specifies that the router responds to a get_nearest_server request by selecting the last server learned: ipx# 5-20 gns-response lastlearned 117369-B Rev. 00 Customizing IPX Using Site Manager To specify which server the router will choose when responding to a get_nearest_server request, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the GNS Response Mode parameter. Click on Help or see the parameter description on page A-21. 6. Click on OK. You return to the Configuration Manager window. Specifying the Table Fill Notify Value The table fill notify value causes the IPX router to notify you when the IPX network table is filled. To specify the table fill notify value, navigate to the global IPX prompt (for example; box; ipx) and enter: table-fill-notify integer integer is any valid integer. For example, to set the table fill notify value to 500, enter: ipx# 117369-B Rev. 00 table-fill-notify 500 5-21 Configuring IPX Services Specifying the Size of the Network Table To specify the size of the network table, navigate to the global IPX prompt (for example; box; ipx) and enter: network-table-size integer integer is any valid integer. For example, to set the size of the network table to 300, enter: ipx# network-table-size 300 Specifying the MIB Reply Slot To specify the slot where IPX sends MIB replies, navigate to the global IPX prompt (for example; box; ipx) and enter: mib-reply-slot slot_no slot_no is any valid integer. For example, to set the MIB reply slot to slot 4, enter: ipx# mib-reply-slot 4 Customizing an IPX Interface Any IPX interface you add to a physical circuit inherits a default set of IPX values from the global/slotwide IPX process. These interface values determine how IPX behaves on individual router interfaces. You can customize the parameters that belong to a specific interface by modifying the values of the IPX interface settings. 5-22 117369-B Rev. 00 Customizing IPX Enabling IPX Routing on an Interface After you add an interface to a circuit, you can enable or disable IPX routing on this interface. By default, IPX is enabled on an interface. Enabling IPX on an interface initializes the IPX interface you added to a circuit or reinitialize an existing disabled IPX interface. The actual operating state of an interface, once enabled, depends on: • The current state of the associated circuit • The current state of the IPX global/slotwide protocol process Disabling an IPX interfaces forces an IPX interface into the down (inoperative) state. Using the BCC To enable IPX routing on an interface, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: ipx enabled To disable IPX routing on an interface, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: ipx disabled 117369-B Rev. 00 5-23 Configuring IPX Services Using Site Manager To enable IPX routing on an interface, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Enable parameter. Click on Help or see the parameter description on page A-23. 5. Click on OK. You return to the Configuration Manager window. Entering a Symbolic Name for an Interface You can specify a symbolic name for an interface on a server. For example, first_floor_printer. See the documentation that came with your NetWare operating system for guidelines on specifying a host, interface, router, or server name. It is a good idea to make the name meaningful to users as well as to routers. Using the BCC To specify a symbolic name for an IPX interface on a server, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: circuit-name name name is any meaningful name for an IPX interface. For example, the following command provides the name first_floor_printer to an IPX interface: ipx/00023456# 5-24 circuit-name first_floor_printer 117369-B Rev. 00 Customizing IPX Using Site Manager To specify a symbolic name for an IPX interface on a server, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Name parameter. Click on Help or see the parameter description on page A-23. 5. Click on OK. You return to the Configuration Manager window. Assigning a Host Number to an Interface You can assign a host number to an IPX interface after you enable multiple host addressing. If you enable multiple host addressing and want to accept the PROM-based default setting for the MAC address, this IPX interface adopts a host number based on the MAC address of the underlying circuit. In this case, a PROM on the circuit supplies the number for the MAC address of the circuit and the host number of the interface. You can enter a host number for this interface when: 117369-B Rev. 00 • Multiple host addressing is enabled. • You do not want to accept the PROM-based (default) setting for the MAC address. • The circuit type supports only selective mode of operation (such as with Ethernet circuits). 5-25 Configuring IPX Services If you enter a host number, the circuit adopts that value as the MAC address at which this interface can receive frames. (The MAC address configured at the circuit/line level remains effective for all other interfaces configured on the same circuit.) Using the BCC To assign a host number to an IPX interface, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: host-address number number is a valid host address in hexadecimal format. For example, the following command assigns the host address 0x0987 to the IPX interface: ipx/00023456# host-address 0x0987 Using Site Manager To assign a host number to an IPX interface, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Host Number parameter. Click on Help or see the parameter description on page A-25. 5. Click on OK. 5-26 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Enabling Source Routing for an Interface on a Token Ring Circuit You can enable or disable source routing for an interface on a Token Ring circuit. By default, source routing is disabled on a Token Ring circuit. Enable source routing if this interface connects to a bridged token ring network. Disable source routing if you do not want to use source routing over this interface. Using the BCC To enable source routing for an IPX interface on a token ring circuit, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: end-station enabled To disable source routing for an IPX interface on a token ring circuit, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: end-station disabled For example, the following command enables source routing on IPX interface 00023456: ipx/00023456# 117369-B Rev. 00 end-station enabled 5-27 Configuring IPX Services Using Site Manager To enable or disable source routing for an IPX interface on a token ring circuit, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the TR End Station parameter. Click on Help or see the parameter description on page A-26. 5. Click on OK. You return to the Configuration Manager window. Entering a Broadcast Address You can enter a WAN broadcast address for an IPX interface. The default value (0xFFFFFFFFFFFF) causes the data link layer to issue a WAN broadcast packet on all active virtual circuits. The value is not actually included in the MAC field of the packet on the WAN. The packet instead contains a value that is appropriate for the type of data link protocol. You accept the default value, or enter a WAN broadcast address to send all broadcast traffic through the IPX interface you are configuring. With the default value, the IPX router sends all broadcast traffic through all logical connections associated with the IPX interface you are configuring. Broadcast traffic includes RIP and SAP broadcasts. Note that Site Manager does not display the default value 0xFFFFFFFFFFFF. 5-28 117369-B Rev. 00 Customizing IPX Using the BCC To enter a WAN broadcast address, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: broadcast-address address address is a valid WAN broadcast address in hexadecimal format. For example, to assign the WAN broadcast address 0x01203406, enter: ipx/00023456# broadcast-address 0x01203406 Using Site Manage To enter a WAN broadcast address, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the FR Broadcast (hex) parameter. Click on Help or see the parameter description on page A-28. 5. Click on OK. You return to the Configuration Manager window. Entering a Multicast Address You can enter a WAN multicast address for an IPX interface. The default value (0xFFFFFFFFFFFF) causes the data link layer to issue a multicast packet on all active virtual circuits. The value is not actually included in the MAC field of the packet on the WAN. The packet instead contains a value that is appropriate for the type of data link protocol. 117369-B Rev. 00 5-29 Configuring IPX Services You can accept the default value, or enter a WAN multicast address to send all multicast traffic through the IPX interface you are configuring. With the default value, the IPX router sends all multicast traffic through all logical connections associated with the IPX interface you are configuring. Note that Site Manager does not display the default value 0xFFFFFFFFFFFF. Using the BCC To enter a WAN multicast address, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: multicast-address address address is a valid WAN multicast address in hexadecimal format. For example, to assign the WAN multicast address 0x01203405, enter: ipx/00023456# multicast-address 0x01203405 Using Site Manager To specify the WAN multicast address, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the FR Multicast (hex) parameter. Click on Help or see the parameter description on page A-28. 5. Click on OK. 5-30 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Responding to IPX Watchdog Packets You can enable or disable a router from responding locally to broadcast IPX watchdog packets on behalf of clients that use dial-in connections. You should enable local watchdog packet acknowledgment to reduce WAN costs by using dial-on-demand routing. SPX Keep Alive Spoofing is enabled when Watchdog Spoofing is enabled. By default, IPX watchdog spoofing is disabled. Enabling local watchdog packet acknowledgment can improve the efficiency of IPX wide area links. Using the BCC To enable a router from responding locally to watchdog packets, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555#) and enter: watchdog-spoofing enabled To disable a router from responding locally to watchdog packets, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555#) and enter: watchdog-spoofing disabled For example, to disable IPX watchdog spoofing, enter: ipx/00023456# 117369-B Rev. 00 watchdog-spoofing disabled 5-31 Configuring IPX Services Using Site Manager To enable or disable a router from responding locally to watchdog packets, complete the following tasks:. Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the IPX Watchdog Spoofing parameter. Click on Help or see the parameter description on page A-29. 5. Click on OK. You return to the Configuration Manager window. Setting the Delay Time You can specify the length of time, from 0 through 2147483647 microseconds, required to transmit 1 byte of data (excluding protocol headers) to a destination on the other end of this IPX circuit, if the circuit is free of other traffic. Using the BCC To specify the amount of time to transmit 1 byte of data, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: delay microseconds microseconds is a value from 0 to 2147483647 microseconds. For example, to specify that the router should take 10,000 microseconds to transmit 1 byte of date, enter: ipx/00023456# 5-32 delay 10000 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the amount of time to transmit 1 byte of data, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Delay parameter. Click on Help or see the parameter description on page A-29. 5. Click on OK. You return to the Configuration Manager window. Specifying Throughput You can specify the amount of data, from 0 to 2147483647 bits per second, that can flow through an IPX circuit if the circuit is free of other traffic. Using the BCC To specify the data throughput, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: throughput bits_per_second bits_per_second is from 0 to 2147483647 bits per second. For example, to specify the data throughput as 1,000,000 bits per second, enter: ipx/00023456# 117369-B Rev. 00 throughput 1000000 5-33 Configuring IPX Services Using Site Manager To specify the data throughput, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Throughput parameter. Click on Help or see the parameter description on page A-30. 5. Click on OK. You return to the Configuration Manager window. Setting the Stabilization Timer Delay You can set the amount of time, from 0 to 2147483647 seconds, that RIP/SAP waits before sending out initial route information when the circuit first becomes active. The more routes that you expect a router to handle or the more dynamic the network is, the higher you should set this value to allow the router enough time to assimilate incoming routes before it sends out an initial update on a circuit. Using the BCC To specify the RIP/SAP delay period, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: stabilization-timer seconds seconds is from 0 to 2147483647 seconds. For example, to specify the RIP/SAP delay period as 100,000 seconds, enter: ipx/00023456# 5-34 stabilization-timer 100000 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the RIP/SAP delay period, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the Stabilization Timer Delay (secs) parameter. Click on Help or see the parameter description on page A-29. 5. Click on OK. You return to the Configuration Manager window. Handling Packets Associated with Upper-Layer Protocols The router encapsulates, within the data field of an IPX packet, any packets associated with Novell’s upper-layer protocols. The structure of a packet, as well as the source and destination socket numbers contained in that packet, identify the protocol type associated with that packet; for example, Service Advertising Protocol and Routing Information Protocol. The upper layer services are: 117369-B Rev. 00 • SPX • NCP 5-35 Configuring IPX Services Bay Networks router software lets you select the basis on which an IPX router makes its routing decisions -- on the number of ticks or the number of hops required to reach a given destination network. The IPX routing software also provides the following services over LAN and WAN media: • Multipath routing and load sharing • Split Horizon capability • NetBIOS all-networks-broadcast packets (type 20 packets) • Source routing and end station support • IPX ping capability The following sections describe how Bay Networks routers support these services. The Routing Information Protocol (RIP) The Routing Information Protocol (RIP) enables workstations and routers to exchange route information and to establish the route to each network with the fewest hops and shortest delay. Each IPX router maintains a route table. The route table contains the following information about every network in the IPX network topology: 5-36 • The network address. • The number of ticks (units of delay time) to that network. (A tick is equal to 1/18 second. The number of ticks to a network is the tick cost for that route.) • The number of hops to that network. (A hop is an adjacent router; the number of hops is equal to the number of adjacent routers that a packet must traverse to reach another network segment.) • The address of the next-hop node to which the local router forwards packets on their way to another destination network. 117369-B Rev. 00 Customizing IPX Routers maintain route tables by exchanging RIP request and response packets. A RIP request packet specifies the destination network. A RIP request packet can be: • A general request broadcast by a router to retrieve the fastest route to all known networks on an internetwork. The value 0xFFFFFFFF in the network address field indicates that the packet is a general request. • A specific request broadcast by a workstation or router to determine the fastest route to a particular network. One or more network addresses (excluding an address of all Fs) in the network address field indicates that the packet is a specific request. Routers issue RIP response packets. RIP response packets contain the network number and the number of hops and ticks required to get to the network. A RIP response can be one of the following types: • A response to a request. • An informational broadcast from a router issued at regular intervals (by default, every 60 seconds). • An informational broadcast when a change occurs in the routing table. Examples of changes in the routing table are tick or hop changes, timing out of routes, and the addition of routes to networks to the table. • An informational broadcast when an interface initializes or performs an orderly shutdown procedure. Each RIP packet can contain up to 50 route updates. To reduce traffic, RIP broadcasts are limited to a router’s immediate segments and are not forwarded by receiving routers. Note: The IPX router learns WAN addresses from RIP and SAP broadcasts received over WANs (Frame Relay, SMDS, ATM). The router stores IPX address/WAN address pairs for future use as next-hop destinations. 117369-B Rev. 00 5-37 Configuring IPX Services Enabling RIP on the Router You can enable or disable RIP on a circuit. By default RIP is not enabled on the router. If you enable RIP on a circuit, a route filter can still prohibit the interface from updating its internal routing tables. See “Using IPX Route Filters,” later in this chapter. If you do not configure RIP for a WAN interface, you must configure adjacent hosts for all transmission paths to nodes adjacent to Frame Relay, ATM, or SMDS circuits when you configure an IPX interface. You must then configure static routes that use the adjacent hosts to reach next-hop routers. Refer to the descriptions of adjacent hosts and static routes in this chapter for more information on these features. Using the BCC To enable RIP on an interface, you must first configure RIP on an IPX interface. To configure RIP on an IPX interface, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: rip If you already configured RIP on an interface, you can change its current state. To enable RIP, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: state enabled To disable RIP on an interface, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: state disabled 5-38 117369-B Rev. 00 Customizing IPX Using Site Manager To enable RIP on the router, complete these tasks; Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Enable parameter. Click on Help or see the parameter description on page A-36. 6. Click on OK. You return to the Configuration Manager window. Choosing the Routing Method You can specify a method for making IPX “best-route” decisions for all slots, based on time delays (ticks) incurred or hops encountered for packet delivery. The router can assess the time delay in one of the following ways: • Number of RIP timer ticks -- the amount of time, expressed in ticks, that a packet requires to reach another network segment. (Each RIP timer tick equals about 1/18th of a second. The maximum configurable number of ticks is 65,534 ticks, multiplied by 1/18th of a second = 3600 seconds, or 60 minutes. • Number of hops -- the number of router hops a packet must traverse to reach a network segment. The maximum number of hops is 15. If you accept the default, Tick, and the router knows about two paths to a network, and both paths have equal tick values, the router chooses the path with the smallest number of hops. If you select Hop, and the best route results in the same number of hops, the router makes its decision based only on the number of hops between network segments. 117369-B Rev. 00 5-39 Configuring IPX Services Bay Networks recommends using the default (tick-based) method. Note that every node on the network must use the same routing method. Using the BCC To specify the routing method, navigate to the global IPX prompt (for example, box; ipx) and enter: routing-method method method is one of the following: tick hop For example, to specify that IPX use tick-based routing, enter: ipx# routing-method tick Using Site Manage To specify the routing method, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Global Advanced Parameters window opens. 5. Set the Routing Method parameter. Click on Help or see the parameter description on page A-14. 6. Click on OK. 5-40 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Setting a Cost for an Interface You can set the cost (number of ticks or hops) for an interface. The value you enter depends on whether you selected hops or ticks for the RIP interface’s routing method. By configuring an interface’s cost you can select the route you want to use, rather than letting the router select the route. For example, two routes go to the same destination. Route A has a tick cost of 2; route B has a tick cost of 3. Because route A has the lower tick cost, the router selects it as the “best route” to the destination. If you want traffic to go over route B, you can set the tick cost of route A to 4, which then forces traffic to go over route B. Using configurable RIP interface tick values, IPX routing decisions can be based on tick values that you define. This allows the implementation of tick-based routing over non-IPX WAN links (for example, HDLC encapsulation), letting you optimize IPX network performance. In Figure 5-3, for example, traffic generated by end system 1 (ES1) on network A is directed to the IPX Server ES2 on network B over interface 2 (route of least tick delay, per RIP specification). However, other protocols such as IP, AppleTalk, and OSI will most likely select this route as the least-cost path between network A and network B, as well. Consequently, traffic congestion over this route may preclude it from being the most efficient path between these two network segments. By implementing the Configurable RIP Interface Tick parameter, interface 1 on router 1 can be assigned a lower tick value than interface 2, so that IPX traffic is routed through interface 1. This lets you maximize IPX internetwork performance between networks A and B, even though it traverses two T1 lines instead of one. 117369-B Rev. 00 5-41 Configuring IPX Services R2 Interface 3 Tick Delay = 6 ES 1 R1 Interface 1 Tick Delay = 3 ES 2 R3 Network B Network A Interface 2 Tick Delay = 12 IPX server IPX0003A Figure 5-3. IPX Configurable RIP Interface Cost You can set the cost (number of ticks or hops) for an interface. The cost is added to route information learned on this interface through RIP and is included in subsequent RIP packets sent to other interfaces. IPX disposes of the packet when its hop count passes a value that is one less than the maximum number of hops. The cost value must be the same across the network. The cost is added to route information learned on this interface through RIP and is included in subsequent RIP packets sent to other interfaces. IPX disposes of the packet when its hop count passes a value that is one less than the value of the maximum number of hops. This value must be the same across the network. For all non-WAN and HSSI interfaces, the default value translates into a tick cost of 1 in the routing table. For all WAN interfaces, the default value translates into a tick cost of 6 in the routing table. Note: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. 5-42 117369-B Rev. 00 Customizing IPX Using the BCC To specify the routing cost for an interface, navigate to the IPX interface prompt (or example, box; ethernet 2/1; ipx 00023456) and enter: cost integer integer is 0 to one less than the number of maximum hops for hop-based routing or 0 to the maximum positive integer for tick-based routing. For example, to set the cost to 120, enter: ipx/00023456# cost 120 Using Site Manager To specify the routing cost for an interface, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Cost parameter. Click on Help or see the parameter description on page A-24. 6. Click on OK. You return to the Configuration Manager window. Specifying the Maximum Number of Hops You can specify the maximum number of hops an IPX packet may take to reach its destination. By default, 16 is the maximum number of hops for an IPX packet to reach a destination. You can set this value from 1 to 255. In the case of RIP, every node in the network should use the same Maximum Hops parameter value. 117369-B Rev. 00 5-43 Configuring IPX Services Using the BCC To specify the maximum number of hops, navigate to the global IPX prompt (for example, box; ipx) and enter: hops hop_count hop_count is the number of hops from 1 to 255 hops. For example, to specify the maximum number of hops as 20, enter: ipx# hops 20 Using Site Manager To specify the maximum number of hops for an IPX packet to reach its destination, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Maximum Hops parameter. Click on Help or see the parameter description on page A-16. 6. Click on OK. You return to the Configuration Manager window. Indicating the Number of Next-Hop Hosts You can enter the maximum next-hop hosts for the router to learn. IPX uses this value to preallocate table sizes for host tables. By default, the router learns a maximum of 1 next-hop hosts. You can set this value from 1 to 5000 next-hop hosts. 5-44 117369-B Rev. 00 Customizing IPX Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect the memory use by IPX, but it can also speed learning time for the router. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. Using the BCC To specify the number of next-hop hosts, navigate to the global IPX prompt (for example, box; ipx) and enter: host-count hosts hosts is the number of hops from 1 to 255 hops. For example, to specify the maximum number of hops as 20, enter: ipx# host-count 20 Using Site Manager To specify the number of next-hop hosts for the router to learn, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The Edit IPX Global Parameters window opens. 4. Click on Advanced. The Edit IPX Advanced Global Parameters window opens. 5. Set the Host Count parameter. Click on Help or see the parameter description on page A-18. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-45 Configuring IPX Services Enabling RIP Listen and Supply Functions The IPX router lets you determine whether the IPX router learns routes received in RIP updates from neighboring routers, transmits RIP periodic and triggered updates to routers in adjacent networks, or does both. By default, the IPX router learns routes ands transmits updates to routers in adjacent networks. Using the BCC To specify that IPX transmits periodic or triggered updates, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456#) and enter: supply enabled To specify that IPX does not transmit periodic or triggered updates, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456#) and enter: supply disabled For example, to specify that IPX interface transmit triggered updates, enter: rip/00023456# supply enabled To specify that IPX transmits learns routes received in RIP updates from neighboring routers, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456#) and enter: listen enabled To specify that IPX does not learn routes received in RIP updates from neighboring routers, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456#) and enter: listen disabled For example, to specify that the IPX interface learns routes received in RIP updates from neighboring routers, enter: rip/00023456# 5-46 listen enabled 117369-B Rev. 00 Customizing IPX Using Site Manager To specify whether IPX transmits and/or receives periodic or triggered RIP updates, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Mode parameter. Click on Help or see the parameter description on page A-36. 6. Click on OK. You return to the Configuration Manager window. Determining the Pace of RIP Packets The RIP pace determines the frequency, in packets per second, at which RIP sends out packets on a circuit. By default, RIP sends 18 packets per second on a circuit. You can specify a RIP pace of 0 to 1000 packets per second. If you enter a value of zero, there is no limit on the pace. Using the BCC To specify the RIP pace, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: pace packets_per_second packets_per_second is the number of packets, from 0 to 1000, that RIP sends per second. For example, to set the IPX RIP interface pace to 20 packets per seconds, enter: pace 20 117369-B Rev. 00 5-47 Configuring IPX Services Using Site Manager Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Pace parameter. Click on Help or see the parameter description on page A-37. 6. Click on OK. You return to the Configuration Manager window. Configurable RIP Timers You can extend the standard 60-second IPX periodic RIP advertisement interval. I By default, the timeout time is three times the standard 60-second RIP advertisement update interval, or 180 seconds. Configuring RIP timers can reduce IPX RIP overhead and enhance bandwidth availability. Furthermore, you can eliminate periodic RIP advertisements by setting the configurable RIP timer to zero; thus, only RIP updates triggered by changes in the internetwork topology will be propagated. To ensure proper RIP operation, all configurable RIP timers must be set at equal advertisement intervals on all router interfaces attached to common IPX network segments. Note: While you can set configurable RIP timers on any Bay Networks router interface, do not use them on LAN interfaces, because IPX servers do not allow configuration of update timers (with internal routers). As a result, IPX servers will by default purge RIP entries after 180 seconds if they have not received any updates within this 180-second period. 5-48 117369-B Rev. 00 Customizing IPX For example, in Figure 5-4, if router R1 is configured to issue periodic RIP advertisements every 240 seconds over interface 1 and router R2 is configured to issue advertisements per the IPX standard (every 60 seconds) over interface 2, then router R2 will purge RIP entries learned through Interface 2 every 180 seconds and reinstate them 60 seconds later when it receives a periodic RIP advertisement from router R1. More critically, router R2 will issue triggered RIP updates through interface 3, propagating these unnecessary changes throughout the internetwork behind router R2. Setting the configurable RIP timers at 240 seconds on both interface 1 on router R1 and interface 2 on router R2 ensures proper RIP operation, because RIP entries are not purged unless an update for a particular entry is not received within a 720-second interval (3 * 240 seconds). Interface 1 RIP Update every 240 seconds Interface 3 RIP Update every 60 seconds ES 1 R1 R2 Network A Network B IPX server Interface 2 RIP Update every 240 seconds IPX0004A Figure 5-4. IPX Configurable RIP Timers Taking into account the fact that IPX Server ES1 (with an internal router) on network B expects periodic RIP advertisements every 60 seconds, router R2 continues to issue RIP advertisements out its LAN interface (interface 3) per the IPX specification, reconciling the fact that periodic RIP advertisements through interface 1 are received every 240 seconds. Should you decide to disable the periodic transmission of RIP updates, RIP immediate (one-time) update packets still propagate through the network, in compliance with Novell standards. The combination of the update interval and age multiplier should be the same for all systems on a network segment. 117369-B Rev. 00 5-49 Configuring IPX Services Note that increasing the value of the age multiplier can cause routes to take longer to age out; decreasing it could cause the router to age routes prematurely, if routing updates are missed. Using the BCC To configure RIP timers, you must configure the RIP update interval and age multiplier for information received in RIP periodic updates. To specify a value for the RIP update interval, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: update-interval seconds seconds is from 0 to 2678400 seconds. For example, to set the update interval to 10,000, enter: rip/00023456# update-interval 10000 To specify an age multiplier, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: age-multiplier integer integer is from 1 to 6. For example, to set the age multiplier to 4, enter: rip/00023456# 5-50 age-multiplier 4 117369-B Rev. 00 Customizing IPX Using Site Manager Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the following parameters: • Update Interval • Age Multiplier Click on Help or see the parameter descriptions on page A-37. 6. Click on OK. You return to the Configuration Manager window. Adjusting the RIP Packet Size By default the size of a RIP update packet is 432 bytes. You should leave the RIP packet size at the default level unless you have a specific reason for specifying a different size packet. If you must change the packet size, the packet size plus the IPX header (30 bytes) cannot exceed the MTU of the link. Using the BCC To specify the the RIP update packet size, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: packet-size bytes bytes is the size of the RIP poacket in bytes. For example, to set the IPX RIP update packet size to 500, enter: rip/00023456# 117369-B Rev. 00 packet-size 500 5-51 Configuring IPX Services Using Site Manager Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the following Packet Size parameter. Click on Help or see the parameter description on page A-38. 6. Click on OK. You return to the Configuration Manager window. Enabling Multicast Transmission of RIP Packets By default, the IPX router broadcasts RIP packets. If you enable this feature, you should specify the multicast address. The multicast address causes the data link layer to issue a multicast packet on all active virtual circuits. The multicast address value is not actually included in the MAC field of the packet on the WAN. The packet instead contains a value that is appropriate for the type of data link protocol. You can use the default multicast address (0xFFFFFFFFFFFF), which causes the IPX router to send all multicast traffic through all logical connections associated with the IPX interface you are configuring. You can also specify a WAN multicast address to send all multicast traffic through the IPX interface you are configuring. 5-52 117369-B Rev. 00 Customizing IPX Using the BCC To use multicasting, first enable multicasting and then specify a WAN multicast address. To enable multicasting, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: use-multicast enabled To specify a WAN multicast address, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: multicast-address address address is a WAN multicast address. For example, to set the WAN multicast address to 0x00432567, enter: multicast-address 0x00432567 To disable multicasting, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: use-multicast disabled 117369-B Rev. 00 5-53 Configuring IPX Services Using Site Manager To use multicasting, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the following parameters: • FR Multicast (hex) • Use Multicast Click on Help or see the parameter descriptions on pages A-28 and A-38. 6. Click on OK. You return to the Configuration Manager window. Configurable Split Horizon The Split Horizon algorithm is part of the Novell specification for the IPX protocol. Its purpose is to prevent circular routes and reduce network traffic. The Bay Networks implementation of Split Horizon excludes RIPs and SAPs learned from a neighbor when forwarding RIP and SAP updates to that neighbor. Split Horizon is enabled by default for each interface. You can enable or disable Split Horizon when you configure an IPX RIP circuit. Fully Meshed Networks A fully meshed network is a WAN in which all nodes have a logically direct connection to each other. Figure 5-5 shows a sample fully meshed network with split horizon enabled. 5-54 117369-B Rev. 00 Customizing IPX Network 1 Router A Split Horizon enabled on this Interface to eliminate all redundant RIP and SAP traffic. WAN Network 2 Router B Router C Network 3 IPX0007A Figure 5-5. Split Horizon Enabled in a Fully Meshed Network Non-Fully Meshed Networks A non-fully meshed network is a WAN in which one or more nodes do not have logically direct connections to all other nodes. In a star or non-fully meshed frame relay or X.25 PDN topology, you may need to disable Split Horizon on certain interfaces so the routers can learn about other networks. Caution: We advise you not to disable Split Horizon unless it is absolutely necessary. Doing so can result in a significant increase in network traffic. 117369-B Rev. 00 5-55 Configuring IPX Services Figure 5-6 shows a sample non-fully meshed network with Split Horizon disabled. Network 1 Router A Split Horizon disabled on this interface so that Router B can learn about Network 3 and Router C can learn about Network 2. Frame relay Network 2 Router B Router C Network 3 IPX0008A Figure 5-6. Split Horizon Disabled in a Non-Fully Meshed Network If you disable IPX Split Horizon, IPX sends all router services over non-fully meshed frame relay and X.25 topologies. For example, as shown in Figure 5-6, router A propagates RIP and SAP packets pertaining to router B to router C, and vice versa. As a result, end stations on network 2 can learn about network 3, and end stations on network 3 can learn about network 2. When Split Horizon is enabled for an interface, routes learned on that interface are not advertised out that interface. 5-56 117369-B Rev. 00 Customizing IPX Using the BCC To enable Split Horizon, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: split-horizon enabled To disable Split Horizon, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: split-horizon disabled Using Site Manager To enable or disable Split Horizon, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Split Horizon parameter. Click on Help or see the parameter description on page A-39. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-57 Configuring IPX Services Updating Routers about a Failed Route By default, when a circuit goes down on a router, the router immediately propagates this status change to other routers in the internetwork. This facilitates network traffic by letting routers know immediately about new or failed routes. When you disable the RIP Immediate Update parameter, other routers learn about such changes only at the next periodic update interval. Using the BCC To determine that routers know immediately about new or failed routes, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: triggered-update enabled To determine that routers know about new or failed routes only at the next periodic update interval, navigate to the IPX RIP interface prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: triggered-update disabled For example, to cause the router to know about state changes immediately, enter: triggered-update enabled 5-58 117369-B Rev. 00 Customizing IPX Using Site Manager Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Immediate Update parameter. Click on Help or see the parameter description on page A-39. 6. Click on OK. You return to the Configuration Manager window. Advertising Default Routes in RIP Packets A RIP packet does not normally include a default route that exists in the routing table. However, if a default route exists in the routing table, you can specify whether to advertise the default route, 0xFFFFFFE, in RIP packets on a circuit. Using the BCC To advertise default routes in RIP packets, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: triggered-update enabled If you do not want to advertise default routes in RIP packets, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: triggered-update disabled 117369-B Rev. 00 5-59 Configuring IPX Services Using Site Manager To advertise default routes in RIP packets, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Default Route Supply parameter. Click on Help or see the parameter description on page A-40. 6. Click on OK. You return to the Configuration Manager window. Accepting Default Route Information When a router receives a RIP packet that advertises a default route, and if you have configured the receiving RIP interface to accept the default route in RIP packets, the router stores the default route in the routing table. Using the BCC To specify that a RIP interface accepts the default route in RIP packets, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: default-route-listen enabled To specify that a RIP interface does not accept the default route in RIP packets, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: default-route-listen disabled 5-60 117369-B Rev. 00 Customizing IPX Using Site Manager To specify whether a RIP interface accepts the default route in RIP packets, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Default Route Listen parameter. Click on Help or see the parameter description on page A-40. 6. Click on OK. You return to the Configuration Manager window. Customizing SAP Parameters NetWare network services use the Service Advertising Protocol to inform clients of their presence. NetWare services use the SAP identification broadcasting services to tell clients their name, type, and IPX address. The IPX address in a broadcast identifies a server’s location in terms of network, host, and socket. You can specify whether you want to use SAP. 117369-B Rev. 00 5-61 Configuring IPX Services Using the BCC When you first configure SAP on an interface, it is automatically enabled. To change SAP’s state, navigate to the IPX SAP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: state disabled To enable SAP on an interface, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: state enabled For example, to disable SAP on IPX interface 0x00023456, enter: ipx/00023456# state disabled Using Site Manager To enable or disable SAP, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Enable parameter. Click on Help or see the parameter description on page A-41. 6. Click on OK. You return to the Configuration Manager window. NetWare Directory Services (NDS) and SAP Networks that implement NetWare 4.x use the NetWare Directory Services (NDS) to advertise services. NDS is a globally distributed network database that replaces the bindery used in NetWare versions earlier than 4.0. Workstations locate services by querying an NDS server. NDS maintains information about all 5-62 117369-B Rev. 00 Customizing IPX network resources (users, groups, servers, file volumes, printers, and so on) in a hierarchical tree structure. Network resources can be organized in the tree independent of their physical location. Thus, network users can access any network resource they have rights to without having to know the exact location of the resource. With NDS, users no longer need to log in or attach to specific servers. Instead, users can log in to the network and get access to all authorized network resources. NDS is compatible with bindery-based versions of NetWare through the bindery emulation feature of NDS. The NDS server distributes the service information using direct unicast-based protocols instead of using broadcast-based SAP. Therefore, the use of SAP in an NDS network is greatly reduced. Even in a network that includes only NetWare 4.0 servers, however, clients still use SAP to locate the nearest NDS server at startup. SAP and the NetWare Bindery (NetWare 3.x and Earlier) Novell IPX routers running NetWare versions earlier than 4.0 maintain a database called a bindery. The bindery includes information such as server type, IPX address, hop count, the interface to the server, a timer value for table entries, and a list of clients. If an entry in a bindery reaches its configured maximum age without being refreshed (timer resets to zero), the router deletes the entry from that bindery. Bay Networks routers implement a similar structure (a global services table) for these services. Each time an IPX router receives a SAP packet, it compares the packet’s contents to the contents of its SAP services table. If the SAP services table already contains information about a specific service, the router simply refreshes the age timer for that entry. If the SAP services table does not contain information about the service, and a route exists to the service, the router adds a new entry to the services table and advertises the new service to all connected networks (except the one on which it was received). Clients use SAP to request information about network services. Client information requests are nearest-service queries, which seek information on the closest service of a specified type. Every IPX server and IPX router on the internetwork learns about all other IPX servers and services through the propagation of bindery information or services table information. 117369-B Rev. 00 5-63 Configuring IPX Services By default, each SAP packet can contain up to seven Service Advertising updates. This number is configurable, but it’s constrained by the maximum transmission unit of the outbound interface. Configurable SAP Timers Configurable SAP timers are similar in function to configurable RIP timers, except that one pertains to SAP advertisements and the other to RIP advertisements. You configure the update interval by determining the timeout time, which consists of the frequency of SAP update transmissions and the holding multiplier for information received in SAP periodic updates. By default, the timeout time is three times the standard 60-second RIP advertisement update interval, or 180 seconds. Configuring SAP timers can reduce IPX SAP overhead and enhance bandwidth availability. You can eliminate periodic SAP advertisements by setting configurable SAP timers to zero; thus, only triggered SAP updates will be propagated. To ensure proper RIP operation, all configurable RIP timers must be set at equal advertisement intervals on all Bay Networks router interfaces attached to common IPX network segments. Note: While you can set configurable SAP timers on any Bay Networks router interface, do not use them on LAN interfaces, because IPX servers do not currently support configurable SAP broadcast timers. As a result, IPX servers will purge SAP entries after 180 seconds if they have not received any updates within this time interval. 5-64 117369-B Rev. 00 Customizing IPX Using the BCC To configure SAP timers, you must configure the SAP update interval and age multiplier for information received in SAP periodic updates. To specify a value for the SAP update interval, navigate to the SAP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: update-interval seconds seconds is from 0 to 2678400 seconds. For example, to set the update interval to 10,000, enter: sap/00023456# update-interval 10000 To specify an age multiplier, navigate to the SAP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: age-multiplier integer integer is from 1 to 6. For example, to set the age multiplier to 4, enter: sap/00023456# 117369-B Rev. 00 age-multiplier 4 5-65 Configuring IPX Services Using Site Manager To configure SAP timers, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interface. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the following parameters: • Update Interval • Age Multiplier Click on Help or see the parameter descriptions on page A-43. 6. Click on OK. You return to the Configuration Manager window. SAP via Default Route A SAP advertisement can be learned from an interface when the network number advertised in the SAP advertisement is unreachable, if a default route is accessible from that interface. This feature gives you the option of making SAP entries available if the IPX default route is reachable. If you enable SAP via default route, you enable IPX default routing globally for SAP advertisements and cause the router to accept a service if a direct or default router is known. If you disable SAP via default route, the router accepts a service only if a direct route to the server advertising the service is known. 5-66 117369-B Rev. 00 Customizing IPX Using the BCC To enable SAP advertising via the default route, navigate to the global IPX prompt (for example, box; ipx) and enter: sap-via-default-route enabled To disable SAP advertising via the default route, navigate to the global IPX prompt (for example, box; ipx) and enter: sap-via-default-route disabled Using Site Manager To enable or disable SAP advertising via the default route, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the SAP Via Default Route parameter. Click on Help or see the parameter description on page A-20. 6. Click on OK. You return to the Configuration Manager window. Enabling SAP Listen and Supply Functions The IPX router lets you enable the listen and supply modes for each IPX interface. When you enable the listen mode, the IPX router listens to SAP Periodic and Triggered updates from neighboring networks and conveys received SAP services information to its internal SAP services table. When you enable the supply function, the IPX router transmits all SAP Periodic and Triggered updates to routers in neighboring networks. 117369-B Rev. 00 5-67 Configuring IPX Services When you enable both the listen and supply mode, the IPX router performs both the listen and supply mode functions described above. The IPX router lets you determine whether the IPX router learns routes received in SAP updates from neighboring routers conveys received SAP services information to its internal SAP services table, transmits SAP periodic and triggered updates to routers in adjacent networks, or does both. By default, the IPX router learns routes ands transmits updates to routers in adjacent networks. Using the BCC To specify that IPX transmits periodic or triggered updates, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: supply enabled To specify that IPX does not transmit periodic or triggered updates, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: supply disabled For example, to specify that IPX interface transmit triggered updates, enter: rip/00023456# supply enabled To specify that IPX transmits learns routes received in SAP updates from neighboring routers, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: listen enabled To specify that IPX does not learn routes received in SAP updates from neighboring routers, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: listen disabled For example, to specify that the IPX interface learns routes received in SAP updates from neighboring routers, enter: rip/00023456# 5-68 listen enabled 117369-B Rev. 00 Customizing IPX Using Site Manager Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Mode parameter. Click on Help or see the parameter description on page A-42. 6. Click on OK. You return to the Configuration Manager window. Determining the Pace of SAP Packets The SAP pace determines the frequency, in packets per second, at which SAP sends packets on a circuit. By default, SAP sends 18 packets per second on a circuit. You can specify a SAP pace of 0 to 1000 packets per second. If you enter a value of zero, there is no limit on the pace. 117369-B Rev. 00 5-69 Configuring IPX Services Using the BCC To specify the RIP pace, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: pace packets_per_second packets_per_second is the number of packets, from 0 to 1000, that SAP sends per second. For example, to set the IPX SAP interface pace to 20 packets per seconds, enter: pace 20 Using Site Manager To specify the SAP pace, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Pace parameter. Click on Help or see the parameter description on page A-42. 6. Click on OK. 5-70 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Adjusting the SAP Packet Size By default the size of a SAP update packet is 480 bytes. You should leave the SAP packet size at the default level unless you have a specific reason for specifying a different size packet. If you must change the packet size, the packet size plus the IPX header (30 bytes) cannot exceed the MTU of the link. Using the BCC To specify the the SAP update packet size, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: packet-size bytes bytes is the size of the SAP packet in bytes. For example, to set the IPX SAP update packet size to 500, enter: packet-size 500 Using Site Manager To specify the packet size, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Packet Size parameter. Click on Help or see the parameter description on page A-44. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-71 Configuring IPX Services Responding to SAP Nearest Server Requests You can specify whether you want the router to respond to SAP get_nearest_server requests. By default, the router responds to a SAP get_nearest_server request. If you have disabled split horizon, you may want to change the setting so that the router does not respond to SAP get_nearest_server requests. Using the BCC To specify that SAP responds to get_nearest_server requests, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: nearest-server-reply enabled To specify that SAP does not respond to get_nearest_server requests, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: nearest-server-reply disabled Using Site Manager To specify whether SAP responst to get_nearest_server requests, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Nearest Server Reply parameter. Click on Help or see the parameter description on page A-44. 6. Click on OK. 5-72 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Using a Multicast Address By default, when you specify SAP on a router, the router uses a multicast address to send out SAP packets. You can accept the default, or change the setting to disallow multicast transmission of SAP packets. Using the BCC To allow multicast transmission of SAP packets, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: multicast enabled To disallow multicast transmission of SAP packets, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: multicast disabled Using Site Manager To determine whether IPX allows multicast transmission of SAP packets, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Use Multicast parameter. Click on Help or see the parameter description on page A-44. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-73 Configuring IPX Services Saving the Service Name By default, a router will save all 48 bytes in the service name field of SAP packets. If you specify that a router should not save all 48 bytes in the service name field, a router will ignore all characters after the null character when a service field name is less than 48 bytes. Using the BCC To cause the router to save all 48 bytes in the service name field of SAP packets, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: save-full-name enabled To cause the router to ignore all characters after the null character when a service field name is less than 48 bytes, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: save-full-name disabled Using Site Manager Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Save Full Name parameter. Click on Help or see the parameter description on page A-45. 6. Click on OK. 5-74 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Transmitting and Receiving SAP Updates over the Same Interface The IPX router, by default, uses split horizon updates, which causes the router to transmit SAP updates received from the interface over that same interface. By using split horizon updates, then the router generates SAP updates to be transmitted from an interface, the interface can exclude SAP servers learned on that interface. If you disable the split horizon updates, the router will transmit SAP updates received from one interface, but will transmit them using routes on a different interface. Refer to the “Configurable Split Horizon” section on page 5-54 for more information about Split Horizon. Using the BCC To cause the router to use split horizon updates, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: split-horizon enabled To specify that the router should not use split horizon updates, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: split-horizon disabled 117369-B Rev. 00 5-75 Configuring IPX Services Using Site Manager Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Split Horizon parameter. Click on Help or see the parameter description on page A-45. 6. Click on OK. You return to the Configuration Manager window. Updating Routers about a Failed Service By default, the router performs immediate SAP updates so that when a change in status occurs for a circuit, the router immediately propagates this status change to other routers in the internetwork. This facilitates network traffic by letting routers know immediately about new or failed routes. When you disable immediate SAP updates, other routers learn about such changes only at the next periodic update interval. Using the BCC To determine that routers know immediately about new or failed routes, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: triggered-update enabled To determine that routers know about new or failed routes only at the next periodic update interval, navigate to the IPX SAP interface prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: triggered-update disabled 5-76 117369-B Rev. 00 Customizing IPX For example, to cause the router to know about state changes immediately, enter: triggered-update enabled Using Site Manager To let routers know immediately about new or failed routes, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the Immediate Update parameter. Click on Help or see the parameter description on page A-46. 6. Click on OK. You return to the Configuration Manager window. Using Static Services When you statically configure NetWare services, the router learns about a NetWare service by means of the SAP information you enter using Site Manager. You can manually configure NetWare static services for each interface on a Bay Networks router. When you configure static services on an interface, you can then use SAP filters to eliminate the SAP announcements. The static service provides an alternative to broadcast Service Advertisement Protocol (SAP) announcements across a WAN. The static service eliminates WAN traffic (and hence, the use of WAN bandwidth) associated with WAN SAP Announcements. 117369-B Rev. 00 5-77 Configuring IPX Services Alternatively, you can disable SAP entirely on an individual-interface basis or disable just the SAP immediate update messages. For network topologies that include slower-speed WAN links, reducing the amount of WAN bandwidth otherwise needed for SAP announcements can be helpful. You can also reduce traffic by setting the Update Interval parameter to zero, which indicates no periodic SAP updates and no aging of SAP information resulting from periodic updates. In this case, SAP immediate updates still propagate through the network. You can also configure the interface to disable immediate updates by disabling the Immediate Update parameter. Using the BCC To reduce traffic and disable immediate updates, you must configure the SAP update interval and determine whether you want to use immediate SAP updates. To specify a value for the SAP update interval, navigate to the SAP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: update-interval seconds seconds is from 0 to 2678400 seconds. For example, to set the update interval to 10,000, enter: sap/00023456# update-interval 10000 To enable immediate updates, navigate to the SAP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: triggered-update enabled To disable immediate updates, navigate to the SAP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: triggered-update disabled 5-78 117369-B Rev. 00 Customizing IPX Using Site Manager To reduce traffic and disable immediate updates, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose SAP. The IPX SAP Circuit window opens. 5. Set the following parameters: • Update Interval • Immediate Update Click on Help or see the parameter descriptions on pages A-43 and A-39. 6. Click on OK. You return to the Configuration Manager window. A service sends an immediate update when one of the following conditions occurs: • A service first comes up. • A service changes. • A service is no longer available. For more information about the Update Interval parameter, see “Configuring RIP and SAP Broadcast Timers” in this chapter. Figure 5-7 shows a sample network configured to use static SAP services. If you want client 1 to have access only to file server 3, you configure file server 3 in the static SAP Service table on router 2’s interface. Then, to suppress any SAP broadcasts from router 1 and thus reduce bandwidth use, you can either turn off the SAP supply or disable SAP. 117369-B Rev. 00 5-79 Configuring IPX Services File server 1 SAP filter set to Suppress R1 R2 File server 2 File Server 3 configured in static SERVICE table Client 1 File server 3 IPX0012A Figure 5-7. Static Service Network Configuration Figure 5-8 shows another example, in which a SAP filter is configured on router R1, prohibiting periodic SAP advertisements and triggered SAP updates from being propagated over the wide area link. As a result, the services resident on server A or server B are not visible to networks C and D. However, SAP services resident on servers A and B are manually entered into router R2’s service table. This way, these servers are visible to IPX end stations on networks C and D (through periodic SAP advertisements, which are broadcast over router R2’s LAN interfaces every 60 seconds, in conformance with IPX specifications). The key benefit in this example is that SAP overhead is eliminated over the WAN link. 5-80 117369-B Rev. 00 Customizing IPX SAP entries pertaining to Servers A and B manually entered and broadcast over attached LAN interface R1 Network A R2 Network C Server A Network B Server B Network D Drop outbound SAP updates pertaining to Server A and Server B IPX0013A Figure 5-8. IPX SAP Filters Prohibiting SAP Broadcasts You add, edit, or delete static services through the IPX Static Services window. For instructions, see “IPX Static Service Configuration Parameters” in Appendix A. You can configure only services that have valid network addresses. Valid network addresses are provided either by RIP or by statically configured routes. If you try to enter any services that have invalid network addresses in the router configuration, the router accepts the information, but the services are unreachable. Note: Broadcast mechanisms, such as periodic RIP and SAP advertisements, can force dial-on-demand connections to be continuously established, preventing user-defined dial-on-demand expiration time limits from being reached. See the next section for more information. Enabling Static Services Enable a static service to restore client access to NetWare services configured earlier on the IPX interface. Disable a static service to make NetWare services configured earlier unavailable to clients. 117369-B Rev. 00 5-81 Configuring IPX Services Using the BCC When you first configure a static service, by default it ie enabled. To change the state of a static service to disabled, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service/00023456/printer/ 0987) and enter: state disabled To enable a static service, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service/00023456/printer/0987) and enter: state enabled For example, to disable the static service named printer, enter: static-service/00023456/printer/0987# state disabled Using Site Manager To enable or disable a static service, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Click on Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Click on Static Serv. The IPX Static Services window opens. 5. Set the Enable parameter. Click on Help or see the parameter description on page A-65. 6. Click on OK. 5-82 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Specifying the Network Address of a Service When you are using a static service, the network address for the service must exist as an entry in the IPX routing table. The router can learn the entry dynamically, or you can configure the entry as a static route. If you configure the entry as a static route, enter a network address of up to 8 hexadecimal characters. Using the BCC To specify the address for the static service, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service/ 00023456/printer/0987) and enter: target-network address address is the network address for the service in hexadecimal notation. For example, to specify 0x980976 as the address for a static service, enter: static-service/00023456/printer/0987# target-network 0x980976 Using Site Manager To specify the address for the static service, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Click on Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Click on Static Serv. The IPX Static Services window opens. 5. Set the Target Network (hex) parameter. Click on Help or see the parameter description on page A-65. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-83 Configuring IPX Services Specifying the Address of the Host that Provides a Service You must specify the address of a remote IPX host (a NetWare server) that can provide local clients with specific NetWare services, such as file, print, gateway, or terminal server services. The remote IPX host address consists of a string of up to 12 hexadecimal characters (6 bytes). Using the BCC To specify the address of a remote IPX host, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service/ 00023456/printer/0987) and enter: host-number address address is the address of a remote host in hexadecimal format. For example, to specify 0x92416 as the address for a remote host, enter: static-service/00023456/printer/0987# host-number 0x92416 Using Site Manager To specify the address of a remote IPX host, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Click on Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Click on Static Serv. The IPX Static Services window opens. 5. Set the Host Number (hex) parameter. Click on Help or see the parameter description on page A-65. 6. Click on OK. 5-84 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Assigning a Symbolic Name to Your Service You must assign a symbolic name to the service you want to advertise. Use the actual name of the server that the clients will attach to. Make this name meaningful to the network administrator. The name must be unique among all names assigned to IPX servers of the same type on the IPX internetwork. See the documentation that came with your NetWare operating system for guidelines on specifying a server name. Using the BCC When you first configure a static service, you must supply a symbolic name for a service. To change the symbolic name for a service, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service/ 00023456/printer/0987) and enter: service-name name name is an alphanumeric string naming a remote service. For example, to give the name gateway to the service you want to advertise, enter: static-service/00023456/printer/0987# 117369-B Rev. 00 service-name gateway 5-85 Configuring IPX Services Using Site Manager To assign a symbolic name to the service you want to advertise, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Click on Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Click on Static Serv. The IPX Static Services window opens. 5. Set the Service Name parameter. Click on Help or see the parameter description on page A-61. 6. Click on OK. You return to the Configuration Manager window. Entering the Service Type Number You must specify the Novell service type number in 4-digit hexadecimal format, including leading zeros. This number specifies the type of service to advertise from the associated IPX (LAN) interface. See Appendix C for a list of common service types. 5-86 117369-B Rev. 00 Customizing IPX Using the BCC To change the service type for a static service, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service 00023456/printer/0987) and enter: service-type type type is a number in 4-digit hexadecimal format (including leading zeros). For example, to specify the Novell service type number as 0x9876, enter: static-service/00023456/printer/0987# service-type 0x9876 Using Site Manager To specify the service type for a static service, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Click on Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Click on Static Serv. The IPX Static Services window opens. 5. Set the Service Type (hex) parameter. Click on Help or see the parameter description on page A-62. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-87 Configuring IPX Services Entering the Socket Address of a Service You must enter a socket address consisting of 4 hexadecimal characters when you are using a static service. Valid socked addresses have a value between 0x0001 and 0xFFFE. Using the BCC To enter a socket address for a static service, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service/ 00023456/printer/0987) and enter: socket address address is a 4-digit hexadecimal socket address. For example, to enter the socket address 0x1234, enter: static-service/00023456/printer/0987# socket address 0x1234 Using Site Manager To enter the socket address, complete the following tasks:. Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Click on Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Click on Static Serv. The IPX Static Services window opens. 5. Set the Socket parameter. Click on Help or see the parameter description on page A-66. 6. Click on OK. 5-88 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Entering the Hop Count Enter the number of router hops that exist between a router and a specific remote Novell server or service. The number of router hops must be in the range of 1 to the number of maximum hops minus 1. The default number of hops is 1. Using the BCC To specify the number of hops, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service/00023456/printer/ 0987) and enter: hops number_of_hops number_of_hops is in the range of 1 to the maximum number of hops minus 1. For example, to enter the maximum number of hops of 3, enter: static-service/00023456/printer/0987# hops 3 Using Site Manager To specify the number of hops, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Click on Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Click on Static Serv. The IPX Static Services window opens. 5. Set the Hop Count parameter. Click on Help or see the parameter description on page A-66. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-89 Configuring IPX Services Customizing NetBIOS Static Routing NetBIOS establishes sessions (logical connections) and allows for communication between PCs. The Bay Networks NetBIOS static route function lets you map NetBIOS names to IPX destination networks by configuring a NetBIOS static route to a NetBIOS service name. The IPX router then converts the broadcast NetBIOS packets to directed broadcast NetBIOS packets, which are usually forwarded to all network interfaces on a single network. This reduces the amount of network traffic due to NetBIOS query requests; that is, broadcasts issued by NetBIOS clients seeking to find and establish sessions with specific NetBIOS applications over an IPX internetwork. Besides minimizing NetBIOS broadcast traffic, using NetBIOS static routes allows a more precise logical partitioning of an IPX NetBIOS internetwork, enhancing internetwork security. The Bay Networks IPX router software lets you specify whether: • You want to direct a NetBIOS broadcast (type 20) packet through a network by configuring a static route only at the first router. Before the packet is directed out an interface, the router software overwrites the IPX destination address of the packet so that it can be routed to its destination. Because the IPX specification states that the network address of broadcast packets must be left unchanged, this option does not conform to Novell standards. • You want the router to propagate a packet out all of its interfaces (in conformance with Novell standards). • You want to direct a packet to its destination by configuring a static route for each hop in the network (in conformance with Novell standards). In the NetWare environment, NetBIOS query requests are encapsulated within IPX packets. When a Bay Networks router receives an IPX packet containing a NetBIOS query request, it compares the NetBIOS name for which a connection is being requested to a statically configured NetBIOS Name-to-IPX Destination Network table. If the requested NetBIOS name matches a table entry, the Bay Networks router forwards the query request packet out only one IPX interface toward the destination network. If a match does not exist, the router propagates the query request packet out of all IPX interfaces, in conformance with the IPX specification. 5-90 117369-B Rev. 00 Customizing IPX In Figure 5-9, for example, when end system ES2 wants to find and establish a connection to a NetBIOS application on the IPX server ES2, it generates a query request broadcast packet. Router R1 receives the broadcast packet, consults its NetBIOS Name-to-IPX Destination Network table, finds that the NetBIOS application being requested is mapped to network B, and routes the packet out interface 1. Similarly, router R3 consults its NetBIOS Name-to-IPX Destination Network table upon receiving the NetBIOS query request, and routes the packet out its interface to network B. R2 Interface 3 Tick Delay = 6 ES1 R1 Interface 1 Tick Delay = 3 ES2 R3 Network B Network A Interface 2 Tick Delay = 12 IPX server IPX0015A Figure 5-9. NetBIOS Static Routes Each IPX router interface supports up to 50 NetBIOS static routes. Each NetBIOS static route specifies a NetBIOS resource name and a destination network where the resource resides. Activating the Static Route Record in the NetBIOS Routing Table You can specify the state (active or inactive) of the static route record in the NetBIOS routing table. If you are sending NetBIOS packets through a network, you should enable this feature. 117369-B Rev. 00 5-91 Configuring IPX Services Using the BCC When you initially activate the static route record, you must supply the symbolic name of the target server as well as the address of the target network. To initially activate the static route record, navigate to the global IPX prompt (for example, box; ipx) and enter: static-netbios-route target-name name target-network address name is the symbolic name of the target server. address is the address, in hexadecimal notation, of the target network. To enable the static route record in the NetBIOS routing table, navigate to the NetBIOS static route prompt (for example, box; ipx; static-netbios-route/ route6/00042567) and enter: state enabled To disable the static router record in the NetBIOS routing table, navigate to the NetBIOS static route prompt (for example, box; ipx; static-netbios-route/ route6/00042567) and enter: state disabled Using Site Manager To activate or deactivate the static route record, complete these tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose NetBIOS Static Routes. The IPX NetBIOS Static Routes window opens. 4. Set the Enable parameter. Click on Help or see the parameter description on page A-49. 5. Click on OK. 5-92 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Entering the Name of the NetBIOS Target Server When you send NetBIOS packet over a network, you must specify the name of the NetBIOS target server, which can be up to 16 alphanumeric characters. The name of a NetBIOS target server can include wildcard and pattern-matching characters, any printable character, including $, #, and so on. To specify a backslash, enter two backslashes (\\). You can also use the hexadecimal equivalent (\xx) of any valid ASCII character. For example, you can specify \20 for space or \21 for ! (note that \xx counts as one character). For a list of the wildcards and pattern-matching characters, refer to Table 5-1 on page 5-142. Using the BCC When you activate the NetBIOS static route record, you must specify the target server name. To change the name of the NetBIOS target server, navigate to the NetBIOS static route prompt (for example, box; ipx; static-netbios-route route6/00042567) and enter: target-name name name is the symbolic name of the target server. For example, to specify that the name of the target server is route12, enter: static-netbios-route/route6/00042567# 117369-B Rev. 00 target-name route12 5-93 Configuring IPX Services Using Site Manager To specify the name of the NetBIOS target server, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose NetBIOS Static Routes. The IPX NetBIOS Static Routes window opens. 4. Click on Add. The IPX NetBIOS Static Route Configuration window opens. 5. Set the Target Server parameter. Click on Help or see the parameter description on page A-47. 6. Click on OK. You return to the Configuration Manager window. Note: The Configuration Manager does not let you reconfigure the Target Server parameter for a static route. If you want to change this parameter, you must delete the static route and add a new route. However, you can reconfigure all other parameters associated with a static route. Entering the Target Network Address When you send NETBIOS packets over a network, you must specify the address of a destination network that you want to receive NetBIOS broadcast packets destined for the specified target server. You can specify a target network address of up to 8 hexadecimal characters. 5-94 117369-B Rev. 00 Customizing IPX Using the BCC When you activate the NetBIOS static route record, you must specify the address of a destination network. To change the the destination network address, navigate to the NetBIOS static route prompt (for example, box; ipx; static-netbios-route/ route6/00042567) and enter: target-network address address is the address, in hexadecimal notation, of the target network. For example, to specify that the name of the target server is 0x678098, enter: static-netbios-route/route6/00042567# target-name 0x678098 Using Site Manager To specify the address of a destination network to receive NetBIOS broadcast packets, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose NetBIOS Static Routes. The IPX NetBIOS Static Routes window opens. 4. Click on Add. The IPX NetBIOS Static Route Configuration window opens. 5. Set the Target Network parameter. Click on Help or see the parameter description on page A-47. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-95 Configuring IPX Services Directing a NetBIOS Packet Using Nonstandard Static Routing You can direct a NetBIOS packet through a network by configuring a NetBIOS static route in the first Bay Networks router to receive a NetBIOS broadcast packet. To do this, you must disable Novell Certification Conformance for all routers in the network. To configure a router to propagate a packet out all of its interfaces -- which conforms to Novell standards -- you set the Novell Certification Conformance parameter on the Edit IPX Advanced Global Parameters window to Enable. You must set this parameter to Enable for all routers on the network. All NetBIOS packets sent from a client to the router must have a destination network value of zero, unless the packet passes a static route in the router. The router tests a packet against the static route table before it checks the packet’s destination, thus allowing the router to accept packets that may not have a destination network of zero. Caution: This method of defining IPX NetBIOS static routes is a nonstandard Bay Networks feature that may not be compatible with routers from other vendors. This method converts a NetBIOS broadcast packet to a NetBIOS directed broadcast packet, thereby eliminating the loop checking and path tracing that is usually done for NetBIOS broadcast packets. This may cause problems with applications that rely on those mechanisms. When you configure a NetBIOS static route, the IPX router inserts the network number configured in the static route into the destination network number of the IPX packet. When you configure NetBIOS static routes on an interface, the IPX router compares all IPX NetBIOS broadcast packets received on the interface with the boxwide NetBIOS static routes. If the NetBIOS destination name found in the packet matches an entry in the routing table, the NetBIOS packet is routed to the associated destination network. If no match is found, the IPX router treats the packet as specified by the NetBIOS Accept and NetBIOS Deliver parameters. 5-96 117369-B Rev. 00 Customizing IPX Using the BCC To enable Novell certification, navigate to the global IPX prompt (for example box; ipx) and enter: novell-certification-conformance enabled To disable Novell certification, navigate to the global IPX prompt (for example box; ipx) and enter: novell-certification-conformance disabled Using Site Manager To enable or disable Novell certification conformance, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Global. The IPX Global Parameters window opens. 4. Click on Advanced. The IPX Advanced Global Parameters window opens. 5. Set the Novell Certification Conformance parameter. Click on Help or see the parameter description on page A-21. 6. Click on OK. You return to the Configuration Manager window. Directing a NetBIOS Packet Using Standard Static Routing If you want to configure NetBIOS static routes in conformance with Novell standards, you must configure a static route for each hop in the network. After you specify the static route to a NetBIOS name, the IPX router converts standard NetBIOS broadcast packets to NetBIOS directed broadcast packets. 117369-B Rev. 00 5-97 Configuring IPX Services • NetBIOS broadcast packets are sent to all accessible host IDs on all accessible IPX networks. • NetBIOS directed broadcast packets are sent to all host IDs on a single IPX network. NetBIOS Broadcast Filters You can control the propagation of IPX NetBIOS broadcasts by configuring NetBIOS broadcast filters on an interface. This feature ensures that visibility to NetBIOS resources is limited only to networks that need to have access to certain resources. This capability can enhance security and preserve bandwidth by controlling the flow of NetBIOS traffic. You can configure an interface to either accept or not accept NetBIOS broadcasts from an attached network, and to deliver or not deliver NetBIOS broadcasts to a network. By default, both of these parameters are disabled. Using the BCC To specify that an interface accepts NetBIOS broadcasts from an attached network, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: netbios-accept enabled To specify that an interface does not accept NetBIOS broadcasts from an attached network, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: netbios-accept disabled To specify that an interface delivers NetBIOS broadcasts from an attached network, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: netbios-deliver enabled To specify that an interface does not deliver NetBIOS broadcasts from an attached network, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: netbios-deliver disabled 5-98 117369-B Rev. 00 Customizing IPX Using Site Manager To configure NetBIOS broadcast filters on an interface, complete these tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set thefollowing paramters: • NetBIOS Accept • NetBIOS Deliver • Maximum Path (hex) parameter. Click on Help or see the parameter descriptions on page A-27. 5. Click on OK. You return to the Configuration Manager window. Note: The description that follows assumes that the NetBIOS destination name found in the packet does not match an entry in the NetBIOS Static Routing table. 117369-B Rev. 00 5-99 Configuring IPX Services When you enable an IPX interface to accept NetBIOS broadcasts, the IPX router accepts NetBIOS broadcast packets received on that interface. For example, in Figure 5-10, the IPX router accepts NetBIOS broadcast packets received only on interfaces 1 and 2. Network 1 Network 2 Interface 1 accept enabled deliver enabled IPX router Interface 3 accept disabled deliver enabled Network 3 Interface 2 accept enabled deliver disabled Interface 4 Accept disabled deliver disabled Network 4 IPX0016A Figure 5-10. NetBIOS Packet Filtering When you enable an IPX interface to accept NetBIOS broadcasts, the IPX router delivers NetBIOS broadcast packets that are routed to that interface. For example, in Figure 5-10, the IPX router delivers NetBIOS broadcast packets only to interfaces 1 and 3. The arrows in Figure 5-11 show the flow of packets in this same model. 5-100 117369-B Rev. 00 Customizing IPX Network 1 Network 2 IPX router Network 3 Network 4 IPX0017A Figure 5-11. NetBIOS Packet Flow You must enable an IPX interface to accept or deliver NetBIOS boradcasts for delivery of such packets to occur. For example, interface 1 can deliver only packets from interface 2 to network 1, because interface 2 is the only other interface that has been configured to accept NetBIOS broadcasts. Thus, NetBIOS client applications on network 1 can initiate and establish sessions with NetBIOS server applications only on network 3. NetBIOS client applications on network 2 can initiate and establish sessions with NetBIOS server applications only on networks 1 and 3. Client applications on networks 3 and 4 cannot initiate any sessions with NetBIOS server applications via the IPX router. 117369-B Rev. 00 5-101 Configuring IPX Services As another example, in Figure 5-12, NetBIOS broadcasts from the end system ES1 on network A are accepted by router R1, but can be prohibited from network C by disabling the interface of router R1 connected to network C from delivering NetBIOS broadcasts. NetBIOS broadcasts will still be delivered on network B. ES 2 ES1 R1 Network A Network B Disable "Deliver NetBIOS broadcasts IPX server Network C IPX0018A Figure 5-12. NetBIOS Broadcast Filtering Configuring an Adjacent Host for an Interface You can determine how the IPX router sends packets to a specific IPX host by configuring an IPX adjacent host. You can configure the adjacent host only if you are not using RIP on a circuit. Adjacent hosts typically use WAN media and do not require RIP. Making the Adjacent Host Record Active You can set the state (active or inactive) of the adjacent host record in the IPX routing tables. 5-102 117369-B Rev. 00 Customizing IPX Using the BCC To make the adjacent host active, you must first configure an adjacent host on an IPX interface. To configure an adjacent host, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: adjacent-host host-address address address is the address, in hexadecimal notation, of the adjacent host. For example: ipx/00023456# adjacent-host host-address 000012345678 To make the adjacent host active, navigate to the adjacent host prompt (for example, box; ethernet 2/1; ipx 00023456; adjacent-host host-address 000012345678) and enter: state enabled To make the adjacent host inactive, navigate to the adjacent host prompt (for example, box;ethernet 2/1; ipx 00023456; adjacent-host host-address 000012345678) and enter: state disabled For example: adjacent-host/00023456/000012345678# state enabled 117369-B Rev. 00 5-103 Configuring IPX Services Using Site Manager To specify the state of the adjacent host, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Adj. Hosts. The IPX Adjacent Hosts window opens. 5. Click on Add. The IPX Adjacent Host Configuration window opens. 6. Set the Enable parameter. Click on Help or see the parameter description on page A-53. 7. Click on OK. You return to the Configuration Manager window. Entering the ID of the Adjacent Host If you are not using RIP on a circuit, supply the host ID of the adjacent host. You can enter a host ID of up to 12 hexadecimal characters. 5-104 117369-B Rev. 00 Customizing IPX Using the BCC When you first configure an adjacent host, you must supply the host ID of the adjacent host. To configure an adjacent host and specify its address, navigate to the adjacent host prompt (for example, box; ethernet 2/1;ipx 00023456; adjacent-host host-address 000012345678) and enter: adjacent-host host-address address address is the address, in hexadecimal notation, of the adjacent host. For example: ipx/00023456# adjacent-host host-address 000012345678 Note: You cannot change the address of the adjacent host using the BCC. Using Site Manager To specify the host ID of the adjacent host, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Adj. Hosts. The IPX Adjacent Hosts window opens. 5. Click on Add. The IPX Adjacent Host Configuration window opens. 6. Set the Host Address parameter. Click on Help or see the parameter description on page A-51. 7. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-105 Configuring IPX Services Entering a WAN Address If the interface you are configuring is on an ATM or SMDS network, supply a WAN address of up to 16 hexadecimal characters. If the interface is on a frame relay network, enter a WAN address or a decimal data link connection identifier number. Using the BCC To specify a WAN address, navigate to the adjacent host prompt (for example, box; ethernet 2/1; ipx 00023456; adjacent-host host-address 000012345678 ) and enter: wan-number number number is one of the following: Number Interface Up to 16-character hexadecimal number ATM or SMDS network 5-106 Decimal DLCI number Frame relay network X.121 address X.25 switched virtual circuit Logical channel number X.25 permanent virtual circuit 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the WAN address, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Adj. Hosts. The IPX Adjacent Host window opens. 5. Click on Add. The IPX Adjacent Hosts Configuration window opens. 6. Set the Adjacent Host Address parameter. Click on Help or see the parameter description on page A-51. 7. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-107 Configuring IPX Services Creating a Frame Relay SVC to an Adjacent Host You can create a frame relay SVC to an adjacent host. You must first enable frame relay SVC broadcasts and then identify the SVC. Using the BCC To enable frame relay SVC broadcasts, navigate to the IPX interfaces prompt (for example, box; framerelay 3/1; ipx 00023456) and enter: svcbroadcast enabled To disable frame relay SVC broadcasts, navigate to the IPX interfaces prompt (for example, box; framerelay 3/1; ipx 00023456) and enter: svcbroadcast disabled To identify the SVC, you must supply: • Hexadecimal address of the remote party • Type of number used to establish an SVC to the adjacent host • Type of adjacent host To identify the remote party, navigate to the adjacent host prompt (for example, box; ethernet 2/1; ipx 00023456; adjacent-host host-address 000012345678 ) and enter: host-subaddress address address is an 8-digit hexadecimal number. For example, to set the subaddress to 0x67678934, enter: adjacent-host/00023456/000012345678# 5-108 host-subaddress 0x67678934 117369-B Rev. 00 Customizing IPX To identify the type of number used to establish an SVC to the adjacent host, navigate to the adjacent host prompt (for example, box; ethernet 2/1; ipx 00023456; adjacent-host host-address 000012345678) and enter: type-of-number option option is one of the following: international unknown For example, to set the type of number to international, enter: adjacent-host/00023456/000012345678# type-of-number international To identify the type of adjacent host, navigate to the adjacent host prompt (for example, box; ethernet 2/1; ipx 00023456; adjacent-host host-address 000012345678) and enter: type host_type host-type is one of the following: fre164 default frx121 frdlci For example, to set the type to fre164, enter: adjacent-host/00023456/000012345678# 117369-B Rev. 00 type fre164 5-109 Configuring IPX Services Using Site Manager To create an SVC to an adjacent host, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the FR SVC Broadcast parameter. Click on Help or see the parameter description on page A-51. 5. Click on OK. You return to the Configuration Manager window. 6. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 7. Choose IPX. The IPX menu opens. 8. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 9. Choose Adj. Hosts. The IPX Adjacent Host window opens. 10. Click on Add. The IPX Adjacent Hosts Configuration window opens. 11. Set the following parameters: • Remote Party Sub-Address • Remote Party Type of Number • Adjacent Host TYpe Click on Help or see the parameter description on page A-51. 12. Click on OK. 5-110 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Dial Services A dial service provides access to a switched network by means of a dial-up line (also called a switched line). Dial-up lines are active only as-needed -- that is, when there is data to send across the network, or when a dial-up line acts as a resource for a failed or congested leased line. Dial-up lines can be a cost-effective alternative to leased lines and packet networks, which are permanent connections and therefore available regardless of network traffic. If you send a limited amount of data or your data transmission is intermittent, dial-up lines can be less expensive than leased lines and they maximize network performance and flexibility. The Bay Networks router provides three types of dial services: dial-on-demand, dial backup, and bandwidth-on-demand. Each dial service serves a different purpose: • Dial-on-demand service reduces your line costs by establishing a connection between two devices only when there is data to send. You do not incur the cost of a leased line that is active regardless of data traffic. • Dial backup service provides a backup circuit when a leased circuit fails. The backup circuit serves as an alternative path for data to reach the destination. • Bandwidth-on-demand service provides up to 29 additional lines for a congested leased line, a dial-on-demand line, or a leased multilink bundle. This provides a total of 30 lines for communication. The additional lines increase bandwidth for data traffic, improving communication and reducing network delays. For more information about dial services, refer to Configuring Dial Services. 117369-B Rev. 00 5-111 Configuring IPX Services Using Dial-on-Demand Service Dial-on-demand supports synchronous lines (RS232, V.35, RS422, and X.21) and ISDN interfaces. When dial-on-demand is configured, the router activates a dial-on-demand circuit for any one of the following reasons: • The router has data to send across the circuit. When the router has data to transmit, it automatically selects one of the demand lines from the circuit’s associated demand pool. As long as data is going across the line, the end-to-end connection remains active. • You enabled a force dial. The router forces the establishment of a circuit. You enabled the Force Dial parameter to immediately activate a line and establish a connection. Using this parameter, you can force the connection to come up, regardless of whether there is data activity. The router brings down the circuit for any one of these reasons: • The configured inactivity time expires. • You scheduled the circuit to come down. • You enabled a forced take down. Figure 5-13 shows a dial-on-demand line connecting two routers. In this example, when the router has data to transmit across a demand circuit, or when you configure the router to bring up a demand circuit, the router instructs the dial device to establish a connection. Note: Do not configure IPX adjacent hosts with dial-on-demand circuits. 5-112 117369-B Rev. 00 Customizing IPX Data arrives at the New York router, but final destination is Dallas. A port in the demand pool transmits the data. Los Angeles Dial device Demand pool 1: Slot 2 Chicago New York Dial device Back of router Dial device Dial device Dallas Dial device IPX0014A Figure 5-13. Dial-on-Demand Service Using Static Routing with Dial-on-Demand As part of its standard operation, IPX sends update packets to maintain routing tables and to gather information about network resources. For dial-on-demand, the frequency of these update packets forces the dial-up connection to remain up permanently, unless you configure a time of day to bring the connection down. When you configure dial-on-demand circuits, you should disable broadcast messages. The router then uses static routes to determine the location of the destination network. 117369-B Rev. 00 5-113 Configuring IPX Services Tips for Using Dial-on-Demand with IPX The following suggestions may help improve overall system efficiency if you’re using dial-on-demand with IPX: • Turn off triggered updates. • Set the periodic update interval to a large value -- the line will be called only infrequently. • Use service filtering and/or route filtering. • Use static routes and static services. • Use the default route. • Enable local watchdog acknowledgment (“spoofing”). • Use traffic filters and protocol prioritization to prohibit routing updates and protocol-specific messages from keeping the circuit up unnecessarily (see Configuring Traffic Filters and Protocol Prioritization for details). Local IPX Watchdog Acknowledgment In a NetWare network, NetWare servers broadcast “watchdog” packets to verify that client nodes are still connected to the server. Watchdog packets are just another form of a data packet. To maintain the connection, the client must respond to this watchdog message (essentially, responding to a poll). With a dial-up connection (that is, when you want to establish periodic connectivity to a remote site using the dial-on-demand feature), this polling mechanism could mean dialing the phone line just to keep the server from bringing down the connection. In addition, the bandwidth consumed by periodic RIP/SAP and watchdog broadcast packets can represent a significant portion of the total dial cost when charged on a per-packet basis. Depending on the network configuration and the application, this excessive broadcast activity can reduce application access performance. To address this problem, Bay Networks routers can use local watchdog acknowledgment to improve the efficiency of IPX wide area links. This feature, also known as “watchdog spoofing,” lets Bay Networks routers locally respond to broadcast IPX watchdog packets on behalf of clients connected over dial-in connections. 5-114 117369-B Rev. 00 Customizing IPX Without local watchdog acknowledgment, each time a server sends an IPX watchdog packet to a logically connected client, the dial-on-demand link will be established and remain up to support the communication between the client and the server (that is, the watchdog packets). Within an IPX network, servers rely on client watchdog acknowledgments to verify that client sessions are still active with the server. The router closest to the server responds on behalf of the client. As a result, NetWare servers may reach the maximum client sessions supported by the server, although not all clients are truly maintaining a session. This can happen if the client does not perform a standard closure of the session; for example, if the client PC is rebooted. You can avoid this potential problem by implementing NetWare’s auto logoff feature to ensure that client sessions are released when they are no longer in use. Using the BCC To configure the router to use local watchdog acknowledgement, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555) and enter: watchdog-spoofing enabled To configure the router not to use local watchdog acknowledgement, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555) and enter: watchdog-spoofing disabled For example, to configure an IPXWAN interface to use local watchdog acknowledgement, enter: ipxwan/00055555# 117369-B Rev. 00 watchdog-spoofing enabled 5-115 Configuring IPX Services Using Site Manager To configure the router to use local watchdog acknowledgment, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the IPX Watchdog Spoofing parameter. Click on Help or see the parameter description on page A-29. 5. Click on OK. You return to the Configuration Manager window. Local SPX Keepalive Acknowledgment In a NetWare network, SPX keepalive packets are periodically transmitted to maintain SPX sessions between client and servers. To prevent these packets from initiating calls on Dial-on-Demand circuits, the router will acknowledge these SPX keepalive packets. Dial Optimized Routing Dial optimized routing lets you exchange IPX RIP/SAP routing updates only when a connection is active for data transmission. By limiting when the router can send updates, dial optimized routing reduces unnecessary connections and line costs. For each dial-on-demand circuit, you have the choice of enabling dial optimized routing. If you enable dial optimized routing, the router establishes a demand connection only for outbound data packets or through requests from the protocol. The presence of IPX RIP/SAP packets alone will not trigger a dial connection. If you disable optimized routing, any packet can initiate demand connections. 5-116 117369-B Rev. 00 Customizing IPX Once you have enabled dial optimized routing on a dial on demand circuit, the only times the router sends routing updates independent of data are: • The first time an IPX interface becomes active • Triggered updates while the circuit is active • Scheduled updates using a broadcast timer You can use dial optimized routing for IPX only after you have enabled it on a PPP dial-on-demand circuit. Refer to “Configuring Dial Services” for information on how to enable dial optimized routing. Getting Optimum Performance Using IPX Dial Optimized Routing To use dial optimized routing optimally, Bay Networks recommends that you follow the practices described below: 1. Set the Inactivity Mode parameter to Transmit Only. Any other setting causes the inactivity mode to reset when the receive end cannot filter serialization, watchdog, and keepalive packets for NORESET. These packets could keep the demand line active for long periods of time. 2. Stop the router from clipping packets when an IPX DOR packet comes up or changes state. As IPX routes and services grow in number, IPX RIP and SAP packets may be clipped when an IPX DOR circuit comes up or changes state. To stop the clipping, reduce the value of the Pace parameter for RIP and SAP packets, or change the RIP/SAP packet size for the IPX DOR circuit. You should reduce the RIP/SAP Pace parameter for IPX DOR circuits to accommodate the number of IPX routes and services in the network. 3. Reduce the frequency of bringing up the line for time synchronization packets. No default priority queuing filters exist for IPX diagnostics packets or packets used in Netware Directory Services (NDS) time synchronization. You can configure a priority queueing filter to keep IPX diagnostic packets from bringing up a demand line. However, since the Bay Networks IPX ping packet is a diagnostic packet, the filter will affect it as well. NDS time synchronization packets are treated as data packets. You can configure NetWare servers for larger polling intervals to reduce the frequency of bringing up the line for time synchronization packets. 117369-B Rev. 00 5-117 Configuring IPX Services Default IPX Dial Optimized Routing Filters When you enable IPX on a dial-optimized routing circuit, several Priority Queuing (PQ) filters are created, by default, to reduce call initiation by various IPX packets. These filters prevent IPX watchdog packets, SPX keepalive packets, and IPX serialization packets from initiating calls or resetting the inactivity timer on IPX demand circuits. Enabling or disabling dial optimized routing on an IPX circuit affects the amount of time that RIP/SAP waits before sending out initial route information when the dial-on-demand route first becomes enabled, and the frequency of RIP/SAP updates. Enabling or disabling dial optimized routing on an IPX circuit changes the default values of the RIP/SAP delay period to 120 seconds and RIP/SAP update interval to 3600 seconds. If you enable dial optimized routing after configuring IPX on a circuit, you should go back and set the Stabilization Timer Delay to 120 seconds and RIP/SAP Update Interval to 3600 seconds. If you disable dial optimized routing, go back and change the RIP/SAP delay period and RIP/SAP update interval to the original default value. Using the BCC To set the maximum number of paths, you must configure: • RIP/SAP delay period • Update interval for RIP and/or SAP To set the RIP/SAP delay period to the default value of 120 seconds, navigate to the IPX interface prompt (for example, box; ethernet 2/1; ipx 00023456) and enter: stabilization-timer 120 To change the RIP update interval period to 3600 seconds, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: update-interval 3600 To change the update interval period to 3600 seconds, navigate to the SAP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: update-interval 3600 5-118 117369-B Rev. 00 Customizing IPX Using Site Manager To change the update interval period, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the following parameters: • Timer Delay • Update Interval (sec) Click on Help or see the parameter descriptions on pages A-29, A-37, and A-43. 6. Click on OK. You return to the Configuration Manager window. Configuring the Routing Update Delay Timer You can define the amount of time, from 0 to 2147483674 seconds, to delay the sending of RIP/SAP updates on a circuit after the dial-on-demand circuit has been enabled. Generally, the more routes that a router is expected to handle or the more dynamic the network is, the higher the value you should set (from 0 to 60 seconds). This timer prevents the router from dialing the remote site multiple times (each time after it collects a subset of routes). For information on how to set the delay period, refer to “Setting the Stabilization Timer Delay” on page 5-34. RIP/SAP Triggered Updates IPX sends triggered updates whenever a routing change occurs while the dial-on-demand circuit is active. However, with dial optimized routing enabled, triggered updates will not initiate a dial-on-demand connection. The updated information will, however, be held in the routing table and forwarded the next time the circuit comes up for data transmission or for a scheduled update. 117369-B Rev. 00 5-119 Configuring IPX Services Determining the Frequency of Scheduled Updates By default, IPX sends out scheduled updates every 60 seconds. You can regulate the frequency of broadcast updates. The value you specify for the frequency of scheduled updates allows the router to accumulate routes for the specified period of time. The higher the number you specify, the longer the time available to accumulate routes and the less frequent the transmissions. If you specify zero, the router will not send out any periodic RIP updates over the IPX interface. However, RIP immediate (one-time) update packets still propagate through the network, in compliance with Novell standards. Using the BCC To regulate the frequency of broadcasts, you must configure the RIP update interval and decide whether you want to use IPX watchdog spoofing. To adjust the frequency of RIP update packet transmissions, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: update-interval seconds seconds is from 0 to 2678400 seconds. To enable a router to respond locally to watchdog packets, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555#) and enter: watchdog-spoofing enabled To disable a router from responding locally to watchdog packets, navigate to the IPXWAN prompt (for example, box; serial 3/1; ppp; ipxwan 00055555#) and enter: watchdog-spoofing disabled 5-120 117369-B Rev. 00 Customizing IPX Using Site Manager To regulate the frequency of broadcasts, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the following parameters: • Update Interval (sec) • IPX Watchdog Spoofing Click on Help or see the parameter descriptions on pages A-37 and A-29. 6. Click on OK. You return to the Configuration Manager window. You must enable IPX watchdog spoofing or the router will continually dial the circuit whenever watchdog packets are sent. When enabled, watchdog spoofing enables a router to respond locally to IPX watchdog packets on behalf of clients. Without these packets, endpoints have no way to tell if a peer has become unreachable. To enable or disable watchdog spoofing, see “Local IPX Watchdog Acknowledgment” on page 5-114. Enabling local watchdog spoofing also enables SPX keepalive spoofing. Configuring RIP and SAP Broadcast Timers A Bay Networks router running IPX lets you control the frequency of RIP and SAP update packet transmissions over both local and wide area links. RIP and SAP transmissions provide the following benefits: • 117369-B Rev. 00 You spend less time manually configuring changes to static services and service routes across your network. 5-121 Configuring IPX Services • You reduce the cost of administering Bay Networks routers installed across your network, compared to the cost of building static routes or static services tables. • You allow a router to respond to changes in services and routes offered on the network. • You enable users to have more accurate, up-to-date information on services and service routes offered on the network. However, periodic RIP and SAP transmissions mean: • Less bandwidth is available for user data. Consequently, user data transmissions take longer, thereby increasing WAN line costs. • You sacrifice some level of manual control over services and routes made available to network users. Your particular networking environment may require a higher degree of manual control over information on services and service routes offered to users on your network. When you adjust the frequency of RIP and SAP update packet transmissions, the higher the number you specify, the less frequent the transmissions. If you specify zero, no periodic RIP or SAP updates are sent out the IPX interface of the router. However, RIP and SAP immediate (one-time) update packets still propagate through the network, in compliance with Novell standards. The default interval is 60 seconds. Eliminating periodic RIP and SAP updates provides the following benefits: • Reduced RIP and SAP overhead on your network • Increased bandwidth available for user data • Reduced WAN line costs for packet transmission • Increased manual control over network services and routes However, not having periodic RIP and SAP transmissions means: 5-122 • A slower response time of the network to changes in network services and routes • An increase in the time and cost of administering changes to services and service routes made available through Bay networks routers on your network 117369-B Rev. 00 Customizing IPX RIP and SAP timer settings should be the same on both sides of the WAN. Refer to the sections “Configurable RIP Timers” and “Configurable SAP Timers” in this chapter for more detailed information. Using the BCC To adjust the frequency of RIP update packet transmissions, navigate to the RIP prompt (for example, box; ethernet 2/1; ipx 00023456; rip 00023456) and enter: update-interval seconds seconds is from 0 to 2678400 seconds. To adjust the frequency of SAP update packet transmissions, navigate to the SAP prompt (for example, box; ethernet 2/1; ipx 00023456; sap 00023456) and enter: update-interval seconds seconds is from 0 to 2678400 seconds. For example, to set the update interval to 10,000, enter: rip/00023456# update-interval 10000 Using Site Manager To adjust the frequency of RIP and SAP updates, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Update Interval (sec) parameter. Click on Help or see the parameter description on page A-37. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-123 Configuring IPX Services Using Static Routes A static route specifies a transmission path between networks. The static route feature lets you manually define an IPX route to a destination network. Static routes specify the next hop in the transmission path a datagram must follow, based on the datagram’s destination address. You configure a static route when you want to restrict the paths that packets can follow. A Bay Networks router running IPX lets you configure static routes on each logical IPX interface. Using static routes is most valuable over wide area links, where bandwidth is at a premium. Static route support also enhances internetwork security because it can be implemented so that traffic across specific IPX networks is restricted, protecting sensitive internetwork resources. Static route support for IPX can do the following: • Direct all IPX traffic not destined for this network to an adjacent host. The adjacent host may be the actual destination, or it may be the next hop to the eventual destination network. See the following section on adjacent host support for more information about adjacent hosts. • Reduce routing traffic by disabling the RIP supply function on all or a subset of attached interfaces that are configured with static routes. • Provide security by eliminating all dynamic routing capabilities and all RIP supply and listen activities over an IPX interface. You should configure static routes and disable IPX RIP and SAP advertisements when implementing dial-on-demand routing over a wide area link. IPX RIP and SAP advertisements force dial-on-demand connections to be continuously established, which prevents user-defined dial-on-demand expiration time limits from being reached. Refer to the description of the dial-on-demand feature later in this chapter for details on using this feature. Unlike routes learned through RIP, static routes remain in the route tables until you delete them. RIP routes have priority over static-learned routes if both routes have the same cost. If you do not have the RIP listen functions enabled, the local network will not learn about new routes on the network, route changes, or deleted routes. 5-124 117369-B Rev. 00 Customizing IPX Static route support lets you identify the next interface and next router in the path toward a destination network. Once you configure a static route for an interface, the router advertises that route in its usual RIP broadcasts. For example, in Figure 5-14, to establish a static route between IPX network A and IPX network B, through interface 1 on router R1, a static route must be established from router R1 to router R2. The static route entry in router R1 directs any traffic destined for network B through interface 1 to router R2. In turn, the static entry in router R2 directs any traffic destined for network B through interface 3 to router R3, and thus to network B. To Network B via Interface 3 and Router 3 R2 Interface 2 Interface 3 ES2 Interface 1 R1 Interface 4 R3 Interface 6 Network A Network B Interface 5 IPX server To Network B via Interface 1 and Router 2 IPX0009A Figure 5-14. IPX Static Routes RIP routes have priority over static-learned routes with the same cost, so if the connection between routers R1 and R3 has the same or greater cost, the packet will travel over the static route from router R1 to router R2 to router R3. If a connection used by the static route fails (and if router R1 has the listen function enabled), router R1 will learn of an alternative route between network A and network B and attempt to send the packet over that connection. 117369-B Rev. 00 5-125 Configuring IPX Services IPX static routes are user-specified routing table entries. Static routes, like routes learned through RIP, are maintained in the IPX routing table. Unlike routes learned through RIP, however, static routes do not expire. Static routes remain in the IPX routing table until they are reconfigured manually. Static routes are removed if the interface they are configured on goes down. Note: You can send packets over a static route if you have mapped an IPX host address to a data link address in a Frame Relay, SMDS, or ATM network. If RIP is disabled on a WAN interface, before you configure a static route to an adjacent host, you must configure an adjacent host and edit the DLCI parameter. Specifying the Target Network Address If you are using the static route feature, you must specify the address of the network to which you want to configure the static route. You can enter a network address of up to 8 hexadecimal characters or specify that the router use the default route 0xFFFFFFFE. Using the BCC When you first create a static route, you must supply a target network address. To modify the network address, navigate to the IPX static route prompt (for example, box; ethernet/2/1; ipx 00023456; static-route 00023456/00054321/ 000000765432) and enter: target-network address address is up to 8 hexadecimal characters. For example, to specify 0x000076d5 as the target network address, enter: static-route/00023456/00054321/000000765432# 5-126 target-network 0x000076d5 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the network address, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Choose RIP. The IPX RIP Circuit window opens. 5. Set the Target Network (hex) parameter. Click on Help or see the parameter description on page A-56. 6. Click on OK. You return to the Configuration Manager window. Entering the Next-Hop Host With the static route feature, you must specify the address of the next-hop host in the static routing path. The next-hop host address consists of up to 12 hexadecimal characters. The next hop host is the host address of the down-stream router’s IPX interface. Note: You cannot change the next-hop host address once you have configured a static route. 117369-B Rev. 00 5-127 Configuring IPX Services Using the BCC When you first create a static route, you must supply a target network address. To modify the network address, navigate to the IPX static route prompt (for example, box; ethernet/2/1; ipx/00023456; static-route/00023456/00054321/ 000000765432) and enter: target-network address address is up to 8 hexadecimal characters. For example, to specify 0x000076d5 as the target network address, enter: static-route/00023456/00054321/000000765432# target-network 0x000076d5 Using Site Manager To specify the address of the next-hop host, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Static Route. The IPX Static Routes window opens. 5. Click on Add. The IPX Static Route Configuration window opens. 6. Set the Next Hop (hex) parameter. Click on Help or see the parameter description on page A-57. 7. Click on OK. 5-128 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Entering the Hop Count The IPX router uses a hop count when determining the best route for a datagram to follow. The hop count is also propagated through RIP. The default setting of 0 for static routes means “use the hop count associated with the interface.” You can accept the default value, zero, or enter a value from 1 to one less than the maximum number of hops. Using the BCC To specify the hop count, navigate to the IPX static route prompt (for example, box; ethernet/2/1; ipx 00023456; static-route 00023456/00054321/ 000000765432) and enter: hops count count is from 0 to one less than the maximum number of hops. For example, to specify a hop count of 18, enter: hops 18 Using Site Manager To specify the hop count, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Static Route. The IPX Static Routes window opens. 5. Click on Add. The IPX Static Route Configuration window opens. 6. Set the Hop Count parameter. Click on Help or see the parameter description on page A-57. 7. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-129 Configuring IPX Services Setting the Timer Ticks With the static route feature, you specify the number of 1/18th-second timer ticks required for an IPX datagram to traverse this static route. The IPX router uses tick cost when determining the best route for a datagram to follow. The tick cost is also propagated through RIP. The default setting of 0 for the tick cost of static routes means “use the tick count associated with the interface.” you can accept the default value, zero, or enter a value from 1 to the maximum positive integer. Using the BCC To specify the tick cost, navigate to the IPX static route prompt (for example, box; ethernet/2/1; ipx 00023456; static-route 00023456/00054321/ 000000765432) and enter: ticks cost cost is from 0 to one less than the maximum positive integer. For example, to specify a cost of 20, enter: ticks 20 5-130 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the number of timer ticks, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Static Route. The IPX Static Routes window opens. 5. Click on Add. The IPX Static Route Configuration window opens. 6. Set the Ticks parameter. Click on Help or see the parameter description on page A-58. 7. Click on OK. You return to the Configuration Manager window. Using Route Filters You can shield the view of networks from users on different network segments by configuring route filters. Route filters give you greater control over the routing of IPX packets from one area of an IPX internetwork to another. This helps maximize the use of the available bandwidth throughout the IPX internetwork, and helps improve network security by shielding a user’s view of other networks. You can configure inbound or outbound route filters on a per-interface basis, instructing the interface to advertise/accept or drop filtered RIP packets. The action parameter that you define for the filter determines whether the router advertises, accepts, or suppresses RIP packets from routers that match the filter pattern. IPX route filters uses the network number field in the IPX RIP packet. Network filtering is based on a two-part definition: filter ID and a corresponding mask. A route filter can be inbound, outbound, or both. You can define filters by network address, or by a range of network addresses. 117369-B Rev. 00 5-131 Configuring IPX Services The filter ID and the mask definition work together to determine which addresses are filtered on the interface. The character F in the mask definition requires an exact match with the corresponding character in the filter ID. The mask character 0 matches any hexadecimal character. You can combine the F and 0 characters in any order in the mask to filter any combination of network and/or area addressing schemes used within the IPX internetwork. For example, suppose you want to filter the range of network addresses from ABCD1200 to ABCD12FF. To do this, you would define: • A filter ID of ABCD12FF • A mask of FFFFFF00 In this example, the filter ID says, “This is the pattern to match.” The mask says, “The first six characters of the address must match the filter ID, but the last two characters are irrelevant.” The IPX Route Filters window displays each route filter entry in the router configuration, as follows: , , , , Once you have configured route filters, you can easily drop all routes to allow one or more specific routes. To drop all routes, apply a filter at a low priority. For example, in the IPX Route Filters window, enter the value 0xFFFFFFFF for the Target Network parameter, the value 0xFFFFFFFF for the Target Network Mask, and set the Action parameter to Suppress. Add the filters you want by specifying higher priorities to advertise specific routes. For example, enter the value 0x3081be86 for the Target Network parameter, the value 0xFFFFFFFF for the Target Network Mask parameter, and set the Priority parameter to 1. 5-132 117369-B Rev. 00 Customizing IPX Using SAP Filters Briefly, a filter is a pattern for matching a service name or service network. The router scans incoming and outgoing SAP packets to see whether certain fields in the packet match the filter. (The type of filter -- service name or service network -determines which fields the router examines.) When you set up the filter, you can specify what the router does with the services in the packet when it finds a match. You can create SAP filters on Bay Networks routers in your network to regulate both incoming and outgoing SAP advertisements. You can use SAP filters to control the size of resident SAP services tables and reduce bandwidth waste on your network due to SAP broadcast overhead. You can also create SAP filters as a security mechanism to limit a user’s view of services located elsewhere on the network. Each SAP filter consists of a service name or network number, a service type, a priority, and a configurable action parameter. (You can also include wildcards or patterns to be matched). As a result, you can tailor SAP filters to your site requirements, improving network security by controlling access and preserving bandwidth by limiting the SAP packet traffic. On a given interface, you can configure a filter as inbound, outbound, or both. 117369-B Rev. 00 • Inbound filters affect only incoming SAP advertisements. The filter determines whether the Bay Networks router accepts or suppresses the service information from certain servers, based upon the action that you specify. • Outbound filters affect only outgoing SAP advertisements. The router either advertises or suppresses SAP information, depending on whether it matches the filter’s content, based upon the action that you specify. • Both applies the same filter pattern to both incoming and outgoing SAP advertisements. 5-133 Configuring IPX Services Using the BCC To specify that a SAP filter accept incoming service information, navigate to the route filter prompt (for example, box; ipx 00023456; route-filter 0x8888/ 0x2121) and enter: inbound enabled To specify that a SAP filter suppress incoming service information, navigate to the route filter prompt (for example, box; ipx 00023456; route-filter 0x8888/ 0x2121) and enter: inbound disabled To specify that a SAP filter enable outgoing SAP advertisements, navigate to the route filter prompt (for example, box; ipx 00023456; route-filter 0x8888/ 0x2121) and enter: outbound enabled To specify that a SAP filter disable outgoing SAP advertisements, navigate to the route filter prompt (for example, box; ipx/00023456; route-filter 0x8888/ 0x2121) and enter: outbound disabled 5-134 117369-B Rev. 00 Customizing IPX Using Site Manager To specify the filter mode, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Route Filter. The IPX Route Filters window opens. 5. Set the Mode parameter. Click on Help or see the parameter description on page A-71. 6. Click on OK. You return to the Configuration Manager window. Figure 5-15 shows an example of SAP outbound filtering. R1 Network A SAP update pertaining only to Server B R2 Network C Server A Network B Server B Network D Server A not visible to Networks C and D Drop outbound SAP updates pertaining to Server A IPX0011A Figure 5-15. 117369-B Rev. 00 SAP Filtering 5-135 Configuring IPX Services In this example, a SAP filter configured on router R1 prevents SAP advertisements and updates pertaining to server A from being propagated over the wide area link. As a result, server A is invisible to networks C and D. Information pertaining to server B, however, continues to be propagated over the WAN link. Note: While SAP filters restrict a user’s view of network service information, they do not prevent users from accessing services. If users have access to resources contained on an IPX network, they can also access all services within that network, regardless of whether a service has been filtered. The IPX router always updates its own SAP services table according to inbound SAP data. You can configure SAP filters using the following levels: • Individual servers • Nnetwork level Using SAP Filters at the Server Level You can filter SAP service information pertaining to individual servers by editing server-level SAP filters. At the service level, the filter matches a pattern that you specify (consisting of a service name pattern and a service type). The filter’s Action parameter determines the action (Accept/Advertise or Suppress). Note: You cannot change a SAP filter’s actions once you have created a service name filter. 5-136 117369-B Rev. 00 Customizing IPX Using the BCC To specify a SAP filter’s action, navigate to the route filter prompt (for example, box; ipx/00023456; route-filter 0x8888/0x2121) and enter: action value value is one of the following: Action Meaning Advertise Enables the filter to allow advertisement or acceptance of routes that match the specified route filter criteria Suppress Causes the IPX router to drop advertisements that match the specified route filter criteria For example, to enable the filter to accept routes that match the filter’s criteria, enter: route-filter 0x8888/0x2121# action advertise Using Site Manager To specify a SAP filter’s action, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Route Filter. The IPX Route Filters window opens. 5. Set the Action parameter. Click on Help or see the parameter description on page A-72. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-137 Configuring IPX Services Using SAP Filters at the Network Level You can filter service information pertaining to entire networks by editing network-level SAP filters. At the network level, the filter matches a pattern that you specify (consisting of a service network number and a service type). The filter’s action determines whether the router advertises or suppresses routes that match the filter’s criteria. Using the BCC To determine the way a filter behaves at the service network level, you must specify the name and type of filter and then configure the action of the filter. To specify the name of the filter, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service 00023456/printer/ 0987) and enter: service-name name name is any valid alphanumeric server name, or one containing wildcard characters or a pattern-matching regular expression. For example, to set the server name to printer2, enter: static-service/00023456/printer/0987# service-name printer2 To specify the type of the filter, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service 00023456/printer/ 0987) and enter: server-type value value is any Novell server type number in hexadecimal format. For example, to set the server type to 0x2121, enter: static-service/00023456/printer/0987# 5-138 service-name 0x2121 117369-B Rev. 00 Customizing IPX To configure a filter’s action, navigate to the route filter prompt (for example, box; ipx/00023456; route-filter 0x8888/0x2121) and enter: action type type is one of the following: Action Meaning Advertise Enables the filter to allow advertisement or acceptance of routes that match the specified route filter criteria Suppress Causes the IPX router to drop advertisements that match the specified route filter criteria Using Site Manager To specify a filter’s action at the service network level, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the following parameters: • Action • Target Server • Target Service Type (hex) Click on Help or see the parameter descriptions on pages A-85 and A-87. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-139 Configuring IPX Services The IPX router with an outbound filter configured on an interface includes information about a service in a SAP packet if either of the following is true: • The router finds a match between an outbound filter’s contents and the service in its SAP services table, and the filter action is Advertise/Accept. • The router does not find an outbound filter that matches the service in its SAP services table. The IPX router excludes information about a service from a SAP packet only if it finds a match between an inbound filter’s contents and the contents of its SAP services table, and the filter action is Suppress. Similarly, the IPX router accepts information about a service in a SAP packet if either of the following is true: • The router finds a match between an inbound filter’s contents and the service in the SAP packet, and the filter action is Advertise/Accept. • The router does not find an inbound filter that matches the service in the SAP packet. Using Wildcards and Pattern Matching with SAP Filters Wildcards and pattern matching are shortcut techniques for setting up SAP filters. Wildcards are characters that match zero or more instances of any valid character. In other words, a wildcard in a filter matches any allowable character(s), depending on which wildcard you specify. Pattern matching lets you selectively filter by named entities. The following sections describe each of these techniques. Using Wildcards with SAP Filters Wildcards in SAP filters let you configure a single SAP filter to match a set of services. When you use wildcards, you can configure the filter based on the service name, which lets you configure a SAP filter based on the characters represented in the service name field of an IPX SAP packet. The service name field contains the 48-byte character string name that is assigned to a NetWare server. The service name, in combination with the service type, uniquely identifies a service on the internetwork. You can use a wildcard SAP filter configured using the service name field to shield users’ view of services that reside on a group of servers that use a common naming convention. 5-140 117369-B Rev. 00 Customizing IPX The wildcard characters are: * (Asterisk) matches any number of instances (zero or more) of the previous character. • (Period or dot) matches any single character. For example, suppose an organization has ten servers within its network, each providing a variety of different services. Five of the servers have names that begin with the character p, while the other servers have names that start with a different character. You could then define a single SAP filter p•* that would filter all SAP information for all five servers whose server name begins with the character p. Similarly, a SAP filter defined as p•int would match the server names print, point, and paint, but not the server name poing, because the wildcard character • matches only a single character in the same position in the string that makes up the server name. 117369-B Rev. 00 5-141 Configuring IPX Services Using Pattern Matching with SAP Filters You can also filter SAP packets by, matching a filter pattern that you define as a regular expression, using the characters shown in Table 5-1. The software compares this regular expression against a service name and returns an indication of whether it finds a match. Functionally, pattern matching on SAP filters is similar to the UNIX grep command. Table 5-1. Characters in SAP Pattern-Matching Filters Filter Character Function C Matches any character, except those listed below. An ordinary character (like a, b, 7, or q) matches only itself. \ (Backslash) The backslash (\) is the escape character. Use this to match a character that would otherwise have special meaning to the software. The special characters that must be preceded by a backslash to match themselves are: \ (backslash) . (period or dot) [ (left bracket) ? (question mark) * (asterisk) { (left brace) ( (left parenthesis) ) (right parenthesis) | (vertical bar) $ (currency symbol) Must be quoted only when it is the last character to be matched. Any other quoted character following a backslash matches itself. For example, to match a backslash (\) in a string, include the following in the filter expression: \\ . (Dot or period) Matches a single character Example: SERVER. Matches: SERVER1 and SERVERA Does not match: SERVER12 or SERVER (continued) 5-142 117369-B Rev. 00 Customizing IPX Table 5-1. Characters in SAP Pattern-Matching Filters (continued) Filter Character Function [c...] As the rightmost element in a string, this element tells the filter to match any one of the characters enclosed in the brackets. To use a right bracket (]) as one of the characters to be matched, make it the first character in the string. The expression: [ ]abc] matches any of the characters: ], a, b, or c. [^c...] When a caret is the first character of the enclosed string, the filter expression matches any character except those in the remainder of the string. For example, the expression [^45678] matches any character except 4, 5, 6, 7, or 8. To include a right bracket (]) in the string of filtered characters, place it directly after the caret. For example, the expression [^] abc] matches every character except ], a, b, or c. [l-r] The minus sign between two characters indicates a range of consecutive ASCII characters to match. This bracketed string of characters is known as a character class. For example, the range: [0-9] is equivalent to the string: [0123456789] The minus sign (-) is treated as an ordinary character if it occurs first (or first after an initial ^ character) or last in a string. You can also construct longer filters by combining (that is, concatenating) these single-character regular expressions using the rules and operators listed in Table 5-2. A filter made up of a concatenation of regular expressions matches a concatenation of text strings, each of which is a match for a successive regular expression in the search pattern. 117369-B Rev. 00 5-143 Configuring IPX Services Table 5-2. Concatenation Rules and Operators Rule/Operator Interpretation ? A single-character regular expression followed by a question mark (?) matches zero or exactly one occurrence of that single-character regular expression. (Question Mark) For example, [a-z]? matches any string of either zero lowercase letters or exactly one lowercase letter. Example: SERVER? Matches: SERVER1 and SERVER Does not match: SERVER12 or SERVER123 * (Asterisk) A single-character regular expression followed by an asterisk (*) matches zero or more occurrences of that single-character regular expression. For example, [a-z]* matches any string of zero or more lowercase letters. Example: SERVER* Matches: SERVER123 and SERVER Does not match: ADMIN123 or PS_SERVER + (Plus Sign) A single-character regular expression followed by a plus sign (+) matches one or more occurrences of that single-character regular expression. For example, [a-z]+ matches any string with one or more lowercase letters. Example: SERVER+ Matches: SERVER12 and SERVERA Does not match: SERVER or ADMIN123 {m} {m,} {m,n} (Where m and n are integers) A one-character regular expression followed by {m}, {m,}, or {m,n} is a regular expression that matches a range of occurrences of the one-character regular expression. The values m and n must be non-negative integers less than 255. The symbols in braces mean the following: {m} matches exactly m occurrences. {m,} matches at least m occurrences. {m,n} matches any number of occurrences between m and n. Whenever a choice exists, the regular expression matches as many occurrences as possible. For example, the ? operator is equivalent to {0,1}, the * operator is equivalent to {0,}, and the + operator is equivalent to {1,}. (continued) 5-144 117369-B Rev. 00 Customizing IPX Table 5-2. Concatenation Rules and Operators (continued) Rule/Operator Interpretation Use the following operators to construct regular expressions from more-than-single-character regular expressions. (...) (Regular expression(s) enclosed in parentheses) A regular expression enclosed within parentheses matches whatever the unadorned regular expression matches. You use parentheses to group a series of regular expressions that you want to have treated as a single-character regular expression. For example, the regular expression 0[Xx]? matches a 0 that may or may not be followed by one X or x, while the regular expression (0[Xx])? matches nothing, the string “0X,” or the string “0x.” You can have up to nine such substrings in a regular expression, and you can nest parentheses. | (Vertical Bar) Two regular expressions separated by the vertical bar (|) match either a match for the first or a match for the second. These two regular expressions are the longest that can be created subject to parentheses grouping. For example, these regular expressions are grouped as follows: and|or = and | or and*|o+r = and* | o+r a(nd|o)r = a, plus either nd or o, plus r Example: SERVER(8FS|1FS) Matches: SERVER8FS and SERVER1FS Does not match: SERVER or SERVER5FS [] (Square Brackets) Matches any single character in the bracketed set. Example: SERVER[123] Matches: SERVER1 and SERVER3 Does not match: SERVER123 or SERVER23 The server name filters take precedence over the service network filters. Both service name and service network filters have an associated priority, with smaller values denoting a higher priority. Matching is performed by first checking all service name filters in order by priority. If a match isn’t found, then the service network filters are checked in order by priority. 117369-B Rev. 00 5-145 Configuring IPX Services For example, you may want to advertise from an IPX interface only one type of service (type 4) belonging to a particular server (server 1). You can configure: • A service name SAP filter with a target service name of server 1, a service type of 4, and an action to advertise. • A service network filter with a target network of 0xFFFFFFFF, a type of 0xFFFF, and an action to suppress. (This service network filter prevents all other services from being advertised from the interface.) Using similar specifications and an action to suppress, you could exclude from an IPX interface a type of service from a particular server. Note: The order in which you create SAP filters does not affect filter precedence. An Example of Using SAP Filters The following example describes a situation in which you might want to configure SAP filters. An office complex contains three buildings. The people in each building use only the print services within their own building and have no need to send files to printers outside their building. To free wasted bandwidth, you could configure a SAP filter that suppresses print server advertisements on the interfaces of the routers that connect the three buildings. To suppress print server advertisements, configure a service network filter on the interfaces of the routers that connect the three buildings and suppress the advertisement of Server Type 0x0047 (print server) for all networks (0xFFFFFFFF). Refer to Appendix A for a list of common server types. The IPX Service Network window displays each service network filter entry in the router configuration, as follows: , , , , , Once you have configured SAP filters, you can easily drop all services to allow one or more specific services. To drop all services, apply a filter at a low priority. 5-146 117369-B Rev. 00 Customizing IPX Example Using Site Manager, open the IPX Service Network Filters window, and for the Target Network (hex) and Target Network Mask (hex) parameters, enter 0xFFFFFFFF (see page A-70). Then set the Action parameter to Suppress (see page A-72). Add the filters you want by specifying higher priorities to advertise specific services. Example For the target network, enter the value 0x3081be86, for the target network mask, enter the value 0xFFFFFFFF for the target service type, enter the value 0x0004, and set the filter priority to 1 (see page A-75). Service Name Filters The service name filters function lets you reduce network traffic by configuring service name filters. Enabling an IPX Service Name Filter If you are configuring service name filters, you must activate the service name filter for each interface. By default, the service name filter is active on an interface. You can disable the service name filter if you do not want to use this feature. 117369-B Rev. 00 5-147 Configuring IPX Services Using the BCC To activate the service name filters feature, you must first configure a service name filter. To configure a service name filter, navigate to the IPX interface prompt (for example, (box; ethernet 2/1; ipx 0x00023456) and enter: server-name-filter server-name name name is any valid alphanumeric server name. For example, to set the server name to Hoboken, enter: ipx/00023456# server-name-filter server-name Hoboken To enable the service name filters feature, navigate to the service name filter prompt, (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: state enabled To disable the service name filters feature, navigate to the service name filter prompt, (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: state disabled 5-148 117369-B Rev. 00 Customizing IPX Using Site Manager To activate the service name filters feature, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the Enable parameter. Click on Help or see the parameter description on page A-84. 6. Click on OK. You return to the Configuration Manager window. Entering the Target Service Name Enter a the name of the server to which you are applying the server-level SAP filter, or enter a filter containing a wildcard or a pattern (regular expression) to be matched. The server name or filter pattern can consist of up to 48 alphanumeric characters. You can specify any valid alphanumeric server name, or one containing wildcard characters or a pattern-matching regular expression. See “Using Wildcards with SAP Filters” and “Using Pattern Matching with SAP Filters” for lists of these characters. 117369-B Rev. 00 5-149 Configuring IPX Services Using the BCC To specify the service name or filter type, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: service_name name name is any valid alphanumeric server name. For example, to set the server name to Hoboken, enter: server-name-filter/00023456/myname# server-name Hoboken Using Site Manager To specify the service name or filter type, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the Target Server parameter. Click on Help or see the parameter description on page A-85. 6. Click on OK. 5-150 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Entering the Target Service Type If you are using a service name filter, you must specify the type of server that the filter should recognize in its criteria for allowing certain SAP broadcasts to pass to the locally attached network segment. To specify the server type, enter the server type number in 4-digit hexadecimal format, making sure to include leading zeros. For all types, enter a value of 0xFFFF. See Appendix C for a list of common service types. Using the BCC To specify the type of server, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/ myname) and enter: type server_type server_type is any valid Novell server type in hexadecimal format. For example, to set the server type to 0x0987, enter: server-name-filter/00023456/myname# type 0x0987 Using Site Manager To specify the type of server, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the Target Service Type (hex) parameter. Click on Help or see the parameter description on page A-85. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-151 Configuring IPX Services Setting the Filter Priority Enter a decimal value that indicates this filter’s priority relative to other filters of the same type for this interface. You can specify a priority in the range of 0 to the maximum positive integer. Lower values indicate higher priorities. The highest priority is zero. Using the BCC To specify a filter’s priority, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/ myname) and enter: priority value value is a decimal value from 0 to the maximum positive integer. For example, to set the priority to 12, enter: server-name-filter/00023456/myname# priority 12 Using Site Manager To specify a filter’s priority, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the Filter Priority parameter. Click on Help or see the parameter description on page A-86. 6. Click on OK. 5-152 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX Applying Filters to Inbound or Outbound Packets You can apply the service name filter to inbound packets, outbound packets, or both. By default, the filter is applied to SAP packets advertised by the specified interface. If you want to apply the filter to SAP packets coming into this interface, specify inbound. If you want to filter both incoming and outgoing packets, specify both. Using the BCC To apply the service name filter to inbound packets, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: inbound enabled If you do not want to apply the service name filter to inbound packets, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: inbound disabled To apply the service name filter to outbound packets, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: outbound enabled If you do not want to apply the service name filter to outbound packets, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: outbound disabled 117369-B Rev. 00 5-153 Configuring IPX Services Using Site Manager To apply the service name filter, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the Mode parameter. Click on Help or see the parameter description on page A-86. 6. Click on OK. You return to the Configuration Manager window. Specifying the Protocol When you send SAP updates, you can apply this outbound filter only to services learned on the specified protocol. This feature does not apply to inbound services. By default, the outbound filter applies to any protocol. You can accept the default, any protocol, or specify that it apply to local, static, or SAP protocols. 5-154 117369-B Rev. 00 Customizing IPX Using the BCC To apply an outbound filter to services learned on a specified protocol, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: protocol protocol protocol is one of the following: any local static sap For example, to set the outbound filter to services learned on the SAP protocol, enter: server-name-filter/00023456/myname# protocol sap Using Site Manager To apply an outbound filter to services learned on a specified protocol, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Global Parameters window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the Protocol parameter. Click on Help or see the parameter description on page A-86. 6. Click on OK. 117369-B Rev. 00 You return to the Configuration Manager window. 5-155 Configuring IPX Services Specifying How to Process SAP Advertisements You can specify how the router should process any SAP advertisement that matches the SAP filter criteria you established in the Target Service Name and Target Service Type parameters. By default, the filter allows advertisement or acceptance of services that match the filter criteria you established in the Service Name and Service Type parameters. You can accept the default or set the filter cause the IPX router to suppress, or drop, SAP advertisements that match the SAP filter criteria you established in the Service Name and Service Type parameters. Using the BCC To specify how the router should process SAP advertisements, navigate to the service name filter prompt (for example, box; ethernet 2/1; ipx 0x00023456; server-name-filter 00023456/myname) and enter: action value value is one of the following: Action Meaning Advertise Enables the filter to allow advertisement or acceptance of routes that match the specified route filter criteria Suppress Causes the IPX router to drop advertisements that match the specified route filter criteria For example, to enable the filter to accept routes that match the filter’s criteria, enter: server-name-filter/00023456/myname# 5-156 action advertise 117369-B Rev. 00 Customizing IPX Using Site Manager To specify how the router should process SAP advertisements, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the Action parameter. Click on Help or see the parameter description on page A-87. 6. Click on OK. You return to the Configuration Manager window. Specifying a Cost If you are enabling the filter to allow advertisement or acceptance of services that match the filter criteria you established when you specified a service name and a service type, you can assign a cost (number of ticks or hops) for this interface. The cost is included in subsequent SAP packets sent to other interfaces. IPX disposes of the packet when its hop count passes a value that is one less than the value of the maximum number of hops. This value must be the same across the network. If the filter is an inbound filter, the entered cost replaces the cost associated with the server in the SAP advertisement, and the router uses this cost in its calculations. If this is an outbound filter, the entered cost replaces the server’s cost that is advertised in SAP packets by this router. 117369-B Rev. 00 5-157 Configuring IPX Services By default, the cost is set to 1. A zero cost indicates that the route’s actual cost should be used. Note: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. Using the BCC To assign a cost for a static service filter, navigate to the IPX static service prompt (for example, box; ethernet 2/1; ipx 00023456; static-service/00023456/ printer/0987) and enter: cost integer integer is 1 to one less than the number of maximum hops for hop-based routing, or 1 to the maximum positive integer for tick-based routing. For example, to set the cost to 120, enter: static-service/00023456/printer/0987# 5-158 cost 120 117369-B Rev. 00 Customizing IPX Using Site Manager To assign a cost for a static service filter, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Static/Filter Tables. The IPX Static Interface Tables Configuration window opens. 4. Choose Name Filter. The IPX Service Name Filters window opens. 5. Set the Cost parameter. Click on Help or see the parameter description on page A-88. 6. Click on OK. You return to the Configuration Manager window. Source Route Bridge End Station Support Source route bridge end station support enables routable traffic generated in a source route bridge environment to be routed to workstations on remote LANs over a multiprotocol backbone. The Bay Networks router running IPX lets you configure source route end station support for token ring networks on each interface. This allows bridging and routing to coexist in the same IBM source route bridging environment. With end station support enabled, end stations that support both source route bridging and IPX can use source routing to traverse bridged networks. In a source routing network, every end station supplies each frame it sends out with route descriptors, so that it can be source routed across the network. Thus, for routers running IPX to route packets across a source routing network, they must act like end stations, supplying route descriptors within each packet before sending it onto the network. 117369-B Rev. 00 5-159 Configuring IPX Services All traffic is source route bridged within the local token ring environment. Routable traffic intended for a destination on a LAN interconnected through a multiprotocol backbone is routed over the backbone by the Bay Networks node. With end station support enabled, the Bay Networks router running IPX does the following whenever it receives a packet and determines that the packet’s next hop is across a source routing network: • Sends out a Single Route Explorer (SRE) frame to discover a path to the next-hop network • Adds the necessary routing information field (RIF) information to the packet’s MAC header • Sends the packet to the network, where it is source routed toward the next hop After the peer router receives the packet from the token ring network, it strips off the RIF field and continues to route the packet toward the destination network address, as shown in Figure 5-16. 5-160 117369-B Rev. 00 Customizing IPX ES1 IPX router 2 Token ring IPX router 1 Token ring Bridge A Token ring Bridge B ES2 WF2 WF1 LLC IPX DATA WF2 WF1 0830 001A002B 0030 WF2 WF1 LLC IPX DATA Packet sent from ES1 LLC IPX DATA Packet sent from router 1 Packet sent from router 2 IPX0019A Figure 5-16. IPX Routers Source Routing across a Token Ring Network The transition to network-layer routing outside the source route bridge environment can improve overall network performance by reducing source route bridge overhead on a WAN and can maximize network availability by rapidly rerouting around a failed link. 117369-B Rev. 00 5-161 Configuring IPX Services Using the BCC To configure source route end station support on each interface, configure IPX on a token ring and navigate to the IPX interfaces prompt (for example, box; tokenring 5/1; ipx 0x00034567) and enter: end-station enabled If you do not want source route end station support on each interface, configure IPX on a token ring and navigate to the IPX interfaces prompt (for example, box; tokenring 5/1; ipx 0x00034567) and enter: end-station disabled Using Site Manager To configure source route end station support on each interface, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Interfaces. The IPX Interfaces window opens. 4. Set the TR End Station parameter. Click on Help or see the parameter description on page A-26. 5. Click on OK. 5-162 You return to the Configuration Manager window. 117369-B Rev. 00 Customizing IPX IPX Ping Support The Bay Networks Site Manager supports the IPX ping feature, which uses an IPX diagnostic packet to ping NetWare servers to determine the accessibility -that is, the status, “alive” or “not responding” -- of the following: • A remote Bay Networks router • A Novell IPX server (except as noted later) • A Novell multiprotocol router • A NetWare client This feature can be particularly useful in troubleshooting large networks. Note: In conformance with the Novell specification, a Bay Networks router running IPX will respond to pings from NetWare servers but will not initiate pings to those servers. Instead, the router running IPX will use diagnostic packets to accomplish the ping function. Using the IPX ping command, the router attempts to communicate with another router running IPX, a server, or an IPX client, and determines whether the destination node is functioning and reachable from the source node. The “pinging” Bay Networks router sends an IPX diagnostic packet, called a configuration request, and either the “pinged” router running IPX, the server, or the IPX client responds with a configure response packet. See Configuring and Managing Routers with Site Manager for instructions on using the ping feature in IPX. Role of Bay Networks Routers in a Client/Server Connection This section describes how Bay Networks routers running IPX provide clients access to servers on an IPX internetwork. • Router builds SAP and RIP tables The Bay networks router builds its routing and services tables by listening to regularly scheduled SAP and RIP broadcasts from file servers. The broadcasts include the services a server has to offer and routes to a server. If regular SAP or RIP broadcasts from a file server stops, the local router ages out the entry and removes it from its services or route table. 117369-B Rev. 00 5-163 Configuring IPX Services • Client sends get_nearest_service/get_nearest_directory_server SAP request A client sends this request to locate a file server. (Refer to the book, Novell’s Guide to NetWare LAN Analysis, by Laura Chappell and Dan E. Hawkes, for more information on this mechanism.) • Router decisions If the server resides on the same network as the client, the server receives the request and responds. The local router does not respond because its services table indicates that the service is available on the client’s network. In this case, client-router communications stop until the client sends the next get_nearest_service SAP request. If the server does not reside on the same network, the router responds, because its services table indicates that the service is not available on the client’s network. The SAP response sent by the router contains the server name, the internal address (if applicable), the service type, the socket number, and the intervening network count of the nearest device offering the service. Continue to the next bullet. If the server does not reside on the same network and multiple servers of the same service type are available, the router picks the server that is the fewest ticks away. If two servers are the same number of ticks away, then the router chooses the server that is the lowest number of hops away. If two servers are the same number of ticks and hops away, then the router chooses based on the alphanumeric order of the server names listed in the services table. • Client’s RIP request The client then broadcasts a RIP request packet to the local segment. This packet requests the best path to the server’s network. • Router’s RIP response The router on the same network as the client refers to its route table and sends a RIP response to the client. The RIP response identifies the network on which the client resides. The RIP response also contains the server’s internal network address and the intervening hop and tick count. • 5-164 Client’s NCP request 117369-B Rev. 00 Customizing IPX The client sends a Network Core Protocol (NCP) create connection request to the server. The request includes the router’s MAC address as the destination address at the data link layer. Within the IPX header, the destination network address is the internal address and the destination node address of the file server. The client forwards the packet to the router. • Router forwards packet The router running IPX forwards the packet to the network identified by the destination network address. Example: Client/Server Connection via Bay Networks Router In the example shown in Figure 5-17, client A sends a SAP request to locate a file server. Here is what happens as a result of that request: 1. Because the server does not reside on LAN A (the same LAN as client A), the Bay Networks IPX router, host 2, sends a SAP response to client A, informing it that the file server, host 3 on token ring 6, is the nearest device offering the requested service. 2. Client A then sends a RIP request to determine the best path to host 3. 3. The Bay Networks IPX router, host 2, sends a RIP response to client A that includes the server’s internal network address and the intervening hop and tick count from host 3 to client A. 4. Client A sends an NCP request packet to the Bay Networks IPX router, host 2. 5. The router then forwards the packet to host 3. 117369-B Rev. 00 5-165 Configuring IPX Services Print server Host 1 Client A Client B Client C LAN A IPX router Host 2 Client D Client F Token Ring File server Host 3 IPX router Host 5 LAN B Client E Host server Host 4 IPX0020A Figure 5-17. 5-166 Sample IPX Network 117369-B Rev. 00 Customizing IPX Deleting IPX from the Router You can use the BCC or Site Manger to delete IPX from the router. Using the BCC To delete IPX from an interface, navigate to the IPX interface prompt (for example, box; ipx 00023456) and enter: delete To delete IPX globally from the router, navigate to the global IPX prompt (for example, box; ipx 00023456) and enter: delete Using Site Manager To delete IPX from the router, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose IPX. The IPX menu opens. 3. Choose Delete IPX. A confirmation window opens. 4. Click on OK. You return to the Configuration Manager window. Note: If you delete IPX, the connectors for those interfaces on which IPX was the only protocol enabled are no longer highlighted in the Configuration Manager window. Interfaces must be reconfigured for these connectors; see Configuring and Managing Routers with Site Manager for instructions. 117369-B Rev. 00 5-167 Configuring IPX Services 5-168 117369-B Rev. 00 Appendix A Site Manager IPX Parameters This appendix explains all the IPX parameters and how to use them if you want to customize an interface you have added to a router. IPX Configuration Parameters The IPX configuration parameters enable you to get IPX up and running quickly by supplying only the necessary configuration information and accepting the defaults supplied by Bay Networks for all other Site Manager parameters. You access these parameters via the IPX Configuration window (Figure A-1). This window may look different depending on the WAN protocol you choose in the Select WAN Protocols window. 117369-B Rev. 00 A-1 Configuring IPX Services Figure A-1. IPX Configuration window Parameter: Configured Network Number (hex) Path: Default: Options: Function: Configuration Manager > Select Protocols > IPX > Interfaces None Any valid IPX network number in hexadecimal format Identifies the IPX network number that the user assigned to this IPX circuit. This parameter is active only for circuits that are not configured as IPXWAN interfaces or for those with the IPXWAN parameter explicitly disabled. Instructions: Enter a valid IPX network number in hexadecimal notation. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.22 A-2 117369-B Rev. 00 Site Manager IPX Parameters Note: The Configured Network Number parameter is active only for circuits that are not configured as IPXWAN interfaces. The IPXWAN, Common Network Number, and Negotiated Protocols parameters appear only when the circuit is configured as an IPXWAN interface. Parameter: RIP/SAP Path: Default: Options: Function: Instructions: Configuration Manager > Select Protocols > IPX > Interfaces Depends on whether you enabled RIP/SAP in the Select Protocols window Yes | No Indicates whether you have RIP/SAP configured on an interface The Configuration Manager sets the default for this parameter based on your selection in the Select Protocols window. If you selected RIP/SAP, both RIP and SAP are enabled. You can disable both RIP and SAP using the IPX Configuration window. You can also disable and reenable just RIP or just SAP using the RIP Circuit window or the SAP Circuit window, which are available via the IPX Interfaces window. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.1 (RIP) 1.3.6.1.4.1.18.3.5.5.33.1.1 (SAP) 117369-B Rev. 00 A-3 Configuring IPX Services Parameter: Configured Encaps Path: Configuration Manager > Select Protocols > IPX > Interfaces Default: Circuit medium dependent Options: Circuit medium dependent (see Instructions) Possible values: Ethernet | LSAP | Novell | SNAP | PPP Function: Specifies the encapsulation methods (such as Ethernet, PPP, Novell, LSAP, or SNAP) available for each circuit type (such as Ethernet, token ring, or sync). The encapsulation method supports communication on a specific logical network. Instructions: Select an encapsulation method that matches the one the clients and servers on the same logical network use and is appropriate for the physical circuit, as follows: • Ethernet circuits support Ethernet, LSAP, Novell, and SNAP frames. • Token ring circuits support LSAP and SNAP frames. • Synchronous circuits (V.35, RS-232/V.24, RS-422/423, X.21, T1/E1) support SNAP, PPP, and X.25 Point-to-Point (Ethernet) frames. • FDDI circuits support LSAP and SNAP frames. • HSSI circuits support PPP and SNAP frames. • ISDN circuits support PPP frames. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.40 Parameter: Circuit Index Path: Default: Options: Function: Instructions: MIB Object ID: A-4 Configuration Manager > Select Protocols > IPX > Interfaces System-assigned Any valid circuit identifier Uniquely identifies this circuit within this instance of IPX. Accept the default or enter a valid circuit identifier. 1.3.6.1.4.1.18.3.5.5.17.1.6 117369-B Rev. 00 Site Manager IPX Parameters Parameter: IPXWAN Path: Default: Options: Function: Configuration Manager > Select Protocols > IPX > Interfaces Enable Enable | Disable Enables or disables IPXWAN for this interface on this router. This parameter is active only for circuits that are configured as IPXWAN interfaces. Instructions: Select Enable to turn on IPXWAN negotiation for this interface. Select Disable to turn on IPXWAN negotiation for this interface. MIB Object ID: Not Applicable Parameter: Common Network Number Path: Configuration Manager > Select Protocols > IPX > Interfaces Default: None Options: Any valid IPX network number, 0x00000000 to 0xFFFFFFFD, in hexadecimal format Function: Specifies the IPX common network number assigned to this IPX circuit. This parameter is active only for circuits that are configured as IPXWAN interfaces that have the IPXWAN parameter enabled. Instructions: Enter a valid IPX network number in hexadecimal format. Do not use the values 0xFFFFFFFE or 0xFFFFFFFF as network numbers. These values are reserved for system use. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.24 117369-B Rev. 00 A-5 Configuring IPX Services Parameter: Negotiated Protocol(s) Path: Default: Options: Function: Configuration Manager > Select Protocols > IPX > Interfaces Unnumbered RIP RIP | Unnumbered RIP Indicates the protocol negotiated for this interface. This parameter is active only for circuits that are configured as IPXWAN interfaces and that have the IPXWAN parameter enabled. Instructions: Accept the default or click on Values to display the other choices. You can select more than one option. Click on the options you prefer, then click on OK to accept your choices. The parameter value appears as a hexadecimal number on the IPX Change Circuit window. The values are as follows: 0x00000008 -- RIP 0x00000010 -- Unnumbered RIP 0x00000018 -- RIP and Unnumbered RIP MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.8 A-6 117369-B Rev. 00 Site Manager IPX Parameters IPXWAN Configuration Parameters The IPX configuration parameters enable you to get IPX using IPXWAN services up and running quickly by supplying only the necessary configuration information and accepting the defaults supplied by Bay Networks for all other Site Manager parameters. You access these parameters via the IPXWAN Configuration window (Figure A-2). This window appears after you enable IPXWAN services in the IPX Configuration window. Figure A-2. IPXWAN Configuration Window Parameter: Router Name Path: Default: Options: Function: Configuration Manager > Select Protocols > IPX > Enable IPXWAN None Any valid NetWare router or server name Specifies a symbolic name for the router. Any IPXWAN (RFC1634-compliant) interface in the node uses this name to identify itself to the IPX router or server at the opposite end of the WAN data link. The symbolic name for the router must be unique among those assigned to IPX file servers and routers anywhere in the IPX internetwork. Instructions: See the documentation that came with your NetWare operating system for guidelines on specifying a router or server name. It is a good idea to make the name meaningful to users as well as routers. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.15.1.9 117369-B Rev. 00 A-7 Configuring IPX Services Parameter: Primary Net Number (hex) Path: Configuration Manager > Select Protocols > IPX > Enable IPXWAN Default: None Options: The Primary Network Number (PNN) is a string of up to 8 hexadecimal characters. Function: Specifies an IPX network number for IPXWAN (RFC1634-compliant) link negotiation on all slots. The value of the PNN determines whether the local or remote WAN interface serves as IPX Link Master. The node with the highest PNN value becomes the IPX Link Master. The PNN should be unique among network numbers currently assigned. Instructions: Enter a unique network number for each node requiring one or more IPXWAN (RFC1634-compliant) interfaces. (This network number must be unique across the IPX network. Do not enter a number that a server is using as an internal network number, or a number that has been assigned on any segment in the network.) All unused values between 0x00000001 and 0xFFFFFFFD are valid values. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.15.1.5 A-8 117369-B Rev. 00 Site Manager IPX Parameters IPX Global Parameters The IPX global parameters determine the way IPX works on the router. You access these parameters via the Edit IPX Global Parameters window (Figure A-3). Figure A-3. 117369-B Rev. 00 Edit IPX Global Parameters Window A-9 Configuring IPX Services Parameter: Enable Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global Enable Enable | Disable Globally enables or disables the system software mechanisms that allow users to add IPX interfaces to the router configuration: Disable -- Shuts down all IPX routing for the entire router. Enable -- Initializes IPX routing for the entire router. Associated IPX interfaces become active, depending on their respective Enable | Disable parameters and on the state of each underlying circuit. Instructions: Select Disable to disable every IPX interface on the router. Select Enable to globally reinitialize all IPX interfaces on the router; each interface maintains the most recent setting of its own interface Enable | Disable parameter. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.15.1.2 Parameter: Multiple Host Address Enable Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global Enable Enable | Disable If you enable this parameter, an IPX interface can: • Use the MAC address located in the PROM on the circuit associated with that interface. • Use a MAC address that you enter in the Host Number parameter field for that interface. Interfaces on a token ring circuit adopt a host ID number based only on the MAC address of the associated circuit. Disabling this parameter causes all IPX interfaces to adopt a single host ID number for the entire host, based either on the serial number of the router backplane or on a number that you enter in the Host Number parameter field. Instructions: Choose Enable or Disable, as appropriate for the type of configuration (standard, multiple interfaces per circuit, or multiple circuits per physical segment). See Chapter 2 for a description of each type of configuration. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.15.1.6 A-10 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Router Host Number (hex) Path: Configuration Manager > Protocols > IPX > Global Default: None Options: Any valid host number Function: The router either uses this value as a host address for all IPX interfaces, or, if left empty, uses the backplane serial number as the host address for all interfaces (circuits). Instructions: If you disable the Multiple Host Address Enable parameter and enter a unique host number, the Configuration Manager assigns this number to all IPX interfaces you configure on the router. If you disable the Multiple Host Address Enable parameter and do not enter a router host ID number for this parameter, the Configuration Manager automatically generates a unique 6-byte host ID number for all IPX interfaces. The generated host ID is based on the serial number of the router’s backplane. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.15.1.7 Caution: The IPX boxwide host address and the token ring MAC address must agree when the Multiple Host Address parameter is disabled. Parameter: Router Name Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global None Any valid NetWare router or server name Specifies a symbolic name for the router. Any IPXWAN (RFC1634-compliant) interface in the node uses this name to identify itself to the IPX router or server at the opposite end of the WAN data link. The symbolic name for the router must be unique among those assigned to IPX file servers and routers anywhere in the IPX internetwork. Instructions: See the documentation that came with your NetWare operating system for guidelines on specifying a router or server name. It is a good idea to make the name meaningful to users as well as routers. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.15.1.9 117369-B Rev. 00 A-11 Configuring IPX Services Parameter: Primary Net Number (hex) Path: Configuration Manager > Protocols > IPX > Global Default: None Options: The Primary Network Number (PNN) is a string of up to 8 hexadecimal characters. Function: Specifies an IPX network number for IPXWAN (RFC1634-compliant) link negotiation on all slots. The value of the PNN determines whether the local or remote WAN interface serves as IPX Link Master. The node with the highest PNN value becomes the IPX Link Master. The PNN should be unique among network numbers currently assigned. Instructions: Enter a unique network number for each node requiring one or more IPXWAN (RFC1634-compliant) interfaces. (This network number must be unique across the IPX network. Do not enter a number that a server is using as an internal network number, or a number that has been assigned on any segment in the network.) All unused values between 0x00000001 and 0xFFFFFFFD are valid values. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.15.1.5 A-12 117369-B Rev. 00 Site Manager IPX Parameters IPX Advanced Global Parameters IPX advanced global parameters enable you to fine tune the way IPX runs on the router. You access these parameters via the Edit IPX Advanced Global Parameters window (Figure A-4). To view all of the parameters in this window, you must click on the scroll bar. Figure A-4. 117369-B Rev. 00 IPX Advanced Global Parameters Window A-13 Configuring IPX Services Parameter: Routing Method Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced Tick Hop | Tick Specifies for all slots the method of making IPX “best-route” decisions by: Ticks -- The amount of time, expressed in ticks, that a packet requires to reach another network segment. (Each tick = 1/18th of a second.) Hops -- The number of router hops a packet must traverse to reach another network segment. If you accept the default, Tick, and the router knows about two paths to a network, and both paths have equal tick values, the router chooses the path with the smallest number of hops. If you select Hop, and the best route results in the same number of hops, the router makes its decision based only on hops. Instructions: Choose the method that results in the best routing performance. Usually, the best route is the one with: • The lowest number of ticks for a packet to reach a node on the destination network • The lowest number of hops (if multiple routes exist with equal numbers of ticks for a packet to reach a node on the destination network) If routes exist with equal numbers of ticks and hops, choose either method. We recommend using the default (tick-based) method, because tick-based routing takes into account actual link delay in determining the best path between IPX networks. Thus, it provides a more accurate routing mechanism than simply “hop count.” MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.3 A-14 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Maximum Path Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced 1 (path) 1 to 1,023 (paths) Specifies the maximum number of paths allowed for a given network destination and routing method. Instructions: Set the Maximum Path parameter to the highest number of paths, in the range 1 to 1,023, that exist from the router to any destination network, regardless of cost. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.5 Parameter: Log Filter Path: Configuration Manager > Protocols > IPX > Global > Advanced Default: Trace Options: None | Debug | Info | Trace | Debug Info | Debug Trace | Info Trace | Debug Info Trace Function: Filters out the specified type of log message. For example, the default setting (Trace) filters out trace messages. Instructions: Do not change the default value of this parameter unless you are an expert IPX user. Changing the value of this parameter produces significant boxwide effects on memory allocation within the router, and these changes can significantly affect router performance. If you are qualified as an expert user, enter a filtering mode that yields a level of performance most appropriate for network applications supported by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.4 117369-B Rev. 00 A-15 Configuring IPX Services Parameter: Maximum Path Splits Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced Enable Enable | Disable If enabled, IPX will do load balancing to a particular destination up to the number of paths specified in the Maximum Path parameter (see above). Instructions: Accept the default (Enable) to do load balancing on the number of equal cost paths specified in the Maximum Path parameter. If you enable this parameter, IPX uses up to Max Path equal cost paths that are equal to the lowest cost path. If you disable this parameter, IPX uses only the lowest cost path to send data to a destination network. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.6 Parameter: Maximum Hops Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced 16 1 to 255 (hops) Specifies the maximum number of hops an IPX packet may take to reach its destination. Instructions: Accept the default (16) or specify an integer in the range 1 to 255. In the case of RIP, every node in the network should use the same Maximum Hops parameter value. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.7 A-16 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Destination Count Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced 0 0 to 5000 (destinations) Specifies the maximum number of destinations (networks) that the user expects the router to learn. IPX uses this value to preallocate table sizes for forwarding and network tables. If you specify zero, the default value, IPX dynamically allocates the amount of memory it needs for the tables. Changing this value can greatly affect the memory use by IPX, but it can also speed learning time for the router. Instructions: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.17 Parameter: Service Count Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced 1 1 to 5000 (services) Indicates the maximum number of services that the user expects the router to learn. IPX uses this value to preallocate table sizes for service tables. If you specify zero, the default value, IPX automatically allocates the amount of memory it needs for the tables. Changing this value can greatly affect the memory use by IPX, but it can also speed learning time for the router. Instructions: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.19 117369-B Rev. 00 A-17 Configuring IPX Services Parameter: Host Count Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced 1 1 to 5000 (hosts) Indicates the maximum next-hop hosts that the user expects the router to learn. IPX uses this value to preallocate table sizes for host tables. Changing this value can greatly affect the memory use by IPX, but it can also speed learning time for the router. Instructions: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.21 Parameter: Aging Frequency Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced 10 1 to the maximum positive integer (seconds) Specifies the granularity, in seconds, for aging RIP and SAP information. IPX checks whether any routes have timed out every n seconds, where n is the interval that this parameter specifies. Instructions: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.23 A-18 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Aging Pending Frequency Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced 100 1 to maximum positive integer (routes and services) Specifies the number of routes and services to age (process) before pending. A higher number lets the aging process proceed more quickly. Instructions: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.24 Parameter: Default Route Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced Enable Enable | Disable Globally enables or disables the use of the default route 0xFFFFFFFE for IPX routing. Enable -- Directs the router to use the default route (if one exists in its routing table) when it receives an IPX packet that does not contain a known IPX destination address within the IPX protocol header. Disable -- Forces the router to drop a packet whose destination address is unknown, even if a default route exists. Instructions: Select Enable to allow IPX default routing. Select Disable to turn off default routing. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.25 117369-B Rev. 00 A-19 Configuring IPX Services Parameter: SAP via Default Route Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced Disable Enable | Disable Indicates whether a SAP advertisement can be learned from an interface if the network number advertised in the SAP advertisement is unreachable, but a default route is accessible from that interface. Enable -- Directs the router to accept a service if a direct or default route to the server is known. Disable -- Accepts a service only if a direct route to the server advertising the service is known. This feature gives you the option of making SAP entries available if the IPX default route is reachable. Instructions: Select Enable to enable IPX default routing globally for SAP advertisements. Select Disable to turn off default SAP advertisement routing. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.26 Note: Since it deviates from the IPX Default Route specification, enabling this feature may cause the interface to be incompatible with other router implementations. A-20 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Novell Certification Conformance Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced Enable Enable | Disable Indicates whether you want the router to conform to Novell NetWare standards by propagating a NetBIOS type 20 packet out of all its interfaces. Instructions: Accept the default, Enable, if you want the router to propagate NetBIOS type 20 packets out of all its interfaces (conforming to Novell standards). Select Disable if you have NetBIOS static routes configured and you want the router to direct a packet to its destination network. You must set the same option (Enable or Disable) for all routers in the network. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.15 Parameter: GNS Response Mode Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Global > Advanced Alphabetical Alphabetical | Last Learned Determines the server to choose when responding to a get_nearest_server request. Instructions: Accept the default to sort through all server names alphabetically. Select Last Learned to choose the last server learned. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.16.1.29 117369-B Rev. 00 A-21 Configuring IPX Services IPX Interface Parameters IPX interface parameters determine how IPX behaves on individual router interfaces. You access these parameters via the IPX Interfaces window (Figure A-5). To view all of the parameters in this window, you must click on the scroll bar. Figure A-5. A-22 IPX Interfaces Window 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Enable Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces Enable Enable | Disable Enables or disables IPX routing on this interface. Enable -- Initializes the IPX interface you added to a circuit. You can also use the Enable setting to reinitialize an existing disabled IPX interface. The actual operating state of an interface, once enabled, depends on: • The current state of the associated circuit • The current state of the IPX global/slotwide protocol process Disable -- Forces an IPX interface into the down (inoperative) state Instructions: Select Enable if you previously set this parameter to Disable and now want to reenable IPX routing on this interface. Select Disable only if you want to disable IPX routing on this interface. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.2 Parameter: Name Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Interfaces None Any valid IPX server name Specifies a symbolic name for the interface. See the documentation that came with your NetWare operating system for guidelines on specifying a host, interface, router, or server name. It is a good idea to make the name meaningful to users as well as to routers. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.7 117369-B Rev. 00 A-23 Configuring IPX Services Parameter: Cost Path: Configuration Manager > Protocols > IPX > Interfaces Default: 0 (for hop- or tick-based routing) Options: 0 to the maximum positive integer (if tick-based routing is enabled) 0 to one less than the value specified in the Maximum Hops parameter (if hop-based routing is enabled) Function: Sets the cost (number of ticks or hops) for this interface. The cost is added to route information learned on this interface through RIP and is included in subsequent RIP packets sent to other interfaces. IPX disposes of the packet when its hop count passes a value that is one less than the value of the Maximum Hops parameter. This value must be the same across the network. For all non-WAN and HSSI interfaces, the default value translates into a tick cost of 1 in the routing table. For all WAN interfaces, the default value translates into a tick cost of 6 in the routing table. Instructions: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.38 A-24 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Host Number (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces None Any valid IPX host ID number If you enable Multiple Host Address Enable and want to accept the PROM-based default setting for the MAC Address Select circuit parameter, this IPX interface adopts a host number based on the MAC address of the underlying circuit. In this case, a PROM on the circuit supplies the number for the MAC address of the circuit and the host number of the interface. You can enter a host number for this interface when: • Multiple Host Addressing is enabled. • You do not want to accept the PROM-based (default) setting for MAC Address Select. • The circuit type supports only selective mode of operation (such as with Ethernet circuits). If you enter a host number, the circuit adopts that value as the MAC address at which this interface can receive frames. (The MAC address configured at the circuit/line level remains effective for all other interfaces configured on the same circuit.) You can enter a host number for this interface when the underlying circuit is token ring; see the instructions that follow. Site Manager does not let you enter an IPX host number for any IPX interface if you first disable Multiple Host Address Enable in the IPX Global Parameters window. Instructions: Enter a value only if the circuit is not token ring and you want to assign a host number that is unique within the IPX internetwork to this IPX interface. To set the host number of an IPX interface on a token ring circuit, you must change the MAC Address Select parameter for that circuit to CNFG (user-configured) and enter a MAC Address Override value for the circuit. The interface uses that value as its host number. This changes the circuit MAC address for all protocols configured on that token ring circuit. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.25 117369-B Rev. 00 A-25 Configuring IPX Services Parameter: Configured Encaps Path: Configuration Manager > Protocols > IPX > Interfaces Default: Circuit medium dependent Options: Circuit medium dependent Possible values: Ethernet | LSAP | Novell | SNAP | PPP Function: Specifies the encapsulation methods (such as Ethernet, PPP, Novell, LSAP, or SNAP) available for each circuit type (such as Ethernet, token ring, or sync). The encapsulation method supports communication on a specific logical network. Instructions: Select an encapsulation method that matches the one the clients and servers on the same logical network use and is appropriate for the physical circuit, as follows: Ethernet circuits support Ethernet, LSAP, Novell, and SNAP frames. Token ring circuits support LSAP and SNAP frames. Synchronous circuits (V.35, RS-232/V.24, RS-422/423, X.21, T1/E1) support SNAP, PPP, and X.25 Point-to-Point (Ethernet) frames. FDDI circuits support LSAP and SNAP frames. HSSI circuits support PPP and SNAP Frames. ISDN circuits support PPP frames. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.40 Parameter: TR End Station Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces Disable Enable | Disable Enables or disables source routing on this interface. This parameter appears only when you add an IPX interface on a token ring circuit. Instructions: Select Enable if this interface connects to a bridged token ring network. Select Disable only if you want to disable source routing over this interface. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.59 A-26 117369-B Rev. 00 Site Manager IPX Parameters Parameter: NetBIOS Accept Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces Disable Enable | Disable Enables or disables acceptance of all NetBIOS Type 20 (broadcast) packets received by this interface from an external source. Instructions: Select Enable if you want this interface to accept all NetBIOS broadcast packets from an external source. Select Disable only if you want this interface to reject all NetBIOS broadcast packets from an external source. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.60 Parameter: NetBIOS Deliver Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces Disable Enable | Disable Enables or disables outbound delivery of all NetBIOS Type 20 (broadcast) packets received by this interface from another interface. Instructions: Select Enable if you want to reenable outbound delivery of NetBIOS broadcast packets received internally. Select Disable only to drop NetBIOS broadcast packets received internally. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.61 117369-B Rev. 00 A-27 Configuring IPX Services Parameter: FR Broadcast (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces 0xFFFFFFFFFFFF (not displayed) Default value or a user-specified WAN broadcast address Specifies a broadcast address for this IPX interface. (This parameter is available for any WAN protocol and any media type.) Instructions: The default value (0xFFFFFFFFFFFF) causes the data link layer to issue a WAN broadcast packet on all active virtual circuits. The value is not actually included in the MAC field of the packet on the WAN. The packet instead contains a value that is appropriate for the type of data link protocol. Leave blank to accept the default value or enter a WAN broadcast address to send all broadcast traffic through the IPX interface you are configuring. With the default value, the IPX router sends all broadcast traffic through all logical connections associated with the IPX interface you are configuring. Broadcast traffic includes RIP and SAP broadcasts. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.28 Parameter: FR Multicast (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces 0xFFFFFFFFFFFF (not displayed) Default value or a user-specified WAN multicast address Specifies a multicast address for this IPX interface. (This parameter is available for any WAN protocol and any media type.) The default value (0xFFFFFFFFFFFF) causes the data link layer to issue a multicast packet on all active virtual circuits. The value is not actually included in the MAC field of the packet on the WAN. The packet instead contains a value that is appropriate for the type of data link protocol. Instructions: Leave blank to accept the default value or enter a WAN multicast address to send all multicast traffic through the IPX interface you are configuring. With the default value, the IPX router sends all multicast traffic through all logical connections associated with the IPX interface you are configuring. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.30 A-28 117369-B Rev. 00 Site Manager IPX Parameters Parameter: IPX Watchdog Spoofing Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces Disable Enable | Disable Specifies whether a router can respond locally to broadcast IPX watchdog packets on behalf of clients that use dial-in connections. When you enable this parameter you also enable SPX Keep Alive Spoofing. Instructions: Enable local watchdog packet acknowledgment to improve the efficiency of IPX wide area links. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.64 Parameter: Delay Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces 0 0 to 2147483647 Specifies the length of time, in microseconds, required to transmit 1 byte of data (excluding protocol headers) to a destination on the other end of this IPX circuit if the circuit is free of other traffic. Instructions: Enter a value between 0 and 2147483647. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.66 Parameter: Stabilization Timer Delay (secs) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP 0 0 to 2147483647 Determines the amount of time, in seconds, that RIP/SAP waits before sending out initial route information when the dial-on-demand route first becomes enabled. Instructions: The more routes that you expect a router to handle or the more dynamic the network is, the higher you should set this value to allow the router enough time to assimilate incoming routes before it sends out an initial update on a circuit. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.69 117369-B Rev. 00 A-29 Configuring IPX Services Parameter: Throughput Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces 0 0 to 2147483647 Specifies the amount of data, in bits per second, that can flow through an IPX circuit if the circuit is free of other traffic. Instructions: Enter a value between 0 and 2147483647. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.67 Parameter: FR SVC Broadcast Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces Disable Enable | Disable Determines whether frame relay SVCs should be established for all adjacent hosts before sending RIP and SAP updates. Instructions: Select Enable to establish SVCs for all adjacent hosts before sending RIP and SAP updates. Otherwise, select Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.70 IPX Change Circuit Parameters IPX change circuit parameters modify the way IPX runs over a particular circuit. You access these parameters via the IPX Change Circuit window (Figure A-6) for each circuit that you have configured. A-30 117369-B Rev. 00 Site Manager IPX Parameters Figure A-6. IPX Change Circuit Window Parameter: Configured Network Number (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > Circuit > Change None Any valid IPX network number in hexadecimal format Identifies the IPX network number that the user assigned to this IPX circuit. This parameter is active only for circuits that are not configured as IPXWAN interfaces or for those with the IPXWAN parameter explicitly disabled. Instructions: Enter a valid IPX network number in hexadecimal notation. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.22 Note: The Configured Network Number parameter is active only for circuits that are not configured as IPXWAN interfaces. The IPXWAN, Common Network Number, and Negotiated Protocols parameters appear only when the circuit is configured as an IPXWAN interface. 117369-B Rev. 00 A-31 Configuring IPX Services Parameter: Configured Encaps Path: Configuration Manager > Protocols > IPX > Interfaces > Circuit > Change Default: Circuit medium dependent Options: Circuit medium dependent Possible values: Ethernet | LSAP | Novell | SNAP | PPP Function: Specifies the encapsulation methods (such as Ethernet, PPP, Novell, LSAP, or SNAP) available for each circuit type (such as Ethernet, token ring, or sync). The encapsulation method supports communication on a specific logical network. Instructions: Select an encapsulation method that matches the one the clients and servers on the same logical network use and is appropriate for the physical circuit, as follows: • Ethernet circuits support Ethernet, LSAP, Novell, and SNAP frames. • Token ring circuits support LSAP and SNAP frames. • Synchronous circuits (V.35, RS-232/V.24, RS-422/423, X.21, T1/E1) support SNAP, PPP, and X.25 Point-to-Point (Ethernet) frames. • FDDI circuits support LSAP and SNAP frames. • HSSI circuits support PPP and SNAP frames. • ISDN circuits support PPP frames. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.40 Parameter: Circuit Index Path: Default: Options: Function: Instructions: MIB Object ID: A-32 Configuration Manager > Protocols > IPX > Interfaces > Circuit > Change System-assigned Any valid circuit identifier Uniquely identifies this circuit within this instance of IPX. Accept the default or enter a valid circuit identifier. 1.3.6.1.4.1.18.3.5.5.17.1.6 117369-B Rev. 00 Site Manager IPX Parameters Parameter: IPXWAN Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > Circuit > Change Enable Enable | Disable Enables or disables IPXWAN for this interface on this router. This parameter is active only for circuits that are configured as IPXWAN interfaces. Instructions: Select Enable to turn on IPXWAN negotiation for this interface. Select Disable to turn on IPXWAN negotiation for this interface. MIB Object ID: Not Applicable Parameter: Common Network Number Path: Configuration Manager > Protocols > IPX > Interfaces > Circuit > Change Default: None Options: Any valid IPX network number, 0x00000000 to 0xFFFFFFFD in hexadecimal format Function: Specifies the IPX common network number assigned to this IPX circuit. This parameter is active only for circuits that are configured as IPXWAN interfaces that have the IPXWAN parameter enabled. Instructions: Enter a valid IPX network number in hexadecimal format. Do not use the values 0xFFFFFFFE or 0xFFFFFFFF as network numbers. These values are reserved for system use. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.24 117369-B Rev. 00 A-33 Configuring IPX Services Parameter: Negotiated Protocol(s) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > Circuit > Change Unnumbered RIP RIP | Unnumbered RIP Indicates the protocol negotiated for this interface. This parameter is active only for circuits that are configured as IPXWAN interfaces and that have the IPXWAN parameter enabled. Instructions: Accept the default or click on Values to display the other choices. You can select more than one option. Click on the options you prefer, then click on OK to accept your choices. The parameter value appears as a hexadecimal number on the IPX Change Circuit window. The values are as follows: 0x00000008 -- RIP 0x00000010 -- Unnumbered RIP 0x00000018 -- RIP and Unnumbered RIP MIB Object ID: 1.3.6.1.4.1.18.3.5.5.17.1.8 A-34 117369-B Rev. 00 Site Manager IPX Parameters IPX RIP Circuit Parameters IPX RIP circuit parameters determine the way RIP behaves on a particular circuit. You access these parameters via the IPX RIP Circuit window (Figure A-7). To view all of the parameters in this window, you must click on the scroll bar. Figure A-7. 117369-B Rev. 00 IPX RIP Circuit Window A-35 Configuring IPX Services Parameter: Enable Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Interfaces > RIP Enable Enable | Disable Specifies whether RIP is enabled on this IPX circuit. Select Enable to enable RIP on this circuit. Select Disable to disable RIP on this circuit. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.2 Note: If this parameter is set to Enable, a route filter can still prohibit the interface from updating its internal routing tables. See the description of route filtering in this chapter. Parameter: Mode Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Interfaces > RIP Listen/Supply Listen/Supply | Listen | Supply Specifies the mode for this circuit. Select one of the following values: Listen/Supply -- specifies that this interface both listens for and supplies RIP updates, as described in the following items. Listen -- specifies that this interface listens to RIP Periodic and Triggered updates from neighboring networks and conveys received routing information to its internal routing table. Supply -- specifies that the interface transmits all RIP Periodic and Triggered updates to routers in neighboring networks. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.6 A-36 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Pace Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP 18 0 to 1000 Specifies the maximum pace (in packets per second) at which RIP packets can be sent on this circuit. A value of zero means that there is no limit on the pace. Instructions: Accept the default or specify an integer value up to 1000. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.7 Parameter: Update Interval (sec) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP 60 0 to 2678400 Adjusts the frequency of RIP update packet transmissions, in seconds, for this circuit. Instructions: The higher the number you enter, the less frequent the transmissions. If you enter zero, no periodic RIP updates are sent out over the IPX interface to the router. However, RIP immediate (one-time) update packets still propagate through the network, in compliance with Novell standards. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.8 Parameter: Age Multiplier Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP 3 1 to 6 (increments) Specifies the holding multiplier as the number of update intervals for information received in RIP periodic updates. Instructions: Accept the default value or specify a value in the range 1 to 6. Increasing this value can cause routes to take longer to age out. Decreasing it could cause the router to age routes prematurely, if routing updates are missed. The combination of the update interval and age multiplier should be the same for all systems on a network segment. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.9 117369-B Rev. 00 A-37 Configuring IPX Services Parameter: Packet Size Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Interfaces > RIP 432 Circuit-type dependent Specifies the maximum RIP packet size, in bytes, used on this circuit. Accept the default (432 bytes) unless you have a specific reason for specifying a different size packet. The packet size plus the IPX header (30 bytes) cannot exceed the MTU of the link. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.10 Parameter: Use Multicast Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP Yes Yes | No Specifies whether to use a multicast address, configured with the Multicast Address parameter, to send RIP packets. Instructions: Accept the default to allow multicast transmission of RIP packets. Select No to disable multicast transmission of RIP packets. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.14 A-38 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Split Horizon Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP Enable Enable | Disable When generating RIP updates to be transmitted from an interface, the interface can exclude RIP routes learned on that interface. Instructions: Select Enable if you previously set this parameter to Disable and now do not want the router to transmit RIP updates received from the interface over that same interface. Select Disable only if you want the router to transmit RIP updates received from the interface over that same interface. Routes learned on that interface will be included in the RIP updates generated for that interface. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.15 Parameter: Immediate Update Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP Enable Enable | Disable When a change in status occurs for this circuit, immediately propagate that information to other routers in the internetwork. Instructions: Accept the default. Enabling this parameter facilitates network traffic by letting routers know immediately about new or failed routes. When this parameter is disabled, other routers learn about such changes only at the next periodic update interval. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.17 117369-B Rev. 00 A-39 Configuring IPX Services Parameter: Default Route Supply Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP Disable Enable | Disable If a default route exists in the routing table, this parameter specifies whether to advertise the default route, 0xFFFFFFE, in RIP packets. Instructions: Select Enable to enable default route supply (that is, to advertise the default route) on this circuit. Select Disable to disable default route supply (that is, not advertise the default route) on this circuit. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.18 Parameter: Default Route Listen Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > RIP Disable Enable | Disable Specifies whether to accept the default route, 0xFFFFFFE, in RIP packets received on this circuit. Instructions: Select Enable to accept the default route in RIP packets on this circuit. Select Disable to reject the default route in RIP packets on this circuit. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.32.1.19 A-40 117369-B Rev. 00 Site Manager IPX Parameters IPX SAP Circuit Parameters IPX SAP circuit parameters determine the way SAP works on a particular circuit. You access these parameters via the IPX SAP Circuit window (Figure A-8). Figure A-8. IPX SAP Circuit Window Parameter: Enable Path: Default: Options: Function: Instructions: MIB Object ID: Configuration Manager > Protocols > IPX > Interfaces > SAP Enable Enable | Disable Specifies whether SAP is enabled on this IPX circuit. Select Enable to enable SAP on this circuit; select Disable to disable it. 1.3.6.1.4.1.18.3.5.5.33.1.2 Note: If this parameter is set to Enable, a SAP filter can still prohibit the interface from updating its internal SAP tables. See the description of SAP filtering in Chapter 5. 117369-B Rev. 00 A-41 Configuring IPX Services Parameter: Mode Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Interfaces > SAP Listen/Supply Listen/Supply | Listen | Supply Specifies the mode for this circuit. Select one of the following values: Listen/Supply -- specifies that this interface both listens for and supplies SAP updates, as described in the following items. Listen -- specifies that this interface listens to SAP Periodic and Triggered updates from neighboring networks and conveys received SAP services information to its internal SAP services table. Supply -- specifies that the interface transmits all SAP Periodic and Triggered updates to routers in neighboring networks. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.6 Parameter: Pace Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > SAP 18 0 to 1000 Specifies the maximum pace (in packets per second) at which SAP packets can be sent on this circuit. A value of zero means that there is no limit on the pace. Instructions: Accept the default or specify an integer value up to 1000. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.7 A-42 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Update Interval (sec) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > SAP 60 0 to 2678400 Adjusts the frequency, in seconds, of SAP update packet transmissions for this circuit. Instructions: The higher the number you enter, the less frequent the transmissions. If you enter zero, no periodic updates are sent out over the IPX interface to the router. However, SAP immediate (one-time) updates still propagate through the network, in compliance with Novell standards. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.8 Parameter: Age Multiplier Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > SAP 3 1 to 6 (increments) Specifies the holding multiplier, in update interval increments, for information received in SAP periodic updates. Instructions: Accept the default value or specify a value in the range 1 to 6. Increasing this value can cause routes to take longer to age out. Decreasing it could cause the router to age routes prematurely, if routing updates are missed. The combination of the update interval and age multiplier should be the same for all systems on a network segment. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.9 117369-B Rev. 00 A-43 Configuring IPX Services Parameter: Packet Size Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Interfaces > SAP 480 Circuit-type dependent Specifies the maximum SAP packet size, in bytes, used on this circuit. Accept the default (480 bytes) unless you have a specific reason for specifying a different size packet. The packet size plus the IPX header (30 bytes) cannot exceed the MTU of the link. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.10 Parameter: Nearest Server Reply Path: Default: Options: Function: Instructions: Configuration Manager Protocols > IPX > Interfaces > SAP Yes Yes | No Specifies whether to respond to SAP get_nearest_server requests. Accept the default to allow this router to respond to a SAP get_nearest_server request. If you have disabled split horizon, you may want to set this parameter to No. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.11 Parameter: Use Multicast Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Interfaces > SAP Yes Yes | No Specifies whether to use a multicast address to send SAP packets. Accept the default to allow multicast transmission of SAP packets. Select No to disable multicast transmission of SAP packets. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.16 A-44 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Save Full Name Path: Configuration Manager > Protocols > IPX > Interfaces > SAP Default: Yes Options: Yes | No Function: Determines whether the router will save all 48 bytes in the service name field of SAP packets or ignore all characters after the null character when a service field name is less than 48 bytes. Instructions: Accept the default to save all 48 bytes in the service name field of SAP packets. Select No to ignore all characters after the null character. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.20 Parameter: Split Horizon Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > SAP Enable Enable | Disable When generating SAP updates to be transmitted from an interface, the interface can exclude SAP servers learned on that interface. Instructions: Select Enable if you previously set this parameter to Disable and now do not want the router to transmit SAP updates received from the interface over that same interface. Select Disable only if you want the router to transmit SAP updates received from the interface over that same interface. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.17 117369-B Rev. 00 A-45 Configuring IPX Services Parameter: Immediate Update Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Interfaces > SAP Enable Enable | Disable When a change in status occurs for this circuit, immediately propagate that information to other routers in the internetwork. Instructions: Accept the default. Enabling this parameter facilitates network traffic by letting routers know immediately about new or failed services. When this parameter is disabled, other routers learn about such changes only at the next periodic update interval. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.33.1.19 IPX NetBIOS Static Route Configuration Parameters IPX NetBIOS static route configuration parameters establish a NetBIOS static route.You access these parameters via the IPX NetBIOS static route configuration window (Figure A-9). Figure A-9. A-46 IPX NetBIOS Static Route Configuration Window 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Target Server Path: Configuration Manager > Protocols > IPX > NetBIOS Static Routes > Add Default: None Options: The name of a NetBIOS target server, specified as a string of up to 16 alphanumeric characters (which can include wildcards and pattern-matching characters). You can include any printable character, including $, #, and so on. To specify a backslash, enter two backslashes (\\). You can also use the hexadecimal equivalent (\xx) of any valid ASCII character. For example, you can specify \20 for space or \21 for ! (note that \xx counts as one character). Function: Specifies the name of the NetBIOS server. Instructions: Enter the name or part of the name of the NetBIOS server. The name can be up to 16 alphanumeric characters. For a list of the wildcards and pattern-matching characters, refer to Table 5-1 on page 5-142. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.27.1.4 Note: You cannot change the Target Server parameter once you set it. Parameter: Target Network (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > NetBIOS Static Routes > Add None Any valid network address in hexadecimal notation Specifies the address of a destination network that you want to receive NetBIOS broadcast packets destined for the specified target server. Instructions: Enter a network address of up to 8 hexadecimal characters. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.27.1.5 Note: The Configuration Manager does not let you reconfigure the Target Server parameter for a static route. If you want to change this parameter, you must delete the static route and add a new route. However, you can reconfigure all other parameters associated with a static route. 117369-B Rev. 00 A-47 Configuring IPX Services IPX NetBIOS Static Route Parameters IPX NetBIOS static route parameters determine the location of a NetBIOS static route.You access these parameters via the IPX NetBIOS static route configuration window (Figure A-10). Figure A-10. A-48 IPX NetBIOS Static Routes Window 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Enable Path: Default: Options: Function: Configuration Manager > Protocols > IPX > NetBIOS Static Routes Enable Enable | Disable Specifies the state (active or inactive) of the static route record in the NetBIOS routing table. Instructions: Select Disable to make the static route record inactive in the NetBIOS routing table. Select Enable to make the static route record active in the NetBIOS routing table. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.27.1.2 Parameter: Target Network (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > NetBIOS Static Routes None Any valid network address in hexadecimal notation Specifies the address of a destination network that you want to receive NetBIOS broadcast packets destined for the specified target server. Instructions: Enter a network address of up to 8 hexadecimal characters. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.27.1.5 117369-B Rev. 00 A-49 Configuring IPX Services Adjacent Hosts Configuration Parameters IPX adjacent hosts configuration parameters establish an adjacent host. You access these parameters via the IPX Adjacent Hosts configuration window (Figure A-11). Figure A-11. A-50 IPX Adjacent Hosts Configuration Window 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Host Address (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: None Options: Valid host ID of the adjacent host Function: Specifies the host ID of the adjacent host. Instructions: Enter a host ID of up to 12 hexadecimal characters. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.5 Parameter: WAN Number Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: None Options: WAN Address | Data Link Connection Identifier | X.25 PVC Logical Channel Number Function: Lets you enter a WAN address, DLCI, or X.25 PVC logical channel number. The format depends on the underlying data link protocol type. Instructions: Enter a WAN address of up to 16 hexadecimal characters if the interface is on an ATM or SMDS network. Enter a decimal DLCI number if the interface is on a frame relay network. Enter an X.121 address if the interface is on an X.25 switched virtual circuit. Enter a logical channel number if the interface is on an X.25 permanent virtual circuit. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.6 117369-B Rev. 00 A-51 Configuring IPX Services Parameter: Remote Party Sub-Address Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: None Options: Eight-digit hexadecimal number Function: Establishes a switched virtual circuit (SVC) connection to the adjacent host. Instructions: Supply the address, in hexadecimal format, of the remote party. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.7 Parameter: Remote Party Type of Number Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: International Options: Unknown | International Function: Specifies the type of number used to establish a switched virtual circuit (SVC) connection to the adjacent host. Instructions: Accept the default. Otherwise, select Unknown. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.8 Parameter: Adjacent Host Type Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: Default Options: Default | Frame Relay (E.164) | Frame Relay (X.121) | Frame Relay (DLCI) Function: Specifies the type of static host used when establishing a switched virtual circuit (SVC) connection to the adjacent host. Instructions: Specify the type of static host. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.9 A-52 117369-B Rev. 00 Site Manager IPX Parameters IPX Adjacent Hosts Parameters IPX adjacent hosts parameters determine the location of an adjacent host. You access these parameters via the IPX Adjacent Hosts window (Figure A-12). Figure A-12. IPX Adjacent Hosts Window Parameter: Enable Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts Enable Enable | Disable Sets the state (active or inactive) of the adjacent host record in the IPX routing tables. Instructions: Select Disable to make the adjacent host record inactive in the IPX host table. Select Enable to make the adjacent host record active in the IPX host table. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.2 117369-B Rev. 00 A-53 Configuring IPX Services Parameter: WAN Number Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: None Options: WAN Address | Data Link Connection Identifier | X.25 PVC Logical Channel Number Function: Lets you enter a WAN address, DLCI, or X.25 PVC logical channel number. The format depends on the underlying data link protocol type. Instructions: Enter a WAN address of up to 16 hexadecimal characters if the interface is on an ATM or SMDS network. Enter a decimal DLCI number if the interface is on a frame relay network. Enter an X.121 address if the interface is on an X.25 switched virtual circuit. Enter a logical channel number if the interface is on an X.25 permanent virtual circuit. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.6 A-54 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Remote Party Sub-Address Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: None Options: Eight-digit hexadecimal number Function: Establishes a switched virtual circuit (SVC) connection to the adjacent host. Instructions: Supply the address, in hexadecimal format, of the remote party. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.7 Parameter: Remote Party Type of Number Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: International Options: Unknown | International Function: Specifies the type of number used to establish a switched virtual circuit (SVC) connection to the adjacent host. Instructions: Accept the default. Otherwise, select Unknown. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.8 Parameter: Adjacent Host Type Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Adj. Hosts > Add Default: Default Options: Default | Frame Relay (E.164) | Frame Relay (X.121) | Frame Relay (DLCI) Function: Specifies the type of static host used when establishing a switched virtual circuit (SVC) connection to the adjacent host. Instructions: Specify the type of static host. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.26.1.9 117369-B Rev. 00 A-55 Configuring IPX Services IPX Static Route Configuration Parameters Figure A-13. IPX Static Route Configuration Window Parameter: Target Network (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Route > Add Default: None Options: Any valid network address in hexadecimal notation Function: Specifies the address of the network to which you want to configure the static route. Instructions: Enter a network address of up to 8 hexadecimal characters or click on Def. Route to have the Configuration Manager fill in the default route 0xFFFFFFFE. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.19.1.5 Note: The Configuration Manager does not let you reconfigure the Target Network parameter for a static route. If you want to change this parameter, you must delete the static route and add a new route with the proper information. However, you can reconfigure all other parameters associated with a static route. A-56 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Next Hop Host (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Route > Add Default: None Options: Any valid host address in hexadecimal notation Function: Specifies the address of the next-hop host in the static routing path. Instructions: Enter a host address of up to 12 hexadecimal characters. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.19.1.8 Parameter: Hop Count Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Route > Add Default: 0 Options: 0 to the value of the Maximum Hops parameter, minus 1 Function: The IPX router uses Hop Count when determining the best route for a datagram to follow. The hop count is also propagated through RIP. The default setting of 0 for static routes means “use the hop count associated with the interface.” Instructions: Accept the default (0) or enter a value from 1 to one less than the maximum number of hops. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.19.1.7 117369-B Rev. 00 A-57 Configuring IPX Services Parameter: Ticks Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Route > Add Default: 0 Options: 0 to maximum positive integer Function: Specifies the number of 1/18th-second timer ticks required for an IPX datagram to traverse this static route. The IPX router uses tick cost when determining the best route for a datagram to follow. The tick cost is also propagated through RIP. The default setting of 0 for the tick cost of static routes means “use the tick count associated with the interface.” Instructions: Accept the default value (0) or enter a value from 1 to the maximum positive integer. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.19.1.6 A-58 117369-B Rev. 00 Site Manager IPX Parameters IPX Static Route Parameter Descriptions Figure A-14. IPX Static Routes Window Parameter: Enable Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Route Enable Enable | Disable Specifies the state (active or inactive) of the static route record in the IPX routing tables. Instructions: Select Disable to make the static route record inactive in the IPX routing table. Select Enable to make the static route record active in the IPX routing table. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.19.1.2 117369-B Rev. 00 A-59 Configuring IPX Services Parameter: Hop Count Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Route 0 0 to the value of the Maximum Hops parameter, minus 1 The IPX router uses Hop Count when determining the best route for a datagram to follow. The hop count is also propagated through RIP. The default setting of 0 for static routes means “use the hop count associated with the interface.” Instructions: Accept the default (0) or enter a value from 1 to one less than the maximum number of hops. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.19.1.7 Parameter: Ticks Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Route 0 0 to maximum positive integer Specifies the number of 1/18th-second timer ticks required for an IPX datagram to traverse this static route. The IPX router uses tick cost when determining the best route for a datagram to follow. The tick cost is also propagated through RIP. The default setting of 0 for the tick cost of static routes means “use the tick count associated with the interface.” Instructions: Accept the default value (0) or enter a value from 1 to the maximum positive integer. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.19.1.6 Parameter: Next Hop Host (hex) Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Route None Any valid host address in hexadecimal notation Specifies the address of the next-hop host in the static routing path. Enter a next-hop host address of up to 12 hexadecimal characters. The next-hop host address is the MAC address of the next hop on the way to your destination. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.19.1.8 A-60 117369-B Rev. 00 Site Manager IPX Parameters IPX Static Service Configuration Parameters This section describes all parameters shown in the IPX Static Service Configuration window (Figure A-15). Figure A-15. IPX Static Service Configuration Window Parameter: Service Name Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv. > Add Default: None Options: Any valid Novell NetWare server name Function: Assigns a symbolic name to the service you want to advertise. Instructions: Use the actual name of the server that the clients will attach to. It helps if this is a name meaningful to the network administrator. The name must be unique among all names assigned to IPX servers of the same type on the IPX internetwork. See the documentation that came with your NetWare operating system for guidelines on specifying a server name. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.5 117369-B Rev. 00 A-61 Configuring IPX Services Parameter: Service Type (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv. > Add Default: None Options: Any valid Novell server type number in 4-digit hexadecimal format. (The number must be a value between 0x0001 and 0xFFFE, inclusive.) Function: Specifies the type of service to advertise from the associated IPX (LAN) interface (for example, 0x0004 for fileserver, 0x0007 for printerserver). Instructions: Enter the server type number in 4-digit hexadecimal format. Include leading zeros. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.6 Parameter: Target Network (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv. > Add Default: None Options: Any valid IPX network address in hexadecimal notation Function: Specifies the network address of this service. Instructions: Enter a network address of up to 8 hexadecimal characters. The path to the network you specify for this service must exist as an entry in the IPX routing table. The entry can be learned dynamically by the router, or you can configure the entry as a static route. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.7 A-62 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Host Number (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv. > Add Default: None Options: The address (host ID) of the service Function: Specifies the address of a remote IPX host (a NetWare server) that can provide local clients with specific NetWare services, such as file, print, gateway, or terminal server services. Instructions: Enter a string of up to 12 hexadecimal characters (6 bytes) as the address (host ID) of the remote IPX host/server. (For example, most NetWare Server host IDs are usually 0x000000000001.) MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.8 Parameter: Socket (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Add Default: None Options: Any valid socket address. (The number must have a value between 0x0001 and 0xFFFE, inclusive.) Function: Specifies the socket address of this service. Instructions: Enter any valid socket address consisting of up to 4 hexadecimal characters (for example, 0x0451). MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.9 Note: Refer to Appendix C for a list of common service types (current as of the publication date of this manual). 117369-B Rev. 00 A-63 Configuring IPX Services IPX Static Service Parameters This section describes all parameters shown in the IPX Static Services window (Figure A-16). Note: The Configuration Manager does not let you change the Service Name or Type parameters you set when you add a static service. To establish new values for these parameters for a particular static service, you must delete that service and configure a new service. You can, however, reconfigure all other parameters associated with a static service. Figure A-16. A-64 IPX Static Services Window 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Enable Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv Enable Enable | Disable Enables or disables a static service previously added to a specific IPX interface. Select Enable to reenable a static service previously disabled. This restores client access to NetWare services configured earlier on the IPX interface. Disable a static service to make NetWare services configured earlier unavailable to clients. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.2 Parameter: Network (hex) Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv None Any valid IPX network address in hexadecimal notation Specifies the network address of this service. Enter a network address of up to 8 hexadecimal characters. The path to the network you specify for this service must exist as an entry in the IPX routing table. The entry can be learned dynamically by the router, or you can configure the entry as a static route. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.7 Parameter: Host Number (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv None The address (host ID) of the service Specifies the address of a remote IPX host (a NetWare server) that can provide local clients with specific NetWare services, such as file, print, gateway, or terminal server services. Instructions: Enter a string of up to 12 hexadecimal characters (6 bytes) as the address (host ID) of the remote IPX host/server. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.8 117369-B Rev. 00 A-65 Configuring IPX Services Parameter: Socket (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv Default: None Options: Any valid socket address. (The number must have a value between 0x0001 and 0xFFFE, inclusive.) Function: Specifies the socket address of this service. Instructions: Enter any valid socket address consisting of up to 4 hexadecimal characters. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.23.1.9 Parameter: Hop Count Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Static Serv Default: None Options: Any valid number of hops, from 1 to the value of the Maximum Hops parameter, minus 1 Function: Specifies the number of subsequent router hops required from this router to reach a specific remote Novell server or service. Instructions: Enter the number of router hops that exist between the router and the service you want to advertise. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.12.1.10 A-66 117369-B Rev. 00 Site Manager IPX Parameters Route Filter Configuration Parameters This section describes all parameters shown in the IPX Route Filter Configuration window (Figure A-17). Figure A-17. IPX Route Filter Configuration Window Parameter: Target Network (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Table > Route Filter > Add Default: None Options: Any valid NetWare address in hexadecimal format Function: Identifies the network on which you want to apply the filter (the “filter ID” in the previous example). Instructions: Enter the address of the target network in hexadecimal format. Using a mask, you can make this stand for a single ID or for a range of IDs with similar addresses. You can select all IDs by entering the wildcard value 0xFFFFFFF. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.6 117369-B Rev. 00 A-67 Configuring IPX Services Parameter: Target Network Mask (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Table > Route Filter > Add Default: None Options: 0x00000000 to 0xFFFFFFFF Function: Specifies the mask that you want to apply. Instructions: Enter 8 hexadecimal characters. The character F in the mask definition requires an exact match with the corresponding character in the filter ID. The mask character 0 matches any alphanumeric character. You can combine the F and 0 characters in any order in the mask to filter any combination of network addressing schemes used within the IPX internetwork. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.7 Parameter: Filter Priority Path: Configuration Manager > Protocols > IPX > Static/Filter Table > Route Filter > Add Default: None Options: 0 to the maximum positive integer Function: Specifies the priority of this filter in relation to other filters of the same type. Instructions: Enter a decimal value that indicates this filter’s priority relative to other filters of the same type for this interface. Lower values indicate higher priorities. (The highest priority is 0.) MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.13 A-68 117369-B Rev. 00 Site Manager IPX Parameters IPX Route Filter Parameters This section describes how to set all the parameters shown on the IPX Route Filters window (Figure A-18). Figure A-18. IPX Route Filters Window Parameter: Enable Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Route Filter Enable Enable | Disable Enables or disables a route filter previously added to a specific IPX interface. Select Enable to enable a route filter. Select Disable to disable a route filter. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.2 117369-B Rev. 00 A-69 Configuring IPX Services Parameter: Target Network (hex) Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Route Filter None Any valid NetWare address in hexadecimal format Identifies the network on which you want to apply the filter. Enter the address of the target network in hexadecimal format. Using a filter, you can make this stand for a single ID or for a range of IDs with similar addresses. You can select all IDs by entering the wildcard value 0xFFFFFFF. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.6 Parameter: Target Network Mask (hex) Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Route Filter None 0x00000000 to 0xFFFFFFFF Specifies the mask that you want to apply. Enter 8 hexadecimal characters. The character F in the mask definition requires an exact match with the corresponding character in the filter ID. The mask character 0 matches any alphanumeric character. You can combine the F and 0 characters in any order in the mask to filter any combination of network addressing schemes used within the IPX internetwork. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.7 A-70 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Filter Priority Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Route Filter None 0 to the maximum positive integer Specifies the priority of this filter in relation to other filters of the same type. Enter a decimal value that indicates this filter’s priority relative to other filters of the same type for this interface. Lower values indicate higher priorities. (The highest priority is 0.) MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.13 Parameter: Mode Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Route Filter Outbound Outbound | Inbound | Both Specifies whether you want to apply the filter to inbound packets, outbound packets, or both. Instructions: Specify Inbound if you want to apply the filter to RIP packets coming into this interface. Specify Both if you want to filter both inbound and outbound packets. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.8 Parameter: Protocol Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Route Filter Any Any | Local | RIP | Static Applies this filter only to routes learned on the specified protocol when sending RIP updates. This does not apply to Inbound routes. Instructions: Specify the protocol on which you want to apply the filter. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.10 117369-B Rev. 00 A-71 Configuring IPX Services Parameter: Action Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Table > Route Filter Advertise/Accept Advertise/Accept | Suppress Specifies how to process any RIP advertisement that matches the route filter criteria you established. Instructions: Select Advertise/Accept to enable the filter to allow advertisement or acceptance of routes that match the specified route filter criteria. Select Suppress to configure the IPX router to drop RIP advertisements that match the specified route filter criteria. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.9 A-72 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Cost Path: Configuration Manager > Protocols > IPX > Static/Filter Table > Route Filter Default: 1 (for hop- or tick-based routing) Options: 1 to maximum positive integer (if tick-based routing is enabled) 1 to one less than the value specified in the Maximum Hops parameter (if hop-based routing is enabled) Function: Used only when the Action parameter is Advertise/Accept, this parameter assigns a cost for routes matching this filter. A zero cost indicates that the route’s actual cost should be used. This parameter sets the cost (number of ticks or hops) for this interface. The cost is included in subsequent RIP packets sent to other interfaces. IPX disposes of the packet when its hop count passes a value that is one less than the value of the Maximum Hops parameter. This value must be the same across the network. Instructions: Do not change the default value of this parameter unless you are an expert IPX user. Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. If the filter is an inbound filter, the entered cost replaces the cost associated with the route in the RIP advertisement, and the router uses this cost in its calculations. If this is an outbound filter, the entered cost replaces the route’s cost that this router advertises in RIP packets. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.29.1.11 117369-B Rev. 00 A-73 Configuring IPX Services Service Network Filter Configuration Parameters This section describes all parameters shown in the IPX Service Network Filter Configuration window (Figure A-19). Figure A-19. IPX Service Network Filter Configuration Window Parameter: Target Network (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter > Add Default: None Options: Any valid network address in hexadecimal notation Function: Specifies the network that you want to filter. The value 0xFFFFFFFF specifies all networks. Instructions: Enter a network address of up to 8 hexadecimal characters. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.6 A-74 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Target Network Mask (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter > Add Default: None Options: Any valid IPX network address in hexadecimal notation Function: The mask, combined with the Target Network parameter value, determines which networks will be filtered. Instructions: Enter a network address or filter pattern of up to 8 hexadecimal characters. A mask of 0xFFFFFFFF specifies an exact match with the network address specified in the Target Network parameter. You can specify all networks by entering a Target Network of 0xFFFFFFFF and a Target Network Mask of 0xFFFFFFFF. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.7 Parameter: Target Service Type (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter > Add Default: None Options: Any valid Novell server type number in 4-digit hexadecimal format Function: Specifies the type of server that the filter should recognize in its criteria for allowing certain SAP broadcasts to pass to the locally attached network segment. Instructions: Enter the server type number in 4-digit hexadecimal format. Include leading 0s. For all types, enter a value of 0xFFFF. See Appendix A for a list of valid server types. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.8 117369-B Rev. 00 A-75 Configuring IPX Services Parameter: Filter Priority Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter > Add Default: None Options: 0 to the maximum positive integer Function: Specifies the priority of this filter in relation to other filters of the same type. Instructions: Enter a decimal value that indicates this filter’s priority relative to other filters of the same type for this interface. Lower values indicate higher priorities. (The highest priority is 0.) MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.14 A-76 117369-B Rev. 00 Site Manager IPX Parameters IPX Service Network Filter Parameters This section describes all parameters shown in the IPX Service Network Filters window (Figure A-20). Figure A-20. 117369-B Rev. 00 IPX Service Network Filters Window A-77 Configuring IPX Services Parameter: Enable Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter Enable Enable | Disable Specifies whether the service network filter displayed is active on this interface. Select Enable to enable the service network filter. Select Disable to disable the service network filter. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.2 Parameter: Target Network (hex) Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter None Any valid NetWare address in hexadecimal notation Specifies the network on which you want to apply the service network filter. Enter the address of the target network in hexadecimal format. Using a mask, you can make this stand for a single network or a range of networks with similar addresses. You can specify all networks by entering a Target Network of 0xFFFFFFF and a Target Network Mask of 0xFFFFFFF. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.6 Parameter: Target Network Mask (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter None Any valid IPX network address in hexadecimal notation The mask, combined with the Target Network parameter value, determines which networks will be filtered. Instructions: Enter a network address or filter pattern of up to 8 hexadecimal characters. A mask of 0xFFFFFFFF specifies an exact match with the network address specified in the Target Network parameter. You can specify all networks by entering a Target Network of 0xFFFFFFFF and a Target Network Mask of 0xFFFFFFFF. A value of 0x0 is invalid. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.7 A-78 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Target Service Type (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter None Any valid Novell server type number in 4-digit hexadecimal format Specifies the type of server that the filter should recognize in its criteria for allowing certain SAP broadcasts to pass to the locally attached network segment. Instructions: Enter the server type number in 4-digit hexadecimal format. Include leading zeros. For all types, enter a value of 0xFFFF. See Appendix A for a list of valid server types. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.8 Parameter: Filter Priority Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter None 0 to the maximum positive integer Specifies the priority of this filter in relation to other filters of the same type. Enter a decimal value that indicates this filter’s priority relative to other filters of the same type for this interface. Lower values indicate higher priorities. (The highest priority is 0.) MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.14 Parameter: Mode Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter Outbound Outbound | Inbound | Both Specifies whether you want to apply the filter to inbound packets, outbound packets, or both. Instructions: Specify Inbound if you want to apply the filter to SAP packets coming into this interface. Specify Both if you want to filter both inbound and outbound packets. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.9 117369-B Rev. 00 A-79 Configuring IPX Services Parameter: Protocol Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter Any Any | Local | Static | SAP Applies this outbound filter only to services learned on the specified protocol when sending SAP updates. This does not apply to inbound services. Instructions: Specify the protocol on which you want to apply the filter. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.11 Parameter: Action Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter Advertise/Accept Advertise/Accept | Suppress Specifies how to process any SAP advertisement that matches the SAP filter criteria you established in the Target Network and Target Service Type parameters. Instructions: Select Advertise/Accept to enable the filter to allow advertisement or acceptance of services that match the filter criteria you established in the Target Network and Target Service Type parameters. Select Suppress to configure the IPX router to drop SAP advertisements that match the SAP filter criteria you established in the Target Network and Target Service Type parameters. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.10 A-80 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Cost Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Net Filter Default: 1 (for hop- or tick-based routing) Options: 1 to maximum positive integer (if tick-based routing is enabled) 1 to one less than the value specified in the Maximum Hops parameter (if hop-based routing is enabled) Function: Used only when the Action parameter is Advertise/Accept, this parameter assigns a cost for routes matching this filter. A zero cost indicates that the route’s actual cost should be used. This parameter sets the cost (number of ticks or hops) for this interface. The cost is included in subsequent SAP packets sent to other interfaces. IPX disposes of the packet when its hop count passes a value that is one less than the value of the Maximum Hops parameter. This value must be the same across the network. Instructions: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. If the filter is an inbound filter, the entered cost replaces the cost associated with the server in SAP advertisements sent from this router. If this is an outbound filter, the entered cost replaces the server’s cost that is advertised in SAP packets by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.30.1.12 117369-B Rev. 00 A-81 Configuring IPX Services IPX Service Name Filter Configuration Parameters This section describes all parameters shown in the IPX Service Name Filter Configuration window (Figure A-21). Figure A-21. IPX Service Name Filter Configuration Window Parameter: Target Service Name Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Service Name Filters Default: None Options: Any valid alphanumeric server name or one containing wildcard characters or a pattern-matching regular expression Function: This is the filter that you want to apply. It can specify the name of the server to which you are applying the service name filter, or it can be a filter containing a wildcard or a pattern (regular expression) to be matched. (See “Using Wildcards with SAP Filters” and “Using Pattern Matching with SAP Filters” for lists of these characters.) Instructions: Enter a service name or filter pattern consisting of up to 48 alphanumeric characters, optionally including wildcards or a regular expression (pattern). MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.6 A-82 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Target Service Type (hex) Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Service Name Filters Default: None Options: Any valid Novell service type number in 4-digit hexadecimal format Function: Specifies the type of service that the filter should recognize in its criteria for allowing certain SAP broadcasts to pass to the locally attached network segment. Instructions: Enter the service type number in 4-digit hexadecimal format. Include leading zeros. For all types, enter a value of FFFF. See Appendix A for a list of valid service types. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.7 Parameter: Filter Priority Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Service Name Filters Default: None Options: 0 to the maximum positive integer Function: Specifies the priority of this filter in relation to other filters of the same type. Instructions: Enter a decimal value that indicates this filter’s priority relative to other filters of the same type for this interface. Lower values indicate higher priorities. (The highest priority is 0.) MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.13 117369-B Rev. 00 A-83 Configuring IPX Services IPX Service Name Filter Parameters This section describes how to set all parameters shown on the IPX Service Name Filters window. Figure A-22. IPX Service Name Filters Window Parameter: Enable Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Name Filter Enable Enable | Disable Specifies whether the service name filter displayed is active on this interface. Select Enable to enable the service name filter. Select Disable to disable the service name filter. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.2 A-84 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Target Service Name Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Name Filter Default: None Options: Any valid alphanumeric server name or one containing wildcard characters or a pattern-matching regular expression. (See “Using Wildcards with SAP Filters” and “Using Pattern Matching with SAP Filters” for lists of these characters.) Function: This is the filter that you want to apply. It can specify the name of the server to which you are applying the server-level SAP filter, or it can be a filter containing a wildcard or a pattern (regular expression) to be matched. Instructions: Enter a service name or filter pattern consisting of up to 48 alphanumeric characters, optionally including wildcards or a regular expression (pattern). MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.6 Parameter: Target Service Type (hex) Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Name Filter None Any valid Novell server type number in 4-digit hexadecimal format Specifies the type of server that the filter should recognize in its criteria for allowing certain SAP broadcasts to pass to the locally attached network segment. Instructions: Enter the server type number in 4-digit hexadecimal format. Include leading 0s. For all types, enter a value of 0xFFFF. See Appendix A for a list of valid service types. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.7 117369-B Rev. 00 A-85 Configuring IPX Services Parameter: Filter Priority Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > IPX > Static/Filter Tables > Name Filter None 0 to the maximum positive integer Specifies the priority of this filter in relation to other filters of the same type. Enter a decimal value that indicates this filter’s priority relative to other filters of the same type for this interface. Lower values indicate higher priorities. (The highest priority is 0.) MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.13 Parameter: Mode Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Name Filter Outbound Outbound | Inbound | Both Specifies whether you want to apply the filter to inbound packets, outbound packets, or both. Instructions: Accept the default, Outbound, if you want to apply the filter to SAP packets advertised by the specified interface. Specify Inbound if you want to apply the filter to SAP packets coming into this interface. Specify Both if you want to filter both inbound and outbound packets. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.8 Parameter: Protocol Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Name Filter Any Any | Local | Static | SAP Applies this outbound filter only to services learned on the specified protocol when sending SAP updates. This does not apply to inbound services. Instructions: Specify the protocol on which you want to apply the filter. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.10 A-86 117369-B Rev. 00 Site Manager IPX Parameters Parameter: Action Path: Default: Options: Function: Configuration Manager > Protocols > IPX > Static/Filter Tables > Name Filter Advertise/Accept Advertise/Accept | Suppress Specifies how to process any SAP advertisement that matches the SAP filter criteria you established in the Target Service Name and Target Service Type parameters. Instructions: Select Advertise/Accept to enable the filter to allow advertisement or acceptance of services that match the filter criteria you established in the Service Name and Service Type parameters. Select Suppress to configure the IPX router to drop SAP advertisements that match the SAP filter criteria you established in the Service Name and Service Type parameters. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.9 117369-B Rev. 00 A-87 Configuring IPX Services Parameter: Cost Path: Configuration Manager > Protocols > IPX > Static/Filter Tables > Name Filter Default: 1 (for hop- or tick-based routing) Options: 1 to maximum positive integer (if tick-based routing is enabled) 1 to one less than the value specified in the Maximum Hops parameter (if hop-based routing is enabled) Function: Used only when the Action parameter is Advertise/Accept, this parameter assigns a cost for routes matching this filter. A zero cost indicates that the route’s actual cost should be used. This parameter sets the cost (number of ticks or hops) for this interface. The cost is included in subsequent SAP packets sent to other interfaces. IPX disposes of the packet when its hop count passes a value that is one less than the value of the Maximum Hops parameter. This value must be the same across the network. Instructions: Do not change the default value of this parameter unless you are an expert IPX user (for example, a Bay Networks Technical Solutions Center engineer). Changing the value of this parameter can significantly affect router performance. If you are qualified as an expert user, enter a value that yields a level of performance most appropriate for network applications supported by this router. If the filter is an inbound filter, the entered cost replaces the cost associated with the server in the SAP advertisement, and the router uses this cost in its calculations. If this is an outbound filter, the entered cost replaces the server’s cost that is advertised in SAP packets by this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.5.31.1.11 A-88 117369-B Rev. 00 Appendix B BCC show Commands for IPX Use the BCC show command to display configuration and statistical information about IPX services. See Using the Bay Command Console for information about show scripts command syntax. Sample Output The show command displays information about the router’s IPX configuration. For example, if you enter the command: bcc> show ipx rip You see this type of output: IPX RIP Interface Record Configuration Information Interface Packet Name --------E21 Configured Current Update Listen Supply Packet Packet State State Interval Mode Mode In Out Bad ---------- ------- -------- ------- ------- ------- -------- ---enabled notpres 60 enabled enabled 0 0 0 Online Help for show Commands You can display a list of available command options by entering show or show
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.2 Linearized : Yes Create Date : 1998:06:01 16:38:49 Producer : Acrobat Distiller 3.0 for Windows Creator : FrameMaker 5.5.2L11a Title : V 12.20, Configuring IPX Services Subject : Part No. 117369-B Rev. 00 Modify Date : 1998:06:01 17:05:35 Page Count : 360 Page Mode : UseOutlinesEXIF Metadata provided by EXIF.tools