 |
|||
     |
|||
|
Revision Notes for Site Manager 2.11 Fix 4
Site Manager Revision 2.11/Fix 4 is a post 2.11 revision. This version
is backwards compatible and supports the following router versions:
8.10
8.01
7.80
7.71
Note: When running fix versions of router software in conjunction with a fix version of Site Manager, be aware that there may be new MIB attributes
that were added in a router fix revision that are not supported in a Site Manager fix revision. Refer to the fix revision notes for both Site Manager and router software.
2.11 Fix 4 corrects the following problems:
=============================================================================
CR 15389: BGP4.
BGP4 Route Policies do not support AS_PATH Pattern Matching as
required by Internet Provider market.
CR 17912: Site Manager.
If you are running Site Manager Version 2.10 or 2.11 and you
connect to a router running Router Software Version 9.00 or later,
or if you are running Site Manager Version 3.00, and connect to a
router running Router Software Version 10.00, ²wfsm² sets
the MIB Version to 7.50. Then the following warning message is
displayed:
"WARNING: Site Manager no longer supports the version of the
software that the router is running. Proceed with caution."
This is a potentially dangerous situation, as you are not
prevented from connecting to that router with Tools or
Administration commands.
CR 17243: SYNC.
Site Manager disallows explicit values outside the 1 through 7 range
for wfSyncLocal/RemoteAddress.
CR 15467: Source Routing Bridge.
When you configure (edit or add) Source Route Global parameters on
a router running a Version 8.01 image, you receive the following
error message:
³Error: Invalid data Entered for ŒConn IP NTWK Ring Number²
This error condition is specific to Version 8.10 images, and
occurs only when IP Encapsulation is enabled or disabled.
This problem does not exist with routers running Versions 8.10,
7.80, or 7.71.
CR 18125: ATM.
You cannot add a circuit to an ATM interface with a VCI
number less than 33.
CR 18316: Site Manager
Upon saving a new user-defined Priority Protocol Filter, Site
Manager PC GPF restarts instead of displaying an error screen
that indicates ³No action specified!².
CR 18553: IPX.
If you are using Site Manager Version 2.10 or Version 2.11/fix3
and you create a 16-character IPX NetBIOS Static Route with the
16th character being a plus sign (+), Site Manager renders this
static route unusable.
CR 18680: Image Builder.
If you open a BN.exe image using the Image Builder tool in Site
Manager and you save the BN.exe image without removing any
components, the new image loses the file lapb.exe.
CR 14286: Switched Services.
Attempts at setting the "Seconds between Xmit of Echo-request" field
on the "PPP Line List" screen to a value of 0 proved unsuccessful.
As a result, in a dial-on-demand over ISDN configuration, the ISDN
line remains in a permanent up state.
CR 18591: DLS.
When you edit a DLS user-defined filter in remote or dynamic mode,
you receive the following error message:
"Invalid field. "USER_DEFINED REF:DL_DEST_OFFSET:952BITWIDTH:32:
If you attempted to edit the filter during dynamic reconfiguration,
the filter is automatically deleted from the router's running
configuration.
CR 15652: E1.
When you attempt to configure a Dual Port E1 while running Router
Software Version 8.01 and Site Manager Version 2.10, the Mini Dacs
are rendered unconfigurable.
CR 17898: IPX.
When you first configure a host number, then you decide later that
you no longer want to use the number, there is no method which to
restore the host number to its initial setting.
When you clear the host number field, SM sends 0x000000000000, which
causes the wfIpxInterfaceEntry.wfIpxInterfaceActiveHostNumber to
set to 0x000000000000 rather than its MAC address.
CR None: IPX.
Added support for two new IPX MIB parameters for Site Manager.
-- New field created in the IPX Global Parameters for Triggered
Updates, which corresponds to WfIpxBase.17.0
-- New field in the RIP Interfaces window for Redundant
Interface support, which corresponds to
wfIpxRipIntfEntry.7.*
======================== Version 2.11 fix 3 ==================================
CR 17609: IP.
Message ³IP Address/Subnet Mask misconfigured² invalidly issued when
attempting to configure an IP interface using Site Manager 2.11
Fix 2 on the PC platform.
CR 13934: Bridge.
Protocols -> Source Routing -> Spanning Tree -> Global contains
a parameter called ³Spanning Tree Protocol Version². It contains
three versions, but only one version (IEEE802.1D) is implemented.
This invalid config parameter has been removed.
CR 13459: Files Manager.
Site Manager router files Manager cannot display directory >128
entries.
The maximum entries that the router files manager can display has
been increased from 128 to 255.
CR 16405: BGP.
No error checking on IP addresses of BGP peers after the first
peer is entered.
======================== Version 2.11 fix 2 =============================
CR 15086: End Station Support.
An IP interface configured for End Station support on a Token Ring
will send an ARP using an STE (Spanning Tree Explorer). It is
desirable to have ARP use an ARE (All Route Explorer) in certain
situations.
To use this new option of configuring ARP as STE or ARE;
1)TR circuit configure IP address
->Interfaces-> TR End station enabled
3)IP->Interfaces-> scroll all the way down, default is STE
STE: Spanning Tree Explorer
* This will configure ARP to go out as a spanning tree
Explorer which does not pass the Blocking BRIDGE.
ARE: All Route Explorer
** If this is configured as ARE, ARP will be transmitted as
ARE, Bridge will forward ARE¹s even when Blocked.
4) configure ARP Cache so the entries will age in the table.
This is the SRB End station RIF table which holds the MAC
addresses of the End stations ŒwfBrSrEsRifEntry¹, this table
keeps each entry for 300 seconds.
CR 13723: IP.
After upgrading from 7.80 to 8.01 the wfCircuitNameEntry is not
created for the circuitless ip interface that was previously
defined when the router was running 7.80. This results in the
message that circuitless ip interface must be created when
selecting PROTOCOLS/IP/CIRCUITLESS IP/CHANGE PROTOCOLS.
CR 16322: BGP.
Using Site Manager 2.10 fix 1 Statistics Manager and displaying
the BGP Peer Info screen, the BGP peer address is shown in the
BGP local address field.
CR 16650: Filters.
Configuring IP or other Protocols with multiple fields we can not
edit filters with large number of ranges. It is possible to edit
the template from the Template Management windows. But you can not
edit the filters.
CR 17214: BGP.
When clicking on the Apply button on the IP Interface List for BGP
screen, even without changes on that screen, a message ³ERROR:
Invalid data entered for ŒFR Broadcast DLCI¹² pops up. This only
happens when Frame Relay is NOT configured on the circuit.
CR 16241: Image Builder.
Image Builder does not display the release version, only display
the fix version as a choice for building new image on the PC.
CR 14348: Configuration Manager.
When the user adds a circuit in Local, Remote or Dynamic
Configuration and clicks on the Details button, the window exits
on the user.
Steps:
-> Setup SM 3.00/25; BLN 9.00/26
-> Get into SM main status window
-> Click on Local, Remote or Dynamic configuration mgr from the
Tools menu
-> Add new Circuit
-> Click on the Details.... button.
Window Exits.
CR None: TFTP.
The volume number is displayed as 200 instead of 2 for example on
the TFTP lack of contiguous spaces error screen.
CR 16689: Bridge.
Bridge Priority will continue to display the default value of 128
even after it has been edited to some valid non-default value.
However, the MIB wfBrStp will display the correct value.
CR 14919: Bridge.
In SM 2.11 using a 8.01rel and a 8.11 router, you can¹t enter valid
addresses in the fields in the ³Translation Bridging Address
Mapping² window.
Steps:
1) Dynamic Cfg
2) Protocols->Global Protocols->Translation Bridging->Create TB
3) Protocols->Global Protocols->Translation Bridging->MAC Addr Conv
4) Select Add button
5) Try to enter any valid data that these 2 fields are looking for.
Notice that the fields don¹t accept any valid input.
CR 15964: Configuration Manager.
Configuration Manager will terminate with an error message when
trying to configure two ospf ports.
CR 14935: Filters.
SM-PC Filter Management Screen does not list more than 100 entries,
If you have more than 100 templates in file template.flt user
cannot read more than 100 templates. They will be saved in file
template.flt but it can not be accessed by the user. Only the first
100 templates are accessible.
This limit is now increased to 500 filter templates.
======================== Version 2.11 fix 1 =============================
CR 13931: System.
As long as the Ping from Router window is open, the user is unable
to execute other Site Manager functions such as changing router
connections. The user must exit from the Ping from Router window
before performing other tasks.
CR 12305: Bridge.
13259: No default value for Spanning Tree MAC address.
The Spanning Tree MAC Address will now be learned during the boot
up time as in the dynamic mode if no values are specified.
CR 10305: Bridge.
12274: Local/Remote config should provide a default for SPAN Bridge
Priority.
The Bridge priority will now be defaulted to 128.
CR 15389: BGP4.
BGP4 Route Policies do not support AS_PATH Pattern Matching as
is required by Internet Provider market.
A new field ³AS Pattern² has been added to BGP4AcceptPolicyFilters
and BGP4AnnouncePolicyFilters screens.
CR 15675: IP.
When configuring IP over PPP the default encapsulation value
is incorrectly set as 0 when it should be Ethernet.
CR 15516: BGP.
Configuring BGP over X.25 DDN and the BGP validation routine for
the BGP Peer dialog says ³BGP ID IP address must be on the same
network as Local IP Interface², even though the Local Peer address
was a local IP address.
CR 13932: Bridge.
SM does not allow the enabling of XB spanning tree. When Bridge,
Translation Bridge, Source Routing, and Spanning Tree are
configured on a token ring interface
wfBrStpInterfaceTranslationDisable is not being enabled. No user
configurable parameter is needed for
wfBrStpInterfaceTranslationDisable. The system will automatically
configure this parameter when the above protocols are configured.
CR 14810: Config Manager.
Selecting a none configuration file from Local Configuration Mgr
results in GPF error.
CR 13541: OSPF.
When displaying the OSPF Interface Statistic screen Point to
Multipoint interfaces are shown as type Œ4¹ instead of an ASCII
description such as ŒPt to Mpt¹.
CR 13478: IP.
Can only add 61 ranges to IP Traffic Filter. Up to 61 ranges for
an IP Traffic Filter that is configured to drop based on IP source
address works. If you add a 62nd range, and then choose ³Save and
Exit², when you are back at the main Traffic Filter Screen, there
are no traffic filter entries listed.
CR 14406: Filters.
Deleting and then adding bridge filters with large ranges can cause
Tag Violation slot resets.
CR 14226: Sync Passthru.
Router adds 0¹s to the right of whatever address was entered for
Sync Passthru MAC addresses. SM should require the user to enter
a 12 digit mac address for sync passthru mac addresses.
CR 14951: X.25.
In rel 8.11 the T1 timer is being triggered at 300msec, regardless
of the configuration. The SM default is changed from 3 sec to 30
sec, which is not the standard default (3 sec. is recommended).
CR 14501: DECnet.
DECnet IV MAC Address is not Correct on Token_Ring Interface.
CR 14935: Filters.
The Site Manager template screen for filter definition will never
list more than 100 entries. If a user defines more than 100
templates they will be saved to the filter template file, but the
oldest templates will not be accessible since they are not loaded
into the templates window. This limit has been increased to 500.
CR 14731: IPX.
PC Site Manager will GPF when the IPXWAN configuration window
is exited.
CR 13929: Files Manager.
A non-descriptive error message displayed from SM when there is not
enough contiguous space available on the target volume.
CR 14789: Files Manager.
Copying Router files to unknown volume result in WFRFS.EXE general
protection error.
CR 13540: PPP.
PC SM GPFs when attempting to define a PPP circuit during
dynamic config.
Notes for Backward Compatibility:
=================================
When using Site Manager to create a new local configuration file for a
router running a previous version, you need to ensure that the new
configuration file has the appropriate MIB stamp. To do this, TFTP the ti.cfg from a router running the MIB version for which you are creating the local
configuration file. In local mode, edit the ti.cfg, using it as a template
to begin your local configuration file. In most cases this will
automatically ensure you have the correct MIB stamp.
Note one exception to the above scheme. The ti.cfg that shipped with
version 7.57 of the router has an incorrect MIB stamp (CR7409). If a 7.57
ti.cfg is the version you are using, boot the router with the ti.cfg and
then save the file. This updates ti.cfg with the appropriate MIB stamp.
--- Internet Message Header Follows ---
Received: from BayNetworks.com (pobox) by paperboy.corpeast.baynetworks.com (4.1/SMI-4.1)
id AA28785; Mon, 18 Sep 95 14:29:36 EDT
Received: from lobster.wellfleet.com by BayNetworks.com (4.1/SMI-4.1)
id AA22223; Mon, 18 Sep 95 14:29:35 EDT
Received: from mechanic.engeast (mechanic.wellfleet.com) by lobster.wellfleet.com (4.1/SMI-4.1)
id AA06496; Mon, 18 Sep 95 14:28:23 EDT
Received: by mechanic.engeast (4.1/SMI-4.1)
id AA13488; Mon, 18 Sep 95 14:32:28 EDT
Message-Id: <9509181832.AA13488@mechanic.engeast>
To: mlinneha@pobox.BayNetworks.com
Subject: Revision Notes for Site Manager 2.11 Fix 3
Date: Mon, 18 Sep 1995 14:32:27 -0400
From: John Burke
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
