Worldwide Customer Service - Lifecycle Support for Adaptive Networking

Site Manager Revision 6.01/Revision 1

Site Manager Revision 6.01/Revision 1 is a post 6.00 revision. This version 
is backwards compatible and supports the following router versions:

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.

=============================================================================
6.01 Revision 1 corrects the following problems:
=============================================================================
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, the FireWall menu should be unavailable.

CR 71674: APPN.
          If you use Site Manager to configure an APPN interface over frame
          relay using source routing, and you add an Adjacent Link Station,
          Site Manager incorrectly sets the MIB attribute wfAppnNodeDlcType to
          3 (transparent bridging). The correct setting for this attribute is
          2 (source routing).

CR 72630: Token Ring.
          When you attempt to configure traps on a token ring interface, that
          interface is not available in "Available Entities."

CR 73066: TCP.
          The delete confirmation windows for Telnet server and Telnet client
          contain a typo.

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 36017: Image Builder.
          If you are using Image Builder in Site Manager Software
          Version 6.01 to modify a Router Software Version 11.03
          router image, the following error message appears: "The
          cross-referenced file is not up-to-date relative to the
          image stamp."

CR 72567: DLSw.
          When you configure DLSw, Site Manager sets the TCP max
          window size to 1 (wfTcp.18.0 = 1). The value should be set
          to the same value for which wfDlsTcpWindowSize is
          configured.

CR 71137: DLSw.
          When you add DLSw to an X.25/QLLC service record, Site
          Manager displays the following error message: "Data entered
          for ’(null)’ is inconsistent with the packet level. Do you
          want the related packet/service record attributes set
          correctly?" When you click the Apply button, Site Manager core dumps
          or GPFs.

CR 35781: DLSw.
          If the router is running pre-BayRS 12.00 router code, the DLSw
          Backup Peer MIB attributes on the DLSw Peer Configuration window are
          incorrect.

CR 31321: DLSw.
          If you configure a local device with maxdata on the DLSw local
          device window, when you exit the window, an error message appears,
          warning you that the maxdata is larger then the sync MTU. This
          happens only in dynamic mode.

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

CR 35239: X.25.
          When you configure X.25/QLLC Maps, Site Manager leaves the
          Generate XID field empty. To save the window, you must
          enter ENABLE in the Generate XID field.
          However, Site Manager incorrectly sets the MIB entry for
          this field to a number between of 15-20, and the
          configuration does not work. To correct the problem, set the
          MIB attribute for the Generate XID field to 1.

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

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 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 34872: PPP.
          SYNC MTU must be at least 56 bytes greater than PPPMRU.

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 30906: IP.
          A problem exists when you apply 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 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 33589: IPX.
          When you delete IPX from a WAN interface (e.g., frame relay or PPP),
          Site Manager does not remove the IPX circuit instance completely.

CR 34024: BOT.
          This is an enhancement request to enable the Bisync
          protocol to support more leading SYNC characters. Currently,
          the BISYNC code is hardcoded for 2 leading SYNC
          characters. The customer’s Bisync controller requires 7 SYNC
          characters. The router software code requires configurable leading
          SYNC characters in order to interoperate.

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

CR 35918: Switched Services.
          When you delete a Dial On Demand schedule entry,
          the following error message appears: "Function was not found
          (xref_standby_tod_delete)." This message occurs only when you use
          Site Manager to configure an 11.02 or an 11.01 MIB attribute.

No CR:    Dial on Demand.
          If you configure scheduled Dial on Demand, and you accept the
          default of 2400 for the End of Time parameter, an error occurs.

Feedback | Service Search | ERC

/tr>