 |
|||
     |
|||
|
Site Manager Revision 3.01/Revision 1
Site Manager Revision 3.01/Revision 1 is a post 3.00 revision. This version
is backwards compatible and supports the following router versions:
9.01
9.00
8.10
8.01
7.80
7.71
Note: When running revisions of router software in conjunction with a revision of Site Manager, be aware that there may be new MIB attributes
that were added in a router revision that are not supported in a Site Manager revision. Refer to the revision notes for both Site Manager and router software.
3.01 Revision 1 corrects the following problems:
=============================================================================
CR 21327: Configuration.
When you have configured a circuit in local mode and a slot goes
down (faulty hardware or FRE removed), the configuration indicates
that the slot is empty. Customer has issued an enhancement request
to provide a warning message, similar to those shown below, for
empty slots that have circuits configured.
WARNING: Empty slot 4 has circuits configured.
WARNING: Empty slot 13 has circuits configured.
CR 21150: Site Manager--Other.
The Site Manager Well-Known Connection list (about 70 router
entries) becomes corrupted when the size of all IP addresses in
the list exceeds 1012 bytes. As a result, the IP addresses at the
end of the list get deleted or truncated, and the IP addresses and
associated communities fail to synchronize.
CR None: Site Manager--Other.
When attempting to make a connection to a router that appears in
the Well-Known Connection list, the router state associated
with the IP address to be connected causes an error to occur.
CR 21191: Site Manager--Other.
The Well-Known Connection list on PC-Site Manager and UNIX-Site
Manager platforms is limited to 100 router entries. This list
should be increased to 500 router entries on the UNIX-Site Manager
platform.
CR 21192: Site Manager--Other.
When you select a router entry from the Well-Known Connection list,
the entry moves to the top of the list, making it difficult to
find the entry in a long list. The entry to be added
should be inserted before the entry currently highlighted, not
at the top of the entry list. This CR is related to CR 21191.
CR 20734: Configuration.
When running Site Manager Version 2.12, you cannot access a
Site Manager Version 3.00 circuit that has been added to a
2.12 configuration.
CR 19832: Configuration.
After you open a Site Manager 2.12 configuration in local or
dynamic mode, Site Manager fails to display any of the configured
protocols.
CR 20733: Configuration.
When you run PC-Site Manager Version 3.00 and then delete an IP
protocol from a circuit that has been added to a Version 3.00
configuration, Site Manager returns a GPF error.
CR 21753: Builder.
The size of the 9.00 release in Image Builder and in the
9.00 release directory do not match. The file size of the
9.00 release in the Image Builder is 2806809; the file size of
the 9.00 release in the 9.00 release directory is 2878332.
CR 19082: Site Manager-BNX Switch.
When you select the Help or Read Description option on certain MIB
objects (for example, wfHardwareConfig.wfHwTable.wfHwModIdOpt)
from the Statistics Quick Get, Screen Builder, or Screen Manager
window, the Statistics screen disappears (UNIX-Site Manager)
or a GPF error (PC-Site Manager) occurs.
CR 20820: Site Manager-BNX Switch.
When adding a new Frame Relay circuit, the DLCMI configuration
screen shows wfFrSwDlcmiCrossNetEnable as disabled. In 4.21fix2,
the default in the MIB for this entry is enabled (Site Manager
4.21 fix 2). Site Manager must be updated to reflect the default
change, and to make available through Site Manager the following
MIB attributes:
-- wfFrSwDlmciCrossNetAsyncUpdateEnable
-- wfFrSwDlcmiAsyncUpdateEnable
-- wfFrSwDlmciCrossNetListenEnable
CR 22267: IP.
In Site Manager Version 2.12, when you click on the Apply
button from the IP Interfaces screen, the error message
"Invalid Data Entered for 'TR End Station ARP Type !" displays,
and the parameter is set to zero. The parameter should default to
STE ARP type.
CR 22036: Configuration.
Site Manager faults when you attempt to create Source Route
NetBIOS Name filters.
CR 19808: Configuration.
A bridge traffic filter configured with several source MAC
addresses, and a pair of destination MAC address will not correctly
match incoming frames.
CR 21959: Events.
Events logs that display in descending order are missing the
first event. This happens on the UNIX-Site Manager and
PC-Site Manager platforms.
CR 20921: IP.
Selecting the Apply button from the IP Interfaces screen removes
the first item in the scroll bar section of the menu.
CR 21271: DECnet
While running Router Software Version 8.12 and Site Manager
Version 3.00 (Windows) release 1, Site Manager lets you change the
attributes under DECnet Global parameters. However, when you
view the log on the router, you can see that Site Manager has
failed to set any of the MIB variables that you have changed.
CR 21273: IP.
When you run Site Manager Version 3.00/release 1 with an 8.12
configuration file and then dynamically change an IP address
using the "Change" option, Site Manager deletes the previous IP
address but fails to add the new address. As a result, the
interface is lost.
CR 16980: Configuration.
When you add an ATM PVC to a Virtual Channel Link screen in Site
Manager (Solaris and SunOS), the screen moves up and down when you
attempt to apply the change, thereby making it difficult to add
multiple virtual channels.
CR 21410: Statistics.
Bluefish ATM circuits appear blank under 'Type' in statistics
window.
CR 20749: Configuration.
You can edit or delete Blackfish circuits from an empty circuit
list window with a Blackfish configuration even though the list is
empty.
CR 20758: Statistics.
When you attempt to launch the IPATMARP (rfc1577) Statistics screen
from PC-Site Manager, Site Manager displays the error message
"Invalid Entry Name".
CR 21087: Configuration.
ATM Virtual Channelıs PCR and SCR should have different range
checking for different media types.
CR 20087: BNX-Switch.
Site Manager cannot build a customized Frame Relay Switch
statistics screen that will display the circuit name along with
the Frame Relay Switch statistics.
CR 19765: Configuration.
The Filter Entities Values Selection scroll list box comes up
with a blank screen with a scroll bar on the right. If you scroll
down the screen, the filter values that display overwrite the
scroll box, making filter entity selection difficult.
CR 17146: Files Manager.
The File Selection widget that displays when you create or select
a local configuration file in Site Manager displays only
100 entries. A Customer has requested the capability to create or
select 400 entries.
CR 20461: TFTP.
You cannot use the Site Manager Router Files Manager (PC or UNIX)
TFTP PUT command to transfer more than 10-12 files onto a Flash
card, after selecting multiple files.
CR 20556: X.25.
After you delete one of the IP interfaces configured on top of a
X25/PDN port, Site Manager deletes the adjacency table too.
CR 20724: IP.
Changes made to the Fast Forwarding table in Version 9.00 and
10.00 need to be ported to Version 8.12. The Fast Forwarding
table needs to include r_tbl instead of tbl so that larger
forwarding tables can be created. This reduces the number of
dropped packets processed by IP.
CR 20737: IPX.
You cannot access IPX NetBIOS Static Routes created with a pre-3.00
version of Site Manager.
CR 20520: BNX Switch.
Site Manager does not verify duplicate IP addresses when you
configure a Frame Relay Switch interface.
If you attempt to configure a duplicate IP interface on a
synchronous or McT1 interface, Site Manager faults.
CR 18915: Configuration.
You are unable to set the bridge priority in the Source Spanning
Tree Global parameters to a value greater than 32K. You should
be able to set a value from 0-65535 for the bridge priority.
CR 19599: Configuration.
When configuring Sync Pass-Thru on an AN or ASN router,
Site Manager 3.00 release (UNIX and PC) does not allow you to add a
"Pass-Thru Local Address" and "Pass-Thru Remote Address".
CR 17337: Configuration.
When you configure the event filter for a specific slot, events
for a different slot displays. For example, if you configure
slot 3, events for slot 2 displays.
CR 18305: IPX.
Site Manager allows only one server to be configured for a
particular target network when multiple servers need to have
NetBIOS static routes configured for a particular target network.
CR 19823: IP.
Site Manager fails to display any of the configured protocols.
CR None: Configuration.
Using Site Manager 2.12 for SunOS, you create two different IP
filters named A and B. You change the state of Filter B to
"disable" and click on Apply. After creating another filter named
C, you select "Reorder", "Insert Before", the number field,
type "1", and click on "OK". When you click on Apply,
Site Manager renames Filter B to Filter C and enables it. But
while Filter Cıs name and state have changed, it continues to
operate under Filter Bıs rules.
In a related case, when you select a traffic filter using the
Reorder and Delete commands, the filters do not appear highlighted.
However, if you select another command (Edit, for example), one
of the filters appears highlighted, but you cannot tell which one.
Feedback | Service Search | ERC Copyright İ Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
