 |
|||
     |
|||
Site Manager Revision 5.02/Revision 5=============================================================================
SITE MANAGER COMPATIBILITY
=============================================================================
Site Manager Revision 5.02/Revision 5 is a post 5.00 revision. This version is backwards compatible and supports the following router versions: 11.02
11.01
11.00
10.01
10.0
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.02 Revision 5 corrects the following problems:
=============================================================
CR 35261: LLC.
If you configure DLS/LLC on an ATM circuit, the LLC1 pull-down menu
on the Service Record window is missing for that circuit.
CR 32366: ATM.
Site Manager sets the "Per-VC Clipping" parameter to an invalid
value when you modify other parameters in the window.
CR 34919: PPP.
Editing the RFC1661 Compliance field in Site Manager for dialup PPP
circuits changes the wfPppLineRfc1661Compliance attribute, but not
the wfSwservOptsRfc1661Compliance attribute. You must set the
wfSwservOptsRfc1661Compliance attribute and the
wfPppLineRfc1661Compliance attribute to the same value.
CR 32581: Site Manager
When you select a slot in which a DS3 or E3 module is installed,
Site Manager displays the wrong part number for that module.
CR 34717: ISDN.
When deleting PRI from an MCT port, Site Manager fails to delete the
local telephone number associated with that port.
CR 34229: IP traffic filters.
When you reorder IP traffic filters on an interface that has fewer
than 32 filters, Site Manager disables the IP extended support
parameter. This occurs even if there is another interface on the
router that has more than 32 traffic filters and requires that the
parameter be enabled. Interfaces requiring this parameter to be
enabled will not apply any filter above the 32nd filter.
CR 34297: PPP.
When you configure source route bridging on a switched services
circuit, Site Manager fails to enable BCP for that PPP circuit. As a
result, BCP is never negotiated when the dial circuit is
established and bridging does not work on that link.
CR 34152: IP traffic filters.
When reordering the IP traffic filters, selecting INSERT AFTER
inserts the filter before the precedence number that you selected.
This condition occurs in both dynamic and local mode.
CR 34024: BISYNC.
Currently, the BISYNC code is hardcoded for 2 leading SYNC
characters. The Bysync protocol should support 7 leading SYNC
characters.
CR 34527: BootP.
When you add an entry to the BootP Relay Agent Preferred Server
Table, Site Manager may display leading ??? characters and an
incorrect Relay Agent IP address in the table.
CR 33887: SYNC.
In Statistics Manager, the Octets In and Octets Out fields in the
SYNC Traffic Information window do not get updated after selecting
Options > Zero All Counters.
CR 33935: ATM.
If you click the SAAL button in the "Edit ATM Connector" window and
the ATM signal AAL record list is empty, an error message appears.
CR 34120: HSSI.
Site Manager does not set the correct default of 32 bits for the CRC
Size parameter (wfHssiCrcSize).
CR 34239: Router Redundancy.
A general protection fault (GPF) occurs on the PC when you use the
"Edit Lines" facility from a non-primary router redundancy interface
to select another line.
CR 34819: LLC2.
LLC Circuit pull-down option displays to the right of Help option
instead of to the right of the Window pull-down option. This problem
occurs only on the PC.
CR 33787: ISDN.
There is a problem with Site Manager that may result
in Site Manager erroneously enabling BOFLs on an MCT-1 module. If
you select a primary circuit on an MCT-1 module from the Dial Backup
Circuits window, click on Cct Type to display the Circuit
Type and the Backup Pool ID, and then click on OK without making
changes, BOFLs are enabled on all logical lines of the MCT-1. This
action disconnects all dial-on-demand and dial backup circuits
configured on that port.
CR 31779: DLSw.
Added the following MIB attribute to the router software:
wfDlsLocalDeviceEntry.wfDlsLocalDeviceEnableXidPassthru Must add the parameter "Enable XID PassThru" to Site Manager. CR 31694: DLSw.
CR 33647: When configuring DLSw on a token ring interface, no source route
bridge windows or prompts appear.
CR 34370: DLSw.
If you add DLSw to a second token ring network, Site Manager sets
the Bridge ID to 0.
CR 34335: Frame Relay.
When you delete a frame relay PVC or service record, Site Manager
does not display a confirmation prompt.
CR 34391: DLSw.
When you configure a new DLSw/SDLC circuit in dynamic mode, the
Source SAP and Destination SAP parameters are missing from the DLS
Local Device Configuration window. Also, Site Manager corrupts the
values you entered for the Source MAC and Destination MAC
parameters.
CR 34023: SDLC.
If you have a router with an SDLC connection to a controller and the
frame relay link is broken (or the FEP is down), the router should
stop polling the controller until it receives a DLSw contact
frame from the controller. Currently, the router polls the
controller before it receives the DLSw contact frame.
CR 34119: Site Manager.
Unable to change the name of an ISDN leased line configured on a BRI
interface when using the Change Lines option from the Circuit
Definition window.
============================================================= 5.02 Revision 4 corrects the following problems: ============================================================= CR 33787: ISDN.
There is a problem with Site Manager that may result
in Site Manager erroneously enabling BOFLs on an MCT-1 module. If
you select a primary circuit on an MCT-1 module from the Dial Backup
Circuits window, click on Cct Type to display the Circuit
Type and the Backup Pool ID, and then click on OK without making
changes, BOFLs are enabled on all logical lines of the MCT-1. This
action causes all dial-on-demand and dial backup circuits
configured on that port to lose connectivity.
CR 33931: Site Manager Installation.
After you install Site Manager, a message should appear, indicating
the environment variables that need to be defined to run Site
Manager.
CR 33602: IP.
Site Manager allows static routes with invalid subnets to be
created.
CR 33882: IP.
In Site Manager, under Protocols > IP > SNMP > Trap > Interfaces,
RREDUND is not listed as an available entity. In Site Manager, under
Protocols > IP > SNMP > Exceptions, when you add an exception for
the Entity Code 98, it lists the entity name as NULL.
CR 33311: DLSw.
Site Manager is missing the LLC Circuit option for an
ATM DLSw interface.
============================================================= 5.02 Revision 3 corrects the following problems: ============================================================= CR 32864: IPEX.
If a failure occurs at the remote IPEX IP interface, IPEX can no
longer establish TCP connections with the remote IPEX routers.
An enhancement to the current IPEX implementation allows you to
configure the secondary remote IP interface for backup using
the new MIB attribute wfIpexMappingRemoteBackupIp.
CR 18444: Switched Services.
The capability to specify a total exclusion of a weekend/weekday/
specific day is missing. The ability to define a Scheduler entry
of weekday/weekend or specific day with the mode set to Not
Available is required. Currently, you can specify only the
available time period.
CR 32524: PPP.
After upgrading to BayRS Version 11.02, PPP connectivity
problems occur because of the new defaults for the MRU size.
There are two new MIB parameters that you can set to comply with
the suggested MRU of 1500 in RFC 1661:
wfPppLineEntry.WfPppRfc1661compliance
wfSwservOptsRfc1661compliance
CR 33151: IPEX.
A problem exists between BayRS Versions 11.00 and 11.02
implementations of IPEX in which an 11.02 router cannot establish
calls with an 11.00 router. Added a new MIB parameter,
wfIpxInsCallingDte, in IPEX base. The default is disabled to prevent
the calling DTE address from being added, but will allow routers
running BayRS 11.02 to interoperate with lower revisions of code.
CR 28170: Router Redundancy.
Enhancement request to add a new attribute (wfRRedundWarmBoot) to
the wfRRedundGroup object. This new object allows you to
dynamically change the role switch mode of the routers between
"warm boot" (method used in software version 11.00 and earlier)
and "hot swap" (method used in software version 11.01 and later).
Please note that the "warm boot" and "hot swap" versions are
incompatible, therefore, all routers running Router Redundancy must
be running the same version.
CR 30222: DLSw.
When the MIB version of a router is lower than 11.00, the IP
addresses in the DLSw Peer IP table are not visible.
CR 32489: Hot Standby.
The Hot Standby code in the router supports the backup of a
primary circuit configured as a bandwidth on demand circuit.
However, Site Manager prevents BOD circuits from being backed up
by the Hot Standby feature.
CR 31518: Router Discovery.
When configuring a Discovery router, Site Manager allows you to
configure the minimum and maximum interval to the same value. The
Help screen indicates that the minimal interval value should be
less than the maximum interval value. The maximum interval should
be at least 4 greater than the minimum interval value. Site Manager
fails to check whether the values are valid.
CR 31906: Multiline.
Protocol Priority fails to display in the Protocols box with
multiline configured.
CR 32581: DS3.
Site Manager displays the part number AG13110114 for DS3Os, which
is incorrect. The correct part number is AG13110115.
CR 28953: Router Redundancy.
When adding router redundancy to a circuit, only the IP and
RIP should be available. When you select router redundancy to
add protocols, unsupported protocols should be deselected (or made
inactive).
CR 30930: SM-OTHER.
The connection list does not reflect the router that has the SNMP
connection.
CR 32915: ARN.
Unable to add TCP, Telnet, or FTP to an ARN router after creating
a new configuration file.
CR 31478: SM-OTHER.
Restarting Site Manager and adding the fully-qualified name of a
router caused Site Manager to immediately abort.
CR 32311: APPN.
Unable to change the Adjacent Node Type parameter from the default
value LEARN.
CR 32461: SM-OTHER.
When installing PC Site Manager, you will notice that the install
screen % complete is inaccurate. The % complete runs up from
0%-89%, then jumps back to 59%. On its way back up, it bounces
back and forth 92%, 93%, 92%, 93%, 94%, 93%, and so forth.
CR 32599: SM-OTHER.
After installing Optivity and populating the Site Manager database,
the router icons for Bay Networks routers are incorrect. When you
run the WFSM_INSTALL script, Site Manager removes the
/usr (or /opt) /lnms/snm/icons/synfleet-router.icon and synfleet-
router.icon files.
CR 28082: ATM.
The ability to enable the SSCS Type field in AAL5 for
interoperability with an IBM ATMARP Server (IBM’s MSS, an ATM ARP
Server for their Switch) is missing.
CR 32129: QLLC/DLS/X.25.
After configuring X.25 with QLLC as the service type and adding
DLSw from the X.25 Service Configuration screen, Site Manager
faults when you select the X.25 service record in the list box.
CR 32127: QLLC/DLS/X.25.
After configuring a circuit with X.25 and QLLC as service type and
adding DLSw from the X.25 Service Configuration screen, DLSw
remains active on a circuit even after you have deleted it (from
the Configuration Manager screen).
CR 32663: Frame Relay.
Frame Relay is not listed under the available WAN protocols for
the AN200 router.
CR 31733: Image Builder.
When the file name of a screen you saved using Image Builder is
13 characters or longer and has a description associated with it,
Site Manager combines the name and the description, causing the
screen to corrupt. You cannot delete these corrupted files with
the Screen Manager utility.
CR 27728: Thresholds.
You are unable to set the Threshold Max Successive Alarms and the
Threshold HoldDown Intervals to values other than their defaults.
CR 31864: SYNC.
The default parameter for Sync Passthru is incorrect.
CR 32110: Statistics Manager.
The Resource MIB is not included in the Statistics Manager utility.
CR 32427: Report Generator.
rpt2cfg fails to set SysName to indicate that the configuration
was built with it.
CR 32350: Token Ring Endstation.
When editing the IP or IPX interface entry of a demand circuit
group, Token Ring Endstation can be enabled but should not be
selectable.
CR 29400: Protocol Priority.
Site Manager allows you to configure the value 0x0021 for the PPP
Protocol ID in priority outbound filters.
CR 28238: SDLC.
SDLC addresses display incorrectly as decimals in the Site Manager
"Show Circuits" screen.
CR 33279: Protocol Priority.
Protocol Priority still does not display in the protocol box for
the circuit, in the protocol menu when editing a circuit, or when
selecting protocols from the main screen.
CR 33355: SM-OTHER.
Performance suffers when configuring a router running BayRS Version
11.00 or later in dynamic configuration mode. When configuring dial
backup in large configurations, it may take several minutes for
the Backup Circuits screen to display because of the inordinate
number of SNMP GETS and replies being performed by the Site
Manager station.
CR 33126: Report Generator.
The Report Generator cannot recognize the new protocols that have
been added.
CR 33097: SNMP.
Unsupported "Hardware Inventory Report" (hdwrpt) tool required the
addition of SNMP language features from the SNMPerl 1.6 Dynamic
Library. However, this library did not get submitted to later
baselines of Site Manager, preventing the hdwrpt tool from
behaving as expected. Disabling an ATM service record while SPT is
turned off globally causes a Vector 2 - MCP error to occur on the
ARE slot.
CR 32970: BGP.
Site Manager prevents you from configuring more than 1 BGP soloist
slot when working with an ISP Mode router (11.00ISP or 11.01ISP).
Any attempt to configure more than 1 soloist slot results in an
error.
CR 26320: Configuration.
The CHAP/PAP password is changed after you exit from the backup
primary circuit types.
CR 33004: Dial Backup.
The Report Generator fails to write to the PC root directory.
CR 30060: SM-OTHER.
The system name that displays does not match the name in the
connection list.
CR 26479: Statistics Manager.
The IPX Circuit screen displays incorrect information when invoked
from the Statistics Manager utility.
CR 33277: TR Endstation.
The TR Endstation ARP type should not be available when configuring
Demand Circuit group.
CR 27715: File Manager.
Files should display in lexicographical order in the Files Manager
TFTP Put screen and in local configuration files list.
CR 29473: NTP.
IP Mask parameter incorrectly defaults to 0.0.0.0.
CR 33797: IP.
A tag violation error may occur on a router when you attempt to
dynamically create an IP filter.
CR 33796: IP.
You can create the IP traffic filter ’Forward to Next Hop’
but you cannot edit it locally or dynamically.
CR 33861: IP.
The Token Ring Endstation ARP type field is missing from the IP
interface definition, even on a Token Ring circuit.
CR 33482: ISDN.
Opening a local configuration with an ISDN adapter module Port
Application Mode configured for 2B+D produces the following
warning message "WARNING: Empty Module 2 has circuits configured".
============================================================= 5.02 Revision 2 corrects the following problems: ============================================================= CR 15970: IP.
If you configure IP on a router interface, edit the interface to add
BootP, and then edit the interface to add another IP address, the
second IP address does not show up in the BootP Relay Agent
Interface Table. This problem does not occur if you select BootP at
the same time you create the IP circuit.
CR 24057: Site Manager.
Running the rpt2cfg command fails to recreate circuitless IP.
CR 30906: IP.
A problem exists when applying a template to a circuit that has one
IP source address range, 22 IP destination address ranges, and at
least one TCP destination port. When this template is applied to a
circuit, it shows up in two fragments. Neither fragment has a
circuit number or IP address; both fragments are inactive.
CR 31270: Frame Relay.
When you configure frame relay multiline, frame relay
does not appear in the WAN protocols window.
CR 27059: APPN.
APPN/DLUR connected via SDLC to 3174 fails at XID negotiation.
CR 30658: IP.
Site Manager does not allow you to activate the third filter in an
IP traffic filter configuration.
CR 31124: BGP.
If you create a BGP announce policy in dynamic mode, the Origin
field defaults to 0. This is not a valid value.
CR 31334: PPP.
Bandwidth-on-demand PPP circuits do not appear in the Bandwidth-on-
demand circuit definition window.
CR 31428: BGP.
The BGP-4 accept policy allows you to include in an injection list
only the default network ID, 0.0.0.0/0.0.0.0.
CR 31474: DLSw.
When you add DLSw to a token ring interface that already has Source
Route Bridge configured, the DLSw Basic Interface window
incorrectly displays the SR Interface Ring ID as 0x0. The field
should display the Interface Ring ID that was already configured
when you configured Source Route Bridge on the interface.
CR 31516: BGP.
After changing an IP address of an interface, the APPLY and PEER
buttons no longer appear on the IP Interface List for BGP window.
CR 23647: PPP.
Running the rpt2cfg command fails to recreate PPP record number
65535.
CR 26777: SYNC.
You cannot configure ASYNC on the COM2 port of an ASN.
CR 26864: Statistics Manager.
When using the Stop Retrieval option from the PC Site Manager
Statistics Manager Quick Get facility, an SNMP receive error (Packet
to Big) occurs.
CR 28231: SDLC.
Site Manager sets the APPN parameters Total Link Activation
Limits, Inbound Link Activation Limits, and Outbound Link Activation
Limits to invalid values. If you define an SDLC line with two 3174s
and DLUR/DLUS, only one device is polled.
CR 28663: Site Manager.
When using BCC to configure a router, TFTP must be explicitly
defined. If TFTP is not defined through BCC, when you choose
Protocols > IP > TFTP from Configuration Manager, a general
protection fault occurs.
CR 28981: OSPF.
The OSPF Maximum Equal Cost Paths parameter on the OSPF Global List
window should be removed. The parameter supports an OSPF multipath
feature, which is not supported in BayRS Version 11.00.
CR 29012: IP.
The RIP Maximum Equal Cost Paths and Multiple Next Hop Calculation
Method parameters should be removed from the IP Global window. These
parameters support the RIP multipath feature, which is not supported
in BayRS Version 11.00.
CR 29466: DLSw.
When you configure two DLSw traffic filters, the first one created
is correct. However, when you create the second filter using the
same action, the action disappears from the template.
CR 29693: IPX.
If you create an ATM service record, add IPX and then select Service
Record > Protocols > IPX > Interfaces, the IPX Token Ring End
Station parameter is greyed out. This parameter should be accessible
in Site Manager.
CR 31034: TCP.
The TCP_ESTABLISHED traffic filter uses incorrect filter criteria.
The filter should be implemented to key on the 107 - 109 bits within
a TCP/IP packet. It should be used as an accept filter,
allowing a router to make outgoing TCP connection requests, but not
to accept an incoming SYN.
CR 31092: BGP.
Site Manager incorrectly allows you to configure a non-local address
for the BGP peer local address parameter.
CR 31523: Site Manager.
Site Manager loads NTP only on slots that contain configured link
modules. NTP must be loaded on all slots.
CR 24206: IPX.
If you change the default values for the FR Broadcast or the FR
Multicast parameters on the IPX Interface window, you cannot change
the values back to the defaults by leaving the fields blank.
Instead, Site Manager assigns each parameter a value of 0x00.
CR 24435: APPN.
The Adjacent Node ID Number and Adjacent Node Block Number fields in
the APPN/SDLC Adjacent Link Station Configuration window are
labelled incorrectly. The Adjacent Node ID Number field actually
represents the Adjacent Node Block Number field and vice versa.
CR 30033: DLSw.
Site Manager should support a MAX PDU greater than 2057, which is
the current limit for SDLC links.
CR 28238: SDLC.
When viewing the Show Circuits and Show LS Stat parameters, the
SDLC address appears in decimal notation, not the 2-digit
hexadecimal value entered.
CR 18444: Switched Services.
Site Manager does not allow you to exclude a weekend, weekday or
specific day with the current scheduler implementation. An
Availability Mode parameter has been added to Site Manager.
CR 31757: Site Manager.
If you use the Technician Interface to delete instance number 4 for
Serial Port Entry on a VME platform, Site Manager recreates
instances 2, 3, and 4.
CR 26176: LNM.
If you delete LLC2 from a circuit that has an LNM Server configured
on it, in dynamic mode, SNMP set errors occur; in local mode, Site
Manager terminates.
CR 23862: FDDI.
After you delete an FDDI link module from a slot, enhanced FDDI
parameter tables remain in the configuration file.
============================================================= 5.02 Revision 1 corrects the following problems: ============================================================= CR 31503: FireWall.
Added support for FireWall.
CR 31908: FireWall.
When you add FireWall to your router, a warning message similar to
the following should appear:
"Adding FireWall to your router configuration will cause loss of IP
connectivity through any ethernet or frame relay port. You should
only proceed if your policies are ready to be downloaded to your
router."
CR 31936: FireWall.
No online help is available for the FireWall parameters in Site
Manager.
CR 31011: FireWall.
When you configure FireWall for an ASN, using Site Manager,
the Site Manager application hangs.
============================================================================= 5.02 Revision 1 corrects the following problems: ============================================================================= CR 31503: FireWall. Added support for FireWall. CR 31908: FireWall. When you add FireWall to your router, a warning message similar to the following should appear: "Adding FireWall to your router configuration will cause loss of IP connectivity through any ethernet or frame relay port. You should only proceed if your policies are ready to be downloaded to your router." CR 31936: FireWall. No online help is available for the FireWall parameters in Site Manager. CR 31011: FireWall. When you configure FireWall for an ASN, using Site Manager, the Site Manager application hangs.
Feedback | Service Search | ERC Copyright © Bay Networks,Inc., 1997. All rights reserved. |
/tr> |
