Bay Networks BayStream 6.10 is a multiservice software that provides a comprehensive set of features for managing and configuring network devices. It offers a user-friendly interface and a wide range of tools for network management, including configuration, monitoring, and troubleshooting. With BayStream 6.10, you can easily manage your network devices, ensuring optimal performance and reliability.
Bay Networks BayStream 6.10 is a multiservice software that provides a comprehensive set of features for managing and configuring network devices. It offers a user-friendly interface and a wide range of tools for network management, including configuration, monitoring, and troubleshooting. With BayStream 6.10, you can easily manage your network devices, ensuring optimal performance and reliability.
December 1997
BayStream Multiservice Software Version 6.10 (Revision 14)
BayStream Site Manager Software Version 6.10 (Revision 14)
BayStream 6.10
(Revision 14)
Release Notes
ii
BayStream Multiservice Software Version 6.10 (Revision 14)
4401 Great America Parkway 8 Federal Street
Santa Clara, CA 95054 Billerica, MA 01821
Copyright © 1988–1997 Bay Networks, Inc.
All rights reserved. Printed in the USA. December 1997.
The information in this document is subject to change without notice. The statements, configurations, technical data,
and recommendations in this document are believed to be accurate and reliable, but are presented without express or
implied warranty. Users must take full responsibility for their applications of any products specified in this document.
The information in this document is proprietary to Bay Networks, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance
with the terms of that license. A summary of the Software License is included in this document.
Restricted Rights Legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notice for All Other Executive Agencies
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in
the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Trademarks of Bay Networks, Inc.
ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, Optivity, PPX, Bay Networks, SynOptics,
SynOptics Communications, Wellfleet and the Wellfleet logo are registered trademarks and Advanced Remote Node,
ANH, ARN, ASN, Bay•SIS, BayStack, BayStream, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN,
IP AutoLearn, PathMan, PhonePlus, Quick2Config, RouterMan, SN, SPEX, Switch Node, Bay Networks Press,
the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks, Inc.
Third-Party Trademarks
All other trademarks and registered trademarks are the property of their respective owners.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the
right to make changes to the products described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
Portions of the code in this software product are Copyright © 1988, Regents of the University of California. All rights
reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above
copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials,
and other materials related to such distribution and use acknowledge that such portions of the software were
developed by the University of California, Berkeley. The name of the University may not be used to endorse or
promote products derived from such portions of the software without specific prior written permission.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
In addition, the program and information contained herein are licensed only pursuant to a license agreement that
contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed
by third parties).
BayStream Multiservice Software Version 6.10 (Revision 14)
iii
Bay Networks Software License
This Software License shall govern the licensing of all software provided to licensee by Bay Networks (“Software”).
Bay Networks will provide licensee with Software in machine-readable form and related documentation
(“Documentation”). The Software provided under this license is proprietary to Bay Networks and to third parties from
whom Bay Networks has acquired license rights. Bay Networks will not grant any Software license whatsoever, either
explicitly or implicitly, except by acceptance of an order for either Software or for a Bay Networks product
(“Equipment”) that is packaged with Software. Each such license is subject to the following restrictions:
1. Upon delivery of the Software, Bay Networks grants to licensee a personal, nontransferable, nonexclusive license
to use the Software with the Equipment with which or for which it was originally acquired, including use at any
of licensee’s facilities to which the Equipment may be transferred, for the useful life of the Equipment unless
earlier terminated by default or cancellation. Use of the Software shall be limited to such Equipment and to such
facility. Software which is licensed for use on hardware not offered by Bay Networks is not subject to restricted
use on any Equipment, however, unless otherwise specified on the Documentation, each licensed copy of such
Software may only be installed on one hardware item at any time.
2. Licensee may use the Software with backup Equipment only if the Equipment with which or for which it was
acquired is inoperative.
3. Licensee may make a single copy of the Software (but not firmware) for safekeeping (archives) or backup
purposes.
4. Licensee may modify Software (but not firmware), or combine it with other software, subject to the provision
that those portions of the resulting software which incorporate Software are subject to the restrictions of this
license. Licensee shall not make the resulting software available for use by any third party.
5. Neither title nor ownership to Software passes to licensee.
6. Licensee shall not provide, or otherwise make available, any Software, in whole or in part, in any form, to any
third party. Third parties do not include consultants, subcontractors, or agents of licensee who have licensee’s
permission to use the Software at licensee’s facility, and who have agreed in writing to use the Software only in
accordance with the restrictions of this license.
7. Third-party owners from whom Bay Networks has acquired license rights to software that is incorporated into
Bay Networks products shall have the right to enforce the provisions of this license against licensee.
8. Licensee shall not remove or obscure any copyright, patent, trademark, trade secret, or similar intellectual
property or restricted rights notice within or affixed to any Software and shall reproduce and affix such notice on
any backup copy of Software or copies of software resulting from modification or combination performed by
licensee as permitted by this license.
Note:
This is Bay Networks basic license document. In the absence of a
software license agreement specifying varying terms, this license -- or the
license included with the particular product -- shall govern licensee’s use of
Bay Networks software.
iv
BayStream Multiservice Software Version 6.10 (Revision 14)
Bay Networks Software License
(continued)
9. Licensee shall not reverse assemble, reverse compile, or in any way reverse engineer the Software. [Note:
For
licensees in the European Community, the Software Directive dated 14 May 1991 (as may be amended from time
to time) shall apply for interoperability purposes. Licensee must notify Bay Networks in writing of any such
intended examination of the Software and Bay Networks may provide review and assistance.]
10. Notwithstanding any foregoing terms to the contrary, if licensee licenses the Bay Networks product “Site
Manager,” licensee may duplicate and install the Site Manager product as specified in the Documentation. This
right is granted solely as necessary for use of Site Manager on hardware installed with licensee’s network.
11. This license will automatically terminate upon improper handling of Software, such as by disclosure, or Bay
Networks may terminate this license by written notice to licensee if licensee fails to comply with any of the
material provisions of this license and fails to cure such failure within thirty (30) days after the receipt of written
notice from Bay Networks. Upon termination of this license, licensee shall discontinue all use of the Software
and return the Software and Documentation, including all copies, to Bay Networks.
12. Licensee’s obligations under this license shall survive expiration or termination of this license.
BayStream Multiservice Software Version 6.10 (Revision 14)
v
About This Guide
This document describes anomalies resolved in BayStream™ Multiservice Software Version 6.10
(Revision 14) and BayStream Site Manager 6.10 (Revision 14).
Acronyms
ATM asynchronous transfer mode
BGP Border Gateway Protocol
DLCI data link connection identifier
DLSw data link switching
DTE data terminal equipment
DVMRP Distance Vector Multicast Routing Protocol
EGP Exterior Gateway Protocol
FR frame relay
FRF Frame Relay Forum
FRSW frame relay switch
FTP File Transfer Protocol
IGMP Interior Gateway Management Protocol
IP Internet Protocol
ISDN Integrated Services Digital Network
LED light emitting diode
LLCP Logical Link Control Protocol
NMS network management station
OSPF Open Shortest Path First Protocol
PCAP Packet Capture
PPP Point-to-Point Protocol
PVC permanent virtual circuit
BayStream 6.10 (Revision 14) Release Notes
vi
BayStream Multiservice Software Version 6.10 (Revision 14)
RARP Reverse Address Resolution Protocol
SDLC Synchronous Data Link Control
SR source routing
STA Statistical Thresholds and Alarms
SVC switched virtual circuit
SWSERV Switched Access Services
TNC Telnet Client
VCI virtual circuit identifier
VPI virtual path identifier
Ordering Bay Networks Publications
To purchase additional copies of this document or other Bay Networks publications, order by part
number from Bay Networks Press
™
at the following numbers:
• Phone--U.S./Canada: 888-422-9773
• Phone--International: 510-490-4752
• FAX--U.S./Canada and International: 510-498-2609
The Bay Networks Press catalog is available on the World Wide Web at
support.baynetworks.com/Library/GenMisc
. Bay Networks publications are
available on the World Wide Web at
support.baynetworks.com/Library/tpubs
.
About This Guide
BayStream Multiservice Software Version 6.10 (Revision 14)
vii
Bay Networks Customer Service
You can purchase a support contract from your Bay Networks distributor or authorized reseller, or
directly from Bay Networks Services. For information about, or to purchase a Bay Networks service
contract, either call your local Bay Networks field sales office or one of the following numbers:
Information about customer service is also available on the World Wide Web at
support.baynetworks.com
.
How to Get Help
If you purchased a service contract for your Bay Networks product from a distributor or authorized
reseller, contact the technical support staff for that distributor or reseller for assistance.
If you purchased a Bay Networks service program, call one of the following Bay Networks Technical
Solutions Centers:
Region Telephone number Fax number
United States and
Canada
800-2LANWAN; then enter Express
Routing Code (ERC) 290, when prompted,
to purchase or renew a service contract
978-916-8880 (direct)
978-916-3514
Europe 33-4-92-96-69-66 33-4-92-96-69-96
Asia/Pacific 61-2-9927-8888 61-2-9927-8899
Latin America 561-988-7661 561-988-7550
Technical Solutions Center Telephone number Fax number
Billerica, MA 800-2LANWAN 978-916-3514
Santa Clara, CA 800-2LANWAN 408-495-1188
Valbonne, France 33-4-92-96-69-68 33-4-92-96-69-98
Sydney, Australia 61-2-9927-8800 61-2-9927-8811
Tokyo, Japan 81-3-5402-0180 81-3-5402-0173
BayStream Multiservice Software Version 6.10 (Revision 14)
1
BayStream Version 6.10
(Revision 14)
This Bay Networks
®
report describes fixes to anomalies found in BayStream Multiservice Software
Version 6.10 (Revision 14) and BayStream Site Manager Software Version 6.10 (Revision 14).
Anomaly: OSPF Max Aged external type 1 routes are not getting aged out of the IP routing
table.
Number: 32438
Description: When a router learns the same route from two sources (for example, an external type
1 with a mask of /24 and an external type 2 with a mask of /24) and an update is not
received for the external type 1 route, it gets max aged in the OSPF LSDB
but not
aged out of the IP routing table.
Resolved: The software is modified to properly manage OSPF routes.
________________________________________________________________________________
Anomaly: The Statistical Data Collection and Reporting software calculated the statistics
file to be much larger than it was.
Number: 32670
Description: When the Statistical Data Collection and Reporting software attempted to write a file
to the flash, it calculated the file size to be larger than it actually was. The file was not
written to the flash and a warning message was logged.
Resolved: The software is revised to calculate the file size correctly.
________________________________________________________________________________
2
BayStream Multiservice Software Version 6.10 (Revision 14)
Anomaly: The Statistical Data Collection and Reporting software record header showed
the wrong file size.
Number: 30068
Description: The Statistical Data Collection and Reporting software did not insert the correct file
size in the record header because the congestion control record size was also
calculated for a circuit that did not have congestion control enabled.
Resolved: The software now calculates the files size and inserts it in the record header
correctly.
________________________________________________________________________________
Anomaly: The wfStatsDcLbcEntry counters line byte counter stops updating.
Number: 31724
Description: The wfStatsDcLbcEntry counters stop updating after several days of successful
updates. If the line byte count
is unloaded from the slot and reloaded,
wfStatsDcLbcEntry counters update for several days. Then the problem reoccurs.
Resolved: The software is modified to update line byte count correctly.
________________________________________________________________________________
Anomaly: When LAPF is disabled, a Trap 12 should be generated.
Number: 33043
Description: When the LAPF entry is disabled, a Trap 12 was not generated. A Trap 12 should be
generated so that NMS is notified of the change of state for the L2 entry.
Resolved: The software is modified to generate the correct trap message when LAPF is
disabled.
________________________________________________________________________________
BayStream Multiservice Software Version 6.10 (Revision 14)
3
Anomaly: The SYNC port did not decode the Calling Party Information Element properly.
Number: 32831
Description: A SYNC port was configured with a local E.164 address of 2132 and a Calling Party
Information Element was set to mandatory. When the SETUP message was sent with
the proper calling party number, the call could not be setup. The slot generates a
debug log message. Although the slot did not decode the information element
properly, the slot did process outgoing calls correctly.
The software incorrectly managed the value of the extension bit in the calling address
information element (IE). This prevented determining the calling E.164 address
correctly.
Resolved: The software is modified to correctly determine the calling E.164 address.
________________________________________________________________________________
Anomaly: When a call request message goes to the egress port, the DLCI should not be
specified.
Number: 33139
Description: When a SETUP message sent to an Egress BNX port (the Called port) across the
frame relay network, the DLCI information element must contain the DLCI of the
ingress BNX port (the calling port) and should not be used to determined the DLCI at
the egress BNX port. The egress BNX port should select the next available DLCI
locally.
Resolved: The software code is modified so that egress port selects the next available DLCI
locally.
________________________________________________________________________________
4
BayStream Multiservice Software Version 6.10 (Revision 14)
Anomaly: If throughput negotiation is in force, the LLCP IE should be included in the
CONNECT message
Number: 33431
Description: Two incoming calls were in a proceeding state with the link layer core parameters
information element included in the setup message from the DTE. The incoming
throughput was less than the maximum incoming throughput per SVC in each of the
setup messages. The sum of the setup messages was greater than the total incoming
negotiable throughput. When the first SVC connected, it connected at the requested
rate. The second SVC connected at the minimum allowable rate. No indication was
given to the calling user that the negotiation had taken place for the second
connection. The software should have included the LLCP information element in the
connect message for the negotiated call. Presently, the LLCP is not being included in
the connect message for this call.
Resolved: The should not include the LLCP information element in the connect message as
described. If LLCP information is not included in the connect message from the
called user, but is included in the setup message from the network (to the user’s
direction), the call should be dropped by the network.
________________________________________________________________________________
Anomaly: The throughput is calculated incorrectly from the committed burst rate.
Number: 32426
Description: The throughput is calculated incorrectly from the committed burst rate.
Resolved: The software is modified to calculate throughput correctly.
________________________________________________________________________________
BayStream Multiservice Software Version 6.10 (Revision 14)
5
Anomaly: A virtual circuit cannot be used for an SVC following the dynamic deletion of a
PVC.
Number: 32466
Description: In a configuration with 250 PVCs in the range of 32 through 281, SVCs were
connecting on the slot beginning at 991 and decrementing. Prior to the SVCs reaching
PVC crossover, when the PVC entries were deleted, SVC requests to use them were
rejected and a warning message was generated that indicated that the software would
create a virtual circuit that already existed for DLCI 259.
Resolved: The software is modified to check the availability of the DLCI and virtual circuit.
________________________________________________________________________________
Anomaly: Burst size was calculated incorrectly for SVCs
Number: 32563
Description: A circuit with a PVC contained the correct value for burst size, but a connected SVC
had a different value for burst size. The values should be the same. However, because
the wfFrSwVcEntry.wfFrSwVcInBc parameter is defined in bytes, the calculations
were skewed by a factor of 8.
Resolved: The software is modified to calculate burst size correctly.
________________________________________________________________________________
Anomaly: According to FRF.4, the Preferred/Exclusive bit should always be 1, not 0.
Number: 32661
Description: When updating the DLCI IE, the SVC software did not always set the Preferred/
Exclusive bit to 1.
Resolved:
The software is modified to set the Preferred/Exclusive bit to 1 when it updates the
DLCI information element.
________________________________________________________________________________
6
BayStream Multiservice Software Version 6.10 (Revision 14)
Anomaly: The BayStream software generated an event message bearing the incorrect cause
code.
Number: 33790
Description: When the BayStream software received a SETUP message in which the calling party
address was not identical to the local port address, the call request was rejected with a
message bearing a cause code that indicated “Invalid IE.” In this case, it would be
more accurate to issue a rejection message with a cause code indicating “Unallocated
(unassigned) number.”
Resolved: The BayStream software is modified to generate a message including the cause
code UNASSIGNED_NUMBER when it receives a SETUP message in which the
calling party address is not identical to the local port address.
__________________________________________________________________________
Anomaly: The FRSW event message that is generated when the BayStream software
receives a SETUP message bearing an incorrect calling party address should
include the incorrect address.
Number: 33791
Description: When the BayStream software encountered a SETUP message in which it could not
determine the calling party address, it generated the following FRSW event message:
# 2: 10/10/97 23:05:45.769 INFO SLOT 13 FRSW Code: 184
cct 67, signaling gate calling address IE error: can't find calling address in local table
on call reference 94.
The event message would be more informative if it included the offending address.
Resolved: Two event messages have been added to the BayStream software to provide more
information in such cases.
__________________________________________________________________________
Anomaly: The
-l
option of the
diag
command did not work for the ARE/DS3 module.
Number: 28699
Description: The diag -l option did not clear the diagnostic LEDs on the ARE/DS3 module. This
option currently works with the FREs.
Resolved: The diag -l command is implemented for the ARE/DS3 module.
________________________________________________________________________________
BayStream Multiservice Software Version 6.10 (Revision 14)
7
Anomaly: The FR entity is not available in the Site Manager Trap Configuration menu.
Number: 32264
Description: The FR entity was not available in the Site Manager Trap Configuration menu.
Therefore, this trap event could not be sent to the SNMP Manager. In addition, the
following entities should be included in the Trap Configuration menu options: ATM,
ATMINTF, BGP3, BGP4, BGP,DVMRP, EGP, FTP, IGMP, ISDN, PCAP, PING, PPP,
RARP, SR, ST2, SWSERV,TELNET, TNC, WCP.
Resolved: All the entities mentioned in the description have been added to the Site
Manager Trap Configuration menu.
________________________________________________________________________________
Anomaly: Site Manager when attempting to configure Multiline on three QMCT logical
lines.
Number: 32286
Description: Site Manager failed to configure Multiline on three QMCT1 logical lines.
Configuring Multiline on two logical lines was successful but the third logical line
failed.
Resolved: The software is modified to enable configuring multiline on three QMCT logical
lines.
________________________________________________________________________________
Anomaly: The STA entity was not available in the Site Manager Trap Configuration menu.
Number: 32474
Description: The STA entity was not available in the Site Manager Trap Configuration menu.
However, STA traps did occur when "All Entities" was selected.
Resolved: The STA entity has been added to the Site Manager Trap Configuration menu.
________________________________________________________________________________
8
BayStream Multiservice Software Version 6.10 (Revision 14)
Anomaly: Site Manager displayed the wrong part number for the DS3 card.
Number: 32581
Description: Site Manager displayed is AG13110114 for the DS3 card. The correct part number is
AG13110115.
Resolved: The software now displays the correct part number for the DS3 card.
________________________________________________________________________________
Anomaly: The LAPF entity is not available in the Site Manager Trap Configuration menu.
[RVA V7-005]
Number: 33031
Description: The LAPF entity is not available in the Site Manager Trap Configuration menu. To
monitor SVC functionality, the FRSW and ALL options must be picked.
Resolved: The LAPF entity has been added to the Site Manager Trap Configuration menu.
________________________________________________________________________________
Anomaly: Site Manager deleted each wfFrSwVcEntry with FRSW/Interworking with 0/32
VPI.
Number: 33888
Description: If a Frame Relay to ATM Interworking PVC was configured using VPI/VCI 0/32, and
Site Manager was used to delete the same PVC, Site Manager deleted each
wfFRSwVcEntry until it found the corresponding wfFRSwVcEntry that matched the
initial delete.
Resolved: The software is modified to delete the correct PVC.
_________________________________________________________________________________
-
1
-
2
-
3
-
4
-
5
-
6
-
7
-
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
Bay Networks BayStream 6.10 Release note
- Type
- Release note
- This manual is also suitable for
Bay Networks BayStream 6.10 is a multiservice software that provides a comprehensive set of features for managing and configuring network devices. It offers a user-friendly interface and a wide range of tools for network management, including configuration, monitoring, and troubleshooting. With BayStream 6.10, you can easily manage your network devices, ensuring optimal performance and reliability.
Ask a question and I''ll find the answer in the document
Finding information in a document is now easier with AI
Related papers
-
Bay Networks BayStream 7.3 Release note
-
-
-
-
Bay Networks 5380 User manual
-
-
-
Nortel Networks 13.03 User manual
-
Other documents
-
Avaya Event Messages for Routers and BNX Platforms User manual
-
-
-
-
-
-
-
-
-