 |
|||
     |
|||
|
Revision Notes for Site Manager 2.10 Fix 1
Date: 4/25/95
Subj: Revision Notes for Site Manager 2.10 Fix 1
Site Manager Revision 2.10/Fix 1 is a post 2.10 revision. This version
is backwards compatible and supports the following router versions:
8.10
8.01
7.80
7.71
Note: Please be aware of the following when running fix versions of
Router software in conjunction with a fix version of Site Manager.
There may be new MIB attributes which were added in a Router fix
revision which are not supported in a Site Manager fix revision.
Please refer to the fix revision notes for both Site Manager
and Router software.
2.10/Fix 1 corrects the following problems:
=============================================================================
CR 13579: IP.
Deleting an element from IP interface list does not delete
corresponding BOOTP interface.
CR 12858: Frame Relay.
Frame Relay Main Info screen displays incorrect value for
wfFrDlcmiStatus.
CR 12615: System.
In 2.10 release, If Site Manager is running on a machine which only
has OpenWindow installed but not X-Windows. SM will produce a lot
of warning messages about the XKeysymDB file, and also the remote
display will not work correctly. It only displays a tiny, separated
windows on the remote site.
CR 13535: Frame Relay.
Cannot configure protocols in direct access mode until config is
saved. To reproduce the problem create a config from scratch in
either dynamic, remote or local mode. Select a sync port for
Frame Relay and enter cancel on Select Protocols. Click on the
sync port and choose edit circuit and click FR Protocol/Interfaces.
Then, click PVCS/ADD and enter in a DLCI number. Next, by choosing
direct access mode the Protocols field becomes highlighted. When
you try to add any protocol nothing happens. However, after saving
the config protocols in direct access mode can be configured.
You should not have to save the configuration file in order to
configure protocols on a direct access mode PVC.
CR 13231: X.25.
After Site Manager creates wfX25 base in dynamic mode, it creates
the wfLapbPktEntry. If this is done too quickly, the router may
PANIC.
CR 8745: IP.
Editing IP interface details under demand circuit configuration
using SiteManager version 1.71 will cause the configuration module
to complete abnormally.
CR 12483: TFTP.
Unable to specify a filename when TFTPing in v2.00. In previous
releases (1.80 and back) you could select a filename and also
specify the target filename by typing characters in at the prompt.
Now this has been restricted to point and click, 2 problems have
been found as a result of this;
1) This feature was very useful for renaming filenames at the
time of the file transfer.
2) Sitemanager cannot be used for tftp'ing Packet Capture files,
because you cannot specify a filename which is not displayed
on the flash (or diskette).
CR 10476: IP.
Cannot configure OSPF or IBGP over Circuitless IP.
Added support for running OSPF (NBMA 0 Priority) and IBGP over
circuitless IP from Site Manager. Protocols can be added/deleted
using the following methods:
Protocol->Circuitless IP->Create choose BGP/OSPF from Protocol menu.
Protocol->Circuitless IP->Change Protocols to delete/add OSPF/BGP
if Circuitless Interface already exists.
CR 10339: TFTP.
TFTP Retry Time Out param: "Enter a value between..." text
inaccurate.
CR 10338: TFTP.
TFTP Close Time Out param: "Enter a value between..." text
inaccurate.
CR 10337: TFTP.
TFTP Retransmit param: "Enter a value between..." text inaccurate.
CR 1678: Statistics Manager.
File name for saving user defined screen to disk can't
include '_' or '-'.
CR 13061: Switched Services.
When a circuit is configured to be backed up, WCP will not appear
in the Add/Delete Protocols menu.
CR 13149: ATM.
Attempting to add the same VPI/VCI value to a different ATMDXI
circuit on the router will trigger Site Manager to return the error
message stating that duplicate VPI/VCIs cannot be added. This
message should be generated when the user attempts to add a
duplicate VPI/VCI on the same DXI circuit. This should not be a
box-wide restriction.
CR 13365: Packet Capture.
If you configure packet capture on a Frame Relay link to capture
data in both directions, after running pktconv to have the capture
displayed on a sniffer all packets are displayed with source
address of DCE and destination of DTE.
CR 10614: System.
Using the Events Manager via the Events Button on the Main Site
Manager screen occasionally results in a GPF when following this
path:
Click on Events button --> File --> Get Current Log File.
If this happens, exit out of Site Manager and then retry. This
appears to be a very intermittent problem.
CR 13011: IP.
The change button, located in the IP interface screen in Site
Manager, corrupts the RIP MIB, overwrites filter names and some
other problems. The problems were introduced by editing the file
in local mode.
CR 9906: Files Manager.
In Router Files Manager: Top line of file list is continually being
defaulted as highlighted. It not only shows up as highlighted when
you first enter the view, but it is also being highlighted upon
exiting various commands from the command menu.
CR 13132: Image Builder.
PC Site Manager, directories, such as 780 rel, 800 rel 810 rel will
not be able to be switched to via Image Builder's File Change
release option (because there is no dot separating filename and
extension).
CR 13128: Image Builder.
When you have a router image up, if you select File/Change Release,
you should be shown only those releases that your router has images
for.. Instead you are shown, and allowed to "change to" ALL
releases in your directories - including ones that there is no
image for your router. Doing so give some VERY BIZARRE results.
CR 12887: Bridge.
If you are managing a 7.80 router with Site Manager 2.00 and want
to use Translation Bridge, the Translation Bridge Enable field is
not present under the Token Ring circuit;
Protocols --> Bridge --> Interface.
CR 12684: ATM.
When you define an ATM interface you are prompted for group mode
protocols, but you are not put into the VCL screen. The user should
be put into the VCL screen as they must be manually configured.
CR 13209: Report Generator.
Site Manager Report Generator does not work if Site Manager is
installed in a directory other than \wf.
CR 5918: XNS.
The XNS Host Number is padded wrong by SM. In the following
example, the host number that was set was 444. Here is what TI
displayed:
wfXnsInterfaceEntry.wfXnsInterfaceMacAddress.0.0.0.204.2 =
x04 x44 x00 x00 x00 x00
CR 13030: IP.
The Select Protocols window's "Cancel" button doesn' t work when
configuring "NEW" COM and MCT1 circuits. In the process of
configuring IP on a new COM port. When you're in the Select
Protocols window...
1) Select IP
2) Select Cancel button
The problem is here. You should be returned to the Dynamic Config
window but instead you are put in the IP configuration window.
CR 13023: Frame Relay.
If one deletes a FR DM PVC configured for backup, frame relay does
not cleanup/update the appropriate SWSERV entries and does not
unload PPP. As a result, the connector is not freed up and the
SWSERV entries are not up-to-date plus PPP is not deleted.
CR 12957: Statistics Manager.
Clicking on the Description menu option in the Launch Facility
window results in G.P.F Application Error 'WFLNCH!.EXE'.
CR 13426: Bootp.
The BootP Interface address and forwarding interface table takes
too long to display.
Getting the bootp interface list (Protocols->IP->Bootp->Relay
Agent Interface Table) has been improved so that it is now
substantially (order of magnitude) faster.
CR 12879: Bootp.
Deleting an interface from the Bootp Relay Agent Table, will not
delete corresponding entries in the Bootp Relay Agent Forwarding
Table.
CR 6994: Filters.
Can't define more than 40 user defined filters. Edit a config
locally, define a bridge port and then add traffic filter on it.
Choose User defined, size 96, Offset 0 and then add 50 ranges.
When you save and go back to edit filter. On the list of ranges,
some are missing and only the first 40 (or 41) are left.
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 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 which 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, first boot the router with the
ti.cfg and then save the file. This will update ti.cfg with the
appropriate MIB stamp.
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
