CR 24449: DECnet
DECnet allows the dynamic configuration of the Max Area parameter to a value
lower than that of the previously configured areas. Consequently, a load map
command could not be issued on the DECnet slot, nor could the log be saved.

CR 26224: IP
Site Manager does not enable you to change an IP address when editing a
circuit in either the dynamic, local, or remote modes. Attempting to do so
produces the following message, "A single IP interface is currently
configured. Multiple IP interfaces must be configured to perform the change
operation."

CR 30151: SWSERV
After dynamically deleting a demand pool, an instance of the object
wfModemEntry is not deleted. The instance should be deleted when the pool is
deleted.

CR 32476: DLSw
The following two problems affect Site Manager windows when configuring DLS on
a token ring interface: 1) Adding DLSw to the 2nd, 3rd or 4th token interface
on a slot, makes the entered slot IP address available. This can cause a
problem if you select the default and assign the same IP address to two slots.
2) If DLSw is already configured on a token ring interface, and you add DLSw
to another token interface a configuration window displays even though source
route bridging is already configured on the interface.

CR 34276: SNMP
When you configure an SNMP community using the BCC it does not change the
read-only default. If you then try to complete the configuration using Site
Manager, SNMP errors result for each set, but they do not properly indicate
that the SNMP community is read-only.

CR 34276: SNMP
Site Manager fails to identify the origin of for SNMP errors that occur when
you attempt to bring up SNMP community read-only defaults from BCC in Site
Manager. Site Manager should display a warning when bringing up SNMP community
read-only defaults.

CR 5438: Installation
Installing Site Manager on a system running HP OpenView displays the
instruction to delete Wellfleet router objects, rather than BayNetworks router
objects.

CR 71702: Pktconv
Using the network general sniffer to open a file on a router converted with
Version 1.8 of the packet conversion tool, pktconv, fails with the message
"Bad Record Header."

CR 83214: Event Logging
Event viewer filters do not work properly when you log in to Site Manager
locally. Logging in locally causes the Filtering Parameters window to display
only a partial list of the slots that are actually available.

CR 86559: MOSPF
The Multicast Forwarding parameter should allow the option, Blocked, when
configuring a circuitless IP interface in either Site Manager or the BCC.

CR 88721: Pktconv
When you convert PCAP files from ARE to ATC using pktconv version 1.8,
attempts to open the converted file cause "unexpected end of file" errors to
occur.

CR 90000: DLSw
For ATM LANE circuits, the DLSw protocol doesn’t show up in the Protocol
window and source routing parameters are not saved.

CR 90169: Report Generator
Using Report Generator to decode binary configuration files to the ASCII
format causes an error.

CR 92997: DVS
The DVS key button is not displaying correct default values. When you add a
key the assigned values display. However, if you delete the key the incorrect
default values display rather than returning these values to zero.

CR 92997: DVS
The DVS key does not display the following correct default values:

Key (Bits 127-96) 0x00000000
Key (Bits 95-64) 0x00000000
Key (Bits 63-32) 0x00000000; Key (Bits 31-0) 0x00000000

CR 97381: X.25
Site Manager does not allow entry of hexadecimal characters as is required,
when entering X. 25 call user data for IPEX Gateway Services (TCP to SVC).

CR 97559: IPEX
Site Manger does not allow configuration of IPEX gateway mappings for PVCs.
Site Manager may also prevent any changes to existing mappings.

CR 97682: DLSw
Site Manager does not configure the LAN ID and Bridge ID global parameters
properly when adding DLSw to a token ring interface. As a result, DLSw sends
data with incorrect RIF information and fails to establish a connection.

CR 98174: Site Manager
Site Manager does not accept entry of numbers as part of the name entered for
any configuration file using the "Save As" function from the File Menu.

CR 98289: ATM
Emulated LAN Segment ID does not appear when an 11.0x configuration file is
opened in Site Manager Versions 6.00 or later.

CR 98343: IP
You cannot create an IP traffic filter from a template with 44 or more actions
(Forward to IP Destination Address) without corrupting it. The 44 or more IP
addresses that you entered will not appear when you attempt to edit the IP
filter using Site Manager.

CR 98525: DLSw
Leaving and reentering the main window under DLSw Basic interface causes the
DLSw slot IP address to be reset, from the correct Slot IP address, to
0.0.0.0. This change also appears in the DLSw slot IP address table.

CR 98585: MCT1
Site Manager does not check whether another port of Dual-MCT1 has already been
configured during a dynamic configuration of an ASN router.

CR 98917: IP
You cannot add or delete router discovery on an existing ATM service record
using Site Manager.

CR 99801: SMDS
Site Manager will not allow configuration of SMDS group address at the IP
interface window.

CR 100368: LLC
The option to edit LLC traffic filters can cause the display of traffic
filters to disappear from Site Manager until you exit and then return to the
circuit.

CR 100499: Protocol Priority
Protocol priority disappears in Site Manager when you move a PVC from group to
direct mode and create a new service record. Although Protocols Priority
continues to appear under the interface list, it disappears when you select
any other protocol (for example, IPX).

CR 100531: ATM
A machine check occurs on ARE in the BCC when you change the SCR (sustained
cell rate) to 0 after adding a PVC to a service record and altering the PCR
(peak cell rate) to 300 and then 1000.

CR 100955: IP
After configuring a router for IP/RIP on a frame relay interface, an error
occurs while adding an adjacent host address. The error message reads, "a
local IP interface cannot be on the same subnet as an adjacent host."

CR 101531: SRB
Site Manager does not display the Source Routing Global window correctly when
you add source route bridging for a different circuit after adding DLSw first.
This can also occur when you add protocols on an ATM circuit.