Revision Notes for Router Software v 7.80 rev 2

Date: 10/12/94
Subj: Revision Notes for 7.80 fix 2

=========================================================================
                         SITE MANAGER COMPATIBILITY
=========================================================================

     Router version     is managed by        Site Manager version

      v7.80                                  1.80, 2.00
       7.80 fix 1, 2                         1.80, 2.00
======================== Version 7.80 fix 2  =============================

The image for FRE hardware is:                 1472625 Oct 11 13:02 boot.exe 
The image for VME & AFN Floppy hardware is:    1498397 Oct 11 13:10 ace.out 
The image for AN hardware is:                  1291709 Oct 11 13:16 boot.exe 
The image for IN & AFN Flash hardware is       1370974 Oct 11 13:19 boot.exe 
_____________________________________________________________________________

Revision fix/7.80/2 corrects the following problems:
=============================================================================

CR  None: Tag violation slot resets can occur when runt (< 14 byte) frames
          are received on HSSI interfaces.

CR 10047: Access Node Token ring interface does not receive a Source
          Route Bridge SRF, ARE, or SRE with a RIF of size greater than
          14 bytes.

CR 10076: Dial on demand using X21 terminal adaptors, ISDN, V25bis
          signalling on 44 pins sync interface does not work. Sync
          interface cannot see the modem, reports CTS failure. Incoming
          calls never transit out of v25bis signalling to data mode, all
          LCP configuration frames are interpreted as illegal v25bis
          commands. Outgoing calls never transit from modem signalling
          to LCP configuration phase.

CR  9453: When about 300 external networks become unreachable and corresponding
          ASE LSAs are flooded with Max Age throughout OSPF AS, OSPF on some
          routers (depending upon configuration) may generate Hogs Bufs errors.

CR 10379: The 'show bgp peers' command doesn't show configured values for
          Hold and Keep Alive timers.

CR 10380: When exporting routes via BGP with the BGP Export Route Filter 
          InterAsMetric set to None the receiving router installs a value
          of 0 instead of nothing.

CR  7221: IP and OSPF remain up when FDDI interface is disconnected.

CR 10009: After the primary line is disabeled, initialization of the 
          backup dial circuit can cause a panic. The PRIMARY line was
          configured as STANDARD.

======================== version 7.80 fix 1 =============================
The image for FRE hardware is 1472061 Sep 28 14:39 boot.exe 
The image for VME hardware is 1497508 Sep 28 14:47 ace.out 
The image for AN  hardware is 1290671 Sep 28 14:52 boot.exe 
The image for IN  hardware is 1370273 Sep 28 14:55 boot.exe 
=========================================================================

CR  7188: Poor performance (Lack of resource errors dropping packets on
          ethernet interfaces) in large (1000 nets, 800 saps) IPX networks.

CR  9968: In particular configuration where certain packets are received
          on an ethernet interface in a specific order VINES packets are
          lost (due to being delivered to wrong ISAP) causing excessive
          delays in file transfers.

CR 10273: If there is a default route configured and BGP-3 export filters
          as in:

          IGNORE default range from ANY protocol from ANY BGP AS from
          specific Peer,
          PROPAGATE default route (0.0.0.0+255.255.255.255) from ANY
          protocol and any AS for specific Peer,
          PROPAGATE class B natural network rangefor everything.

          Watchdog expiration slot resets can occur in routine
          'ip_ck_export_rules' routine when BGP-3 processes default route.

CR 9197: IP Host is not relearned after an adjacent host entry for that host
         is dynamically disabled. Also, if this host happens to be a router,
         then any networks beyond that router become unreachable.

CR 9885: When IP data is to be forwarded to a network which is not directly
         connected to the local router and is available via a non-peer
         BGP-3 speaker, the router fails to ARP for the next hop media
         address of the non peer BGP-3 speaker. 

CR 9739: Spanning Tree does not forward packets immediately after changing a
         previously blocked port to forwarding when convergence is completed.

CR 9466: The MIB variable 'wfIpInterfaceForwDatagrams' decreases instead 
         of increasing on OSPF interfaces.

CR 7711: 'PANIC in map_rem.c at line 60' error can occur when dial backup
         circuit is changed from primary to normal.

CR 9960: Multiline circuits do not recover properly when there are more than
         2 lines per circuit and one of the lines goes down.

CR 9761: When packets are fragmented by X.25 using the M bit, there is a
         forced 200ms delay between fragments (even when the window is
         open) providing that no inbound packets are seen. This causes a
         sub-optimal use of the transmit window which is especially
         noticable over a satellite link.

CR 9225: Bridge traffic doesn't properly switch back to the primary line
   8743: from a dial backup one. The router may stop learning and taking
         incoming traffic from the sync port. Also the router may loop
         back broadcast packets in the sync port.

CR 9467: The Threshold feature configured under Global Protocols which
         allows messages to be put in the log file when certain statistics
         reach predefined values, displays the threshold event in the log
         with asn.1 notation (such as 1.3.6.1.4.1.18.4.3.1.1.28.2.1)
         instead of the variable that it represents (wfCSMACDErr).

         This functionality has been provided by a new configuration option
         in Statistical Threshold and Alarms (STA). The administrator can
         now configure the threshold Object name portion of the MIB
         variable to be a user defined string.

         For example, if the ThresholdLabel is not configured the logged
         event looks like;

         'Object 1.3.6.1.4.1.18.3.4.5.1.36.2.1 with value = 233 units/sec
         is > low threshold.'

         If the ThresholdLabel is configured the logged event looks like;

         'Object wfSyncTxOctets.2.1 with value = 235 units/sec is >
         low threshold.'

         To configure from TI;

         s wfStaThresholdEntry.wfStaThresholdLabel.14.1.3.6.1.4.1.18.3.4.5.1.36.2.1
         "wfSyncTxOctets.2.1".

         With SiteManager version 2.0 or greater it can be configured via
         protocols->global->threshold>->wfswconfig->wfline->wfSyncTable->
         wfSyncRxoctes, bring up the window to add the port and circuit
         number to see the Threshold label screen.

CR 9978: Force takedown does not work for dial demand and takedown does
         not work for dial backup.

CR 9708: After configuring an ospf import route filter to ignore all type
         1 externals, the type 1 externals do not get filtered.

CR 9842: With LNM enabled on a Token Ring interface receiving a lot of
         traffic continuously 'scheduler exited due to orphaned buffer'
         faults can occur.

CR 9839: Setting up Bridge Traffic Filters to drop IP broadcast traffic
         while bridging and running IP 'Not Forwarding' mode does not
         work. The Traffic Filters are not applied.

CR 9215: The MIB variable wfOspfIfEntry.wfOspfMtuSize added in version
         fix/7.71/1 is supposed to control the MTU size for OSPF packets
         sent over this interface.  When set to a value of 2, it should
         send packets no larger than the IP MTU size for Ethernet.  This
         restriction is not working and much larger packets are being sent.

CR 9690: The External Route Tag Field within an OSPF AS External Link
         State Advertisement is inconsistant when the ASE is generated
         from a 7 series router.  The use of this field, although not
         documented in the OSPF specification to this effect, in the 5
         series is to list the IP address of the gateway from which an ASE
         Type 2 was originally learned via RIP (or other protocol).  The 5
         series does this consistently and has proved to be an invaluable
         troubleshooting tool when debugging a large OSPF network where
         there are multiple routers advertising the same ASE Type 2s.  The
         7 series on the other hand, will use the field in the same way
         initially, but seems to lose track of what data is actually being
         plugged into the field if the ASE Type 2 is refreshed for any
         reason.  An example of when this might happen is if an ASE Type
         2 is aged, flushed and then relearned and refreshed again.  The
         External Route Tag field may look fine in an advertisement prior
         to and when it is actually  flushed, but when a new instance is
         generated, bogus data may appear in this field.

CR 9887: During the learning of BGP-3 routes from 2 BGP-3 peers (both
         advertising the same routes) router may generate Hogs Bufs errors
         in the BGP-3 module leading to PANIC's from other processes
         trying to get buffers.

CR 8044: X25 has 6 point to point connections to 6 differnet destinations.
         If Connection ID 1 and 2 are used to set up call from A to
         destination B.  Then you cannot use connection ID 1 and 2 to
         set up a call from A to Destination C.  From a LAN analyzer once
         A connects to B connection ID 1 and 2 are being Used.  IF A then
         tries to connect C, A will report that it already has a call on
         connection ID 1 and 2, dropping the connection from C. This
         contradicts The Wellfleet Manual which states that Different
         destinations can use the same connection ID.

CR 9477: Learning Bridge sometimes PANICs during momentary period of all
         packet buffers on a slot being in use.

CR 9330: Booting the router with configuration that contains import and
         export route filters will FAULT continously with 'Watchdog
         expired, service terminating' message. This problem was introduced
         at revision fix/7.71.4.

CR none: IPX NetBios static routes may now be used to direct a NetBios
         propagation packet (type 20) through a network.  This done by
         setting a NetBios static route filter for a destination server,
         and setting wfIpxBaseNovellCertificationConformance to disable (2).
         This MIB attribute must be set to 2 in all routers in the network
         for this feature to work.  This also requires all NetBios
         propagation packets to be sent from a client with the destination
         network as zero, unless this packet will pass a static route
         filter in that router.  (Packets are tested against the static
         route filters before the destination is checked.  This allows
         accepting packets that may not have a destination network of
         zero, and will allow for redirecting the packet.)

CR None: The configuration of IPX NetBios Static Routes has been improved
         to allow the use of partial NetBios server names for static
         routes. This partial name will act as a wildcard.  Any NetBios
         packet that matches this partial name will be sent to the static
         route. The MIB attribute 'wfIpxNetBiosStaticRouteEntry' may now
         contain names of less than 16 characters. When a NetBios packet
         is received, it is compared to this static route name.  The
         comparison is now done by the length of the static route name.
         If the static route name is 5 characters, the FIRST 5 characters
         of the NetBios name in the packet is compared to the static route.
         This provides wildcard like name matching on the ending portion
         of the NetBios server name.

   Note: A NetBios static route of length zero will match ALL packets.

CR 9301: The get wfKernelEntry.*. command uses excessive amount of
         CPU time.

         Performance improvements have been made to the way that process
         ids are searched. Before this revision (fix/7.71/7), an ACE
         booted with the default config file would use 400ms to complete
         the get wfKernelEntry.*. command. The same setup now uses
         only 20ms.

CR 9468: When running Translating Bridge (TR to Ethernet) in the presence
         of an older application, the manner in which we cache (backwards)
         and then include a RIF when translating a packet from Ethernet
         to Token Ring may cause an application failure.

CR 9553: Router token interface configured for IP Host Only/Source Route
         Bridge Local ARP request (no rif field) for different IP address
         than router causes wfBrSrInterfaceDropInvalidRings to increment.

CR 9185: NetBIOS cache incorrectly stores the RIF from a Name Recognized
         frame causing all subsequent packets to be dropped due to a
         non-optimal RIF path.

CR 9716: The TI 'save log' command has been improved to record the load
         map and image stamp in the log before saving.

CR 9646: When two ABRs bordering the same areas and all members of an area
         summary range disappear on one ABR, the configured area summary
         range is used for forwarding traffic to the other ABR. (this is
         correct). But when the local interfaces come back on the first
         ABR, the summary entry is still used for forwarding when it's
         not supposed to.

CR 9428: If three routers (a,b,c) are connected together in the config-
         uration (a--b--c) where (a) is a AS boundary router, (b) is a
         area border router and (c) is a router connected to the area border
         router, a problem occurs when we sever the connection between
         routers (b) and (c).  If we look at the ip routing table on
         router (c), we will still see an entry for the AS external that
         is advertised by router (a). This problem will not occur if all
         of the routers are in the backbone. Also the problem will not
         occur if another router is attached to router (c).

CR None: Decnet router exhibits poor performance (sometimes including
         watchdog PANICs upon circuits going down/up) in large topology
         of many (> 15) areas.

CR 9482: Router running OSPF as an AS Boundary Router may generate
         'PANIC: exception vector 2 - Bus error' in routine
         'add_network_route' when it shares advertisement of a common
         AS External Route with an adjacent neighbor.

CR 9866: IP router drops TCP packets when IP option padding bytes are
         non-zero.

CR 9849: IP proxy arp does not respond to different networks as it did
         in 5 series platform.

   Note: The fix for this problem was to add a new attribute
         wfArpBaseNonlocalDest into ARP_BASE_GROUP mib record. If
         wfArpBaseNonlocalSDest is set to DROP, the arp request will
         be dropped if the source and destination are from different
         networks/subnetworks; If wfArpBaseNonlocalSDest is set to
         ACCEPT, the arp request will be processed. The default option
         is DROP.

CR 9197: IP Host is not relearned after an adjacent host entry for that host
         is dynamically disabled. Also, if this host happens to be a router,
         then any networks beyond that router become unreachable.

CR 9029: IPX router configured for Tick based routing responds to getnearest
         server requests with a remote file server even though there is a
         local file server of the same type on the network.

Feedback | Service Search | ERC

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