SITE MANAGER COMPATIBILITY

Router Version is managed by Site Manager version

v11.03 revision 1 --------------------------> V5.03, V5.03 rev1
v11.03 revision 2 --------------------------> V5.03, V5.03 rev1
v11.03 revision 3 --------------------------> V5.03, V5.03 rev 1, rev 3
v11.03 revision 4 --------------------------> V5.03, V5.03 rev 1, rev 3
rev 4
v11.03 revision 5 --------------------------> V5.03, V5.03 rev 1, rev 3
rev 4, rev 5

Revision 11.03/5 corrects the following problems:

CR 29743: Technician Interface.
The prom command does not work properly for the ACE platform.

CR 29756: OSPF.
An OSPF router might unicast link-state updates unnecessarily to its
neighbors due to a timing error. This can occur following the
transmit whenever the link state unit moves from the retrans_pend
queue to the retransmit queue. If the retransmit timer fires before
neighbors can acknowledge it, the update is unicasted unnecessarily.

CR 33504: Telnet.
A Telnet session hangs when a client telnets in to and out of the
same router.

CR 33569: Translation Bridge.
When the translation bridge base is bounced in a LANE configuration,
the scheduler exits because of an orphaned buffer.

CR 33846: PPP.
When you bring up a PPP connection on a remote router, and then swap
out the remote router with a different router (the router has a
different IP address but is on the same subnet), the adjacent host
entry in the host router has the old remote router’s IP address.
This still occurs even after bouncing the sync line.

CR 34421: Sync.
This is an enhancement request to add a new MIB parameter to
wfSyncEntry called wfSyncUcastMap, which will map InUcastPkts and
OutUcastPkts in the ifEntry to RxFrames and TxFrames in the
wfSyncEntry.

CR 34988: OSPF.
Bouncing OSPF on an Area Border Router with several point-to-point
OSPF nbrs might result in a bus error in OSPF.

CR 35417: BootP.
The following message from the log should be removed because it
fills up the log and the customer can track the information using
the MIB:

# 1: 01/30/98 16:03:33.472 INFO SLOT 4 BOOTP Code: 77
BOOTREQUEST rcvd on 165.222.48.1 dropped - pkt type not relayed.

CR 35665: WCP.
When you configure a frame relay service record with WAN compression
protocol (WCP) it does not show received BECN records in the
statistics.

CR 35990: IPX.
If you disable an IPX interface and then reboot the router with the
saved configuration file, the router bridges IPX traffic with a
matching encapsulation type.

CR 36052: OSPF.
In certain configurations, OSPF summarizes a summary advertisement
that is based on a stub network that is up. When the stub network
goes down, OSPF fails to flush the summary generated based on the
stub.

CR 40944: ATM.
While running continuous bridge traffic to 2000 different unresolved
MAC addresses, the ATM slot sometimes restarts, logging the message
"atmizer heartbeat failure." This problem occurs when a heartbeat
response is not received.

SP 71111: MIB.
When you boot the router it creates MIB-2 ifEntry instances for
logical circuits only. RFC 1213 requires that ifEntry instances be
created for logical circuits (such as, IP), the associated PVC, and
the underlying physical interface. The following MIB attributes all
remain at zero: ifMtu, ifSpeed, ifPhysAddress, ifInErrors,
ifOutErrors, and ifOutQlen. The following are the only MIB
attributes that display valid data: ifIndex, ifAdminStatus,
ifOperStatus, ifLastChange, ifInOctets, ifOutOctets, ifInDiscards,
and ifOutDiscards.

CR 71388: OSPF.
If you install a summary link with a network address of 0.0.0.0 and
a subnet mask of 255.255.255.0, an Area Boarder Router sends that
summary link to a neighbor in the stub area.

CR 71852: OSPF.
When an IP circuitless interface moves to a new slot on which many
static routes are configured to point to the same circuitless
interface, the router does not recreate the static routes correctly.

CR 71942: FTP.
The router crashes when you try to change the local directories
while the router is connecting.

CR 74095: APPN.
APPN HPR disallows new session establishment after an HPR path
switch. Existing LU-LU sessions continue but new sessions fail with
an SNA sense code of 8002.

CR 74167: X.25.
When full addressing is set to off for the Public Data Network, the
router makes a connection for the first X.25 service record only.
The remaining X.25 service records then attempt to connect using the
remote X.121 address of the first service record configured.

CR 75239: BGP.
When more that one BGP peer exists between a pair of routers, and
you disable the BGP collision detect parameter, changes to the
announce policy are lost.

CR 75455: ATM
A TAG violation might occur when populating the IP route cache under
load.

CR 75991: OSPF.
When an OSPF border router generates default LSDBs for a stub area,
and if there has been a summary network LSDB with an LSID of 0, a
bus error occurs in OSPF.

CR 76040: WCP.
Bouncing a Frame Relay PVC that has WCP enabled might cause a bus
error.

CR 78147: ARP.
Connectivity might be lost to a single host once that host has aged
out of the host cache. Traffic is received by the router destined
for that host, but the router fails to re-ARP for it.

CR 78294: ARP.
The router incorrectly caches an ARP response of all Fs as its
MAC address which ultimately causes a network outage after the TTL
expires.

CR 78321: BGP.
When you have more than one BGP peer between a pair of routers, and
you have BGP collision detect disabled, changes to the announce
policy do not take effect.

CR 78499: SDLC.
SDLC trace logging is not fully implemented.

CR 78501: DLSw.
DLSw does not handle the HALT_NOACK command defined in RFC 1795.

CR 78669: DLSw.
Slow performance occurs when you transfer NetBIOS files using DLSw
RFC 1795.

CR 78737: SDLC.
An SDLC link configured as primary multi-drop fails to respond
after receiving an I-Frame with the poll bit set. If there are 2
PUs, one of them must be inactive on the host for this condition to
occur. The router should respond with a final bit.

CR 78807: APPN.
Routers running APPN experience assertion failure in function
ndsnsstp.c at line 983.

CR 78812: Source Route Bridge.
The router faults if you disable and enable a source route base or a
source route interface on the same T1 line. This fault occurs
because the initialization routines start before the disable routine
completes.

CR 78813: Source Route Bridge.
Bouncing a source route interface on an 802.5 LEC causes a fault to
occur.

CR 78866: ATM.
System 5000 BH router slot locks up under load with wrt_thru enabled
for Release 12.10.

CR 79071: Frame Relay.
The Frame Relay sync interface state constantly changes from UP -->
INIT --> LMI WAIT --> NOT PRESENT. This happens only if you have a
group, direct and a hybrid mode PVC configured.

CR 79357: BGP.
The router faults when you attempt to dynamically change the BGP
peer addresses.

CR 79893: SYNC.
A UNIX server PU 2.1 fails to connect to a SDLC PU 4 (3745) through
DLSw routers whenever PU 2.1 is activated before PU 4. When this
condition occurs, the UNIX server continuously sends XID Fmt 3
frames while receiving nothing. Also, PU 4 does not forward XID Fmt
3 frames to the peer router by the secondary SDLC router.

CR 79904: TI.
The User login should not have the privileges to change the date and
time.

CR 79920: MCT1E1.
A system 5000 with several 5380s experiences CPU resource issues.
After loading the ASN and Munich drivers and setting the clocking to
internal, the CPU use went from 40 to 50 percent.

CR 79932: IP.
RIP 1 does not broadcast routing updates to a subnetted LAN segment.
Also, no default route is generated if the default route generate
feature is enabled.

CR 80007: TCP.
TCP peers are very slow to form in a DLSw environment with many
peers are configured.

CR 80042: X.25.
A bus error might occur in X.25 when it disconnects.

CR 80105: ATM.
In SSCOP, when the top of the transmit window is reached, subsequent
messages are placed in a queue for later. When the transmit window
is incremented, the postponed messages are not sent out. The
messages remain in the private buffer pool for the SSCOP gate until
some event (e.g., bouncing signaling) restores them. Depending on
the circumstances, the slot might run out of buffers.

CR 80114: ATM.
A router acting as an ATM RFC 1577 client faults when trying to
connect to the ARP server if the connecting switch keeps returning
release cause 51. Cause 51 indicates that the router needs to modify
the ATM Traffic Descriptor IE because the requested cell rate is not
available.

CR 80217: IP.
If a multislot router is running in host only mode, and if a slot
resets other slots, the router might report a fault in ip_rtm.c at
line 809. This problem seems to be exacerbated by having two or more
slots configured with IP addresses.

CR 80274: IP.
A bus error occurs when you reset an IP interface.

CR 80321: ATM.
A router running with an ATM interface in a source route environment
experiences an ARE MCP error.

CR 80401: VINES.
The wfVinesIfCostUsed is flipping between 0 and the cost that is
being used for the interface.

CR 80532: BGP.
Routes are not properly withdrawn if a BGP route matches a network
criteria exactly.

CR 80754: VINES.
The default cost for an ATM LANE interface should be 1.

CR 81058: BOT.
When transmitting a frame over a bisync line at a low speed
(less than 4800 baud), the bisync driver inserts two sync characters
every 256 bytes. Normally, the remote device driver recognizes the
sync characters. However, when a frame, followed by a bcc checksum,
ends on a 256-byte boundary, the router assumes that the sync
characters are the checksum and rejects the frame because the
checksum is invalid.

CR 81321: Switched Services.
When you use dial backup or a demand circuit, the ISDN line fails to
connect on every other attempt if only one PRI B channel is enabled.
CR 81489: VINES.
The router forwards broadcast STDA packets with a zero hop count
when the transmitting station is in the neighbor table.

CR 82294: BootP.
Configuring the Schedule Boot parameter using Site Manager causes
the router to fault.

CR 82662: OSI.
If the primary circuit fails, OSI might fail to reestablish itself
onto the backup circuit.

CR 83164: OSPF.
An LSA can go to MaxAge (3600) and not be removed from IP. The LSA
sequence number hangs and the router will not flood the LSA.

CR 83691: Flash Handler.
The Flash driver code is unable to recognize SanDisk ATA flash cards
used in crash dumps. The driver cannot identify the following
boards:

40MB PCMCIA PC CARD ATA (Product No. SDP3B-40-101-00)
85MB PCMCIA PC CARD ATA (Product No. SDP3B-85-101-00)

CR 84379: ARP.
A tag violation might occur in ARP when a circuit goes down.

CR 84425: IP.
Creating an IP traffic filter using Site Manager causes a tag
violation error. This violation occurs because the rule size is
smaller than the fragment size.

CR 84619: ISDN.
The router faults when you configure one local phone/SPID
for Switch Type NI-1 and repeatedly set the MIB instance
wfIsdnLocalPhoneNumEntry.wfIsdnLocalSpid to an invalid SPID
value at intervals of approximately one second.

CR 84897: OSPF.
When you add a summary range with the same link-state ID to
an area border router (ABR), all the other area border routers fail
to remove the specific routes and summary route. This occurs even
though the originating ABR is only propagating the summary range.

CR 85076: OSPF.
An OSPF area border router incorrectly summarizes a Type 2
Network-LSA, resulting in loss of inter-area connectivity. When the
ABR generates the Type 3 Summary-LSA, it sends the wrong Link State
ID because it fails to apply the network mask to the original Type 2
Network Link State ID.

CR 85312: DLSw.
QLLC sessions might not be reestablished after inactivating then
activating the PU device. As a result, the QLLC device does not
clear the call or initiate a new session.

CR 85393: IP.
When configuring IP and a Token Ring LANE LAN emulation client on a
router, the router sometimes sets LAN emulation ARP for a MAC
address rather than for the route descriptor. As a result, traffic
traverses the BUS causing connectivity problems.

CR 85612: VINES.
A fault might occur in VINES when the following conditions are met:
- The router receives a VIP (VINES IP) packet destined for a
client at the network layer.
- The VIP packet originates from a source on the same LAN.
- The client’s routing server is not in the local routing table
but does appear in the neighboring table.

CR 85908: Packet Capture.
When you start a SNA session with packet capture enabled on an ATM
circuit over an ATM LAN emulation, the router faults. If you enable
packet capture on an ATM circuit but do not start it, the router
does not fault.

CR 85967: DLSw.
If you configured a specific TP/learning bridge (LB) filter on the
router and then you disable DLSw, the router faults. When you
reenable DLSw, the LB stops receiving packets on the Ethernet
interface.

CR 86281: TCP.
A tag violation occurs in TCP when closing a TCP connection.

CR 86586: OSI.
OSI does not build second ‘Code 2’ section in non-psuedonode LSP
after the first ‘Code 2’ section has filled up.

CR 87577: Technician Interface.
The year 1999 appears as 0099 in the year parameter of the date
field in the file directory.

CR 87946: OSPF.
OSPF faults when processing a non-self originated Type 3 summary
that was previously received from the same advertising router and is
subsequently received with a different subnet mask.

CR 87947: OSPF.
OSPF faults when deleting a self-originated Type 3 summary LSDB with
host bits activated, in the event of more or less specific masks in
the same LSID.

CR 88236: SRB IP Encapsulation.
Configuring a router with a Directed IP Encaps Explorer filter
causes a bus error if the filter has more than one IP Explorer
entry, the first of which resides in the global explorer table.

CR 86617: SRB IP Encapsulation.
IP Encaps uses the new protocol UDP port 12289 for all explorer
entries when it configures an explorer entry.

CR 86650: SRB IP Encapsulation.
The router incorrectly responds using port 12289 after receiving an
IP encapsulated test poll on UDP port 12288. This problem prevents
the router from making a connection whenever the source route bridge
(SRB) IP encapsulation uses the SRB protocol on a BayRS version
prior to 11.00.

CR 88298: VINES.
When a router running VINES receives a RDR for a local client, it
does not add the client to the neighboring table.

CR 89309: DLSw.
Multislot broadcast does not work correctly on SDLC secondary
interfaces. The router receives the CANUREACH and propagates it to
all slots, but does not respond with an ICANREACH. The multislot
broadcast works correctly only when the DLS slot IP address is in
the peer table and a TCP connection exists. This does not occur for
a remote IP address configured as a peer when the CANUREACH arrives
on a different slot.

Revision 11.03/4 corrects the following problems:

CR 25571: OSI.
Within the default metric field of an OSI LSP, the 0x40 bit
indicates whether the metric is internal or external. The router
does not check this field.

CR 31110: SNMP.
When you type "show snmp base" using the Technician Interface, the
displayed information has some misspelled words.

CR 33687: OSI.
After the router receives a new LSP with a new sequence number and
checksum, the sequence number and checksum in WfOsiL2LspHdrEntry are
not updated.

CR 33778: OSPF.
If there are multiple ASBRs announcing default routes in their
ASEs, the Technician Interface lists only one default route.

CR 33841: ATM.
The SSCOP window does not conform to the Q.SAAL (Q.2110)
specification. Bay Networks router code does not respect the Q.SAAL
window credit specified by the switch. As a side effect of this
change, LECs might struggle to come up if signaling goes down for
any reason because the router and the switch cannot communicate fast
enough to keep the connections from timing out. If this occurs, we
suggest that the value of wfAtmSscopEntry.wfAtmSscopMaxPd be set to
a low value (4 or 5).

CR 33867: IP.
A bus error occurs when setting wfIpBaseExtendedTrafficFilterSupport
to 1 when ISP Mode is enabled.

CR 33969: OSI.
Disabling an OSI interface causes other OSI slots to terminate
operation with a panic in mib_ent.c.

CR 34957: ATM.
The Bay VNR gives a signalling credit window of 128 frames to its
peer. The Fore Switch typically provides a credit of eight frames,
resulting in an unbalanced window. The MIB attribute
wfAtmSscopInitCredit was created to set the initial window credit
for the Bay Networks router.

CR 71585: Technician Interface.
When you use the show csmacd stats command, if the numbers that
appear are large, the Technician Interface displays them as negative
numbers.

CR 72024: FTP.
When you attempt to send files less than 2K from a Unix system to a
router, the transfer fails.

CR 72134: ASN.
When you boot an ASN with 100Meg ENET net modules and Circuitless
IP, a bus error might occur.

CR 72794: Technician Interface.
Using the disable sync circ <cir name> command on a multiline
circuit only disables the first circuit.

CR 73832: SDLC.
A router connected via SDLC to an IBM controller will not set the
poll/final bit in any I-frames it transmits, despite the fact that
the default value for wfSdlcLSAdminEntry.24 (PollOnIframeEnable) is
set to TRUE. This value should be set to FALSE if the controller
cannot tolerate the poll bit set in an I-frame and left to TRUE if
it can.

CR 74301: Technician Interface.
The log command should display the year as four digits (for example,
2000) in the header of each log entry. Also the dir command should
display the year of the file’s timestamp as four digits.

CR 75414: APPN.
In a large APPN network, some of the routers unexpectedly terminate
operation.

CR 75484: DLSw.
In certain protocol exchanges, DLSw connections can get stuck in the
CIRCUIT_PENDING state and do not recover until DLSw or LLC is
bounced (or the router is rebooted).

CR 75726: Switched Services.
The weekend schedule for a backup circuit does not function
correctly when another schedule is configured. For example, if you
modify the date on the router so that the backup circuit is active
for the scheduled weekday, the backup circuit is not active.

CR 78421: SRB.
A router running Source Route Bridge over Token Ring might cause
an MCP error.

CR 78426: Learning Bridge.
An orphan buffer might occur when bridging packets over a PPP
interface.

CR 78498: Flash.
When a crash dump is omitted at system restart, a message that
indicates the reason should be written to the log.

CR 78589: OSPF.
In a redundant environment, with two area border routers into an
area, when one of those routers is configured to summarize routes
from one area into another area, the router continuously faults in
ospf_sum_net at line 1110. This fault occurs until OSPF unloads
from the slot.

CR 78863: OSPF.
If an OSPF border router learns a route which is less specific than
the summary range configured on it, it then will generate the wrong
type 3 lsdb.

CR 79226: OSPF.
After bouncing an IP or OSPF base, and exception vector 2 bus error
occurs.

Revision 11.03/3 corrects the following problems:

CR 24390: ATM.
An MCP might occur after dynamically changing a Hybrid Mode PVC on
an ATM interface.

CR 26774: ATM.
A router running LANE crashes with an MCP error after losing and
then regaining signalling.

CR 28218: IP.
A fault will occur after a route with an invalid subnet mask is
added to the route table and then a subsequent route in the same
range is submitted.

CR 28589: BootP.
If you configure DHCP on a multinetted interface, the last IP
address configured should become the DHCP gateway. If you reboot the
router, the last configured IP address is no longer the DHCP
gateway. Instead, another IP address on that interface becomes the
gateway.

CR 28639: APPN.
To use a Default DLUS name for link stations that are not defined in
the APPN Adjacent Link Stations table, you must define both the
Default DLUS name and the Backup Default DLUS name. This feature
should work with only the Default DLUS name specified.

CR 29307: APPN.
When you have Dependent (PU2.0) devices in session and enter the
command "appn show dlur route," garbage is displayed in the route
field.

CR 31528: IPEX.
When configuring IPEX mapping sessions for the X.25 gateway, the
source circuit and source type are not being set.

CR 32070: Dial-on-Demand.
In a configuration where AURP runs over a Dial-On-Demand line with
WCP configured, packets might be lost, causing loss of IP
connectivity.

CR 32142: IP.
A counter problem causes wfIpInterfaceCacheNetworks to show a larger
value than wfIpInterfaceFwdCacheSize. wfIpInterfaceCacheNetworks
should never be larger than wfIpInterfaceFwdCacheSize.

CR 32624: Technician Interface.
In User mode, the Read and Read/Write Communities can be viewed.
Only the Read communities should be visible.

CR 32662: Technician Interface.
If you run diagnostics for certain link modules (for example, Octal
Sync, 100 Meg ethernet, or MCT1), a bus error occurs. The following
conditions must be met to cause the error:
1. The link module is the first to be installed in that slot.
2. The FRE card must be installed first and have already completed
its boot process.

CR 32997: IP.
When a Token Ring interface receives a segmented IP packet that
was incorrectly routed to it, the interface fails to send a second
packet to the next correct hop.

CR 33453: LAPB.
LAPB retransmits already acknowledged X.25 packets, causing
the X25 switch on the other side to reset the LAPB session between
the X.25 switch and the router. This causes X.25 virtual circuits to
be reset and IP circuits over those virtual circuits to come down.

CR 33530: Telnet.
An outbound Telnet session might hang and then freeze up the entire
Technician Interface session.

CR 33681: LNM.
When you run any show lnm command, the lnm.bat file does not
terminate properly.

CR 34236: SYNC.
Configuring a dial backup line using async PPP with Hayes modem on a
DSNM causes a bus error.

CR 34254: DLSw.
The log message for a negative CAPx message shows an offset of 0 for
certain CAPx errors.

CR 34258: IP.
This is an enhancement request to provide the ability to display the
total number of IP routes per slot for all slots. Use the command
"ip routes -O -s#" (where # is the slot number). If you do not enter
a slot number, all slots are displayed.

CR 34487: PPP.
If you have multiple PPP circuits on the same slot configured for
LQR, a race condition might occur when the circuit states change,
causing a bus error.

CR 34511: Translation Bridge.
Configuring translation bridge dynamically over TR LANE causes an
Exception Vector 2 MCP error on an ARE. The same error occurs if you
bounce a service record which contains a translation bridge
configuration.

CR 34595: Router Redundancy.
When you add multiple resources to a backed-up interface, only the
first resource is checked.

CR 34746: QLLC.
After modifying the QLLC map several times on an upstream router
(with no more than a minute separating the modifications), a bus
error occurs on the downstream router.

CR 35096: SDLC.
SDLC does not properly interoperate with the AS/400 high
speed line controller. SDLC should support "Flag Streaming" between
frames while holding the Poll/Final bit, and then revert to Idle
fill after the RR or last I-Frame returns the P/F bit to the AS/400.
Added the following MIB parameters: wfSyncEntry.wfSyncForceIFTF
(sync.mib) and wfLogicalLineEntry.wfLogicalLineIFTF(ds1e1.mib)

CR 35177: DLSw.
BayRS is not fully compliant with RFC 1434 or RFC 1795 when
operating with two half-duplex TCP connections. Added the
wfDlsPeerInteroperability field in wfDlsPeerEntry
object, which can take 2 values: enabled/disabled.

CR 35181: ASN.
When you boot an ASN that used to contain an MCE1 link module
with an MCE port configured, bus errors or tag violation faults
occur.

CR 35414: IP.
In a multiline setup with three or more lines, if one of the lines
goes down, the router might fail to resolve the far-end host address
via ARP.

CR 35570: PPP.
The PPP header size is incorrectly included in the calculation for
determining the maximum frame size
(wfIpxCircEntry.wfIpxCircLocalMaxPacketSize).

CR 35611: BGP.
A VBM error might occur if BGP adds a new route while running on an
ATM interface.

CR 35751: OSPF.
An ABR will not originate a new type 3 summary in the non-backbone
area if another summary with the same LSID already exists in that
area. The existing type 3 summary might not be valid.

CR 35878: DLSw.
DLSw interoperability fails with non Bay Networks routers
running RFC 2166.

CR 35985: SDLC.
A DLSw connection does not recover properly after the SDLC line is
brought down while in flow control.

CR 35992: ATM.
When an LE_ARP request is sent to an ATM interface on the router,
and the request is for the Group LAN ID of the source route bridges
in the network, the router fails to respond.

CR 36052: OSPF.
A problem exists in OSPF where under certain configurations, it will
summarize a summary advertisement that is based on a stub network
that is down. When the stub network goes down, OSPF fails to flush
the summary generated based on the stub.

CR 70923: DECnet.
DECnet adjacencies are aging prematurely because hello packets are
being missed. Because of a timing problem, the router believes that
three hellos have been missed instead of just one.

CR 71025: DLSw.
An orphan buffer might occur if TCP is unable to transmit a buffer
from DLSw after it is restored to DLSw.

CR 71080: IP.
IP traffic filter with log and deny actions will send a message to
the router log even if there is a match on another traffic filter
higher in the list.

CR 71175: Switched Services.
If you have backup circuits configured, setting the schedule
parameter to any valid value has no functional effect. When the
primary circuit fails, the backup circuit is activated, regardless
of the configured time/day. This occurs only when the Availability
Mode parameter is set to Not Available.

CR 71443: IPX.
The router might experience a bus error when a host sends a RIP
request or SAP request using a source socket of 9001 (NLSP).

CR 71517: IPX.
If a static route is added after a learned route with a better cost,
the static route is never added to the table. When the learned
route ages out, the static route does not take effect.

CR 71769: Source Route Bridge.
An SRF received on a source routing interface does not get sent out
over the IP Encaps cloud after a panic or bounce of IP.

CR 71975: DLSw.
DLS connection is not recovered after granted units counter reaches
zero, which is a protocol violation.

CR 72074: X.25.
If X.25 receives a disconnect request from the local interface and
then receives a disconnect from the remote interface through IPEX,
the VC might remain in an operational state and never be cleared.

CR 72328: IP.
If you delete an a 10Meg Ethernet interface that is receiving
traffic, and then re-add the interface with IP, the router
terminates operation.

CR 72468: DVMRP.
A router running DVMRP might deliver multicast packets to an
application out-of-order.

CR 72565: Switched Services.
You cannot manually activate a standby circuit when Bandwidth-on-
Demand is enabled on a demand circuit.

CR 72633: VINES.
When a VINES client sends a broadcast request, all servers respond.
The client connects to the first server and then sends a disconnect
message to the other servers. When the VINES client sends the
disconnect message, the VINES interface on the router performs
intensive processing for the forward cache and the slot where the
client resides experiences a Watchdog fault.

CR 72792: LLC.
When an LLC interface is disabled, a panic might occur after 30
minutes instead of after one minute if the router is having resource
problems.

CR 72996: ISDN.
SPID is not registering after TE1 loss because two SPIDS are sent
out of order.

CR 73592: VINES.
A router does not properly update the VINES routing table after it
receives a redirect packet.

CR 73764: IP.
The router is dropping IP packets after ARPing for a destination’s
address.

CR 73793: DLSw.
The problem occurs with the following configuration: DLSw and SDLC
configured as a single switch with a PU2.0 3174 controller. If the
upstream or host side issues a disconnect message followed by an
immediate XID poll five milliseconds later, the XID poll resets the
internal LLC connection from state "HALT_PENDING" to
"CIRCUIT_PENDING." The SDLC side proceeds to disconnect while the
LLC side proceeds to the connected state. The connection remains
hung with SDLC showing a state of CONTACT_PENDING, and LLC showing
"CONNECTED" and no data flow. This results in an interoperation
problem with the 5745 Enterprise Server.

CR 74189: VINES.
A router running VINES does not reply to a request for Check
Neighbor from a server running on NT. The VINES Server waits for a
response and then resends the request until a timeout value is
reached.

CR 74931: ATM.
An ATM interface stops transmitting or intermittently transmits if a
router is connected to an ATM switch that supports OAM. This
problem occurs if the remote end of a PVC is brought down.

Revision 11.03/2 corrects the following problems:

CR 26589: OSPF.
When you globally reset OSPF, a bus error might occur. The error
occurs because the OSPF primary receive gate is holding an excessive
number of buffers while it is waiting for buffers to be allocated to
send to the secondary gate.

CR 35021: OSPF.
The ignore action of an OSPF accept policy does not work.


CR 35414: IP.
In a multiline setup with three or more lines, if one of the lines
goes down, the router might fail to resolve the far-end host address
via ARP.

CR 35570: PPP.
The PPP header size is incorrectly included in the calculation for
determining the maximum frame size
(wfIpxCircEntry.wfIpxCircLocalMaxPacketSize).

CR 35611: BGP.
If you are running BGP on an ARE, BGP faults when you try to add a
new route.

CR 35887: OSPF.
When you use an OSPF Announce Policy filter to aggregate a range of
external networks, the aggregated LSA might constantly refresh if a
network within the range is unstable.

CR 36052: OSPF.
A problem exists in OSPF where under certain configurations, it will
summarize a summary advertisement that is based on a stub network
that is down. When the stub network goes down, OSPF fails to flush
the summary generated based on the stub.

CR 36065: ATM.
A VBM error occurs when the remote end of a PVC comes up with ATM
switches that support OAM signals.

CR 71779: IPX.
IPX route filters do not work if multiple filters with
different priorities are configured on a circuit.

CR 72873: OSPF.
When you modify a router ID, more than one type 2 advertisement gets
installed in the database. When the old advertisement is aged out,
the route is removed, but no route is installed in the routing table
for the new type 2 advertisement.

Revision 11.03/1 corrects the following problems: