REVISION NOTES FOR SITE MANAGER VERSION 5.03 REVISION 9

Site Manager Version 5.03 Revision 9 is a post 5.00 revision. This version is
backwards compatible and supports the following BayRS (router software)
versions:

11.03
11.02
11.01
11.00
10.01
10.0

Note: When running revisions of BayRS 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 BayRS software.

5.03 Revision 9 is Year 2000 Compliance Certified by Bay Networks. It has
successfully passed Bay Networks Test Procedure which tests conformance to Bay
Networks Year 2000 compliance definition, both of which can be found at Bay
Networks Year 2000 Web site at http://www.baynetworks.com/year2000/.

5.03 Revision 9 corrects the following problems:

CR 91577: IP
There is a compatibility problem with Site Manager on HP/UX 10.20
with the X/Motif 1.2 Libraries Y2K patch (PHSS_13113, PHSS_14040,
and PHSS_16120. While using Events -> Load Local Log Files, the
message "Log Browser module completed abnormally (E1701)"
incorrectly displays. Also, when choosing router types in a local
file configuration the window color obscures the clear display of
router types.

CR 94229: Source route bridging
Using Site Manager to add a frame relay circuit, when source route
bridging is enabled, also defines a new Point-to-Point interface for
the circuit.

CR 95215: Config
Creating an ASN2 config from scratch, then opening and saving the
config file using Site Manager in local mode will cause the router
to fault when the new config is booted on the router.

5.03 Revision 8 corrects the following problems:

CR 33127: Frame relay.
Site Manager does not allow you to apply a bridge filter "forward to
circuit" to a frame relay service record other than the default
service record.

CR 71702: PCAP.
Using the network general sniffer to open a file on a router
converted with Version 1.8 of the packet conversion tool, pktconv,
fails with the message "Bad Record Header."

CR 88721: ATM.
The packet conversion tool, pktconv, does not convert PCAP files to
sniffer ATC files.

CR 94176: Site Manager.
Site Manager will not open a configuration in local/remote mode if
unrecognizable MIB instances exist in the saved config file.

5.03 Revision 7 corrects the following problem:

CR 22893: Site Manager.
PC Site Manager incorrectly allows you to set the month value to
zero in the Router Date and Time window and then sets the month
to 1.

5.03 Revision 6 corrects the following problem:

CR 83757: Multiline.
A WFCFG program error occurs when you delete and then add a
multiline circuit using Site Manager on Windows 95. This issue
does not affect UNIX platforms.

5.03 Revision 5 corrects the following problems:

CR 32557: Switched Services.
When you enter 2400 for the End Time in the Circuit Time of Day
Schedule, the message "Invalid Data for End of Time" appears.
Also, no help is available for the Availability Mode parameter.

CR 32604: Site Manager.
This is an enhancement request to make the Add Circuit window on
the PC appear the same as that on UNIX. On UNIX, circuits that you
can select are highlighted and the ones you cannot select are grayed
out. On the PC, the circuits that you can select are highlighted and
the ones you cannot select are hidden.

CR 33614: SDLC.
When you configure an SDLC circuit using dynamic mode, the two
following MIB attributes in the wfSdlcLSAdminEntry MIB do not get
updated:

wfSdlcLSAdminEntry.wfSdlcLSAdminIfIndex.2.64 = 0
wfSdlcLSAdminEntry.wfSdlcLSAdminAddress.2.64 = 0

As a result, the SDLC circuit never comes up.

CR 33679: IP.
Site Manager incorrectly allows you to configure HP Probe as an ARP
type on sync media. HP probe is supported on Ethernet only.

CR 34736: PPP.
Site Manager causes a general protection fault on a DOS platform
when you change the PPP MRU of a dial circuit in local mode only and
then save the configuration file.

CR 35732: Switched Services.
The outbound phone number attributes wfSwservOutPhoneNumAggrChanCnt
and wfSwservOutPhoneNumChannelType in wfSwservOutPhoneNumEntry are
being set with incorrect values by Site Manager resulting in an
invalid configuration file.

CR 72741: IP/OSPF.
When you set OSPF or IP global variables in Site Manager/Windows 95
causes SNMP sets to transmit continuously. You must restart Windows
95 to recover from this condition.

CR 74522: SNMP.
If a hostname in a well-known connections list is no longer able to
be resolved (e.g., the router hostname is changed or is no longer
present), Site Manager generates an SNMP request directed to a
BROADCAST address (destination MAC=FF:FF:FF:FF:FF:FF and destination
IP=255.255.255.255). The broadcasts are sent each time you click on
the unresolved hostname in the well-known connections list. This is
a problem because other devices on the same LAN receive the
broadcast and, if they use different communities than the router,
generate authentication traps back to their trap receivers.

CR 79896: Site Manager.
When you configure a router redundancy hot standby member
configuration and save it using the Save As option, Site Manager
displays the Primary Save and Secondary Save buttons. This might
cause confusion because the user does not require a primary or
a secondary configuration file.

CR 80826: Site Manager.
This is an enhancement request to increase the number of
configuration files displayed in Site Manager on UNIX. Currently,
when you go to Tools > Configuration Manager > Local File, the Open
Configuration File window does not display all files in a directory
if the total is greater than 500. This limit has been increased to
2,048.

CR 81675: Site Manager.
Site Manager incorrectly creates an interface redundancy instance on
a circuit when you select Change Lines to change the circuit name.

CR 81726: Traffic Filters.
Site Manager does not allow you to delete traffic filters.

CR 82245: Report Generator.
Attempting to run smcfgrpt from the command line in Report Generator
produces a core dump at the end of the program. This problem does
not occur when you start Report Generator in Site Manager.

CR 82470: Report Generator.
In the output produced by Report Generator, the display format of
wfIpRipAnnounceNetworks and wfIpRipAcceptNetworks is inconsistent
(wfRipAnnounceNetworks is displayed in hex only). Both entries
should be displayed in both dotted decimal and hexadecimal formats.
Without the dotted decimal format, you must perform the conversion
manually.

CR 82695: IP.
Before SNMP traffic starts, in order to validate the router IP
address passed to the Configuration Manager, a test applies the
subnet mask to the specified router IP address. The test checks
whether the IP address is misconfigured to be a broadcast or network
address (all ones or all zeros), but it applies the subnet mask of
the Site Manager workstation against the IP address of the router.
This test would be valid if the router and the Site Manager station
were on the same subnet, but problems arise if they are on different
subnets.

CR 82907: Site Manager.
For Site Manager running on UNIX systems, a hard-coded limit
prevents dynamic configuration from launching if the number of local
interfaces on the UNIX system exceeds eight. When this occurs, the
message "Unable to run configuration module. (E1602)" displays. This
problem affects only dynamic configuration mode launched against
router connection entries that are IP addresses rather than
resolvable hostnames. Other configuration modes (remote file, local
file) are not affected.

CR 84308: ISDN.
Site Manager does not allow you to configure a dial backup line. The
PhoneOut menu also lists ISDN as the only choice under Dial Type.

CR 84371: RIP.
Site Manager incorrectly allows the entry of a noncontiguous subnet
mask when defining a RIP Accept Policy filter on Windows NT and UNIX
platforms. For releases prior to 11.03/3, such an entry corrupts the
LSDB and resets the OSPF throughout the network.

5.03 Revision 4 corrects the following problems:

CR 71031: BGP.
In order for BGP Routes to be exported to the OSPF Link State Data
Base, the BGP Intra-AS parameter must be set to Disabled. By
default, this parameter is set to Enabled. If you disable this
parameter dynamically, Site Manager generates multiple bus errors
and a watchdog.

CR 75254: SNMP
When you click on OK from the Edit Adapter Module 2, 56/64K DUS CSU
Parameters window, Site Manager sets the attribute
wfSyncExternalClkSpeed to the value determined by the Option Mode
parameter, even if the attribute’s value has not changed.

CR 75303: X.25
When you add an X.25/PTOP line, the Connection ID parameter defaults
to 0. The range of valid values is from 1 to 255.

CR 75341: Sync.
When you select the Values button for the Sync B Channel Override
parameter, the message "Sorry, No additional information available"
appears. The valid values are BCHANNEL1, BCHANNEL2, Default, and
FLOATINGB.

CR 75561: IP.
When you reorder a small traffic filter, in ascending or
descending order, past a large traffic filter with many IP addresses
within the same filter, a memory fault condition occurs on the
router. In some cases, Site Manager unloads IP from the slot.

CR 75894: Protocol Priority.
When you apply a new Protocol Priority outbound filter,
Configuration Manager faults and then terminates. The fault
occurs on the PC only.

CR 76000: ISDN.
When you configure a MCT-1 port for PRI and you enable RFC 1661
compliance, if you change the MRU size, the information message
"Please make sure that the SYNC MTU is >= PPP MRU + 56 bytes"
appears for each channel on the MCT-1 port. The message should only
appear once.

CR 78156: Source Route Bridge.
If you configure a sync interface for source route bridging, the
Source Routing Interfaces window from the Protocols pull-down menu
option on the Frame Relay Service List window shows all 0s for the
sync interface.

CR 78722: IPX.
If you enter a valid DLCI into the IPX adjacent host
definition, Site Manager displays an error message, indicating that
you have entered an incorrect number range or format.

5.03 Revision 3 corrects the following problems:

CR 28400: Router Files Manager.
If you enter an invalid community name in the Router Files Manager
window, Site Manager displays the error message "Unable to reach
Router." When you click on OK, the same message appears again.

CR 34891: IP.
After you configure 56 RIP Accept Policy Filters, a GPF error occurs
on the PC, or a segmentation fault occurs on the UNIX workstation.

CR 35695: Site Manager.
When you attempt to delete an SNMP community, the message "SNMP Set
Error" appears. When you press OK or Cancel to exit the message, the
message reappears.

CR 71347: DLSw.
When you configure an 802.5 service record for DLS/LLC/SRB, Site
Manager incorrectly sets the DLS DLC type (wfDlsInterfaceEntry.
wfDlsInterfaceDlcType) to 3 (learning bridge); the DLS DLC type
should be set to 2 (source route).

CR 72071: FDDI.
When you change a slot containing an FDDI module to Empty
Slot, Site Manager does not delete the following enhanced
FDDI MIB objects from the configuration file:
wfFddiSmtExtEntry, wfFddiSmtActionEntry, wfFddiMacExtEntry,
wfFddiPathExtEntry, wfFddiPortExtEntry, and
wfFddiPortActionEntry.

CR 72689: Frame Relay.
The IFTF (Inter Frame Time Fill) must be set to "7E" when you
configure Frame Relay on a BRI Leased Line and use a Japanese NTT
Frame Relay network. This requires setting the MIB
wfSyncEntry.wfSyncForceIFTF to 2. Added the ability to set this MIB
attribute via Site Manager.

CR 73066: TCP.
The delete confirmation windows for Telnet server and Telnet client
contain a typo.
CR 73309: BGP.
Site Manager does not allow you to change the value for the "Route
Preference" parameter in a BGP4 accept policy.

CR 73799: LLC.
The LLC circuit option under the Circuit Definition window is grayed
out after you select the LLC2 circuit option from the LLC circuit
pull-down menu.

CR 75049: IP.
When you delete BGP-3 from a configuration, Site Manager deletes all
the IBGP peers.

5.03 Revision 1 corrects the following problems:

CR 30180: IP.
When you list the Announce Policy Filters, Site Manager duplicates
the entries.

CR 33513: Events Manager.
The events log displays the incorrect date for any year before the
leap year.

CR 33829: Logical Lines.
If you UNSELECT the MCT card from the "Add Circuit" window, Site
Manager does not allow you to re-select it.

CR 34872: PPP.
SYNC MTU must be at least 56 bytes greater than PPP MRU.

CR 34913: Source Route Bridge.
After you configure source route bridge on a dial on demand
circuit, the source route interface window displays zeroes in all
fields for that circuit.

CR 34951: Static Routes.
If you attempt to configure a subnetted static route, such as
12.12.12.0/255.255.255.0 or 192.32.37.0/255.25.255.240, Site Manager
displays the message "IP Address/Subnet Mask are misconfigured" and
does not add the route. Site Manager does allow you to add networks
with a natural mask, such as 12.0.0.0/255.0.0.0.

CR 35142: OSPF.
When you change any field in the "Edit OSPF Global Parameters"
window, Site Manager resets the slot mask, causing OSPF to recycle.

CR 35251: Site Manager.
Defaults for MIBs are read from cdl-generated ASCII output files.
Default values for MIBs of type GAUGE are represented as signed
numbers. Site Manager reads type INTEGER values as long
unsigned numbers.

CR 35348: Router Redundancy.
Clicking on "Edit Lines" for ethernet and 100Base-T router redundant
interfaces brings up the 100Mb/s CSMA/CD parameters window, which is
incorrect. Site Manager should bring up the Edit CSMA/CD
parameters window. If you click on OK, Site Manager displays the
following message: "ERROR: Invalid data entered for Interface Line
Speed". To exit the window, you must click on Cancel or enter an
incorrect value for line speed.

CR 35354: PPP.
For a dial backup circuit, if you enable the "RFC1661 Compliance"
field in the "PPP Line List" window, wfSwservOptsRfc1661Compliance
must be set to the same value as wfPppLineRfc1661Compliance
internally.

CR 35580: LLC2 traffic filters
Site Manager lets you create LLC2 traffic filters under the wrong
circuit number. If you create an LLC2 traffic filter by selecting
LLC Circuit > LLC2 Circuit and then Protocols > LLC2 Traffic
filters, the filter will not work because Site Manager uses a
circuit number that is different from the number assigned to
this interface.

CR 35692: SNMP.
When running Configuration Manager in dynamic mode, the wfProtocols
MIB gets set to the value to which it is already set. The set does
not affect service.

CR 35797: BGP.
Although the "Multi hop EBGP connection" parameter is set to
enabled, you cannot configure BGP peers that are not on the same
subnet.

CR 35899: BGP.
When you create a BGP peer to a circuitless IP address, invalid and/
or multiple instances of wfCircuitNameEntry are created.

CR 35936: IP.
When you use a circuitless IP address with an instance number of 1
(under wfCircuitNameEntry), Site Manager can cause the router to
unload and reload certain protocols.

CR 72781: FireWall.
The FireWall product was introduced in 11.02/Rev 2. When you use
Site Manager to connect to a router that is running a release
earlier than 11.02/Rev 2, the FireWall menu should be unavailable.