Site Manager Revision 4.00/Revision 2
Site Manager Revision 4.00/Revision 2 is a post 4.00 revision. This version
is backwards compatible and supports the following router versions:
10.0
9.00
8.10
8.01
7.80
7.71
Note: When running revisions 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 revision that are not supported
in a Site Manager revision. Refer to the revision notes for both Site
Manager and router software.
4.00 Revision 2 corrects the following problems:
=============================================================================
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. The maximum
value has been increased to 500 entries on the UNIX-Site
Manager platform and 100 entries (formerly 64) on the PC platform.
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 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 22137: Source Route Bridge.
The parameter 'Max Number Query Cache Entries' in Site Manager
is limited to 100 entries. However, from the Technician Interface,
the same parameter, 'wfBrSr.wfBrSrBaseNbMaximumQueryEntries',
allows you to set a value greater than 100. The maximum value
allowed now is 2147483647.
CR 22315: SM-Configuration.
When you attempt to add a new X.25 sync circuit on a router
running Version 8.10, the Add button in the Service Configuration
screen is missing. When the screen switches from adding the packet
layer, an error message is displayed.
The edit menu also did not contain the add function.
CR 22984: Frame Relay Switch.
When you attempt to change the value of the FDDI bit mask for Stats
Data Collection using Site Manager, the router displays a
NIL value.
CR None. BNX-SM.
Added Atmizer physical line support for statistical data collection.
CR None. SM-BNX.
Enhancement request to query the user on PVC duplicate/overwrite.
This enhancement queries the user on the Frame Relay Switch and
the ATM router side of the configuration. The user must decide
whether or not to overwrite an existing/duplicate VC/Dlci.
CR 23121: SM-BNX Switch.
Site Manager must check that a duplicate Call IP address and PVC
do not exist on the same DLCMI.
CR 22048: SM-5000R.
When you perform a "named boot" on separate partitions of a Flash
card on a 5380 router module, Site Manager generates an error
message, indicating that the boot command failed.
CR 22958: SM-BNX.
Customer request to add the proceeding 0 to the telephone number
and to append the telephone number with ffff's. This would
require the user to add only the telephone number.
CR 22990: SM-CONFIG.
If you use Site Manager 3.01 Windows to manage a CN router
running 8.11 fix 4 (with an 8.10 MIB stamp) and attempt to
access the configuration file, Site Manager sets wfProtocols.1.0
to 0. This unloads IP from all the slots in the router.
CR 23607: SM-Builder.
The Save As function does not always work properly. One reason
why this problem occurs is that the header file versions in the
image do not match. Site Manager should generate an informational
message informing the users of this condition.
CR 22447: SM-OTHER.
Site Manager install does not modify the file
/usr/OV/conf/oid_to_type correctly, thereby causing Site Manager
to fault.
CR 22876: SM-CONFIG.
Site Manager's dynamic configuration does not delete Frame Relay
interfaces when you delete an MCE1 circuit.
CR 22957: SM-BNX Switch.
This is no help for the Cross Net Listen Enable parameter.
CR 22970: SM-BNX Switch.
Site Manager requires Help information on ATM OAM in the DLCMI
management screen.
CR 23563: SM-BNX Switch.
When configuring Frame Relay circuits (either UNI or Demand),
Site Manager creates DLCMI entries after it warns you
that a duplicate IP has been entered and that the circuit is not
configured. The IP portion of the circuit is not created, but the
DLCMI and the CircuitNameEntry is created.
CR 23654: SM-BNX
When deleting ATM interface dynamically, Site Manager
generates an erroneous screen. This screen indicates that
Frame Relay Switch is configured on this circuit. It also allows
you to delete Frame Relay Switch, IP, and change the
DLCMI interface IP address to use the IP interface screen. If
you click on OK, Site Manager proceeds to delete the ATM
interface.
CR 23701: SM-BNX.
After you delete the IP Interface and add a new interface with a
different IP address, Site Manager fails to warn you that this
action may affect the Frame Relay Switch interface,
since the IP address must map there too.
Site Manager should display a warning message to prevent you from
making this mistake.
CR 22728: Configuration.
Unable to use 4.00 Site Manager to configure Backup circuit on
8.1x series configuration file when an Integrated ISDN BRI port is
used in Backup Pool. This problem occurs because the
Backup circuit option under the Dial Up pull-down list from the
Configuration Manager window is disabled (greyed out).
CR 23385: Configuration.
IP unnumbered associated address is incorrectly set to
byte-swapped value in the Demand Circuit Group.
CR 23756: SM.
When installing Site Manager on a system with OpenView already
installed, Site Manager generates the following error messages:
HP OpenView detected: installing Site Manager hooks...
cp: cannot create /symbols/C: No such file or directory
cp: /bitmaps/C not found
CR 23185: SM-BNX.
The Atmizer "Phy Enable Disable" attribute,
wfStatsDcAtmizerPhyDisable, is no longer being supported in the
stats.mib, and therefore Site Manager must no longer attempt
to reference it.
CR None. Configuration.
The router generates GPF error messages when you attempt to add
a static service whose server name exceeds 44 characters.
CR 19717: SM-JAM.
Adding a adjacent host to an existing configuration causes Site
Manager to fault. Site Manager works properly if an adjacent host
is already in the list and you simply add another one to the
list. However, it faults when there are no adjacent hosts already
configured.
CR 23600: Configuration.
When you attempt to add a BGP peer to a Version
8.10 configuration file, Site Manager generates a GPF error
in the file WFCFG.EXE.
CR 23954: SM-BNX Switch.
When adding a new Frame Relay ATM Interworking circuit in dynamic
or local mode, Site Manager generates the wrong PVC screen.
CR 22933: Configuration.
Site Manager allows you to set the MIB attributes
wfAppnNodePortImplicitLlErrorRecovery and
wfAppnNodeLsLlErrorRecovery, to Disable. Link stations will
come up, but data will not be transmitted if these fields are
disabled in Site Manager. The fields are now set for APPN over
Frame Relay, but you cannot modify them while Frame Relay is
configured.
CR 23586: Configuration.
Source Route traffic filters remain associated with an interface
after you have deleted the interface.
CR 23811: SM-OTHER.
The Site Manager application does not recognize the module ID
number 1058, which is used by the AN2 with DCM installed.
CR 23511: Configuration.
Unidentified cell transmitted upon initialization of ATM slot.

Feedback | Service Search
| ERC
Copyright
© Bay Networks,Inc., 1997. All rights reserved.
|
/tr> |