Revision Notes for Router v10.01 rev 5
============================================================================
SITE MANAGER COMPATIBILITY
=============================================================================
Router Version is managed by Site Manager version
v10.01 revision 1 --------------------------> V4.01, 4.00 rev 2
v10.01 revision 2 --------------------------> V4.01, 4.00 rev 2
v10.01 revision 3 --------------------------> V4.01, 4.00 rev 2
v10.01 revision 4 --------------------------> V4.01, 4.00 rev 2
v10.01 revision 5 --------------------------> V4.01, 4.00 rev 2
------------------------------------------------------------------------------
Revision 10.01/5 corrects the following problems:
=============================================================================
CR 27247:
27251: DLSw.
Dynamically adding a local device to a multidrop SDLC line does
not work.
CR 27052: IP.
IP fragmentation does not work properly when using SNAP
encapsulation over Ethernet.
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 27419: DLSw.
An active session running on a local device does not disconnect
when you disable the session.
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 26467: APPN.
A tag violation occurs when you attempt to ping a router configured
with APPN over SDLC.
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 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 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 25918: Switched Services.
In certain situations, the Raise DTR modem will not attempt
subsequent retries if the initial call fails.
CR 17269: BOOTP.
The wfBootpRelayFulEntry interface attributes are zero until
forwarding occurs.
CR 17283: BOOTP.
When you configure a router using Site Manager, the router will
not update the Preferred Server IP addresses.
CR 19940: MIB.
The MIB attribute wfHwEntry.wfMotherBdRev is incorrectly stored in
decimal instead of hexadecimal.
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 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 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 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 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 26912: PPP.
An error exists in scripts associated with router software version
8.12 and later. This error prevents you from accessing the MIB
variable wfHssiEntry.wfHssiActiveCct when you run the SHOW PPP
CIRCUITS command on a HSSI interface. This problem occurs because
the MIB entry wfHssiActiveCct does not exist.
CR 27608: BOOTP.
Unable to set MIB variables for BOOTP in MIB version 9.00 for
the MIB object wfBootpClientIntfEntry.
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 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.
CR 25087: IP.
When configuring an IP traffic filter to accept destination TCP
port 23 (Telnet), and to drop all other TCP ports, the accept
filter does not get executed. This problem is specific to the ARE
router.
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 26293: Technician Interface.
The help for the log command contains no mention of the -x
argument.
The "log" command in the Technician Interface contains a feature
that disables the logging of events (as opposed the display of
the logged events). This is accomplished by using the -xargument to
the log command, in combination with other arguments, such as
-e, -s, -f, to specify the events being
disabled.
CR 27620: ATM.
After telnetting into an ATM slot (ARE/0C3) and attempting to
disable or enable an Ethernet circuit on another slot (for example,
disable csmacd conn 1.1), the ATM slot fails with an exception
vector 5 - VBM error recorded in the event log.
CR 27822: DLSw.
When DLSw builds a XID-F based on the received XID-P, the XID data
is copied to the LLC header portion of the buffer rather than to
the position following the header.
CR 27972: SNMP.
The router will attempt to generate authentication failure traps
when queried by network management stations that support the
SNMPv2C protocol. SNMP should just discard the message and
increment snmpInBadVersions.0.
CR None: SDLC.
A link station fails to connect after deleting a local device and
adding a new local device.
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 21979: TCP.
During IPEX testing of flow control through TCP it was determined
that the xmit echo sequence counter was being updated locally and
not from the remote TCP peer. This caused the local peer window
to open and the remote peer window to close.
CR 22005: TCP.
When the client acknowledges received data, TCP does not
consistently send a window acknowledgment back to the peer. This
causes the transmission of data to stop.
CR 22007: TCP.
TCP window update is not passed to IPEX client consistently.
Apparently, TCP is waiting to be polled by the client.
CR 22009: TCP.
TCP was incorrectly fragmenting packets transmitted from IPEX.
CR 22012: TCP.
When the TCP sending client tx window is full, data is fragmented
and data loss is detected by the receiving client. This results in
a client fault at the receiving end.
CR 22016: TCP.
TCP will intermittently retransmit message blocks continuously, and
remains in this retransmission loop. In this state, TCP does not
pass data to the client.
CR 22019: TCP.
TCP will retransmit multiple messages simultaneously, thereby
consuming the majority of the bandwidth on the WAN link.
CR 22446: TCP.
The router faults at the remote TCP connection when packets whose
size is 64 bytes or less are transmitted to IPEX.
CR 23899: TCP.
A fault occur occurs in "error in tcp_xmt.c at line 366" when the
remote wfSyncEntry is bounced and data is being passed.
CR 24916: IPEX.
The router faults with the following TCP error: "error in
tcp_xmt.c at line 366".
CR 26654: DLSw.
A TCP connection in 11.00 rel was consuming more memory than
required.
CR 28072: Source Route Bridge.
A router configured to run source routing bridge (SRB) with SRB
traffic filters may drop Specifically Routed Frames (SRFs)
randomly.
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 28067: SYNC.
If you configure a BCN router for Standard WAN protocol and set
the wfSyncEntry.wfSyncLocalAddress and/or the
wfSyncEntry.wfSyncRemoteAddress MIB object to 48 or greater, a bus
error will occur when you run the embedded SHOW SYNC scripts.
CR 28134: ST2.
ST2 connection bandwidth allocations will not be cleaned up when
only one line of a multiline circuit goes down.
CR 27402: Frame Relay.
When running partial frame relay switch, loss of a physical or
logical link goes undetected.
CR 28039: LLC.
When you dynamically delete a 11c circuit that you configured with
Frame Relay, a bus error occurs.
CR 27533: ATM.
A problem occurs in 10.01 rev 3 in which an ATM slot resets under
heavy traffic conditions and under heavy CPU utilization.
CR 25558: OSPF.
OSPF adjacency sometimes gets stuck in state loading after
rebooting.
CR 27005: OSPF.
A router running software version 10.00 code in an OSPF
environment in which other routers run 8.12 code may choose a
higher path cost route over OSPF point-to-point interfaces. This
may cause the router to use non-optimal routing paths.
CR 28003:
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 27651: IPX.
The IPX routing tables show incorrect routes or routes with
inflated costs.
CR 27866: OSPF.
In an OSPF multiarea environment, some networks from one area may
not be visible in the routing tables of routers in other area(s).
CR 27900: AT.
A problem exists in the 10.00 router code that prevents AURP
from forwarding traffic after introducing a network change that
would force one AURP tunnel to go down and another to take over.
This results in loss of AppleTalk connectivity.
CR 28153: Technician Interface.
When running SHOW CIRCUIT STATS when specifying one individual
circuit, a tag violation occurs on the slot on which the circuit
resides.
CR 28200: OSPF.
An Area Border Router may fail to properly summarize routes when
attached to more than two areas. This occurs because their type
3 network summaries had been managed incorrectly.
CR 28296: BOOTP.
When you set the broadcast bit in a BOOTP reply packet, the router
as a relay agent sends the packet with an IP broadcast address
(which is correct) and the client hardware address (which is
incorrect; it should be a broadcast address according to RFC
1541).
CR 28781: DLSw.
If a DLSw/TCP connection gets congested, it will issue an
"ENTERBUSY" signal for the connections which need to send data.
When the congestion has abated, DLSw should issue an "EXITBUSY"
for all connections it put into "ENTERBUSY". If there are more
than 20 connections put into "ENTERBUSY", the router will fail to
bring the 21 connection out of EXITBUSY. The connection remains
like this until the client is reset.
CR 25351: DLSw.
When a DLS Mac entry is cached (for example when a test poll was
received from that MAC address), creating an instance of
wfDlsDefaultMacEntry for that MAC peer address causes a fault.
CR 27299: DLSw.
When you dynamically delete a DLS default NetBIOS peer instance,
errors occur in mib_ent.c.
CR 27806: IP.
An X.25 IP-peer (adjacent host) is unreachable after X.25 packet
level was down in an OSPF environment in which the OSPF type for
the X.25 IP interface is Point-to-Point or Point-to-Multipoint.
As a result, the OSPF neighbors cannot exchange their tables.
CR 28364: OSPF.
OSPF Adjacencies over PtoP (or PtoMP) will remain FULL after
bidirectional connectivity is lost.
CR 28423: Telnet.
Under heavy load conditions, TCP may fail to register TCP clients
for certain IP interfaces once the interfaces become active.
CR 27088: Technician Interface.
Enhancement request to use a wildcard to shorten the list of
MIB objects returns. Use "list wfIpx*" to return all MIB objects
that begin with wfIpx. This command is case sensitive.
CR 27965: IPX.
29317:
28078:
IPX fails to upgrade a NetBIOS static route when the 8.12 router
software version instance ID is a length of 9. If a special
character exists in a pre-9.00 configuration, a "\" character
should be prepended to the special character. Also, if a name is
less than 16 characters, append an asterisk (".*") to the end to
account for functionality prior to router software version 9.00.
CR 23591: DLSw.
The MAC and NetBIOS cache would not age out correctly.
CR 28680: OSPF.
Internal cost is not compared when two LSAs give equal OSPF type 2
cost to the same destination.
CR 29529: OSPF.
When you attempt to bounce IP in two remote AS boundary routers, a
bus error occurs.
CR None. ARE.
An ARE fails to ping to a device attached to an IBM 8260 in
LAN emulation.
CR 28291: AT.
When you configure multiple tunnels, AURP will forward
AppleTalk frames out the wrong tunnel.
------------------------------------------------------------------------------
Revision 10.01/4 corrects the following problems:
=============================================================================
CR 26102: IPX.
A router configured with NetBIOS static routes in a hub and spoke
environment does not forward traffic. These IPX encapsulated
NetBIOS packets, which are broadcast from spoke router to spoke
router, are dropped because the network address of the receiving
interface is contained in the list of network addresses resident
in the packet.
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 25480: IPX.
A 16-character server name in the IPX encapsulated NetBIOS packet
can cause the name matching routine to fail.
CR 25968: TCP.
Enabling and disabling TCP may place the TCP connection
in a closed state, from which it never recovers.
CR 25291: MIB II.
The fainter MIB object contains two attributes, affinities 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 both the synchronous interface
statistics contained in a multiline interface.
CR 26687: MIB II.
While using the SNMP manager, the MIB-11 attribute ifEntry.5
(speed) does not return the aggregated line speed of a
mulcting circuit.
CR 27489: Switched Services.
A bus error occurred after the primary circuit in backup mode is
terminated on the slave side.
CR 27243: Loader.
When unloading run.exe and sh_ip.exe simultaneously from the same
slot, the router experiences the following error:
Error: exception vector 2 - Bus error OR (2) Watchdog expired,
service terminating.
This condition occurs after automgr.bat or autouser.bat is
loaded on a slot and the SHOW IP routes (embedded script) is
executed via a Telnet session. If the Telnet session if forced to
terminate prior to the completion of the SHOW IP routes script,
the slot configured for IP in the Telnet session faults.
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 26637: IP.
FTP may hang when transferring data over slow links.
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 26943: DVMRP.
Mutilates 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 27039: MCT1E1.
If the router sends inverted data to a QMCT1 and you reset the
slot, the port will remain in a red alarm state.
CR 27120: DLSw.
SDLC tests on the DLS hurdle consist of a BLN router connected
to APPN HOST BLN via DLS over Token Ring. SDLC cannot
establish a link with DLS, causing all three (3) SDLC-related tests
on the DLS hurdle to fail.
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 27212: OSPF.
The wfOspfGeneralGroup.wfOspfPrimarySlot.0 can report the
incorrect primary OSPF soloist slot after OSPF bounces.
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 27045: FTP.
The FTP command displays the wrong command entries.
CR 25618: Technician Interface.
When issuing the SHOW CIRCUIT BASE command, the Technician
Interface enters into a loop condition in which it displays
circuits on the screen repeatedly until you intervene.
CR 25635: Technician Interface.
The SHOW CSMACD BASE CIRCUIT command does not list circuits if
you change the circuit name from its default name.
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 zero, and
a traffic filter is created for network zero, the router ignores
the traffic filter.
CR 27470: IPX.
System performance degradation may occur because the "lost route
algorithm" was executed unnecessarily.
CR 27055: IP.
If the sending host sends multicast data with the IP fragment bit
set, the IP-forward-to-IP-address filter does not retain the
IP fragment bit, and assigns different IP sequence numbers.
CR 26885: IP.
After booting the router, several OSPF routes were missing from
each slot, except for the OSPF soloist slot. During the route
update process, IP may have skipped over a group of routes
because its RNP queue was being modified before IP completed
processing all routes.
CR 25842: IP.
Host entries may fail to display when the wfIpNetToMedia MIB table
is queried.
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 27474: VINES.
VINES experiences a bus error when it unsuccessfully attempts to
allocate a buffer and then attempts to free the same buffer.
------------------------------------------------------------------------------
Revision 10.01/3 corrects the following problems:
=============================================================================
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 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 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 25956: IPX.
The initiation of IPX RIP and SAP updates are staggered so that
SAP updates start after a time delay of half the RIP update
period. If you fail to configure RIP, then the value used to
initiate the SAP updates may be incorrect, thereby preventing SAPs
from being sent.
CR 21151: DVMRP.
In a route loop topology, the non-dominant router rejected routes
on the wrong interface.
CR 23779: DVMRP.
In a route loop topology, the non-dominant router accepted the
multicast data from its dominant router and deleted the cache
entry on the correct VIF, thereby causing DVMRP to fail.
CR 24985: DVMRP.
A nexthop address of 0.0.0.0 sometimes appears in the DVMRP
routing table, thereby causing DVMRP to fault.
CR None: LLC.
The presence of the g_timer_get_read() variable caused the timer
to expire prematurely which led to the transmission of multiple
SABME's. This condition caused sessions to disconnect.
CR 23215: MIB II.
A problem in the router code causes indexing errors to occur
in Frame Relay direct mode PVC's. This problem affects network
management stations in particular, which are unable to correlate
IP addresses to their corresponding Frame Relay direct mode PVC's
in network management maps.
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 26441: BNX SWITCH.
A T1 port can be suspended in a loopback state. The only way to
disable this state is to bounce the port.
CR 26296: DLSw.
A router configured on a Token Ring network receives a test frame,
which it sends as a CANUREACH to the router's DLS peer.
The peer sends an LLC test poll explorer frame as a single-route
broadcast (STE) only. A MIB variable has been created that allows
you to send STE's or ARE's (all-routes explorer frames) to each
interface.
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 23695: DLSw.
When you deactivate the line from the host, and then reactivate
it, the DLSw connection to the controller does not come up. The
log shows the disconnect message transmitted out to the AN router,
but fails to show the router's response. To activate the line, you
must bounce DLSw on the remote AN.
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 26791: DVMRP.
The non-dominant router sends a graft upon receipt of a IGMP host
join message. This results in duplicate packets being forwarded
to the LAN.
CR 26825: DVMRP.
Bay Networks routers do not accept route updates from unknown
neighbors. Because Cisco routers do not send DVMRP probe messages
over a tunnel, Bay Networks routers will drop all route updates
and multicast traffic transmitted from the Cisco routers. A switch
must be added to allow accepting route updates from unknown
neighbors.
CR 26853: DLS.
A recovery problem occurred after disconnecting/reconnecting the
SDLC lines to the PU or the host on an SDLC-to-SDLC connection.
CR 26842: MCT1.
MCT1 module faults with multiple bus errors and fails to recover
when attempting to boot LN routers.
CR 23288: IGMP.
A fault occurs in igmp.misc.c when attempting to create a new
IGMP interface.
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 26885: IP.
After OSPF goes down one slot and comes back on another slot,
some IP routes may be missing on one slot (the old OSPF soloist
slot), and all other slots are pointing to the old OSPF slot as
the author of that route.
CR None: Frame Relay.
Frame Relay-ATM network interworking required support allowing many
DLCI's to map to the same VCID.
CR 25885: DLSw.
CR 25929 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 26593: DLSw.
PUs can fail to activate in a manner that results in
NCP status code PAPU2 after you execute a prescribed sequence
of actions. This sequence of actions can be cleared only by
a NetView operator.
CR 25849: SDLC.
The primary FRAD inexplicably fails to issue DISCs to all
configured remote devices. For example, when you configure 3 PUs
with link station addresses 01, 02, and 03, the FRAD initially
sends DISCs for all three, but after all three failed to respond,
FRAD stops sending DISCs. Then when 03 eventually responded, the
FRAD still failed to send a DISC for it. Resetting the slot caused
the FRAD to begin sending DISCs for PU 03, but not for 01 and 02.
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 None: SNMP.
When setting multiple VARs in one PDU that includes display
strings, the SNMP agent sets the value of the strings to the
correct length, but truncates the last three to four bytes.
CR 26192: MIB.
The configuration file for the ASN router (ti_asn.cfg) supplied
with all versions of 10.00 (rel through 10.00 rev4) has a 9.00 MIB
version.
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 25123
CR 23427: DLSw.
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 27063: DLSw.
The router generates the following log message too frequently:
"received an SSP command in TCP local"
CR 27087: IPX.
An ARE router constantly resets when IPX is configured within any
ATM Service Record. The problem has been seen in both a PVC and
LANE configuration where IPX is configured on the ARE and at least
one other slot on a BLN or BCN router.
CR 26440: DataPath.
Successive attempts to disable and re-enable 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 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 27140: IP.
A problem occurred when routers running OSPF learned the same
external network with two different masks (the more specific mask
learned by RIP being injected into the OSPF cloud; the less
specific mask via a static route). Then when the RIP network is
disabled, the more specific route gets flushed out of the
OSPF lsdb, and IP points to a disabled interface as the next valid
hop.
CR 26129: MIB.
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. Problem
exists on both PC/Windows and UNIX SM platform.
Added support for the following IPX MIB attributes to ensure
backward-compatibility for the Site Manager IPX MIB.
wfIpxBaseNetSizeBoundEn
Allows you to enable or disable the maximum allowable size of the
network table.
wfIpxBaseMaxNetTblSize
Allows you to specify an integer that determines the maximum
allowable size of the network table.
wfIpxBaseNetTblFillNotify
Allows you to specify an integer from 1 through 100 that
notifies you when (configured) percentage is reached.
CR 20940: Redundancy.
A router experienced a bus error when Router Redundancy received
corrupted frames and attempted to process the frames as multiple
Router Redundancy PDU fragments along with SNMP frames.
CR 26268: BNX Switch.
Congestion control was not setting FECN and BECN on trunks
correctly.
------------------------------------------------------------------------------
Revision 10.01/2 corrects the following problems:
==============================================================================
CR 26969: DLSw.
Test polls generated by running a TCL script in a dual switch
DLS network causes the router to fault with tag violations.
-----------------------------------------------------------------------------
Revision 10.01/1 corrects the following problems:
==============================================================================
NOTE: Revision 10.01/1 incorrectly referenced CR 25249. The correct CR
number is 24249, as documented in the 10.01/1 revision notes.
-----------------------------------------------------------------------------
CR 23065: IP.
Attempting to boot an ASN router configured for IP host-only may
cause a tag violation to occur.
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 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 26452: GAME.
A g_fwd may fail before the slot has discovered that the remote
slot has gone down. This results in a panic as the sending slot
thinks the remote slot should have received the buffer because
it is still in its slot mask.
CR 25591: Translation Bridge.
RIF entries on a Token Ring segment may fail to age properly.
CR 24346: Translation Bridge.
Disabling the Translation Bridge base results in bus errors when
transferring files back and forth to an end station on an
Ethernet segment from an end station on a Token Ring segment while
multiple SRF's are being received simultaneously.
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 25126: MCT1E1.
The Munich driver mail may fail to transmit all frames, except
interrupt queue frames on the priority queue. This problem occurs
only on logical lines with high error rates.
CR 24714: OSPF.
When you configure two AN routers across a synchronous interface
with a MTU size of 4608, OSPF adjacencies can take up to 20
minutes to form. The AN router receiving the Data Base Description
packets remains in the loading state while the router sending this
information will be in the full state.
CR 19711: Scripts.
The SHOW HARDWARE SLOT command generates too many columns on a
screen, causing Link Serial Number of 1346 wraps on an 80 column
display down to the next line. For example:
[1:1]$ show hardware slot
Hardware Information per Slot
-----------------------------
Slot Processor Processor Processor Link Link Link
Module Revision Serial No. Module Revision Serial No
------ ------- --------- ---------- ------------ -------- ------
1 Access Node 129 00000542 module#1045 2147483777 134
6
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 22792: IP.
Within IP traffic filters, for any rule that has a log action,
the router logs an entry. Only the rule with the highest
procedure should be performed.
CR 23340: LLC.
The router may fault with the following error during a test poll
storm:
"Error in Buffer.c at line 157"
CR 24142: IP.
The router faults after receiving corrupted ICMP packets that have
an IP length that exceeds 65,000 bytes.
CR 25569: DLSw.
A Windows NT/NetBIOS session may randomly fail to establish through
DLSw whenever the server and the client pick up the same local
session ID for the session they are attempting to establish.
CR 25656: GAME.
The first day of each month the clock on the AN router shifts by
one extra day. As a result, the Frame Relay circuit on the router
disconnects, preventing the router from sending LMIs to the
switch. This condition also has caused the clock to stop
temporarily.
CR 24249: FRE-2.
If you plug an incorrect console cable/connector into the SRML
module of a running BN router, the LED's located in the front of
the FRE's suddenly stop blinking, indicating that the router is
inoperable. The lights resume normal operation when you remove
the console connector.
CR 25844: DLSw.
Playing a test poll storm in a dual switch configuration
causes a watchdog to occur on the adjacent router.
CR 24048: LNM.
An IBM LAN Network Manager station intermittently fails to
establish a link to a Token Ring interface. This situation occurs
only when the Token Ring interface was previously linked and then
unlinked from another LNM station.
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 25418: DLSw.
When you issue a "get wfDlsSlotEntry.*.5" command from the
Technician Interface, the router generates invalid information
for the MIB variables .wfDlsCurrentMemory and .wfDlsHiWaterMark.
CR 25805: NVFS.
Compacting Series 2 Flash cards (especially Epson Seiko Flash
cards) can occasionally corrupt file systems.
CR 25956: IPX.
IPX may stop sending IPX SAPs if you have not configured IPX RIP.
CR 24311: IPX.
If IPX tries to send IPX update messages to busy slots, it may
fault because of a g_fwd failure.
CR 25867: DLSw.
A router running with hundreds of DLS connections may fault with
the following error because a buffer is being freed erroneously:
"Error in Buf.float.c at line 114"
CR 24821: X.25.
When X.25 processes a connect indicate 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 26107: Frame Relay Switch.
Excess burst is not being calculated correctly, causing frames
that exceed excess burst to be dropped at the ingress; the
data does not exceed excess burst. Excess burst
uses the large default that should never be exceeded.
CR 26139/
25737: Frame Relay Switch.
When one Navtel is configured to send packets at 256 bytes, and the
second Navtel has a packet size of 32 or lower, the traffic
stops. Traffic resumes when the packet size is increased to a
value of 64 or higher.
CR 26118: Frame Relay Switch.
When creating multiple mappings for the MIB attribute
wfCctOptsCngcEntry, the first map fired and deleted all the
structures and the second map tried to use invalid memory. This
caused a tag violation to occur.
CR 25846: OSPF.
After OSPF's Dykstra algorithm runs for 65,535 tries, OSPF faults
with the following message: "LSA in UNEXPECTED STATE".
CR 26163: MCT1E1.
When selecting an unused QMCT1 or DMCT1 interface in Site Manager,
the Link Module Fail LED lights up. When you reboot the router,
the fail LED's on both the QMCT1 and Dual MCT1 link modules turn
off.
CR 25900: MCT1E1.
On a router configured with IP over PPP, with 64-byte packets
using one slot with 48 logical lines, the QMCT1 is unable to
utilize 85 percent of the 128K line.
CR 26230: DLSw.
If SDLC secondary disconnects, and the router reaches a
CANUREACH state during this period, DLS never reestablishes.
CR 25351: DLSw.
When a DLS MAC entry is cached (for example, when a test poll was
received from that MAC address), creating an instance of
wfDlsDefaultMacEntry for that MAC address may cause the router to
fault.
CR 20516: LLC.
Disabling a DLS interface on a Token Ring network while it is
transmitting and receiving DLS traffic causes a watchdog timeout
to occur in llc.
CR 21715/
22160: DLSw.
A watchdog timeout occurs in DLS after disabling the DLS base
record. If you have multiple SAPs configured (for example, all 127
possible SAPs), DP takes too long to deregister SAPs when DLS
shuts down.
CR 23591: DLSw.
Establishing a DLS over SDLC connection may take a long time
because of a delay in the transmission of CANUREACH.
CR 24959: MCT1E1.
When listing the instances of the MIB variable
wfDs1E1BertStatsEntry, the listing succeeds intermittently for
port 1 but fails to succeed for subsequent ports.
CR 25119: MCT1E1.
When a primary clock is lost on a QMCT1, the router fails to
initiate the secondary clock on port 3.
CR 25255: Hardware Compression.
The driver faults when it mistakenly determines the state of the
rings as hung when the rings are functioning properly.
CR 25096: MCT1E1.
The QMCT1 port 1 primary clock was changed to an external clock.
However, there is no external clock connected. Therefore,
port 1 clocking should revert to the secondary clock but does not.
CR 24161/
CR 25120: Bisynchronous.
The Bisync/BOT code does not handle a DLE-DLE combination
correctly within transparent text.
CR 23255: DataPath.
When running a bridge storm (bridging loops without Spanning Tree),
a slot may reset with an "out of memory" error or a watchdog timer
error.
CR 25443: FDDI.
A hardware problem can occur when the state of a protocol is
"down", but the state of the interface is "up". If you monitor the
FDDIEntry, the Tx stats continue to grow while the Rx no longer
increments. If you perform a packet capture on Rx on this
interface, the trace will show that packets are being received,
but unacknowledged. This condition can be caused by hardware
corrupting information in the Ring Descriptors, which causes the
interface to hang and never recover.
CR 25473: DLSw.
Link stations do not recover when a Frame Relay cable is
disconnected and connected again.
CR 24918: GAME.
A new Autosave log feature has been implemented on LN routers
that allows users to automatically save the log to the Flash card
or floppy drive when the log is about to wrap. This new feature
prevents the log information from being lost.
You can enable the Log Autosave feature from the Technician
Interface only.
The Log Autosave feature requires that you set two new attributes
in wfSerialPortEntry object: wfSerialPortAutoSaveNumFiles and
wfSerialPortAutoSaveVolume. The wfSerialPortAutoSaveNumFiles
attribute allows you to specify a value that determines the number
of times a log will be saved when it wraps. Specifying a value of
0 disables the feature; 0 is the default.
The wfSerialPortAutoSaveVolume attribute allows you to specify
a volume number ("2:"), or a volume name ("a:"), which determines
where you want logs to be saved. Specifying a colon after the
volume or volume name is optional.
On a BN platform, there is only one instance of the
wfSerialPortEntry object. Therefore, you will need to specify the
attributes described above for this instance.
On an ASN platform, there are 4 instances of wfSerialPortEntry,
each corresponding to a possible slot. You can configure the
feature on only one of the instances corresponding to an existing
slot.
On an LN platform, there are also 4 instances of wfSerialPortEntry.
Enable the feature on the first instance, which should correspond
to the console port (wfSerialPortEntry.wfSerialPortName.1 =
"CONSOLE").
The log gets saved in a file named "auto.log", where is a
number from 1 to the number you specify in
wfSerialPortAutoSaveNumFiles.
The logs will be saved until the number of logs reaches
wfSerialPortAutoSave\NumFiles, or until the Flash card or floppy
drive is full.
Wrapping a log on any slot automatically saves the log.
CR 25335: DVMRP.
A watchdog error can occur in DVMRP if some DVMRP interfaces are
being dynamically configured while other DVMRP interfaces are
learning multiple routes.
CR 25499: DLSw.
After activating flow control, traffic flow of the remaining
unsent frames will be sluggish after the traffic congestion
is rectified.
CR 23216: SDLC.
When deleting a primary SDLC circuit and then reconfiguring it,
DLS connections will not recover.
CR 25065: AN2.
An enhancement request has been issued to allow non-Token Ring AN
routers to support buffer sizes similar to the Token Ring AN's.
You can set buffers sizes on non-Token Ring AN routers to 1824 or
4800 bytes. This setting will be saved in NOVRAM and will be read
in at boot time.
Buffers can be carved by issuing the following set commands from
the Technician Interface:
set wfKernCfgParamEntry.wfKernCfgParamDelete.1 1
set wfKernCfgParamEntry.wfKernCfgParamBufSize.1 4800 (or 1824)
set wfKernCfgParamEntry.wfKernCfgParamDelete.1 2
commit
reset 1
To return to the default buffer sizes, enter the following
set command from the Technician Interface:
set wfKernCfgParamEntry.wfKernCfgParamBufSizeReset.1 1 ; commit
*** We recommend that you follow the above steps in the order in
which they appear. We also recommend that you delete
instances of wfKernCfgParamEntry before saving the config.
This process is similar to carving local/global memory
partitions.
When you set wfKernCfgParamEntry.wfKernCfgParamBufSize.1, the
buffer size gets saved to NOVRAM. At boot time, this setting
determines the buffer size.
CR 23172: IPX.
IPX accepts broadcast packets with an incorrect destination
address and tries to forward them.
CR 25212: Frame Relay.
Access Circuit does not recover after you pull a cable out and
plug it back in when the management type is NONE.
CR 24049: LNM.
When issuing the SHOW LNM LINKS command or viewing the MIB
(wfLnmInterfaceEntry) for LNM, the router displays incorrect
information about LNM link status after unlinking an IBM LNM
station.
CR 23288/:IGMP.
CR 23783 A fault occurs in igmp.misc.c when attempting to create a new
IGMP interface.
CR 25742: Frame Relay Switch.
A typographic error occurs in the translating tool, add2base. The
second description for each time unit should be Tx not Rx. For
example, for time unit 13, the description should be
StatsDcLbcTxMaxDelta13 not StatsDcLbcRxMaxDelta13!
Circuit (cct) number 8 (0x8)
StatsDcLbcRxMaxDelta13 448
StatsDcLbcRxMaxDelta13 508 <-----
StatsDcLbcRxMaxDelta14 448
StatsDcLbcRxMaxDelta14 508 <-----
CR 25399: Frame Relay Switch.
The add2base tool did not comply with channel assignment
requirement.
CR 25777: DLSw.
A session cannot be re-established after disabling and
then enabling DLS on an interface.
CR 25727: Frame Relay Switch.
The DE bit has not been set properly after the circuit has been
idle for a while. A Frame Relay circuit is up and passing traffic
and traffic is stopped for a period of time. When traffic resumes
at line rate (128k) and CIR is set low (10k), a certain
amount of traffic will be passed before the DE is set. The amount
of traffic allowed through before setting DE is directly
proportionate to the amount of time the circuit is idle.
CR 24378: OSPF.
When the OSPF backup soloist transitions from backup to primary,
OSPF neighbors may time out.
CR 25820: TI.
Running install.bat script displays the option of 'QMCT1_RJ48'.
This is not a supported link module.
CR 25557: LB.
A problem exists in which packets bridged from FDDI to Frame Relay
are being corrupted. The router is incorrectly modifying the
Ethertype to an invalid and different value for every
bridge packet transmitted from the FDDI. The receiving router does
not understand the Ethertype so it drops these frames.
CR 25647: Frame Relay Switch.
The Status Enq. on a Frame Relay Switch circuit configured for
bi-directional polling will drift past the polling interval when
the slot is experiencing heavy traffic volume.
CR 25592: IPX.
A bus error occurs when enabling and disabling IPX globally on a
router with a large RIP and SAP table.
CR 25539: IP.
After configuring an OSPF Announce policy range, disabling the
interface will cause OSPF to change the LSDB to announce the last
address set in the range.
CR 25830: Frame Relay.
When setting wfCctOptsCngcEntry.wfCctOptsCngcCfgHwtxQThreshold to
a value greater than the value of the
wfLogicalLineEntry.wfLogicalLineCfgTxQueueLength, the following
MIB does not get set to that value:
wfCctOptsCngcEntry.wfCctOptsCngcHwtxQThreshold
CR 25822: Frame Relay Switch.
Configuring the Statistics Data Collector to run on a a switch
caused a bus error to occur.
CR 25460: SYNC.
A buffer leak may occur on a slot in which priority queuing and
BOFLs are enabled and the synchronous interface is in a down state.
CR 25480: NetBIOS.
A router configured with NetBIOS 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 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 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 26748: OSPF.
An OSPF bus error occurs on routers that contain multiple
flopping OSPF point-to-point links.
CR None: IPX.
An orphan buffer error occurs as a result of encaps failure.
CR 25525: MCT1E1.
Removing the cable does not report 'Loss of Signal' in the
expected threshold.
CR 25925: Frame Relay Switch.
After resetting the slot on a Dual MCT1 and QMCT1 that contain an
external clock, the slot uses the secondary clock (internal)
rather than the primary clock (external). The slot should
use the primary clock because it is still operational.
CR 25847: MCT1E1.
When hotswapping (specifically when putting it back in) the QMCT1
in slot 2 on a BCN router while under load, the router
faults and fails to recover.
CR 25924: Frame Relay Switch.
Under certain conditions a logical line on a port with 12 logical
lines stops receiving packets and receives no interrupts.
CR 21181: SDLC.
When you disable SDLC globally, the MIB attribute wfSdlcDisable
is set to 2, but SDLC continues operating.
CR 25679: SDLC.
Disabling the SDLC base does not disconnect an SDLC session; it
remains operational.
CR 22101: OSPF.
The outcome of applying an Accept Policy filter is not used when
submitting an external route to IP.
CR 24731: Switched Services.
When the dial-on-demand inactivity timer elapsed, IP shuts down
on a WAN interface and fails to recover.
CR 25988: Frame Relay Switch.
RCN time delta value overlap will cause problems with billing
systems. The TIME DELTA for the switch RCN file is set for 24 hours
(or 8640000). Because the start time is also at midnight, there
will be a overlap or .0001 second if each file is created at
midnight and the time delta is always 24 hours (or 8640000).
CR 25960: BNX Switch.
wfDs1E1PortLoopbackState does not change when the
wfDs1E1ConfigLoopbackConfig attribute is set to lineloop(3) or
payloadloop(2).
CR None: HSSI.
This attribute determines how many seconds to wait before
transitioning to the Carrier Lost state when the Carrier Signal
is lost. When set to 0 (default), the Driver immediately
transitions to the lost state upon detecting Carrier Loss. If
the Carrier Signal returns before reaching this threshold,
the Driver fails to enter the Carrier Lost state.
C
Feedback | Service Search
| ERC
Copyright
© Bay Networks,Inc., 1997. All rights reserved.
|
/tr> |
