 |
|||
     |
|||
|
Site Manager Revision 5.01/Revision 2
Site Manager Revision 5.01/Revision 2 is a post 5.00 revision. This version
is backwards compatible and supports the following router versions:
11.01
11.00
10.01
10.0
9.00
8.10
8.01
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.
=============================================================================
5.01 Revision 2 corrects the following problems:
=============================================================================
CR 15970: Configuration.
After you configure an IP circuit, edit the circuit by adding
BOOTP to it, then edit the interface again to add another IP
address to the interface, the second IP address will not display
in the BOOTP Relay Agent Interface table. This problem does not
occur if you select BOOTP and IP at the same time when creating
the circuit.
CR 30654: DLSw.
Site Manager faults when you configure DLSw after configuring
Frame Relay PVC with IP and RIP.
CR 28164: SM-OTHER.
If you are connected to multiple routers with different community
names, the last router does not get moved to
the top of the list but the community name does.
CR 29256: BOT.
You receive a bus error when you attempt to add a BOT interface to
an ASN router.
CR 29717: SM-OTHER.
When you attempt to run the rpt2cfg tool on the HP-UX platform, an
error occurs.
CR 30154: Configuration.
If you configure BGP on a circuit on the BGP soloist slot (and
that circuit is the only circuit with BGP on that slot) and you
delete the circuit, Site Manager will unload BGP from the soloist
slot.
CR 30216: SM-ADMIN.
Cannot edit or change the community name using Site Manager version
5.01. When you attempt to change the community name, Site Manager
fails to respond. It should display a screen that enables you to
change the community name.
CR 30415: SM-Configuration.
The auto negotiation configuration window is missing in Site
Manager Dynamic Configuration version 5.01 and 5.02.
CR 30418: OSPF.
When you attempt to change an interface type from point-to-point
to broadcast in remote mode using Site Manager version 5.01, Site
Manager sets the MIB to invalid. However, you can perform this
same operation successfully in dynamic mode.
CR 30476: Frame Relay.
When using Site Manager version 5.01 for Windows, you cannot
access the PVC list for a Frame Relay circuit using a version
11.0 configuration file.
CR 26615: SM-CONFIG.
Site Manager allows you to add any LAN protocol to SDLC or
PassThru in Circuit Definition window.
CR 29340: QLLC.
In dynamic mode, if you add a QLLC-type X25 service record
to a circuit, add one QLLC map entry, then add a PDN-type X25
service record with the IP/RIP protocol for the same circuit,
error message when you attempt to add a QLLC map entry in the
QLLC-type X25 service record.
CR 29340: SM-ADMIN.
Site Manager produces a core dump when you attempt to add a X.25
service configuration entry.
CR 30092: SM-OTHER.
Unable to configure global memory using Site Manager Kernel
Configuration when running Site Manager versions 5.00/2 and 5.01
on an ASN2 router.
CR 30417: SM-CONFIG.
The Line Advertising Capabilities field in the Auto Neg
Advertising Capabilities window displays numbers rather than a
text description. This problem occurs in versions 5.00, 5.01, and
5.02.
CR 30763: ATM LANE.
A method is required to allow you to set the Lec Local Seg ID for
a Token Ring end station using Site Manager.
CR 27712: APPN.
APPN adjacent link station configuration screen displays ID BLOCK
and ID NUM in reverse order. ID NUM column should read ID BLOCK
and ID BLOCK column should read ID NUM.
CR 27764: SM: Configuration.
When using the Syslog facility, Site Manager allows you to add
more hosts than the maximum allowable number in the maximum
number of hosts field.
CR 27880: APPN.
Site Manager allows you to configure multiple SDLC addresses
when editing a SDLC interface.
CR 27951: APPN.
When configuring an APPN Adjacent Link Station with DLUR on an
SDLC link, the Adjacent Node Type should default to DSPU NO XID.
CR 27952: APPN.
Site Manager allows you to select HPR support and DLUR support on
the same adjacent link station. DLUR is reserved for non-APPN
nodes. You should not be able to select HPR and DLUR.
CR 27953: APPN.
When naming the DSPU on the Adjacent Link Station, the data
should shift or translate to uppercase.
CR 27984: SM-Configuration.
The Circuit Password field in the Edit OSI Interface window
allows you to enter a password that exceeds 8 characters. The same
situation exists for the L1 LSP Password field in the Edit OSI
Global Parameters window.
CR 27986: SM-Configuration.
OSI Router Type Levels 1 and 2 fields are inaccessible.
CR 28117: SM-EVENT.
Entities in the Filters window in the Event Manager do
not filter correctly; these entities are known to acquire
unrelated entities. For example: RARP also acquires ARP entries;
NOV_SYNC acquires SYNC entries, and ASYNC acquires SYNC entries.
CR 28300: SM-Configuration.
Site Manager does not allow you to rename a configuration file
when configuring a local file. Instead, Site Manager automatically
saves the configuration file as the same name.
CR 28741: QLLC.
The QLLC option button can disappear on X.25 services window if
IPEX is received.
CR 29270: SM-OTHER.
The Report Generator report template does not use the correct
directory or extension.
CR 29506: SM-EVENT.
On a BCN router, the Events Manager filtering is off by -1 for
slots 8 through 14. Thus, to filter on slot 10, for instance, you
must select 11 in the filter field.
CR 29698: SM-Configuration.
Unable to change IP Address of the Circuitless IP parameter.
CR 29700: SM-Configuration.
When you create a circuitless IP address with OSPF and
then change it using Protocols-->IP-->Interface, the address will
change only in the IP interface, not in OSPF interface (they are
supposed to be the same). Also, after you make this change and
you select Protocols-->IP-->Circuitless IP, the "create" option
is active. This is incorrect because there can be only one
circuitless IP.
CR 29701: SM-Configuration.
Site Manager for Window allows you to configure a Class C network
with a mask greater than 24 bits (255.255.255.0) on the router's
first interface, even though the IP Global parameter Zero Subnet
Enable is disabled. The parameter is checked when configuring all
subsequent interfaces.
CR 29733: SM-Configuration.
When you delete a circuit configured with a BGP peer, the
BGP peer information does not get deleted from the MIB.
CR 29784: BGP.
When you add a BGP announce policy, the default value for the
"Origin" attribute displays as "4" in Site Manager. This does
not correspond with the values displayed in the Help (AS_IS,
IGP, EGP, INCOMPLETE), and also does not match the values
in the MIB itself (1=IGP, 2=EGP, 3=INCOMPLETE, 4=NONE).
CR 29785: BGP.
There is a mismatch between the "values" given for the "atomic"
attribute and the corresponding help in BGP announce policies.
The options are: AS-IS, FORCE, and IGNORE. The Help displays the
following options: AUTOMATIC, FORCE and IGNORE.
CR 29786: BGP.
here is a mismatch between the "help" and "values" for the
"local-pref-override" attribute in BGP announce policies.
The values display a range from 0-21474836, whereas the help
displays a range from 0-4294967295.
CR 29787: BGP.
In BGP Announce policies, Site Manager allows only values up
to 65535. MED in BGP is defined as a 4 octet value, therefore
values up to 2^32 should be allowed.
The Help also does not mention a valid range.
CR 29989: SM-Configuration.
Site Manager CM need to remove 12pt EHub/2S/CSU_DSU/N11/DCM from
the module list.
CR 30001: SM-Configuration.
Site Manager faults using Site Manager 5.01 when you attempt
to list protocols/PPP/interfaces, regardless of router platform.
CR 30034: DLSw.
The default sync MTU is 1600 bytes. DLSw/SDLC allows you to
configure MAXDATA with a larger value than the value used to
configure the sync MTU.
CR 30135: SM-Configuration.
The BGP Accept Policy Injection List displays two columns labeled
"Network Number". The second column in the BGP Accept Policy
Injection List should be labeled "Network Mask".
CR 30137: SM-Configuration.
You must configure a network number and network mask in the
Injection List of a BGP Accept Policy (the second column should be
labeled 'Network Mask'; CR30135). Currently, Site Manager does
not check to make sure that a Network Mask is configured for a
Network Number.
CR 30663: SM-OTHER.
A problem occurs in the Well-Known Connection List, causing Site
Manager to experience a General Protection Fault (GPF).
=============================================================================
5.01 Revision 1 corrects the following problems:
=============================================================================
CR 27267: Filters.
After you finish editing a filter, Site Manager immediately
proceeds to delete the filter. If the filter that you are editing
accepts your IP address, and there is another filter that drops
your IP address, you can be filtered out of your router.
CR 29436: Switched Services.
When you specify Async as the Out Phone Num Type, Site Manager
experiences a General Protection Fault (GPF) error in Dynamic mode
or exits out abnormally in both Remote and Local mode.
CR 29439: Switched Services.
When you attempt to dynamically list 80 PPD DOD interfaces on a
PRI line, Site Manager faults.
CR 26690: IPX/PCSM.
When you use the IPX Change utility to change an IPX circuit to
IPXWAN or an IPXWAN circuit to IPX, PC Site Manager experiences
a GPF error.
CR 26980: IPX.
When you delete an IPX interface and then add the interface
in the Circuit Definition window, Site Manager experiences a GPF
error.
CR 29337: Policy Filters.
When configuring and viewing the Networks list for RIP/OSPF/BGP
policy filters, the match criteria shows incorrect information
when more than 5 network entries are present. The list of networks
and the range scroll properly when you check them, however, the
exact match criteria does not scroll properly.
CR 27365: BGP.
After adding several networks (approximately 16) to the network
lists in BGP Announce Policies, Site Manager corrupts the list,
causing the router to eventually fault.
CR 27943: BGP.
Changing BGP Global parameters using Site Manager 5.00/2 unloads
BGP from wfProtocols, preventing it from displaying in the loadmap.
CR 29596: BGP.
If while operating in ISP mode you attempt to dynamically
add a new BGP peer to a slot that you had not previously
configured for BGP peers or for the BGP soloist, Site Manager will
incorrectly load BGP on that slot.
CR 27808: BGP.
When creating BGP4 Accept Policy Filters, you cannot set the two
parameters, Route Preference and BGP4 Preference, to a value
other than 1 (default). If you attempt to set these parameters to
a value other than the default (possible values range from 1-16),
Site Manager automatically sets it back to the default value.
CR 27044: MCT1.
A customer request to add a confirmation prompt before you can
delete a logical line on a dual MCT1 or Quad MCT1. This prevents
accidental deletion of the logical line.
CR 27894: DLSw.
DLSw Mode on the DLSw Local Device screen defaults to
Primary mode in all cases.
CR 29463: SDLC.
Site Manager does not set the MIB entry
wfSdlcLSAdminEntry.wfSdlcLSAdminRole to secondary; it remains
primary.
CR 29659: Frame Relay.
Site Manager fails to show changes made in dynamic mode.
CR 28508: DLSw.
You should be able to configure the DLS Global parameter, MAC
Cache Age (MIB Parameter wfDls.wfDlsMacAgeTime), with a value of 0.
Setting this parameter to 0 is helpful when redundant TIC
addresses are in use and every test poll should be delivered to all
DLS peers.
CR 27944: BGP.
Configuring BGP or BGP peers will incorrectly set Local AS or Peer
AS to a negative number, if you set the AS to a value greater than
32767.
CR 27280: BGP.
Site Manager fails to configure a BGP peer to a multinetted address
on an interface correctly. Instead, Site Manager adds the peer to
the lowest address on the interface.
CR 29886: Scripts.
The directory /usr/wf/scripts contains the inst_arn.bat file,
which does not belong there.
CR None: Scripts.
The Metrics script faults in the .rpt directory, yielding
inaccurate results; the PCSM terminal shows "Copyright 1993,
Wellfleet Comms. Inc."
CR 28746: IP/ETF.
Using Site Manager to create and edit IP/ETF's can prove
troublesome when multiple traffic filters are already configured
on the router. Whenever you make a change, Site Manager retrieves
all traffic filter instances for that interface.
CR 29856: IPX.
An IPX static route does not assume the cost of its associated
interface when the static route cost is the default.
CR 30090: PPP.
A problem exist in Site Manager Version 4.01 in which Site Manager
continues to prompt for a "Caller Resolution Table and/or "PAP/CHAP
Local Name," even though Authentication Protocols is set to
None.
CR 29925: OSPF.
A problem exists in AIX Site Manager Version 4.01/2 in which
Site Manager fails to display a Global OSPF parameter. This
problem is specific to the ASN router.
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
