 |
|||||||||||||||||||||||||||||
     |
|||||||||||||||||||||||||||||
Technical Response Center Release Notes Bay Networks makes every effort to provide all documentation for its products online. Printed copies of many books are also available to order. The release notes are listed by product, date and technology. They can be accessed from the Library page.
Read Me First Router Software 9.00 and Site Manager 3.00This document supplements the Release Notes for Router Software Version 9.00, Release Notes for Site Manager Software Version 3.00, and Known Anomalies: Router Software Version 9.00 and Site Manager Version 3.00. It contains information about the following:
Known Anomalies in Version 9.00 These known anomalies supplement those included in Known Anomalies: Router Software Version 9.00 and Site Manager Version 3.00. Anomaly: Outbound SAP filter cost parameter does not work properly Number: 19199 Description: If you configure an outbound SAP network or name level filter to advertise a particular service or group of services with a specific cost (hop), the cost defined will be advertised in all services of a particular type; that is, 0x0004, if the filter matches one of the services in this particular type. For example, if one type 0x0004 service matches the filter with a cost of 10, all type 0x0004 services will be advertised with a cost of 10 even though they do not match the filter. Workaround: A possible workaround is to configure another outbound SAP filter with a lower priority to advertise services of a particular type or all types with a cost of 0. SAP inbound filters may also be used. Anomaly: New IPX MIB not easily seen using Quick Get facility Number: 19139 Description: When you select the Quick Get facility from the Statistics Manager, Site Manager displays the former IPX MIB followed by the new IPX MIB. If you do not scroll down the MIB beyond the former IPX MIB, you might be led to believe that you cannot access the new IPX MIB through the Quick Get facility and the Screen Builder facility. Anomaly: Configuring trap exceptions in Site Manager causes GPF fault Number: 19236 Description: When you enter ProtocolsÔIP ÔSNMPÔTrap ConfigurationÔExceptions, then add the exceptions and press OK, Site Manager attempts to configure trap exceptions on the Windows version but generates a GPF fault instead. This condition applies only to the PC platform. The UNIX platform remains unaffected. Workaround: From the Technician Interface, enter the MIB variable wfSnmpTrapEventEntry. A list of MIB variables displays. Add an exception configuration by entering the following command: setwfSnmpTrapEvent Entry.2.<entity code>.<event code> <always/never traps>;commit where:
Anomaly: Enhancement to give control over who initiates the call for X.25 PTOP Number: 14609 Description: Bay Networks has enhanced the X.25 PTOP software to enable you to configure a X.25 PTOP link to determine who initiates the call request on a Point-to-Point link, regardless of the router’s X.121 address. You can configure a PTOP link by setting wfX25ServiceEntry.wfX25ServicePtopCallRequest to one of the following interface options:
Anomaly: Protocol Prioritization does not work over an ISDN PRI circuit Number: 19096 Description: Protocol Prioritization/Outbound filtering does not work properly (filters fail to increment) when used over ISDN PRI demand circuits on MCT1/E1 cards. Similar filters that operate over ISDN BRI and Switched Services circuits using modems/TA (COM ports) work properly, as do non-PRI circuits configured on MCT1/E1 cards. Anomaly: ANH router with X10 will not work with Optivity D and A if the Ethernet is not configured as circuit 1 Number: 18808 Description: An ANH router with X10 will not work with Optivity D and A if you have not configured the Ethernet interface that supports the X10 as the first circuit. Anomaly: OSPF does not send default summary into stub area when Import Summaries is set to No Number: 19127 Description: An Area Boundary Router (ABR) should generate a default summary into a stub area (if it has a default) regardless of whether you have set the Import Summaries switch for stub areas to Yes or No. However, an ABR does not generate a default summary into a stub area unless you set the Import Summaries switch to Yes. Workaround: Set the Import Summaries switch for stub areas to Yes. Interface Redundancy Effects on MAC Address Usage When you configure interface redundancy, the active interface uses the following a MAC address in hexadecimal radix: 0x2000 A2 xx xxxx &127 0x20 indicates that the address is locally administered by Bay Networks &127 00A2 identifies the Bay Networks OUI &127 xx xxxx identifies the unique router identification The active interface in an interface redundancy group uses the MAC address for all traffic, including Breath of Life (BOFL). The MAC address switches among interfaces in the interface redundancy group so that it always represents the active interface. The MAC address affects network layer protocol adjacent host setups on adjacent routers. For example, if you have adjacent routers and the IP adjacent host is defined with its next hop being the active interface in an interface redundancy group, the adjacent host MAC address must be the active MAC address, that is 0x2000 A2 xx xxxx You can find the complete active MAC address in the interface MIB (Ethernet, Token Ring, FDDI) of the router on which interface redundancy is configured. For example, if you are configuring Ethernet, you can find the active MAC address in the Ethernet MIB by entering the following command from the Technician Interface: get wfCSMACDEntry.wfCSMACDMadr.* Among the entries displayed in the MIB is the MAC address 0x2000 A2xx xxxx, which is used for interface redundancy. If you configured more than one interface redundancy group on the same router, you will see more than one entry with the same MAC address. This is not a problem because the two redundancy groups are in different subnets. Configuring the NetBIOS Query Cache When you configure the NetBIOS Query Cache parameter, which appears in the Source Route Bridge Global Parameters window, you can now globally enable or disable the ability of bridges to cache the NetBIOS source name, MAC address, and RIF path associated with each NetBIOS name query, add name query, and add group name query handled by the node. To edit the Source Route Bridge global parameters using Site Manager, select Protocols ÔSource Routing ÔGlobal from the Configuration Manager window. Using the install.bat Script with Network Management Tools Referring to establishing an initial IP interface with the router, the introduction to the install.bat script states: "You perform this procedure so that the router can communicate with the Site Manager workstation." Actually, you do not have to use Site Manager. The IP connection established through install.bat lets you configure and manage a router through any SNMP-compliant network management system. Version 9.00 provides Unnumbered RIP support. Unnumbered RIP operates in a manner similar to RIP, with one notable exception. Unlike RIP, Unnumbered RIP is a numberless protocol that provides a convenient and economical method to assign IPX network numbers. With Unnumbered RIP, you are no longer required to assign an IPX network number to a WAN link using the IPXWAN2 protocol; the router software negotiates between the entities and assigns the IPX network numbers for you. Configuration Message Enhancement Due to a parameter name change, the following IPX configuration error message is incorrect: The Circuit Type must have at least 1 item selected if IPXWAN is enabled The message should now read: The Negotiated Protocols field must have at least 1 item selected if IPXWAN is enabled IPX Accept and Deliver Parameters In the Release Notes for Router Software Version 9.00, in the subsection entitled "IPX Enhancements," we included incorrect information about configuring IPX NetBIOS Accept and Deliver parameters when upgrading to Router Software Version 9.00. The IPX configurations from previous releases are converted properly. Guidelines for Working with Version 9.00 Version 9.00 is generally the equivalent of Version 8.11 fix 4, with a few notable exceptions. The fixes come from Clarify Reports (CRs) sent to the Sustaining Engineering department. We will incorporate all fixes into Version 9.00 fix 1 as soon as it becomes available. Table 1 shows the CRs that we have identified and resolved in the Version 8.11 fix 4 software integration. We have not resolved these CRs in Router Software Version 9.00. Apart from these exceptions, Version 8.11 fix 4 and Version 9.00 contain the same fixes.
Copyright © 1988–1995 Bay Networks, Inc. All rights reserved. Printed in the USA. August 1995. 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. 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. Notice for All Other Executive Agencies 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. Trademarks of Bay Networks, Inc. ACE, AFN, BCN, BLN, BN, CN, FRE, LN, Optivity, SynOptics, SynOptics Communications, Wellfleet and the Wellfleet logo are registered trademarks and AN, ANH, ASN, BaySIS, BCNX, BLNX, BNX, EZ Internetwork, EZ LAN, FN, PhonePlus, PPX, Quick2Config, RouterMan, SPEX, Bay Networks, Bay Networks Press, the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks, Inc. Third-Party Trademarks All other trademarks and registered trademarks are the property of their respective owners. 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). Bay Networks Software License Note: This is Bay Networks basic license document. In the absence of a software license agreement specifying varying terms, this license — or the license included with the particular product — shall govern licensee’s use of Bay Networks software. This Software License shall govern the licensing of all software provided to licensee by Bay Networks ("Software"). Bay Networks will provide licensee with Software in machine-readable form and related documentation ("Documentation"). The Software provided under this license is proprietary to Bay Networks and to third parties from whom Bay Networks has acquired license rights. Bay Networks will not grant any Software license whatsoever, either explicitly or implicitly, except by acceptance of an order for either Software or for a Bay Networks product ("Equipment") that is packaged with Software. Each such license is subject to the following restrictions: 1. Upon delivery of the Software, Bay Networks grants to licensee a personal, nontransferable, nonexclusive license to use the Software with the Equipment with which or for which it was originally acquired, including use at any of licensee’s facilities to which the Equipment may be transferred, for the useful life of the Equipment unless earlier terminated by default or cancellation. Use of the Software shall be limited to such Equipment and to such facility. Software which is licensed for use on hardware not offered by Bay Networks is not subject to restricted use on any Equipment, however, unless otherwise specified on the Documentation, each licensed copy of such Software may only be installed on one hardware item at any time. 2. Licensee may use the Software with backup Equipment only if the Equipment with which or for which it was acquired is inoperative. 3. Licensee may make a single copy of the Software (but not firmware) for safekeeping (archives) or backup purposes. 4. Licensee may modify Software (but not firmware), or combine it with other software, subject to the provision that those portions of the resulting software which incorporate Software are subject to the restrictions of this license. Licensee shall not make the resulting software available for use by any third party. 5. Neither title nor ownership to Software passes to licensee. 6. Licensee shall not provide, or otherwise make available, any Software, in whole or in part, in any form, to any third party. Third parties do not include consultants, subcontractors, or agents of licensee who have licensee’s permission to use the Software at licensee’s facility, and who have agreed in writing to use the Software only in accordance with the restrictions of this license. 7. Third-party owners from whom Bay Networks has acquired license rights to software that is incorporated into Bay Networks products shall have the right to enforce the provisions of this license against licensee. 8. Licensee shall not remove or obscure any copyright, patent, trademark, trade secret, or similar intellectual property or restricted rights notice within or affixed to any Software and shall reproduce and affix such notice on any backup copy of Software or copies of software resulting from modification or combination performed by licensee as permitted by this license. 9. Licensee shall not reverse assemble, reverse compile, or in any way reverse engineer the Software. [Note: For licensees in the European Community, the Software Directive dated 14 May 1991 (as may be amended from time to time) shall apply for interoperability purposes. Licensee must notify Bay Networks in writing of any such intended examination of the Software and Bay Networks may provide review and assistance.] 10. Notwithstanding any foregoing terms to the contrary, if licensee licenses the Bay Networks product "Site Manager," licensee may duplicate and install the Site Manager product as specified in the Documentation. This right is granted solely as necessary for use of Site Manager on hardware installed with licensee’s network. 11. This license will automatically terminate upon improper handling of Software, such as by disclosure, or Bay Networks may terminate this license by written notice to licensee if licensee fails to comply with any of the material provisions of this license and fails to cure such failure within thirty (30) days after the receipt of written notice from Bay Networks. Upon termination of this license, licensee shall discontinue all use of the Software and return the Software and Documentation, including all copies, to Bay Networks. 12. Licensee’s obligations under this license shall survive expiration or termination of this license.
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
|||||||||||||||||||||||||||||
