Bay Networks

Worldwide Customer Service - Lifecycle Support for Adaptive Networking

Information
Service/Support
Products
Solutions
Partnerweb
Regional
Search/Sitemap
Feedback
Service & Support
Service OnlineProgramsTrainingSoftwareLibrary
 

 

 

Revision Notes for Router Software 9.00 rev 2

=============================================================================
                       SITE MANAGER COMPATIBILITY
=============================================================================
       Router Version       is managed by          Site Manager version
                                                                                    v9.00 --------------------------------------> v3.00, 3.00 Rev 1
       9.00 Rev 2 ---------------------------------> v3.00, 3.00 Rev 1
                
-----------------------------------------------------------------------------
Revision 9.00/2 corrects the following problem:
=============================================================================

CR 20681: Tools.
          In Version 9.00, Revision 1, the VME-based router boot image,
          ace.out, contains an executable file that was built with an
          incorrect pathname. This causes problems when you attempt to open
          and/or save the ace.out image file using the Image Builder in
          PC and UNIX-based Site Manager. PC Site Manager will not allow
          you to open the ace.out image using the Image Builder; UNIX Site
          Manager will allow you to open ace.out in Image Builder but will
          save the file with zero bytes.

============================ Revision 9.00/1 ================================
 
 Revision 9.00/1 corrects the following problems:
=============================================================================

CR 18201: Scripts/ATM.
          When you enter SHOW ATM, duplicate information displays.
 
CR 18214: DLSw.
          The DLSw Packaging and DLSw Protocol Prioritization
          Global parameter needs to be added to the dls.bat file. This
          parameter displays when you enter SHOW DLS BASE.

CR 18215: DLSw.
          When you enter SHOW DLS LOCAL from the Technician Interface in a
          SDLC configuration, the ID number that displays is different
          than the Id number shown in the MIB. Also, the Link Station Address
          should be converted to hexadecimal.

CR 17415: DVMRP.
          SHOW DVMRP needs a value-- ON or OFF-- to indicate the status of
          pruning. SHOW DVMRP CIRCUITS needs to include status of "advertise
          own interface". 

CR 17414: IGMP.
          Enhance display of ³SHOW IGMP CIRCUITS DISABLED² script.

CR 14864: Switched Services.
          When you enter SHOW PPP CHAP Local, a run error occurs if PPP
          is configured on a dial-up circuit.

CR 16478: IP.
          A bus error may occur in IP while aging routes if other tasks
          are accessing the route entries simultaneously.

CR 17698: IP.
          The following misleading IP warning message might be logged
          periodically:

           ³Error deleting x.x.x.x from Aging Queue-- Not Found.²

CR 16838: LNM.
          A RESYNC from an LNM station may fail following a nearest upstream
          neighbor (NAUN) change of a router's interface to the ring to be
          RESYNC'd. The failure reported from the LNM station generally
          indicates no response from the router's upstream neighbor.
          However, the failure follows that station even if another device
          becomes the routers¹ nearest upstream neighbor.

CR 18598: X.25.
          Unable to use a large window size with modulo 128. When you
          attempt to use the larger window sizes 124-127, the line becomes
          congested with RNRs while no traffic is being sent. With window
          sizes 123 and sizes less than 123, you get RNRs as the traffic
          load increases.

CR 18513: DLSw.
          A specific frame exchange between stations connected through a
          DLSw cloud can cause an incoming XID to be incorrectly transmitted
          as an outgoing TEST response from the same interface. This TEST
          response has the P/F bit set to 0, which causes the PC that
          receives it to hang. Although the PC should not hang (from the
          LLC point of view the frame is correct), the router is considered
          responsible for it since there is no reason to send such a frame.

CR 18830: APPN.
          When you enter APPN SHOW PORT, the following system message appears:
          
              MIB variable not found

CR 18945: Frame Relay Switch.
          If congestion control is activated on a HSSI or SYNC trunk, any
          frames that have the bit DE set will be changed to NONDE at egress. 

CR 16948: DLSw.
          If you have an active NetBIOS session running over a DLS switch and
          you disable the TCP base on one of the DLS routers, a bus error
          occurs, causing loss of NetBIOS traffic.

CR 18937: IPX.
          The next hop network for routes does not remain constant when 
          redundant equal cost paths between two routers exist and the 
          number of paths is greater than the maximum paths configured.
          As a result, when interfaces are disabled/enabled, some networks
          may stop advertising and clients may fail to connect to servers.

CR 18986: VINES.
          VINES may fault when aging routes.

CR 18990: IGMP.
          Several problems with IGMP scripts have been resolved.

CR 15834: ISDN_DRVR
          The munich driver failed to conform to the NET5
          specifications, as determined during the PRI ISDN layer 1
          pre-testing.

CR 19132: OSPF.
          An incorrect argument passed to ospf_submit_route may cause
          a bus error during route calculation.
        
CR 19127: OSPF.
          An Area Boundary Router (ABR) does not generate a default into a
          stub area unless the "Import Summaries" switch, which determines
          whether internal OSPF networks are summarized and flooded into a
          stub area, is set to "Yes". An ABR should generate a default
          summary into a stub area, regardless of the switch setting
          for "Import Summaries".
          
CR 18279: RIP.
          RIP allows a RIP entry to age beyond the maximum allowable timeout
          limit in the routing table instead of removing it from the table.

CR 18810: Frame Relay Switch.
          Converting from BNX Version 4.20 to BNX Version 5.0 produced errors
          when using a customer configuration file.

CR 19301: Frame Relay Switch.
          An A-Bit MIB listener parameter is required to dynamically
          convert large switching environments to A-Bit switching environment.
          wfFrSwDlcmiEntry.wfFrSwDlcmiCrossNet Listen Enable should be
          disabled. This causes the management entity on a Frame Relay
          circuit to disregard end-to-end updates.
          
CR 19439: Frame Relay Switch.
          A BNX NNI running Annex A to a Cascade switch causes repeated "Bad
          Report Type" errors, and eventually shuts down the PVCs on the NNI
          after exceeding the error threshold. 

CR 18885: DLSw.
          When you establish a local NetBIOS session, the DLSw router
          creates an LLC2 link entry for that session. As a result, a DISCp
          that is sent between the client and server to initiate session
          shutdown causes the router to generate a DMf (0x1f) on behalf of
          the server.

CR 19450: MCT1E1.
          The TI script file hardware.bat does not support the new
          MCE1-II Respin link module IDs.

CR 19414: BGP.
          When booting a BGP peer, it is possible that after the router
          boots, it will receive messages indicating that the BGP port is
          unreachable and therefore never establish a peer relationship.
          This condition is known to occur in large routing environments.

CR 19095: LB.
          A router that has slots with different memory sizes may end up
          with different bridge table sizes on different slots. As a
          result, packets that should be forwarded instead get flooded,
          causing decreased performance.

CR 19543: Source Routing Bridge.
          In a Group Mode configuration within Frame Relay, the Hub router
          may transmit Specifically Routed Frames (SRFs) out the incorrect
          DLCI intermittently. This condition occurs on a Hub router within a
          nonfully meshed environment.

CR 19603: IPX.
          A watchdog occurred on a FRE1 while attempting to run numerous
         (1000) lost router algorithm processes.

CR 18574: Source Routing Bridge.
          Under certain conditions, a Frame Relay interface configured for
          Transparent Bridge, Source Route Bridge, and IP will interpret an
          incoming frame incorrectly as a Source Routed 8101 type frame.
          This causes a buffer to be incorrectly formed and passed within
          the router, thereby producing a parity violation on the sending
          FRE2 or a tag violation on a FRE1. This condition occurs when 
          receiving a small Ethernet type frames (0x27 bytes) after
          processing several Source Routing Bridge (SRB) frames.

CR 19563: Source Routing Bridge.
          Upgrading a router to Version 8.11 causes other routers on the
          FDDI ring running Version 7.80 to panic on the FDDI slot
          configured for Source Routing Bridge. As a result, the router
          running Version 8.11 sees a message indicating bad frame
          length on transmit request messages in the log for SRB Token Ring
          interfaces.

CR 19776: DataPath.
          Selecting Reset Active from Site Manager causes a bus fault to
          occur in DP if the primary interface of a circuit becomes
          inactive.

CR 19791: DataPath.
          Source Routing Bridge is not configured properly on standby Token
          Ring redundant interfaces. Token Ring interfaces require that you
          configure the first active interface for a circuit, but not for
          standby circuits.  



CR 19559: VINES.
          Bouncing a VINES interface may result in panics, bus errors,
          and/or orphan buffers in the router.

CR 19780: OSPF.
          An OSPF adjacency may fail to form because of a sequence number
          mismatch if the master has no LSA¹s to send in its Database
          Description Packet.

CR 18278: IPX.
          Server names are not identical to the name contained in learned
          packet. Some devices use all 48 characters in the server name
          field rather than stopping at the null character. This causes 
          connectivity problems.
   
CR 19199: IPX.
          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. 

          This occurs on outbound only and occurs with SAP name and network 
          filters.

CR 19773: IPX.
          The Service age is not set to zero after SAP updates are received.
          This causes the services to age out the IPX Service Table and then
          be relearned.
          
CR 19846: AppleTalk.
          A bus fault occurs when a slot receives a certain RTMP
          packet on an interface configured with AppleTalk.

CR None:  During the execution of power-up diagnostics for net modules for
          an ASN router, the instruction cache fails to maintain
          coherency during the beginning stages of the net module execution. 

          Because all net module diagnostics load to the same address
          space, the instruction cache must be flushed before the CPU jumps
          to the newly loaded code. If the instruction cache is not flushed,
          it can ³hit² when fetching an instruction for the newly loaded
          image, resulting in the CPU fetching ³stale² data; that is, 
          instructions that are left behind in the cache from the previous
          module diagnostic image.



Feedback | Service Search | ERC

Copyright © Bay Networks,Inc., 1997. All rights reserved.

/tr>