 |
|||
     |
|||
|
Revision Notes for Router v11.00 rev 6
============================================================================
TE MANAGER COMPATIBILITY
=============================================================================
Router Version is managed by Site Manager version
v11.00 revision 1 --------------------------> V5.00, 5.00 rev 1
v11.00 revision 2 --------------------------> V5.00, 5.00 rev 1
v11.00 revision 4 --------------------------> V5.00, 5.00 rev 1
v11.00 revision 5 --------------------------> V5.00, 5.00 rev 1
v11.00 revision 6 --------------------------> V5.00, 5.00 rev 1
NOTE: Please be advised that 11.00/3 was never shipped for customer release.
------------------------------------------------------------------------------
Revision 11.00/6 corrects the following problems:
==============================================================================
CR 29336: GAME.
A problem exists in router software version 11.00 rev 5 in which a
BCN router experiences periodic watchdog errors in Gate Die
Cleanup. This condition causes the slot to reset, which results in
loss of connectivity.
CR 28244: DLSw.
A Bay Networks router sends an SNA request (SSP Infoframe) to a
a Proteon router. The Proteon router forwards the request to the
host on the TR but fails to forward the response from the host to
the Bay Networks router. This occurs because the Bay Networks
router running DLS code ignores the flow control information
received with XID frames and fails to send proper flow messages
to the Proteon router.
------------------------------------------------------------------------------
Revision 11.00/5 corrects the following problems:
==============================================================================
CR 25291: MIB II.
The ifEntry MIB object contains two attributes, ifInOctets and
ifOutOctets, which do not contain the correct information when
corresponding to a multiline circuit where the circuits, are
on different slots. The value for the ifEntry object should be
the aggregate of all the synchronous interface statistics
contained in a multiline interface.
CR 25842: IP.
Host entries may fail to display when the wfIpNetToMedia MIB table
is queried.
CR 26564: DLSw.
Specific DLSw gates will incorrectly increase their memory
consumption each time you establish a session involving non-NULL
XIDs through the router.
CR 26687: MIB.
A query of the MIB-II attribute ifEntrySpeed does not return
the aggregated line speed of a multiline circuit when using
external clocking.
CR 27470: IPX.
System performance degradation may occur because the "lost route
algorithm" was executed unnecessarily.
CR 26743: ATM.
Issuing the "SHOW ATM INTERFACE" command produces an error using
mixed Tsunami/BF configurations.
CR 27240: DECnet.
After configuring DECnet on the router, modifying any interface
parameter leaves the DECnet interface in a down state from which
it never recovers.
CR 27489: Switched Services.
A bus error occurred after the primary circuit in backup mode is
terminated on the slave side.
CR 26125: DLSw.
A Walts script that is driving the automat generates 500 test
polls per second with the destination address equal to that of the
host and a unique source address. After a few minutes of
operation, the router experiences a watchdog error.
CR 27479: DLSw.
A NetBIOS name query is sent through a router to its destination
but the destination fails to respond. Subsequent name queries sent
less that 5 seconds apart are dropped.
CR 28003: LAN Bridge.
Adding a Bridge Forward_to_cct filter onto an ATM PVC it can cause
a Bus error to occur or cause the router to discard the traffic
being transmitted through this filter.
CR 28012: IPX.
The router experiences bus errors when running high traffic
throughput tests.
CR 28186: Learning Bridge.
Adding a Bridge Forward_to_cct filter onto an ATM PVC can cause
the router to discard the traffic being transmitted through this
filter. The filter count will increment but it will never make
it to the circuit to which it is being forwarded across the
backplane.
CR 27177: ATM.
Unable to connect to IBM LANE Services. Control distribute VC's
were rejected because the AAL5 packet size was not one of the known
sizes. We should check the packet size on Data VC's.
CR 27779: BOT.
Deleting an S11 circuit on an ARN router may cause the router to
fault.
CR 27969: BOT.
The log on the router fills with messages and wraps
on the active side until a route becomes available. If a route
does not become available, the log continues to collect messages,
rendering it invalid.
CR 28158: BOT.
Data transfer on the ARN and ASN routers may stop after a certain
amount of time.
CR 27536: IP.
IP consumes all local memory when pinging through a router to a
non-existent IP addresses. For instance, this problem could occur
if a network management workstation ping all IP addresses within
a subnet.
CR 28039: LLC.
When you dynamically delete a 11c circuit that you configured with
Frame Relay, a bus error occurs.
CR 27503: TCP.
After disabling the wfTcpBase, a router configured with DLS
processes slowly because hogs bufs are being generated.
CR 27765: DLSw.
When a Bay Networks router receives continuous NetBIOS
Name Queries from a third-party router configured with DLSw,
the Bay Networks router will fault with a tag violation error.
The tag violations, which do not occur immediately, appear to be in
the TCP fragmentation/sequence handling.
CR 27665: Spanning Tree.
When two routers are interconnected via ATM and Spanning Tree
is configured on these circuits, the blocking circuit never
establishes a steady state. The blocking circuit repeats
the cycle of blocking, listening, learning, and forwarding
because the bridge information expired and the Spanning Tree
restarts the root bridge protocol again.
CR 27666: IPX.
A problem exists with the new SPX keepalive spoofing feature that
gets enabled automatically when IPX watchdog spoofing is enabled.
The problem is that the router spoofs SPX acknowledgment frames
(SPX Connection control field = 80), preventing the SPX session
from establishing.
CR 27826: Compression.
Router faults occurred while performing a test on a BLN and ASN
routers to verify that WCP works for dial-backup using V.25bis and
for dial-backup using ISDN PRI and BRI.
CR 27595: OSPF.
Information in the MIB indicates that the primary and backup
soloists are running on the same slot when in fact they are
running on different slots.
CR 27724: OSPF.
A requested OSPF enhancement that will allow you to manually
configure an OSPF neighbor on an OSPF interface that has been
configured for a standard point-to-multipoint network.
(In previous versions, you have been able to configure an OSPF
neighbor manually on a nonbroadcast multi-access - NBMA - interface
only. On a broadcast or point-to-point network, the Hello protocol
dynamically discovers neighbors.)
When you manually configure a neighbor on a standard
point-to-multipoint interface, OSPF uses the OSPF multicast address
244.0.0.5 - instead of the configured unicast address - to send
Hello packets.
CR 25311: BOT.
The Bisynchronous driver fails to indicate that the cable
connecting the router to the controller (CCU) has been
disconnected.
CR 23512: BOT.
The Bisynchronous and SDLC protocols require the ability to display
and control the following signals via Site Manager or the
Technician Interface in order to simplify troubleshooting:
DTR, DSR, CTS, RTS, DCD.
CR 27752: SNMP.
Bus errors can occur after you enter the command "show snmp
community". These errors occur after you reboot the router but
not while the router is operational.
CR 27899: TCP.
When attempting to track down tag violations in GAME's map_map,
map_walk, and other functions, the router experienced a fault
(PANIC in g_mfree) when using "debug krnl x all_mem".
CR 27938: Protocol Prioritization.
Non-SNAP and IP traffic (for example, OSI and SNA BNN) are not
filtered correctly when looking for a specific NLPID, or when a
user-defined filter is based on the FR_MPE reference point.
The FR_MPE reference point was being initialized only for SNAP
encapsulated frames.
CR 27982: ARE.
32 MB of tags are enabled for 64 MB boards on the ARE router. When
a configuration pushes the memory consumption over 32 MB, the
board constantly faults. Memory tagging is disabled for these
boards and a future hardware ECO is required for this
functionality to work.
CR 28063: SYSLOG.
When you configure a filter without a respective
host, SYSLOG will fault when calling sysl_chg_hoststate().
CR 26578: IP.
A problem exist in 10.00 (+) where entries in the ARP cache do
not get removed after you change the wfIpNetToMediaType attribute
from dynamic to invalid.
CR 26467: APPN.
A tag violation occurs when you attempt to ping a router configured
with APPN over SDLC.
CR 27483: ATM.
An ARE router experiences an VBM error on a slot when routing
between 1577 IP and LANE on the same port and when certain traffic
conditions are present.
CR 27551: OSPF.
The router accesses a null pointer (best_route), causing a bus
error to occur in ospf_ase_fill_in_cost().
CR 27114: TCP.
The router software does not close TCP connections according to the
RFC. This causes problems when interoperating with products
intolerant to variations on the connection close protocol
specified by the TCP RFC.
CR 27560: IP.
The BGP hold timer is not negotiated properly. For instance, if
either of the BGP peers sets the hold timer to 0, then the
hold timer is turned off. Currently, we are turning off the hold
timer only when both peers have their hold timer set to 0.
CR 27474: VINES.
VINES experiences a bus error when it unsuccessfully attempts to
allocate a buffer and then attempts to free the same buffer.
CR 26238: BOT.
Occasionally when booting the ASN (primary, TCP originator to
several connections) router, it faults with an error in
tcp_abort.c.
On other occasions, rebooting the BN router (which is secondary to
the ASN router) and disabling BOT globally on the ASN causes the
same errors.
CR 27237: IPX.
IPX does not filter a network address of 0. For example, if the
source network address of a packet you specify is 0, and
a traffic filter is created for network 0, the router ignores
the traffic filter.
CR 27501: X.25.
X.25 occasionally receives a data packet from LAPB before the
DP line is active; X.25 should discard this packet.
CR 25756: SM-Configuration.
When changing the SPI key dynamically, the change does not take
effect until you save the configuration and reboot the
system.
CR 17283: BOOTP.
When you configure a router using Site Manager, the router will
not update the Preferred Server IP addresses.
CR 7269: BOOTP.
The interface parameters (wfBootpRelayFwdAgentIntf and
wfBootpRelayFwdOutIntf) in the BOOTP record 'wfBootpRelayFwdEntry'
are seen as all zeros in the MIB and via bootp.bat script until
forwarding occurs. When forwarding occurs, the BOOTP relay agent
fills in the interface parameters with the instance ID information.
CR 25558: OSPF.
OSPF adjacency sometimes gets stuck in state loading after
rebooting.
CR 27030: ATM.
If the ARE router receives an LE-ARP that was sourced from an end
station with a MAC address of 000000000000, the router experiences
a bus error.
CR 23703: AT.
The router experiences a hogs bufs condition that causes it to
reset a slot because it is unable to allocate a buffer.
CR 27132: IPX.
If a packet contains a network with a hop count of 15, the router
sends RIPs out its other interfaces in periodic updates with a hop
count of 16.
CR 27326: IPX.
The router ages out a routing entry when you set the update
interval on the RIP interface from which the route is learned to a
value of 0 (no periodic updates).
CR 27373: IPX.
Networks learned through RIP occasionally do not age out
correctly even though they have reached the default timers
(180 seconds).
CR 27413: IPX.
Disabling and reenabling an interface on which there are several
(1000, for example) hosts configured will cause these hosts to lose
synchronization across slots.
CR 27613: ATM.
When attempting to join multiple (5) ELANs (on a C100), the
router may not respond to incoming SETUP's (usually from the BUS).
Upon receiving a SETUP, the router's interface waits approximately
4 to 5 seconds before releasing or failing to respond to the
message.
CR 27686: Hardware Compression.
The router experienced a bus error and orphaned buffers when
bouncing a synchronous line running hardware compression.
CR 27695: DLSw.
The Version String control vector in the CAPX message is currently
a null string and does not include any information about the Bay
Networks router. While this is acceptable according to the RFC,
we should be sending this information to help customers identify
the software version.
CR 27713: BOT.
TCP connections do not come up when the Ethernet interface (only
IP interface) is down and then comes back up.
CR 25452: IPX.
A router running router software version 9.02 and later
will process SAPs for only one host at a time. The router responds
to each of the hosts sequentially and will not respond to the next
host until the entire SAP table has been sent to the previous
host. A problem can exist when multiple requests are received and
the router has a large SAP table. Even if a Get Nearest Server
request is received, it will not be responded to until the General
Service Query has been responded to.
CR 27568: Frame Relay.
A problem exists in the router code with a Frame Relay direct mode
PVC running software compression. It is possible for WCP to
enter a state where one end of the PVC has WCP in an
operational state (enabled) while the remote end of the PVC has
WCP in a non-operational state (disabled).
CR 22465: PPP.
SHOW PPP commands do not display correct information for HSSI
circuits if you have configured a multiline for a PPP circuit and
configured at least one PPP circuit over a HSSI.
CR 27608: BOOTP.
Unable to set MIB variables for BOOTP in MIB version 9.00 for
the MIB object wfBootpClientIntfEntry.
CR 27636: IP/RIP.
A problem exists in which the router advertises static routes out
the next hop interface when the RIP mode is set to Poison Reverse
or Split Horizon.
CR 27188: VINES.
The router experiences a bus error when configuring VINES inbound
traffic filters on a synchronous interface. VINES interface never
recovers.
CR 26812: OSPF.
OSPF faults after experiencing a bus error in ospf_extern_comp().
This problem exists only when the router has route policies
configured to ignore OSPF external routes.
CR 27052: IP.
IP fragmentation does not work properly when using SNAP
encapsulation over Ethernet.
-----------------------------------------------------------------------------
Revision 11.00/4 corrects the following problems:
==============================================================================
CR 24662: LAN Bridge and Source Route Bridge.
If a router encounters a slot disconnect, all bridge traffic
generated between the affected slots will terminate.
CR 23512: BOT.
The Bisynchronous and SDLC protocols require the ability to display
and control the following signals via Site Manager or the
Technician Interface in order to simplify troubleshooting:
DTR, DSR, CTS, RTS, DCD.
CR 27009: DVMRP.
When the route threshold is set to a value greater than 1, DVMRP
messages are not sent out an interface.
CR 27017: Switched Services.
A router configured with a primary line and a dial back-up line
may cause Dial Backup to fail because the secondary line may never
dial the modem should the primary line fail.
CR 27117: Switched Services.
The dial backup master configured on an IN router may fail to dial
the modem on the first attempt.
CR 27319: DVMRP.
DVMRP sent probe packets before it had been configured to receive
multicast traffic. As a result, the router learned the wrong
upstream neighbor, causing a loop condition to exist.
CR 25311: BOT.
The Bisynchronous driver fails to indicate that the cable
connecting the router to the controller (CCU) has been
disconnected.
For example:
HOST<----->RTR<------>CLOUD<------>RTR<----->CCU
CR 27419: DLSw.
An active session running on a local device does not disconnect
when you disable the session.
CR 26102: IPX.
An IPX encapsulated NetBIOS packet that is sent from a spoke
router (group mode Frame Relay) to another spoke router will not
propagate to the destination spoke router's LAN. The destination
router will accept the packet and will increment
wfIpxInterfaceInReceives and wfIpxInterfaceForwDatagrams for the
synchronous interface, but the packet will not propagate to the
LAN interface.
CR 25480: IPX.
A router configured with IPX static routes may not forward
packets correctly because of a timing problem that causes a host
entry to be created with the wrong slot information.
CR 27289: ISDN.
PRI cards cannot make two demand calls simultaneously; the second
call appears to establish itself, however, no PPP negotiation takes
place.
CR 27418: DLSw.
After you establish an active session across a network and then
delete a local device associated with this session, the
session fails to disconnect (remains active).
This condition occurs with secondary and primary local devices.
CR None: DECnet.
After you delete a DECnet circuit, disabling and reenabling
the circuit using decnet.bat will disable and enable the wrong
circuit.
CR 26943: DVMRP.
Multicast storms occur when traffic arrives over a tunnel that
you have configured and there is no route through which to
transmit the traffic, or the traffic is destined to be transmitted
out the wrong interface. This condition should cause the router to
drop the traffic, but instead the router floods the
traffic out all interfaces, including the tunnel itself.
CR 27216: Technician Interface.
A bus error occurs when you issue the IP routes command.
CR 27136: IP.
Aggregating Policy may not be followed correctly if a policy
exists for the same network ID with a larger mask.
CR 26924: DLSw.
The router code corrupts DLSw data packets during periods in which
the buffer depletes its memory. The packets become corrupted when
the 16-byte DLSw data frames get inserted between the end of the
TCP header and the start of the DLSw data. This condition causes
the receiving routers to experience tag violations.
CR 26129: MIB.
A problem occurred when attempting to open an 8.12 config file
(with a MIB stamp of 8.10) with SM 4.01/rel in local mode. The
problem exists on both PC/Windows and UNIX Site Manager platform.
CR 27005: OSPF.
A router running router software version 10.00 code in an OPSF
environment in which all other routers run 8.12 code chooses a
higher path cost route. This may cause the router to use
non-optimal routing paths.
CR 22142: IP.
The router may generate an error in IP_rt_cache.c at line 245
when you attempt to add IP routes.
CR 26684: Switched Services/PPP.
BOD monitor stops calling second ISDN number in phone list.
CR 26975: Switched Services.
The router does not use the second phone number in the outgoing
phone list when you have configured a 2B+D line with a pool
channel count of 1.
If you set the channel count to a value greater than 1,
the router will try the second phone number in the outgoing phone
list.
CR 27247: DLSw.
Dynamically adding a local device to a multidrop SDLC line does
not work.
CR 26798: ISDN.
In this scenario, you have configured a demand and bandwidth
pool with two PRIs on two BLN routers and you use packet generator
(pktgen) to bring up the two demand circuits. With all the channels
active and transmitting roughly 80% traffic, disconnect the two
PRIs on the BOD non-monitor side, and then reconnect them. After
all the calls are disconnected and the non-monitor PRIs come back
up, only the demand circuits come up, not the BOD secondary lines.
CR 27212: OSPF.
The wfOspfGeneralGroup.wfOspfPrimarySlot.0 can report the
incorrect primary OSPF soloist slot after OSPF bounces.
CR 27240: DECnet.
After configuring DECnet on a router and then attempting to modify
an interface parameter, the DECnet interface becomes inactive (down
state) and fails to recover.
CR 25842: IP.
Host entries may fail to display when the wfIpNetToMedia MIB table
is queried.
CR 27288: PPP.
Spanning Tree will form a looped environment over a PPP multilink
connection between two routers running router software version
11.00.
CR 19688: DLSw.
DLSw drops non-NameQuery/NameRegisterNetBios broadcast frames that
a router receives in a short interval because of the nature of its
caching system.
CR 27241: IP.
The default AS weight array was not properly initialized,
causing incorrect calculation of AS weights. The array of 8
elements should be initialized to a default value of 8 for all
elements. However, only the first element was set to 8; all other
elements were initialized to 0.
CR 22822: SM-Configuration.
When you select Apply in the IP Interfaces window, the
Enable field becomes blank. The SNMP set occurs without problems,
and when reentering the view the field is set to the correct
value. However, if you try to make a second change, an error
results indicating an invalid value for Enable.
CR 23215: MIB II.
A problem exists in the router code that causes indexing errors in
Frame Relay direct mode PVC's. This affects Network Management
stations, which are unable to map PVC's IP address to Frame Relay.
CR 25483: Switched Services.
The router fails to redial if the first connection attempt times
out before the DCE asserts DSR, but after receiving a connection
indication (CNX) from the DCE.
CR 25558: OSPF.
OSPF adjacency sometimes gets stuck in state loading after
rebooting because the LSA's circulating in the network and are not
being cleared out.
CR 26227: IP.
A bus error occurred in ip_fft when you configure traffic filters
to drop packets for an interface.
CR 26440: Transparent Bridge.
Successive attempts to disable and reenable Learning Bridge
causes the router to eventually fault because of insufficient
memory. This problem stems from a memory leak in the routine
dp_cc_op_act.
CR 26690: Switched Services.
A fault condition in map_rem.c occurs if a slave router receives
a call via Dial Backup while a Primary Direct Mode PVC line
still exists. This condition causes the IP interface on the
specific Direct Mode PVC to remain inactive until you restart the
physical interface.
CR 26842: MCT1.
MCT1 module faults with multiple bus errors and fails to recover
when attempting to boot LN routers.
CR 26937: Frame Relay Switch.
When a logical line is put into Fractional Loopback frames
are dropped.
CR 27012: IP.
Running an unnumbered IP interface on a PPP line with circuitless
IP as the associated address caused the router to fault when IPCP
becomes active.
CR 27193: IPEX.
X.25 cannot detect that the client gate is disable, causing
X.25 SVC to remain active even though the client is gone.
Eventually all X.25 SVCs are used up without any client using
them, and no subsequent calls are made.
CR 23251: DLSw.
Disabling TCP on a BLN router that is configured as a
single-switch disconnects and then reconnects sessions while TCP
remains disabled. Since the sessions all reconnected and work
while TCP was disabled, it would appear that TCP is not needed in
a single switch configuration.
CR 23427: DLSw.
CR 25123 A bus error occurred in dls_flow_tcp_busy after disabling DLS
on a remote router. The remote router is a BCN. The BCN's SDLC
lines are configured as Primary. This error occurs if there is no
configured slot IP address in DLS.
CR 24875: Source Route Bridge.
When the router switches to the backup line and then later
switches back to the primary line, source route frames get
dropped.
CR 25350: APPN.
APPN interfaces do not activate after rebooting a router.
CR 25521: IP.
Panic occurred when making a dynamic change to OSPF Max Path.
CR 25525: MCT1E1.
Removing the cable does not report 'Loss of Signal' in the
expected threshold.
CR 25760: SDLC.
DLC multidrop with equal SAPs functions improperly.Occassionally,
all the link stations establish sessions successfully while on
other occasions only one link station establishes a session.
CR 25885: DLSw.
A bus error occurs when attempting to establish a DLS/SDLC
connection to one particular link station. This condition can be
attributed to the configuration of a duplicate local device.
CR 25899: IP.
Unable to boot router with 600 interfaces configured.
CR 25968: TCP.
Enabling and disabling TCP may place the TCP connection
in a closed state, from which it never recovers.
CR 25986: TCP.
When a client issues a Telnet session to a network address of
which the router is a subnet, the router attempts to establish a
Telnet session, but the local memory allocated to this process is
never returned when the session ends. The log clearly indicates
the Telnet/TCP session initializing, but does not indicate that
the session has ended. As a result, a memory leak occurs.
CR 26209: IGMP.
The router received the following error upon boot up:
"IGMP RTBL Delete Failure"
CR 26222: SDLC.
Bus error in sdlc_disconnect_send_msg on slot 8 during scaling
testing where there were 12 primary SDLC devices per port on all
ports. This bus error would repeat every 3 to 20 minutes.
CR 26314: IGMP.
CR 26326 Tag violation occurs when dynamically configuring IGMP static group.
CR 26341: Frame Relay Switch.
The default settings need to be adjusted when more than 12MB of
buffers space is available.
CR 26362: IP.
Unable to forward IP traffic over a backup link because an error
occurred while switching over from a primary to a backup line.
This happens only when primary and backup lines are located on
different slots.
CR 26380: IGMP.
The command "SHOW IGMP GROUPS" fails after you configure a static
group. An instance for the group exists but contains no associated
MIB entry.
CR 26414: ISDN.
French delta PRI TC30007 and TC30008 tests failed because the
router ISDN did switch to the IDLE state upon receipt of
a SETUP with an incompatible party number or subaddress.
CR 26487: DVMRP.
The router will accept route updates from an unknown neighbor
provided the source IP address of the update resides on the
correct network. DVMRP should not send route updates
before sending probe packets, and DVMRP should not accept route
updates from an unlearned neighbor.
CR 26561: APPN.
DLU sessions fail to recover if a router or host in the session
path is down for a long period of time (7-10 minutes).
CR 26630: DLSw.
A router experiences a bus error when attempting to reestablish
a DLS connection.
CR 26637: IP.
FTP may hang when transferring data over slow links.
CR 26807: SDLC.
Unequal SAPs cause link stations to fault and not recover when a
host line is disabled and then reenabled.
CR 26847: DLSw.
A problem exists with DLS connections recovering after rebooting
a router or after resetting a slot. The cur2 timer and number of
retries never started after the cur1 timer and number of retries
expired.
CR 26872: IP.
When you delete a circuit configured with IP and TCP, the router
faults when no other circuit on that slot is configured with IP.
CR 26918: APPN.
An APPN/DLUR link station does not establish a connection when the
router is configured as DLUR and then booted.
However, it does establish a connection after you issue the
"APPN ENA LS" command.
CR 26919: SDLC.
In the below network, PC3270 sessions fail to recover
after disabling and enabling the wfSyncEntry instance for the
Frame Relay port on a router configured with Primary SDLC
ports. This problem occurs because the remote/primary SDLC router
does not send out the XID null frames onto the Frame Relay line and
the host/secondary SDLC router does not send out a DISC request
to the host after the frame relay port on the host router notices
that the primary router stops polling the host router.
host remote
host -- sdlc -- router --- FR 1490 --- router -- sdlc -- PCs
CR 21216: MCT1E1.
Poor ds1e1.bat performance when listing multiple logical lines.
The ds1e1.bat script file uses instenv to retrieve all logical
lines instances.
CR 24821: X.25.
When X.25 processes a connect indication and you have not enabled
the flow control negotiation parameter, X.25 rejects all facility
code. The flow control negotiation parameter is limited to
packet and window size only.
CR 25591: Translation Bridge.
RIF entries on a Token Ring segment may fail to age properly.
CR 25940: SYNC.
The driver goes mute under certain traffic patterns because of an
interrupt race condition in the asynchronous driver.
CR 26182: MIB.
Running 8.01 rev 7 on ANís and 8.01 rev 8 on ASNís, the MIB
variable ipAdEntReasmMaxSiz reports a value of 0 (about 50% of the
time) when it should report a value of 1598.
CR 26247: APPN.
APPN attempts to connect to a link station 10 times (its fixed
limit) before it times out. This problem occurs with APPN over
SDLC when SDLC tries to bring up the link station 10 times before
timing out and alerting APPN. If APPN reaches its limit of 10
retries, it deletes the link station.
CR 26269: DLSw.
A test frame received by a router on a Token Ring is sent as a
CANUREACH to the router's DLS peer. The peer sends a LLC test poll
explorer frame as a single-route broadcast (STE). A request has
been issued to be able to specify STE's or ARE's (all-routes
explorer frames), on a per-interface basis.
CR 26364: APPN.
You cannot enter a host name consisting of 17 characters
when issuing an APPN ping at the Technician Interface prompt.
You should be able to enter up to 17 characters for an APPN
host name.
CR 26370: DCMMW.
Both etherHistoryTable and logTable return inconsistent instances
when the router issues a genNextRequest command.
CR 26537: DLSw.
An orphan buffer occurs when a DLS connection disconnects and
then attempts to reestablish itself. The DLS disconnection can
be caused by disabling and reenabling TCP, DLS, or physical
circuits.
CR 26751: Frame Relay.
Frame Relay Dial Backup experiences a problem in which traffic
will not forward out on a backup link on the slave router. This
condition occurs only when you intentionally disable the
Sync Driver on the Frame Relay circuit from the master side.
CR 26813: DLSw.
A bus error occurs when you attempt to vary SSAP and DSAP for
DLS local devices.
CR 18837: BOOTP.
In a multinetting environment, the router chooses the last address
added to the multinetted interface as the BOOTP gateway. If you
disable BOOTP for that address, the router continues to use this
address as the BOOTP gateway instead of selecting the next
address in the network configuration as the new BOOTP gateway.
CR 24049: LNM.
When unlinking an IBM LNM Manager from a Token Ring interface,
the router generates incorrect LNM link status for the MIB variable
wfLnmInterfaceEntry. When you unlink the LNM station,
the LNM link status should reflect a "nil" value, rather than
retain the previous MAC address of the IBM LNM Manager station.
CR 24365: DLSw.
A new DLSw feature has been introduced that will allow you to
enable or disable NetBIOS session alive frame transmissions.
Previously, a NetBIOS session would always transmit session alive
frames over DLSw every 30 seconds. These session alive frames
could cause lines to remain active unnecessarily, possibly
increasing the usage cost of the line.
Use the Technician Interface to enable or disable NetBIOS session
alive frame transmissions. To enable the NetBIOS session alive
filter, stopping session alive frame transmissions, issue the
following Technician Interface command:
set wfDlsNetbiosSessionAliveFilter.1
To disable the NetBIOS session alive filter, allowing session
alive frame transmissions, issue the following Technician
Interface command:
set wfDlsNetbiosSessionAliveFilter.2
CR 25759: ISP.
MIB allocates an insufficient amount of cache space when attempting
to send information to other slots on a router.
CR 26199: ATM.
The ATM signalling UME faults when it receives a Get-Request
for the UNI version ILMI object.
CR 26258: PPP.
The following problems related to PPP/Mulitlink
interoperability were discovered:
1. If a valid PPP/ML encapsulated NCP packet arrives with a
Protocol ID that is not supported by our routers, we must
send an LCP level Protocol-Reject packet.Currently we are
discarding these packets, which does not comply with the
the PPP RFC.
2. The router faults when the size of the peer's CHAP challenge
is larger than 50 bytes. There were at least two vendors that
sent CHAP challenge size larger than 50 bytes.
CR 26346: LLC.
Using the g_timer_read() causes the timer to expire early. This
leads to multiple SABME's sent, causing sessions to disconnect.
CR 26371: DCMMW.
The router restarts when it runs out of memory while alarm/events
traffic is being transmitted through DCMMW's RSAA.
CR 26406: IPX.
A request has been issued to add the capability to display Dial
Opportunity Routing circuit information.
CR 26485: IPEX.
The "SHOW X25 CONFIG" command fails to indicate that an IPEX
service is available after you configure IPEX.
CR 26486: IPEX.
When you configure 1980 as the CCITT conformance parameter, the
script shows 1980, 1984, and 1988. This is incorrect and displaces
the remaining statistics being displayed.
CR 26515: IPEX.
An IPEX call is routed to the wrong IP address when using wildcard
addressing.
CR 26527: Frame Relay.
When you specify DLCMI "None" and then reset compression, the
DLCMI gate may receive an invalid frame.
CR 26404: Switched Services.
An incorrect line in the router code causes a flag to be set
that erroneously indicates that the modem is down when it is
in fact operational.
CR 26790: Technician Interface.
When issuing the IP routes command, the router displays invalid
data for the total networks number if you have compiled set memory
debugging and wrt_thru into GAME.
CR 27045: FTP.
After an unsuccessful log in attempt, FTP does not behave properly.
CR 27479: DLSw.
A NetBIOS name query is sent through a router to its destination
but the destination fails to respond. Subsequent name queries sent
less that 5 seconds apart are dropped.
------------------------------------------------------------------------------
Revision 11.00/2 corrects the following problems:
==============================================================================
CR 26996: DLSw.
When using TCP to establish multiple TCP connections
(50 plus) using DLSw 1795 mode, the router occasionally ignores
the CAPX response, causing the TCP peer connection to use
1434 mode.
CR 26702: LAPB.
Added a third option (activeDisc) to the MIB object
wfLapbEntry.wfLapbActionInitiate to enable LAPB to send a DISC
command as the initial frame after establishing a physical
connection to non-X.25 compliant IBM 5394 and 5294 controllers.
You can configure this option from Site Manager or from the
Technician Interface. From Site Manager, set "Initiate Link Setup
Action" on LAPB screen to ACTIVE DISC. From the Technician
Interface, set the MIB object
wfLapbEntry.wfLapbActionInitiate to 3 (activeDisc).
CR 27012: IP.
Running an unnumbered IP interface on a PPP line with Circuitless IP
configured as the associated address caused the router to fault
when IPCP becomes active.
CR 27023: SDLC.
When you attempt to boot an SDLC session, a full connection is
never established and the session eventually disconnects.
CR 27064: TCP.
When trying to establish a DLSw connection to an IBM 2210 router,
the Bay Networks router receives a DLSw CAPx message from
the IBM router, but fails to send a message back to the IBM router.
CR 26654: DLSw.
A TCP connection in 11.0 rel was consuming more memory than
required.
The following is a known anomaly associated with rev/11.00/2 software:
-----------------------------------------------------------------------------
Anomaly: SNA session connects but fails to transmit data
Number: N/A
Description: In a dual switch environment where SDLC is configured
on a Token Ring host or Ethernet host, an SNA session
connects but fails to transmit data. This problem
can be attributed to a flow control problem tied to the SDLC
1795 code.
Workaround: Bouncing the synchronous line on a router that is
connected to the SDLC station will establish a
connection to the SNA session and permit the
transmission of data.
------------------------------------------------------------------------------
=============================================================================
Revision 11.00/1 corrects the following problem:
==============================================================================
NOTE: Revision 11.00/1 is managed by rel/5.00 and/or revision 5.00/1.
Revision 5.00/1 is necessary to properly manage the new MIB attribute
in revision 11.00/1, but otherwise rel/5.00 will work as usual.
-----------------------------------------------------------------------------
CR 26702: LAPB.
Added a third option (activeDisc) to the MIB object
wfLapbEntry.wfLapbActionInitiate to enable LAPB to send a DISC
command as the initial frame after establishing a physical
connection to non-X.25 compliant IBM 5394 and 5294 controllers.
You can configure this option from Site Manager or from the
Technician Interface. From Site Manager, set "Initiate Link Setup
Action" on LAPB screen to ACTIVE DISC. From the Technician
Interface, set the MIB object
wfLapbEntry.wfLapbActionInitiate to 3 (activeDisc).
}ˇ
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
