 |
|||
     |
|||
|
Revision Notes for Router Software v8.01 rev 2
Date: 2/15/95
Subj: Revision Notes for 8.01 fix 2
===========================================================================
SITE MANAGER COMPATIBILITY
===========================================================================
Router version is managed by Site Manager version
v8.01 2.00
8.01 fix 1, 2 2.00, 2.00 fix 1
========================= Version 8.01 fix 2 =============================
The image for FRE hardware is: 1767298 Feb 14 17:06 boot.exe
The image for VME & AFN Floppy hardware is: 1651470 Feb 14 17:29 ace.out
The image for AN hardware is: 1537418 Feb 14 17:12 boot.exe
The image for IN & AFN Flash hardware is: 1640873 Feb 14 17:21 boot.exe
___________________________________________________________________________
Revision fix/8.01/2 corrects the following problems:
===========================================================================
CR 12532: DLSw.
When DLSw and LNM are both configured on the same slot either
may fail to operate.
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/8.01/1 in CR 9999.
CR 12895: Vines.
The Vines client program SEND.EXE does not work on serverless
segments.
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 12535: Config.
QSYNC interface will not come up after running install.bat.
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 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 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 11250: IP.
Default Route IP Export Route Filtering Causes Bus Error. When
Export Route Filter is configured to filter out the default route
(0.0.0.0/255.255.255.255 IP_ADDR/IP_MASK) it would cause bus
errors on the 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 12434: IP.
Rip Import Route Filters do not apply mask correctly. RIP applies
the interface mask instead of the configured import route filter
mask.
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 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 12589: PPP.
All bridge traffic is discarded on PPP link between Wellfleet
and Network Systems router/bridge.
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.
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 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 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 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 10597: Spanning Tree Bridge.
Non-root AN sync port detect topology change under no-load
conditions. Log messages stating "spanning tree topology change
detected, sending TCN out port %x" have been seen on the non-root
bridge of a two AN-ES test configuration. Port %x is the sync
port connecting the AN's. This behavior is causing increased
packet loss over the sync pipe.
CR 11376: LNM.
LNM can cause 'out of memory' slot resets when receiving excessive
non-isolating errors.
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 11877: OSPF.
ospf.bat script incorrectly displays two-word neighbor statuses.
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 11692: System.
Slot resets infrequently occur with an 'out of GID' error in the log.
CR 10388: XNS.
The show xns routes script displays the next hop host but NOT
the next hop network.
CR 12184: Spanning Tree Bridge.
A slot may incorrectly consider it's Bridge ID to be Root.
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 (12376).
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 11611: System.
Various unexplained RPC Timouts in mib_ent.c.
CR 11677: OSPF.
OSPF virtual link will cause OSPF resets at versions > 8.0.
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 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 12134: OSPF.
OSPF does not properly notify IP when an LSU is received with a
change of MASK.
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.
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 12115: IP.
Receipt of a RIP broadcast sourced from another network results in
an Error: exception vector 2 - Bus error. Receipt of multiple
broadcasts back to back may result in IP restarting. A likely
configuration where this may occur is a multi-net'd environment
where the suspect router is only partially or non multi-net'd.
CR 11589: Source Route Bridge.
Source route bridge filter setup to drop all routes explorer frames
based on the RIF length do not drop the frames in 8.01. The same
filter works in tests on 7.80 fix 3 and 7.71 fix 4.
CR 12085: DECnet.
DECnet Level 2 router doesn't listen to the DECnet Level 2 router
multicast. This problem was previously reported by CR 8599 and
fixed in v7.80 (also version 7.71 fix 5).
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 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 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 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.
======================== Version 8.01 fix 1 ==============================
The image for FRE hardware is: 1773483 Dec 20 12:40 boot.exe
The image for VME & AFN Floppy hardware is: 1651186 Dec 20 12:59 ace.out
The image for AN hardware is: 1544831 Dec 20 13:36 boot.exe
The image for IN & AFN Flash hardware is 1645144 Dec 20 14:07 boot.exe
----------------------------------------------------------------------------
CR 4270: Source Route Bridge.
In source routing environment Apple end stations issue test frame
with 0xAAAAF3 dsap_ssap_ctrl field to the router. The router doesn't
reply to this frame and Apple end station support doesn't come up
on the network.
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 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 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 9839: Bridge.
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 9175: SMDS.
Router responds to SMDS heartbeat poll on logical link 0 instead
of logical link 1.
CR 10685: Source Route Bridge.
Running NetBIOS Caching may cause panic in sr_nb_process_are due
to RIF entries being aged while the same RIF entries are being
relearned.
CR 10684: Source Route Bridge.
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 10543: System.
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 10498: NML.
Slot running NML can bus error in tfind when bridging traffic .
CR 10412: Bridge.
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 10557: AppleTalk.
Slot routing AppleTalk can experience Tag Violation reset upon
receipt of illegal NBP tuples.
CR 9870: OSPF.
Dynamic disabling of an OSPF interface can cause a PANIC bus
error on non-backbone routers.
CR 9958: Vines.
Vines router does not respond to StreetTalk requests from clients
on serverless segments.
CR 10314: DECnet.
In particular configuration DECnet router sends incorrect level
2 routing message designating local area as 1 hop and some non
zero cost away.
CR 10790: System.
On an ASN the attribute 'HwModuleModRev' was 0 all the time
instead of displaying the true Net Module revision number.
CR 9690: OSPF.
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 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 10696: Bridge.
Learning bridge over token ring does not learn about station
moves as it should.
CR 10745: Switched Services.
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 9225: Bridge.
8743: Bridge traffic doesn't properly switch back to the primary line
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 10787: IPX.
IPX router does not age out rip entries received with a hop
count of 15.
CR 9999: IPX.
Slot can reset with 'Out of Memory' errors when IPX interface with
many (> 400) hosts entries goes down.
CR 10667: IPX.
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 10819: XNS.
XNS can restart on the slot where one or both sync lines in a
multiline configuration go down/up.
CR 10746: IPX.
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 10859: IPX.
IPX router does not correctly forwarded IPX Netbios frames
(type 14h).
CR 10857: IPX.
IPX router doesn't update its SAP advertisement after socket
number changes.
CR 7221: IP.
IP and OSPF remain up when FDDI interface is disconnected.
CR 10616: IPX.
Accept option doesn't work properly for IPX Traffic Filters.
CR 10569: IP.
When deleting one IP address from a multinetted interface arp
will no longer function correctly. If an IP address gets deleted
from a multinetted interface all devices on remaining network
will be unreachable.
CR 10029: Filters.
When configuring outbound 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 10724: Switched Services.
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 10563: Vines.
When running Vines over Frame Relay with Vines Fragmentation
Protocol (FRP) disabled, Vines traffic will not be forwarded.
CR 10702: IP.
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 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.
CR None: System.
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 10793: IPX.
IPX ping over token ring fails intermittently.
CR 10814: DECnet.
DECnet router does not generate triggered update when adjacency
comes up.
CR 10966: DECnet.
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 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 10860: Vines.
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 10885: DLSw.
DLSw may cause a MIB panic when deleting instances after
failure of multiple DLSw sessions.
CR 11369: IP.
IP router loses track (has no ARP entry and doesn't send ARP
request for new one) of host entries after another slot resets.
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 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 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 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 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 11168: OSI.
OSI router fails to accept packets with pad bytes before the
NLPID when received over PPP interface.
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.
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
