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 v7.80 rev 8

Date: 3/29/95
Subj: Revision Notes for 7.80 fix 8

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

     Router version     is managed by        Site Manager version

      v7.80                                  1.80, 2.00
       7.80 fix 1, 2, 3, 4, 5, 6, 7, 8       1.80, 2.00, 2.00 fix 1, 2

========================= Version 7.80 fix 8  =============================
The image for FRE hardware is:               1479542 May 22 16:37 boot.exe 
The image for VME & AFN Floppy hardware is:  1509621 May 22 17:10 ace.out 
The image for AN hardware is:                1299525 May 22 16:44 boot.exe 
The image for IN & AFN Flash hardware is:    1374224 May 22 16:57 boot.exe 
___________________________________________________________________________

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

CR  None: IPX.
          IPX router bus errors upon receipt of directed broadcast packets
          that were not destined for this router.

          This problem was introduced as a side effect of the repair
          documented below in fix/7.80/7 in CR 12355.

========================= Version 7.80 fix 7  =============================
The image for FRE hardware is:               1479677 Mar 28 17:11 boot.exe 
The image for VME & AFN Floppy hardware is:  1509777 Mar 28 17:32 ace.out 
The image for AN hardware is:                1300400 Mar 28 17:16 boot.exe 
The image for IN & AFN Flash hardware is:    1374406 Mar 28 17:24 boot.exe 
___________________________________________________________________________

CR 13198: X.25.
          When configuring an X25 Closed User Group with a value of 0 the
          router does not create a facility in the Call Request Packet for
          the CUG. Any other value from 1 - 999 will create this facility.
          Site Manager says that all values from 0 - 999 are valid.

CR 13461: IP.
          Slot resets infrequently occur with an 'Panic at gid_rem.c
          line 59' error in the log. The operating system has been improved
          so that the panic above will no longer occur due to a second
          attempt to remove a process.

CR 12776: DLSw.
          Disabling LLc2 on a router can cause Panic Vector 2 Bus Errors
          if Sap 0 is configured.

CR 13286: IP.
          IP packets with bad headers (fails checksum) where the header's
          total length field contains a large value (larger than the size
          of a buffer), can cause Tag Violation slot resets.

CR 12355: IPX.
          IN particular circumstances (misconfiguration in an IPX network)
          IPX Directed broadcast(rip/sap) gets routed out same interface
          it was received on.

CR 13363: OSI.
          When a Ping is issued from TI for OSI the field only allows you
          to enter 38 Hex digits for the value of the address.  The problem
          is that you should be able to enter the Selector field with the
          address which would be a total of 40 Hex digits.

CR 13297: DLSw.
          The receipt of a CANUREACH with different source and destination
          SAP's where the destination SAP is one defined in the DLS SAP
          table but the source one is not, will cause a BUS error.  If both
          SAP's are  defined in the SAP table the problem doesn't happen.
          There is also no problem if neither is defined in the SAP table.

CR 13119: IP.
          Snap Encapsulated 802.3 ARP requests incorrectly have the Hardware
          Type Field set to 1 (Ethernet).  This field should be set to 
          6 (IEEE 802 Network).  It seems that certain End-stations, IBM
          RS6000s for one, will not respond to our SNAP Encapsulated ARP
          Requests over Enet when the endstation is configured for an 802.3
          Network Interface.  They will only respond if this field is set to 6.

CR 12886: IPX.
          Adding a SAP filter to PPP interface that is going down/up can
          cause Tag Violation slot resets.

CR  None: IPX.
          IPX router intermittently stops forwarding traffic for a
          particular connection. This most typically occurs in a source
          routed environment with end-station support configured.
          
CR 13210: Switched Services.
          Hold down timer for dial backup does not work. If it is configured
          the primary line may never come up on boot.

CR 13299: MIB.
          The Mib tree does not support the case of two instances of the
          same object, when one instance is a prefix of the other one
          (variable length instances) the Mib will insert both of them in
          the tree, but the longer one is then inaccessible and if one
          deletes the shorter instances then both instances will be deleted
          (creating a memory leak).

CR  None: System:
          TI 'save config' command fails on large config files even though
          free memory available on the slot running TI is more than twice
          the size of the config file. When the save fails, although an
          informative error is recorded in the system log, NO error is
          displayed to the TI session.

    Note: The configuration save module now requires much less memory to
          save the file to flash but it is important to note that the
          memory used comes from a single segment which must be smaller
          then the value recorded in the slot's MIB attribute
          wfKernelMemoryMaxSegFree.
         
          If the config save does fail for lack of a single memory segment
          large enough there will now be an error displayed to the TI 
          session like; 'Config. file retrieval error.'

CR 13036: DLSw.
          When an LLC token ring interface gets congested and starts sending
          RNRs, the session gets stuck in 'enter busy' state and never gets
          'exit busy'. The configuration is dual switch, two OS/2
          workstations are used to establish an LU-LU connection.

CR  6432: System.
          Network packets normally routed (if configured) are momentarily
          bridged while routing sub-system (IP, IPX, AppleTalk...) is being
          restarted. The packets are bridged permanently if the routing 
          sub-system is configured but disabled. This behavior as designed
          in the series 7 and 8 architecture has created some rather
          pernicious traffic conditions in looped IPX topologies as an 
          example.

          This enhancement changes the router's behavior as described in
          the chart below which makes distinctions between a routing
          sub-system that is operating, configured but disabled, and
          deleted.

          SITUATION                  ACTION            WHY
  
       1. Box up  -  protocol        Drop protocol.    The way 5 series
                     disabled.                         platform works.

       2. Boot with  protocol        Drop protocol.    The way 5 series
                     disabled.                         platform works.

       3. Box up  -  protocol        Drop protocol.    Stop routing loops.
                     fails.         

       4. Box up  -  protocol        Bridge protocol.  Protocol no longer
                     deleted.                          registered should in a
                                                       dynamic system act as 
                                                       if never there.

       5. Box up  - protocol added   Drop protocol.    Similar to #2.
                    but disabled.

       6. Box up  - protocol         Route protocol.   Expected.  
                    enabled.

          Prior to this enhancement #1 thru #5 would bridge the protocol.

CR 12751: IPX.
          With a looped environment and number of paths greater than 1,
          IPX never loses routes that should be aged out.

CR 12916: PPP.
          Slots running IPX router can panic when changing IPX network
          address on a PPP interface.

CR 13057: IP.
          Slot resets with Tag violations can occur on receipt of 
          re-ordered IP fragments when IP header of the first fragment
          exceeds 20 bytes.

========================= Version 7.80 fix 6  =============================

The image for FRE hardware is:               1472596 Feb 24 12:33 boot.exe 
The image for VME & AFN Floppy hardware is:  1501295 Feb 24 12:57 ace.out 
The image for AN hardware is:                1292422 Feb 24 12:40 boot.exe 
The image for IN & AFN Flash hardware is:    1368709 Feb 24 12:49 boot.exe 
___________________________________________________________________________

CR 13179: Vines.
          Vines router tends to PANIC during momentary period of all packet
          buffers on a slot being in use.

CR 12807: Bridge.
          Bridge SNAP filters do not work over PPP or Frame Relay interfaces.

CR 13166: Vines.
          Under particular circumstances servers that use a neighbor as a
          gateway can become unreachable from behind a BNET router.

CR 13000: Source Route Bridge.
          Source Route Traffic Filter to Forward to Circuit Group only,
          also forwards packets to IP Encaps subsystem.

CR 13092: Sync.
          The 7.80 install.bat creates an erroneous line definition for
          Sync connection.

CR 13131: System.
          When the operating system's mechanism for single threading access
          to a shared resource is utilized and one process waits behind 
          another, a 32 byte memory block is lost. Over time, this memory
          leak that does not show up in the wfKernelEntry stats other than
          a lack of free memory, can cause 'out of memory' slot resets.

CR 10670: OSPF.
          OSPF adjacencies do not form when using the dial backup line 
          after the primary line is disabled.

CR 11762: DLSw.
          A particular Netbios SQL application fails when going through
          WF DLSw because we only allow for one connection per data link.
          This application needs the client and server to have 2 sessions
          opened, for 2 different Netbios names, at the same time. The first
          session is opened OK but when the second tries to come up the WF
          routers will terminate the data link (DISC at both ends). 

CR 12905: IP.
          Proxy ARP would stop responding to ARP request for reachable
          hosts located across sync lines, after a specific sequence of
          events. If the sync line connected to the remote router is brought
          down and a minute later up again, the first time everything will
          still work. The line is then dropped again, but this time the ARP
          entry for the PC in the remote site is removed from the station
          in the central site. When the line is put back the router will
          no longer respond to the ARP requests for the remote PC arriving
          at the port with proxy ARP enabled. Routing and ARP tables look
          OK at all times. Entering a manual ARP entry for the PC in the
          central station or bouncing IP in the router solves the problem.

CR 13021: SNMP.
          SNMP Get Request (45 Objects) from SunNet Mgr fails with 
          Error - Get Request Too Big. It used to work in 7.71 fix 8 and it
          fails with 7.80 fix 5 and up.

CR 12671: Vines.
          Running Vines with FRP enabled over sync lines with one side 7
          series and the other 8.10 can cause slot resets (parity errors)
          in the 7 series router.

CR 12895: Vines.
          The Vines client program SEND.EXE does not work on serverless 
          segments.

CR 10946: IP.
          An ip circuit configured dynamically on a demand circuit will not
          transition to the UP state until the router is rebooted.

CR 12687: LNM.
          In the response to a Request Bridge Status in LNM the router
          assigns the MAC address of the ring being queried to the Internal
          LAN ID. The MAC address should be the pseudo MAC address assigned
          by the user. This causes confusion on the management workstation
          and reports the wrong ring speed for the ring that the 
          workstation is connected.

CR 11623: LNM.
          When the Token Ring MAC address and the LNM interface MAC address
          have a zero in the last digit then we cannot link to the 
          Wellfleet from the IBM_LNM station.

CR 12830: IP.
          IP Router responds to a UDP echo request with the same DST and
          SRC ports as the requesting packet.

CR 12532: DLSw.
          When DLSw and LNM are both configured on the same slot either
          may fail to operate.

CR 12908: LNM.
          PANIC in mib_ent.c at line 1041 can occur after disabling LNM
          Interface.

CR 11719: Source Route Bridge.
          Running NetBIOS Caching may cause exception vector panic in
          sr_nb_process_are as a result of RIF entries being aged while
          the same RIF entries are being relearned.

CR 12855: SNMP.
          Watchdog expiration slot resets can occur if router receives an
          SNMP packet containing a zero len INTEGER_TAG.

CR  9266: ETHernet.
          With a simple config of bridging with an enet port and fddi port
          running 7.71, if you disable the enet port via TI,
          's wfCSMACDEntry.2.instance 2', and then check the interface
          operator status (wfifEntry.ifOperStatus), it will toggle between
          a 1 and a 3.  this instability will also occur if the enet cable
          is pulled with the exception that the value returned from
          wfifEntry.ifOperStatus will now be toggling between a 1 and a 2.

CR 12782: System.
          Improved the debug information recorded in the system log on
          occurrences of BB TAG violation slot resets.

CR 12583: E1.
          E1 board configured with external clock uses the clock received
          from port 1 as its clock source. If port 1 goes down then clock
          source switches to port 2. After port 1 returns the clock source
          remains with port 2 instead of returning to  port 1.

CR 12735: Frame Relay.
          In a Bridged Environment where a combination of FDDI, Ethernet
          and Frame Relay exist, intermittent TAG VIOLATIONS may occur on
          the Frame Relay slot.

CR 11058: Config.
          7.80 Router log shows up as slots booting off different router 
          versions. With SM 1.80 connect to a 7.71 router, go to Config Mgr 
          in dynamic mode and save the file.  Then reboot the router under
          7.80, SM displays msgs showing what versions the slots are
          booting off of.  What will appear in the log, in an alternating
          fashion, is the first slot will show "booting off 7.80", the
          second slot will be "booting off 7.71",  the third slot will be
          "booting off 7.80" and the fourth will be "booting off
          7.71", and so on.

CR 12336: X.25.
          IP RIP advertisements stop on random X.25 PDN circuits after a 
          reboot.

CR 12541: IPX.
          After executing an incorrect ipx ping such as 'ping -IPX 0x1.0'
          the slot running ti will either become disconnected but not show
          anything in the log as in the case of VME hardware or reset with
          a tag violation in the case of the BN or ASN hardware.

CR 12388: PPP.
          When the PPP protocol determines that a sync line has gone down,
          through either missing echoes or LQR, the LCP will cause the NCPs
          to go into a starting state but the
          wfPppCircuitEntry.wfPppCircuitState is still up.

CR 12334: OSPF.
          If the router is configured to run OSPF NBMA and does not have 
          Static Neighbor configured it will not have Dynamic Neighbor in
          the MIB even if adjacency with the neighbor can be established.

========================= Version 7.80 fix 5  =============================
The image for FRE hardware is:               1478287 Jan 30 11:40 boot.exe 
The image for VME & AFN Floppy hardware is:  1504360 Jan 30 14:33 ace.out 
The image for AN hardware is:                1297876 Jan 30 11:58 boot.exe 
The image for IN & AFN Flash hardware is     1377302 Jan 30 15:25 boot.exe 
___________________________________________________________________________


CR  9999: IPX.
          Loss of connectivity for IPX hosts that use inter-slot routing
          can occur. This usually happens after an IPX interface goes
          down/up or End Station Support learns a new RIF for a given
          IPX host.

          This problem was introduced as a side effect of the repair
          documented below in fix/7.80/3 in CR 9999.

CR 12647: IPX.
          In IPX networks with large numbers of end stations with many 
          clients attempting to open connections to one server a system
          task and its associated memory can be lost.

CR 12589: PPP.
          All bridge traffic is discarded on PPP link between Wellfleet
          and Network Systems router/bridge.

CR 12575: Vines.
          Zero hop count NetRPC search and search-all broadcasts are
          forwarded even if ARP is not enabled on the interface.  This can
          result in broadcasts storms if a local StreetTalk server goes down.

CR 12555: LLC.
          After having opened and closed around 270 LLC sessions through a
          router, it is no longer possible to establish new sessions. The
          typical error messages in the log are:

          933: 01/20/95 12:12:40.271  DEBUG    SLOT  2  LLC       Code:  11
          Context not found or unavailable.
          934: 01/20/95 12:12:40.271  DEBUG    SLOT  2  LLC       Code:  11
          LLC ERROR: No Context Available

CR 11932: OSPF.
          During a dynamic configuration, the router may BUS ERROR when
          adding or deleting area 0 when other areas already exist.

CR 12476: Packet Capture.
          Unable to restart packet capture if the first PCAP file is too
          large. To reproduce problem:
          Calculate the maximum amount of memory allowed for Packet Capture
          on a slot. You will be able to successfully run this capture
          once, if you stop the capture when the trace is full, and attempt
          to restart you get the following warning message for PCAP:
          "wfPktCaptureBufSize  for  line xxx101 invalid"
          The wfPktCaptureControl is set to 1 (start), but
          wfPktCaptureCapture is set to 2 (stopped). It seems that the
          memory resources are being checked but memory resources allocated
          for the previous PCAP file are not being considered for the
          PCAP file overwrite.

CR 12358: LNM.
          Stations cannot insert onto a ring on which an ANts is the only
          available Ring Parameter Server. Ring station sends out a Request
          Initialization to the RPS functional address C00000000002, and
          the frame is returned from the ring with the AR/FC bits set,
          indicating an RPS is available. The AN does not return an answer
          to this request (it sees them as illegally formatted), and after
          3 retries the ring station exits from the ring.

CR 12451: LNM.
          Multiple out of memory slot resets can occur while using LNM on
          heavily loaded rings.         

CR 12423: IP.
          IP router allows various types of invalid IP subnet masks. The
          IP interface should not come up when an invalid IP subnet mask
          is configured.

CR 12436: Vines.
          Vines internal network table gets corrupted in a Vines network
          with redundant links.  This causes servers behind a router to
          become unreachable even though the MIB has a valid metric for
          the route.

CR 12409: OSPF.
          OSPF problem when 2 wf routers are configured as follows:

          -------    Area A1  -------     Area A2
          |  R1  |-----------|  R2   |--------------
          -------  Network N1 -------  Network N2

          When both routers come up for the first time and establish a full 
          adjacency network N2 is advertised into A1 by R2 as a summary
          link, installed as such in R1's lsdb and also appears in R1's
          ip routing table.

          At this point R1 is rebooted. When it comes up and establishes
          a full adjacency with R2 it correctly installs N2 as a summary
          link in the lsdb but N2 is now missing from R1's routing table.

CR 11031: Vines.
          When Vines Fragmentation Protocol (FRP) is disabled on a WAN
          interface, a bus error panic will occur when the sync interface
          is disabled and enabled.

CR 12260: Netboot.
          Netboot does not work when bofl is configured on a sync line.

CR 11557: OSPF.
          OSPF routes learned over a virtual link are not processed 
          properly on the backbone router that is receiving them in certain
          (large routing table) topologies due to a non-recoverable 
          hogs bufs situation.

CR 12376: IP.
          Arp Request is discarded if the source IP address is not in the
          same subnet.

CR 12373: SNMP.
          Snmp packets containing a get request for 24 or more objects
          causes various problems (usually ASN1parse errors).

CR 11433: Token Ring.
          The ring data rate is incorrect in the 8502 frame sent from the
          router to the IBM Lan Network Manager. Even though the ring is
          configured for 4Mbps it still sends the ring data rate as 16Mbps.

CR 10842: System.
          A VME router fails to boot properly with very large config files. 
          Some slots are unable to receive the config info.

CR 12086: Circuits.
          Enabling Hardware Filters in ESAF 5531-2 Link Modules caused the
          interface to hung in the initialization state if it was 
          configured via install.bat.

CR 11934: IP.
          Under very heady loads, routing information may not be properly 
          maintained after IP on another slot resets.

CR 10722: IP.
          IP connectivity can be lost while aging hosts. This is due to the
          routing table getting corrupted if no buffers are available while
          Host aging is happening.

CR 10520: Source Route Bridge.
          A source route packet with length field bits set to 3 (4472)
          that originates on a Token Ring segment will have the length
          field decreased to 2 (2072) when it crosses an FDDI ring.

CR 12127: Token Ring.
          The Token Ring interface on an AN will continuously reset with a
          timeout error on a network that is very busy. Some example log
          messages are;

          Connector MAU1 Cmd (0xa) time-out (s=008c) 
          (a=0000 0000 0000 0000).
          Connector MAU1 stop... env->phy_addr = 04000000.

========================= Version 7.80 fix 4  =============================

The image for FRE hardware is:              1479172 Dec 30 17:11 boot.exe
The image for VME & AFN Floppy hardware is: 1504240 Jan  4 16:08 ace.out
The image for AN hardware is:               1291272 Dec 30 17:41 boot.exe
The image for IN & AFN Flash hardware is:   1377702 Dec 30 17:49 boot.exe
___________________________________________________________________________


CR 12134: OSPF.
          OSPF does not properly notify IP when an LSU is received with a
          change of MASK.

CR 11376: LNM.
          LNM can cause 'out of memory' slot resets when receiving excessive 
          non-isolating errors.

CR 11374: DLSw.
          When DLS is terminated at the same port that SRB uses for the SNA
          client to continue its communication path  to the host, DLS enters
          invalid state.  

CR 10870: IP.
          IP router does not update ARP Cache according to RFC. RFC 826
          suggests the desired algorithm for receipt of an ARP request is
          for a receiver (even though he may not be the target) to update his
          ARP Cache when a request is received containing a new source MAC
          address for an entry that already exists. The IP router does not
          update the ARP cache for existing entry upon receiving ARP request
          containing new source MAC Address if the ARP destination is not for
          the local interface.

CR 11845: Vines.
          Vines Routing Table Manager uses excessive memory storing remote
          end-station information gratuitously.

CR 11866: Vines.
          Vines router permanently looses local memory after circuit goes
          down/up.

CR  None: Spanning Tree Bridge.
          Transparent bridge spanning tree tunneled over token ring does not
          recognize 5 series BPDU's because of the 8103 protocol id field.
          Likewise, the 5 series does not recognize the 7 series BPDU's
          because of the 0000 protocol id field.

CR 11814: PPP.
          OSI over PPP may not be established; The OSI NCP remains in closed
          state. This can happen to any NCP, not just OSI. The problem will
          appear if the remote router sends a PPP Protocol Reject packet to
          WF in response to WF sending a PPP Configuration Request packet.
          RFC 1548 specifies that the NCP should remain in whatever state it
          is in when it receives the Protocol Reject, and that the NCP should
          stop sending out whatever is causing the peer router to send back
          Protocol Rejects. Instead, WF router is generating a closed event
          and transitioning to Closed state. This prevents us from
          establishing a connection if/when the remote router ever does
          send a Connection Request.

CR 11977: Vines.
          Running Vines over Source Route Bridge using End Station support
          may result in RIFs being changed too often causing Vines servers
          to go into suppression.

CR 11190: OSPF.
          When OSPF is configured with BGP3 to connect multiple ASs, BGP3
          learned routes can become unreachable within OSPF for no apparent
          reason.

CR 11839: IPX.
          Directed broadcast diag packets are not being forwarded by the IPX
          router. These are packets with an IPX socket number of 456 or 7777. 
          These two sockets are used for IPX ping when the IPX destination
          node is not a broadcast, in the case when the destination node is
          a broadcast (FFFFFFFF) the router should forward the packet to the
          appropriate interface and node if one exists. If the network is
          known but not the node the packet should be broadcast on that 
          known network.

CR 11857: System.
          An orphan buffer error can appear in the log with the source gate
          ID value in the 0x400 range (I.E. 0x401, 0x402, 0x403 etc).

CR 10557: AppleTalk.
          Slot routing AppleTalk can experience Tag Violation reset upon
          receipt of illegal NBP tuples.

CR 11529: OSPF.
          OSPF no longer advertises attached external interface after CSMACD
          bounces. External interface is up and appears in the routing table
          but is not found in the LSDB. This occurs after the CSMACD has
          bounced (seen in the log).  All external routes learned over that
          external interface are no longer reachable from the OSPF network.

CR 11638: IP.
          The propagation of a zero subnet over the same network/different
          IP subnet will not get installed into the IP routing table.  This
          failure can be seen when the following scenario exists, standard
          class b network is sub-netted with a class c mask and a zero subnet
          exists within network.

CR 11815: OSI.
          OSI connectivity may not be established over Level1 or  Level2 
          PtoP Adjacencies.

CR 11829: IPX.
          If the destination network of a SAP entry does not exist in the 
          routing table, IPX may panic while calculating the nearest server.

CR 11704: X.25
          Querying the router for its MIB-II ifTable on an interface configured 
          for X.25 returns the value 6 for the ifType. The value 6 is
          enumerated to ethernet-csmacd in  MIB-II.

CR  None: System.
          Doing a 'get wfKernelEntry.*.' at TI sometimes returns zeros
          for all values.

CR  None: IP.
          Receipt of IP packets that would cause the router to send an ICMP
          redirect would permanently lose memory.

CR 11692: System.
          Slot resets infrequently occur with an 'out of GID' error in the log.

CR 11006: DLSw.
          The loss of a number of segments in the IP cloud between 2 routers
          running DLSw causes a high number (70+ %) of TCP retransmissions
          for the rest of the life of the connection. Slots can also reset
          with out of memory errors.

          The out of memory resets were caused by the method of handling  
          broadcast frames which are not flow-controlled - if TCP was busy
          DLS would try to save incoming broadcast traffic for as long as
          there is memory on a slot.  In some cases this would result in DLS
          eventually using up all available local memory causing a slot to
          reset. This problem has been resolved by the following improvements
          to the configurability of DLS. 

          Three new MIB attributes were added to the wfDlsSlotEntry MIB object.
 
          wfDlsCurrentMemory    -- to reflect the amount of memory in kilobytes
                                   currently used by DLS on a particular slot.

          wfDlsMaxAllowedMemory -- this is a configurable parameter. It 
                                   reflects how much memory in kilobytes DLS
                                   is allowed to use on a particular slot.
                                   When this number is reached DLS would start
                                   dropping incoming traffic. Thus preventing
                                   a router from crashing. The default value
                                   is -1, Which means infinity. (all available
                                   memory).

          wfDlsHiWaterMark      -- to reflect the highest memory consumption 
                                   in kilobytes reached on a particular slot
                                   by DLS since the last reboot. 

          The last attribute is intended to be used in the following way.  
          Since every customer environment is different and it is hard to 
          predict an average traffic load, the user should let a router run
          with wfDlsMaxAllowedMemory set to the default value for sometime.
          Assuming there were no unusual events during this period of time a
          user should set wfDlsMaxAllowedMemory to wfDlsHiWaterMark or some 
          number close to it. For example: after booting wfDlsMaxAllowedMemory 
          is set to -1. wfDlsHiWaterMark is 0. wfDlsCurrentMemory is 0. 
          Looking at the above attributes after 3 days one sees
          wfDlsMaxAllowedMemory is still set to -1. wfDlsCurrentMemory is 100
          and wfDlsHiWaterMark is 300. Now if you set wfDlsMaxAllowedMemory 
          to 300, it would assure that in an emergency situation DLS would not
          run a slot out of memory because of the unlimited consumption of
          memory. The optimal amount of memory allowed to be taken by DLS
          should be determined experimentally for the particular configuration.
          Access to the above attributes is available from TI only for now.
          The Site Manager support for this enhancement will be implemented
          in a later release.

CR 11754: IP.
          When IP circuits are disabled/enabled, OSPF HELLO packets can be
          sent to wrong subsystem causing unpredictable results (like
          orphaned buffer log entries).

CR  None: IPX.
          The maximum number of IPX SAP filters per interface that can be
          configured has been increased from 50 to 150.

          The Site Manager support for this enhancement will be implemented
          in versions 2.00 fix 1 and 2.1.

CR 11370: OSPF.
          Version 7.xx advertises default summary with stab metric of 0 into
          a stub area. Version 5.78 does not have this problem. The metric
          for the summary link advertisement is set to the (per-area) 
          configurable parameter Stub metric.

CR 11596: MIB.
          The Mib stat if.ifOutErrors can be erroneously high on enet
          circuits.  It appears that the mib stat
          wfCSMACDEntry.wfCSMACDDeferredTx is incorrectly being added in
          the calculation of if.ifOutErrors.

CR 10026: IPX.
          Ipx over dial-on-demand circuit intermittently failing on boot.
          This problem has been seen using an AFNES 4MB platform configured
          for IP and IPX (ipxcp) dial in demand in v7.80. The interface used
          was v35/v25bis signaling. The WAN link did not carry any dynamic
          information, all routes were statically configured and all IPX
          services were statically configured. When booting the routers the
          following IPX warning event message was logged on one router:
 
          'IPXWAN/PPP Incorrectly configured: IPX intf non-zero and
          PPP-negotiated net is not equal to IPX intf'.  After this IPX would
          fail to register with the demand cct and no data would be passed.

CR 10922: PPP.
          AN is connected to a Network Systems router via sync port. Sync
          port is configured for PPP with bridging and IP. IP comes up fine.
          When the BNCP negotiation takes place the Network Systems router
          sends the AN a BNCP configure reject for all mac types (FDDI
          ETHERNET and TOKEN RING). When the AN receives the configure reject
          a bus error Panic occurs.

CR 11168: OSI.
          OSI router fails to accept packets with pad bytes before the
          NLPID when received over PPP interface.

CR 11366: IPX.
          IPX is incorrectly processing SAP names followed by NULL chars and
          ending with garbage characters. The problem shows up as large SAP
          tables with many duplicated entries which are all the same server. 
          This causes the router to send out many SAP packets with what
          appears to be the duplicate server entries.  

CR  8101: System.
          Slot Resets with 'checksum error found in old system log'. The
          entire system log for that slot is then lost. System log validation
          has been improved to be more discriminating when making its 
          decision to eliminate a slot's damaged log.
          
CR 11477: IP.
          IP ARP does not properly resolve the address. When a multi-netted
          IP interface receives an ICMP request and needs to ARP to resolve
          the address of the next hop router before responding, The router
          does not issue the ARP, but logs the following message;

          'Tried to send invalid arp for  on intf
          
           - is the IP address of the next hop router.
            - is the IP address of a local interface, 
          diff network'.

          Once the router is in this state you need to ping from the router
          to the correct next hop address, this properly resolves the address.

CR 11438: IP.
          If router A has an adjacent host configured for router B in IP and
          router B then sends an ARP request to router A one system task and
          its associated memory is lost.

CR  None: System.
          The message 'gate 0x0c1fe being killed by 0x00049 @ 0x304a2c3e
          is dead - ignored' frequently appears in the log. Although this
          message can be generated from many subsystems, one particular
          problem involving HostCache which produced those messages is
          now resolved.

CR 10885: DLSw.
          DLSw may cause a MIB panic when deleting instances after
          failure of multiple DLSw sessions.

CR 11095: DLSw.
          DLS, when configured for an ethernet interface erroneously
          responds with a Disconnect Mode packet to sna bind requests
          which are destined to hosts on the same local ethernet segment.
          This problem has the effect of preventing sna sessions between
          hosts on the local ethernet segment from working.

CR  none: IPX.
          When IPX responds to Get Nearest Server, in the case of a tie in
          the hop count to a number of different servers, IPX router should
          respond with the one that is first in alphabetical order, which
          is not the case starting with 7.71 fix 7. This problem was
          introduced by the fix for CR 10746.

CR 11369: IP.
          IP router looses track (has no ARP entry and doesn't send ARP
          request for new one) of host entries after another slot resets.

CR 11231: IPX.
          Multiple instances of the same IPX route will appear in the MIB
          if a router has multiple connections to another router, even
          with multi-path turned off.

CR 10582: Switched Services.
          The dial backup link is not initiated in the following cases:

          1. When the modem is set to loopback.
          2. When Rx wire is being disconnected either on the master or on
             the slave side.

          This has been resolved by enhancing the sync drivers to check
          for the BOFL packets and detect the loopback condition. The
          loopback is detected by comparing the source MAC address in the
          BOFL packets with the sync interface's MAC address. When the
          loopback is detected the sync line driver is brought down. When
          it is trying to come back up it goes into loopback state and stays
          in it until it receives the BOFL from the remote side.

          A new MIB attribute 'wfSyncRemoteLpbkDetection' has been added to
          the wfSyncEntry. The above actions will take place only if this
          attribute is set to ENABLED. This has been done intentionally since
          most customers are using loopback for verifying that the link
          functions properly. Site Manager support for this option will
          be implemented in release 2.10.

======================== Version 7.80 fix 3  =============================

The image for FRE hardware is:              1472507 Nov 22 15:02 boot.exe
The image for VME & AFN Floppy hardware is: 1498139 Nov 22 15:16 ace.out
The image for AN hardware is:               1294417 Nov 22 15:25 boot.exe
The image for IN & AFN Flash hardware is:   1372181 Nov 22 15:30 boot.exe
_____________________________________________________________________________

CR 11259: Frames less than or equal to 16 bytes in length do not get picked
          up by Learning Bridge. The initial frame was generated from a client
          on an ethernet segment and destined for a server on a remote
          ethernet. The two ethernet segments were connected via two Wellfleet
          bridges with fddi as the connecting transport.

CR 10860: A network that routes Vines and also has end station support and
          servers that are redundantly linked to the bridged network, 
          may show servers as unreachable on the remote slots where Vines 
          is routed.

CR 10814: DECnet router does not generate triggered update when adjacency
          comes up.

CR 10966: DECNET router may experience a hogs bufs condition which could lead
          to multiple PANICS when a topology change occurs.  The specific
          topology change would be in the form of a number of adjacencies
          going unreachable at the same time and the presence of at least one
          other router sharing a common segment.  What can happen is that when
          the adjacencies time-out, DECNET, which does not support
          split-horizon, counts to infinity to age out the routes.  During
          this time of counting to infinity hogs bufs can occur. Also,
          counting to infinity takes more CPU cycles than it should.

CR 10793: IPX ping over token ring fails intermittently.

CR  9999: Slot can reset with 'Out of Memory' errors when IPX interface with
          many (> 400) hosts entries goes down.

CR 10702: Although a Wellfleet router running version 7.80 and 8.0 software
          can transport DHCP requests/replies, there are still areas where
          Wellfleet routers are not 100% RFC1532 compliant.

          1) The BootP Relay agent should only care about UDP BootP Server 
             packets (port 67).  The current code registers and processes for 
             both BootPC and BootPS ports. A relay agent MUST silently discard 
             any received UDP message whose UDP destination port number is 
             BootPC (68) in paragraph 4.1 of RFC1532.

          2) Seconds field should apply to request packets only so one can set
             the seconds field to a non-zero number and still let 0 second
             replies through.  Our implementation checks both request and
             replies.  The Microsoft implementation has a minor problem of
             not setting it to 0 initially and not incrementing it
             subsequently (see paragraph 3.2 in RFC1532).

          3) The newly defined Broadcast flag is not checked in the current 
             code, the correct behavior is to broadcast only if 'ciaddr'
             field is zero and the flag is set.  (See paragraphs 3.1.1 and
             5.3 in RFC1532).

CR  None: System reliability is now improved on ACE32 processors by the
          addition of a watchdog process which will restart a slot if a
          single task runs for more than 16 seconds.

CR 10569: When deleting one IP address from a multi-netted interface arp
          will no longer function correctly.  If an IP address gets deleted
          from a multi-netted interface all devices on remaining network
          will be unreachable.

CR  9763: When using Protocol Prioritization - Bandwidth Allocation Method,
          there is a condition that the serial port could enter where all
          traffic would stop flowing, under saturation conditions. If Bofl
          was enabled, the port would be restarted after the Bofl timeout
          (resulting in a 'transmitter timeout' logged message), otherwise
          the port would hang indefinitely. This problem would often occur
          on both sides of the serial link (even if PQ wasn't enabled on
          the remote side).

CR 10724: If multiple packets are sent to a dial on demand circuit in quick
          sequence bus error/panic will occur before the modem dials out.
          The packets in this case were ip encapsulated source route 
          explorer packets.

CR  8616: Dial back up circuit is unable to establish the PPP link the first
          time the primary link goes down after being booted.

CR 10583: In a dial backup configuration. When the Tx wire is disconnected
    8630: from a Slave router, the master's primary line goes down. When
          the slave accepts the call from the master a bus error occurs.
          
CR 10029: When configuring out-bound filters based on source or destination
          MAC address, the MAX address must be entered in canonical format.
          The problem then arises that when entering a MAC address range in
          canonical format, the high address range could end up with a lower
          value than the low range and Site Manager will give a message
          'Minimum Value Greater Than Maximum Value'. Added a new MIB variable
          'wfCctOptsEntry.wfCctOptsMacFilterFormat'.  The default is 1,
          which is canonical.  Setting this to 2 will allow entering MAC
          filters in token ring format.  (Note: All filters on the interface
          must be in token ring format!).  Site Manager support for this option
          will be implemented in a future release.

CR 10563: When running Vines over Frame Relay with Vines Fragmentation
          Protocol (FRP) disabled, Vines traffic will not be forwarded.

CR 10746: IPX router responds to Get Nearest Server request when sap
          filters are configured on the same interface where both a
          server and a client reside (10746).

CR 10857: IPX router doesn't update its SAP advertisement after socket
          number changes.

CR 10859: IPX router does not correctly forwarded IPX Netbios frames
          (type 14h).

CR 10819: XNS can restart on the slot where one or both sync lines in a
          multiline configuration go down/up.

CR 10787: IPX router does not age out rip entries received with a hop
          count of 15.

CR 10607: EGP neighbor connection not re-established after circuit goes
          down/up.

CR 10667: IPX Routes May Fail to Age Properly. The Lost Route implementation
          incorrectly forms the packet to be sent out in the case where that
          route was learned to be dead (hop count of 16) from a different
          interface than the one that the route was originally learned from.

CR 10763: Transparent bridge / Multiline interface fails to come up on boot 
          or slot reset.

CR 10745: Enhancement for Dial-on-Demand circuits to allow the configuration
          of the inactivity timer to be in seconds instead of minutes. Note
          that this change affects existing config files such that what the
          network administrator previously configured in minutes is now a
          value in seconds.
          
CR 10696: Learning bridge over token ring does not learn about station
          moves as it should.

CR 10314: In particular configuration DECnet router sends incorrect level
          2 routing message designating local area as 1 hop and some non
          zero cost away.

CR  9958: Vines router does not respond to StreetTalk requests from clients
          on serverless segments.

CR  9870: Dynamic disabling of an OSPF interface can cause a PANIC bus
          error on non-backbone routers.

CR 10412: When Learning bridge traffic is flooded over FDDI onto a Frame
          Relay network the router at the remote side does not flood the
          bridge traffic out its other interfaces which reside on the same
          slot as the Frame Relay interface.

CR 10417: BGP-3 Update messages are sent with incorrect next hop in
          particular configuration.

CR 10543: Slot resets with 'System restart in tmo_wdog.c at line 51' when
          XNS router learns many (500) routes after wan link goes down/up.

CR 10685: Running NetBIOS Caching may cause panic in sr_nb_process_are due
          to RIF entries being aged while the same RIF entries are being
          re-learned.

CR 10684: Running NetBIOS Caching may cause a 'PANIC in mib_ent.c at line
          710' due to RIF entries being aged while the same RIF entries
          are being learned.

CR  9175: Router responds to SMDS heartbeat poll on logical link 0 instead 
          of logical link 1.

======================== 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 
_____________________________________________________________________________

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
          signaling on 44 pins sync interface does not work. Sync
          interface cannot see the modem, reports CTS failure. Incoming
          calls never transit out of v25bis signaling to data mode, all
          LCP configuration frames are interpreted as illegal v25bis
          commands. Outgoing calls never transit from modem signaling
          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 disabled, 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 range for 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 re-learned 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 in-bound packets are seen. This causes a
         sub-optimal use of the transmit window which is especially
         noticeable 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 take down does not work for dial demand and take down 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 inconsistent 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 re-learned 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 different 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 continuously 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 re-learned 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.

/tr>